Bug#868015: knockd does not start after system reboot
Affected me as well. Debian Buster. Can be dangerous when working with a remote server!
Bug#851331: file: error message gets written to stdout, not stderr, and exit code is still 0
Package: file Version: 1:5.22+15-2 Severity: important Dear Maintainer, file -b --mime-type NONEXISTING_FILE > mimetype.txt && echo "success" will print "success" even though NONEXISTING_FILE does not exist, and the string "cannot open `NONEXISTING_FILE' (No such file or directory)" will be written to mimetype.txt, and nothing will be printed to stderr. What I expected: Nothing be written to mimetype.txt, an error message be written to stderr, "success" not be printed. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 8.0 (jessie) Release:8.0 Codename: jessie Architecture: armv7l Kernel: Linux 4.1.13-v7+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages file depends on: ii libc6 2.19-18+deb8u1 ii libmagic1 1:5.22+15-2 ii zlib1g 1:1.2.8.dfsg-2 file recommends no packages. file suggests no packages. -- no debconf information
Bug#812842: EnableLogging=1 doesn't have any effect
Package: usb-modeswitch Version: 2.2.0+repack0-2 According to the comments in /etc/usb_modeswitch.conf, setting EnableLogging=1 should make i produce a logfile in /var/log. When I invoke usb_modeswitch it does work (switches mode of my 3G dongle) but no logfile is created in /var/log. This is how I invoke it: usb_modeswitch --default-vendor=0x12d1 --default-product=0x1446 -J -Q This is the config file: # cat /etc/usb_modeswitch.conf # Configuration for the usb_modeswitch package, a mode switching tool for # USB devices providing multiple states or modes # # Evaluated by the wrapper script /usr/sbin/usb_modeswitch_dispatcher # # To enable an option, set it to "1", "yes" or "true" (case doesn't matter) # Everything else counts as "disable" # Disable automatic mode switching globally (e.g. to access the original # install storage) DisableSwitching=0 # Enable logging (results in a extensive report file in /var/log, named # "usb_modeswitch_" and probably others EnableLogging=1 # Optional increase of "delay_use" for the usb-storage driver; there are hints # that a recent kernel default change to 1 sec. may lead to problems, particu- # larly with USB 3.0 ports. Set this to at least 3 (seconds) in that case. # Does nothing if the current system value is same or higher #SetStorageDelay=4
Bug#506274: strange cp preserve mode behaviour
Package: coreutils Version: 5.97-5.3 $ umask 0077 $ touch foo $ ls -l foo -rw--- 1 user user 0 2008-11-20 03:04 foo $ chmod 0400 foo $ ls -l foo -r 1 user user 0 2008-11-20 02:47 foo $ cpfoo copy1 $ cp --no-preserve=mode foo copy2 $ cp -i foo copy3 $ cp --preserve=modefoo copy4 $ ls -l total 0 -rw--- 1 user user 0 2008-11-20 02:47 copy1 -r 1 user user 0 2008-11-20 02:47 copy2 -r 1 user user 0 2008-11-20 02:48 copy3 -r 1 user user 0 2008-11-20 02:50 copy4 -r 1 user user 0 2008-11-20 02:47 foo $ i would expect copy2 to have mode 0600 (default for new files with my umask) and i would expect copy1 and copy3 to have identical modes regardless of which it is. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#465467: python2.5: strange regex matching behavior with swedish UTF8 and non-UTF8 locales
Package: python2.5 Version: 2.5-5 Severity: normal Tags: l10n Expected behavior of the program below: Running the program like this should make it match just the first string: LANG=POSIX python2.5 testcase.py LANG=sv_SE python2.5 testcase.py Running the program like this should make it match both strings: LANG=sv_SE.utf8 python2.5 testcase.py Actual behaviour: Running the program like this makes it match just the first string: LANG=POSIX python2.5 testcase.py LANG=sv_SE.utf8 python2.5 testcase.py Running the program like this makes it match both strings: LANG=sv_SE python2.5 testcase.py So it's sort of reversed. Setting the locale to just sv_SE makes it unicode aware, while setting it to sv_SE.utf8, which is an unicode locale, makes it _not_ unicode aware. --- !/usr/bin/python import re import locale locale.setlocale(locale.LC_ALL, '') r=re.compile(r^\w, re.LOCALE) l1=ua l2=u\u00E5 # LATIN SMALL LETTER A WITH RING ABOVE if r.search(l1): print l1 matches if r.search(l2): print l2 matches - -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.58 Locale: LANG=sv_SE.UTF-8, LC_CTYPE=sv_SE.UTF-8 (charmap=UTF-8) Versions of packages python2.5 depends on: ii libbz2-1.0 1.0.3-6 high-quality block-sorting file co ii libc6 2.3.6.ds1-13etch4 GNU C Library: Shared libraries ii libdb4.4 4.4.20-8 Berkeley v4.4 Database Libraries [ ii libncursesw5 5.5-5 Shared libraries for terminal hand ii libreadline5 5.2-2 GNU readline and history libraries ii libsqlite3-0 3.3.8-1.1 SQLite 3 shared library ii libssl0.9.80.9.8c-4etch1 SSL shared libraries ii mime-support 3.39-1MIME files 'mime.types' 'mailcap ii python2.5-minimal 2.5-5 A minimal subset of the Python lan python2.5 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
