Re: pbuilder maybe? Perhaps?
Harald Dunkel wrote: pbuilder seems to be missing. There were no updates in the amd64(gcc-3.4) pool for some days, anyway. Of course if the gcc-3.4 archive has a problem it needs to be fixed. But your note suggests that you are just looking for a good pbuilder package. So I will comment on that, since I can't help with the other. Since pbuilder is an all package it is not dependent upon gcc-3.4. I just updated from the pure64 archive this morning and it did install a new pbuilder. If you were looking for a pbuilder update then you may pull just the architecture pbuilder_0.118_all.deb from any of the sid archives. Bob signature.asc Description: Digital signature
Re: pbuilder maybe? Perhaps?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bob Proulx wrote: | Harald Dunkel wrote: | |pbuilder seems to be missing. There were no updates in the |amd64(gcc-3.4) pool for some days, anyway. | | | Of course if the gcc-3.4 archive has a problem it needs to be fixed. | But your note suggests that you are just looking for a good pbuilder | package. So I will comment on that, since I can't help with the | other. | | Since pbuilder is an all package it is not dependent upon gcc-3.4. | I just updated from the pure64 archive this morning and it did install | a new pbuilder. If you were looking for a pbuilder update then you | may pull just the architecture pbuilder_0.118_all.deb from any of the | sid archives. | | Bob Pbuilder is in the archive. I could manually download and install it. But at runtime (using the same server http://debian-amd64.alioth.debian.org/gcc-3.4) pbuilder complained about the Packages file and about Bash: Distribution is sarge. Building the build environment ~ - running debootstrap I: Retrieving debootstrap.invalid_dists_sarge_Release I: Validating debootstrap.invalid_dists_sarge_Release I: Retrieving debootstrap.invalid_dists_sarge_main_binary-amd64_Packages I: Validating debootstrap.invalid_dists_sarge_main_binary-amd64_Packages W: http://debian-amd64.alioth.debian.org/gcc-3.4/dists/sarge/main/binary-amd64/Packages.gz was corrupt I: Retrieving debootstrap.invalid_dists_sarge_main_binary-amd64_Packages I: Validating debootstrap.invalid_dists_sarge_main_binary-amd64_Packages W: http://debian-amd64.alioth.debian.org/gcc-3.4/dists/sarge/main/binary-amd64/Packages was corrupt I: Checking apt... : : I: Retrieving bash E: Couldn't download bash pbuilder: debootstrap failed ~ - Aborting with an error ~ - cleaning the build env ~- removing directory /var/cache/pbuilder/build//5703 and its subdirectories Would anybody mind to check? Many thanx Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFBhlxcUTlbRTxpHjcRAkXgAJ9bAkWOCLPjYIDI8XgIQnS5ubjicQCcCju3 kZjh2kVmR+/Jm6X4borpDUc= =14pT -END PGP SIGNATURE-
Re: pbuilder maybe? Perhaps?
On 04-Nov-01 16:55, Harald Dunkel wrote: Pbuilder is in the archive. I could manually download and install it. But at runtime (using the same server http://debian-amd64.alioth.debian.org/gcc-3.4) pbuilder complained about the Packages file and about Bash: Distribution is sarge. Building the build environment ~ - running debootstrap I: Retrieving debootstrap.invalid_dists_sarge_Release I: Validating debootstrap.invalid_dists_sarge_Release I: Retrieving debootstrap.invalid_dists_sarge_main_binary-amd64_Packages I: Validating debootstrap.invalid_dists_sarge_main_binary-amd64_Packages W: http://debian-amd64.alioth.debian.org/gcc-3.4/dists/sarge/main/binary-amd64/Packages.gz was corrupt I: Retrieving debootstrap.invalid_dists_sarge_main_binary-amd64_Packages I: Validating debootstrap.invalid_dists_sarge_main_binary-amd64_Packages W: http://debian-amd64.alioth.debian.org/gcc-3.4/dists/sarge/main/binary-amd64/Packages was corrupt I: Checking apt... : : I: Retrieving bash E: Couldn't download bash pbuilder: debootstrap failed ~ - Aborting with an error ~ - cleaning the build env ~- removing directory /var/cache/pbuilder/build//5703 and its subdirectories Would anybody mind to check? pbuilder is trying to debootstrap a 'sarge' chroot environment. The gcc-3.4 archive does not have 'sarge' at the moment, only 'unstable'. This is why the debootstrap cannot download packages from 'sarge' and fails. However, this may change soon. I have prepared a gcc-3.4 version of 'sarge' and I plan to upload it to alioth at the end of this week. The uploading process will take a few days because of the limited upload bandwidth of my internet connection. I had to to do some restructuring in my own gcc-3.4 archive to also handle 'sarge' in addition to 'unstable' and this lead to some delayed package updates on alioth. Sorry for the incoveniece this may have caused. Regards Andreas Jochens
Re: pbuilder maybe? Perhaps?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jochens wrote: | | pbuilder is trying to debootstrap a 'sarge' chroot environment. | The gcc-3.4 archive does not have 'sarge' at the moment, only | 'unstable'. This is why the debootstrap cannot download packages | from 'sarge' and fails. | Pbuilder does not support unstable, only sid. But for sid I get the same error as for sarge: Distribution is sid. Building the build environment ~ - running debootstrap I: Retrieving debootstrap.invalid_dists_sid_Release I: Validating debootstrap.invalid_dists_sid_Release I: Retrieving debootstrap.invalid_dists_sid_main_binary-amd64_Packages I: Validating debootstrap.invalid_dists_sid_main_binary-amd64_Packages W: http://debian-amd64.alioth.debian.org/gcc-3.4/dists/sid/main/binary-amd64/Packages.gz was corrupt I: Retrieving debootstrap.invalid_dists_sid_main_binary-amd64_Packages I: Validating debootstrap.invalid_dists_sid_main_binary-amd64_Packages W: http://debian-amd64.alioth.debian.org/gcc-3.4/dists/sid/main/binary-amd64/Packages was corrupt I: Checking apt... I: Checking base-files... Did you note that there are some Packages.gz files from 4 days ago, while the up-to-date Packages.gz.new are waiting to be renamed? I would suggest to check the write permissions of the Packages.gz and Sources.gz files and maybe the directories. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Debian - http://enigmail.mozdev.org iD8DBQFBhorrUTlbRTxpHjcRAiDRAJ9KQUqq1yEJf+e/bJRIr1KYdk91ZgCeK/0M Kt8+PDtxE3OQUhTab3yG8Es= =eioj -END PGP SIGNATURE-
Re: pbuilder maybe? Perhaps?
On Mon, Nov 01, 2004 at 08:13:48PM +0100, Harald Dunkel wrote: Did you note that there are some Packages.gz files from 4 days ago, while the up-to-date Packages.gz.new are waiting to be renamed? This seems to have been caused by the new archive key. The secret keyring had a size of 0. The script stopped just before it signed the Release file. It's fixed now. Kurt
