Bug#903016: python3-libvirt: import fails with current python interpreter in sid

[Manuel Traut]

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



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-libvirt depends on:
ii  libc6 2.27-3
ii  libvirt0  4.3.0-1
ii  python3   3.6.6-1

Versions of packages python3-libvirt recommends:
ii  libvirt-daemon  4.3.0-1

python3-libvirt suggests no packages.

-- debconf-show failed
>From e27528204c887b4099b892a0237766f187959737 Mon Sep 17 00:00:00 2001
From: Cole Robinson 
Date: Mon, 25 Jun 2018 14:14:57 -0400
Subject: [PATCH 1/2] libvirtaio: Fix compat with python 3.7

In python 3.7, async is now a keyword, so this throws a syntax error:

  File "/usr/lib64/python3.7/site-packages/libvirtaio.py", line 49
from asyncio import async as ensure_future
^
  SyntaxError: invalid syntax

Switch to getattr trickery to accomplish the same goal

Reviewed-by: Pavel Hrdina 
Reviewed-by: Andrea Bolognani 
Signed-off-by: Cole Robinson 
---
 libvirtaio.py | 11 +++
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/libvirtaio.py b/libvirtaio.py
index 1c432dd..328e6f2 100644
--- a/libvirtaio.py
+++ b/libvirtaio.py
@@ -43,10 +43,13 @@ import warnings
 
 import libvirt
 
-try:
-from asyncio import ensure_future
-except ImportError:
-from asyncio import async as ensure_future
+# Python < 3.4.4 doesn't have 'ensure_future', so we have to fall
+# back to 'async'; however, since 'async' is a reserved keyword
+# in Python >= 3.7, we can't perform a straightforward import and
+# we have to resort to getattr() instead
+ensure_future = getattr(asyncio, "ensure_future", None)
+if not ensure_future:
+ensure_future = getattr(asyncio, "async")
 
 
 class Callback(object):
-- 
2.18.0

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

[Helmut Grohne]

Control: tags -1 - moreinfo

On Wed, Jul 04, 2018 at 10:37:32PM +0200, Michael Biebl wrote:
> sound like an sbuild bug. Using pbuilder I have no problems building the
> gnupg2 package.

I kinda agree with you here. I actually ran into this bug a while
earlier:

Unlike systemd-sysv, systemd-shim isn't Multi-Arch: foreign. So
installing a foreign libpam-systemd (as some cross builds do) did run
into the very same issue for a while already: It tried installing
systemd-shim and gave up even though just picking systemd-sysv would
have worked.

Actually, sbuild defers to apt here, so it would be an apt bug, no?

> Can you please reassign this bug report to the appropriate package?

I thus filed this bug with apt as #883555. The irc discussion on the
matter was unfortunately not reflected on the bug, but essentially deity
ruled that solving each and every situation was infeasible and that
packages must coordinate better to resolve such issues.

In the case of #883555 that meant that both alternatives should share
the same Multi-Arch value.

So even though this issue can be considered and apt bug, it'll be
wontfix there and you'll have to fix it in systemd anyway. I'm Ccing
deity here to have them speak up in case they disagree with that
analysis.

On irc you proposed two solutions:
 * dropping the -shim alternative
 * adding the inverse version restriction of the breaks to the -shim
   alternative

As far as I understand, either solution would solve this bug.

Helmut

Processed: Re: Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - moreinfo
Bug #902998 [libpam-systemd] libpam-systemd: breaks installing build depends 
e.g. gnupg2
Removed tag(s) moreinfo.

-- 
902998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 897504 is forwarded to https://github.com/hashicorp/go-plugin/issues/73

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 897504 https://github.com/hashicorp/go-plugin/issues/73
Bug #897504 [src:golang-github-hashicorp-go-plugin] 
golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu 
&& go test -vet=off -v -p 1 github.com/hashicorp/go-plugin returned exit code 1
Set Bug forwarded-to-address to 
'https://github.com/hashicorp/go-plugin/issues/73'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 897504

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 897504 + upstream
Bug #897504 [src:golang-github-hashicorp-go-plugin] 
golang-github-hashicorp-go-plugin: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu 
&& go test -vet=off -v -p 1 github.com/hashicorp/go-plugin returned exit code 1
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 902943 in 2:2.0.3-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 902943 2:2.0.3-2
Bug #902943 [cryptsetup-initramfs] cryptsetup-initramfs: regression: LV holding 
LUKS device isn't activated at initramfs stage
Marked as found in versions cryptsetup/2:2.0.3-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902248: marked as done (linux-image-4.16.0-2-amd64: General protection fault (with nvidia driver) redulting in Xork proces hanging in "D" state)

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 02:18:27 +
with message-id 
and subject line Bug#901919: fixed in nvidia-graphics-drivers 390.67-2
has caused the Debian Bug report #901919,
regarding linux-image-4.16.0-2-amd64: General protection fault (with nvidia 
driver) redulting in Xork proces hanging in "D" state
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.)


-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.16.16-2
Severity: important

Dear Maintainer,

After booting new kernel after the upgrade the system came up with blank screen 
(initial console boot messages were visible,
but around the time display manager should load the screen went blank). I could 
not switch local consoles.
After logging in remotely i have discovered Xorg process hanging in a "D" 
state. Searching the kernel logs 
I have found the messages below in kern.log. The Nvidia binary driver version 
(built by DKMS) is 390.59.
--- cut ---
Jun 23 22:43:39 sid kernel: [  810.244238] [ cut here ]
Jun 23 22:43:39 sid kernel: [  810.244238] kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Jun 23 22:43:39 sid kernel: [  810.244242] invalid opcode:  [#1] SMP PTI
Jun 23 22:43:39 sid kernel: [  810.244243] Modules linked in: nvidia_drm(PO) 
nvidia_modeset(PO) nvidia(PO) ctr ccm devlink ebtable_filter ebtables 
ip6table_filter ip6_tables iptable_filte
r bnep cpufreq_userspace cpufreq_conservative cpufreq_powersave binfmt_misc 
nls_ascii nls_cp437 vfat fat iTCO_wdt iTCO_vendor_support mxm_wmi intel_rapl 
x86_pkg_temp_thermal intel_powercl
amp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul efi_pstore 
ghash_clmulni_intel intel_cstate intel_uncore intel_rapl_perf arc4 btusb btrtl 
btbcm btintel pcspkr efivars bluetooth 
ath9k ath9k_common drbg snd_virtuoso snd_oxygen_lib ath9k_hw snd_mpu401_uart 
ath snd_rawmidi ansi_cprng snd_seq_device snd_pcm_oss mac80211 snd_mixer_oss 
snd_pcm evdev joydev snd_timer cf
g80211 snd soundcore ecdh_generic mei_me lpc_ich mei sg rfkill shpchp wmi 
coretemp f71882fg
Jun 23 22:43:39 sid kernel: [  810.244271]  video button parport_pc ppdev lp 
parport sunrpc efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 
fscrypto ecb raid10 raid456 async_r
aid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c 
crc32c_generic raid1 raid0 multipath linear md_mod drm_kms_helper drm 
ata_generic sd_mod hid_logitech_hidpp hid_
logitech_dj hid_generic usbhid hid uas usb_storage crc32c_intel ahci libahci 
ipmi_devintf ipmi_msghandler aesni_intel ata_piix xhci_pci aes_x86_64 
crypto_simd cryptd glue_helper ehci_pci 
xhci_hcd ehci_hcd libata i2c_i801 r8169 scsi_mod mii usbcore usb_common fan 
thermal [last unloaded: nvidia]
Jun 23 22:43:39 sid kernel: [  810.244296] CPU: 2 PID: 17283 Comm: Xorg 
Tainted: P   O 4.16.0-2-amd64 #1 Debian 4.16.16-2
Jun 23 22:43:39 sid kernel: [  810.244297] Hardware name: MSI MS-7681/P67A-GD55 
(MS-7681), BIOS V4.3 01/09/2013
Jun 23 22:43:39 sid kernel: [  810.244301] RIP: 0010:usercopy_abort+0x69/0x80
Jun 23 22:43:39 sid kernel: [  810.244302] RSP: 0018:971d4237bb50 EFLAGS: 
00010282
Jun 23 22:43:39 sid kernel: [  810.244303] RAX: 006f RBX: 
0003 RCX: 
Jun 23 22:43:39 sid kernel: [  810.244304] RDX:  RSI: 
8bd35ed16738 RDI: 8bd35ed16738
Jun 23 22:43:39 sid kernel: [  810.244305] RBP: 0003 R08: 
03ba R09: 0004
Jun 23 22:43:39 sid kernel: [  810.244306] R10: a7277e48 R11: 
a79a8dcd R12: 0001
Jun 23 22:43:39 sid kernel: [  810.244307] R13: 8bd34b895cb3 R14: 
 R15: 8bd34b895cf8
Jun 23 22:43:39 sid kernel: [  810.244308] FS:  7f30a422e6c0() 
GS:8bd35ed0() knlGS:
Jun 23 22:43:39 sid kernel: [  810.244309] CS:  0010 DS:  ES:  CR0: 
80050033
Jun 23 22:43:39 sid kernel: [  810.244310] CR2: 7f309cbf5068 CR3: 
00020cae0005 CR4: 000606e0
Jun 23 22:43:39 sid kernel: [  810.244311] Call Trace:
Jun 23 22:43:39 sid kernel: [  810.244316]  __check_heap_object+0xe7/0x120
Jun 23 22:43:39 sid kernel: [  810.244318]  __check_object_size+0x9c/0x1a0
Jun 23 22:43:39 sid kernel: [  810.244429]  os_memcpy_to_user+0x21/0x40 [nvidia]
Jun 23 22:43:39 sid kernel: [  810.244542]  _nv009383rm+0xbf/0xe0 [nvidia]
Jun 23 22:43:39 sid kernel: [  810.244637]  ? _nv028084rm+0x79/0x90 [nvidia]
Jun 23 22:43:39 sid kernel: [  

Bug#901932: marked as done (linux-image-4.16.0-2-amd64: Blank screen after update kernel 4.16.16)

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 02:18:27 +
with message-id 
and subject line Bug#901919: fixed in nvidia-graphics-drivers 390.67-2
has caused the Debian Bug report #901919,
regarding linux-image-4.16.0-2-amd64: Blank screen after update kernel 4.16.16
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.)


-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.16.16-1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Blank (black) screen after kernel image 4.16.16 update. 
At boot the system don't response after the kernel loading, i have to do hard 
reset from power button.
   * 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 ***


-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-1 (2018-06-19)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/nvme0n1p6 ro single

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Default string
chassis_version: Default string
bios_vendor: American Megatrends Inc.
bios_version: 1301
board_vendor: ASUSTeK COMPUTER INC.
board_name: STRIX Z270F GAMING
board_version: Rev 1.xx

** Loaded modules:
snd_hda_codec_hdmi
nls_ascii
nls_cp437
vfat
fat
ext4
crc16
mbcache
jbd2
intel_rapl
x86_pkg_temp_thermal
intel_powerclamp
snd_hda_codec_realtek
coretemp
snd_hda_codec_generic
kvm
snd_hda_intel
irqbypass
snd_hda_codec
crct10dif_pclmul
snd_hda_core
ghash_clmulni_intel
efi_pstore
snd_hwdep
intel_cstate
eeepc_wmi
snd_pcm
snd_timer
asus_wmi
sparse_keymap
mei_me
intel_uncore
joydev
snd
intel_rapl_perf
rfkill
iTCO_wdt
wmi_bmof
efivars
pcspkr
soundcore
iTCO_vendor_support
sg
mei
shpchp
nvidia_drm(PO)
acpi_pad
evdev
drm_kms_helper
drm
nvidia_modeset(PO)
nvidia(PO)
ipmi_devintf
ipmi_msghandler
parport_pc
ppdev
lp
parport
efivarfs
ip_tables
x_tables
autofs4
hid_logitech_hidpp
libcrc32c
crc32_generic
f2fs
crc32c_generic
fscrypto
ecb
hid_logitech_dj
hid_generic
usbhid
hid
sd_mod
crc32_pclmul
crc32c_intel
ahci
libahci
mxm_wmi
aesni_intel
xhci_pci
aes_x86_64
nvme
crypto_simd
xhci_hcd
libata
cryptd
glue_helper
e1000e
i2c_i801
nvme_core
usbcore
scsi_mod
usb_common
wmi
video
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Intel Kaby Lake Host Bridge 
[8086:591f] (rev 05)
Subsystem: ASUSTeK Computer Inc. Intel Kaby Lake Host Bridge [1043:872f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) 
[8086:1901] (rev 05) (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
Kernel modules: shpchp

00:14.0 USB controller [0c03]: Intel Corporation 200 Series PCH USB 3.0 xHCI 
Controller [8086:a2af] (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. 200 Series PCH USB 3.0 xHCI Controller 
[1043:872f]
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: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME 
HECI [8086:a2ba]
Subsystem: ASUSTeK Computer Inc. 200 Series PCH CSME HECI [1043:872f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

Bug#901990: marked as done (linux-image-4.16.0-2-amd64: kernel BUG at startup in usercopy.c ; impossible to boot)

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 02:18:27 +
with message-id 
and subject line Bug#901919: fixed in nvidia-graphics-drivers 390.67-2
has caused the Debian Bug report #901919,
regarding linux-image-4.16.0-2-amd64: kernel BUG at startup in usercopy.c ; 
impossible to boot
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.)


-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.16.16-1
Severity: critical
Justification: breaks the whole system

Dear debian kernel maintainers

after switching to version 4.16.16-1 of linux-image-4.16.0-2-amd64 my system 
does not boot anymore. I obtain a kernel BUG message in syslog in usercopy.c.

Reverting to the current testing version of the amd64 kernel makes the system 
bootable again (and no kernel BUG message appears anymore in syslog).

Since i'm reporting the bug from the recovery startup mode, i can't attach now 
the kernel BUG message, but i'll do it soon after booting with the testing 
version of the kernel.

Best,

Ara

-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-1 (2018-06-19)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.16.0-2-amd64 
root=UUID=745bad16-7720-4350-805d-956d712c90fd ro single

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[   13.738558] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 1)
[   13.738559] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 1)
[   13.738645] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 1)
[   13.739542] CPU5: Core temperature/speed normal
[   13.739542] CPU2: Package temperature/speed normal
[   13.739543] CPU6: Package temperature/speed normal
[   13.739543] CPU3: Package temperature/speed normal
[   13.739544] CPU7: Package temperature/speed normal
[   13.739544] CPU1: Package temperature/speed normal
[   13.739545] CPU0: Package temperature/speed normal
[   13.739546] CPU4: Core temperature/speed normal
[   13.739621] CPU5: Package temperature/speed normal
[   13.739696] CPU4: Package temperature/speed normal
[   13.749499] input: PC Speaker as /devices/platform/pcspkr/input/input12
[   13.882051] iwlwifi :3e:00.0: Detected Intel(R) Dual Band Wireless N 
7260, REV=0x144
[   13.903339] iwlwifi :3e:00.0: base HW address: a4:c4:94:3f:55:b6
[   13.964115] ACPI: AC Adapter [AC] (off-line)
[   13.964335] input: Sleep Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input13
[   13.964446] ACPI: Sleep Button [SLPB]
[   13.964567] input: Lid Switch as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input14
[   13.964673] ACPI: Lid Switch [LID]
[   13.964784] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input15
[   13.964828] ACPI: Battery Slot [BAT0] (battery absent)
[   13.964908] ACPI: Power Button [PWRF]
[   13.969747] ACPI: Battery Slot [BAT1] (battery absent)
[   14.141074] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   14.290474] hp_wmi: query 0xd returned error 0x5
[   14.290609] input: HP WMI hotkeys as /devices/virtual/input/input16
[   14.364058] snd_hda_intel :01:00.1: Disabling MSI
[   14.364141] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client
[   14.461229] media: Linux media interface: v0.10
[   14.528410] Linux video capture interface: v2.00
[   14.619245] usbcore: registered new interface driver snd-usb-audio
[   14.670472] uvcvideo: Found UVC 1.00 device HP HD Webcam (05c8:0374)
[   14.671925] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. 
Opts: (null)
[   14.679051] uvcvideo 1-7:1.0: Entity type for entity Extension 4 was not 
initialized!
[   14.679144] uvcvideo 1-7:1.0: Entity type for entity Extension 3 was not 
initialized!
[   14.679238] uvcvideo 1-7:1.0: Entity type for entity Processing 2 was not 
initialized!
[   14.679344] uvcvideo 1-7:1.0: Entity type for entity Camera 1 was not 
initialized!
[   14.679506] input: HP HD Webcam: HP HD Webcam as 
/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input17
[   14.679652] usbcore: registered new interface driver uvcvideo
[   14.679731] USB Video Class driver (1.1.1)
[   14.690168] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3228: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[   14.690268] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 

Bug#902661: marked as done (linux-image-4.16.0-2-amd64: kernel BUG at /build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!)

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 02:18:27 +
with message-id 
and subject line Bug#901919: fixed in nvidia-graphics-drivers 390.67-2
has caused the Debian Bug report #901919,
regarding linux-image-4.16.0-2-amd64: kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
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.)


-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.16.16-2
Severity: important

Dear Maintainer,

starting X via 'startx' causes every screen to stay black, no more
interaction with mouse or keyboards is possible. So I connected via ssh
and tried to execute 'systemctl reboot'. Only the ssh connection was
closed but the system stayed running without any interaction.
After a reboot I looked again via ssh what dmesg prints out.
It said "usercopy: Kernel memory exposure attempt detected from SLUB
object 'nvidia_stack_cache' (offset: 11440, size 3)!", followed by the
message mentioned in the subject.
Therefore the system is not usable with X in this configuration.

nvidia-driver is in version 390.67-1

-- Package-specific info:
** Version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-2 (2018-06-22)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-2-amd64 root=/dev/mapper/loki-root ro 
cgroup_enable=memory swapaccount=1 quiet

** Tainted: PDO (4225)
 * Proprietary module has been loaded.
 * Kernel has oopsed before.
 * Out-of-tree module has been loaded.

