fedup --product=nonproduct --network 22 is upgrading to the unreleased fc23 !!!
jd1008
jd1008 at gmail.com
Fri Sep 18 01:27:03 UTC 2015
On 09/17/2015 06:21 PM, Rick Stevens wrote:
> On 09/17/2015 03:41 PM, jd1008 wrote:
>>
>>
>> On 09/16/2015 11:40 AM, Gordon Messmer wrote:
>>>
>>> yum repolist
>> $ yum repolist
>> Loaded plugins: aliases, auto-update-debuginfo, changelog,
>> fastestmirror, filter-data, fs-snapshot, keys, langpacks, list-data,
>> : local, merge-conf, post-transaction-actions,
>> priorities, protectbase, refresh-packagekit, refresh-updatesd,
>> : remove-with-leaves, rpm-warm-cache, show-leaves,
>> tmprepo, tsflags, upgrade-helper, verify, versionlock
>> _local | 2.9 kB 00:00:00
>> fedora/20/x86_64/metalink | 3.5 kB 00:00:00
>> fedora-debuginfo/20/x86_64/metalink | 2.4 kB 00:00:00
>> fedora-debuginfo | 3.1 kB 00:00:00
>> fedora-source/20/x86_64/metalink | 2.8 kB 00:00:00
>> fedora-source | 3.0 kB 00:00:00
>> google-earth | 951 B 00:00:00
>> rpmfusion-free | 3.3 kB 00:00:00
>> rpmfusion-free-debuginfo | 2.7 kB 00:00:00
>> rpmfusion-free-source | 2.7 kB 00:00:00
>> rpmfusion-free-updates | 3.3 kB 00:00:00
>> rpmfusion-nonfree-updates | 3.3 kB 00:00:00
>> skype | 1.2 kB 00:00:00
>> updates/20/x86_64/metalink | 3.3 kB 00:00:00
>> updates-debuginfo/20/x86_64/metalink | 2.3 kB 00:00:00
>> updates-debuginfo | 3.0 kB 00:00:00
>> updates-source/20/x86_64/metalink | 2.6 kB 00:00:00
>> updates-source | 3.7 kB 00:00:00
>> (1/4): updates-debuginfo/20/x86_64/primary_db | 859 kB 00:00:01
>> (2/4): fedora-debuginfo/20/x86_64/primary_db | 1.9 MB 00:00:02
>> (3/4): updates-source/20/x86_64/primary_db | 1.8 MB 00:00:02
>> (4/4): fedora-source/20/x86_64/primary_db | 4.7 MB 00:00:02
>> (1/4): rpmfusion-free-debuginfo/20/x86_64/primary_db | 49 kB 00:00:01
>> (2/4): rpmfusion-free-source/20/x86_64/primary_db | 87 kB 00:00:01
>> (3/4): updates-source/20/x86_64/updateinfo | 2.0 MB 00:00:01
>> (4/4): updates-source/20/x86_64/pkgtags | 1.6 MB 00:00:00
>> Loading mirror speeds from cached hostfile
>> * fedora: dl.fedoraproject.org
>> * fedora-debuginfo: dl.fedoraproject.org
>> * fedora-source: dl.fedoraproject.org
>> * rpmfusion-free: lug.mtu.edu
>> * rpmfusion-free-debuginfo: lug.mtu.edu
>> * rpmfusion-free-source: lug.mtu.edu
>> * rpmfusion-free-updates: lug.mtu.edu
>> * rpmfusion-nonfree: lug.mtu.edu
>> * rpmfusion-nonfree-updates: lug.mtu.edu
>> * updates: dl.fedoraproject.org
>> * updates-debuginfo: dl.fedoraproject.org
>> * updates-source: dl.fedoraproject.org
>> 0 packages excluded due to repository protections
>> repo id repo name status
>> _local Automatic local repo.
>> (manged by the "local" yum plugin). 64
>> fedora/20/x86_64 Fedora 20 - x86_64
>> 38,597
>> fedora-debuginfo/20/x86_64 Fedora 20 - x86_64 -
>> Debug 6,881
>> fedora-source/20/x86_64 Fedora 20 - Source 0
>> google-earth google-earth 1
>> rpmfusion-free/20/x86_64 RPM Fusion for Fedora
>> 20 - Free 468
>> rpmfusion-free-debuginfo/20/x86_64 RPM Fusion for Fedora
>> 20 - Free - Debug 166
>> rpmfusion-free-source/20/x86_64 RPM Fusion for Fedora
>> 20 - Free - Source 0
>> rpmfusion-free-updates/20/x86_64 RPM Fusion for Fedora
>> 20 - Free - Updates 683
>> rpmfusion-nonfree/20/x86_64 RPM Fusion for Fedora
>> 20 - Nonfree 203
>> rpmfusion-nonfree-updates/20/x86_64 RPM Fusion for Fedora
>> 20 - Nonfree - Updates 561
>> skype Skype Repository 1
>> updates/20/x86_64 Fedora 20 - x86_64 -
>> Updates 22,459
>> updates-debuginfo/20/x86_64 Fedora 20 - x86_64 -
>> Updates - Debug 3,079
>> updates-source/20/x86_64 Fedora 20 - Updates
>> Source 0
>
> Well, you really should be using "dnf repolist", but it's pretty
> obvious you have F20 repos for the most part. You also seem to have
> a local repo and that may be where your F23 stuff is coming from.
I did not create the local repo.
It is present in /etc/yum.repos.d/_local
and it contains:
[_local]
name=Automatic local repo. (manged by the "local" yum plugin).
baseurl=file:/var/lib/yum/plugins/local
enabled=1
gpgcheck=true
# Metadata expire could be set to "never" because the local plugin will
# automatically cause a cache refresh when new packages are added. However
# it's really cheap to check, and this way people can dump stuff in whenever
# and it never gets out of sync. for long.
metadata_expire=1h
# Make cost smaller, as we know it's "local". If you really want to be
sure,
# you can do this ... but the name will do pretty much the same thing,
and that
# way we can also see the other packages (with: --showduplicates list).
# cost=500
But I guarantee you I did not create that beast.
So, I went ahead and deleted it and restarted fedup (which you say
should not behave as it does),
and it still tries to unsuccessfully download the fc23 packages.
So, there must be something else that is telling fedup to download fc23
packages.
>
> I'm still not sure why your fedup is not puking when you specify the
> "--product" flag. It is NOT allowed with the current 0.9.2 versions,
> so the first thing I'd do is sort out which fedup you're getting.
>
> Could you possibly have an old fedup that's getting called instead of
> the one in /bin (perhaps in /usr/local/bin or something)? You could
> try "which fedup" to see which one is being called.
$ type fedup
fedup is a tracked alias for /bin/fedup
$ rpm -qv --whatprovides /bin/fedup
fedup-0.9.2-1.fc20.noarch
And the repos of f21 and f22 show the same version !
See
http://dl.fedoraproject.org/pub/fedora/linux/releases/22/Everything/x86_64/os/Packages/f/
>
> Second, I wouldn't even attempt an update to F22 from here. I would
> upgrade to F21 first with the local repo disabled.
Going the route of first installing f21 and then f22 is way too long
(i.e. time consuming, during which the computer is not being used
for more important things.
> You might be able
> to disable it at the command line:
>
> fedup --network 21 --disablerepo=\*local\*
I deleted it. I do not need it. But still no go.
It IS rather weird that something is telling fedup to go for f23
whereas the command line is telling it to go for f22.
>
> .....
>
> Your machine is in a weird state, so these are somewhat draconian
> measures to try to drag it into currency. The alternative is a good
> backup followed by a fresh install of F22 or whatever you want to use.
Can't argue with that. It is indeed in a weird state.
The other day, there was a process I did not start, which was trying to
install something on the machine. Since I could not trace it's parents,
as it was alredy inherited by PID1, I had to shut down the machine
and reboot very quickly (perhaps not quickly enough).
Sorry to say I did not record the process' name :(
so, not sure what to look for in the log files.
More information about the users
mailing list