Source: qtcreator
Version: 3.2.1+dfsg-7
Severity: grave
Justification: renders package unusable
Several Qt packages seem to have too specific dependencies:
# aptitude install qtcreator
The following NEW packages will be installed:
libbotan-1.10-0{a} libqt5clucene5{a} libqt5concurrent5{ab}
Package: python-mode
Version: 1:6.1.3-2
Severity: normal
Error message at installation:
Setting up python-mode (1:6.1.3-2) ...
ERROR: python-mode is broken - called emacs-package-install as a new-style
add-on, but has no compat file.
Install python-mode for emacs
Install python-mode for emacs23
Package: kdm
Version: 4:4.3.4-4
For a long time one of my old systems that had been upgraded from KDE3
to KDE4 suffered from a visually broken KDM login screen.
By removing two old KDE3 theme packages that were left installed,
despite the upgrade. to KDE4, the KDM greeter now displays
Package: reportbug
Version: 4.10.2
$ reportbug
/usr/lib/pymodules/python2.5/reportbug/ui/gtk2_ui.py:446: PangoWarning:
pango_layout_get_line_count: assertion `layout != NULL' failed
gtk.main
()
Package: glibc-doc-reference
Version: 2.9-2
Severity: normal
Aptitude install log:
Selecting previously deselected package glibc-doc-reference.
Unpacking glibc-doc-reference (from .../glibc-doc-reference_2.9-2_all.deb) ...
Processing triggers for man-db ...
Processing triggers for doc-base ...
On Tuesday 04 August 2009 06:09:37 Trent W. Buck wrote:
On Mon, Aug 03, 2009 at 01:36:32PM +0300, Leonard Norrgård wrote:
The emacs package ultimately depends on emacs23-common =23.1+1-1,
which is outdated and gone.
I can't reproduce this problem. The packages in my repo which depend
Package: emacs
Severity: grave
Justification: renders package unusable
The emacs package ultimately depends on emacs23-common =23.1+1-1, which is
outdated and gone.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64
Package: motion
Version: 3.2.9-1
Severity: normal
Relevant output:
Setting up motion (3.2.9-1) ...
addgroup: The group `motion' already exists.
dpkg: error processing motion (--configure):
subprocess post-installation script returned error exit status 1
Errors were encountered while processing:
Package: quilt
Version: 0.45-6
Followup-For: Bug #410890
The problem is that quilt expects /usr/sbin to be in the user's path, which it
by
default isn't. The following patch against the quilt-0.45 source package fixes
the
-- Leonard
problem.
--- quilt-0.45/debian/patches/debianize
Could you provide me with the contents of /conf/conf.d/cryptroot from the
initramfs image?
conf/conf.d/cryptroot:
target=VG00-root_crypt,source=/dev/mapper/VG00-root,key=none
target=VG00-swap_crypt,source=/dev/mapper/VG00-swap,key=none
Also, what behaviour do you get when you boot after the
Package: cryptsetup
Version: 2:1.0.4+svn26-1
Severity: normal
I used the suspend to disk function in kpowersave to suspend. On the next
boot, cryptsetup fails to handle the
suspend filesystem in swap (and it doesn't mount swap over it).
-- System Information:
Debian Release: 4.0
APT prefers
On Tue, 6 Feb 2007 19:39:33 +0100, Mattia Dongili wrote:
On Tue, Feb 06, 2007 at 10:23:35AM +0200, Leonard Norrgard wrote:
I've got a basic package done, coming soon.
Humm, did you already see my work?
http://oioio.altervista.org and look for the git repo.
Anyway, I've been working with
Package: reportbug
Version: 3.31
Severity: normal
I was browsing a long issue (such as #396332) and had scrolled towards the end.
When
trying to return to the bug list, this assertion occured:
Traceback (most recent call last):
File /usr/bin/reportbug, line 1747, in ?
main()
File
Package: passwd
Version: 1:4.0.18.1-6
Severity: critical
Tags: security
Justification: root security hole
An ordinary user may end up with group ownership of system files
in the following scenario [2]:
1. A user is added, and receives the user and group ids, name.
2. Later, a package is
Package: kvm
Version: 7-1
Severity: grave
Justification: renders package unusable
The version of kvm currently in testing, kvm-7, has many known stability bugs
that have
been fixed in later upstream versions. These cause the guest operating system
to crash,
possibly causing data loss etc.
Since 2.6.20 includes kvm modules that are much newer than the kvm-7
userland from the kvm-7 package, you'll have to either 1) remove the
2.6.20 kvm modules (merely rmmod:ing them isn't enough) or
2) uninstall kvm-7 and compile the kvm-11 userland and use that.
Btw, work is underway to get kvm-11
16 matches
Mail list logo