** Kernel log:
[  116.932901]  ? _nv028088rm+0x55/0x90 [nvidia]
[  116.933048]  ? _nv013695rm+0xee/0x100 [nvidia]
[  116.933195]  ? _nv015343rm+0x154/0x270 [nvidia]
[  116.933350]  ? _nv008317rm+0x134/0x1a0 [nvidia]
[  116.933505]  ? _nv008296rm+0x29c/0x2b0 [nvidia]
[  116.933661]  ? _nv001072rm+0xe/0x20 [nvidia]
[  116.933818]  ? _nv007324rm+0xd8/0x100 [nvidia]
[  116.933962]  ? _nv001171rm+0x627/0x830 [nvidia]
[  116.934106]  ? rm_ioctl+0x73/0x100 [nvidia]
[  116.934240]  ? nvidia_ioctl+0xb0/0x730 [nvidia]
[  116.934370]  ? nvidia_ioctl+0x57c/0x730 [nvidia]
[  116.934371]  ? kmem_cache_free+0x19c/0x1d0
[  116.934501]  ? nvidia_frontend_unlocked_ioctl+0x3e/0x50 [nvidia]
[  116.934502]  ? do_vfs_ioctl+0xa4/0x630
[  116.934504]  ? __fput+0x164/0x1e0
[  116.934505]  ? SyS_ioctl+0x74/0x80
[  116.934507]  ? do_syscall_64+0x6c/0x130
[  116.934508]  ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[  116.934509] Code: 2e 00 00 44 8d 42 01 88 50 01 48 8b 05 4a 2e 00 00 8a 48 
02 48 8b 05 40 2e 00 00 41 0b c8 88 48 02 48 8b 05 33 2e 00 00 8a 48 02 <41> 84 
c8 74 0e 66 41 03 d0 b8 ff ff 00 00 66 3b d0 72 e3 f3 c3 
[  126.968483] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 2.416 msecs
[  126.970325] general protection fault:  [#2] SMP NOPTI
[  126.970328] Modules linked in: ctr ccm ipt_MASQUERADE nf_nat_masquerade_ipv4 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat 
nf_conntrack br_netfilter bridge stp llc overlay aufs(O) ebtable_filter 
ebtables devlink ip6table_filter ip6_tables iptable_filter pci_stub vboxpci(O) 
vboxnetadp(O) vboxnetflt(O) vboxdrv(O) tun arc4 snd_hda_codec_hdmi nls_ascii 
rt2800usb nls_cp437 rt2x00usb vfat rt2800lib fat rt2x00lib eeepc_wmi asus_wmi 
sparse_keymap mac80211 snd_hda_codec_realtek video mxm_wmi wmi_bmof efi_pstore 
snd_hda_codec_generic cfg80211 edac_mce_amd kvm_amd ccp crc_ccitt rng_core 
evdev rfkill snd_hda_intel joydev kvm snd_hda_codec irqbypass serio_raw efivars 
fam15h_power sg snd_hda_core snd_hwdep snd_pcm snd_timer
[  126.970372]  snd wmi soundcore button shpchp sp5100_tco k10temp 
nvidia_drm(PO) drm_kms_helper drm nvidia_modeset(PO) nvidia(PO) ipmi_devintf 
ipmi_msghandler it87 hwmon_vid loop parport_pc ppdev lp parport efivarfs 
ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb algif_skcipher 
af_alg uas usb_storage dm_crypt dm_mod sr_mod cdrom raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_holtek_mouse 
hid_generic usbhid hid sd_mod raid6_pq libcrc32c crc32c_generic raid1 raid0 
multipath linear md_mod ohci_pci crct10dif_pclmul crc32_pclmul crc32c_intel 
ghash_clmulni_intel pcbc ahci aesni_intel aes_x86_64 libahci crypto_simd 
glue_helper xhci_pci cryptd ohci_hcd ehci_pci libata xhci_hcd ehci_hcd 
i2c_piix4 usbcore e1000e usb_common scsi_mod
[  126.970449] CPU: 7 PID: 2270 Comm: Xorg Tainted: P  DO 
4.16.0-2-amd64 #1 Debian 4.16.16-2
[ 

Bug#902868: marked as done (linux-image-4.16.0-2-amd64 fails to boot)

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 02:18:27 +
with message-id 
and subject line Bug#901919: fixed in nvidia-graphics-drivers 390.67-2
has caused the Debian Bug report #901919,
regarding linux-image-4.16.0-2-amd64 fails to boot
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.)


-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.16.16-2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?

Up to date Debian testing on 2 July 2018
apt-get update
apt-get upgrade
   linux-image-4.16.0-2-amd64 updated (I think)
reboot

   * What was the outcome of this action?

System did not boot
Re-booted into previous kernel version and reviewed system logs
The following seems to indicate the fault:

Jul  2 09:04:31 kernel: [   15.055880] [ cut here ]
Jul  2 09:04:31 kernel: [   15.055881] kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Jul  2 09:04:31 kernel: [   15.055888] invalid opcode:  [#1] SMP PTI
Jul  2 09:04:31 kernel: [   15.055890] Modules linked in: intel_rapl sb_edac 
x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm snd_hda_codec_hdmi 
irqbypass iTCO_wdt iTCO_vendor_support crct10dif_pclmul crc32_pclmul mxm_wmi 
evdev ghash_clmulni_intel intel_cstate intel_uncore intel_rapl_perf pcspkr 
serio_raw snd_hda_codec_realtek snd_hda_codec_generic sg lpc_ich snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer ioatdma snd mei_me mei 
soundcore shpchp dca wmi button nvidia_drm(PO) drm_kms_helper drm 
nvidia_modeset(PO) nvidia(PO) ipmi_devintf ipmi_msghandler parport_pc ppdev lp 
parport ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic 
fscrypto ecb sr_mod cdrom sd_mod hid_generic usbhid hid crc32c_intel ahci isci 
aesni_intel libahci libsas aes_x86_64 crypto_simd cryptd glue_helper psmouse
Jul  2 09:04:31 kernel: [   15.055943]  sym53c8xx scsi_transport_spi xhci_pci 
i2c_i801 libata ehci_pci xhci_hcd ehci_hcd scsi_transport_sas e1000e usbcore 
scsi_mod usb_common
Jul  2 09:04:31 kernel: [   15.055954] CPU: 2 PID: 1184 Comm: Xorg Tainted: P   
O 4.16.0-2-amd64 #1 Debian 4.16.16-2
Jul  2 09:04:31 kernel: [   15.055956] Hardware name: Viglen VIG430P/X9DAL, 
BIOS 3.0 01/02/2014
Jul  2 09:04:31 kernel: [   15.055963] RIP: 0010:usercopy_abort+0x69/0x80
Jul  2 09:04:31 kernel: [   15.055965] RSP: 0018:b81543c9bb50 EFLAGS: 
00010282
Jul  2 09:04:31 kernel: [   15.055967] RAX: 006f RBX: 
0003 RCX: 
Jul  2 09:04:31 kernel: [   15.055969] RDX:  RSI: 
8d90ffd16738 RDI: 8d90ffd16738
Jul  2 09:04:31 kernel: [   15.055971] RBP: 0003 R08: 
03ac R09: 0004
Jul  2 09:04:31 kernel: [   15.055972] R10: ad877e48 R11: 
adfa8dcd R12: 0001
Jul  2 09:04:31 kernel: [   15.055974] R13: 8d90d828dcb3 R14: 
 R15: 8d90d828dcf8
Jul  2 09:04:31 kernel: [   15.055977] FS:  7f841b5f96c0() 
GS:8d90ffd0() knlGS:
Jul  2 09:04:31 kernel: [   15.055979] CS:  0010 DS:  ES:  CR0: 
80050033
Jul  2 09:04:31 kernel: [   15.055981] CR2: 7f8413711010 CR3: 
0004583c8005 CR4: 000606e0
Jul  2 09:04:31 kernel: [   15.055982] Call Trace:
Jul  2 09:04:31 kernel: [   15.055992]  __check_heap_object+0xe7/0x120
Jul  2 09:04:31 kernel: [   15.055995]  __check_object_size+0x9c/0x1a0
Jul  2 09:04:31 kernel: [   15.056199]  os_memcpy_to_user+0x21/0x40 [nvidia]
Jul  2 09:04:31 kernel: [   15.056416]  _nv009377rm+0xbf/0xe0 [nvidia]
Jul  2 09:04:31 kernel: [   15.056600]  ? _nv028067rm+0x79/0x90 [nvidia]
Jul  2 09:04:31 kernel: [   15.056780]  ? _nv028067rm+0x55/0x90 [nvidia]
Jul  2 09:04:31 kernel: [   15.056950]  ? _nv013694rm+0xee/0x100 [nvidia]
Jul  2 09:04:31 kernel: [   15.057120]  ? _nv015342rm+0x154/0x270 [nvidia]
Jul  2 09:04:31 kernel: [   15.057336]  ? _nv008310rm+0x134/0x1a0 [nvidia]
Jul  2 09:04:31 kernel: [   15.057548]  ? _nv008289rm+0x29c/0x2b0 [nvidia]
Jul  2 09:04:31 kernel: [   15.057759]  ? _nv001072rm+0xe/0x20 [nvidia]
Jul  2 09:04:31 kernel: [   15.057972]  ? _nv007316rm+0xd8/0x100 [nvidia]
Jul  2 09:04:31 kernel: [   15.058181]  ? _nv001171rm+0x627/0x830 [nvidia]
Jul  2 09:04:31 kernel: [   15.058389]  ? rm_ioctl+0x73/0x100 [nvidia]
Jul  2 09:04:31 kernel: [   15.058507]  ? nvidia_ioctl+0xf0/0x720 [nvidia]
Jul  2 09:04:31 kernel: [   15.058623]  ? 

Bug#901919: marked as done (nvidia-driver: black screen with the latest Linux kernel - general protection fault)

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 02:18:27 +
with message-id 
and subject line Bug#901919: fixed in nvidia-graphics-drivers 390.67-2
has caused the Debian Bug report #901919,
regarding nvidia-driver: black screen with the latest Linux kernel - general 
protection fault
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.)


-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.48-3
Severity: grave
Justification: renders package unusable

After upgrade to the Linux kernel 4.16.16-1, I get a black screen.

-- Package-specific info:
uname -a:
Linux zira 4.16.0-2-amd64 #1 SMP Debian 4.16.16-1 (2018-06-19) x86_64 GNU/Linux

/proc/version:
Linux version 4.16.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-23)) #1 SMP Debian 4.16.16-1 (2018-06-19)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 PDT 
2018
GCC version:  gcc version 7.3.0 (Debian 7.3.0-23) 

lspci 'display controller [030?]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK208GLM [Quadro 
K610M] [10de:12b9] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company GK208GLM [Quadro K610M] [103c:2254]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:

Device node permissions:
crw-rw 1 root video 226,   0 2018-06-20 11:46:55 /dev/dri/card0
crw-rw 1 root video 226, 128 2018-06-20 11:46:55 /dev/dri/renderD128
crw-rw-rw- 1 root root  195, 254 2018-06-20 11:46:57 /dev/nvidia-modeset
crw-rw-rw- 1 root root  195,   0 2018-06-20 11:46:57 /dev/nvidia0
crw-rw-rw- 1 root root  195, 255 2018-06-20 11:46:56 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root  8 2018-06-20 11:46:55 pci-:01:00.0-card -> ../card0
lrwxrwxrwx 1 root root 13 2018-06-20 11:46:55 pci-:01:00.0-render -> 
../renderD128
video:x:44:vinc17

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 2018-01-07 20:11:56 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   49 2016-04-11 21:40:32 
/etc/alternatives/glx--libEGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so
lrwxrwxrwx 1 root root   51 2018-01-07 20:11:56 
/etc/alternatives/glx--libEGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libEGL.so.1
lrwxrwxrwx 1 root root   48 2016-04-11 21:40:32 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   48 2016-04-11 21:40:32 
/etc/alternatives/glx--libGL.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so
lrwxrwxrwx 1 root root   50 2018-01-07 20:11:56 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   50 2018-01-07 20:11:56 
/etc/alternatives/glx--libGL.so.1-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGL.so.1
lrwxrwxrwx 1 root root   52 2016-04-11 21:40:32 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   52 2016-04-11 21:40:32 
/etc/alternatives/glx--libGLESv2.so-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so
lrwxrwxrwx 1 root root   54 2018-01-07 20:11:56 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   54 2018-01-07 20:11:56 
/etc/alternatives/glx--libGLESv2.so.2-x86_64-linux-gnu -> 
/usr/lib/mesa-diverted/x86_64-linux-gnu/libGLESv2.so.2
lrwxrwxrwx 1 root root   51 2018-01-07 20:11:56 
/etc/alternatives/glx--libnvidia-cfg.so.1-x86_64-linux-gnu -> 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 2018-01-07 20:11:56 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 2018-01-07 20:11:56 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 2018-01-07 20:11:56 

Bug#902819: marked as done (system freeze (hang task) when launching Xorg(1) after a new version of linux-image installed)

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 02:18:27 +
with message-id 
and subject line Bug#901919: fixed in nvidia-graphics-drivers 390.67-2
has caused the Debian Bug report #901919,
regarding system freeze (hang task) when launching Xorg(1) after a new version 
of linux-image installed
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.)


-- 
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nvidia-driver
Version: 390.48
Severity: serious

Dear Maintainer:
I had upgrade my linux-image to a new version (4.16.0-2, exactly 
4.16.16), then i found the Xorg were failed to start up, the screen shows blank 
and the keyboard stops answer, then i try to grab out what's kernel happening 
in the meantime, and i found kernel gives looping oop with "CPU stuck" and 
"hang task" messages.
Probably the issue were still exists in upstream, i try to remove this 
package and install the offical nVIDIA linux driver (version 390.67), and the 
bug were still exists and perfectly reproduce. Then i remove the nvidia driver 
and turn to uses nouveau, this issue disappear(but as well known, the nouveau 
takes a huge performance penalty on graphics that i can't accept)


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nvidia-driver depends on:
pn  nvidia-alternative
pn  nvidia-driver-bin 
pn  nvidia-driver-libs | nvidia-driver-libs-nonglvnd  
pn  nvidia-installer-cleanup  
pn  nvidia-kernel-dkms | nvidia-kernel-390.48 
pn  nvidia-legacy-check   
pn  nvidia-support
pn  nvidia-vdpau-driver   
pn  xserver-xorg-video-nvidia 

Versions of packages nvidia-driver recommends:
pn  nvidia-persistenced  
pn  nvidia-settings  

Versions of packages nvidia-driver suggests:
pn  nvidia-kernel-dkms | nvidia-kernel-source  
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 390.67-2

We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, 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 901...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Thu, 05 Jul 2018 02:01:31 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 nvidia-driver-libs-nonglvnd 
nvidia-driver-libs-nonglvnd-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglx-nvidia0 libgl1-nvidia-glvnd-glx libgl1-nvidia-glx libnvidia-glcore 
libegl1-nvidia libegl-nvidia0 libgles1-nvidia libgles-nvidia1 libgles2-nvidia 
libgles-nvidia2 libnvidia-eglcore nvidia-egl-common nvidia-egl-icd 
libnvidia-egl-wayland1 nvidia-egl-wayland-common nvidia-egl-wayland-icd 
nvidia-vulkan-common nvidia-vulkan-icd nvidia-nonglvnd-vulkan-common 
nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 nvidia-alternative 
nvidia-kernel-support nvidia-kernel-dkms nvidia-kernel-source 
nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 libcuda1-i386 
libnvidia-compiler libnvidia-fatbinaryloader libnvidia-ptxjitcompiler1 
libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 libnvidia-fbc1 libnvidia-ml1 
nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1 nvidia-detect
Architecture: source
Version: 390.67-2
Distribution: unstable
Urgency: high
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library
 

Processed: retitle 902943 to cryptsetup-initramfs: regression: LV holding LUKS device isn't activated at initramfs stage ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 902943 cryptsetup-initramfs: regression: LV holding LUKS device isn't 
> activated at initramfs stage
Bug #902943 [cryptsetup-initramfs] cryptsetup-initramfs: Encrypted rootfs in 
LVM is not found after upgrade
Changed Bug title to 'cryptsetup-initramfs: regression: LV holding LUKS device 
isn't activated at initramfs stage' from 'cryptsetup-initramfs: Encrypted 
rootfs in LVM is not found after upgrade'.
> tags 902943 + pending
Bug #902943 [cryptsetup-initramfs] cryptsetup-initramfs: regression: LV holding 
LUKS device isn't activated at initramfs stage
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902563: marked as done (golang-github-shirou-gopsutil: FTBFS in machines not having virtualization support (?))

[Debian Bug Tracking System]

Your message dated Thu, 05 Jul 2018 01:34:05 +
with message-id 
and subject line Bug#902563: fixed in golang-github-shirou-gopsutil 2.18.02-2
has caused the Debian Bug report #902563,
regarding golang-github-shirou-gopsutil: FTBFS in machines not having 
virtualization support (?)
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.)


-- 
902563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-shirou-gopsutil
Version: 2.18.02-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu 
github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker 
github.com/shirou/gopsutil/host github.com/shirou/gopsutil/internal/common 
github.com/shirou/gopsutil/load github.com/shirou/gopsutil/mem 
github.com/shirou/gopsutil/net github.com/shirou/gopsutil/process
github.com/shirou/gopsutil
github.com/shirou/gopsutil/internal/common
github.com/shirou/gopsutil/cpu
golang.org/x/sys/unix
github.com/shirou/gopsutil/disk
github.com/shirou/gopsutil/docker

[... snipped ...]

=== RUN   TestVirtualization
--- FAIL: TestVirtualization (0.00s)
host_test.go:137: Virtualization() retuns empty system or role:  , 
host_test.go:140: Virtualization(): , 
=== RUN   TestKernelVersion
--- PASS: TestKernelVersion (0.00s)
host_test.go:152: KernelVersion(): 4.9.0-6-amd64
FAIL
FAILgithub.com/shirou/gopsutil/host 0.020s

[...]

--- PASS: Test_OpenFiles (0.00s)
=== RUN   Test_Kill
--- PASS: Test_Kill (0.10s)
PASS
ok  github.com/shirou/gopsutil/process  0.314s
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu 
github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker 
github.com/shirou/gopsutil/host github.com/shirou/gopsutil/internal/common 
github.com/shirou/gopsutil/load github.com/shirou/gopsutil/mem 
github.com/shirou/gopsutil/net github.com/shirou/gopsutil/process returned exit 
code 1
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The failure is not related to using "dpkg-buildpackage -A" at all, as
a similar error happens here in reproducible builds in the i386 architecture:

https://tests.reproducible-builds.org/debian/rb-pkg/buster/i386/golang-github-shirou-gopsutil.html

