Bug#935086: insighttoolkit4 REMOVED from testing

[Andreas Tille]

Hi Steve and Gert,

since I have no idea about itk I have ignored this issue.  Is there
any chance to get this fixed soon to make sure this package and its
rdepends will migrate back to testing soon?

Kind regards

  Andreas.

On Fri, Oct 04, 2019 at 04:39:19AM +, Debian testing watch wrote:
> FYI: The status of the insighttoolkit4 source package
> in Debian's testing distribution has changed.
> 
>   Previous version: 4.12.2-dfsg1-4
>   Current version:  (not in testing)
>   Hint: 
> Bug #935086: insighttoolkit4: FTBFS with GCC-9: use of undeclared 
> identifier '__builtin_is_constant_evaluated'
> 
> The script that generates this mail tries to extract removal
> reasons from comments in the britney hint files. Those comments
> were not originally meant to be machine readable, so if the
> reason for removing your package seems to be nonsense, it is
> probably the reporting script that got confused. Please check the
> actual hints file before you complain about meaningless removals.
> 
> -- 
> This email is automatically generated once a day.  As the installation of
> new packages into testing happens multiple times a day you will receive
> later changes on the next day.
> See https://release.debian.org/testing-watch/ for more information.
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de

Bug#849308: wireguard: Wireguard should not transition to stable yet

[Willem van den Akker]

Hi DKG,


