Bug#903800: 4.9.110-1 Xen PV boot workaround
Hi Michael, Sorry for my mistake. Indeed, whith extra = 'elevator=noop pti=off' All xen guests boot without a problem. Thanks a lot for your help. Benoît Le mar. 17 juil. 2018 à 01:20, Michael J. Redd a écrit : > I've tested the workaround successfully. Added `pti=off` to my kernel's > boot arguments, updated GRUB, and it started as intended. > > Benoît, > > Just to be sure, since you're loading your guests' kernels directly > like that, you're passing pti=off via the `extra` config line in your > domU config files, right? I.e. > > extra = 'elevator=noop pti=off' > > > > On Tue, 2018-07-17 at 00:39 +0200, Benoît Tonnerre wrote: > > Hi, > > > > I tested this workaround : I confirm that it works on Xen host, but > > not on Xen guest. > > If you try to start a vm with latest kernel i.e. theses parameters in > > cfg file : > > > > # > > # Kernel + memory size > > # > > kernel = '/boot/vmlinuz-4.9.0-7-amd64' > > extra = 'elevator=noop' > > ramdisk = '/boot/initrd.img-4.9.0-7-amd64' > > > >
Processed: Bug #902378 in mugshot marked as pending
Processing control commands: > tag -1 pending Bug #902378 [mugshot] mugshot: fails to start: ImportError: No module named 'gi' Added tag(s) pending. -- 902378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902378: Bug #902378 in mugshot marked as pending
Control: tag -1 pending Hello, Bug #902378 in mugshot reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/python-team/applications/mugshot/commit/2b902e92aa709c63c3066930bcea511705e139df d/control: Add depend on python3-gi. Closes: #902378 (this message was generated automatically) -- Greetings https://bugs.debian.org/902378
Bug#903225: marked as done (freedv FTBFS Cannot find (any matches for) "credits.txt" (tried in .))
Your message dated Tue, 17 Jul 2018 03:33:55 + with message-id and subject line Bug#903225: fixed in freedv 1.3.1-1 has caused the Debian Bug report #903225, regarding freedv FTBFS Cannot find (any matches for) "credits.txt" (tried in .) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 903225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: freedv Version: 1.3-1 Severity: serious freedv failed to build during the binnmu for the libcodec transition. https://buildd.debian.org/status/package.php?p=freedv=unstable dh_installdocs -a -O--builddir=Build -O--build-system=cmake dh_installdocs: Cannot find (any matches for) "credits.txt" (tried in .) --- End Message --- --- Begin Message --- Source: freedv Source-Version: 1.3.1-1 We believe that the bug you reported is fixed in the latest version of freedv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 903...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. A. Maitland Bottoms (supplier of updated freedv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 16 Jul 2018 22:52:22 -0400 Source: freedv Binary: freedv Architecture: source Version: 1.3.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: A. Maitland Bottoms Description: freedv - Software Defined Radio (SDR) Closes: 903225 Changes: freedv (1.3.1-1) unstable; urgency=medium . * New upstream release * support codec2 0.8.1 (Closes: #903225) Checksums-Sha1: 0d382ad493b2ba9b1cc6876a411bf2dc3a73a1c2 2022 freedv_1.3.1-1.dsc 32ad617a4b8ce0e297b0dc7cadfb7c1cbe4abed1 536864 freedv_1.3.1.orig.tar.xz 823e95d6f2c36c8f6941bbd26e5b12044adc5bd3 16672 freedv_1.3.1-1.debian.tar.xz 38bdf537801e24cac32e9924e4117781d045b57d 11532 freedv_1.3.1-1_amd64.buildinfo Checksums-Sha256: d2fab12e81ee91398b615aaf319d473671b7017e3138c3fbf725719a4f26c4a2 2022 freedv_1.3.1-1.dsc 9365459d4c8d478d32d91629f6fdf0cb6bd27cbb71ddc5a09b37e10df03dff65 536864 freedv_1.3.1.orig.tar.xz 7b546514b547e6d28d2ee4c94d8e0d42903745ef249f8f7b5ad8704007081eb2 16672 freedv_1.3.1-1.debian.tar.xz 588b6b83ac6d89410338f302fd74e8fc553c62d067cbf70943b9aa63a35d598d 11532 freedv_1.3.1-1_amd64.buildinfo Files: ac6ac66a815c155675d2ffd7bb66f058 2022 hamradio optional freedv_1.3.1-1.dsc 43a4bca546def09662998509fe5c7abe 536864 hamradio optional freedv_1.3.1.orig.tar.xz 9a4c804202dc6030693880d0bc7d5d1b 16672 hamradio optional freedv_1.3.1-1.debian.tar.xz a55ffaccfa47f7d02a9beb28228974fd 11532 hamradio optional freedv_1.3.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEB8qH3cTCsGJAtrF0UEHxiR9E4JAFAltNYEoACgkQUEHxiR9E 4JAxbw//RtDGgW0a+QGO6RiFfELVHT83h7qo7AS+5T3rvDJEBYM0PT7DZssn46gW pHd8Nan24xpA/qcj8CDVF5Pd6m/YFAMpVnnwho3/JIXcMk1B1AlPg+bV2Cq/kmvS kwrKXkf11Aqr1FALw8O+sJc2vEJOxIcKlrwYL929GtUgQEWtH7wQOdMdoDsgzpb7 i2t2ue/vaqiLe99pNTBDVmFrb1AF/nshzDe+kVTq2RH3Wdc5hqC5D0fj60g6WH64 QWSZkKq3+akgqJs/uMgOzr0+aCXNwUcxbsep3Rxi3IjPa4s4RqCtCyKBv99JcTL7 i+ujnp7hmsPVn5VeT733vk0/BZlmDN2KH8TENkNPk+7KoMk86PpFhCStGckasnh+ iOwhgiJSX89xS2i5EEXHIzT96f5sn0053ucUioDFHJHMsPSXAFCWUGbL022LgWqV s7O/kRlRpODeHlwwB+Jn+bxCWF5veb8JEVgGsTqNyXKP/pELWmHYgge3nV18O29M ZQ01Fm4cnhbb6FDS2zwkV/UmkaWfb1dzLR8VNWRdDYnRxqYNW7kYGbaFa7vMbfMS oA5Ma9sn3pMUUbUGVhmnkc+VYQIyn4iyfvywoVrDZGChA0EAm77EAG7Bi5yrn65h xE7WPk2IURQGviHH251iOreSOqpzTi7GmOJ4rslzxYy15qI2Sfw= =eiCa -END PGP SIGNATURE End Message ---
Bug#903940: Integer overflow on buffer sizes causes complete failure of driver
Package: libtowitoko2
Version: 2.0.7-9
Severity: grave
Tags: patch
pcscd nowadays passes in buffers much larger than can be represented in an
unsigned short when communicating with the card reader, but libtowitoko2
simply casts the length to an unsigned short, which leads to
overflow/truncation of the buffer size and thus to complete failure to use
the Towitoko reader using this driver.
The attached patch simply limits the buffer sizes that are passed into the
driver to what can be represented in unsigned shorts, which makes it all
work again for me.
diff --git a/src/ifd-handler/ifdhandler.c b/src/ifd-handler/ifdhandler.c
index 5fc0299..b3dbcaa 100644
--- a/src/ifd-handler/ifdhandler.c
+++ b/src/ifd-handler/ifdhandler.c
@@ -33,6 +33,7 @@
#include
#include
#include
+#include
#ifdef HAVE_PTHREAD_H
#include
#endif
@@ -497,15 +498,24 @@ IFDHTransmitToICC (DWORD Lun, SCARD_IO_HEADER SendPci,
#endif
dad = (UCHAR) ((slot == 0) ? 0x00 : slot + 1);
sad = 0x02;
- lr = (unsigned short) (*RxLength);
- lc = (unsigned short) TxLength;
-
- ret = CT_data (ctn, , , lc, TxBuffer, , RxBuffer);
-
- if (ret == OK)
+ lr = ((*RxLength) > USHRT_MAX) ? USHRT_MAX : ((unsigned short) (*RxLength));
+ if (TxLength <= USHRT_MAX)
{
- (*RxLength) = lr;
- rv = IFD_SUCCESS;
+ lc = (unsigned short) TxLength;
+
+ ret = CT_data (ctn, , , lc, TxBuffer, , RxBuffer);
+
+ if (ret == OK)
+{
+ (*RxLength) = lr;
+ rv = IFD_SUCCESS;
+}
+
+ else
+{
+ (*RxLength) = 0;
+ rv = IFD_COMMUNICATION_ERROR;
+}
}
else
Bug#903937: /etc/reader.conf.d/libtowitoko2 causes driver failure
Package: libtowitoko2 Version: 2.0.7-9 Severity: grave /etc/reader.conf.d/libtowitoko2 should not contain a DEVICENAME line as this driver does not support opening readers by device name, but the presence of the line in the config file triggers a bug in pcscd that always causes /dev/ttyS0 to be opened when a DEVICENAME line is present, no matter what else is configured. Instead, it should be documented that "normal" serial devices start at CHANNELID 1 for /dev/ttyS0 and USB devices start at 0x20 for /dev/ttyUSB0, and possibly the automatically generated /etc/reader.conf.d/libtowitoko2 should be removed completely (or made into a conffile), so as to not break a working manual configuration on each update/reinstall, given that the debconf options don't support every possible setup.
Bug#881205: NMU for backintime 1.1.24
On Sunday, July 01 2018, Fabian Wolff wrote: > Hi Jonathan, > > On Fri, 29 Jun 2018 22:21:54 +0100, Jonathan Wiltshire wrote: >> Would you like to co-maintain? If so, please add yourself to uploaders and >> prepare a maintainer upload (rather than NMU). I added you to the >> repository members in anticipation. > > Thanks. In principle, I'd be interested in co-maintaining the package, > but unfortunately, I don't think that I have the time for it right > now. I might reconsider co-maintaining this package in the future, > though. > > For the time being, I'd like to leave it at a NMU. Can I proceed with > the NMU? If so, would you like to sponsor it, or should I look for a > sponsor elsewhere? Hello Jonathan, FYI, Fabian contacted me and I accepted to sponsor his NMU. I have been working with him for some time and his uploads are always very good; I've also reviewed the modifications he made and they are sensible. I'll be uploading the package to the DELAYED queue as a courtesy. As a side note, he forked your repository on salsa and did his work on his repo: https://salsa.debian.org/wolff-guest/pkg-backintime I think it makes sense to set up a new "debian/backintime" repository and use his repo as the starting point; I can do that if you want. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/ signature.asc Description: PGP signature
Bug#903821: 4.9.110-1 Xen PV boot workaround
I've tested the workaround successfully. Added `pti=off` to my kernel's boot arguments, updated GRUB, and it started as intended. Benoît, Just to be sure, since you're loading your guests' kernels directly like that, you're passing pti=off via the `extra` config line in your domU config files, right? I.e. extra = 'elevator=noop pti=off' On Tue, 2018-07-17 at 00:39 +0200, Benoît Tonnerre wrote: > Hi, > > I tested this workaround : I confirm that it works on Xen host, but > not on Xen guest. > If you try to start a vm with latest kernel i.e. theses parameters in > cfg file : > > # > # Kernel + memory size > # > kernel = '/boot/vmlinuz-4.9.0-7-amd64' > extra = 'elevator=noop' > ramdisk = '/boot/initrd.img-4.9.0-7-amd64'
Bug#903767: 4.9.110-1 Xen PV boot workaround
Hi, I tested this workaround : I confirm that it works on Xen host, but not on Xen guest. If you try to start a vm with latest kernel i.e. theses parameters in cfg file : # # Kernel + memory size # kernel = '/boot/vmlinuz-4.9.0-7-amd64' extra = 'elevator=noop' ramdisk = '/boot/initrd.img-4.9.0-7-amd64' The VM crash in loop with kernel error : [0.00] Linux version 4.9.0-7-amd64 (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.110-1 (2018-07-05) [0.00] Command line: root=/dev/xvda2 ro elevator=noop [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] ACPI in unprivileged domain disabled [0.00] Released 0 page(s) [0.00] e820: BIOS-provided physical RAM map: [0.00] Xen: [mem 0x-0x0009] usable [0.00] Xen: [mem 0x000a-0x000f] reserved [0.00] Xen: [mem 0x0010-0x7fff] usable [0.00] NX (Execute Disable) protection: active [0.00] DMI not present or invalid. [0.00] Hypervisor detected: Xen [0.00] e820: last_pfn = 0x8 max_arch_pfn = 0x4 [0.00] MTRR: Disabled [0.00] x86/PAT: MTRRs disabled, skipping PAT initialization too. [0.00] x86/PAT: Configuration [0-7]: WB WT UC- UC WC WP UC UC [0.00] RAMDISK: [mem 0x0200-0x05996fff] [0.00] NUMA turned off [0.00] Faking a node at [mem 0x-0x7fff] [0.00] NODE_DATA(0) allocated [mem 0x7fc16000-0x7fc1afff] [0.00] Zone ranges: [0.00] DMA [mem 0x1000-0x00ff] [0.00] DMA32[mem 0x0100-0x7fff] [0.00] Normal empty [0.00] Device empty [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009] [0.00] node 0: [mem 0x0010-0x7fff] [0.00] Initmem setup node 0 [mem 0x1000-0x7fff] [0.00] p2m virtual area at c900, size is 4000 [0.00] Remapped 0 page(s) [0.00] SFI: Simple Firmware Interface v0.81 http://simplefirmware.org [0.00] smpboot: Allowing 1 CPUs, 0 hotplug CPUs [0.00] PM: Registered nosave memory: [mem 0x-0x0fff] [0.00] PM: Registered nosave memory: [mem 0x000a-0x000f] [0.00] e820: [mem 0x8000-0x] available for PCI devices [0.00] Booting paravirtualized kernel on Xen [0.00] Xen version: 4.8.4-pre (preserve-AD) [0.00] clocksource: refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 7645519600211568 ns [0.00] setup_percpu: NR_CPUS:512 nr_cpumask_bits:512 nr_cpu_ids:1 nr_node_ids:1 [0.00] percpu: Embedded 35 pages/cpu @88007f60 s105304 r8192 d29864 u2097152 [0.00] PV qspinlock hash table entries: 256 (order: 0, 4096 bytes) [0.00] Built 1 zonelists in Node order, mobility grouping on. Total pages: 515978 [0.00] Policy zone: DMA32 [0.00] Kernel command line: root=/dev/xvda2 ro elevator=noop [0.00] PID hash table entries: 4096 (order: 3, 32768 bytes) [0.00] Memory: 1980804K/2096764K available (6250K kernel code, 1159K rwdata, 2868K rodata, 1420K init, 688K bss, 115960K reserved, 0K cma-reserved) [0.00] Kernel/User page tables isolation: enabled [0.00] Hierarchical RCU implementation. [0.00] Build-time adjustment of leaf fanout to 64. [0.00] RCU restricting CPUs from NR_CPUS=512 to nr_cpu_ids=1. [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=1 [0.00] Using NULL legacy PIC [0.00] NR_IRQS:33024 nr_irqs:32 0 [0.00] xen:events: Using FIFO-based ABI [0.00] Console: colour dummy device 80x25 [0.00] console [tty0] enabled [0.00] console [hvc0] enabled [0.00] clocksource: xen: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.00] installing Xen timer for CPU 0 [0.00] tsc: Unable to calibrate against PIT [0.00] tsc: No reference (HPET/PMTIMER) available [0.00] tsc: Detected 2597.018 MHz processor [0.004000] Calibrating delay loop (skipped), value calculated using timer frequency.. 5194.03 BogoMIPS (lpj=10388072) [0.004000] pid_max: default: 32768 minimum: 301 [0.004000] Security Framework initialized [0.004000] Yama:
Bug#903932: marked as done (udisks2 breaks sysvinit-core)
Your message dated Mon, 16 Jul 2018 23:11:53 +0200 with message-id <5bc3a1e3-bbdd-77a4-a266-a2b664d00...@debian.org> and subject line Re: [Pkg-utopia-maintainers] Bug#903932: udisks2 breaks sysvinit-core has caused the Debian Bug report #903932, regarding udisks2 breaks sysvinit-core to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 903932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udisks2 Version: 2.7.6-3 Severity: serious Justification: - Dear Maintainer, udisks2 conflicts with sysvinit-core, which means i.e. that the plasma-desktop environment cannot be installed without replacing init with systemd, because some kde package is depending on udisks2. I believe the problem is in udisks2, as it depends on libpam-systemd which seems to break the things, while it probably should not be necceassy for udisk2, when init is used. with kind regards, Alex -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages udisks2 depends on: ii dbus 1.12.8-3 ii libacl12.2.52-3+b1 ii libatasmart4 0.19-5 ii libblockdev-fs22.16-2 ii libblockdev-loop2 2.16-2 ii libblockdev-part2 2.16-2 ii libblockdev-swap2 2.16-2 ii libblockdev-utils2 2.16-2 ii libblockdev2 2.16-2 ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 ii libgudev-1.0-0 232-2 ii libmount1 2.32-0.1 ii libpam-systemd 239-5 ii libpolkit-agent-1-00.105-21 ii libpolkit-gobject-1-0 0.105-21 ii libsystemd0239-5 ii libudisks2-0 2.7.6-3 ii parted 3.2-21+b1 ii udev 239-5 Versions of packages udisks2 recommends: ii dosfstools 4.1-2 ii e2fsprogs1.44.3-1 ii eject2.1.5+deb1+cvs20081104-13.2 ii exfat-utils 1.2.8-1 ii libblockdev-crypto2 2.16-2 ii ntfs-3g 1:2017.3.23-2 ii policykit-1 0.105-21 Versions of packages udisks2 suggests: ii btrfs-progs 4.16.1-2 pn f2fs-tools pn libblockdev-mdraid2 pn mdadm pn nilfs-tools pn reiserfsprogs pn udftools pn udisks2-btrfs pn udisks2-lvm2 ii xfsprogs 4.15.1-1 -- no debconf information --- End Message --- --- Begin Message --- Am 15.07.2018 um 15:06 schrieb Alex: > Package: udisks2 > Version: 2.7.6-3 > Severity: serious > Justification: - > > Dear Maintainer, > udisks2 conflicts with sysvinit-core, which means i.e. that the this must be a mistake, udisks2 does not conflict with sysvinit-core. I suppose you actually want to look at #903295 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature --- End Message ---
Bug#903932: udisks2 breaks sysvinit-core
Package: udisks2 Version: 2.7.6-3 Severity: serious Justification: - Dear Maintainer, udisks2 conflicts with sysvinit-core, which means i.e. that the plasma-desktop environment cannot be installed without replacing init with systemd, because some kde package is depending on udisks2. I believe the problem is in udisks2, as it depends on libpam-systemd which seems to break the things, while it probably should not be necceassy for udisk2, when init is used. with kind regards, Alex -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages udisks2 depends on: ii dbus 1.12.8-3 ii libacl12.2.52-3+b1 ii libatasmart4 0.19-5 ii libblockdev-fs22.16-2 ii libblockdev-loop2 2.16-2 ii libblockdev-part2 2.16-2 ii libblockdev-swap2 2.16-2 ii libblockdev-utils2 2.16-2 ii libblockdev2 2.16-2 ii libc6 2.27-3 ii libglib2.0-0 2.56.1-2 ii libgudev-1.0-0 232-2 ii libmount1 2.32-0.1 ii libpam-systemd 239-5 ii libpolkit-agent-1-00.105-21 ii libpolkit-gobject-1-0 0.105-21 ii libsystemd0239-5 ii libudisks2-0 2.7.6-3 ii parted 3.2-21+b1 ii udev 239-5 Versions of packages udisks2 recommends: ii dosfstools 4.1-2 ii e2fsprogs1.44.3-1 ii eject2.1.5+deb1+cvs20081104-13.2 ii exfat-utils 1.2.8-1 ii libblockdev-crypto2 2.16-2 ii ntfs-3g 1:2017.3.23-2 ii policykit-1 0.105-21 Versions of packages udisks2 suggests: ii btrfs-progs 4.16.1-2 pn f2fs-tools pn libblockdev-mdraid2 pn mdadm pn nilfs-tools pn reiserfsprogs pn udftools pn udisks2-btrfs pn udisks2-lvm2 ii xfsprogs 4.15.1-1 -- no debconf information
Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot
Just wanted to add a me too. After upgrading a Xen hypervisor to 4.9.0-7-amd64 I see the same infinite reboot loop as reported above. As this box is a production server I downgraded back to 4.9.0-6 to fix the issue for now. Thanks, -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64)
Bug#903679: Processed: severity of 903679 is grave
Control: severity -1 important On Mon, 2018-07-16 at 16:57 +, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > severity 903679 grave > > Bug #903679 [src:linux] /build/linux-hny3SU/linux- > 4.16.5/drivers/gpu/drm/drm_vblank.c:1073 > drm_wait_one_vblank+0x16e/0x180 [drm] > Severity set to 'grave' from 'normal' > > thanks This is not a grave bug. It might make the package unusable for you, but it does not make the package unusable in general. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Processed: Re: Processed: severity of 903679 is grave
Processing control commands: > severity -1 important Bug #903679 [src:linux] /build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x16e/0x180 [drm] Severity set to 'important' from 'grave' -- 903679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903821: 4.9.110-1 Xen PV boot workaround
Reportedly, adding pti=off to the kernel boot parameters will work around the issue for now. Turning off pti in the guest kernel is done in any case for PV. The issue between 4.9.107 and 4.9.111 affects the detection and turning off of pti, that's why forcing it off helps. In 4.9.112 it's fixed in commit 1adc34adc3447c34926994b87db5d929f5ab45b5 "x86/cpu: Re-apply forced caps every time CPU caps are re-read" Hans
Bug#903917: Acknowledgement (libsss-sudo.postinst clobbers local change to /etc/nsswitch.conf)
I wonder if "dpkg -P libsss-sudo" is a reasonable workaround. Are there any cases where libsss-sudo needs to be installed but not active in nsswitch.conf? signature.asc Description: PGP signature
Processed: Re: exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>)
Processing control commands: > tag -1 - stretch Bug #903125 [src:exec-maven-plugin] exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>) Removed tag(s) stretch. > retitle -1 exec-maven-plugin: FTBFS: tests fail with (expected:<[mvn] > --version> but was:<['mvn'] --version>) Bug #903125 [src:exec-maven-plugin] exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>) Changed Bug title to 'exec-maven-plugin: FTBFS: tests fail with (expected:<[mvn] --version> but was:<['mvn'] --version>)' from 'exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>)'. -- 903125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903125: exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>)
Control: tag -1 - stretch Control: retitle -1 exec-maven-plugin: FTBFS: tests fail with (expected:<[mvn] --version> but was:<['mvn'] --version>) This is also reproducible in jessie: ... --- T E S T S --- Running org.codehaus.mojo.exec.ExecJavaMojoTest Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 10.492 sec Running org.codehaus.mojo.exec.ExecMojoTest [debug] Toolchains are ignored, 'executable' parameter is set to target/java [debug] got arguments from system properties: -f pom.xml Tests run: 7, Failures: 5, Errors: 0, Skipped: 0, Time elapsed: 0.124 sec <<< FAILURE! Results : Failed tests: testRunOK(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> testRunFailure(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> testRunError(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> testOverrides(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] -f pom.xml> but was:<['mvn'] -f pom.xml> testOverrides3(org.codehaus.mojo.exec.ExecMojoTest): expected:<[mvn] --version> but was:<['mvn'] --version> Tests run: 14, Failures: 5, Errors: 0, Skipped: 0 [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] There are test failures. Please refer to /build/exec-maven-plugin-1.1.1+dfsg/target/surefire-reports for the individual test results. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 14 seconds [INFO] Finished at: Mon Jul 16 16:46:31 UTC 2018 [INFO] Final Memory: 22M/608M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 Andreas
Bug#903917: libsss-sudo.postinst clobbers local change to /etc/nsswitch.conf
Package: libsss-sudo Version: 1.16.2-1 Severity: serious Justification: policy violation (section 10.7.3) User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu cosmic Steps to reproduce: 1. apt install sssd 2. Edit /etc/nsswitch.conf and remove "sss" from the "sudoers" entry 3. apt install --reinstall libsss-sudo Expected behaviour: "sss" remains not present in /etc/nsswitch.conf (ie. the local change is preserved). Actual behaviour: "sss" is re-added to nsswitch.conf. I have verified this behaviour in a Debian sid container today. Policy violation: This breaks "local changes must be preserved during a package upgrade" from policy section 10.7.3. Suggested fix: Make the change only on fresh install of the package, rather than on upgrade. Additional information: You might be interested to know that the reason users are hitting this is that they are trying to work around a different bug that is reported downstream here: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1249777. But the workaround gets removed on upgrade. Thanks, Robie signature.asc Description: PGP signature
Processed: severity of 903679 is grave
Processing commands for cont...@bugs.debian.org: > severity 903679 grave Bug #903679 [src:linux] /build/linux-hny3SU/linux-4.16.5/drivers/gpu/drm/drm_vblank.c:1073 drm_wait_one_vblank+0x16e/0x180 [drm] Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 903679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902198: octave-odepkg FTBFS with octave 4.4.0
On Tue, 2018-07-17 at 00:30 +0800, Drew Parsons wrote: > On Mon, 2018-07-16 at 13:54 +0200, Rafael Laboissière wrote: > > > > I tried to build the package using the tip of the Mercurial > > repository > Weird though, https://wiki.octave.org/Odepkg points at https://bitbucket.org/odepkg/odepkg Is this a fork? The recent commits diverge from sourceforge. (more importantly, does it build, and pass tests?)
Bug#902198: octave-odepkg FTBFS with octave 4.4.0
On Mon, 2018-07-16 at 13:54 +0200, Rafael Laboissière wrote: > > I tried to build the package using the tip of the Mercurial > repository > for the odepkg package [1]. After some tweaks in the documentation, > I > was able to compile the source code, but the unit tests fail > miserably. > > I just noticed that odepkg was removed from the list of supported > Octave-Forge packages That's regrettable if odepkg has been abandoned ;( (just as well I've been moving my computations over to FEniCS/dolfin...) Rafael, could you push your tip efforts to a branch on odepkg salsa? I can build and test against my own octave scripts that use odepkg. Drew
Bug#903916: undertow: Keep it out of Buster
Source: undertow Version: 1.4.25-1 Severity: serious I am filing this bug report to prevent the migration of undertow to testing and subsequently being part of the next stable release Debian 10, "Buster". This was also briefly discussed with the Security Team. Reasons: - Undertow is regularly affected by security vulnerabilities but upstream often does not provide enough information to fix the issue with a targeted patch. Sometimes additional information are not public or are only disclosed weeks and months later. I have filed a bug report and suggested to improve the communication policy but so far nothing has happened. - Undertow has no reverse-dependencies besides syncany in experimental. Once Buster is released this bug report can be closed again and hopefully the situation has improved by then. Markus
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
I can confirm version 5.2.14-dfsg-7 fixes the issue. Thank you! Kind regards Filip
Processed: Re: Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Processing control commands:
> fixed -1 5.2.14-dfsg-7
Bug #902897 {Done: Gianfranco Costamagna }
[virtualbox] virtualbox: fails to start vm
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Marked as fixed in versions virtualbox/5.2.14-dfsg-7.
--
902897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Control: fixed -1 5.2.14-dfsg-7 Seems to be fixed now.
Processed: found 892139 in 20180710-1, tagging 903295, tagging 902597, tagging 903380, fixed 903125 in 1.6.0-4
Processing commands for cont...@bugs.debian.org: > found 892139 20180710-1 Bug #892139 [src:eclib] eclib: FTBFS on i386: tests fail: reference solution precision mismatch Marked as found in versions eclib/20180710-1. > tags 903295 + sid buster Bug #903295 [systemd-shim] libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed Added tag(s) sid and buster. > tags 902597 + experimental Bug #902597 [src:protobuf] protobuf ftbfs with python3.7 as a supported version Added tag(s) experimental. > tags 903380 - sid buster Bug #903380 [src:libxmlada] libxmlada: FTBFS with unicode-data 11 Removed tag(s) buster and sid. > fixed 903125 1.6.0-4 Bug #903125 [src:exec-maven-plugin] exec-maven-plugin: FTBFS in stretch (expected:<[mvn] --version> but was:<['mvn'] --version>) Marked as fixed in versions exec-maven-plugin/1.6.0-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 892139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892139 902597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902597 903125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903125 903295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903295 903380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
I received: virtualbox 5.2.14-dfsg-7 and its associated files as part of the normal system updated this morning. This correspondence is simply to report that vbox_now works well_ for me. I hope others affected can report the same. Thank you,
Processed: Re: Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Processing control commands:
> notfixed -1 5.2.14-dfsg-5
Bug #902897 {Done: Gianfranco Costamagna }
[virtualbox] virtualbox: fails to start vm
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Ignoring request to alter fixed versions of bug #902897 to the same values
previously set
--
902897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Control: notfixed -1 5.2.14-dfsg-5 I also still see this bug with the latest version.
Processed: tagging 897453, fixed 838384 in 1.15-1, notfixed 838384 in 1.15.1+deb9u1, reassign 897644 to src:gwcs ...
Processing commands for cont...@bugs.debian.org:
> tags 897453 + experimental
Bug #897453 {Done: Adrian Bunk } [src:mtbl] mtbl: FTBFS:
configure: error: Package requirements (liblz4 > 129) were not met
Added tag(s) experimental.
> fixed 838384 1.15-1
Bug #838384 {Done: Benjamin Kaduk } [krb5-user] krb5-user:
k5srvutil man page claims it can add new keys to the keytab, but it cannot
Marked as fixed in versions krb5/1.15-1.
> notfixed 838384 1.15.1+deb9u1
Bug #838384 {Done: Benjamin Kaduk } [krb5-user] krb5-user:
k5srvutil man page claims it can add new keys to the keytab, but it cannot
There is no source info for the package 'krb5-user' at version '1.15.1+deb9u1'
with architecture ''
Unable to make a source version for version '1.15.1+deb9u1'
No longer marked as fixed in versions 1.15.1+deb9u1.
> reassign 897644 src:gwcs 0.8.0-1
Bug #897644 {Done: Ole Streicher } [python-gwcs]
python-gwcs depends on cruft package python-asdf
Bug reassigned from package 'python-gwcs' to 'src:gwcs'.
No longer marked as found in versions gwcs/0.8.0-1.
No longer marked as fixed in versions gwcs/0.9.1-1.
Bug #897644 {Done: Ole Streicher } [src:gwcs] python-gwcs
depends on cruft package python-asdf
Marked as found in versions gwcs/0.8.0-1.
> fixed 897644 0.9.1-1
Bug #897644 {Done: Ole Streicher } [src:gwcs] python-gwcs
depends on cruft package python-asdf
Marked as fixed in versions gwcs/0.9.1-1.
> tags 892395 + experimental
Bug #892395 {Done: Mike Hommey } [src:firefox-esr]
firefox-esr: build-depends on GCC 6
Added tag(s) experimental.
> tags 853402 + experimental
Bug #853402 {Done: Mike Hommey } [src:firefox-esr]
firefox-esr: ftbfs with GCC-7
Added tag(s) experimental.
> fixed 889915 2.8.1-1
Bug #889915 {Done: Markus Koschany } [libfaad2] libfaad2 in
Wheezy contains patches for some security bugs. They were not backported to
Jessie.
Marked as fixed in versions faad2/2.8.1-1.
> fixed 867271 1.936
Bug #867271 {Done: Holger Levsen } [debian-edu-config]
debian-edu: Network problems when installing ltsp-server from USB iso
Marked as fixed in versions debian-edu-config/1.936.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
838384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838384
853402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853402
867271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867271
889915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889915
892395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892395
897453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897453
897644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#900912: openjdk-10: Accessibility does not get loaded
On 13.07.2018 12:39, Samuel Thibault wrote: Hello, Matthias Klose, le ven. 13 juil. 2018 12:04:42 +0200, a ecrit: this issue now has two patches, one to install the properties file, and the other to extend the class path. Are both needed? Yes. Can you see any compatibility issues when the accessibility stuff isn't used? I didn't see any. hmm, I'm not sure. the upstream issue asks instead about """ This is a consequence of the JPMS. ATK will need to be reimplemented as a Service Provider, to be loaded by java.util.ServiceLoader. In order to do this it must provide an SPI which extends javax.accessibility.AccessibilityProvider See https://docs.oracle.com/javase/10/docs/api/java/awt/Toolkit.html#getDefaultToolkit() and https://docs.oracle.com/javase/10/docs/api/javax/accessibility/AccessibilityProvider.html """
Bug#902198: octave-odepkg FTBFS with octave 4.4.0
* Sébastien Villemot [2018-06-28 21:57]: On Fri, Jun 29, 2018 at 03:04:56AM +0800, Drew Parsons wrote: Or does latest the upstream git work, should we just grab that? I remember having tried to apply some upstream patches, but maybe not the second one that you linked to. In any case, someone has to try again. I tried to build the package using the tip of the Mercurial repository for the odepkg package [1]. After some tweaks in the documentation, I was able to compile the source code, but the unit tests fail miserably. I just noticed that odepkg was removed from the list of supported Octave-Forge packages [2]. It seems that octave-odepkg will become a candidate for removal from Debian. If this happens, octave-ocs will have to be remove as well. Rafael [1] https://sourceforge.net/p/octave/odepkg/ci/default/tree/ [2] https://octave.sourceforge.io/packages.php
Bug#901001: python3-minimal should Pre-Depend on python3.N-minimal
On 14.07.2018 22:01, Andreas Beckmann wrote: Followup-For: Bug #901001 Hi, are there known upgrade problems related to this bug when upgrading from jessie to stretch (python 3.4 -> 3.5) or could we tag this bug as 'sid buster'? It's the same, but maybe not seen that frequently as the popularity of Python3 was not as high as it is now.
Bug#894432: marked as done (python-ncclient FTBFS: AttributeError: 'NoneType' object has no attribute 'settimeout')
Your message dated Mon, 16 Jul 2018 10:49:56 + with message-id and subject line Bug#894432: fixed in python-ncclient 0.6.0-1 has caused the Debian Bug report #894432, regarding python-ncclient FTBFS: AttributeError: 'NoneType' object has no attribute 'settimeout' to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 894432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894432 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-ncclient Version: 0.5.3-4 Severity: serious Some recent change in unstable makes python-ncclient FTBFS: https://tests.reproducible-builds.org/debian/history/python-ncclient.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-ncclient.html ... == ERROR: test_auth_agent (unit.transport.test_ssh.TestSSH) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched return func(*args, **keywargs) File "/build/1st/python-ncclient-0.5.3/test/unit/transport/test_ssh.py", line 121, in test_auth_agent obj._transport = paramiko.Transport(None) File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 339, in __init__ self.sock.settimeout(self._active_check_timeout) AttributeError: 'NoneType' object has no attribute 'settimeout' >> begin captured logging << ncclient.transport.session: DEBUG: created: client_capabilities= - >> end captured logging << - == ERROR: test_auth_agent_exception (unit.transport.test_ssh.TestSSH) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched return func(*args, **keywargs) File "/build/1st/python-ncclient-0.5.3/test/unit/transport/test_ssh.py", line 135, in test_auth_agent_exception obj._transport = paramiko.Transport(None) File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 339, in __init__ self.sock.settimeout(self._active_check_timeout) AttributeError: 'NoneType' object has no attribute 'settimeout' >> begin captured logging << ncclient.transport.session: DEBUG: created: client_capabilities= - >> end captured logging << - == ERROR: test_auth_default_keyfiles (unit.transport.test_ssh.TestSSH) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched return func(*args, **keywargs) File "/build/1st/python-ncclient-0.5.3/test/unit/transport/test_ssh.py", line 173, in test_auth_default_keyfiles obj._transport = paramiko.Transport(None) File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 339, in __init__ self.sock.settimeout(self._active_check_timeout) AttributeError: 'NoneType' object has no attribute 'settimeout' >> begin captured logging << ncclient.transport.session: DEBUG: created: client_capabilities= - >> end captured logging << - == ERROR: test_auth_default_keyfiles_exception (unit.transport.test_ssh.TestSSH) -- Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/mock/mock.py", line 1305, in patched return func(*args, **keywargs) File "/build/1st/python-ncclient-0.5.3/test/unit/transport/test_ssh.py", line 189, in test_auth_default_keyfiles_exception obj._transport = paramiko.Transport(None) File "/usr/lib/python2.7/dist-packages/paramiko/transport.py", line 339, in __init__ self.sock.settimeout(self._active_check_timeout) AttributeError: 'NoneType' object has no attribute 'settimeout' >> begin captured logging << ncclient.transport.session: DEBUG: created: client_capabilities= - >> end captured logging << - == ERROR: test_auth_exception
Bug#903895: colord-kde: build-depends on no longer available plasma-framework-dev
Source: colord-kde Version: 0.5.0-2 Severity: serious Justification: fails to build from source Hi, colord-kde cannot be built any more since plasma-framework-dev is gone. Andreas
Bug#903188: marked as done (python-can: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))
Your message dated Mon, 16 Jul 2018 10:21:05 + with message-id and subject line Bug#903188: fixed in python-can 2.2.1-1 has caused the Debian Bug report #903188, regarding python-can: FTBFS in buster/sid (dh_installdocs: Cannot find "README") to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 903188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-can Version: 2.1.0-3 Severity: serious Tags: ftbfs Dear maintainer: I tried to build this package in buster but it failed: [...] debian/rules build-indep dh build-indep --with python3,python2,sphinxdoc --buildsystem=pybuild dh_update_autotools_config -i -O--buildsystem=pybuild dh_auto_configure -i -O--buildsystem=pybuild I: pybuild base:217: python2.7 setup.py config running config I: pybuild base:217: python3.6 setup.py config running config debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build I: pybuild base:217: /usr/bin/python setup.py build running build running build_py [... snipped ...] byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/socketcan/socketcan_common.py to socketcan_common.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/socketcan/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/socketcan/socketcan_constants.py to socketcan_constants.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/socketcan/socketcan_native.py to socketcan_native.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/socketcan/socketcan_ctypes.py to socketcan_ctypes.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/slcan.py to slcan.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/pcan/PCANBasic.py to PCANBasic.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/pcan/pcan.py to pcan.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/pcan/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/virtual.py to virtual.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/usb2can/serial_selector.py to serial_selector.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/usb2can/usb2canabstractionlayer.py to usb2canabstractionlayer.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/usb2can/usb2canInterface.py to usb2canInterface.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/usb2can/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/interface.py to interface.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/kvaser/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/kvaser/canlib.py to canlib.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/kvaser/argument_parser.py to argument_parser.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/kvaser/constants.py to constants.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/nican.py to nican.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/vector/__init__.py to __init__.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/vector/exceptions.py to exceptions.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/vector/vxlapi.py to vxlapi.cpython-36.pyc byte-compiling /<>/debian/python3-can/usr/lib/python3.6/dist-packages/can/interfaces/vector/canlib.py to
Bug#890691: ruby-bio FTBFS with ruby 2.5
Hi, I'd love to fix this bug since this package is of relevance for Debian Med. It seems to boil down to Error: test_na_seqstat(Bio::TestShellPluginSeq): ArgumentError: incomplete format specifier; use %% (double %) instead which sounds pretty easy for somebody who speaks Ruby (which is not the case for me). Could anybody provide a patch (or just do a team upload of this package which I updated in Git to latest upstream since Mai)? Thanks a lot Andreas. -- http://fam-tille.de
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
On 16 juil. 2018 09:25, "Filip W." wrote: > Package: virtualbox > Version: 5.2.14-dfsg-5 > Followup-For: Bug #902897 > > Dear Maintainer, > > Unfortunately the bug still exists in 5.2.14-dfsg-5 version of package. > > Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed > (VERR_LDRELF_RELOCATION_NOT_SUPPORTED). I see the same. Christian
Processed: Bug#895463: keyutils FTBFS: Can't Determine Endianness
Processing control commands:
> tags -1 pending
Bug #895463 {Done: James Cowgill } [src:keyutils] keyutils
FTBFS: Can't Determine Endianness
Added tag(s) pending.
--
895463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#895463: keyutils FTBFS: Can't Determine Endianness
Control: tags -1 pending
Hi,
I've uploaded the attached debdiff which fixes this bug. While I was
preparing the upload, I also migrated the git repository from alioth to
salsa.
James
diff -Nru keyutils-1.5.9/debian/changelog keyutils-1.5.9/debian/changelog
--- keyutils-1.5.9/debian/changelog 2017-11-16 12:19:11.0 +
+++ keyutils-1.5.9/debian/changelog 2018-07-16 09:53:06.0 +0100
@@ -1,3 +1,12 @@
+keyutils (1.5.9-9.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * d/control: Migrate Vcs repository to salsa.d.o.
+ * d/patches: Add endianness-and-PIE.patch to fix FTBFS.
+Thanks to Steve Langasek and Adam Conrad (Closes: #895463)
+
+ -- James Cowgill Mon, 16 Jul 2018 09:53:06 +0100
+
keyutils (1.5.9-9.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru keyutils-1.5.9/debian/control keyutils-1.5.9/debian/control
--- keyutils-1.5.9/debian/control 2017-09-28 13:12:55.0 +0100
+++ keyutils-1.5.9/debian/control 2018-07-16 09:52:48.0 +0100
@@ -7,8 +7,8 @@
lsb-release,
Standards-Version: 3.9.8
Homepage: http://people.redhat.com/~dhowells/keyutils/
-Vcs-Git: https://anonscm.debian.org/git/collab-maint/keyutils.git
-Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/keyutils.git
+Vcs-Git: https://salsa.debian.org/debian/keyutils.git
+Vcs-Browser: https://salsa.debian.org/debian/keyutils
Package: keyutils
Architecture: linux-any
diff -Nru keyutils-1.5.9/debian/patches/endianness-and-PIE.patch
keyutils-1.5.9/debian/patches/endianness-and-PIE.patch
--- keyutils-1.5.9/debian/patches/endianness-and-PIE.patch 1970-01-01
01:00:00.0 +0100
+++ keyutils-1.5.9/debian/patches/endianness-and-PIE.patch 2018-07-16
09:51:51.0 +0100
@@ -0,0 +1,23 @@
+Description: fix regexp match against `file /proc/$$/exe` for -fPIE bash
+ Now that bash is built with PIE enabled, keyutils' check for endianness
+ fails because file no longer returns "executable", but instead returns
+ "shared object" for file << 5.33 and "pie executable" for file >= 5.33.
+Author: Steve Langasek
+Author: Adam Conrad
+Last-Modified: 2018-05-07
+
+--- a/tests/toolbox.inc.sh
b/tests/toolbox.inc.sh
+@@ -19,10 +19,10 @@ includes=${includes%/*}/
+ echo === $OUTPUTFILE ===
+
+ endian=`file -L /proc/$$/exe`
+-if expr "$endian" : '.* MSB executable.*' >&/dev/null
++if expr "$endian" : '.* MSB \(executable\|shared object\|pie executable\).*'
>&/dev/null
+ then
+ endian=BE
+-elif expr "$endian" : '.* LSB executable.*' >&/dev/null
++elif expr "$endian" : '.* LSB \(executable\|shared object\|pie
executable\).*' >&/dev/null
+ then
+ endian=LE
+ else
diff -Nru keyutils-1.5.9/debian/patches/series
keyutils-1.5.9/debian/patches/series
--- keyutils-1.5.9/debian/patches/series2017-09-28 13:12:55.0
+0100
+++ keyutils-1.5.9/debian/patches/series2018-07-16 09:51:51.0
+0100
@@ -16,3 +16,4 @@
Make-build-reproducible.patch
Drop-tests-requiring-CONFIG_BIG_KEYS.patch
Adjust-tests-for-3.18-kernel-change.patch
+endianness-and-PIE.patch
signature.asc
Description: OpenPGP digital signature
Bug#895463: marked as done (keyutils FTBFS: Can't Determine Endianness)
Your message dated Mon, 16 Jul 2018 09:19:50 + with message-id and subject line Bug#895463: fixed in keyutils 1.5.9-9.3 has caused the Debian Bug report #895463, regarding keyutils FTBFS: Can't Determine Endianness to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 895463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: keyutils Version: 1.5.9-9.2 Severity: serious Some recent change in unstable makes keyutils FTBFS: https://tests.reproducible-builds.org/debian/history/keyutils.html https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/keyutils.html ... dh_auto_test -- \ PATH=/build/1st/keyutils-1.5.9:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \ LD_LIBRARY_PATH=/build/1st/keyutils-1.5.9 \ SKIPROOT=yes \ SKIPINSTALLED=yes make -j1 test PATH=/build/1st/keyutils-1.5.9:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LD_LIBRARY_PATH=/build/1st/keyutils-1.5.9 SKIPROOT=yes SKIPINSTALLED=yes make[2]: Entering directory '/build/1st/keyutils-1.5.9' grep: /etc/rpm/macros.dist: No such file or directory make -C tests run make[3]: Entering directory '/build/1st/keyutils-1.5.9/tests' sh runtest.sh keyctl/update/userupdate keyctl/update/noargs keyctl/update/bad-args keyctl/unlink/valid keyctl/unlink/noargs keyctl/unlink/bad-args keyctl/unlink/all keyctl/timeout/valid keyctl/timeout/noargs keyctl/timeout/bad-args keyctl/show/valid keyctl/show/noargs keyctl/session/valid keyctl/session/bad-args keyctl/search/valid keyctl/search/noargs keyctl/search/bad-args keyctl/revoke/valid keyctl/revoke/noargs keyctl/revoke/bad-args keyctl/requesting/valid keyctl/requesting/piped keyctl/requesting/noargs keyctl/requesting/bad-args keyctl/reading/valid keyctl/reading/noargs keyctl/reading/bad-args keyctl/pupdate/userupdate keyctl/pupdate/noargs keyctl/pupdate/bad-args keyctl/permitting/valid keyctl/permitting/noargs keyctl/permitting/bad-args keyctl/padd/useradd keyctl/padd/noargs keyctl/padd/bad-args keyctl/noargs keyctl/newring/valid keyctl/newring/noargs keyctl/newring/bad-args keyctl/listing/valid keyctl/listing/noargs keyctl/listing/bad-args keyctl/link/valid keyctl/link/recursion keyctl/link/noargs keyctl/link/bad-args keyctl/invalidate/valid keyctl/invalidate/noargs keyctl/invalidate/bad-args keyctl/instantiating/noargs keyctl/instantiating/bad-args keyctl/describing/valid keyctl/describing/noargs keyctl/describing/bad-args keyctl/clear/valid keyctl/clear/noargs keyctl/clear/bad-args keyctl/add/useradd keyctl/add/noargs keyctl/add/bad-args bugzillas/bz1033467 Some tests require root privileges. It is recommended that this be run as root. Running with session keyring RHTS/keyctl/45279 Joined session keyring: 541509331 === /build/1st/keyutils-1.5.9/tests/keyctl/update/userupdate/test.out === +++ [31;1mCan't Determine Endianness[0m make[3]: *** [Makefile:42: run] Error 1 --- End Message --- --- Begin Message --- Source: keyutils Source-Version: 1.5.9-9.3 We believe that the bug you reported is fixed in the latest version of keyutils, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 895...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. James Cowgill (supplier of updated keyutils package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 16 Jul 2018 09:53:06 +0100 Source: keyutils Binary: keyutils libkeyutils1 libkeyutils-dev Architecture: source Version: 1.5.9-9.3 Distribution: unstable Urgency: medium Maintainer: Christian Kastner Changed-By: James Cowgill Description: keyutils - Linux Key Management Utilities libkeyutils-dev - Linux Key Management Utilities (development) libkeyutils1 - Linux Key Management Utilities (library) Closes: 895463 Changes: keyutils (1.5.9-9.3) unstable; urgency=medium . * Non-maintainer upload. * d/control: Migrate Vcs repository to salsa.d.o. * d/patches: Add endianness-and-PIE.patch to fix FTBFS. Thanks to Steve Langasek and Adam Conrad (Closes: #895463) Checksums-Sha1: 07d346021528d7941efca5f2fa1e1d531f013bc2 2093
Bug#541538: flat-volumes = no
Was redirected here after another bug report: https://gitlab.gnome.org/ GNOME/epiphany/issues/73 Suprised to see this has been open since 2009. I vote for changing default to 'flat-volumes = no' as I do find the current default both dangerous and unintuitive. I actually thought the applications I were running had bugs, but turns out they didn't.
Bug#896921: [Pkg-salt-team] Bug#896921: Bug#896921: Salt 2018.3.2 has been released
Am Sonntag, den 01.07.2018, 10:45 +0200 schrieb Dirk Heinrichs: > Am 18.05.2018 um 10:27 schrieb Benjamin Drung: > > > 2018.3 unless there is a blocking reason. > > There's 2018.3.2 meanwhile. Can we get this one, then? Sadly no, since this version still does not work with Tornado 5 in Python 3. -- Benjamin Drung System Developer Debian & Ubuntu Developer ProfitBricks GmbH Greifswalder Str. 207 10405 Berlin Email: benjamin.dr...@profitbricks.com URL: https://www.profitbricks.de Sitz der Gesellschaft: Berlin Registergericht: Amtsgericht Charlottenburg, HRB 125506 B Geschäftsführer: Achim Weiss, Matthias Steinberg, Christoph Steffens signature.asc Description: This is a digitally signed message part
Bug#903889: senlin-dashboard: unsatisfiable build-depends
Source: senlin-dashboard Version: 0.4.0-1 Severity: serious Justification: fails to build from source Hi, the Build-depends for senlin-dashboard are no longer installable: The following packages have unmet dependencies: python3-django-horizon : Conflicts: python-django-openstack-auth but 3.5.0-2 is to be installed Andreas
Bug#872413: kpatch: Please package new upstream version
tags 872413 + pending
thanks
Dear maintainer,
I've prepared an NMU for kpatch (versioned as 0.6.0-0.1) and
uploaded it to DELAYED/10. Please feel free to tell me if I should
delay it longer.
Best regards,
Nobuhiro
2018-06-20 10:09 GMT+09:00 Nobuhiro Iwamatsu :
> Hi, all.
>
> Is there any progress about this?
>
> Well, I want to use latest kpatch.
> And I created v0.6.0 package with Simon and Vincent's patches, and I
> plan to do NMU.
>
> Chris, could do you check attached patch?
>
> Best regards,
> Nobuhiro
>
> On Mon, Apr 16, 2018 at 10:03:24AM +0200, Vincent Bernat wrote:
>> ❦ 15 avril 2018 09:58 +0200, Simon Ruderich :
>>
>> >> As the package is not currently usable with our kernel, or even the
>> >> one in stable, I am bumping the severity. Since you already worked a
>> >> lot on this, would you be interested to prepare an upload for 0.5.0? If
>> >> yes, we could sort out how to organize that.
>>
>> > Thanks for your initiative. Patch to update to 0.5.0 (as diff
>> > from the current version in Debian Sid) is attached. It's based
>> > on the upstream kpatch tarball from github with the following
>> > sha512 checksum:
>> >
>> >
>> > d7e45a4395a8c7632187ca5c8b837bad0d7583f66ce5f5d2b8f1acabf9ff2539d038a16986f9846818183f5c3268a613580a98ad72f3766e286e6273d57ddc78
>> > kpatch_0.5.0.orig.tar.gz
>>
>> Simon, your patch looks OK to me. I'll change the changelog entry to
>> say:
>>
>> * Non-maintainer upload.
>> * New upstream release. Closes: #872413.
>>
>> Chris, do you object to an upload to update kpatch?
>> --
>> Must I hold a candle to my shames?
>> -- William Shakespeare, "The Merchant of Venice"
>
>
--
Nobuhiro Iwamatsu
iwamatsu at {nigauri.org / debian.org}
GPG ID: 40AD1FA6
Processed: Re: Bug#872413: kpatch: Please package new upstream version
Processing commands for cont...@bugs.debian.org: > tags 872413 + pending Bug #872413 [kpatch] kpatch: Please package new upstream version Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 872413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#903016: python3-libvirt: import fails with current python interpreter in sid
Hi, On Thu, Jul 05, 2018 at 07:45:30AM +0200, Manuel Traut wrote: > Package: python3-libvirt > Version: 4.0.0-1+b1 > Severity: grave > Tags: patch > Justification: renders package unusable > > Dear Maintainer, > > the package is broken on sid: > > The following packages were automatically installed and are no longer > required: > iputils-arping liblogging-stdlog0 libnginx-mod-http-auth-pam > libnginx-mod-http-dav-ext libnginx-mod-http-echo libngin > libnginx-mod-http-xslt-filter libnginx-mod-mail libnginx-mod-stream > libplacebo4 libwireshark10 libwiretap7 libwscodec > Use 'sudo apt autoremove' to remove them. > The following packages have been kept back: > medcon xmedcon > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. > 1 not fully installed or removed. > After this operation, 0 B of additional disk space will be used. > Do you want to continue? [Y/n] > Setting up python3-libvirt (4.0.0-1+b1) ... > File "/usr/lib/python3/dist-packages/libvirtaio.py", line 49 > from asyncio import async as ensure_future > ^ > SyntaxError: invalid syntax > > dpkg: error processing package python3-libvirt (--configure): > installed python3-libvirt package post-installation script subprocess > returned error exit status 1 > Errors were encountered while processing: > python3-libvirt > E: Sub-process /usr/bin/dpkg returned an error code (1) > > The problem is fixed upstream with this commit: > > https://github.com/libvirt/libvirt-python/commit/e27528204c887b4099b892a0237766f187959737#diff-cd56dd4108fa77f26cb6c1e6358beba1 Instead of backporting that one I want to update to a new upstream version but that needs a newer libirt which has some problems I need to look into first during the week. Cheers, -- Guido
Processed: reassign 903885 to src:linux, severity of 903885 is serious, forcibly merging 903767 903885
Processing commands for cont...@bugs.debian.org: > reassign 903885 src:linux 4.9.110-1 Bug #903885 [linux-image-4.9.0-7-amd64] Xen domU panic on boot Bug reassigned from package 'linux-image-4.9.0-7-amd64' to 'src:linux'. No longer marked as found in versions linux/4.9.110-1. Ignoring request to alter fixed versions of bug #903885 to the same values previously set Bug #903885 [src:linux] Xen domU panic on boot Marked as found in versions linux/4.9.110-1. > severity 903885 serious Bug #903885 [src:linux] Xen domU panic on boot Severity set to 'serious' from 'important' > forcemerge 903767 903885 Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor 4.8 Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64) Bug #903885 [src:linux] Xen domU panic on boot Added tag(s) pending. Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot Bug #903821 [src:linux] xen-hypervisor-4.8-amd64: Kernel Panic after upgrading to stretch 9.5 (linux-image-4.9.0-7-amd64) Merged 903767 903800 903821 903885 > thanks Stopping processing here. Please contact me if you need assistance. -- 903767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903767 903800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903800 903821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903821 903885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#900011: marked as done (src:htsjdk: Fake bug to prevent migration to testing)
Your message dated Mon, 16 Jul 2018 09:25:02 +0200 with message-id <20180716072502.4eecigp2rbze7...@an3as.eu> and subject line [olivier.sal...@irisa.fr: Re: [nore...@release.debian.org: htsjdk is marked for autoremoval from testing]] has caused the Debian Bug report #900011, regarding src:htsjdk: Fake bug to prevent migration to testing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 900011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:htsjdk Version: 2.14.3+dfsg-2 Severity: critical Justification: causes serious data loss This new version was uploaded to unstable to enable building of its new dependencies. It should not migrate to testing since it would break several dependant packages. Testing should simply keep version 2.8.1+dfsg-2 of the package. For more information see this thread: https://lists.debian.org/debian-med/2018/05/msg00020.html Kind regards Andreas. -- System Information: Debian Release: 9.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-5-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Closing the fake bug that was blocking migration. - Forwarded message from Olivier Sallou - Date: Mon, 16 Jul 2018 08:42:30 +0200 (CEST) From: Olivier Sallou To: Andreas Tille Subject: Re: [nore...@release.debian.org: htsjdk is marked for autoremoval from testing] - Andreas Tille a écrit : > Hi Olivier, > > any news about htsjdk? Hi, Htsjdk in unstable 2.14.3 fixes the pb and issue is marked at done with this release. However your fake bug 90001 prevents it to move to testing which was expecring for other packages upload and testing related to picard. I think that you can now remove your fake bug to allow it to move to testing and prevent its removal and let others as well move to testing too I will come back from holiday in a week. Olivier > > Kind regards > > Andreas. > > - Forwarded message from Debian testing autoremoval watch > - > > Date: Mon, 16 Jul 2018 04:39:06 + > From: Debian testing autoremoval watch > To: hts...@packages.debian.org > Subject: htsjdk is marked for autoremoval from testing > > htsjdk 2.8.1+dfsg-2 is marked for autoremoval from testing on 2018-07-22 > > It is affected by these RC bugs: > 894289: htsjdk: htsjdk FTBFS with openjdk-9 > > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > > - End forwarded message - > > -- > http://fam-tille.de - End forwarded message - -- http://fam-tille.de--- End Message ---
Bug#902897: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Package: virtualbox
Version: 5.2.14-dfsg-5
Followup-For: Bug #902897
Dear Maintainer,
Unfortunately the bug still exists in 5.2.14-dfsg-5 version of package.
Failed to load R0 module /usr/lib/virtualbox/VMMR0.r0: RTLdrGetBits failed
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Failed to load VMMR0.r0 (VERR_LDRELF_RELOCATION_NOT_SUPPORTED).
Kod wyniku (RC): NS_ERROR_FAILURE (0x80004005)
Komponent: ConsoleWrap
Interfejs: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8),
LANGUAGE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages virtualbox depends on:
ii adduser 3.117
ii iproute2 4.17.0-2
ii libc6 2.27-4
ii libcurl3-gnutls 7.60.0-2
ii libdevmapper1.02.12:1.02.145-4.1
ii libgcc1 1:8.1.0-10
ii libgsoap-2.8.60 2.8.60-2
ii libopus0 1.3~beta+20180518-1
ii libpng16-16 1.6.34-2
ii libpython3.6 3.6.6-1
ii libsdl1.2debian 1.2.15+dfsg2-1
ii libssl1.1 1.1.0h-4
ii libstdc++68.1.0-10
ii libvncserver1 0.9.11+dfsg-1.1
ii libvpx5 1.7.0-3
ii libx11-6 2:1.6.5-1
ii libxcursor1 1:1.1.15-1
ii libxext6 2:1.3.3-1+b2
ii libxml2 2.9.4+dfsg1-7+b1
ii libxmu6 2:1.1.2-2
ii libxt61:1.1.5-1
ii procps2:3.3.15-2
ii python3 3.6.6-1
ii python3.6 3.6.6-1
ii virtualbox-dkms [virtualbox-modules] 5.2.14-dfsg-5
ii zlib1g1:1.2.11.dfsg-1
Versions of packages virtualbox recommends:
ii libgl1 1.0.0+git20180308-3
ii libqt5core5a5.10.1+dfsg-7
ii libqt5opengl5 5.10.1+dfsg-7
ii libqt5widgets5 5.10.1+dfsg-7
ii virtualbox-qt 5.2.14-dfsg-5
Versions of packages virtualbox suggests:
pn vde2
ii virtualbox-guest-additions-iso 5.2.14-1
-- no debconf information
Bug#903347: marked as done (libnlopt-cxx-dev: missing dependency on libnlopt-cxx0 (= ${binary:Version}))
Your message dated Mon, 16 Jul 2018 06:33:57 +
with message-id
and subject line Bug#903347: fixed in nlopt 2.4.2+dfsg-8
has caused the Debian Bug report #903347,
regarding libnlopt-cxx-dev: missing dependency on libnlopt-cxx0 (=
${binary:Version})
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
903347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libnlopt-cxx-dev
Version: 2.4.2+dfsg-5
Severity: serious
This makes /usr/lib/x86_64-linux-gnu/libnlopt_cxx.so a dangling
symlink, resulting in users silently using the static library instead.
--- End Message ---
--- Begin Message ---
Source: nlopt
Source-Version: 2.4.2+dfsg-8
We believe that the bug you reported is fixed in the latest version of
nlopt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Tille (supplier of updated nlopt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 16 Jul 2018 08:02:26 +0200
Source: nlopt
Binary: libnlopt0 libnlopt-dev libnlopt-cxx0 libnlopt-cxx-dev python-nlopt
octave-nlopt libnlopt-guile0
Architecture: source
Version: 2.4.2+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
Changed-By: Andreas Tille
Description:
libnlopt-cxx-dev - nonlinear optimization library -- development package for
C++
libnlopt-cxx0 - nonlinear optimization library (C++ interface)
libnlopt-dev - nonlinear optimization library -- development package
libnlopt-guile0 - nonlinear optimization library -- Guile bindings
libnlopt0 - nonlinear optimization library
octave-nlopt - nonlinear optimization library -- GNU Octave package
python-nlopt - nonlinear optimization library -- Python bindings
Closes: 903347
Changes:
nlopt (2.4.2+dfsg-8) unstable; urgency=medium
.
* Team upload
* Add missing Depends: libnlopt-cxx0 to libnlopt-cpp-dev
Closes: #903347
* Standards-Version: 4.1.5
* Files-Excluded in d/copyright to document repackaging
Checksums-Sha1:
01ed6336a2e9fe5057f09d197fbd52c7a394e90e 2499 nlopt_2.4.2+dfsg-8.dsc
c14aa659d299159499f9d29c332512b7309c1a34 12852 nlopt_2.4.2+dfsg-8.debian.tar.xz
Checksums-Sha256:
6c17a98c522ee2c79ff91000106cbb719293edc7687beb8f185d46154174d0b2 2499
nlopt_2.4.2+dfsg-8.dsc
5d5b3e245089a3f99bec67c7a369f2227f77a5b53923dd821641af6a119d3e1b 12852
nlopt_2.4.2+dfsg-8.debian.tar.xz
Files:
c0f2703e85a375707724eef4c29132cf 2499 math optional nlopt_2.4.2+dfsg-8.dsc
6dc3b673e70a028bf098e85325d1cc0a 12852 math optional
nlopt_2.4.2+dfsg-8.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltMNvsRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtETPBAAgwZV0PxUeqlrOFXwDgqMUc+JQWrqeCm8
TdoJ3TKP/cxPkpBXq7wtdh/3tSUvGxXIGs/Mx29QTilHKRaxDrT0MLQ5WjjUuvf4
pN2BDjnQcNvotx8mYdn41voNdBKQTtNsA1TvJzKXtfQkke4Ojd+Z0zLlR5oOLm9z
nnuiUPaTA+QOmHpDgUKiAyLcGDj+9CRU+HSmjXzMv/eZx+K1u7zBBB80W79L6v63
DyeTAEX0OheFBTYTZUjIn1pAIf4ezQZ8OVIfqujWGsdrF0iyqVVfYhH7CzhB76nG
zq0v1XbGVfCouYXxCEOlWyNQNDyxPP4EF9e9xa6zmbmdd631P7vdwoFHmIj53/wJ
TfZCCIDuhX4ZHHn6iPSZv6d2F9GxgTiyYEhxD/c0KEhbffDo25S3qQo+VkWIdT6e
mUz0QDjxcZsV6ChxCd83KB+265U7+Fa3NNndTQhhHICNMyIA9NK2VRdRMZ3V3P4W
AeHmg22TjzAI0nEb1baolNXeCu2ZI8bDIXRHQPo7upb9b/381kVrPoph6slBG4pZ
f6tAsng/s3oH5VT5P8bXT45tY1S1WdRQ3NdDpMWrO9cCEw4Dqf+sL6lAUYoXAgh5
ciNgoredVkW3FZbp+3CQumf/mQhN09EnDzBYMM4qzUMZZIEdogtSlvo/gbQCxDin
lQ+Odd1UeCw=
=4Zc7
-END PGP SIGNATURE End Message ---
