Dear Debian-Devel, we need your advices.

Yesterday, we (the qt-kde packagers) uploaded qt3 version 3.3.8b. The biggest
differences over 3.3.7 is that it is now also gplv3 licensed.

And then this bug report came:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465028 - libqt3-mt: Missing
weak symbols for stat64 functions

basically, in qt3 3:3.3.7-9 and earlier, libqt3-mt seems to provide some
symbols:

$ objdump -T libqt-mt.so.3 | grep stat64
004d2d9e w DF .text 00000032 Base stat64
002f19de w DF .text 00000032 Base fstat64
005dcba0 w DF .text 00000032 Base lstat64

These symbols are also provided by the etch package of libqt3-mt.

With this newly built qt3 3.3.8b, these symbols is no longer provided. A
newly rebuilt version of 3:3.3.7-9 is also not providing these symbols, which
kind of makes it looks like a toolchain issue.

Some packages expects these symbols (gwenview, ktorrent, virtualbox-ose and
probably many others)

The question is simply: How to proceed?
Do it like ubuntu did and just binNMU the packages expecting these symbols?
Locate the packages expecting these symbols and have a gigantic Conflicts:
line?
Kick in a major transition and rename libqt3-mt and rebuild all rdpendencies
Isolate the toolchain change and revert it?
something else?

I am not in favour of just binNMUing everything, as we breaks partial upgrades
I am also not in favour of the big mess it would be to package-namechange qt3

And I don't know if other packages are affected by the same toolchain change ?

Any advice is most appreciated.

/Sune
--
I cannot cancel a GPU, how does it work?

You must ping a connection on the fan of the Ultra 3D tower for inserting in
the controller on the forward.

> it looks like a toolchain issue.

Some people point to binutils 2.17 -> 2.18.
We think about a binutils-2.17 bug that ?stat64 appeared in the first place.
Indeed, ?stat64 weren't defined in Qt3.

> Some packages expects these symbols (gwenview, ktorrent, virtualbox-ose and
> probably many others)

so far, identified packages are:

k3b
kdebase
ktorrent
gwenview (already rebuilded against Qt3.3.8b)
virtualbox-ose

> Do it like ubuntu did and just binNMU the packages expecting these symbols?

I'm in favor of binNMU needed packages.
For informations, KDE 3.5.9 will be tagged on february 13th and
released on 19th.
In case of binNMU, we can skip KDE3 packages and wait for KDE 3.5.9 upload.

> And I don't know if other packages are affected by the same toolchain change ?

ldd -r -d 2>&1 | grep undefined | grep stat64 on /usr/lib and /usr/lib/kde3

I found some other undefined not related to ?stat64 symbols.

cheers,

Fathi


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Am Montag, 11. Februar 2008 09:45:32 schrieb fboudra@gmail.com:
> so far, identified packages are:
>
> k3b
> kdebase
> ktorrent
> gwenview (already rebuilded against Qt3.3.8b)
> virtualbox-ose
I've a rebuilded virtualbox-ose against the newest qt3.38b but wanted to
wait with an upload, until I know what exactly will happen with this bug.
If we decide to binNMU, I'll upload this package.. it contains not only a
fix for this issue but for some other issues, too.

>
> > Do it like ubuntu did and just binNMU the packages expecting these
> > symbols?
>
> I'm in favor of binNMU needed packages.
I would also favour to binNMU all needed packages.

Greetings
Winnie

