Project

General

Profile

Actions

Bug #6386

open

eclipse-titan 9.0.0 not building in debian unstable

Added by laforge about 2 months ago. Updated about 2 months ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
-
Start date:
03/02/2024
Due date:
% Done:

10%

Spec Reference:

Description

I just ran into bugs caused by running a too old version of eclipse-titan (8.2.0 provided by debian), since our 9.0.0 is not building on unstable: https://obs.osmocom.org/package/show/osmocom:latest/eclipse-titan

Please have a look, thanks!

Actions #1

Updated by osmith about 2 months ago

  • 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.

Actions #2

Updated by laforge about 2 months ago

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

Actions #3

Updated by osmith about 2 months ago

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
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)