Public bug reported:
Binary package hint: pyflakes
The pyflakes package only installs a changelog, a copyright file and a
manpage. Those would be more useful if the actual program was also
included :)
I fixed this (following a few hints in the python-support README) by
removing
*** This bug is a duplicate of bug 462961 ***
https://bugs.launchpad.net/bugs/462961
Looks like this got fixed as bug #462961 so marking this as a duplicate
of that. If someone can teach me what caused that bug report to be
picked up and fixed instead of this one I would appreciate it, so I
Public bug reported:
Binary package hint: bzr-builddeb
import-dsc sets author information from debian/changelog and/or
debian/control as revision property as bytestrings. At least using bzr
2.0 chk_serializer's write_revision_to_string tries to encode those to
utf-8, which fails if the names
** Attachment added: One of the crash reports bzr produced
http://launchpadlibrarian.net/33387578/bzr-20091010024415-7709.crash
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33387579/Dependencies.txt
** Branch linked: lp:~marienz/+junk/import-dsc-hack
--
bzr
Public bug reported:
Binary package hint: grub2
I'm encountering this on a system using lvm with a separate /boot
partition outside of lvm used by jaunty but no separate /boot for
karmic, but I think it will affect every system with grub 1 on a
separate /boot partition, not just those also using
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/33221201/XsessionErrors.txt
--
os-prober entries do not use correct /boot device
https://bugs.launchpad.net/bugs/445367
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
Binary package hint: ubuntu-dev-tools
mk-sbuild-lv tries to modprobe dm_snapshot and bails if this fails,
assuming snapshots will not work. But the kernel I'm running (jaunty's
default linux-image-2.6.28-13-generic kernel) has CONFIG_DM_SNAPSHOT=y,
so that modprobe fails
Public bug reported:
As documented on
http://www.crummy.com/software/BeautifulSoup/3.1-problems.html the 3.1
BeautifulSoup branch uses a different parser to be compatible with
Python 3. Unfortunately this parser does much worse on invalid html than
the old one did, and a very common reason to use
