Re: Easy way of testing packages?
On Sat, 2012-06-02 at 17:22 +0200, Stefan Schulze Frielinghaus wrote: On Sat, 2012-06-02 at 17:00 +0200, Kevin Kofler wrote: Stefan Schulze Frielinghaus wrote: is there an easy way to test packages except of using $ yum --enablerepo=updates-testing update package yum install yum-security yum --enablerepo=updates-testing --advisory=FEDORA-2012- update Ah this looks good! However, I have one question left. Does the yum plugin download the package directly from koji or do I have to wait until the package is distributed to all mirrors (because the command still mentions the updates-testing repo)? It uses the repos defined in yum. So updates-testing. If you're in a hurry to get an update earlier, you can use koji or bodhi command-line tools to download specific NEVRs or (in the case of bodhi) update IDs. e.g.: bodhi -D FEDORA-2012-7716 bodhi -D mesa-8.0.2-8.fc17 koji download-build --arch=x86_64 --arch=noarch 321768 koji download-build --arch=x86_64 --arch=noarch ocaml-3.12.1-9.fc17 see 'man koji' and 'man bodhi' for more details. If you do this regularly it's probably easiest to set up a local 'side' repo - I have ~/local/repo/x86_64 and a file in /etc/yum.repos.d/ to make that directory a repository (with a very short metadata expiry time). I download the packages to that path, run 'createrepo .', and then use yum to install the packages. For occasional use, you can just run yum directly on the packages; it's getting quite good at that. e.g. running 'yum update *' on a directory full of .rpms will do what you'd (probably) expect - for any of those packages you have installed, it'll update them; others will be left out. Hope that helps... -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Easy way of testing packages?
On Sun, 2012-06-03 at 23:51 -0700, Adam Williamson wrote: [...] If you're in a hurry to get an update earlier, you can use koji or bodhi command-line tools to download specific NEVRs or (in the case of bodhi) update IDs. e.g.: bodhi -D FEDORA-2012-7716 bodhi -D mesa-8.0.2-8.fc17 koji download-build --arch=x86_64 --arch=noarch 321768 koji download-build --arch=x86_64 --arch=noarch ocaml-3.12.1-9.fc17 see 'man koji' and 'man bodhi' for more details. If you do this regularly it's probably easiest to set up a local 'side' repo - I have ~/local/repo/x86_64 and a file in /etc/yum.repos.d/ to make that directory a repository (with a very short metadata expiry time). I download the packages to that path, run 'createrepo .', and then use yum to install the packages. For occasional use, you can just run yum directly on the packages; it's getting quite good at that. e.g. running 'yum update *' on a directory full of .rpms will do what you'd (probably) expect - for any of those packages you have installed, it'll update them; others will be left out. Ah this is really nice. koji/bodhi commands make life really easy, and since yum accepts RPMs from the current directory, an update is made easy! Next time I will provide Karma faster and _easier_ :D Thanks a lot, Stefan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Easy way of testing packages?
Hi all, is there an easy way to test packages except of using $ yum --enablerepo=updates-testing update package For example, on May 30 a message reached the devel list that Pidgin needs an update because of a security flaw. A new package was created and needed karma in order to get pushed to stable quickly. Now comes the part I do not like very much: I have to download and install the package and all its sub-packages manually from koji. In case of the mentioned Pidgin update, I have to check if one of the following packages are installed on my system: finch finch-devel libpurple libpurple-devel libpurple-perl libpurple-tcl pidgin pidgin-devel pidgin-docs pidgin-evolution pidgin-perl pidgin-debuginfo Of course, I could wait two or three days (I do not have the exact number in mind) until the package hits updates-testing and is finally deployed to the mirror which I use, but for a package which fixes a security flaw, this is an awful long time. So using yum and enable the updates testing repo is not really a good choice. But manually downloading and checking which packages I should update is bothersome. My question is: Is there an easy/friendly way of testing packages in order to quickly give karma? I only found [1] suggesting yum with the updates-testing repo enabled. Regards, Stefan [1] http://fedoraproject.org/wiki/QA/Updates_Testing -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Easy way of testing packages?
Stefan Schulze Frielinghaus wrote: is there an easy way to test packages except of using $ yum --enablerepo=updates-testing update package yum install yum-security yum --enablerepo=updates-testing --advisory=FEDORA-2012- update Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Easy way of testing packages?
On Sat, 2012-06-02 at 17:00 +0200, Kevin Kofler wrote: Stefan Schulze Frielinghaus wrote: is there an easy way to test packages except of using $ yum --enablerepo=updates-testing update package yum install yum-security yum --enablerepo=updates-testing --advisory=FEDORA-2012- update Ah this looks good! However, I have one question left. Does the yum plugin download the package directly from koji or do I have to wait until the package is distributed to all mirrors (because the command still mentions the updates-testing repo)? Regards, Stefan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Easy way of testing packages?
Stefan Schulze Frielinghaus wrote: However, I have one question left. Does the yum plugin download the package directly from koji or do I have to wait until the package is distributed to all mirrors (because the command still mentions the updates-testing repo)? Unfortunately, this also only works once the package is actually pushed to updates-testing. That's of course because yum still pulls it from updates- testing (yum cannot pull directly from Koji as the required metadata is not there), and also because the advisory number is only handed out at that time (so you cannot actually spell out the command before that point in time). Kevin Kofler -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Easy way of testing packages?
On Sat, 02 Jun 2012 18:53:14 +0200, Kevin Kofler wrote: Unfortunately, this also only works once the package is actually pushed to updates-testing. That's of course because yum still pulls it from updates- testing (yum cannot pull directly from Koji as the required metadata is not there), There was http://koji.fedoraproject.org/static-repos/ which I am not sure if it would help in this case or not - but it no longer works. Regards, Jan -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Easy way of testing packages?
Something similar already was requested: https://bugzilla.redhat.com/show_bug.cgi?id=563285 Please look there also for some mentioned alternatives in comments. 02.06.2012 17:40, Stefan Schulze Frielinghaus wrote: Hi all, is there an easy way to test packages except of using $ yum --enablerepo=updates-testing updatepackage For example, on May 30 a message reached the devel list that Pidgin needs an update because of a security flaw. A new package was created and needed karma in order to get pushed to stable quickly. Now comes the part I do not like very much: I have to download and install the package and all its sub-packages manually from koji. In case of the mentioned Pidgin update, I have to check if one of the following packages are installed on my system: finch finch-devel libpurple libpurple-devel libpurple-perl libpurple-tcl pidgin pidgin-devel pidgin-docs pidgin-evolution pidgin-perl pidgin-debuginfo Of course, I could wait two or three days (I do not have the exact number in mind) until the package hits updates-testing and is finally deployed to the mirror which I use, but for a package which fixes a security flaw, this is an awful long time. So using yum and enable the updates testing repo is not really a good choice. But manually downloading and checking which packages I should update is bothersome. My question is: Is there an easy/friendly way of testing packages in order to quickly give karma? I only found [1] suggesting yum with the updates-testing repo enabled. Regards, Stefan [1] http://fedoraproject.org/wiki/QA/Updates_Testing -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Easy way of testing packages?
On 02/06/12 14:40, Stefan Schulze Frielinghaus wrote: Hi all, is there an easy way to test packages except of using $ yum --enablerepo=updates-testing updatepackage Hopefully this may be a step in the right direction. Have put in an rfe for Security as a yum config option. https://bugzilla.redhat.com/show_bug.cgi?id=823245 About the 3 days wait, I cannot help, but if security=1, could be put in updates-testing(or other testing repo) it may make the process a little more helpful. -- Regards, Frank Jack of all, fubars -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
