A few packages have "Requires: boost-devel" in their -devel subpackage. This leads to unresolved dependencies like this:
have choice for boost-devel needed by whatever-devel: boost_1_58_0-devel boost-devel
This happens only in Leap 42.1 and 42.2. How is boost supposed to be used? If there are indeed two packages providing the same thing within a prj, then this base prj must add the relevant Prefer:.
And for some reason this started to happen only recently, the last successful build is from 2016-12-02.
Olaf
On Mittwoch, 21. Dezember 2016, 12:27:13 CET wrote Olaf Hering:
A few packages have "Requires: boost-devel" in their -devel subpackage. This leads to unresolved dependencies like this:
have choice for boost-devel needed by whatever-devel: boost_1_58_0-devel boost-develThis happens only in Leap 42.1 and 42.2. How is boost supposed to be used?
If there are indeed two packages providing the same thing within a prj, then this base prj must add the relevant Prefer:.
a de-prefer to the 1.58 one here actually.
And for some reason this started to happen only recently, the last successful build is from 2016-12-02.
no idea.
On Mittwoch, 21. Dezember 2016, 12:55:07 CET wrote Adrian Schröter:
On Mittwoch, 21. Dezember 2016, 12:27:13 CET wrote Olaf Hering:
A few packages have "Requires: boost-devel" in their -devel subpackage. This leads to unresolved dependencies like this:
have choice for boost-devel needed by whatever-devel: boost_1_58_0-devel boost-develThis happens only in Leap 42.1 and 42.2. How is boost supposed to be used?
If there are indeed two packages providing the same thing within a prj, then this base prj must add the relevant Prefer:.
a de-prefer to the 1.58 one here actually.
And for some reason this started to happen only recently, the last successful build is from 2016-12-02.
no idea.
Just for the record, with last packaging changes of boost, the recommended way to use it is always
BuildRequires: boost-devel
and when you need a special version
BuildRequires: boost-devel > 1.55
for example
Am 21.12.2016 um 12:55 schrieb Adrian Schröter:
If there are indeed two packages providing the same thing within a prj, then this base prj must add the relevant Prefer:.
a de-prefer to the 1.58 one here actually.
I guess I lack the permissions to adjust prjconf in openSUSE:Leap:42.*:Update, where it belongs.
Olaf
On 12/21/2016 01:08 PM, Olaf Hering wrote:
Am 21.12.2016 um 12:55 schrieb Adrian Schröter:
If there are indeed two packages providing the same thing within a prj, then this base prj must add the relevant Prefer:.
a de-prefer to the 1.58 one here actually.
I guess I lack the permissions to adjust prjconf in openSUSE:Leap:42.*:Update, where it belongs.
Yes, these ambiguities need to be resolved in Project Config. The reason that Boost 1.58 was fixed to provide boost-devel is
https://bugzilla.opensuse.org/show_bug.cgi?id=974690
- Adam
Olaf Hering wrote:
A few packages have "Requires: boost-devel" in their -devel subpackage. This leads to unresolved dependencies like this:
have choice for boost-devel needed by whatever-devel: boost_1_58_0-devel boost-develThis happens only in Leap 42.1 and 42.2. How is boost supposed to be used? If there are indeed two packages providing the same thing within a prj, then this base prj must add the relevant Prefer:.
And for some reason this started to happen only recently, the last successful build is from 2016-12-02.
Caused by an online update for boost. I've applied the fix we added in 42.3 now also to 42.2 and 42.1 prjconf's.
cu Ludwig
-
Adam Majer -
Adrian Schröter -
Ludwig Nussel -
Olaf Hering