Given that the bug is fixed in LSB, and unlikely to be hit anywhere
(there are other issues with trying to install postfix before lsb-
release is configured on an ubuntu system), I'm going to consider the
bug fixed, esp since lsb has been fixed to deal with it correctly.
** Changed in: postfix (Ub
** Changed in: lsb (Ubuntu)
Assignee: Colin Watson (cjwatson) => Michael Vogt (mvo)
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
This bug was fixed in the package lsb - 4.0-0ubuntu3
---
lsb (4.0-0ubuntu3) karmic; urgency=low
* rebuild using python-central and DH_PYCENTRAL=include-links
(LP: #383697)
* debian/control:
- set XS-Python-Version to "all"
- depend on python-central
* debian/lsb-rele
** Attachment added: "debdiff to build lsb with python-central and
DH_PYCENTRAL=include-links"
http://launchpadlibrarian.net/30642745/lsb_4.0-0ubuntu3.debdiff
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you a
** Tags added: amd64
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/
Feel free to edit; I'm not going to waste time fine-tuning tags :-)
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Bug appears on AMD64-version as well, so the i386-tag is not needed I
would think :-)
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I figured out what's really going on here - the debconf GNOME frontend
calls lsb_release! No wonder we've been getting so many duplicates.
** Changed in: lsb (Ubuntu)
Importance: Wishlist => High
** Changed in: lsb (Ubuntu)
Assignee: (unassigned) => Colin Watson (cjwatson)
--
lsb_releas
more information about the crash - actually it seems to be either x or
gnome. in fact booting into recovery and then resume normal booting also
stopped working. however, i was able to complete boot by alt-ctrl-f1
(try to watch where it crashed), and then it did not crash at all and
booted into gdm
i am not sure whether it is related, but the 2.6.31-4-generic booting
crashed with not even alt-ctl-del working. however, if i start with the
recovery mode and then continue to boot normally, it was fine. could not
find anything in logs and when i got into gnome, there was an
exclamation mark telli
Hi Julian.
Can you tell me, how I'm gonna do this upgrade from Jaunty do Karmic.
Thanks.
From: Julian Lam
To: paspalj...@yahoo.com
Sent: Sunday, July 19, 2009 7:06:38 PM
Subject: [Bug 383697] Re: lsb_release crashed with ImportError in ()
Hi all,
On my system (this is by no means necessarily complete):
./postfix.config:27:my $distribution = lc(`lsb_release -is 2>/dev/null`);
./samba.postinst:125: && [ "`lsb_release -s -i`" = "Ubuntu" ]
samba depends on lsb-base so it's probably OK. postfix has no way of
doing so here - the only way t
(This was never an upstream bug in the first place.)
It's probably a different bug caused by some other package. Please
attach /var/log/apt/term.log so that we can tell.
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification becaus
Hi all,
Just upgraded to Karmic:
'util-linux:
Installed: 2.16-1ubuntu1
Candidate: 2.16-1ubuntu1
Version table:
*** 2.16-1ubuntu1 0
500 http://ubuntu.mirror.rafal.ca karmic/main Packages
100 /var/lib/dpkg/status
Looks like the problem still occurs, despite upstream comments
On Mon, Jul 13, 2009 at 12:34:45PM -, Jean-Paul Calderone wrote:
> I encountered this problem yesterday when I upgraded a Jaunty machine to
> Karmic. The version of util-linux I got was 2.15.1~rc1-1ubuntu3.
It's probably a different bug caused by some other package. Please
attach /var/log/apt
I encountered this problem yesterday when I upgraded a Jaunty machine to
Karmic. The version of util-linux I got was 2.15.1~rc1-1ubuntu3.
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bug
It might be nice for lsb_release to be a bit more tolerant of this kind
of thing, given its rather central position in the system, but it's
always possible to work around it, so I'm downgrading the remaining part
of this bug to wishlist.
** Changed in: lsb (Ubuntu)
Importance: Medium => Wishlis
This bug was fixed in the package util-linux - 2.15.1~rc1-1ubuntu3
---
util-linux (2.15.1~rc1-1ubuntu3) karmic; urgency=low
* Remove lsb_release call from mount.preinst and just unconditionally
remove the guarded code from the Ubuntu package; lsb_release is not
guaranteed to
Got the error too.
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
I've got this error too.
** Attachment added: "_usr_bin_lsb_release.0.crash"
http://launchpadlibrarian.net/28849540/_usr_bin_lsb_release.0.crash
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of
On Mon, Jul 06, 2009 at 03:24:23PM -, Scott James Remnant wrote:
> Won't this be a bug in Debian as well?
Debian would need to make the code in question unconditional rather than
using lsb_release. I haven't provided a patch for that but it's trivial;
just remove the if/fi and an indentation l
Won't this be a bug in Debian as well?
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Oh, well, in that case the updated patch is rather trivial. How about
this?
** Attachment added: "util-linux.383697.diff"
http://launchpadlibrarian.net/28728746/util-linux.383697.diff
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug no
On Tue, 2009-06-16 at 10:46 +, Colin Watson wrote:
> I know LaMont prefers to keep the packaging as common between Debian and
> Ubuntu as possible. LaMont/Scott, how about the attached patch?
>
I think we've tended not to worry with the preinst/postinst etc. because
they're pretty different
I know LaMont prefers to keep the packaging as common between Debian and
Ubuntu as possible. LaMont/Scott, how about the attached patch?
** Attachment added: "util-linux.383697.diff"
http://launchpadlibrarian.net/27985873/util-linux.383697.diff
--
lsb_release crashed with ImportError in ()
ht
This is currently painful to fix in lsb-release because python-support
does not have the necessary feature ("include-links" in python-central;
see https://blueprints.launchpad.net/ubuntu/+spec/foundations-karmic-
robust-python-packaging). In the meantime, I recommend that the mount
package should d
** Visibility changed to: Public
--
lsb_release crashed with ImportError in ()
https://bugs.launchpad.net/bugs/383697
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists
27 matches
Mail list logo
