package buildd (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/buildd', which is also in package ubuntu-dev-tools 0:0.81.2

Bug #558461 reported by Paul van Genderen
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sbuild (Ubuntu)
Fix Released
Medium
Unassigned
Lucid
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: sbuild

Apparently, the last fix didn't really fix it.

Description: Ubuntu 9.10
Release: 9.10

$ LANG=C apt-cache policy buildd ubuntu-dev-tools
buildd:
  Installed: (none)
  Candidate: 0.59.0-1ubuntu1
  Version table:
     0.59.0-1ubuntu1 0
        500 http://nl.archive.ubuntu.com karmic/universe Packages
ubuntu-dev-tools:
  Installed: 0.81.2
  Candidate: 0.81.2
  Version table:
 *** 0.81.2 0
        500 http://nl.archive.ubuntu.com karmic-updates/universe Packages
        100 /var/lib/dpkg/status
     0.81 0
        500 http://nl.archive.ubuntu.com karmic/universe Packages

ProblemType: Package
Architecture: amd64
Date: Thu Apr 8 16:51:04 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: trying to overwrite '/usr/bin/buildd', which is also in package ubuntu-dev-tools 0:0.81.2
NonfreeKernelModules: nvidia
Package: buildd (not installed)
ProcVersionSignature: Ubuntu 2.6.31-20.58-generic
SourcePackage: sbuild
Title: package buildd (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/buildd', which is also in package ubuntu-dev-tools 0:0.81.2
Uname: Linux 2.6.31-20-generic x86_64

Revision history for this message
Paul van Genderen (paulvg) wrote :
Revision history for this message
Felix Geyer (debfx) wrote :

/usr/bin/buildd has been renamed in ubuntu-dev-tools 0.84:
  * Rename buildd to ubuntu-build to resolve filename conflict
    (Closes: #558816).

To make upgrades work correctly buildd needs to declare Replaces and Breaks on ubuntu-dev-tools (<= 0.83).
I prepared the changes for the package in maverick in merge bug #580724.

Once the package has been uploaded to maverick it should be fixed in lucid:

sbuild (0.59.0-1ubuntu2.1) lucid-proposed; urgency=low

  * buildd: Declare Replaces and Breaks on ubuntu-dev-tools (<= 0.83) as
    both packages contain /usr/bin/buildd. (LP: #558461)

 -- Felix Geyer <email address hidden> Fri, 14 May 2010 23:51:27 +0200

Changed in sbuild (Ubuntu):
status: New → Confirmed
Daniel Hahler (blueyed)
Changed in sbuild (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (4.5 KiB)

This bug was fixed in the package sbuild - 0.60.0-1ubuntu1

---------------
sbuild (0.60.0-1ubuntu1) maverick; urgency=low

  * Merge from Debian unstable (LP: #580724), remaining changes:
    - Do not install debfoster into the chroots because it is in universe
      and not needed for package building itself.
  * buildd: Declare Replaces and Breaks on ubuntu-dev-tools (<= 0.83) as
    both packages contain /usr/bin/buildd. (LP: #558461)

sbuild (0.60.0-1) unstable; urgency=low

  * debian/control:
    - Upgrade to Standards-Version 3.8.4.
    - Use ${misc:Depends} as required by debhelper.
  * sbuild:
    - Only run "schroot --info" once on startup, to speed up the startup
      time when many chroots exist (Closes: #546624). Thanks to
      Nelson Elhage for finding this issue and suggesting a suitable
      approach for fixing it.
    - Don't append binNMU or extra version to version number for use
      in the DSC filename (Closes: #546647). Thanks to Nelson Elhage
      for finding this issue.
    - Distinguish between failed/attempted builds (Closes: #538083).
    - Build directory cleaned under all failure conditions
      (Closes: #538085).
    - Flush stdout explicitly in logger to avoid "choppy" output when
      monitoring interactively. Autoflushing stdout appears to be
      broken in Perl 5.10 so flush explicitly in addition to
      enabling autoflush. Thanks to Ryan Niebur for spotting this.
    - Print a list of all installed packages and versions, in addition
      to toolchain packages (Closes: #553301). Thanks to Felipe
      Sateler for this suggestion.
    - Don't default distribution to unstable (Closes: #559659).
      Defaulting to unstable can result in unintentional uploads of
      packages targetted at other distributions, such as experimental,
      which can potentially cause serious breakage. As a result, it is
      safer to require manually specifying the distribution, or
      explicitly setting it in the configuration file.
    - Set the man-db man-db/auto-update parameter to false to disable
      unnecessary work in a build environment.
    - Don't give back packages failing the arch check (Closes: #561936).
      Thanks to Philipp Kern for reporting this.
    - Add command-line and configuration options to enable running
      apt-get clean, upgrade and dist-upgrade prior to building. These
      complement the existing option to update the chroot, which is now
      also fixed (Closes: #521096).
    - Add $build_source variable to sbuild.conf to complement the
      --source command-line options (Closes: #564528). Thanks to
      David Bremner for this suggestion.
    - Allow setting of $build_dir in sbuild.conf (Closes: #535911).
      Thanks to Andres Mejia for this patch.
    - Add $check_space option to allow free space checking to be
      disabled (Closes: #551917). Thanks to Bruno Kleinert for this
      suggestion.
    - --apt-update both updates and upgrades the chroot
      (Closes: #521096). Thanks to Gustavo Noronha Silva for this
      patch. Note the original bug report 'get_apt_command' error
      was fixed on the 17th March 2009.
    - Allow the use of -C as well as --check-...

Read more...

Changed in sbuild (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Felix Geyer (debfx) wrote :

I just noticed that it's not worth a SRU.
You couldn't have installed ubuntu-dev-tools and buildd at the same time in <= karmic anyway.
Sorry for the noise.

Changed in sbuild (Ubuntu Lucid):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.