I don't even understand the purpose of the test. Following a common
reasoning from Chris Lamb in similar cases: Does this failing test
means the program will not work properly on machines not having
virtualization support? (I don't really think so).

Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-github-shirou-gopsutil
Source-Version: 2.18.02-2

We believe that the bug you reported is fixed in the latest version of
golang-github-shirou-gopsutil, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated 
golang-github-shirou-gopsutil 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: Thu, 05 Jul 2018 11:20:46 +1000
Source: golang-github-shirou-gopsutil
Binary: golang-github-shirou-gopsutil-dev
Architecture: source all
Version: 2.18.02-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Bug#902946: [systemd/systemd] Fails to load autofs module through autofs4 alias (#9501)

[Linus Torvalds]

Trying to send test-patch to the Debian bug tracker too.. I suspect
this will be rejected as spam, but I can try.

Linus
 fs/autofs/Makefile | 4 ++--
 fs/autofs/init.c   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/fs/autofs/Makefile b/fs/autofs/Makefile
index 43fedde15c26..1f85d35ec8b7 100644
--- a/fs/autofs/Makefile
+++ b/fs/autofs/Makefile
@@ -2,6 +2,6 @@
 # Makefile for the linux autofs-filesystem routines.
 #
 
-obj-$(CONFIG_AUTOFS_FS) += autofs.o
+obj-$(CONFIG_AUTOFS_FS) += autofs4.o
 
-autofs-objs := init.o inode.o root.o symlink.o waitq.o expire.o dev-ioctl.o
+autofs4-objs := init.o inode.o root.o symlink.o waitq.o expire.o dev-ioctl.o
diff --git a/fs/autofs/init.c b/fs/autofs/init.c
index cc9447e1903f..79ae07d9592f 100644
--- a/fs/autofs/init.c
+++ b/fs/autofs/init.c
@@ -23,7 +23,7 @@ static struct file_system_type autofs_fs_type = {
 	.kill_sb	= autofs_kill_sb,
 };
 MODULE_ALIAS_FS("autofs");
-MODULE_ALIAS("autofs4");
+MODULE_ALIAS("autofs");
 
 static int __init init_autofs_fs(void)
 {

Bug#902526: marked as done (zsh-syntax-highlighting: FTBFS in buster/sid (does not work with recent debhelper))

[Debian Bug Tracking System]

Your message dated Thu, 5 Jul 2018 03:08:29 +0200
with message-id <20180705010829.gu28...@sym.noone.org>
and subject line Bug#902526 (zsh-syntax-highlighting: FTBFS in buster/sid) 
fixed in 0.6.0-2 upload included in the recent 0.6.0-3 upload
has caused the Debian Bug report #902526,
regarding zsh-syntax-highlighting: FTBFS in buster/sid (does not work with 
recent debhelper)
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.)


-- 
902526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zsh-syntax-highlighting
Version: 0.6.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
cd docs && \
cp highlighters.md all.md && \
printf '\n\nIndividual highlighters 
documentation\n=' >> all.md && \
for doc in highlighters/*.md; do printf '\n\n'; cat "$doc"; done >> all.md
make[1]: Leaving directory '/<>'

[... snipped ...]

ok 1 - [1,8] «rm -rf /»
make[1]: Leaving directory '/<>'
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install -- PREFIX=/usr
make -j1 install 
DESTDIR=/<>/debian/zsh-syntax-highlighting AM_UPDATE_INFO_DIR=no 
PREFIX=/usr
make[2]: Entering directory '/<>'
cd docs && \
cp highlighters.md all.md && \
printf '\n\nIndividual highlighters 
documentation\n=' >> all.md && \
for doc in highlighters/*.md; do printf '\n\n'; cat "$doc"; done >> all.md
install -c -d 
/<>/debian/zsh-syntax-highlighting/usr/share/zsh-syntax-highlighting
install -c -d 
/<>/debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting
cp .version zsh-syntax-highlighting.zsh 
/<>/debian/zsh-syntax-highlighting/usr/share/zsh-syntax-highlighting
cp COPYING.md README.md changelog.md 
/<>/debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting
sed -e '1s/ .*//' -e '/^\[build-status-[a-z]*\]: /d' < README.md > 
/<>/debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/README.md
printf "%s_%s%s\n" "0.6.0-1" "debian"  \
> 
/<>/debian/zsh-syntax-highlighting/usr/share/zsh-syntax-highlighting/.version
printf "%s/%s\n" "debian" "0.6.0-1" \
> 
/<>/debian/zsh-syntax-highlighting/usr/share/zsh-syntax-highlighting/.revision-hash
:
for dirname in highlighters highlighters/*/ ; do \
install -c -d 
/<>/debian/zsh-syntax-highlighting/usr/share/zsh-syntax-highlighting/"$dirname";
 \
for fname in "$dirname"/*.zsh ; do [ -e "$fname" ] && cp "$fname" 
/<>/debian/zsh-syntax-highlighting/usr/share/zsh-syntax-highlighting"/$dirname";
 done; \
done
cp -R docs/* 
/<>/debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting
make[2]: Leaving directory '/<>'
rm 
debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/COPYING.md
make[1]: Leaving directory '/<>'
   dh_installdocs -i
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/<>'
dh_installchangelogs
rm 
debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/changelog.md
rm: cannot remove 
'debian/zsh-syntax-highlighting/usr/share/doc/zsh-syntax-highlighting/changelog.md':
 No such file or directory
debian/rules:14: recipe for target 'override_dh_installchangelogs' failed
make[1]: *** [override_dh_installchangelogs] Error 1
make[1]: Leaving directory '/<>'
debian/rules:18: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zsh-syntax-highlighting.html

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

[ But in this case, I believe this 

Processed: tagging 902563

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 902563 + upstream
Bug #902563 [src:golang-github-shirou-gopsutil] golang-github-shirou-gopsutil: 
FTBFS in machines not having virtualization support (?)
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 902563 is forwarded to https://github.com/shirou/gopsutil/issues/547

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 902563 https://github.com/shirou/gopsutil/issues/547
Bug #902563 [src:golang-github-shirou-gopsutil] golang-github-shirou-gopsutil: 
FTBFS in machines not having virtualization support (?)
Set Bug forwarded-to-address to 'https://github.com/shirou/gopsutil/issues/547'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903008: procps does not show existing process

[Igor Liferenko]

Package: procps
Version: 2:3.3.15-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The following process is running on my machine:

$ ps -ef|grep qemu|grep -v grep
user 28971 28635  0 Jul04 pts/000:01:32 qemu-system-x86_64 -enable-kvm 
-display vnc=localhost:0 -hda newcd-qemu.qcow2 -cdrom newcd-qemu.iso -m 1G 
-boot once=d

It is shown as follows by ps from procps version 2:3.3.14-1+b1:

$ ps h -fC qemu-system-x86_64
user 28971 28635  0 Jul04 pts/0Sl+1:32 qemu-system-x86_64 
-enable-kvm -display vnc=local
Then I upgrade procps to version 2:3.3.15-2 and see an _empty_ output with the 
same command:

$ ps h -fC qemu-system-x86_64


Of course, qemu process is still running:

$ ps -ef|grep qemu|grep -v grep
user 28971 28635  0 Jul04 pts/000:01:32 qemu-system-x86_64 -enable-kvm 
-display vnc=localhost:0 -hda newcd-qemu.qcow2 -cdrom newcd-qemu.iso -m 1G 
-boot once=d

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages procps depends on:
ii  init-system-helpers  1.51
ii  libc62.27-3
ii  libncurses6  6.1+20180210-2
ii  libncursesw6 6.1+20180210-2
ii  libprocps7   2:3.3.15-2
ii  libtinfo66.1+20180210-2
ii  lsb-base 9.20170808

Versions of packages procps recommends:
ii  psmisc  23.1-1+b1

procps suggests no packages.

-- no debconf information

Processed: severity of 902998 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 902998 serious
Bug #902998 [libpam-systemd] libpam-systemd: breaks installing build depends 
e.g. gnupg2
Severity set to 'serious' from 'critical'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899896: marked as done (euca2ools: Invalid maintainer address pkg-eucalyptus-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Thu, 5 Jul 2018 07:55:44 +0900
with message-id <20180704225544.jtjijb3orqkoj...@bubu.plessy.net>
and subject line Re: Bug#899896: euca2ools: Invalid maintainer address 
pkg-eucalyptus-maintain...@lists.alioth.debian.org
has caused the Debian Bug report #899896,
regarding euca2ools: Invalid maintainer address 
pkg-eucalyptus-maintain...@lists.alioth.debian.org
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.)


-- 
899896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:euca2ools
Version: 3.3.1-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of euca2ools,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package euca2ools since the list address
pkg-eucalyptus-maintain...@lists.alioth.debian.org used in the
Maintainer: field was not transferred to the alioth-lists service that
provides a continuation for the lists in the @lists.alioth.debian.org
domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-eucalyptus-maintain...@lists.alioth.debian.org is 1.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Le Thu, May 24, 2018 at 09:43:52AM +0200, Christoph Biedl a écrit :
> 
> as you've probably heard, Debian's alioth services are shutting down.
> This affects your package euca2ools since the list address
> pkg-eucalyptus-maintain...@lists.alioth.debian.org used in the
> Maintainer: field was not transferred to the alioth-lists service that
> provides a continuation for the lists in the @lists.alioth.debian.org
> domain.

I have changed the address to "Debian Cloud team
" and checked that it works.

-- 
Charles--- End Message ---

Processed: severity of 901919 is serious, severity of 899998 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 901919 serious
Bug #901919 [nvidia-driver] nvidia-driver: black screen with the latest Linux 
kernel - general protection fault
Bug #901932 [nvidia-driver] linux-image-4.16.0-2-amd64: Blank screen after 
update kernel 4.16.16
Bug #901990 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at startup 
in usercopy.c ; impossible to boot
Bug #902248 [nvidia-driver] linux-image-4.16.0-2-amd64: General protection 
fault (with nvidia driver) redulting in Xork proces hanging in "D" state
Bug #902661 [nvidia-driver] linux-image-4.16.0-2-amd64: kernel BUG at 
/build/linux-uwVqDp/linux-4.16.16/mm/usercopy.c:100!
Bug #902773 [nvidia-driver] nvidia-driver: Kernel BUG on 4.16.16 with 390.67-1, 
crashes on desktop boot
Bug #902819 [nvidia-driver] system freeze (hang task) when launching Xorg(1) 
after a new version of linux-image installed
Bug #902868 [nvidia-driver] linux-image-4.16.0-2-amd64 fails to boot
Bug #902891 [nvidia-driver] nvidia-kernel-source: usercopy: Kernel memory 
exposure attempt detected from SLUB object 'nvidia_stack_cache'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> severity 88 serious
Bug #88 [nvidia-legacy-340xx-kernel-dkms] nvidia-legacy-340xx-kernel-dkms: 
Dmesg output: "Bad or missing usercopy whitelist? Kernel memory exposure 
attempt detected from SLUB object 'nvidia_stack_t'"
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
88: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=88
901919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919
901932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901932
901990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901990
902248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902248
902661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902661
902773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902773
902819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902819
902868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902868
902891: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902891
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902130: marked as done (ocaml-theora FTBFS with ocaml-ogg 0.5.2-1)

[Debian Bug Tracking System]

Your message dated Thu, 5 Jul 2018 00:13:07 +0200
with message-id <01139d38-cb2d-1926-f199-9f404f456...@gmail.com>
and subject line Fixed by upload into unstable
has caused the Debian Bug report #902130,
regarding ocaml-theora FTBFS with ocaml-ogg 0.5.2-1
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.)


-- 
902130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-theora
Version: 0.3.0-3
Severity: serious
Tags: buster sid ftbfs

https://buildd.debian.org/status/package.php?p=ocaml-theora=sid

...
ocamlc.opt -c -cc "gcc" -ccopt "-fPIC -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include  -Wall -DCAML_NAME_SPACE \
-DPIC -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include  \
  -I/usr/lib/ocaml/ogg  -o theora_stubs.o " 
theora_stubs.c 
ar rcs libtheora_stubs.a  theora_stubs.o
ocamlc.opt -c -g -I /usr/lib/ocaml/ogg theora.mli
File "theora.mli", line 163, characters 27-39:
Error: Unbound type constructor Ogg.Stream.t
make[3]: *** [OCamlMakefile:934: theora.cmi] Error 2
--- End Message ---
--- Begin Message ---
Package: ocaml-theora
Version: 0.3.1-2

Fixed by upload of 0.3.1-2 into unstable




signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#902133: marked as done (ocaml-opus FTBFS with ocaml-ogg 0.5.2-1)

[Debian Bug Tracking System]

Your message dated Thu, 5 Jul 2018 00:11:58 +0200
with message-id <1c333bc3-ca4a-fa41-2bad-ce7ebccdc...@gmail.com>
and subject line Fixed by new upload into unstable
has caused the Debian Bug report #902133,
regarding ocaml-opus FTBFS with ocaml-ogg 0.5.2-1
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.)


-- 
902133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ocaml-opus
Version: 0.1.0-4
Severity: serious
Tags: buster sid ftbfs

https://buildd.debian.org/status/package.php?p=ocaml-opus=sid

...
ocamlc.opt -c -dtypes -g -I /usr/lib/ocaml/ogg opus.mli
File "opus.mli", line 56, characters 46-58:
Error: Unbound type constructor Ogg.Stream.t
make[3]: *** [OCamlMakefile:1048: opus.cmi] Error 2
--- End Message ---
--- Begin Message ---
Package: ocaml-opus
Version: 0.1.2-2

Fixed by upload of 0.1.2-2 into unstable




signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

[Sven Joachim]

On 2018-07-04 23:33 +0200, Michael Biebl wrote:

> Control: tags -1 moreinfo
>
>
> This is what I get when I build a package using pbuilder, which
> build-depends on policykit-1 (which in turn pulls in libpam-systemd):
>
> The following packages have unmet dependencies:
>  systemd : Breaks: systemd-shim (< 10-4~) but 10-3 is to be installed
> The following actions will resolve these dependencies:
>
>  Install the following packages:
> 1) systemd-sysv [239-4 (unstable)]
>
>  Keep the following packages at their current version:
> 2) systemd-shim [Not Installed]
>
> And the build succeeds.
>
> Or running apt install libpam-systemd inside a chroot:
>
> # apt install libpam-systemd
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following additional packages will be installed:
>   dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
> libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
>   libidn11 libip4tc0 libjson-c3 libkmod2 libprocps7 lsb-base procps
> systemd systemd-sysv
> Suggested packages:
>   default-dbus-session-bus | dbus-session-bus systemd-container policykit-1
> Recommended packages:
>   psmisc libnss-systemd
> The following NEW packages will be installed:
>   dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
> libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
>   libidn11 libip4tc0 libjson-c3 libkmod2 libpam-systemd libprocps7
> lsb-base procps systemd systemd-sysv
> 0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
> Need to get 0 B/5069 kB of archives.
> After this operation, 17.4 MB of additional disk space will be used.
> Do you want to continue? [Y/n] n
> Abort.

This works, but "apt install libgtk-3-0" does not, for instance:

,
| # apt install libgtk-3-0
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
| 
| The following packages have unmet dependencies:
|  libgtk-3-0 : Depends: libgtk-3-common (>= 3.22.30-2) but it is not going to 
be installed
|   Depends: librest-0.7-0 (>= 0.7) but it is not going to be 
installed
|   Depends: libsoup2.4-1 (>= 2.4.0) but it is not going to be 
installed
| E: Unable to correct problems, you have held broken packages.
`

Cheers,
   Sven

Bug#897174: marked as done (Package erroneously expects googletest headers in /usr/include)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 21:50:18 +
with message-id 
and subject line Bug#897174: fixed in meson 0.47.0-1
has caused the Debian Bug report #897174,
regarding Package erroneously expects googletest headers in /usr/include
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.)


-- 
897174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:meson
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

The googletest package provides full sources -- including header files
-- in /usr/src/googletest.  Prior to version 1.8.0-9, a second copy of
the headers was mistakenly installed into /usr/include.

Your package relies on this behaviour and now fails to build since
googletest version 1.8.0-9 no longer installs the duplicate header
files.

I can suggest three alternative approaches to fix this.

1. Modify the build to look for headers in /usr/src/googletest.

2. Change to using pre-build libraries, in which case you would switch
build-dependencies to libgtest-dev and libgmock-dev rather than using
googletest.

3. Add build-dependency on libgtest-dev to ensure the headers are
located in /usr/include as before.  If gmock is used, then add a
dependency on libgmock-dev as well.


-Steve
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.47.0-1

We believe that the bug you reported is fixed in the latest version of
meson, 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 897...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson 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, 02 Jul 2018 20:54:05 +0300
Source: meson
Binary: meson
Architecture: source
Version: 0.47.0-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Description:
 meson  - high-productivity build system
Closes: 897174
Changes:
 meson (0.47.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Switch to using standard Python install because trying to keep the
 library private is just too damn hard and annoying.
   * Updated Google test dependencies. Closes: #897174.
   * Added build deps to test new functionality.
Checksums-Sha1:
 3be217212a02e2204b7d6bb2ed217e046b919b06 3349 meson_0.47.0-1.dsc
 a83d0b1432302c4233cd0db39140e6a54c259931 1246350 meson_0.47.0.orig.tar.gz
 88f953a0110f44a810f1db4894be808233b437d1 11440 meson_0.47.0-1.debian.tar.xz
 e8096ae08eac8fe7013ae98f4c4e5a04a3676a93 6274 meson_0.47.0-1_source.buildinfo
Checksums-Sha256:
 887139e20e209c62696e1f68dcd516e9d2f5d39a52b5aaa2995f27b878fc0053 3349 
meson_0.47.0-1.dsc
 1bd360a58c28039cdb3b8ce909764e90a58481deb79396227ba4081af377f009 1246350 
meson_0.47.0.orig.tar.gz
 1d04592a61283eedf23001eb39f97ed9315041a9b7f9c0d72c401ea914c9a3f9 11440 
meson_0.47.0-1.debian.tar.xz
 564393ec36abe1c41ce718c7973dc7e7821b2c03aafef4b212ba8e76300f 6274 
meson_0.47.0-1_source.buildinfo
Files:
 aee49dd54c8aea6fba3958c3ce7d1743 3349 devel optional meson_0.47.0-1.dsc
 5ec10121fcd1e130fdc7e9a10d762a4c 1246350 devel optional 
meson_0.47.0.orig.tar.gz
 d358702271a27fd833bb3bc3f8a9fc18 11440 devel optional 
meson_0.47.0-1.debian.tar.xz
 f1f552cab5ced7143b2152f560ffe4cb 6274 devel optional 
meson_0.47.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEExkOAo1eT0DvBz+1oxrkYDUvYt64FAls9Or8ACgkQxrkYDUvY
t66jCw/+Leppw37PsPiJXAPb7m9UP6yTQijcCqfNM543nHOGtgFdP76m5xe/GKio
Qe3I560QVnNT2KaGWZQK74ljZBpZdw8xJuwA93vJqPSXcEpRAngu4QOzppfEZS3y
xDbxqX6Ph6/UmMrAOBKzlIJllvYf8ZkMYqh2ZET+rvVHCL2xpLQLq51LYuO18SFB
H4j0DNDBtwDQ9ixSV4JZTFUOEQ3VyNRJsy8PQVnhbg+ioKZfAK4DPJ9vNIBS1EZ1
n9jTC9jarNOp0PVugt7tXsDH//REHP/VmvxfL7LEOut+G4BtiY9rXjJMA4SQivTx
9KvjwdxdH420xPMJDV+fWWdttdFodSu8XEmNSF8N4VXBVd62VwMBwwuX9d8LouL4
QyHy2eX7KnCD3BfTSQ7NPy/tFQFVZHPm+lwb/Ditkyxj7X3WTH3rFjXQcrsHK6UY
CaT6eG+RmJymJQdI4Bas4BxgoR5eSi2Tapap6/OvllE0fPy39RJxUM1s36DN7nez
PeaOUxPKDhrOzlwU0gYMNasqH5l21iSUtni3JxXBg8DDz0TyguIL4fvKHPJ8ieTh
qiuwT7fCFvy8R2/aS5/Tg3TA3CAKvjvNTkrvU6zEPOdbEYycW2bFhcpo9eNUM6IG

Bug#882103: marked as done (python-pkg-resources: crashing with "ImportError: No module named load_entry_point")

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 21:47:18 +
with message-id 
and subject line Bug#882103: fixed in obfsproxy 0.2.13-2+deb9u1
has caused the Debian Bug report #882103,
regarding python-pkg-resources: crashing with "ImportError: No module named 
load_entry_point"
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.)


-- 
882103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pkg-resources
Version: 36.7.1-1
Severity: important

Dear Maintainer,

I have a cron job running each day and it stopped working.

When I investigated I found this error.

Traceback (most recent call last):
  File "/usr/bin/obfsproxy", line 6, in 
from pkg_resources import load_entry_point
ImportError: cannot import name load_entry_point




-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages python-pkg-resources depends on:
ii  python  2.7.14-1

python-pkg-resources recommends no packages.

Versions of packages python-pkg-resources suggests:
ii  python-setuptools  36.7.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: obfsproxy
Source-Version: 0.2.13-2+deb9u1

We believe that the bug you reported is fixed in the latest version of
obfsproxy, 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 882...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated obfsproxy 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: Wed, 28 Feb 2018 23:03:50 +0200
Source: obfsproxy
Binary: obfsproxy
Architecture: source
Version: 0.2.13-2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Adrian Bunk 
Description:
 obfsproxy  - pluggable transport proxy for Tor
Closes: 882103
Changes:
 obfsproxy (0.2.13-2+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Don't install the broken AppArmor profile. (Closes: #882103)
Checksums-Sha1:
 c6bf28f583316a2ddcbc0b60db27dbbd073400cf 2217 obfsproxy_0.2.13-2+deb9u1.dsc
 40b92279212a09658e3b83af768305ca493e4cb3 14620 
obfsproxy_0.2.13-2+deb9u1.debian.tar.xz
Checksums-Sha256:
 f0587f26245c990bab05a7aa1e3dc13d1aa42c19857ea69cc4bfa63ccf98e6a6 2217 
obfsproxy_0.2.13-2+deb9u1.dsc
 321ba1b283c73de51417433ba77f5bb2b6a7424d5acdff9fecd1779e05c35f1c 14620 
obfsproxy_0.2.13-2+deb9u1.debian.tar.xz
Files:
 bf795e29c4a04ea8f14502b76f144a3e 2217 net extra obfsproxy_0.2.13-2+deb9u1.dsc
 a2669a36bd952628b85d4d94b421cf55 14620 net extra 
obfsproxy_0.2.13-2+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqXHH8ACgkQiNJCh6LY
mLGxAg//SXNugPJSv887U38HXqmqVVw1rH7fonVF+vgdQMORJ1jSiTazY27viq8M
KYML71gMpxNPTKHPXqG7QsxLnObnHpCqb9iyfT0Kk+E65LL/es4/GSByVPWunmW0
zCJoDhy9bPmOJQBf7yfX5V6RpBb8gx5xOdCrw6wws4hs3awyAXRy2biLotJh194Y
rpfgaqENXe0bQ2H8RXq+AhVXG9cp7VJt1Gc/HCJAOAyUK6eBP7dOFEXVKW45+ZUl
sajfbt1DfrNVyCdAFe8yl1aw0glmTOfBG+aiNpc0wpEZr3K64lCCz49epbtXkP6G
Bi3K+GZnlMk7tJ+FnvGoq+sZn//WDCWH2SHmUtrGM4L3xnFR2fYky09y2y32GKQH
gc4Q9P8n6KodLQi0EJW0jhYm29uqc5/1rym9xOxEl4Nzrym+RMrhyasnnrguNZ5Y
xMQpQaP+GC4TNX76U0VPsvYT/tLxMBKc5Ld/fgEr130UdWBahnUo27p5QtbFeOUL
6rHWNjRJxmWRq3PuBx5CRtMhmAUr03R0GJjewlBEbXxEZtWWf7cOO6XoUWp2ciKj
8TSXc0Z8y0Ll8ZI7sib1zs9ZkPadMLYwuWJshbqTBL+HQqp8i33IsMErSpoG9abS
sjrMI5ogahFkMlcz+UTpM35EQ12SJduqZ/Pm0Xodh1lecDxVyYk=
=i3vn
-END PGP SIGNATURE End Message ---

Bug#902723: marked as done (CVE-2018-1000528)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 21:47:17 +
with message-id 
and subject line Bug#902723: fixed in gosa 2.7.4+reloaded2-13+deb9u1
has caused the Debian Bug report #902723,
regarding CVE-2018-1000528
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.)


-- 
902723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gosa
Severity: grave
Tags: security

This was assigned CVE-2018-1000528:
https://github.com/gosa-project/gosa-core/commit/56070d6289d47ba3f5918885954dcceb75606001
https://github.com/gosa-project/gosa-core/issues/14

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: gosa
Source-Version: 2.7.4+reloaded2-13+deb9u1

We believe that the bug you reported is fixed in the latest version of
gosa, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated gosa 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: Wed, 04 Jul 2018 09:15:17 +0200
Source: gosa
Binary: gosa gosa-dev gosa-desktop gosa-schema gosa-help-en gosa-help-de 
gosa-help-fr gosa-help-nl gosa-plugin-connectivity gosa-plugin-dhcp 
gosa-plugin-dhcp-schema gosa-plugin-dns gosa-plugin-dns-schema gosa-plugin-fai 
gosa-plugin-fai-schema gosa-plugin-gofax gosa-plugin-gofon gosa-plugin-goto 
gosa-plugin-kolab gosa-plugin-kolab-schema gosa-plugin-ldapmanager 
gosa-plugin-mail gosa-plugin-mit-krb5 gosa-plugin-mit-krb5-schema 
gosa-plugin-nagios gosa-plugin-nagios-schema gosa-plugin-netatalk 
gosa-plugin-opengroupware gosa-plugin-openxchange 
gosa-plugin-openxchange-schema gosa-plugin-opsi gosa-plugin-phpgw 
gosa-plugin-phpgw-schema gosa-plugin-phpscheduleit 
gosa-plugin-phpscheduleit-schema gosa-plugin-pptp gosa-plugin-pptp-schema 
gosa-plugin-pureftpd gosa-plugin-pureftpd-schema gosa-plugin-rolemanagement 
gosa-plugin-rsyslog gosa-plugin-samba gosa-plugin-scalix gosa-plugin-squid 
gosa-plugin-ssh gosa-plugin-ssh-schema gosa-plugin-sudo gosa-plugin-sudo-schema 
gosa-plugin-systems
 gosa-plugin-uw-imap
 gosa-plugin-webdav
Architecture: source all
Version: 2.7.4+reloaded2-13+deb9u1
Distribution: stretch-security
Urgency: medium
Maintainer: Debian Edu Packaging Team 

Changed-By: Mike Gabriel 
Description:
 gosa   - Web Based LDAP Administration Program
 gosa-desktop - Desktop integration for GOsa²
 gosa-dev   - GOsa² development utilities
 gosa-help-de - German online help for GOsa²
 gosa-help-en - English online help for GOsa
 gosa-help-fr - French online help for GOsa²
 gosa-help-nl - Dutch online help for GOsa
 gosa-plugin-connectivity - connectivity plugin for GOsa²
 gosa-plugin-dhcp - dhcp plugin for GOsa²
 gosa-plugin-dhcp-schema - LDAP schema for GOsa² dhcp plugin
 gosa-plugin-dns - dns plugin for GOsa²
 gosa-plugin-dns-schema - LDAP schema for GOsa² dns plugin
 gosa-plugin-fai - fai plugin for GOsa²
 gosa-plugin-fai-schema - LDAP schema for GOsa² fai plugin
 gosa-plugin-gofax - gofax plugin for GOsa²
 gosa-plugin-gofon - gofon plugin for GOsa²
 gosa-plugin-goto - goto plugin for GOsa²
 gosa-plugin-kolab - kolab plugin for GOsa²
 gosa-plugin-kolab-schema - LDAP schema for GOsa² kolab plugin
 gosa-plugin-ldapmanager - ldapmanager plugin for GOsa²
 gosa-plugin-mail - base mail plugin for GOsa²
 gosa-plugin-mit-krb5 - mit-krb5 plugin for GOsa²
 gosa-plugin-mit-krb5-schema - LDAP schema for GOsa² mit-krb5 plugin
 gosa-plugin-nagios - nagios plugin for GOsa²
 gosa-plugin-nagios-schema - LDAP schema for GOsa² nagios plugin
 gosa-plugin-netatalk - netatalk plugin for GOsa²
 gosa-plugin-opengroupware - opengroupware plugin for GOsa²
 gosa-plugin-openxchange - openxchange plugin for GOsa²
 gosa-plugin-openxchange-schema - LDAP schema for GOsa² openxchange plugin
 gosa-plugin-opsi - opsi plugin for GOsa²
 gosa-plugin-phpgw - phpgw plugin for GOsa²
 gosa-plugin-phpgw-schema - LDAP schema for GOsa² phpgw plugin
 gosa-plugin-phpscheduleit - phpscheduleit plugin for GOsa²
 gosa-plugin-phpscheduleit-schema - LDAP schema for GOsa² phpscheduleit plugin
 gosa-plugin-pptp - pptp plugin for 

Bug#881753: marked as done (local-apt-repository: breaks apt operation if removed)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 21:47:17 +
with message-id 
and subject line Bug#881753: fixed in local-apt-repository 0.4+deb9u1
has caused the Debian Bug report #881753,
regarding local-apt-repository: breaks apt operation if removed
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.)


-- 
881753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: local-apt-repository
Version: 0.4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package can cause problems.

If local-apt-repository is removed (but not purged) from stretch,
/etc/apt/sources.list.d/local-apt-repository.list is left behind.

Subsequent 'apt-get update' will fail since the repository is no longer
available:

4m5.4s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpeMVqg3', 'apt-get', 'update']
  Get:1 file:/var/lib/local-apt-repository ./ InRelease
  Ign:1 file:/var/lib/local-apt-repository ./ InRelease
  Get:2 file:/var/lib/local-apt-repository ./ Release
  Ign:2 file:/var/lib/local-apt-repository ./ Release
  Get:3 file:/var/lib/local-apt-repository ./ Sources
  Ign:3 file:/var/lib/local-apt-repository ./ Sources
  Get:4 file:/var/lib/local-apt-repository ./ Packages
  Ign:4 file:/var/lib/local-apt-repository ./ Packages
  Get:5 file:/var/lib/local-apt-repository ./ Translation-en
  Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
  Get:3 file:/var/lib/local-apt-repository ./ Sources
  Ign:3 file:/var/lib/local-apt-repository ./ Sources
  Get:4 file:/var/lib/local-apt-repository ./ Packages
  Ign:4 file:/var/lib/local-apt-repository ./ Packages
  Get:5 file:/var/lib/local-apt-repository ./ Translation-en
  Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
  Get:3 file:/var/lib/local-apt-repository ./ Sources
  Ign:3 file:/var/lib/local-apt-repository ./ Sources
  Get:4 file:/var/lib/local-apt-repository ./ Packages
  Ign:4 file:/var/lib/local-apt-repository ./ Packages
  Get:5 file:/var/lib/local-apt-repository ./ Translation-en
  Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
  Get:3 file:/var/lib/local-apt-repository ./ Sources
  Ign:3 file:/var/lib/local-apt-repository ./ Sources
  Get:4 file:/var/lib/local-apt-repository ./ Packages
  Ign:4 file:/var/lib/local-apt-repository ./ Packages
  Get:5 file:/var/lib/local-apt-repository ./ Translation-en
  Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
  Get:3 file:/var/lib/local-apt-repository ./ Sources
  Ign:3 file:/var/lib/local-apt-repository ./ Sources
  Get:4 file:/var/lib/local-apt-repository ./ Packages
  Ign:4 file:/var/lib/local-apt-repository ./ Packages
  Get:5 file:/var/lib/local-apt-repository ./ Translation-en
  Ign:5 file:/var/lib/local-apt-repository ./ Translation-en
  Get:3 file:/var/lib/local-apt-repository ./ Sources
  Err:3 file:/var/lib/local-apt-repository ./ Sources
File not found - /var/lib/local-apt-repository/./Sources (2: No such file 
or directory)
  Get:4 file:/var/lib/local-apt-repository ./ Packages
  Ign:4 file:/var/lib/local-apt-repository ./ Packages
  Get:6 http://ftp.de.debian.org/debian buster InRelease [136 kB]
  Get:7 http://ftp.de.debian.org/debian buster/main amd64 Packages [7258 kB]
  Get:8 http://ftp.de.debian.org/debian buster/main Translation-en [5553 kB]
  Fetched 12.9 MB in 18s (696 kB/s)
  Reading package lists...
  E: Failed to fetch file:/var/lib/local-apt-repository/./Sources  File not 
found - /var/lib/local-apt-repository/./Sources (2: No such file or directory)
  E: Some index files failed to download. They have been ignored, or old ones 
used instead.


Andreas


local-apt-repository_0.4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: local-apt-repository
Source-Version: 0.4+deb9u1

We believe that the bug you reported is fixed in the latest version of
local-apt-repository, 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 881...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated local-apt-repository 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 

Bug#862065: marked as done (starplot: does not start due to invalid pointer error)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 21:47:18 +
with message-id 
and subject line Bug#862065: fixed in starplot 0.95.5-8.2+deb9u1
has caused the Debian Bug report #862065,
regarding starplot: does not start due to invalid pointer error
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.)


-- 
862065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: starplot
Version: 0.95.5-8.2
Severity: important

Dear Maintainer,

Starplot doesn't start and returns `*** Error in `starplot': free(): invalid
pointer: 0x55f5759e60d0 ***` when started from terminal.

However, `valgrind starplot` allows starplot to run normally.

This is a completely fresh installation of starplot on a computer that's never
had starplot installed before (so no leftover data in ${HOME}).



-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64
 (x86_64)

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

Versions of packages starplot depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-10
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgcc1  1:6.3.0-16
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk2.0-0  2.24.31-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libstdc++6   6.3.0-16

Versions of packages starplot recommends:
ii  stardata-common  0.8+b1

Versions of packages starplot suggests:
pn  gliese  
pn  yale

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: starplot
Source-Version: 0.95.5-8.2+deb9u1

We believe that the bug you reported is fixed in the latest version of
starplot, 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 862...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated starplot 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: Wed, 28 Feb 2018 22:37:50 +0200
Source: starplot
Binary: starplot
Architecture: source
Version: 0.95.5-8.2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Francisco Manuel Garcia Claramonte 
Changed-By: Adrian Bunk 
Description:
 starplot   - 3-dimensional perspective star map viewer
Closes: 862065
Changes:
 starplot (0.95.5-8.2+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Add patch from Bernhard Übelacker to fix startup crash.
 (Closes: #862065)
Checksums-Sha1:
 7b21de521edcdc29d6ee66f54c8b539bea0782aa 1899 starplot_0.95.5-8.2+deb9u1.dsc
 4c5363e9def685e91bcfefb1153aefd00721e70e 14448 
starplot_0.95.5-8.2+deb9u1.debian.tar.xz
Checksums-Sha256:
 13b5f5d0b2d08d1b034565b5b3aed1aea64065a7a934c760fb889f0e466c0d57 1899 
starplot_0.95.5-8.2+deb9u1.dsc
 dd6fdf17bd8920cb99835e98c5b2b7aef27c3335d41b00c38e231eb9ea98ebb3 14448 
starplot_0.95.5-8.2+deb9u1.debian.tar.xz
Files:
 69f2c643218c26cacee9b67d106e9a3f 1899 science optional 
starplot_0.95.5-8.2+deb9u1.dsc
 571b90c7163e1eca19b4936a7b5957e3 14448 science optional 
starplot_0.95.5-8.2+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqXFNwACgkQiNJCh6LY
mLEeEQ/+Ky/SHCDnWBB/xs0iXfc+VgqIaJVSouBgg9a9roM/ywUFPRRHrbZVXZCr
u7uwtBaEfnMO1l94REC4PJ+B0GKx1ZSzykcHRa3WCaUHhZZPUuXJg1rkohn1Ofev
3u5UWuChTW7LAVxwcb0xJmaTOAL3fpyQ+yLZ1TPB0DbJqPIvbqhrZ16HiBHpRSfc
iOfhppPydfh+CNwCdTwCZKD6gBS+3FmJWDXLFVvS5sXyYqm7DjNXT3f0816HTtgI
EAjTGG6+EnMWgMIRuAR9xhuMKhmepqusTKlRwFbfYCPSVGqDB+wGGogBGCtPijeu
SwivoI7iTFUBpRz5vQIVCfPIGBxOGSz2y1vCs+LcirUB4ANPW7oBWgyENPyzwcPi
/cmsRRENZ4gbdfjXTTeQ71XdsaJik1sMD06Q/a5pRVVhHUDBKIL5/TOCYgFQ0WwN
hVT9WtUBCr0Gy/LP1g/Rbtelbmh0mVH3we3Je+fcnIDeQ7UT4Bv39ktgh2/h2ZZv
REUU4HWZNuBO89jhmEXPlpaPf1yCQknJfKH3phtYjTQ2tZeH8jiFgQxaonE/X640
AjNAehIEO8qkyz+61bDi6FD1tOmJElUxV6wrEAmpfcGIiex28Q3S9kodwgYSdns4
4giqoSbUzzVbhh8fbZkC3MWVkQSyU0amM4tdlwT142gSFM05SBs=

Processed: Re: Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #902998 [libpam-systemd] libpam-systemd: breaks installing build depends 
e.g. gnupg2
Added tag(s) moreinfo.

-- 
902998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

[Michael Biebl]

Control: tags -1 moreinfo


This is what I get when I build a package using pbuilder, which
build-depends on policykit-1 (which in turn pulls in libpam-systemd):

The following packages have unmet dependencies:
 systemd : Breaks: systemd-shim (< 10-4~) but 10-3 is to be installed
The following actions will resolve these dependencies:

 Install the following packages:
1) systemd-sysv [239-4 (unstable)]

 Keep the following packages at their current version:
2) systemd-shim [Not Installed]

And the build succeeds.

Or running apt install libpam-systemd inside a chroot:

# apt install libpam-systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
  libidn11 libip4tc0 libjson-c3 libkmod2 libprocps7 lsb-base procps
systemd systemd-sysv
Suggested packages:
  default-dbus-session-bus | dbus-session-bus systemd-container policykit-1
Recommended packages:
  psmisc libnss-systemd
The following NEW packages will be installed:
  dbus dmsetup libapparmor1 libargon2-0 libargon2-1 libcap2
libcryptsetup12 libdbus-1-3 libdevmapper1.02.1 libexpat1
  libidn11 libip4tc0 libjson-c3 libkmod2 libpam-systemd libprocps7
lsb-base procps systemd systemd-sysv
0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/5069 kB of archives.
After this operation, 17.4 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.


-- 
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

Processed: affects 902941

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 902941 src:lua-luv
Bug #902941 [libuv1] libuv1 1.21 broke ABI without SONAME bump
Added indication that 902941 affects src:lua-luv
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

[Alexis Murzeau]

Hi,

Le 27/06/2018 à 00:21, Alexis Murzeau a écrit :
> Le 26/06/2018 à 04:13, vasudev-debian a écrit :
>> I'll have a look. if possible clone from team repo and raise a pr on it.
>>
> 
> I've created 3 PR at [0], one for each branch (in this order: upstream,
> pristine-tar and master).
> The 5.0.10+really4.7.0~dfsg orig tar I imported is the same as the one
> used for 4.7.0~dfsg.
> Debian/watch file tracks the v4 branch (ignoring v5.*)
> I've also added a autopkgtest test to ensure symlinks are not broken.
> 
> [0] https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests
> 
> Le 26/06/2018 à 09:26, Sean Whitton a écrit :
>>
>> The git history is up to you but resetting the changelog seems like a
>> really bad idea -- it is confusing to see that there are uploads to the
>> archive that are not present in the changelog.
>>
>> I think you should at least retain d/changelog, even if you reset
>> everything else (personally, I would keep all the git history).
>>
> 
> I finally kept the full changelog and git history, to not lie the past
> :) if someone wonders what happened.
> Thanks for your advices.
> 

Vasudev, did you get a chance to take a look to the merge requests [0] ?

[0] https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests

-- 
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F



signature.asc
Description: OpenPGP digital signature

Processed: reassign 902941 to libuv1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 902941 libuv1 1.21.0-1
Bug #902941 [src:libuv1, src:lua-luv] libuv1 1.21 broke ABI without SONAME bump
Bug reassigned from package 'src:libuv1, src:lua-luv' to 'libuv1'.
Ignoring request to alter found versions of bug #902941 to the same values 
previously set
Ignoring request to alter fixed versions of bug #902941 to the same values 
previously set
Bug #902941 [libuv1] libuv1 1.21 broke ABI without SONAME bump
Marked as found in versions libuv1/1.21.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: notfound 902962 in 2.08.3-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 902962 2.08.3-1
Bug #902962 [mandelbulber2] mandelbulber2: Missing Replaces: header
No longer marked as found in versions mandelbulber2/2.08.3-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug happens in stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 897523 - buster sid
Bug #897523 {Done: Christoph Berg } 
[src:check-postgres] check-postgres: FTBFS: tests failed
Removed tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 885961 dietlibc-dev
Bug #885961 [src:util-vserver] FTBFS: __kernel_rwf_t in 4.14 kernel headers
Bug reassigned from package 'src:util-vserver' to 'dietlibc-dev'.
No longer marked as found in versions util-vserver/0.30.216-pre3120-1.4.
Ignoring request to alter fixed versions of bug #885961 to the same values 
previously set
> forcemerge 883534 885961
Bug #883534 {Done: Thorsten Glaser } [dietlibc-dev] 
dietlibc-dev: linux-libc-dev 4.14.2-1 linux/fs.h does not compile with 
dietlibc-dev linux/types.h
Bug #883534 {Done: Thorsten Glaser } [dietlibc-dev] 
dietlibc-dev: linux-libc-dev 4.14.2-1 linux/fs.h does not compile with 
dietlibc-dev linux/types.h
885961 was blocked by: 883534
885961 was not blocking any bugs.
Removed blocking bug(s) of 885961: 883534
Added tag(s) ftbfs, buster, and sid.
Bug #885961 [dietlibc-dev] FTBFS: __kernel_rwf_t in 4.14 kernel headers
Marked Bug as done
Added indication that 885961 affects linux-libc-dev,src:util-vserver
Marked as fixed in versions dietlibc/0.34~cvs20160606-8.
Marked as found in versions dietlibc/0.34~cvs20160606-7.
Merged 883534 885961
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
883534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883534
885961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Fix the found version

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 902962 2.08.3-1+b1
Bug #902962 [mandelbulber2] mandelbulber2: Missing Replaces: header
Ignoring request to alter found versions of bug #902962 to the same values 
previously set
> found 902962 2.13.2-3
Bug #902962 [mandelbulber2] mandelbulber2: Missing Replaces: header
Marked as found in versions mandelbulber2/2.13.2-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902962
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#900533: The bug still exists in stable

[Michael Wyraz]

Hi,

I'm running chromium 67.0.3396.87-1~deb9u1 on stable - the bug still 
occurs here.


Example video: https://www.dailymotion.com/video/x6nlrix (just randomly 
picked from dailymotion)


Behaviour: nothing happens when pressing the play button

Console message: 
[289:318:0704/224715.089182:ERROR:render_media_log.cc(30)] MediaEvent: 
MEDIA_ERROR_LOG_ENTRY {"error":"FFmpegDemuxer: open context failed"}
[289:289:0704/224715.089572:ERROR:render_media_log.cc(30)] MediaEvent: 
PIPELINE_ERROR DEMUXER_ERROR_COULD_NOT_OPEN


Tested with a fresh clean chromium profile.

Processed: tagging 902945

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 902945 + buster sid
Bug #902945 [src:igraph] igraph: FTBFS with ARPACK 3.6
Added tag(s) buster and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902945: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902945
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902009: marked as done (cfitsio: FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 20:49:14 +
with message-id 
and subject line Bug#902009: fixed in cfitsio 3.430-3
has caused the Debian Bug report #902009,
regarding cfitsio: FTBFS
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.)


-- 
902009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfitsio
Version: 3.440-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

cfitsio/experimental recently started to FTBFS:

[...]
gcc -c -o ./f77_wrap1.o -g -O2 -fdebug-prefix-map=/build/cfitsio-3.440=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Dg77Fortran 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -DPACKAGE_NAME=\"\" -DPAC
KAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMOR
Y_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_LIBBZ2=1 -DHAVE_BZLIB_H=1 -DHAVE_BZIP2=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MATH_H=1 -DHAVE_LIMITS_H=1 
-D_LARGEFILE_S
OURCE=1 -D_FILE_OFFSET_BITS=64 -DCFITSIO_HAVE_CURL=1 -DHAVE_FTRUNCATE=1 
-DHAVE_LONGLONG=1 -DHAVE_SHMEM_SERVICES=1 -D_REENTRANT=1 -D_XOPEN_SOURCE=700 
-DHAVE_LIBPTHREAD=1 -DHAVE_NET_SERVICES=1 f77_wrap1.c
f77_wrap1.c:68:1: warning: parameter names (without types) in function 
declaration
 FCALLSCSUB2(Cffgiou,FTGIOU,ftgiou,PINT,PINT)
 ^~~
In file included from f77_wrap1.c:43:0:
f77_wrap.h:276:12: error: '_' declared as function returning a function
   CFextern _(T0,_cfF)(UN,LN)   
\
^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
f77_wrap.h:276:12: warning: return type defaults to 'int' [-Wimplicit-int]
   CFextern _(T0,_cfF)(UN,LN)   
\
^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
In file included from f77_wrap.h:3:0,
 from f77_wrap1.c:43:
f77_wrap1.c: In function '_':
f77_wrap1.c:68:40: error: expected identifier or '(' before 'int'
 FCALLSCSUB2(Cffgiou,FTGIOU,ftgiou,PINT,PINT)
^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
f77_wrap1.c:68:35: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before 'int'
 FCALLSCSUB2(Cffgiou,FTGIOU,ftgiou,PINT,PINT)
   ^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
f77_wrap1.c:72:1: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '{' token
 {
 ^
In file included from f77_wrap.h:3:0,
 from f77_wrap1.c:43:
f77_wrap1.c:81:35: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before 'int'
 FCALLSCSUB2(Cfffiou,FTFIOU,ftfiou,INT,PINT)
   ^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
[...]


Andreas


cfitsio_3.440-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cfitsio
Source-Version: 3.430-3

We believe that the bug you reported is fixed in the latest version of
cfitsio, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated cfitsio 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: Wed, 04 Jul 2018 

Processed: block 902788 with 902900

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 902788 with 902900
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902766 902989 902794 902715 902757 902646 902631 902761 
902650
902788 was blocking: 902582
Added blocking bug(s) of 902788: 902900
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#849240: marked as done (auto-complete-el: ac-menu-delete setq of 1 arg)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 20:47:09 +
with message-id 
and subject line Bug#849240: fixed in auto-complete-el 1.3.1-2+deb9u1
has caused the Debian Bug report #849240,
regarding auto-complete-el: ac-menu-delete setq of 1 arg
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.)


-- 
849240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: auto-complete-el
Version: 1.3.1-2
Severity: normal
File: /usr/share/emacs/site-lisp/auto-complete/auto-complete.el

Starting from "emacs25 -q" and in the *scratch* buffer,

(require 'auto-complete)
M-x auto-complete-mode
type: o r g

gives messages

Error running timer ‘ac-update-greedy’: (wrong-number-of-arguments setq 1)
Error running timer ‘ac-show-menu’: (wrong-number-of-arguments setq 1)
auto-complete error: (wrong-number-of-arguments setq 1)

and auto-complete mode turns itself off.

I think this is due to ac-menu-delete containing

(setq ac-menu)

An incompatible change in emacs25 has broken this.  I get some joy from

(setq ac-menu nil)


-- System Information:
Debian Release: stretch/sid
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages auto-complete-el depends on:
ii  emacs46.1
ii  emacs23-lucid [emacs23]  23.4+1-4.1+b1

auto-complete-el recommends no packages.

auto-complete-el suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: auto-complete-el
Source-Version: 1.3.1-2+deb9u1

We believe that the bug you reported is fixed in the latest version of
auto-complete-el, 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 849...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated auto-complete-el 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: Sun, 25 Feb 2018 22:08:51 +0200
Source: auto-complete-el
Binary: auto-complete-el
Architecture: source
Version: 1.3.1-2+deb9u1
Distribution: stretch
Urgency: medium
Maintainer: Takaya Yamashita 
Changed-By: Adrian Bunk 
Description:
 auto-complete-el - intelligent auto-completion extension for GNU Emacs
Closes: 746982 849240
Changes:
 auto-complete-el (1.3.1-2+deb9u1) stretch; urgency=medium
 .
   * Non-maintainer upload.
   * Add upstream fix for emacs25. (Closes: #849240)
   * Adjust the emacs dependencies to the emacs versions in stretch.
 (Closes: #746982)
   * Set auto-complete-el.emacsen-compat to silence installation warning.
Checksums-Sha1:
 f9f205f433f1445828ed58e3b302266943d22d55 1825 
auto-complete-el_1.3.1-2+deb9u1.dsc
 25f37a974cea6aa7252badc4279e4d499fd2 41752 
auto-complete-el_1.3.1-2+deb9u1.debian.tar.xz
Checksums-Sha256:
 be5703447b9c5204649b639e06cc6ef851279604c5a48ca4c67a4d786476d37f 1825 
auto-complete-el_1.3.1-2+deb9u1.dsc
 f47dfb2323db21bacfc3c44819376bbd12603f231de7eec37a07890c8ed1dce7 41752 
auto-complete-el_1.3.1-2+deb9u1.debian.tar.xz
Files:
 7199491b2aeb1e63bfe58fa1ce101e98 1825 lisp extra 
auto-complete-el_1.3.1-2+deb9u1.dsc
 c9c77404028773c369cff22a40ae0f48 41752 lisp extra 
auto-complete-el_1.3.1-2+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqTI80ACgkQiNJCh6LY
mLEsYA//cZqUWbEKVznaw9w6f7xtDvB6J4TQAoHBrnT2etIMfrRwja/7XS6pW4Nr
Rq+TBmY/zhpnQ2zWxPpdRSjtIq74vrQipVE7JbYYOTuCw18J/TBzNhug4UHmvCl9
aR5aYeFpXinYFwneBisEMOCOyfllHUUYaIQ2T4lMOzhyxHgm7+NcylGHsNWVxOcs
2+LJiE92wwfRflbzMTwE6M7WO+6WNeX5jJ+D0gueIEeNc3RJOx1/pwB/e52sCmDf
nmYktlZZ+Zpy71H/4AW3uje9Iw7WtYMCyAcpBpcvd74VUAe+l+bKbNjZ4I9rS14B
JuUb5TzOkfY3ze05fVWAfvuKy9O9L02k+4eJne0R9Vz/e9R+8FZPx2KA6JuLIBEg
pADsuP0/xhETUgnFHW7SRUan65n/iAgcpX1L/DGyjGog+e9u9RzFXe2RElamZ95Y
nX6o/oH2lPGh0HaswR3BdjR6bVPtufYi0NkoQklU9b+IiZj5l57fPzHJ1pxMnvPh
oBXQrhkOsVPUdDObkOGMDO8sqTew8vu7/y7iwmu4u9x7zeE7q9tETWsD9/jNhSO0
X1dNENhyFtGIDNpiQjSxaDy6agjmpz93LYr/CovwO78WK/lWnqAJTqgI/f57i+Tj
Ph7aifAFNw5ONjKGXrhMOUBK4kwFz3ak9jHbnFN3zZlrFR7BDQ8=
=r16L

Bug#868537: marked as done (File conflict between abiword-dbgsym and abiword-plugin-grammar-dbgsym)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 20:47:09 +
with message-id 
and subject line Bug#868537: fixed in abiword 3.0.2-2+deb9u2
has caused the Debian Bug report #868537,
regarding File conflict between abiword-dbgsym and abiword-plugin-grammar-dbgsym
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.)


-- 
868537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: abiword
Version: 3.0.2-2
Severity: serious
Control: affects -1 abiword-dbgsym abiword-plugin-grammar-dbgsym

# apt-get install abiword-dbgsym abiword-plugin-grammar-dbgsym
...
dpkg: error processing archive 
/var/cache/apt/archives/abiword-plugin-grammar-dbgsym_3.0.2-2_amd64.deb 
(--unpack):
 trying to overwrite 
'/usr/lib/debug/.build-id/30/e90eef3ab895a8c526b88940ee8d1f6ff47710.debug', 
which is also in package abiword-dbgsym 3.0.2-2


The problem is the following in debian/rules:

override_dh_makeshlibs:
$(RM) -v 
debian/abiword/usr/lib/$(DEB_HOST_MULTIARCH)/abiword-*/plugins/grammar.*
dh_makeshlibs -V


When grammar.so is removed from the abiword package,
dh_strip already ran and added its debug information
to abiword-dbgsym.
--- End Message ---
--- Begin Message ---
Source: abiword
Source-Version: 3.0.2-2+deb9u2

We believe that the bug you reported is fixed in the latest version of
abiword, 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 868...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated abiword 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: Wed, 28 Feb 2018 22:17:26 +0200
Source: abiword
Binary: abiword-common abiword abiword-plugin-grammar libabiword-3.0 
libabiword-3.0-dev gir1.2-abiword-3.0
Architecture: source
Version: 3.0.2-2+deb9u2
Distribution: stretch
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 abiword- efficient, featureful word processor with collaboration
 abiword-common - efficient, featureful word processor with collaboration -- 
common
 abiword-plugin-grammar - grammar checking plugin for AbiWord
 gir1.2-abiword-3.0 - GObject introspection data for libabiword
 libabiword-3.0 - efficient, featureful word processor with collaboration -- 
shared
 libabiword-3.0-dev - efficient, featureful word processor with collaboration 
-- develo
Closes: 868537
Changes:
 abiword (3.0.2-2+deb9u2) stretch; urgency=medium
 .
   * QA upload.
 .
   [ Simon Quigley ]
   * Solve binary file conflict between abiword-dbgsym
 and abiword-plugin-grammar-dbgsym (Closes: #868537).
Checksums-Sha1:
 b2ddfb571683de22da520903512a435865de8182 2952 abiword_3.0.2-2+deb9u2.dsc
 02e9ceba43f32feb6723d6728571eec54293b7ee 48400 
abiword_3.0.2-2+deb9u2.debian.tar.xz
Checksums-Sha256:
 73228de62ab1f7d385a6558e559e86e3d43b50d46770ce0b8073e6294137ef64 2952 
abiword_3.0.2-2+deb9u2.dsc
 60ce8be22ddbe0aba23b5565a72ba7f4cb0cc87066bcc9d831bbd516f6aff8be 48400 
abiword_3.0.2-2+deb9u2.debian.tar.xz
Files:
 e0d15ad0656bd6a36f287008a8f70371 2952 gnome optional abiword_3.0.2-2+deb9u2.dsc
 178b291312596496123dd89a28165e60 48400 gnome optional 
abiword_3.0.2-2+deb9u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlqXElgACgkQiNJCh6LY
mLHM+w//WL+oSq3Er0gQjeh+cMo08cgGzJEUgI26qHXRScgD5kOAvT0epNfgq78f
uU0JZKfndnmTQ1WL9sqlShuKrusEWvpEQzv56X8VmMJKYMDhhI3TyPn+D9Whs38R
7JYrFBBlra7NxOZ+ah/3282S7pOr7WZzfX+B17qdpIrd++q0Ox2ujBZaxzJKlRsE
fVNg/fRoe7WZgUMseA7BjwBWo6IYGdOvurkuEvok3OnpDKjefjFQ3Mnuj48edtb1
FNzTCLhBnC4favknTVgng+5DrmTOjAhIpoeWIM2XtdZtB7IedhPLZLNve/MvzAkh
hX7uNsotv6qrMECoXA2ElSte83dv2v2GPWggR4kWApk/fDvSUK0pFS+loRgBvut9
7JJSO/PKrj2eL/hpQGl+NDfaVTqXMWyOVO8OB4ljVEVkhpSs7413IPrxJiKcDiZM
fu8r4/0Ao2Fz6nS+VAK7vhX/QiTLqTvyA65U8Qajl1sPBrOXny2GZgppRlu32qhH
oClNxOXbZV7ha3vgOXRH73y0PV+XpJFoTq0SWG2iYP/nV7UoCHZ7ZRafL968gUKl
67lwhgh4O+R2+pyxRjAkqXBxyEnmccxHbltMjVF478AdNkI+slhjkw0ItSFpHZEE
AHFRsKC30FhKds/OVe2X2tQ5NY+kEaSU8fh8Ti5uG3W3WUp/Noc=
=AN8h
-END PGP SIGNATURE End Message ---

Processed: Coorect the direction of the block

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unblock 902989 by 902788
Bug #902989 [python3-pyatspi] python3-pyatspi: fresh installation breaks
902989 was blocked by: 902788
902989 was not blocking any bugs.
Removed blocking bug(s) of 902989: 902788
> block 902788 by 902989
Bug #902788 [python3.7] python3-minimal needs Breaks for software/modules 
broken by 3.7
902788 was blocked by: 902650 902766 902794 902631 902757 902715 902761 902646
902788 was blocking: 902582
Added blocking bug(s) of 902788: 902989
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902788: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902788
902989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

[Michael Biebl]

Am 04.07.2018 um 20:39 schrieb Helmut Grohne:
> Package: libpam-systemd
> Version: 239-4
> Severity: critical
> Justification: makes gnupg2 ftbfs
> User: helm...@debian.org
> Usertags: rebootstrap
> Control: affects -1 + src:gnupg2
> 
> A native(!) build of gnupg2 with sbuild and
> --bd-uninstallable-explainer=apt fails. dose3 finds an installation set,
> but it is too tricky to find for apt and it is caused by systemd, which
> simultaneously "Breaks: systemd-shim" and "Depends: systemd-shim |
> systemd-sysv".
> 
> See explainer output below:
> 
> | Reading package lists...
> | Building dependency tree...
> | Reading state information...
> |   MarkInstall sbuild-build-depends-gnupg2-dummy:amd64 < none -> 0.invalid.0 
> @un puN Ib > FU=1
> |   Installing automake as Depends of sbuild-build-depends-gnupg2-dummy
> | MarkInstall automake:amd64 < none -> 1:1.15.1-3.1 @un uN Ib > FU=0
> | Installing autoconf as Depends of automake
> |   MarkInstall autoconf:amd64 < none -> 2.69-11 @un uN Ib > FU=0
> |   Installing m4 as Depends of autoconf
> | MarkInstall m4:amd64 < none -> 1.4.18-1 @un uN Ib > FU=0
> | Installing libsigsegv2 as Depends of m4
> |   MarkInstall libsigsegv2:amd64 < none -> 2.12-2 @un uN > FU=0
> | Installing autotools-dev as Depends of automake
> |   MarkInstall autotools-dev:amd64 < none -> 20180224.1 @un uN > FU=0
> |   Installing autopoint as Depends of sbuild-build-depends-gnupg2-dummy
> | MarkInstall autopoint:amd64 < none -> 0.19.8.1-6 @un uN > FU=0
> |   Installing debhelper as Depends of sbuild-build-depends-gnupg2-dummy
> | MarkInstall debhelper:amd64 < none -> 11.3.5 @un uN Ib > FU=0
> | Installing dh-autoreconf as Depends of debhelper
> |   MarkInstall dh-autoreconf:amd64 < none -> 19 @un uN Ib > FU=0
> |   Installing libtool as Depends of dh-autoreconf
> | MarkInstall libtool:amd64 < none -> 2.4.6-2.1 @un uN Ib > FU=0
> | Installing file as Depends of libtool
> |   MarkInstall file:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
> |   Installing libmagic1 as Depends of file
> | MarkInstall libmagic1:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
> | Installing libmagic-mgc as Depends of libmagic1
> |   MarkInstall libmagic-mgc:amd64 < none -> 1:5.33-3 @un uN > 
> FU=0
> | Installing dh-strip-nondeterminism as Depends of debhelper
> |   MarkInstall dh-strip-nondeterminism:amd64 < none -> 0.042-1 @un uN Ib 
> > FU=0
> |   Installing libfile-stripnondeterminism-perl as Depends of 
> dh-strip-nondeterminism
> | MarkInstall libfile-stripnondeterminism-perl:amd64 < none -> 
> 0.042-1 @un uN Ib > FU=0
> | Installing libarchive-zip-perl as Depends of 
> libfile-stripnondeterminism-perl
> |   MarkInstall libarchive-zip-perl:amd64 < none -> 1.60-1 @un uN > 
> FU=0
> |   Installing libtimedate-perl as Depends of dh-strip-nondeterminism
> | MarkInstall libtimedate-perl:amd64 < none -> 2.3000-2 @un uN > FU=0
> | Installing dwz as Depends of debhelper
> |   MarkInstall dwz:amd64 < none -> 0.12-2 @un uN Ib > FU=0
> |   Installing libelf1 as Depends of dwz
> | MarkInstall libelf1:amd64 < none -> 0.170-0.5 @un uN > FU=0
> | Installing man-db as Depends of debhelper
> |   MarkInstall man-db:amd64 < none -> 2.8.3-2 @un uN Ib > FU=0
> |   Installing bsdmainutils as Depends of man-db
> | MarkInstall bsdmainutils:amd64 < none -> 11.1.2+b1 @un uN Ib > FU=0
> | Installing libbsd0 as Depends of bsdmainutils
> |   MarkInstall libbsd0:amd64 < none -> 0.9.1-1 @un uN > FU=0
> |   Installing groff-base as Depends of man-db
> | MarkInstall groff-base:amd64 < none -> 1.22.3-10 @un uN > FU=0
> |   Installing libpipeline1 as Depends of man-db
> | MarkInstall libpipeline1:amd64 < none -> 1.5.0-1 @un uN > FU=0
> | Installing po-debconf as Depends of debhelper
> |   MarkInstall po-debconf:amd64 < none -> 1.0.20 @un uN Ib > FU=0
> |   Installing gettext as Depends of po-debconf
> | MarkInstall gettext:amd64 < none -> 0.19.8.1-6+b1 @un uN Ib > FU=0
> | Installing libcroco3 as Depends of gettext
> |   MarkInstall libcroco3:amd64 < none -> 0.6.12-2 @un uN Ib > FU=0
> |   Installing libglib2.0-0 as Depends of libcroco3
> | MarkInstall libglib2.0-0:amd64 < none -> 2.56.1-2 @un uN > FU=0
> |   Installing libxml2 as Depends of libcroco3
> | MarkInstall libxml2:amd64 < none -> 2.9.4+dfsg1-7+b1 @un uN Ib 
> > FU=0
> | Installing libicu60 as Depends of libxml2
> |   MarkInstall libicu60:amd64 < none -> 60.2-6 @un uN Ib > FU=0
> |   Installing libicu-le-hb0 as Depends of libicu60
> | MarkInstall libicu-le-hb0:amd64 < none -> 1.0.3+git161113-5 
> @un uN Ib > FU=0
> | Installing libharfbuzz0b as Depends of libicu-le-hb0
> |   

Bug#902009: marked as done (cfitsio: FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 20:34:34 +
with message-id 
and subject line Bug#902009: fixed in cfitsio 3.440-3
has caused the Debian Bug report #902009,
regarding cfitsio: FTBFS
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.)


-- 
902009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfitsio
Version: 3.440-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

cfitsio/experimental recently started to FTBFS:

[...]
gcc -c -o ./f77_wrap1.o -g -O2 -fdebug-prefix-map=/build/cfitsio-3.440=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Dg77Fortran 
-fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -DPACKAGE_NAME=\"\" -DPAC
KAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMOR
Y_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_LIBBZ2=1 -DHAVE_BZLIB_H=1 -DHAVE_BZIP2=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MATH_H=1 -DHAVE_LIMITS_H=1 
-D_LARGEFILE_S
OURCE=1 -D_FILE_OFFSET_BITS=64 -DCFITSIO_HAVE_CURL=1 -DHAVE_FTRUNCATE=1 
-DHAVE_LONGLONG=1 -DHAVE_SHMEM_SERVICES=1 -D_REENTRANT=1 -D_XOPEN_SOURCE=700 
-DHAVE_LIBPTHREAD=1 -DHAVE_NET_SERVICES=1 f77_wrap1.c
f77_wrap1.c:68:1: warning: parameter names (without types) in function 
declaration
 FCALLSCSUB2(Cffgiou,FTGIOU,ftgiou,PINT,PINT)
 ^~~
In file included from f77_wrap1.c:43:0:
f77_wrap.h:276:12: error: '_' declared as function returning a function
   CFextern _(T0,_cfF)(UN,LN)   
\
^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
f77_wrap.h:276:12: warning: return type defaults to 'int' [-Wimplicit-int]
   CFextern _(T0,_cfF)(UN,LN)   
\
^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
In file included from f77_wrap.h:3:0,
 from f77_wrap1.c:43:
f77_wrap1.c: In function '_':
f77_wrap1.c:68:40: error: expected identifier or '(' before 'int'
 FCALLSCSUB2(Cffgiou,FTGIOU,ftgiou,PINT,PINT)
^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
f77_wrap1.c:68:35: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before 'int'
 FCALLSCSUB2(Cffgiou,FTGIOU,ftgiou,PINT,PINT)
   ^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
f77_wrap1.c:72:1: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before '{' token
 {
 ^
In file included from f77_wrap.h:3:0,
 from f77_wrap1.c:43:
f77_wrap1.c:81:35: error: expected '=', ',', ';', 'asm' or '__attribute__' 
before 'int'
 FCALLSCSUB2(Cfffiou,FTFIOU,ftfiou,INT,PINT)
   ^
/usr/include/cfortran.h:2295:9: note: in expansion of macro 'FCALLSCFUN14'
 
FCALLSCFUN14(T0,CN,UN,LN,T1,T2,T3,T4,T5,T6,T7,T8,T9,TA,CF_0,CF_0,CF_0,CF_0)
 ^~~~
[...]


Andreas


cfitsio_3.440-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: cfitsio
Source-Version: 3.440-3

We believe that the bug you reported is fixed in the latest version of
cfitsio, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated cfitsio 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: Wed, 04 Jul 2018 

Bug#898075: more info

[ant]

hello,

  just ran into this today when trying to get cd into
music collection.

  unfortunately i'm too new to python and multiarch to 
make sense of this but perhaps it will help someone else 
figure it out.


me@ant(33)~$ gdb python
GNU gdb (Debian 7.12-6+b2) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from python...Reading symbols from 
/usr/lib/debug/.build-id/ff/383265973a03ce803bda26de44d4a6c82f0db9.debug...done.
done.
(gdb) run /usr/bin/jack
Starting program: /usr/bin/python /usr/bin/jack
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
This is jack 3.1.1 (C)2004 Arne Zellentin 
 "Album - 01 - Tracktitle.[ext]"
 *info* matching dir found: /home/me/music/jack-a707b20c

Program received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at 
../sysdeps/x86_64/multiarch/strlen-avx2.S:62
62  ../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
(gdb) backtrace
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62
#1  0x72ecf6be in waddnstr ()
   from /lib/x86_64-linux-gnu/libncursesw.so.6
#2  0x73103585 in ?? ()
   from /usr/lib/python2.7/dist-packages/jack_curses.x86_64-linux-gnu.so
#3  0x5564969a in call_function (oparg=, 
pp_stack=0x7fffde30) at ../Python/ceval.c:4372
#4  PyEval_EvalFrameEx () at ../Python/ceval.c:3009
#5  0x5564e3e2 in fast_function (nk=, 
na=, n=2, pp_stack=0x7fffdf40, func=)
at ../Python/ceval.c:4457
#6  call_function (oparg=, pp_stack=0x7fffdf40)
at ../Python/ceval.c:4392
#7  PyEval_EvalFrameEx () at ../Python/ceval.c:3009
#8  0x5564e3e2 in fast_function (nk=, 
na=, n=0, pp_stack=0x7fffe050, func=)
at ../Python/ceval.c:4457
#9  call_function (oparg=, pp_stack=0x7fffe050)
at ../Python/ceval.c:4392
#10 PyEval_EvalFrameEx () at ../Python/ceval.c:3009
#11 0x55646c7a in PyEval_EvalCodeEx () at ../Python/ceval.c:3604
#12 0x5564e7ae in fast_function (nk=0, na=, 
n=, pp_stack=0x7fffe230, func=)
at ../Python/ceval.c:4467
---Type  to continue, or q  to quit---

