Bug#776298: transcode: Uses avcodec_encode_video no longer present in current libavcodec56

2015-01-26 Thread Michael Schuerig
Package: transcode
Version: 3:1.1.7-9+b4
Severity: normal

Dear Maintainer,

I was trying to rip a DVD in k3b. This resulted in an error and
the log contained

/usr/bin/transcode: symbol lookup error:
 /usr/lib/transcode/export_ffmpeg.so:
 undefined symbol: avcodec_encode_video

Judging by the docs at
https://libav.org/doxygen/master/group__lavc__encoding.html
avcodec_encode_video is no longer part of the API. Instead,
there's a new call avcodec_encode_video2.

Cheers,
Michael

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages transcode depends on:
ii  gawk   1:4.1.1+dfsg-1
ii  konsole [x-terminal-emulator]  4:4.14.2-1
ii  liba52-0.7.4   0.7.4-17
ii  libasound2 1.0.28-1
ii  libavcodec-extra-566:11.2-1
ii  libavformat56  6:11.2-1
ii  libavresample2 6:11.2-1
ii  libavutil546:11.2-1
ii  libc6  2.19-13
ii  libdv4 1.0.0-6
ii  libdvdread45.0.0-1
ii  libfreetype6   2.5.2-2
ii  libgomp1   4.9.2-10
ii  libice62:1.0.9-1+b1
ii  libjpeg62-turbo1:1.3.1-11
ii  liblzo2-2  2.08-1.2
ii  libmagickcore-6.q16-2  8:6.8.9.9-5
ii  libmagickwand-6.q16-2  8:6.8.9.9-5
ii  libmjpegutils-2.1-01:2.1.0+debian-3
ii  libmp3lame03.99.5+repack1-5
ii  libmpeg2-4 0.5.1-6
ii  libogg01.3.2-1
ii  libpostproc52  6:0.git20120821-4
ii  libquicktime2  2:1.2.4-7+b1
ii  libsdl1.2debian1.2.15-10+b1
ii  libsm6 2:1.2.2-1+b1
ii  libtheora0 1.1.1+dfsg.1-6
ii  libvorbis0a1.3.4-2
ii  libvorbisfile3 1.3.4-2
ii  libx11-6   2:1.6.2-3
ii  libxaw72:1.0.12-2+b1
ii  libxext6   2:1.3.3-1
ii  libxml22.9.2+dfsg1-1+b1
ii  libxpm41:3.5.11-1+b1
ii  libxt6 1:1.1.4-1+b1
ii  libxv1 2:1.0.10-1+b1
ii  mawk   1.3.3-17
ii  xterm [x-terminal-emulator]312-1
ii  zlib1g 1:1.2.8.dfsg-2+b1

Versions of packages transcode recommends:
ii  sox14.4.1-5
ii  transcode-doc  3:1.1.7-9
ii  twolame0.3.13-1.1

Versions of packages transcode suggests:
pn  mjpegtools  none
pn  xvid4conf   none

-- 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#766438: Acknowledgement (no longer restarts containers on boot)

2014-10-26 Thread Michael Schuerig
On Sat, 25 Oct 2014 15:08:05 -0600 Tianon Gravi admwig...@gmail.com 
wrote:
 On 23 October 2014 01:05, Joey Hess jo...@debian.org wrote:
  Maybe --restart=always or --restart=on-error is needed to get the 
old
  behavior? I cannot make much sense of the upstream changelog.
 
 You've interpreted it correctly here.  Upstream decided that it was
 better to add an explicit restart policy for each container than to
 continue to maintain their fragile heuristics for when a container is
 deemed appropriate to automatically restart (since it didn't actually
 work correctly half the time anyways).

Tianon,

reading the docs at

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766438

I don't think your explanation applies to this particular case

# quote
Using the --restart flag on Docker run you can specify a restart policy 
for how a container should or should not be restarted on exit.

no - Do not restart the container when it exits.

on-failure - Restart the container only if it exits with a non zero exit 
status.

always - Always restart the container regardless of the exit status.

You can also specify the maximum amount of times Docker will try to 
restart the container when using the on-failure policy. The default is 
that Docker will try forever to restart the container.
# endquote

My understanding of this excerpt is that containers that exit by 
themselves (e.g. due to a failure) are restarted according to the 
restart policy. It does not seem to apply to containers that were 
stopped by docker itself before the system was shutdown or rebooted.

Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#766399: android-tools-adb: udev rules expect group adbusers to exist

2014-10-22 Thread Michael Schuerig
Package: android-tools-adb
Version: 4.2.2+git20130529-4
Severity: normal

Dear Maintainer,

the udev rules in /lib/udev/rules.d/70-android-tools-adb.rules
expect a group adbusers to exist. However, if there is no such
group, the package scripts do not create it. As a result,
systemd-udevd logs error messages about the missing group every
couple of minutes.

Also, the file contains fancy quotation marks in line 324. It
ought to look like

ATTR{idProduct}==3252, OPTIONS==ignore_device


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages android-tools-adb depends on:
ii  libc62.19-11
ii  libssl1.0.0  1.0.1j-1
ii  zlib1g   1:1.2.8.dfsg-2

android-tools-adb recommends no packages.

