Re: Rebuild of the libqt3.
On 05-Feb-19 00:31, Javier Kohen wrote: > > Cvs 1.12.9-11 from gcc-3.4 seems to work fine now. I'll report if it This is good to know. I could not make cvs work properly with either gcc-3.4 or gcc-4.0 before. It compiled but it did not work at all. Thanks for the report. Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
Cvs 1.12.9-11 from gcc-3.4 seems to work fine now. I'll report if it starts behaving funny later on. The recompiled python is still broken, and I don't have libqt3 installed. Cheers, Javier Kohen wrote: Thanks a lot. If not compiling counts, then wxwidgets2.5 should enter the list. It compiles cleanly (at least until I ran out of space) with apt-src and gcc-3.4 where it won't go past the configure stage in the last autobuilder build. Andreas Jochens wrote On 05-Feb-17 17:34, Javier Kohen wrote: Can we mark some packages as "broken by compiler" so when a new version of the compiler reaches the archive we can recompile them and see if the problem was fixed? This is a good idea. I will take your list as a start and schedule all listed packages for recompilation whenever a new version of gcc-4.0 becomes available. Some candidates: libqt3 (already being handled) cvs (just guessing here, but it works if compiled with 3.4) python2.3 (see a post by me from two days ago for a detailed explanation of (one of?) the problem) xfree86 (based on a post by Andreas) Please report any other packages which appear to have similar problems. Regards Andreas Jochens -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
[EMAIL PROTECTED] writes: > On Thu, Feb 17, 2005 at 04:49:51PM +0100, Goswin von Brederlow wrote: >> > Should I file a bug report ? >> >> Against what? If a recompile fixes the problem then libQT3 is not to >> blame. No, you just have to get Andreas to rebuild it. > > Againt miscompilation of this package , it must be treaten as if there > was code broken since the package makes major packages unusable > (everything that depends on libqt3, quite a lot of packages to my opinion). > > Something like libqt3-3.3.3-8.0.0.1.1, > with changelog: > fix bad generation of the package. > > Don't know why it should be treaten differently as a bug (it is a bug). > > seb For bugs to be filed we would need to have a BTS running. I doubt Debian maintainers would welcome having amd64 and especially gcc-4.0 bugs intrude on their packages. hmm, hey, we have a BTS on alioth. We could start using the bug tracker there? What we can do is mark those packages in wanna-build, anyone with an alioth account and in the debian-amd64 group can do that. Maybe someone can even implement some shell code for the wanna-build + build.sh that would trigger a rebuild on certain contidions (in wanna-build) and increase the version (in build.sh). MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
Thanks a lot. If not compiling counts, then wxwidgets2.5 should enter the list. It compiles cleanly (at least until I ran out of space) with apt-src and gcc-3.4 where it won't go past the configure stage in the last autobuilder build. Andreas Jochens wrote On 05-Feb-17 17:34, Javier Kohen wrote: Can we mark some packages as "broken by compiler" so when a new version of the compiler reaches the archive we can recompile them and see if the problem was fixed? This is a good idea. I will take your list as a start and schedule all listed packages for recompilation whenever a new version of gcc-4.0 becomes available. Some candidates: libqt3 (already being handled) cvs (just guessing here, but it works if compiled with 3.4) python2.3 (see a post by me from two days ago for a detailed explanation of (one of?) the problem) xfree86 (based on a post by Andreas) Please report any other packages which appear to have similar problems. Regards Andreas Jochens -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
On 05-Feb-17 17:34, Javier Kohen wrote: > Can we mark some packages as "broken by compiler" so when a new version > of the compiler reaches the archive we can recompile them and see if the > problem was fixed? This is a good idea. I will take your list as a start and schedule all listed packages for recompilation whenever a new version of gcc-4.0 becomes available. > Some candidates: > libqt3 (already being handled) > cvs (just guessing here, but it works if compiled with 3.4) > python2.3 (see a post by me from two days ago for a detailed > explanation of (one of?) the problem) > xfree86 (based on a post by Andreas) Please report any other packages which appear to have similar problems. Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
Hi all, Can we mark some packages as "broken by compiler" so when a new version of the compiler reaches the archive we can recompile them and see if the problem was fixed? Some candidates: libqt3 (already being handled) cvs (just guessing here, but it works if compiled with 3.4) python2.3 (see a post by me from two days ago for a detailed explanation of (one of?) the problem) xfree86 (based on a post by Andreas) Thanks, [EMAIL PROTECTED] wrote: Againt miscompilation of this package , it must be treaten as if there was code broken since the package makes major packages unusable (everything that depends on libqt3, quite a lot of packages to my opinion). Something like libqt3-3.3.3-8.0.0.1.1, with changelog: fix bad generation of the package. Don't know why it should be treaten differently as a bug (it is a bug). -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] -- Javier Kohen <[EMAIL PROTECTED]> ICQ: blashyrkh #2361802 Jabber: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
On Thu, Feb 17, 2005 at 04:49:51PM +0100, Goswin von Brederlow wrote: > >> > Can someone please regenerate the packages since apt-get keeps writing > >> > the alioth packages over the localy built packages. > > A small note, packages should never just be regenerated. A deb package > file should never ever change since that causes all kinds of > logistical problems. The version MUST be increased. Yes, I understand. > > > > Sure I could do this. I could build my own debian alone and not sharing > > this with others. > > > > This would fix it for me, not for the others, fix it the repo then > > everyone should benefit for it. > > Going by your mail you already did compile it locally. Changing the > version is just so that apt-get won't undo your manual fix and you > don't get anoyed. Your choice ultimately. As I previously said, the fix is ok for me. > > > My point is that your version of libQT3 package in the repo is utterly > > broken and makes the kde desktop unusable and this is not an amd64 bug, > > but a miscompilation of the package. So, why not bumping the release in > > the repo and makes another build ? > > You have to ask Andreas for that. He is the only one building packages > for gcc-3.4. Ok, I think he already noticed the problem and agreed to rebuild it. > > > Should I file a bug report ? > > Against what? If a recompile fixes the problem then libQT3 is not to > blame. No, you just have to get Andreas to rebuild it. Againt miscompilation of this package , it must be treaten as if there was code broken since the package makes major packages unusable (everything that depends on libqt3, quite a lot of packages to my opinion). Something like libqt3-3.3.3-8.0.0.1.1, with changelog: fix bad generation of the package. Don't know why it should be treaten differently as a bug (it is a bug). seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
[EMAIL PROTECTED] writes: > On Thu, Feb 17, 2005 at 07:57:03AM +0100, Goswin von Brederlow wrote: >> [EMAIL PROTECTED] writes: >> >> > Can someone please regenerate the packages since apt-get keeps writing >> > the alioth packages over the localy built packages. A small note, packages should never just be regenerated. A deb package file should never ever change since that causes all kinds of logistical problems. The version MUST be increased. >> Add a new changelog entry to the source and add +b0.1 to the >> version. Then rebuild and install. Since now your loac version is >> higher apt-get won't reinstall the gcc-3.4 version anymore. >> >> MfG >> Goswin >> > > Sure I could do this. I could build my own debian alone and not sharing > this with others. > > This would fix it for me, not for the others, fix it the repo then > everyone should benefit for it. Going by your mail you already did compile it locally. Changing the version is just so that apt-get won't undo your manual fix and you don't get anoyed. Your choice ultimately. > My point is that your version of libQT3 package in the repo is utterly > broken and makes the kde desktop unusable and this is not an amd64 bug, > but a miscompilation of the package. So, why not bumping the release in > the repo and makes another build ? You have to ask Andreas for that. He is the only one building packages for gcc-3.4. > Should I file a bug report ? Against what? If a recompile fixes the problem then libQT3 is not to blame. No, you just have to get Andreas to rebuild it. > Seb MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
For what it's worth, I'm also seeing this weird behaviour in my kde apps (started from gnome, I don't really use KDE). I'm using gcc-3.4 too. Will this be fixed in the repository ? I can build my own package if it fixes the problem, but I can wait a little longer. Thanks in advance, Manuel On Thu, 17 Feb 2005 07:57:03 +0100, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] writes: > > > Can someone please regenerate the packages since apt-get keeps writing > > the alioth packages over the localy built packages. > > Add a new changelog entry to the source and add +b0.1 to the > version. Then rebuild and install. Since now your loac version is > higher apt-get won't reinstall the gcc-3.4 version anymore. > > MfG > Goswin > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
On 05-Feb-17 12:36, Manuel Capinha wrote: > For what it's worth, I'm also seeing this weird behaviour in my kde > apps (started from gnome, I don't really use KDE). I'm using gcc-3.4 > too. > > Will this be fixed in the repository ? I can build my own package if > it fixes the problem, but I can wait a little longer. I will upload a fixed version to the gcc-3.4 archive as soon as I have completed some tests on my own desktop machine. Thank you for your patience. Regards Andreas Jochens -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
On Thu, Feb 17, 2005 at 07:57:03AM +0100, Goswin von Brederlow wrote: > [EMAIL PROTECTED] writes: > > > Can someone please regenerate the packages since apt-get keeps writing > > the alioth packages over the localy built packages. > > Add a new changelog entry to the source and add +b0.1 to the > version. Then rebuild and install. Since now your loac version is > higher apt-get won't reinstall the gcc-3.4 version anymore. > > MfG > Goswin > Sure I could do this. I could build my own debian alone and not sharing this with others. This would fix it for me, not for the others, fix it the repo then everyone should benefit for it. My point is that your version of libQT3 package in the repo is utterly broken and makes the kde desktop unusable and this is not an amd64 bug, but a miscompilation of the package. So, why not bumping the release in the repo and makes another build ? Should I file a bug report ? Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
[EMAIL PROTECTED] writes: > Can someone please regenerate the packages since apt-get keeps writing > the alioth packages over the localy built packages. Add a new changelog entry to the source and add +b0.1 to the version. Then rebuild and install. Since now your loac version is higher apt-get won't reinstall the gcc-3.4 version anymore. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
On Thu, Feb 17, 2005 at 12:20:57AM +0100, Kurt Roeckx wrote: [snip] > > > > The libqt3c102-mt and libqt3c102 are broken on alioth. > > I wish I had access to the repository to put the recompiled binaries but > > I have not. > > > > Can someone please regenerate the packages since apt-get keeps writing > > the alioth packages over the localy built packages. > > > > This is quite annoying I think. > > Is this the pure64 or the gcc-3.4 port? > > And what is exactly the problem you have with them? > > > Kurt > Oopps sorry, I forgot all those informations. This is the gcc-3.4 port and the problem is a bad widget rendering which is quite obvious when you install the packages and restart kde. I can send you screenshots if you want. For example, in the konsole menus, only the title of the first menu (session) is displayed despite the fact that other menus are not displayed, they are selectable. Trying the font selector show only one font (it was the bitstream one). Editable widget in kdm show garbage under the box, the hierachical tree widget used in the knode for example, is completely messed up. And so on... Rebuilding this package from source and installing it fixes the problem (with gcc-3.4). Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Rebuild of the libqt3.
On Thu, Feb 17, 2005 at 12:09:30AM +0100, [EMAIL PROTECTED] wrote: > Second message since the first was of no interest to anyone. > > The libqt3c102-mt and libqt3c102 are broken on alioth. > I wish I had access to the repository to put the recompiled binaries but > I have not. > > Can someone please regenerate the packages since apt-get keeps writing > the alioth packages over the localy built packages. > > This is quite annoying I think. Is this the pure64 or the gcc-3.4 port? And what is exactly the problem you have with them? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