ant

Bug#897523: fixed in check-postgres 2.24.0-1

[Santiago Vila]

found 897523 2.22.0-2
thanks

Dear maintainer: I tried to build this package in
stretch + security + stretch-proposed-updates and it failed with the
same error posted by Lucas Nussbaum.

Please consider an upload for stretch-proposed-updates, as packages in
stretch must be buildable in stretch.

Thanks.

Processed: Re: Bug#897523: fixed in check-postgres 2.24.0-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 897523 2.22.0-2
Bug #897523 {Done: Christoph Berg } 
[src:check-postgres] check-postgres: FTBFS: tests failed
Marked as found in versions check-postgres/2.22.0-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
897523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 902810

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 902810 + stretch
Bug #902810 [src:user-mode-linux] user-mode-linux: FTBFS in stretch (Hunk #1 
FAILED in 07-remove-rpath.patch)
Added tag(s) stretch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#902290: Too abrupt removal of configuration option in stable update

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #902290 [clamav-daemon] Too abrupt removal of configuration option in 
stable update
Added tag(s) patch.

-- 
902290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902290: Too abrupt removal of configuration option in stable update

[Sebastian Andrzej Siewior]

control: tags -1 patch

On 2018-07-04 14:06:54 [+0200], To Hans van Kranenburg wrote:
> On 2018-06-24 17:12:19 [+0200], Hans van Kranenburg wrote:
> > My mailserver logs now contain 'ERROR: Parse error at line 74: Unknown
> > option StatsHostID', and when that's removed, it reports the next option
> > that is removed, 'StatsPEDisabled', and so on.
> …
> > Or, alternatively when throwing newer versions in stable, they have to
> > be closely inspected to detect options that are removed and get patches
> > like you did for #826406.
> 
> I'm sorry. I've seen the removal of options and I didn't think about
> this. If handle the config file with debconf then the option should
> vanish automaticaly. However if you edit the file manually then user's
> input is required and if nothing happens then clamav will abort.
> 
> I intend to address this to for deb9 and document this behaviour so I
> will remember it next time. I have to figure out who is in charge of
> deb8 and I *think* it is LTS by now.

