Package: mcabber
Version: 0.10.2-1
Severity: normal
The module xttitle included with mcabber, which changes the title
bar of a terminal window to indicate unread message counts, doesn't work
most of the time.
If you load it as part of the startup of mcabber, you can see it set the
initial
Sorry for not responding to the last few comments. I'm really unlikely to
do any more with this than I already have. What remains appears to be
updating the debian packaging bits and making sure the patch set is still
sane with the new version. Neither of those things are something I want to
deal
Package: src:android-tools
Followup-For: Bug #738119
Although the android-tools packaging is indeed rather bad, I've made an
attempt to update it for 5.0.1. (Integrating it with
android-platform-system-core was beyond my skill.)
I'm attaching updates of the three custom makefiles supplied under
I forgot to say, that I put the full tree I worked on at
http://www.contrib.andrew.cmu.edu/~rjkohler/ for reference.
On Sat, Dec 13, 2014 at 6:17 PM, Ray Kohler ataraxia...@gmail.com wrote:
Package: src:android-tools
Followup-For: Bug #738119
Although the android-tools packaging is indeed
Package: android-tools-adb
Version: 4.2.2+git20130529-5.1
Followup-For: Bug #738119
There's now an actual reason to update this package. The version of adb
in 4.2.2 is too old to interact with devices running Android 5.x. adb
sideload, for instance, makes the device complain of a version
I noticed these, where the maintainer has already changed priorities in the
packages themselves:
nfacct: important - extra (#758229)
texinfo: standard - optional (#538112)
Same with this already-reported one:
libswitch-perl: standard - optional (changelog for version 2.17-1)
Something odd is going on with the previous NMU. The priority in the
control file has indeed changed to extra, but the binary package still
says important.
$ aptitude show nfacct | grep -e Version -e Priority
Version: 1.0.1-1.1
Priority: important
I am on jessie/amd64.
Package: systemd
Version: 215-5+b1
Followup-For: Bug #760649
This appears to be caused by exiting a systemd user session when the
user's home directory doesn't exist. In this case, the user is nobody,
and the homedir is /nonexistent. When systemd starts
systemd-exit.service to run the kill
Package: sane-utils
Version: 1.0.24-3
Severity: normal
I noticed while looking at this package that saned.socket sets
Accept=yes, but this disagrees with saned.service being
single-instance. Therefore, connecting to port 6566 just makes systemd
complain that it doesn't know what to do:
Nov 11
Package: qemu-system-x86
Version: 2.1+dfsg-5+b1
Severity: normal
virtio-scsi is quite unreliable compared to the version in wheezy. I see
many crashes, with this output:
qemu-system-x86_64: wrong size for virtio-scsi headers
This looks like the bug referenced at
, Ray Kohler wrote:
virtio-scsi is quite unreliable compared to the version in wheezy. I see
many crashes, with this output:
qemu-system-x86_64: wrong size for virtio-scsi headers
So you're saying this is a regression compared with version 1.1.2.
But the thing is -- did virtio-scsi
confirmed
[Adding qemu-devel@]
08.11.2014 04:28, Ray Kohler wrote:
virtio-scsi is quite unreliable compared to the version in wheezy. I
see
many crashes, with this output:
qemu-system-x86_64: wrong size for virtio-scsi headers
So you're saying this is a regression compared
On Thu, Feb 28, 2013 at 12:24 PM, Kurt Roeckx k...@roeckx.be wrote:
That one has been fixed upstream after the 1.0.1e release:
commit 9fe4603b8245425a4c46986ed000fca054231253
Author: David Woodhouse dw...@infradead.org
Date: Tue Feb 12 14:55:32 2013 +
Check DTLS_BAD_VER for
Package: libssl1.0.0
Version: 1.0.1e-1
Severity: normal
After upgrading libssl1.0.0 from 1.0.1c-4 to 1.0.1e-1, using the
openconnect VPN client (version 3.20-3, both before and after the
openssl upgrade) produces many of these messages, about one pair per
minute:
Feb 27 09:08:52 asenath
Package: openoffice.org
Severity: grave
Justification: renders package unusable
The new OpenOffice.org 2.0.3 still does not build properly on amd64. The
build does not error out, but it doesn't really do anything useful. The
only package generated in libmythes-dev, which appears to be incomplete
Package: openafs-modules-source
Version: 1.4.1-3
Followup-For: Bug #374367
This turns out to be a gcc 4.0 - 4.1 transition problem.
I rebuilt the latest kernel packages (the 'official' ones, not a custom
one) with gcc-4.1 to match the new AFS module, and the module now loads.
If the kernel
Package: openafs-modules-source
Version: 1.4.1-3
Severity: grave
Justification: renders package unusable
The module built from this version, at least on AMD64, does not load:
--
# modprobe openafs
FATAL: Error inserting
Package: sg3-utils
Version: 1.20-1
Severity: minor
/usr/share/doc/sg3-utils/examples contains some broken symlinks (some of
which actually just point to each other). Looks like an artifact of the
build process.
lrwxrwxrwx 1 root root 11 2006-05-15 21:37
Package: kugar
Version: 1:1.5.1-1
Severity: minor
The example doc symlinks installed into /usr/share/doc/kugar/examples
are broken. They use the .kud and .kut extensions rather than .kdf and
..ktf, which is how the files are actually named:
lrwxrwxrwx 1 root root 41 2006-05-23 08:40
Package: discover-data
Version: 2.2005.02.13-1
Severity: minor
There are a couple of broken symlinks in this package:
lrwxrwxrwx 1 root root 25 2006-04-17 19:39 /usr/share/discover/sbus-26.lst -
/lib/discover/sbus-26.lst
lrwxrwxrwx 1 root root 22 2006-04-17 19:39 /usr/share/discover/sbus.lst -
Package: linux-image-2.6.16-2-amd64-k8
Version: 2.6.16-14
Severity: normal
After installing this kernel upgrade, my sound no longer works. It is a
builtin board which uses the snd-atiixp driver. It appears to probe
correctly:
snd_atiixp 20184 0
snd_ac97_codec102012 1
Package: alsa-lib
Version: 1.0.11-6
Severity: serious
Justification: no longer builds from source
The build fails when linking one of the 32-bit components. Looks like the wrong
rpath is being used (/usr/lib32 instead of /lib32):
/bin/sh ../libtool --tag=CC --mode=link gcc -m32 -g -Wall -O2
, 29 May 2006 the mental interface of
Ray Kohler told:
Package: alsa-lib
Version: 1.0.11-6
Severity: serious
Justification: no longer builds from source
The build fails when linking one of the 32-bit components. Looks like the wrong
rpath is being used (/usr/lib32 instead of /lib32):
/bin/sh
wrote:
On Mon, 29 May 2006 the mental interface of
Ray Kohler told:
Not effective, no change at all. I also tried this variation, which was not any
better:
Hmm, these where for installing. I introduced LDFLAGS and have no
amd64 handy. Could you please one more try then?
--- rules.orig 2006-05
Package: sablevm
Version: 1.13-1
Severity: minor
The sablevm(1) man page has a typo:
sablevm.boot.library.path
changes native libraries patch which are used by boot classpath
patch should be path.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
Steve Langasek wrote:
On Wed, May 03, 2006 at 06:35:56PM -0400, Ray Kohler wrote:
Package: x11-common
Version: 1:7.0.16
Severity: grave
Justification: renders package unusable
Version 7.0.16 of x11-common depends on xfree86-common, which is a
useless compatibility package. Making things
Package: x11-common
Version: 1:7.0.16
Severity: grave
Justification: renders package unusable
Version 7.0.16 of x11-common depends on xfree86-common, which is a
useless compatibility package. Making things worse is that
xfree86-common conflicts with x11-common. This prevents x11-common from
being
I screwed this up. It installs fine if I do it right.
smime.p7s
Description: S/MIME Cryptographic Signature
Package: cupsys-client
Version: 1.1.99.rc2-0exp1
Severity: minor
cupsenable(8) and cupsdisable(8) are missing symlinks:
mandb: warning: /usr/share/man/man8/cupsdisable.8.gz is a dangling symlink
mandb: warning: /usr/share/man/man8/cupsenable.8.gz is a dangling symlink
They ought to point to
Package: debsums
Version: 2.0.27
Severity: normal
debsums splits conffile lines from the status file improperly. If the
obsolete keyword is present, it will split the line on the space in
front of it, instead of the one between the filename and the checksum.
You end up with things like:
Package: openafs-client
Version: 1.4.1-1
Severity: important
If the module has not been installed, this package will not install
either. The postinst script runs the initscript to start afsd, but if
there is no module, the initscript returns 1, causing dpkg to fail the
installation.
I don't
Package: xserver-xorg-core
Version: 1:1.0.2-3
Followup-For: Bug #362229
I am also seeing XKB problems. The server logs this:
(WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
and xdm logs this:
sh: /usr/bin/xkbcomp: No such file or directory
Thu Apr 13 21:50:13 2006 xdm error (pid
Package: thunderbird
Version: 1.5-4
Severity: serious
Justification: Policy 3.5
The recommendation of a myspell dictionary should be a hard dependency.
Without a dictionary installed, it is impossible to compose messages,
even if you turn off all spelling-related options. An error
dialog appears
Daniel Burrows wrote:
On Sat, Mar 11, 2006 at 02:46:06PM -0500, Ray Kohler [EMAIL PROTECTED] was
heard to say:
Daniel Burrows wrote:
On Wed, Mar 08, 2006 at 08:57:07PM -0500, Ray Kohler [EMAIL PROTECTED]
was heard to say:
Package: lbreakout2
Version: 2.5.2-2.1
Followup-For: Bug #355657
Daniel Burrows wrote:
On Wed, Mar 08, 2006 at 08:57:07PM -0500, Ray Kohler [EMAIL PROTECTED] was
heard to say:
Package: lbreakout2
Version: 2.5.2-2.1
Followup-For: Bug #355657
There is no problem here. I had accidentally copied the dotfiles from
this game from a PPC machine to an AMD64
Package: lbreakout2
Version: 2.5.2-2.1
Followup-For: Bug #355657
There is no problem here. I had accidentally copied the dotfiles from
this game from a PPC machine to an AMD64 machine. Apparently there is
something in them that didn't like either the 32 - 64 bit change or
the Endian-ness change.
Package: lbreakout2
Version: 2.5.2-2.1
Severity: important
lbreakout2 crashes with a Bus error at startup on amd64. I tried just
recompiling it on my local machine (hey, sometimes it works). This had
no effect.
(You also get a SEGV, but that seems to be SDL's fatal signal handler
falling apart
Package: gcc-defaults
Version: 4.0.0-2
Severity: serious
Justification: Policy 3.5
gcj-4.0 requires the file /usr/lib/libgcj.spec from libgcj6-dev. Either
this file should be repackaged into libgcj6 or gcj-4.0 should depend on
libgcj6-dev. (I suggest the former.)
Without this file, gcj errors
Package: clamav
Version: 0.86.1-2
Followup-For: Bug #317853
Details of the dependency change: libgmp3 has been split into libgmp3c2
(C API) and libgmpxx3 (C++ portion). Dependencies need to point to the
appropriate one (or both, if really needed).
-- System Information:
Debian Release:
Package: defrag
Version: 0.73pjm1
Followup-For: Bug #169584
I got this package to compile on powerpc. I don't think it's actually
usable yet, though - it fails every test in the testsuite with bad
superblock on trying to mount the after image. Hopefully, it's still
helpful.
--- buffers.c.orig
Package: librep9
Version: 0.17-7
Severity: grave
Justification: renders package unusable
This package needs to be rebuilt due to the splitting off of libgmp3
into libgmp3c2 (C functionality) and libgmpxx3 (C++ functionality). It
will not install due to out-of-date shlibs depends.
My apologies
Package: flwm
Version: 1.00-7
Severity: normal
Flwm occasionally leaves zombies lying around. I cannot predictably
reproduce this - there are always a few out there but I can't make them
on demand.
F UID PID PPID PRI NIVSZ RSS WCHAN STAT TTYTIME COMMAND
4 1000 26510 26489
Package: findimagedupes
Version: 0.1.3-5
Severity: serious
Justification: Policy 3.5
This tool requires libltdl3 to run, and does not depend on it:
~/pics % findimagedupes -v
Can't load '/usr/lib/perl5/auto/Image/Magick/Magick.so' for module
Image::Magick: libltdl.so.3: cannot open shared
Package: most
Version: 4.9.5-1
Severity: minor
Tags: patch
There ought to be a line break before the +lineno command line option
entry in the man page.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux
Package: kobodeluxe
Version: 0.4pre9-5
Severity: minor
Tags: patch
The man page incorrectly documents the 'cheat' option. It says you can
select any level (which you can't), and doesn't mention that it also
gives you infinite ships.
Here is a simple manpage patch:
--- debian/kobodl.man.orig
Package: lbreakout2
Version: 2.5.2-1
Severity: normal
If you set the warp limit to 0, you will still be unable to warp if
you have created more blocks with the current ball than you have
destroyed (e.g. if you have hit a lot of the creates up to 8 bricks on
destruction blocks), since in effect
Package: installation-reports
INSTALL REPORT
Debian-installer-version: netinst rc3 powerpc
uname -a: Linux arkadia 2.6.11-powerpc #1 Mon Apr 4 04:03:40 CEST 2005 ppc
GNU/Linux
Date: 2005-04-08 21:00 (GMT)
Method: Booted from CD, did a clean install, and used the whole disk.
Machine:
Package: xpuyopuyo
Version: 0.9.8-1
Severity: minor
Very minor issue - If you open the Advanced Options and hover the
mouse over any of the fields, the tooltip popup complains that it can't
open the manpage rather than displaying the expected help item:
Can't open help file
Package: xpuyopuyo
Version: 0.9.8-1
Severity: important
If these three conditions are met:
1) You start xpuyopuyo in a directory for which you have write access;
2) You have sound enabled for the game;
3) Some other process has the sound device locked;
then xpuyopuyo will create a file called
Package: xzgv
Version: 0.8-3
Followup-For: Bug #214112
Unless this is really a separate problem, the original description isn't
quite correct - you don't need to zoom to reproduce this. All you need
to do is open a directory that's already been thumbnailed. Whatever
items that you can see listed
50 matches
Mail list logo
