** Changed in: sbuild (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791134
Title:
Debian/sid and oneiric based builds fail
To manage notifications
This bug was fixed in the package sbuild - 0.60.9-1ubuntu3.1
---
sbuild (0.60.9-1ubuntu3.1) natty-proposed; urgency=low
* Cherry-pick a couple of commits from tip; fixes locks in chroots of
recents suites like oneiric or current Debian sid; LP: #791134.
-
These tests were done on a Natty (11.04) host trying to build packages
for an Oneiric build environment.
With the previous version: 0.60.9-1ubuntu3 I get this when trying to
build a package:
E: Can't create lock file
/var/lib/schroot/mount/oneiric-i386-e7023eb5-9377-4c7b-a91a-
On Mon, Jul 25, 2011, Daniel Manrique wrote:
My package builds successfully, the only extraneous message I see is
this:
Purging
/var/lib/schroot/mount/oneiric-i386-da4725cc-0b05-41a2-9f0f-1818eb230de7/build/root-checkbox_0.12.4-i386-6XTBrR
Not cleaning session: cloned chroot in use
As I
Hi Loïc:
Things work fine, despite the message which I interpret as being just a
warning. I also did repeated build attempts and they all worked fine.
I'm a newbie while using sbuild so I hadn't really paid attention to
behavior with chroot directories, but I did notice this:
Purging
Cool, thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791134
Title:
Debian/sid and oneiric based builds fail
To manage
Hello James, or anyone else affected,
Accepted sbuild into natty-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Branch linked: lp:ubuntu/natty-proposed/sbuild
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791134
Title:
Debian/sid and oneiric based builds fail
To manage notifications about this bug go to:
I second the SRU idea :-)
** Also affects: sbuild (Ubuntu Natty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791134
Title:
Debian/sid and oneiric
** Changed in: sbuild (Ubuntu Natty)
Status: New = In Progress
** Changed in: sbuild (Ubuntu Natty)
Assignee: (unassigned) = Loïc Minier (lool)
** Changed in: sbuild (Ubuntu Natty)
Importance: Undecided = Medium
** Changed in: sbuild (Ubuntu Natty)
Status: In Progress =
because /var/lock is now a symlink to /run/lock, including in chroots
(per Debian policy on symlinks between top-level directories), sbuild
needs to cope. The fix for this is in the Debian package in unstable,
so it looks like this just needs a merge/cherry-pick for oneiric.
** Also affects:
** Changed in: sbuild (Ubuntu Oneiric)
Milestone: None = oneiric-alpha-3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791134
Title:
Debian/sid and oneiric based builds fail
To manage
** Bug watch added: Debian Bug tracker #626826
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626826
** Also affects: sbuild (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626826
Importance: Unknown
Status: Unknown
--
You received this bug notification because
slangasek barry: ideally we would SRU this as well, for the benefit of
anyone who might actually want to use sbuild for building in
chroots for a different release than the one they're running :)
--
You received this bug notification because you are a member of Ubuntu
unstable has 0.62.4-1 now and that has been merged to Oneiric with some
remaining changes (0.62.4-1ubuntu1). So this *should* be fixed in
Oneiric now. I'm testing this to double check.
It may still make sense to SRU the change, but I think I'll let someone
request that first. :)
** Changed
15 matches
Mail list logo
