libglib2.0-0t64 vs libglib2.0-0 dependencies

[Ed Robbins]

Hi all,
I have noticed that there have been a few broken packages on the
repository for some time, that presumably need to be rebuilt or fixed
after libglib2.0 moved to t64. Notably I have been wanting to install
xpra for a while but it has not been updated.

Is this a problem specific to our port or is it a wider problem? Is it
being tracked anywhere? A brief search didn't turn up anything.

Thanks,
Ed

[John Paul Adrian Glaubitz]

Hello Ed,

Post by Ed Robbins
I have noticed that there have been a few broken packages on the
repository for some time, that presumably need to be rebuilt or fixed
after libglib2.0 moved to t64. Notably I have been wanting to install
xpra for a while but it has not been updated.
Is this a problem specific to our port or is it a wider problem? Is it
being tracked anywhere? A brief search didn't turn up anything.

Such situations can occur when the package in question or one of its build
dependencies didn't build successfully. It can also occur that one of the
build dependencies went away before the package could be rebuilt due to the
way Debian Port works [1].

Just let me know which packages are affected and I can look into fixing it.

Adrian

Post by Ed Robbins
[1] https://lists.debian.org/debian-sparc/2017/12/msg00060.html

[John Paul Adrian Glaubitz]

Post by John Paul Adrian Glaubitz
Such situations can occur when the package in question or one of its build
dependencies didn't build successfully.

The former is true: https://buildd.debian.org/status/package.php?p=xpra&suite=sid

On this page, you will two bug reports referenced and both refer to an FTBFS.

So, if you want to use xpra, someone needs to fix the package.

Adrian

[Ed Robbins]

Post by John Paul Adrian Glaubitz

Post by John Paul Adrian Glaubitz
Such situations can occur when the package in question or one of its build
dependencies didn't build successfully.

The former is true: https://buildd.debian.org/status/package.php?p=xpra&suite=sid
On this page, you will two bug reports referenced and both refer to an FTBFS.
So, if you want to use xpra, someone needs to fix the package.
Adrian

Thanks Adrian. It turns out that the version in debian is ancient anyway, so I will just try to build a newer package.

Ed

Post by John Paul Adrian Glaubitz
--
.''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

[John Paul Adrian Glaubitz]

So basically Pidgin won't work anymore? It required Glib 2.0

Could you please keep this on-list?

And please don't forget that this is a community project, so if you
see something broken, I suggest looking into how you can help.

Thanks,
Adrian

[Leo Historias]

What? It's on-list since it's an app requiring it,

On Thu, Oct 31, 2024 at 2:09 PM John Paul Adrian Glaubitz <

Post by John Paul Adrian Glaubitz

So basically Pidgin won't work anymore? It required Glib 2.0

Could you please keep this on-list?
And please don't forget that this is a community project, so if you
see something broken, I suggest looking into how you can help.
Thanks,
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913

[John Paul Adrian Glaubitz]

Post by Leo Historias
What? It's on-list since it's an app requiring it,

I was talking about keeping the discussion on the mailing list, your
previous mail was off-list and therefore only visible by me.

As for Pidgin, like I have explained, I cannot fix every bug in the
universe that affects PowerPC. I'm doing this just as a hobby and
I'm already investing quite a lot of time into this.

Without my work, it wouldn't even possible to install any recent version
of Debian on any of the architectures that I'm maintaining.

If you see a particular thing that you want to get fixed, you can either
give it a try yourself or file a bug report (preferably upstream).

Adrian

[Ed Robbins]

On Sat, 2 Nov 2024 at 11:13, John Paul Adrian Glaubitz

Post by John Paul Adrian Glaubitz
As for Pidgin, like I have explained, I cannot fix every bug in the
universe that affects PowerPC. I'm doing this just as a hobby and
I'm already investing quite a lot of time into this.

I am not sure exactly what the issue is with pidgin, but if it's just
a concern about availability of glib 2.0, then there is no need for
concern. Glib 2.0 is still there, it's just been updated to use 64 bit
time_t to avoid the 2038 problem. The change breaks the ABI, which
means that packages that are dependent on glib 2.0 need to be rebuilt,
that's all. Pidgin is available in the repository and presumably has
already been rebuilt.

xpra breakage seems to be unrelated to glib after all, it's just that
the last version that built successfully and is in the debian
repository was built against 32 bit time_t version of glib 2.0. The
version of xpra in debian is too old to be really useful in any case
(if I remember rightly it is version 3.something, and the latest
version is 6.something).

Ed