bodhi client question

[Joachim Backes]

Dear bodhi/koji specialists,

perhaps, this is a dumb question:

sometimes after having filed a BZ, I get some email like

-----------------------------------------------------------
Package xxxxx-4.1.0.0-4.beta1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xxxxx-4.1.0.0-4.beta1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-9971/xxxxx-4.1.0.0-4....
------------------------------------------------------------

*My question:* if xxxxx consists of a lot of packages, and I'm only 
needing some few of them (libreoffice is a good example), how then can I 
automatically download only those packages installed on my site?

The usage of "bodhi -D xxxxx....." will download *all* and not only the 
locally installed pkgs.

Kind regards

Joachim Backes
-- 

Fedora release 19 (Schrödinger’s Cat): Kernel-3.9.4-302.fc19.x86_64

Joachim Backes <joachim.backes(a)rhrk.uni-kl.de&gt;
https://www-user.rhrk.uni-kl.de/~backes

[Adam Jackson]

On Wed, 2013-06-05 at 10:58 +0200, Joachim Backes wrote:

>  -----------------------------------------------------------
>  Package xxxxx-4.1.0.0-4.beta1.fc19:
>  * should fix your issue,
>  * was pushed to the Fedora 19 testing repository,
>  * should be available at your local mirror within two days.
>  Update it with:
>  # su -c 'yum update --enablerepo=updates-testing xxxxx-4.1.0.0-4.beta1.fc19'
>  as soon as you are able to.
>  Please go to the following url:
>  https://admin.fedoraproject.org/updates/FEDORA-2013-9971/xxxxx-4.1.0.0-4....
>  ------------------------------------------------------------
>  
>  *My question:* if xxxxx consists of a lot of packages, and I'm only 
>  needing some few of them (libreoffice is a good example), how then can I 
>  automatically download only those packages installed on my site? 
Wouldn't this just be:

% sudo yum update --enablerepo=updates-testing --downloadonly xxxxx-4.1.0.0-4.beta1.fc19

- ajax

[Joachim Backes]

On 06/05/2013 02:37 PM, Adam Jackson wrote:
>  On Wed, 2013-06-05 at 10:58 +0200, Joachim Backes wrote:
>
> > -----------------------------------------------------------
> > Package xxxxx-4.1.0.0-4.beta1.fc19:
> > * should fix your issue,
> > * was pushed to the Fedora 19 testing repository,
> > * should be available at your local mirror within two days.
> > Update it with:
> > # su -c 'yum update --enablerepo=updates-testing xxxxx-4.1.0.0-4.beta1.fc19'
> > as soon as you are able to.
> > Please go to the following url:
> > https://admin.fedoraproject.org/updates/FEDORA-2013-9971/xxxxx-4.1.0.0-4....
> > ------------------------------------------------------------
> >
> > *My question:* if xxxxx consists of a lot of packages, and I'm only
> > needing some few of them (libreoffice is a good example), how then can I
> > automatically download only those packages installed on my site?
>
>  Wouldn't this just be:
>
>  % sudo yum update --enablerepo=updates-testing --downloadonly xxxxx-4.1.0.0-4.beta1.fc19
>
>  - ajax
>  
No, because in the most cases I receive this email, it's not yet arrived 
in updates-testing. This is the problem. And I want to avoid a download 
for a lot of single pkg's which is a painful thing.

JB

-- 

Fedora release 19 (Schrödinger’s Cat): Kernel-3.9.4-302.fc19.x86_64

Joachim Backes <joachim.backes(a)rhrk.uni-kl.de&gt;
https://www-user.rhrk.uni-kl.de/~backes

[Adam Jackson]

On Wed, 2013-06-05 at 15:35 +0200, Joachim Backes wrote:
>  On 06/05/2013 02:37 PM, Adam Jackson wrote:
>  > Wouldn't this just be:
>  >
>  > % sudo yum update --enablerepo=updates-testing --downloadonly
> xxxxx-4.1.0.0-4.beta1.fc19
>  >
>  > - ajax
>  >
>  
>  No, because in the most cases I receive this email, it's not yet arrived 
>  in updates-testing. This is the problem. And I want to avoid a download 
>  for a lot of single pkg's which is a painful thing. 
Well, okay, that sounds like two bugs to me:

1) That email shouldn't be sent until the update actually hits testing
2) We should have per-update repos and a reasonable way to enable them