--
.'`. Patrick Winnertz <winnie@debian.org>
: :' : GNU/Linux Debian Developer
`. `'` http://www.der-winnie.de http://people.skolelinux.org/~winnie
`- Debian - when you have better things to do than fixing systems

On Sun, Feb 10, 2008 at 08:44:02PM +0100, Sune Vuorela wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465028 - libqt3-mt: Missing
> weak symbols for stat64 functions

libqt3-mt isn't supposed to provide stat64, right?

> The question is simply: How to proceed?
> Do it like ubuntu did and just binNMU the packages expecting these symbols?

This is what I would suppose.

> I am not in favour of just binNMUing everything, as we breaks partial upgrades

Could you elaborate?

> And I don't know if other packages are affected by the same toolchain change ?

The big question here is, what exactly happened.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 2008-02-11, Michael Meskes <meskes@debian.org> wrote:
> On Sun, Feb 10, 2008 at 08:44:02PM +0100, Sune Vuorela wrote:
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465028 - libqt3-mt: Missing
>> weak symbols for stat64 functions
>
> libqt3-mt isn't supposed to provide stat64, right?

I don't think so, no.

>> The question is simply: How to proceed?
>> Do it like ubuntu did and just binNMU the packages expecting these symbols?
>
> This is what I would suppose.
>
>> I am not in favour of just binNMUing everything, as we breaks partial upgrades
>
> Could you elaborate?

Someone is running etch, but wants the newest ksomething from testing.
That newest ksomething will quite soon pull in libqt3-mt from 3.3.8b
with dropped symbols.
That means that half his kde programs doesn't work anymore.


/Sune


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Feb 11, 2008 at 10:04:53AM +0100, Patrick Winnertz wrote:
> I've a rebuilded virtualbox-ose against the newest qt3.38b but wanted to
> wait with an upload, until I know what exactly will happen with this bug.
> If we decide to binNMU, I'll upload this package.. it contains not only a
> fix for this issue but for some other issues, too.

???

Which other issues do you think you fix in an binNMU? Keep in mind that
we talk about rebuilding 1.5.4-dfsg-4.

Michael

--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

> On Mon, Feb 11, 2008 at 10:04:53AM +0100, Patrick Winnertz wrote:
> > I've a rebuilded virtualbox-ose against the newest qt3.38b but wanted to
> > wait with an upload, until I know what exactly will happen with this bug.
> > If we decide to binNMU, I'll upload this package.. it contains not only a
> > fix for this issue but for some other issues, too.
>
> ???
>
> Which other issues do you think you fix in an binNMU? Keep in mind that
> we talk about rebuilding 1.5.4-dfsg-4.

if we choose the binNMU needed packages way,
virtualbox-ose binNMU will become useless in case of a 1.5.4-dfsg-5
upload is pending.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On Mon, Feb 11, 2008 at 12:01:47PM +0100, Fathi Boudra wrote:
> if we choose the binNMU needed packages way,
> virtualbox-ose binNMU will become useless in case of a 1.5.4-dfsg-5
> upload is pending.

Yes, I got confused by this email talking about a new version and
binNMUs.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On 2008-02-10, Sune Vuorela <debian@pusling.com> wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D465028 - libqt3-mt: Miss=
> ing=20
> weak symbols for stat64 functions
>
> basically, in qt3 3:3.3.7-9 and earlier, libqt3-mt seems to provide some=20
> symbols:
>
> $ objdump -T libqt-mt.so.3 | grep stat64
> 004d2d9e w DF .text 00000032 Base stat64
> 002f19de w DF .text 00000032 Base fstat64
> 005dcba0 w DF .text 00000032 Base lstat64

I have now tried different things:

Etch chroot with the following packages pulled from unstable:
binutils console-tools cpp-4.1 g++-4.1 gcc-4.1 gcc-4.1-base
gcc-4.3-base libc6 libgcc1 libncurses5 libselinux1 libslang2
libstdc++6 libstdc++6-4.1-dev
linux-libc-dev tzdata libc6-dev

the stat64 symbols was missing

Etch chroot with linux-libc-dev from unstable installed

the stat64 symbols was around

Etch chroot with backported unstable binutils:

the stat64 symbols was around

Etch chroot with backported binutils build with backported binutils:

the stat64 symbols was around

Etch chroot with backported binutils build with backported binutils and
linux-libc-dev pulled in from unstable:

the stat64 symbols was around


Any advice on how to proceed is still more than welcome

/Sune


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

On dim, fév 10, 2008 at 07:44:02 +0000, Sune Vuorela wrote:
> Dear Debian-Devel, we need your advices.
>
> Yesterday, we (the qt-kde packagers) uploaded qt3 version 3.3.8b. The biggest
> differences over 3.3.7 is that it is now also gplv3 licensed.
>
> And then this bug report came:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465028 - libqt3-mt: Missing
> weak symbols for stat64 functions
>
> basically, in qt3 3:3.3.7-9 and earlier, libqt3-mt seems to provide some
> symbols:
>
> $ objdump -T libqt-mt.so.3 | grep stat64
> 004d2d9e w DF .text 00000032 Base stat64
> 002f19de w DF .text 00000032 Base fstat64
> 005dcba0 w DF .text 00000032 Base lstat64

We tracked the issue down. The thing is that libc6 used (before 2.7)
to "export inline" those symbols, whereas now it's only done for C (not
C++) and when gcc is >= 4.3.

The thing is, when not using visiblity=hidden, 'extern inline' emits
symbols in the resulting binary. The glibc _was_ wrong before, and it
now has the proper behavior. Though, it means that some libraries had
stat64 and friends exported in them, and that may cause lot of grief.

A list of packages having or using those three symbols are beeing
built, I'm unsure about what should be done about them, it's _not_ only
qt3 that will have issues here.

--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org