Bug#706679: Missing Depends: file
Stuart Pook wrote:
> I have the "expr: syntax error" as well
expr doesn't appear in the codebase as at debian/4.0_alpha30-1.
This appears to be the commit that fixes it.
The new version could probably use SUS parameter expansion:
$ busybox ash
BusyBox v1.18.4 (Ubuntu 1:1.18.4-2ubuntu2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
$ DEVICE=/dev/sda1p1
$ DEVICE=${DEVICE#/dev/} DEVICE=${DEVICE%%[0-9]*}
$ echo "$DEVICE"
sda
commit 3ce6f9e8fe33cfdda99b0bffbb3fa69063014047
Author: Daniel Baumann
Date: Mon May 6 20:42:55 2013 +0200
Replacing expr usage in initscript for eject boot media with something less
error prone.
diff --git a/bin/boot-init.sh b/bin/boot-init.sh
index 83f37bc..3027d28 100755
--- a/bin/boot-init.sh
+++ b/bin/boot-init.sh
@@ -80,10 +80,17 @@ get_boot_device()
device_is_USB_flash_drive()
{
# remove leading "/dev/" and all trailing numbers from input
- DEVICE=$(expr substr ${1} 6 3)
+ DEVICE=$(echo ${1} | sed -e 's|/dev/||' -e 's|[0-9].*$||')
# check that device starts with "sd"
- [ "$(expr substr ${DEVICE} 1 2)" != "sd" ] && return 1
+ case "${DEVICE}" in
+ sd*)
+ ;;
+
+ *)
+ return 1
+ ;;
+ esac
# check that the device is an USB device
if readlink /sys/block/${DEVICE} | grep -q usb
signature.asc
Description: Digital signature
Bug#739258: has_option ignores first line of file
Package: x11-common Version: 1:7.7+6 Severity: normal File: /etc/X11/Xsession.d/20x11-common_process-args There is a straightforward bug in Xsession.options parsing: if the first line is an option, it's ignored. echo use-session-dbus >/etc/X11/Xsession.options will not dbus-launch, but printf '\nuse-session-dbus\n' >/etc/X11/Xsession.options will. I don't really want to think about parsing in raw sh right now, so I'm just going to add a blank line at the top of my file and leave the problem with you guys. Good luck! -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages x11-common depends on: ii debconf [debconf-2.0] 1.5.52 ii lsb-base 4.1+Debian12 x11-common recommends no packages. x11-common suggests no packages. -- debconf information: x11-common/xwrapper/allowed_users: Console Users Only x11-common/xwrapper/actual_allowed_users: console -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#445513: interesting race condition with mutex logins
althaser wrote: > Could you please try to reproduce this issue with newer version of > gnome-terminal like 3.4.1.1-2 or 3.10.1-1 ? I can probably find time for that in the next week or two. signature.asc Description: Digital signature
Bug#736380: RFA: paredit-el -- Emacs minor mode for structurally editing Lisp code
Package: wnpp Severity: normal I request an adopter for the paredit-el package. The package description is: Paredit mode instruments several common keybindings to automatically balance all parentheses and respect the structure of S-expressions; it also provides numerous high-level operations to change the structure of lists. I've been neglecting my maintainer responsibilities for years, and it's past time to admit it. paredit is a rarely-updated, single-file elisp library. IMO it would be better in emacs-goodies-el than standalone, but I can't bear to learn CVS. http://bugs.debian.org/526598 There are also new upstream versions. http://mumble.net/~campbell/emacs/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#737595: Warning when installed with --path-exclude=/usr/share/doc/*
Package: kgoldrunner Version: 4:4.8.4-3 Severity: wishlist Debian Policy §12.3 says packages are supposed to work when /usr/share/doc is absent. When I tried it, I got this info dialog: Get Folders - KGoldRunner Cannot find documentation sub-folder 'en/kgoldrunner/' in area '/root/.kde/share/doc/HTML/:/usr/share/doc/kde/HTML/' of the KDE folder ($KDEDIRS). If I hit "OK", kgoldrunner can be played. The warning reappears each time kgoldrunner is launched. On that basis, I was about to cancel the bug report, but #debian-mentors encouraged me to file it anyway with --severity=grumble :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#738495: "mono install" hides "Mono requires /proc" error
Package: mono
Version: 2.10.8.1-8
Severity: normal
Installing gbrainy into a chroot failed.
It didn't say *why*.
I've seen java fail because /proc wasn't mounted,
so I specifically went looking for that.
mono-gac.postinst
-> /usr/share/cli-common/gac-install mono
-> /usr/share/cli-common/gac-package-install libglib2.0-cil
-> /usr/share/cli-common/runtimes.d/mono install libglib2.0-cil
/usr/lib/cli/glib-sharp-2.0/glib-sharp.dll
None of these mention /proc.
But stracing them shows the problem immediately:
(bootstrap)# strace -f /usr/share/cli-common/gac-install mono |& grep /proc
| head -6
open("/proc/meminfo", O_RDONLY) = -1 ENOENT (No such file or
directory)
[pid 6373] readlink("/proc/self/exe", 0x7fff5952eab0, 4095) = -1 ENOENT
(No such file or directory)
[pid 6374] readlink("/proc/self/exe", 0x7fff47709210, 4095) = -1 ENOENT
(No such file or directory)
[pid 6375] readlink("/proc/self/exe", 0x7fff1e52a8a0, 4095) = -1 ENOENT
(No such file or directory)
[pid 6377] access("/proc/self/maps", F_OK) = -1 ENOENT (No such file or
directory)
[pid 6377] write(1, "Mono requires /proc to be mounte"..., 35) = 35
One of the subprocesses is writing the important information, "Mono
requires /proc", to stderr. But something further up the chain
(/usr/share/cli-common/runtimes.d/mono or below) is hiding that
information.
I'm not filing a bug "shouldn't need /proc at install time" -- I'm
assuming that's a lost cause.
But can mono please let the "needs /proc" error reach the user, so he
can see just from "apt-get install gbrainy" what went wrong?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732249: cal -M (like ncal -M)
Package: bsdmainutils Version: 9.0.5 Severity: wishlist File: /usr/bin/cal "ncal -M" starts weeks on Monday. "cal -M" gives an error. I wish "cal -M" started weeks on Monday. See also http://bugs.debian.org/729336 . -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bsdmainutils depends on: ii bsdutils 1:2.20.1-5.5 ii debianutils 4.4 ii libc62.17-97 ii libncurses5 5.9+20130608-1 ii libtinfo55.9+20130608-1 bsdmainutils recommends no packages. Versions of packages bsdmainutils suggests: ii cpp4:4.8.1-3 pn vacation ii wbritish-small [wordlist] 7.1-1 ii whois 5.0.26 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#732249: cal -M (like ncal -M)
Michael Meskes wrote: > On Mon, Dec 16, 2013 at 11:06:02AM +1100, Trent W. Buck wrote: > > "ncal -M" starts weeks on Monday. > > "cal -M" gives an error. > > I wish "cal -M" started weeks on Monday. > > See also http://bugs.debian.org/729336 . > > Similar to that one this one also is not a bug. cal is supposed to be > identical > to a historic version, ncal gets the new features. But ncal -CM doesn't work either, though ncal -C works and ncal -M works. I don't care if I have to call it ncal so that "cal" behaviour remains unchanged, but I'd like to have the days along the x axis (like ncal -C) *and* the weeks starting on Monday (like ncal -M). signature.asc Description: Digital signature
Bug#734331: RFH: mg -- microscopic GNU Emacs-style editor
Package: wnpp Severity: normal I request assistance with maintaining the mg package. There's been a new release waiting to go for months, but I have been too lazy to do it. I need someone to either do it or nag me into doing it. Current mg has a dependency on a new C library "clens". A working draft clens package is ready. Step #1 is to get that sponsored. https://opensource.conformal.com/wiki/clens Once that's done, mg's new upstream is trivial. The package description is: This program is intended to be a small, fast, and portable editor for people who can't (or don't want to) run real Emacs for one reason or another. It is compatible with GNU because there shouldn't be any reason to learn more than one Emacs flavor. . Packages which provide editors with broadly similar goals include . * e3; * joe; * jove and xjove; * ng-cjk, ng-cjk-canna and ng-latin; * qemacs and qemacs-nox; and * zile signature.asc Description: Digital signature
Bug#663941: Cannot rebase commits at midnight, 1 Jan 1970 (epoch 0)
Jonathan Nieder wrote: > Version: 1:1.7.9.1-1 > notfound 663941 git/1:1.7.9.1-1 > quit > > Zbigniew Jędrzejewski-Szmek wrote: > > > I just tested this, and with v1.7.9.1~8 I get the error message "fatal: > > invalid date format: 0 +", and with v1.7.9.1~7 (i.e. after the > > branch with the supposed fix is merged), the testcase succeeds. > > > > I suppose that Trent must have been using a different version of git > > than the one reported. FYI, this is quite likely. I'm not allowed to install sid on every host. :-) At a glance, the versions I'm likely to have been using are - whatever testing/unstable had when I reported the problem; - 1:1.7.9.5-1; and - 1:1.7.0.4-1ubuntu0.2 I run reportbug from a sid host. I usually set --package-version, but I might have forgotten for this bug (which would cause reportbug to pick the testing/unstable version). I'm not worried about this bug, so I won't bother to dig further. :-) signature.asc Description: Digital signature
Bug#734331: RFH: mg -- microscopic GNU Emacs-style editor
Peter De Wachter wrote: > Hi Trent, > I'd like to help with mg. I'm not a DD, so I won't be able to sponsor, > but I can help with anything else. Thanks. I'm usually in #debian-mentors on irc.oftc.net from ca. 10AM to 6PM Australia/Melbourne time. The mg stuff probably still says it's maintained in darcs, but the repo (inc. history) was migrated to git, at git.debian.org:/git/collab-maint/mg.git It's a repo of just debian/, which appears to be an unusual workflow among the git people. I'm open to changing that if you feel strongly. As I said in the RFH, the next step should be to get clens into a finished state, then get it sponsored. I've rsynced what I've currently got to ~twb-guest/Desktop/mg/ on git.debian.org; you should have read access. signature.asc Description: Digital signature
Bug#734331: mg-20131118 sans clens
Han, Peter (another Debian packager) made mg works with libbsd alone; no clens. Is this likely to bite us on the ass later? Adding clens to Debian is work we'd rather avoid if possible. --- Begin Message --- On 13-01-14 00:19, Trent W. Buck wrote: > I'm usually in #debian-mentors on irc.oftc.net from ca. 10AM to 6PM > Australia/Melbourne time. I rarely IRC. If necessary I can come online but that's midnight to 8AM Europe/Brussels time... > The mg stuff probably still says it's maintained in darcs, but the > repo (inc. history) was migrated to git, at > git.debian.org:/git/collab-maint/mg.git > > It's a repo of just debian/, which appears to be an unusual workflow > among the git people. I'm open to changing that if you feel strongly. No problem. I actually still keep all my packages in Subversion... > As I said in the RFH, the next step should be to get clens into a > finished state, then get it sponsored. > > I've rsynced what I've currently got to ~twb-guest/Desktop/mg/ on > git.debian.org; you should have read access. Ok, I've taken a look, and I think we don't need to bother with clens at all. As far as I can tell it only duplicates stuff that's already in libbsd. I've attached a trivial patch to use that library and it seems to work fine. Can you check if that's okay with upstream? diff --git a/GNUmakefile b/GNUmakefile index f9a02da..eac73c5 100644 --- a/GNUmakefile +++ b/GNUmakefile @@ -13,13 +13,15 @@ libdir= $(prefix)/lib includedir= $(prefix)/include mandir= $(prefix)/man +BSD_CFLAGS:= $(shell pkg-config --cflags libbsd-overlay) +BSD_LIBS:= $(shell pkg-config --libs libbsd-overlay) CC= gcc CFLAGS?= -O2 -pipe CFLAGS+= -g -Wall -Werror -Wno-error=unused-but-set-variable -Wno-error=maybe-uninitialized CFLAGS+= -DFKEYS -DREGEX -DXKEYS -CFLAGS+= -I$(includedir)/clens -LIBS= -lcurses -lclens +CFLAGS+= $(BSD_CFLAGS) -D__dead=__dead2 +LIBS= -lcurses $(BSD_LIBS) INSTALL= /usr/bin/install STRIP= /usr/bin/strip diff --git a/def.h b/def.h index c7dc24e..1ef0edc 100644 --- a/def.h +++ b/def.h @@ -13,7 +13,6 @@ #include "sysdef.h" /* Order is critical. */ #include "ttydef.h" #include "chrdef.h" -#include typedef int (*PF)(int, int); /* generally useful type */ diff --git a/theo.c b/theo.c index a5cf284..fadac2a 100644 --- a/theo.c +++ b/theo.c @@ -24,6 +24,7 @@ * ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. */ +#include #include "def.h" #include "kbd.h" #include "funmap.h" --- End Message --- signature.asc Description: Digital signature
Bug#734331: RFH: mg -- microscopic GNU Emacs-style editor
Peter, Peter De Wachter wrote: > Ok, I've taken a look, and I think we don't need to bother with clens at > all. As far as I can tell it only duplicates stuff that's already in > libbsd. I've attached a trivial patch to use that library and it seems > to work fine. Can you check if that's okay with upstream? Han replied (without CC'ing you) with "I'll look into that sometime". So I suggest we proceed with your patch and not bother with clens. signature.asc Description: Digital signature
Bug#729041: breaks panic=N (users can get a ramdisk shell)
Package: live-boot Version: 3.0.1-1 Severity: normal Below, I'm deliberately starting a Debian Wheezy live-boot system without ANY access to its root filesystem. (As a test for this happening as a result of a transient network outage.) Because panic=N is passed, it's *supposed* to reboot without letting the user get a ramdisk shell. When boot=live is used, the user can gets two shells (one after the other), before the advertised behaviour finally kicks in. ii live-boot 3.0.1-1 ii live-boot-initramfs-tools 3.0.1-1 ii initramfs-tools0.109.1 | # kvm -m 512 -nographic -kernel vmlinuz -initrd initrd.img -append 'console=ttyS0 boot=live loglevel=1 panic=3 plainroot root=/dev/canthappen' | Loading, please wait... | Begin: Loading essential drivers ... done. | Begin: Running /scripts/init-premount ... done. | Begin: Mounting root file system ... | | .''`. | : :' : BOOT FAILED! | `. `'` |`- This Debian Live image failed to boot. | | Please file a bug against the 'live-boot' package or email the Debian | Live mailing list at , making sure to note the | exact version, name and distribution of the image you were attempting to boot. | | The file /boot.log contains some debugging information but booting with the | debug command-line parameter will greatly increase its verbosity which is | extremely useful when diagnosing issues. | | live-boot will now restart your system. The error message was: | | Can not mount /dev/canthappen on //filesystem | Rebooting automatically due to panic= boot argument | | | BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) | Enter 'help' for a list of built-in commands. | | /bin/sh: can't access tty; job control turned off | (initramfs) # that slept for three seconds, but then it gave me this shell | (initramfs) exit | mount: mounting //filesystem on /live/medium failed: Invalid argument | done. | mount: mounting aufs on /root/ failed: Invalid argument | mount aufs on /root/ failed with option -o noatime,noxino,dirs=/live/overlay/=rw://filesystem/=rr+wh | Rebooting automatically due to panic= boot argument | | | BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) | Enter 'help' for a list of built-in commands. | | /bin/sh: can't access tty; job control turned off | (initramfs) # then it slept another three seconds and gave me ANOTHER shell. | (initramfs) exit | mount: mounting //filesystem on /live/rootfs/filesystem failed: Invalid argument | done. | Begin: Configuring fstab ... /init: line 68: can't create /root/etc/fstab: nonexistent directory | /init: line 68: can't create /root/etc/fstab: nonexistent directory | done. | Begin: Preconfiguring networking ... /init: line 68: can't create /root/etc/network/interfaces: nonexistent directory | /init: line 68: can't create /root/etc/network/interfaces: nonexistent directory | done. | /init: line 68: 6: Bad file descriptor | [ 28.568265] Kernel panic - not syncing: Attempted to kill init! | [ 28.569203] Pid: 1, comm: init Tainted: G C 3.2.0-4-amd64 #1 Debian 3.2.51-1 | [ 28.570402] Call Trace: | [ 28.570784] [] ? panic+0x95/0x1a2 | [ 28.571557] [] ? do_exit+0x95/0x713 | [ 28.572405] [] ? do_group_exit+0x74/0x9e | [ 28.573262] [] ? sys_exit_group+0xf/0xf | [ 28.574061] [] ? system_call_fastpath+0x16/0x1b | [ 28.574992] Rebooting in 3 seconds.. When live-boot is installed but not used, the problem is actually worse -- exiting the shells that shouldn't appear several times still doesn't make it reboot. | # kvm -m 512 -nographic -kernel vmlinuz -initrd initrd.img -append 'console=ttyS0 loglevel=1 panic=3 rootdelay=1 root=/dev/canthappen' | Loading, please wait... | Begin: Loading essential drivers ... done. | Begin: Running /scripts/init-premount ... done. | Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. | Begin: Waiting for root file system ... done. | Gave up waiting for root device. Common problems: | - Boot args (cat /proc/cmdline) |- Check rootdelay= (did the system wait long enough?) |- Check root= (did the system wait for the right device?) | - Missing modules (cat /proc/modules; ls /dev) | ALERT! /dev/canthappen does not exist. Dropping to a shell! | Rebooting automatically due to panic= boot argument | | | BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) | Enter 'help' for a list of built-in commands. | | /bin/sh: can't access tty; job control turned off | (initramfs) | (initramfs) exit | Gave up waiting for root device. Common problems: | - Boot args (cat /proc/cmdline) |- Check rootdelay= (did the system wait long enough?) |- Check root= (did the sy
Bug#752492: mount(8klibc) does not support --no-canonicalize -- breaks httpfs2 in live-boot
Package: fuse Version: 2.9.3-10 Severity: normal When I try to use httpfs2 from within an initramfs-tools ramdisk, I get httpfs2 http://example.net/filesystem.squashfs /filesystem /bin/mount: invalid option -- There's no instance of "--" in the httpfs2 source. In both 2.9.0-2+deb7u1 and 2.9.3-10, fuse source appears to be calling mount like this: /bin/mount --no-canonicalize -i -f -t type -o opts fsname mnt That option is *not* supported by klibc-utils' mount: $ /usr/lib/klibc/bin/mount --no-canonicalize /usr/lib/klibc/bin/mount: invalid option -- The immediate result is live-boot's documented support for loading the rootfs *on demand* over HTTP using httpfs, simply can't work. This is annoying because (I think) I could have done load balancing more easily on HTTP than on iSCSI. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744167: udhcpc down script assumes pidfile exists
Package: ifupdown
Version: 0.7.48.1
Severity: minor
This morning when I turned on my machine,
for some reason I got an IP address but no route,
so I did
root@frey:~# ifdown wlan0
ifdown: interface wlan0 not configured
root@frey:~# ifup wlan0
ifup: interface wlan0 already configured
root@frey:~# ifdown -a
cat: /run/udhcpc.wlan0.pid: No such file or directory
/bin/sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid |
job]... or
kill -l [exitstatus]
cat: /run/udhcpc.wlan0.pid: No such file or directory
/bin/sh: 1: kill: Usage: kill [-s sigspec | -signum | -sigspec] [pid |
job]... or
kill -l [exitstatus]
root@frey:~# ifup -a
root@frey:~#
And then I was happy again:
$ ip r
default via 203.7.155.65 dev wlan0
203.7.155.64/26 dev wlan0 proto kernel scope link src 203.7.155.97
$ ip -4 a
1: lo: mtu 65536 qdisc noqueue state DOWN group default
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: wlan0: mtu 1500 qdisc mq state UP
group default qlen 1000
inet 203.7.155.97/26 brd 203.7.155.127 scope global wlan0
valid_lft forever preferred_lft forever
But the output from the "ifdown -a" suggests that ifupdown is assuming
that udhcpc suceeded at least enough to write a pidfile, which is
clearly not a safe assumption to make.
The issue appears to be this
kill -USR2 $(cat /run/udhcpc.%iface%.pid); kill -TERM $(cat
/run/udhcpc.%iface%.pid) \
elsif (execable("/sbin/udhcpc"))
How about this? dpkg is "Essential: yes", so it should be no problem.
start-stop-daemon --stop --oknodo --user root --name udhcpc --pidfile
/run/udhcpc.wlan0.pid --retry=USR2/5/INT/5/KILL/5
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ifupdown depends on:
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-51
ii iproute 1:3.12.0-2
ii iproute2 3.12.0-2
ii libc62.18-4
ii lsb-base 4.1+Debian12
Versions of packages ifupdown recommends:
pn isc-dhcp-client | dhcp-client
Versions of packages ifupdown suggests:
ii net-tools 1.60-25
pn ppp
pn rdnssd
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#744836: "Device driver support needs thus be built-in linux image!" --> "Ensure all necessary drivers are built into the linux image!"
Package: initramfs-tools Version: 0.115 Severity: wishlist File: /usr/sbin/mkinitramfs When building a live-boot image with a custom kernel that lacks CONFIG_MODULE, I ran into this warning output: Setting up linux-image-3.13.7inmate (3.13.7inmate-1) ... update-initramfs: Generating /boot/initrd.img-3.13.7inmate WARNING: missing /lib/modules/3.13.7inmate Device driver support needs thus be built-in linux image! ERROR: could not open directory /lib/modules/3.13.7inmate: No such file or directory FATAL: could not search modules: No such file or directory df: Warning: cannot read table of mounted file systems: No such file or directory warning: failed to read mtab live-boot: core filesystems devices utils udev blockdev. WARNING: could not open /var/tmp/mkinitramfs_9M1xNs/lib/modules/3.13.7inmate/modules.order: No such file or directory WARNING: could not open /var/tmp/mkinitramfs_9M1xNs/lib/modules/3.13.7inmate/modules.builtin: No such file or directory The "needs thus" line confused me, so I suggest this replacement: Ensure all necessary drivers are built into the linux image! I am a native Australian English speaker. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#742759: Consider removing "userhelper must be setuid root"
Package: usermode
Version: 1.109-1
Severity: wishlist
I am using usermode to let LDAP users change their attributes
(password, shell, full name) from the GUI.
This doesn't require root privileges,
because the accounts aren't on the local machine at all:
# chmod 755 /usr/bin/passwd
# su - p -s /bin/sh -c 'exec passwd'
(current) LDAP Password:
New password:
Retype new password:
passwd: password updated successfully
I would like to remove userhelper's setuid bit,
but its source code explicitly checks for "am I root",
not "can I do what I was asked":
if (geteuid() != 0) {
fprintf(stderr, _("userhelper must be setuid root\n"));
debug_msg("userhelper: not setuid\n");
exit(ERR_NO_RIGHTS);
}
I'm not sure how to test for "can I do what I was asked" -- I don't
think userhelper can know what will be needed without parsing the pam
configuration, which is a bit much to ask.
So instead, can you downgrade it from an error to a warning?
Something like this:
if (geteuid() != 0) {
fprintf(stderr, _("userhelper is not setuid root\n"));
fprintf(stderr, _("The next step will fail for pam_unix
accounts\n"));
debug_msg("userhelper: not setuid\n");
/* no exit here */
}
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743464: After this operation, N MB would have been used. [-s, --simulate, --just-print, --dry-run, --recon, --no-act]
Package: apt Version: 0.9.16.1 Severity: wishlist File: /usr/bin/apt-get I want to generate lists of install sizes. I don't mean the Installed-Size of the package I'm asking for, but the aggregate of everything that'll be installed. For example $ sudo apt-get install libreoffice --assume-no | grep disk.space After this operation, 390 MB of additional disk space will be used. I want to use --dry-run but then it doesn't print such a line: $ apt-get install libreoffice --dry-run | grep disk.space This wouldn't be a big deal, except that packages with no dependencies will be installed even when I try to answer "no" to apt-get: $ sudo apt-get install crossfire-maps --assume-no -oAPT::Get::Trivial-Only=no Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: linux-image-3.12-1-amd64 Use 'apt-get autoremove' to remove it. Suggested packages: crossfire-server The following NEW packages will be installed: crossfire-maps *** NO PROMPT HERE 0 upgraded, 1 newly installed, 0 to remove and 30 not upgraded. Need to get 24.4 MB of archives. After this operation, 203 MB of additional disk space will be used. Get:1 http://apt/debian/ testing/main crossfire-maps all 1.70.0-1 [24.4 MB] Can --dry-run please be changed to either just print this as-is: After this operation, 390 MB of additional disk space will be used. Or, if that's too misleading, change the tense: After this operation, 390 MB of additional disk space would have been used. This issue occurs in wheezy's apt-get (0.9.7.9+deb7u1), too. -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "false"; APT::Install-Suggests "0"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-amd64$"; APT::NeverAutoRemove:: "^linux-headers-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-headers-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-amd64$"; APT::NeverAutoRemove:: "^.*-modules-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^.*-modules-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-3\.13-1-amd64$"; APT::NeverAutoRemove:: "^linux-backports-modules-.*-amd64$"; APT::VersionedKernelPackages ""; APT::VersionedKernelPackages:: "linux-image"; APT::VersionedKernelPackages:: "linux-headers"; APT::VersionedKernelPackages:: "linux-image-extra"; APT::VersionedKernelPackages:: "linux-signed-image"; APT::VersionedKernelPackages:: "kfreebsd-image"; APT::VersionedKernelPackages:: "kfreebsd-headers"; APT::VersionedKernelPackages:: "gnumach-image"; APT::VersionedKernelPackages:: ".*-modules"; APT::VersionedKernelPackages:: ".*-kernel"; APT::VersionedKernelPackages:: "linux-backports-modules-.*"; APT::Never-MarkAuto-Sections ""; APT::Never-MarkAuto-Sections:: "metapackages"; APT::Never-MarkAuto-Sections:: "restricted/metapackages"; APT::Never-MarkAuto-Sections:: "universe/metapackages"; APT::Never-MarkAuto-Sections:: "multiverse/metapackages"; APT::Never-MarkAuto-Sections:: "oldlibs"; APT::Never-MarkAuto-Sections:: "restricted/oldlibs"; APT::Never-MarkAuto-Sections:: "universe/oldlibs"; APT::Never-MarkAuto-Sections:: "multiverse/oldlibs"; APT::Default-Release "jessie"; APT::Architectures ""; APT::Architectures:: "amd64"; APT::Compressor ""; APT::Compressor::. ""; APT::Compressor::.::Name "."; APT::Compressor::.::Extension ""; APT::Compressor::.::Binary ""; APT::Compressor::.::Cost "1"; APT::Compressor::gzip ""; APT::Compressor::gzip::Name "gzip"; APT::Compressor::gzip::Extension ".gz"; APT::Compressor::gzip::Binary "gzip"; APT::Compressor::gzip::Cost "2"; APT::Compressor::gzip::CompressArg ""; APT::Compressor::gzip::CompressArg:: "-9n"; APT::Compressor::gzip::UncompressArg ""; APT::Compressor::gzip::UncompressArg:: "-d"; APT::Compressor::bzip2 ""; APT::Compressor::bzip2::Name "bzip2"; APT::Compressor::bzip2::Extension ".bz2"; APT::Compressor::bzip2::Binary "bzip2"; APT::Compressor::bzip2::Cost "3"; APT::Compressor::bzip2::CompressArg ""; APT::Compressor::bzip2::CompressArg:: "-9"; APT::Compressor::bzip2::UncompressArg ""; AP
Bug#743468: Replace GenericName "Board Game" with "Sudoku" in menu.
Package: gnudoq Version: 0.94-2.1 Severity: minor When you have a bunch of board games installed like chess, go and shogi, it's silly to have sudoku appear in the menu as "Board Game", which is what happens in xfce4-panel with 'show-generic-names' turned on. I think the generic name "Board Game" is *too* generic. I suggest changing it to GenericName=Sudoku -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743476: Strange path /usr/etc/default/keyboard.VARIANT
Package: console-setup Version: 1.102 Severity: minor File: /bin/setupcon In the following transcript, the path setupcon claims to search does not match its documentation and is not an FHS 2.3 path. # setupcon --help |& grep VARIANT Usage: setupcon [OPTION] [VARIANT] If VARIANT is not specified setupcon looks for the configuration files a VARIANT is specified then setupcon looks for the configuration files ~/.console-setup.VARIANT and /etc/default/console-setup.VARIANT. # cat /etc/default/console-setup.small FONTFACE="Terminus" FONTSIZE="12x6" XKBOPTIONS="altwin:ctrl_win,ctrl:nocaps" # setupcon --font-only --verbose small setupcon: None of /usr/etc/default/keyboard.small nor /root/.console-setup.small exists. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-setup-linux 1.102 ii debconf 1.5.52 ii keyboard-configuration 1.102 ii xkb-data2.10.1-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.18-4 ii lsb-base 4.1+Debian12 Versions of packages keyboard-configuration depends on: ii debconf 1.5.52 ii initscripts 2.88dsf-51 ii liblocale-gettext-perl 1.05-8 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-1 ii keyboard-configuration 1.102 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common pn console-data pn console-tools ii kbd 1.15.5-1 -- debconf information: console-setup/framebuffer_only: keyboard-configuration/toggle: No toggling console-setup/fontsize-text47: 8x16 keyboard-configuration/unsupported_layout: true keyboard-configuration/optionscode: keyboard-configuration/layoutcode: us keyboard-configuration/variantcode: * console-setup/codeset47: Guess optimal character set * keyboard-configuration/variant: English (US) console-setup/codesetcode: guess keyboard-configuration/compose: No compose key keyboard-configuration/switch: No temporary switch keyboard-configuration/ctrl_alt_bksp: false console-setup/use_system_font: console-setup/fontsize-fb47: 8x16 keyboard-configuration/modelcode: pc105 console-setup/store_defaults_in_debconf_db: true keyboard-configuration/unsupported_config_layout: true keyboard-configuration/model: Generic 105-key (Intl) PC console-setup/guess_font: console-setup/fontface47: Fixed keyboard-configuration/store_defaults_in_debconf_db: true console-setup/fontsize: 8x16 keyboard-configuration/altgr: The default for the keyboard layout debian-installer/console-setup-udeb/title: keyboard-configuration/other: keyboard-configuration/unsupported_options: true * console-setup/charmap47: UTF-8 keyboard-configuration/xkb-keymap: us keyboard-configuration/unsupported_config_options: true keyboard-configuration/layout: -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#743476: Acknowledgement (Strange path /usr/etc/default/keyboard.VARIANT)
Update: strace indicates it can find my file, but ignores it?
# ls -ld /etc/default/console-setup.small
-rw-r--r-- 1 root root 77 Apr 3 18:20 /etc/default/console-setup.small
# strace -etrace=file setupcon --font-only --verbose small
execve("/bin/setupcon", ["setupcon", "--font-only", "--verbose", "small"],
[/* 19 vars */]) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
stat("/root", {st_mode=S_IFDIR|0700, st_size=238, ...}) = 0
stat(".", {st_mode=S_IFDIR|0700, st_size=238, ...}) = 0
open("/bin/setupcon", O_RDONLY) = 3
stat("/bin", {st_mode=S_IFDIR|0755, st_size=1370, ...}) = 0
stat("/etc/default/keyboard.small", 0x7fff0d5f00a0) = -1 ENOENT (No such
file or directory)
stat("/etc/default/console-setup.small", {st_mode=S_IFREG|0644, st_size=77,
...}) = 0
stat("/root/.console-setup.small", 0x7fff0d5f00a0) = -1 ENOENT (No such
file or directory)
stat("/usr/etc/default/keyboard.small", 0x7fff0d5f0070) = -1 ENOENT (No
such file or directory)
setupcon: None of /usr/etc/default/keyboard.small nor
/root/.console-setup.small exists.
I noticed when I deployed this jessie host, that it was more picky
(than squeeze) about having some variables in /etc/default/keyboard
and some in /etc/default/console-setup. Maybe for a variant to work
in /etc, I have to have BOTH files?
# cat >console-setup.small
FONTFACE="Terminus"
FONTSIZE="12x6"
# cat >keyboard.small
XKBOPTIONS="altwin:ctrl_win,ctrl:nocaps"
# setupcon --font-only small
We are not on the console, the console is left unconfigured.
OK, so that works. The issues I see are:
1. this behaviour is not obvious from the --help, manpage, and error;
2. if I ask for -f it shouldn't care about keyboard.VARIANT; and
3. likewise for -k and console-setup.VARIANT.
signature.asc
Description: Digital signature
Bug#514651: request for enhancement: core.newwhitespace=error
#514651 is about "this should be possible", I wrote the below about "this should be easy", before I found #514651. I'll sending it just in chance it's actually useful. I want to be able to say, on a user-wide basis, 1. these things are whitespace errors; 2. NEVER let me introduce whitespace errors. core.whitespace meets (1), but apply.whitespace=error doesn't meet (2), and there's nothing like commit.whitespace=error. I commit bad whitespace, and don't find out until I try to rebase it. And the rebase doesn't tell me what's wrong, it just says "apply failed". I want things like commit and cherry-pick to say something like Aborted foo/bar.c:123: introduces trailing whitespace foo/quux.c: does not end in a newline If I need to commit something like a PNG or a symlink that would trigger an abort, I'd just comment it out temporarily. Apparently this can be done with hooks or smudge/clean filters, but it's a bit fiddly to arrange for it to always happen. Below is the #git conversation that lead to this ticket. twb> So I'm a bit sad because apply.whitespace=error doesn't trigger because I use "git add -p" then "git commit". twb> But it *does* trigger when I do "git rebase master" on symlinks, because git's fake symlink files have no trailing newline. twb> This is with git version 1.7.0.4 -- anybody know offhand if that's magically fixed by "FFS just use a current version!"? twb> Oh also if I can get "git commit" to abort when there are whitespace errors, that would also be fantastic. twb> PS: this is also with core.whitespace = space-before-tab, tab-in-indent, trailing-space, cr-at-eol cbreak-work> twb: apply is just apply, not commit and so on twb> cbreak-work: yeah I realize that twb> I only turn it on for apply because AFAIK that's the only place I can turn it on kadoban> twb: You can, with hooks. I use it in code all the time, goes right before running the test cases and bailing if they fail. kadoban> twb: actually I think the example hook is something about bailing on whitespace errors, iirc twb> hooks are a bit fiddly because then I have to turn them on for every repo separately (right?) cbreak-work> twb: just like configuration, hooks are repository local and not part of the history twb> cbreak-work: yeah what I want is an option that applies to everything my user does, like ~/.gitconfig cbreak-work> twb: put the hooks into your repository template cbreak-work> then they'll be in all new repositories you create twb> cbreak-work: even ones I clone? I haven't heard of repo templates before cbreak-work> clone is just a git init & other stuff kadoban> Yeah, that's what I do. Getting it to work well in a lot of cases is actually pretty hairy...think I found a guide at one point cbreak-work> ll /usr/local/share/git-core/templates/ twb> Mm, I really just want a thing that says "these things are whitespace errors. Don't let me introduce them EVER" cbreak-work> twb: use git diff --check somethingsomething in a pre-commit hook twb> cbreak-work: OK, can I edit those in $HOME? I don't have root on all my hosts. cbreak-work> I don't think so. Maybe. twb> Bleh. cbreak-work> they are in git's $PREFIX twb> May I quote you guys in a feature request? kadoban> Me? Uh sure if you want to. cbreak-work> if you want. twb> Thanks. kadoban> I think if I was going to request any features on it, I'd want a way to make the hook act on "what's about to be commited", IIRC it ws pretty annoying to wrap it in git resets and stashes to get that right. cbreak-work> kadoban: git diff --cached should give you the index, and unless some noob uses the per-file commit, that should be correct twb> I don't want it to "fix" it I just want it to dump core and say "whitespace was crap at foo.c:123" kadoban> cbreak-work: Yeah I think it wasn't too bad for something like whitespace, but IIRC like, running my test-cases required way more work cbreak-work> kadoban: hmm... I'd probably use git checkout with an external working dir overlay cbreak-work> twb: if you wanted to fix it, a clean/smudge filter pair with auto formating or whitespace cleaning would do that. cbreak-work> twb: that can also be configured in the settings twb> Hm. cbreak-work> (but needs a .gitattributes) twb> I think I'll just file a feature request and wait for someone else to make it turnkey signature.asc Description: Digital signature
Bug#746560: please package tig 2.0.1
Aníbal, Sebastian, Aníbal Monsalve Salazar wrote: > Please package tig 2.0.1 available at: > http://jonas.nitro.dk/tig/releases/tig-2.0.1.tar.gz I've done the first pass at packaging tig 2. I haven't updated debian/copyright, but I did the other things I usually do. Lintian is happy except for P: tig source: debian-watch-may-check-gpg-signature P: tig: no-upstream-changelog W: tig: manpage-has-errors-from-man usr/share/man/man7/tigmanual.7.gz 1015: warning [p 7, 10.8i, div `3tbd7,1', 0.3i]: can't break line I made a couple of contentious changes out of personal preference: - I stopped shipping HTML/PDF, since the manpages have the same content. - I moved tigrc from /etc/ to /usr/share/doc/tig/examples, since the default config is also built into the binary. tig_2.0.2-1.debian.tar.xz Description: Binary data signature.asc Description: Digital signature
Bug#751199: RFP: shellcheck -- static analysis and linting tool for sh/bash scripts
Package: wnpp Severity: wishlist * Package name: shellcheck Version : 0.3.3 Upstream Author : Vidar Holen * URL : https://hackage.haskell.org/package/ShellCheck * License : Affero GPL3 Programming Lang: Haskell Description : static analysis and linting tool for sh/bash scripts The goals of ShellCheck are: . * To point out and clarify typical beginner's syntax issues, that causes a shell to give cryptic error messages. * To point out and clarify typical intermediate level semantic problems, that causes a shell to behave strangely and counter-intuitively. * To point out subtle caveats, corner cases and pitfalls, that may cause an advanced user's otherwise working script to fail under future circumstances. . ShellCheck can output gcc style error messages and checkstyle compatible xml, which allows any editor to show inlined error messages. . It's also supported directly by Syntastic in Vim and Flycheck in Emacs. - why is this package useful/relevant? is it a dependency for another package? ==> no do you use it? ==> I want to *start* using it regularly. You can try shellcheck online: http://www.shellcheck.net/ I was idly considering running it on all the scripts in Debian and filing gazillions of patch bugs, but I'll probably never do it. :-) if there are other packages providing similar functionality, how does it compare? ==> AFAIK the closest thing to this in Debian is checkbashisms, which addresses a different issue. Similar functionality exists for *other* languages in Debian, e.g. perlcritic for perl. - how do you plan to maintain it? ==> No, I don't have the time or resources. I'm hoping the Haskell team can maintain it with near-zero effort. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643948: Doesn't occur when LDAP is unencrypted
Arthur, This datapoint is probably intuitive, but I'll point it out anyway. I've been running 0.9.2-1wheezy1 (my own backport) on top of wheezy for a while, and never saw this issue. In the last couple of weeks, I switched from unencrypted ldap://ldap to encrypted ldaps://ldap, and now I'm seeing it on around 10% to 20% of boots (with a sample set of about ten boots). I haven't tried with STARTTLS. So anyway: this issue appears to only arise if TLS is used. nslcd.conf diff: uid nslcd gid nslcd -uri ldap://ldap/ +uri ldaps://ldap/ +tls_cacertfile /etc/ssl/certs/com.prisonpc.pem base o=PrisonPC pam_authz_search (&(objectClass=posixGroup)(cn=prisoners)(memberUid=$username)) FTR, workarounds I'm considering are: - stunnel4 on the clients, then plaintext ldap over that. (I'm already doing this for http://wiki.squid-cache.org/Features/HTTPS#Encrypted_browser-Squid_connection due to problems with chromium.) - build openldap against openssl instead of gnutls. I used to do this to get sudo-ldap to work with PADL libpam-ldap, where gnutls+ldaps+setuid was broken. Obviously neither are appropriate fixes for Debian. signature.asc Description: Digital signature
Bug#741579: Hard-codes broken udhcpc args
Package: ifupdown
Version: 0.7.47.2
Severity: normal
inet.defn has this:
udhcpc -n -p /run/udhcpc.%iface%.pid -i %iface% [[-H %hostname%]] \
[[-c %client%]] \
elsif (execable("/sbin/udhcpc") && mylinuxver() >= mylinux(2,2,0))
But -H is not valid in the old udhcpc still in Debian:
$ /sbin/udhcpc --help |& grep -e -H
I think -H should be one of these, but I'm not sure which.
$ /sbin/udhcpc --help |& grep -i name
-x hostname:bbox - option 12
-F,--fqdn NAME Ask server to update DNS mapping for NAME
The [[-c %client%]] option is also gone.
I'm not sure what that is supposed to be -- possibly the vendorclass?
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ifupdown depends on:
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-51
ii iproute2 3.12.0-2
ii libc62.18-4
ii lsb-base 4.1+Debian12
Versions of packages ifupdown recommends:
pn isc-dhcp-client | dhcp-client
Versions of packages ifupdown suggests:
ii net-tools 1.60-25
pn ppp
pn rdnssd
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741593: Support profiling of ramdisk (a.k.a. initramfs, initrd)
Package: bootchart2 Version: 0.14.4-3 Severity: wishlist Currently bootchart2 can be used to profile everything after init easily, by booting with init=/sbin/bootchartd. I have some netboot kiosks that spend about 10s in the ramdisk doing boot=live (live-initramfs-tools) and then another 10s or so in init. It would be really awesome if I could get pretty graphs of what is wasting all the time in the initramfs. I tried to do it myself with bootchart2, then with busybox's builtin bootchart applet[0], but I couldn't work it out. [0] disabled at compile time in Debian busybox packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741593: Support profiling of ramdisk (a.k.a. initramfs, initrd)
Riccardo, I added /etc/initramfs-tools/hooks/bootchart2 as per #603656, and ran update-initramfs -ukall. With init=/sbin/bootchartd, the system boots normally. When I add rdinit=/sbin/bootchartd, it hangs at the kernel message "switched to clocksource tsc". The keyboard isn't working so I can't investigate further. I'm PXE booting a wheezy image using live-initramfs-tools 3.0.1-1 and bootchart2 0.14.4-3. root@spoon:~# cat /srv/tftp/pxelinux.cfg/01-00-e0-4c-a6-1a-a9 PROMPT 0 NOESCAPE 1 LABEL linux IPAPPEND 2 KERNEL images/tvserver-twb/vmlinuz APPEND initrd=images/tvserver-twb/initrd.img boot=live noprompt noeject netboot=nfs nfsroot=/srv/netboot/images live-media-path=tvserver-twb break single init=/sbin/bootchartd rdinit=/sbin/bootchartd root@spoon:~# file /srv/tftp/images/tvserver-twb/vmlinuz /srv/tftp/images/tvserver-twb/vmlinuz: Linux kernel x86 boot executable bzImage, version 3.12-0.bpo.1-amd64 (debian-kern, RO-rootFS, swap_dev 0x2, Normal VGA root@spoon:~# xzcat /srv/tftp/images/tvserver-twb/initrd.img | cpio -t | grep -e bash -e bootchart sbin/bootchartd lib/bootchart lib/bootchart/tmpfs lib/bootchart/bootchart-collector 113363 blocks etc/bootchartd.conf bin/bash And suggestions about what to try next? signature.asc Description: Digital signature
Bug#742003: Additional notes
From #d-mentors, [...] twb> Actually the reason is that under wheezy, scribus templates assume Arial is in the path twb> And installing Liberation fonts doesn't help twb> It just pops up a thing saying "what typeface should I use instead?" which defaults to the *FIRST* font in the list, lexicographically pabs> sounds like a usability bug, is it fixed in jessie? twb> cjb says no pabs> if so options are backport the whole thing or backport a small patch to wheezy version and get it accepted by the release team twb> atm this is my shitty workaround: # Remove references to MS fonts from Scribus templates. gunzip /usr/share/scribus/templates/*/*.sla.gz sed -i /usr/share/scribus/templates/*/*.sla \ -e 's/Arial Regular/Liberation Sans Regular/g' \ -e 's/Arial Black Regular/Liberation Sans Bold/g' \ -e 's/FreeSans Medium/Liberation Sans Bold/g' gzip --fast /usr/share/scribus/templates/*/*.sla SamB> twb: if you actually wanted Arial, the .deb probably doesn't contain the font itself? twb> SamB: I don't want Arial. twb> SamB: I want scribus to believe "fc-match Arial" which says to use Liberation Sans pabs> I need to write a template for 'please use fontconfig for looking up font locations' pabs> https://wiki.debian.org/Fonts#fontconfig [...] pabs> hmm, includes less detail [on #742003] than you mentioned on IRC twb> pabs: with your permission, I'll just dump this IRC transcript in an email to that task. pabs> sure An affected file is /usr/share/scribus/templates/pres_backgr_4/bokeh.sla.gz in In the above I'm replacing FreeSans; that's in Debian, it's just fugly. You're doing Recommends: xfonts-scalable | gsfonts-x11, you might add the fonts-* packages that your templates use. fonts-liberation is the obvious replacement for Arial. I guess freemono is "fonts-freefont-ttf | fonts-freefont-otf". signature.asc Description: Digital signature
Bug#741593: Support profiling of ramdisk (a.k.a. initramfs, initrd)
I did some more investigation, and after reading /sbin/bootchartd came up with a simpler hook that's 90% right: #!/bin/sh # Absolute barebones setup for rdinit=/sbin/bootchartd. # Does not support /etc/bootchartd.conf magic, # which in the ramdisk is only the sample rate (default 50Hz). set -e case $1 in (prereqs) echo busybox; exit;; esac . /usr/share/initramfs-tools/hook-functions copy_exec /lib/bootchart/bootchart-collector printf '#!/bin/sh\n/lib/bootchart/bootchart-collector -c &\nexec /init "$@"\n' >"$DESTDIR"/sbin/bootchartd chmod +x "$DESTDIR"/sbin/bootchartd # bootchart-collector mounts a tmpfs here. mkdir -p "$DESTDIR"/lib/bootchart/tmpfs Now when I boot with "break rdinit=/sbin/bootchartd", I get /sbin/bootchartd: line 2: can't open '/dev/null' Loading, please wait... Begin: Loading essential drivers ... done. [...] and if I run "ps | grep [b]ootchart" from the break (ramdisk shell), I can see bootchart-collector isn't running. If I then run "/lib/bootchart/bootchart-collector -c &" it falsely claims bootchart-collector run outside initrd It's whinging about /dev/null because sh implicitly redirects stdin of backgrounded children there. Explicitly closing stdin first didn't work: printf '#!/bin/sh\n/lib/bootchart/bootchart-collector -c <&- & exec /init "$@"\n' >"$DESTDIR"/sbin/bootchartd But creating /dev/null does! printf '#!/bin/sh\nmknod /dev/null c 1 3; ls -ld /dev/null; /lib/bootchart/bootchart-collector -c & exec /init "$@"\n' >"$DESTDIR"/sbin/bootchartd That successfully starts a bootchart-collector which is still running when I get to the "break" shell, though it is also complaining about "run outside initrd". OK, so after I confirmed bootchart-collector is running there, I let boot proceed. But when I let that proceed to the desktop, there's no /var/log/bootchart*. I'll have to leave it here for now. signature.asc Description: Digital signature
Bug#505382: libnss3-tools binaries are missing man pages
Package: libnss3-tools Version: 2:3.15.4-2 Followup-For: Bug #505382 As at 3.15.4, upstream ships manpages! They are in nss/doc/*.xml in docbook format, but pre-rendered HTML and roff versions are also available. Please create this file to quickly include them in Debian: debian/libnss3-tools.manpages: nss/doc/nroff/*.1 -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnss3-tools depends on: ii libc6 2.18-4 ii libnspr4 2:4.10.3-1 ii libnss3 2:3.15.4-2 ii libsqlite3-0 3.8.3.1-1 ii zlib1g1:1.2.8.dfsg-1 libnss3-tools recommends no packages. libnss3-tools suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#611754: bugs.debian.org: oldbugs.html shows quite a recent bugs
Package: bugs.debian.org Followup-For: Bug #611754 This bug is still present today (Mar 2014). Thanks to Murukesh Mohanan for pointing it out on #debian-mentors. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.13-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698203: Not a directory at /var/lib/dpkg/info/linux-base.postinst line 1177. (extlinux)
Package: linux-base
Version: 3.5
Severity: minor
I did the following:
- basic squeeze install, choose no bootloader,
- manually do an extlinux install in /boot (extlinux package is NOT installed)
- set link_in_boot=yes in kernel-img.conf
Those are about the only things I did. Then I tried to upgrade from
squeeze to wheezy and got
Not a directory at /var/lib/dpkg/info/linux-base.postinst line 1177.
...without further helpful output. That line is part of a generic
function, so I straced dpkg --configure -a and found
4875 open("/boot/extlinux/options.cfg", O_RDONLY) = -1 ENOTDIR (Not a
directory)
I have not investigated further but I guess this is because linux-base
is finding /boot/ldlinux.sys and assuming it was configured in the way
update-extlinux does it.
FWIW even when I do install extlinux via apt, I typically have a
static /boot/syslinux.cfg and I disable update-extlinux so it doesn't
run.
If you aren't interested in supporting odd extlinux setups, that's OK
with me, but I would appreciate a less obscure error message.
Here is what my system looks like:
root@debian:~# cat /etc/kernel-img.conf
# Kernel image management overrides
# See kernel-img.conf(5) for details
do_symlinks = yes
do_bootloader = no
do_initrd = yes
link_in_boot = yes
root@debian:~# find /boot -ls
3440654 drwxr-xr-x 2 root root 4096 Jan 15 17:06 /boot
344067 108 -rw-r--r-- 1 root root 106172 Sep 24 00:08
/boot/config-2.6.32-5-amd64
344068 1632 -rw-r--r-- 1 root root 1666397 Sep 24 00:08
/boot/System.map-2.6.32-5-amd64
3440690 lrwxrwxrwx 1 root root 22 Jan 15 15:45
/boot/vmlinuz -> vmlinuz-2.6.32-5-amd64
3440710 lrwxrwxrwx 1 root root 25 Jan 15 15:45
/boot/initrd.img -> initrd.img-2.6.32-5-amd64
344072 60 -rwxr-xr-x 1 root root55176 Jan 15 15:45
/boot/extlinux
344066 2372 -rw-r--r-- 1 root root 2423968 Sep 23 23:59
/boot/vmlinuz-2.6.32-5-amd64
344080 8700 -rw-r--r-- 1 root root 8891560 Jan 15 17:06
/boot/initrd.img-2.6.32-5-amd64
344073 60 -rw-r--r-- 1 root root56164 Jan 15 15:46
/boot/menu.c32
344074 32 -r--r--r-- 1 root root32256 Jan 15 15:46
/boot/ldlinux.sys
3440764 -rw-r--r-- 1 root root 457 Jan 15 15:54
/boot/syslinux.cfg
344070 2060 -rw-r--r-- 1 root root 2101443 Dec 20 01:19
/boot/System.map-3.2.0-4-amd64
3440754 -rw-r--r-- 1 root root 445 Jan 15 15:54
/boot/syslinux.cfg~
344078 132 -rw-r--r-- 1 root root 128903 Dec 20 01:19
/boot/config-3.2.0-4-amd64
344079 2768 -rw-r--r-- 1 root root 2829472 Dec 20 01:16
/boot/vmlinuz-3.2.0-4-amd64
root@debian:~# cat /proc/partitions
major minor #blocks name
808388608 sda
root@debian:~# cat /proc/mounts
rootfs / rootfs rw 0 0
none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
none /proc proc rw,nosuid,nodev,noexec,relatime 0 0
none /dev devtmpfs rw,relatime,size=508624k,nr_inodes=127156,mode=755 0 0
none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000
0 0
/dev/disk/by-label/root / ext2 rw,relatime,errors=remount-ro 0 0
tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
/dev/disk/by-label/root /run ext2 rw,relatime,errors=remount-ro 0 0
/dev/disk/by-label/root /run/lock ext2 rw,relatime,errors=remount-ro 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698615: lp ignores silly options; should give error
Package: cups-client Version: 1.5.3-2.12 Severity: wishlist Tags: upstream While dealing with an unrelated issue, I tried to type date | lp -n2 -o collate=true but instead I typed date | lp -n2 --collate=true AFAICT, lp silently ignored the bogus option. I would strongly prefer that it instead gave an error like this, possibly followed by a help synopsis of valid options. lp: illegal option -- - In this case, because I didn't notice the typo, I ended up wasting a couple of hours trying to debug the pxlmono.ppd that (I thought) wasn't working as advertised :-( http://www.linuxfoundation.org/collaborate/workgroups/openprinting/database/ricohfaq#Why_can_I_not_print_multiple_copies.3F -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups-client depends on: ii adduser3.113+nmu3 ii cups-common1.5.3-2.12 ii libc6 2.13-33 ii libcups2 1.5.3-2.12 ii libcupsimage2 1.5.3-1 Versions of packages cups-client recommends: pn smbclient Versions of packages cups-client suggests: pn cups pn cups-bsd pn xpp -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698203: Not a directory at /var/lib/dpkg/info/linux-base.postinst line 1177. (extlinux)
Ben Hutchings wrote:
> I'll change it to treat ENOTDIR as non-fatal (same as ENOENT).
Thanks, that sounds appropriate to me.
> > 4875 open("/boot/extlinux/options.cfg", O_RDONLY) = -1 ENOTDIR (Not a
> > directory)
FTR, this was happening because /boot/extlinux existed -- it was the
installer program that on a normal install would be /usr/sbin/extlinux.
The same error would arise if the sysadmin did something like
echo "Don't forget this system isn't using grub!" > /boot/extlinux
I worked around it on my own system by simply "mv extlinux extlinux.exe".
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#452484: dosage: Multiplexing option similar to make -j 4
FTR, this is the workaround I came up with since filing the ticket: cd Comics && find * -type d | xargs -n1 -P4 mainline -vcb. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#668439: mg: leaves alternatives after purge
Andreas Beckmann wrote: > Followup-For: Bug #668439 > Control: tag -1 patch > > Hi, > > I'm attaching a minimal fix to the prerm script that fixes two issues: > * unregister the alternative in prerm remove > * keep the alternative untouched during upgrades - removing and readding > it everytime could overwrite any user customization. > > I intend to NMU this package in a few days with the above patch applied. Please do. I have been super lazy about mg for months, and if I'm honest, that is unlikely to change in the near future. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693393: Increase in .deb size from 2MB to 1.2GB!
Package: ns3-doc Version: 3.15+dfsg-1 Severity: normal At 1.2GiB, ns3-doc is currently the largest package in the repo. Since the previous version was only 2MiB, I suspect this is a bug. 11:44 Hm, $ rsync mirror.internode.on.net::debian/pool/main/n/ns3/ | grep doc 11:44 -rw-r--r-- 1320450910 2012/09/27 02:36:48 ns3-doc_3.15+dfsg-1_all.deb 11:44 -rw-rw-r-- 2085820 2010/04/18 03:02:20 ns3-doc_3.7.1-7_all.deb 11:44 That looks really really wrong 11:45 Same on http://ftp.debian.org/debian/pool/main/n/ns3/ On #debian-mentors, nbreen observes that that 3.14.1+dfsg-1 was only 12MB; that the problem appears to be an enormous doxygen tree, and that the issue appears to also affect freefoam-dev-doc (623MiB) and possibly mrpt-doc (280MiB). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693394: freefoam-dev-doc package increased from 66MB to 622MB!
Package: freefoam-dev-doc Version: 0.1.0+dfsg-1 Severity: normal Your dev-doc package is now one of the largest files in the repo. Since the previous version was relatively small, this may be a bug. On #debian-mentors, nbreen says the problem appears to be an enormous doxygen tree. Ref. http://bugs.debian.org/693393 (same issue for ns3-doc) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693946: mailfilter.crm spw misleading comment (underscore vs. hyphen)
Package: crm114 Version: 20100106-3 Severity: minor Tags: upstream mailfilter.cf says: #If you leave it as "DEFAULT-PASSWORD", you will not be able to #access the mail-to-myself commanding system, as "DEFAULT-PASSWORD" #is specifically _disabled_ as a legal password. Just pick something, eh? # :spw: /DEFAULT_PASSWORD/ Note that the comments use DEFAULT-PASSWORD (hyphen); the code uses DEFAULT_PASSWORD (underscore). From looking at mailreaver.crm, the underscore is correct. Please double-check that and (if I'm right) change the comments accordingly. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#694123: debcommit: support $onlydebian=1 for git
Package: devscripts
Version: 2.12.5
Severity: wishlist
File: /usr/bin/debcommit
I just migrated my packaging (collab-maint/mg) from darcs to git.
I maintain debian/ as a separate repo, which appears to correspond to:
} elsif (-d "debian/_darcs") {
$onlydebian = 1;
return "darcs";
}
There is no equivalent for git, so debcommit complains.
I think you want:
} elsif (-d "debian/.git") {
$onlydebian = 1;
return "git";
}
I don't know if other changes are also required.
-- Package-specific info:
--- /etc/devscripts.conf ---
--- ~/.devscripts ---
BTS_CACHE=no
DEBCHANGE_RELEASE_HEURISTIC=changelog
DEBUILD_DPKG_BUILDPACKAGE_OPTS="-tc -Zxz"
DEBUILD_LINTIAN_OPTS="--info --display-info --display-experimental --pedantic
--show-overrides --color auto"
DEB_BUILD_HARDENING=1
DEB_BUILD_OPTIONS=parallel=$(getconf _NPROCESSORS_ONLN || echo 1)
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages devscripts depends on:
ii dpkg-dev 1.16.9
ii libc6 2.13-33
ii perl 5.14.2-15
ii python2.7.3~rc2-1
Versions of packages devscripts recommends:
ii at3.1.13-2
ii curl 7.26.0-1
ii dctrl-tools 2.22.2
ii debian-keyring2012.06.01
ii dput 0.9.6.3
ii equivs2.0.9
ii fakeroot 1.18.4-2
ii gnupg 1.4.12-6
ii libcrypt-ssleay-perl 0.58-1
ii libdistro-info-perl 0.10
ii libjson-perl 2.53-1
ii libparse-debcontrol-perl 2.005-3
ii libsoap-lite-perl 0.714-1
ii liburi-perl 1.60-1
ii libwww-perl 6.04-1
ii lintian 2.5.10.2
ii man-db2.6.2-1
ii patch 2.6.1-3
ii patchutils0.3.2-1.1
ii python-debian 0.1.21
ii python-magic 5.11-2
ii sensible-utils0.0.7
ii strace4.5.20-2.3
ii unzip 6.0-7
ii wdiff 1.1.2-1
ii wget 1.13.4-3
ii xz-utils 5.1.1alpha+20120614-1
Versions of packages devscripts suggests:
pn bsd-mailx | mailx
ii build-essential 11.5
pn cvs-buildpackage
pn devscripts-el
pn gnuplot
pn libauthen-sasl-perl
pn libfile-desktopentry-perl
pn libnet-smtp-ssl-perl
pn libterm-size-perl
ii libtimedate-perl 1.2000-1
ii libyaml-syck-perl1.20-1
ii mutt 1.5.21-6.2
ii openssh-client [ssh-client] 1:6.0p1-3
pn svn-buildpackage
ii w3m 0.5.3-8
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#631167: On purge, deletes RRD databases without prompting.
Sebastian Harl wrote: > However, policy does not talk about anything else (besides log files > which should be removed as well) in that respect. *Imho*, "purge" is > meant to be "remove any trace of the package in question" which includes > generated data as well. Anyway, for now I'm downgrading the severity of > this bug, since there is no clear requirement for any behavior. I can see your point; I was pretty grumpy when I filed the report -- not least because as well as deleting /var/lib/collectd/rrd/ it also deleted all my /var/lib/collectd/rrd_-MM-DD.sq backups. >> This is *not cool*. I suppose it's reasonable to clean up /var/lib >> after oneself, but collectd-core should follow the example of RDBMSs >> and ask the user (via debconf) for confirmation before doing so. > > This is not handled consistently across different RDBMSs: while > MySQL prompts the user (and defaults to "keep the data") PostgreSQL > unconditionally removes all databases on "purge" as well. I apologize; I didn't know that. > Anyway, prompting the user in case of purging databases seems to be a > commonly accepted behavior. I currently tend to prompt the user on > "purge" using a debconf question of priority "high" but default to > remove the data. This seems like the best approach to me; taking into > account the arguments of both sides. Also, imho, that's in the spirit of > "with a chance to preserve the data" as mentioned above. > > Does that sound reasonable to you? That's ideal, thanks. > I've Cc'ed the collectd mailing list, hoping for some more user > feedback. IIRC that list is subscriber-only, but hopefully I have successfully spoofed my From to my subscribed address, and it won't be held for moderation there :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#679361: RFP: nwipe (DBAN) -- Erase disks for computer recycling
Package: wnpp Severity: wishlist * Package name: nwipe (DBAN) Version : 0.08 Upstream Author : Andy Bev * URL : http://www.andybev.com/index.php/Nwipe * License : GPL Programming Lang: C Description : Erase disks prior to donation DBAN is a well-known live image to wipe HDDs so that you can give the hardware to others without them getting access to your old data. Apparently the "active ingredient" of DBAN is dwipe, which is forked into a stand-alone package called nwipe. Having nwipe available in a Debian Live CD would avoid having to carry around a separate DBAN CD. See also https://en.wikipedia.org/wiki/DBAN -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642172: packaged 6.1.0.62018-1
Hi, Richard Sellam wrote: > Thank you for your interest in likewise-open package. > As said in http://mentors.debian.net/package/likewise-open , > i have a working likewise-open package in version 6.1.0.62018-1. > You can get this version from mentors or wait for the package to be > uploaded (hopefully soon, i've filled an RFS). Please note that Ubuntu has maintained packages of likewise-open since 2008 -- it is probably worth collaborating with them to avoid spurious packaging differences. I don't know why they didn't push their work into Debian :-/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#704504: dget: confused by "compressed" in ~/.curlrc
Package: devscripts Version: 2.12.6 Severity: wishlist File: /usr/bin/dget $ dget --insecure https://launchpad.net/~linrunner/+archive/tlp/+files/tlp_0.3.8.1-1.dsc [...] $ dpkg-source -x *dsc gpgv: Signature made Sat 30 Mar 2013 10:06:24 EST using DSA key ID BB97FFE6 gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./tlp_0.3.8.1-1.dsc dpkg-source: error: File ./tlp_0.3.8.1-1.diff.gz has size 21414 instead of expected 7455 $ file *.diff.gz tlp_0.3.8.1-1.diff.gz: unified diff output, UTF-8 Unicode text If I comment out "compressed" from my ~/.curlrc and refetch, I get $ file *diff.gz tlp_0.3.8.1-1.diff.gz: gzip compressed data, from Unix, max compression Since I'm reluctant to leave it commented out, it would be nice if dget passed the appropriate options to make curl DTRT. Unfortunately I suspect it won't be as easy as simply adding --no-compressed -- I darkly suspect that will break things for someone else. If that's the case, feel free to WONTFIX this, the issue doesn't bother me much. (FYI, this comment says why I originally added the option.) # When an httpd compresses without being told to, you end up with a # file "foo" that should actually be "foo.gz". This tells curl to # DTRT and decompress it so that "foo" contains "foo". compressed -- Package-specific info: --- /etc/devscripts.conf --- --- ~/.devscripts --- BTS_CACHE=no DEBCHANGE_RELEASE_HEURISTIC=changelog DEBUILD_LINTIAN_OPTS="--info --display-info --display-experimental --pedantic --show-overrides --color auto" DEB_BUILD_HARDENING=1 DEB_BUILD_OPTIONS=parallel=$(getconf _NPROCESSORS_ONLN || echo 1) -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages devscripts depends on: ii dpkg-dev 1.16.9 ii libc6 2.13-38 ii perl 5.14.2-20 ii python2.7.3-4 Versions of packages devscripts recommends: ii at3.1.13-2 ii curl 7.26.0-1+wheezy1 ii dctrl-tools 2.22.2 ii debian-keyring2012.11.15 ii dput 0.9.6.3+nmu1 ii equivs2.0.9 ii fakeroot 1.18.4-2 ii gnupg 1.4.12-7 ii libcrypt-ssleay-perl 0.58-1 ii libdistro-info-perl 0.10 ii libjson-perl 2.53-1 ii libparse-debcontrol-perl 2.005-3 ii libsoap-lite-perl 0.714-1 ii liburi-perl 1.60-1 ii libwww-perl 6.04-1 ii lintian 2.5.10.4 ii man-db2.6.2-1 ii patch 2.6.1-3 ii patchutils0.3.2-1.1 ii python-debian 0.1.21 ii python-magic 5.11-2 ii sensible-utils0.0.7 ii strace4.5.20-2.3 ii unzip 6.0-8 ii wdiff 1.1.2-1 ii wget 1.13.4-3 ii xz-utils 5.1.1alpha+20120614-2 Versions of packages devscripts suggests: pn bsd-mailx | mailx ii build-essential 11.5 pn cvs-buildpackage pn devscripts-el pn gnuplot pn libauthen-sasl-perl pn libfile-desktopentry-perl pn libnet-smtp-ssl-perl pn libterm-size-perl ii libtimedate-perl 1.2000-1 ii libyaml-syck-perl1.20-1 ii mutt 1.5.21-6.2 ii openssh-client [ssh-client] 1:6.0p1-4 pn svn-buildpackage ii w3m 0.5.3-8 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#101317: fixed ages ago
Hi, this issue was resolved many years ago by ifenslave-2.6 providing hooks in if-[up|down].d. I was about to close this, but first I think ifupdown should add a "Suggests: ifenslave", as it currently does for similar integration packages for ppp, dhcp and icmpv6. Opinions? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705584: syslog a succesful login (like pam_unix does)
Package: libpam-ldap Version: 184-8.6 Severity: wishlist On my netboot desktop farm, I used to have both pam_ldap and pam_unix enabled. I turned off pam_unix to workaround something or other. Only later did I realize this also meant I have no logs of when a user has successfully logged in, because pam_ldap has no equivalent of 2013-03-01T13:47:07+11:00 rental-su1-c20-92188 xdm[1818]: pam_unix(xdm:session): session opened for user p92188 by p92188(uid=0) I was about to roll a workaround (like, re-adding "session optional pam_unix.so"), but I noticed you're already patching pam_ldap.so to log failure to write to shadowLastChanged. How do you feel about adding a similar patch to log an opened session? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#705913: Choosing -ize/-ise has no effect
Package: aspell-en Version: 7.1-0-1 Severity: normal I can't see it stated anywhere, but I think en_GB-ize is supposed to let me have something close to Oxford spelling (en-GB-oed). When I tried it, it didn't work for me. $ cat test.txt The group analysed labour statistics published by the organization $ aspell dump dicts | while read dict; do printf %s' ' "$dict"; aspell list -l "$dict" < test.txt | fmt; done | column -t enanalysed en-variant_0 analysed en-variant_1 analysed en-variant_2 analysed en-w_accents analysed en-wo_accents analysed en_CA analysed en_CA-variant_0 analysed en_CA-variant_1 analysed en_CA-w_accents analysed en_CA-wo_accents analysed en_GB organization en_GB-ise organization en_GB-ise-w_accents organization en_GB-ise-wo_accents organization en_GB-ize organization en_GB-ize-w_accents organization en_GB-ize-wo_accents organization en_GB-variant_0 organization en_GB-variant_1 organization en_GB-w_accents organization en_GB-wo_accents organization en_US analysed labour en_US-variant_0 analysed labour en_US-variant_1 analysed labour en_US-w_accents analysed labour en_US-wo_accents analysed labour -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages aspell-en depends on: ii aspell 0.60.7~20110707-1 ii dictionaries-common 1.12.11 aspell-en recommends no packages. aspell-en suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706055: Unicode box art lines in git log --graph
Package: git Version: 1:1.8.2.1-1 Severity: wishlist Tags: upstream I like git log --graph. I'd like it more if it could use Unicode lines. A trivial example is mocked up below. BEFORE * 8f78c67 (origin/prisonpc-satellite) Merge branch 'wheezy' into prisonpc-satellite |\ | * 0278e82 (origin/wheezy) Fix authorized_keys - curl was not following the 302. * | 7c00a55 curl is not being used, nfs server will be. |/ * d44ef57 Remove obsolete workaround for Ubuntu Precise issues. * 8dc4129 Fix git describe. | * 1f2abd4 (origin/understudy-generic) Remove need for curl. | | * 8bebb40 (origin/prisonpc-gnome) Add notes on setting an appopriate pxelinux.cfg for Debian/NFSv3. | | * 90dcc9e Add necessary packages for gnome and iscsi. | |/ |/| * | 3045bd0 Sid now has a fix for NFSv3 with newer kernels. AFTER •─┐ 8f78c67 (origin/prisonpc-satellite) Merge branch 'wheezy' into prisonpc-satellite │ │ │ • 0278e82 (origin/wheezy) Fix authorized_keys - curl was not following the 302. • │ 7c00a55 curl is not being used, nfs server will be. ├─┘ • d44ef57 Remove obsolete workaround for Ubuntu Precise issues. • 8dc4129 Fix git describe. │ • 1f2abd4 (origin/understudy-generic) Remove need for curl. │ │ • 8bebb40 (origin/prisonpc-gnome) Add notes on setting an appopriate pxelinux.cfg for Debian/NFSv3. │ │ • 90dcc9e Add necessary packages for gnome and iscsi. │ │ │ ├─│─┘ • │ 3045bd0 Sid now has a fix for NFSv3 with newer kernels. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git depends on: ii git-man 1:1.8.2.1-1 ii libc62.13-38 ii libcurl3-gnutls 7.26.0-1+wheezy2 ii liberror-perl0.17-1 ii libexpat12.1.0-1 ii libpcre3 1:8.30-5 ii perl-modules 5.14.2-20 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages git recommends: ii less 444-4 ii openssh-client [ssh-client] 1:6.0p1-4 ii patch2.6.1-3 ii rsync3.0.9-4 Versions of packages git suggests: ii gettext-base 0.18.1.1-9 pn git-arch pn git-bzr pn git-cvs pn git-daemon-run | git-daemon-sysvinit pn git-doc pn git-el pn git-email pn git-gui pn git-svn pn gitk pn gitweb -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706596: wget tftp:// support
Package: busybox
Version: 1:1.20.0-7
Severity: wishlist
Tags: upstream
curl has a "conventional" tftp:/// syntax to download a
file from a TFTP server. To do the same with busybox tftp, you have
to break up the URL into pieces. If busybox wget supported tftp://
when the tftp applet was also compiled in, that would avoid the need
for this kind of code in live-boot:
case "$url" in
tftp*)
ip="$(dirname $url | sed -e 's|tftp://||g' -e 's|/.*$||g')"
rfile="$(echo $url | sed -e "s|tftp://$ip||g")"
lfile="$(basename $url)"
log_begin_msg "Trying tftp -g -b 10240 -r $rfile -l ${dest}/$lfile $ip"
tftp -g -b 10240 -r $rfile -l ${dest}/$lfile $ip
;;
*)
log_begin_msg "Trying wget ${url} -O ${dest}/$(basename ${url})"
wget "${url}" -O "${dest}/$(basename ${url})"
;;
esac
It would simplify to
wget "${url}" -O "${dest}/$(basename ${url})"
Hm... I just noticed that I'm losing the -b 10240 (default is 512),
which increases the download of a 40MB test file from 10s to 28s.
Maybe that's a good enough reason not to bother implementing this --
adding --tftp-block-size to the wget applet would be overkill.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706679: Missing Depends: file
Package: live-config Version: 3.0.23-1 Severity: minor During reboot of a minimal live image, I get live-boot: caching reboot files... /lib/live/boot-init.sh: 38: /lib/live/boot-init.sh: file: not found /lib/live/boot-init.sh: 38: /lib/live/boot-init.sh: file: not found /lib/live/boot-init.sh: 38: /lib/live/boot-init.sh: file: not found expr: syntax error Please remove the disc, close the tray (if any) and press ENTER to continue: This is because file is not installed. AFAICT, there are no hard depends anywhere in live-config's dependency chain, so it should either add one or check for file's presence before using it. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706679: Missing Depends: file
Trent W. Buck wrote: > Package: live-config > Version: 3.0.23-1 > Severity: minor > > During reboot of a minimal live image, I get > > live-boot: caching reboot files... > /lib/live/boot-init.sh: 38: /lib/live/boot-init.sh: file: not found > /lib/live/boot-init.sh: 38: /lib/live/boot-init.sh: file: not found > /lib/live/boot-init.sh: 38: /lib/live/boot-init.sh: file: not found > expr: syntax error > > > Please remove the disc, close the tray (if any) and press ENTER to > continue: > > This is because file is not installed. The expr line is an unrelated bug; if I install file, the expr line remains. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706686: quickreboot ignored by /lib/live/boot-init.sh
Package: live-config Version: 3.0.23-1 Severity: wishlist While quickreboot is documented in and parsed by live-boot, the actual prompting is done in /lib/live/boot-init.sh (from live-config). I am testing wheezy images with live-boot 3.0.1-1. If and only if live-config installed, "quickreboot" in /proc/cmdline is ignored, and I am prompted: Please remove the disc, close the tray (if any) and press ENTER to continue: If I change "quickreboot" to "noprompt noeject", it reboots without prompting (as desired). The full APPEND line passed via pxelinux.cfg is initrd=live-satellite/initrd.img boot=live quickreboot ipv6.disable=1 fetch=tftp://10.128.0.1/live-satellite/filesystem.squashfs loglevel=1 personality=fred live-config Does it even make sense to prompt before shutdown when netbooting? If so, the prompt should not mention disc or tray. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706691: In rc0.d, sendsigs stops before rpcbind stops
Package: rpcbind Version: 0.2.0-8 Severity: normal In a minimal live-boot image I built, I noticed that sendsigs was running before all the NFS stuff was turned off. # ls /etc/rc0.d/ -l total 4 lrwxrwxrwx 2 root root 23 2013-05-03 21:19 K01busybox-klogd -> ../init.d/busybox-klogd lrwxrwxrwx 2 root root 25 2013-05-03 21:19 K01busybox-syslogd -> ../init.d/busybox-syslogd lrwxrwxrwx 2 root root 27 2013-05-03 21:19 K01nfs-kernel-server -> ../init.d/nfs-kernel-server lrwxrwxrwx 4 root root 17 2013-05-03 21:17 K01urandom -> ../init.d/urandom lrwxrwxrwx 2 root root 18 2013-05-03 21:19 K02sendsigs -> ../init.d/sendsigs lrwxrwxrwx 2 root root 22 2013-05-03 21:19 K03umountnfs.sh -> ../init.d/umountnfs.sh lrwxrwxrwx 2 root root 20 2013-05-03 21:19 K04nfs-common -> ../init.d/nfs-common lrwxrwxrwx 2 root root 17 2013-05-03 21:19 K04rpcbind -> ../init.d/rpcbind lrwxrwxrwx 2 root root 20 2013-05-03 21:19 K05hwclock.sh -> ../init.d/hwclock.sh lrwxrwxrwx 2 root root 20 2013-05-03 21:19 K05networking -> ../init.d/networking lrwxrwxrwx 2 root root 18 2013-05-03 21:19 K06umountfs -> ../init.d/umountfs lrwxrwxrwx 2 root root 20 2013-05-03 21:19 K07umountroot -> ../init.d/umountroot lrwxrwxrwx 2 root root 14 2013-05-03 21:19 K08halt -> ../init.d/halt -rw-r--r-- 4 root root 353 2012-10-16 04:30 README pere (Petter Reinholdtsen) and I had a bit of a puzzle over it. Since rpcbind's init.d exactly matches the one portmap 6.0.0-5 had, he thinks it's probably related to sendsigs omit list, which is stored in /run/sendsigs.omit* and (therefore) generated at boot time. Perhaps this issue occurs for me because I have no /etc/exports yet, so nfs-kernel-server doesn't start -- but rpcbind does? When I look at a running system I see root@s-a:~# ls -l /run/sendsigs* total 0 lrwxrwxrwx 1 root root 16 May 3 21:29 rpcbind -> /run/rpcbind.pid lrwxrwxrwx 1 root root 22 May 3 21:29 statd -> /var/run/rpc.statd.pid root@s-a:~# grep ^ /run/sendsigs.omit.d/* /run/sendsigs.omit.d/rpcbind:1955 /run/sendsigs.omit.d/statd:1989 I notice that statd has a trailing newline but rpcbind doesn't. Is that significant? RTFS of sendsigs' init.d suggests not. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706693: hwclock.sh creates incorrect /etc/adjtime
Package: util-linux Version: 2.20.1-5.3 Severity: normal I created a minimal live netboot image, and I noticed it was complaining during shutdown: [info] Saving the system clock. hwclock: Warning: unrecognized third line in adjtime file (Expected: `UTC' or `LOCAL' or nothing.) The file doesn't exist before boot; after boot it contains 0.0 0 0.0 0 UTC *BUT* it has no trailing newline. If I add the trailing newline by hand, hwclock does not complain during the shutdown sequence. AFAICT, my /etc/adjtime is created by a printf in /etc/init.d/hwclock.sh. I think the fix is simply to change printf "0.0 0 0.0\n0\nUTC" > /etc/adjtime to printf "0.0 0 0.0\n0\nUTC\n" > /etc/adjtime -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#706933: 1100-sslcert checks for wrong package; snakeoil cert is not regenerated
Package: live-config Version: 3.0.23-1 Severity: normal [When asked privately in IRC, dba didn't consider this a security issue, so I'm reporting it normally.] It looks like /lib/live/config/1100-sslcert is trying to regenerate the snakeoil key & cert at boot time, similar to how SSH host keys are handled in 1170-openssh-server. AFAICT this code will never run, because it looks for "sslcert" when it should look for "ssl-cert". If someone builds a live SOE with a daemon, and that daemon is stupid enough to use the snakeoil certs instead of generating its own, that daemon will be using the same key across all boots/instances. If an attacker got hold of the SOE, they could extract the build-time snakeoil key and use it for MITM type things. (Of course, any daemon that generates its own certs would need an equivalent to this script, or be similarly affected. Same thing if someone builds a live SOE with dropbear or lsh instead of openssh.) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703392: Support round numbers (4GiB not 4GB)
Package: partman Severity: wishlist Quick ticket before I forget this again. When I do an install with LVM LVs created by partman, and I say "4GB" and partman reports them as 4GB, once the install is finished lvs will list them as 3.78g or something, so I lvextend them. This is a bit icky, and it means that all my LVs start their lives with non-adjacent extents at the end. I did try "4GiB" and suchlike, but partman couldn't parse that. I didn't try specifying the size in bytes, that might have worked. Apologies for the lack of Version: - I don't remember what versions of d-i I found this against. Maybe this has even been fixed already. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#703593: squashfs4 support
Package: file-roller Severity: wishlist Tags: upstream Squashfs4 is a compressed archive format that can EITHER be mounted as a loopback read-only filesystem OR it can be treated as an archive like tgz or zip -- using "unsquashfs foo.sq" to extract some/all files, or with -ls / -ll to list the contents. I've been cheerfully using squashfs with CLI tools for some time, but some of my managers are more comfortable with a GUI archiver -- I think file-roller is what they use. It would be great if file-roller could create and open squashfs archives. PS: a little background - squashfs3 is an older variant that you can probably ignore. squashfs4 initially used zlib from compression; newer tools/kernels also support LZMA2 and LZO. AFAIK squashfs-tools does not provide a library to link to, just mksquashfs and unsquashfs. Also note those two are very picky about the order of their arguments. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699410: false positive for shell-script-fails-syntax-check (bash -O extglob)
Package: lintian
Version: 2.5.10.3
Severity: minor
In an exceptionally stupid in-house package, I ran across a false
positive for shell-script-fails-syntax-check. Distilled, it is
$ cat tmp.bash
#!/bin/bash
shopt -s extglob
ls -ld /home/!(prisoners)
$ bash -n tmp.bash
tmp.bash: line 3: syntax error near unexpected token `('
tmp.bash: line 3: `ls -ld /home/!(prisoners)'
$ bash -O extglob -n tmp.bash
$ bash tmp.bash
drwxr-xr-x 1 twb twb 6538 Jan 27 00:00 /home/twb
This happens because -n prevents bash from switching into extglob mode
before parsing the third line. Manually telling bash to be in extglob
at the start of the file shows it has no syntax errors.
A pathological script could turn extglob/nullglob/&c on and off
halfway through, so I see no way to handle this other than to
downgrade the certainty from "certain", at least for bash scripts.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages lintian depends on:
ii binutils 2.22-7.1
ii bzip2 1.0.6-4
ii diffstat 1.55-3
ii file 5.11-2
ii gettext0.18.1.1-9
ii hardening-includes 2.2
ii intltool-debian0.35.0+20060710.1
ii libapt-pkg-perl0.1.26+b1
ii libarchive-zip-perl1.30-6
ii libc-bin 2.13-37
ii libclass-accessor-perl 0.34-1
ii libclone-perl 0.31-1+b2
ii libdpkg-perl 1.16.9
ii libemail-valid-perl0.190-1
ii libipc-run-perl0.92-1
ii libparse-debianchangelog-perl 1.2.0-1
ii libtimedate-perl 1.2000-1
ii liburi-perl1.60-1
ii locales2.13-37
ii man-db 2.6.2-1
ii patchutils 0.3.2-1.1
ii perl [libdigest-sha-perl] 5.14.2-16
lintian recommends no packages.
Versions of packages lintian suggests:
pn binutils-multiarch
ii dpkg-dev 1.16.9
ii libhtml-parser-perl3.69-2
pn libperlio-gzip-perl
pn libtext-template-perl
ii man-db 2.6.2-1
ii xz-utils [lzma]5.1.1alpha+20120614-2
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645286: fix works
Trent W. Buck wrote: > I applied 5629fba80b05cc906c45e62c397d18e5afa18636 to wheezy's > 1.4.25-2 and the resulting binary fixed the problems I was having, > when run with buffer_mail=on in ~/.msmtprc. (Without > buffer_mail=on, the problem came back, so the test is sound.) > > So, if it's not too much trouble, I would like this functionality to > be maintained in new releases of msmtp. Thanks! Hi, while doing something else, I found this in cron's Debian.NEWS file: cron (3.0pl1-110) unstable; urgency=low In the past, long-running jobs caused certain MTAs to time out, resulting in no output being sent. Justin Pryzby's patch to fix this has been included. crontab(1) now refuses any crontabs missing a newline before EOF. cron(8) now recovers from broken symlinks in /etc/cron.d. This fix may cause power management issues (disk spin-ups), feedback welcome. -- Christian Kastner Thu, 29 Apr 2010 13:25:09 +0200 So I guess this is fixed now? I haven't had time to test it yet. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701863: invoke-rc.d: report service when policy-rc.d prevents execution.
Package: sysv-rc Version: 2.88dsf-41 Severity: wishlist File: /usr/sbin/invoke-rc.d When doing "dpkg-reconfigure -a" in a chroot where everything is denied by policy-rc.d, I see a sequence like this: live-boot: core filesystems devices utils udev blockdev. update-initramfs: deferring update (trigger activated) invoke-rc.d: policy-rc.d denied execution of stop. invoke-rc.d: policy-rc.d denied execution of start. invoke-rc.d: policy-rc.d denied execution of restart. invoke-rc.d: policy-rc.d denied execution of stop. invoke-rc.d: policy-rc.d denied execution of start. invoke-rc.d: policy-rc.d denied execution of restart. Not restarting sysvinit I can't tell which services weren't restarted. How do you feel about including the service name in that output? Something like this: live-boot: core filesystems devices utils udev blockdev. update-initramfs: deferring update (trigger activated) invoke-rc.d: policy-rc.d denied execution of stop (acpid). invoke-rc.d: policy-rc.d denied execution of start (acpid). invoke-rc.d: policy-rc.d denied execution of restart (busybox-syslogd). invoke-rc.d: policy-rc.d denied execution of stop (ntp). invoke-rc.d: policy-rc.d denied execution of start (ntp). invoke-rc.d: policy-rc.d denied execution of restart (ssh). Not restarting sysvinit -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702835: debhelper-but-no-misc-depends
Package: dh-make
Version: 0.61
Severity: minor
File: /usr/share/debhelper/dh_make/debianl/control
Building a freshly dh-make'd library package, I get
debhelper-but-no-misc-depends. I think this is a trivial fix by
adding the ${misc:Depends} lines to control by default, at least when
using dh7 style.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.7-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dh-make depends on:
ii debhelper 9.20120909
ii dpkg-dev 1.16.9
ii make 3.81-8.2
ii perl 5.14.2-16
dh-make recommends no packages.
Versions of packages dh-make suggests:
ii build-essential 11.5
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#702925: Replace cups-specific mime.types/libcupsmime with libmagic
Package: cups Version: 1.5.3-2.15 Severity: wishlist File: /usr/share/cups/mime/mime.types Tags: upstream I came across mime.types / libcupsmime and my immediate reaction is "why is cups doing this, when libmagic already provides a perfectly good library and database of MIME type heuristics?" There's probably a reason, but I couldn't work it out from a brief search. I'm creating this ticket in case nobody has ever thought of this before. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#568074: Xfbdev: LinuxInit: Server must be suid root
Cyril Brulebois wrote:
> Trent W. Buck (03/02/2010):
> > Julien Cristau wrote:
> > >> $ xinit -- /usr/bin/Xfbdev
> > >> Fatal server error:
> > >> LinuxInit: Server must be suid root
> > > It doesn't get the wrong mode. It needs to be started as root.
> >
> > Is it reasonable to patch the source so that the error message
> > reflects this?
>
> That:
> s/suid/{started,run} as/
>
> should do? I'll do so if there's no objection.
Yes, thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571300: fsck.btrfs does not support -a option used by checkroot.sh
Version: 0.19-8 Joey Hess wrote: > /etc/init.d/checkroot.sh runs fsck with an option of either -a or -y > (depending on a configuration variable). FYI, the -f option also appears to be important; with a btrfs root filesystem I tried "touch /forcefsck; reboot" and got Checking root file system...fsck from util-linux-ng 2.16.2 Could not open -f fsck died with exit status 1 failed (code 1). AFAICT this doesn't affect the solution (workaround) discussed elsewhere in this thread. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#573108: Clarify what "ldap support" means.
Package: sudo-ldap Version: 1.7.2p1-1.2 Severity: wishlist Currently this variant describes itself as This version is built with LDAP support. This puzzled me, because libpam-ldap already allows you to perform authentication via LDAP -- did sudo-ldap only exist for people that hated pam and wanted to talk directly to the LDAP database? In discussion it was suggested that the purpose of sudo-ldap is that it allows the sudoers database to be distributed as LDAP objects instead of a flat /etc/sudoers file. If that's the case, a description like This version is built with LDAP support. This allows the sudoers database to be distributed via LDAP (instead of /etc/sudoers). Authentication is still performed via pam. will help me remember why this package exists. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571054: Divert /sbin/initctl to fix start(8) in lucid postinsts.
Junichi Uekawa wrote: >> pbuilder currently creates a policy-rc.d that prevents daemons from >> starting when they are installed to satisfy build dependencies. >> This works well for sysvinit packages. >> >> However, when working with Ubuntu Lucid[0] chroots, many daemons >> use upstart instead of sysvinit. Thus, they ignore policy-rc.d, >> try (and fail) to start, further causing the postinst, dpkg, >> satisfybuildepends and ultimately the entire pdebuild to fail. > > Erm... why not fix upstart to respect policy-rc.d ? I don't know if it should -- I'm just a lowly sysadmin. By all means try to convince the upstart people to support policy-rc.d. If so, please retitle and reassign this ticket to upstart. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575797: There is no layout engine support for "dot". Perhaps "dot -c" needs to be run (with installer's privileges) to register the plugins?
Package: graphviz Version: 2.26.3-3 Severity: important Upon installing graphviz, I am confronted with $ dot --help There is no layout engine support for "dot" Perhaps "dot -c" needs to be run (with installer's privileges) to register the plugins? I don't remember seeing this before. Is there any reason this operation can't be done at build time (debian/rules) or at install time (debian/postinst)? Running "sudo dot -c" appears to fix it. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages graphviz depends on: ii libc62.10.2-6Embedded GNU C Library: Shared lib ii libcdt4 2.26.3-3rich set of graph drawing tools - ii libcgraph5 2.26.3-3rich set of graph drawing tools - ii libexpat12.0.1-7 XML parsing C library - runtime li ii libgd2-noxpm 2.0.36~rc1~dfsg-3.1 GD Graphics Library version 2 (wit ii libgraph42.26.3-3rich set of graph drawing tools - ii libgvc5 2.26.3-3rich set of graph drawing tools - ii libgvpr1 2.26.3-3rich set of graph drawing tools - ii libx11-6 2:1.3.3-2 X11 client-side library ii libxaw7 2:1.0.7-1 X11 Athena Widget library ii libxmu6 2:1.0.5-1 X11 miscellaneous utility library ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library Versions of packages graphviz recommends: ii ttf-liberation 1.05.2.20091019-4 Fonts with the same metrics as Tim Versions of packages graphviz suggests: pn graphviz-doc (no description available) ii gsfonts 1:8.11+urwcyr1.0.7~pre44-4 Fonts for the Ghostscript interpre -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#575883: Ignores USB keyboards connected after boot.
Package: sleepd Version: 2.01 Severity: normal File: /usr/sbin/sleepd If I boot my laptop, THEN connect a USB keyboard, sleepd puts my system to sleep while I'm busy typing (on the external keyboard). The symptoms don't appear if the keyboard is connected at boot, and they disappear if I issue a "sudo /etc/init.d/sleepd restart" while the keyboard is connected. I therefore hypothesize that sleepd doesn't notice when HIDs are added/removed; it simply monitors the list of HIDs present when it started. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sleepd depends on: ii libapm1 3.2.2-14 Library for interacting with APM d ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst ii libhal1 0.5.14-2 Hardware Abstraction Layer - share ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip Versions of packages sleepd recommends: pn hal(no description available) ii pm-utils 1.3.0-1utilities and scripts for power ma sleepd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#576120: Sending 333 in response to /query confuses rcirc.
Package: bitlbee Version: 1.2.5-1 Severity: normal I got the error below when connecting rcirc (part of GNU Emacs) to bitlbee, which was speaking XMPP to an internal server (running ejabberd, I believe). rcirc's developer, rcy, believes bitlbee is at fault. Please investigate. I just got this when /query'ing a nick on a bitlbee server: 14:10 *** 311 ron ron soy.office.cyber.com.au * ron 14:10 *** 312 ron t...@soy.office.cyber.com.au. jabber network 14:10 !!! ":localhost 333 twb ron :Status: wtf am I doing here?" (wrong-type-argument stringp nil) 14:10 *** 318 ron End of /WHOIS list rcirc expects that 333 is sent after 332, which describes the topic. Weird that bitlbee is sending it there to show what looks like a user status. Yeah, http://www.alien.net.au/irc/irc2numerics.html says its RPL_TOPICWHOTIME. So I say ron should just fix his shit. FSVO ron = bitlbee. Because ron is probably running pidgin. Right. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bitlbee depends on: ii adduser 3.112 add and remove users and groups ii debconf [debconf-2.0]1.5.30 Debian configuration management sy ii debianutils 3.2.2 Miscellaneous utilities specific t ii libc62.10.2-6Embedded GNU C Library: Shared lib ii libevent-1.4-2 1.4.13-stable-1 An asynchronous event notification ii libglib2.0-0 2.22.4-1The GLib library of C routines ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr ii net-tools1.60-23 The NET-3 networking toolkit bitlbee recommends no packages. bitlbee suggests no packages. -- debconf information: bitlbee/serveport: 6667 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#576248: Preserve mutt Old flag.
Package: offlineimap Version: 6.2.0+nmu2 Severity: wishlist I use offlineimap unidirectionally to create a local cache of my gmail inbox. I browse both imap.gmail.com and ~/Mail with mutt. For the former, mutt distinguishes between "new" and "old" (in mutt terms) by adding (KEYWORD Old) to IMAP messages. After running offlineimap, the mail in the maildir inbox all shows up as "new" (in mutt terms). I wish offlinimap would magically preserve mutt's notion of "oldness" when turning an IMAP folder into a maildir folder. PS: note that (KEYWORD Old) isn't the same as IMAP's notion of OLD, i.e. (NOT RECENT). -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.33-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages offlineimap depends on: ii python2.5.4-9An interactive high-level object-o ii python-support1.0.7 automated rebuilding support for P offlineimap recommends no packages. Versions of packages offlineimap suggests: pn python-kerberos(no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#526598: emacs-goodies-el: please include paredit.el 21
# Put this ticket in MY queue. reopen 526598 reassign 526598 paredit-el retitle 526598 Prepare paredit for inclusion in emacs-goodies-el thanks Peter S Galbraith wrote: > - Instead of the HTML, provide documention in a form suitable for >inclusion into the Info doc of emacs-goodies-el (I can do the markup; >I just need the text. It might simply be most of the commentary in >the elisp file.) Upstream builds the HTML from elisp using elisp, so I'll have to patch it to emit texinfo instead. > BTW, the mentors link: > > http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=paredit-el > doesn't lead to a file that I can download (anymore?) so I never saw > your latest version. Yeah, I don't know what happened there. I lost that copy, too, but the changes were only to debian/; I never touched the .el or .html contents. Upstream is still http://mumble.net/~campbell/emacs/; with paredit-N.el being a release, paredit.el being the latest release, and paredit/ being the VCS repo. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630108: Stopped propagating errors from child.
Package: kbd Version: 1.15.3-3 Severity: normal File: /bin/openvt The version of openvt(1) I had yesterday, would return an error if its child did, i.e. "openvt -sw -- false", failed. This version doesn't. I want the old behaviour back, because it's useful for my scripts. I think my old version was [UPGRADE] kbd 1.15.2-3 -> 1.15.3-3 but I upgraded a lot of stuff yesterday. :-( PS: I'm using kbd instead of console-setup because the former can do a smaller Terminus font than the latter. If you can tell me how to do that in console-setup, I'm happy to switch to it. $ cat ~/.console-setup # -*- sh -*- #. /etc/default/console-setup || : ## FIXME: only list tty's owned by my user. # ACTIVE_CONSOLES="/dev/tty[1-6]" # CHARMAP="UTF-8" # CODESET="Uni2" FONTFACE="Terminus" FONTSIZE="12x6" # XKBMODEL="pc105" # XKBLAYOUT="us" # XKBVARIANT="" XKBOPTIONS="ctrl:nocaps" -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kbd depends on: ii console-setup 1.73 console font and keymap setup prog ii libc6 2.13-6 Embedded GNU C Library: Shared lib ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip Versions of packages kbd recommends: ii console-setup 1.73 console font and keymap setup prog kbd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630108: [Pkg-kbd-devel] Bug#630108: Stopped propagating errors from child.
Anton Zinoviev wrote: >>> PS: I'm using kbd instead of console-setup because the former can do a >>> smaller Terminus font than the latter. [...] > > Maybe Trent means console-tools (not console-setup)? Console-tools > doesn't support small font sizes (12x6). Sorry, yes, I meant console-tools. I explicitly replace it with kbd on my systems to get 12x6 fonts. I assume that's a well-known and well-understood limitation of console-tools, but I can still provide debugging information if that'll lead to it being fixed :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#630448: iptables-apply: does not rollback on error.
Package: iptables Version: 1.4.10-1 Severity: normal File: /usr/sbin/iptables-apply If iptables-restore exits with a non-zero status, iptables-apply will NOT roll back to the original ruleset. This is not a problem if the file contains a single table (e.g. *filter ... COMMIT), because that is atomic. However if the file contains multiple tables, and the Nth one contains a bug (for example, -d does-not-resolve), the system will be left in an inconsistent state, with the first through (n-1)th tables loaded, and the remaining tables NOT loaded. The most likely scenario is *filter + *nat, but the behaviour is easy to reproduce with two *filter tables -- first loading a "paranoid" ruleset, and then loading a "featureful" ruleset. The former exists to prevent the system winding up in an "allow all" state if the latter fails to load at boot time (say, because you have installed a new kernel but not a new xtables-addons). Here is a concrete example. Suppose someone breaks local resolution of "www" and "mail" because "hey, they're in DNS, no need to put them in /etc/hosts as well". At this point, iptables-restore will load the first ruleset, "mail" will stop resolving, and iptables-restore will exit, as will iptables-apply. The first ruleset is left in place instead of the original ruleset that existed *prior* to running iptables-apply. #!/usr/sbin/iptables-apply *filter :INPUT DROP :FORWARD DROP :OUTPUT ACCEPT -A INPUT -p tcp --dport ssh -j ACCEPT # DNS lookups should fail immediately (not timeout). -A OUTPUT -p udp --dport domain -j REJECT COMMIT *filter :OUTPUT ACCEPT :INPUT DROP :FORWARD DROP -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT -A INPUT -m conntrack ! --ctstate NEW -j DROP -A INPUT -p icmp -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -p tcp --dport ssh -j ACCEPT -A FORWARD -d mail -p tcp -m multiport --dports smtp,submission,imaps -j ACCEPT -A FORWARD -d www -p tcp -m multiport --dports http,https-j ACCEPT -A INPUT -j REJECT -A FORWARD -j REJECT COMMIT This behaviour is actually desirable for me during boot, but I can get that by running iptables-restore. As as "safety net", I think iptables-apply should behave differently, like this: diff -ud /usr/sbin/iptables-apply /tmp/buffer-content-1489yVu --- /usr/sbin/iptables-apply2010-10-30 03:46:48.0 +1100 +++ /tmp/buffer-content-1489yVu 2011-06-14 16:22:10.679281774 +1000 @@ -141,6 +141,10 @@ if ! "$RESTORE" <"$FILE"; then echo "failed." echo "E: unknown error applying new iptables ruleset." >&2 +echo "Timeout. Something happened (or did not). Better play it safe..." +echo -n "Reverting to old ruleset... " +"$RESTORE" <"$TMPFILE"; +echo done. exit 5 else echo done. Perhaps it should trap ERR and INT and rollback to $TEMPFILE in the face of *any* problem. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iptables depends on: ii libc6 2.13-6 Embedded GNU C Library: Shared lib ii libnfnetlink0 1.0.0-1Netfilter netlink library iptables recommends no packages. iptables suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#628476: Package does not seem to work at all
Jakub Wilk wrote: > tags 628476 + confirmed upstream fixed-upstream thanks > > * Florian Weimer , 2011-05-29, 12:59: > >The documentation mentions importing wordaxe.DCWHyphenator. But this > >does not work: > > > >fw@deneb:~$ python > >Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48) > >[GCC 4.4.5] on linux2 > >Type "help", "copyright", "credits" or "license" for more information. > import wordaxe.DCWHyphenator > >/usr/lib/pymodules/python2.6/wordaxe/DCWHyphenator.py:12: > >DeprecationWarning: the sets module is deprecated > > import sets > >Traceback (most recent call last): > > File "", line 1, in > > File "/usr/lib/pymodules/python2.6/wordaxe/DCWHyphenator.py", line 26, in > > > > import wordaxe.dict.DEhyph as DEhyph > >ImportError: No module named dict.DEhyph > > Indeed, the module in question is available in the upstream tarball, > but it's not installed due to a bug in setup.py. This appears to be > fixed in 1.0.1. > > Please note however that DCWHyphenator is only one of the available > hyphenators; you might have better luck with others. FYI: Probably my end goal was/is to get hyphenation in rst2pdf output, and I distilled the above from whatever it was doing. It wouldn't surprise me if rst2pdf was hard-coded to use a german hyphenator, though what *I* actually want to hyphenate is English prose. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645286: Can't send mail from long cron jobs.
Package: msmtp-mta Version: 1.4.24-2 Severity: important Consider the following scenario: msmtp-mta is installed and configured to relay mail to a postfix smarthost at smtp., which accepts it. Thus, cron can demonstrably send mail, e.g. with a job "@hourly echo foo". Now, suppose there is a backup program that is invoked from /etc/cron.daily. For simplicity, let it be this simple example: #!/bin/sh echo "I had a recoverable error!" sleep 1h Now, what happens is this: 1. cron runs run-parts, which runs the backup script 2. as soon as cron sees some output, it runs msmtp, and provides it with the headers. It leaves the pipe open, because the job hasn't finished and there might be more output. 3. msmtp opens the connection to postfix *as soon as it receives all the headers*, and then leaves that connection open while it waits for the rest of the body. 4. postfix closes the idle connection after less than an hour. The end result is, mail from cron is lost. Here is what syslog reports when this happens: flora msmtp: host=smtp tls=off auth=off from=root recipients=root smtpstatus=421 smtpmsg='421 4.4.2 stomp.cyber.com.au Error: timeout exceeded' errormsg='the server did not accept the mail' exitcode=EX_UNAVAILABLE flora CRON: (root) MAIL (mailed 44 bytes of output but got status 0x0045#012) For now, I am working around it as follows, but this feels like a dirty hack, and it's a pain to have to do it on all my hosts. # dpkg-divert --rename /usr/sbin/sendmail # cat >/usr/sbin/sendmail <<-EOF #!/bin/bash -e ## Workaround long cron jobs being discarded because ## msmtp opens the connection as soon as the headers finish, ## resulting in stomp/postfix timing out the connection. f="`mktemp -t sendmail.XX`" trap "rm -f \"$f\"" 0 TERM INT QUIT cat >"$f" exec /usr/sbin/sendmail.distrib "$@" <"$f" EOF # chmod +x /usr/sbin/sendmail A better solution, I think, would be to have the option of telling msmtp not to open a connection to the smarthost until it receives an EOF from stdin. I could then set it in my /etc/msmtprc and be happy. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages msmtp-mta depends on: ii msmtp 1.4.24-2 msmtp-mta recommends no packages. msmtp-mta suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#635772: [ha...@afaics.de: Bug#635772: mg should not touch modification date of the backup]
tag 635772 + wontfix thank you Han Boetes wrote: > As stated in the source code: > > /* > * Make a backup copy of "fname". On Unix the backup has the same > * name as the original file, with a "~" on the end; this seems to > * be newest of the new-speak. The error handling is all in "file.c". > * We do a copy instead of a rename since otherwise another process > * with an open fd will get the backup, not the new file. This is > * a problem when using mg with things like crontab and vipw. > */ > > This is for security reasons. If you know a decent workaround > please let me know. Upstream has spoken, and I won't make Debian mg different from upstream mg in this respect. If you want to debate it, you can talk to the OpenBSD people, but I doubt you'll get anywhere :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641270: aptitude segfault in qemu-arm-static.
Package: qemu-user-static Version: 0.15.0~rc2+dfsg-1 Severity: normal File: /usr/bin/qemu-arm-static I did this: mkdir -p target/usr/bin cp /usr/bin/qemu-arm-static target/usr/bin cdebootstrap -f minimal -k /etc/debmirror/trustedkeys.gpg -a armhf unstable target http://apt/debian-ports Where http://apt/debian-ports is a partial mirror of debian-ports.org, made today. When this finished, I chrooted in and installed aptitude. Running aptitude --help works, but aptitude -u clears the screen then prints Segmentation fault And aptitude (without arguments) was printing something different about the stack being uninitialized or something, but now it's also printing "Segmentation fault". I tried stracing it, but strace says that ptrace isn't supported by qemu-user-static. Ref. http://wiki.debian.org/QemuUserEmulation -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash qemu-user-static depends on no packages. Versions of packages qemu-user-static recommends: ii binfmt-support2.0.6 Support for extra binary formats Versions of packages qemu-user-static suggests: ii sudo 1.7.4p6-1 Provide limited super user privile -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641270: Acknowledgement (aptitude segfault in qemu-arm-static.)
Here's another one: (bootstrap)root@twb:~# git clone git://github.com/lilstevie/CrOS-Hybrid-Kernel.git Cloning into CrOS-Hybrid-Kernel... *** longjmp causes uninitialized stack frame ***: /usr/bin/qemu-arm-static terminated === Backtrace: = [0x600d6395] [0x600d6329] [0x600d6293] [0x6002ee60] [0x6001f2f8] [0x600184cd] [0x6008e400] [0x6037f69d] === Memory map: ^C^C^C^C^Z [1]+ Stopped git clone git://github.com/lilstevie/CrOS-Hybrid-Kernel.git (bootstrap)root@twb:~# kill -9 %1 [1]+ Stopped git clone git://github.com/lilstevie/CrOS-Hybrid-Kernel.git (bootstrap)root@twb:~# [1]+ Killed git clone git://github.com/lilstevie/CrOS-Hybrid-Kernel.git (bootstrap)root@twb:~# exit root@twb:~# qemu-arm-static --version | head -1 qemu-arm version 0.14.92 (Debian 0.15.0~rc2+dfsg-1), Copyright (c) 2003-2008 Fabrice Bellard Because it was on faster hardware, I also tried copying that sid armhf rootfs onto an Ubuntu Lucid system, with similar results root@lucid:~/twb-abuse# chroot squashfs-root/ # NOTE: at this point, sid's qemu-arm-static is in the chroot's usr/bin/ (bootstrap)root@lucid:/# cd root (bootstrap)root@lucid:~# export LC_ALL=C (bootstrap)root@lucid:~# git clone git://github.com/lilstevie/CrOS-Hybrid-Kernel.git Cloning into CrOS-Hybrid-Kernel... Segmentation fault (bootstrap)root@lucid:~# exit root@lucid:~/twb-abuse# cp -b /usr/bin/qemu-arm-static squashfs-root/usr/bin/# now it has lucid's qemu root@lucid:~/twb-abuse# chroot squashfs-root qemu: fatal: cp15 insn ee1d7f70 R00=4009f958 R01=0d696914 R02=000190e0 R03=00018e00 R04=42082988 R05=00021106 R06=420829a8 R07= R08= R09=000ae62c R10=4009f000 R11= R12=000ae62c R13=4007f450 R14=4008f538 R15=4008b116 PSR=2030 --C- T usr32 ^C^C^C^Z # at this point I had to kill -9 the qemu process. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642349: Please put cache in ~/.cache
Josh Triplett wrote: > Darcs seems to store a cache in ~/.darcs/cache . Please consider moving > this to a darcs subdirectory in the common ~/.cache directory. As a short-term workaround, you can manually make .darcs/cache a symlink to .cache/darcs; Darcs will honour this. You can also specify different/additional cache locations in .darcs/sources. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643306: Don't ask about GRUB2 when it isn't used.
Package: kexec-tools Version: 1:2.0.2-2 Severity: minor On upgrading to current sid version as at today, kexec-tools asked If you choose this option, kexec will read grub2 config file to determine which kernel and options to load for kexec reboot, as opposed to what is in /etc/default/kexec. This is a silly question as grub isn't installed and /boot contains no mention of anything remotely grub related. IMO it shouldn't prompt me unless it looks like grub is installed. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kexec-tools depends on: ii debconf [debconf-2.0] 1.5.40 ii libc6 2.13-21 kexec-tools recommends no packages. kexec-tools suggests no packages. -- debconf information: * kexec-tools/load_kexec: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643311: secure_defaults affects BOTH sudo -i and sudo -iufred
Package: sudo Version: 1.8.2-1 Severity: important This issue may tie in with the change that closed #85123 and #85917 and opened #639841. Once upon a time, I ran "su -", and it gave me a clean root login shell, with /sbin and /usr/sbin in its path. Then I switched to "sudo su -" or "sudo -H -s". Then I switched to "sudo -i", which was best, because it gave the same environment as "su -", but without having to use su. Now, when I run "sudo -i", I get the original user's $PATH. My immediate reaction is "that's broken", but OK, I will try to do the recommended change to sudoers: -Defaults env_reset +Defaults env_reset, secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" But this is definitely wrong: $ sudo -i root@dali:~# echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin root@dali:~# logout $ sudo -i -u fred fred@dali:~$ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin So what am I supposed to do about this? sudoers revolves around the user you're switching *from*, not the user you're switching *to*. AFAICT I need to do something like this: Defaults env_reset -root ALL=(ALL:ALL) NOPASSWD:ALL +root ALL=(root:ALL) SECURE_PATH:"..." NOPASSWD:ALL +root ALL=(ALL:ALL) NOPASSWD:ALL -%sudo ALL=(ALL:ALL) NOPASSWD:ALL +%sudo ALL=(root:ALL) SECURE_PATH:"..." NOPASSWD:ALL +%sudo ALL=(ALL:ALL) NOPASSWD:ALL This doubling is fugly and verbose, but might just fly for such a simple ruleset. But at work I have a couple dozen LDAP sudoRole objects, and maintaining another dozen almost identical ones will be a pain in the arse. Now, I suspect this is not sudo's fault -- that the change in sudo has just happened to expose some other misconfiguration in my system. Specifically I think that /etc/profile doesn't set $PATH anymore (it expects pam to), and PAM isn't doing so in this case for some reason. OK, fine, whatever. I don't care which component is misconfigured here, I just want to "sudo -i" to DWIM and not have to go back to "sudo su -" to get a "real" login environment. PS: sorry if I sound really grumpy above, this just bit me unexpectedly because apt-listchanges didn't warn me. $ sudo egrep -v '^(#|$)' /etc/sudoers /etc/profile /etc/environment /etc/login.defs /etc/sudoers:Defaults env_reset /etc/sudoers:Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" /etc/sudoers:root ALL=(ALL:ALL) NOPASSWD:ALL /etc/sudoers:%sudo ALL=(ALL:ALL) NOPASSWD:ALL /etc/profile:if [ "$PS1" ]; then /etc/profile: if [ "$BASH" ]; then /etc/profile:# The file bash.bashrc already sets the default PS1. /etc/profile:# PS1='\h:\w\$ ' /etc/profile:if [ -f /etc/bash.bashrc ]; then /etc/profile: . /etc/bash.bashrc /etc/profile:fi /etc/profile: else /etc/profile:if [ "`id -u`" -eq 0 ]; then /etc/profile: PS1='# ' /etc/profile:else /etc/profile: PS1='$ ' /etc/profile:fi /etc/profile: fi /etc/profile:fi /etc/profile:umask 022 /etc/login.defs:MAIL_DIR/var/mail /etc/login.defs:FAILLOG_ENAByes /etc/login.defs:LOG_UNKFAIL_ENABno /etc/login.defs:LOG_OK_LOGINS no /etc/login.defs:SYSLOG_SU_ENAB yes /etc/login.defs:SYSLOG_SG_ENAB yes /etc/login.defs:FTMP_FILE /var/log/btmp /etc/login.defs:SU_NAME su /etc/login.defs:HUSHLOGIN_FILE .hushlogin /etc/login.defs:ENV_SUPATH PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /etc/login.defs:ENV_PATH PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games /etc/login.defs:TTYGROUPtty /etc/login.defs:TTYPERM 0600 /etc/login.defs:ERASECHAR 0177 /etc/login.defs:KILLCHAR025 /etc/login.defs:UMASK 022 /etc/login.defs:PASS_MAX_DAYS 9 /etc/login.defs:PASS_MIN_DAYS 0 /etc/login.defs:PASS_WARN_AGE 7 /etc/login.defs:UID_MIN 1000 /etc/login.defs:UID_MAX 6 /etc/login.defs:GID_MIN 1000 /etc/login.defs:GID_MAX 6 /etc/login.defs:LOGIN_RETRIES 5 /etc/login.defs:LOGIN_TIMEOUT 60 /etc/login.defs:CHFN_RESTRICT rwh /etc/login.defs:DEFAULT_HOMEyes /etc/login.defs:USERGROUPS_ENAB yes -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sudo depends on: ii libc6 2.13-21 ii libpam-modules 1.1.3-4 ii libpam0g1.1.3-2 sudo recommends no packages. sudo suggests no packages. -- Configuration Files: /etc/sudoers [Errno 13] Permission denied: u'/etc/sudoers' /etc/sudoers.d/README [Errno 13] Permission denied: u'/etc/sud
Bug#643321: no bt after upgrade (4.94-2 -> 4.96-1)
Package: bluez Version: 4.96-1 Severity: important After a large dist-upgrade today, typing on bluetooth keyboard had no effect. Initial investigation follows. Please advise how to proceed. The relevant bluez upgrades were as follows. The kernel was not upgraded; it is 2.6.38-2-amd64. dbus was not upgraded; it is 1.5.6-1. 2011-09-27 16:28:07 upgrade bluez 4.94-2 4.96-1 2011-09-27 17:54:29 upgrade libbluetooth3 4.94-2 4.96-1 2011-09-27 12:53:40 upgrade python-dbus 0.84.0-1 0.84.0-2 2011-09-27 17:54:50 upgrade libdbus-glib-1-2 0.94-4 0.96-1 The keyboard was configured as described in the ticket below; it is the same keyboard. I do not use bluetooth for anything else. http://bugs.debian.org/599894 Re-doing that process no longer works: # hcitool scan Device is not available: No such device # hcitool dev Devices: # hcitool -i hci0 scan Invalid device: Network is down # rfkill list bluetooth 1: eeepc-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 3: hci0: Bluetooth Soft blocked: no Hard blocked: no # lsusb -vs 005:002 | head -20 Bus 005 Device 002: ID 0b05:1788 ASUSTek Computer, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize064 idVendor 0x0b05 ASUSTek Computer, Inc. idProduct 0x1788 bcdDevice4.49 iManufacturer 1 Broadcom Corp iProduct2 BT-270 iSerial 3 1C4BD605DE97 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bluez depends on: ii dbus 1.5.6-1 ii libbluetooth3 4.96-1 ii libc6 2.13-21 ii libcap-ng0 0.6.6-1 ii libdbus-1-31.5.6-1 ii libglib2.0-0 2.28.6-1 ii libreadline6 6.2-4 ii libudev0 172-1 ii libusb-0.1-4 2:0.1.12-19 ii lsb-base 3.2-28 ii module-init-tools 3.16-1 ii python-dbus0.84.0-2 ii python-gobject 2.28.6-5 ii udev 172-1 bluez recommends no packages. bluez suggests no packages. -- Configuration Files: /etc/dbus-1/system.d/bluetooth.conf [Errno 2] No such file or directory: u'/etc/dbus-1/system.d/bluetooth.conf' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643321: Acknowledgement (no bt after upgrade (4.94-2 -> 4.96-1))
PS: looking through the logs, I found /var/log/apt/term.log contained this: Unpacking replacement cron ... Preparing to replace bluez 4.94-2 (using .../bluez_4.96-1_amd64.deb) ... Stopping bluetooth: /usr/sbin/bluetoothd. dpkg: warning: version 'bluez' has bad syntax: version number does not start with digit Unpacking replacement bluez ... Preparing to replace udev 171-3 (using .../archives/udev_172-1_amd64.deb) ... Unpacking replacement udev ... This appears to relate to /var/lib/dpkg/info/bluez.preinst: ... if dpkg-maintscript-helper supports mv_conffile; then dpkg-maintscript-helper mv_conffile \ /etc/dbus-1/system.d/bluetooth.conf 3.7-1 bluez -- "$@" ... Based on the second call in that file, you have forgotten the mv destination. I don't know if this has any bearing on the symptoms I'm seeing, but # ls /etc/dbus-1/system.d/ bluetooth.conf.dpkg-remove org.debian.AptXapianIndex.conf wpa_supplicant.conf Attempting to move it back didn't help: # mv /etc/dbus-1/system.d/bluetooth.conf.dpkg-remove /etc/dbus-1/system.d/bluetooth.conf # /etc/init.d/dbus start Starting system message bus: dbus. # hcitool scan Device is not available: No such device -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#643321: Acknowledgement (no bt after upgrade (4.94-2 -> 4.96-1))
OK, yes, that mv_conffile fuckup is the cause of this problem. Moving it back *and* restarting dbus and bluetooth daemons fixed it. I didn't realize at first that hcitool talked to the daemon; its manpage gave me the impression that it talked directly to the devices; that the bluetooth daemon was merely some higher-level thing. It might be useful to mention in the manpages that bluetoothd *needs* a system dbus to do anything at all, and likewise hcitool *needs* bluetoothd. It might also be useful for "hcitool scan" to report something like along the lines of "I can't see bluetoothd" rather than "no devices found". # logread -f & [1] 2717 # /etc/init.d/bluetooth restart Stopping bluetooth: /usr/sbin/bluetoothd. Starting bluetooth: bluetoothd. # Sep 27 19:02:21 dali daemon.info bluetoothd[2729]: Bluetooth daemon 4.96 Sep 27 19:02:21 dali daemon.err bluetoothd[2729]: Unable to get on D-Bus # /etc/init.d/dbus start system message bus already started; not starting.. # /etc/init.d/dbus restart Stopping system message bus: dbus. Starting system message bus: dbus. # mv /etc/dbus-1/system.d/bluetooth.conf.dpkg-remove /etc/dbus-1/system.d/bluetooth.conf # Sep 27 19:02:54 dali daemon.notice dbus[2746]: [system] Reloaded configuration /etc/init.d/bluetooth restart Stopping bluetooth: /usr/sbin/bluetoothd. Starting bluetooth: bluetoothd. # Sep 27 19:03:03 dali daemon.info bluetoothd[2763]: Bluetooth daemon 4.96 Sep 27 19:03:03 dali daemon.info bluetoothd[2763]: Starting SDP server Sep 27 19:03:03 dali daemon.err bluetoothd[2763]: D-Bus failed to register org.bluez.Proximity interface Sep 27 19:03:03 dali user.info kernel: [ 1830.878025] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Sep 27 19:03:03 dali user.info kernel: [ 1830.878038] Bluetooth: BNEP filters: protocol multicast Sep 27 19:03:03 dali daemon.info bluetoothd[2763]: Listening for HCI events on hci0 Sep 27 19:03:03 dali user.info kernel: [ 1830.900768] Bluetooth: SCO (Voice Link) ver 0.6 Sep 27 19:03:03 dali user.info kernel: [ 1830.900780] Bluetooth: SCO socket layer initialized Sep 27 19:03:03 dali daemon.info bluetoothd[2763]: HCI dev 0 up Sep 27 19:03:03 dali daemon.info bluetoothd[2763]: Adapter /org/bluez/2763/hci0 has been enabled # hcitool scan Scanning ... # Sep 27 19:03:48 dali user.info kernel: [ 1875.994795] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Sep 27 19:03:48 dali user.info kernel: [ 1876.009182] input: Apple Wireless Keyboard as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.0/bluetooth/hci0/hci0:11/input12 Sep 27 19:03:48 dali user.info kernel: [ 1876.009901] apple 0005:05AC:0239.0001: input,hidraw0: BLUETOOTH HID v0.50 Keyboard [Apple Wireless Keyboard] on 1C:4B:D6:05:DE:97 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#637365: Also affects fbi
Package: fbi Version: 2.07-8 Followup-For: Bug #637365 After an overdue dist-upgrade, this issue affects me in fbi. That is, fbi -e foo.jpg, hit l, and it segfaults. 2011-09-27 15:13:43 upgrade fbi 2.07-7 2.07-8 -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fbi depends on: ii ghostscript 9.02~dfsg-3 ii libc62.13-21 ii libcurl3-gnutls 7.21.7-3 ii libexif120.6.20-1 ii libfontconfig1 2.8.0-3 ii libfreetype6 2.4.6-2 ii libgif4 4.1.6-9 ii libjpeg8 8c-2 ii libpng12-0 1.2.46-3 ii libtiff4 3.9.5-2 ii zlib1g 1:1.2.3.4.dfsg-3 fbi recommends no packages. Versions of packages fbi suggests: ii imagemagick 8:6.6.9.7-5+b1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#495163: useless static library due to libkrb5
Hannes von Haugwitz wrote: > What is the state of this bug? I would like to add curl support to > the aide pkg (which is statically linked). AFAIK, no change. If it were a private package, I'd advise you to reroll curl without kerberos support, so it can be statically linked into aide. To do that within Debian, I guess you'd need the curl maintainer to provide an alternative libcurl-static-dev or something. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674744: Wikipedia broke w3m-search-escape-query-string (+ vs. %20)
Tatsuya Kinoshita wrote: > Hi Trent, > > On May 27, 2012 at 6:46PM +1000, trentbuck (at gmail.com) wrote: > > Package: w3m-el-snapshot > > Version: 1.4.478+0.20120501-1 > > Around 15 July 2011, this stopped working properly. It turned out to > > be because Wikipedia started treating these links differently: > > > > https://en.wikipedia.org/wiki/Special:Search/foo+bar > > https://en.wikipedia.org/wiki/Special:Search/foo%20bar > > Do you still have a problem? > > Currently, foo+bar seems to work. I've been using this patch: ;;; Guerilla patch -- http://bugs.debian.org/674744 (eval-after-load "w3m-search" '(defun w3m-search-escape-query-string (str &optional coding) (mapconcat (lambda (s) (w3m-url-encode-string s (or coding w3m-default-coding-system))) (split-string str) "%20"))) Although now I look at it, this is simpler: (eval-after-load "w3m-search" '(defun w3m-search-escape-query-string (str &optional coding) (w3m-url-encode-string str (or coding w3m-default-coding-system Wikipedia *does* give diffrent results for .../foo+bar and .../foo bar (encoded as %20 or not). The former has no exact match, so it goes to a results page, the latter goes to a specific article. Do any search engines need "+" instead of " "? If not, maybe this function should not bother to split and rejoin. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#720134: Missing but documented option: --monochrome
Package: netrik Version: 1.16.1-1.1 Severity: minor I was looking at alternatives to lynx --dump to turn text/plain into text/html. The manpage describes using TERM=ansi, but since I didn't want *any* escape sequences, I tried TERM=dumb. That tells me to pass --monochrome, but netrik doesn't accept --monochrome. $ date >x $ TERM=dumb netrik --monochrome --dump x netrik: unrecognized option '--monochrome' Can't get color capabilities -- starting in monochrome mode. If this is what you want, use --monochrome option to suppress this warning. Otherwise, please check your $TERM environment variable. (See README for details.) Press to continue. Monday 19 August 14:16:09 EST 2013 $ -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages netrik depends on: ii libc6 2.17-92 ii libncursesw5 5.9+20130608-1 ii libreadline6 6.2+dfsg-0.1 ii libtinfo5 5.9+20130608-1 netrik recommends no packages. netrik suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#635093: GTK3 Adwaita - gtk3-demo segfaults without notebook tab style.
Package: gnome-themes-standard
Version: 3.0.2-1
Severity: important
File: /usr/lib/gtk-3.0/3.0.0/theming-engines/libadwaita.so
With the following ~/.config/gtk-3.0/gtk.css, gtk3-demo segfaults on start:
* { engine: adwaita; }
This gtk.css doesn't cause a segfault:
* { engine: adwaita; }
.notebook tab:active { -adwaita-border-gradient: -gtk-gradient (linear,
left top, left bottom, from (#f00), to (#0f0)); }
I take this to mean that libadwaita.so is broken somehow; I *assume*
one should be able to simply specify a theme engine without segfaults.
If you can't reproduce this, I can provide strace and suchlike on
request.
Note that I am not running GNOME or settings daemons or anything, just
"xinit /usr/bin/xterm" and running gtk3-demo from that xterm's shell.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gnome-themes-standard depends on:
ii gconf22.32.4-1 GNOME configuration database syste
ii libatk1.0-0 2.0.1-2ATK accessibility toolkit
ii libc6 2.13-10Embedded GNU C Library: Shared lib
ii libcairo-gobject2 1.10.2-6 The Cairo 2D vector graphics libra
ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra
ii libfontconfig12.8.0-3generic font configuration library
ii libfreetype6 2.4.4-1FreeType 2 font engine, shared lib
ii libgdk-pixbuf2.0-02.23.3-3 GDK Pixbuf library
ii libglib2.0-0 2.28.6-1 The GLib library of C routines
ii libgtk-3-03.0.11-1 GTK+ graphical user interface libr
ii libpango1.0-0 1.28.3-6 Layout and rendering of internatio
Versions of packages gnome-themes-standard recommends:
ii gtk2-engines 1:2.20.1-1 theme engines for GTK+ 2.x
gnome-themes-standard suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#714235: Allow not sending Accept, Accept-Encoding, Accept-Language headers
Package: w3m Version: 0.5.3-8 Severity: wishlist I was reading http://panopticlick,eff.org and I see that it looks at Accept headers to help "fingerprint" a user. I thought: the simplest thing was to turn off those headers, since I don't rely on them AFAIK. It looks like I can't in w3m -- url.c:1294 will ALWAYS send SOMETHING, and rc.c:1203 explicitly forbids sending the empty string. Is this a reasonable thing to ask for? I used to use polipo to remove my User-Agent header as well, until Wikipedia refused to return content if no User-Agent was sent :-/ -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.9-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages w3m depends on: ii libc62.17-3 ii libgc1c2 1:7.1-9.1 ii libgpm2 1.20.4-6 ii libssl1.0.0 1.0.1e-3 ii libtinfo55.9+20130608-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages w3m recommends: ii ca-certificates 20130610 Versions of packages w3m suggests: ii man-db2.6.3-7 pn menu pn migemo ii mime-support 3.54 ii w3m-el-snapshot [w3m-el] 1.4.513+0.20130419-1 pn w3m-img -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#353980: fortune-mod: Fortune invocation by relative path broken in two different ways.
Andrea, Andrea Colangelo wrote: > I wasn't able to reproduce this bug: [...] I can still reproduce this issue as at fortune-mod 1:1.99.1-6, but only for the trailing slash case. $ with-temp-dir with-temp-dir: entering directory `/tmp/with-temp-dir.J22eEB' This directory will be deleted when you exit. $ echo Success! >x $ strfile -s x $ fortune x Success! $ fortune . Success! $ fortune ./ ./: No such file or directory ./: No such file or directory Success! $ fortune $PWD Success! $ mkdir y $ cd y $ fortune .. Success! $ fortune ../ ../: No such file or directory ../: No such file or directory Success! $ cd /tmp $ fortune with-temp-dir.J22eEB Success! $ fortune with-temp-dir.J22eEB/ Success! $ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#662765: RFP: MARS (Core Wars / corewars) -- Memory Array Redcode Simulator
Package: wnpp Severity: wishlist * Package name: mars Version : not sure Upstream Author : not sure * URL : http://corewar.co.uk/mars.htm https://en.wikipedia.org/wiki/Core_War * License : not sure Programming Lang: C Description : Memory Array Redcode Simulator A while back there was a package in Debian called "corewars", where assembly programs battled to control an VM's memory. It looks like it was removed because it depends on GTK1 (not GTK2). I was interested to actually get around to trying it, but I'm not quite interested enough to bother compiling / packaging it myself. It looks like there is a reference simulator posted on usenet, written in C, and a bunch of different simulators that were subsequently derived from or inspired by the reference implementation. I haven't investigated which one should be packaged, or if any are DSFG-licensed. If none are, I guess this ticket can be updated to reflect that and at least it'll be in wnpp-check next time I remember corewars. The above links include a list of implementations. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#647600: PS1=\\W reports "pocc" for /proc
Package: bash Version: 4.1-3 Severity: minor File: /bin/bash I noticed a strange thing on my laptop: root@dali:~# PS1=\\W ~cd /proc pocc For some reason the \W of /proc is reported as "pocc"; \w is reported correctly (as "/proc") and other paths (e.g. /usr) are reported correctly. This behaviour is reproducible both as my user (who has dotfiles) and as root (who has none). I can't reproduce this on a similarly configured KVM VM that is running mostly wheezy, whereas my laptop is mostly sid. I have no idea what's going on, but I'm very curious. Can you suggest any diagnostics I can try? If not, I suppose just tag + moreinfo and close/wontfix. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bash depends on: ii base-files 6.5 ii dash 0.5.7-2 ii debianutils 4.0.4 ii libc62.13-21 ii libncurses5 5.9-2 Versions of packages bash recommends: ii bash-completion 1:1.3-1 Versions of packages bash suggests: pn bash-doc -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645286: Patch dropped
Martin, Martin Lambers wrote: >> Hi Trent, >> >> The latest git version of msmtp adds a 'buffer_mail' command and >> '--buffer-mail' option which tells msmtp to first buffer the complete >> mail in a temporary file before sending it. >> >> Can you test if this works for you? > > Since there was no reaction to the proposed patch in almost 4 > weeks (neither here nor on the msmtp-users mailing list), I conclude > that this issue is not important. To avoid adding useless bloat > that nobody uses anyway, I dropped the patch and released 1.4.26 > without it. For whatever reason[*] I didn't get these emails. The issue *is* important to me, but I have a working (if icky) workaround, and in production I'm mainly using Ubuntu LTS releases, so my deadline is April 2012 or 2014, rather than this week/month :-) My TODO list now has an entry to test your patch. I expect to get to that sometime this month (Dec 2011). Sorry about the lack of communication! [*] 12:25 twb: best be subscribing to those next time. ;) 12:25 [SpamapS always forgets to subscribe to the bugs he files in Debian] 12:25 It ought to have subscribed me automagically to the one I filed, surely? 12:25 twb: no, Debian's BTS does not subscribe you to bugs you file 12:26 OH 12:26 So it's just normally people hit group reply 12:26 exactly -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#641270: aptitude segfault in qemu-arm-static.
Vagrant Cascadian wrote: > Version: 1.0+dfsg-1 > > On Mon, Sep 12, 2011 at 07:18:40PM +1000, Trent W. Buck wrote: > > Package: qemu-user-static > > Version: 0.15.0~rc2+dfsg-1 > > Severity: normal > > File: /usr/bin/qemu-arm-static > > > > I did this: > > > > mkdir -p target/usr/bin > > cp /usr/bin/qemu-arm-static target/usr/bin > > cdebootstrap -f minimal -k /etc/debmirror/trustedkeys.gpg -a armhf > > unstable target http://apt/debian-ports > > > > Where http://apt/debian-ports is a partial mirror of debian-ports.org, made > > today. > > > > When this finished, I chrooted in and installed aptitude. Running > > aptitude --help works, but aptitude -u clears the screen then prints > > > > Segmentation fault > > apparently, armhf is at least reasonably well supported now(maybe it always > was), and so i tested with aptitude 0.6.4-1.2+b1 in an armhf sid chroot. > > i was able to reproduce this behavior with qemu-user-static 0.15.1+dfsg-3, but > not with qemu-user-static 1.0+dfsg-1, so it appears to be fixed in newer > versions. Sorry, I forgot all about this ticket. I don't remember if I said so when I reported this, but (assuming I'm remembering the right bug) it turned out to be something about qemu not zeroing memory before handing it out to the guest process or something. Someone on #kvm or #qemu gave me a short (~dozen lines) patch that I applied to debian's qemu source package, and after doing that I compiled a qemu-arm-static binary that didn't exhibit this behaviour. Sorry for dropping the ball on this one. Fortunately it looks like the chap from IRC pushed the patch into upstream, since Vagrant indicates it has trickled down to Debian in the current version :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#654674: vim-tiny incompatible with vim-common's mailcap
Package: vim-common Version: 2:7.3.363-1 Severity: minor File: /usr/lib/mime/packages/vim-common After installing vim-tiny, $ compose /tmp/tmp.c sh: 1: vim: not found Warning: program returned non-zero exit code #127 This is because vim-tiny provides "vi" but not "vim", and vim-common claims the latter can edit text/* files. I think either vim-tiny should provide an alternative for /usr/bin/vim, or the mailcap should refer to vi instead of vim. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vim-common depends on: ii libc6 2.13-23 Versions of packages vim-common recommends: ii vim-tiny 2:7.3.363-1 vim-common suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645286: fix works
I applied 5629fba80b05cc906c45e62c397d18e5afa18636 to wheezy's 1.4.25-2 and the resulting binary fixed the problems I was having, when run with buffer_mail=on in ~/.msmtprc. (Without buffer_mail=on, the problem came back, so the test is sound.) So, if it's not too much trouble, I would like this functionality to be maintained in new releases of msmtp. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