so I added a fix [0] to the Stretch branch for this. It would be nice if
you could have a look on the Stretch package in case something else is
missing :)

With this change you should see something like
| Jul 04 22:14:08 deb9amd64 clamd[8720]: WARNING: Ignoring deprecated option 
StatsTimeout at line 88
| Jul 04 22:14:08 deb9amd64 clamd[8720]: WARNING: Ignoring deprecated option 
StatsPEDisabled at line 89

and move on.
Now Jessie. It would be nice if the LTS team could pick it up. On the
other hand the point-release exposed the problem and everyone had to
deal with it…

[0] 
https://salsa.debian.org/clamav-team/clamav/blob/stretch/debian/patches/Deprecate-unused-options-instead-of-removing-it.patch

> > Thanks,

Sebastian

Processed: Bug present in stretch

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> unarchive 897523
Bug #897523 {Done: Christoph Berg } 
[src:check-postgres] check-postgres: FTBFS: tests failed
Unarchived Bug 897523
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
897523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897523
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 903003

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 903003 + ftbfs
Bug #903003 [src:soapaligner] soapaligner should be limited to any-amd64 x32
Warning: Unknown package 'src:soapaligner'
Added tag(s) ftbfs.
Warning: Unknown package 'src:soapaligner'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
903003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#903003: soapaligner should be limited to any-amd64 x32