> Please make sure you can build the package from the debian/master branch
> at 
https://salsa.debian.org/debian/wireguard> .
> 
> If you can do that successfully (it shouldn't be too hard), feel free to
> take a look at the debian/TODO file, which contains a handful of
> suggestions, mostly about setting up more detailed autopkgtest testing.

Building is no problem. I will dig into the autopkgtest testing. It is
rather new to me.

> 
> Another thing that might be handy is to read through the discussion
> starting here:
> 
> 
> https://lists.debian.org/deity/2019/09/msg00017.html
> 
> 
> The idea is to propose a debian package for binary wireguard kernel
> modules that matches the current kernel package, so that users
> wouldn't
> need to use dkms.  getting the dependency details right there is
> tricky,
> as is keeping it up to date, but it might be worth trying.

Interesting, needs more digging from my side.

> 
> I've pushed a very ungainly initial attempt at this binary module
> packaging to 
> https://salsa.debian.org/debian/wireguard-modules
>  -- you
> might want to take a look at that and consider fixing one of the
> things
> in debian/TODO there, and proposing a fix.  


> Alternately, testing its
> build and seeing whether the resultant binary works or not on systems
> without dkms would also be interesting.

That shouldn't be a problem.


First I will take the autopkgtest.

Greetings,
Willem

Bug#941712: hfs partitions corrupted when removing lots of files over network

[Graham Coster]

Package: hfsutils
Version: 3.2.6-14
Severity: grave
 Output from uname -a
Linux raspberrypi 4.19.66-v7l+ #1253 SMP Thu Aug 15 12:02:08 BST 2019 armv7l 
GNU/Linux


 Output from apt show libc6 2>&1 | grep ^Version
Version: 2.28-10+rpi1

 Hardware;
RaspberryPi model 2b and RaspberryPi model 4b


 What led up to the situation?
I set up a new RaspberryPi to be a Samba network file server for an HFS 
partition  (see setup section at end of this email for details). I then deleted 
about 300 files from the HFS partition from a client machine.  This caused an 
"Internal error: Oops: 206 [#1] SMP ARM".  See kern.log below for Oops details.

After the error, the filesytem was corrputed and could not be repaired using 
fsck.  See fsck output below.

To reproduce the problem, I run the following from a client machine;
for i in {1..300}; do touch /Volumes/TimeMachineBackup/$i; done ; rm 
/Volumes/TimeMachineBackup/*

Every time I re-run this test on a freshly formatted drive, the same error 
occurs and the filesystem is always corrupted and cannot be repaired (i.e. 
total data loss).


 What exactly did you do (or not do) that was effective (or ineffective)?
I tried all of the following;
- Replaced Samba network sharing with Netatalk
- Re-installed Raspbian from scratch
- Different mkfs.hfs formatting options to add journal files and alter the 
b-node sizes
- Various samba configurations to change sync / async options, threading 
options, permissions, etc
- 3 different disk drives (USB flash drive, USB powered HDD, Separately powered 
HDD)
- 2 different RaspberryPi models (2b and 4b)
- Different network connections speeds (WiFi at 200Mbs, Ethernet at 100Mbs, 
Ethernet at 1000Mbs)
- Deleted 300 files locally on the RaspberryPi file server (i.e. not over 
network)
- Replaced HFS+ format with EXT4


 What was the outcome of this action?
None the the things I tried above had any impact on the problem except;
- The problem did not occur at all when deleting locally on the RaspberryPi 
file server.
- The problem did not occur at all when HFS+ was replaced with EXT4

 What outcome did you expect instead?
Given the problem did not occur locally on the file server, but did over 
Sambaa, I expected the problem to go away when I replaced Samba with Netatalk.  
It did not.

I wonder if the problem relates to how all file-networking protocols interact 
with local filesystems?


#
# LOGS AND OUTPUT   #
#
   
# kern.log;

Sep 26 16:09:25 raspberrypi kernel: [  222.906719] hfsplus: trying to free free 
bnode 0(1)
Sep 26 16:09:25 raspberrypi kernel: [  222.906844] hfsplus: trying to free free 
bnode 0(1)
Sep 26 16:09:25 raspberrypi kernel: [  222.906893] Unable to handle kernel NULL 
pointer dereference at virtual address 
Sep 26 16:09:25 raspberrypi kernel: [  222.906906] pgd = bc442823
Sep 26 16:09:25 raspberrypi kernel: [  222.906914] [] *pgd=11d05003, 
*pmd=
Sep 26 16:09:25 raspberrypi kernel: [  222.906933] Internal error: Oops: 206 
[#1] SMP ARM
Sep 26 16:09:25 raspberrypi kernel: [  222.906942] Modules linked in: nls_utf8 
hfsplus bnep hci_uart btbcm serdev bluetooth ecdh_generic 8021q garp stp llc 
vc4 v3d drm_kms_helper brcmfmac gpu_sched brcmutil drm 
drm_panel_orientation_quirks snd_bcm2835(C) snd_soc_core sha256_generic 
snd_compress snd_pcm_dmaengine snd_pcm sg snd_timer syscopyarea sysfillrect 
sysimgblt fb_sys_fops cfg80211 rfkill snd raspberrypi_hwmon hwmon 
bcm2835_codec(C) bcm2835_v4l2(C) v4l2_mem2mem v4l2_common videobuf2_vmalloc 
bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 
videobuf2_common videodev media vc_sm_cma(C) rpivid_mem uio_pdrv_genirq uio 
fixed ip_tables x_tables ipv6
Sep 26 16:09:25 raspberrypi kernel: [  222.907150] CPU: 3 PID: 634 Comm: smbd 
Tainted: G C4.19.66-v7l+ #1253
Sep 26 16:09:25 raspberrypi kernel: [  222.907160] Hardware name: BCM2835
Sep 26 16:09:25 raspberrypi kernel: [  222.907177] PC is at kmap+0x1c/0x44
Sep 26 16:09:25 raspberrypi kernel: [  222.907188] LR is at 
_cond_resched+0x30/0x50
Sep 26 16:09:25 raspberrypi kernel: [  222.907196] pc : []lr : 
[]psr: 6013
Sep 26 16:09:25 raspberrypi kernel: [  222.907205] sp : dc0e3cc0  ip : dc0e3cb0 
 fp : dc0e3cd4
Sep 26 16:09:25 raspberrypi kernel: [  222.907214] r10: 002e  r9 : dcdf9c48 
 r8 : 
Sep 26 16:09:25 raspberrypi kernel: [  222.907222] r7 : dc0e3d02  r6 : dcdf9c7c 
 r5 : 0002  r4 : 
Sep 26 16:09:25 raspberrypi kernel: [  222.907231] r3 :   r2 : c0e953fc 
 r1 :   r0 : 
Sep 26 16:09:25 raspberrypi kernel: [  222.907241] Flags: nZCv  IRQs on  FIQs 
on  Mode SVC_32  ISA ARM  Segment user
Sep 26 16:09:25 raspberrypi kernel: [  222.907250] Control: 30c5383d  Table: 
1e71cfc0  DAC: 
Sep 26 16:09:25 raspberrypi 

Bug#935669: assaultcube-data: Outdated version makes assaultcube uninstallable

[Jeremy Bicha]

To fix this bug, a Debian Developer will need to do a binary upload of
this package. Once the package makes it through the NEW queue, then
you can follow the final step in the final link of
https://lintian.debian.org/tags/source-only-upload-to-non-free-without-autobuild.html

After all that has been done, you can do a source-only upload off
assaultcube-data.

Thanks,
Jeremy

Bug#941619: ruby-odbc: ODBC dlopen regression in Debian 10

[Martin Dorey]

I've raised this bug again, in a hopefully more coherent way, as:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941707
ruby-odbc: [RubyODBC]Cannot allocate SQLHENV (ODBC::Error)

Sorry for the noise.

Processed: Re: ruby-odbc: ODBC dlopen regression in Debian 10

[Debian Bug Tracking System]

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

> close 941619
Bug #941619 [ruby-odbc] ruby-odbc: ODBC dlopen regression in Debian 10
Marked Bug as done
> tags 941619 - ftbfs upstream
Bug #941619 {Done: Martin Dorey } [ruby-odbc] 
ruby-odbc: ODBC dlopen regression in Debian 10
Removed tag(s) ftbfs and upstream.
>
End of message, stopping processing here.

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

Processed: Raising severity of wxwidgets3.0-gtk transition blockers

[Debian Bug Tracking System]

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

> severity 933407 serious
Bug #933407 [codeblocks] codeblocks: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933408 serious
Bug #933408 [usbprog] usbprog: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933411 serious
Bug #933411 [fwknop-gui] fwknop-gui: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933412 serious
Bug #933412 {Done: Christoph Berg } [limesuite] limesuite: 
Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933415 serious
Bug #933415 [openbabel] openbabel: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933416 serious
Bug #933416 [filezilla] filezilla: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933419 serious
Bug #933419 [darkradiant] darkradiant: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933424 serious
Bug #933424 [sitplus] sitplus: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933425 serious
Bug #933425 [sooperlooper] sooperlooper: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933426 serious
Bug #933426 [mediainfo] mediainfo: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933427 serious
Bug #933427 [delaboratory] delaboratory: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933431 serious
Bug #933431 [gnuplot] gnuplot: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933433 serious
Bug #933433 [chipw] chipw: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933434 serious
Bug #933434 [cba] cba: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933435 serious
Bug #933435 {Done: Olly Betts } [freedink-dfarc] 
freedink-dfarc: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933438 serious
Bug #933438 [spek] spek: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933440 serious
Bug #933440 [munipack] munipack: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933441 serious
Bug #933441 [pcsx2] pcsx2: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933442 serious
Bug #933442 [ebook2cwgui] ebook2cwgui: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933445 serious
Bug #933445 [sandboxgamemaker] sandboxgamemaker: Please rebuild against 
wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933451 serious
Bug #933451 [pgn2web] pgn2web: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933457 serious
Bug #933457 [gspiceui] gspiceui: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933459 serious
Bug #933459 [pgadmin3] pgadmin3: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933462 serious
Bug #933462 [wxsvg] wxsvg: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933463 serious
Bug #933463 [treesheets] treesheets: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933465 serious
Bug #933465 [freespace2-launcher-wxlauncher] freespace2-launcher-wxlauncher: 
Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933466 serious
Bug #933466 [rapidsvn] rapidsvn: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933469 serious
Bug #933469 [mrpt] mrpt: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933473 serious
Bug #933473 [bossa] bossa: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933474 serious
Bug #933474 [cubicsdr] cubicsdr: Please rebuild against wxWidgets GTK 3 package
Severity set to 'serious' from 'important'
> severity 933475 serious
Bug #933475 [wxastrocapture] wxastrocapture: Please rebuild against wxWidgets 
GTK 3 package
Severity set to 'serious' from 'important'
> severity 933476 serious
Bug #933476 [stx-btree] stx-btree: Please rebuild against wxWidgets GTK 3 
package
Severity set to 'serious' from 'important'
> severity 933478 serious
Bug #933478 

Processed: reassign 941242 to ftp.debian.org ...

[Debian Bug Tracking System]

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

> reassign 941242 ftp.debian.org
Bug #941242 [src:pymc] pymc: intention to remove this package from Debian
Bug reassigned from package 'src:pymc' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #941242 to the same values 
previously set
Ignoring request to alter fixed versions of bug #941242 to the same values 
previously set
> retitle 941242 RM: pymc -- RoM; RC buggy; abandoned upstream, replaced by 
> pymc3, python2-only
Bug #941242 [ftp.debian.org] pymc: intention to remove this package from Debian
Changed Bug title to 'RM: pymc -- RoM; RC buggy; abandoned upstream, replaced 
by pymc3, python2-only' from 'pymc: intention to remove this package from 
Debian'.
> thanks
Stopping processing here.

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

Bug#941242: pymc: intention to remove this package from Debian

[Sandro Tosi]

thanks! retitle+reassing'ing now

On Thu, Sep 26, 2019 at 7:46 PM Yaroslav Halchenko  wrote:
>
> I guess it could indeed be removed, even if only to raise later from ashes as 
> pymc3
>
> Cheers
>
> On September 26, 2019 7:18:08 PM EDT, Sandro Tosi  wrote:
> >Source: pymc
> >Severity: serious
> >
> >Hello,
> >pymc is abandoned upstream and replaced by pymc3 (python3 only module),
> >https://github.com/pymc-devs/pymc3 .
> >
> >Currently pymc has a single (initial) maintainer upload, the only other
> >one
> >being a NMU, it's not in the last 2 stable releases, have 2 RCs bugs
> >unaddressed, so it's my belief we should remove this package.
> >
> >if I dont get back a good reason to keep this package in Debian withing
> >a week,
> >i will file for its removal (it has no reverse dependencies).
> >
> >Regards,
> >Sandro
> >
> >-- System Information:
> >Debian Release: 10.0
> >  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.19.0-5-amd64 (SMP w/8 CPU cores)
> >Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> >TAINT_UNSIGNED_MODULE
> >Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> >LANGUAGE= (charmap=UTF-8)
> >Shell: /bin/sh linked to /bin/dash
> >Init: systemd (via /run/systemd/system)
> >LSM: AppArmor: enabled
>
> --
> Yaroslav O. Halchenko (mobile version)
> Center for Open Neuroscience   http://centerforopenneuroscience.org
> Dartmouth College, NH, USA



-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Bug#941661: marked as done (daemon fails to start)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 21:34:14 +
with message-id 
and subject line Bug#941661: fixed in fwupd 1.3.2-2
has caused the Debian Bug report #941661,
regarding daemon fails to start
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.)


-- 
941661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd
Version: 1.3.2-1
Severity: serious

Hi,

It seems that the fwupd daemon fails to start:

oct 03 15:23:38 edoras systemd[1]: Starting Firmware update daemon...
oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed to set up special 
execution directory in /var/cache: Not a directory
oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed at step 
CACHE_DIRECTORY spawning /usr/lib/fwupd/fwupd: Not a directory
oct 03 15:23:38 edoras systemd[1]: fwupd.service: Main process exited, 
code=exited, status=239/CACHE_DIRECTORY
oct 03 15:23:38 edoras systemd[1]: fwupd.service: Failed with result 
'exit-code'.
oct 03 15:23:38 edoras systemd[1]: Failed to start Firmware update daemon.


Looking at /var/cache, I see:

ls -la /var/cache/fwupd/ 
[...]
lrwxr-xr-x.  1 root  root13 sep 28 22:49 fwupd -> 
private/fwupd
[...]

/var/cache/private/fwupd also exists

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (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

Versions of packages fwupd depends on:
ii  libarchive13   3.4.0-1
ii  libc6  2.29-2
ii  libefiboot137-2
ii  libefivar1 37-2
ii  libelf10.176-1.1
ii  libfwupd2  1.3.2-1
ii  libgcab-1.0-0  1.2-5
ii  libglib2.0-0   2.62.0-3
ii  libgnutls303.6.9-5
ii  libgpg-error0  1.36-7
ii  libgpgme11 1.13.1-1
ii  libgudev-1.0-0 233-1
ii  libgusb2   0.3.0-1
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpolkit-gobject-1-0  0.105-26
ii  libsmbios-c2   2.4.1-1
ii  libsoup2.4-1   2.68.1-2
ii  libsqlite3-0   3.29.0-2
ii  libtss2-esys0  2.1.0-4+b1
ii  libxmlb1   0.1.8-1+b1
ii  shared-mime-info   1.10-1

Versions of packages fwupd recommends:
ii  bolt   0.8-4
ii  fwupd-amd64-signed [fwupd-signed]  1.3.2+1
ii  python33.7.5-1

fwupd suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.3.2-2

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
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: Thu, 03 Oct 2019 15:52:23 -0500
Source: fwupd
Binary: libfwupd2 fwupd fwupd-tests fwupd-doc libfwupd-dev gir1.2-fwupd-2.0 
fwupd-amd64-signed-template fwupd-i386-signed-template 
fwupd-armhf-signed-template fwupd-arm64-signed-template
Architecture: source
Version: 1.3.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Description:
 fwupd  - Firmware update daemon
 fwupd-amd64-signed-template - Template for signed fwupd package
 fwupd-arm64-signed-template - Template for signed fwupd package
 fwupd-armhf-signed-template - Template for signed fwupd package
 fwupd-doc  - Firmware update daemon documentation (HTML format)
 fwupd-i386-signed-template - Template for signed fwupd package
 fwupd-tests - Test suite for firmware update daemon
 gir1.2-fwupd-2.0 - GObject introspection data for libfwupd
 libfwupd-dev - development files for 

Bug#941559: marked as done (libxvidcore4: immediately crashes on amd64 since binNMU)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 20:38:41 +
with message-id 
and subject line Bug#941559: fixed in xvidcore 2:1.3.5-2
has caused the Debian Bug report #941559,
regarding libxvidcore4: immediately crashes on amd64 since binNMU
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.)


-- 
941559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxvidcore4
Version: 2:1.3.5-1
Severity: grave
Tags: sid bullseye

Hi,

Just over a month ago xvidcore was binNMUed and this seems to have
triggered a bug somewhere and now any application which tries to
initialize libxvidcore will segfault.

Test app:
#include 
#include 

int main(void)
{
xvid_gbl_init_t init = {
.version = XVID_VERSION,
.cpu_flags = 0,
.debug = 0,
};
xvid_global(NULL, XVID_GBL_INIT, , NULL);
return 0;
}

$ gcc -o xvid-test xvid-test.c -lxvidcore
$ ./xvid-test 
Segmentation fault (core dumped)

The crash happens here:
Program received signal SIGSEGV, Segmentation fault.
0x77f22940 in check_cpu_features () from 
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4
(gdb) bt
#0  0x77f22940 in check_cpu_features () from 
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4
#1  0x77e9c15b in detect_cpu_flags () at ../../src/xvid.c:156
#2  0x77e9d265 in xvid_gbl_init (init=0x7fffdee4, 
init=0x7fffdee4) at ../../src/xvid.c:793
#3  xvid_global (handle=, opt=, 
param1=0x7fffdee4, param2=) at ../../src/xvid.c:816
#4  0x516d in main ()

Which in turn seems to happen because the check_cpu_features function is
in a non-executable read only memory region.

$ /proc/4658/maps
[...]
77e87000-77e8b000 rw-p  00:00 0 
77e8b000-77e8d000 r--p  fd:00 954232 
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
77e8d000-77ef5000 r-xp 2000 fd:00 954232 
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
[vvv]
77ef5000-77f2b000 r--p 0006a000 fd:00 954232 
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
[^^^]
77f2b000-77f2c000 r--p 0009f000 fd:00 954232 
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
77f2c000-77f36000 rw-p 000a fd:00 954232 
/usr/lib/x86_64-linux-gnu/libxvidcore.so.4.3
77f36000-77fa1000 rw-p  00:00 0 
[...]

Indeed readelf contains some non-executable program headers in
2:1.3.5-1+b1 which do not appear in 2:1.3.5-1 in buster. The
".rotext" section sounds suspicious.

2:1.3.5-1+b1:
$ readelf -l /usr/lib/x86_64-linux-gnu/libxvidcore.so.4
[...]
Program Headers:
  Type   Offset VirtAddr   PhysAddr
 FileSizMemSiz  Flags  Align
  LOAD   0x 0x 0x
 0x18a8 0x18a8  R  0x1000
  LOAD   0x2000 0x2000 0x2000
 0x000673c9 0x000673c9  R E0x1000
  LOAD   0x0006a000 0x0006a000 0x0006a000
 0x00035088 0x00035088  R  0x1000
  LOAD   0x0009fb90 0x000a0b90 0x000a0b90
 0x98d0 0x00073138  RW 0x1000
[...]
   00 .note.gnu.build-id .gnu.hash .dynsym .dynstr .gnu.version 
.gnu.version_r .rela.dyn .rela.plt 
   01 .init .plt .plt.got .text .fini 
   02 .rodata .rotext .eh_frame_hdr .eh_frame 
   03 .init_array .fini_array .data.rel.ro .dynamic .got .data .bss 

2:1.3.5-1:
$ readelf -l /usr/lib/x86_64-linux-gnu/libxvidcore.so.4
[...]
Program Headers:
  Type   Offset VirtAddr   PhysAddr
 FileSizMemSiz  Flags  Align
  LOAD   0x 0x 0x
 0x0009da50 0x0009da50  R E0x20
  LOAD   0x0009db90 0x0029db90 0x0029db90
 0x98d0 0x00073138  RW 0x20
[...]
   00 .note.gnu.build-id .gnu.hash .dynsym .dynstr .gnu.version 
.gnu.version_r .rela.dyn .rela.plt .init .plt .plt.got .text .fini .rodata 
.rotext .eh_frame_hdr .eh_frame 
   01 .init_array .fini_array .data.rel.ro .dynamic .got .data .bss 

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: xvidcore
Source-Version: 2:1.3.5-2

We believe 

Bug#939792: marked as done (hovercraft: autopkgtest needs update for new version of lxml)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 20:34:40 +
with message-id 
and subject line Bug#939792: fixed in hovercraft 2.6-5
has caused the Debian Bug report #939792,
regarding hovercraft: autopkgtest needs update for new version of lxml
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.)


-- 
939792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939792
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hovercraft
Version: 2.6-4
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, l...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:lxml

Dear maintainers,

With a recent upload of lxml the autopkgtest of hovercraft fails in
testing when that autopkgtest is run with the binary packages of lxml
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
lxml   from testing4.4.1-1
hovercraft from testing2.6-4
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of lxml to testing
[1]. Of course, lxml shouldn't just break your autopkgtest (or even
worse, your package), but it seems to me that the change in lxml was
intended and your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from lxml should really add a
versioned Breaks on the unfixed version of (one of your) package(s).

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=lxml

https://ci.debian.net/data/autopkgtest/testing/amd64/h/hovercraft/2909341/log.gz

=== FAILURES
===
 SlideMakerTests.test_advanced
_

self = 

def test_advanced(self):
tree = SlideMaker(make_tree('test_data/advanced.rst')).walk()
xml = etree.tostring(tree)
target = (
b'This
is an advanced '
b'presentation. It doesn\'t have a section in the first\nstep, '
b'meaning the first step will not be a step at all, but a
sort of\n'
b'introductory comment about the presentation, that will not
show up '
b'in the\npresentation at all.It also
sets a '
b'title and a transition-duration.'
b'Advanced PresentationHere we '
b'show the positioning feature, where we can explicitly set a '
b'position\non one of the
steps.'
b'FormattingLet us also try some basic '
b'formatting, like italic, and
bold'
b'.'
b'We can also'
b'have a list'
b'of things.'
b''
b'There should also be possible to have\n'
b'preformatted text for code.'
b'def foo(bar):\n# Comment'
b'\na = 1
+ "hubbub"'
b'\nreturn '
b'NoneAn image, with
attributes:'
b'Character
sets'
b'The character set is UTF-8 as of now. Like this: '
b'.')
>   self.assertEqual(xml, target)
E   AssertionError: b'' != b''

tests/test_parse.py:73: AssertionError



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: hovercraft
Source-Version: 2.6-5

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated hovercraft 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: Thu, 03 Oct 2019 15:52:29 -0400
Source: hovercraft
Architecture: source
Version: 2.6-5
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Boyuan 

Bug#939807: sbcl build-depends on package that is cruft in unstable and gone in testing.

[Sébastien Villemot]

Hi Steve,

Le mardi 01 octobre 2019 à 14:58 -0700, Steve Langasek a écrit :
> Package: sbcl
> Followup-For: Bug #939807
> User: ubuntu-de...@lists.ubuntu.com
> 
> Usertags: origin-ubuntu eoan ubuntu-patch
> 
> Dear maintainers,
> 
> Attached is a straightforward patch for this issue.

Note that this issue had already been fixed in Debian. It looks like
sbcl in Ubuntu is out-of-sync.

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org



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

Processed: [bts-link] source package src:python-persistent

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:python-persistent
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #935619 (http://bugs.debian.org/935619)
> # Bug title: python-persistent: FTBFS on amd64
> #  * https://github.com/zopefoundation/persistent/issues/86
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 935619 + fixed-upstream
Bug #935619 [src:python-persistent] python-persistent: FTBFS on amd64
Added tag(s) fixed-upstream.
> usertags 935619 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#941559: marked as pending in xvidcore

[Fabian Greffrath]

Control: tag -1 pending

Hello,

Bug #941559 in xvidcore reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/xvidcore/commit/57faa77ceeae42d6da6f87f654e18ae134d6b0e6


Define a standard ELF .text section in ASM code, instead of .rotext (Closes: 
#941559).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941559

Processed: Bug#941559 marked as pending in xvidcore

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941559 [libxvidcore4] libxvidcore4: immediately crashes on amd64 since 
binNMU
Added tag(s) pending.

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

Bug#941533: marked as done (jags: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 18:34:40 +
with message-id 
and subject line Bug#941533: fixed in jags 4.3.0-3
has caused the Debian Bug report #941533,
regarding jags: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
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.)


-- 
941533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jags
Version: 4.3.0-2
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Dirk,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru jags-4.3.0/debian/control jags-4.3.0/debian/control
--- jags-4.3.0/debian/control   2018-07-08 19:28:15.0 -0700
+++ jags-4.3.0/debian/control   2019-10-01 14:04:20.0 -0700
@@ -2,7 +2,7 @@
 Section: math
 Priority: optional
 Maintainer: Dirk Eddelbuettel 
-Build-Depends: debhelper (>= 7.0.50~), gfortran (>= 4:5.2), liblapack-dev, 
libltdl-dev (>= 2.2.6b), texlive-base, texlive-latex-base, 
texlive-generic-recommended, texlive-fonts-recommended, texlive-extra-utils, 
texlive-latex-recommended, texlive-latex-extra, texinfo, autotools-dev, 
faketime, g++ (>= 4:5.2), libcppunit-dev, dh-autoreconf, pkg-config, mercurial
+Build-Depends: debhelper (>= 7.0.50~), gfortran (>= 4:5.2), liblapack-dev, 
libltdl-dev (>= 2.2.6b), texlive-base, texlive-latex-base, 
texlive-plain-generic, texlive-fonts-recommended, texlive-extra-utils, 
texlive-latex-recommended, texlive-latex-extra, texinfo, autotools-dev, 
faketime, g++ (>= 4:5.2), libcppunit-dev, dh-autoreconf, pkg-config, mercurial
 Standards-Version: 3.9.8
 Homepage: http://www-fis.iarc.fr/~martyn/software/jags/
 
--- End Message ---
--- Begin Message ---
Source: jags
Source-Version: 4.3.0-3

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated jags 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, 03 Oct 2019 13:11:00 -0500
Source: jags
Architecture: source
Version: 4.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Closes: 941533
Changes:
 jags (4.3.0-3) unstable; urgency=medium
 .
   * debian/control: Change Build-Depends: from texlive-generic-recommended
 to texlive-plain-generic   (Closes: #941533)
 .
   * debian/control: Set Standards-Version: to current version
Checksums-Sha1:
 f40b3ff65185eb0adfc45ad6b2d4317a12811a9b 1969 jags_4.3.0-3.dsc
 bdd7295e87185331a983cf700f92e863bbefd68e 5936 jags_4.3.0-3.debian.tar.xz
 ce0c69f934f43c92bf85bdd37ded9790635901b7 8596 jags_4.3.0-3_amd64.buildinfo
Checksums-Sha256:
 180189afb953c7ae85b9adbfcd054623fcf5841a5baa33837190bdaf212dffec 1969 
jags_4.3.0-3.dsc
 81e928c78ec7a9bc58fe4f0d257075f1ba0d44172846dde5812d16a0ea45608c 5936 
jags_4.3.0-3.debian.tar.xz
 0e2e390d86cb29a7c2c41e93fcd6edc8483a6d513b9e4572c9490980950f4d64 8596 
jags_4.3.0-3_amd64.buildinfo
Files:
 700d4dcea71f7cff5eae78474d43735e 1969 math optional jags_4.3.0-3.dsc
 eb067fec6a43fff872e8d750d034ef61 5936 math optional jags_4.3.0-3.debian.tar.xz
 b687ba2737098ccfef26dd0d19c826a7 8596 math optional 
jags_4.3.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBXZY7K6FIn+KrmaIaAQjolw/+J11ilugzlbYOehRY7GanxBmqrlRbmbZX
AezsgtOuvWJlmn/UrzaMs9Ajh48iIZYomXXOpNjAaQ4em26fIplEUhfhV34KVYVH
5XG6b1SAYW4BYpqJN7Wpuxmyb4dmW62oUyAmnBSWsNaOE1nU+bSRHBlTuqdi9FTm
EXLp27qQ2HWNBgi1qdMBS6494kzQxQejarSTS37uT4ye8sRt15CM2Bb/+5QotVIZ

Bug#941517: marked as done (ess: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 18:04:02 +
with message-id 
and subject line Bug#941517: fixed in ess 18.10.2-2
has caused the Debian Bug report #941517,
regarding ess: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
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.)


-- 
941517: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ess
Version: 18.10.2-1
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Dirk,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ess-18.10.2/debian/control ess-18.10.2/debian/control
--- ess-18.10.2/debian/control  2018-08-18 14:39:10.0 -0700
+++ ess-18.10.2/debian/control  2019-10-01 12:46:03.0 -0700
@@ -4,7 +4,7 @@
 Maintainer: Dirk Eddelbuettel 
 Standards-Version: 4.1.1
 Build-Depends: debhelper (>= 10)
-Build-Depends-Indep: dh-elpa, texlive-base, texlive-latex-base, 
texlive-latex-recommended, texlive-latex-extra, texlive-generic-recommended, 
texlive-extra-utils, texlive-fonts-recommended, texinfo
+Build-Depends-Indep: dh-elpa, texlive-base, texlive-latex-base, 
texlive-latex-recommended, texlive-latex-extra, texlive-plain-generic, 
texlive-extra-utils, texlive-fonts-recommended, texinfo
 Vcs-Browser: https://salsa.debian.org/edd/ess
 Vcs-Git: https://salsa.debian.org/edd/ess.git
 Homepage: http://ess.r-project.org
--- End Message ---
--- Begin Message ---
Source: ess
Source-Version: 18.10.2-2

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated ess 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, 03 Oct 2019 12:38:13 -0500
Source: ess
Architecture: source
Version: 18.10.2-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Closes: 941517
Changes:
 ess (18.10.2-2) unstable; urgency=medium
 .
   * debian/control: Change Build-Depends: from texlive-generic-recommended
 to texlive-plain-generic   (Closes: #941517)
Checksums-Sha1:
 420cca221b50b96b6eb4c908d953b01741fd3bed 1965 ess_18.10.2-2.dsc
 662efc0d64feb009ce66a73eaf8aa6c177891699 11968 ess_18.10.2-2.debian.tar.xz
 cd2c960fdb51394721b84263870b5b95510f0bc7 10210 ess_18.10.2-2_amd64.buildinfo
Checksums-Sha256:
 e0a6fc9bf910379b83846e05718ba55dd3f59e74fb90363cb96765ab7680ffc5 1965 
ess_18.10.2-2.dsc
 d448e89508d957e021542a9c63949d1edd8474c9a7d57c5db01302186e7792d4 11968 
ess_18.10.2-2.debian.tar.xz
 51e10673571342f2f6f8eb85b588bd91a25118d8b34a6847995aa9b2818773e4 10210 
ess_18.10.2-2_amd64.buildinfo
Files:
 53940e8b799c7f08a5120a3a69f5edbb 1965 gnu-r optional ess_18.10.2-2.dsc
 8997c05d7c429908723e8a29f629ed84 11968 gnu-r optional 
ess_18.10.2-2.debian.tar.xz
 8808201055f69376c97607fed6bf5c7e 10210 gnu-r optional 
ess_18.10.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBXZYy36FIn+KrmaIaAQj51xAAop0y60Ns2IsGJk6SKKSnbgdudBhpESjI
JjK3bP+m92PdQ50ewTqm40phNzJgVhs91WdGMxgnXQyyLLul0kRmAf7rnPiAjY37
T2CfNm3XQ/FsLbDcsJkp0VCuIIcwtNmEsl816ZYHPWiH1H6CccMKi3A0zZLdycAw
ADMTMTsC7nz1lxEdaJHreinffRLLJWypXSTKh00gWBczUJHjVNw8f3SQIyqmRuSZ
l1SpIe9ebxm8C62c2Bz3Hishz6LyWStLuHAA/NJWSl5SQZj7vgoIF0Pmh27G1Lad
a90MipjvkzTnhIGethjoL8/Aw1dkCFptxEjtMTZ2RN+rmfUI2hRIdvCRr/DYqR6Z
3eFBmZeOA2qKkJB5cKxN6OkOgJAZ1UDu0Rp3JEa7mO8mtnQkBkn7S6bEdulLaaX7
pIRbAAAz47qdkWUlALvyzzld37mxoWC2M2OP3tqauvJ3lczdIsnIrCwsYyXaTqKd
vcf422NCQwHJ19NCklnwCOJD1Bn/OxNSjvWllNpGGBuF9hm5RQNjTLgTWDQNtA1Z

Bug#941516: marked as done (dieharder: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 17:49:07 +
with message-id 
and subject line Bug#941516: fixed in dieharder 3.31.1-8
has caused the Debian Bug report #941516,
regarding dieharder: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
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.)


-- 
941516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dieharder
Version: 3.31.1-7
Severity: serious
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch

Hi Dirk,

The texlive-generic-recommended transitional package has been dropped from
texlive-base in sid.  Please update your build-dependency to
texlive-plain-generic instead.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -u dieharder-3.31.1/debian/control dieharder-3.31.1/debian/control
--- dieharder-3.31.1/debian/control
+++ dieharder-3.31.1/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Dirk Eddelbuettel 
 Standards-Version: 3.9.6
-Build-Depends: debhelper (>= 7), libgsl-dev, automake, libtool, ghostscript, 
texlive-base, texlive-latex-base, texlive-generic-recommended
+Build-Depends: debhelper (>= 7), libgsl-dev, automake, libtool, ghostscript, 
texlive-base, texlive-latex-base, texlive-plain-generic
 
 Package: dieharder
 Architecture: any
--- End Message ---
--- Begin Message ---
Source: dieharder
Source-Version: 3.31.1-8

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated dieharder 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, 03 Oct 2019 12:17:00 -0500
Source: dieharder
Architecture: source
Version: 3.31.1-8
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Closes: 941516
Changes:
 dieharder (3.31.1-8) unstable; urgency=medium
 .
   * debian/control: Change Build-Depends: from texlive-generic-recommended
 to texlive-plain-generic   (Closes: #941516)
 .
   * debian/control: Set Build-Depends: to 'debhelper (>= 10)'
   * debian/control: Set Standards-Version: to current version
   * debian/control: Add Vcs-Browser: and Vcs-Git:
   * debian/compat: Increase level to 9
Checksums-Sha1:
 6f33977eaccf2141e9bcc3a0ea37cd9decebba99 2037 dieharder_3.31.1-8.dsc
 758d74c37ded29d04ca6bc2e06303432ec6487f3 8624 dieharder_3.31.1-8.debian.tar.xz
 3a464dc70e2ba3aab9a6a814b7d7c9533756850a 8763 
dieharder_3.31.1-8_amd64.buildinfo
Checksums-Sha256:
 607d8636bf3f43f7c051ebbbf1a3a0e60b976053b99246cd79d13dfee6260b92 2037 
dieharder_3.31.1-8.dsc
 3caeeb8ed0ba53f0866e55082c7934f12151c1da0cc54af9d535f8f7a8e71a18 8624 
dieharder_3.31.1-8.debian.tar.xz
 2fda2e8a1d2c384f4b12116519ff848bbbf012b746d00a268ac849875de0f6fd 8763 
dieharder_3.31.1-8_amd64.buildinfo
Files:
 ad04c1d49ebdc588f7afc5c6c86c1c16 2037 devel optional dieharder_3.31.1-8.dsc
 3cd7b9010a65d0da3b7c52e2ae7b030f 8624 devel optional 
dieharder_3.31.1-8.debian.tar.xz
 6f1769e288a20a87e8bbad78ebde56bd 8763 devel optional 
dieharder_3.31.1-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBXZYwmKFIn+KrmaIaAQgK2BAAl/aUPw7+SyJ7sRBdyrrSmcNqPYm91uWc
uV/JzTLasS3ST+NvfOL5SYQEEW5I+DbAAfX+3/qb8U3tL00AZ6qHl9X8pdMFZ9j6
u1AW5SSwv7nAd8LzMO9Th4VYe+DEhuuZAdqz1DwYS7Yv6kH59HZLMnqa8wZxjN8W
egdpiFAncWPAItgIDBbtEyBlWvXh0mrG9bjFYZkwJjX+4Y1LaHvbHG+l9z0gGKD+
Gqm8AeqfwOH2SZAuKo5SFW0fIEHUkB/I433/G2J2IaSaNkzLYHK9OzFZrDljwV4K
mlS+x5zjYlG8AyY0Opwqdcb/klyjxBmTP6d/kaWoNQ80UjTWMpe4Ml8O5TiRwwlb
NXhgIIP+YE2bBWc/3N7PymI5AyEsgbDgJ5w2kR67xfcA+2fMwyFjLZSq6zK/PoNs
9XMeRBd3k192UlI0B3iq+vDrQYpggittUq9A+8waOR8P4g79h3ARIb1X1NuOU6lv

Bug#941674: gnome-shell-extension-dashtodock: Not working

[Domenico Cufalo]

Package: gnome-shell-extension-dashtodock
Version: 66-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Latest upgrade to Gnome 3.34

   * What exactly did you do (or not do) that was effective (or ineffective)?

//

   * What was the outcome of this action?

Dashtodock is not working and https://extensions.gnome.org/local/ report an
error.

Maybe due to this error, at every error all extensions are disabled and I am
forced to activate them by hand by Gnome Tweak Tool.

I don't know how to debug this issue, but, if necessary, tell me how to do it
and I will do, if possible.

   * What outcome did you expect instead?

Dashtodock working. ;-)

Thank you very much in advance,
Domenico



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

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

Versions of packages gnome-shell-extension-dashtodock depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gir1.2-clutter-1.0   1.26.2+dfsg-12
ii  gnome-shell  3.34.0-2

gnome-shell-extension-dashtodock recommends no packages.

gnome-shell-extension-dashtodock suggests no packages.

-- no debconf information

Bug#939645: marked as done (Please use YAML.load_stream() instead of YAML.load_documents(), which was removed in ruby 2.5)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 16:19:38 +
with message-id 
and subject line Bug#939645: fixed in serverspec-runner 1.3.8-1
has caused the Debian Bug report #939645,
regarding Please use YAML.load_stream() instead of YAML.load_documents(), which 
was removed in ruby 2.5
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.)


-- 
939645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: serverspec-runner
Version: 1.2.2-1
Severity: grave
Tags: patch upstream
Justification: renders package unusable

Dear Maintainer,

The package uses the YAML.load_documents() method, which is no longer present
in the Ruby version that ships with Debian.

The method is replaced with YAML.load_stream(), which is compatible.

The error message, when run, is:

/tmp/tmp.o0z1Ka0UgW$ serverspec-runner
Traceback (most recent call last):
7: from /usr/bin/serverspec-runner:61:in `'
6: from /usr/bin/serverspec-runner:61:in `load'
5: from /usr/share/serverspec-runner/Rakefile:14:in `'
4: from /usr/lib/ruby/vendor_ruby/rake/dsl_definition.rb:141:in 
`namespace'
3: from /usr/lib/ruby/vendor_ruby/rake/task_manager.rb:224:in 
`in_namespace'
2: from /usr/share/serverspec-runner/Rakefile:167:in `block in '
1: from /usr/share/serverspec-runner/Rakefile:167:in `open'
/usr/share/serverspec-runner/Rakefile:168:in `block (2 levels) in ': undefined method `load_documents' for Psych:Module (NoMethodError)
Did you mean?  load_stream


A patch is available in the upstream repo, at
https://github.com/hiracy/serverspec-runner/pull/47/commits/c459787defe1b08bbe46a5acf0ea07039fe44f61
this is also included in upstream version 1.3.8

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/24 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages serverspec-runner depends on:
ii  ruby 1:2.5.1
ii  ruby-net-ssh 1:5.1.0-1
ii  ruby-serverspec  2.41.3-3

serverspec-runner recommends no packages.

serverspec-runner suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: serverspec-runner
Source-Version: 1.3.8-1

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

Debian distribution maintenance software
pp.
KURASHIKI Satoru  (supplier of updated serverspec-runner 
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, 02 Oct 2019 23:04:12 +0900
Source: serverspec-runner
Architecture: source
Version: 1.3.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: KURASHIKI Satoru 
Closes: 939645
Changes:
 serverspec-runner (1.3.8-1) unstable; urgency=medium
 .
   * New upstream release.
 - supports ruby > 2.5 (Closes: #939645)
   * New Standards-Version: 4.4.1.
   * Update gemwatch url.
Checksums-Sha1:
 eeab330d83a10d51fd02cceee66b5bc9ea90901d 2122 serverspec-runner_1.3.8-1.dsc
 6553fe787d91f4701bfe611a5c15a022e50b6504 10686 
serverspec-runner_1.3.8.orig.tar.gz
 e829a48c3ef3cc852a025a2cbd7e5005af9fd651 4056 
serverspec-runner_1.3.8-1.debian.tar.xz
 35808c8c55328d97c7c8872f2cf3c2511fc9ead3 9428 
serverspec-runner_1.3.8-1_amd64.buildinfo
Checksums-Sha256:
 752f4d11781341cf817fa1bb627877f8dee961ef3c2521e8417ec62e348ba7f3 2122 
serverspec-runner_1.3.8-1.dsc
 59748b6c33459d54925dd9c51015eb1476dc9a82d0081350cffd1349acd6b3c2 10686 
serverspec-runner_1.3.8.orig.tar.gz
 6b2f9b5ead1fff9d0dc599e1d2aa0899d3fe1d2cdf7b058cbd912251fa467218 

Bug#941669: python3-rpi.gpio fails to work on aarch64 (upgrade needed)

[André Draszik]

Package: python3-rpi.gpio
Version: 0.6.5-1
Severity: grave
Tags: upstream
Justification: renders package unusable


Hi,

python3-rpi.gpio 0.6.5 as is current in sid, doesn't support
aarch64:

Traceback (most recent call last):
  File "./server.py", line 8, in 
import RPi.GPIO as GPIO
  File "/usr/lib/python3/dist-packages/RPi/GPIO/__init__.py", line 23, in 

from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!


Upstream has fixed this in the 0.7.0 release, see here
https://sourceforge.net/p/raspberry-gpio-python/tickets/161/

I am kindly asking to please update the Debian package.

Andre'

-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 4.19.0-5-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-rpi.gpio depends on:
ii  libc62.28-10
ii  python3  3.7.3-1
ii  rpi.gpio-common  0.6.5-1

python3-rpi.gpio recommends no packages.

python3-rpi.gpio suggests no packages.

-- no debconf information

Bug#937154: marked as done (nordugrid-arc-nagios-plugins: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 14:52:53 +
with message-id 
and subject line Bug#937154: fixed in nordugrid-arc-nagios-plugins 2.0.0~rc2-1
has caused the Debian Bug report #937154,
regarding nordugrid-arc-nagios-plugins: Python2 removal in sid/bullseye
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.)


-- 
937154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nordugrid-arc-nagios-plugins
Version: 1.9.1-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + 
src:nordugrid-arc-nagios-plugins

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: nordugrid-arc-nagios-plugins
Source-Version: 2.0.0~rc2-1

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

Debian distribution maintenance software
pp.
Mattias Ellert  (supplier of updated 
nordugrid-arc-nagios-plugins 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: Thu, 03 Oct 2019 13:59:58 +0200
Source: nordugrid-arc-nagios-plugins
Architecture: source
Version: 2.0.0~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Mattias Ellert 
Changed-By: Mattias Ellert 
Closes: 937154
Changes:
 nordugrid-arc-nagios-plugins (2.0.0~rc2-1) unstable; urgency=medium
 .
   * Version 2.0.0 rc2
   * This version uses python 3 (Closes: #937154)
Checksums-Sha1:
 b0c7d6bbab23e1891ba45245baa824bf461a7500 2406 
nordugrid-arc-nagios-plugins_2.0.0~rc2-1.dsc
 a4ae8656afb8213148f3c71246cefeb8551a0f28 153757 
nordugrid-arc-nagios-plugins_2.0.0~rc2.orig.tar.gz
 edc7d70334e30d8d91d25d35126d97134869af6b 2732 
nordugrid-arc-nagios-plugins_2.0.0~rc2-1.debian.tar.xz
 48312a9545f5bd940b833bce18f0acaeb4f46539 8100 
nordugrid-arc-nagios-plugins_2.0.0~rc2-1_amd64.buildinfo
Checksums-Sha256:
 

Bug#941530: jackson-databind: CVE-2019-16942 CVE-2019-16943

[Sébastien Delafond]

On 02/10 09:43, Salvatore Bonaccorso wrote:
> Whilst I'm not yet sure if we should really release a futher DSA for
> jackson-databind (we will come back to you on that), a possible idea
> for bullseye (might be better cloned/filled as new bug, but want to
> mention it here already):

Let's do a DSA for this one. For future issues, we can choose to decide
on DSA vs. point release on a case-by-case basis, depending on severity.

Cheers,

-- 
Seb

Bug#941530: marked as done (jackson-databind: CVE-2019-16942 CVE-2019-16943)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 14:49:11 +
with message-id 
and subject line Bug#941530: fixed in jackson-databind 2.10.0-2
has caused the Debian Bug report #941530,
regarding jackson-databind: CVE-2019-16942 CVE-2019-16943
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.)


-- 
941530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jackson-databind
Version: 2.10.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/FasterXML/jackson-databind/issues/2478
Control: found -1 2.9.8-3
Control: found -1 2.8.6-1+deb9u5
Control: found -1 2.8.6-1

Hi,

Tony, Markus, As it was already expected ;-). Upstream, whilst it
affects as well 2.10.0, seemigly is not considering doing an update
for 2.10 specifically but have fixed this one as well for older
versions. Previous point, that this is just going to start to be silly
upholds.

That said, let's follow with the usual information:

The following vulnerabilities were published for jackson-databind.

CVE-2019-16942[0]:
| A Polymorphic Typing issue was discovered in FasterXML jackson-
| databind 2.0.0 through 2.9.10. When Default Typing is enabled (either
| globally or for a specific property) for an externally exposed JSON
| endpoint and the service has the commons-dbcp (1.4) jar in the
| classpath, and an attacker can find an RMI service endpoint to access,
| it is possible to make the service execute a malicious payload. This
| issue exists because of
| org.apache.commons.dbcp.datasources.SharedPoolDataSource and
| org.apache.commons.dbcp.datasources.PerUserPoolDataSource mishandling.


CVE-2019-16943[1]:
| A Polymorphic Typing issue was discovered in FasterXML jackson-
| databind 2.0.0 through 2.9.10. When Default Typing is enabled (either
| globally or for a specific property) for an externally exposed JSON
| endpoint and the service has the p6spy (3.8.6) jar in the classpath,
| and an attacker can find an RMI service endpoint to access, it is
| possible to make the service execute a malicious payload. This issue
| exists because of com.p6spy.engine.spy.P6DataSource mishandling.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-16942
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16942
[1] https://security-tracker.debian.org/tracker/CVE-2019-16943
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16943
[2] https://github.com/FasterXML/jackson-databind/issues/2478

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jackson-databind
Source-Version: 2.10.0-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated jackson-databind 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: Thu, 03 Oct 2019 15:48:58 +0200
Source: jackson-databind
Architecture: source
Version: 2.10.0-2
Distribution: unstable
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Closes: 941530
Changes:
 jackson-databind (2.10.0-2) unstable; urgency=high
 .
   * Fix CVE-2019-16942 and CVE-2019-16943.
 Block two more gadget types (commons-dbcp, p6spy). (Closes: #941530)
Checksums-Sha1:
 d85a666c27064d71ab0a5a528048f168c956f2d2 2689 jackson-databind_2.10.0-2.dsc
 30339c21d3c94c48628de2a4b54e9ae5f873b054 5728 
jackson-databind_2.10.0-2.debian.tar.xz
 d98b146913d8808dbd2e0bdcccdbe7e7b70191ce 16739 
jackson-databind_2.10.0-2_amd64.buildinfo
Checksums-Sha256:
 04812f6aa9d6e61734e8a606ce52f2a0f87bc935ce3bcd656528717105b2f7de 2689 
jackson-databind_2.10.0-2.dsc
 47bf0995591e22eddbf88c6cc667b541ca3017283e322fae2391c8ee7879adaa 5728 
jackson-databind_2.10.0-2.debian.tar.xz
 85edf15e6ea4bc7b4c245b6d7da37a46256d031ff5d30ff1670c1f9a3b119fa7 16739 

Bug#941661: daemon fails to start

[Mario.Limonciello]

This is a duplicate of 941360, which is fixed in git but waiting for review on 
some other important changes before upload:
https://salsa.debian.org/efi-team/fwupd/commit/04cb53bdce9037c4af09b70486efd26eb89686e0

> -Original Message-
> From: Laurent Bigonville 
> Sent: Thursday, October 3, 2019 8:29 AM
> To: Debian Bug Tracking System
> Subject: Bug#941661: daemon fails to start
> 
> 
> [EXTERNAL EMAIL]
> 
> Package: fwupd
> Version: 1.3.2-1
> Severity: serious
> 
> Hi,
> 
> It seems that the fwupd daemon fails to start:
> 
> oct 03 15:23:38 edoras systemd[1]: Starting Firmware update daemon...
> oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed to set up special
> execution directory in /var/cache: Not a directory
> oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed at step
> CACHE_DIRECTORY spawning /usr/lib/fwupd/fwupd: Not a directory
> oct 03 15:23:38 edoras systemd[1]: fwupd.service: Main process exited,
> code=exited, status=239/CACHE_DIRECTORY
> oct 03 15:23:38 edoras systemd[1]: fwupd.service: Failed with result 
> 'exit-code'.
> oct 03 15:23:38 edoras systemd[1]: Failed to start Firmware update daemon.
> 
> 
> Looking at /var/cache, I see:
> 
> ls -la /var/cache/fwupd/
> [...]
> lrwxr-xr-x.  1 root  root13 sep 28 22:49 fwupd -> 
> private/fwupd
> [...]
> 
> /var/cache/private/fwupd also exists
> 
> Kind regards,
> 
> Laurent Bigonville
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 
> 'experimental-debug'),
> (1, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
> Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
> LANGUAGE=fr_BE:fr (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
> 
> Versions of packages fwupd depends on:
> ii  libarchive13   3.4.0-1
> ii  libc6  2.29-2
> ii  libefiboot137-2
> ii  libefivar1 37-2
> ii  libelf10.176-1.1
> ii  libfwupd2  1.3.2-1
> ii  libgcab-1.0-0  1.2-5
> ii  libglib2.0-0   2.62.0-3
> ii  libgnutls303.6.9-5
> ii  libgpg-error0  1.36-7
> ii  libgpgme11 1.13.1-1
> ii  libgudev-1.0-0 233-1
> ii  libgusb2   0.3.0-1
> ii  libjson-glib-1.0-0 1.4.4-2
> ii  libpolkit-gobject-1-0  0.105-26
> ii  libsmbios-c2   2.4.1-1
> ii  libsoup2.4-1   2.68.1-2
> ii  libsqlite3-0   3.29.0-2
> ii  libtss2-esys0  2.1.0-4+b1
> ii  libxmlb1   0.1.8-1+b1
> ii  shared-mime-info   1.10-1
> 
> Versions of packages fwupd recommends:
> ii  bolt   0.8-4
> ii  fwupd-amd64-signed [fwupd-signed]  1.3.2+1
> ii  python33.7.5-1
> 
> fwupd suggests no packages.
> 
> -- no debconf information

Processed: Re: Bug#941530: jackson-databind: CVE-2019-16942 CVE-2019-16943

[Debian Bug Tracking System]

Processing control commands:

> clone 941530 -1
Bug #941530 [src:jackson-databind] jackson-databind: CVE-2019-16942 
CVE-2019-16943
Bug 941530 cloned as bug 941662
> retitle -1 jackson-databind: consider using a whitelist
Bug #941662 [src:jackson-databind] jackson-databind: CVE-2019-16942 
CVE-2019-16943
Changed Bug title to 'jackson-databind: consider using a whitelist' from 
'jackson-databind: CVE-2019-16942 CVE-2019-16943'.
> severity -1 wishlist
Bug #941662 [src:jackson-databind] jackson-databind: consider using a whitelist
Severity set to 'wishlist' from 'grave'

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

Bug#941530: jackson-databind: CVE-2019-16942 CVE-2019-16943

[Markus Koschany]

Control: clone 941530 -1
Control: retitle -1 jackson-databind: consider using a whitelist
Control: severity -1 wishlist

Hi,

Am 02.10.19 um 09:43 schrieb Salvatore Bonaccorso:
[...]
> Whilst I'm not yet sure if we should really release a futher DSA for
> jackson-databind (we will come back to you on that), a possible idea
> for bullseye (might be better cloned/filled as new bug, but want to
> mention it here already):
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1731271
> 
> Red Hat recently had fixed a CVE for codehaus. The approach they took
> there was to rather continuing on jackson-databind side (that is my
> interpretation), they started a whitelist approach on the applications
> side which use jackson-databind.
> 
> This might be something to consider for bullseye as well for the
> reverse dependencies. Not sure if this is feasible in our case, but
> this might be worth investigating.

Good idea. Let's investigate this solution. I will track that in another
bug report.

Regards,

Markus





signature.asc
Description: OpenPGP digital signature

Bug#941661: daemon fails to start

[Laurent Bigonville]

Package: fwupd
Version: 1.3.2-1
Severity: serious

Hi,

It seems that the fwupd daemon fails to start:

oct 03 15:23:38 edoras systemd[1]: Starting Firmware update daemon...
oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed to set up special 
execution directory in /var/cache: Not a directory
oct 03 15:23:38 edoras systemd[3854]: fwupd.service: Failed at step 
CACHE_DIRECTORY spawning /usr/lib/fwupd/fwupd: Not a directory
oct 03 15:23:38 edoras systemd[1]: fwupd.service: Main process exited, 
code=exited, status=239/CACHE_DIRECTORY
oct 03 15:23:38 edoras systemd[1]: fwupd.service: Failed with result 
'exit-code'.
oct 03 15:23:38 edoras systemd[1]: Failed to start Firmware update daemon.


Looking at /var/cache, I see:

ls -la /var/cache/fwupd/ 
[...]
lrwxr-xr-x.  1 root  root13 sep 28 22:49 fwupd -> 
private/fwupd
[...]

/var/cache/private/fwupd also exists

Kind regards,

Laurent Bigonville

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (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

Versions of packages fwupd depends on:
ii  libarchive13   3.4.0-1
ii  libc6  2.29-2
ii  libefiboot137-2
ii  libefivar1 37-2
ii  libelf10.176-1.1
ii  libfwupd2  1.3.2-1
ii  libgcab-1.0-0  1.2-5
ii  libglib2.0-0   2.62.0-3
ii  libgnutls303.6.9-5
ii  libgpg-error0  1.36-7
ii  libgpgme11 1.13.1-1
ii  libgudev-1.0-0 233-1
ii  libgusb2   0.3.0-1
ii  libjson-glib-1.0-0 1.4.4-2
ii  libpolkit-gobject-1-0  0.105-26
ii  libsmbios-c2   2.4.1-1
ii  libsoup2.4-1   2.68.1-2
ii  libsqlite3-0   3.29.0-2
ii  libtss2-esys0  2.1.0-4+b1
ii  libxmlb1   0.1.8-1+b1
ii  shared-mime-info   1.10-1

Versions of packages fwupd recommends:
ii  bolt   0.8-4
ii  fwupd-amd64-signed [fwupd-signed]  1.3.2+1
ii  python33.7.5-1

fwupd suggests no packages.

-- no debconf information

Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"

[Andreas Henriksson]

Control: reassign 940468 gnome-session
Control: forcemerge 940468 -1

Hi,

On Thu, Oct 03, 2019 at 02:16:32PM +0200, Michael Ott wrote:
> Hi!
> 
> I have the same problem. And I already create a bug report here
> #940468
> 
> But I found out that it is a problem with mutter.
> Using mutter 3.34.0-1 it works

I'm not sure how mutter has anything to do with anything here, but your log 
also contains:

Sep 16 07:52:31 k-c13 gnome-session-c[44308]: Failed to call signal 
initialization: GDBus.Error:org.gnome.SessionManager.GeneralError: Initialized 
interface is only available when gnome-session is managed by systemd

Which means it's likely the same problem.

Please be more specific about which actual session you're using in the
future (and my recommendation would be to stay away from the
"System X11 Default" one).

Hopefully the just uploaded version should fix your problems.

Regards,
Andreas Henriksson

Processed: Re: Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"

[Debian Bug Tracking System]

Processing control commands:

> reassign 940468 gnome-session
Bug #940468 [mutter] mutter: Crash on login after update to 3.34.0-2
Bug reassigned from package 'mutter' to 'gnome-session'.
No longer marked as found in versions mutter/3.34.0-2.
Ignoring request to alter fixed versions of bug #940468 to the same values 
previously set
> forcemerge 940468 -1
Bug #940468 [gnome-session] mutter: Crash on login after update to 3.34.0-2
Bug #940468 [gnome-session] mutter: Crash on login after update to 3.34.0-2
The source gnome-session and version 3.34.0-3 do not appear to match any binary 
packages
Marked as fixed in versions gnome-session/3.34.0-3.
Marked as found in versions gnome-session/3.34.0-2.
Bug #941640 {Done: Andreas Henriksson } [gnome-session] 
System X11 Default session fails in GNOME 3.34
Severity set to 'important' from 'grave'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions gnome-session/3.34.0-3.
Bug #941640 [gnome-session] System X11 Default session fails in GNOME 3.34
The source gnome-session and version 3.34.0-3 do not appear to match any binary 
packages
Marked as fixed in versions gnome-session/3.34.0-3.
Merged 940468 941640

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

Bug#941640: marked as done (System X11 Default session fails in GNOME 3.34)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 12:49:33 +
with message-id 
and subject line Bug#941640: fixed in gnome-session 3.34.0-3
has caused the Debian Bug report #941640,
regarding System X11 Default session fails in GNOME 3.34
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.)


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

With the Gnome upgrade from 3.30 to 3.34, a Gnome session now fails to
start.

gdm3 runs fine, the login screen is shown and I can proceed with
logging in.  But instead of logging in and starting a session, it
instead switches to a grey screen with the message

"Oh no, something has gone wrong. A problem has occurred and the
system can't recover. Please log out and try again." 

So Gnome 3.34 is currently unusable.

This is with Gnome x11, not wayland.


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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages gnome-session depends on:
ii  gnome-session-bin  3.34.0-2
ii  gnome-session-common   3.34.0-2
ii  gnome-settings-daemon  3.34.0-3
ii  gnome-shell3.34.0-2

gnome-session recommends no packages.

Versions of packages gnome-session suggests:
ii  desktop-base   10.0.3
ii  gnome-keyring  3.34.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-session
Source-Version: 3.34.0-3

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated gnome-session 
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: Thu, 03 Oct 2019 14:27:50 +0200
Source: gnome-session
Architecture: source
Version: 3.34.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Andreas Henriksson 
Closes: 941640
Changes:
 gnome-session (3.34.0-3) unstable; urgency=medium
 .
   * Add d/p/Make-sure-to-pass-systemd-when-we-re-managing-the-user-se.patch
 Thanks to Iain Lane for the patch. (Closes: #941640)
Checksums-Sha1:
 814e99fb14ddbfa443d1b5ba63cb3cf549739b73 2568 gnome-session_3.34.0-3.dsc
 e994850d3c715a99f2ac645e0ac31c3753435839 34404 
gnome-session_3.34.0-3.debian.tar.xz
 d402cabcd0bc4c4516f14878021eb19fe76dfca6 15497 
gnome-session_3.34.0-3_amd64.buildinfo
Checksums-Sha256:
 099ac43971b0d5435aabe3a11bc88140dae8da6ffa1262551a166fc25e8c4e82 2568 
gnome-session_3.34.0-3.dsc
 96be64c171a42b22c6aaefd30f173ec7fdd28790680144cf614f9a867df02828 34404 
gnome-session_3.34.0-3.debian.tar.xz
 33400647a5876b1b697db86e213d4261751536bf49bd1811b9b13450db0494f7 15497 
gnome-session_3.34.0-3_amd64.buildinfo
Files:
 e65377262ad9b6018d570bb8bb668470 2568 gnome optional gnome-session_3.34.0-3.dsc
 1ed57f9e1d2b9fd5fc6bbc2435df3129 34404 gnome optional 
gnome-session_3.34.0-3.debian.tar.xz
 0e4b2bb5e4b990c3c73d4e086bc15c48 15497 gnome optional 
gnome-session_3.34.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE+uHltkZSvnmOJ4zCC8R9xk0TUwYFAl2V6e4RHGFuZHJlYXNA
ZmF0YWwuc2UACgkQC8R9xk0TUwYPtw/+PXNZq0zQOWMzqrf/ENwT/57EUMmOYu5w
NA28AoB4tMATTLl1rE4i7HYsAQTc9DqrlDOebn4LAZrLZgfwoB4dZyIey3GF8FIk
9MrZASq2sgk6n1D8LoKjP0bQjam/4OLcJwcLJGcOuGSV3epPcDuV3IHOgmWK17Wu
WkcUrmF9rqjUa+MohL9UmDNYhW/sjJ5VQYEHDmz4W7p11k30WJh75Z477QHiPWyN
qyI0QDdwqTmuxQMuaLYbBx89DHQqfEffIT80AcF0sP2aUpgLqBIJgOjYUYH2oOxa
TFFQYsd5GfN3MO5muDrTZ74+ZclIYSTuyYf5pgyFdYj4VFmotgAzDgs9ZtoPe7+d
Eo7REXw/dKAeSWGM9izHGC2ax0P7FcRSSSgNMGjSWLB9a5jBugQYkGIAG7nQyPBC

Bug#941643: marked as done (Python2 still used in the autopkg tests)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 12:35:21 +
with message-id 
and subject line Bug#941643: fixed in python-csb 1.2.5+dfsg-5
has caused the Debian Bug report #941643,
regarding Python2 still used in the autopkg tests
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.)


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

Package: src:python-csb
Version: 1.2.5+dfsg-4
Severity: serious
Tags: sid bullseye patch

Python2 is still used in the autopkg tests. Patch at
http://launchpadlibrarian.net/445147475/python-csb_1.2.5+dfsg-4_1.2.5+dfsg-4ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: python-csb
Source-Version: 1.2.5+dfsg-5

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-csb 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: Thu, 03 Oct 2019 14:01:27 +0200
Source: python-csb
Architecture: source
Version: 1.2.5+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 941643
Changes:
 python-csb (1.2.5+dfsg-5) unstable; urgency=medium
 .
   [ Matthias Klose ]
   * Stop running Python2 autopkg tests.
 Closes: #941643
 .
   [ Andreas Tille ]
   * Set upstream metadata fields: Repository.
Checksums-Sha1:
 267f6ee7ac5bde9a168d21f0ba65c68a5bfd4296 2250 python-csb_1.2.5+dfsg-5.dsc
 36dd4885b9be3eb350abcfca3222bc746b31cd93 9788 
python-csb_1.2.5+dfsg-5.debian.tar.xz
 128449d01d2c7235f8c3c77f8d433a2c3256a9b2 7088 
python-csb_1.2.5+dfsg-5_amd64.buildinfo
Checksums-Sha256:
 edf7ddce8b45274f600c7fb2f86c5a291f05eb85ad70b545197a67b463d2e1dc 2250 
python-csb_1.2.5+dfsg-5.dsc
 9b5b1977d36a8c1e2fcb7d9b49e89bcf271e05a9620b13318836f8b13da143c6 9788 
python-csb_1.2.5+dfsg-5.debian.tar.xz
 87912f3b462103e8966b7e20a11464c874f302c868a368b3e196e05709ffa9e8 7088 
python-csb_1.2.5+dfsg-5_amd64.buildinfo
Files:
 ad1f446ae6c7127da2784ffbdb539b6b 2250 science optional 
python-csb_1.2.5+dfsg-5.dsc
 5399ee0b4541c171ad400f0d4462d327 9788 science optional 
python-csb_1.2.5+dfsg-5.debian.tar.xz
 198cffc1481e87375d430edf13231902 7088 science optional 
python-csb_1.2.5+dfsg-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl2V5HgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE1/g//YfJ9nzljwKFmyJ5FvqL/j8xa2XeVp/4L
r9WQbJoxJ3VbNKLRSFq2X+P8KBHggrTUWcNVPBul50oNLw7EhBElaBJc2dc5eXjQ
YJp5y+wFX2d9oRSDld8ATVHfdfizarLh8UW0sHmfT+gjmuoSQuVzPRVv8MbZKKbS
AtX8031fkQhtrKDooYXenkQljRPRE+yd+kCE/dwdhun/Qb4hT6CpgD/BHTZ7RmXn
Vh3di/1uvRrBNi1adBoKq0AJSjwpb3QIBNQ3xnHbUh3qsTa7RvRV6ToTMj7MPLBm
Mk/VWZtlKWXaiko9PhIJ5GuVeC98xyYN5I+4YFxyOUwV7rhX+SYZgyUcy3dYOAGZ
dAc1E6wacBrv4Hgw2OUww+kq/8N8VOJjSfx47Lc6B7KQ3sE1R9G9kEnN46l6ML5V
Y07yhyPIhVxVdmEbvH9SY7ou/fVn4//FkNSsqagpPMHFtKXSfidrjKKkYFMShnNa
NFajbPgR0G/CiJHnY68a+tato8A//9/WrK8Sy9w7e8umOXGr+pAefq3rzUiHQ0ou
BRYJfdnAEqBnbSECKYthvUd69Gl4D4tQ2widiaamTqeoF8KBlONADH1b9IfTRjJZ
85xHb98gACbeTHnKZjvwxJ0brZGtgZd72daAczoAwCv1pg16fKfbsp6uXUfrFA7D
tv3J0wxgFyE=
=MYAz
-END PGP SIGNATURE End Message ---

Bug#925666: marked as done (ddd: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 12:34:06 +
with message-id 
and subject line Bug#925666: fixed in ddd 1:3.3.12-5.2
has caused the Debian Bug report #925666,
regarding ddd: ftbfs with GCC-9
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.)


-- 
925666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ddd
Version: 1:3.3.12-5.1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/ddd_3.3.12-5.1_unstable_gcc9.log
The last lines of the build log are at the end of this report.

To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
cat > root.h~ && mv root.h~ root.h
/usr/bin/make ddd.info
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o assert.o 
/<>/./ddd/assert.C
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o basename.o 
/<>/./ddd/basename.C
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o compare.o 
/<>/./ddd/compare.C
make[4]: Entering directory '/<>/builddir/ddd'
make[4]: Leaving directory '/<>/builddir/ddd'
info --subnodes -o - -f /<>/./ddd/ddd.info | cat > 
/<>/./ddd/ddd.info.txt~ \
&& mv /<>/./ddd/ddd.info.txt~ 
/<>/./ddd/ddd.info.txt
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o cook.o 
/<>/./ddd/cook.C
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o cwd.o 
/<>/./ddd/cwd.C
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o glob.o 
/<>/./ddd/glob.C
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o hash.o 
/<>/./ddd/hash.C
g++ -DHAVE_CONFIG_H -I. -I/<>/./ddd  -I/<>/./ddd/..  
-Wdate-time -D_FORTIFY_SOURCE=2  -O2 -g -Wall -W -Wwrite-strings -Wformat 
-Werror=format-security -W -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -DNDEBUG -trigraphs  -c -o home.o 
/<>/./ddd/home.C
In file included from /<>/./ddd/cook.h:31,
 from /<>/./ddd/cook.C:36:
/<>/./ddd/strclass.h:813:19: error: friend declaration of 'string 
common_prefix(const string&, const string&, int)' specifies default arguments 
and isn't a definition [-fpermissive]
  813 | friend string common_prefix(const string& x, const string& y,

Processed: Bug#941640 marked as pending in gnome-session

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941640 [gnome-session] System X11 Default session fails in GNOME 3.34
Added tag(s) pending.

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

Bug#941640: marked as pending in gnome-session

[Andreas Henriksson]

Control: tag -1 pending

Hello,

Bug #941640 in gnome-session reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gnome-session/commit/7790aef10c84bdf72f75c0dc870cf31a5d30e9a9


Add d/p/Make-sure-to-pass-systemd-when-we-re-managing-the-user-se.patch

Closes: #941640
Thanks: Iain Lane for the patch.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941640

Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"

[Michael Ott]

Hi!

I have the same problem. And I already create a bug report here
#940468

But I found out that it is a problem with mutter.
Using mutter 3.34.0-1 it works

CU
  Michael

Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"

[Drew Parsons]

On 2019-10-03 19:55, Andreas Henriksson wrote:


So Gnome 3.34 is currently unusable.


FWIW I have a hard time agreeing with this conclusion.
One solution would be to simply drop support for "System X11 Default"
which we're currently patching in. I'd say using it is not recommended
and it only exists for legacy reasons. If you're using GNOME you should
use either of the GNOME sessions and if not, then you should probably
use something else than gdm. (And given this I don't think the current
severity is warranted either.)



Fair call, Gnome standard is fine (it also seemed to be failing when I 
first filed the bug, it must have cleared after reboot).  Whether the 
bug severity should be downgraded depends I guess on how important the 
"Gnome classic" mode is.


Drew

Bug#941645: marked as done (autopkg test still using Python2)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 12:05:43 +
with message-id 
and subject line Bug#941645: fixed in python-croniter 0.3.30-2
has caused the Debian Bug report #941645,
regarding autopkg test still using Python2
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.)


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

Package: src:python-croniter
Version: 0.3.29-2
Severity: serious
Tags: sid bullseye patch

The autopkg test is still using Python2. Patch at
http://launchpadlibrarian.net/445148515/python-croniter_0.3.29-2_0.3.29-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: python-croniter
Source-Version: 0.3.30-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-croniter 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, 03 Oct 2019 13:34:34 +0200
Source: python-croniter
Architecture: source
Version: 0.3.30-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 941645
Changes:
 python-croniter (0.3.30-2) experimental; urgency=medium
 .
   * Do not use Python2 in autopkgtest (Closes: #941645).
Checksums-Sha1:
 b9f5308c48bbe312dc2efca59ada2393ebcb46d0 2182 python-croniter_0.3.30-2.dsc
 48a9f2a087a8d80ad1d796c7bbc546d00472b6e6 3544 
python-croniter_0.3.30-2.debian.tar.xz
 6ccda01e15831b879c8280e2c40babe2d15a4eb4 6703 
python-croniter_0.3.30-2_amd64.buildinfo
Checksums-Sha256:
 4d9cfabeeb0a738cf449b3d717b3a67c9162c6a53be6958c9fb459df1783daa2 2182 
python-croniter_0.3.30-2.dsc
 f336f6bf2d72b1f963dfd5ae4ec0a0a6d340fa2881fd74efa156bcb8812f320d 3544 
python-croniter_0.3.30-2.debian.tar.xz
 929036f999ae7bf7449a131a88a12294eb6edb54a0a30688dd21278e95860191 6703 
python-croniter_0.3.30-2_amd64.buildinfo
Files:
 074b80fac38bb0027f229bbb058d6d3a 2182 python optional 
python-croniter_0.3.30-2.dsc
 273075ad8562ccd8eeab222ac734bbb7 3544 python optional 
python-croniter_0.3.30-2.debian.tar.xz
 6a457ab7b9a64917032e4fc9a3dccac1 6703 python optional 
python-croniter_0.3.30-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl2V3TwACgkQ1BatFaxr
Q/6LYQ/+J7rpsW9VSKF2049QbIWU2iew6JsQpCogyNRyxHXVuz1v96QlKZoqFYYP
SoIqN+5nsS07PnNWkL2qvqC+g5rroRfMYhWTQiDNAMPg7t1SPho6ho3o01bDlAxK
E8Fc0yyvMTt/A5oE4Fm+1djTSQ+dHbcd9uDQR1j9AqafJvfPCXLsOtjWa8sSSthr
X7NPMPkiu3w+9cq7FoSpOwNKroRCi0BmSKSt4ntxq0cv9bbsZj8eSrpkfN3NE+Kq
RI6D11b+r73NKDijgpGB9634Td1TeLEYHMVPbSLf+x7jgmd/yp0MscvyFVxnAMCH
lh9OxuAQqSiwe1EtHrbwm0DPW9NnBTKPiOHwKc6sPSm/XkVqCgcImrgn24Z8nUeZ
5VXyJfOLAHpWfz7gnmuvVUqjMGOMqt9Cwvap5U/VsZMPPw0KiWOZmUSSykvC4aE/
kcsgkX/prrOxbf39KpA4mZ519hhH3xcK8kE6Zu/337paELG+PfFx+6ojuaESMV+h
0iEjhjADasx89zqZjee8UHOmv7aG8F8lKEcCYl5tBHLIjsunfE5lBxx5VKc+eQGF
fcMWgF7vRBNisWSO4xvJHUOhgZJizonHJeBoe10B2JctlBKVUZ0WnARu0+vvkmJq
HjSUwRh0kBYr0A7jWwcas33U7vL/nSxBsBtqj7tsESgHPkkC+jE=
=avSp
-END PGP SIGNATURE End Message ---

Bug#849308: wireguard: Wireguard should not transition to stable yet

[Daniel Kahn Gillmor]

Hi Willem--

On Tue 2019-10-01 06:50:29 +0200, Willem van den Akker wrote:

> I offer by help for maintaining packaging WG.

Thank you, happy to have help!

> Please let me know how I can help.

Please make sure you can build the package from the debian/master branch
at https://salsa.debian.org/debian/wireguard.

If you can do that successfully (it shouldn't be too hard), feel free to
take a look at the debian/TODO file, which contains a handful of
suggestions, mostly about setting up more detailed autopkgtest testing.

Another thing that might be handy is to read through the discussion
starting here:

https://lists.debian.org/deity/2019/09/msg00017.html

The idea is to propose a debian package for binary wireguard kernel
modules that matches the current kernel package, so that users wouldn't
need to use dkms.  getting the dependency details right there is tricky,
as is keeping it up to date, but it might be worth trying.

I've pushed a very ungainly initial attempt at this binary module
packaging to https://salsa.debian.org/debian/wireguard-modules -- you
might want to take a look at that and consider fixing one of the things
in debian/TODO there, and proposing a fix.  Alternately, testing its
build and seeing whether the resultant binary works or not on systems
without dkms would also be interesting.

Thanks for offering to help!

   --dkg


signature.asc
Description: PGP signature

Processed: Re: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 System X11 Default session fails in GNOME 3.34
Bug #941640 [gnome-session] gnome-session: Gnome 3.34 fails to start showing 
grey screen "Oh no, something has gone wrong"
Changed Bug title to 'System X11 Default session fails in GNOME 3.34' from 
'gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something 
has gone wrong"'.

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

Bug#941644: marked as done (autopkg test still using Python2)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 11:50:01 +
with message-id 
and subject line Bug#941644: fixed in python-debtcollector 1.22.0-2
has caused the Debian Bug report #941644,
regarding autopkg test still using Python2
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.)


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

Package: src:python-debtcollector
Version: 1.21.0-2
Severity: serious
Tags: sid bullseye patch

The autopkg test is still using Python2. Patch at
http://launchpadlibrarian.net/445149005/python-debtcollector_1.21.0-2_1.21.0-2ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: python-debtcollector
Source-Version: 1.22.0-2

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-debtcollector 
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, 03 Oct 2019 13:29:12 +0200
Source: python-debtcollector
Architecture: source
Version: 1.22.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 941644
Changes:
 python-debtcollector (1.22.0-2) experimental; urgency=medium
 .
   * Do not use Python2 in autopkgtest (Closes: #941644).
Checksums-Sha1:
 8d64c54400331d3e59077569b84a7887b2b775d5 2443 python-debtcollector_1.22.0-2.dsc
 87739079df0841ff9acaa1ffafd132a4334d 3500 
python-debtcollector_1.22.0-2.debian.tar.xz
 bd6d7a3791825c100413918b9365daf90488937a 8921 
python-debtcollector_1.22.0-2_amd64.buildinfo
Checksums-Sha256:
 c720d21f7a0a155d0f84cdf84c70857ac1904a6105957a765959c6df63160b91 2443 
python-debtcollector_1.22.0-2.dsc
 34b8664a93b9a69a449b0f3c97c3869b261d8301a5b72ef93d36c9a601e85d69 3500 
python-debtcollector_1.22.0-2.debian.tar.xz
 f9144c690bd4c83516681c1d25f71bf2149defd26af9e8f50c24bd5c1d208478 8921 
python-debtcollector_1.22.0-2_amd64.buildinfo
Files:
 8d884cbc8784ae828cdf8bd2093c2ca6 2443 python optional 
python-debtcollector_1.22.0-2.dsc
 dea9840f6e5e6f279e8df32d0217c42b 3500 python optional 
python-debtcollector_1.22.0-2.debian.tar.xz
 f9527af8013db121ee796bd493165283 8921 python optional 
python-debtcollector_1.22.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl2V3CYACgkQ1BatFaxr
Q/49ig/+NYSHgfM6d4+eHPRyjjNgvD563aVkQlJN1t9SvwJHUl3VMib5ML1mOA+f
gvw3C307LW4QPdhWpEYaqVC5qHp40cf6XOrllnkboaW2kz5O3JynTk87xuBzp+9t
EcrPHQbJV74zbERxSrRTkjJ2hTnXlvz6sCC86ePZ/0GrcAiKlJFyFIcAuBKa8H7C
qqu9AYvIToxHkt3L/KRaM9HPv161w5kQhw1gfWTAYXwVJvMoqLagGlfmTEMW+rgM
/UpL0FbAh5bf3xlfwB8kaMBP+12anTcObCo7FXLeQBAiVVuI7VuJe7cU16b1YhaC
Q796Oaywqhio7X1MpqjCB64m2iAl+jnteC/OrpOn8+BacgBqFkvYTFr55e4LpEs8
WbatCnQT+4ExK8KYoRnaFnEFRkVi7Rf2opmQFz9gqXySFiZT2pZx/S3KsJAcRUIJ
4Y752BUcfGh2B2cRidenDv4KyhWkOpltgIy7X23dsysxaJ+yC8CSaJ1anXQeCpW2
rVR/kA7xFt1Wg4O2ZFYLuuISRlRM1Gzg1HPnfM/pnXARwy4f00PJvpz9I7BM7Lca
NaEvk++bGbXEu5IOMPbO6GnTBvo15oEKbx7QcAaSRQ6n88E1FuE8Z5vDIy9A1oXm
unQRsYHBCqRFS7EAah88GwK8BtaYtPQ2TVbyWrZmrnNbgtTcqgo=
=FYVp
-END PGP SIGNATURE End Message ---

Processed: Bug#941644 marked as pending in python-debtcollector

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #941644 [src:python-debtcollector] autopkg test still using Python2
Added tag(s) pending.

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

Bug#941644: marked as pending in python-debtcollector

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #941644 in python-debtcollector reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/libs/python-debtcollector/commit/c0388a7c7d530f555d65527d01c3c1c8ee123717


Do not use Python2 in autopkgtest (Closes: #941644).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/941644

Bug#905206: Seems to crash in fortran lib

[Michael Crusoe]

Here is the crash with debug symbols (courtesy libc6-dbg libgfortran5-dbg
and a locally created profnet-snapfun-dbgym)

root@mrc-tux:/tmp# profnet_snapfun switch 385 55 10 46 100 PROFin.dat
PROFacc_tst.jct none

Program received signal SIGSEGV: Segmentation fault - invalid memory
reference.

Backtrace for this error:
#0  0x7faaf117e0ff in ???
at
/build/glibc-sPWrSm/glibc-2.29/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
#1  0x7faaf1680018 in formatted_transfer_scalar_read
at ../../../src/libgfortran/io/transfer.c:1649
#2  0x7faaf1681803 in formatted_transfer
at ../../../src/libgfortran/io/transfer.c:2326
#3  0x55a7ca3a63c6 in rdjct_jct2_
at ./snapfun_dir/prof.f:1042
#4  0x55a7ca3a7c64 in rdjct_
at ./snapfun_dir/prof.f:876
#5  0x55a7ca3b0967 in prof
at ./snapfun_dir/prof.f:108
#6  0x55a7ca39f25e in main
at ./snapfun_dir/prof.f:179
Segmentation fault (core dumped)

On Thu, Oct 3, 2019 at 12:35 PM olivier sallou  wrote:

>
>
> Le jeu. 3 oct. 2019 à 12:08, Michael Crusoe  a
> écrit :
>
>> On Sat, 9 Mar 2019 17:44:02 +0100 olivier sallou 
>> wrote:
>> > Looking at core generated file and using gdb we see that it fails in
>> > fortran lib.
>> >
>> > Either program tries something wrong in a fortran updated lib version,
>> > either the fortran lib is itself buggy.
>> >
>> > I have no fortran knowledge to debug this however. And it lacks debug
>> info
>> > to find calling line in profnet.
>>
>> The debug symbols exists for non-amd64 archs:
>> https://packages.debian.org/sid/profnet-snapfun-dbgsym
>>
>
> Fun to see it in different arch but not amd64... Will give a try when
> possible.
>
>
>> So you can make your own debug symbols locally by rebuilding the package,
>> or someone could upload a new source package as it has been almost a year.
>> I made some cosmetic cleanups to the Debian packaging if that is a good
>> enough excuse (though snapfun still segfaults for me)
>>
>> >
>> > Test: rofnet_snapfun switch 385 55 10 46 100 PROFin.dat PROFacc_tst.jct
>> > none dbg
>> >
>> > Gdb result:
>> >
>> > Core was generated by `profnet_snapfun switch 385 55 10 46 100
>> PROFin.dat
>> > PROFacc_tst.jct none dbg'.
>>
>> --
>> Michael
>>
>

-- 
Michael R. Crusoe
Co-founder & Lead, Common Workflow Language project

https://orcid.org/-0002-2961-9670

m...@commonwl.org
+1 480 627 9108

Bug#933573: marked as done (FTBFS against evolution-data-server 3.33.4: error: too few arguments to function ‘e_book_client_add_contact_sync’)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 10:49:22 +
with message-id 
and subject line Bug#933573: fixed in eweouz 0.12
has caused the Debian Bug report #933573,
regarding FTBFS against evolution-data-server 3.33.4: error: too few arguments 
to function ‘e_book_client_add_contact_sync’
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.)


-- 
933573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:eweous
Version: 0.11
Severity: wishlist
Tags: patch upstream

Control: user pkg-gnome-maintain...@lists.alioth.debian.org
Control: usertag -1 = evolution-data-server-3-33

Hi,

This version of e-d-s is still in experimental-NEW, but I'm trying to
prepare the archive for it to be uploaded (and I want to upload to
Ubuntu sooner probably). If you build from Vcs-Git, you should be able
to test this patch if you like.

eweous fails to build. One of the functions has changed its signature.
Build log attached, and a patch. Instead of E_BOOK_OPERATION_FLAG_NONE,
you could pass any other of the flags if that's appropriate.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]
sbuild (Debian sbuild) 0.77.1 (10 September 2018) on disco

+==+
| eweouz 0.11 (amd64)  Wed, 31 Jul 2019 16:11:23 + |
+==+

Package: eweouz
Version: 0.11
Source Version: 0.11
Distribution: experimental
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/experimental-amd64-3688a7c7-abac-464b-afbd-23d258e6e54c' 
with '<>'
I: NOTICE: Log filtering will replace 'build/eweouz-aSh58r/resolver-m1XVh2' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 file:/srv/mirrors/debian sid InRelease [149 kB]
Get:1 file:/srv/mirrors/debian sid InRelease [149 kB]
Get:2 file:/srv/mirrors/debian experimental InRelease [78.9 kB]
Get:2 file:/srv/mirrors/debian experimental InRelease [78.9 kB]
Get:3 file:/srv/mirrors/debian sid/contrib Sources [48.6 kB]
Ign:3 file:/srv/mirrors/debian sid/contrib Sources
Get:4 file:/srv/mirrors/debian sid/main Sources [8519 kB]
Ign:4 file:/srv/mirrors/debian sid/main Sources
Get:5 file:/srv/mirrors/debian sid/contrib amd64 Packages [58.3 kB]
Ign:5 file:/srv/mirrors/debian sid/contrib amd64 Packages
Get:6 file:/srv/mirrors/debian sid/main amd64 Packages [8380 kB]
Ign:6 file:/srv/mirrors/debian sid/main amd64 Packages
Get:3 file:/srv/mirrors/debian sid/contrib Sources [48.6 kB]
Get:4 file:/srv/mirrors/debian sid/main Sources [8519 kB]
Get:5 file:/srv/mirrors/debian sid/contrib amd64 Packages [58.3 kB]
Get:6 file:/srv/mirrors/debian sid/main amd64 Packages [8380 kB]
Get:7 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [43.2 
kB]
Get:8 file:/srv/mirrors/debian experimental/main Sources [387 kB]
Ign:8 file:/srv/mirrors/debian experimental/main Sources
Get:9 file:/srv/mirrors/debian experimental/main amd64 Packages [423 kB]
Ign:9 file:/srv/mirrors/debian experimental/main amd64 Packages
Get:8 file:/srv/mirrors/debian experimental/main Sources [387 kB]
Get:9 file:/srv/mirrors/debian experimental/main amd64 Packages [423 kB]
Get:10 
https://swift-proxy.bos01.canonistack.canonical.com:8080/v1/AUTH_1c975a261cc3453c8543c7485f5e4560/debian
 experimental InRelease [5991 B]
Get:11 
https://swift-proxy.bos01.canonistack.canonical.com:8080/v1/AUTH_1c975a261cc3453c8543c7485f5e4560/debian
 experimental/main amd64 Packages [24.2 kB]
Get:12 http://incoming.debian.org/debian-buildd buildd-unstable/contrib amd64 
Packages [3788 B]
Get:13 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 
Packages [158 kB]
Fetched 235 kB in 2s (102 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   

Bug#905206: Seems to crash in fortran lib

[olivier sallou]

Le jeu. 3 oct. 2019 à 12:08, Michael Crusoe  a
écrit :

> On Sat, 9 Mar 2019 17:44:02 +0100 olivier sallou 
> wrote:
> > Looking at core generated file and using gdb we see that it fails in
> > fortran lib.
> >
> > Either program tries something wrong in a fortran updated lib version,
> > either the fortran lib is itself buggy.
> >
> > I have no fortran knowledge to debug this however. And it lacks debug
> info
> > to find calling line in profnet.
>
> The debug symbols exists for non-amd64 archs:
> https://packages.debian.org/sid/profnet-snapfun-dbgsym
>

Fun to see it in different arch but not amd64... Will give a try when
possible.


> So you can make your own debug symbols locally by rebuilding the package,
> or someone could upload a new source package as it has been almost a year.
> I made some cosmetic cleanups to the Debian packaging if that is a good
> enough excuse (though snapfun still segfaults for me)
>
> >
> > Test: rofnet_snapfun switch 385 55 10 46 100 PROFin.dat PROFacc_tst.jct
> > none dbg
> >
> > Gdb result:
> >
> > Core was generated by `profnet_snapfun switch 385 55 10 46 100 PROFin.dat
> > PROFacc_tst.jct none dbg'.
>
> --
> Michael
>

Processed: unblock 934630 with 919641, block 934630 with 941518 ...

[Debian Bug Tracking System]

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

> unblock 934630 with 919641
Bug #934630 [release.debian.org] transition: octave
934630 was blocked by: 919641
934630 was not blocking any bugs.
Removed blocking bug(s) of 934630: 919641
> block 934630 with 941518
Bug #934630 [release.debian.org] transition: octave
934630 was not blocked by any bugs.
934630 was not blocking any bugs.
Added blocking bug(s) of 934630: 941518
> forwarded 919641 
> https://release.debian.org/transitions/html/auto-readline.html
Bug #919641 [release.debian.org] transition: readline (7 -> 8)
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-readline.html'.
> thanks
Stopping processing here.

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

Bug#941650: python-iptables ftbfs in unstable, accessing the network

[Matthias Klose]

Package: src:python-iptables
Version: 0.14.0~ds-1
Severity: serious
Tags: sid bullseye

python-iptables ftbfs in unstable, trying to download depndencies from the 
network:

python3 -m sphinx -N -E -T -b html . 
/home/packages/tmp/p/python-iptables-0.14.0~ds/.pybuild/docs/html/

Running Sphinx v1.8.5
making output directory...
loading intersphinx inventory from http://docs.python.org/objects.inv...
WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'http://docs.python.org/objects.inv' not fetchable due to 
: HTTPConnectionPool(host='127.0.0.1', 
port=9): Max retries exceeded with url: http://docs.python.org/objects.inv 
(Caused by ProxyError('Cannot connect to proxy.', 
NewConnectionError('0x7f648f975f50>: Failed to establish a new connection: [Errno 111] Connection 
refused')))

building [mo]: targets for 0 po files that are out of date
building [html]: targets for 4 source files that are out of date
updating environment: 4 added, 0 changed, 0 removed
reading sources... [ 25%] examples
reading sources... [ 50%] index
reading sources... [ 75%] intro
reading sources... [100%] usage
Segmentation fault (core dumped)
make[1]: *** [debian/rules:9: override_dh_auto_build-indep] Error 139
make[1]: Leaving directory '/home/packages/tmp/p/python-iptables-0.14.0~ds'
make: *** [debian/rules:5: build] Error 2

Bug#905206: Seems to crash in fortran lib

[Michael Crusoe]

On Sat, 9 Mar 2019 17:44:02 +0100 olivier sallou  wrote:
> Looking at core generated file and using gdb we see that it fails in
> fortran lib.
>
> Either program tries something wrong in a fortran updated lib version,
> either the fortran lib is itself buggy.
>
> I have no fortran knowledge to debug this however. And it lacks debug info
> to find calling line in profnet.

The debug symbols exists for non-amd64 archs:
https://packages.debian.org/sid/profnet-snapfun-dbgsym

So you can make your own debug symbols locally by rebuilding the package,
or someone could upload a new source package as it has been almost a year.
I made some cosmetic cleanups to the Debian packaging if that is a good
enough excuse (though snapfun still segfaults for me)

>
> Test: rofnet_snapfun switch 385 55 10 46 100 PROFin.dat PROFacc_tst.jct
> none dbg
>
> Gdb result:
>
> Core was generated by `profnet_snapfun switch 385 55 10 46 100 PROFin.dat
> PROFacc_tst.jct none dbg'.

--
Michael

Bug#941648: nm-tray FTBFS: error: invalid use of incomplete type ‘class QMetaEnum’

[Helmut Grohne]

Source: nm-tray
Version: 0.4.3-1
Severity: serious
Tags: ftbfs

nm-tray fails to build from source in unstable using sbuild on amd64. A
build log ends with:

| [ 64%] Building CXX object CMakeFiles/nm-tray.dir/src/nmmodel.cpp.o
| /usr/bin/c++  -DNM_TRAY_VERSION=\"0.4.2\" -DQT_CORE_LIB -DQT_DBUS_LIB 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_SIGNALS_SLOTS_KEYWORDS 
-DQT_WIDGETS_LIB -DQT_XML_LIB -DTRANSLATION_DIR=\"/usr/share/nm-tray\" 
-I/<>/obj-x86_64-linux-gnu -I/<> 
-I/<>/obj-x86_64-linux-gnu/nm-tray_autogen/include -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/KF5/NetworkManagerQt -isystem /usr/include/libnm -isystem 
/usr/include/libmount -isystem /usr/include/blkid -isystem 
/usr/include/glib-2.0 -isystem /usr/lib/x86_64-linux-gnu/glib-2.0/include 
-isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/KF5/ModemManagerQt -isystem /usr/include/ModemManager -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -O2 -g 
-DNDEBUG   -fPIC -std=gnu++11 -o CMakeFiles/nm-tray.dir/src/nmmodel.cpp.o -c 
/<>/src/nmmodel.cpp
| /<>/src/nmmodel.cpp: In member function ‘QVariant 
NmModel::dataRole(const QModelIndex&) const [with int role = 265]’:
| /<>/src/nmmodel.cpp:1041:141: error: invalid use of incomplete 
type ‘class QMetaEnum’
|  1041 | auto m_enum = 
NetworkManager::Device::staticMetaObject.enumerator(NetworkManager::Device::staticMetaObject.indexOfEnumerator("Type"));
|   |   
  ^
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qmetatype.h:49,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:46,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qabstractitemmodel.h:43,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/QAbstractItemModel:1,
|  from /<>/src/nmmodel.h:26,
|  from /<>/src/nmmodel.cpp:23:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:284:7: note: forward 
declaration of ‘class QMetaEnum’
|   284 | class QMetaEnum;
|   |   ^
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value ‘Ppp’ 
not handled in switch [-Wswitch]
|  1046 | switch (dev->type())
|   |^
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value 
‘OvsInterface’ not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value 
‘OvsPort’ not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value 
‘OvsBridge’ not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value ‘Wpan’ 
not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value ‘Lowpan’ 
not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value 
‘WireGuard’ not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1046:16: warning: enumeration value 
‘WifiP2P’ not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp: In member function ‘void 
NmModel::activateConnection(const QModelIndex&)’:
| /<>/src/nmmodel.cpp:1527:28: warning: enumeration value 
‘StaticWep’ not handled in switch [-Wswitch]
|  1527 | switch (sec_type)
|   |^
| /<>/src/nmmodel.cpp:1527:28: warning: enumeration value 
‘DynamicWep’ not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1527:28: warning: enumeration value ‘Leap’ 
not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1527:28: warning: enumeration value ‘WpaEap’ 
not handled in switch [-Wswitch]
| /<>/src/nmmodel.cpp:1527:28: warning: enumeration value 
‘Wpa2Eap’ not handled in switch [-Wswitch]
| make[3]: *** [CMakeFiles/nm-tray.dir/build.make:167: 
CMakeFiles/nm-tray.dir/src/nmmodel.cpp.o] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:108: CMakeFiles/nm-tray.dir/all] Error 2
| make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[1]: *** [Makefile:133: all] Error 2
| make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" returned exit code 2
| make: *** [debian/rules:9: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut

Bug#941432: [pkg-uWSGI-devel] Bug#941432: Bug#941432: Bug#941432: Bug#941432: uwsgi-core: Dependency libmatheval is getting out of bullseye

[Jonas Smedegaard]

Quoting Alexandre Rossi (2019-10-02 15:04:54)
> > > > > Do you have plans/solutions regarding this issue? Is it possible 
> > > > > to drop uwsgi-core dependency on libmatheval1?
> > > > 
> > > > It should be as simple as not building the matheval plugin which is 
> > > > not critical to uwsgi. Should I go on with this?
> > > 
> > > Yeah, I just wasn't sure that it'd be an acceptable solution for you.
> > > 
> > > But it's perfectly fine with me. :)
> > 
> > Well, I would say "tolerable" rather than "acceptable" - it is a real 
> > annoyance since it will directly remove features now offered in uwsgi.
> 
> upstream says in 1.9.20 changelog:
> 
> The matheval support has been removed, while a generic “matheval” plugin
> (for internal routing) is available (but not compiled in by default).
> See below for the new way for making “math” in config files.
> 
> > @Alexandre: Make sure to add a NEWS entry warning users of the removal 
> > of matheval - ideally enumerating explicitly all uwsgi options which has 
> > disappeared and may silently wreak havoc on local systems.
> > 
> > Also, better check e.g. with codesearch.debian.net if any packages rely 
> > on matheval-related uwsgi config options, and if so alert them with 
> > bugreports.
> 
> Search on "uwsgi matheval" or "uwsgi math" yields no result.

Ah well, seems you got better knowledge here than me, Alex :-)

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#941644: autopkg test still using Python2

[Matthias Klose]

Package: src:python-debtcollector
Version: 1.21.0-2
Severity: serious
Tags: sid bullseye patch

The autopkg test is still using Python2. Patch at
http://launchpadlibrarian.net/445149005/python-debtcollector_1.21.0-2_1.21.0-2ubuntu1.diff.gz

Bug#941645: autopkg test still using Python2

[Matthias Klose]

Package: src:python-croniter
Version: 0.3.29-2
Severity: serious
Tags: sid bullseye patch

The autopkg test is still using Python2. Patch at
http://launchpadlibrarian.net/445148515/python-croniter_0.3.29-2_0.3.29-2ubuntu1.diff.gz

Bug#941643: Python2 still used in the autopkg tests

[Matthias Klose]

Package: src:python-csb
Version: 1.2.5+dfsg-4
Severity: serious
Tags: sid bullseye patch

Python2 is still used in the autopkg tests. Patch at
http://launchpadlibrarian.net/445147475/python-csb_1.2.5+dfsg-4_1.2.5+dfsg-4ubuntu1.diff.gz

Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong")

[Drew Parsons]

More tests: the failure occurs when logging in with "System X11 Default" 
or "Gnome Classic" selected from the gdm3 login screen.


Log-in via the plain "Gnome" option does successfully start a 
gnome-session.  Extensions from 3.30 cause it to freeze, but that's a 
separate issue (it works if extensions are disabled).

Processed: block 919641 with 941641

[Debian Bug Tracking System]

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

> block 919641 with 941641
Bug #919641 [release.debian.org] transition: readline (7 -> 8)
919641 was not blocked by any bugs.
919641 was blocking: 934630
Added blocking bug(s) of 919641: 941641
> thanks
Stopping processing here.

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

Bug#940682: lava-server: depends on cruft package.

[Remi Duraffort]

> lava depends on gunicorn3 which is no longer built by the gunicorn source
package. I belive you need to change your dependency to gunicorn, possiblly
with a version constraint of >= 19.9.0-4

Should be fixed by https://git.lavasoftware.org/lava/lava/merge_requests/737


Thanks for reporting the issue.

-- 
Rémi Duraffort

Bug#941641: acl2: Build-Depends on emacs25 which has been removed from unstable/bullseye

[Paul Gevers]

Source: acl2
Version: 8.0dfsg-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

You package Build-Depends on "emacs25 | emacsen". For reproducibility reasons,
the Debian buildds only consider the first alternative. The emacs25 has been a
transitional package in buster, and src:emacs has recently stopped building
that package. Please update your Build-Depends.

This all came about because your package is part of the readline transition,
but it FTBFS on mipsel now.

Paul

PS: your package isn't migrating because you uploaded an arch:all
binary. Please do a source-only upload when you fix this issue.

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2VuEkACgkQnFyZ6wW9
dQoXcwf/RrWQfP6v0BeScTnd3LU6dznMK1p0ldlHrnRrOgLg8SjKrDVe9SaQm6JX
vvZXzUnhW/Vjdvk2BKqSlbUBCMo75ZY93cTNQDK9y6ht41dAfn3er/QDc5V44yA0
exW3rHJWUo4guTUeufvvWg3SZf4ooGkemjyHbppedPioNc9N7T7NyL8Qwt29L2l3
lHLVHrIK4dRuw3EMYaVI8fyrGkBHHU4oCi3Ljhck6hhjtt3ibITMkDt6yBFCmaih
Wg0qTCu1M5qmRlLTxE+IPkb3bOw8Kv3rc58tPbR6ktcl5KYJvvlZdg3uzA58isuZ
OPGqctPFxOElSxJcie43cSN3Dwafxg==
=3F00
-END PGP SIGNATURE-

Bug#941640: gnome-session: Gnome 3.34 fails to start showing grey screen "Oh no, something has gone wrong"

[Drew Parsons]

Package: gnome-session
Version: 3.34.0-2
Severity: grave
Justification: renders package unusable

With the Gnome upgrade from 3.30 to 3.34, a Gnome session now fails to
start.

gdm3 runs fine, the login screen is shown and I can proceed with
logging in.  But instead of logging in and starting a session, it
instead switches to a grey screen with the message

"Oh no, something has gone wrong. A problem has occurred and the
system can't recover. Please log out and try again." 

So Gnome 3.34 is currently unusable.

This is with Gnome x11, not wayland.


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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages gnome-session depends on:
ii  gnome-session-bin  3.34.0-2
ii  gnome-session-common   3.34.0-2
ii  gnome-settings-daemon  3.34.0-3
ii  gnome-shell3.34.0-2

gnome-session recommends no packages.

Versions of packages gnome-session suggests:
ii  desktop-base   10.0.3
ii  gnome-keyring  3.34.0-1

-- no debconf information

Bug#941639: update dependencies in autopkg test

[Matthias Klose]

Package: src:jupyter-sphinx-theme
Version: 0.0.6+ds1-8
Severity: serious
Tags: sid bullseye patch

update dependencies in autopkg test. patch at
http://launchpadlibrarian.net/445141023/jupyter-sphinx-theme_0.0.6+ds1-8_0.0.6+ds1-8ubuntu1.diff.gz

Bug#941638: autopkg tests still rely on removed python-schema

[Matthias Klose]

Package: src:docopt
Version: 0.6.2-2
Severity: serious
Tags: sid bullseye patch

The autopkg tests still rely on the removed python-schema.
Patch at
http://launchpadlibrarian.net/445139187/docopt_0.6.2-2_0.6.2-2ubuntu1.diff.gz

Bug#912860: Bug#933548: transition: gnome-desktop3

[Paul Gevers]

Hi,

On 03-10-2019 09:39, intrigeri wrote:
> FWIW, libgtk2-perl is going away in Bullseye; most of its
> reverse-dependencies were either ported to GTK 3, or not shipped in
> Buster thanks to RC bugs I had filed, or removed from the archive.
> What's left is tracked there:
> 
>  - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912860
>  - 
> https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=gtk2-removal=debian-perl%40lists.debian.org
> 
> The only reason why this set of packages was not automatically removed
> from testing yet is that libgtk2-perl is still on the list of key
> packages, because it's installed on many machines ("popcon").
> I believe this is explained by historical reasons that are invalid
> nowadays: this package used to have major reverse dependencies.
> 
> So, if it helps make the GNOME 3.34 transitions smoother, IMO it would
> be fine to remove libgtk2-perl and its reverse-dependencies from
> testing. Some might see this as a heavy hammer approach, but this was
> announced a year ago to all affected maintainers; either way, it will
> happen during the Bullseye cycle, eventually.

According to dak there are no reverse dependencies in testing, so I have
added a removal hint.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#941635: autopkg test still tries to test Python2

[Matthias Klose]

Package: src:commonmark-bkrs
Version: 0.5.4+ds-3
Severity: serious
Tags: sid bullseye patch

The autopkg test still tries to test Python2. Patch at
http://launchpadlibrarian.net/445137928/commonmark-bkrs_0.5.4+ds-3_0.5.4+ds-3ubuntu1.diff.gz

Bug#941634: thawab depends on python-okasha which isn't provided by src:okasha anymore

[Paul Gevers]

Package: thawab
Version: 4.1-1
Severity: serious
Justification: non-installable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

You package depends on python-okasha. However the maintainers of src:okasha
have desided to drop that package as Debian is try to get rid of Python 2
before the release of bullseye. This move makes your package
non-installable. So either fix the dependency you have on that package by
upgrading your package towards Python 3, or have the maintainer of src:okasha
(temporarily) revert the removal of the python2 package for now if the solution
to this issue takes more time. In that case please align with the maintainers
of okasha for a plan forward.

Paul

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

Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
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 thawab depends on:
ii  gir1.2-gtk-3.0  3.24.11-1
pn  gir1.2-webkit2-4.0  
pn  mdbtools
ii  python  2.7.16-1
ii  python-gi   3.34.0-1
pn  python-okasha   
pn  python-othman   
pn  python-paste
pn  python-whoosh   

Versions of packages thawab recommends:
pn  islamic-menus  

thawab suggests no packages.

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl2VpxcACgkQnFyZ6wW9
dQowVQf/Uoi+ePq054LXj2tMQZ8dmPfr2dP639qkmEqWE8TMTnQvprSc2yujsJza
bTJru9ituK+ZvdhftQbafcDsWOgLbD09nRJ5sWRBe8Ck5Ggove3vIu/w7669uLhc
XDktOTeYetDZwyoklrjaH7G6Drmp1yugBo/76JHkehePr60Hucnc5hC+PkIe1tTE
hDeFOklK2FDyhxG/pLLBZikdvSHqmsZL0mibv54fOzh0oSXQ9xdxhwpbm75S7dii
Y+FqmI/mzKCem8RvuwBXQ5m4h6QoyjLDGYzN/GNA2c0LDmDgat7EeR6d6LZmvKJs
cPsGErr4JYM/Js6dCtUWpUNCLU4QmQ==
=d7yL
-END PGP SIGNATURE-

Processed: Re: nordugrid-arc-nagios-plugins: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #937154 [src:nordugrid-arc-nagios-plugins] nordugrid-arc-nagios-plugins: 
Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'

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

Bug#933573: Bug#933548: transition: gnome-desktop3

[intrigeri]

Hi,

Simon McVittie wrote:
> On Thu, 03 Oct 2019 at 08:48:35 +0200, Andreas Henriksson wrote:
>> The odd one out is libgtk2-perl which fails test 44:
> ...
>> GdkPixbuf [ warning ] Inline XPM data is broken: Invalid XPM header
>> not ok 44 - Don't crash on partial pixmap data

> I think this might be caused by better error handling in gdk-pixbuf 2.38.2
> (),
> which I uploaded to make gdk-pixbuf silence the GTimeVal deprecation
> warnings in its own animation API, so that it wouldn't trigger -Werror
> in other packages if they don't actively use the animation API.

FWIW, libgtk2-perl is going away in Bullseye; most of its
reverse-dependencies were either ported to GTK 3, or not shipped in
Buster thanks to RC bugs I had filed, or removed from the archive.
What's left is tracked there:

 - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912860
 - 
https://udd.debian.org/cgi-bin/bts-usertags.cgi?tag=gtk2-removal=debian-perl%40lists.debian.org

The only reason why this set of packages was not automatically removed
from testing yet is that libgtk2-perl is still on the list of key
packages, because it's installed on many machines ("popcon").
I believe this is explained by historical reasons that are invalid
nowadays: this package used to have major reverse dependencies.

So, if it helps make the GNOME 3.34 transitions smoother, IMO it would
be fine to remove libgtk2-perl and its reverse-dependencies from
testing. Some might see this as a heavy hammer approach, but this was
announced a year ago to all affected maintainers; either way, it will
happen during the Bullseye cycle, eventually.

Cheers,
-- 
intrigeri

Bug#941124: marked as done (elixir-lang (autopkgtest) fails with new erlang)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 07:20:04 +
with message-id 
and subject line Bug#941124: fixed in erlang 1:22.1.1+dfsg-2
has caused the Debian Bug report #941124,
regarding elixir-lang (autopkgtest) fails with new erlang
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.)


-- 
941124: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941124
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu elixir-lang_1.9.1.dfsg-1 . ANY . unstable . -m "Rebuild against erlang 22.1"

Hi release team!

Apparently, elixir-land needs to be rebuilt against newer erlang 22.1.
Currently, it doesn't pass autopkgtest (see [1] for details).

There were some internal changes in Erlang re module (regular expressions) which
triggered the test failure. After a simple rebuild all tests pass again.

[1] 
https://ci.debian.net/data/autopkgtest/testing/amd64/e/elixir-lang/3018464/log.gz

-- System Information:
Debian Release: 10.1
  APT prefers stable-debug
  APT policy: (500, 'stable-debug'), (500, 'oldoldstable'), (500, 'stable'), 
(500, 'oldstable'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/12 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)
--- End Message ---
--- Begin Message ---
Source: erlang
Source-Version: 1:22.1.1+dfsg-2

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

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated erlang 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, 03 Oct 2019 07:55:19 +0300
Source: erlang
Architecture: source
Version: 1:22.1.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Erlang Packagers 
Changed-By: Sergei Golovan 
Closes: 941124
Changes:
 erlang (1:22.1.1+dfsg-2) unstable; urgency=medium
 .
   * Make erlang-base and erlang-base-hipe provide the erlang-pcre-
 virtual package to help tracking if elixir-lang or any other package
 that uses precompiled regexs needs rebuild (closes: #941124).
   * Use the version of upwards-stack.patch which has been approved upstream.
Checksums-Sha1:
 9bdc4c61c8710214c494bd47c5035eef5bfb7065 5093 erlang_22.1.1+dfsg-2.dsc
 94a1ef8872f3b32d36ee95d347a20e1c0ad3488e 61460 
erlang_22.1.1+dfsg-2.debian.tar.xz
 c166a195eaa9852f1d23933ed608c3020f362d19 28659 
erlang_22.1.1+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 1f33de1b10547edfcbf433e48e9a278ac7f386484954eae71fd0f4857a3ab4c2 5093 
erlang_22.1.1+dfsg-2.dsc
 082aa9873b0b118c115fdfa056ce63feb4d819a0bc10eb973ec32fd30562685f 61460 
erlang_22.1.1+dfsg-2.debian.tar.xz
 57ff06b20dc94e8a340b2d54eaff7f9ae8b7c7a6d2c1233788c90a2e922fe2cf 28659 
erlang_22.1.1+dfsg-2_amd64.buildinfo
Files:
 a04b493734a2d65b18f984d219a97ebd 5093 interpreters optional 
erlang_22.1.1+dfsg-2.dsc
 6b9c9fdf64c598a83b982453df4eab57 61460 interpreters optional 
erlang_22.1.1+dfsg-2.debian.tar.xz
 e291ab6102379f606222bb0eaa4e5679 28659 interpreters optional 
erlang_22.1.1+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAl2Vni8ACgkQTyrk60tj
54eaEQ/9FXXBUm/Od8rL0g6tCYlHFOuePmCOgh9pZBhG0tTRKJgavJ1JJRtk79od
0s24Ia3nmbiqQ1TZcWVyYDDewOolYxSfuYW7rnbDA1aHWHdhWpiNIxxs41X7Hq5H
9QOfiQ3iEjbZjrQD0GCMlCYQd4eo2B/5iV4a20mMMcAR7JfmgKlSZI+GVYAnutfk
rnv78eZ3ZKIlXAR+Wwuy+KPiX9WXPKnQHOxoDN6gQgVW9qRXLEtqEKgI3UuVcptg
xVum4/MBG2AtagNevZS77upUBjwO5vgAQQBlnD695Psg4ygnYCSe9avbWULotZVi
g8kmrrWvS6xr8C6GpP5r4DBwwlgVVruY1WcJsXQFwaPQJrxIbo/72kR8VQgjoB0E
f/3bazx+z9fUAYfQhNc672YFEaXU+KRz5r0qDErogvhr/ptR1GDZ7CPHu6dCRx8c
/coXq8j6Q9LS+HsofsqO6f+uoVrIwiN5nQek/jkIcsPW1eI8RE48+/VOqgBGJ5IH
ONtelYeYSRLDecCWIMyK6WOmAcoy+EcQ35GWaE+gFbEt2cemIQaUK2Yr4HrLIfYs
yqHbY3dxw4SUqyXyiywrFLUPDIEnLlPnk8+NIHbh9ncNB1tJODZ2knb+AOt63teX

Bug#933573: Bug#933548: transition: gnome-desktop3

[Simon McVittie]

On Thu, 03 Oct 2019 at 08:48:35 +0200, Andreas Henriksson wrote:
> On Wed, Oct 02, 2019 at 08:46:50PM -0400, Jeremy Bicha wrote:
> > There are also several autopkgtest failures triggered by glib2.0 and
> > gobject-introspection.
> 
> I quickly looked over these and it seems they're all except one related
> to compiling stuff with -Werror. Mostly because of using GTime and/or
> GTimeVal which is deprecated.
> 
> The odd one out is libgtk2-perl which fails test 44:
...
> GdkPixbuf [ warning ] Inline XPM data is broken: Invalid XPM header
> not ok 44 - Don't crash on partial pixmap data

I think this might be caused by better error handling in gdk-pixbuf 2.38.2
(),
which I uploaded to make gdk-pixbuf silence the GTimeVal deprecation
warnings in its own animation API, so that it wouldn't trigger -Werror
in other packages if they don't actively use the animation API.

> The one not related to GTime / GTimeVal is dbus-test-runner:
> test-libdbustest-mock.c:392:13: error: g_main_context_pending [-Werror]
>   392 |  while (g_main_pending())
>   | ^   
> test-libdbustest-mock.c:393:13: error: g_main_context_iteration [-Werror]
>   393 |   g_main_iteration(TRUE);
>   | ^ 

These macros have been deprecated for 17 years (it's not often that I
get to say that!). I opened #941488, for which Iain did an NMU already.

smcv

Bug#933573: Bug#933548: transition: gnome-desktop3

[Andreas Henriksson]

On Wed, Oct 02, 2019 at 08:46:50PM -0400, Jeremy Bicha wrote:
> There are also several autopkgtest failures triggered by glib2.0 and
> gobject-introspection.

I quickly looked over these and it seems they're all except one related
to compiling stuff with -Werror. Mostly because of using GTime and/or
GTimeVal which is deprecated.

The odd one out is libgtk2-perl which fails test 44:
[...]
ok 38
ok 39 - 'new_from_xpm_data' isa 'Gtk2::Gdk::Pixbuf'
ok 40
ok 41
ok 42
GdkPixbuf [ warning ] Inline XPM data is broken: Cannot read XPM
colormap
ok 43 - Don't crash on broken pixmap data
GdkPixbuf [ warning ] Inline XPM data is broken: Invalid XPM header
not ok 44 - Don't crash on partial pixmap data
#   Failed test 'Don't crash on partial pixmap data'
#   at t/GdkPixbuf.t line 126.
ok 45 - 'new_from_data' isa 'Gtk2::Gdk::Pixbuf'
ok 46
ok 47
ok 48
[...]

The one not related to GTime / GTimeVal is dbus-test-runner:
[...]
/bin/bash ../libtool  --tag=CC   --mode=link gcc -pthread 
-I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -Wall 
-Werror -g -O2 
-fdebug-prefix-map=/tmp/autopkgtest-lxc.ftgi3a2g/downtmp/build.NS5/src=. 
-fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro 
-Wl,-z,now -Wl,-z,defs -Wl,--as-needed -o test-own-name 
test_own_name-test-own-name.o -lgio-2.0 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 
-lglib-2.0 
test-libdbustest-mock.c: In function ‘test_signals’:
test-libdbustest-mock.c:392:13: error: g_main_context_pending [-Werror]
  392 |  while (g_main_pending())
  | ^   
test-libdbustest-mock.c:393:13: error: g_main_context_iteration [-Werror]
  393 |   g_main_iteration(TRUE);
  | ^ 
test-libdbustest-mock.c:413:13: error: g_main_context_pending [-Werror]
  413 |  while (g_main_pending())
  | ^   
test-libdbustest-mock.c:414:13: error: g_main_context_iteration [-Werror]
  414 |   g_main_iteration(TRUE);
  | ^ 
[...]


Regards,
Andreas Henriksson

Bug#941467: marked as done (samba: FTBFS on armel, armhf, mipsel)

[Debian Bug Tracking System]

Your message dated Thu, 03 Oct 2019 06:21:51 +
with message-id 
and subject line Bug#941467: fixed in samba 2:4.11.0+dfsg-8
has caused the Debian Bug report #941467,
regarding samba: FTBFS on armel, armhf, mipsel
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.)


-- 
941467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: samba
Version: 2:4.10.8+dfsg-1
Severity: serious
Justification: FTBFS

Dear Maintainer,

As you're probably well aware of the samba package fails to build  from
source on a few architectures in unstable (and I didn't see an open bug
report about it so I'm filing this for tracking/discussion purposes).

The problem has now become more problematic as the transitions related
to gnome 3.34 was started yesterday. The gnome-control-center package
build-depends on samba and is now thus blocked in "BD-Uninstallable".

As release-team resources are scarse and there are many other
transitions waiting we'll need to figure out a way to unblock things.
Ideas?

(I see the new upstream version in experimental also has build
issues...)

Regards,
Andreas Henriksson
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.11.0+dfsg-8

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

Debian distribution maintenance software
pp.
Mathieu Parent  (supplier of updated samba 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: Thu, 03 Oct 2019 07:52:39 +0200
Source: samba
Architecture: source
Version: 2:4.11.0+dfsg-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Mathieu Parent 
Closes: 931734 941467
Changes:
 samba (2:4.11.0+dfsg-8) unstable; urgency=medium
 .
   * d/gbp.conf: sign-tags = True
   * Do not check smb.conf with testparm when server role=active directory 
domain
 controller (Closes: #931734)
   * Force one job during configure step with -j 1 (Closes: #941467).
 Not setting -j leads to default which is number of cpus
Checksums-Sha1:
 cfbb78f167ec069f59404e5076ecc65068dbd38e 4313 samba_4.11.0+dfsg-8.dsc
 4e02093259fad2beb8e1958e8382093f73966b96 243200 
samba_4.11.0+dfsg-8.debian.tar.xz
 ad5a826e8d3084cb387dff89a58b7ea0deb1a598 6153 
samba_4.11.0+dfsg-8_source.buildinfo
Checksums-Sha256:
 ca4020079b660e334266f59c1c493bc4e93a68af0d80e9e68b3a05a9a5b99446 4313 
samba_4.11.0+dfsg-8.dsc
 84e7dfa29e81777533389f89c62021d0d635fd7a186205cc10a19f4ab3e32d44 243200 
samba_4.11.0+dfsg-8.debian.tar.xz
 4fec3dd84826269025db003fa3905bca9ef536d5403e9a5d461a83b18effdf66 6153 
samba_4.11.0+dfsg-8_source.buildinfo
Files:
 f1fbd7c1201df39e8908c98a74a7d10a 4313 net optional samba_4.11.0+dfsg-8.dsc
 1d5ecb66cbac129f051ff92cf275b767 243200 net optional 
samba_4.11.0+dfsg-8.debian.tar.xz
 4a9385b34009fcca45eb2f5cd4553fa5 6153 net optional 
samba_4.11.0+dfsg-8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEqqWLhC6ILPQU4Lqxp8cqHHgrjD8FAl2VjSwTHHNhdGhpZXVA
ZGViaWFuLm9yZwAKCRCnxyoceCuMP0dBD/9vWwITXNsJH1zDMTR0pqEDgL1V0FcO
SDgkxHkDLbjhCymSPAGYdOwVIbuBa/KPQ4a/lWzl97QrqMUvugwWXmMUaDqHvuVd
X1+mUy9qervHXgtg13hry7OUxshPYZIj8H9T5sYRnEHi5+e5rs3Q5pis014nRHaS
7xyiPm2ZG0xCNLd2hhrtxlQvEJs09J3/d6HjZwhT/FC/MxqLZQobdIvVfpL8qAPH
xTBB/3Q7Il1VrV+UCj02Vvws3RDZ3ZU7FlHlVPOC/C4merUvE9c9o7K6/94yKHIb
0hzxfNJlnjR4E5dg3B5imcjX450XqB/OR72OIubeHZsn2Q8HMTBkr22rreG5ugPp
brME/UqxI0E605n+6Z7AeUqxrLV8XtzP/xf4rLOa5/m+2hr7v48kFB1l9YAtRr6k
t194g1VRvP8PZ3Hdyb8scvYPMi/wFCtdti+WCZPQAX0YbetPEckcdsFHDGjOcgMb
xO2zTaBBWCsiKlGcYcnjsdrfdc9SpA1A6vGBQgWvZ8KtoSwnePPjiUe3AgWRPN5p
hHmrjGtJjcxHig8UqJcTYtT+/C2ao2gSKT61k+dyjwbt+esDve2OhdisjyqtlHYR
6cit14fuiWhSKhKhHG/ccd5R3VK6ahOokqEym0ecMyZrKtBIqe32okjpVHyrQrUO
3iUTvSG+aljRKQ==
=GY8+
-END PGP SIGNATURE End Message ---