Re: Checking package builds on hppa/arm/m68k?
Andreas Fester [EMAIL PROTECTED] writes: Benjamin Mesing wrote: Please (re)check, if the package can be built by g++ 3.4 on [hppa/arm/m68k]? Do I simply remove the explicit build dependency on g++, upload the package and wait if it succeeds (and probably create another package version with the build dependencies re-added again if it still fails)? As Matthias Klose in his announce [1], this workaround is no longer needed (if you are speaking about the issue affecting a lot of QT/KDE My issue was the ICE which occured on these platforms for (also non-Qt/KDE) c++ builds (I think this is not related to the mt_alloc issue): http://lists.debian.org/debian-gcc/2005/11/msg00123.html Since this bug seems to be solved now, and Matthias also said Please (re)check, if the package can be built I was just wondering what the proper way of checking is. Best Regards, Andreas Normaly you have 3 choices: 1. log into the Debian systems for each arch and check 2. upload and reupload if it still fails Only if the problem should be gone now, e.g. the gcc ICE bug got closed. You should probably 'Build-Depends: g++-3.4 (= fixed-version) [arch]' to force a g++ update before build. 3. ask the porters As non DD (1) becomes difficult and (2) can be tiresome to your sponsor and yourself. (3) on the other hand is also work. MfG Goswin PS: I would upload the package to be build with the normal g++-3.4 and leave it failed on some archs unless it is something critical. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Checking package builds on hppa/arm/m68k?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Benjamin Mesing wrote: Please (re)check, if the package can be built by g++ 3.4 on [hppa/arm/m68k]? Do I simply remove the explicit build dependency on g++, upload the package and wait if it succeeds (and probably create another package version with the build dependencies re-added again if it still fails)? As Matthias Klose in his announce [1], this workaround is no longer needed (if you are speaking about the issue affecting a lot of QT/KDE My issue was the ICE which occured on these platforms for (also non-Qt/KDE) c++ builds (I think this is not related to the mt_alloc issue): http://lists.debian.org/debian-gcc/2005/11/msg00123.html Since this bug seems to be solved now, and Matthias also said Please (re)check, if the package can be built I was just wondering what the proper way of checking is. Best Regards, Andreas - -- Andreas Fester mailto:[EMAIL PROTECTED] WWW: http://www.littletux.net ICQ: 326674288 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDpTaOZ3bQVzeW+rsRAqssAKCIm2IibmZ+21T0/cOXcnHiExcBRACg86lb g3/efB0Nful/iyDqfD8SMng= =f138 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Checking package builds on hppa/arm/m68k?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, what is the proper way to Please (re)check, if the package can be built by g++ 3.4 on [hppa/arm/m68k]? Do I simply remove the explicit build dependency on g++, upload the package and wait if it succeeds (and probably create another package version with the build dependencies re-added again if it still fails)? Or are there any sandboxes (I am no Debian Developer) to try it on specific architectures before uploading? Thanks Best Regards, Andreas - -- Andreas Fester mailto:[EMAIL PROTECTED] WWW: http://www.littletux.net ICQ: 326674288 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDo8VzZ3bQVzeW+rsRApGoAJ0dyjxkOUxeUmCl7sY76v4D24ugKwCg2ANZ UogPtvGck0JsTdU3j0QdO6k= =Hesk -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Checking package builds on hppa/arm/m68k?
Andreas Fester [EMAIL PROTECTED] wrote: [...] what is the proper way to Please (re)check, if the package can be built by g++ 3.4 on [hppa/arm/m68k]? Do I simply remove the explicit build dependency on g++, upload the package and wait if it succeeds (and probably create another package version with the build dependencies re-added again if it still fails)? Or are there any sandboxes (I am no Debian Developer) to try it on specific architectures before uploading? [...] I'd ask on the respective porter mailinglists. cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken.(c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Checking package builds on hppa/arm/m68k?
Please (re)check, if the package can be built by g++ 3.4 on [hppa/arm/m68k]? Do I simply remove the explicit build dependency on g++, upload the package and wait if it succeeds (and probably create another package version with the build dependencies re-added again if it still fails)? As Matthias Klose in his announce [1], this workaround is no longer needed (if you are speaking about the issue affecting a lot of QT/KDE programs). Best regards Ben [1] http://lists.debian.org/debian-devel-announce/2005/11/msg00010.html -- Please do not send any email to [EMAIL PROTECTED] -- all email not originating from the mailing list will be deleted. Use the reply to address instead. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