[Adrian Bunk]

Source: soapaligner
Version: 2.20-2
Severity: serious

https://buildd.debian.org/status/package.php?p=soapaligner=sid

soapaligner uses SSE directly, so the architecture list should
be limited to any-amd64 x32 (and an RM bug filed for the SSE3-using
stale i386 package).

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 900110 fixed-upstream
Bug #900110 [src:xserver-xorg-video-r128] xserver-xorg-video-r128: FTBFS with 
xserver 1.20
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
900110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: virtualbox: fails to start vm (VERR_LDRELF_RELOCATION_NOT_SUPPORTED)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #902897 [virtualbox] virtualbox: fails to start vm 
(VERR_LDRELF_RELOCATION_NOT_SUPPORTED)
Severity set to 'serious' from 'important'

-- 
902897: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902990: FTBFS: bus error, alignment problems

[Aurelien Jarno]

control: forwarded -1 https://github.com/esheldon/fitsio/issues/86

On 2018-07-04 17:48, Steve McIntyre wrote:
> On Wed, Jul 04, 2018 at 04:56:30PM +0100, Steve McIntyre wrote:
> >Source: python-fitsio
> >Version: 0.9.11+dfsg-1
> >Severity: serious
> >Justification: fails to build from source (but built successfully in the 
> >past)
> >
> >Hi!
> >
> >First seen on the build arm-arm-01 which is an arm64 machine
> >configured to build for armhf, build log at
> >
> >https://buildd.debian.org/status/fetch.php?pkg=python-fitsio=armhf=0.9.11%2Bdfsg-1%2Bb2=1530604224=0
> 
> ...
> 
> >The ldrd instruction will be the read from input[ii]. That's clearly
> >unaligned, given the LONGLONG *input which starts at 0x16568df.
> >
> >This doesn't look like an issue with the compiler coalescing unrelated
> >values (which was an initial guess at the problem when discussing it
> >in #debian-buildd). It's simply reading an unaligned 64-bit value and
> >that's failing.
> 
> Just tested this on the 32-bit porter box abel. It builds fine there
> as we have (slow) alignment fixups enabled in the kernel. Disabling
> that briefly and rebuilding, I see exactly the same build failure:
> 
> ...
> I: pybuild base:217: cd 
> /home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
>  python2.7 -m unittest discover -v 
> testAsciiTableWriteRead (fitsio.test.TestReadWrite) ... ok
> testBz2Read (fitsio.test.TestReadWrite) ... skipped 'bzip2 is not supported 
> with debian cfitsio package'
> testChecksum (fitsio.test.TestReadWrite) ... Bus error
> E: pybuild pybuild:336: test: plugin distutils failed with: exit code=135: cd 
> /home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
>  python2.7 -m unittest discover -v 
> dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
> debian/rules:10: recipe for target 'build' failed
> make: *** [build] Error 25
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This is upstream issue #86. Marking the bug as forwarded.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Processed: Re: FTBFS: bus error, alignment problems

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/esheldon/fitsio/issues/86
Bug #902990 [src:python-fitsio] FTBFS: bus error, alignment problems
Set Bug forwarded-to-address to 'https://github.com/esheldon/fitsio/issues/86'.

-- 
902990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: l^e

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 902290 0.100.0+dfsg-0+deb9u1
Bug #902290 [clamav-daemon] Too abrupt removal of configuration option in 
stable update
Marked as found in versions clamav/0.100.0+dfsg-0+deb9u1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
902290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: limit source to cfitsio, tagging 902009

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source cfitsio
Limiting to bugs with field 'source' containing at least one of 'cfitsio'
Limit currently set to 'source':'cfitsio'

> tags 902009 + pending
Bug #902009 [src:cfitsio] cfitsio: FTBFS
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902009
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #897535 [src:openafs] openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 
returned exit code 2
Severity set to 'important' from 'serious'

-- 
897535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897535
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2

[Adrian Bunk]

Control: severity -1 important

On Wed, May 02, 2018 at 10:52:53PM +0200, Lucas Nussbaum wrote:
>...
> > volser/vos..FAILED 5
> > bucoord/backup-man..ok
> > kauth/kas-man...ok
> > 
> > Failed Set Fail/Total (%) Skip Stat  Failing Tests
> > -- --    
> > 
> > volser/vos1/6 17%00  5
> > 
> > Failed 1/710 tests, 99.86% okay.
> > Files=23,  Tests=710,  16.66 seconds (1.13 usr + 1.99 sys = 3.12 CPU)
> > make[2]: *** [Makefile:25: check] Error 1
> > make[2]: Leaving directory '/<>/tests'
> > make[1]: *** [Makefile:644: test] Error 2
> > make[1]: Leaving directory '/<>'
> > dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2
>  
> The full build log is available from:
>http://aws-logs.debian.net/2018/05/02/openafs_1.8.0-1_unstable.log
> 
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on EC2 VM instances from
> Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> failed build was retried once to eliminate random failures.

The same sources built on the autobuilder 3 days after this bug report
was submitted:
  https://buildd.debian.org/status/logs.php?pkg=openafs=amd64

There might be some problem somewhere, but when it builds on the 
autobuilders it is usually not considered RC.

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Processed: libpam-systemd: breaks installing build depends e.g. gnupg2

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:gnupg2
Bug #902998 [libpam-systemd] libpam-systemd: breaks installing build depends 
e.g. gnupg2
Added indication that 902998 affects src:gnupg2

-- 
902998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902998
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902998: libpam-systemd: breaks installing build depends e.g. gnupg2

[Helmut Grohne]

Package: libpam-systemd
Version: 239-4
Severity: critical
Justification: makes gnupg2 ftbfs
User: helm...@debian.org
Usertags: rebootstrap
Control: affects -1 + src:gnupg2

A native(!) build of gnupg2 with sbuild and
--bd-uninstallable-explainer=apt fails. dose3 finds an installation set,
but it is too tricky to find for apt and it is caused by systemd, which
simultaneously "Breaks: systemd-shim" and "Depends: systemd-shim |
systemd-sysv".

See explainer output below:

| Reading package lists...
| Building dependency tree...
| Reading state information...
|   MarkInstall sbuild-build-depends-gnupg2-dummy:amd64 < none -> 0.invalid.0 
@un puN Ib > FU=1
|   Installing automake as Depends of sbuild-build-depends-gnupg2-dummy
| MarkInstall automake:amd64 < none -> 1:1.15.1-3.1 @un uN Ib > FU=0
| Installing autoconf as Depends of automake
|   MarkInstall autoconf:amd64 < none -> 2.69-11 @un uN Ib > FU=0
|   Installing m4 as Depends of autoconf
| MarkInstall m4:amd64 < none -> 1.4.18-1 @un uN Ib > FU=0
| Installing libsigsegv2 as Depends of m4
|   MarkInstall libsigsegv2:amd64 < none -> 2.12-2 @un uN > FU=0
| Installing autotools-dev as Depends of automake
|   MarkInstall autotools-dev:amd64 < none -> 20180224.1 @un uN > FU=0
|   Installing autopoint as Depends of sbuild-build-depends-gnupg2-dummy
| MarkInstall autopoint:amd64 < none -> 0.19.8.1-6 @un uN > FU=0
|   Installing debhelper as Depends of sbuild-build-depends-gnupg2-dummy
| MarkInstall debhelper:amd64 < none -> 11.3.5 @un uN Ib > FU=0
| Installing dh-autoreconf as Depends of debhelper
|   MarkInstall dh-autoreconf:amd64 < none -> 19 @un uN Ib > FU=0
|   Installing libtool as Depends of dh-autoreconf
| MarkInstall libtool:amd64 < none -> 2.4.6-2.1 @un uN Ib > FU=0
| Installing file as Depends of libtool
|   MarkInstall file:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
|   Installing libmagic1 as Depends of file
| MarkInstall libmagic1:amd64 < none -> 1:5.33-3 @un uN Ib > FU=0
| Installing libmagic-mgc as Depends of libmagic1
|   MarkInstall libmagic-mgc:amd64 < none -> 1:5.33-3 @un uN > FU=0
| Installing dh-strip-nondeterminism as Depends of debhelper
|   MarkInstall dh-strip-nondeterminism:amd64 < none -> 0.042-1 @un uN Ib > 
FU=0
|   Installing libfile-stripnondeterminism-perl as Depends of 
dh-strip-nondeterminism
| MarkInstall libfile-stripnondeterminism-perl:amd64 < none -> 0.042-1 
@un uN Ib > FU=0
| Installing libarchive-zip-perl as Depends of 
libfile-stripnondeterminism-perl
|   MarkInstall libarchive-zip-perl:amd64 < none -> 1.60-1 @un uN > FU=0
|   Installing libtimedate-perl as Depends of dh-strip-nondeterminism
| MarkInstall libtimedate-perl:amd64 < none -> 2.3000-2 @un uN > FU=0
| Installing dwz as Depends of debhelper
|   MarkInstall dwz:amd64 < none -> 0.12-2 @un uN Ib > FU=0
|   Installing libelf1 as Depends of dwz
| MarkInstall libelf1:amd64 < none -> 0.170-0.5 @un uN > FU=0
| Installing man-db as Depends of debhelper
|   MarkInstall man-db:amd64 < none -> 2.8.3-2 @un uN Ib > FU=0
|   Installing bsdmainutils as Depends of man-db
| MarkInstall bsdmainutils:amd64 < none -> 11.1.2+b1 @un uN Ib > FU=0
| Installing libbsd0 as Depends of bsdmainutils
|   MarkInstall libbsd0:amd64 < none -> 0.9.1-1 @un uN > FU=0
|   Installing groff-base as Depends of man-db
| MarkInstall groff-base:amd64 < none -> 1.22.3-10 @un uN > FU=0
|   Installing libpipeline1 as Depends of man-db
| MarkInstall libpipeline1:amd64 < none -> 1.5.0-1 @un uN > FU=0
| Installing po-debconf as Depends of debhelper
|   MarkInstall po-debconf:amd64 < none -> 1.0.20 @un uN Ib > FU=0
|   Installing gettext as Depends of po-debconf
| MarkInstall gettext:amd64 < none -> 0.19.8.1-6+b1 @un uN Ib > FU=0
| Installing libcroco3 as Depends of gettext
|   MarkInstall libcroco3:amd64 < none -> 0.6.12-2 @un uN Ib > FU=0
|   Installing libglib2.0-0 as Depends of libcroco3
| MarkInstall libglib2.0-0:amd64 < none -> 2.56.1-2 @un uN > FU=0
|   Installing libxml2 as Depends of libcroco3
| MarkInstall libxml2:amd64 < none -> 2.9.4+dfsg1-7+b1 @un uN Ib > 
FU=0
| Installing libicu60 as Depends of libxml2
|   MarkInstall libicu60:amd64 < none -> 60.2-6 @un uN Ib > FU=0
|   Installing libicu-le-hb0 as Depends of libicu60
| MarkInstall libicu-le-hb0:amd64 < none -> 1.0.3+git161113-5 
@un uN Ib > FU=0
| Installing libharfbuzz0b as Depends of libicu-le-hb0
|   MarkInstall libharfbuzz0b:amd64 < none -> 1.8.1-1 @un uN Ib 
> FU=0
|   Installing libfreetype6 as Depends of libharfbuzz0b
| MarkInstall libfreetype6:amd64 < none -> 2.8.1-2 @un uN 
Ib > FU=0
|

Processed: Re: Bug#902989: python3-pyatspi: fresh installation breaks

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 902788
Bug #902989 [python3-pyatspi] python3-pyatspi: fresh installation breaks
902989 was not blocked by any bugs.
902989 was not blocking any bugs.
Added blocking bug(s) of 902989: 902788

-- 
902989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902989: python3-pyatspi: fresh installation breaks

[Paul Gevers]

Control: block -1 by 902788

Hi Wolfgang,

On 04-07-18 16:47, Wolfgang Schweer wrote:
> Setting up python3-pyatspi (2.26.0+dfsg-1) ...
>   File "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 114
> self.async = False# not fully supported yet
>  ^
> SyntaxError: invalid syntax

Thanks for reporting this. This is caused by the python3.7 transition.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#902989: python3-pyatspi: fresh installation breaks

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 902788
Bug #902989 [python3-pyatspi] python3-pyatspi: fresh installation breaks
902989 was blocked by: 902788
902989 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #902989 to the same blocks 
previously set

-- 
902989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902989
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 902941 is forwarded to https://github.com/libuv/libuv/issues/1908

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 902941 https://github.com/libuv/libuv/issues/1908
Bug #902941 [src:libuv1, src:lua-luv] libuv1 1.21 broke ABI without SONAME bump
Ignoring request to change the forwarded-to-address of bug#902941 to the same 
value
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902673: marked as done (please add support for python 3.7)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 17:05:45 +
with message-id 
and subject line Bug#902673: fixed in pycxx 7.0.3-2
has caused the Debian Bug report #902673,
regarding please add support for python 3.7
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.)


