Re: More dnf annoyance
- Original Message - > From: "Michael Schwendt" > To: users@lists.fedoraproject.org > Sent: Sunday, August 16, 2015 2:01:27 PM > Subject: Re: More dnf annoyance > > On Sun, 16 Aug 2015 11:51:47 + (UTC), Andreas M. Kirchwitz wrote: > > > >> "dnf --refresh" is more like "dnf clean expire-cache", which sometimes > > >> gives additional updates to plain "dnf upgrade", but there still seems > > >> some caching involved that keeps it from providing all updates > > >> available. > > > > > > Doubtful. > > > > > > "dnf update --refresh" here (Rawhide) always redownloads the metadata. > > > That's behaviour like running after "dnf clean metadata", > > > not "dnf clean expire-cache". [1] > > > > Neither "dnf --refresh upgrade" nor "dnf clean expire-cache;dnf upgrade" > > will try to download the base Fedora data (F22). Only "dnf clean metadata" > > plus "dnf upgrade" force a full refresh. > > Rawhide. I refer to Rawhide! I cannot afford spending time on this issue > with F22 in addition to Rawhide. > > "dnf --refresh update" here **always** redownloads the metadata. > > > Just try it out. "--refresh" and "clean expire-cache" result in the same. > > That also matches the documentation. Both set the metadata some kind of > > expired but don't really remove the data. > > Once more: doubtful. Whether "--refresh" doesn't remove the metadata is not > of interest, since it redownloads it afterwards anyway. > > And whether it "matches the documentation" remains to be seen. I haven't > examined the implementation. Does --refresh really do anything to confirm > the checksum of the metadata cache before deciding to redownload? Then why > does it redownload always here? It's a bug: https://bugzilla.redhat.com/show_bug.cgi?id=1226724 :-( -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Upgrade to fedora 22
- Original Message - > From: "Ed Greshko" > To: "Community support for Fedora users" > Sent: Monday, July 27, 2015 4:42:57 PM > Subject: Re: Upgrade to fedora 22 > > On 07/27/15 22:26, Radek Holy wrote: > > - Original Message - > >> From: "Patrick O'Callaghan" > >> To: users@lists.fedoraproject.org > >> Sent: Monday, July 27, 2015 1:11:31 AM > >> Subject: Re: Upgrade to fedora 22 > >> > >> On Mon, 2015-07-27 at 00:53 +0200, Patrick Dupre wrote: > >>> Should I be more patient, or should I kill the process and run dnf? > >> On F22 yum *is* dnf (which you would know if you read the message it > >> prints when it starts), so something else is wrong. > >> > >> poc > > Well, DNF does not print these messages AFAIK. > > I don't think poc was saying "dnf" prints the messages. Just that a message > is printed when you use yum which indicates it has been depreciated. e.g. > > Konsole output > [egreshko@meimei ~]$ yum check-update > Yum command has been deprecated, redirecting to '/usr/bin/dnf check-update'. > See 'man dnf' and 'man yum2dnf' for more information. > To transfer transaction metadata from yum to DNF, run: > 'dnf install python-dnf-plugins-extras-migrate && dnf-2 migrate' > > langpacks: No languages are enabled > Adding en_US to language list > Last metadata expiration check performed 0:00:00 ago on Mon Jul 27 22:39:39 > 2015. > > FWIW, /bin/yum is actually a shell script in F22. > > -- > If I wanted a blog or social media I'd go elsewhere Right, sorry for not being clear. I didn't notice that the original message was shortened by poc while I still remembered the context. I corrected myself later, see: https://lists.fedoraproject.org/pipermail/users/2015-July/463473.html -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Upgrade to fedora 22
- Original Message - > From: "Radek Holy" > To: "Community support for Fedora users" > Sent: Monday, July 27, 2015 4:26:46 PM > Subject: Re: Upgrade to fedora 22 > > - Original Message - > > From: "Patrick O'Callaghan" > > To: users@lists.fedoraproject.org > > Sent: Monday, July 27, 2015 1:11:31 AM > > Subject: Re: Upgrade to fedora 22 > > > > On Mon, 2015-07-27 at 00:53 +0200, Patrick Dupre wrote: > > > Should I be more patient, or should I kill the process and run dnf? > > > > On F22 yum *is* dnf (which you would know if you read the message it > > prints when it starts), so something else is wrong. > > > > poc > > Well, DNF does not print these messages AFAIK. > -- > Radek Holý > Associate Software Engineer > Software Management Team > Red Hat Czech > ...I mean that "Processing Dependency: xz-libs (x82-32)". -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Upgrade to fedora 22
- Original Message - > From: "Patrick O'Callaghan" > To: users@lists.fedoraproject.org > Sent: Monday, July 27, 2015 1:11:31 AM > Subject: Re: Upgrade to fedora 22 > > On Mon, 2015-07-27 at 00:53 +0200, Patrick Dupre wrote: > > Should I be more patient, or should I kill the process and run dnf? > > On F22 yum *is* dnf (which you would know if you read the message it > prints when it starts), so something else is wrong. > > poc Well, DNF does not print these messages AFAIK. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Ed Greshko" > To: "Community support for Fedora users" > Sent: Thursday, July 23, 2015 11:20:05 AM > Subject: Re: dnf update vs Software Udpates > > On 07/23/15 14:30, Radek Holy wrote: > > Well, "dnf update" is a deprecated alias for "dnf upgrade" > > (http://dnf.readthedocs.org/en/latest/command_ref.html#update-command). > > At the risk of sounding pedantic, shouldn't there then be a change to > "check-upgrade" and depreciate "check-update". :-) > > FWIW, I'm not having any real issues with using dnf. One just has to commit > to the learning curve. :-) > > -- > If I wanted a blog or social media I'd go elsewhere Yes, sounds reasonable :) -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Radek Holy" > To: "Community support for Fedora users" > Sent: Thursday, July 23, 2015 9:01:24 AM > Subject: Re: dnf update vs Software Udpates > > > > - Original Message - > > From: "Ron Yorston" > > To: users@lists.fedoraproject.org > > Sent: Wednesday, July 22, 2015 8:20:11 PM > > Subject: Re: dnf update vs Software Udpates > > > > Suvayu Ali wrote: > > >That said, I sometimes do not understand what's the harm in getting > > >updates few hours later. dnf already tells you how old the metadata is > > >when it starts, you can choose to get the latest metadata if it is too > > >old. So what's the big deal? > > > > I certainly get the impression that dnf tells me about updates less > > frequently than yum did. It also seems to pull in metadata less > > frequently. > > > > In fedora-updates.repo I have: metadata_expire=6h. I also have the > > dnf-makecache.timer 'masked'. > > > > It's more than 6 hours since I last ran dnf but: > > > > [root@vulcan rmyf22]# dnf check-update > > Fedora 22 - x86_64 - RMY repository 131 kB/s | 6.0 kB 00:00 > > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:38:32 > > 2015. > > [root@vulcan rmyf22]# > > > > No updates. It pulled in metadata for my private repo but not > > fedora-updates. So is it really telling me "how old the metadata is"? > > The message just refers to the last time an expiration check was > > performed. Does that mean the metadata was up to date as of 0:00:00 ago? > > Because, as we shall see, it clearly wasn't. > > No, precisely, it tells you the maximum of all timestamps of caches of all > repositories. I mean, if the cache of "fedora" is 3 hours old, the cache of > "updates" is 2 hours old and the cache of "updates-testing" is 1 hour old, > the output is 1 hour. ...which means that 1 hour ago, DNF found out that only "updates-testing" is expired (according to "metadata_expire"). I mean, there might be updates in another repositories as well but DNF is allowed to check it only after the "metadata_expire" period. > To see all the timestamps, you should use "--debug". Maybe you can help us by > filling an RFE with a suggestion of a better message? > > > Let's try the --refresh option: > > > > [root@vulcan rmyf22]# dnf --refresh check-update > > Fedora 22 - x86_64 - RMY repository 113 kB/s | 6.0 kB 00:00 > > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:39:01 > > 2015. > > [root@vulcan rmyf22]# > > > > Still no updates. Time for a bigger hammer (don't try this at home or > > offer it as advice to newbies): > > > > [root@vulcan rmyf22]# rm -rf /var/cache/dnf/x86_64/22/updates* > > [root@vulcan rmyf22]# dnf check-update > > Fedora 22 - x86_64 - Updates774 kB/s | 12 MB 00:16 > > Last metadata expiration check performed 0:00:16 ago on Wed Jul 22 08:40:02 > > 2015. > > > > environment-modules.x86_64 3.2.10-16.fc22 > > updates > > ... > > > > Plus 55 other updates. What's going on? > > > > Ron > > -- > > users mailing list > > users@lists.fedoraproject.org > > To unsubscribe or change subscription options: > > https://admin.fedoraproject.org/mailman/listinfo/users > > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > Have a question? Ask away: http://ask.fedoraproject.org > > > > -- > Radek Holý > Associate Software Engineer > Software Management Team > Red Hat Czech -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Radek Holy" > To: "Community support for Fedora users" > Sent: Thursday, July 23, 2015 9:01:24 AM > Subject: Re: dnf update vs Software Udpates > > > > - Original Message - > > From: "Ron Yorston" > > To: users@lists.fedoraproject.org > > Sent: Wednesday, July 22, 2015 8:20:11 PM > > Subject: Re: dnf update vs Software Udpates > > > > Suvayu Ali wrote: > > >That said, I sometimes do not understand what's the harm in getting > > >updates few hours later. dnf already tells you how old the metadata is > > >when it starts, you can choose to get the latest metadata if it is too > > >old. So what's the big deal? > > > > I certainly get the impression that dnf tells me about updates less > > frequently than yum did. It also seems to pull in metadata less > > frequently. > > > > In fedora-updates.repo I have: metadata_expire=6h. I also have the > > dnf-makecache.timer 'masked'. > > > > It's more than 6 hours since I last ran dnf but: > > > > [root@vulcan rmyf22]# dnf check-update > > Fedora 22 - x86_64 - RMY repository 131 kB/s | 6.0 kB 00:00 > > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:38:32 > > 2015. > > [root@vulcan rmyf22]# > > > > No updates. It pulled in metadata for my private repo but not > > fedora-updates. So is it really telling me "how old the metadata is"? > > The message just refers to the last time an expiration check was > > performed. Does that mean the metadata was up to date as of 0:00:00 ago? > > Because, as we shall see, it clearly wasn't. > > No, precisely, it tells you the maximum of all timestamps of caches of all > repositories. I mean, if the cache of "fedora" is 3 hours old, the cache of > "updates" is 2 hours old and the cache of "updates-testing" is 1 hour old, > the output is 1 hour. > > To see all the timestamps, you should use "--debug". Maybe you can help us by > filling an RFE with a suggestion of a better message? I mean "--verbose", sorry. > > Let's try the --refresh option: > > > > [root@vulcan rmyf22]# dnf --refresh check-update > > Fedora 22 - x86_64 - RMY repository 113 kB/s | 6.0 kB 00:00 > > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:39:01 > > 2015. > > [root@vulcan rmyf22]# > > > > Still no updates. Time for a bigger hammer (don't try this at home or > > offer it as advice to newbies): > > > > [root@vulcan rmyf22]# rm -rf /var/cache/dnf/x86_64/22/updates* > > [root@vulcan rmyf22]# dnf check-update > > Fedora 22 - x86_64 - Updates774 kB/s | 12 MB 00:16 > > Last metadata expiration check performed 0:00:16 ago on Wed Jul 22 08:40:02 > > 2015. > > > > environment-modules.x86_64 3.2.10-16.fc22 > > updates > > ... > > > > Plus 55 other updates. What's going on? > > > > Ron > > -- > > users mailing list > > users@lists.fedoraproject.org > > To unsubscribe or change subscription options: > > https://admin.fedoraproject.org/mailman/listinfo/users > > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > > Have a question? Ask away: http://ask.fedoraproject.org > > > > -- > Radek Holý > Associate Software Engineer > Software Management Team > Red Hat Czech -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Ron Yorston" > To: users@lists.fedoraproject.org > Sent: Wednesday, July 22, 2015 8:20:11 PM > Subject: Re: dnf update vs Software Udpates > > Suvayu Ali wrote: > >That said, I sometimes do not understand what's the harm in getting > >updates few hours later. dnf already tells you how old the metadata is > >when it starts, you can choose to get the latest metadata if it is too > >old. So what's the big deal? > > I certainly get the impression that dnf tells me about updates less > frequently than yum did. It also seems to pull in metadata less > frequently. > > In fedora-updates.repo I have: metadata_expire=6h. I also have the > dnf-makecache.timer 'masked'. > > It's more than 6 hours since I last ran dnf but: > > [root@vulcan rmyf22]# dnf check-update > Fedora 22 - x86_64 - RMY repository 131 kB/s | 6.0 kB 00:00 > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:38:32 > 2015. > [root@vulcan rmyf22]# > > No updates. It pulled in metadata for my private repo but not > fedora-updates. So is it really telling me "how old the metadata is"? > The message just refers to the last time an expiration check was > performed. Does that mean the metadata was up to date as of 0:00:00 ago? > Because, as we shall see, it clearly wasn't. No, precisely, it tells you the maximum of all timestamps of caches of all repositories. I mean, if the cache of "fedora" is 3 hours old, the cache of "updates" is 2 hours old and the cache of "updates-testing" is 1 hour old, the output is 1 hour. To see all the timestamps, you should use "--debug". Maybe you can help us by filling an RFE with a suggestion of a better message? > Let's try the --refresh option: > > [root@vulcan rmyf22]# dnf --refresh check-update > Fedora 22 - x86_64 - RMY repository 113 kB/s | 6.0 kB 00:00 > Last metadata expiration check performed 0:00:00 ago on Wed Jul 22 08:39:01 > 2015. > [root@vulcan rmyf22]# > > Still no updates. Time for a bigger hammer (don't try this at home or > offer it as advice to newbies): > > [root@vulcan rmyf22]# rm -rf /var/cache/dnf/x86_64/22/updates* > [root@vulcan rmyf22]# dnf check-update > Fedora 22 - x86_64 - Updates774 kB/s | 12 MB 00:16 > Last metadata expiration check performed 0:00:16 ago on Wed Jul 22 08:40:02 > 2015. > > environment-modules.x86_64 3.2.10-16.fc22 > updates > ... > > Plus 55 other updates. What's going on? > > Ron > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Suvayu Ali" > To: users@lists.fedoraproject.org > Sent: Thursday, July 23, 2015 1:07:13 AM > Subject: Re: dnf update vs Software Udpates > > Hi Pete, > > On Wed, Jul 22, 2015 at 05:42:15PM -0500, Pete Travis wrote: > > > > There is a timer unit, `/usr/lib/systemd/system/dnf-makecache.timer`, that > > fires ten minutes after each boot then one hour following the execution of > > each previous run. It triggers > > `/usr/lib/systemd/system/dnf-makecache.service`, a service that executes > > `dnf -v makecache timer`. When that command runs, dnf will check the age > > of the current metadata cache and refresh it if it is older than the value > > of * metadata_timer_sync* (seconds) in `/etc/dnf/dnf.conf`. > > Thank you for this clear and very nice explanation. > > > So, an always-on computer should never have metadata older than 4 hours; in > > practical terms, I think values >2 hours are increasingly unlikely. A > > computer that's been off overnight and turned on in the morning should have > > a fresh cache within 15 minutes of boot. If you have, say, a laptop that > > you power down often and often install or update packages immediately after > > boot, you might adjust the OnBootSec value by copying dnf-makecache.timer > > to /etc/systemd/system/ and editing accordingly. Or, consider appending > > --refresh on an as-needed basis. > > I think this is where things go wrong. OnBootSec handles powerdowns, > what about intermittent connections? In principle, it is quite possible > everytime the timer triggers the makecache service, the connection is > absent. In fact, the probability to hit the sweet spot is directly > determined by the reliability of the connection. So a connection that > is up 50% of the time, will miss 50% of the makecache jobs. Maybe the > makecache jobs can reset the timer to try again in 10 mins in case of no > network connectivity. I think that would make the odds more favourable. > > Essentially I'm suggesting to treat no connectivity as a powercycle. > Hopefully this gives the devs some ideas. > > Cheers, > > -- > Suvayu Can you please file an RFE? Thanks -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Rick Stevens" > To: "Community support for Fedora users" > Sent: Wednesday, July 22, 2015 7:52:32 PM > Subject: Re: dnf update vs Software Udpates > > On 07/22/2015 10:38 AM, Maurizio Marini wrote: > > On Tue, 21 Jul 2015 20:33:27 -0400 > > Matthew Miller wrote: > > > >> On Wed, Jul 22, 2015 at 02:10:10AM +0200, Suvayu Ali wrote: > >>> I'm sorry but "clean all" is not necessary at all! "clean metadata" or > >>> "clean expire-cache" should be sufficient. > >> > >> You don't even need to do that. Just use the --refresh flag -- `dnf > >> --refresh upgrade`. > > > > > > dnf --refresh upgrade > > does not work for me > > > > dnf clean expire-cache > > does not work for me > > > > dnf clean metadata > > does work instaed > > I think that was a typo. You need: > > dnf --refresh update Well, "dnf update" is a deprecated alias for "dnf upgrade" (http://dnf.readthedocs.org/en/latest/command_ref.html#update-command). > Running it on my machine: > > [root@prophead conf]# dnf --refresh update > RPM Fusion for Fedora 21 - Free - Updates44 kB/s | 406 kB > 00:09 > Adobe Systems Incorporated 1.2 kB/s | 1.8 kB > 00:01 > RPM Fusion for Fedora 21 - Nonfree - Updates543 kB/s | 152 kB > 00:00 > RPM Fusion for Fedora 21 - Free 17 kB/s | 508 kB > 00:29 > google-chrome77 kB/s | 3.5 kB > 00:00 > RPM Fusion for Fedora 21 - Nonfree 527 kB/s | 179 kB > 00:00 > Using metadata from Wed Jul 22 10:49:27 2015 (0:00:52 hours old) > Dependencies resolved. > > Package Arch VersionRepository > Size > > Upgrading: > google-chrome-stable x86_64 44.0.2403.89-1 google-chrome > 46 M > > Transaction Summary > > Upgrade 1 Package > > Total download size: 46 M > Is this ok [y/N]: > > This was on a machine that had been fully updated yesterday. > -- > - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - > - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - > -- > - The problem with being poor is that it takes up all of your time - > -- > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Ralf Corsepius" > To: users@lists.fedoraproject.org > Sent: Wednesday, July 22, 2015 6:58:49 PM > Subject: Re: dnf update vs Software Udpates > > On 07/22/2015 05:41 PM, Heinz Diehl wrote: > > On 22.07.2015, Suvayu Ali wrote: > > > > I usually update weekly (or at least once within two weeks). And since > > F22, I get "nothing to do" every time I do this > > What you describe indicates you could be victim of what I conside a > massive design flaw in dnf, the dnf guys have been ignoring ever since, > because they believe to know better: When dnf encounters a broken > dependency, it doesn't tell you about it and ignores it. > > Try "dnf --refresh --best update" > > Ralf Let's admit that you ignore us as well. As said many times, we are working on it [1]. First step is dnf-1.0.2. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1210445 -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Thank God for yum-deprecated :-)
- Original Message - > From: "Bruno Wolff III" > To: "Radek Holy" > Cc: "Community support for Fedora users" > Sent: Tuesday, July 21, 2015 11:20:02 PM > Subject: Re: Thank God for yum-deprecated :-) > > On Tue, Jul 21, 2015 at 11:32:58 -0400, > Radek Holy wrote: > > > >Right, it still does not allow the depsolver to remove a capability at all. > >It allows it only to replace a package which provides a required capability > >with another package which provides it as well. > > Can you describe this more precisely? Packages still provide themselves > and the installed files and these don't seem to be locked down. Is this > limited to explicit provides? And/or perhaps the automatic soname provides? > Hm, it seems that I was too tired yesterday :( It really allows the solver to remove any package in order to fulfil the given request. Sorry for the noise :( If it does not work in some cases, I believe we can collaborate with libsolv authors to find out the reason. The most precise description is that it sets the SOLVER_FLAG_ALLOW_UNINSTALL flag which is described here: https://github.com/openSUSE/libsolv/blob/master/doc/libsolv-bindings.txt#L2024 Sorry :( -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf update vs Software Udpates
- Original Message - > From: "Suvayu Ali" > To: users@lists.fedoraproject.org > Sent: Monday, July 20, 2015 10:58:05 AM > Subject: Re: dnf update vs Software Udpates > > On Mon, Jul 20, 2015 at 10:36:01AM +0200, Maurizio Marini wrote: > > On Mon, 20 Jul 2015 10:01:37 +0200 > > Michael Schwendt wrote: > > > > > On Sun, 19 Jul 2015 20:39:36 -0500, Javier Perez wrote: > > > > > > > Ok, just did a dnf clean all , and the dnf update and the updates > > > > showed up > > > > > > > > Weird. > > > > > > Just some hours before your post I had sent this: > > > https://lists.fedoraproject.org/pipermail/users/2015-July/463183.html > > > > Michael is right: all we are a mass of lame > > I have shamed very much reading his answer to me; I have posted w/out RTFM > > and > > who do not RTFM should be banned like in old good irc times > > Unfortunately Michael, this `yum/dnf clean all' business will never go > away. I remember there was a time on this list, when everytime someone > suggested that, they got corrected. But all the people who used to do > the correction are tired of repeating themselves, myself included. It's > a lost cause. > -- > Suvayu > > Open source is the future. It sets us free. > IIUUC, this is not completely true. I believe that once both PackageKit and DNF are integrated with the new CAShe [1], we will *be able* to improve this situation [2]. [1] https://github.com/james-antill/CAShe [2] If users/Fedora will be OK with downloading repomd.xml more often. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: Thank God for yum-deprecated :-)
- Original Message - > From: "Bruno Wolff III" > To: "Jan Zelený" > Cc: users@lists.fedoraproject.org > Sent: Monday, July 20, 2015 5:54:34 PM > Subject: Re: Thank God for yum-deprecated :-) > > On Mon, Jul 20, 2015 at 17:35:18 +0200, > Jan Zelený wrote: > > > >That's basically what --allowerasing is about. The idea is that when you run > >upgrade, you most likely don't want this upgrade to remove any of the > >packages > >that are currently installed on your system. As the name says, the -- > >allowerasing switch removes this assumption, allowing the dependency solver > >to > >have more available solutions to choose from. > > But it doesn't always remove packages that would allow upgrading another > package. The documentation doesn't appear to give precise information > about when packages will be erased in order to allow upgrades. The case > where I'd like to see it work is when there is a soname bump, but not all > dependencies have been updated yet. In most cases I prefer to remove the > unupdated packages temporary so that I can use the latest version of the > library. It would also be useful for upograding between Fedora releases > where retired packages can also block library updates. Right, it still does not allow the depsolver to remove a capability at all. It allows it only to replace a package which provides a required capability with another package which provides it as well. > >Back to your original question, I am not sure what the problem is. You seem > >to > >describe a situation where package has some broken deps and therefore can't > >be > >installed in which case it is not going to be installed, neither by yum nor > >by > >dnf and --skip-broken will have no effect on that. Or am I missing > >something? > > There are cases where yum gets to a point where it won't do any installs > or updates, even though --skip-broken is turned on and some installs or > updates are possible. You can work around this by trying to update or install > a smaller set of packages. For updates dnf is better, but for installs it is > currently worse. > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf command to download
- Original Message -
> From: "Ed Greshko"
> To: "Fedora"
> Sent: Monday, July 6, 2015 2:56:56 AM
> Subject: Re: dnf command to download
>
> On 07/06/15 08:47, Ed Greshko wrote:
> > On 07/06/15 08:33, Kevin Fenzi wrote:
> >> It's a plugin
> > A plugin question then.
> >
> > I see python3-dnf-plugins-core as well as python-dnf-plugins-core. They
> > have the same description. Is there a preference as to which have
> > installed?
> >
>
> I guess, never mind... Not a python person but...
>
> I see /bin/dnf is a symbolic link to dnf-2 and /bin/python is also a symlink
> to python2. So, it seems, the default version used on the system is python2
> so python-dnf-plugins-core is the proper one.
>
> --
> Sorta what I want to say when folks habitually complain about Fedora -
> https://youtu.be/ZArl8fTfub4
It depends on your use case.
If you want to use plugins of the regular DNF, just install "dnf-plugins-core"
(no need to choose between python*-dnf-plugins-core).
If you need the plugins to be available from a particular Python version,
install the appropriate python*-dnf-plugins-core package. But since these
plugins does not provide any API and the plugins are not accessible from DNF's
API, there is probably no good use case.
Well, "python3-dnf" on Fedora < 23 and "python-dnf" on Fedora >= 23 provides an
experimental binary ("/usr/bin/dnf-3" and "/usr/bin/dnf-2" respectively) which
allows you to test DNF with the Python version which is not the default in the
given Fedora. If you want to test plugins with these, then you need to install
"python3-dnf-plugins-core" on Fedora < 23 and "python-dnf-plugins-core" on
Fedora >= 23.
--
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: F22: dnf - seems to do nothing?
- Original Message - > From: "John Horne" > To: users@lists.fedoraproject.org > Sent: Wednesday, June 17, 2015 11:42:28 AM > Subject: Re: F22: dnf - seems to do nothing? > > On Tue, 2015-06-16 at 06:24 -0400, Radek Holy wrote: > > > > > > > > > I have just installed F22 (KDE spin) onto my laptop at home. After > > > installation I ran 'dnf update' and it installed a load of patches. > > > However, now whenever I invoke dnf it seems to do nothing (no output on > > > terminal). My first thought was to perhaps try using 'strace' to see > > > what it was doing, but of course I can't install it. A reboot made no > > > difference. > > > > > > > > can you run it with the --verbose switch and the environment variable > > LIBREPO_DEBUG=1? Can you share your dnf.log? File a bug with all these > > information, please. > > > > "dnf clean all" may work around it. > > > Hello, > > Thanks for this. I have now solved the problem. > > The 'clean all' made no difference. However the 'dnf -v' showed that the > process was waiting on the mirror server for some reason. The dnf log > showed the URL it was trying to use, and when I tried this in a browser > it worked fine (the XML file was displayed). However, when I tried with > 'curl -v' it hung up. The problem was with the EPSV command: > > > < 250 Directory successfully changed. > > EPSV > * Connect data stream passively > 421 Timeout.ng Extended Passive Mode (|||14410|) > * Connection time-out > * Failed EPSV attempt. Disabling EPSV > > PASV > * response reading failed > * Closing connection 0 > curl: (56) response reading failed > > > Running curl with the '--disable-epsv' option, and the file downloaded > immediately. > > I then found someone else had recently reported a similar problem: > http://forums.fedoraforum.org/showthread.php?t=305034 > > By enabling the 'fastestmirror' option in dnf, downloads now work fine. > > What is a bit annoying is that the original mirror being used was the > one at the University of Kent here in the UK. Fortunately the > 'fastestmirror' has chosen a different mirror, but I guess at some > future time the problem could emerge again if that mirror gets selected. > > I'll see about letting the mirror know of the problem. > > > > John. > > -- > John Horne Tel: +44 (0)1752 587287 > Plymouth University, UK Then, you've probably hit this bug in librepo: https://bugzilla.redhat.com/show_bug.cgi?id=1219817. librepo-1.7.16-1.fc22 should fix the problem. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22: dnf - seems to do nothing?
- Original Message - > From: "John Horne" > To: "Fedora List" > Sent: Tuesday, June 16, 2015 12:12:51 PM > Subject: F22: dnf - seems to do nothing? > > Hello, > > I have just installed F22 (KDE spin) onto my laptop at home. After > installation I ran 'dnf update' and it installed a load of patches. > However, now whenever I invoke dnf it seems to do nothing (no output on > terminal). My first thought was to perhaps try using 'strace' to see > what it was doing, but of course I can't install it. A reboot made no > difference. > > A bit of searching seems to indicate that there was (?) a problem with > dnf 'install' (perhaps with metadata?), but I couldn't find out if this > was resolved (I assume not since the latest updates obviously didn't fix > it), or if there was some sort of workaround. > > Does anyone know if there is a workaround for this problem? > > > > Thanks, > > John. > > -- > John Horne Tel: +44 (0)1752 587287 > Plymouth University, UK Hello, can you run it with the --verbose switch and the environment variable LIBREPO_DEBUG=1? Can you share your dnf.log? File a bug with all these information, please. "dnf clean all" may work around it. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf headaches.
- Original Message - > From: "Derrik Walker v2.0" > To: "fedora users" > Sent: Thursday, June 11, 2015 3:44:37 AM > Subject: dnf headaches. > > I seem to have some issues with dnf, and Dr Google isn't helping ... > > So I installed the "Games and Entertainment," which did exactly nothing, > except mark it installed. > > So, I figured out, that if I really want the games installed, I probably > should have: > > # dnf group install with-optional "Games and Entertainment" > > Cool except it tells me that "Games and Entertainment" is already > installed. > > OK, so I'll just remove it and re-install it ... but is says NOPE!!! > > # dnf group remove "Games and Entertainment" > Warning: Group 'Games and Entertainment' does not exist. > ... > > So, now I can't install it properly, or uninstall it. > > And the versions I have installed: > > # rpm -qa | grep ^dnf > dnf-1.0.0-1.fc22.noarch > dnf-plugins-core-0.1.8-1.fc22.noarch > dnf-langpacks-0.10.0-1.fc22.noarch > dnf-yum-1.0.0-1.fc22.noarch > dnf-conf-1.0.0-1.fc22.noarch > > Not sure if It's a bug, or if I overlooked something in the > documentation. But my kid want's his games! > > Thanks. > > -- > -- Derrik > > Derrik Walker v2.0, RHCE > dwal...@doomd.net > > "Those UNIX guys, they think weird!" -- John C. Dvorak You hit this: https://bugzilla.redhat.com/show_bug.cgi?id=1214968 Fixed in the upstream recently. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf whatprovides and library files
- Original Message - > From: "Gordon Messmer" > To: "Community support for Fedora users" > Sent: Wednesday, June 10, 2015 7:38:13 PM > Subject: Re: dnf whatprovides and library files > > On 06/10/2015 12:24 AM, Ed Greshko wrote: > > But, just to be clear, the issue I'm addressing is what an average > > user may do in a given circumstance. Upon seeing an error message > > such as this one, > > > > error while loading shared libraries: /lib64/libexempi.so.3: file too > > short > > > > assuming they know of dnf whatprovides I think it is more likely they > > will simply use copy/paste and issue the command "dnf whatprovides > > /lib64/libexempi.so.3" > > Interesting. I've never actually seen an error with an installed shared > object, so I never considered that you'd query one with "whatprovides." > > In that case, I agree with you. rpm and dnf behave differently with > such a query (which I also did not know): > > $ rpm -q --whatprovides /lib64/libXv.so.1.* > libXv-1.0.10-2.fc22.x86_64 > $ dnf whatprovides /lib64/libXv.so.1.* > Error: No Matches found > > dnf really should behave the same way as rpm. If possible, it should > call the rpm library functions for the query, rather than > re-implementing them. > > > Yes, rpm can tell you this *if* the file and providing package exists > > on your system. But, it is usual that you get a message about > > something missing and that is where you need dnf. > > Yes, but in the case where something is missing, you won't get a path. > You'll get a shared object name, and querying that with "dnf > whatprovides" will work correctly, as it is. Anyone, feel free to file an RFE if you really need something mentioned in this thread. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf nonlocal update
- Original Message - > From: "Rick Stevens" > To: "Community support for Fedora users" > Sent: Tuesday, June 9, 2015 10:23:29 PM > Subject: Re: dnf nonlocal update > > On 06/09/2015 04:52 AM, Robert Dady wrote: > > Hi, > > > > I have 2 computers: "A" has F22 and 3G cell phone Internet connection > > with a limited data plan, "B" has Windows7 / Ubuntu 15.04 / F22 Live and > > broadband Internet connection. > > > > I want "A" make a (dnf) list of packages of available updates, which I > > could download on "B" and install them offline on "A" from a USB stick. > > > > Is it feasible? > > Sure. One way would be to create a local repo. I'd set aside a > partition on B and creating the local repo on that partition. Then you > could copy the RPMs you need on A from this local repo onto the USB > stick and do a local update on A. > > Instructions on creating a local repo: > > http://dotancohen.com/howto/yum_repo.html > > -- > - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com - > - AIM/Skype: therps2ICQ: 226437340 Yahoo: origrps2 - > -- > - I haven't lost my mind. It's backed up on tape somewhere, but - > - probably not recoverable.- > -- Or if you don't want to mirror repositories, you can run "dnf --assumeno upgrade" on "A", save the resolved packages into a file and use "dnf download" on "B" to download them. Then you can install the packages with "dnf install" on "A". To make a script, I'd suggest using the Python API instead of parsing the output of "dnf upgrade". -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf whatprovides and library files
- Original Message - > From: "Ed Greshko" > To: users@lists.fedoraproject.org > Sent: Wednesday, June 10, 2015 9:24:09 AM > Subject: Re: dnf whatprovides and library files > > On 06/10/15 14:55, Gordon Messmer wrote: > > On 06/09/2015 04:53 PM, Ed Greshko wrote: > >> I can't seem to get dnf to tell me what package supplies a library. > > ... > >> [root@f22k ~]# ll /lib64/libXv.so.1.0.0 > >> -rwxr-xr-x. 1 root root 19664 Aug 17 2014 /lib64/libXv.so.1.0.0 > >> [root@f22k ~]# dnf whatprovides /lib64/libXv.so.1.0.0 > > > > That's the correct query for a file, but not a library. > > > > Two things: > > > > First, applications don't link against libXv.so.1.0.0, they link against > > libXv.so.1. It is up to the dynamic linker to locate that library within > > the search path: > > > > $ ldd /usr/bin/xvinfo | grep libXv > > libXv.so.1 => /lib64/libXv.so.1 (0x0032d360) > > > > You'll see the same string in the first column when a library is not found, > > so that's the string that you look for. > > > > Second, rpm generates "provides" with pathless library names. In the > > example above, "xvinfo" is linked against "libXv.so.1". rpm behaves the > > same way. Since the application is linked against "libXv.so.1" that is > > the correct string to use when searching for a package that provides it. > > > > $ dnf whatprovides libXv.so.1 > > libXv-1.0.10-2.fc22.i686 : X.Org X11 libXv runtime library > > Repo: @System > > > > Thanks for the info > > But, just to be clear, the issue I'm addressing is what an average user may > do in a given circumstance. Upon seeing an error message such as this one, > > error while loading shared libraries: /lib64/libexempi.so.3: file too short > > assuming they know of dnf whatprovides I think it is more likely they will > simply use copy/paste and issue the command "dnf whatprovides > /lib64/libexempi.so.3" > > Yes, the Subject I picked was not as accurate as it would be had I known then > what I know now. Maybe :-) > > -- > Sorta what I want to say when folks habitually complain about Fedora - > https://youtu.be/ZArl8fTfub4 > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > BTW, RPM can do that: $ rpm --query --file /lib64/libXv.so.1.0.0 So, if RPM tracks these symlinks and if it provides an API to get this information, DNF could do the magic at least for the installed packages. But maybe it could become even more confusing for users since "whatprovides" would sometimes find the package and sometimes not depending on whether the package is installed or not. Maybe printing a warning would be sufficient... -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Yumex doesn't take clean_requirements_on_remove into account (Re: kernel number in dnf)
- Original Message - > From: "Antonio M" > To: "Community support for Fedora users" > Sent: Tuesday, June 2, 2015 8:02:45 AM > Subject: kernel number in dnf > I switched from yumex to umex-dnf. This morning a new kernel was found, but I > got 4 kernels installed, even if my dnf,conf sounds like: > [main] > gpgcheck=1 > installonly_limit=3 > clean_requirements_on_remove=true > why?? > -- > Antonio Montagnani > Skype : amontag52 > Linux Fedora 21 (Twenty-one) > inviato da Gmail > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org I guess that's because Yumex doesn't take DNF's clean_requirements_on_remove into account. I wonder whether it's even desired because then the actual value of clean_requirements_on_remove would depend on the chosen backend and I believe that backend changes should not affect the behavior of the application. But I don't know Yumex... -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf has no command to check all
- Original Message - > From: "Matthew Miller" > To: "Radek Holy" > Cc: "Community support for Fedora users" > Sent: Thursday, May 28, 2015 2:29:23 PM > Subject: Re: dnf has no command to check all > > On Thu, May 28, 2015 at 08:17:24AM -0400, Radek Holy wrote: > > > > # dnf check all > > > > No such command: check. Please use /bin/dnf --help > > > > It could be a DNF plugin command, try: "dnf install > > > > 'dnf-command(check)'" > > Any idea how to make it smarter without a need to (re)download metadata? > > Sure — a core plugin could know about deprecated yum commands and print > the alternative. Or better, for _at least_ everything listed in the yum > man page where there's an obvious mapping, just do it (even if those > things stay documented as compatibility options). > > -- > Matthew Miller > > Fedora Project Leader > Sounds good. Would you mind filing an RFE? -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf failed to download repomd.xml from updates
- Original Message - > From: "jd1008" > To: "Fedora Community Users Support" > Sent: Thursday, May 28, 2015 12:11:34 AM > Subject: dnf failed to download repomd.xml from updates > > # dnf distro-sync > Fedora 22 - x86_64 3.1 MB/s | 41 MB 00:13 > RPM Fusion for Fedora 22 - Free - > Updates 1.1 kB/s | 399 > B 00:00 > RPM Fusion for Fedora 22 - Nonfree - > Updates2.8 kB/s | 399 B > 00:00 > RPM Fusion for Fedora 22 - > Free 955 kB/s | > 551 kB 00:00 > Error: Failed to synchronize cache for repo 'updates' from > 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f22&arch=x86_64': > Cannot download repomd.xml: Curl error (56): Failure when receiving data > from the peer for > ftp://mirror.lstn.net/fedora/updates/22/x86_64/repodata/repomd.xml > [response reading failed] I guess that this is the same as https://bugzilla.redhat.com/show_bug.cgi?id=1220269 even though it happened at another time. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf has no command to check all
- Original Message - > From: "Matthew Miller" > To: "Community support for Fedora users" > Sent: Thursday, May 28, 2015 4:15:24 AM > Subject: Re: dnf has no command to check all > > On Wed, May 27, 2015 at 08:02:55PM -0600, jd1008 wrote: > > I had to use > > # /bin/yum-deprecated check all > > Yum command has been deprecated, use dnf instead. > > See 'man dnf' and 'man yum2dnf' for more information. > > See > http://dnf.readthedocs.org/en/latest/cli_vs_yum.html#changes-in-dnf-plugins-compared-to-yum-plugins > > > # dnf check all > > No such command: check. Please use /bin/dnf --help > > It could be a DNF plugin command, try: "dnf install 'dnf-command(check)'" > > This message is _trying_ to be helpful, but it's not very smart. > > > > -- > Matthew Miller > > Fedora Project Leader Any idea how to make it smarter without a need to (re)download metadata? -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: F22 - DNF migrate
- Original Message - > From: "antonio montagnani" > To: "Fedora List" > Sent: Wednesday, May 27, 2015 12:33:19 PM > Subject: F22 - DNF migrate > > if I issue the command dnf-2 migrate I get: > > > vim-minimal-7.4.475-2.fc20.x86_64 found in DNFDB; skipping > vlc-2.1.5-1.fc20.x86_64 found in DNFDB; skipping > vino-3.14.2-1.fc21.x86_64 found in DNFDB; skipping > vim-common-7.4.027-2.fc19.x86_64 found in DNFDB; skipping > vte291-0.38.3-1.fc21.x86_64 found in DNFDB; skipping > vim-enhanced-7.4.475-2.fc20.x86_64 found in DNFDB; skipping > 3930 YUMDB records found, 0 migrated, 3930 skipped/preserved > Migrating groups data... > Yum command has been deprecated, use dnf instead. > See 'man dnf' and 'man yum2dnf' for more information. > > Errore: Malformed yum output > > > Not very familiar with Dnf.What does it mean?? > -- > Antonio M > Skype: amontag52 > > Linux Fedora F22 on PcDesktop1 > > http://lugsaronno.altervista.org > http://campingmonterosa.altervista.org This is a bug in the community plugins (see https://bugzilla.redhat.com/show_bug.cgi?id=1214807). Fixed in dnf-plugins-extras-0.0.8-1.fc22. -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf issues in f22
- Original Message -
> From: "Isaac Cortés González"
> To: "Community support for Fedora users"
> Sent: Wednesday, May 27, 2015 8:08:44 PM
> Subject: Re: dnf issues in f22
>
> > What problems exactly?
>
> This:
>
> .
> Traceback (most recent call last):
> File "/bin/dnf", line 36, in
>main.user_main(sys.argv[1:], exit_code=True)
> File "/usr/lib/python2.7/site-packages/dnf/cli/main.py", line 185, in
> user_mai
> n
>errcode = main(args)
> File "/usr/lib/python2.7/site-packages/dnf/cli/main.py", line 84, in main
>return _main(base, args)
> File "/usr/lib/python2.7/site-packages/dnf/cli/main.py", line 134, in _main
>cli.run()
> File "/usr/lib/python2.7/site-packages/dnf/cli/cli.py", line 1077, in run
>return self.command.run(self.base.extcmds)
> File "/usr/lib/python2.7/site-packages/dnf/cli/commands/group.py", line 385,
> i
> n run
>return self.base.env_group_install(patterns, types)
> File "/usr/lib/python2.7/site-packages/dnf/base.py", line 1253, in
> env_group_i
> nstall
>res.groups, types)
> File "/usr/lib/python2.7/site-packages/dnf/comps.py", line 88, in
> install_or_s
> kip
>logger.warning("%s, %s", str(e)[:-1], _("skipping."))
> UnicodeEncodeError: 'ascii' codec can't encode character u'\xe1' in position
> 30:
> ordinal not in range(128)
This is a bug (see https://bugzilla.redhat.com/show_bug.cgi?id=1223932). Fixed
in upstream.
--
Radek Holý
Associate Software Engineer
Software Management Team
Red Hat Czech
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
Re: dnf metalink issue: Fedora Updates repo
- Original Message - > From: "Kevin Fenzi" > To: users@lists.fedoraproject.org > Sent: Sunday, May 10, 2015 5:57:58 PM > Subject: Re: dnf metalink issue: Fedora Updates repo > > There's an issue with the f20 updates repo metalink in mirrormanager. > > We were hoping to have it fixed up quickly, but it's of course proving > more difficult than it seems at first. ;( > > Anyhow, folks are working on it, and we hope to have it fixed later > today. > > I'd suggest just waiting to grab updates until then, or if you need > something right away from the f20 updates repo you can edit your repo > file and comment the metalink and uncomment the baseurl. If you do > that, please remember to move it back once this is fixed as the > metalink provides normally many advantages over the baseurl. Yes, one of the advantages is that it provides a checksum of "repomd.xml". And that's why was DNF failing (https://bugzilla.redhat.com/show_bug.cgi?id=1219283) -- the checksum of "repomd.xml" stored on the mirrors did not match the checksum provided by the metalink. Personally, I'd be afraid of switching to baseurl because of that. > Sorry for the trouble. > > kevin > > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
Re: systemd-nspawn container
- Original Message - > From: "arnaud gaboury" > To: users@lists.fedoraproject.org > Sent: Thursday, April 23, 2015 11:34:02 AM > Subject: systemd-nspawn container > > I am running Archlinux and want to build a systemd-nspawn conatiner > with Fedora 22 server. > > Here is what I did: > > --- > # machinectl pull-raw --verify=no > http://ftp.halifax.rwth-aachen.de/fedora/linux/releases/test/22_Beta/Cloud/x86_64/Images/Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw.xz > $ tar > # systemd-nspawn -M Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw > Spawning container Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw on > /var/lib/machines/Fedora-Cloud-Base-22_Beta-20150415.x86_64.raw. > Press ^] three times within 1s to kill container. > [root@Fedora-Cloud-Base-22_Beta-20150415 ~]# dnf -y --releasever=22 > --nogpg --installroot=/var/lib/machines/MyContainer --disablerepo='*' > --enablerepo=fedora install systemd passwd dnf fedora-release-server > vim-minimal > Error: Failed to synchronize cache for repo 'fedora' from > 'https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=x86_64': > Cannot prepare internal mirrorlist: Status code: 503 for > https://mirrors.fedoraproject.org/metalink?repo=fedora-22&arch=x86_64 > [root@Fedora-Cloud-Base-22_Beta-20150415 ~]# dnf clean metada > --releasever=22 Remove cached data > [root@Fedora-Cloud-Base-22_Beta-20150415 ~]# dnf list sqlite --releasever=22 >Fedora 22 - x86_64 > 3.5 MB/s | 41 MB 00:11 > Fedora 22 - x86_64 - Test Updates >3.7 MB/s | 14 MB 00:03 > Error: Failed to synchronize cache for repo 'updates' from > 'https://mirrors.fedoraproject.org/metalink?repo=updates-released-f22&arch=x86_64': > Cannot prepare internal mirrorlist: Status code: 503 for > https://mirrors.fedoraproject.org/metalink?repo=updates-released-f22&arch=x86_64 > [root@Fedora-Cloud-Base-22_Beta-20150415 ~]# > > > I can't install. > > Anything I am missing? > > Thank you for hints > > > > -- > > google.com/+arnaudgabourygabx > -- > users mailing list > users@lists.fedoraproject.org > To unsubscribe or change subscription options: > https://admin.fedoraproject.org/mailman/listinfo/users > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > Have a question? Ask away: http://ask.fedoraproject.org > According the the status code, I'd expect that the server was temporarily unavailable and according to the other mailing list(s) where you posted a similar question, it seems that it works for you now, doesn't it? -- Radek Holý Associate Software Engineer Software Management Team Red Hat Czech -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
