Package: incron
Version: 0.5.7-1
Severity: minor
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is a small readbility typo in the incrontab.1 man page. Patch
included.
Thanks for maintaining.
jamie.
- -- System Information:
Debian Release: lenny/sid
APT prefers testing
Package: aptitude
Version: 0.4.11.8-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aptitude should give priority to removing and purging packages before
handling any other package installs or upgrades. In this way, things
can be cleared out, space can be made, and complexity
Package: fakechroot
Version: 2.9-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
So we (debirf maintainers) have stumbled upon a strangeness in the
behavior of getcwd() under fakechroot. It appears that the path gets
confused depending on if the chroot root path has been
Package: debirf
Version: 0.23-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
After upgrading to grub2, I am no longer able to build a debirf iso
image:
servo:/srv/debirf/rescue 0$ debirf makeiso .
Loading profile 'rescue'...
Failed to find a grub El Torito stage2 loader at
Package: rxvt-unicode
Version: 9.09-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When urxvtd is invoked with no options, it is supposed to run in the
foreground. However, I believe after the upgrade to 9.09, the daemon
is forking into the background and producing the
On Wed, Nov 19, 2008 at 01:30:04PM +, Gerrit Pape wrote:
...Having written that, I see your service is down when removing it
servo:~ 0$ sudo svstat /etc/service/cereal.foo
/etc/service/cereal.foo: down 51 seconds
Hmm. If you can reproduce the issue reliably, can you make the service
On Sun, 31 Jan 2010 08:31:35 +0100, Mike Hommey m...@glandium.org wrote:
Hum, if *I* file a bug as RC against a package *I* maintain, it *is* RC.
Actually, that does not follow. The severity of a bug affects a lot of
things other than just the maintainer. For instance, by setting the
severity
Package: wnpp
Severity: wishlist
Owner: Jameson Graef Rollins [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: debirf
Version : 0.18
Upstream Author : Jameson Graef Rollins [EMAIL PROTECTED]
* URL : http://cmrg.fifthhorseman.net/wiki
Package: lvm2
Version: 2.02.39-2
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I recently had a problem that involved being dropped into the
emergency shell of the initramfs: the rootfs was on lvm on a raid
array that was not properly detected during boot. I was able to use
On Mon, Oct 27, 2008 at 08:01:47AM +, Alasdair G Kergon wrote:
'lvm' binary should be present for use as prefix to other cmds e.g.
# lvm lvchange -ay vg1/lvol1
Hi, Alasdair. I agree that the lvm binary *should* be present for use
under the name 'lvm', but it's currently not. The binary is
Package: fakechroot
Version: 2.8-1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have found that on systems running nscd, certain (all?) nameservice
calls are not properly faked when running fakechroot, which can cause
improper failures in the chrooted environment. For
Package: runit
Version: 2.0.0-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello, Gerrit. I'm encountering a problem with runit that I'm hoping
you can help me with.
It appears that stopped runsv processes are not responding to TERM
signals. The big problem that this is
Package: wnpp
Severity: wishlist
Owner: Jameson Graef Rollins [EMAIL PROTECTED]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
* Package name: monkeysphere
Version : 0.20
Upstream Author : Jameson Graef Rollins [EMAIL PROTECTED]
* URL : http://web.monkeysphere.info
Package: octave3.0-headers
Version: 3.0.5-6+b1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The package appears to have incompatible dependencies for squeeze:
servo:~ 0$ apt-cache policy gcc-4.3
gcc-4.3:
Installed: 4.3.4-1
Package: devscripts
Version: 2.10.35lenny1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've found a small bug in checkbashisms' processing of the ((...))
bashisms. For some reason, it doesn't find the bashism if $# is
used in the enclosed expression:
servo:/tmp/cdtemp.JNHNWu
Package: devscripts
Version: 2.10.35lenny1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It appears that checkbashisms does not detect the bash function
'source':
servo:/tmp/cdtemp.XcoaZB 0$ cat foo
#!/bin/sh
source bar
servo:/tmp/cdtemp.XcoaZB 0$ checkbashisms -p ./foo
On Wed, Dec 31, 2008 at 06:26:43PM +, Adam D. Barratt wrote:
It does, but only if it's one of the forms source ./foo,
source /foo/bar or source $foo. I can't see any obvious reason from
the changelog, that source bar isn't flagged, but I'm not currently
sure whether there was a good reason
Package: dash
Version: 0.5.4-12
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey, Gerrit. As I fumble through the bash/sh - dash/sh transition,
I'm noticing some trouble with test expressions that use '' or ''.
It appears that these characters are being treated as file
Package: dash
Version: 0.5.4-12
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey, Gerrit.
I notice that dash supports the '-p prompt' option for the read
function. However, the devscripts checkbashisms script flags this:
servo:/tmp/cdtemp.XcoaZB 0$ cat ./foo
#!/bin/sh
read -p
Package: cereal
Version: 0.22-1
Severity: important
User: debian-rele...@lists.debian.org
Usertags: goal-dash
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The cereal command uses the bashism source to source the common
functions. This causes the command to fail if /bin/sh is linked to
dash,
Package: ncmpcpp
Version: 0.5.2-1
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Strangely, I can't seem to copy or paste in this curses application.
When running ncmpcpp in an rxvt terminal, I can't select text with the
mouse, nor can I paste in any text from the copy buffer.
Package: jparse
Version: 1.4.0-3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This package has no man page, or even a --help option, which makes it
next to impossible to use it. It sounds useful, but it's hard to
know. Obviously this is a violation of policy as well.
Package: nagios3-doc
Version: 3.0.6-4~lenny2
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The nagios web front page (main.html) embeds an image from an external
http site (sourceforge). This is quite problematic for systems that
wish to provide their nagios web
Package: wnpp
Severity: wishlist
Owner: Jameson Rollins jroll...@finestructure.net
Owner: Jameson Rollins jroll...@finestructure.net
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: xul-ext-monkeysphere
Version : 0.1
Upstream Author : monkeysph...@lists.riseup.net
On Thu, Dec 24, 2009 at 05:39:59PM +0100, Lucas Nussbaum wrote:
During a rebuild of all packages in sid, your package failed to build on
amd64.
Thank you very much for this report, Lucas. I have added cpio to the
Build-Depends, so this should be resolved on the next upload.
jamie.
Hi, Christian. Thanks so much for the bug report. Can you provide a
little more information about the system where you have built the
debirf image, and the system on which you are having trouble booting
it? In particular, can you provide:
- version of debirf used to build the image
-
On Sun, Dec 27, 2009 at 11:55:20AM +0100, Christian Svensson wrote:
The issue was that the testing machine didn't have enough RAM - increasing
from the default 256 solved it.
Hi, Christian. I'm glad that increasing the ram solved your problem,
but I'm really surprised that 256M was not enough.
On Sun, Dec 27, 2009 at 04:55:30PM +0100, Christian Svensson wrote:
Problem is reproducible with a standard VMware Workstation with 256 MB RAM
(or less). Increasing to 260 MB RAM is enough for it to boot.
Thanks so much for the further info, Christian. I'm very glad things
are working for you
Package: ssh
Version: 1:5.6p1-1
Severity: normal
Tags: experimental
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello, I have the following ~/.ssh/config:
Host *
ControlMaster autoask
ControlPath /home/jrollins/.ssh/controls/%...@%h:%p
ControlPersist 10
When I try to connect to a hidden
Package: nbibtex
Version: 0.9.18-9
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
nbibtex is failing to compile a bibliography that compiles fine with
regular bibtex:
0 $ bibtex thesis
This is BibTeX, Version 0.99c (TeX Live 2009/Debian)
The top-level auxiliary file:
Package: pybtex
Version: 0.13.2-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello. pybtex is failing to compile my bibtex file with the following
key error:
0 $ pybtex -e ISO-8859-1 thesis
Traceback (most recent call last):
File /usr/bin/pybtex, line 21, in module
Package: pybtex
Version: 0.13.2-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've run into a strange problem where pybtex just completely hangs
when trying to compile a certain bibtex entry. I've included a super
simple tex file and a bibtex file that includes a single
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello, release team. I would like to request a freeze-exception for
the monkeysphere package.
A recently filed bug (#600304) was
Package: openssh-client
Version: 1:5.1p1-4
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I am encountering a small bug when using ssh-keygen -l with
known_hosts files. For lines that have comments, the hostname is not
diplayed in the ssh-keygen -l output:
Package: openssh-client
Version: 1:5.1p1-4
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
ssh-keygen -R is currently removing all comments from the known_hosts
file it's processing. Below is an example of ssh-keygen -R being run
on a test known_host file:
Package: openssh-client
Version: 1:5.1p1-4
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Reading from stdin is either broken or not properly supported in
ssh-keygen. It appears that ssh-keygen will read from a file
redirection, but not from a pipeline:
servo:/tmp/cdtemp.laHoFb
Package: luakit
Version: 0~20100813-4
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey. It looks like luakit is not currently one of the available
choices in update-alternatives for x-www-browser:
0 servo:~ $ update-alternatives --list x-www-browser
/usr/bin/chromium-browser
Package: luakit
Version: 0~20100813-5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
pretty self explanatory:
0 servo:~ $ man luakit
No manual entry for luakit
See 'man 7 undocumented' for help when manual pages are not available.
16 servo:~ $
Thanks maintaining!
- --
Package: mailutils
Version: 1:2.0+dfsg1-4
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm experiencing a very strange problem with the 'mail' utility and I
have no idea what it means:
servo:~ 0$ echo foo | /usr/bin/mail -s test jroll...@finestructure.net
input in flex
Package: thttpd
Version: 2.25b-6
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello. thttpd is currently lacking support for the following ogg mime
types:
oga audio/ogg
ogv video/ogg
ogx application/ogg
The included patch adds them to the
Package: gdm
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
gdmflexiserver is a useful program. It is also usable and useful on
it's own, and by many other display managers other than gdm. It's
unfortunate that installation of this package requires installing gdm
and all of
reopen 557590
thanks
On Mon, Nov 23, 2009 at 10:41:10AM +0100, Josselin Mouette wrote:
Le dimanche 22 novembre 2009 à 21:44 -0500, Jameson Graef Rollins a
écrit :
It's
unfortunate that installation of this package requires installing gdm
and all of it's dependencies, many of which
Package: cupt
Version: 1.0.0~beta1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It appears that cupt is not recognizing or respecting apt pinning
preferences defined in /etc/apt/preferences. This is causing major
problems for mixed systems, since essentially upgrades are
On Sat, Oct 03, 2009 at 12:45:08PM +0300, Eugene V. Lyubimkin wrote:
Thanks for the report, I've reproduced the bug with your pin settings and
fixed it in the master branch of cupt. The fix will go to the 1.0.0~rc2
version, as I already uploaded 1.0.0~rc1.
Thanks so much for the prompt
Package: grub-pc
Version: 1.97~beta3-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Here is a simple illustration of the problem from the grub shell:
sh:grub if true ; then
sh: menuentry foo {
syntax error
Incorrect command
syntax error
sh:grub
I can't see any reason why
Package: libgmime-2.4-2
Version: 2.4.23-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since 2.4.23, PGP/MIME signature verification is broken. Signatures
that were previously reporting GMIME_SIGNATURE_STATUS_GOOD are now
returning some other signature status.
It was
It looks like this has been reported upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=645787
jamie.
pgpS3783K6Zrj.pgp
Description: PGP signature
Hi, folks. So what exactly is the current status of kst? I see that it
has been removed entirely from testing, which is very unfortunate. Is
someone taking over packaging?
kst2 is also now available, and it even looks like it's packaged for
Ubuntu:
On Fri, 15 Apr 2011 16:53:42 -0500, Dirk Eddelbuettel e...@debian.org wrote:
On 15 April 2011 at 13:27, Jameson Graef Rollins wrote:
| Can we get this into Debian as well?
Yes please!
cool!
| Can kst2 just take over the kst
| name, seeing as there's not currently a kst package?
Maybe
Package: pbuilder
Version: 0.199+nmu3
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
pbuilder and cowbuilder are both failing to create base images on my
system. I have tried with multiple distributions, with both pbuilder
and cowbuilder, and nothing works. I would have
Hi, Michael. Thanks for the response. Comments below.
On Fri, 06 May 2011 19:56:46 +0400, Michael Tokarev m...@tls.msk.ru wrote:
initramfs-tools does not depend on busybox indeed, but it
recommends busybox|busybox-initramfs. With default apt
settings that basically translates to depends,
Package: python-gtk2
Version: 2.17.0-4+b1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi. The pygtk package is failing with python2.7:
servo:~ 0 python2.7 -c import pygtk
Traceback (most recent call last):
File string, line 1, in module
ImportError: No module named
Package: python-gst0.10
Version: 0.10.21-2+b1
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
gst is failing to load the python plugin provided by python-gst0.10
[0]. Upon closer inspection, it appears that the plugin is hard-coded
to use python 2.7, even if it is not
/jrollins/.reportbugrc:
reportbug_version 3.2
realname Jameson Graef Rollins
email jroll...@finestructure.net
mode advanced
ui text
editor emacs -nw
sign gpg
- -- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (600, 'testing'), (500, 'unstable'), (101, 'experimental
On Mon, 28 Mar 2011 12:19:16 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
It looks like this has been reported upstream:
https://bugzilla.gnome.org/show_bug.cgi?id=645787
Hey, Mirco. It looks like Jeffrey pushed out a new version of gmime-2.4
to fix this issue:
http
Package: libgphoto2-2
Version: 2.4.10.1-5
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The libgphoto2 Debian README [0] says:
This version of libgphoto2-installs udev files in
/etc/udev/libgphoto2.rules to allow camera access to all members of
group 'plugdev'.
Package: libgphoto2-2
Version: 2.4.10.1-5
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It seems that the permissions on my camera's USB device is not being
set correctly. When trying to access the camera I get the following
error:
servo:~ 0$ gphoto2 -L
***
On Tue, 5 Apr 2011 08:47:57 +0200, David Paleino da...@debian.org wrote:
Err, that's /lib/udev/rules.d/60-libgphoto2-2.rules now.
So I guess this is just an out-of-date-documentation issue. Mangling the bug
accordingly, and fixing it.
Can you check you have it?
Hey, David. Thanks so much
On Tue, 5 Apr 2011 11:48:58 +0200, David Paleino da...@debian.org wrote:
I seem to have found the solution for the bugs you reported (which I'm merging
now), i.e. gphoto/udev not setting the permissions properly (namely: leaving
the group as root instead of plugdev).
Would you please apply
On Tue, 5 Apr 2011 11:09:17 +0200, David Paleino da...@debian.org wrote:
Just one more information from you: can you please say what vendorid+productid
your camera is? You can find it from lsusb (it's the two strings ID:
:), or from dmesg when you attach your camera to the computer.
reassign 621717 fakechroot
forcemerge 621717 561991
thanks
On Fri, 08 Apr 2011 12:52:42 +1000, Andrew Worsley amwors...@gmail.com wrote:
dpkg: ../../src/archives.c:823: tarobject: Assertion `r == stab.st_size'
failed.
Aborted
Hey, Andrew. This is a know issue in fakechroot in squeeze:
Package: spamassassin
Version: 3.3.1-2
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The cron script (/etc/cron.daily/spamassassin) runs sa-update as root.
However, sa-update pulls spamassassin rules from the net
(updates.spamassassin.org by default). It seems to me that
Package: xserver-xorg
Version: 1:7.6+6
Followup-For: Bug #622175
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I think I am experiencing this same problem. When xdm starts, I have
no keyboard or mouse, either with my internal keyboard/mouse (thinkpad
x201) or with an external USB keyboard.
On Sun, 24 Apr 2011 11:36:42 +0200, Cyril Brulebois k...@debian.org wrote:
Isn't that just udev + /run fun? See #621036
Ah! Thank you so much KiBi! Thank you thank you thank you. rm -rf'ing
/run and restarting (after making sure 167-3 was installed) seemed to
fix the problem.
jamie.
On Sun, 24 Apr 2011 11:51:10 -0700, Jameson Graef Rollins
jroll...@finestructure.net wrote:
Ah! Thank you so much KiBi! Thank you thank you thank you. rm -rf'ing
/run and restarting (after making sure 167-3 was installed) seemed to
fix the problem.
Just for clarification, that's udev 167-2
Package: linux-2.6
Version: 2.6.38-3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
As you can see from the kern.log snippet below, I am seeing frequent
messages reporting bio too big device md0 (248 240).
I run what I imagine is a fairly unusual disk setup on my laptop,
I am starting to suspect that these messages are in face associated with
data loss on my system. I have witnessed these messages occur during
write operations to the disk, and I have also started to see some
strange behavior on my system. dhclient started acting weird after
these messages
Package: msva-perl
Version: 0.8-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It appears that there is no information provided with the msva-perl
package about how to get msva-perl to actually run. This was
highlighted by a user on #monkeysphere. The method, as described
So this issue is a little less important than I thought, since I forgot
that in more recent versions of msva-perl the agent is automatically
started.
However, I'm not seeing any documentation about *disabling* the agent,
so we should document that somewhere, presumably in man 1 msva-perl.
jamie.
On Fri, 29 Apr 2011 05:39:40 +0100, Ben Hutchings b...@decadent.org.uk wrote:
On Wed, 2011-04-27 at 09:19 -0700, Jameson Graef Rollins wrote:
I run what I imagine is a fairly unusual disk setup on my laptop,
consisting of:
ssd - raid1 - dm-crypt - lvm - ext4
I use the raid1
On Mon, 02 May 2011 02:04:18 +0100, Ben Hutchings b...@decadent.org.uk wrote:
On Sun, 2011-05-01 at 20:42 -0400, Daniel Kahn Gillmor wrote:
So far as I'm aware, the RAID may stop working, but without loss of data
that's already on disk.
What exactly does RAID may stop working mean? Do you
On Mon, 02 May 2011 11:11:25 +0200, David Brown da...@westcontrol.com wrote:
This is not directly related to your issues here, but it is possible to
make a 1-disk raid1 set so that you are not normally degraded. When you
want to do the backup, you can grow the raid1 set with the usb disk,
On Thu, 18 Aug 2011 18:54:04 +, ow...@bugs.debian.org (Debian Bug Tracking
System) wrote:
If you think it still reproduces, come back.
Hi, Junichi. I am still unable to build a base image, but I think it is
due to a different bug (631314). So I can't actually confirm that this
bug has
Hi. What exactly is the status of this bug? I am currently
experiencing it with 0.64. The /var/cache/pbuilder/base.cow/proc
directory that is created is unremovable, causing cowbuilder to fail.
And this is definitely *not* a debootstrap issue, since debootstrap is
working on it's own just fine.
On Sat, 3 Sep 2011 10:25:16 -0500, Jonathan Nieder jrnie...@gmail.com wrote:
Now I'm in suspense. Did you get a chance to test the kernel with
Tejun Heo's commit bf2253a6f00e[1] reverted?
Hi, Jonathan. Sorry to keep you in suspense!
So I just tried reverting the patch and rebuilding the
Package: udev
Version: 172-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Occasionally I find a cdrom_id process stuck in the D
(uninterruptible sleep) state that can not be killed. I'm not
exactly sure what's causing this (possibly detaching from my dock?)
but this causes
On Wed, 24 Aug 2011 19:49:53 +0200, m...@linux.it (Marco d'Itri) wrote:
Occasionally I find a cdrom_id process stuck in the D
(uninterruptible sleep) state that can not be killed. I'm not
This is always a kernel bug.
Hi, Marco. Can you explain why this is always a kernel bug? It's
So this problem is now happening with other udev functions as well:
Aug 25 00:53:14 servo udevd[23014]: timeout: killing 'scsi_id --export
--whitelisted --device=/dev/sr0' [23017]
This leaves me not particularly convinced that this is not at least
partially a udev issue.
This issue has become
On Thu, 25 Aug 2011 12:42:00 -0500, Jonathan Nieder jrnie...@gmail.com wrote:
Does downgrading udev or the kernel help? /var/log/dpkg.log should
describe the upgrade history of both, and http://snapshot.debian.org/
has historical packages.
I'm fairly confident that this started happening
Package: conky-cli
Version: 1.8.1-3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
After installing conky-cli, I tried to run it and immediately got the following
errors:
servo:~ 0$ conky
Conky: /etc/conky/conky.conf: 26: no such configuration: 'alignment'
Conky:
On Thu, 25 Aug 2011 15:45:55 -0700, Vincent Cheng vincentc1...@gmail.com
wrote:
conky-cli should use conky_no_x11.conf instead of the regular
conky.conf by default; however, I'm unsure whether or not conky can be
compiled to look for an alternative config file instead of the default
located
On Thu, 25 Aug 2011 12:42:00 -0500, Jonathan Nieder jrnie...@gmail.com wrote:
Please send the full content of /var/log/dmesg after running
echo d /proc/sysrq-trigger/proc/sysrq-trigger
echo w /proc/sysrq-trigger
when a process is in this hung state.
Attached is a diff of the
On Thu, 25 Aug 2011 12:42:00 -0500, Jonathan Nieder jrnie...@gmail.com wrote:
Does downgrading udev or the kernel help? /var/log/dpkg.log should
describe the upgrade history of both, and http://snapshot.debian.org/
has historical packages.
If I keep everything else the same (same version of
On Fri, 26 Aug 2011 19:56:11 -0700, Vincent Cheng vincentc1...@gmail.com
wrote:
I don't know; to be honest, I know rather little about conffile
handling. If you can point me in the right direction, or better yet,
write up a patch to do so, I'd be grateful! :)
So as far as I can tell, there
On Sat, 27 Aug 2011 14:34:56 -0500, Jonathan Nieder jrnie...@gmail.com wrote:
The only potentially problematic commit I could find is the following.
It might be worth testing with it backed out.
Hey, Jonathan. I haven't done much kernel rebuilding at all, so I'm not
sure what's the best way to
Package: luakit
Version: 2011.05.06+unique-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello. After a recent upgrade, luakit started failing to start, producing the
following error:
servo:~ 0$ luakit
/usr/share/luakit/lib/userscripts.lua:18: module 'lfs' not found:
On Sat, 6 Aug 2011 12:23:52 +, Clint Adams cl...@debian.org wrote:
On Fri, Aug 05, 2011 at 10:47:18PM -0700, Jameson Graef Rollins wrote:
ii liblua5.1-0 5.1.4-5Simple, extensible, embeddable
pro
ii liblua5.1-filesystem0 1.5.0-2luafilesystem library
Package: dpkg-dev
Version: 1.16.0.3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
For some reason I have recently been unable to build packages linked
against libc.so.6 or libpthread.so.0 because dpkg-shlibdeps keeps
failing with the following errors:
...
dh_shlibdeps
On Sat, 9 Jul 2011 18:59:51 -0500, Jonathan Nieder jrnie...@gmail.com wrote:
What does
ldd debian/notmuch/usr/bin/notmuch
say?
Hey, Jonathan. I think this is what you're looking for (gbp specifies
./debian-build as the export-dir):
servo:~/src/notmuch/git [personal] 0$ ldd
On Sun, 10 Jul 2011 08:51:46 +0200, Raphael Hertzog hert...@debian.org wrote:
If that error was more than a local problem, we would have noticed it by
now. :-)
Maybe, or I'm just the first person to report it.
Please paste the output of the failing dpkg-shlibdeps run with -v -v.
Output of
On Sun, 10 Jul 2011 20:47:11 +0200, Raphael Hertzog hert...@debian.org wrote:
What version of libc6 do you have? Please show me the output of dpkg
-s libc6.
I've got 2.13-7 installed.
$ dpkg -S /etc/ld.so.conf.d/x86_64-linux-gnu.conf
libc6: /etc/ld.so.conf.d/x86_64-linux-gnu.conf
$ sudo
On Sun, 10 Jul 2011 17:20:23 -0500, Jonathan Nieder jrnie...@gmail.com wrote:
Could you grep through /var/log/dpkg.log* for the upgrade history of
libc6? I would like to learn what caused this so we can prevent it
from happening again.
Hi, Jonathan. Thanks for trying to figure this out. I
On Thu, 21 Jul 2011 21:40:53 +0200, Daniel Kahn Gillmor
d...@fifthhorseman.net wrote:
when /var is full, cereal-admin create fails to work. This is
probably to be expected, but if this kind of failure happens, it
should probably bail out earlier, and it should probably return a
value other
Hey, Thomas. Thanks so much for the bug report, and sorry you ran into
trouble.
On Thu, 28 Jul 2011 12:02:54 +0200, Thomas Koch tho...@koch.ro wrote:
Failed running transition script /usr/share/monkeysphere/transitions/0.23
dpkg: error processing monkeysphere (--configure):
subprocess
Package: cowbuilder
Version: 0.70
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Right out of the box, cowbuilder fails to create an image:
servo:~ 0$ sudo cowbuilder --create
- Invoking pbuilder
forking: pbuilder create --buildplace /var/cache/pbuilder/base.cow --mirror
Also fails to start if /etc/asound.conf is configured the same way.
I'm tempted to raise the severity of this bug, since setting asound.conf
this way was basically the ONLY way to get pulseaudio working
previously, so I imagine most people have this configured. At the very
least pulseaudio needs
On Wed, May 16 2012, Michael Biebl bi...@debian.org wrote:
If I fail to understand the role of consolekit please do enlighten me.
From /usr/share/doc/network-manager/README.Debian:
Security
To allow users to connect to the NetworkManager daemon they have to be in
the
On Thu, May 17 2012, Michael Biebl bi...@debian.org wrote:
This is not a network-manager problem per se.
Having a properly setup ConsoleKit/PolicyKit stack is something your
desktop environment should provide as a *lot* of tools are nowadays
depending on that.
That's the problem of using
Just complaining doesn't magically fix things and suggesting that I
wasted other people's time or treat them like second class citizens
really annoys me. If you read the bug report you will notice that I
invested a lot of time trying to find out what was going on.
Hi, Michael. I don't think
affects 542361 okular
thanks
Can I get some update on what's going on with this bug? I *just*
encountered this and now I can't use okular at all. It just hangs
waiting for some /tmp/fam- socket that doesn't exist:
servo:~ 0$ strace okular
...
1 - 100 of 261 matches
Mail list logo