-- 
902673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: src:pycxx
Version: 7.0.3-1
Severity: important
Tags: sid buster

please add support for python 3.7. pycxx needs a sourceful upload. However there 
need some fixes too, seen when building pysvn:


Compile: /usr/share/python3.7/CXX/IndirectPythonInterface.cxx into 
IndirectPythonInterface.o
/usr/share/python3.7/CXX/IndirectPythonInterface.cxx: In function ‘char* 
Py::__Py_PackageContext()’:
/usr/share/python3.7/CXX/IndirectPythonInterface.cxx:471:50: error: invalid 
conversion from ‘const char*’ to ‘char*’ [-fpermissive]

 char *__Py_PackageContext() { return _Py_PackageContext; }
  ^~
Makefile:169: recipe for target 'IndirectPythonInterface.o' failed
make[2]: *** [IndirectPythonInterface.o] Error 1
--- End Message ---
--- Begin Message ---
Source: pycxx
Source-Version: 7.0.3-2

We believe that the bug you reported is fixed in the latest version of
pycxx, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julian Taylor  (supplier of updated pycxx 
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: Wed, 04 Jul 2018 18:41:18 +0200
Source: pycxx
Binary: python-cxx-dev python3-cxx-dev
Architecture: source
Version: 7.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Julian Taylor 
Description:
 python-cxx-dev - Set of facilities to extend Python with C++
 python3-cxx-dev - Set of facilities to extend Python3 with C++
Closes: 888414 902673
Changes:
 pycxx (7.0.3-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
 .
   [ Julian Taylor ]
   * fix compilation in test with python3.7 (Closes: #902673)
   * fix test failure on 32 bit, thanks to Graham Inggs for the patch
 Closes: #888414
   * update debian/compat to 9
   * update standards to 4.1.4
Checksums-Sha1:
 a232fea9dbf45cc46298b19d8a5a49b3d72314a3 2189 pycxx_7.0.3-2.dsc
 3758eebd5d61e8bfdcf17469853d356e6a7c895d 8312 pycxx_7.0.3-2.debian.tar.xz
 a9b2bc26abb25e7f86016b7a0927932dbd96cb04 7994 pycxx_7.0.3-2_source.buildinfo
Checksums-Sha256:
 aa6ad69b0fd92a2384ad1d0453a3310b9206464f502b1c2414ac7d00ee81bb09 2189 
pycxx_7.0.3-2.dsc
 ecc60fe0781fa80f06a4a7e94bb68dfcb51028f9c82c274d5c68469ddf96a005 8312 
pycxx_7.0.3-2.debian.tar.xz
 b5d0d3cbef028575165ae4cd3e02fab27511d83f850af712cffd14ceee21961f 7994 
pycxx_7.0.3-2_source.buildinfo
Files:
 fbfdf21c6e2f1a247a84066076c91e25 2189 python optional pycxx_7.0.3-2.dsc
 ed51f3150487911b138203090734736a 8312 python optional 
pycxx_7.0.3-2.debian.tar.xz
 decf2560eb71a4690db022743f1180a9 7994 python optional 
pycxx_7.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEi3e6SDkbPOUcIpUxMsxKrAKHVv8FAls8+3UACgkQMsxKrAKH
Vv9hAQ/+PdqzWNpxOyFPqlAfXZ6j6BoBLuLqjzgiONYRobiSwm4qWrKnVDSj3o8J
vVpSaaWLslGRz8QIubzy0fjrO2fSqTdcYvR05EX6C+uzOcHHndhK9CNRtm7VmfrF
ditw7YrxboMbytpPYCzsAGOjOhoZq1SQls9nFqWrEbxBnDujkUHHq1KZ8v9KjVLA
/pWggkSC86DXCUShNOv95oQsqgwANNQGbCXAqNIBp2hPMIKGrqah2Uw6fhvtxHbo
ZePbYHiW2VVafZoLbHhR2cUXruFxyV+ChnMJzjSVj18/9rSRQgol17JbZF3YNV9i
Coo0Al6WT7iarZ1gct9IIxuUV5feujxBBfrXzccVAPK8hMlkEs6FODcbKGcsek1+
pdHe0FOXuM/jSXJp/rNXqLnjhTEcNpDBl0YE/u/tgtfPJhS/3SnciNJXn2DAH18M
jyVog2wDapWRB+drX20XTk76+UuZUYjFjTcF5n+QFdVl1EoU+FSbvOo8WvSm83oh
gjigFTtNFy3zVXqKiDhpYMeLz2y1429XDjokegtwIZZtK2emTcUGaYKeWLru3Fn0
refHZKJdFuFtyOU3Ax9m9q3hEj9pRR+Lh9M36MktjoFpeFSN0yz7TbP1vAMPKSFA
QbQBFaHYPonwM52lGP833sJS7E/sADUEcJB28QnwCeRM7ar/tVc=
=zPs/
-END PGP SIGNATURE End Message ---

Bug#861027: gprolog bug still there despite easy fixes

[Cedric Ware]

Hello,

I don't think anything changed with this bug, which still prevents
gprolog's inclusion in any stable release, and affects Ubuntu as well.

I believe just pulling the latest upstream source would fix it.

Alternatively, if downgrading to the stable gprolog-1.4.4 is an option,
the attached patch lets it compile with gcc 6.  Tested on Debian 9.4.

Thanks in advance,
Cedric Ware.
diff -ru gprolog-1.4.4.orig/src/Ma2Asm/x86_64_any.c gprolog-1.4.4/src/Ma2Asm/x86_64_any.c
--- gprolog-1.4.4.orig/src/Ma2Asm/x86_64_any.c	2013-04-22 13:52:16.0 +0200
+++ gprolog-1.4.4/src/Ma2Asm/x86_64_any.c	2018-05-10 16:31:10.534235899 +0200
@@ -204,8 +204,8 @@
   strcpy(asm_reg_cp, Off_Reg_Bank(MAP_OFFSET_CP));
 #endif
 
-#ifdef M_x86_64_darwin
-  pic_code = 1;			/* NB: on darwin everything is PIC code */
+#if defined(M_x86_64_darwin) || defined(M_x86_64_bsd) || defined(M_x86_64_linux)
+  pic_code = 1;			/* NB: on darwin and BSD everything is PIC code, last gcc 6 needs this for linux */
 #elif defined(_WIN32)
   pic_code = 0;			/* NB: on MinGW nothing is needed for PIC code */
 #endif

Bug#902990: FTBFS: bus error, alignment problems

[Steve McIntyre]

On Wed, Jul 04, 2018 at 04:56:30PM +0100, Steve McIntyre wrote:
>Source: python-fitsio
>Version: 0.9.11+dfsg-1
>Severity: serious
>Justification: fails to build from source (but built successfully in the past)
>
>Hi!
>
>First seen on the build arm-arm-01 which is an arm64 machine
>configured to build for armhf, build log at
>
>https://buildd.debian.org/status/fetch.php?pkg=python-fitsio=armhf=0.9.11%2Bdfsg-1%2Bb2=1530604224=0

...

>The ldrd instruction will be the read from input[ii]. That's clearly
>unaligned, given the LONGLONG *input which starts at 0x16568df.
>
>This doesn't look like an issue with the compiler coalescing unrelated
>values (which was an initial guess at the problem when discussing it
>in #debian-buildd). It's simply reading an unaligned 64-bit value and
>that's failing.

Just tested this on the 32-bit porter box abel. It builds fine there
as we have (slow) alignment fixups enabled in the kernel. Disabling
that briefly and rebuilding, I see exactly the same build failure:

...
I: pybuild base:217: cd 
/home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
 python2.7 -m unittest discover -v 
testAsciiTableWriteRead (fitsio.test.TestReadWrite) ... ok
testBz2Read (fitsio.test.TestReadWrite) ... skipped 'bzip2 is not supported 
with debian cfitsio package'
testChecksum (fitsio.test.TestReadWrite) ... Bus error
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=135: cd 
/home/93sam/build/python-fitsio/python-fitsio-0.9.11+dfsg/.pybuild/cpython2_2.7_fitsio/build;
 python2.7 -m unittest discover -v 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Who needs computer imagery when you've got Brian Blessed?

Processed: bug 902941 is forwarded to https://github.com/libuv/libuv/issues/1908

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 902941 https://github.com/libuv/libuv/issues/1908
Bug #902941 [src:libuv1, src:lua-luv] libuv1 1.21 broke ABI without SONAME bump
Set Bug forwarded-to-address to 'https://github.com/libuv/libuv/issues/1908'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: libuv1/1.21.0-1 appears to break lua-luv/1.9.1-0-2 autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libuv1 1.21 broke ABI without SONAME bump
Bug #902941 [src:libuv1, src:lua-luv] libuv1/1.21.0-1 appears to break 
lua-luv/1.9.1-0-2 autopkgtest
Changed Bug title to 'libuv1 1.21 broke ABI without SONAME bump' from 
'libuv1/1.21.0-1 appears to break lua-luv/1.9.1-0-2 autopkgtest'.
> severity -1 serious
Bug #902941 [src:libuv1, src:lua-luv] libuv1 1.21 broke ABI without SONAME bump
Severity set to 'serious' from 'normal'
> affects -1 nodejs
Bug #902941 [src:libuv1, src:lua-luv] libuv1 1.21 broke ABI without SONAME bump
Added indication that 902941 affects nodejs

-- 
902941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#899324: ruby-font-awesome-rails: broken with fonts-font-awesome 5

[Pirate Praveen]

On Tue, 22 May 2018 16:49:12 -0300 Antonio Terceiro
 wrote:
> My suggestion would be to:
> 
> - base the CSS template on
>   /usr/share/fonts-font-awesome/css/font-awesome.css which is a modified
>   version of the FontAwesome v5 stylesheet adding backwards
>   compatibility for usage of FontAwesome v4.
> - symlink /usr/share/ruby-font-awesome-rails/app/assets/fonts/ directly
>   to /usr/share/fonts-font-awesome/webfonts instead of symlinking
>   individual files (and probably rename the link from fonts to webfonts)

The consensus on fonts-font-awesome bug seems to be a +really upload

There is already an open mr
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899124#164

So once that is uploaded, we can close this bug.



signature.asc
Description: OpenPGP digital signature

Processed: affects 899124

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 899124 ruby-font-awesome-rails
Bug #899124 [fonts-font-awesome] fonts-font-awesome: completely breaks web 
applications, with no notice
Added indication that 899124 affects ruby-font-awesome-rails
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
899124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: block 899324 with 899124

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 899324 with 899124
Bug #899324 [ruby-font-awesome-rails] ruby-font-awesome-rails: broken with 
fonts-font-awesome 5
899324 was not blocked by any bugs.
899324 was not blocking any bugs.
Added blocking bug(s) of 899324: 899124
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
899324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902992: live-build broken due subversion recommends

[PICCORO McKAY Lenz]

Package: live-build
Version: 1:20171207
Severity: grave

we need a mechanish to avoid bad or abuse of recommends in apt, this
problem avoit the automatization of the process

if we list the package subversion-tools, that recomends exim4 over any
other, take preference to a specific package

root@pc-desk-w32:/vnx/osposos/debianlive8# aptitude why exim4
i   subversion-tools Recomienda exim4 | mail-transport-agent

so then process end with this:

The following packages have unmet dependencies:
 courier-mta : Conflicts: mail-transport-agent
 exim4-config : Conflicts: courier-mta but 0.76.3-5 is to be installed
 exim4-daemon-light : Conflicts: mail-transport-agent

and lb build fails, with a only solution to make interactive shell and
avoiting automatization of the process

we need the mechanish due we cannot track all packages that abuse or
are bad mantained due policy violations!

Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#902990: FTBFS: bus error, alignment problems

[Steve McIntyre]

Source: python-fitsio
Version: 0.9.11+dfsg-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi!

First seen on the build arm-arm-01 which is an arm64 machine
configured to build for armhf, build log at

https://buildd.debian.org/status/fetch.php?pkg=python-fitsio=armhf=0.9.11%2Bdfsg-1%2Bb2=1530604224=0

I can similarly reproduce this on other arm64 hardware. Backtrace
shows:

(gdb) bt
#0  ffi8fi8 (input=input@entry=0x16568df, ntodo=ntodo@entry=1, scale=1, zero=0, 
output=output@entry=0xfff3d1a0, status=status@entry=0xfff44384) at 
putcolj.c:1871
#1  0xf6cc5a8a in ffpcljj (fptr=0x15d3660, colnum=8, firstrow=, 
firstelem=1, nelem=1, array=0x16568df, status=0xfff44384) at putcolj.c:1428
#2  0xf6cc5c3c in ffpcljj (fptr=, colnum=, 
firstrow=, firstelem=firstelem@entry=1, nelem=nelem@entry=1, 
array=array@entry=0x16568df, 
status=status@entry=0xfff44384) at putcolj.c:1538
#3  0xf6cbc2b4 in ffpcl (fptr=, datatype=, 
colnum=, firstrow=1, firstelem=1, nelem=1, array=0x16568df, 
status=0xfff44384) at putcol.c:701
#4  0xf6e02a26 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) p input
$2 = (LONGLONG *) 0x16568df

Disassembly of the problem area gives:

   0xf6cc54ce <+206>:   ldr.w   r0, [r10]
   0xf6cc54d2 <+210>:   ldmia.w sp!, {r4, r5, r6, r7, r8, r10, r11, pc}
   0xf6cc54d6 <+214>:   cmp r1, #0
   0xf6cc54d8 <+216>:   ble.n   0xf6cc54ca 
   0xf6cc54da <+218>:   subsr2, #8
   0xf6cc54dc <+220>:   add.w   r1, r0, r1, lsl #3
=> 0xf6cc54e0 <+224>:   ldrdr4, r5, [r0], #8
   0xf6cc54e4 <+228>:   cmp r1, r0
   0xf6cc54e6 <+230>:   strdr4, r5, [r2, #8]!
   0xf6cc54ea <+234>:   bne.n   0xf6cc54e0 
   0xf6cc54ec <+236>:   vpop{d8-d12}
   0xf6cc54f0 <+240>:   ldr.w   r0, [r10]

The offending ldrd instruction here clearly matches up with the
source, which is the simple-case loop in ffi8fi8():

if (scale == 1. && zero == 0.)
{   
for (ii = 0; ii < ntodo; ii++)
output[ii] = input[ii];
}

The ldrd instruction will be the read from input[ii]. That's clearly
unaligned, given the LONGLONG *input which starts at 0x16568df.

This doesn't look like an issue with the compiler coalescing unrelated
values (which was an initial guess at the problem when discussing it
in #debian-buildd). It's simply reading an unaligned 64-bit value and
that's failing.

-- System Information:
Debian Release: 9.4
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Processed: Re: Bug#902513: openturns: FTBFS in buster/sid (nlopt.hpp: No such file or directory)

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 902513 openturns/1.11-2
Bug #902513 [src:openturns] openturns: FTBFS in buster/sid (nlopt.hpp: No such 
file or directory)
Marked as fixed in versions openturns/1.11-2.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
902513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902513: openturns: FTBFS in buster/sid (nlopt.hpp: No such file or directory)

[D. Barbier]

fixed 902513 openturns/1.11-2
stop

On 2018-06-27 14:50 GMT+02:00 Santiago Vila wrote:
> Package: src:openturns
> Version: 1.10-5
> Severity: serious
> Tags: ftbfs
[...]
> /<>/lib/src/Base/Optim/NLopt.cxx:27:11: fatal error: nlopt.hpp: 
> No such file or directory
>  # include 
>^~~
> compilation terminated.
> lib/src/CMakeFiles/OT.dir/build.make:3302: recipe for target 
> 'lib/src/CMakeFiles/OT.dir/Base/Optim/NLopt.cxx.o' failed
> make[4]: *** [lib/src/CMakeFiles/OT.dir/Base/Optim/NLopt.cxx.o] Error 1

Hello,

This bug is already fixed in experimental, but I have to fix FTBFS on
several architectures before uploading to unstable.

Denis

Bug#874421: python3-cliapp: fails to upgrade from 'stretch' - trying to overwrite /usr/share/man/man5/cliapp.5.gz

[Lars Wirzenius]

On Wed, Sep 06, 2017 at 12:31:19AM +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.
> 
> See policy 7.6 at
> https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

While it's true there's a bug, and I will fix that, I do not
understand why piuparts is installing python3-cliapp. That doesn't
seem like an obvious thing to do. The python3 version of the package
did not exist in stretch, and upgrading the python2 version from
stretch to buster seems to work just fine: I just tested that manually
in a chroot.

From the piuparts log I see that it is explicitly installing the
python3 version after upgrading to buster.

(Also, the advice to use Replaces+Breaks is just wrong for this
package. The bug is that the same file is in both the python2 and
python3 versions of the package. The correct solution is to have it in
at most one package. I will be making that fix eventually.)

-- 
I want to build worthwhile things that might last. --joeyh


signature.asc
Description: PGP signature

Bug#902892: marked as done (plinth: Any change to user account will lock out user)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 15:23:30 +
with message-id 
and subject line Bug#902892: fixed in plinth 0.33.1
has caused the Debian Bug report #902892,
regarding plinth: Any change to user account will lock out user
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.)


-- 
902892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902892
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plinth
Version: 0.33.0
Severity: grave
Justification: renders package unusable

If plinth has a single admin user account, and any changes are made to
that user account, the user will be locked out of plinth.

More information and logs:
https://salsa.debian.org/freedombox-team/plinth/issues/1314
--- End Message ---
--- Begin Message ---
Source: plinth
Source-Version: 0.33.1

We believe that the bug you reported is fixed in the latest version of
plinth, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated plinth 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: Wed, 04 Jul 2018 10:32:23 -0400
Source: plinth
Binary: plinth
Architecture: source
Version: 0.33.1
Distribution: unstable
Urgency: medium
Maintainer: FreedomBox packaging team 

Changed-By: James Valleroy 
Description:
 plinth - web front end for administering every aspect of a FreedomBox
Closes: 902892
Changes:
 plinth (0.33.1) unstable; urgency=medium
 .
   [ Doma Gergő ]
   * Translated using Weblate (Hungarian)
 .
   [ Pavel Borecki ]
   * Translated using Weblate (Czech)
 .
   [ advocatux ]
   * Translated using Weblate (Spanish)
 .
   [ Igor ]
   * Translated using Weblate (Russian)
 .
   [ Joseph Nuthalapati ]
   * Change get-group-users to a simpler implementation
   * users: Replace disabled with readonly for admin group checkbox
 (Closes: #902892)
 .
   [ Gayathri Das ]
   * Translated using Weblate (Hindi)
Checksums-Sha1:
 f40912b72d56df6056f796d450e89b3b15dd408d 2423 plinth_0.33.1.dsc
 9670efd9e06c18865ea34d5c47f14ee8c81a55f8 10782168 plinth_0.33.1.tar.xz
 6872f6d4055aab045984ce865e6b09cf2c927dd3 12394 plinth_0.33.1_amd64.buildinfo
Checksums-Sha256:
 8213a95766350ad483893433d4ad8b4e9cc5847390a6cc34c372d00c3d16e775 2423 
plinth_0.33.1.dsc
 7efc7fdbe2dcca238ad16c740e81dee41212037de5d2183655c0e195b5b95f0a 10782168 
plinth_0.33.1.tar.xz
 195517ed8ef60ecfb1cd9ea83e11e09b192d2236eb01fb9ec7ffb351221d95dd 12394 
plinth_0.33.1_amd64.buildinfo
Files:
 b5a36289105528fb69a8900e80de9e69 2423 web optional plinth_0.33.1.dsc
 cfc727e322683bc3008b483303b14f6d 10782168 web optional plinth_0.33.1.tar.xz
 317eb93bb7969e8b9bf1e42314f1e6fa 12394 web optional 
plinth_0.33.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAls83+0WHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICISYD/97THRrLRB8MqBOi/wnDeaX6p63
fTJjGGMM/CjyNs/gKqkkXyDYVEuONYSowLmLxadsA6iFkzX15yjY8dEW3cCRS+PW
wgwp827bQqZfUVBfxpxUaVdj1N3C/DuFNPTXFu0Rz3cn8dumKOhazs0vf8BzGBlO
nzdm79VtWx5TXMpzPmNJVm1EHz1bTpICbfl9gKh36NQNXaDTAKDa34IpnzgifbJB
dviR3d3oANVPOD2IrQi6nlmawgkJRc09VJ2EB6HjESdJF8ny07c+MkiRaN0k/v2U
R4WJrmWMHKubYxY950sC5G/2+yBp65Jm3LH2ttxMHAFwTMy6aXuSXrGu3qtlEFSO
+mJkE6Qzu5L1ISGLMkxhM7kt64LWInPnpe80Ruso6/MkZRC95C1leuaQSgoDX5Ld
RiWSs0yEa99XIdqDp1CbEBYpQz19N+897RQp9Fxkl858AgygBPlwe67/xOmqJcNS
42R3erIZJ0GgH1UmVMjeyZ1JaBHgJj/MnTKu9u2S22z5kw8CdPBxhgQuJVkmzsDm
iLEpxZaJmIIRxIrwVLC4KJtiXpNl3vKTrCVmXyJLBAHAkOVSkNdl86zu5WbOlAo8
UZx0wXp34r4hUUu/fCCq26PJoVOfaexnv02jiiWJtzWBjnHfPMBKfeVzRsoJNQ57
ykC/yOvrux2NhlQSlQ==
=1FUO
-END PGP SIGNATURE End Message ---

Bug#902989: python3-pyatspi: fresh installation breaks

[Wolfgang Schweer]

Package:  python3-pyatspi
Version:  2.26.0+dfsg-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: debian-edu


Dear Maintainer,

when running 'apt --reinstall install python3-pyatspi' on a system 
running buster/sid the installation breaks. 
This is the error output when running 'LC_ALL=C apt -f install':

Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up python3-pyatspi (2.26.0+dfsg-1) ...
  File "/usr/lib/python3/dist-packages/pyatspi/registry.py", line 114
self.async = False  # not fully supported yet
 ^
SyntaxError: invalid syntax

dpkg: error processing package python3-pyatspi (--configure):
 installed python3-pyatspi package post-installation script subprocess 
returned error exit status 1
Errors were encountered while processing:
 python3-pyatspi
E: Sub-process /usr/bin/dpkg returned an error code (1)

I noticed this problem in the first place when searching for reasons why
the src:debian-edu autopkgtest is failing; see:
https://ci.debian.net/data/autopkgtest/unstable/amd64/d/debian-edu/556605/log.gz

Due to this bug, both GNOME and MATE desktop installations seem to be 
broken.

Wolfgang


signature.asc
Description: PGP signature

Processed: reassign 902981 to fonts-font-awesome, notfixed 792205 in 1:2.3.16-1 ..., fixed 901001 in 3.6.6-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 902981 fonts-font-awesome
Bug #902981 [font-font-awesome] new upstream (5.1.0)
Warning: Unknown package 'font-font-awesome'
Bug reassigned from package 'font-font-awesome' to 'fonts-font-awesome'.
Ignoring request to alter found versions of bug #902981 to the same values 
previously set
Ignoring request to alter fixed versions of bug #902981 to the same values 
previously set
> notfixed 792205 1:2.3.16-1
Bug #792205 {Done: Guillaume Bougard } 
[fusioninventory-agent] fusioninventory-agent: modifies conffiles (policy 
10.7.3): /etc/fusioninventory/agent.cfg
No longer marked as fixed in versions 1:2.3.16-1.
> reassign 901001 python3-minimal
Bug #901001 {Done: Matthias Klose } 
[src:python3-defaults,src:dh-python] python3-minimal should Pre-Depend on 
python3.N-minimal
Bug reassigned from package 'src:python3-defaults,src:dh-python' to 
'python3-minimal'.
Ignoring request to alter found versions of bug #901001 to the same values 
previously set
No longer marked as fixed in versions python3-defaults/3.6.6-1.
> fixed 901001 3.6.6-1
Bug #901001 {Done: Matthias Klose } [python3-minimal] 
python3-minimal should Pre-Depend on python3.N-minimal
Marked as fixed in versions python3-defaults/3.6.6-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
792205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792205
901001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901001
902981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#902972: libargon2-0 install a symlink pointin to libargon2.so.1

[Laurent Bigonville]

Le 04/07/18 à 10:02, Luca BRUNO a écrit :

On Wednesday, 4 July 2018 07:31:30 UTC you wrote:
  

The libargon2-0 package is pulling the libargon2-1 package and contains
a symlink pointing to libargon2.so.1.

This is not a good idea and a proper transition should be done.

Is there a specific issue this is causing?

While odd, the rationale for such setup is described here:
https://salsa.debian.org/debian/argon2/merge_requests/3#note_28753
If a library changes its soname all the reverse dependencies needs to be 
rebuild, this is happening 10 times a month in the debian archive (and 
there far bigger transition happening in the archive that this one)


Adding the "compatibility" package here is completely useless and is 
IMHO against best practices.

Bug#902290: [Pkg-clamav-devel] Bug#902290: Too abrupt removal of configuration option in stable update

[Sebastian Andrzej Siewior]

On 2018-06-24 17:12:19 [+0200], Hans van Kranenburg wrote:
> My mailserver logs now contain 'ERROR: Parse error at line 74: Unknown
> option StatsHostID', and when that's removed, it reports the next option
> that is removed, 'StatsPEDisabled', and so on.
…
> Or, alternatively when throwing newer versions in stable, they have to
> be closely inspected to detect options that are removed and get patches
> like you did for #826406.

I'm sorry. I've seen the removal of options and I didn't think about
this. If handle the config file with debconf then the option should
vanish automaticaly. However if you edit the file manually then user's
input is required and if nothing happens then clamav will abort.

I intend to address this to for deb9 and document this behaviour so I
will remember it next time. I have to figure out who is in charge of
deb8 and I *think* it is LTS by now.

> Thanks,

Sebastian

Bug#902977: libctl-dev: guile 2.0/2.2 mixture

[Andreas Beckmann]

Package: libctl-dev
Version: 4.1.0-1
Severity: serious

Hi,

I wanted to request a binNMU of mpb/experimental against libctl7, but
could not even build this locally due to unsatisfiable transitive B-D
on both guile-2.0-dev and guile-2.2-dev.

* libctl/experimental has B-D: guile-2.0-dev
* libctl7/experimental has D: guile-2.0-libs
* libctl-dev/experimental has D: guile-2.2-dev

That looks inconsistent ...


Andreas

Bug#902921: boost1.63: FTBFS with python3.7 supported: libs/python/src/converter/builtin_converters.cpp:51:35: error: invalid conversion from 'const void*' to 'void*' [-fpermissive]

[Anton Gladky]

I think, there is no need to keep the deprecated
code in the archive. Especially if all our forces
are directed to 1.67.

Regards

Anton


2018-07-03 18:45 GMT+02:00 Giovanni Mascellani :
> Hi,
>
> Il 03/07/2018 17:01, Simon McVittie ha scritto:> Similar to #902702,
> boost1.63 fails to build when binNMU'd against
>> python3.7. This example build log is from amd64:
> Thanks for reporting. My feeling here is that it would be advisable to
> just remove boost1.63 from unstable. No package depends on it (as it was
> never promoted to the default boost version) and hopefully both 1.62 and
> 1.63 will be soon replaced by 1.67, which is close to being ready now.
>
> What do other boost maintainers propose?
>
> Giovanni.
> --
> Giovanni Mascellani 
> Postdoc researcher - Université Libre de Bruxelles
>

Bug#888931: marked as done (forge FTBFS with libglm-dev 0.9.9~a2-1)

[Debian Bug Tracking System]

Your message dated Wed, 04 Jul 2018 10:22:56 +
with message-id 
and subject line Bug#888931: fixed in forge 1.0.1-2
has caused the Debian Bug report #888931,
regarding forge FTBFS with libglm-dev 0.9.9~a2-1
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.)


-- 
888931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: forge
Version: 0.9.2-2
Severity: serious
Tags: buster sid experimental

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/forge.html

...
In file included from /usr/include/glm/gtx/string_cast.hpp:23:0,
 from /build/1st/forge-0.9.2/src/backend/opengl/common.hpp:21,
 from /build/1st/forge-0.9.2/src/backend/opengl/backend.hpp:12,
 from /build/1st/forge-0.9.2/src/backend/window.hpp:12,
 from /build/1st/forge-0.9.2/src/backend/handle.hpp:14,
 from /build/1st/forge-0.9.2/src/api/c/font.cpp:12:
/usr/include/glm/gtx/dual_quaternion.hpp:24:3: error: #error "GLM: 
GLM_GTX_dual_quaternion is an experimental extension and may change in the 
future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, if you really 
want to use it."
 # error "GLM: GLM_GTX_dual_quaternion is an experimental extension and may 
change in the future. Use #define GLM_ENABLE_EXPERIMENTAL before including it, 
if you really want to use it."
   ^
--- End Message ---
--- Begin Message ---
Source: forge
Source-Version: 1.0.1-2

We believe that the bug you reported is fixed in the latest version of
forge, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated forge 
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: Wed, 04 Jul 2018 11:58:54 +0200
Source: forge
Binary: libforge1 libforge-dev forge-doc
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Gianfranco Costamagna 
Description:
 forge-doc  - documentation for forge
 libforge-dev - development files for forge
 libforge1  - high-performance OpenGL visualization
Closes: 888931
Changes:
 forge (1.0.1-2) unstable; urgency=medium
 .
   * Upload to unstable
   * Team upload
   * Add -Wno-dev to tests, to avoid cmake warnings being sent to stderr
   * cherry-pick two upstream fixes for build failures (Closes: #888931):
 - debian/patches/63e4a2037e42c00554a26de2355d962f91a9ab20.patch:
 - debian/patches/befa265294fd9ff679dece7874c1de50fea97b25.patch:
Checksums-Sha1:
 d2d1a06dcf59d8a476a6621bccf67a481a4f0d43 2458 forge_1.0.1-2.dsc
 270156b23058e443a0943e4f98555ead50bfa8ca 5696 forge_1.0.1-2.debian.tar.xz
 96bd1eabb29f597c26675eb0b39c9712b241c768 10524 forge_1.0.1-2_source.buildinfo
Checksums-Sha256:
 512f5e5585a6e5e0d71a4e1b46f2d5cde8ee1e37c5a8281f91aff64e673f6e08 2458 
forge_1.0.1-2.dsc
 664c30f6ddc6d7cd7eb14232f3baac9f9768a9767e90ac26e80635bbafa5ecfc 5696 
forge_1.0.1-2.debian.tar.xz
 20f0ec95789e8c42d9ce0f676aec4745514f413926854942be5442c402dfc91d 10524 
forge_1.0.1-2_source.buildinfo
Files:
 94bd7984d71db9dce8d7f5b2d5d7927e 2458 libs optional forge_1.0.1-2.dsc
 3acd826b046f6e9f7031323b5f467353 5696 libs optional forge_1.0.1-2.debian.tar.xz
 c27bb1c6bd0b73bb9d31f53723e0936d 10524 libs optional 
forge_1.0.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAls8nJcACgkQ808JdE6f
XdnoMg/+KK0LCF3yUE4QesNfaMLr7KYH+u/ggiI/NNLgFq26Hga8HMsT+QPpiVTk
IqKq6RKERxZmgiVr0aHYT8oCFkl4Zdghnhguk0xTv5+VfLBkWLKTP5eRx1bvk1RK
K9S/HYW95oHv8nEV0yu6nhoSll3T48F0HiwXPlybum7O04F5lzR7UTNFOPlJ/Rvq
GLu0bEPE+SEutSZvcJseY3KcOG7Svy3nQQpbSYmGAgIElQS3nqK3sYVGiJn9g+PG
v6wfbMSmiP2IYaZRpXsiDyE1ZBeD2d7M0vgjqBrYQS3TcPF1Ru0eYNfqxqDyOOHt
+miqXXQR7uqGLiKhuMR91KU0Q+iiVo1oETsSJRiDBCExOhCt2kD2t5GQflii4WkJ
k4lFwML6ny/9ks/DUCCQPFhMGpycn9blztxiSqlKo2Ro2HnYRKKWMHdAkrVQTeq9
IHE1XgikE7GnEwLv8+UWJO6LUD17z7vEanqg/qHLaKiRVNu8WknKgX8eGxHp4A4C
gr02959EpGpdgpYohdybajtsPaNE5x3/T4RUTmutAOAz7YZG2ed+cb1ra/f90vgf

Bug#902972: libargon2-0 install a symlink pointin to libargon2.so.1

[Luca BRUNO]

On Wednesday, 4 July 2018 07:31:30 UTC you wrote:
 
> The libargon2-0 package is pulling the libargon2-1 package and contains
> a symlink pointing to libargon2.so.1.
> 
> This is not a good idea and a proper transition should be done.

Is there a specific issue this is causing?

While odd, the rationale for such setup is described here:
https://salsa.debian.org/debian/argon2/merge_requests/3#note_28753

Ciao, Luca

-- 
"If you build a wall, think of what you leave outside it" - Italo Calvino


signature.asc
Description: This is a digitally signed message part.

Bug#902972: libargon2-0 install a symlink pointin to libargon2.so.1

[Laurent Bigonville]

Source: argon2
Version: 0~20171227-0.1
Severity: serious

Hi,

The libargon2-0 package is pulling the libargon2-1 package and contains
a symlink pointing to libargon2.so.1.

This is not a good idea and a proper transition should be done.

The package shouldn't enter testing until this is fixed.

Regards,

Laurent Bigonville

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

Kernel: Linux 4.17.0-rc5+ (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Processed: block 902526 with 902970

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 902526 with 902970
Bug #902526 [src:zsh-syntax-highlighting] zsh-syntax-highlighting: FTBFS in 
buster/sid (does not work with recent debhelper)
902526 was not blocked by any bugs.
902526 was not blocking any bugs.
Added blocking bug(s) of 902526: 902970
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
902526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems