Mailinglist Archive: zypp-devel (24 mails)

[Jan Kupec <jkupec@xxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

PGNet wrote:
> On Fri, Apr 3, 2009 at 8:04 AM, Duncan Mac-Vicar Prett
> <dmacvicar@xxxxxxx> wrote:
> > PGNet wrote:
> > > is it possible to set up -- and then limit/filter -- a repo so as to
> > > only upgrade a single file, or subset of files?
> > >
> > > e.g.,  atm i'd like to update to:
> > >
> > >   
> > > http://download.opensuse.org/update/11.1-test/rpm/x86_64/module-init-tools-3.4-56.10.1.x86_64.rpm
> > zypper in module-init-tools ?
> >
> > install upgrades if the package is installed and there is a new version
> > of that package (you can see new packages with zypper lu )
>
> heh, clearly i've mis-asked my question.  "take 2" ...
>
> yes, "zypper in" works.  but that presumes that that repo has been added.
>
> and, if it has, then "zypper up/dup" updates will pick up all _other_
> files from that repo, too.  no?
>
> _that_ is what i'm trying to avoid ... i.e, i want _only_ repo-based
> updates of that ONE file from the repo.

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?

What is your use case?

This is what comes to my mind: i have 11.1 system with 11.1 repo + 11.1
updates. I want to have the newest git, so i add a factory repo, but i
want only git (and it's deps, as needed) from it. I want to keep my
system up to date with 'zypper up'.

If the repo in question contains only packages that are not in other
repos, then there's no problem - zypper up will only update _installed_
packages.

The answer is no, this is currently not easily possible.

The only thing that comes to my mind would be to create a script that
would parse the output of 'zypper se -r your-repo', get the names of the
packages and calle 'zypper al -r your-repo $packagename' on them. Then
you would unlock the packages you _want_ to track using 'zypper rl
$packagename'.

But this would create a lock for each of the repo's packages that you do
not wish to track, and that could mean a severe peformance penalty,
depending on the number of the packages in the repo. Plus, you might
have problems with dependencies of the packages (you would need to
unlock them, too).

Any other use cases? Is this worth looking into? Anybody has an idea how
to do it?

- --
cheers,
jano


 Ján Kupec
 YaST team
- ---------------------------------------------------------(PGP)---
 Key ID: 637EE901
 Fingerprint: 93B9 C79B 2D20 51C3 800B  E09B 8048 46A6 637E E901
- ---------------------------------------------------------(IRC)---
 Server: irc.freenode.net
 Nick: jniq
 Channels: #zypp #yast #suse #susecz
- ---------------------------------------------------------(EOF)---
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAknWMYEACgkQgEhGpmN+6QHcKwCfRDsL7a1uHxtfmWgHEj3D1u3/
CRQAoIiAfOO1XmvtDSph3aDVVwer8TYH
=u9vS
-----END PGP SIGNATURE-----
-- 
To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx