Bug#1037450: procps: [pgrep] [regression]: >15 characters warning when long regex doesn't match

Craig Small schrob: > I'm thinking of adding a quick and dirty check for a regex. A very quick > set of characters to say "this is a regex" and suppress the warning. > The first idea is just look for a '[' or a '|'. I think that covers most > simple conditions. I'm not looking for some sort odd

Bug#1037450: procps: [pgrep] [regression]: >15 characters warning when long regex doesn't match

Package: procps Version: 2:4.0.3-1 Severity: normal Dear Maintainer, Bug #896062 has come back from the grave: | $ pgrep "something|otherthing" | pgrep: pattern that searches for process name longer than 15 characters will result in zero matches | Try `pgrep -f' option to match against the

Bug#1010173: workaround

Hi, for me, removing the commit graph cache with rm -r .git/objects/info/commit-graph{,s} and regenerating with git commit-graph write worked as well. See here https://lore.kernel.org/git/f50e74f0-9ffa-f4f2-4663-269801495...@github.com/ for confirmation that it's indeed just a cache, and

Bug#541473: exim4: Per-user smarthost settings

Package: exim4 Version: 4.94-8 Followup-For: Bug #541473 Hi, While Marc Haber gives reasons for not doing this in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750122#20 , I found the following: https://debianforum.de/forum/viewtopic.php?t=147183#p970884 | # Fix to use user specific

Bug#969722: ratpoison: Maybe clean up root window xprops after tmpwm?

Package: ratpoison Version: 1.4.9-1+b1 Severity: wishlist Dear Maintainer, When using ":tmpwm openbox", and subsequently quitting Openbox again, some root window X properties set by openbox remain: | $ xprop -root ; ratpoison -c 'tmpwm openbox' & sleep 2 ; killall openbox ; fg ; xprop -root |

Bug#964555: pal: please provide pal2ical and ical2pal binaries

Package: pal Version: 0.4.3-8.1+b5 Severity: wishlist Dear Maintainer, pal2ical and ical2pal from the "src/convert" directory are currently distributed as source in /usr/share/doc/pal/examples/ . I've found ical2pal extremely helpful in the past, and now have a use case for pal2ical as well.

Bug#963202: ssh: ExitOnForwardFailure and X forwarding

Package: openssh-client Version: 1:8.3p1-1 Severity: minor Dear Maintainer, The ExitOnForwardFailure ssh(1) option is apparently not considering a failed X forwarding: | user@host:~$ /usr/bin/ssh -X otheruser@localhost -o "exitonforwardfailure yes" | X11 forwarding request failed on channel 0 |

Bug#954342: aqbanking-tools: README.aqhbci-tool missing

Package: aqbanking-tools Version: 6.0.1-2 Severity: normal Dear Maintainer, The manpage for aqhbci-tool4(1) mentions: | The README file[1] contains the README which describes some setup | scenarios in detail. [...] | 1. The README file |

Bug#953942: RM: jack -- RoQA; python2-only; no new upstream code since 2005; better alternatives exist; blocking py2removal effort

Package: ftp.debian.org Followup-For: Bug #953942 Wow. Gone in 4 days. While I can understand that ftpmasters are triggerhappy due to the py2 removal, that seems excessive. As for the "no upstream activity", that tends to happen when software is feature-complete. And when claiming "better

Bug#930869: Don't release with buster

Package: pm-utils Followup-For: Bug #930869 pm-utils is now marked for autoremoval due to this frivolous RC bug. As another satisfied pm-utils user, this worries me. Would someone with more authority please downgrade/close this as invalid, or at least get Michael Biebl to to adress the questions

Bug#948522: If I rebuild src:file with libseccomp-dev installed, then "fakeroot file ..." crashes with "Bad system call"

Hi, I was just passing by and noticed this: Christoph Biedl schrob: > It might be an interesting topic whether "Not needed packages installed > in the build system trigger a build error" should be considered a bug - Yes, that's a bug. Ideally, building should succeed. Otherwise, there should be

Bug#942111: dpkg,debhelper: please set HOME, XDG_* to a temporary location during the build

Simon McVittie schrob: > Before Ubuntu switched from Upstart to systemd, they had a > standalone implementation of XDG_RUNTIME_DIR as a PAM module, which as far > as I'm aware is entirely init-system-agnostic: > https://launchpad.net/pam-xdg-support Heh, interesting. I wasn't aware of that,

Bug#942111: dpkg,debhelper: please set HOME, XDG_* to a temporary location during the build

Niels Thykier schrob: > Having debhelper support/do this will have no influence on whether init > or login systems will need to support it in the first place AFAICT. True. > The use case in debhelper is to setup an empty directory and point an > ENV variable at it to ensure we get a defined

Bug#942111: dpkg,debhelper: please set HOME, XDG_* to a temporary location during the build

Package: dpkg-dev,debhelper Followup-For: Bug #942111 Control: reopen 942111 Dear Maintainer, Sorry for being late to the party. Please reconsider the XDG_RUNTIME_DIR part of this change. XDG_RUNTIME_DIR is a systemd-ism, and due to the way it is specified, it's extremely unlikely to be

Bug#945464: /lib/init/init-d-script: stop action: missing --oknodo in s-s-d invocation

Hey, Guillem Jover schrob: > Actually, and this is something I've had pending raising for a long > time, I don't understand that two s-s-d invocations pattern in stop > which seems a bit pointless TBH? The --retry should make s-s-d wait > for the child to exit, or terminate it forcibly. I think

Bug#945464: /lib/init/init-d-script: stop action: missing --oknodo in s-s-d invocation

Package: sysvinit-utils Version: 2.96-1 Severity: serious Justification: Policy 9.3.2. Dear Maintainer, The /lib/init/init-d-script errorneously returns failure when asked to stop a non-running service: | $ sudo service kxd start ; echo $? | Starting key exchange daemon: kxd. | 0 | $ sudo

Bug#934500: dh-runit: permissions of supervise directory

Hi, Dmitry Bogatov schrob: > [2019-08-24 16:03] Jan Braun > > That means they'll get a conffile prompt if/whe the maintainer changes > > the run file. > > This can be solved in /lib/runit/invoke-run. Something like running > /etc/service/foo/run.pre before "run"

Bug#934500: dh-runit: permissions of supervise directory

Dmitry Bogatov schrob: > No, I did not consider this aspect. Thank you. > But since runscripts are conffiles, admin can add line > > chown -R trusted_user:0 /run/runit/supervise/foo > > into /etc/sv/foo/run, and they will be preserved during upgrade. Not > that staightforward, but still

Bug#934500: dh-runit: permissions of supervise directory

Source: dh-runit Followup-For: Bug #934500 Dear Maintainer, I'd like to point out that moving the supervise directories to /run means that they get wiped on reboot. Therefore the local admin can't persistently change their permissions, to give certain users additional rights. Personally, I see

Bug#933909: subdownloader: CLI broken

Mattia Rizzolo schrob: > Alas, it seems upstream stalled a bit, with no new commits for more than > a year :( Sorry to hear that. > Could I suggest you take this directly to upstream in > https://github.com/subdownloader/subdownloader/issues ? I'm sorry, I don't have a Github account and don't

Bug#933909: subdownloader: CLI broken

Package: subdownloader Version: 2.1.0~rc4-1 Severity: normal Dear Maintainer, I just tried the subdownloader version in experimental. Sadly, I couldn't get it to do anything useful. Previously, I would call subdownloader as | subdownloader -c --rename-subs -l en -V . , and it would

Bug#932624: mkchromecast: pidfile issues

Package: mkchromecast Version: 0.3.8.1-1 Severity: normal Dear Maintainer, mkchromecast always creates a pidfile a) in the fixed location /tmp/mkcchromecast.pid b) aborts if it can't write that file c) doesn't clean up the pidfile on exit.[1] This breaks the following use cases:

Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes

Package: apt Version: 1.8.2 Followup-For: Bug #879786 Dear Maintainer, I've had to spend far too much time to figure this out due the release yesterday. I'm running apt-get, and apt-get tells me nothing except | E: The repository 'http://security.debian.org testing/updates Release' no longer

Bug#915901: pastebinit: cxg.de stopped service

Package: pastebinit Version: 1.5-2 Severity: normal Dear Maintainer, http://cxg.de/ apparently has stopped providing service, it displays only a "buy this domain" ad. It should probably be removed from the "supported sites" list. Additionally, http://lpaste.net/ times out for me, you might want

Bug#912748: psmisc: killall doesn't handle long command names correctly anymore

Hey, Craig Small schrob: > I had a look at the specific part of killall and it already calculates > the length of process command names and given options so it was a simple > matter of adding an additional check. > [...] > $ src/killall alongnametestprocess > [1]+ Terminated

Bug#912748: psmisc: killall doesn't handle long command names correctly anymore

Craig Small schrob: > Hi Jan, > The issue is that the command name is increasing in length in the kernel. > So the utilities needed to increase their command name length as well. > > ps -o comm > > Would show you the field it's trying to match against and unless you have a > very recent

Bug#912748: psmisc: killall doesn't handle long command names correctly anymore

Package: psmisc Version: 23.2-1 Severity: normal control: notfound -1 23.1-1 Dear Maintainer, killall stopped handling long command names: | $ cat averylongcommandname | #!/bin/sh | sleep 1h | $ ./averylongcommandname & | [1] 25467 | $ killall -CONT averylongcommandname | averylongcommandname:

Bug#906435: /usr/bin/wine-development: wineserver: mkdir /run/user/1000/wine: No such file or directory

Package: wine-development Version: 3.13-3 Severity: important File: /usr/bin/wine-development Dear Maintainer, In wine-development 3.13-3 , wine fails to start for me with the following error message: | wineserver: mkdir /run/user/1000/wine: No such file or directory That's because /run/user

Bug#896062: pgrep: >15 characters warning when long regex doesn't match

Jan Braun schrob: > My solution/hack would probably be to just add a > > >&& (strchr(opt_pattern,'[') != NULL) Gah. That ought to be a == NULL. If the opt_pattern does not contain [ print the message.

Bug#896062: pgrep: >15 characters warning when long regex doesn't match

Package: procps Version: 2:3.3.14-1 Severity: normal Tags: upstream Dear Maintainer, I just upgraded procps from 2:3.3.12-4 to 2:3.3.14-1 and my scripting started to produce unexpected and (in my case) pointless messages on stderr, because apparently I like to do the following: | $ pgrep

Bug#875958: #875958 sa-compile: The package fails to run sa-compile

Hi, Fred de Brouwer schrob: > I ran into this problem as well and I found this way to get spamassassin > installed. > [...] > If the installation script creates the user with the "bash" - shell it might > solve this broken installation. So there's a bashism somewhere, and it needs to be fixed.

Bug#883381: neomutt interface to gpg broken

Package: neomutt Followup-For: Bug #883381 Control: fixed 883381 20171215+dfsg.1-1 I had the same issue with 20171027+dfsg.1-4 , but upgrading to 20171215+dfsg.1-1 fixed it for me. HTH, Jan -- Package-specific info: NeoMutt 20171215 Copyright (C) 1996-2016 Michael R. Elkins and others.

Bug#882159: Fw: Bug #882159: duply: occasionally shows negative runtimes

Hello, Joachim Wiedorn schrob: > Hello Jan, FYI: > original message > From: e...@users.sourceforge.net > Date: Sun, 26 Nov 2017 21:55:28 +0100 > To: Joachim Wiedorn , cont...@bugs.debian.org, > 882...@bugs.debian.org > > can the reporter maybe test the current

Bug#882159: duply: occasionally shows negative runtimes due to non-atomic timestamps

Package: duply Version: 2.0.3-1 Severity: minor Tags: upstream Dear Maintainer, Duply occasionally displays silly runtimes like the following: | --- Finished state OK at 00:14:15.001 - Runtime 00:00:00.-930 --- This is due to it taking start/stop timestamps by doing | RUN_START=$(date_fix

Bug#845758: espeak-ng: please provide espeak

Package: espeak-ng Version: 1.49.0+dfsg-2 Severity: wishlist Dear Maintainer, while I'm excited to see an active fork of espeak, I felt let down by the debian packaging: I'd like to switch from using espeak to espeak-ng, but I'll have to edit my scripts to append the -ng suffix everywhere. Or

Bug#823971: +1

control: retitle 823971 mutt: displays text/html raw instead of using mailcap Eduard Bloch schrob: > same here, the ability to read inline HTML parts without ugly > workarounds is really missed. There are two easy workarounds. The first is using "m". Quoting TFM, Table 9.7. Default Attachment

Bug#815162: xserver-xorg-legacy: completely broken (locks up input / xf86OpenConsole: Cannot open virtual console)

Control: unmerge -1 Control: severity -1 important Control: tag -1 - moreinfo Control: retitle -1 xserver-xorg-legacy: locks up input when used with neither libpam-systemd nor manual configuration Jan Braun schrob: > If you want to downgrade (and merge with #814313), I won't object, but >

Bug#815162: xserver-xorg-legacy: completely broken (locks up input / xf86OpenConsole: Cannot open virtual console)

Sven Joachim schrob: > You need to install libpam-systemd, or put "needs_root_rights = yes" in > /etc/X11/Xwrapper.config. Thanks, needs_root_rights=yes solves the issue. [systemd rant available on request] > See #814313 and #814394. If you want to downgrade (and merge with #814313), I won't

Bug#815162: xserver-xorg-legacy: completely broken (locks up input / xf86OpenConsole: Cannot open virtual console)

Package: xserver-xorg-legacy Version: 2:1.18.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, Starting X via "startx" somehow locks up the input system: my xsession starts up, but keyboard and trackpoint stop working (including ctrl-alt-f#, ctrl-alt-backspace). My

Bug#809617: qupzilla: SIGABRTs without libqt5xcbqpa5

Package: qupzilla Version: 1.8.9~dfsg1-1 Severity: serious Justification: Policy 3.5 Dear Maintainer, qupzilla fails to start for me: | $ qupzilla | Fatal: This application failed to start because it could not find or load the Qt platform plugin "xcb". | | Available platform plugins are:

Bug#801976: samba-common: dhclient hook fails if samba not installed

Package: samba-common Version: 2:4.1.17+dfsg-4 Severity: normal Tags: patch Dear Maintainer, On interface changes, I'm getting the following syslog message: | $DATE $HOSTNAME root: /etc/dhcp/dhclient-enter-hooks.d/samba returned non-zero exit status 1 It seems #414841 wasn't fixed properly:

Bug#792439: duply: Warning: Option --exclude-globbing-filelist is pending deprecation

Joachim Wiedorn schrob: now I have made a new package and tried to fix the bug which you have reported. This package is already in unstable, but in 5 days also in testing (I hope so). Please test this new package and send me a feedback. I did both an incremental and a full backup and a

Bug#792439: Warning: Option --exclude-globbing-filelist is pending deprecation

Package: duply Version: 1.9.1-1 Severity: minor Tags: upstream Forwarded: http://sourceforge.net/p/ftplicity/bugs/81/ Dear Maintainer, Duplicity is deprecating some options, including --exclude-globbing-filelist , which is used by duply. Therefore every invocation of duply currently prints |

Bug#788785: munge: logrotate errors if removed but not purged

Package: munge Version: 0.5.11-2 Severity: normal Tags: patch Dear Maintainer, with munge removed, but not purged, the initscript always exits with returncode 5, i.e. unsuccessfully. I think this is a Debian policy violation on its own, but in any case it causes weekly complaints from logrotate:

Bug#786503: cppcheck: Homepage URL 404s

Package: cppcheck Version: 1.69-1 Severity: minor Dear Maintainer, The cppcheck package has set the Homepage: field to http://cppcheck.wiki.sourceforge.net/ , which currently 404s for me: | $ wget --no-proxy cppcheck.wiki.sourceforge.net | --2015-05-22 12:57:18--

Bug#711031: /usr/bin/xdg-open: xdg-open does not use default application set with xdg-mime

retitle 711031 xdg-mime default should warn on unknown typ[eo]s severity 711031 wishlist thanks J. Eike von Seggern schrob: I changed the default application using xdg-mime. But xdg-open does not use this: % xdg-mime default ristretto.desktop images/png

Bug#729926: polipo: crashes due to syslog logging

Package: polipo Version: 1.0.4.1-4 Severity: grave Tags: patch Justification: renders package (mostly) unusable Polipo crashes after few minutes of browsing on my amd64 boxen with syslog logging enabled. Since syslog logging is now the default, I think grave severity is appropriate, even if other

Bug#729926: polipo: crashes due to syslog logging

Rolf Leggewie schrob: I've already been testing upstream git for quite a while. Most bug tickets in Debian were informed to test the package from http://oss.leggewie.org/deb/ so that I know which bugs become resolved by the new upstream. I plan to release the git version to experimental

Bug#712033: ekiga: README.security not installed

Package: ekiga Version: 4.0.1-2 Severity: minor Hi, I noticed the mention of README.security in the changelog, but the file didn't actually get installed: | $ dpkg -L ekiga | grep READ | /usr/share/doc/ekiga/README.Debian | $ It's in the source, however. regards, Jan -- System

Bug#709767: xprop: Out of memory for _NET_WM_ICON

Package: x11-utils Version: 7.7~1 Severity: normal | $ xprop -id $WINDOWID | XdndAware(ATOM) = BITMAP | WM_STATE(WM_STATE): | window state: Normal | icon window: 0x0 | _NET_WM_ICON(CARDINAL) = xprop: error: Out of memory! | $ This is in mlterm, which sets

Bug#392321: sudo: cannot use env_delete with env_reset

fixed 392321 1.8.3p1-2 fixed 523882 1.8.3p1-2 thanks Hi, both these bugs have been fixed in the meantime. All environment variables can now be preserved and removed by env_keep/env_check and env_delete, respectively. Or at least I tried the examples given, got the desired results, and see no

Bug#523882: sudo -i doesn't unset some environment variables

Vincent Lefevre schrob: However, though my /etc/environment is an empty file, some other variables are preserved. This includes LC_* variables, LS_COLORS, COLORTERM and XAUTHORITY. Example: # export LS_COLORS=blah # sudo -i env | grep LS_ LS_COLORS=blah Works for me: | # LS_COLORS=blah

Bug#523882: sudo -i doesn't unset some environment variables

And I get the same problem on another machine. That's strange. Ha, I think I got it. LS_COLORS is included by default in env_keep. If you don't set (or just append to) env_keep, LS_COLORS will be passed on, irrespective of -i and/or env_reset. If you overwrite env_keep (by assigning to it),

Bug#645537: oss4-dkms: dkms build fail

Package: oss4-dkms Version: 4.2-build2005-1 Followup-For: Bug #645537 tags 645537 + patch Hi, Indeed it seems to be i386-specific; the attached patch fixes the build here. On my amd64 box, 4.2-build2005-1 works fine both with and without the patch. regards, Jan -- System Information: Debian

Bug#640180: mlterm+screen crash with yes command

Package: mlterm Version: 3.0.6-1 Followup-For: Bug #640180 Hi, While the screen yes recipe doesn't bother mlterm here, I can reproducably make mlterm segfault by opening a non-empty file in vim and deleting several lines with the dd command. Moving my .mlterm/ and .vimrc out of the way doesn't

Bug#640434: reportbug -N tries to send mail to fixed_versions

: UTF-8 | Please change your locale if this is incorrect. | | Using 'Jan Braun janbr...@gmx.net' as your from address. | Retrieving report #561295 from Debian bug tracking system... | What do you want to do now? [N|x|o|r|b|e|q|?]? x | Getting status for cron... | Verifying package integrity

Bug#561295: too easy to delete crontab via `crontab -r`

Package: cron Version: 3.0pl1-118 Followup-For: Bug #561295 My workaround (after the first dataloss :) was placing a @daily crontab -l | ~/.crontab.jan line in my crontab. HTH, Jan P.S.: is it intentional that the /usr/share/bug/cron/script only reports that I have EDITOR set, but not to

Bug#595298: linux 2.6.36 not supported

Package: oss4-dkms Followup-For: Bug #595298 Linux 2.6.38-2 has entered testing, and is also affected by this. Fortunately, importing the 4.2-build2004 upstream version is very straightforward, it just needs adjusting of os_cmd.patch and bumping of the version number. Here, this created a working

Bug#619565: deluge-console: ignores all but first argument

Cristian Greco schrob: Jan Braun janbr...@gmx.net wrote: deluge-console ignores all its command line arguments but the first. this problem seems to be already known upstream: http://dev.deluge-torrent.org/ticket/1548 Anyway, there is an ongoing effort for a complete rewrite of deluge

Bug#619565: deluge-console: ignores all but first argument

Package: deluge-console Version: 1.3.1-1 Severity: normal Tags: patch Hi, deluge-console ignores all its command line arguments but the first. This means I have to write $ deluge-console add /some/torrent rather than the natural $ deluge-console add /some/torrent An obvoius patch is attached.

Bug#582137: dc is ignoring the .dcrc file.

Package: dc Version: 1.06.95-2 Followup-For: Bug #582137 This is a regression. Terran Melconian ter...@consistent.org provided patches in bug #167274 to implement .dcrc and the -E command line option, wich were applied in version 1.06-9 . The 1.06.94-1 debian changelog entry notes: * Upstream

Bug#386743: console-screen.sh sets $NUM_CONSOLES at inappropriate location

Package: console-tools Version: 1:0.2.3dbs-70 Severity: normal Still present in the current version. I'm surprised this obvious, trivial, (patch,pending) bug is still open after almost 4.5 years. And yes, the patch in #17 works for me. regards, Jan -- System Information: Debian Release:

Bug#574131: xdg-utils: xdg-email never launchs a mua if desktop is not gnome neither kde neither xfce

Per Olofsson schrob: 2010-06-28 15:55, Jonathan Nieder skrev: As you can see, I suspect would require some kind of per-package registration to be usable. Grasping at straws, I suggest maybe a field in the .desktop file. Is there prior art for this? Is there a relevant mailng list? I'm

Bug#574131: xdg-utils: xdg-email never launchs a mua if desktop is not gnome neither kde neither xfce

Per Olofsson schrob: 2010-10-22 11:53, Jan Braun skrev: I'm not aware of anything. But I'm being bold and propose $MAILER as user-configurable place, analogous to $EDITOR, $BROWSER, $PAGER.[1] Patch attached. I can't see the patches... Uh, that's because they weren't there. Sorry

Bug#511248: xdg-utils: Patch still not applied?

Matthieu Moy schrob: I can still see the bug, and applying the patch already attached to this bug report fixes it. Attached is a slightly updated patch, if it helps: I didn't modify the patch, but just fixed some conflict while applying it to the latest version. In case you (Pelle) prefer a

Bug#574131: xdg-utils: xdg-email never launchs a mua if desktop is not gnome neither kde neither xfce

Jonathan Nieder schrob: Interesting! I like it. Thanks! Nitpicks: Also thanks! :) - I think it would be good to call the envvar XDG_MAILER, because (1) the mailer for use in the console may not be the mailer to use on the desktop, I considered that, but since there's no

Bug#574131: xdg-utils: xdg-email never launchs a mua if desktop is not gnome neither kde neither xfce

[ wildly merged quotes from 3 mails. I hope you don't mind.] Per Olofsson schrob: Thanks. There's a problem though. xdg-email is meant specifically for GUI programs. That means there's no tty available in general. So you can't simply run mutt - you need to run it in a terminal window.

Bug#600662: konqueror: passes literal ipv6 address to HTTP CONNECT proxy

Package: konqueror Version: 4:4.4.5-1 Severity: normal Tags: ipv6 Hi, When I try to browse https://www.sixxs.net/ in Konqueror, it issues the following HTTP CONNECT call to my local http proxy[1]: | CONNECT 2001:1AF8:1:F006:0:0:0:6:443 HTTP/1.1 | Proxy-Connection: keep-alive | User-Agent:

Bug#600678: polipo: does not recognize long literal IPv6 addresses

Package: polipo Version: 1.0.4.1-1.1 Severity: normal Tags: patch ipv6 Hi, Polipo does not recognize very long literal IPv6 addresses as such: | $ wget http://[2001:1AF8:1:F006:0:0:0:6]/ | --2010-10-19 06:13:55-- http://[2001:1af8:1:f006:0:0:0:6]/ | Resolving localhost... ::1, 127.0.0.1 |

Bug#392321: sudo: cannot use env_delete with env_reset

Hi again, Ich schrob: The problem here is that the hardcoded keep these at all costs list in debian/patches/env.c-safety.diff (the second hunk) prevents that approach. I suggest just dropping that, particularly as all but XAPPLRESDIR, XFILESEARCHPATH, XUSERFILESEARCHPATH are already listed

Bug#598567: sudo requires reauthentication on each use, ignoring time stamp

Hi, Diggory Hardy schrob: The sudo man-page states: Once a user has been authenticated, a time stamp is updated and the user may then use sudo without a password for a short period of time (15 minutes unless overridden in sudoers). Since a few weeks this hasn't been happening on my

Bug#392321: sudo: cannot use env_delete with env_reset

Bdale Garbee schrob: On Wed, 2006-10-11 at 10:51 +0200, Arnaud Giersch wrote: The patch below causes to the deletion of the variables listed in env_deleted, even when env_reset is in use. Makes sense to me. Forwarding to upstream for comment / inclusion. With upstream sudo, you can

Bug#595886: syntax/lhaskell.vim: please support autoindent of Bird-style .lhs

Package: vim-runtime Version: 2:7.3.000+hg~ee53a39d5896-1 Severity: wishlist Hi, I wish for vim to honor my autoindent on setting and smartly indent Bird-style literate haskell. E.g.: somefun a b c = foo . bar . baz where foo = a bar = b ... and now hitting enter at the end of

Bug#582475: [fetchmail] The bug is still present (was: fetchmail: init script should wait for DNS)

Gabriele 'LightKnight' Stilli schrob: unfortunately the bug is still present on my system: fetchmail is still started before postfix, therefore its first run fails because it doesn't find any MTA to deliver the mail to. [...] Any hint on what could be wrong? I'd guess postfix doesn't

Bug#582475: [fetchmail] The bug is still present

Gabriele 'LightKnight' Stilli schrob: /etc/insserv.conf makes no mention of $mail-transport-agent whatsoever. /etc/init.d/postfix says: # Provides: postfix mail-transport-agent There's no $ in front of m-t-a. I have no idea whether or how that's significant. I'll read the docs

Bug#582475: fetchmail: init script should wait for DNS

Petter Reinholdtsen schrob: Actually, there is $mail-transport-agent (see URL: http://wiki.debian.org/LSBInitScripts/DebianVirtualFacilities ), but it is not widely implemented yet. Nice, thanks for the pointer. So I would modify the patch to look like this: +# Should-Start:

Bug#582475: [pkg-fetchmail-maint] Bug#582475: fetchmail: init script should wait for DNS

Nico Golde schrob: Hi, * Jan Braun janbr...@gmx.net [2010-05-21 13:38]: Fetchmail's init script should probably depend on exim4 and $named, rather than just $network. At least here, with dependency-based boot enabled, the first run always fails because DNS (a local pdnsd) is not yet

Bug#582475: fetchmail: init script should wait for DNS

Package: fetchmail Version: 6.3.17-1 Severity: normal Tags: patch Hi, Fetchmail's init script should probably depend on exim4 and $named, rather than just $network. At least here, with dependency-based boot enabled, the first run always fails because DNS (a local pdnsd) is not yet available when

Bug#580284: reportbug: NameError: global name 'options' is not defined when reporting FTBS

set: UTF-8 Please change your locale if this is incorrect. Using 'Jan Braun janbr...@gmx.net' as your from address. Getting status for pal... Verifying package integrity... Checking for newer versions at packages.debian.org... Will send report to Debian (per lsb_release). Querying Debian BTS

Bug#555376: tinyurl.pl is broken

Hi, The URL given by Jonas works again, here's the diff to the version in irssi-scripts 20090810. It's mostly whitespace, but at the end there's a comment about tinyurl.com changed their HTML output and a changed regex. I didn't test either version, however. HTH, Jan -- () ascii ribbon

Bug#550888: elinks does not recognize Cache-Control response headers

Hi, Kalle Olavi Niemitalo schrob: Juan Montoya th3pr0p...@gmail.com writes: Oh! I didn't expected document.cache.ignore_cache_control to be enabled by default. Yes, the option works as expected. I suggest disabled as the default value to produce a similar behaviour with other

Bug#565702: irssi-scripts: bitlbee_join_notice.pl needs use Irssi::TextUI;

Package: irssi-scripts Version: 20090810 Severity: normal Tags: patch Hi, bitlbee_join_notice.pl produces the following error: | 01:46 -!- Irssi: Error in script bitlbee_join_notice: | 01:46 Can't locate auto/Irssi/statusbar_i.al in @INC (@INC contains: /home/rlj/.irssi/scripts |

Bug#510374: xmms2-client-cli: please respect unix conventions wrt output verbosity

Benjamin Drung schrob: thanks for this patch. One thing is missing: running xmms2 with --verbose / -v should trigger the previous behavior. Here you go... Jan -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments diff -ru

Bug#510375: xmms2-launcher: please be more smart and silent

Hi, Adam Flott schrob: A patch is attached which turns off all output unless given --verbose. I hope that's what you were looking for. Yes, thank you. @@ -92,10 +98,14 @@ main (int argc, char **argv) if (res == -1) perror (read); if (res

Bug#510374: xmms2-client-cli: please respect unix conventions wrt output verbosity

tags 510374 + patch thanks HTH, Jan -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments --- ./clients/cli/cmd_pls.c.orig 2009-08-20 16:28:17.0 +0200 +++ ./clients/cli/cmd_pls.c 2009-08-20 16:28:20.0 +0200 @@ -38,7

Bug#478977: ratpoison: histories should be separate

Bernhard R. Link schrob: Well, an execute is an execute. Not having to remember which prompt was used to get back to it is a feature in my eyes. (Though this feature was mostly added because ratpoison has only one history file and there are at least two histories to remember). Ok, if that's

Bug#478977: ratpoison: histories should be separate

Package: ratpoison Version: 1.4.4-1 Severity: normal Hi, With 1.4.4-1, the original reporter's case C-t : resize C-t ! UPARROW is fixed: resize appears only in the : history, not in the ! one. However, the reverse case C-t ! true C-t : UPARROW still(?) presents :exec true as an entry in the

Bug#511248: xdg-utils: xdg-screensaver and basic x.org screen blanking

Package: xdg-utils Version: 1.0.2-6.1 Hi, There's more than xset s off to it. I can only blank my screen using StandbyTime (using native xorg.conf screenblanking) which is not turned off by xset s off. -dpms is needed to turn off StandBy'ing the screen. But xdg-screensaver already does

Bug#520639: mumble-server: generates noise when set to not automatically start

Package: mumble-server Version: 1.1.7-3 Severity: normal Hi, I have mumble-server installed and set it to NOT automatically start in /etc/default/mumble-server . Now, 1) logrotate fails daily: | /etc/cron.daily/logrotate: | error: error running non-shared postrotate script for

Bug#513119: murmur-user-wrapper: confused about dbus

Patrick Matthäi schrob: Jan Braun schrieb: 1. it requires dbus-x11 [...] Yeah, it is recommend by dbus, which is a depend of mumble-server. Explicit adding dbus-x11 as dependency to mumble-server would be a bit bloated, because not su much users use the user-wrapper, but there should

Bug#513119: murmur-user-wrapper: confused about dbus

Package: mumble-server Version: 1.1.4-4+lenny1 Severity: normal Tags: patch When trying to get murmur-user-wrapper to do its job, I ran into 3 issues: 1. it requires dbus-x11, which is only recommended: by dbus, not by mumble-server itself. 2. it exits successfully on errors. 3. it can't start

Bug#510374: xmms2-client-cli: please respect unix conventions wrt output verbosity

Package: xmms2-client-cli Version: 0.5DrLecter-2 Severity: minor Hi, common unix convention for CLI programs is being silent for successful operations, and being verbose on errors. xmms2 gets both wrong: $ ls some.ogg doesnotexist.ogg ls: cannot access doesnotexist.ogg: No such file or directory

Bug#510375: xmms2-launcher: please be more smart and silent

Package: xmms2-core Version: 0.5DrLecter-2 Severity: wishlist Hi, |$ xmms2-launcher |Log output will be stored in /home/jani/.cache/xmms2/xmms2d.log |xmms2 started |$ xmms2-launcher |Log output will be stored in /home/jani/.cache/xmms2/xmms2d.log |startup failed! |$ grep -C1 xmms2-launcher

Bug#510376: screen: bash completion would be nice

Package: screen Version: 4.0.3-11 Severity: wishlist Hi, I wish for bash recognizing screen as a program-that-runs-other-programs and doing completions accordingly. (More advanced stuff, such as completing sessions for -r, would of course be nice, but I don't miss that much.) |$ screen basTabTab

Bug#419572: make powermanga sgid games

Package: powermanga Version: 0.90-dfsg-1 Followup-For: Bug #419572 Hi, As pointed out in bug #502150, powermanga should be setgid games to write the highscores, normal users are _not_ supposed to be in that group. I don't know the correct debian way to package sgid binaries, but sudo chown :games

Bug#510372: manpage: non-portable echo example

Package: netcat-openbsd Version: 1.89-3 Severity: minor Hi, the nc(1) manpage says: | For example, to retrieve the home page of a web site: | $ echo -n GET / HTTP/1.0\r\n\r\n | nc host.example.com 80 This is a nonportable use of echo that happens to work as expected in dash, but not in bash: | $

Bug#481611: fbgs: should pass on more fbi options (again)

Package: fbi Version: 2.06-3 Severity: wishlist Tags: patch Hi, this is #361393, and the promised patch. I'm really sorry for being this late, I was sure I'd already sent it. :( -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (990, 'testing') Architecture:

Bug#470573: autofs starts before nis and fails reading its nis maps

Package: autofs Version: 4.1.4-13 Severity: important Good evening. I installed this new computer from scratch via debian netinstall CD. Afterwards, I installed by apt-get nis, nfs and than autofs (in this particular order). I made the appropriate changes to /etc/nsswitch.conf, in order to

Bug#407497: passwd: chsh,chfn prompt root for the password (breaking .postinst scripts)

Package: passwd Version: 1:4.0.18.1-6 Severity: normal Hi, I had upgrades of logcheck and sash fail because they use chfn and chsh (respectively) in their postinst script, and these ask for a password even when invoked by root. This causes a hang since the postinst script doesn't seem to be in

Bug#374370: wine: please make the dialog boxes keyboard-controllable

Ove Kaaven schrob: Could you submit it in diff -u format, perhaps? Sure. Jan --- wine.org2006-11-15 20:29:48.0 +0100 +++ wine.new2006-11-15 20:38:36.0 +0100 @@ -59,6 +59,7 @@ # xmessage not found; make sure the user notices this error # (GUI users wouldn't

  1   2   >