Bug#728582: bacula-sd on kFreeBSD: unable to use tape drive
Package: bacula
Version: 5.2.6+dfsg-9
Severity: important
Dear Maintainer and Developers,
bacula is unable to use tape drives on Debian kFreeBSD.
Using tape drives within bacula works with the Linux Kernel on amd64 and
sparc without any problem. Native FreeBSD with bacula works too.
bacula-sd is able to use disk storage without problems. But no tape drive.
This problem is only reproducable on kFreeBSD Systems!
The hardware works with kFreeBSD, I am able to use the tapedrive and the
changer with the mt, mtx and tar commands without problems.
Log of my test by hand:
root@vorlon:~# camcontrol devlist
IBM ULTRIUM-TD3 5BG2 at scbus0 target 5 lun 0 (sa0,pass0)
DELL PV-124T 0031at scbus0 target 5 lun 1 (pass1,ch0)
WDC WD1002FBYS-02A6B0 03.00C06 at scbus1 target 0 lun 0 (ada0,pass2)
WDC WD1002FBYS-02A6B0 03.00C06 at scbus2 target 0 lun 0 (ada1,pass3)
WDC WD30EFRX-68AX9N0 80.00A80at scbus3 target 0 lun 0 (ada2,pass4)
WDC WD30EFRX-68AX9N0 80.00A80at scbus4 target 0 lun 0 (ada3,pass5)
SAMSUNG SSD 830 Series CXM03B1Q at scbus6 target 0 lun 0 (ada4,pass6)
root@vorlon:~# mtx -f /dev/pass1 status
Storage Changer /dev/pass1:1 Drives, 16 Slots ( 0 Import/Export )
Data Transfer Element 0:Full (Storage Element 9 Loaded):VolumeTag = FZ0009L3
Storage Element 1:Full :VolumeTag=FZ0001L3
Storage Element 2:Full :VolumeTag=FZ0002L3
Storage Element 3:Full :VolumeTag=FZ0003L3
Storage Element 4:Full :VolumeTag=FZ0004L3
Storage Element 5:Full :VolumeTag=FZ0005L3
Storage Element 6:Full :VolumeTag=FZ0006L3
Storage Element 7:Full :VolumeTag=FZ0007L3
Storage Element 8:Full :VolumeTag=FZ0008L3
Storage Element 9:Empty
Storage Element 10:Full :VolumeTag=FZ0010L3
Storage Element 11:Full :VolumeTag=FZ0011L3
Storage Element 12:Full :VolumeTag=FZ0012L3
Storage Element 13:Full :VolumeTag=FZ0013L3
Storage Element 14:Full :VolumeTag=FZ0014L3
Storage Element 15:Full :VolumeTag=FZ0015L3
Storage Element 16:Full :VolumeTag=FZ0016L3
root@vorlon:~# mt -f /dev/nsa0 rewind
root@vorlon:~# mt -f /dev/nsa0 weof
root@vorlon:~# tar cvf /dev/nsa0 testfile20GB
testfile20GB
root@vorlon:~# mt -f /dev/nsa0 rewind
root@vorlon:~# tar tvf /dev/nsa0
-rw-r--r-- root/root 21474836480 2013-11-03 09:41 testfile20GB
root@vorlon:~#
root@vorlon:~# mt -f /dev/nsa0 rewind
root@vorlon:~# mt -f /dev/nsa0 weof
But when using the bacula tools, tape access fails:
root@vorlon:~# btape Drive-1
Tape block granularity is 1024 bytes.
btape: butil.c:290 Using device: Drive-1 for writing.
03-Nov 10:28 btape JobId 0: 3301 Issuing autochanger loaded? drive 0 command.
03-Nov 10:28 btape JobId 0: 3302 Autochanger loaded? drive 0, result is Slot
9.
btape: btape.c:477 open device Drive-1 (/dev/nsa0): OK
*test
=== Write, rewind, and re-read test ===
I'm going to write 1 records and an EOF
then write 1 records and an EOF, then rewind,
and re-read the data to verify that it is correct.
This is an *essential* feature ...
03-Nov 10:30 btape JobId 0: End of Volume at 0:0 on device Drive-1
(/dev/nsa0). Write of 64512 bytes got 0.
03-Nov 10:30 btape JobId 0: Error: Error writing final EOF to tape. This Volume
may not be readable.
dev.c:1557 ioctl MTWEOF error on Drive-1 (/dev/nsa0).
ERR=Eingabe-/Ausgabefehler.
btape: btape.c:1151 Error writing block to device.
*q
03-Nov 10:30 btape: ERROR in dev.c:1662 dev.c:1661 I/O function MTREW not
supported on this device.
^C
root@vorlon:~#
Content of /etc/bacula/bacula-sd.conf (only tape and autochanger related):
Autochanger {
Name = pv124t
Device = Drive-1
Description = LTO-3 Library Dell PowerVault 124T
Changer Device = /dev/pass1
Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
}
Device {
Description = LTO-3 Library Dell PowerVault 124T
Archive Device = /dev/nsa0
Fast Forward Space File = no
TWO EOF = yes
AutoChanger = yes
Device Type = Tape
Name = Drive-1
Media Type = LTO-3
Drive Index = 0
RandomAccess = no;
RemovableMedia = yes;
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = no;
# Offline On Unmount = no
Hardware End of Medium = yes
Backward Space Record = yes
Backward Space File = yes
Fast Forward Space File = yes
Forward Space File = yes
BSF at EOM = yes
Maximum File Size = 4GB
# Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# If you have smartctl, enable this, it has more info than tapeinfo
# Alert Command = sh -c 'smartctl -H -l error
Bug#728446: kFreeBSD: apcupsd unable to communicate with Back-UPS ES 700G via usb
Package: apcupsd Version: 3.14.10-2 Severity: important Dear Maintainer, apcupsd is unable to find any usb bus or device on kFreeBSD systems. The UPS Device is a Back-UPS ES 700 G. The UPS uses usb to communicate with apcupsd. On Linux systems everything works perfekt. Here is the output of apctest -d 1000: 2013-11-01 12:55:34 apctest 3.14.10 (13 September 2011) debian Checking configuration ... 0.000 apcupsd: apcconfig.c:799 After config scriptdir: /etc/apcupsd 0.000 apcupsd: apcconfig.c:800 After config pwrfailpath: /etc/apcupsd 0.000 apcupsd: apcconfig.c:801 After config nologinpath: /etc 0.000 apcupsd: newups.c:102 write_lock at drivers.c:208 0.000 apcupsd: drivers.c:210 Looking for driver: usb 0.000 apcupsd: drivers.c:214 Driver dumb is configured. 0.000 apcupsd: drivers.c:214 Driver apcsmart is configured. 0.000 apcupsd: drivers.c:214 Driver net is configured. 0.000 apcupsd: drivers.c:214 Driver usb is configured. 0.000 apcupsd: drivers.c:217 Driver usb found and attached. 0.000 apcupsd: newups.c:108 write_unlock at drivers.c:234 0.000 apcupsd: drivers.c:236 Driver ptr=0x431080 Attached to driver: usb sharenet.type = Network ShareUPS Disabled cable.type = USB Cable mode.type = USB UPS Driver Setting up the port ... usb_set_debug: Setting debugging level to 10 (on) 0.001 apcupsd: newups.c:102 write_lock at generic-usb.c:655 0.001 apcupsd: generic-usb.c:425 Initializing libusb 0.001 apcupsd: generic-usb.c:430 Found 0 USB busses 0.001 apcupsd: generic-usb.c:432 Found 0 USB devices 0.001 apcupsd: newups.c:108 write_unlock at generic-usb.c:671 apctest FATAL ERROR in generic-usb.c at line 674 Cannot find UPS device -- For a link to detailed USB trouble shooting information, please see http://www.apcupsd.com/support.html. 0.002 apcupsd: newups.c:102 write_lock at generic-usb.c:694 0.002 apcupsd: newups.c:108 write_unlock at generic-usb.c:701 apctest error termination completed Output of lsusb: Bus 000 Device 001: ID : Bus 001 Device 001: ID : Bus 002 Device 001: ID : Bus 003 Device 001: ID : Bus 004 Device 001: ID : Bus 005 Device 001: ID : Bus 003 Device 002: ID 0624:0248 Avocent Corp. Bus 002 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply Output of dmesg | tail -n 3 - ugen0.2: APC at usbus0 ugen0.2: APC at usbus0 (disconnected) ugen2.2: APC at usbus2 -- System Information: Debian Release: 7.2 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apcupsd depends on: ii libc0.1 2.13-38 ii libgcc1 1:4.7.2-5 ii libusb-0.1-4 2:0.1.12-20+nmu1 ii libwrap0 7.6.q-24 Versions of packages apcupsd recommends: ii apcupsd-doc 3.14.10-2 Versions of packages apcupsd suggests: ii apcupsd-cgi 3.14.10-2 pn udev none -- Configuration Files: /etc/apcupsd/apcupsd.conf changed: UPSNAME ES 700G UPSCABLE usb UPSTYPE usb DEVICE /dev/ugen2.2 LOCKFILE /var/lock SCRIPTDIR /etc/apcupsd PWRFAILDIR /etc/apcupsd NOLOGINDIR /etc ONBATTERYDELAY 6 BATTERYLEVEL 10 MINUTES 10 TIMEOUT 0 ANNOY 30 ANNOYDELAY 60 NOLOGON disable KILLDELAY 0 NETSERVER on NISIP 0.0.0.0 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 10 UPSCLASS standalone UPSMODE disable STATTIME 0 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 0 /etc/apcupsd/hosts.conf changed: MONITOR 192.168.0.12 meteohub.athome MONITOR 192.168.0.33 proliant.athome MONITOR 192.168.0.39 vorlon.athome /etc/default/apcupsd changed: APCACCESS=/sbin/apcaccess ISCONFIGURED=yes -- 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#696629: uptimed on kFreeBSD fails to keep stats on reboot
Package: uptimed Version: 1:0.3.17-3.1 Severity: normal Dear Maintainer, I use uptimed/uprecords on different machines with different architectures. With Linux everything works as expected. With kFreeBSD the statistics seems to be frozen. The first record is persistent after a reboot. The actual running time does not survive a reboot. Example: fz@vorlon:~$ uprecords # Uptime | System Boot up +--- - 1 0 days, 16:47:29 | GNU/kFreeBSD 9.0-2-amd64 Sun Dec 23 21:09:01 2012 2 0 days, 00:20:00 | GNU/kFreeBSD 9.0-2-amd64 Tue Nov 6 19:38:46 2012 +--- NewRec 0 days, 16:27:28 | since Sun Dec 23 21:29:01 2012 up 0 days, 17:07:29 | since Tue Nov 6 19:38:46 2012 down47 days, 01:10:15 | since Tue Nov 6 19:38:46 2012 %up1.494 | since Tue Nov 6 19:38:46 2012 This #2 record is highest running time after every reboot. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages uptimed depends on: ii debconf [debconf-2.0] 1.5.48 ii dpkg 1.16.9 ii libc0.12.13-37 ii libuptimed01:0.3.17-3.1 ii lsb-base 4.1+Debian8 uptimed recommends no packages. uptimed suggests no packages. -- debconf information: uptimed/mail/do_mail: Never uptimed/mail/address: root@localhost uptimed/mail/milestones_info: uptimed/maxrecords: 50 uptimed/interval: 60 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577692: iw reg set regioncode does not work with Atheros AR2413 on squeeze
Package: iw Version: 0.9.14-1 Severity: normal My Alix 6E2 embedded board is equipped with an Atheros AR2413 miniPCI wireless card. At system boot and every time I try do load the kernel modules using modprobe ath5k I can only use the default US frequency settings. When I try to set the regularity settings with iw like this everything is unchanged: alix6:~# iw reg get country US: (2402 - 2472 @ 40), (6, 27) (5170 - 5190 @ 40), (6, 23) (5190 - 5210 @ 40), (6, 23) (5210 - 5230 @ 40), (6, 23) (5230 - 5330 @ 40), (6, 23) (5735 - 5835 @ 40), (6, 30) alix6:~# iw reg set DE alix6:~# iw reg get country US: (2402 - 2472 @ 40), (6, 27) (5170 - 5190 @ 40), (6, 23) (5190 - 5210 @ 40), (6, 23) (5210 - 5230 @ 40), (6, 23) (5230 - 5330 @ 40), (6, 23) (5735 - 5835 @ 40), (6, 30) I always get the old US settings. No way to change it. Then I tried to load the module cfg80211 with module options as shown below with regulatory settings EU and this succeeded. But still no way to set the region using iw reg set regioncode --- contents of /etc/modprobe.d/cfg80211.conf options cfg80211 ieee80211_regdom=EU -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.32-3-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages iw depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libnl11.1-5 library for dealing with netlink s iw recommends no packages. iw suggests no packages. -- no debconf information -- output of lspci 00:01.0 Host bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion] Host Bridge (rev 33) 00:01.2 Entertainment encryption device: Advanced Micro Devices [AMD] Geode LX AES Security Block 00:09.0 Ethernet controller: VIA Technologies, Inc. VT6105M [Rhine-III] (rev 96) 00:0a.0 Ethernet controller: VIA Technologies, Inc. VT6105M [Rhine-III] (rev 96) 00:0c.0 Ethernet controller: Atheros Communications Inc. AR2413 802.11bg NIC (rev 01) 00:0f.0 ISA bridge: Advanced Micro Devices [AMD] CS5536 [Geode companion] ISA (rev 03) 00:0f.2 IDE interface: Advanced Micro Devices [AMD] CS5536 [Geode companion] IDE (rev 01) 00:0f.4 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] OHC (rev 02) 00:0f.5 USB Controller: Advanced Micro Devices [AMD] CS5536 [Geode companion] EHC (rev 02) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#577692: Bug 577692: Output of strace iw reg set DE
Maybe this is helpful ...
alix6:~# strace iw reg set DE
execve(/usr/bin/iw, [iw, reg, set, DE], [/* 12 vars */]) = 0
brk(0) = 0x9e99000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb77b7000
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=21094, ...}) = 0
mmap2(NULL, 21094, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb77b1000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/usr/lib/libnl.so.1, O_RDONLY) = 3
read(3, \177elf\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\...@\374\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=279280, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb77b
mmap2(NULL, 278268, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb776c000
mmap2(0xb77ad000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x41) = 0xb77ad000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260l\1\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1331496, ...}) = 0
mmap2(NULL, 1337704, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb7625000
mmap2(0xb7766000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x141) = 0xb7766000
mmap2(0xb7769000, 10600, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_ANONYMOUS, -1, 0) = 0xb7769000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
directory)
open(/lib/libm.so.6, O_RDONLY)= 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`4\0\0004\0\0\0...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=149392, ...}) = 0
mmap2(NULL, 151680, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xb75ff000
mmap2(0xb7623000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x23) = 0xb7623000
close(3)= 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb75fe000
set_thread_area({entry_number:-1 - 6, base_addr:0xb75fe6c0, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}) = 0
mprotect(0xb7623000, 4096, PROT_READ) = 0
mprotect(0xb7766000, 8192, PROT_READ) = 0
mprotect(0xb77d5000, 4096, PROT_READ) = 0
munmap(0xb77b1000, 21094) = 0
brk(0) = 0x9e99000
brk(0x9eba000) = 0x9eba000
open(/proc/net/psched, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb77b6000
read(3, 03e8 0040 000f4240 0..., 1024) = 36
close(3)= 0
munmap(0xb77b6000, 4096)= 0
time(NULL) = 1271179881
getpid()= 3216
socket(PF_NETLINK, SOCK_RAW, 16)= 3
setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
setsockopt(3, SOL_SOCKET, SO_RCVBUF, [32768], 4) = 0
bind(3, {sa_family=AF_NETLINK, pid=3216, groups=}, 12) = 0
getsockname(3, {sa_family=AF_NETLINK, pid=3216, groups=}, [12]) = 0
sendmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\20\0\5\3i\252\304K\220\f\0\0\3\1\0\0, 20}],
msg_controllen=0, msg_flags=0}, 0) = 20
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{t\0\0\0\20\0\2\0i\252\304K\220\f\0\0\1\2\0\0\v\0\2\0nlctrl\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 1228
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\24\0\0\0\3\0\2\0i\252\304K\220\f\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 20
sendmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{\34\0\0\0\24\0\5\0j\252\304K\220\f\0\0\33\0\0\0\7\0!\0DE\0\0,
28}], msg_controllen=0, msg_flags=0}, 0) = 28
recvmsg(3, {msg_name(12)={sa_family=AF_NETLINK, pid=0, groups=},
msg_iov(1)=[{$\0\0\0\2\0\0\0j\252\304K\220\f\0\0\0\0\0\0\34\0\0\0\24\0\5\0j\252\304K...,
4096}], msg_controllen=0, msg_flags=0}, 0) = 36
close(3)= 0
exit_group(0) = ?
alix6:~#
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517796: linux-image-2.6-amd64-etchnhalf: Firewire-HDD doesn't work and md can't get assembled
Package: linux-image-2.6-amd64-etchnhalf Severity: normal With the 2.6.18-6 Kernel in Etch the System is running perfectly. After installing the Etch'n'half-kernel the system fails to boot with this kernel. Current setup: /dev/md0 as /boot (RAID1) /dev/md1 as PV for LVM (RAID1) /dev/md2 as PV for LVM (RAID5) miraculix:~# pvs vgs lvs pvs PV VGFmt Attr PSize PFree pvs /dev/md1 miraculix lvm2 a-67,88G 33,44G pvs /dev/md2 datensilo lvm2 a- 931,52G 65,52G vgs VG#PV #LV #SN Attr VSize VFree vgs datensilo 1 4 0 wz--n- 931,52G 65,52G vgs miraculix 1 5 0 wz--n- 67,88G 33,44G lvs LVVGAttr LSize Origin Snap% Move Log Copy% lvs home datensilo -wi-ao 750,00G lvs repositorydatensilo -wi-ao 100,00G lvs sambaprofiles datensilo -wi-ao 5,00G lvs www datensilo -wi-ao 11,00G lvs root miraculix -wi-ao 2,44G lvs swap miraculix -wi-ao 6,00G lvs temp miraculix -wi-ao 1,00G lvs usr miraculix -wi-ao 15,00G lvs var miraculix -wi-ao 10,00G All the required files to start the system are located on RAID1. When the system tries to boot, the assembly of all md-devices fails and the kernel is unable to communicate with the firewire-HDD usually used as medium for BackupPC. -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