android-tools-adb suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /lib/udev/rules.d/70-android-tools-adb.rules (from 
android-tools-adb package)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#764270: dpkg: warning: unable to delete old directory '/etc/chromium': Directory

2014-10-06 Thread Michael Schuerig

To me it looks like something in the upgrade process is broken. The 
package contains files in /etc/chromium, yet when I upgraded to 
37.0.2062.120-3 or when I reinstall it, afterwards /etc/chromium is 
empty.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#669618: Wanted

2014-09-27 Thread Michael Schuerig
On Thursday 25 September 2014 11:24:13 Daniele Scasciafratte wrote:
 This feature will be very useful!
 
 michael your script not work for me :-/

Some of the time it hasn't been working for me, either. Right now (on a 
current sid) it appears to work. I'm not really sure why.

In your case, I'm sorry to say, you'll have to do some debugging 
yourself.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#669618: bash-completion should autocomplete bash alias as well

2014-07-19 Thread Michael Schuerig

I just stumbled on the same problem and after some experimentation, I'm 
sourcing a modified completion loader at the end of my .bashrc (specifically 
after the original completion code is loaded).

_custom_completion_loader()
{
local cmd=${1##*/}
local cmdt=$(type -t $1)
local compfile=./completions

#[[ $BASH_SOURCE == */* ]]  compfile=${BASH_SOURCE%/*}/completions
compfile=/usr/share/bash-completion/completions

if [[ $cmdt = 'alias' ]]; then
  cmd=$( alias $cmd | sed s/^alias [^=]*='\([^ ']*\)[ '].*$/\1/ )
  [[ $(type -t _${cmd}) = 'function' ]]  complete -F _${cmd} $1  
return 124
fi
compfile+=/${cmd}  

# Avoid trying to source dirs; https://bugzilla.redhat.com/903540
[[ -f $compfile ]]  . $compfile /dev/null  return 124

# Need to define *something*, otherwise there will be no completion at 
all.
complete -F _minimal $cmd  return 124
}
complete -D -F _custom_completion_loader


Beware of wrapped lines. This code is fresh from my keyboard and not at all 
well-tested!

Michael


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#755019: autofs: Debug messages logged as errors

2014-07-16 Thread Michael Schuerig
Package: autofs
Version: 5.0.8-1
Severity: normal

Dear Maintainer,

automounter logs irrelevant messages as errors.

A block of messages like these appears every 15 minutes in my logs

Jul 16 22:15:58 fuchsia automount[25623]: macro_setenv: table 0x7f334c000c00
Jul 16 22:15:58 fuchsia automount[25623]: lv-def SHOST lv-val fuchsia
lv-next 0x7f334c000b70
Jul 16 22:15:58 fuchsia automount[25623]: lv-def HOME lv-val /home/michael
lv-next 0x7f334c000ab0
Jul 16 22:15:58 fuchsia automount[25623]: lv-def GROUP lv-val michael
lv-next 0x7f334c000a40
Jul 16 22:15:58 fuchsia automount[25623]: lv-def USER lv-val michael
lv-next 0x7f334c0009d0
Jul 16 22:15:58 fuchsia automount[25623]: lv-def GID lv-val 1000 lv-next
0x7f334c000960
Jul 16 22:15:58 fuchsia automount[25623]: lv-def UID lv-val 1000 lv-next
(nil)

They originate from macro_setenv in lib/macros.rb. The relevant lines are

error(LOGOPT_ANY, table %p, table);
dump_table(table);

As the function still continues and returns without internally indicating
any error, I take it that these messages are simply debugging leftovers
from when the code was originally written.

In themselves, these messages are not harmful, but they overcrowd log files
and may distract from important messages.


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages autofs depends on:
ii  libc6  2.19-7
ii  libxml22.9.1+dfsg1-4
ii  multiarch-support  2.19-7
ii  ucf3.0030

Versions of packages autofs recommends:
ii  kmod   18-1
ii  module-init-tools  18-1
pn  nfs-common none

autofs 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#751971: docker.io: Please consider providing an nsinit binary

2014-06-18 Thread Michael Schuerig
Package: docker.io
Version: 1.0.0~dfsg1-1
Severity: wishlist

Dear Maintainer,

nsinit is a tool that allows to attach to a running container.
This is very helpful when debugging a problem in a container
and a lot more lightweight than running sshd in each container.

nsinit is already contained in the docker.io source package
at pkg/libcontainer/nsinit/.

Thanks,
Michael


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages docker.io depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.19
ii  iptables 1.4.21-2
ii  libapparmor1 2.8.0-5.1+b1
ii  libc62.19-3
ii  libdevmapper1.02.1   2:1.02.85-2
ii  libsqlite3-0 3.8.5-2
ii  perl 5.18.2-4

Versions of packages docker.io recommends:
ii  aufs-tools   1:3.2+20130722-1.1
ii  ca-certificates  20140325
ii  cgroupfs-mount   1.0
ii  git  1:2.0.0-2
ii  xz-utils 5.1.1alpha+20120614-2

Versions of packages docker.io suggests:
ii  btrfs-tools  3.14.1-1
ii  debootstrap  1.0.60
ii  lxc  1.0.4-3
pn  rinsenone

-- 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#743776: plasma-widget-cwp: CWP floods .xsession-errors with messages

2014-04-06 Thread Michael Schuerig
Package: plasma-widget-cwp
Version: 1.10.2-1
Severity: minor

Dear Maintainer,

on each update, the CWP widget writes a lot of messages to .xsession-errors;
see below. In KDE's Debug Settings (kdebugdialog), I have disabled all debug
output, in addition I have explicitly disabled kweather and kweatherservice.
None of these affect the messages written by CWP.

I see the point of having these messages for debugging purposes, but they
should only be written if debugging messages are enabled.

Michael

setting locale to  utf-8  and encoding to  utf8
data_location_location:  Bonn
data_location_country:  Deutschland
data_sun_sunrise:  06:57
data_sun_sunset:  20:12
data_provider_update_time:  N.A.
data_current_temperature:  13
data_current_temperature_felt:  13
data_current_wind_code:  SSW
data_current_wind_speed:  18 km/h
data_current_wind:  Aus SSW 18 km/h
data_current_icon_code (orig):  26
data_current_icon_code:  26
data_current_icon_text:  Bedeckt
data_current_humidity:  74%
data_current_rain:  
data_current_dew_point:  8
data_current_visibility:  16,1 km
data_current_pressure:  1.006,1
data_current_uv_index:  1 - Niedrig
data_day_name[ 0 ]:  Heute
data_day_temperature_high[ 0 ]:  19
data_day_temperature_low[ 0 ]:  12
data_current_icon_code (orig):  28
data_day_icon_code[ 0 ]:  28
data_day_icon_text[ 0 ]:  Stark bewölkt
data_day_name[ 1 ]:  Morgen
data_day_temperature_high[ 1 ]:  22
data_day_temperature_low[ 1 ]:  11
data_current_icon_code (orig):  30
data_day_icon_code[ 1 ]:  30
data_day_icon_text[ 1 ]:  Wolkig
data_day_name[ 2 ]:  Di
data_day_temperature_high[ 2 ]:  12
data_day_temperature_low[ 2 ]:  4
data_current_icon_code (orig):  30
data_day_icon_code[ 2 ]:  30
data_day_icon_text[ 2 ]:  Wolkig
data_day_name[ 3 ]:  Mi
data_day_temperature_high[ 3 ]:  14
data_day_temperature_low[ 3 ]:  4
data_current_icon_code (orig):  30
data_day_icon_code[ 3 ]:  30
data_day_icon_text[ 3 ]:  Wolkig
data_day_name[ 4 ]:  Do
data_day_temperature_high[ 4 ]:  18
data_day_temperature_low[ 4 ]:  7
data_current_icon_code (orig):  30
data_day_icon_code[ 4 ]:  30
data_day_icon_text[ 4 ]:  Wolkig
data_day_name[ 5 ]:  Fr
data_day_temperature_high[ 5 ]:  14
data_day_temperature_low[ 5 ]:  4
data_current_icon_code (orig):  26
data_day_icon_code[ 5 ]:  26
data_day_icon_text[ 5 ]:  Bedeckt
data_day_name[ 6 ]:  Sa
data_day_temperature_high[ 6 ]:  13
data_day_temperature_low[ 6 ]:  6
data_current_icon_code (orig):  30
data_day_icon_code[ 6 ]:  30
data_day_icon_text[ 6 ]:  Wolkig


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages plasma-widget-cwp depends on:
ii  libc62.18-4
ii  libkdecore5  4:4.11.5-1
ii  libkdeui54:4.11.5-1
ii  libkio5  4:4.11.5-1
ii  libplasma3   4:4.11.5-1
ii  libqt4-xml   4:4.8.5+git242-g0315971+dfsg-2
ii  libqtcore4   4:4.8.5+git242-g0315971+dfsg-2
ii  libqtgui44:4.8.5+git242-g0315971+dfsg-2
ii  libsolid44:4.11.5-1
ii  libstdc++6   4.8.2-19

plasma-widget-cwp recommends no packages.

plasma-widget-cwp 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#739894: snapper: Storing snapshots in their mounted parent subvolume breaks things

2014-02-23 Thread Michael Schuerig
Package: snapper
Version: 0.1.8-2
Severity: normal
Tags: upstream

Dear Maintainer,

this is probably a problem for upstream, but I can't find their bug tracker. So 
here it goes:

Snapper stores the snapshots it makes of a subvolume in a subdirectory
..snapshots in that same subvolume. E.g., if I have a configuration home
for /home, its snapshots are stored in /home/.snapshots.

As a result, programs that traverse the filesystem inadvertantly walk
into the snapshots. The simplest case is an invocation of find somewhere
above a snappered subvolume. Locate/updatedb index each individual
snapshot. An NFS export of such a subvolume exposes its snapshots.

Presumably, the convention of putting snapshots in a .snapshots
subdirectory makes it easier to apply snapper to an existing filesystem.
Unfortunately, it breaks other things.

Solution: Change the filesystem layout so that snapshots are not stored
in (permanently) mounted subvolumes.

Compare the layout Ubuntu uses with btrfs:
https://help.ubuntu.com/community/btrfs#Ubuntu-specific_subvolume_layout_in_11.04_and_later

I suggest snapper use a similar (same?) layout.

Michael


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages snapper depends on:
ii  btrfs-tools3.12-1
ii  libboost-system1.54.0  1.54.0-4+b1
ii  libboost-thread1.54.0  1.54.0-4+b1
ii  libc6  2.18-1
ii  libdbus-1-31.8.0-1
ii  libgcc11:4.8.2-16
ii  libsnapper20.1.8-2
ii  libstdc++6 4.8.2-16
ii  libxml22.9.1+dfsg1-3
ii  zlib1g 1:1.2.8.dfsg-1

snapper recommends no packages.

snapper 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#706227: krfb: Crashes on start; missing file?

2013-04-26 Thread Michael Schuerig
Package: krfb
Version: 4:4.8.4-1+b1
Severity: normal

Dear Maintainer,

when I start krfb it crashes immediately. On the commandline I get

$ krfb 
krfb(1808) KXMLGUIClient::setXMLFile: cannot find .rc file krfbui.rc for 
component krfb 
KCrash: Application 'krfb' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/michael/.kde/socket-fuchsia/kdeinit4__0

It looks like a file defining the user interface is missing from the package.

I tried the 4:4.10.2-1 package, too, and get the same error there.

Michael

-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages krfb depends on:
ii  kde-runtime 4:4.8.4-2
ii  libc6   2.13-38
ii  libjpeg88d-1
ii  libkdecore5 4:4.8.4-4
ii  libkdeui5   4:4.8.4-4
ii  libkdnssd4  4:4.8.4-4
ii  libqt4-network  4:4.8.2+dfsg-11
ii  libqtcore4  4:4.8.2+dfsg-11
ii  libqtgui4   4:4.8.2+dfsg-11
ii  libstdc++6  4.7.2-5
ii  libx11-62:1.5.0-1
ii  libxdamage1 1:1.1.3-2
ii  libxext62:1.3.1-2
ii  libxtst62:1.2.1-1
ii  zlib1g  1:1.2.7.dfsg-13

krfb recommends no packages.

Versions of packages krfb suggests:
ii  khelpcenter4  4:4.8.4-2
ii  krdc  4:4.8.4-1+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#639391: sudo: Changes to session handling cause ecryptfs $HOME to be unmounted

2011-08-26 Thread Michael Schuerig
Package: sudo
Version: 1.8.2-1
Severity: important


After upgrading sudo, I noticed that my ecryptfs encrypted home
directory was unmounted after using sudo. Specifically, after
a newly authenticated a sudo session was finished.

The encrypted home dir is mounted automatically through
pam_ecryptfs.so and is meant to be unmounted only when the last
session is closed.

For this purpose, ecryptfs keeps track of the mount count in
/dev/shm/ecryptfs-$USER-Private. Only when the count reaches 0
is the umount performed.

This worked with all versions of sudo until now. The changed
PAM configuration has the effect that at the start of a sudo
session the ecryptfs mount count is *not* incremented, while it
is decremented when the session ends. When the counter reaches
0, this causes the encrypted directory to be unmounted.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.39-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages sudo depends on:
ii  libc6 2.13-16Embedded GNU C Library: 
Shared lib
ii  libpam-modules1.1.3-2Pluggable Authentication 
Modules f
ii  libpam0g  1.1.3-2Pluggable Authentication 
Modules l

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/sudoers.d/README'

-- 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#585153: cups-pdf: Sets too restrictive permissions on /usr/lib/cups/backend

2010-06-09 Thread Michael Schuerig
Package: cups-pdf
Version: 2.5.0-15
Severity: normal


Today I noticed that I couldn't print anymore to my dead tree
printer. In /var/log/cups/error_log I see

D [09/Jun/2010:17:34:26 +0200] [Job 1319] /usr/lib/cups/backend/socket: 
Permission denied

Indeed that directory has rather restrictive permissions

drwx-- 2 root root 4.096 2010-06-09 17:44 /usr/lib/cups/backend

Before upgrading to 2.5.0-15, these were drwxr-xr-x.
After I changed the permissions back, printing worked again.

I'm not certain, whether the restrictive permissions the error
or whether they are correct and whatever else that's broken by
them is at fault.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cups-pdf depends on:
ii  cups1.4.3-1  Common UNIX Printing System(tm) - 
ii  cups-client 1.4.3-1  Common UNIX Printing System(tm) - 
ii  ghostscript 8.71~dfsg2-3 The GPL Ghostscript PostScript/PDF
ii  libc6   2.11.1-3 Embedded GNU C Library: Shared lib
ii  libpaper-utils  1.1.24   library for handling paper charact

cups-pdf recommends no packages.

Versions of packages cups-pdf suggests:
ii  system-config-printer-kde 4:4.4.4-1  KDE printer configuration utility

-- 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#584544: ecryptfs-setup-private: script inconsistent with man-page

2010-06-04 Thread Michael Schuerig
Package: ecryptfs-utils
Version: 83-1
Severity: normal


The man-page for ecryptfs-setup-private mentions options

  -a, --all-home
 Generate a setup for encrypting the user's
 entire home directory

However, the script itself does not understand this option.
Possibly the script is an outdated version.

The output from ecryptfs-setup-private --help does contain

 -b, --bootstrap  Bootstrap a new user's entire home directory
  Generates a random mount passphrase, which
  will be wrapped when the new login passphrase
  is set. SHOULD ONLY BE CALLED FROM 'adduser'.

This option is not mentioned in the man-page. Also, the current
version of adduser (3.112) does not support creating users
with encrypted home directories.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ecryptfs-utils depends on:
ii  gettext-base  0.18-1 GNU Internationalization utilities
ii  keyutils  1.4-1  Linux Key Management Utilities
ii  libc6 2.11.1-2   Embedded GNU C Library: Shared lib
ii  libecryptfs0  83-1   ecryptfs cryptographic filesystem 
ii  libgpg-error0 1.6-1  library for common error values an
ii  libgpgme111.2.0-1.2  GPGME - GnuPG Made Easy
ii  libkeyutils1  1.4-1  Linux Key Management Utilities (li
ii  libnss3-1d3.12.6-2   Network Security Service libraries
ii  libpam-runtime1.1.1-3Runtime support for the PAM librar
ii  libpam0g  1.1.1-3Pluggable Authentication Modules l

ecryptfs-utils recommends no packages.

Versions of packages ecryptfs-utils suggests:
ii  cryptsetup2:1.1.2-1  configures encrypted block devices
pn  opencryptoki  none (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#580578: It's probably a libsane problem

2010-05-08 Thread Michael Schuerig
On Saturday 08 May 2010, Julien BLACHE wrote:
 Your backtrace points at the umax1220u backend, but that doesn't mean
 this backend is at fault (especially given the segfault actually
 happens in libusb). It's possible that a previous backend messed
 something up and it's just umax1220u that trips up on that.

After upgrading libusb-1.0-0 to version 2:1.0.8-1, the problem 
disappeared.

Michael




-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#580578: It's probably a libsane problem

2010-05-08 Thread Michael Schuerig
On Saturday 08 May 2010, Julien BLACHE wrote:
 Michael Schuerig mich...@schuerig.de wrote:
 
 Hi,
 
  After upgrading libusb-1.0-0 to version 2:1.0.8-1, the problem
  disappeared.
 
 Funny, because libsane doesn't actually use libusb-1.0 ...

Yes, I had noticed that. I have no idea what the root cause might have 
been.

Michael



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#580636: libpam-mount: Mount on login and mount.crypt only work with slot 0 password

2010-05-07 Thread Michael Schuerig
Package: libpam-mount
Version: 2.0-1
Severity: normal
Tags: sid


I have a LUKS encrypted /home partition with two keys.
Slot 0 is a longish phrase, slot 1 is the same as my login password.

Since a recent upgrade, /home isn't mounted automatically anymore
when I log in. Apparently, the underlying mount.crypt stopped
working with the slot 1 password, whereas it still works with the
slot 0 one.

This is the case when I try to switch the user (su) from root to
the single one that triggers mounting of /home, as well as when I
run mount.crypt explicitly.

Regarding the fskeyhash specified in /etc/security/pam_mount.conf.xml,
it makes no difference, whether I leave it out (produces a warning),
give it as (null) or sha1.

Notably, cryptsetup luksOpen and subsequent mounting of the mapped
device, still works with the slot 1 password as well as the slot 0
one.

Michael


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libpam-mount depends on:
ii  libc6   2.10.2-6 Embedded GNU C Library: Shared lib
ii  libcryptsetup1  2:1.1.0-2.1  libcryptsetup shared library
ii  libhx22 3.4-1A library providing queue, tree, I
ii  libpam-runtime  1.1.1-3  Runtime support for the PAM librar
ii  libpam0g1.1.1-3  Pluggable Authentication Modules l
ii  libssl0.9.8 0.9.8n-1 SSL shared libraries
ii  libxml2 2.7.7.dfsg-2 GNOME XML library
ii  mount   2.16.2-0 Tools for mounting and manipulatin

libpam-mount recommends no packages.

Versions of packages libpam-mount suggests:
ii  davfs2 1.4.5-1   mount a WebDAV resource as a regul
ii  fuse-utils 2.8.1-1.2 Filesystem in USErspace (utilities
ii  lsof   4.81.dfsg.1-1 List open files
pn  ncpfs  none(no description available)
ii  openssl0.9.8n-1  Secure Socket Layer (SSL) binary a
ii  psmisc 22.11-1   utilities that use the proc file s
ii  smbfs  2:4.1-1   Common Internet File System utilit
ii  sshfs  2.2-1 filesystem client based on SSH Fil
pn  tc-utils   none(no description available)
ii  xfsprogs   3.1.1 Utilities for managing the XFS fil

-- Configuration Files:
/etc/security/pam_mount.conf.xml changed:
?xml version=1.0 encoding=utf-8 ?
!DOCTYPE pam_mount SYSTEM pam_mount.conf.xml.dtd
!--
See pam_mount.conf(5) for a description.
--
pam_mount
!-- Volume definitions --
!-- MS --
volume
 user=michael
 fstype=crypt
 path=/dev/disk/by-uuid/90ccd500-0d23-417c-af6c-c5d3ca09f7da
 mountpoint=/home
 fskeyhash=sha1
 options=noatime
/
!-- pam_mount parameters: General tunables --
debug enable=1 /
!--
luserconf name=.pam_mount.conf.xml /
--
!-- Note that commenting out mntoptions will give you the defaults.
 You will need to explicitly initialize it with the empty string
 to reset the defaults to nothing. --
mntoptions 
allow=nosuid,nodev,loop,encryption,fsck,nonempty,allow_root,allow_other /
!--
mntoptions deny=suid,dev /
mntoptions allow=* /
mntoptions deny=* /
--
mntoptions require=nosuid,nodev /
path/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin/path
logout wait=0 hup=0 term=0 kill=0 /
!-- pam_mount parameters: Volume-related --
mkmountpoint enable=1 remove=true /
/pam_mount


-- debconf information:
  libpam-mount/convert-xml-config: false
# su michael
pam_mount(pam_mount.c:552): pam_mount 2.0: entering session stage
reenter password for pam_mount: entered slot 1 password
pam_mount(misc.c:38): Session open: (uid=0, euid=0, gid=1000, egid=1000)
pam_mount(mount.c:196): Mount info: globalconf, user=michael volume 
fstype=crypt server=(null) 
path=/dev/disk/by-uuid/90ccd500-0d23-417c-af6c-c5d3ca09f7da 
mountpoint=/home cipher=(null) fskeypath=(null) fskeycipher=(null) 
fskeyhash=sha1 options=noatime / fstab=0
command: 'mount.crypt' '-ofsk_hash=sha1' '-onoatime' 
'/dev/disk/by-uuid/90ccd500-0d23-417c-af6c-c5d3ca09f7da' '/home' 
pam_mount(misc.c:38): set_myuidpre: (uid=0, euid=0, gid=1000, egid=1000)
pam_mount(misc.c:38): set_myuidpost: (uid=0, euid=0, gid=1000, egid=1000)
FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/sda1 ext3  964500211772703732  24% /
tmpfstmpfs 1552796 8   1552788   1% /lib/init/rw
proc  proc   0 0 0   -  /proc
sysfssysfs   0 0 0   -  /sys
udev tmpfs 1547364   336   1547028   1% /dev
tmpfstmpfs

Bug#580578: xsane: Segfault on startup

2010-05-06 Thread Michael Schuerig
Package: xsane
Version: 0.996-4
Severity: normal
Tags: sid


Xsane on my system reliably crashes on startup with a segfault.

I'm not certain whether xsane is the real culprit, but that is
where this problem manifests itself. I've attached a backtrace.

Michael


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages xsane depends on:
ii  libatk1.0-0 1.30.0-1 The ATK accessibility toolkit
ii  libc6   2.10.2-6 Embedded GNU C Library: Shared lib
ii  libcairo2   1.8.10-4 The Cairo 2D vector graphics libra
ii  libfontconfig1  2.8.0-2.1generic font configuration library
ii  libfreetype62.3.11-1 FreeType 2 font engine, shared lib
ii  libgimp2.0  2.6.8-3  Libraries for the GNU Image Manipu
ii  libglib2.0-02.24.1-1 The GLib library of C routines
ii  libgtk2.0-0 2.20.1-1 The GTK+ graphical user interface 
ii  libjpeg62   6b-16.1  The Independent JPEG Group's JPEG 
ii  liblcms11.18.dfsg-1.2+b1 Color management library
ii  libpango1.0-0   1.28.0-1 Layout and rendering of internatio
ii  libpng12-0  1.2.43-1 PNG library - runtime
ii  libsane 1.0.21-1 API library for scanners
ii  libtiff43.9.2-3+b1   Tag Image File Format (TIFF) libra
ii  xsane-common0.996-4  featureful graphical frontend for 
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

Versions of packages xsane recommends:
ii  cups-client 1.4.3-1  Common UNIX Printing System(tm) - 
ii  elinks [www-browser]0.12~pre5-2  advanced text-mode WWW browser
ii  iceweasel [www-browser] 3.5.9-3  Web browser based on Firefox
ii  konqueror [www-browser] 4:4.4.3-1KDE 4's advanced file manager, web
ii  lynx-cur [www-browser]  2.8.8dev.3-3 Text-mode WWW Browser with NLS sup
ii  w3m [www-browser]   0.5.2-4  WWW browsable pager with excellent

Versions of packages xsane suggests:
ii  gimp  2.6.8-3The GNU Image Manipulation Program
ii  gocr  0.48-1 A command line OCR
ii  gv1:3.6.9-1  PostScript and PDF viewer for X
pn  hylafax-client | mgetty-fax   none (no description available)

-- no debconf information
$ gdb xsane
GNU gdb (GDB) 7.1-debian
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as i486-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/xsane...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/xsane 
[Thread debugging using libthread_db enabled]

Program received signal SIGSEGV, Segmentation fault.
*__GI___libc_free (mem=0x20058205) at malloc.c:3709
3709malloc.c: No such file or directory.
in malloc.c
(gdb) bt full
#0  *__GI___libc_free (mem=0x20058205) at malloc.c:3709
ar_ptr = value optimized out
p = 0x200581fd
#1  0xb6d25d5d in usb_destroy_configuration () from /lib/libusb-0.1.so.4
No symbol table info available.
#2  0xb6d254e2 in usb_free_dev () from /lib/libusb-0.1.so.4
No symbol table info available.
#3  0xb6d25940 in usb_find_devices () from /lib/libusb-0.1.so.4
No symbol table info available.
#4  0xb6d14849 in sanei_usb_init () at sanei_usb.c:574
prefix = 0xbfff95f0
prefixlist = {0xb6d1d934 /dev/, 0xb6d1f9c3 usbscanner, 0xb6d1d93a 
/dev/usb/, 
  0xb6d1f960 scanner, 0x0, 0x0}
vendor = 135780272
product = -1227753054
devname = 
x5\001\000\377\377\377\377\364\357\377\267\006\000\000\000\000\000\000\000ؒ\377\277?\317\376\267\330\331\027\bP\333\027\b,
 '\000' repeats 12 times, 

Bug#580578: It's probably a libsane problem

2010-05-06 Thread Michael Schuerig

I've removed everything from /usr/lib/sane except the libs needed by my 
scanner, an Epson V200 Photo, installed by Avasys iscan package. Now, at 
least I can scan again. As I don't think that these drivers do something 
magically different than all the others, my hypothesis is that the real 
problem is related to probing for the right driver to use.

Also, it's pretty clear that xsane is not the culprit. More likely 
libsane is. However, I have reinstalled 1.0.20-13, a version of which I 
know that is has worked before, and there the segfault occurs, too.

Michael



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#517841: network-manager-kde: Shared key is stored encrypted, but not decrypted when read

2009-03-02 Thread Michael Schuerig
Package: network-manager-kde
Version: 1:0.7~~svn931033-1
Severity: important


Whereas knetworkmanager 0.2.2 used kwallet for storing passwords
(as it should), 0.7 saves its shared keys in its own config file,
~/.kde/share/config/knetworkmanagerrc. Apparently, shared keys
are encrypted in some way when stored, but they are not decrypted
again when read from the config file.

This behavior at least affects the edit connections dialog, as
I was able to confirm by changing the config file with a text
editor. The contents of the config file entry are displayed
undecrypted in the dialog.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages network-manager-kde depends on:
ii  kdelibs4c2a 4:3.5.10.dfsg.1-1+b1 core libraries and binaries for al
ii  libc6   2.9-4GNU C Library: Shared libraries
ii  libdbus-1-3 1.2.12-1 simple interprocess messaging syst
ii  libdbus-1-qt3-0 0.9-2backport of Qt4 D-Bus bindings (sh
ii  libgcc1 1:4.3.3-5GCC support library
ii  libhal1 0.5.11-8 Hardware Abstraction Layer - share
ii  libice6 2:1.0.5-1X11 Inter-Client Exchange library
ii  libnl1  1.1-5library for dealing with netlink s
ii  libpng12-0  1.2.35-1 PNG library - runtime
ii  libqt3-mt   3:3.3.8b-5+b1Qt GUI Library (Threaded runtime v
ii  libsm6  2:1.1.0-2X11 Session Management library
ii  libstdc++6  4.3.3-5  The GNU Standard C++ Library v3
ii  libx11-62:1.1.5-2X11 client-side library
ii  libxext62:1.0.4-1X11 miscellaneous extension librar
ii  network-manager 0.7.0.97-1   network management framework daemo
ii  zlib1g  1:1.2.3.3.dfsg-12compression library - runtime

Versions of packages network-manager-kde recommends:
ii  kwalletmanager4:3.5.10-2 wallet manager for KDE
ii  network-manager-openvpn   0.7.0.97-1 network management framework (Open
ii  network-manager-vpnc  0.7.0.97-1 network management framework (VPNC

network-manager-kde 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#512787: upgrade makes system unbootable

2009-01-26 Thread Michael Schuerig

The same happened on my notebook (Dell D820) after the recent upgrade 
from 1.96+20080724-12 to 1.96+20080724-14.

set root=(hd0,1)
search --fs-uuid --set 546d6205-7424-4a37-86e5-d1e355c3d2ba
menuentry Debian GNU/Linux, linux 2.6.26-1-686 {
linux   /boot/vmlinuz-2.6.26-1-686 
root=UUID=546d6205-7424-4a37-86e5-d1e355c3d2ba ro
initrd  /boot/initrd.img-2.6.26-1-686
}

I checked in grub-emu (...-14!) and

  search --fs-uuid --set 546d6205-7424-4a37-86e5-d1e355c3d2ba

didn't produce any output at all. Whatever it did, I got another prompt 
afterwards.

Michael



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#487967: e2fsprogs: fsck -A tries to check everything in /etc/fstab

2008-06-25 Thread Michael Schuerig
Package: e2fsprogs
Version: 1.40.11-1
Severity: normal

On startup, fsck -A, called from /etc/init.d/checkfs.sh, apparently tries to 
check all filesystems listed in /etc/fstab, including those with option noauto. 
I have an external USB-disk for backups and since some recent update, I get 
consistently dropped to the maintenance console on startup, no matter if the 
disk is powered on or not.

In /etc/fstab I have

LABEL=rsnapshot /usr/var/cache/rsnapshotauto
noauto,ro,user,noatime,nodiratime   0   2

and I also tried

UUID=ea5196c8-ee9a-4297-9bfc-42148eb82c30 /usr/var/cache/rsnapshot auto
noauto,ro,user,noatime,nodiratime   0   2

Both, label and uuid, are correctly mapped to /dev/sdb1 in /etc/blkid.tab. 
Nevertheless, I get the following error message in /var/log/fsck/checkfs

Log of fsck -C -V -R -A -a
Wed Jun 25 08:09:23 2008

fsck 1.40.11 (17-June-2008)
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /usr/var/cache/rsnapshot] fsck.ext3 -a -C0 /dev/sdb1
fsck.ext3: No such file or directory while trying to open /dev/sdb1
/dev/sdb1:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 device

fsck died with exit status 8

When the disk is attached and powered on, it might not be available yet, as the 
timestamp in /var/log/syslog indicates

Jun 25 08:10:22 debby kernel: sd 2:0:0:0: [sdb] Attached SCSI disk

At any rate, fsck should not try to check disk that aren't there.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages e2fsprogs depends on:
ii  e2fslibs  1.40.11-1  ext2 filesystem libraries
ii  libblkid1 1.40.11-1  block device id library
ii  libc6 2.7-12 GNU C Library: Shared libraries
ii  libcomerr21.40.11-1  common error description library
ii  libss21.40.11-1  command-line interface parsing lib
ii  libuuid1  1.40.11-1  universally unique id library

e2fsprogs recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#482388: grub-pc: grub-set-default has no effect, is probably obsolete

2008-05-22 Thread Michael Schuerig
Package: grub-pc
Version: 1.96+20080512-1
Severity: normal


grub-set-default no longer has any effect, it does write /boot/grub/default,
but that file is ignored by /usr/sbin/update-grub, which instead reads
defaults from /etc/default/grub.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages grub-pc depends on:
ii  debconf [debconf-2.0]1.5.22  Debian configuration management sy
ii  grub-common  1.96+20080512-1 GRand Unified Bootloader, version 
ii  libc62.7-11  GNU C Library: Shared libraries
ii  liblzo2-22.03-1  data compression library
ii  libncurses5  5.6+20080503-1  Shared libraries for terminal hand

grub-pc recommends no packages.

-- debconf information excluded



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#409386: tiger: Please add fusectl to skipped local filesystems

2007-02-02 Thread Michael Schuerig
Package: tiger
Version: 1:3.2.1-35
Severity: wishlist


Tiger complains about a fusectl filesystem with the following warning

--CONFIG-- [con010c] Filesystem 'fusectl' used by 'none' is not recognised as a 
local filesystem

fusectl just needs to be added to /usr/lib/tiger/systems/Linux/2/gen_mounts

Cheers,
Michael

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages tiger depends on:
ii  binutils2.17-3   The GNU assembler, linker and bina
ii  coreutils   5.97-5.3 The GNU core utilities
ii  debconf [debconf-2.0]   1.5.11   Debian configuration management sy
ii  diff2.8.1-11 File comparison utilities
ii  libc6   2.3.6.ds1-10 GNU C Library: Shared libraries
ii  net-tools   1.60-17  The NET-3 networking toolkit

Versions of packages tiger recommends:
ii  chkrootkit0.47-1 Checks for signs of rootkits on th
ii  exim4-daemon-light [mail-tran 4.63-17lightweight exim MTA (v4) daemon
ii  john  1.6-40 active password cracking tool

-- debconf information:
* tiger/mail_rcpt: root
* tiger/remove_mess: true
* tiger/policy_adapt:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#307051: Bash completion for rake

2005-04-30 Thread Michael Schuerig
Package: rake
Version: 0.5.3-1
Severity: wishlist
Tags: patch


Here's a bash completion function that adds command line completion 
for rake. It needs to be placed in /etc/bash_completion.d


_rake()
{
local cur prev rakef i

COMPREPLY=()
cur=${COMP_WORDS[COMP_CWORD]}
prev=${COMP_WORDS[COMP_CWORD-1]}
rakef=Rakefile

if [[ $prev == -f ]]; then
_filedir
return 0
fi

if [[ $cur == *=* ]]; then
prev=${cur/=*/}
cur=${cur/*=/}
if [[ $prev == --rakefile= ]]; then
_filedir -o nospace
return 0
fi
fi

if [[ $cur == -* ]]; then
COMPREPLY=( $( compgen -W '-n -H -I -N -P -q -f\
-r -s -T -t -h -v -V\
--dry-run --help '--libdir=' --nosearch --prereqs --quiet\
'--rakefile=' '--require=' --silent --tasks --trace --usage\
--verbose --version'\
-- $cur ))
else

for (( i=0; i  [EMAIL PROTECTED]; i++)); do
case ${COMP_WORDS[i]} in
-f)
eval rakef=${COMP_WORDS[i+1]}
break
;;
--rakefile=*|--rakefile\=*)
eval rakef=${COMP_WORDS[i]/*=/}
break
;;
esac
done

[ ! -f $rakef ]  return 0

COMPREPLY=( $( rake -s -f $rakef -T | \
awk -F ' ' '/^rake / { print $2 }' | \
command grep ^$cur ))

fi
}
[ -n ${have:-} ]  complete -F _rake $filenames rake


Cheers,
Michael

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11
Locale: LANG=POSIX, [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages rake depends on:
ii  ruby  1.8.2-1An interpreter of object-oriented 

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]