Mailinglist Archive: zypp-devel (24 mails)

[Dave Plater <dave.plater@xxxxxxxxxxx>]

PGNet wrote:
> On Fri, Apr 3, 2009 at 8:55 AM, Jan Kupec <jkupec@xxxxxxx> wrote:
>   
> > In other words, you want to lock all the packages from that repo, except
> >  a few, so that the next time you run up (without arguments) or dup, it
> > will upgrade only the few packages, right?
> >     
>
> yes.  as usual, better stated than i could.  thanks.
>
>   
> > What is your use case?
> >     
>
> very specific example ...
>
> i'm working on a bug where i need to track,
>
>   
> http://download.opensuse.org/repositories/Kernel:/SL111_BRANCH/openSUSE_11.1/
>
> _that_ repo "got broke", adding a pesky, unresolvable dependency, e.g.,
>
>        "error: Failed dependencies:  module-init-tools_fix_bnc480524
> is needed by kernel-default ..."
>
> with help from @suse folks, i find the workaround resolving pkgs @
>
>      http://download.opensuse.org/update/11.1-test/rpm/x86_64/?P=module-init*
>
> now, _those_ pkgs i can, of course, manually "rpm -Uvh".  works great.
>  but, (for) now, i want to track updates @ both
>
>     repositories/Kernel:/SL111_BRANCH/openSUSE_11.1/    <--- ALL files
> in the repo
>     update/11.1-test/rpm/x86_64/?P=module-init*                   <--
> just the m-i-t pkgs, and NOTHING ELSE in the repo
>
> not clear how that's done ...
>
>   
> > This is what comes to my mind: i have 11.1 system with 11.1 repo + 11.1
> >     
> (snip)
>
> iiuc, yes. that's a similar example.
>
>   
> > The answer is no, this is currently not easily possible.
> >     
>
> rats.
>
>   
> > The only thing that comes to my mind would be to create a script that
> >     
> (snip)
>
> understood.  clumsy & inflexible, tho.
>
>   
> > Any other use cases?
> >     
>
> well, anytime/everytime that "solutions" to problems comes from
> multiple BuildService sources.  and, as BS usage takes off, that's
> going to happen more frequently, not less, i'd guess ...
>
> thanks.
>   
"zypper up --force-resolution -r yourrepo module-ini*" is possibly what
you are looking for?
Regards
Dave P

-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx