no such option --append-version in recipe build

[Jelmer Vernooij]

The lucid recipe build of bzr is failing with the following error:

Building recipe:
# bzr-builder format 0.2 deb-version 2.3~beta3+bzr{revno}~ppa{revno:packaging}+{revno:debian}
lp:bzr
merge packaging lp:~bzr/bzr/daily-ppa
merge debian lp:~debian-bazaar/bzr/experimental

Running in chroot: 'sudo' '-i' '-u' 'buildd' '<email address hidden>' 'DEBFULLNAME=Launchpad Package Builder' 'BZR_EMAIL=buildd@lansones' 'bzr' 'dailydeb' '--no-build' '/home/buildd/work/recipe' '/home/buildd/work/tree' '--manifest' '/home/buildd/work/tree/manifest' '--append-version' '~lucid1'
bzr: ERROR: no such option: --append-version

Full log here:
https://launchpadlibrarian.net/59825283/buildlog.txt.gz

It looks like there is perhaps an older version of bzr-builder installed?

[Aaron Bentley (abentley)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/29/2010 08:00 PM, Jelmer Vernooij wrote:
> Public bug reported:
> It looks like there is perhaps an older version of bzr-builder
> installed?

That's how it looks. Please post a link to the build. The build log
doesn't provide navigation to the build, and it doesn't provide all the
information we need.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkz0VYYACgkQ0F+nu1YWqI2G3QCfcgkwXZxwQY3InIzEeamPAQpw
l1IAnRtkl7IHFnACFV+oEzfn1v0aIjak
=AUPn
-----END PGP SIGNATURE-----

[Philip Muškovac (yofel)]

I got the same error here:
https://code.launchpad.net/~scribus/+recipe/scribus-daily/+build/9469

[Tim Penhey (thumper)]

On Tue, 30 Nov 2010 18:27:12 you wrote:
> I got the same error here:
> https://code.launchpad.net/~scribus/+recipe/scribus-daily/+build/9469
>
> ** Changed in: launchpad-code
> Status: New => Confirmed

I'm pretty sure that this was an intermittant failure caused by one of the new
builders in the build farm not being set up properly.

I'm going to set to fix released as I'm fairly sure this is now fixed, but if it
comes up again, please set back to new.

  status fixcomplete

[Philip Muškovac (yofel)]

Today these failed:
https://code.launchpad.net/~neon/+recipe/project-neon-meta/+build/9651
https://code.launchpad.net/~neon/+recipe/project-neon-kdeutils/+build/9650

[Philip Muškovac (yofel)]

Add one more
https://code.launchpad.net/~neon/+recipe/project-neon-kdegames/+build/9669

[Max Bowsher (maxb)]

It looks like (some) builders are no longer using the <series>-cat-lpbuildd archives, even though they need to for a new enough bzr-builder.

NB that the broken builders can still process *natty* recipe builds OK, since there the bzr-builder comes from the primary archive.

[Aaron Bentley (abentley)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/30/2010 08:16 PM, Max Bowsher wrote:
> It looks like (some) builders are no longer using the <series>-cat-
> lpbuildd archives, even though they need to for a new enough bzr-
> builder.
>
> NB that the broken builders can still process *natty* recipe builds OK,
> since there the bzr-builder comes from the primary archive.

Sounds like the correct symptoms, but builders are no longer supposed to
be using the <series>-cat-lpbuildd archives. All builders should be
doing tree builds outside the chroot since buildd rev 74 was deployed,
and the non-chrooted environment already uses the appropriate archives.

So it seems what's really happening is that some builders aren't using
rev 74.

Aaron

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkz1s0EACgkQ0F+nu1YWqI3O0gCfUt6OWczI1/SfREJ9voRyE7lW
ZjAAn0z+Rkw632W+YstqxQb0iPk59vWk
=/Ji7
-----END PGP SIGNATURE-----

[Michael Vogt (mvo)]

My daily software-center build failed as well:
https://launchpadlibrarian.net/59906878/buildlog.txt.gz
but only the maverick one, the natty one build fine.

[Aaron Bentley (abentley)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/01/2010 03:04 AM, Michael Vogt wrote:
> My daily software-center build failed as well:
> https://launchpadlibrarian.net/59906878/buildlog.txt.gz
> but only the maverick one, the natty one build fine.

Please link to the build, not the build log, because the build log
doesn't allow me to navigate back to the build.

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkz2UrUACgkQ0F+nu1YWqI34NACfTuU7HLJUg505CJUznk3YapDm
UwMAoIE2rAyuqfbNj/rB1hpxncKlb8uX
=Ek17
-----END PGP SIGNATURE-----

[Aaron Bentley (abentley)]

The affected builders have been updated to the correct version of the buildd. Sorry for the inconvenience.