Преминаване от StotinkaOS на CentOS
#11
Извинявай

sudo yum update

Също

ls /etc/yum.repos.d
* StotinkaOS SOS хранилища .
* (NEW) Fedora COPR хранилища .

Не отговарям на технически въпроси на ЛС.
Отговори
#12
[Iliyan@iliyan ~]$ sudo yum update
[sudo] password for Iliyan:
Заредени плъгини: fastestmirror, langpacks
Loading mirror speeds from cached hostfile


One of the configured repositories failed (Неизвестно),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7-5.1804.el7.centos.1/x86_64
[Iliyan@iliyan ~]$ ls /etc/yum.repos.d
adobe-linux-i386.repo CentOS-fasttrack.repo epel.repo infonotary.repo
adobe-linux-x86_64.repo CentOS-Media.repo epel.repo.rpmnew StotinkaOS.repo
CentOS-Base.repo CentOS-Sources.repo epel-steam.repo virtualbox.repo
CentOS-CR.repo CentOS-Vault.repo epel-testing.repo
CentOS-Debuginfo.repo elrepo.repo google-chrome.repo
[Iliyan@iliyan ~]$
Отговори
#13
sudo rm /etc/yum.repos.d/StotinkaOS.repo
sudo yum update
* StotinkaOS SOS хранилища .
* (NEW) Fedora COPR хранилища .

Не отговарям на технически въпроси на ЛС.
Отговори
#14
[Iliyan@iliyan ~]$ sudo rm /etc/yum.repos.d/StotinkaOS.repo
[Iliyan@iliyan ~]$ sudo yum update
Заредени плъгини: fastestmirror, langpacks
Loading mirror speeds from cached hostfile


One of the configured repositories failed (Неизвестно),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7-5.1804.el7.centos.1/x86_64
[Iliyan@iliyan ~]$
Отговори
#15
Код:
sudo rm /etc/yum.repos.d/CentOS-Base.repo
sudo rpm -e --nodeps centos-release
sudo rpm -ivh --force http://mirror.centos.org/centos/7/os/x86_64/Packages/centos-release-7-6.1810.2.el7.centos.x86_64.rpm
sudo clean all
sudo yum update
* StotinkaOS SOS хранилища .
* (NEW) Fedora COPR хранилища .

Не отговарям на технически въпроси на ЛС.
Отговори
#16
[Iliyan@iliyan ~]$ sudo rm /etc/yum.repos.d/CentOS-Base.repo
[sudo] password for Iliyan:
[Iliyan@iliyan ~]$ sudo rpm -e --nodeps centos-release
[Iliyan@iliyan ~]$ sudo rpm -ivh --force http://mirror.centos.org/centos/7/os/x86...x86_64.rpm
Retrieving http://mirror.centos.org/centos/7/os/x86...x86_64.rpm
Preparing... ################################# [100%]
Updating / installing...
1:centos-release-7-6.1810.2.el7.cen################################# [100%]
[Iliyan@iliyan ~]$ sudo yum update
Заредени плъгини: fastestmirror, langpacks
Loading mirror speeds from cached hostfile


One of the configured repositories failed (Неизвестно),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7-5.1804.el7.centos.1/x86_64
[Iliyan@iliyan ~]$

Грешка
Отговори
#17
sudo yum clean all
sudo yum update --disablerepo=base
* StotinkaOS SOS хранилища .
* (NEW) Fedora COPR хранилища .

Не отговарям на технически въпроси на ЛС.
Отговори
#18
[Iliyan@iliyan ~]$ sudo clean all
sudo: clean: command not found

[Iliyan@iliyan ~]$ sudo yum update --disablerepo=base
Заредени плъгини: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
epel/x86_64/metalink | 30 kB 00:00:00


One of the configured repositories failed (Неизвестно),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: extras/7-5.1804.el7.centos.1/x86_64
[Iliyan@iliyan ~]$
Отговори
#19
редактирах , беше грешка, виж поста отново
* StotinkaOS SOS хранилища .
* (NEW) Fedora COPR хранилища .

Не отговарям на технически въпроси на ЛС.
Отговори
#20
[Iliyan@iliyan ~]$ sudo yum clean all
Заредени плъгини: fastestmirror, langpacks
Почиствам хранилища: adobe-linux-i386 adobe-linux-x86_64 base elrepo epel epel-steam extras
: google-chrome infonotary updates virtualbox
Cleaning up everything
Maybe you want: rm -rf /var/cache/yum, to also free up space taken by orphaned data from disabled or removed repos
Cleaning up list of fastest mirrors
[Iliyan@iliyan ~]$ sudo yum update --disablerepo=base
Заредени плъгини: fastestmirror, langpacks
Determining fastest mirrors
epel/x86_64/metalink | 30 kB 00:00:00


One of the configured repositories failed (Неизвестно),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: extras/7-5.1804.el7.centos.1/x86_64
[Iliyan@iliyan ~]$
Отговори




Потребители разглеждащи темата: 1 гост(и)