even though i've enabled the updates-testing repo on my fedora 22 system, i can't seem to update to the newer packages in that repo. i've got everything set up exactly as it's described here:
http://forums.fedoraforum.org/showthread.php?t=304760
but even though my updates-testing repo is enabled, i'm told there's "Nothing to do"; however, it *seems* that there is clearly a newer version of a package i'm interested in:
$ dnf info cockpit langpacks: No languages are enabled Last metadata expiration check performed 2 days, 13:40:05 ago on Thu Jul 23 16:13:59 2015. Installed Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.60 Release : 1.fc22 Size : 35 k Repo : @System
From repo : updates
Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
Available Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.62 Release : 1.fc22 Size : 32 k Repo : updates-testing Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
as you can see, the installed version is 0.60, while the updates-testing version is 0.62. so ... what am i misunderstanding here?
rday
Did you run 'dnf update' after enabling the repo? What does 'dnf repolist' say?
On Sun, Jul 26, 2015 at 12:55 PM, Robert P. J. Day rpjday@crashcourse.ca wrote:
even though i've enabled the updates-testing repo on my fedora 22 system, i can't seem to update to the newer packages in that repo. i've got everything set up exactly as it's described here:
http://forums.fedoraforum.org/showthread.php?t=304760
but even though my updates-testing repo is enabled, i'm told there's "Nothing to do"; however, it *seems* that there is clearly a newer version of a package i'm interested in:
$ dnf info cockpit langpacks: No languages are enabled Last metadata expiration check performed 2 days, 13:40:05 ago on Thu Jul 23 16:13:59 2015. Installed Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.60 Release : 1.fc22 Size : 35 k Repo : @System From repo : updates Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
Available Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.62 Release : 1.fc22 Size : 32 k Repo : updates-testing Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
as you can see, the installed version is 0.60, while the updates-testing version is 0.62. so ... what am i misunderstanding here?
rday
--
======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca
Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
On Sun, 26 Jul 2015, Rares Aioanei wrote:
Did you run 'dnf update' after enabling the repo? What does 'dnf repolist' say?
i've run "sudo dnf update" a number of times, tells me "Nothing to do". and:
$ dnf repolist langpacks: No languages are enabled Last metadata expiration check performed 2 days, 13:48:11 ago on Thu Jul 23 16:13:59 2015. repo id repo name status adobe-linux-x86_64 Adobe Systems Incorporated 2 *fedora Fedora 22 - x86_64 44,762 *updates Fedora 22 - x86_64 - Updates 7,590 *updates-testing Fedora 22 - x86_64 - Test Updates 2,265
so it *seems* like updates-testing is enabled. i'm puzzled.
rday
On Dom, 2015-07-26 at 06:04 -0400, Robert P. J. Day wrote:
On Sun, 26 Jul 2015, Rares Aioanei wrote:
Did you run 'dnf update' after enabling the repo? What does 'dnf repolist' say?
i've run "sudo dnf update" a number of times, tells me "Nothing to do". and:
$ dnf repolist langpacks: No languages are enabled Last metadata expiration check performed 2 days, 13:48:11 ago on Thu Jul 23 16:13:59 2015. repo id repo name status adobe-linux-x86_64 Adobe Systems Incorporated 2 *fedora Fedora 22 - x86_64 44,762 *updates Fedora 22 - x86_64 - Updates 7,590 *updates-testing Fedora 22 - x86_64 - Test Updates 2,265
so it *seems* like updates-testing is enabled. i'm puzzled.
Hi, hopefully dnf have good documentation :
googling for : dnf enable
http://dnf-plugins-core.readthedocs.org/en/latest/config_manager.html
so you : dnf config-manager --set-enable updates-testing
and disable with : dnf config-manager --set-disable updates-testing
You also have the choice of enable or disable repos in dnf command line with:
dnf --enablerepo=updates-testing
and you don't need clean metadata anymore, if you want be sure that is used latest metadata use --refresh:
dnf update --refresh
Best regards,
On Sun, 26 Jul 2015, Sérgio Basto wrote:
On Dom, 2015-07-26 at 06:04 -0400, Robert P. J. Day wrote:
On Sun, 26 Jul 2015, Rares Aioanei wrote:
Did you run 'dnf update' after enabling the repo? What does 'dnf repolist' say?
i've run "sudo dnf update" a number of times, tells me "Nothing to do". and:
$ dnf repolist langpacks: No languages are enabled Last metadata expiration check performed 2 days, 13:48:11 ago on Thu Jul 23 16:13:59 2015. repo id repo name status adobe-linux-x86_64 Adobe Systems Incorporated 2 *fedora Fedora 22 - x86_64 44,762 *updates Fedora 22 - x86_64 - Updates 7,590 *updates-testing Fedora 22 - x86_64 - Test Updates 2,265
so it *seems* like updates-testing is enabled. i'm puzzled.
Hi, hopefully dnf have good documentation :
googling for : dnf enable
http://dnf-plugins-core.readthedocs.org/en/latest/config_manager.html
so you : dnf config-manager --set-enable updates-testing
and disable with : dnf config-manager --set-disable updates-testing
You also have the choice of enable or disable repos in dnf command line with:
dnf --enablerepo=updates-testing
and you don't need clean metadata anymore, if you want be sure that is used latest metadata use --refresh:
dnf update --refresh
i did all of the above and, as ed(?) suggested, i may just be unluckily hitting an out-of-date mirror.
rday
This may or may not have anything to do with your problem but it's one I ran into with dnf...
I was trying to update a package I KNEW was in updates-testing (I pushed it myself) but when I asked dnf to update it it gave me the "Nothing to do" message.
After that I tried all the dnf clean metadata|all tricks and it still wouldn't find the updated package. Then I tried dnf --enablerepo=updates-testing list <package> and lo and behold it was there!
Then I released that because it was a library, and another package was dependent on it, that it was refusing to update the package!
While that's certainly the correct behavior, the lack of any sort of USEFUL message to the user is extremely confusing and frustrating.
Thanks, Richard
On Dom, 2015-07-26 at 09:09 -0500, Richard Shaw wrote:
This may or may not have anything to do with your problem but it's one I ran into with dnf...
I was trying to update a package I KNEW was in updates-testing (I pushed it myself) but when I asked dnf to update it it gave me the "Nothing to do" message.
After that I tried all the dnf clean metadata|all tricks and it still wouldn't find the updated package. Then I tried dnf --enablerepo=updates-testing list <package> and lo and behold it was there!
Then I released that because it was a library, and another package was dependent on it, that it was refusing to update the package!
While that's certainly the correct behavior, the lack of any sort of USEFUL message to the user is extremely confusing and frustrating.
You could use --best :
dnf update --refresh --best RPM Fusion for Fedora 21 - Nonfree - Test Updates 45 kB/s | 9.4 kB 00:00 Copr repo for gimp-saveforweb-plugin owned by region51 2.2 kB/s | 2.3 kB 00:01 RPM Fusion for Fedora 21 - Free - Test Updates 30 kB/s | 4.7 kB 00:00 Copr repo for buildsforF21 owned by sergiomb 18 kB/s | 15 kB 00:00 google-talkplugin 21 kB/s | 2.7 kB 00:00 RPM Fusion for Fedora 21 - Free - Updates 633 kB/s | 406 kB 00:00 RPM Fusion for Fedora 21 - Nonfree - Updates 215 kB/s | 148 kB 00:00 RPM Fusion for Fedora 21 - Free 511 kB/s | 508 kB 00:00 google-chrome 29 kB/s | 3.7 kB 00:00 RPM Fusion for Fedora 21 - Nonfree 349 kB/s | 179 kB 00:00 Copr repo for peazip owned by sergiomb 3.8 kB/s | 3.5 kB 00:00 Using metadata from Sun Jul 26 15:25:14 2015 (0:00:22 hours old) Error: nothing provides kernel-uname-r = 4.0.9-200.fc21.x86_64 needed by kmod-VirtualBox-4.0.9-200.fc21.x86_64-4.3.30-1.fc21.2.x86_64
Thanks, Richard
-- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
On Sun, Jul 26, 2015 at 9:28 AM, Sérgio Basto sergio@serjux.com wrote:
On Dom, 2015-07-26 at 09:09 -0500, Richard Shaw wrote:
While that's certainly the correct behavior, the lack of any sort of USEFUL message to the user is extremely confusing and frustrating.
You could use --best :
I would expect silent behavior from a gui/automatic updates, but if a user is specifically asking for something from the command line, shouldn't --best be the default?
Thanks, Richard
On Sun, 26 Jul 2015 09:09:00 -0500, Richard Shaw wrote:
This may or may not have anything to do with your problem but it's one I ran into with dnf...
I was trying to update a package I KNEW was in updates-testing (I pushed it myself) but when I asked dnf to update it it gave me the "Nothing to do" message.
After that I tried all the dnf clean metadata|all tricks and it still wouldn't find the updated package. Then I tried dnf --enablerepo=updates-testing list <package> and lo and behold it was there!
Then I released that because it was a library, and another package was dependent on it, that it was refusing to update the package!
While that's certainly the correct behavior, the lack of any sort of USEFUL message to the user is extremely confusing and frustrating.
It's a known thing and a major design flaw in that tool. It tries to be helpful by hiding some things under the carpet, but that is counter-productive as it causes too much confusion. I think I've seen a few related messages on devel@ list recently, too. The evelopers are aware of it.
With Yum it has been a bit similar with --skip-broken and suggesting that option when running into unresolvable dependencies. Many users follow such suggestions without even trying to understand the broken dependencies, and things can get worse because --skip-broken is not a safe solution.
On 07/26/15 21:50, Robert P. J. Day wrote:
i did all of the above and, as ed(?) suggested, i may just be unluckily hitting an out-of-date mirror.
FWIW, if you look back on "updates-testing reports" you'd see that the last one to have "cockpit" was this one. Konsole output
https://lists.fedoraproject.org/pipermail/test/2015-July/127028.html
And it was for cockpit-0.65-2.fc22 which I suspect was also subsequently withdrawn.
Now, this does raise an interesting question in my mind... If we get reports that show packages being pushed to updates-testing then couldn't/shouldn't we get reports showing withdrawals?
Hello Robert, well if you have enable=1 the update-testing repo try this:
dnf clean all && dnf install <yourpackage>
On Sun, Jul 26, 2015 at 6:55 AM, Robert P. J. Day rpjday@crashcourse.ca wrote:
even though i've enabled the updates-testing repo on my fedora 22 system, i can't seem to update to the newer packages in that repo. i've got everything set up exactly as it's described here:
http://forums.fedoraforum.org/showthread.php?t=304760
but even though my updates-testing repo is enabled, i'm told there's "Nothing to do"; however, it *seems* that there is clearly a newer version of a package i'm interested in:
$ dnf info cockpit langpacks: No languages are enabled Last metadata expiration check performed 2 days, 13:40:05 ago on Thu Jul 23 16:13:59 2015. Installed Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.60 Release : 1.fc22 Size : 35 k Repo : @System From repo : updates Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
Available Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.62 Release : 1.fc22 Size : 32 k Repo : updates-testing Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
as you can see, the installed version is 0.60, while the updates-testing version is 0.62. so ... what am i misunderstanding here?
rday
--
======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca
Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
On 26 July 2015 at 11:03, Carlos Morel-Riquelme leinfeva@fedoraproject.org wrote:
Hello Robert, well if you have enable=1 the update-testing repo try this:
dnf clean all && dnf install <yourpackage>
Please stop telling people to run 'dnf clean all', which will remove cached packages that will often just be downloaded again. If you're concerned about the metadata being up to date just do 'dnf clean metadata'. Or use the '--refresh' option when running 'dnf update'. See dnf(1).
poc
On Sun, 26 Jul 2015, Carlos Morel-Riquelme wrote:
Hello Robert, well if you have enable=1 the update-testing repo try this:
dnf clean all
now, just to be clear, i shouldn't *need* to do this, correct? in any case, i did and:
$ sudo dnf clean all [sudo] password for rpjday: langpacks: No languages are enabled Cleaning repos: fedora updates-testing updates adobe-linux-x86_64 Cleaning up Everything $
so you can see updates-testing is one of the repos being cleaned. next, i tried to update *only* the cockpit package, which again appears to show that updates-testing is being consulted:
$ sudo dnf update cockpit langpacks: No languages are enabled Fedora 22 - x86_64 2.3 MB/s | 41 MB 00:17 Fedora 22 - x86_64 - Test Updates 728 kB/s | 3.1 MB 00:04 Fedora 22 - x86_64 - Updates 530 kB/s | 13 MB 00:24 ... snip ... Last metadata expiration check performed 0:00:00 ago on Sun Jul 26 06:14:26 2015. Dependencies resolved. langpacks: enabled languages are [] Nothing to do. Complete! $
but once again, nothing is done, even though it seems pretty clear there is a newer version of that package in updates-testing:
[rpjday@localhost yum.repos.d]$ rpm -q cockpit cockpit-0.60-1.fc22.x86_64 [rpjday@localhost yum.repos.d]$ dnf info cockpit langpacks: No languages are enabled Last metadata expiration check performed 2 days, 14:04:08 ago on Thu Jul 23 16:13:59 2015. Installed Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.60 Release : 1.fc22 Size : 35 k Repo : @System
From repo : updates
Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
Available Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.62 Release : 1.fc22 Size : 32 k Repo : updates-testing Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
[rpjday@localhost yum.repos.d]$
so i'm still confused.
rday
On 07/26/15 18:19, Robert P. J. Day wrote:
[rpjday@localhost yum.repos.d]$ dnf info cockpit langpacks: No languages are enabled Last metadata expiration check performed 2 days, 14:04:08 ago on Thu Jul 23 16:13:59 2015. Installed Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.60 Release : 1.fc22 Size : 35 k Repo : @System From repo : updates Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
Available Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.62 Release : 1.fc22 Size : 32 k Repo : updates-testing Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
[rpjday@localhost yum.repos.d]$
so i'm still confused.
Maybe you're getting info from an out of date mirror?
Konsole output [root@meimei ~]# dnf info cockpit langpacks: No languages are enabled Adding en_US to language list Last metadata expiration check performed 0:15:30 ago on Sun Jul 26 18:06:22 2015. Available Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.60 Release : 1.fc22 Size : 32 k Repo : updates Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
On 07/26/15 17:55, Robert P. J. Day wrote:
as you can see, the installed version is 0.60, while the updates-testing version is 0.62. so ... what am i misunderstanding here?
Not sure why you're seeing Version : 0.62 in updates-testing. I don't see it. Maybe you need to clean your meta data since if you check koji you'd find it was relegated to the trashcan.
http://koji.fedoraproject.org/koji/buildinfo?buildID=665181
On Sun, 26 Jul 2015, Ed Greshko wrote:
On 07/26/15 17:55, Robert P. J. Day wrote:
as you can see, the installed version is 0.60, while the updates-testing version is 0.62. so ... what am i misunderstanding here?
Not sure why you're seeing Version : 0.62 in updates-testing. I don't see it. Maybe you need to clean your meta data since if you check koji you'd find it was relegated to the trashcan.
ah, so i'm almost assuredly seeing some obsolete metadata? so let's try:
$ sudo dnf clean metadata langpacks: No languages are enabled Cleaning repos: fedora updates-testing updates adobe-linux-x86_64 22 metadata files removed 13 dbcache files removed $
then:
$ sudo dnf update ... chug chug chug ... $
and:
$ dnf info cockpit langpacks: No languages are enabled Last metadata expiration check performed 2 days, 14:13:16 ago on Thu Jul 23 16:13:59 2015. Installed Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.60 Release : 1.fc22 Size : 35 k Repo : @System
From repo : updates
Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
Available Packages Name : cockpit Arch : x86_64 Epoch : 0 Version : 0.62 Release : 1.fc22 Size : 32 k Repo : updates-testing Summary : A user interface for Linux servers URL : http://cockpit-project.org/ License : LGPLv2+ Description : Cockpit runs in a browser and can manage your network of GNU/Linux : machines.
nope, dnf still sees the 0.62 version in updates-testing.
rday
-
Carlos Morel-Riquelme -
Ed Greshko -
Michael Schwendt -
Patrick O'Callaghan -
Rares Aioanei -
Richard Shaw -
Robert P. J. Day -
Sérgio Basto