Bug #6386
open
- Status changed from New to In Progress
- % Done changed from 0 to 10
(eclipse-titan is enabled for debian unstable)
Right now, dependency resolving fails for all debian unstable packages:
- "have choice for libdb5.3 needed by libperl5.38: libdb5.3 libdb5.3t64"
- "have choice for libevent-2.1-7 >= 2.1.8-stable needed by libunbound8: libevent-2.1-7 libevent-2.1-7t64"
I have tried "Prefer" in the project config as usually: https://en.opensuse.org/openSUSE:Build_Service_prjconf#Prefer
For similar errors this had fixed it in the past, but here it doesn't work. I've asked in the opensuse-buildservice IRC.
On Mon, Mar 04, 2024 at 10:09:30AM +0000, osmith wrote:
- "have choice for libdb5.3 needed by libperl5.38: libdb5.3 libdb5.3t64"
't64' refers to 64bit time_t, so this likely only affects 32bit architectures; amd64 always had 64bit time_t
as fer as I know.
https://wiki.debian.org/ReleaseGoals/64bit-time
laforge wrote in #note-2:
On Mon, Mar 04, 2024 at 10:09:30AM +0000, osmith wrote:
- "have choice for libdb5.3 needed by libperl5.38: libdb5.3 libdb5.3t64"
't64' refers to 64bit time_t, so this likely only affects 32bit architectures; amd64 always had 64bit time_t
as fer as I know.
https://wiki.debian.org/ReleaseGoals/64bit-time
It does affect our x86_64 packages.
IRC:
13:04:08 <adrianS> I have now a horrible workaround for that in our Debian:Unstable project ... and it solved the unresolvable here at least
13:04:39 <adrianS> but it seems you need to prefer the new t64 libs now or you run into dependency issues
13:30:54 <adrianS> osmith: there are follow up problems now at build time, but I don't have time for that atm
14:15:12 <bluca> most of the t64 stuff is there to say, unfortunately
14:15:20 <bluca> /say/stay/
14:15:41 <bluca> huge amount of effort for two dead architectures
14:15:56 <bluca> only libpam, libselinux and libuuid will be reverted as they got patched to do dual-abi
14:16:20 <bluca> I'd recommend to stay away from unstable for a week or two, it will take a long time for the dust to settle, and any workaround added today might not work tomorrow
Also available in: Atom
PDF
