Bug#1074250: ifupdown2 not working with python3.12
Package: ifupdown2 Version: 3.0.0-1.2 Followup-For: Bug #1074250 Issue still exists inn the -1.2 version. Bug is fixed in commit https://github.com/CumulusNetworks/ifupdown2/commit/fc0318378e878ffe639d1d1285936d1256dd67cf, but not included in package. -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500, 'testing'), (500, 'oldstable'), (100, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.9.7-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown2 depends on: ii iproute2 6.9.0-1 ii python3 3.12.3-1 ifupdown2 recommends no packages. Versions of packages ifupdown2 suggests: ii bridge-utils 1.7.1-2 pn ethtool ii isc-dhcp-client 4.4.3-P1-5 pn python3-gvgen pn python3-mako -- no debconf information
Bug#1074250: ifupdown2: PR offered to maintainers for merge
Package: ifupdown2 Version: 3.0.0-1.1 Followup-For: Bug #1074250 I found this bug yesterday on my systems, it was reported upstream on 4-4-2024, maintainer asked for a pull request so it could be patched but it was never offered. The maintainer just got a pull request by me to patch this issue. Please incorporate the patch into the package and update. -- System Information: Debian Release: trixie/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500, 'testing'), (500, 'oldstable'), (100, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.9.7-amd64 (SMP w/32 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown2 depends on: ii iproute2 6.9.0-1 ii python3 3.12.2-1 ifupdown2 recommends no packages. Versions of packages ifupdown2 suggests: ii bridge-utils 1.7.1-2 pn ethtool ii isc-dhcp-client 4.4.3-P1-5 pn python3-gvgen pn python3-mako -- no debconf information
Bug#1027010: (no subject)
> > I will install it from unstable manually. Thanks for the hint! > Installing libtfm1 0.13.1-1 made it indeed work again. I just tried installing libtfm1 and get 0.13-4.1 (arm64) and this doesn't solve the issue. The only thing that works here is a downgrade to 0.103.7+dfsg-0+deb11u1 . -- Jan Huijsmans b...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#1027130: libclamav9: LibClamAV Error: Can't verify database integrity
Package: libclamav9 Version: 0.103.7+dfsg-1+b2 Severity: grave Justification: renders package unusable Dear Maintainer, Upgrade of package and related clamav packages to 0.103.7+dfsg-1+b2 resulted in an inability to verify the clamav database daily.cvd (1st it tries). Dodngrade of packages clamav-daemon and clamav-freshclam didn't dolve the issue, libclamav9 needed to be downgraded to 0.103.7+dfsg-0+deb11u1 to be able to start clamab-daemon again. Errors in syslog: LibClamAV Error: Can't load /var/lib/clamav/daily.cvd: Can't verify database integrity LibClamAV Error: cli_loaddbdir(): error loading database /var/lib/clamav/daily.cvd Please put the 0.103.7+dfsg-1+b2 version in sid on hold, as it breaks clamav, allowing virusses to get past the scanner... Regards, Jan Huijsmans -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (100, 'stable'), (50, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 6.0.0-6-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages libclamav9 depends on: ii libbz2-1.01.0.8-5+b1 ii libc6 2.36-6 ii libcurl4 7.86.0-2 ii libjson-c50.16-2 ii libltdl7 2.4.7-5 ii libmspack00.10.1-2 ii libpcre2-8-0 10.40-3 ii libssl3 3.0.7-1 ii libtfm1 0.13-4.1 ii libxml2 2.9.14+dfsg-1.1+b2 ii zlib1g1:1.2.13.dfsg-1 libclamav9 recommends no packages. Versions of packages libclamav9 suggests: pn libclamunrar pn libclamunrar9 -- no debconf information
Bug#1023123: linux-image-5.19.0-1-arm64: RPi3 fails to boot when headless
Package: linux-image-5.19.0-1-arm64 Severity: critical Justification: breaks the whole system Dear Maintainer, After upgrading from linux-image-5.18.0-4-arm64 to linux-image-5.19.0-1-arm64 the RPi model 3Bs I have in use headless refuse to boot. The moment you boot the RPi with screen to check what's happening, it boots. This issue is for all Raspberry Pi 3 Model B Rev 1.2 devices I have active. Both RPi 4s run without issue when headless. Issue found in all kernels > 5.18, only way to solve this is to revert back to the 5.18 kernel by editing the config.txt on the firmware partition. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: arm64 (aarch64) Kernel: Linux 5.18.0-4-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#991714: linux-image-5.10.0-8-arm64: RPi 4 (8 GB) - CPU stuck in highest speed
Package: src:linux Version: 5.10.46-3 Severity: critical Justification: breaks the whole system Dear Maintainer, Looking into the instability of my RPi 4 (8GB) showed the CPU constantly in the highest clock setting with a load of 0 and 99.5%+ idle state. The instability was 1st discovered after updates in januari, but unable to get researched until now. (so no clue which kernel version triggered it, I expect a 5.x kernel, as on 4.9 it was stable) I tried setting the default govenour (performance, tad optimistic for an arm) to ondemand, powersave and schedutil and install cpufreqd, but cpufreqd reports no cpufreq support. The CPU reports to be full-time in the highest speed. Only way to limit the highest speed is to set arm_freq in /boot/firmware/config.txt to a lower max cpu freq. (testing with 1000 now) Running fulltime at 1500 MHz causes the device to crash several times a day. (housing is very hot) I expected the CPU to run in the lowest speed most of the time, as it's almost fulltime idle. Somehow the kernel doesn't use the governor setting. The issue is not seen on my RPi3 systems (same kernel, same config, gouvenour defaults to schedutil there), so I'd guess it's either an RPi4 or specifically a specific RPi 4 8 GB issue. -- Package-specific info: ** Version: Linux version 5.10.0-8-arm64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-3 (2021-07-28) ** Command line: video=HDMI-A-1:1280x1024M@60 dma.dmachans=0x37f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x5e78c29f bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:B8:7F:26 vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 console=tty0 console=ttyS1,115200 root=/dev/sda1 rw fsck.repair=yes net.ifnames=0 rootwait ** Tainted: C (1024) * staging driver was loaded ** Kernel log: [ 22.247985] mc: Linux media interface: v0.10 [ 22.260008] bcm2835_audio bcm2835_audio: card created with 8 channels [ 22.313119] videodev: Linux video capture interface: v2.00 [ 22.328566] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 22.330090] usbcore: registered new interface driver brcmfmac [ 22.357834] debugfs: Directory 'fef00700.hdmi' with parent 'vc4-hdmi-0' already present! [ 22.359215] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.bin [ 22.362740] cryptd: max_cpu_qlen set to 1000 [ 22.364355] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt [ 22.368338] vc4-drm gpu: bound fef00700.hdmi (ops vc4_hdmi_ops [vc4]) [ 22.368822] debugfs: Directory 'fef05700.hdmi' with parent 'vc4-hdmi-1' already present! [ 22.373047] vc4-drm gpu: bound fef05700.hdmi (ops vc4_hdmi_ops [vc4]) [ 22.373234] vc4-drm gpu: bound fe40.hvs (ops vc4_hvs_ops [vc4]) [ 22.373552] vc4-drm gpu: bound fe004000.txp (ops vc4_txp_ops [vc4]) [ 22.373680] vc4-drm gpu: bound fe206000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 22.373784] vc4-drm gpu: bound fe207000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 22.373889] vc4-drm gpu: bound fe20a000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 22.373962] vc4-drm gpu: bound fe216000.pixelvalve (ops vc4_crtc_ops [vc4]) [ 22.374258] checking generic (3e6c7000 50) vs hw (0 ) [ 22.374264] fb0: switching to vc4drmfb from simple [ 22.375966] Console: switching to colour dummy device 80x25 [ 22.380163] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 22.405236] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. [ 22.411921] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 0 [ 22.498091] Adding 8388948k swap on /dev/sda2. Priority:-2 extents:1 across:8388948k FS [ 22.498288] Console: switching to colour frame buffer device 160x64 [ 22.530659] vc4-drm gpu: [drm] fb0: vc4drmfb frame buffer device [ 22.533470] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 22.534245] brcmfmac mmc0:0001:1: firmware: direct-loading firmware brcm/brcmfmac43455-sdio.clm_blob [ 22.539177] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Sep 18 2020 02:27:58 version 7.45.221 (3a6d3a0 CY) FWID 01-bbd9282b [ 22.756347] Bluetooth: Core ver 2.22 [ 22.756479] NET: Registered protocol family 31 [ 22.756484] Bluetooth: HCI device and connection manager initialized [ 22.756799] Bluetooth: HCI socket layer initialized [ 22.756811] Bluetooth: L2CAP socket layer initialized [ 22.756839] Bluetooth: SCO socket layer initialized [ 22.796142] Bluetooth: HCI UART driver ver 2.3 [ 22.796159] Bluetooth: HCI UART protocol H4 registered [ 22.796255] Bluetooth: HCI UART protocol LL registered [ 22.796259] Bluetooth: HCI UART protocol ATH3K registered [ 22.796309] Bluetoot
Bug#984873: linux-image-5.10.0-4-arm64: RPi4 8 GB lost USB support (doesn't start with / on USB device)
Package: src:linux Version: 5.10.19-1 Severity: critical Justification: breaks the whole system Dear Maintainer, Updating from linux-image-5.9.0-4-arm64 to linux-image-5.10.0-3/4-arm64 resulted in a non-booting system due to missing/incorrect USB support for the RPi4 8GB. (system has / on USB SSD) Only method to get the system booting again is to change config.txt to boot the available 5.9.0-4 kernel. System came up as expected. With the 5.10 kernels I tested (-3 and -4 packages) the boot halted after detecting the partitions on mmcblk1 , on 5.9.0-4 it continues to detect the storange via USB and boots from it. Regards, Jan Huijsmans -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information Device Tree model: Raspberry Pi 4 Model B Rev 1.4 ** PCI devices: not available ** USB devices: Bus 002 Device 002: ID 0578:0578 Intrinsix Corp. KingSpec Z3-128 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard SK-8115 Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (1001, 'testing'), (100, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.9.0-4-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.10.0-4-arm64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.139 ii kmod28-1 ii linux-base 4.6 Versions of packages linux-image-5.10.0-4-arm64 recommends: ii apparmor 2.13.6-9 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.10.0-4-arm64 suggests: pn debian-kernel-handbook pn linux-doc-5.10 Versions of packages linux-image-5.10.0-4-arm64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x ii firmware-brcm8021120210208-3 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree pn firmware-misc-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
Bug#972454: Confirmed fix 2.13-1 on aarch64
Thanks for the fix Jeremy. Sorry I couldn't test sooner. I see unstable has been updated to 2.13-1 and I can confirm the package now installs correctly with a 5.9 kernel on aarch64 (correct arch name instead of arm64). --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#972454: Bug confirmed on arm64 as well
Hi, Was preparing a report for this bug when I found it already logged. Yesterday I found this issue as wel on arm64. Solution: Build 3.11 from source. Attachement: make.log --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server DKMS make.log for xtables-addons-3.9 for kernel 5.9.0-2-arm64 (aarch64) Tue Nov 17 08:02:58 CET 2020 make: Entering directory '/usr/src/linux-headers-5.9.0-2-arm64' make -C /usr/src/linux-headers-5.9.0-2-arm64 -f /usr/src/linux-headers-5.9.0-2-common/Makefile modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) make -f /usr/src/linux-headers-5.9.0-2-common/scripts/Makefile.build obj=/var/lib/dkms/xtables-addons/3.9/build/extensions \ single-build= \ need-builtin=1 need-modorder=1 make -f /usr/src/linux-headers-5.9.0-2-common/scripts/Makefile.build obj=/var/lib/dkms/xtables-addons/3.9/build/extensions/ACCOUNT \ \ need-builtin= \ need-modorder=1 make -f /usr/src/linux-headers-5.9.0-2-common/scripts/Makefile.build obj=/var/lib/dkms/xtables-addons/3.9/build/extensions/pknock \ \ need-builtin= \ need-modorder=1 gcc-10 -Wp,-MMD,/var/lib/dkms/xtables-addons/3.9/build/extensions/.compat_xtables.o.d -nostdinc -isystem /usr/lib/gcc/aarch64-linux-gnu/10/include -I/usr/src/linux-headers-5.9.0-2-common/arch/arm64/include -I./arch/arm64/include/generated -I/usr/src/linux-headers-5.9.0-2-common/include -I./include -I/usr/src/linux-headers-5.9.0-2-common/arch/arm64/include/uapi -I./arch/arm64/include/generated/uapi -I/usr/src/linux-headers-5.9.0-2-common/include/uapi -I./include/generated/uapi -include /usr/src/linux-headers-5.9.0-2-common/include/linux/kconfig.h -include /usr/src/linux-headers-5.9.0-2-common/include/linux/compiler_types.h -D__KERNEL__ -mlittle-endian -DCC_USING_PATCHABLE_FUNCTION_ENTRY -DKASAN_SHADOW_SCALE_SHIFT=3 -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mgeneral-regs-only -DCONFIG_CC_HAS_K_CONSTRAINT=1 -fno-asynchronous- unwind-tables -Wno-psabi -mabi=lp64 -mbranch-protection=pac-ret+leaf+bti -Wa,-march=armv8.4-a -DARM64_ASM_ARCH='"armv8.4-a"' -DKASAN_SHADOW_SCALE_SHIFT=3 -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=2048 -fstack-protector-strong -Wno-unused-but-set-variable -Wimplicit-fallthrough -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-var-tracking-assignments -g -fpatchable-function-entry=2 -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -fno-strict-overflow -fno-merge-all-constants -fmerge-constants -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -fmacro-prefix-map=/usr/src/linux-headers-5.9.0-2-common/= -Wno-packed-not-aligned -m stack-protector-guard=sysreg -mstack-protector-guard- reg=sp_el0 -mstack-protector-guard-offset=1272 -DMODULE -DKBUILD_BASENAME='"compat_xtables"' -DKBUILD_MODNAME='"compat_xtables"' -c -o /var/lib/dkms/xtables-addons/3.9/build/extensions/compat_xtables.o /var/lib/dkms/xtables-addons/3.9/build/extensions/compat_xtables.c gcc-10 -Wp,-MMD,/var/lib/dkms/xtables-addons/3.9/build/extensions/.xt_CHAOS.o.d -nostdinc -isystem /usr/lib/gcc/aarch64-linux-gnu/10/include -I/usr/src/linux-headers-5.9.0-2-common/arch/arm64/include -I./arch/arm64/include/generated -I/usr/src/linux-headers-5.9.0-2-common/include -I./include -I/usr/src/linux-headers-5.9.0-2-common/arch/arm64/include/uapi -I./arch/arm64/include/generated/uapi -I/usr/src/linux-headers-5.9.0-2-common/include/uapi -I./include/generated/uapi -include /usr/src/linux-headers-5.9.0-2-common/include/linux/kconfig.h -include /usr/src/linux-headers-5.9.0-2-common/include/linux/compiler_types.h -D__KERNEL__ -mlittle-endian -DCC_USING_PATCHABLE_FUNCTION_ENTRY -DKASAN_SHADOW_SCALE_SHIFT=3 -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Wno-format-security -std=gnu89 -mgeneral-regs-only -DCONFIG_CC_HAS_K_CONSTRAINT=1 -fno-asynchronous-unwind -tables -Wno-psabi -mabi=lp64 -mbranch-protection=pac-ret+leaf+bti -Wa,-march=ar
Bug#947352: python-pyqt5.qtwebengine: No install candidate in raspbian stretch/buster/bullseye/sid
Package: python-pyqt5.qtwebengine Version: 5.11.3+dfsg-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Unknown * What exactly did you do (or not do) that was effective (or ineffective)? Apt-get dist-upgrade -> uninstall calibre and install puthon-qt5 packages Work around: apt-get upgrade and leave rest of the packages at old level. * What was the outcome of this action? Apt-get dist-upgrade wants to uninstall calibre as it wants to upgrade python-gt5 packages and this package isn't available in raspbian. * What outcome did you expect instead? Correct upgrade of all installed packages, including calibre. Calibre upgrad e would be from 4.0.0+really3.48.dfsg-1 to 4.6.0+dfsg-1 This is probably a raspbian only issue or a calibre dependency that should be fixed. *** End of the template - remove these template lines *** -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux bullseye/sid Release:oldstable Codename: sid Architecture: armv7l Kernel: Linux 4.19.57-v7+ (SMP w/4 CPU cores) Kernel taint flags: TAINT_CRAP Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#934350: Debug make.log
ASENAME='"xt_pknock"' -DKBUILD_MODNAME='"xt_pknock"' -c -o /var/lib/dkms/xtables-addons/3.2/build/extensions/pknock/xt_pknock.o /var/lib/dkms/xtables-addons/3.2/build/extensions/pknock/xt_pknock.c /var/lib/dkms/xtables-addons/3.2/build/extensions/pknock/xt_pknock.c: In function 'xt_pknock_mt_init': /var/lib/dkms/xtables-addons/3.2/build/extensions/pknock/xt_pknock.c:1128:13: error: 'struct shash_desc' has no member named 'flags' crypto.desc.flags = 0; ^ make[4]: *** [/usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build:290: /var/lib/dkms/xtables-addons/3.2/build/extensions/pknock/xt_pknock.o] Error 1 make[3]: *** [/usr/src/linux-headers-5.2.0-2-common/scripts/Makefile.build:494: /var/lib/dkms/xtables-addons/3.2/build/extensions/pknock] Error 2 make[2]: *** [/usr/src/linux-headers-5.2.0-2-common/Makefile:1610: _module_/var/lib/dkms/xtables-addons/3.2/build/extensions] Error 2 make[1]: *** [Makefile:179: sub-make] Error 2 make: *** [Makefile:8: all] Error 2 make: Leaving directory '/usr/src/linux-headers-5.2.0-2-amd64' --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#749991: A tiresome subject for YEARS.
On Mon, 11 Feb 2019 15:21:12 +0100 Jan Huijsmans wrote: > Sorry for the spam, PEBKAC, wront netboot.tar.gz. (wget renamed as the > old one from just after 4.19.0-2 kernel update was still there) > > Linking kernel + netboot update would be great though, or is there a > standard delay of a day or 2? I shouldn't do this mailing thing when I'm tired... :( PEBKAC on the PEBKAC report, issue still exists, the netboot.tar.gz just downloaded for amd64 (timestamp on server ftp.nl.debian.org 19-01-2019 18:03) contains kernel 4.19.0-1-amd64 (4.19.12 (2018-12-22)) but the repo has 4.19.0-2-amd64 (4.19.16-1 (2019-01-17)). When I look at the date of the netboot.tar.gz upload, it should be able to have the new kernel, but it hasn't. The file I use is downloaded from: http://ftp.nl.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/ The source (I guess) is at: http://ftp.debian.org/debian/dists/buster/main/installer-amd64/current/images/netboot/ and has timestamp 2019-01-18 20:43. --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#749991: A tiresome subject for YEARS.
On Mon, 11 Feb 2019 15:17:04 +0100 Jan Huijsmans wrote: > On Thu, 25 Oct 2018 15:09:31 +0200 Oliver Riesener > wrote: > > On 10/25/18 11:06 AM, Oliver Riesener wrote: > > > On 10/25/18 1:45 AM, Ben Hutchings wrote: > > >> On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz > > >> wrote: > > >>> On 10/24/18 6:42 PM, Oliver Riesener wrote: > > >>>> No unetbootin, it’s the stock stretch netboot installation. > > >>>> initrd kernel from actual > > >>>> Debian9.5/…./amd64/netboot/netboot.tar.gz didn’t find kernel > > >>>> modules anymore. The old one before too. It’s a point release > > >>>> problem. Older versions of modules (.udeb ?) seems > > >>>> to be from debian repo. > > >>> Are you sure you used a matching kernel image and initrd? Both > > >>> have to match > > >>> their version otherwise it won't work. > > >> But when you use netboot the udebs in the archive *also* have to > > >> match. And they don't after a point release. > > >> > > >> Ben. > > > Yes, that's the point. Packages are updated, today it runs perfect > > > again. > > Oh, i am sorry, i got the issue yesterday with jessie 8.0 point > > release, becource > > my (old) bootp entry points to 8.0/pxelinux.0. > > > > Upgraded to jessie/current/netboot image, works also fine. > > The problem exists again with the buster netboot.tar.gz from the > server (just downloaded). The available netboot.tar.gz still contains > the 4.19.0-1 kernel, while the 4.19.0-2 is the only one available in > the repo. > > Would it be possible to update the netboot.tar.gz for the arch the > moment the updated kernel is being added in the repo. (or leave the > old kernel with modules in the repo until the netboot.tar.gz is > updated) > > I expect the generation of the tars is automated, so it would be nice > if the kernel and tar update can be linked. Sorry for the spam, PEBKAC, wront netboot.tar.gz. (wget renamed as the old one from just after 4.19.0-2 kernel update was still there) Linking kernel + netboot update would be great though, or is there a standard delay of a day or 2? --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#749991: A tiresome subject for YEARS.
On Thu, 25 Oct 2018 15:09:31 +0200 Oliver Riesener wrote: > On 10/25/18 11:06 AM, Oliver Riesener wrote: > > On 10/25/18 1:45 AM, Ben Hutchings wrote: > >> On Wed, 2018-10-24 at 18:44 +0200, John Paul Adrian Glaubitz wrote: > >>> On 10/24/18 6:42 PM, Oliver Riesener wrote: > >>>> No unetbootin, it’s the stock stretch netboot installation. > >>>> initrd kernel from actual > >>>> Debian9.5/…./amd64/netboot/netboot.tar.gz didn’t find kernel > >>>> modules anymore. The old one before too. It’s a point release > >>>> problem. Older versions of modules (.udeb ?) seems > >>>> to be from debian repo. > >>> Are you sure you used a matching kernel image and initrd? Both > >>> have to match > >>> their version otherwise it won't work. > >> But when you use netboot the udebs in the archive *also* have to > >> match. And they don't after a point release. > >> > >> Ben. > > Yes, that's the point. Packages are updated, today it runs perfect > > again. > Oh, i am sorry, i got the issue yesterday with jessie 8.0 point > release, becource > my (old) bootp entry points to 8.0/pxelinux.0. > > Upgraded to jessie/current/netboot image, works also fine. The problem exists again with the buster netboot.tar.gz from the server (just downloaded). The available netboot.tar.gz still contains the 4.19.0-1 kernel, while the 4.19.0-2 is the only one available in the repo. Would it be possible to update the netboot.tar.gz for the arch the moment the updated kernel is being added in the repo. (or leave the old kernel with modules in the repo until the netboot.tar.gz is updated) I expect the generation of the tars is automated, so it would be nice if the kernel and tar update can be linked. --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#892737: [Pkg-puppet-devel] Bug#892737: Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'
On Tue, 13 Mar 2018 13:25:25 +0100 Jan Huijsmans wrote: > On Tue, 13 Mar 2018 10:28:49 +0100 Georg Faerber > wrote: > > On 18-03-13 10:36:34, Apollon Oikonomopoulos wrote: > > Yeah.. Thanks for your work, too! I like teamwork a lot! :) > Thanks, will test as soon as I get it, ruby-gettext-setup was pulled > in with r10k, so I now also know how I got it. (and that it's a > requirement for r10k package) Can confirm the bug is fixed. Thanks for the very quick fix. --- Jan Huijsmans b...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#892737: [Pkg-puppet-devel] Bug#892737: Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'
On Tue, 13 Mar 2018 10:28:49 +0100 Georg Faerber wrote: > On 18-03-13 10:36:34, Apollon Oikonomopoulos wrote: > Yeah.. Thanks for your work, too! I like teamwork a lot! :) Thanks, will test as soon as I get it, ruby-gettext-setup was pulled in with r10k, so I now also know how I got it. (and that it's a requirement for r10k package) --- Jan Huijsmans b...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server
Bug#892737: [Pkg-puppet-devel] Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'
Hi Apollon, On Mon, 12 Mar 2018 13:57:03 +0200 Apollon Oikonomopoulos wrote: > Hi, > > Thanks for the report, > > On 12:33 Mon 12 Mar , Jan Huijsmans wrote: > > Would love tips on how to get this setup working or downgrade back > > to 4.10.4. > > I'll have a look at the issue as soon as possible. In the meantime, > you can obtain 4.10.4 from > http://snapshot.debian.org/package/puppet/4.10.4-2/ Thanks for the link, great to be able to get the packages. Reinstalled the old version and everything works again as expected. I'll compare the debian (a few clients) and the raspbian (puppet-master) to see if I can find differences. Iy looks like gettext(-setup) is a dependency. (but have it installed and it gives the error) Regards, Jan
Bug#892737: puppet: /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain'
Package: puppet Version: 5.4.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** Situation: My puppet environment broke after dist-upgrade of buster, changing puppet related packages from 4.10.4-2 to 5.4.0-1. (date 2018-03-02) All action from the clients that connect to the master (passenger mode) fail with error: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: undefined method `chain' for # Trying a clean install of 5.4.0-1 results in the error below when trying to regenerate the certs: puppet cert generate trillian --allow-dns-alt-names --debug --verbose Traceback (most recent call last): 4: from /usr/bin/puppet:5:in `' 3: from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:73:in `execute' 2: from /usr/lib/ruby/vendor_ruby/puppet/util/command_line.rb:126:in `run' 1: from /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:70:in `reset_text_domain' /usr/lib/ruby/vendor_ruby/puppet/gettext/config.rb:156:in `copy_default_translations': undefined method `chain' for # (NoMethodError) Reinstall was attempted to see if some config had changed, which it didn't. Tested with personal configuration as well as clean setup. At the moment puppet naster operations fail, regeneration of cert fails. Can't test more, as I need a working puppet-master setup for this. Did an update of all gems to see if this would help, no result. (debian packages of all gems were up-to-date as well) Downgrade to 4.10 is not possible, as it's not obtainable anumore, 4.8 in stable is to old as I need 4.9 or 4.10 due to functionality I've installed in my puppet code. Would love tips on how to get this setup working or downgrade back to 4.10.4. Looks like a dependency is missing in the 5.4 package. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux testing (buster) Release:testing Codename: buster Architecture: armv7l Kernel: Linux 4.9.59-v7+ (SMP w/4 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15), LANGUAGE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages puppet depends on: ii adduser 3.117 ii facter 3.10.0-3 ii hiera 3.2.0-2 ii init-system-helpers 1.51 ii lsb-base9.20161125+rpi1 ii ruby1:2.5.0 ii ruby-augeas 1:0.5.0-3+b2 ii ruby-deep-merge 1.1.1-1 ii ruby-shadow 2.5.0-1 ii ruby2.0 [ruby-interpreter] 2.0.0.484+really457-3 ii ruby2.1 [ruby-interpreter] 2.1.5-2+deb8u3 Versions of packages puppet recommends: ii debconf-utils 1.5.66 ii lsb-release9.20161125+rpi1 pn ruby-selinux Versions of packages puppet suggests: pn ruby-hocon pn ruby-rrd -- Configuration Files: /etc/puppet/hiera.yaml changed [not included] /etc/puppet/puppet.conf changed [not included] -- no debconf information -- gem list *** LOCAL GEMS *** bigdecimal (default: 1.3.4) cmath (default: 1.0.0) colored (1.2) cri (2.10.1) csv (default: 1.0.0) date (default: 1.0.0) deep_merge (1.1.1) did_you_mean (1.0.0) etc (default: 1.0.0) faraday (0.9.2) faraday_middleware (0.12.2) fast_gettext (1.2.0) fcntl (default: 1.0.0) fiddle (default: 1.0.0) fileutils (default: 1.0.2) gdbm (default: 2.0.0) gettext (3.2.4) gettext-setup (0.7) hiera (3.2.0) io-console (default: 0.4.6) ipaddr (default: 1.2.0) json (default: 2.1.0) locale (2.1.2) log4r (1.1.10) minitar (0.6.1) minitest (5.10.3) multi_json (1.12.1) multipart-post (1.2.0) net-telnet (0.1.1) nokogiri (1.8.2) openssl (default: 2.1.0) pkg-config (1.2.9) power_assert (0.2.7) psych (default: 3.0.2) puppet_forge (2.2.9) r10k (2.6.2) rack (1.6.4) rake (12.3.0) rdoc (default: 6.0.1) rgen (0.8.0) ruby-shadow (2.5.0) safe_yaml (1.0.4) scanf (default: 1.0.0) sdbm (default: 1.0.0) semantic_puppet (1.0.1) soap4r-ruby1.9 (2.0.5) stringio (default: 0.0.1) strscan (default: 1.0.0) systemu (2.6.5) test-unit (3.2.5) text (1.3.0) webrick (default: 1.4.2) zlib (default: 1.0.0)
Bug#852658: collectd-core: Won't start without non-required packages libsensors4 liboping0
Package: collectd-core Version: 5.7.0-3 Severity: grave Justification: renders package unusable Dear Maintainer, Installation of collectd fails on the start of the package. The package misses files from libsensors4 liboping0, but these packages are only recommended or even suggested. Manual installation of libsensors4 liboping0 solved the issue. When a package won't complete it's installation without a package, it should be a requirement, not anything less. Probably an issue with the debian packages as well. -- System Information: Distributor ID: Raspbian Description:Raspbian GNU/Linux 9.0 (stretch) Release:9.0 Codename: stretch Architecture: armv7l Kernel: Linux 4.4.34-v7+ (SMP w/4 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages collectd-core depends on: ii debconf [debconf-2.0] 1.5.59 ii init-system-helpers1.46 ii libc6 2.24-8+rpi1 ii libcap21:2.25-1 ii libltdl7 2.4.6-2 ii lsb-base 9.20161125+rpi1 Versions of packages collectd-core recommends: ii perl 5.24.1~rc4-1 pn rrdtool Versions of packages collectd-core suggests: ii apache2 [httpd-cgi] 2.4.25-1 pn apcupsd ii bind9 1:9.10.3.dfsg.P4-10.1 pn ceph pn chrony pn collectd-dev pn default-jre-headless pn default-mysql-server pn gpsd pn hddtemp ii iptables1.6.0+snapshot20161117-4 pn ipvsadm pn libatasmart4 pn libconfig-general-perl ii libcurl3-gnutls 7.51.0-1 ii libdbi1 0.9.0-4 pn libesmtp6 pn libganglia1 ii libgcrypt20 1.7.5-2 pn libgdk-pixbuf2.0-0 ii libglib2.0-02.50.2-2 pn libgps22 pn libhiredis0.13 ii libhtml-parser-perl 3.72-3 ii libip4tc0 1.6.0+snapshot20161117-4 ii libip6tc0 1.6.0+snapshot20161117-4 ii libldap-2.4-2 2.4.44+dfsg-3 pn liblua5.3-0 pn liblvm2app2.2 ii libmariadbclient18 10.0.28-2+b1 pn libmemcached11 pn libmicrohttpd12 ii libmnl0 1.0.4-2 pn libmodbus5 pn libmosquitto1 pn libnotify4 pn libnspr4 pn libnss3 pn libopenipmi0 pn liboping0 pn libowcapi-3.1-4 pn libpcap0.8 ii libperl5.24 5.24.1~rc4-1 ii libpq5 9.6.1-2 pn libprotobuf-c1 ii libpython2.72.7.13-1 pn librabbitmq4 pn librdkafka1 pn libregexp-common-perl pn libriemann-client0 ii librrd8 1.6.0-1+b1 ii librrds-perl1.6.0-1+b1 pn libsensors4 pn libsigrok2 pn libsnmp30 ii libssl1.1 1.1.0c-2 pn libtokyotyrant3 ii libudev1232-8 pn libupsclient4 ii liburi-perl 1.71-1 pn libvarnishapi1 pn libvirt0 pn libxen-4.6 ii libxml2 2.9.4+dfsg1-2.1 ii libyajl22.1.0-2 pn lm-sensors pn mbmon pn memcached pn nginx pn notification-daemon pn nut pn olsrd pn openvpn pn pdns-server pn postgresql pn redis-server pn slapd pn time-daemon pn varnish ii zlib1g 1:1.2.8.dfsg-4 pn zookeeper -- debconf information: collectd/auto-migrate-3-4: false collectd/migration-4-5: collectd/migration-3-4: collectd/auto-migrate-4-5: false collectd/postrm_purge_data: true
Bug#852059: opendnssec-signer: installation hangs on invoke-rc.d due to script name being to long
Package: opendnssec-signer Version: 1:2.0.3-5 Severity: important Dear Maintainer, During installation of opendnssec the installation of this package and opendnssec-enforcer hang on command: invoke-rc.d start Each configuration round teh script has to be killed to end the wait. Don't know of this should be reported here, as the scriptname is longer then 15 characters, or with the maintainers of invoke-rc.d or the start-stop-daemon function. The scripts will never start this way. (at least on this system) I haven't been able to fix this, and as this is a new installation, no comparisons with older versions. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing'), (500, 'oldstable'), (60, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages opendnssec-signer depends on: ii init-system-helpers 1.46 ii libc62.24-8 ii libldns2 1.7.0-1 ii libssl1.11.1.0c-2 ii libxml2 2.9.4+dfsg1-2.1 ii opendnssec-common1:2.0.3-5 Versions of packages opendnssec-signer recommends: iu opendnssec 1:2.0.3-5 ih opendnssec-enforcer 1:2.0.3-5 pn softhsm2 opendnssec-signer suggests no packages. -- no debconf information
Bug#756479: [Pkg-nagios-devel] Bug#756479: nagios-nrpe-server: Ignores dont_blame_nrpe=1
So you solve ignorant users by disabling a feature of the software package. That would leave the choice between recompiling every time there is an update to fix the cripled package, stay at the 2.13 level or ditch Debian after 18 years. On 30/07/14 13:57, Alexander Wirt wrote: > tag 756479 wontfix > thanks > > On Wed, 30 Jul 2014, Jan Huijsmans wrote: > >> Package: nagios-nrpe-server >> Version: 2.15-1 >> Severity: important >> >> Dear Maintainer, >> >> >> *** Reporter, please consider answering these questions, where appropriate >> *** >> >>* What led up to the situation? >> >> Upgrade from 2.13-3.1 to 2.15-1 >> >>* What exactly did you do (or not do) that was effective (or >> ineffective)? >> >> Downgrade to 2.13-3 >> >>* What was the outcome of this action? >> >> Listens to dont_blame_nrpe again. >> >>* What outcome did you expect instead? >> >> >From the upgrade, that this wouldn't break. > This change is on intention. Please read the NEWS file. > > Alex > -- --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#756485: acpid: Unable to upgrade/downgrade
Package: acpid Version: 1:2.0.22-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade to this version resulted in the inability to stop package * What exactly did you do (or not do) that was effective (or ineffective)? 1. AFter first upgrade (previous version to this one) moved /etc/sysctl.d directory, so upgrade would continue. From this version to next (or previous) failes completely as acpid won't stop. (or at least stop script exits with error) 2. manually remove status of acpid from /var/lib/dpkg/status * What was the outcome of this action? 1. Unable to upgrade package. 2. Was able to install -3 version of package * What outcome did you expect instead? Upgrade to succeed from -2 to -3 version. *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages acpid depends on: ii kmod 18-1 ii libc6 2.19-7 ii lsb-base 4.1+Debian13 Versions of packages acpid recommends: pn acpi-support-base acpid 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#756479: nagios-nrpe-server: Ignores dont_blame_nrpe=1
Package: nagios-nrpe-server Version: 2.15-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Upgrade from 2.13-3.1 to 2.15-1 * What exactly did you do (or not do) that was effective (or ineffective)? Downgrade to 2.13-3 * What was the outcome of this action? Listens to dont_blame_nrpe again. * What outcome did you expect instead? >From the upgrade, that this wouldn't break. *** End of the template - remove these template lines *** -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages nagios-nrpe-server depends on: ii adduser 3.113+nmu3 ii libc62.19-7 ii libssl1.0.0 1.0.1h-3 ii libwrap0 7.6.q-25 ii lsb-base 4.1+Debian13 Versions of packages nagios-nrpe-server recommends: ii nagios-plugins1.5-3 ii nagios-plugins-basic 1.5-3 nagios-nrpe-server suggests no packages. -- Configuration Files: /etc/nagios/nrpe.cfg changed: log_facility=daemon pid_file=/var/run/nrpe.pid server_port=5666 server_address=* nrpe_user=nagios nrpe_group=nagios allowed_hosts=* dont_blame_nrpe=1 allow_bash_command_substitution=0 debug=0 command_timeout=60 connection_timeout=300 command[check_users]=/usr/lib/nagios/plugins/check_users -w 5 -c 10 command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20 command[check_hda1]=/usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /dev/hda1 command[check_zombie_procs]=/usr/lib/nagios/plugins/check_procs -w 5 -c 10 -s Z command[check_total_procs]=/usr/lib/nagios/plugins/check_procs -w 150 -c 200 include=/etc/nagios/nrpe_local.cfg include_dir=/etc/nagios/nrpe.d/ /etc/nagios/nrpe_local.cfg changed: command[check_disk]=/usr/lib/nagios/plugins/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$ command[check_load]=/usr/lib/nagios/plugins/check_load --warning=$ARG1$,$ARG2$,$ARG3$ --critical=$ARG4$,$ARG5$,$ARG6$ command[check_users]=/usr/lib/nagios/plugins/check_users -w $ARG1$ -c $ARG2$ command[check_procs]=/usr/lib/nagios/plugins/check_procs -w $ARG1$ -c $ARG2$ command[check_mailq_postfix]=/usr/lib/nagios/plugins/check_mailq -w $ARG1$ -c $ARG2$ -M postfix command[check_apt]=/usr/bin/sudo /usr/local/sbin/check-apt-upgrade.pl --run-apt command[check_raid]=/usr/local/sbin/nagios_raid -- 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#716670: Cancel bug
Sorry, my bad. I had selinux installed and removed it. With removal of the packages, it didn't remove the selinux options in /etc/default/grub -> GRUB_CMDLINE_LINUX This caused the hang in the mount of root. (can't explain why the 3.2 kernel did boot tho) With regards, Jan Huijsmans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#716670: linux-image-3.9-1-amd64 unbootable with mdadm raid1 /boot
Package: src:linux Version: 3.9.8-1 Severity: critical Justification: breaks the whole system Dear Maintainer, After switching from linux-image-3.2.0-4-amd64 to linux-image-3.9-1-amd64 I got an unbootable system. The previous version 3.9.6-1 gave errors with mdadm config. During boot message mdadm: No devices listed in conf file were found before halt. With version 3.9.8-1 the root filesystem (lv in vg on md raid1) is not found. Booting back to linux-image-3.2.0-4-amd64 3.2.46-1 restores the system to a perfect working condition. Looks like a mismatch with update-initramfs, mdadm and the 3.9 kernel from this package. BTW a self compiled kernel version 3.9.3 and 3.9.4 were working without problems. (wil be testing with 3.9.9 compiles from kernel.org source) With regards Jan Huijsmans -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: To Be Filled By O.E.M. product_name: To Be Filled By O.E.M. product_version: To Be Filled By O.E.M. chassis_vendor: To Be Filled By O.E.M. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: P1.60 board_vendor: ASRock board_name: A790GXH/128M board_version: ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge [1022:9600] Subsystem: ASRock Incorporation Device [1849:9600] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00:01.0 PCI bridge [0604]: ASRock Incorporation Device [1849:9602] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 5) [1022:9609] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] (prog-if 01 [AHCI 1.0]) Subsystem: ASRock Incorporation Device [1849:4391] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: ahci 00:12.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: ASRock Incorporation Device [1849:4397] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:13.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller [1002:4397] (prog-if 10 [OHCI]) Subsystem: ASRock Incorporation Device [1849:4397] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: ehci_hcd 00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller [1002:4385] (rev 3c) Subsystem: ASRock Incorporation Device [1849:4385] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- 00:14.1 IDE interface [0101]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 IDE Controller [1002:439c] (prog-if 8a [Master SecP PriP]) Subsystem: ASRock Incorporation Device [1849:439c] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: pata_atiixp 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASRock Incorporation Device [1849:0397] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- D
Bug#673370: centerim: Crash at startup (suspect login msn)
On Thu, Aug 23, 2012 at 05:30:10PM +0200, gregor herrmann wrote: > Control: tag -1 unreproducible > > On Fri, 18 May 2012 08:47:44 +0200, Jan Huijsmans wrote: > > > After performing a dist-upgrade yesterday the package stopped functioning. > > Works fine here (msn logins, no crashes or whatever) now with > centerim and centerim-utf8 4.22.10-2+b1 (amd64). Checked after this email and it works again. I guess it was a problem with one of the libraries that's been updated since reporting the bug. I've been using Pidgin since I reported the bug and tested a few times since then. Bug can be closed. Greetings, Jan Huijsmans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#682794: Collectd-core: missing dependency on liboping0 (ping plugin requires it)
Package: collectd-core
Version: 5.1.0-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After installing the package I got the error below.
# /etc/init.d/collectd restart
Restarting statistics collection and monitoring daemon: collectdERROR:
lt_dlopen ("/usr/lib/collectd/ping.so") failed: file not found. The most common
cause for this problem are missing dependencies. Use ldd(1) to check the
dependencies of the plugin / shared object.
Unable to load plugin ping.
ERROR: lt_dlopen ("/usr/lib/collectd/ping.so") failed: file not found. The most
common cause for this problem are missing dependencies. Use ldd(1) to check the
dependencies of the plugin / shared object.
Unable to load plugin ping.
.
Checking with ldd gave:
ldd /usr/lib/collectd/ping.so
linux-vdso.so.1 => (0x7fff9c1ff000)
liboping.so.0 => not found
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7feb82b4d000)
libiptc.so.0 => /lib/libiptc.so.0 (0x7feb8294a000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7feb82746000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7feb823bf000)
libip4tc.so.0 => /lib/libip4tc.so.0 (0x7feb821b6000)
libip6tc.so.0 => /lib/libip6tc.so.0 (0x7feb81fae000)
/lib64/ld-linux-x86-64.so.2 (0x7feb82fd9000)
This file is included in the liboping0 package.
Installing the package solved the problem. (It's installed now)
The file is missing in the requirements, only mentioned in the Suggests section.
The crash of collectd is not expected with a Suggest package. I would eighter
move the package to the Required section or prevent the ping.so module to crash
when it can't find the library, but just exit so it wouldn't prevent collectd to
start.
Greetings,
Jan Huijsmans
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15)
(ignored: LC_ALL set to en_US.ISO8859-15)
Shell: /bin/sh linked to /bin/dash
Versions of packages collectd-core depends on:
ii debconf [debconf-2.0] 1.5.44
ii iptables 1.4.14-2
ii libc6 2.13-33
ii libltdl7 2.4.2-1.1
Versions of packages collectd-core recommends:
pn perl
ii rrdtool 1.4.7-1.1
Versions of packages collectd-core suggests:
ii apache2 2.2.22-9
ii apache2-mpm-prefork [httpd-cgi] 2.2.22-9
pn apcupsd
ii bind91:9.8.1.dfsg.P1-4.1
pn collectd-dev
ii hddtemp 0.3-beta15-51
pn ipvsadm
ii libc62.13-33
pn libconfig-general-perl
ii libcurl3-gnutls 7.25.0-1
ii libdbi1 0.8.4-6
ii libdbus-1-3 1.6.0-1
pn libesmtp6
ii libgcrypt11 1.5.0-3
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.32.3-1
ii libhal1 0.5.14-8
ii libhtml-parser-perl 3.69-2
pn libmemcached10
pn libmodbus5
ii libmysqlclient18 5.5.24+dfsg-4
ii libnotify4 0.7.5-1
ii libopenipmi0 2.0.16-1.3
ii liboping01.6.2-1
ii libpcap0.8 1.3.0-1
ii libperl5.14 5.14.2-12
ii libpq5 9.1.4-2
pn libprotobuf-c0
ii libpython2.7 2.7.3~rc2-2.1
pn librabbitmq0
pn libregexp-common-perl
ii librrd4 1.4.7-1.1
ii librrds-perl 1.4.7-1.1
ii libsensors4 1:3.3.2-2
ii libsnmp155.4.3~dfsg-2.5
ii libssl1.0.0 1.0.1c-3
pn libtokyotyrant3
pn libupsclient1
ii liburi-perl 1.60-1
pn libvarnishapi1
pn libvirt0
ii libxml2 2.8.0+dfsg1-4
ii libyajl2 2.0.4-2
ii lm-sensors 1:3.3.2-2
pn mbmon
ii memcached1.4.13-0.1
pn mysql-server
pn nginx
pn notification-daemon
pn nut
pn olsrd
pn openvpn
pn pdns-server
ii postgresql 9.1+132
pn time-daemon
Bug#673370: M$ handshake failure
On Sat, Jun 30, 2012 at 11:55:35PM +0200, Boris Petersen wrote: > On 05/18/2012 02:27 PM, Jan Huijsmans wrote: > > After the debug run I changes msn status in ~/.centerim/config from o to _ > > and centerim starts without a problem. The msn connection has changed > > somehow. > > (I expect M$ to be the problem) > since this is a release critical bug i guess it can be closed right? It isn't solved, so I wouldn't release. I jyst updated the computer, tested again and the error persists, when logging into msn, it crashes. BTW I downgraded to .1 and the problem exists there as well. Greetings, Jan Huijsmans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674786: netbase: Ignores /etc/network/interfaces except for ipv4 eth0 and lo0
Hello, On Mon, May 28, 2012 at 08:35:56AM +0200, Andrew Shadura wrote: > tags 674786 moreinfo > thanks > > > Hello, > > On Sun, 27 May 2012 18:05:22 +0200 > Jan Huijsmans wrote: > > > After upgrade to netbase 5.0 from 4.47 all entries > > in /etc/network/interfaces except for eth0 ipv4 and lo0 ipv4 are > > completely ignored. No virtual interfaces or ipv6 addresses are set > > at all. > > Either you provide full information about your configuration *and* it's > not invalid as last time, or it's not a bug. When finding an error in the interfaces file, the bootscript fails and quits. I don't think this is desirable behaviour. I would skip to the next interface and resume there, instead of just giving up. Especially when switching to another subtool for network configuration that's pickier then the previous one. --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674775: netbase: Netbase ignores /etc/network/interfaces ipv6 settings
Hello, On Sun, May 27, 2012 at 05:58:05PM +0200, Andrew Shadura wrote: > Hello, > > On Sun, 27 May 2012 17:24:38 +0200 > Jan Huijsmans wrote: > > > Package: netbase > > Version: 5.0 > > Severity: critical > > Tags: ipv6 > > Justification: breaks the whole system > > > > Dear Maintainer, > > > > Upgrade from 4.47 to 5.0 resulted in failure to add every static ipv6 > > address configured in /etc/network/interfaces. Looks like ipv6 is > > completely ignored. Adding manually works. > If you did read what does it say, you could see the following: > > Error: an inet prefix is expected rather than "2001:610:611:2::42/64/64". > Failed to bring up eth0. Nop, just 'eth0 already configured' when restarting via /etc/init.d/networking Haven't got access to the console and no errors were found in any of the logfiles. > Which means that you have specified the netmask twice: > > > iface eth0 inet6 static > > address 2001:610:611:2::42/64 > > netmask 64 > > Previously, ifupdown was using ifconfig which would silently swallow > this and just set it up, but iproute (which we use now) does complain. > Probably, in the next upload I will teach ifupdown to cope with this, > but this isn't strictly a valid configuration. When correcting the error, all interfaces are back online again after reboot. When finding an error in the interfaces file, the bootscript fails and quits. I don't think this is desirable behaviour. I would skip to the next interface and resume there. > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::4/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::140/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::141/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::142/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::143/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::144/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::145/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::146/64 > > up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::642/64 > This is not needed any more, by the way, you can specify as many 'iface > eth0 inet6 static' sections as you want. Also, I promise to come up > with a better syntax to the next release ;) It could, but this is easier (and a lot less typing is required) --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674786: netbase: Ignores /etc/network/interfaces except for ipv4 eth0 and lo0
Package: netbase Version: 5.0 Severity: critical Tags: ipv6 Justification: breaks the whole system Dear Maintainer, After upgrade to netbase 5.0 from 4.47 all entries in /etc/network/interfaces except for eth0 ipv4 and lo0 ipv4 are completely ignored. No virtual interfaces or ipv6 addresses are set at all. Previous report of this affecting only ipv6 can be scrapped, it affects every interface not being eth0 of lo0. (or every main interface, I only have 1, so I can't test this. Holding this package in 4.xx is the only option, reverting back to 4.47 isn't an option when you don't have the file anymore, reverting back to netbase 4.45 won't solve this. Work around installed here, manual startup script with the ifconfig options until this is sorted out or the new and badly or even not documented location for the configuration is found. Jan Huijsmans -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages netbase depends on: ii lsb-base 4.1+Debian3 Versions of packages netbase recommends: ii ifupdown 0.7~rc3 netbase 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#674775: netbase: Netbase ignores /etc/network/interfaces ipv6 settings
Package: netbase Version: 5.0 Severity: critical Tags: ipv6 Justification: breaks the whole system Dear Maintainer, Upgrade from 4.47 to 5.0 resulted in failure to add every static ipv6 address configured in /etc/network/interfaces. Looks like ipv6 is completely ignored. Adding manually works. Ipv4 addresses work perfectly. snippet config: iface eth0 inet6 static address 2001:610:611:2::42/64 netmask 64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::4/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::140/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::141/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::142/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::143/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::144/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::145/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::146/64 up /sbin/ifconfig eth0 inet6 add 2001:610:611:2::642/64 Jan Huijsmans -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages netbase depends on: ii lsb-base 4.1+Debian3 Versions of packages netbase recommends: ii ifupdown 0.7~rc3 netbase 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#673370: M$ handshake failure
On Fri, May 18, 2012 at 10:33:28AM +0200, Boris Petersen wrote: > On Fri, May 18, 2012 at 9:10 AM, Jan Huijsmans wrote: > > I've started centerim withub strace and collected the included output. > > Recompile of the package didn't solve the problem. > instead of strace, please run centerim through gdb. Before trying > that, please also try to run centerim with the -d switch. Make sure > that you deleted you ~/.centerim/debug file. After the debug run I changes msn status in ~/.centerim/config from o to _ and centerim starts without a problem. The msn connection has changed somehow. (I expect M$ to be the problem) Greetings, Jan Huijsmans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673370: strace output
Hello, On Fri, May 18, 2012 at 10:33:28AM +0200, Boris Petersen wrote: > On Fri, May 18, 2012 at 9:10 AM, Jan Huijsmans wrote: > > Hello, > > > > I've started centerim withub strace and collected the included output. > > Recompile of the package didn't solve the problem. > instead of strace, please run centerim through gdb. Before trying > that, please also try to run centerim with the -d switch. Make sure > that you deleted you ~/.centerim/debug file. Started with the -d option, with the enclosed last lines of the debug file as a result. Looking at this I would expect a policy change from msn instead of a bug. [IN] VER 4 MSNP8 [OUT] CVR 5 0x0409 winnt 5.2 i386 MSNMSGR 7.5.0324 MSMSGS huysm...@koffie.nu^M Received packet from Server 2a 02 e1 70 01 78 00 01 00 0f 80 00 9a ed d8 0d *..p.x.. 0010 00 06 00 01 00 02 00 03 08 31 33 38 30 34 35 35 .1380455 0020 32 00 00 00 0f 00 01 00 02 00 50 00 06 00 04 20 2.P 0030 03 00 00 00 05 00 04 35 7d 89 98 00 0d 00 40 09 ...5}.@. 0040 46 13 44 4c 7f 11 d1 82 22 44 45 53 54 00 00 09 F.DL"DEST... 0050 46 13 49 4c 7f 11 d1 82 22 44 45 53 54 00 00 97 F.IL"DEST... 0060 b1 27 51 24 3c 43 34 ad 22 d6 ab f7 3f 14 92 56 .'Q$http://msgruser.dlservice.microsoft.com/download/9/7/6/976085F9-D0F8-4D96-9208-FC1B461CD3D7/Install_MSN_Messenger_DL.exe http://download.live.com/?sku=messenger [OUT] USR 6 TWN I huysm...@koffie.nu^M Received packet from Server 2a 02 e1 71 00 25 00 03 00 0a 00 00 9a ed d8 7e *..q.%.~ 0010 09 31 31 34 36 39 34 30 32 32 08 31 30 37 35 39 .114694022.10759 0020 39 39 36 07 38 33 35 37 35 30 39 996.8357509 Unknown SNAC packet received - Family: 0x3 Subtype: 0xa Received packet from Server 2a 02 e1 72 00 28 00 03 00 0c 00 00 9a ed d8 7f *..r.(.. 0010 07 37 31 35 35 35 38 38 00 00 00 03 00 01 00 02 .7155588 0020 00 00 00 37 00 04 00 00 00 00 00 1d 00 00...7.. Received Buddy Offline for 7155588 (7155588) from server Received packet from Server 2a 02 e1 73 00 29 00 03 00 0c 00 00 9a ed d8 80 *..s.).. 0010 08 34 38 31 37 32 31 37 33 00 00 00 03 00 01 00 .48172173... 0020 02 00 00 00 37 00 04 00 00 00 00 00 1d 00 00 7..
Bug#673370: centerim: Crash at startup (suspect login msn)
Package: centerim Version: 4.22.10-2+b1 Severity: grave Justification: renders package unusable Dear Maintainer, After performing a dist-upgrade yesterday the package stopped functioning. When starting, it crashes with the following output (part I was able to capture added): 7f28ab4a7000-7f28ab6a6000 ---p 00013000 09:00 63678 /lib/x86_64-linux-gnu/libresolv-2.13.so 7f28ab6a6000-7f28ab6a7000 r--p 00012000 09:00 63678 /lib/x86_64-linux-gnu/libresolv-2.13.so 7f28ab6a7000-7f28ab6a8000 rw-p 00013000 09:00 63678 /lib/x86_64-linux-gnu/libresolv-2.13.so 7f28ab6a8000-7f28ab6aa000 rw-p 00:00 0 7f28ab6aa000-7f28ab6cd000 r-xp 09:00 63568 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f28ab6cd000-7f28ab8cd000 ---p 00023000 09:00 63568 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f28ab8cd000-7f28ab8d1000 r--p 00023000 09:00 63568 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f28ab8d1000-7f28ab8d2000 rw-p 00027000 09:00 63568 /lib/x86_64-linux-gnu/libtinfo.so.5.9 7f28ab8d2000-7f28ab8d4000 r-xp 09:00 63770 /lib/x86_64-linux-gnu/libdl-2.13.so 7f28ab8d4000-7f28abad4000 ---p 2000 09:00 63770 /lib/x86_64-linux-gnu/libdl-2.13.so 7f28abad4000-7f28abad5000 r--p 2000 09:00 63770 /lib/x86_64-linux-gnu/libdl-2.13.so 7f28abad5000-7f28abad6000 rw-p 3000 09:00 63770 /lib/x86_64-linux-gnu/libdl-2.13.so 7f28abad6000-7f28abaef000 r-xp fd:02 336468 /usr/lib/x86_64-linux-gnu/librtmp.so.0 7f28abaef000-7f28abcef000 ---p 00019000 fd:02 336468 /usr/lib/x86_64-linux-gnu/librtmp.so.0 7f28abcef000-7f28abcf rw-p 00019000 fd:02 336468 /usr/lib/x86_64-linux-gnu/librtmp.so.0 7f28abcf-7f28abd2c000 r-xp fd:02 90243 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 7f28abd2c000-7f28abf2c000 ---p 0003c000 fd:02 90243 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 7f28abf2c000-7f28abf2d000 r--p 0003c000 fd:02 90243 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 7f28abf2d000-7f28abf2f000 rw-p 0003d000 fd:02 90243 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 7f28abf2f000-7f28abf36000 r-xp 09:00 63914 /lib/x86_64-linux-gnu/librt-2.13.so 7f28abf36000-7f28ac135000 ---p 7000 09:00 63914 Aborted this was just after message 'logging into msn'. I'm using icq and msn, icq was already logging in. This begaviour was also seen with the latest 3.2.0-2 kernel. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Ve
Bug#645865: Additional info
Hello, I tested the 2.6.11-8 version, and this problem is still there. The manual navigation is possible, but in the tree I'm having it's a lot of clicking before I'm where I need to be. Especially as I started gimp in the correct directory. (.) Was bug 644244 the correct one to add this report to? That bug is reported as solved, but the problem still remains (at least for me) --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#649456: Confirm workaround
Hello, I can confirm the workaround from Stefan Becker. Setting environment variable NSS_SSL_CBC_RANDOM_IV=0 just before starting pidgin solves the problem. I'm curious if this is solved in the 1.12 version. (bug 646389) --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#645870: reportbug: Doesn't parse /etc/apt/preferences correctly
Package: reportbug Version: 6.2.2 Severity: important Dear Maintainer, When reporting a bug I noticed the 'APT prefers' line below, when the content of /etc/apt/preferences is as included below. It doesn't seem to ignore the commented out lines and/or can't handle preferences for specified packages. Greetings, Jan Huijsmans cat /etc/apt/preferences #Package: *clamav* #Pin: version 0.96* #Pin-Priority: 500 #Package: asterisk* #Pin: release a=oldstable #Pin-Priority: 500 Package: grub* mailgraph amule* Pin: release a=stable Pin-Priority: 500 Package: * Pin: release a=testing Pin-Priority: 500 Package: * Pin: release a=stable Pin-Priority: 60 Package: squeezeboxserver Pin: release a=unstable Pin-Priority: 500 Package: * Pin: release a=unstable Pin-Priority: 50 -- Package-specific info: ** Environment settings: EDITOR="vi" INTERFACE="gtk2" ** /home/huysmans/.reportbugrc: reportbug_version "5.1.1" mode standard ui gtk2 -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 0.8.15.8 ii python2.7.2-8 ii python-reportbug 6.2.2 reportbug recommends no packages. Versions of packages reportbug suggests: ii debconf-utils ii debsums ii dlocate ii emacs22-bin-common | emacs23-bin-common ii file 5.08-1 ii gnupg1.4.11-3 ii postfix [mail-transport-agent] 2.8.3-1 ii python-gtk2 2.24.0-2 ii python-gtkspell ii python-urwid ii python-vte ii xdg-utils1.1.0~rc1-2 -- 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#645865: gimp: Doesn't open default from current directory but 'Recent Images'
Package: gimp Version: 2.6.11-5 Severity: normal Dear Maintainer, After the latest upgrade, gimp shows the reasent images list when using -O to open a file instead of opening the current directory. The original responce was showing . (working directory when starting gimp) This hinders 'normal' use of gimp in my opinion, as it's a lot easier to navigate directories on the commandline instead of the pointy-clicky interface of the gimp navigator. APT prefers testing, except for some packages that are broken. -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages gimp depends on: ii gimp-data 2.6.11-5 ii libaa1 1.4p5-39 ii libatk1.0-0 2.2.0-1 ii libbabl-0.0-0 0.0.22-1 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libdbus-1-3 1.4.16-1 ii libdbus-glib-1-20.98-1 ii libexif12 0.6.20-1 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.6-2 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libgegl-0.0-0 0.0.22-2+b1 ii libgimp2.0 2.6.11-5 ii libglib2.0-02.28.6-1 ii libgtk2.0-0 2.24.6-2 ii libjpeg88c-2 ii liblcms11.19.dfsg-1+b1 ii libmng1 1.0.10-3 ii libpango1.0-0 1.29.4-1 ii libpng12-0 1.2.46-3 ii libpoppler-glib60.16.7-2+b1 ii librsvg2-2 2.34.1-2 ii libtiff43.9.5-2 ii libwebkitgtk-1.0-0 1.4.2-2 ii libwmf0.2-7 0.2.8.4-8.1 ii libx11-62:1.4.4-2 ii libxext62:1.3.0-3 ii libxfixes3 1:5.0-4 ii libxmu6 2:1.1.0-2 ii libxpm4 1:3.5.9-1 ii python 2.7.2-8 ii python-gtk2 2.24.0-2 ii python2.7 2.7.2-5 ii zlib1g 1:1.2.3.4.dfsg-3 Versions of packages gimp recommends: ii ghostscript 9.04~dfsg-2 Versions of packages gimp suggests: ii gimp-data-extras ii gimp-help-en [gimp-help] 2.6.1-1 ii gvfs-backends ii libasound21.0.24.1-4 -- 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#642199: Fails to connect to office communicator server with pidgin-sipe plugin (2.10.0-1 works)
On Tue, Sep 20, 2011 at 11:24:23AM +0200, Jan Huijsmans wrote: > Package: pidgin > Version: 2.10.0-1+b1 > Severity: grave > Justification: renders package unusable > > After upgrade of pidgin from 2.10.0-1 to 2.10.0-1+b1 I'm unable to connect to > the company communicator server. Works again after downgrade to the stable > version. (was unable to downgrade to 2.10.0-1) > > Greetings, > > > Jan Huijsmans > > Dear Maintainer, > *** Please consider answering these questions, where appropiate *** > >* What led up to the situation? apt-get dist-upgrade (including a pidgin upgrade) Software stack of 2011-09-19 11:45:13 >* What exactly did you do (or not do) that was effective (or > ineffective)? - Downgrade to the squeeze version (including all requirements) restored the connection. - Compile from sid source (2.10.0-1) which didn't work. - Complete reinstall with sources on 2011-09-21 No connect - apt-get dist-upgrade on 2011-09-27 12:30:46 Works again As pidgin asn't included in the upgrade today, the bug must be caused by one of the packages installed in both runs. Wheb required, a copy of the dpkg.log can be included. >* What was the outcome of this action? >* What outcome did you expect instead? > > *** End of the template - remove these lines *** > > > -- System Information: > Debian Release: wheezy/sid > APT prefers oldstable > APT policy: (500, 'oldstable'), (500, 'testing'), (60, 'stable'), (50, > 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 > (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) > Shell: /bin/sh linked to /bin/dash > > Versions of packages pidgin depends on: > ii gconf2 2.32.4-1 > ii libatk1.0-0 2.0.1-2 > ii libc6 2.13-21 > ii libcairo2 1.10.2-6.1 > ii libdbus-1-3 1.4.14-1 > ii libdbus-glib-1-20.94-4 > ii libfontconfig1 2.8.0-3 > ii libfreetype62.4.6-2 > ii libgdk-pixbuf2.0-0 2.24.0-1 > ii libglib2.0-02.28.6-1 > ii libgstreamer0.10-0 0.10.35-1 > ii libgtk2.0-0 2.24.4-3 > ii libgtkspell02.0.16-1 > ii libice6 2:1.0.7-2 > ii libpango1.0-0 1.28.4-3 > ii libpurple0 2.10.0-1+b1 > ii libsm6 2:1.2.0-2 > ii libx11-62:1.4.4-1 > ii libxml2 2.7.8.dfsg-4 > ii libxss1 1:1.2.1-2 > ii perl-base [perlapi-5.12.4] 5.12.4-4 > ii pidgin-data 2.10.0-1 > > Versions of packages pidgin recommends: > ii gstreamer0.10-plugins-base 0.10.35-1 > ii gstreamer0.10-plugins-good 0.10.30-1 > > Versions of packages pidgin suggests: > ii evolution-data-server > ii gnome-panel | kdebase-workspace-bin | docker > ii libsqlite3-0 3.7.7-2 > > -- no debconf information > > -- --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642199: Fails to connect to office communicator server with pidgin-sipe plugin (2.10.0-1 works)
Hello, On Tue, Sep 20, 2011 at 11:24:23AM +0200, Jan Huijsmans wrote: > After upgrade of pidgin from 2.10.0-1 to 2.10.0-1+b1 I'm unable to connect to > the company communicator server. Works again after downgrade to the stable > version. (was unable to downgrade to 2.10.0-1) I just tried to compile the source package, resulting in a 2.10.0-1 package of pidgin and noticed this package has the same problem. I checked with pidgin-sipe 1.9.0-1.1 and 1.11.2-1, both no go with the current setup and the compiled pidgin 2.10.0-1 or the downloaded 2.10.0-1+b1 . The squeeze version (2.7.3-1+squeeze1) works, but there is major downgrading needed. (unwanted, as this breaks slapd in my setup) Greetings, Jan Huijsmans -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#642199: Fails to connect to office communicator server with pidgin-sipe plugin (2.10.0-1 works)
Package: pidgin Version: 2.10.0-1+b1 Severity: grave Justification: renders package unusable After upgrade of pidgin from 2.10.0-1 to 2.10.0-1+b1 I'm unable to connect to the company communicator server. Works again after downgrade to the stable version. (was unable to downgrade to 2.10.0-1) Greetings, Jan Huijsmans Dear Maintainer, *** Please consider answering these questions, where appropiate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.ISO8859-15, LC_CTYPE=en_US.ISO8859-15 (charmap=ISO-8859-15) (ignored: LC_ALL set to en_US.ISO8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages pidgin depends on: ii gconf2 2.32.4-1 ii libatk1.0-0 2.0.1-2 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libdbus-1-3 1.4.14-1 ii libdbus-glib-1-20.94-4 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.6-2 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.28.6-1 ii libgstreamer0.10-0 0.10.35-1 ii libgtk2.0-0 2.24.4-3 ii libgtkspell02.0.16-1 ii libice6 2:1.0.7-2 ii libpango1.0-0 1.28.4-3 ii libpurple0 2.10.0-1+b1 ii libsm6 2:1.2.0-2 ii libx11-62:1.4.4-1 ii libxml2 2.7.8.dfsg-4 ii libxss1 1:1.2.1-2 ii perl-base [perlapi-5.12.4] 5.12.4-4 ii pidgin-data 2.10.0-1 Versions of packages pidgin recommends: ii gstreamer0.10-plugins-base 0.10.35-1 ii gstreamer0.10-plugins-good 0.10.30-1 Versions of packages pidgin suggests: ii evolution-data-server ii gnome-panel | kdebase-workspace-bin | docker ii libsqlite3-0 3.7.7-2 -- 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#639120: libdbus-1-dev: File /usr/lib/dbus-1.0/include/dbus/dbus-arch-deps.h missing
Package: libdbus-1-dev Version: 1.4.14-1 Severity: grave Justification: renders package unusable Hello, During compile of Firefox 6.0 I noticed this file being missing. Install of version 1.2.24-4+squeeze1 resulted in the availability of this file and a correct compile. As the file is included in /usr/include/dbus-1.0/dbus/dbus.h (line 29) I suspect a packaging error. Greetings, Jan Huijsmans -- System Information: Debian Release: wheezy/sid APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'testing'), (60, 'stable'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages libdbus-1-dev depends on: ii libdbus-1-3 1.4.14-1 simple interprocess messaging syst ii pkg-config0.26-1 manage compile and link flags for libdbus-1-dev recommends no packages. libdbus-1-dev 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#628895: Update
Hello, I just testen a sourcecompile of the -3 software stack, same result. The -2 softwarestack however compiles nicely with the -3 requirements and the window navigation works again. Looks like a patch in the -3 version which caused the bug, perl is not the cause. (as the -2 version works fine with perl 5.12) --- Jan Huijsmans huysm...@koffie.nu ... cannot activate /dev/brain, no response from main coffee server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#628895: irssi: upgrade 0.8.15-2 -> -3 - and - stopped working
Package: irssi
Version: 0.8.15-3
Severity: normal
After the upgrade this functionality for navigating windows within irssi.
Downgrade back to -2 isn't possible, as this version depends on perl 5.10.1.
I'm not shure if this is irssi or perl related. (the bug)
Greetings,
Jan Huijsmans
-- System Information:
Debian Release: wheezy/sid
APT prefers oldstable
APT policy: (500, 'oldstable'), (500, 'testing'), (60, 'stable'), (50,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_US.ISO8859-15 (charmap=locale: Cannot set
LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Versions of packages irssi depends on:
ii libc6 2.13-4 Embedded GNU C Library: Shared lib
ii libglib2.0-0 2.28.6-1 The GLib library of C routines
ii libncurses5 5.9-1 shared libraries for terminal hand
ii libperl5.12 5.12.3-7 shared Perl library
ii libssl1.0.0 1.0.0d-2 SSL shared libraries
ii perl 5.12.3-7 Larry Wall's Practical Extraction
ii perl-base [perlapi-5.12.3]5.12.3-7 minimal Perl system
irssi recommends no packages.
Versions of packages irssi suggests:
pn irssi-scripts (no description available)
-- debconf information:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
LANGUAGE = (unset),
LC_ALL = (unset),
LC_CTYPE = "en_US.ISO8859-15",
LANG = "en_GB.UTF-8"
are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#560168: yubikey-server-c: Fails to install on creation of user
Package: yubikey-server-c Version: 0.3-1 Severity: grave Tags: patch Justification: renders package unusable Command useradd fails on the fact -X and -g is used. Remove -g and package installs without problem. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (1001, 'testing'), (500, 'oldstable'), (60, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/dash Versions of packages yubikey-server-c depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libgcrypt11 1.4.4-6LGPL Crypto library - runtime libr ii libmicrohttpd50.4.4-1library embedding HTTP server func ii libpq58.4.1-1PostgreSQL C client library ii libyubikey0 1.5-1 Yubikey OTP handling library runti yubikey-server-c recommends no packages. yubikey-server-c 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
