[opensuse-packaging] File-package-in-two-packages-error only on 13.1?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Evening everybody, is there a reason why the following is an error only on 13.1, and not on 13.2?
ERROR: /usr/sbin/rclxc is packaged in both lxc-libs and lxc, and the packages do not conflict
The package is here, and as you can see, it builds fine for
https://build.opensuse.org/package/live_build_log/home:ojkastl_buildservice:...
Is
this intentional? Or what am I missing? (The solution is to exclude the link in the files section of the libs package. And the error is gone on 13.1, too, and it builds fine. At least locally) Regards, Johannes - -- Working with Unix is like wrestling a worthy opponent. Working with windows is like attacking a small whining child who is carrying a .38. -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlSXEXsACgkQzi3gQ/xETbJ/dwCfeDA0SLYhtzuFE0A+7ZyxSROX ckcAnRpp4CXQOAoN9jY6MEvrLkJExvbe =cvzv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Sun, 2014-12-21 at 19:29 +0100, Johannes Kastl wrote:
Evening everybody,
is there a reason why the following is an error only on 13.1, and not on 13.2?
ERROR: /usr/sbin/rclxc is packaged in both lxc-libs and lxc, and the packages do not conflict
The package is here, and as you can see, it builds fine for
https://build.opensuse.org/package/live_build_log/home:ojkastl_buildservice:...
Is
this intentional? Or what am I missing?
(The solution is to exclude the link in the files section of the libs package. And the error is gone on 13.1, too, and it builds fine. At least locally)
This is indeed a new check - it does not mean it was correct on the
previous versions (in fact, it was not: the two packages conflict when
you try to normally install them using rpm) - but the tests evolved and
now catch such errors.
Dominique
--
Dimstar / Dominique Leuenberger
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22.12.14 Dimstar / Dominique Leuenberger wrote:
(in fact, it was not: the two packages conflict when you try to normally install them using rpm)
Uh? Normally, building from the upstream spec should generate two packages lxc and lxc-libs, both of which have to be installed to work with lxc. At least in my other tries it was like this. I'll have a look. Regards, Johannes - -- Outside of a dog, a book is man's best friend. Inside of a dog it's too dark to read. (Groucho Marx) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlSZw2QACgkQzi3gQ/xETbJznACfea2yHuXdNBW/w7xki9Ipnqfh eLoAn2w0p1P7mXtn5tIIJf9/zyh3s9DD =9+rF -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22.12.14 Dimstar / Dominique Leuenberger wrote:
in fact, it was not: the two packages conflict when you try to normally install them using rpm
No, they dont conflict. I just checked. Installing lxc pulls in lxc-libs as dependency. As it is supposed to do. So, why does this error only appear on 13.1? And is not detected/not an error on 13.2? Regards, Johannes - -- "And trust no-- Trust practically no-one. All right? Except trustworthy people." (Terry Pratchett: Jingo) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlSfHWUACgkQzi3gQ/xETbLX1wCfUYkm1n6ZBhAsQS9lhKiXy4w6 jGIAn0wkQTtmJXMgOH1bxvC8oEVBhMYQ =wGqe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (2)
-
Dimstar / Dominique Leuenberger -
Johannes Kastl