Bug#1056147: midge possibly contains non-DFSG-free examples

Control: tag -1 patch I have now uploaded a possible repackaged .orig.tar.bz2: http://users.am-1.org/~ivan/src/sfn.2xNKGoveuNoRGASEQosuADUES3vYQfQmWVeMuitdtLI.tar.bz2 It was produced with the following shell command (where 39 blocks starting with 180 cover the entirety

Bug#1056146: xsok possibly contains non-DFSG-free data files

Source: xsok Version: 1.02-19 Severity: serious Justification: possible DFSG violation [Please do not Cc: me, as I’m “on the list,” so to say, and I prefer to reserve my inbox for private communication only. I’d have set up Mail-Followup-To:, but there doesn’t seem

Bug#1056147: midge possibly contains non-DFSG-free examples

Source: midge Version: 0.2.41-4 Severity: serious Justification: possible DFSG violation [Please do not Cc: me, as I’m “on the list,” so to say, and I prefer to reserve my inbox for private communication only. I’d have set up Mail-Followup-To:, but there doesn’t seem

Bug#672808: aylet: couldn't open sound device.

severity 672808 normal thanks Dmitry Semyonov linu...@gmail.com writes: Package: aylet Version: 0.5-3 Severity: important aylet is compiled to use OSS driver, and it seems OSS compatibility layer is not installed by default in Debian Wheezy. As a workaround, one can install alsa-oss

Bug#510051: Control keys do not work when aylet is started via xargs

Krystian Wlosek kwlo...@gmail.com writes: tags 510051 wontfix thanks Use command similar to the following to reproduce: echo AgentX.ay AgentX2.ay |xargs aylet JFTR, using xargs(1) with an interactive program doesn’t seem like a very clever idea, for with the number of

Bug#714557: emacs-jabber: conference messages aren't recorded in the history

Package: emacs-jabber Version: 0.8.0-3 Somewhat counter-intuitively, emacs-jabber’s “history” facility (:group 'jabber-history, (jabber) Message history) doesn’t record messages sent to or received via XMPP conferences (MUCs.) The incoming conference messages

Re: Packages removing alternatives on upgrade

Jakub Wilk jw...@debian.org writes: [Cross-posting to packages@qa, for elvis is maintained by the QA group.] Many packages remove alternatives on upgrade, only to re-add them later, potentially discarding manual choices of the user. See also bug #71621. […] Debian QA

Bug#594134: metastore(1) -f option's argument isn't handled properly

Package: metastore Version: 1+20080623+debian-1 Apparently, the command's ‘-f’ option's argument isn't handled properly: $ command time metastore -sf FILE -- . Failed to open (null): Bad address Command exited with non-zero status 1 … $ command time metastore -s -f FILE -- .