[opensuse-packaging] Build issues against openSUSE Tumbleweed
Dear hackers and packagers,
My sincere apologies - once again we are struck by a delete request
having impacts way beyond what we expect to to touch.
As part of the cleanup activities, gcc5 has been removed from the
distro. This also impacts libffi4; The distro has gained a new libffi
implementation (libffi7, version 3.2.1) which has been around for a
while.
As we now deleted libffi4, though, it became apparent that not
everything is yet rebuilt against libffi7 (no real surprise there: we
have the rebuild strategy of least changes implemented)
So far nothing bad - except: as libffi4 has been removed from
openSUSE:Factory, this not only impacts /standard (which we would not
have a problem - ever), but also /snapshot. Which means all the builds
against openSUSE:Tumbleweed will be broken at least until the next
snapshot can be published (0313 that is).
I apologize for this issue caused and will be trying to find a
workaround for now to get you guys going again. Please stay tuned.
Cheers,
Dominique
--
Dimstar / Dominique Leuenberger
On Mon, 2017-03-13 at 16:25 +0100, Dimstar / Dominique Leuenberger wrote:
Dear hackers and packagers,
My sincere apologies - once again we are struck by a delete request having impacts way beyond what we expect to to touch.
As part of the cleanup activities, gcc5 has been removed from the distro. This also impacts libffi4; The distro has gained a new libffi implementation (libffi7, version 3.2.1) which has been around for a while.
As we now deleted libffi4, though, it became apparent that not everything is yet rebuilt against libffi7 (no real surprise there: we have the rebuild strategy of least changes implemented)
So far nothing bad - except: as libffi4 has been removed from openSUSE:Factory, this not only impacts /standard (which we would not have a problem - ever), but also /snapshot. Which means all the builds against openSUSE:Tumbleweed will be broken at least until the next snapshot can be published (0313 that is).
I apologize for this issue caused and will be trying to find a workaround for now to get you guys going again. Please stay tuned.
I filed this as https://progress.opensuse.org/issues/17688
Any ideas are welcome on how to avoid this in the future - the more
automatic it is, the higher the chance of it not failing again.
Please keep the discussion on -buildservice or in the ticket.
-packaging should merely be informed of the outcome in the end.
Cheers,
Dominique
--
Dimstar / Dominique Leuenberger
On Mon, 13 Mar 2017, Dimstar / Dominique Leuenberger wrote:
Dear hackers and packagers,
My sincere apologies - once again we are struck by a delete request having impacts way beyond what we expect to to touch.
As part of the cleanup activities, gcc5 has been removed from the distro. This also impacts libffi4; The distro has gained a new libffi implementation (libffi7, version 3.2.1) which has been around for a while.
As we now deleted libffi4, though, it became apparent that not everything is yet rebuilt against libffi7 (no real surprise there: we have the rebuild strategy of least changes implemented)
So far nothing bad - except: as libffi4 has been removed from openSUSE:Factory, this not only impacts /standard (which we would not have a problem - ever), but also /snapshot. Which means all the builds against openSUSE:Tumbleweed will be broken at least until the next snapshot can be published (0313 that is).
I apologize for this issue caused and will be trying to find a workaround for now to get you guys going again. Please stay tuned.
In the past I was (repeatedly) asking for "old" shlib packages _not_ to be pruned like this but "garbage collected" only. Both from _repository (to avoid dances when doing SONAME updates in Ring-0) and of course from published repositories. But appearantly it's not annoying often enough to warrant fixing... Richard.
Cheers, Dominique
--
Richard Biener
On Tue, 2017-03-14 at 09:30 +0100, Richard Biener wrote:
In the past I was (repeatedly) asking for "old" shlib packages _not_ to be pruned like this but "garbage collected" only. Both from _repository (to avoid dances when doing SONAME updates in Ring-0) and of course from published repositories.
But appearantly it's not annoying often enough to warrant fixing...
Oh it IS annoying enough - at least from a distro-building PoV; sadly, not for OBS it seems. We are currently seeking options on how to design our process to make sure we can avoid this... so far the idea in my head is: * when a delete request is 'ready to accept' - don't accept it, but only build-disable the pkg and wipe the binaries of the package in openSUSE:Factory/standard => this results in the package to be gone from /standard, but the binaries remain in /snapshot * once /standard is copied to /snapshot (so in fact, the snapshot had been built, tested AND published), ultimately accept the delete request Now this sounds very simplistic, but to get it right might be a bit more complex - especially when taking into account that the time between disabling /standard and having the binaries removed from /snapshot is not exactly clear - and we also have to make sure to catch all linked packages of the first one. Add on top of that a new package might be introduced to replace the old one, then the workflow is again different. But this is what we are currently trying to work out from the distro process side of things - as the tooling so far does not allow us to 'just go ahead'. cheers, Dominique
On Mon, 2017-03-13 at 16:25 +0100, Dimstar / Dominique Leuenberger wrote:
Dear hackers and packagers,
My sincere apologies - once again we are struck by a delete request having impacts way beyond what we expect to to touch.
As part of the cleanup activities, gcc5 has been removed from the distro. This also impacts libffi4; The distro has gained a new libffi implementation (libffi7, version 3.2.1) which has been around for a while.
With the successful testing and publishing og the 0314 snapshot we
should have resolved this problem and building packages for openSUSE
Tumbleweed should be functional without this problem again.
you might need to trigger a rebuild in case OBS ended the build with
"Failed to find banaries: libffi4"
Cheers,
Dominique
--
Dimstar / Dominique Leuenberger
On 03/15/2017 10:30 AM, Dimstar / Dominique Leuenberger wrote:
With the successful testing and publishing og the 0314 snapshot we should have resolved this problem and building packages for openSUSE Tumbleweed should be functional without this problem again. Thanks! you might need to trigger a rebuild in case OBS ended the build with "Failed to find banaries: libffi4" Couldn't this be triggered for all packages in this state?
-- python programming - mail server - photo - video - https://sebix.at cryptographic key at https://sebix.at/DC9B463B.asc and on public keyservers
participants (3)
-
Dimstar / Dominique Leuenberger -
Richard Biener -
Sebastian