[packman] dependencies of packman subpackages from same build

Olaf Hering olaf at aepfle.de
Tue Feb 7 17:27:26 CET 2017

On Tue, Feb 07, Daniel Pecka wrote:

> We were discussing this with olaf few weeks ago and I've suggested to
> ensure that proper libs from proper vendor are satisfied if you explicitely
> set your deps to be `= %version-%release' (eg they will require lib
> packages that have same version-release string) ..

Jan Engelhardt suggested that libzypp should make sure that each
subpackage comes from the same src.rpm. Its unclear if such info is in
the repo metadata. Making the change there would cover all cases.
I did not follow up on this with the zypp maintainers at
zypp-devel at opensuse.org.

My suggestion was to tweak the few affected packages (ffmpeg, gstreamer)
to make sure each subpkg comes from the same build.

> Current workaround in suse is, that ppl rely on the fact, that packman his

'zypper dup --from packman' is not a workaround.
It is the correct way to handle overlapping packages, not just for the
packman repository.

> SUSEhelp on freenode knows this factoid:
> <SUSEhelp> ``zypper dup --from packman'' is wrong. It will forcefully
> update _all_ packages that you have already in your system with theirs
> packman instances (if they exist), just imagine ...

Whoever put that there is overreacting.
Please get this removed, it is wrong. Especially with 42.2 and
Tumbleweed, they have very few overlapping packages.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.links2linux.de/pipermail/packman/attachments/20170207/cbdf4660/attachment.sig>

More information about the Packman mailing list