But there's not really a good way to do what you're asking for as it is.
It's straightforward to hack up the bodhi client to grab only packages
with names that match your installed system, but that will fall down if
the new versions you're about to test require things you don't yet have
installed.

- ajax

[Kevin Fenzi]

On Wed, 05 Jun 2013 11:36:27 -0400
Adam Jackson <ajax(a)redhat.com&gt; wrote:

>  Well, okay, that sounds like two bugs to me:
>  
>  1) That email shouldn't be sent until the update actually hits testing 
It actually has landed on the master mirror. I'm not sure it's
practical for bodhi to check all mirrors or sample various external
ones. Perhaps the message could be more clear?

...snip...

kevin

[Adam Williamson]

On Wed, 2013-06-05 at 10:16 -0600, Kevin Fenzi wrote:
>  On Wed, 05 Jun 2013 11:36:27 -0400
>  Adam Jackson <ajax(a)redhat.com&gt; wrote:
>  
>  > Well, okay, that sounds like two bugs to me:
>  > 
>  > 1) That email shouldn't be sent until the update actually hits testing
>  
>  It actually has landed on the master mirror. I'm not sure it's
>  practical for bodhi to check all mirrors or sample various external
>  ones. Perhaps the message could be more clear? 
IIRC there are two messages sent: one when the update is submitted
(state is changed to MODIFIED) and one when it is pushed (state is
changed to ON_QA).

To go back to the original question - I don't believe you can split an
update like that with the bodhi client. But you can do it with koji:
'koji download-build --arch=x86_64 --arch=noarch (build ID)' is what I
usually use. Change x86_64 to i686 if appropriate, obviously. Adding
--arch=noarch makes sure you get any noarch subpackages. I think, with
recent koji versions, you can substitute a NEVR for the koji build ID,
which saves you having to go and find the build ID.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net

[Emmanuel Seyman]

* Adam Jackson [05/06/2013 11:36] :
>  1) That email shouldn't be sent until the update actually hits testing 
There's no specific moment in time at which an update hits testing.
It depends on which mirror you're hitting and how frequently it is updated.

Emmanuel

[Sérgio Basto]

On Qua, 2013-06-05 at 18:17 +0200, Emmanuel Seyman wrote: 
>  * Adam Jackson [05/06/2013 11:36] :
>  >
>  > 1) That email shouldn't be sent until the update actually hits testing
>  
>  There's no specific moment in time at which an update hits testing.
>  It depends on which mirror you're hitting and how frequently it is updated.
>  
>  Emmanuel 
About this , you may choose one mirror that you know that is fast. Right
now I'm waiting for clamav update on F17 and I choose mirrors.kernel 
edit /etc/yum.repos.d/fedora-updates-testing.repo
baseurl=http://mirrors.eu.kernel.org/fedora/updates/testing/$releasever/$...
#mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=updates-testing-f$releasever&arch=$basearch

http://mirrors.eu.kernel.org/fedora/updates/testing/17/SRPMS/?C=M;O=D
in this link I saw that was updated 13-Jun-2013 04:48, so should updated
again in 3 hours 

I will do : 
yum clean all --enablerepo=updates-testing (for clean also
updates-testing)


another cool thing you may use advisory with yum-plugin-security for
update your system like this:

yum --advisory=FEDORA-2013-8202 update --enablerepo=updates-testing

oops, I receive one bodhi notification , but the package wasn't push yet
to updates-testing 

by seeing Pushed: False and yet haven't advisory  

Best regards, 
-- 
Sérgio M. B.

On 6/13/13 17:33 Sérgio Basto wrote:

On 6/13/13 17:33 Sérgio Basto wrote:

[Matthias Runge]

On 06/05/2013 03:35 PM, Joachim Backes wrote:
> >
> > Wouldn't this just be:
> >
> > % sudo yum update --enablerepo=updates-testing --downloadonly
> > xxxxx-4.1.0.0-4.beta1.fc19
> >
> > - ajax
> >
>  
>  No, because in the most cases I receive this email, it's not yet arrived
>  in updates-testing. This is the problem. And I want to avoid a download
>  for a lot of single pkg's which is a painful thing. 
if you do
yum update --enablerepo=updates-testing ####
then you'd get just that specific update only when it already hit your
mirror.
-- 
Matthias Runge <mrunge(a)matthias-runge.de&gt;

[Sérgio Basto]

On Qua, 2013-06-05 at 10:58 +0200, Joachim Backes wrote:
>  as soon as you are able to. 
this is a clear message .

-- 
Sérgio M. B.