Mailinglist Archive: opensuse (1502 mails)
| < Previous | Next > |
Re: [opensuse] Local Update Server Works Great!
- From: Jan Kupec <jkupec@xxxxxxx>
- Date: Fri, 03 Apr 2009 15:12:43 +0200
- Message-id: <49D60B4B.1000808@xxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi David,
David C. Rankin wrote:
What you get with createrepo from dirs with rpms is just plain packages.
The update repositories contain also special metadata called 'Patches'.
These live only in the metadata, that's why you don't get them with
createrepo. There're located in <repository>/repodata/updateinfo.xml.gz
in recent update repos (they used to be in /repodata/patches.xml +
patch-*.xml files before 11.0).
My guess is that copying these raw metadata to corresponding dir on the
client machines will suffice, they contain all architectures the repo
contains.
HTH
BTW (info for those on 11.1) on a 11.1+ system:
zypper up == zypper up -t package
zypper patch == zypper up -t patch
- --
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
iEYEARECAAYFAknWC0sACgkQgEhGpmN+6QF6bwCff1Q/cuCgvR5y9mxawElpygfH
LCYAnim6SMqEpIG872K2/KIQuEUMm/n8
=VRQF
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
Hash: SHA1
Hi David,
David C. Rankin wrote:
Maybe you can help with another problem with the local update setup.
The only
problem I have is that to access rpms on the local repository I have to use
the
'-t package' option even if the rpms were originally cached from the openSuSE
Update server during an online update.
It's really just more annoying than anything else. I would expect that
doing a
"zypper up -r localrepo" would return a list of updates that have not yet been
applied to the client machine. Instead, you get the "Nothing to do" answer.
If you use -t package against the local repo, then you get all the
updates
both from the online-update repo as well as all of the packages cached during
a
regular zypper up -t package update.
Is there any designation of flag the online-update metadata has that I
might
be missing in creating the repo with 'createrepo -p -d openSUSE_11.0'?
What you get with createrepo from dirs with rpms is just plain packages.
The update repositories contain also special metadata called 'Patches'.
These live only in the metadata, that's why you don't get them with
createrepo. There're located in <repository>/repodata/updateinfo.xml.gz
in recent update repos (they used to be in /repodata/patches.xml +
patch-*.xml files before 11.0).
My guess is that copying these raw metadata to corresponding dir on the
client machines will suffice, they contain all architectures the repo
contains.
HTH
BTW (info for those on 11.1) on a 11.1+ system:
zypper up == zypper up -t package
zypper patch == zypper up -t patch
- --
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
iEYEARECAAYFAknWC0sACgkQgEhGpmN+6QF6bwCff1Q/cuCgvR5y9mxawElpygfH
LCYAnim6SMqEpIG872K2/KIQuEUMm/n8
=VRQF
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |