Processed: Re: Bug#941898: munin-node: all Plugins fail with "Can't drop privileges: at /usr/share/perl5/Munin/Node/Service.pm line 228."

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #941898 [munin-node] munin-node: all Plugins fail with "Can't drop 
privileges:  at /usr/share/perl5/Munin/Node/Service.pm line 228."
Severity set to 'important' from 'grave'

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

Bug#941898: munin-node: all Plugins fail with "Can't drop privileges: at /usr/share/perl5/Munin/Node/Service.pm line 228."

[Holger Levsen]

control: severity -1 important
thanks

Hi Cord,

On Mon, Oct 07, 2019 at 01:44:51PM +0200, Cord Beermann wrote:
> Severity: grave
> all Plugins produce this Error after perl 5.30 migration

the mail on d-d-a asked not to file serious (or higher) bugs for issues
due to the perl transition, until the transition is over. why did you
ignore this?

> theres an upstream issue for this: 
> https://github.com/munin-monitoring/munin/issues/1202
 
this bug report says the issue is in perl, not in munin.

I'll still keep this bug open but I'm not impressed.


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C



signature.asc
Description: PGP signature

Bug#905206: [Debian-med-packaging] Bug#905206: Seems to crash in fortran lib

[Olivier Sallou]

On 10/4/19 3:07 PM, Andreas Tille wrote:
> Hi Olivier,
>
> On Fri, Oct 04, 2019 at 02:14:02PM +0200, olivier sallou wrote:
>>> Program received signal SIGSEGV: Segmentation fault - invalid memory
>>> reference.
>> I really do not see what error could be. Maybe a fortran issue after an
>> upgrade (something that was working but not done the same way now)
>> Sorry, I have no skill to fix this kind of issue. Should be reported
>> upstream
> Since Laszlo changed his job we do not have real upstream contact.
>  
>> I see on their web site that it was superseeded by snap2 in 2015. So maybe
>> time to let it go
> Fine for me.  Where exactly did you found this? 

On https://rostlab.org/owiki/index.php/Snapfun:

"""

2015-07-23 : The Snapfun (SNAPweb service) has been superseded by an
improved version of SNAP, named SNAP2. Requests for the SNAPweb service
now point to SNAP2. If for some reason, you require the original SNAPweb
service, please contact he...@rostlab.org. More information about SNAP2
is available here.

"""


Snap2 links:

https://rostlab.org/owiki/index.php/Snap2

https://github.com/Rostlab/SNAP2


>  I only found a snap^2
> web interface.  What about the reverse depends of profnet?

this is indeed an issue, but if "old" release is not maintained anymore
and if we don't have local skills on this

This kind of issue goes beyond "maintainer" packaging, need skills in
language and software itself.

>
> Kind regards
>
>   Andreas.
>
-- 
Olivier Sallou
Univ Rennes, Inria, CNRS, IRISA
Irisa, Campus de Beaulieu
F-35042 RENNES - FRANCE
Tel: 02.99.84.71.95

gpg key id: 4096R/326D8438  (keyring.debian.org)
Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438

Bug#941913: marked as done ([Debian Buster 10.1] [arm64] [python-dev] The following packages have unmet dependencies:)

[Debian Bug Tracking System]

Your message dated Tue, 8 Oct 2019 09:59:38 +0200
with message-id <0ee01bdf-25d2-b055-01d2-fe68d0c1d...@debian.org>
and subject line Re: Bug#941913: [Debian Buster 10.1] [arm64] [python-dev] The 
following packages have unmet dependencies:
has caused the Debian Bug report #941913,
regarding [Debian Buster 10.1] [arm64] [python-dev] The following packages have 
unmet dependencies:
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.)


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

Package: python-dev
Version: 2.7.16-1
Severity: grave

Dear maintainers,

It seems there is a dependency issue when installing python-dev as 
indicated in following trace.


My target is one arm64 Pinebook Debian buster 10.1

My test conditions are ...

ansible@pinebook:~$ uname -a
Linux pinebook 5.3.3-sunxi64 #5.98.191007 SMP Mon Oct 7 02:47:01 CEST 
2019 aarch64 GNU/Linux


ansible@pinebook:~$ cat /etc/debian_version
10.1

ansible@pinebook:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#"
/etc/apt/sources.list.d/armbian_apt_v_10_buster.list:deb 
http://apt.armbian.com buster main buster-utils buster-desktop
/etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb 
http://ftp.fr.debian.org/debian buster-backports main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb 
http://ftp.debian.org/debian/ buster main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb 
http://ftp.debian.org/debian/ stretch main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb 
http://security.debian.org buster/updates main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb 
http://ftp.fr.debian.org/debian buster-updates main contrib non-free




ansible@pinebook:~$ cat /etc/apt/preferences.d/preferences_* |grep -v 
"#"  |grep -v "^$"

Package: hostapd
Pin: origin "apt.armbian.com"
Pin-Priority: -1
Package: *
Pin: origin "apt.armbian.com"
Pin-Priority: 500
Package: *
Pin: release o=Debian,l=Debian,n=buster-update
Pin-Priority: 901
Package: *
Pin: release o=Debian,l=Debian,n=buster
Pin-Priority: 900
Package: *
Pin: release o=Debian,l=Debian,n=buster-backports
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=stretch
Pin-Priority: 400
Package: *
Pin: release o=Debian,l=Debian,n=testing
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=unstable
Pin-Priority: -1
Package: dhcpcd5
Pin: release *
Pin-Priority: -1
Package: systemd
Pin: release *
Pin-Priority: -1


ansible@pinebook:~$ deborphan
ansible@pinebook:~$


ansible@pinebook:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version 
Architecture Description

+++-=-==--===

ansible@pinebook:~$ pstree -anp
init,1
  |-cron,2398
  |-sshd,2532
  |   `-sshd,2760
  |   `-sshd,2762
  |   `-bash,2763
  |   `-pstree,1015 -anp
  |-login,2590 --
  |-getty,2591 38400 tty2
  |-getty,2592 38400 tty3
  |-getty,2593 38400 tty4
  |-getty,2594 115200 ttyS0
  |-dbus-daemon,3962 --system
  |-systemd-udevd,10415
  `-syslog-ng,28841
  `-syslog-ng,28842 -p /var/run/syslog-ng.pid --no-caps


ansible@pinebook:~$ sudo apt install python-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python-dev : Depends: libpython-dev (= 2.7.16-1) but it is not going 
to be installed
  Depends: python2.7-dev (>= 2.7.16-1~) but it is not going 
to be installed
  Depends: python2-dev (= 2.7.16-1) but it is not going to 
be installed

E: Unable to correct problems, you have held broken packages.


Thanks in advance for your help
Best regards
--- End Message ---
--- Begin Message ---

On 07.10.19 16:48, Jean-Marc LACROIX wrote:

ansible@pinebook:~$ grep deb /etc/apt/sources.list.d/* |grep -v "#"
/etc/apt/sources.list.d/armbian_apt_v

Bug#941967: postgresql-11: fails to start after upgrade: EPERM on SSL snakeoil key

[Thorsten Glaser]

Package: postgresql-11
Version: 11.5-3sid2
Severity: grave
Justification: renders package unusable

[master ac9ac01] committing changes in /etc made by "apt-get --purge 
dist-upgrade"
 5 files changed, 4 insertions(+), 7 deletions(-)
E: Sub-process /usr/bin/dpkg returned an error code (1)
100|root@ci-busyapps:~ # dpkg -a --configure
Setting up postgresql-11 (11.5-3sid2) ...
Starting PostgreSQL 11 database server: mainError: 
/usr/lib/postgresql/11/bin/pg_ctl /usr/lib/postgresql/11/bin/pg_ctl start -D 
/var/lib/postgresql/11/main -l /var/log/postgresql/postgresql-11-main.log -s -o 
-c config_file="/etc/postgresql/11/main/postgresql.conf" exited with status 1: 
2019-10-08 08:43:41 UTC [2601-1] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied 2019-10-08 08:43:41 
UTC [2601-2] LOG: database system is shut down pg_ctl: could not start server 
Examine the log output. ... failed!
 failed!
invoke-rc.d: initscript postgresql, action "start" failed.
dpkg: error processing package postgresql-11 (--configure):
 installed postgresql-11 package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 postgresql-11
1|root@ci-busyapps:~ # ll /etc/ssl/private/ssl-cert-snakeoil.key
-rw-r- 1 root ssl-cert 1704 Sep 28  2015 
/etc/ssl/private/ssl-cert-snakeoil.key
root@ci-busyapps:~ # ll -d /etc/ssl/private
drwx--x--- 2 root ssl-cert 4096 Sep  6  2018 /etc/ssl/private/



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages postgresql-11 depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.29-2
ii  libgcc11:9.2.1-8
ii  libgssapi-krb5-2   1.17-6
ii  libicu63   63.2-2
ii  libldap-2.4-2  2.4.48+dfsg-1+b1
ii  libllvm9   1:9-2
ii  libpam0g   1.3.1-5
ii  libpq5 12.0-1+b1
ii  libselinux12.9-2+b2
ii  libssl1.1  1.1.1d-1
ii  libstdc++6 9.2.1-8
ii  libsystemd0242-7
ii  libuuid1   2.34-0.1
ii  libxml22.9.4+dfsg1-7+b3tarent1
ii  libxslt1.1 1.1.32-2.1
ii  locales2.29-2
ii  locales-all2.29-2
ii  postgresql-client-11   11.5-3sid2
ii  postgresql-common  207
ii  ssl-cert   1.0.39
ii  tzdata 2019c-3
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages postgresql-11 recommends:
ii  sysstat  12.0.6-1

postgresql-11 suggests no packages.

-- debconf information:
  postgresql-11/postrm_purge_data: true

Bug#941967: postgresql-11: fails to start after upgrade: EPERM on SSL snakeoil key

[Thorsten Glaser]

On Tue, 8 Oct 2019, Thorsten Glaser wrote:

> [master ac9ac01] committing changes in /etc made by "apt-get --purge 
> dist-upgrade"

FWIW, this upgrade was:

Unpacking postgresql-11 (11.5-3sid2) over (11.5-2+b1) ...

> Starting PostgreSQL 11 database server: mainError: 
> /usr/lib/postgresql/11/bin/pg_ctl /usr/lib/postgresql/11/bin/pg_ctl start -D 
> /var/lib/postgresql/11/main -l /var/log/postgresql/postgresql-11-main.log -s 
> -o -c config_file="/etc/postgresql/11/main/postgresql.conf" exited with 
> status 1: 2019-10-08 08:43:41 UTC [2601-1] FATAL: could not access private 
> key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied 
> 2019-10-08 08:43:41 UTC [2601-2] LOG: database system is shut down pg_ctl: 
> could not start server Examine the log output. ... failed!

FWIW, I never configured SSL in PostgreSQL and don’t use it.

> 1|root@ci-busyapps:~ # ll /etc/ssl/private/ssl-cert-snakeoil.key
> -rw-r- 1 root ssl-cert 1704 Sep 28  2015 
> /etc/ssl/private/ssl-cert-snakeoil.key
> root@ci-busyapps:~ # ll -d /etc/ssl/private
> drwx--x--- 2 root ssl-cert 4096 Sep  6  2018 /etc/ssl/private/

FWIW:

root@ci-busyapps:~ # id postgres
uid=110(postgres) gid=118(postgres) groups=118(postgres),111(ssl-cert)

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#885263: caja-dropbox: Depends on unmaintained pygtk

[Vlad Orlov]

Hi,

The migration to Python 3 and GI had been done in caja-dropbox 1.22.0.
I guess we can close this?

Bug#941971: raspi3-firmware: serial console output sent to bluetooth port with kernel 5.x

[Thorsten Glaser]

Package: raspi3-firmware
Version: 1.20190215-1+deb10u1
Severity: critical
Justification: breaks the whole system

I’ve set the severity high because this MIGHT break hardware,
but it it doesn’t (I don’t know enough to judge) feel free to
classify as less critical.

/etc/kernel/postinst.d/z50-raspi3-firmware contains this gem:

   90   serial="ttyAMA0,115200"
   91   kernelmajor=$(echo "${latest_kernel_basename}" | sed 's,^vmlinuz-,,g' | 
cut -d. -f 1)
   92   kernelminor=$(echo "${latest_kernel_basename}" | cut -d. -f 2)
   93   if [ $kernelmajor -ge 4 ]; then
   94 if [ $kernelminor -ge 14 ]; then
   95   # Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
   96   serial="ttyS1,115200"
   97 fi
   98   fi

The intent is to set serial to ttyAMA0 for Linux << 4.14
and to ttyS1 for Linux >= 4.14, but this fails obviously
using the old location for 5.0‥5.13, 6.0‥6.13, …

You’ll wish to use this instead:

serial="ttyAMA0,115200"
kernelmajmin=$(($(echo $latest_kernel_basename | sed -n \
's/^vmlinu.-\([0-9]*\)\.\([0-9]*\)\..*$/\1*1000+\2/p')))
if test $kernelmajmin -ge 4014; then
# Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
serial="ttyS1,115200"
fi

This must be fixed in stable, since the 5.x kernel is in
backports, or at least in unstable and available via backports
and the backports kernel must Breaks the versions prior to this fix.

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

Kernel: Linux 5.2.0-0.bpo.2-arm64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages raspi3-firmware depends on:
ii  dosfstools  4.1-2

raspi3-firmware recommends no packages.

raspi3-firmware suggests no packages.

-- Configuration Files:
/etc/default/raspi3-firmware changed:
CMA=128M


-- no debconf information

Bug#941908: gnome: unable to start gnome-shell, cursor only with no login

[Jean-Marc]

On Mon, 07 Oct 2019 14:26:28 -0500 william l-k 
 wrote:
> Thank you for your suggestions. I'll give it try and report back.

gnome-shell 3.34 released to testing yesterday solving a similar issue (see 
https://bugs.debian.org/941782).

Can you check if the problem you reported is also solved now after 
full-upgrading to the last testing version ?

And in case it is, confirm it here ?

Thank you for reporting this issue.

Regards,

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt


pgpKKS_1dY1ll.pgp
Description: PGP signature

Processed: Re: Bug#941971: raspi3-firmware: serial console output sent to bluetooth port with kernel 5.x

[Debian Bug Tracking System]

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

> clone 941971 -1
Bug #941971 [raspi3-firmware] raspi3-firmware: serial console output sent to 
bluetooth port with kernel 5.x
Bug 941971 cloned as bug 941974
> reassign -1 raspi-firmware
Bug #941974 [raspi3-firmware] raspi3-firmware: serial console output sent to 
bluetooth port with kernel 5.x
Bug reassigned from package 'raspi3-firmware' to 'raspi-firmware'.
No longer marked as found in versions raspi3-firmware/1.20190215-1+deb10u1.
Ignoring request to alter fixed versions of bug #941974 to the same values 
previously set
> found -1 1.20190819-1
Bug #941974 [raspi-firmware] raspi3-firmware: serial console output sent to 
bluetooth port with kernel 5.x
Marked as found in versions raspi-firmware/1.20190819-1.
> thanks
Stopping processing here.

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

Bug#941971: raspi3-firmware: serial console output sent to bluetooth port with kernel 5.x

[Thorsten Glaser]

clone 941971 -1
reassign -1 raspi-firmware
found -1 1.20190819-1
thanks

On Tue, 8 Oct 2019, Thorsten Glaser wrote:

> /etc/kernel/postinst.d/z50-raspi3-firmware contains this gem:

Same in sid: /etc/kernel/postinst.d/z50-raspi-firmware has:

   91   if [ "$CONSOLES" = "auto" ]; then
   92 serial="ttyAMA0,115200"
   93 kernelmajor=$(echo "${latest_kernel_basename}" | sed 's,^vmlinuz-,,g' 
| cut -d. -f 1)
   94 kernelminor=$(echo "${latest_kernel_basename}" | cut -d. -f 2)
   95 if [ $kernelmajor -ge 4 ]; then
   96   if [ $kernelminor -ge 14 ]; then
   97 # Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
   98 serial="ttyS1,115200"
   99   fi
  100 fi
  101   fi


This debugging sponsored by ⮡ tarent.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#935786: marked as done (epiphany-browser: arch:all builds fails)

[Debian Bug Tracking System]

Your message dated Tue, 8 Oct 2019 06:25:56 -0400
with message-id 

and subject line Re: epiphany-browser: arch:all builds fails
has caused the Debian Bug report #935786,
regarding epiphany-browser: arch:all builds fails
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.)


-- 
935786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: epiphany-browser
Version: 3.33.91-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

epiphany-browser/experimental fails during the arch:all build:

https://buildd.debian.org/status/fetch.php?pkg=epiphany-browser&arch=all&ver=3.33.91-1&stamp=1566403443&raw=0

10/11 String test FAIL 0.07 s (killed by signal 
5 SIGTRAP)

--- command ---
GSETTINGS_BACKEND='memory' 
GSETTINGS_SCHEMA_DIR='/<>/obj-x86_64-linux-gnu/data' 
G_TEST_SRCDIR='/<>/tests' 
G_TEST_BUILDDIR='/<>/obj-x86_64-linux-gnu/tests' 
/<>/obj-x86_64-linux-gnu/tests/test-ephy-string
--- stdout ---
# random seed: R02S27f41fd9039356b78c1df4b50aae
--- stderr ---
Unable to init server: Could not connect: Connection refused

(/<>/obj-x86_64-linux-gnu/tests/test-ephy-string:11345): 
Gtk-WARNING **: 16:03:55.824: cannot open display: :99
---


Andreas
--- End Message ---
--- Begin Message ---
Version: 3.34.0-1

epiphany builds fine now.
https://buildd.debian.org/status/package.php?p=epiphany-browser

Thanks,
Jeremy--- End Message ---

Bug#885263: marked as done (caja-dropbox: Depends on unmaintained pygtk)

[Debian Bug Tracking System]

Your message dated Tue, 8 Oct 2019 06:27:49 -0400
with message-id 

and subject line Re: caja-dropbox: Depends on unmaintained pygtk
has caused the Debian Bug report #885263,
regarding caja-dropbox: Depends on unmaintained pygtk
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.)


-- 
885263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caja-dropbox
Version: 1.18.0-2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 1.22.1-1--- End Message ---

Bug#941389: marked as done (virt-manager: Missing dependency from gir1.2-gtksource-4)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 10:52:03 +
with message-id 
and subject line Bug#941249: fixed in virt-manager 1:2.2.1-2
has caused the Debian Bug report #941249,
regarding virt-manager: Missing dependency from gir1.2-gtksource-4
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.)


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

Dear Maintainer,

After upgrading virt-manager to the latest version, once started it is unable 
to open virtual machine details/console pop windows (as well as some other pop 
windows like connection settings etc).
Installing gir1.2-gtksource-4 fixes the issue but, it is not in the current 
dependencies of virt-manager (which I believe it must be).

Thank you.


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

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

Versions of packages virt-manager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gir1.2-gtk-3.0   3.24.11-1
ii  gir1.2-gtk-vnc-2.0   0.9.0-1.1+b1
ii  gir1.2-libosinfo-1.0 1.6.0-1
ii  gir1.2-libvirt-glib-1.0  1.0.0-1
ii  gir1.2-vte-2.91  0.58.0-1
ii  librsvg2-common  2.44.14-1
ii  python3  3.7.3-1
ii  python3-dbus 1.2.12-1
ii  python3-gi   3.34.0-1
ii  python3-gi-cairo 3.34.0-1
ii  python3-libvirt  5.0.0-1
ii  virtinst 1:2.2.1-1

Versions of packages virt-manager recommends:
ii  gir1.2-spiceclientglib-2.0  0.37-1
ii  gir1.2-spiceclientgtk-3.0   0.37-1
ii  libvirt-daemon-system   5.6.0-2

Versions of packages virt-manager suggests:
pn  gir1.2-secret-1  
pn  gnome-keyring
pn  python3-guestfs  
ii  ssh-askpass  1:1.2.4.1-10+b1
pn  virt-viewer  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: virt-manager
Source-Version: 1:2.2.1-2

We believe that the bug you reported is fixed in the latest version of
virt-manager, 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.
Guido Günther  (supplier of updated virt-manager 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: Tue, 08 Oct 2019 12:02:30 +0200
Source: virt-manager
Binary: virt-manager virtinst
Architecture: source all
Version: 1:2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Libvirt Maintainers 

Changed-By: Guido Günther 
Description:
 virt-manager - desktop application for managing virtual machines
 virtinst   - Programs to create and clone virtual machines
Closes: 941249
Changes:
 virt-manager (1:2.2.1-2) unstable; urgency=medium
 .
   * d/control: wrap and sort
   * d/control: Depend on gir1.2-gtksource-4 (Closes: #941249)
Checksums-Sha1:
 a13da2cd5a1ba708a1a4fb47a192db13f523ab60 2296 virt-manager_2.2.1-2.dsc
 2c8f14d83c07c8d832d6f437bb4eccc97d260ac3 14224 
virt-manager_2.2.1-2.debian.tar.xz
 97f4a886cc771a3aca1d473f39cc766e2e12c5ad 878704 virt-manager_2.2.1-2_all.deb
 95fc4c92f59a7ee85695b04b79e3899cf544ab46 11640 
virt-manager_2.2.1-2_amd64.buildinfo
 aeda4752266bb0834d5320510c9b525d82ce8867 192264 virtinst_2.2.1-2_all.deb
Checksums-Sha256:
 8791089c1e553d96d71b22f71d31b6bae14e5b808f749bc9ddcc6033f5d32c18 2296 
virt-manager_2.2.1-2.dsc
 5b41739f407b7b8210fda01900c9acc491edaa7b9d8ff46849e23d65c23046af 14224 
virt-manager_2.2.1-2.debian.tar.xz
 5f3cb3bc9069a7aad151b4f711b48fbdd2f978c3225be83bad1a7209c83666cf 878704 
v

Bug#941249: marked as done (virt-manager: Can not open detail of connection and detail or console of a VM)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 10:52:03 +
with message-id 
and subject line Bug#941249: fixed in virt-manager 1:2.2.1-2
has caused the Debian Bug report #941249,
regarding virt-manager: Can not open detail of connection and detail or console 
of a VM
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.)


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

Dear Maintainer,

After upgrade from virt-manager 2.0.0 to 2.2.1, I can not open any more detail 
of connection, or detail/console of a VM, no window is open when I click or if 
I select Open in the menu.

Here's the output of virt-manager --debug --no-fork:

[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (cli:208) Launched with 
command line: /usr/share/virt-manager/virt-manager --debug --no-fork
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:223) 
virt-manager version: 2.2.1
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:224) 
virtManager import: 

(virt-manager:2944): dbind-WARNING **: 07:56:10.508: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-0YN5eotkNt: Connexion 
refusée
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:274) 
PyGObject version: 3.34.0
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (virt-manager:278) GTK 
version: 3.24.11
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (systray:213) Showing 
systray: False
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (inspection:41) python 
guestfs is not installed
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:116) Loading 
stored URIs:
qemu+ssh://shelleu@10.10.43.16/system  
qemu:///system
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:537) processing 
cli command uri= show_window=manager domain=
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:539) No cli 
action requested, launching default window
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (manager:184) Showing 
manager
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:391) window 
counter incremented to 1
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (engine:285) Initial 
gtkapplication activated
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:533) 
conn=qemu:///system changed to state=Connexion
[ven., 27 sept. 2019 07:56:10 virt-manager 2944] DEBUG (connection:946) 
Scheduling background open thread for qemu:///system
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:986) libvirt 
version=5006000
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:988) daemon 
version=5006000
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:989) conn 
version=4001000
[ven., 27 sept. 2019 07:56:11 virt-manager 2944] DEBUG (connection:991) 
qemu:///system capabilities:


  
eef59000-6784---

  x86_64
  Westmere
  Intel
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  


  
  
  



  
  
tcp
rdma
  


  

  3959980
  989995
  0
  0
  

  
  




  

  


  


  none
  0


  dac
  0
  +101:+112
  +101:+112

  

  
hvm

  64
  /usr/bin/qemu-system-alpha
  clipper
  


  
  
  

  

  
hvm

  32
  /usr/bin/qemu-system-arm
  integratorcp
  versatileab
  smdkc210
  nuri
  palmetto-bmc
  microbit
  mainstone
  canon-a1100
  terrier
  n800
  verdex
  kzm
  versatilepb
  midway
  virt-2.7
  emcraft-sf2
  mcimx7d-sabre
  highbank
  imx25-pdk
  n810
  virt-2.11
  realview-pbx-a9
  tosa
  sx1-v1
  swift-bmc
  mps2-an511
  musca-a
  realview-pb-a8
  sabrelite
  akita
  cubieboard
  virt-2.9
  xilinx-zynq-a9
  virt-3.1
  vexpress-a15
  virt-4.1
  virt

Bug#940564: [lbcb-sci/racon] Incompatible with latest spoa release (#6)

[Andreas Tille]

On Tue, Oct 08, 2019 at 03:51:47AM -0700, Robert Vaser wrote:
> Hi Andreas, yes I have a plan how to deal with it but I am not available for 
> a week or more. Will let you know.
Thanks a lot.  Just take your time until end of October since I'll be not 
available until then. ;-)

Bug#936579: marked as done (gamin: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 11:19:33 +
with message-id 
and subject line Bug#936579: fixed in gamin 0.1.10-6
has caused the Debian Bug report #936579,
regarding gamin: 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.)


-- 
936579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gamin
Version: 0.1.10-5
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:gamin

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: gamin
Source-Version: 0.1.10-6

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gamin package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 07 Oct 2019 07:03:38 -0400
Source: gamin
Architecture: source
Version: 0.1.10-6
Distribution: unstable
Urgency: medium
Maintainer: Michael Banck 
Changed-By: Jeremy Bicha 
Closes: 737108 936579
Changes:
 gamin (0.1.10-6) unstable; urgency=medium
 .
   * Drop unused python-gamin package (Closes: #936579, #737108)
   * Switch from cdbs to debhelper
   * Build-Depend on debhelper-compat 12 and drop debian/compat
   * Add Vcs fields
Checksums-Sha1:
 d51458326a4195722e54e6558318845ff9539dba 2093 gamin_0.1.10-6.dsc
 c816dc5b8e9086c63781d107bfd7cbf8a5a9d83f 8772 gamin_0.1.10-6.debian.tar.xz
 99a5059ebddb71b2eeef6aec2fdf2051fc7f6d25 11005 gamin_0.1.10-6_source.buildinfo
Checksums-Sha256:
 36ec46dc100991ef2b373501e92b2c62403bb8d6caec6f85bfc702ff21de8b3a 2093 
gamin_0.1.10-6.dsc
 a70339f18b78b9d3ca0ed5b66a464dcfe2d3fd124e8326a23c456e184d3e648e 8772 
gamin_0.1.10-6.debian.tar.xz
 756b389b641b33b4d751475ed04eb1572d4742c3c858a290ca02bf42fedb25f0 11005 
gamin_0.1.10-6_source.buildinfo
Files:

Processed: re: nototools: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> severity 937162 serious
Bug #937162 [src:nototools] nototools: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#941934: marked as done (libnbd: FTBFS on several architectures)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 14:39:22 +0200
with message-id <87ftk3s96t@msgid.hilluzination.de>
and subject line Re: Bug#941934: libnbd: FTBFS on several architectures
has caused the Debian Bug report #941934,
regarding libnbd: FTBFS on several architectures
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.)


-- 
941934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnbd
Version: 1.0.2-1
Tags: ftbfs
Severity: serious
Contol: affects -1 nbdkit
Control: block 935737 with -1

This package failed to build on arm64, armel, armhf, mips64el and mipsel,
mostly due to test failures. 1.0.1-1 built successfully on some of those,
so this is preventing testing migration.

It looks like libnbd has never built on armel and armhf, so nbdkit is
currently unbuildable on those architectures due to missing libnbd-dev.
This interferes with the ongoing Perl 5.30 transition as nbdkit cannot be
rebuilt against the new perl on armel and armhf. Marking this as blocker
for the transition.

As always, build logs can be found at

  https://buildd.debian.org/status/package.php?p=libnbd&suite=unstable

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
control: fixed -1 1.0.2-5

After tweaking the build system and adding a timeout patch for tests on
apparently slowwer or overloaded buildds (arm*, mips*), the package is
now built on all release architectures.

Cheers,
-Hilko--- End Message ---

Bug#941982: libsys-info-base-perl: missing file Sys/Info.pm

[Vincent Lefevre]

Package: libsys-info-base-perl
Version: 0.7807-2
Severity: grave
Justification: renders package unusable

I wanted to get the number of CPUs (see Sys::Info::Device::CPU man page),
but this fails at "use Sys::Info;":

$ perl -MSys::Info -e ''
Can't locate Sys/Info.pm in @INC (you may need to install the Sys::Info module)
[...]

There is no such issue with upstream's module version 0.78 (at least
before perl 5.30). (I haven't tested the latest version yet due to a
bug that occurs under Debian with the latest version of some
dependency.)

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libsys-info-base-perl depends on:
ii  perl  5.30.0-5

libsys-info-base-perl recommends no packages.

libsys-info-base-perl suggests no packages.

-- no debconf information

Bug#941982: libsys-info-base-perl: missing file Sys/Info.pm

[gregor herrmann]

On Tue, 08 Oct 2019 15:47:50 +0200, Vincent Lefevre wrote:

> Package: libsys-info-base-perl
> Version: 0.7807-2
> Severity: grave
> Justification: renders package unusable
> 
> I wanted to get the number of CPUs (see Sys::Info::Device::CPU man page),
> but this fails at "use Sys::Info;":
> 
> $ perl -MSys::Info -e ''
> Can't locate Sys/Info.pm in @INC (you may need to install the Sys::Info 
> module)
> [...]
> 
> There is no such issue with upstream's module version 0.78

Note that libsys-info-base-perl is the package for the CPAN
distribution https://metacpan.org/release/Sys-Info-Base which does
not contain Sys::Info.

Sys::Info is in https://metacpan.org/release/Sys-Info which
apparently is currently not available in Debian; maybe this
should be changed … Interestingly the metadata of Sys-Info-Base don't
refer to Sys::Info, just some examples in the documentation.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   BOFH excuse #153:  Big to little endian conversion error 

Processed: reassign 941967 to postgresql-common, forcibly merging 941967 941948

[Debian Bug Tracking System]

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

> reassign 941967 postgresql-common
Bug #941967 [postgresql-11] postgresql-11: fails to start after upgrade: EPERM 
on SSL snakeoil key
Bug reassigned from package 'postgresql-11' to 'postgresql-common'.
No longer marked as found in versions postgresql-11/11.5-3sid2.
Ignoring request to alter fixed versions of bug #941967 to the same values 
previously set
> forcemerge 941967 941948
Bug #941967 [postgresql-common] postgresql-11: fails to start after upgrade: 
EPERM on SSL snakeoil key
Bug #941973 [postgresql-common] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Severity set to 'grave' from 'important'
Severity set to 'grave' from 'important'
Bug #941967 [postgresql-common] postgresql-11: fails to start after upgrade: 
EPERM on SSL snakeoil key
Marked as found in versions postgresql-common/207.
Bug #941948 [postgresql-common] postgresql-common: postgresql fails to start 
via systemd
Merged 941948 941967 941973
> thanks
Stopping processing here.

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

Bug#874880: [freemedforms-project] Future Qt4 removal from Buster

[Andreas Tille]

Hi again,

I'm sorry to repeat myself but please pretty please help finding some
solution.  Freemedform-project is about to be removed from Debian and
I see no way to prevent this.

Kind regards

  Andreas.

On Sat, Sep 21, 2019 at 08:45:05AM +0200, Andreas Tille wrote:
> Hi Eric,
> 
> any idea when you might find some time to comment on this build issue.
> Its really urgent now and since we are basically two years in an
> unchanged situation that the package does not build I have no idea
> what to tell the release team.
> 
> Kind regards
> 
>Andreas.
> 
> On Fri, Sep 06, 2019 at 11:41:33AM +0200, Andreas Tille wrote:
> > Hi,
> > 
> > thanks to a patch by Michael Crusoe I'm a bit further now but there are
> > remaining errors.  I have no idea about C++/Qt and thus need to ask for
> > help.  Eric, are you up to safe your package inside Debian?
> > 
> > ...
> > g++ -c -pipe -g -O2 -fdebug-prefix-map=/build/freemedforms-project-1.0.0=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> > -D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -fPIC -DFREEMEDFORMS -   
> > DDRUGS_DATABASE_VERSION=0x000804 -DWITH_EPISODE_REMOVAL 
> > -DWITH_CHEQUE_PRINTING -DWITH_FRENCH_FSP -DWITH_FRENCH_HPRIM_INTEGRATOR 
> > -DFULLAPPLICATION_BUILD -DBINARY_NAME="\"DataPackUtils\"" - 
> > DBUILD_PATH_POSTFIXE="\"FreeMedForms\"" 
> > -DPACKAGE_VERSION="\"1.0.0\"" 
> > -DSOURCES_ROOT_PATH="\"/build/freemedforms-project-1.0.0\"" 
> > -DLINUX_INTEGRATED -DLINUX_QT_PATH="\"/usr/lib/x86_64-linux-gnu\"" -
> >   DLINUX_QT_PLUGINS_PATH="\"/usr/lib/x86_64-linux-gnu/qt5/plugins\"" 
> > -DLIBRARY_BASENAME="\"lib/x86_64-linux-gnu\"" 
> > -DLINUX_PLUGIN_PATH="\"/usr//lib/x86_64-linux-gnu/DataPackUtils\"" 
> > -DGIT_REVISION_HASH="\"DEBR1.0. 0-1\"" -DQT_NO_CAST_TO_ASCII 
> > -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION -DRELEASE 
> > -DQT_DISABLE_DEPRECATED_BEFORE=0x040900 -DDATAPACKUTILS_LIBRARY 
> > -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -   DQT_WIDGETS_LIB 
> > -DQT_GUI_LIB -DQT_CONCURRENT_LIB -DQT_SQL_LIB -DQT_XML_LIB -DQT_NETWORK_LIB 
> > -DQT_CORE_LIB -I. -I/build/freemedforms-project-1.0.0/plugins 
> > -I/build/freemedforms-project-1.0.0/libs -I/build/
> > freemedforms-project-1.0.0/contrib 
> > -I/build/freemedforms-project-1.0.0/contrib/quazip -isystem 
> > /usr/include/x86_64-linux-gnu/qt5 -isystem 
> > /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem /usr/include/x86_64- 
> > linux-gnu/qt5/QtPrintSupport -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/QtConcurrent -isystem /usr/include/   
> > x86_64-linux-gnu/qt5/QtSql -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml 
> > -isystem /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> > /usr/include/x86_64-linux-gnu/qt5/QtCore -I/build/freemedforms-project-1. 
> > 0.0/build/Qt5_linux-gpp/FreeMedForms/DataPackUtils/.moc -isystem 
> > /usr/include/libdrm 
> > -I/build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/.ui 
> > -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
> > /build/freemedforms-project-1.0.0/build/Qt5_linux-gpp/FreeMedForms/DataPackUtils/.obj/unix/packservercreator.o
> >  servercreation/packservercreator.cpp
> > servercreation/servercreationwidget.cpp: In member function 'void 
> > DataPack::Internal::ServerCreationWidgetPrivate::createActions()':
> > servercreation/servercreationwidget.cpp:97:39: error: invalid use of 
> > incomplete type 'class QAction'
> >97 | aGroupByServer = new QAction(q);
> >   |   ^
> > In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
> >  from servercreation/servercreationwidget.h:18,
> >  from servercreation/servercreationwidget.cpp:28:
> > /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward 
> > declaration of 'class QAction'
> >68 | class QAction;
> >   |   ^~~
> > servercreation/servercreationwidget.cpp:98:38: error: invalid use of 
> > incomplete type 'class QAction'
> >98 | aGroupByQueue = new QAction(q);
> >   |  ^
> > In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
> >  from servercreation/servercreationwidget.h:18,
> >  from servercreation/servercreationwidget.cpp:28:
> > /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:68:7: note: forward 
> > declaration of 'class QAction'
> >68 | class QAction;
> >   |   ^~~
> > servercreation/servercreationwidget.cpp: In member function 'void 
> > DataPack::ServerCreationWidget::retranslate()':
> > servercreation/servercreationwidget.cpp:258:22: error: invalid use of 
> > incomplete type 'class QAction'
> >   258 | d->aGroupByServer->setText(tr("Group by server"));
> >   |  

Bug#941948: postgresql-common: postgresql fails to start via systemd

[Christoph Berg]

Control: clone -1 -2
Control: reassign -2 perl 5.30.0-5
Control: severity -2 grave
Control: retitle -2 Setting groups via $) is broken in perl 5.30
Control: forwarded -2 https://rt.perl.org/Ticket/Display.html?id=134169
Control: block -1 -2

Re: C. Dominik Bodi 2019-10-07 
<157048138766.24767.6435696852589087342.report...@odysseus.dominikbodi.de>
> Package: postgresql-common
> Version: 207
> Severity: important
> 
> when trying to start service postgresql@12-main (the same with 11)
> service using systemctl start postgresql@12-main
> starting the server fails, the log file says it failed to read
> /etc/ssl/private/ssl-cert-snakeoil.key (no read permissions)
> ls -l that file says (dates redacted):
> -rw-r- 1 root ssl-cert 1704 MMM  DD   ssl-cert-snakeoil.key
> ls -l the directoy says (dates redacted):
> drwxr-x--- 2 root ssl-cert   323 MMM DD   private
> 
> The user postgres is member of group ssl-cert.

That's a perl 5.30 bug:

https://rt.perl.org/Ticket/Display.html?id=134169

Christoph

Processed (with 6 errors): Re: Bug#941948: postgresql-common: postgresql fails to start via systemd

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #941948 [postgresql-common] postgresql-common: postgresql fails to start 
via systemd
Bug #941967 [postgresql-common] postgresql-11: fails to start after upgrade: 
EPERM on SSL snakeoil key
Bug #941973 [postgresql-common] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Failed to clone 941948: Bug is marked as being merged with others. Use an 
existing clone.

> reassign -2 perl 5.30.0-5
Failed to clear fixed versions and reopen on -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_package did not pass regex check
.

> severity -2 grave
Failed to set severity of Bug -2 to grave: The 'bug' parameter ("-2") to 
Debbugs::Control::set_severity did not pass regex check
.

> retitle -2 Setting groups via $) is broken in perl 5.30
Failed to set the title of -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_title did not pass regex check
.

> forwarded -2 https://rt.perl.org/Ticket/Display.html?id=134169
Failed to set the forwarded-to-address of -2: The 'bug' parameter ("-2") to 
Debbugs::Control::set_forwarded did not pass regex check
.

> block -1 -2
Unknown command or malformed arguments to command.


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

Bug#941967: reassign 941967 to postgresql-common, forcibly merging 941967 941948

[Thorsten Glaser]

On Tue, 8 Oct 2019, Christoph Berg wrote:

> reassign 941967 postgresql-common 

Interestingly enough, the last postgresql-common update was
a week ago and did not introduce any errors (unless it’s the
combination of buggy postgresql-common and newer postgresql-11
of course).

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Bug#941948: postgresql-common: postgresql fails to start via systemd

[Thorsten Glaser]

On Tue, 8 Oct 2019, Andreas Kurth wrote:

> A better fix is to add
> 
>   User=postgres
> 
> to the [Service] section of your systemd unit file. This should be

Note that systemd-less operation with sysvinit is also broken,
so that alone is no fix.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**

Processed: reassign 941948 to perl, affects 941948, affects 941948, affects 941948

[Debian Bug Tracking System]

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

> reassign 941948 perl 5.30.0-5
Bug #941948 [postgresql-common] postgresql-common: postgresql fails to start 
via systemd
Bug #941967 [postgresql-common] postgresql-11: fails to start after upgrade: 
EPERM on SSL snakeoil key
Bug #941973 [postgresql-common] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Bug reassigned from package 'postgresql-common' to 'perl'.
Bug reassigned from package 'postgresql-common' to 'perl'.
Bug reassigned from package 'postgresql-common' to 'perl'.
No longer marked as found in versions postgresql-common/207.
No longer marked as found in versions postgresql-common/207.
No longer marked as found in versions postgresql-common/207.
Ignoring request to alter fixed versions of bug #941948 to the same values 
previously set
Ignoring request to alter fixed versions of bug #941967 to the same values 
previously set
Ignoring request to alter fixed versions of bug #941973 to the same values 
previously set
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL 
snakeoil key
Bug #941973 [perl] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Marked as found in versions perl/5.30.0-5.
Marked as found in versions perl/5.30.0-5.
Marked as found in versions perl/5.30.0-5.
> affects 941948 postgresql-common
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL 
snakeoil key
Bug #941973 [perl] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Added indication that 941948 affects postgresql-common
Added indication that 941967 affects postgresql-common
Added indication that 941973 affects postgresql-common
> affects 941948 postgresql-11
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL 
snakeoil key
Bug #941973 [perl] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Added indication that 941948 affects postgresql-11
Added indication that 941967 affects postgresql-11
Added indication that 941973 affects postgresql-11
> affects 941948 postgresql-12
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL 
snakeoil key
Bug #941973 [perl] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Added indication that 941948 affects postgresql-12
Added indication that 941967 affects postgresql-12
Added indication that 941973 affects postgresql-12
> thanks
Stopping processing here.

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

Processed: bug 941948 is forwarded to https://rt.perl.org/Ticket/Display.html?id=134169

[Debian Bug Tracking System]

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

> forwarded 941948 https://rt.perl.org/Ticket/Display.html?id=134169
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL 
snakeoil key
Bug #941973 [perl] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Set Bug forwarded-to-address to 
'https://rt.perl.org/Ticket/Display.html?id=134169'.
Set Bug forwarded-to-address to 
'https://rt.perl.org/Ticket/Display.html?id=134169'.
Set Bug forwarded-to-address to 
'https://rt.perl.org/Ticket/Display.html?id=134169'.
> thanks
Stopping processing here.

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

Bug#941984: backintime: files under the GFDL

[Sean Whitton]

Source: backintime
Version: 1.1.24-0.1
Severity: serious

Dear maintainer,

Files in the source package matching qt4/docbook/en/* look to be under
the GFDL, not the GPL, as implied by d/copyright.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#905206: Status of rostlab software in Debian (Was: Bug#905206: Seems to crash in fortran lib)

[Andreas Tille]

Hello,

back in 2009 Laszlo Kajan did quite some effort to package several
projects from rostlab.org for official Debian.  There was a very good
cooperation between RostLab and Debian - mediated by Laszlo who was
introducing other members (who probably left Rostlab meanwhile to find
other jobs).

Since Laszlo moved away from Munich he lost contact to Rostlab and had
also no time to keep on maintaining the existing Software inside Debian.
So the Debian Med team took over the maintenance.  The packages were
regularly updated to latest versions released by Rostlab as well as to
the latest packaging standards in Debian.  This also included continuous
integration tests to verify the functionality of the programs.

It now turned out that one of the tests for profnet failed (you might
like to read the full story and the effort we did to track the issue
down in the according bug report https://bugs.debian.org/905206 ).
The reason seems to be inside a FORTRAN module
(see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905206#69 ).
Unfortunately there is nobody in the team who can even decide whether
this might be caused by a broken gfortran compiler or whether the code
is broken.  Thus we can not guarantee the proper functionality of the
code for our users without help.

As you can read below Olivier Sallou from Debian Med team found reasons
to assume that the software stack based on profnet is superseeded
anyway.  It would be nice if you could confirm this.  In this case we
could stop our desperate efforts to get profnet fully functional again.

If you consider that packaging SNAP2 is more fruitful - may be other
software you would like to see inside Debian - we would rather
concentrate on this and would be happy to package your latest and
greatest code.

In general we would love to refresh the closer relation between RostLab
and Debian since Laszlo made us believe this would be quite fruitfully.
May be you would like to send a member of your lab to our next Sprint
which will happen somewhen in the beginning of next year in Berlin (to
be announced).  Such kind of sprint once was the entry point for Laszlo
into Debian.  Inside the Debian Med team we have quite a record for
teaching about Debian packaging which could be quite interesting for
you.

I'd be really happy to revive the connection again.

Kind regards

   Andreas.

On Tue, Oct 08, 2019 at 09:26:13AM +0200, Olivier Sallou wrote:
> 
> On 10/4/19 3:07 PM, Andreas Tille wrote:
> > Hi Olivier,
> >
> > On Fri, Oct 04, 2019 at 02:14:02PM +0200, olivier sallou wrote:
> >>> Program received signal SIGSEGV: Segmentation fault - invalid memory
> >>> reference.
> >> I really do not see what error could be. Maybe a fortran issue after an
> >> upgrade (something that was working but not done the same way now)
> >> Sorry, I have no skill to fix this kind of issue. Should be reported
> >> upstream
> > Since Laszlo changed his job we do not have real upstream contact.
> >  
> >> I see on their web site that it was superseeded by snap2 in 2015. So maybe
> >> time to let it go
> > Fine for me.  Where exactly did you found this? 
> 
> On https://rostlab.org/owiki/index.php/Snapfun:
> 
> """
> 
> 2015-07-23 : The Snapfun (SNAPweb service) has been superseded by an
> improved version of SNAP, named SNAP2. Requests for the SNAPweb service
> now point to SNAP2. If for some reason, you require the original SNAPweb
> service, please contact he...@rostlab.org. More information about SNAP2
> is available here.
> 
> """
> 
> 
> Snap2 links:
> 
> https://rostlab.org/owiki/index.php/Snap2
> 
> https://github.com/Rostlab/SNAP2
> 
> 
> >  I only found a snap^2
> > web interface.  What about the reverse depends of profnet?
> 
> this is indeed an issue, but if "old" release is not maintained anymore
> and if we don't have local skills on this
> 
> This kind of issue goes beyond "maintainer" packaging, need skills in
> language and software itself.
> 
> >
> > Kind regards
> >
> >   Andreas.
> >
> -- 
> Olivier Sallou
> Univ Rennes, Inria, CNRS, IRISA
> Irisa, Campus de Beaulieu
> F-35042 RENNES - FRANCE
> Tel: 02.99.84.71.95
> 
> gpg key id: 4096R/326D8438  (keyring.debian.org)
> Key fingerprint = 5FB4 6F83 D3B9 5204 6335  D26D 78DC 68DB 326D 8438
> 
> 

-- 
http://fam-tille.de

Bug#941985: perl 5.30.0 - Unable to set supplementary group IDs

[Dagfinn Ilmari Mannsåker]

Package: perl
Version: 5.30.0-5
Forwarded: https://rt.perl.org/Public/Bug/Display.html?id=134169
Severity: serious

A regression in perl 5.30.0 breaks setting supplementary groups by
assigning a space-separated string to the $) variable.  This breaks
postgresql-common, which relies on taking on all the supplementary
groups of the postgres user (specifically ssl-cert, to be able to read
SSL certificates).

This has been fixed in blead¹, and proposed for backporting to the 5.30
branch².

[1]: 
http://perl5.git.perl.org/perl.git/commitdiff/79e302e6c3f815bf4cb72a5bacc3012595970db9
[2]: 
https://perl5.git.perl.org/perl.git/commitdiff/37615aed2d5ce7dd5e254533f5235478f3378422

- ilmari
-- 
"The surreality of the universe tends towards a maximum" -- Skud's Law
"Never formulate a law or axiom that you're not prepared to live with
 the consequences of."  -- Skud's Meta-Law

Processed: slic3r-prusa: fails to build on arm*

[Debian Bug Tracking System]

Processing control commands:

> block 935737 with -1
Bug #935737 [release.debian.org] transition: perl
935737 was blocked by: 941920 941915 941933 941917 941919 941935 941926 941934
935737 was not blocking any bugs.
Added blocking bug(s) of 935737: 941989

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

Bug#941989: slic3r-prusa: fails to build on arm*

[gregor herrmann]

Source: slic3r-prusa
Version: 1.41.2+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: block 935737 with -1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

During the perl transition we noticed that slic3r-prusa failed to
build on the arm* architectures (and alpha):
https://buildd.debian.org/status/package.php?p=slic3r-prusa

In fact, 1.41.* has never built on any of them:
https://buildd.debian.org/status/logs.php?pkg=slic3r-prusa


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2csKNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbTEA/+INFvRjbntxXOCMPkyH11sILNqhqBuEnIICEUMrA54D/Qtg2g0PzMOS30
ztmaLDY3B88LP3Mz6TqwezlXRMUZs7RB6tWIgDiUEEHkheui7PFhRuigNXdCWPRr
og1t0G3SaCF+ZkmyDHn/pv2Fi/HYXKDQaoF/xz7Sdm40QUjcLsKqQ+/fpxi7QOWA
2HuJVl+9ZIyL0dAoZKm6MfPWg4pdGymdaH7bxwnWwBIrrao69PYc6k1ZVKq8EVNF
9K7XoBqvKxKjxnqvtAfwOcSsPmhscBoCXfgygSYJo4UnalK+8L1sEEObXzQ0geOB
OvL8AMpw7Dz+2hYnrkpiGPyrO2ElzWs/9tp7X10Zu0ezSQst4K+IOTQwUTlH21X+
ZH8qlwsJAwiGtNA16GUcDjvNw/yIDLaNjaU6LEY4hzzFsUNgjy4eMThBey/hhxvs
u//A4vpr5sQEPwJ1gyra5C1CS0HUr0MK4usfG2IIiQKGCUEiCrLJqzLG859oJJ+3
oVKNVWF+tb7bY6UzUCu6W8zZUHzMW8YHEtk2w3/ZOSt5igww9ZK5+4MNKZCnzvZg
QRLTYMKFiFH4pKVXBHSEs900aS7VqpTyAD7SrW0zbCNmc3OpuU7TkVqPOymRKUrn
fcbWzcknpouDI2nGxZDSWOSZvcKwmEm03+rFH/bAOMYhaEmddRs=
=a8zO
-END PGP SIGNATURE-

Bug#941650: marked as done (python-iptables ftbfs in unstable: segfault)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 17:06:48 +
with message-id 
and subject line Bug#941650: fixed in python3.7 3.7.5~rc1-2
has caused the Debian Bug report #941650,
regarding python-iptables ftbfs in unstable: segfault
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.)


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

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
--- End Message ---
--- Begin Message ---
Source: python3.7
Source-Version: 3.7.5~rc1-2

We believe that the bug you reported is fixed in the latest version of
python3.7, 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.
Matthias Klose  (supplier of updated python3.7 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: Tue, 08 Oct 2019 18:47:45 +0200
Source: python3.7
Architecture: source
Version: 3.7.5~rc1-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 941650
Changes:
 python3.7 (3.7.5~rc1-2) unstable; urgency=medium
 .
   * Apply proposed patch for issue 38368. LP: #1847036. Closes: #941650.
Checksums-Sha1:
 e29ac756e857f54bb61dca6fc947359168910bee 3447 python3.7_3.7.5~rc1-2.dsc
 08e6addc15f6396d8fce7281bce9c46f609d7e60 213648 
python3.7_3.7.5~rc1-2.debian.tar.xz
 110266aa834349df578a932dd41f69b8d0561f4c 9759 
python3.7_3.7.5~rc1-2_source.buildinfo
Checksums-Sha256:
 59776ecf138fe9f50034a88bb05e2e7b8a55f3278903780c16587291843df4b3 3447 
python3.7_3.7.5~rc1-2.dsc
 04e6372b036ed26bcdee4a4ab44624b253832430f1b035325dd8174585c40190 213648 
python3.7_3.7.5~rc1-2.debian.tar.xz
 51bc8b7c61e48ffd28a2c0959d55190e8d4265b6e0c2bd1981ad03d951a25c45 9759 
python3.7_3.7.5~rc1-2_source.buildinfo
Files:
 90ca248e01fec85a20f20888ae6a8488 3447 python optional python3.7_3.7.5~rc1-2.dsc
 f3f99061e8ce5c283223906bd773989c 213648 python optional 
python3.7_3.7.5~rc1-2.debian.tar.xz
 8914929505fa80bffb9f9aa8d5f3eddf 9759 python optional 
python3.7_3.7.5~rc1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl2cvjQQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9ff8D/9e2O+kW5jAte1u44Ay/5RAWi0bjuA0qtcr
ztfILHbG6ezvtS8rHV70vnp/cz3pXUjjYXKKLXQETBEzsp+u3K+1eo3XxB/peVk6
aRpRiBI27w2SNONRhjmxbxvWd/B/N7mxcPvTYw7quonlskGNPpYgG9kAqgKX+ITA
9WixnInFnep0+EkhVc7EbJV/DgvATlg3ACvNuUEBRv0u6AgrUB/F4oJjiD7NZwyA
7VxBWsGWrnfMle0WgomfjNIdv/TYGPnPGyL5DddOKuJI2nbWcI7NUvD9qHuyVfv4
CF8i50zyP/7nJLT85mN+NWBN7M6duSSAQJzFvPKgtFObbF82uso9nARDzB8btrsN
RDMy8pd4PnFobRRAyjoM4dM8ti1oZug2nfKLJeKH7MxCudZ+Iea2V87jQ+kREG1z
lphydIhcQPuBreeKnZ+gDxtb2ya3msdEFbd/l7WCtXZivC4fAGjl9bYxpT3pFQEa
cZJ9fO7Aqi3JOY4WTlv3MMHKluYaLNraOwwW20pfebCWf/fWJTAZNfdo03Od/7BS
w5xY3Ngxm+5RZ/gUM1iTN0MWGbgmSXnKWPdL6/UDdnchZsvHRvs

Processed: merge

[Debian Bug Tracking System]

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

> forcemerge 941948 941985
Bug #941948 [perl] postgresql-common: postgresql fails to start via systemd
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL 
snakeoil key
Bug #941973 [perl] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Bug #941985 [perl] perl 5.30.0 - Unable to set supplementary group IDs
Changed Bug forwarded-to-address to 
'https://rt.perl.org/Ticket/Display.html?id=134169' from 
'https://rt.perl.org/Public/Bug/Display.html?id=134169'.
Severity set to 'grave' from 'serious'
Added indication that 941985 affects 
postgresql-12,postgresql-11,postgresql-common
Bug #941973 [perl] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
Removed indication that 941973 affects postgresql-12, postgresql-common, and 
postgresql-11
Added indication that 941973 affects 
postgresql-12,postgresql-11,postgresql-common
Removed indication that 941948 affects postgresql-common, postgresql-12, and 
postgresql-11
Added indication that 941948 affects 
postgresql-12,postgresql-11,postgresql-common
Removed indication that 941967 affects postgresql-12, postgresql-common, and 
postgresql-11
Added indication that 941967 affects 
postgresql-12,postgresql-11,postgresql-common
Bug #941967 [perl] postgresql-11: fails to start after upgrade: EPERM on SSL 
snakeoil key
Merged 941948 941967 941973 941985
> --
Stopping processing here.

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

Bug#935086: insighttoolkit4 REMOVED from testing

[Gilles Filippini]

Control: tags -1 + patch

Hi,

Michael Crusoe a écrit le 04/10/2019 à 16:01 :
> Attached is a patch to force gcc 8; so far it has gotten farther than
> the previous failure for me (but my local build is still at 86%)

Looking at the related lines of /usr/include/c++/9/bits/stl_function.h,
it seems that __builtin_is_constant_evaluated is used only for C++
standard greater or equal to c++14:
> #if __cplusplus >= 201402L
> #ifdef _GLIBCXX_HAVE_BUILTIN_IS_CONSTANT_EVALUATED
>   if (__builtin_is_constant_evaluated())
> #else
>   if (__builtin_constant_p(__x > __y))
> #endif
> return __x > __y;
> #endif
>   return (__UINTPTR_TYPE__)__x > (__UINTPTR_TYPE__)__y;


Then I tried using '-std=c++11' and the build was successful.

Patch attached.

Thanks,

_g.
diff -Nru insighttoolkit4-4.12.2-dfsg1/debian/changelog 
insighttoolkit4-4.12.2-dfsg1/debian/changelog
--- insighttoolkit4-4.12.2-dfsg1/debian/changelog   2018-08-28 
16:27:47.0 +0200
+++ insighttoolkit4-4.12.2-dfsg1/debian/changelog   2019-10-07 
21:50:28.0 +0200
@@ -1,3 +1,10 @@
+insighttoolkit4 (4.12.2-dfsg1-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Force -std=c++11 to fix FTBFS with GCC-9 (closes: #935086)
+
+ -- Gilles Filippini   Mon, 07 Oct 2019 21:50:28 +0200
+
 insighttoolkit4 (4.12.2-dfsg1-4) unstable; urgency=medium
 
   * d/rules: Remove build dir right after installation
diff -Nru insighttoolkit4-4.12.2-dfsg1/debian/rules 
insighttoolkit4-4.12.2-dfsg1/debian/rules
--- insighttoolkit4-4.12.2-dfsg1/debian/rules   2018-08-28 16:27:47.0 
+0200
+++ insighttoolkit4-4.12.2-dfsg1/debian/rules   2019-10-07 21:50:28.0 
+0200
@@ -25,6 +25,9 @@
   ENABLE_UNSIGNED_LONG=ON 
 endif 
 
+# Fix for #935086
+export DEB_CXXFLAGS_MAINT_APPEND+=-std=c++11
+
 CMAKE_FLAGS = \
-DBUILD_EXAMPLES:BOOL=ON \
-DBUILD_SHARED_LIBS:BOOL=ON \


signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#935086: insighttoolkit4 REMOVED from testing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #935086 [src:insighttoolkit4] insighttoolkit4: FTBFS with GCC-9: use of 
undeclared identifier '__builtin_is_constant_evaluated'
Added tag(s) patch.

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

Processed: affects 939838

[Debian Bug Tracking System]

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

> affects 939838 + firewalld
Bug #939838 [src:nftables] nftables: please apply upstream commits to fix 
firewalld testsuite failures
Added indication that 939838 affects firewalld
> thanks
Stopping processing here.

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

Processed: affects 939838

[Debian Bug Tracking System]

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

> affects 939838 + src:firewalld
Bug #939838 [src:nftables] nftables: please apply upstream commits to fix 
firewalld testsuite failures
Added indication that 939838 affects src:firewalld
> thanks
Stopping processing here.

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

Processed: affects 939838

[Debian Bug Tracking System]

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

> affects 939838 - firewalld
Bug #939838 [src:nftables] nftables: please apply upstream commits to fix 
firewalld testsuite failures
Removed indication that 939838 affects firewalld
> thanks
Stopping processing here.

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

Bug#939838: nftables: please apply upstream commits to fix firewalld testsuite failures

[Michael Biebl]

On Mon, 9 Sep 2019 14:25:31 +0200 Gianfranco Costamagna
 wrote:
> Source: nftables
> Version: 0.9.2-1
> Severity: serious
> Justification: breaks another package from working correctly
> 
> Hello, according to firewalld upstream devs, we need 2 commits to fixup their 
> test failures.
> I also cherry-picked another hotfix, because it seemed important to me
> (note, I just uploaded them in Ubuntu, I didn't run the tests yet)
> commit ids:
> - 2e57d4ff79fa166f2dea3686ca4fe051b656a8d2
> - 03478af1bea03eafd43df94334cb001ed26145a3
> - 1e2aae7d73ce733650d78da452d45d6c5498cc33
> 
> patch here:
> 
> http://launchpadlibrarian.net/441272565/nftables_0.9.2-1_0.9.2-1ubuntu1.diff.gz
> 
> 


Any news here?
I ran into this while packaging an update for firewalld (unfortunately
we can't yet run the qemu based autopkgtests on Debian infra yet which
would have caught this regression automatically)

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#941991: gnome-shell: crashes on startup (Wayland only) with "JS ERROR: TypeError: actor.get_meta_window(...) is null"

[Zack Weinberg]

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

On my computer, after upgrading to gnome-shell 3.34, I consistently get a
gnome-shell catastrophic failure about 10 seconds after logging in, but only
when running under Wayland.  This error appears in the logs:

gnome-shell[2608]: JS ERROR: TypeError: actor.get_meta_window(...) is null
  destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1773:26
  onStopped@resource:///org/gnome/shell/ui/windowManager.js:1742:34
  makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
  easeActor/<@resource:///org/gnome/shell/ui/environment.js:126:60
gnome-shell[2608]: JS ERROR: TypeError: actor.get_meta_window(...) is null
  destroyWindowDone@resource:///org/gnome/shell/ui/windowManager.js:1773:26
  onStopped@resource:///org/gnome/shell/ui/windowManager.js:1742:34
  makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:73:13
  easeActor/<@resource:///org/gnome/shell/ui/environment.js:126:60
gdm-wayland-session[2571]: Received signal:15->'Terminated'

I don't see anything else that is obviously related, but I could have
missed something.  Please let me know if you need more information.

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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  evolution-data-server3.34.1-1
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-atspi-2.0 2.34.0-3
ii  gir1.2-freedesktop   1.62.0-2
ii  gir1.2-gcr-3 3.33.4-3
ii  gir1.2-gdesktopenums-3.0 3.34.0-2
ii  gir1.2-gdm-1.0   3.34.1-1
ii  gir1.2-geoclue-2.0   2.5.5-1
ii  gir1.2-glib-2.0  1.62.0-2
ii  gir1.2-gnomebluetooth-1.03.34.0-1
ii  gir1.2-gnomedesktop-3.0  3.34.0-3
ii  gir1.2-gtk-3.0   3.24.12-1
ii  gir1.2-gweather-3.0  3.28.3-2
ii  gir1.2-ibus-1.0  1.5.21-1
ii  gir1.2-mutter-5  3.34.0-4
ii  gir1.2-nm-1.01.20.4-2
ii  gir1.2-nma-1.0   1.8.22-2
ii  gir1.2-pango-1.0 1.42.4-7
ii  gir1.2-polkit-1.00.105-26
ii  gir1.2-rsvg-2.0  2.44.15-1
ii  gir1.2-soup-2.4  2.68.1-2
ii  gir1.2-upowerglib-1.00.99.11-1
ii  gjs  1.58.0-2
ii  gnome-backgrounds3.34.0-1
ii  gnome-settings-daemon3.34.0-3
ii  gnome-shell-common   3.34.0-2
ii  gsettings-desktop-schemas3.34.0-2
ii  libatk-bridge2.0-0   2.34.0-3
ii  libatk1.0-0  2.34.0-1
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libcroco30.6.13-1
ii  libecal-2.0-13.34.1-1
ii  libedataserver-1.2-243.34.1-1
ii  libgcr-base-3-1  3.33.4-3
ii  libgdk-pixbuf2.0-0   2.38.2+dfsg-1
ii  libgirepository-1.0-11.62.0-2
ii  libgjs0g 1.58.0-2
ii  libgles2 1.1.0-1+b1
ii  libglib2.0-0 2.62.1-1
ii  libglib2.0-bin   2.62.1-1
ii  libgnome-autoar-0-0  0.2.3-2
ii  libgstreamer1.0-01.16.1-1
ii  libgtk-3-0   3.24.12-1
ii  libical3 3.0.5-2
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-5-03.34.0-4
ii  libnm0   1.20.4-2
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpolkit-agent-1-0  0.105-26
ii  libpolkit-gobject-1-00.105-26
ii  libpulse-mainloop-glib0  13.0-2
ii  libpulse013.0-2
ii  libsecret-1-00.19.1-1
ii  libsystemd0  242-

Bug#941973: marked as done (FATAL: could not access private key file "/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id 
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
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.)


-- 
941985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-11
Version: 11.5-3sid2
Severity: important

Since yesterday postgresql@11-main.service fails to start and systemctl
status ends with:
postgresql@11-main.service: Failed with result 'protocol'.
Failed to start PostgreSQL Cluster 11-main.

In /var/log/postgresql/postgresql-11-main.log I see this:
2019-10-07 13:29:48.816 CEST [1058] LOG:  listening on IPv6 address "::1", port 
5432
2019-10-07 13:29:48.816 CEST [1058] LOG:  listening on IPv4 address 
"127.0.0.1", port 5432
2019-10-07 13:29:48.820 CEST [1058] LOG:  listening on Unix socket 
"/var/run/postgresql/.s.PGSQL.5432"
2019-10-07 13:29:48.845 CEST [1060] LOG:  database system was shut down at 
2019-10-07 07:54:57 CEST
2019-10-07 13:29:48.864 CEST [1058] LOG:  database system is ready to accept 
connections
2019-10-07 13:29:49.395 CEST [1098] [unknown]@[unknown] LOG:  incomplete 
startup packet
2019-10-07 13:43:20.898 CEST [1058] LOG:  received fast shutdown request
2019-10-07 13:43:20.904 CEST [1058] LOG:  aborting any active transactions
2019-10-07 13:43:20.905 CEST [1058] LOG:  background worker "logical 
replication launcher" (PID 1066) exited with exit code 1
2019-10-07 13:43:20.905 CEST [1061] LOG:  shutting down
2019-10-07 13:43:20.979 CEST [1058] LOG:  database system is shut down
2019-10-07 13:44:00.487 CEST [1086] FATAL:  could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied
2019-10-07 13:44:00.487 CEST [1086] LOG:  database system is shut down
pg_ctl: could not start server
Examine the log output.

And then the last 4 lines get repeated many times.

A bit further up the log file, when postgresql-11 got upgraded to this
version, there are these lines:

2019-10-06 23:23:42.714 CEST [2172] diederik@akonadi_diederik FATAL:  
terminating connection due to administrator command
2019-10-06 23:23:42.714 CEST [1054] LOG:  background worker "logical 
replication launcher" (PID 1064) exited with exit code 1

The FATAL line appears ~30 times, all within the same second.
Downgrading postgresql-11 and postgresql-client-11 to the version in
testing (11.5-2+b1) did not fix the issue.
I then tried to access /etc/ssl/private/ssl-cert-snakeoil.key (as user
postgres) and indeed couldn't access that file. User postgres is in
group ssl-cert and this was the permissions to the private dir:
drwx--x--- 2 root ssl-cert  4096 okt  7 18:13 private

When I changed it to this:
drwxr-x--- 2 root ssl-cert  4096 okt  7 18:13 private

I could access the ssl-cert-snakeoil.key file as user postgres, but this
did not resolve the issue. It kept reporting "Permission denied".

Since 2019-10-07 13:44:00.487 CEST, I only get those last 4 lines.


I don't know if it's relevant, but together with the upgrade of
postgresql-11, apparmor and llvm got upgraded.
And the FATAL line appeared when perl got upgraded from 5.28 to 5.30.


I mention those other upgrades as downgrading the postgresql packages to
the testing versions did not fix the issue (which it often does).
As I'm therefor not 100% sure the issue is (directly) in the postgresql
packages, I set the severity to important instead of grave.


Anyway, the result is no running postgresql, thus no akonadi, thus no 
working kmail for me.

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

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

Versions of packages postgresql-11 depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.29-2
ii  libgcc11:9.2.1-8
ii  libgssapi-krb5-2   1.17-6
ii  libicu63   63.2-2
ii  libldap-2.4-2  2.4.48+dfsg-1+b1
ii  libllvm9   1:9-2
ii  libpam0g   1.3.1-5
ii  libpq5 12.0-1+b1
ii  libselinux12.9-2+b2
ii  libssl1.1   

Bug#941985: marked as done (perl 5.30.0 - Unable to set supplementary group IDs)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id 
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding perl 5.30.0 - Unable to set supplementary group IDs
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.)


-- 
941985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl
Version: 5.30.0-5
Forwarded: https://rt.perl.org/Public/Bug/Display.html?id=134169
Severity: serious

A regression in perl 5.30.0 breaks setting supplementary groups by
assigning a space-separated string to the $) variable.  This breaks
postgresql-common, which relies on taking on all the supplementary
groups of the postgres user (specifically ssl-cert, to be able to read
SSL certificates).

This has been fixed in blead¹, and proposed for backporting to the 5.30
branch².

[1]: 
http://perl5.git.perl.org/perl.git/commitdiff/79e302e6c3f815bf4cb72a5bacc3012595970db9
[2]: 
https://perl5.git.perl.org/perl.git/commitdiff/37615aed2d5ce7dd5e254533f5235478f3378422

- ilmari
-- 
"The surreality of the universe tends towards a maximum" -- Skud's Law
"Never formulate a law or axiom that you're not prepared to live with
 the consequences of."  -- Skud's Meta-Law
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.30.0-6

We believe that the bug you reported is fixed in the latest version of
perl, 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.
Niko Tyni  (supplier of updated perl 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: Tue, 08 Oct 2019 20:25:35 +0300
Source: perl
Architecture: source
Version: 5.30.0-6
Distribution: unstable
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Closes: 941985
Changes:
 perl (5.30.0-6) unstable; urgency=medium
 .
   * Apply upstream patch fixing a regression in group id parsing that
 broke setting supplementary group IDs. (Closes: #941985)
Checksums-Sha1:
 65b0c4c9300925093f939a2ab4b419e000686d75 2983 perl_5.30.0-6.dsc
 3a63ae2e0e74e460ece01ab319b3358b6168aa45 161256 perl_5.30.0-6.debian.tar.xz
Checksums-Sha256:
 3d480d10a1368303d235abd2b986d3f3cd1d56f64150867dba4041eba7b4a2ec 2983 
perl_5.30.0-6.dsc
 2d65fb2db865784b04ee99917b4232c72b28b8e62cc9599978fc1839f1fba808 161256 
perl_5.30.0-6.debian.tar.xz
Files:
 0b2026f08aacba87cee98cbc3be84684 2983 perl standard perl_5.30.0-6.dsc
 3d5fcf3b0d17523e3a939c25cf0e2af9 161256 perl standard 
perl_5.30.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAl2c0NERHG50eW5pQGRl
Ymlhbi5vcmcACgkQLsD/s7cwGx/8/A//YZ+Z3H5kRMfkGn31wl1fdsGPVFVPY3Gv
qUhebqnMgYy6uf2YTgwN0ZjqJGs2ZLKPx1ifC1YEy86MZZ1DAHxwViMR4lRUe2R2
cM9GqJXrlcBmjz46mD98FR2Q6mXn0GEw7GguLLaj1mw+MobH7beuDcqaBG8iXlWH
dpl9hAgMZAce5mj9b2qcWvclnol2YIll6KaXx8FccFoVop8z+tCmp9Diby3fRn0q
j5DBh3z9Fszm6mGZdepxB9dyKqXXBneWZAXUB8kS6HZRnLU790YLBY2YnLC4NiDH
Jpax4BXcRFQwcBGbHNUp5SDrWrk6xJOwDd1kZ3465klIkHx0S7Z4jvf4pEQVZSqo
ok49L3pK3sB5B6ajeNYBFd0uhQajtxt8CTKK/1ySCdHTBLPqPpTw0vw719MMS5/H
56pKSERo6qMaB0ofsnh28mpbgZiIl2Hdmd0MjVL8T05L9U70dxjSIQ4tPfAAFcTg
/IT+TtuAuORJH7omCIC27vaTsJCNhxA4quete83JPKL2kht6wJRcxvBbQ5zMjeTF
KMy9w5983REfbmnGHtjZUODNZUwtCMmlo+/LNP4bODrbkrF+7uh2C8Wg+4jOMGib
tcDp/+3bho+7BDdNVSD+mBBheVfuqGFr3oCVD8Ri3NrMsbGpDKRYY4UCcxgMRKoE
cjK4sg96RGI=
=2gnT
-END PGP SIGNATURE End Message ---

Bug#941967: marked as done (postgresql-11: fails to start after upgrade: EPERM on SSL snakeoil key)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id 
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding postgresql-11: fails to start after upgrade: EPERM on SSL snakeoil key
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.)


-- 
941985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-11
Version: 11.5-3sid2
Severity: grave
Justification: renders package unusable

[master ac9ac01] committing changes in /etc made by "apt-get --purge 
dist-upgrade"
 5 files changed, 4 insertions(+), 7 deletions(-)
E: Sub-process /usr/bin/dpkg returned an error code (1)
100|root@ci-busyapps:~ # dpkg -a --configure
Setting up postgresql-11 (11.5-3sid2) ...
Starting PostgreSQL 11 database server: mainError: 
/usr/lib/postgresql/11/bin/pg_ctl /usr/lib/postgresql/11/bin/pg_ctl start -D 
/var/lib/postgresql/11/main -l /var/log/postgresql/postgresql-11-main.log -s -o 
-c config_file="/etc/postgresql/11/main/postgresql.conf" exited with status 1: 
2019-10-08 08:43:41 UTC [2601-1] FATAL: could not access private key file 
"/etc/ssl/private/ssl-cert-snakeoil.key": Permission denied 2019-10-08 08:43:41 
UTC [2601-2] LOG: database system is shut down pg_ctl: could not start server 
Examine the log output. ... failed!
 failed!
invoke-rc.d: initscript postgresql, action "start" failed.
dpkg: error processing package postgresql-11 (--configure):
 installed postgresql-11 package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 postgresql-11
1|root@ci-busyapps:~ # ll /etc/ssl/private/ssl-cert-snakeoil.key
-rw-r- 1 root ssl-cert 1704 Sep 28  2015 
/etc/ssl/private/ssl-cert-snakeoil.key
root@ci-busyapps:~ # ll -d /etc/ssl/private
drwx--x--- 2 root ssl-cert 4096 Sep  6  2018 /etc/ssl/private/



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages postgresql-11 depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libc6  2.29-2
ii  libgcc11:9.2.1-8
ii  libgssapi-krb5-2   1.17-6
ii  libicu63   63.2-2
ii  libldap-2.4-2  2.4.48+dfsg-1+b1
ii  libllvm9   1:9-2
ii  libpam0g   1.3.1-5
ii  libpq5 12.0-1+b1
ii  libselinux12.9-2+b2
ii  libssl1.1  1.1.1d-1
ii  libstdc++6 9.2.1-8
ii  libsystemd0242-7
ii  libuuid1   2.34-0.1
ii  libxml22.9.4+dfsg1-7+b3tarent1
ii  libxslt1.1 1.1.32-2.1
ii  locales2.29-2
ii  locales-all2.29-2
ii  postgresql-client-11   11.5-3sid2
ii  postgresql-common  207
ii  ssl-cert   1.0.39
ii  tzdata 2019c-3
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages postgresql-11 recommends:
ii  sysstat  12.0.6-1

postgresql-11 suggests no packages.

-- debconf information:
  postgresql-11/postrm_purge_data: true
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.30.0-6

We believe that the bug you reported is fixed in the latest version of
perl, 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.
Niko Tyni  (supplier of updated perl 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: Tue, 08 Oct 2019 20:25:35 +0300
Source: perl
Architecture: source
Version: 5.30.0-6
Distribution: unstable
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Closes: 941985
Changes:
 perl (5.30.0-6) unstable; urgency=medium
 .
   * Apply upstream patch fixing a regression in group id parsing that
 broke setting supplementary group IDs. (Closes: #941985)
Checksums-Sha1:
 65b0c4c9300925093f939a2ab4b419e000686d75 2983 perl_5.3

Bug#941948: marked as done (postgresql-common: postgresql fails to start via systemd)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 18:37:08 +
with message-id 
and subject line Bug#941985: fixed in perl 5.30.0-6
has caused the Debian Bug report #941985,
regarding postgresql-common: postgresql fails to start via systemd
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.)


-- 
941985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941985
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-common
Version: 207
Severity: important

when trying to start service postgresql@12-main (the same with 11)
service using systemctl start postgresql@12-main
starting the server fails, the log file says it failed to read
/etc/ssl/private/ssl-cert-snakeoil.key (no read permissions)
ls -l that file says (dates redacted):
-rw-r- 1 root ssl-cert 1704 MMM  DD   ssl-cert-snakeoil.key
ls -l the directoy says (dates redacted):
drwxr-x--- 2 root ssl-cert   323 MMM DD   private

The user postgres is member of group ssl-cert.

According to the upstream docs, this is as it should be.

However, starting a postgresql cluser manually via
a su -s /bin/bash postgres session works normally.

My current workaroud is to start the postgresql server manually
after every bootup, but this is tedious. I am at loss what
the cause might be.

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages postgresql-common depends on:
ii  adduser   3.118
ii  debconf [debconf-2.0] 1.5.73
ii  lsb-base  11.1.0
ii  postgresql-client-common  207
ii  procps2:3.3.15-2+b1
ii  ssl-cert  1.0.39
ii  ucf   3.0038+nmu1

Versions of packages postgresql-common recommends:
ii  e2fsprogs  1.45.4-1
ii  logrotate  3.15.1-1

Versions of packages postgresql-common suggests:
ii  libjson-perl  4.02000-1

-- debconf information:
  postgresql-common/ssl: true
* postgresql-common/obsolete-major:
  postgresql-common/catversion-bump:
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.30.0-6

We believe that the bug you reported is fixed in the latest version of
perl, 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.
Niko Tyni  (supplier of updated perl 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: Tue, 08 Oct 2019 20:25:35 +0300
Source: perl
Architecture: source
Version: 5.30.0-6
Distribution: unstable
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Closes: 941985
Changes:
 perl (5.30.0-6) unstable; urgency=medium
 .
   * Apply upstream patch fixing a regression in group id parsing that
 broke setting supplementary group IDs. (Closes: #941985)
Checksums-Sha1:
 65b0c4c9300925093f939a2ab4b419e000686d75 2983 perl_5.30.0-6.dsc
 3a63ae2e0e74e460ece01ab319b3358b6168aa45 161256 perl_5.30.0-6.debian.tar.xz
Checksums-Sha256:
 3d480d10a1368303d235abd2b986d3f3cd1d56f64150867dba4041eba7b4a2ec 2983 
perl_5.30.0-6.dsc
 2d65fb2db865784b04ee99917b4232c72b28b8e62cc9599978fc1839f1fba808 161256 
perl_5.30.0-6.debian.tar.xz
Files:
 0b2026f08aacba87cee98cbc3be84684 2983 perl standard perl_5.30.0-6.dsc
 3d5fcf3b0d17523e3a939c25cf0e2af9 161256 perl standard 
perl_5.30.0-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAl2c0NERHG50eW5pQGRl
Ymlhbi5vcmcACgkQLsD/s7cwGx/8/A//YZ+Z3H5kRMfkGn31wl1fdsGPVFVPY3Gv
qUhebqnMgYy6uf2YTgwN0ZjqJGs2ZLKPx1ifC1YEy86MZZ1DAHxwViMR4lRUe2R2
cM9GqJXrlcBmjz46mD98FR2Q6mXn0GEw7GguLLaj1mw+MobH7beuDcqaBG8iXlWH
dpl9hAgMZAce5mj9b2qcWvclnol2YIll6KaXx8FccFoVop8z+tCmp9Diby3fRn0q
j5DBh3z9Fszm6mGZdepxB9dyKqXXBneWZAXUB8kS6HZRnLU790YLBY2YnLC4NiDH
Jpax4BXcRFQwcBGbHNUp5SDrWrk6xJOwDd1kZ3465klIkHx0S7Z4jvf4pEQVZSqo
ok49L3pK3sB5B6ajeNYBFd0uhQajtxt8CTKK/1

Bug#938804: marked as done (vtk6: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 19:07:59 +
with message-id 
and subject line Bug#938804: fixed in vtk6 6.3.0+dfsg2-4
has caused the Debian Bug report #938804,
regarding vtk6: 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.)


-- 
938804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vtk6
Version: 6.3.0+dfsg2-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:vtk6

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: vtk6
Source-Version: 6.3.0+dfsg2-4

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated vtk6 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: Tue, 08 Oct 2019 20:17:20 +0200
Source: vtk6
Architecture: source
Version: 6.3.0+dfsg2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Anton Gladky 
Closes: 938804
Changes:
 vtk6 (6.3.0+dfsg2-4) unstable; urgency=medium
 .
   * [31d14a1] Drop python-vtk6 package due to py2 removal. (Closes: #938804)
   * [eb5d4a3] Set compat-level 12
   * [8263228] Set standards-version to 4.4.1
   * [c3f906a] Set upstream metadata fields: Repository.
   * [afc9b7a] Drop unnecessary dh arguments: --parallel
Checksums-Sha1:
 b6cda035abc3577a6e13af67ef3a01ceda65c3cc 2964 vtk6_6.3.0+dfsg2-4.dsc
 b01b2fdcf9c0bda626c788cbcdb6d92f12d0debf 30724 vtk6_6.3.0+dfsg2-4.debian.tar.xz
 afd2005c507d8840b993c355dc15ebc3081f9a16 6637 
vtk6_6.3.0+dfsg2-4_source.buildinfo
Checksums-Sha256:
 1f393734c953d1889002c09b9c431a5106b0a6f453171ed1d6786e8d224259f4 2964 
vtk6_6.3.0+dfsg2-4.dsc
 419528c885b8fe6af03005e3c3b5c062afa5b21c71a58f3f5eedd311d457c68f 30724 
vtk6_6.3.0+dfsg2-

Bug#941996: openmpi-bin: segfaults with the 'verbs' OFI provider

[Lucas Nussbaum]

Package: openmpi-bin
Version: 3.1.3-11
Severity: serious

Hi,

This is tracked upstream as https://github.com/open-mpi/ompi/issues/7035 .

mpirun segfaults during MTL OFI provider section when run on a machine
with an InfiniBand network. This happens for the following reason: Until
version 3.1.2, OFI used an opt-in mechanism to include providers.
'verbs' wasn't included by default. This was changed by
https://github.com/open-mpi/ompi/commit/d00c387284b6197946452a0938e76615a17fa689

The discussion is still ongoing upstream, but it looks like this might
be related to the libfabric version in Debian.  The chosen solution
upstream might be to disable the 'verbs' provider.

Also, v4.x is not affected.

I believe this should be fixed in stable. Infiniband is common in HPC
clusters, so a broken OpenMPI is of limited use without its support.

Lucas


-- System Information:
Debian Release: 10.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-6-amd64 (SMP w/32 CPU cores)
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:en (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 openmpi-bin depends on:
ii  libc62.28-10
ii  libevent-2.1-6   2.1.8-stable-4
ii  libevent-pthreads-2.1-6  2.1.8-stable-4
ii  libhwloc51.11.12-3
ii  libopenmpi3  3.1.3-11
ii  openmpi-common   3.1.3-11
ii  openssh-client [ssh-client]  1:7.9p1-10
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages openmpi-bin recommends:
ii  libopenmpi-dev  3.1.3-11

Versions of packages openmpi-bin suggests:
ii  gfortran [fortran-compiler]  4:8.3.0-1

-- no debconf information

Bug#941531: marked as done (gsl-doc: build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 19:19:34 +
with message-id 
and subject line Bug#941531: fixed in gsl-doc 2.6-1
has caused the Debian Bug report #941531,
regarding gsl-doc: 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.)


-- 
941531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsl-doc
Version: 2.3-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 -u gsl-doc-2.3/debian/control gsl-doc-2.3/debian/control
--- gsl-doc-2.3/debian/control
+++ gsl-doc-2.3/debian/control
@@ -4,7 +4,7 @@
 Maintainer: Dirk Eddelbuettel 
 Standards-Version: 3.9.8
 Build-Depends: debhelper (>= 7.2.17), autotools-dev
-Build-Depends-Indep: texlive-base, texlive-latex-base, 
texlive-generic-recommended, texlive-font-utils, texinfo, ghostscript, ps2eps
+Build-Depends-Indep: texlive-base, texlive-latex-base, texlive-plain-generic, 
texlive-font-utils, texinfo, ghostscript, ps2eps
 Homepage: http://www.gnu.org/software/gsl
 
 Package: gsl-doc-pdf
--- End Message ---
--- Begin Message ---
Source: gsl-doc
Source-Version: 2.6-1

We believe that the bug you reported is fixed in the latest version of
gsl-doc, 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 gsl-doc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Oct 2019 21:13:12 -0500
Source: gsl-doc
Binary: gsl-doc-info gsl-doc-pdf
Architecture: source all
Version: 2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 gsl-doc-info - GNU Scientific Library (GSL) Reference Manual in info
 gsl-doc-pdf - GNU Scientific Library (GSL) Reference Manual in pdf
Closes: 941531
Changes:
 gsl-doc (2.6-1) unstable; urgency=medium
 .
   * New upstream release
 .
   * debian/control: Change Build-Depends: from texlive-generic-recommended
 to texlive-plain-generic   (Closes: #941531)
 .
   * debian/control: Set Standards-Version: to current version
Checksums-Sha1:
 bdbde167f3007f7c3f4ab55e8d442b37b2b0667a 1999 gsl-doc_2.6-1.dsc
 9273164b6bdf60d0577518a1c1310eff6659e3dd 7398548 gsl-doc_2.6.orig.tar.gz
 07d5986af138c12059c82938ae597c5aa9014663 12352 gsl-doc_2.6-1.debian.tar.xz
 5bef50cd1d0b68291923fe151e04a5d76f3d1764 477636 gsl-doc-info_2.6-1_all.deb
 00ebafcf8f4fddfbde4cf3a0b531656237ada1fa 4775280 gsl-doc-pdf_2.6-1_all.deb
 e730079284d0c9652d303de3d418c091a8c91a6c 10222 gsl-doc_2.6-1_amd64.buildinfo
Checksums-Sha256:
 1d7e8446b0c83174474e181be5df7abe6a94d8c50d27ee2b6fc82be7613f07bc 1999 
gsl-doc_2.6-1.dsc
 b782339fc7a38fe17689cb39966c4d821236c28018b6593ddb6fd59ee40786a8 7398548 
gsl-doc_2.6.orig.tar.gz
 38bb3bd102e76022c90039266e6bff3304f4720d60672332a940f6c48a32b761 12352 
gsl-doc_2.6-1.debian.tar.xz
 5b3b5059418b8ef3e163e41cabfacaf2ad54c3e909aee6db1cf1e4ecc4eda5e3 477636 
gsl-doc-info_2.6-1_all.deb
 310ec9367db00ec5ccc645d149a0cd7a33fc0537f65e1529b2278c96e107f78f 4775280 
gsl-doc-pdf_2.6-1_all.deb
 dec3f2a6fe312b6ad57327ab519fd1df701c6a48141ac0cc5c2e3430b78efeca 10222 
gsl-doc_2.6-1_amd64.buildinfo
Files:
 0620f2a1035f10527e42418d592c0159 1999 non-free/math optional gsl-doc_2.6-1.dsc
 bda73a3dd5ff2f30b5956764399db6e7 7398548 non-free/math optional 
gsl-doc_2.6.orig.tar.gz
 8a50e669ce6cc2eadc7ff51397a204bc 12352 non-free/math optional 
gsl-doc_2.6-1.debian.tar.xz
 1833b25d20b9f56edeb371ae7abc32a0 477636 non-free

Bug#941982: libsys-info-base-perl: missing file Sys/Info.pm

[Vincent Lefevre]

On 2019-10-08 16:03:40 +0200, gregor herrmann wrote:
> On Tue, 08 Oct 2019 15:47:50 +0200, Vincent Lefevre wrote:
> 
> > Package: libsys-info-base-perl
> > Version: 0.7807-2
> > Severity: grave
> > Justification: renders package unusable
> > 
> > I wanted to get the number of CPUs (see Sys::Info::Device::CPU man page),
> > but this fails at "use Sys::Info;":
> > 
> > $ perl -MSys::Info -e ''
> > Can't locate Sys/Info.pm in @INC (you may need to install the Sys::Info 
> > module)
> > [...]
> > 
> > There is no such issue with upstream's module version 0.78
> 
> Note that libsys-info-base-perl is the package for the CPAN
> distribution https://metacpan.org/release/Sys-Info-Base which does
> not contain Sys::Info.

Then it should be provided by a dependency, since it is needed
(see the man page I've mentioned).

> Sys::Info is in https://metacpan.org/release/Sys-Info which
> apparently is currently not available in Debian; maybe this
> should be changed … Interestingly the metadata of Sys-Info-Base don't
> refer to Sys::Info, just some examples in the documentation.

Perhaps something missing in the metadata.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Processed: kopanocore: autopkgtest tries to install packages itself but doesn't exit appropriately if that fails

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:perl
Bug #941999 [src:kopanocore] kopanocore: autopkgtest tries to install packages 
itself but doesn't exit appropriately if that fails
Added indication that 941999 affects src:perl

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

Bug#941999: kopanocore: autopkgtest tries to install packages itself but doesn't exit appropriately if that fails

[Paul Gevers]

Source: kopanocore
Version: 8.7.0-3
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: issue
Control: affects -1 src:perl

Dear maintainers,

With a recent upload of perl the autopkgtest of kopanocore fails in
testing when that autopkgtest is run with the binary packages of perl
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
perl   from testing5.30.0-5
kopanocore from testing8.7.0-3
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. The problem is
that you seem to be installing the mariadb-server package (and others)
in the autopkgtest, such that the test fails if the installation in the
migration setup fails. It seems that some of the (indirect) dependencies
of mariadb-server need to come from unstable with the latest perl
installed. If you really need to install during the autopkgtest (e.g. to
have the pre-seeding work) I suggest you mark this test as skippable (an
autopkgtest restriction) and exit with code 77 in case you can't install
a package.

Currently this regression is blocking the migration of perl to testing [1].

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

Paul
PS: you may be interested in the hint-testsuite-triggers 'restriction'
and add a testcase with that restriction that depends on mariadb-server,
to make sure that when mariadb-server is updated, your package is also
tested for regressions.

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
perl/5.30.0-5. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=perl

https://ci.debian.net/data/autopkgtest/testing/amd64/k/kopanocore/3120902/log.gz

autopkgtest [19:14:13]: test smoke: [---
###
# Setting up database configuration...#
# Setting up database configuration... done.  #
###

###
# Installing MariaDB server package...#
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 mariadb-server : Depends: mariadb-server-10.3 (>= 1:10.3.18-1) but it
is not going to be installed
E: Unable to correct problems, you have held broken packages.
autopkgtest [19:14:14]: test smoke: ---]



signature.asc
Description: OpenPGP digital signature

Bug#885263: caja-dropbox: Depends on unmaintained pygtk

[mike . gabriel]

Hi,

Am Dienstag, 8. Oktober 2019 schrieb Vlad Orlov:
> Hi,
> 
> The migration to Python 3 and GI had been done in caja-dropbox 1.22.0.
> I guess we can close this

This can only ve closed once the Debian packaging has switched to Py3. I will 
look into that after my VAC.

Mike

-- 
Gesendet von meinem Fairphone2 (powered by Sailfish OS).

Bug#942000: dune-grid build-depends on removed python-vtk6

[Anton Gladky]

Source: dune-grid
Severity: serious

Dear Maintainer,

dune-grid build-depends on the python-vtk6 package, which was dropped
due to the python2-removal.

Please remove the package from build-depends.

Thanks,

Anton

Bug#933217: RM: check-mk -- RoQA, RC-Buggy, unmaintained, no reverse dependency

[Moritz Mühlenhoff]

On Mon, Sep 30, 2019 at 09:34:46AM -0700, Matt Taggart wrote:
> Hi,
> 
> 
> I think it's fine for check-mk to be removed from unstable, if it does
> end up in Debian again it will be repackaged and should go through NEW
> again anyway.

Ack, I've just filed a removal bug. I suppose the version from
experimental should be removed as well?

Cheers,
Moritz

Bug#941837: texlive-fonts-extra: file conflice with (older) texlive-fonts-extra-links

[Hilmar Preuße]

On 10/6/19 10:04 AM, Ansgar Burchardt wrote:

Hi Norbert,

> when upgrading in Debian testing I saw the following error message:
> 
> +---
> | Unpacking texlive-fonts-extra (2019.20190930-2) over (2019.20190830-1) ...
> | dpkg: error processing archive 
> /tmp/apt-dpkg-install-h6VDTu/50-texlive-fonts-extra_2019.20190930-2_all.deb 
> (--unpack):
> |  trying to overwrite 
> '/usr/share/texlive/texmf-dist/fonts/opentype/arkandis/berenisadf/BerenisADFProSC-Bold.otf',
>  which is also in package texlive-fonts-extra-links 2019.20190830-1
> | dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> +---
> 
> It looks like texlive-fonts-extra is missing a (versioned) Replaces on
> texlive-fonts-extra-links.
> 
Do you have some time to care about this? I'm lost, sorry!

Hilmar
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature

Processed: Re: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[Debian Bug Tracking System]

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

> tags 940973 + fixed-upstream
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[Chris Lamb]

tags 940973 + fixed-upstream
thanks

This has apparently been fixed (again) upstream in version 1.67:

  
https://github.com/redhotpenguin/perl-Archive-Zip/issues/51#issuecomment-539679696


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#940973: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[gregor herrmann]

Control: tag -1 - fixed-upstream
COntrol: notforwarded -1

On Tue, 08 Oct 2019 14:10:19 -0700, Chris Lamb wrote:

> This has apparently been fixed (again) upstream in version 1.67:
> 
>   
> https://github.com/redhotpenguin/perl-Archive-Zip/issues/51#issuecomment-539679696

Thanks for the notice but I'm afraid this is a different issue, and
"our" problem is not yet fixed.
(I tried with some of the merge requests earlier, and Salvatore tried
today with the 1.67 release.)

I guess now that 1.67 is out we should open a separate issue upstream
…


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Processed: Re: libarchive-zip-perl breaks strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - fixed-upstream
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Removed tag(s) fixed-upstream.
> notforwarded -1
Bug #940973 [src:libarchive-zip-perl] libarchive-zip-perl breaks 
strip-nondeterminism autopkgtest: error: becoming Archive::Zip::DirectoryMember
Unset Bug forwarded-to-address

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

Bug#933217: RM: check-mk -- RoQA, RC-Buggy, unmaintained, no reverse dependency

[Matt Taggart]

On 10/8/19 2:06 PM, Moritz Mühlenhoff wrote:
> On Mon, Sep 30, 2019 at 09:34:46AM -0700, Matt Taggart wrote:
>> Hi,
>>
>>
>> I think it's fine for check-mk to be removed from unstable, if it does
>> end up in Debian again it will be repackaged and should go through NEW
>> again anyway.
> 
> Ack, I've just filed a removal bug. I suppose the version from
> experimental should be removed as well?

Yes.

Thanks,

-- 
Matt Taggart
tagg...@debian.org

Bug#941837: texlive-fonts-extra: file conflice with (older) texlive-fonts-extra-links

[Norbert Preining]

On Tue, 08 Oct 2019, Hilmar Preuße wrote:
> Do you have some time to care about this? I'm lost, sorry!

Uploading soon. Rather simple, the BerenisADFProSC fonts were obviously
dropped from Debian, so I reincluded them and they end up in the
texlive-extra-fonts package, while the links previously there are in the
tl-e-f-links package. See git commit 9ab9bb01387f2604a0b65b9677e246be58d29077

Best


Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#938952: [debian Buster] [arm64 pinebook] [sysvinit-core] libsoup2.4-1 : Depends: glib-networking (>= 2.32.0) but it is not going to be installed

[Adam Borowski]

On Mon, Oct 07, 2019 at 10:44:12PM +0200, Thorsten Glaser wrote:
> On Mon, 7 Oct 2019, Jean-Marc LACROIX wrote:
> > It seems that now all is ok, because sysvinit is correctly installed on 
> > Debian
> > 10.1
> 
> Yes, but the other packages are not yet ready for elogind
> in Debian 10.anything and never will, because Debian 10.x
> was released in April 2019, and this will not get updated.
> 
> (Backporting elogind once everything works will help, but
> not enough, because other packages hard-depend on (usually)
> libpam-systemd and lack the | logind alternative.)

And that's basically the only problem.

elogind in buster uses a separate libelogind which makes it immune to the
libsystemd alternative problem that haunts unstable.  That makes grabbing
libpam-elogind-compat or bolting it upon buster's libpam-elogind enough
to satisfy dependencies.

I don't remember if that's enough or not for policykit-1 to work adequately,
though.

> If you wish to use elogind, either be prepared to do
> unspeakably evil things (such as editing the internal
> dpkg status database, which I did to great success on
> an RPi last week) or upgrade to unstable (in which the
> only missing piece polkit-qt is).

Editing dpkg status is bad.  An equivs package (which libpam-elogind-compat
essentially is) is a much cleaner option.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
⠈⠳⣄ etc), let the drink age at least 3-6 months.

Processed: reassign 941143 to src:graphviz, fixed 941143 in 2.42.2-2, notfound 938770 in 2.0.1-4 ...

[Debian Bug Tracking System]

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

> reassign 941143 src:graphviz 2.40.1-7
Bug #941143 {Done: Laszlo Boszormenyi (GCS) } 
[libcgraph6,libcdt5,libpathplan4,libgvpr2,libxdot1,liblab-gamut1] multiarchify 
graphviz libraries
Warning: Unknown package 'libxdot1'
Bug reassigned from package 
'libcgraph6,libcdt5,libpathplan4,libgvpr2,libxdot1,liblab-gamut1' to 
'src:graphviz'.
No longer marked as found in versions 2.40.1-7.
No longer marked as fixed in versions graphviz/2.42.2-2.
Bug #941143 {Done: Laszlo Boszormenyi (GCS) } [src:graphviz] 
multiarchify graphviz libraries
Marked as found in versions graphviz/2.40.1-7.
> fixed 941143 2.42.2-2
Bug #941143 {Done: Laszlo Boszormenyi (GCS) } [src:graphviz] 
multiarchify graphviz libraries
Marked as fixed in versions graphviz/2.42.2-2.
> notfound 938770 2.0.1-4
Bug #938770 {Done: Sandro Tosi } [src:vcr.py] vcr.py: Python2 
removal in sid/bullseye
No longer marked as found in versions vcr.py/2.0.1-4.
> found 938770 2.0.1-3
Bug #938770 {Done: Sandro Tosi } [src:vcr.py] vcr.py: Python2 
removal in sid/bullseye
Marked as found in versions vcr.py/2.0.1-3.
> reassign 941124 src:erlang 1:22.1+dfsg-1
Bug #941124 {Done: Sergei Golovan } 
[src:erlang,src:elixir-lang] elixir-lang (autopkgtest) fails with new erlang
Bug reassigned from package 'src:erlang,src:elixir-lang' to 'src:erlang'.
No longer marked as found in versions elixir-lang/1.9.1.dfsg-1 and 
erlang/1:22.1+dfsg-1.
No longer marked as fixed in versions erlang/1:22.1.1+dfsg-2.
Bug #941124 {Done: Sergei Golovan } [src:erlang] 
elixir-lang (autopkgtest) fails with new erlang
Marked as found in versions erlang/1:22.1+dfsg-1.
> fixed 941124 1:22.1.1+dfsg-2
Bug #941124 {Done: Sergei Golovan } [src:erlang] 
elixir-lang (autopkgtest) fails with new erlang
The source 'erlang' and version '1:22.1.1+dfsg-2' do not appear to match any 
binary packages
Marked as fixed in versions erlang/1:22.1.1+dfsg-2.
> affects 941124 + src:elixir-lang
Bug #941124 {Done: Sergei Golovan } [src:erlang] 
elixir-lang (autopkgtest) fails with new erlang
Added indication that 941124 affects src:elixir-lang
> reassign 935903 src:linux 5.2.9-2
Bug #935903 [linux-headers-5.2.0-2-amd64] linux-headers-5.2.0-2-amd64: kernel 
panic after upgrading to linux-5.2.0
Warning: Unknown package 'linux-headers-5.2.0-2-amd64'
Bug reassigned from package 'linux-headers-5.2.0-2-amd64' to 'src:linux'.
No longer marked as found in versions linux/5.2.9-2.
Ignoring request to alter fixed versions of bug #935903 to the same values 
previously set
Bug #935903 [src:linux] linux-headers-5.2.0-2-amd64: kernel panic after 
upgrading to linux-5.2.0
Marked as found in versions linux/5.2.9-2.
> reassign 935047 src:linux
Bug #935047 [linux-image-5.2.0-2-amd64] pulseaudio: regularly stops producing 
sound over USB interface
Warning: Unknown package 'linux-image-5.2.0-2-amd64'
Bug reassigned from package 'linux-image-5.2.0-2-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #935047 to the same values 
previously set
Ignoring request to alter fixed versions of bug #935047 to the same values 
previously set
> reassign 940710 src:linux
Bug #940710 [linux-image-5.2.0-2-amd64] Please enable 
CONFIG_PKCS8_PRIVATE_KEY_PARSER
Warning: Unknown package 'linux-image-5.2.0-2-amd64'
Bug reassigned from package 'linux-image-5.2.0-2-amd64' to 'src:linux'.
Ignoring request to alter found versions of bug #940710 to the same values 
previously set
Ignoring request to alter fixed versions of bug #940710 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#925628: marked as done (afnix: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Tue, 08 Oct 2019 23:49:11 +
with message-id 
and subject line Bug#925628: fixed in afnix 2.9.2-2
has caused the Debian Bug report #925628,
regarding afnix: 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.)


-- 
925628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:afnix
Version: 2.9.2-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/afnix_2.9.2-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.

[...]
make[6]: Entering directory '/<>/prj/std/sps/src'
make[6]: Leaving directory '/<>/prj/std/sps/src'
make[5]: Leaving directory '/<>/prj/std/sps'
make[5]: Entering directory '/<>/prj/std/tls'
make[6]: Entering directory '/<>/prj/std/tls/src'
make[6]: Leaving directory '/<>/prj/std/tls/src'
make[5]: Leaving directory '/<>/prj/std/tls'
make[4]: Leaving directory '/<>/prj/std'
make[3]: Leaving directory '/<>/prj'
make[3]: Entering directory '/<>/tst'
make[4]: Entering directory '/<>/tst/ref'
make[4]: Leaving directory '/<>/tst/ref'
make[4]: Entering directory '/<>/tst/mod'
make[4]: Leaving directory '/<>/tst/mod'
make[3]: Leaving directory '/<>/tst'
make[3]: Entering directory '/<>/exp'
make[4]: Entering directory '/<>/exp/ref'
make[4]: Leaving directory '/<>/exp/ref'
make[4]: Entering directory '/<>/exp/api'
make[4]: Leaving directory '/<>/exp/api'
make[4]: Entering directory '/<>/exp/prj'
make[5]: Entering directory '/<>/exp/prj/amd'
make[6]: Entering directory '/<>/exp/prj/amd/src'
make[7]: Entering directory '/<>/exp/prj/amd/src/app'
make[7]: Leaving directory '/<>/exp/prj/amd/src/app'
make[7]: Entering directory '/<>/exp/prj/amd/src/tst'
make[7]: Leaving directory '/<>/exp/prj/amd/src/tst'
make[6]: Leaving directory '/<>/exp/prj/amd/src'
make[6]: Entering directory '/<>/exp/prj/amd/doc'
make[6]: Leaving directory '/<>/exp/prj/amd/doc'
make[5]: Leaving directory '/<>/exp/prj/amd'
make[4]: Leaving directory '/<>/exp/prj'
make[3]: Leaving directory '/<>/exp'
make[3]: Entering directory '/<>/doc'
make[4]: Entering directory '/<>/doc/dtd'
make[4]: Leaving directory '/<>/doc/dtd'
make[4]: Entering directory '/<>/doc/etc'
make[4]: Leaving directory '/<>/doc/etc'
make[4]: Entering directory '/<>/doc/xml'
make[5]: Entering directory '/<>/doc/xml/eul'
make[5]: Leaving directory '/<>/doc/xml/eul'
make[5]: Entering directory '/<>/doc/xml/vol'
make[6]: Entering directory '/<>/doc/xml/vol/vol-0'
make[6]: Leaving directory '/<>/doc/xml/vol/vol-0'
make[6]: Entering directory '/<>/doc/xml/vol/vol-1'
make[6]: Leaving directory '/<>/doc/xml/vol/vol-1'
make[6]: Entering directory '/<>/doc/xml/vol/vol-2'
make[6]: Leaving directory '/<>/doc/xml/vol/vol-2'
make[5]: Leaving directory '/<>/doc/xml/vol'
make[4]: Leaving directory '/<>/doc/xml'
make[3]: Leaving directory '/<>/doc'
make[3]: Entering directory '/<>/etc'
make[3]: Leaving directory '/<>/etc'
make[2]: Leaving directory '/<>'
rm -rf bld
dh_clean
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
./cnf/bin/afnix-setup -o --prefix=/usr
afnix-setup: cannot find compiler file error: cannot fin

Bug#941957: marked as done (check-manifest: needs a source-only upload)

[Debian Bug Tracking System]

Your message dated Wed, 9 Oct 2019 00:58:34 +0100
with message-id 
and subject line re: check-manifest: needs a source-only upload
has caused the Debian Bug report #941957,
regarding check-manifest: needs a source-only upload
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.)


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

Package: check-manifest
Version: 0.39-1
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing, please make a source-only upload so your package can migrate.
--- End Message ---
--- Begin Message ---

Version: 0.39-2

A source-only upload has now been made, thanks.--- End Message ---

Bug#941837: marked as done (texlive-fonts-extra: file conflice with (older) texlive-fonts-extra-links)

[Debian Bug Tracking System]

Your message dated Wed, 09 Oct 2019 00:27:52 +
with message-id 
and subject line Bug#941837: fixed in texlive-extra 2019.20190930-3
has caused the Debian Bug report #941837,
regarding texlive-fonts-extra: file conflice with (older) 
texlive-fonts-extra-links
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.)


-- 
941837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941837
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-fonts-extra
Version: 2019.20190930-2
Severity: serious

Hi,

when upgrading in Debian testing I saw the following error message:

+---
| Unpacking texlive-fonts-extra (2019.20190930-2) over (2019.20190830-1) ...
| dpkg: error processing archive 
/tmp/apt-dpkg-install-h6VDTu/50-texlive-fonts-extra_2019.20190930-2_all.deb 
(--unpack):
|  trying to overwrite 
'/usr/share/texlive/texmf-dist/fonts/opentype/arkandis/berenisadf/BerenisADFProSC-Bold.otf',
 which is also in package texlive-fonts-extra-links 2019.20190830-1
| dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
+---

It looks like texlive-fonts-extra is missing a (versioned) Replaces on
texlive-fonts-extra-links.

Thanks for maintaining LaTeX in Debian,
Ansgar

-- Package-specific info:

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores)
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)

Versions of packages texlive-fonts-extra depends on:
it  tex-common6.12
ii  texlive-base  2019.20190930-1

Versions of packages texlive-fonts-extra recommends:
ii  fonts-adf-accanthis0.20190904-1.1
ii  fonts-adf-berenis  0.20190904-1.1
ii  fonts-adf-gillius  0.20190904-1.1
ii  fonts-adf-universalis  0.20190904-1.1
ii  fonts-cabin1.5-2
ii  fonts-comfortaa3.001-2
ii  fonts-croscore 20181227-1
ii  fonts-crosextra-caladea20130214-2
ii  fonts-crosextra-carlito20130920-1
ii  fonts-dejavu-core  2.37-1
ii  fonts-dejavu-extra 2.37-1
ii  fonts-ebgaramond   0.016-1
ii  fonts-ebgaramond-extra 0.016-1
ii  fonts-font-awesome 5.0.10+really4.7.0~dfsg-1
ii  fonts-freefont-otf 20120503-9
ii  fonts-freefont-ttf 20120503-9
ii  fonts-gfs-artemisia1.1-5
ii  fonts-gfs-complutum1.1-6
ii  fonts-gfs-didot1.1-6
ii  fonts-gfs-neohellenic  1.1-6
ii  fonts-gfs-olga 1.1-5
ii  fonts-gfs-solomos  1.1-5
ii  fonts-go   0~20170330-1
ii  fonts-junicode 1.002-1
ii  fonts-lato 2.0-2
ii  fonts-linuxlibertine   5.3.0-4
ii  fonts-lobstertwo   2.0-2
ii  fonts-noto-hinted  20181227-1
ii  fonts-noto-mono20181227-1
ii  fonts-oflb-asana-math  000.907-6
ii  fonts-open-sans1.11-1
ii  fonts-roboto-unhinted  2:0~20170802-3
ii  fonts-sil-gentium  20081126:1.03-2
ii  fonts-sil-gentium-basic1.102-1
ii  fonts-sil-gentiumplus  5.000-2
ii  fonts-sil-gentiumplus-compact  5.000-2
ii  fonts-stix 1.1.1-4
iu  texlive-fonts-extra-links  2019.20190930-2
ii  texlive-fonts-recommended  2019.20190930-1
iu  texlive-latex-extra2019.20190930-2

Versions of packages texlive-fonts-extra suggests:
ii  cm-super 0.3.4-15
iu  texlive-fonts-extra-doc  2019.20190930-2

Versions of packages tex-common depends on:
ii  dpkg  1.19.7
ii  ucf   3.0038+nmu1

Versions of packages tex-common suggests:
ii  debhelper  12.6.1

Versions of packages texlive-fonts-extra is related to:
it  tex-common6.12
ii  texlive-binaries  2019.20190605.51237-3

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2019.20190930-3

We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 repo

Processed: found 941888 in 1.4~bzr32-1, tagging 941888, found 941376 in 1.1-9, tagging 941376 ...

[Debian Bug Tracking System]

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

> found 941888 1.4~bzr32-1
Bug #941888 [qtqr] python-zbar: requires libzbar0 (= 0.22-1) but installed 
libzbar0 is 0.23-1.1+b1
Marked as found in versions qr-tools/1.4~bzr32-1.
> tags 941888 + sid bullseye
Bug #941888 [qtqr] python-zbar: requires libzbar0 (= 0.22-1) but installed 
libzbar0 is 0.23-1.1+b1
Added tag(s) bullseye and sid.
> found 941376 1.1-9
Bug #941376 [src:monotone] Should monotone be removed?
Marked as found in versions monotone/1.1-9.
> tags 941376 + sid
Bug #941376 [src:monotone] Should monotone be removed?
Added tag(s) sid.
> found 933424 1.0.3-5.1
Bug #933424 [sitplus] sitplus: Please rebuild against wxWidgets GTK 3 package
Marked as found in versions sitplus/1.0.3-5.1.
> tags 933424 + sid bullseye
Bug #933424 [sitplus] sitplus: Please rebuild against wxWidgets GTK 3 package
Added tag(s) sid and bullseye.
> tags 923190 + sid bullseye
Bug #923190 {Done: Jonathan McDowell } [ghdl] ghdl: Allow 
building against LLVM 8
Added tag(s) sid and bullseye.
> tags 940163 + sid bullseye
Bug #940163 {Done: Kartik Mistry } [src:dee] dee: FTBFS with 
GLib 2.62: uses deprecated G_TYPE_INSTANCE_GET_PRIVATE with -Werror
Added tag(s) bullseye and sid.
> tags 940164 + sid bullseye
Bug #940164 [src:bamf] bamf: FTBFS with GLib 2.62: uses deprecated 
G_TYPE_INSTANCE_GET_PRIVATE with -Werror
Added tag(s) sid and bullseye.
> tags 941514 + sid bullseye
Bug #941514 [cffi] cffi: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941522 + sid bullseye
Bug #941522 [gawk-doc] gawk-doc: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941523 + sid bullseye
Bug #941523 [geomview] geomview: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941524 + sid bullseye
Bug #941524 [gitmagic] gitmagic: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) sid and bullseye.
> found 941527 3.0.2-2
Bug #941527 [src:matplotlib] Build-depends on Qt4
Marked as found in versions matplotlib/3.0.2-2.
> tags 941527 + sid bullseye
Bug #941527 [src:matplotlib] Build-depends on Qt4
Added tag(s) bullseye and sid.
> tags 941525 + sid bullseye
Bug #941525 [gnu-standards] gnu-standards: build-depend on 
texlive-plain-generic, not obsolete texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941528 + sid bullseye
Bug #941528 [goldencheetah] goldencheetah: build-depend on 
texlive-plain-generic, not obsolete texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941513 + sid bullseye
Bug #941513 [c-graph] c-graph: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941534 + sid bullseye
Bug #941534 [khronos-api] khronos-api: build-depend on texlive-plain-generic, 
not obsolete texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941535 + sid bullseye
Bug #941535 [libforms] libforms: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941537 + sid bullseye
Bug #941537 [lilypond] lilypond: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941539 + sid bullseye
Bug #941539 [mh-e] mh-e: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941540 + sid bullseye
Bug #941540 [moon-buggy] moon-buggy: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941541 + sid bullseye
Bug #941541 [nbconvert] nbconvert: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941546 + sid bullseye
Bug #941546 [sdcc] sdcc: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941548 + sid bullseye
Bug #941548 [sgf2dg] sgf2dg: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941555 + sid bullseye experimental
Bug #941555 [yosys] yosys: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
Added tag(s) sid, bullseye, and experimental.
> tags 941553 + sid bullseye
Bug #941553 {Done: Vincent Bernat } [xnee] xnee: 
build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended
Added tag(s) bullseye and sid.
> tags 941542 + sid bullseye
Bug #941542 [ngspice] ngspice: build-depend on texlive-plain-generic, not 
obsolete texlive-generic-recommended
Added tag(s) sid and bullseye.
> tags 941545 + sid bullseye
Bug #941545 {Done: Georges Khaznadar } [pycode-browser] 
pycode-browser: build-depend on texlive-plain-generic, not obsolete 
texlive-generic-recommended
Added tag(s) sid and bull

Processed: found 941531 in 2.6.0-3, tagging 885267

[Debian Bug Tracking System]

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

> found 941531 2.6.0-3
Bug #941531 {Done: Dirk Eddelbuettel } [gsl-doc] gsl-doc: 
build-depend on texlive-plain-generic, not obsolete texlive-generic-recommended
There is no source info for the package 'gsl-doc' at version '2.6.0-3' with 
architecture ''
Unable to make a source version for version '2.6.0-3'
Marked as found in versions 2.6.0-3 and reopened.
> tags 885267 + sid bullseye experimental
Bug #885267 [src:coccinelle] coccinelle: Depends on unmaintained pygtk
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Bug#941880: marked as done (gnome-shell-extension-easyscreencast: Depends on gnome-shell << 3.33)

[Debian Bug Tracking System]

Your message dated Wed, 09 Oct 2019 00:49:27 +
with message-id 
and subject line Bug#941880: fixed in gnome-shell-extension-easyscreencast 
1.0.2+git20191008-1
has caused the Debian Bug report #941880,
regarding gnome-shell-extension-easyscreencast: Depends on gnome-shell << 3.33
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.)


-- 
941880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-shell-extension-easyscreencast
Version: 1.0.2-2
Severity: serious

gnome-shell-extension-easyscreencast depends on gnome-shell << 3.33
but gnome-shell 3.34 is in Unstable.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-easyscreencast
Source-Version: 1.0.2+git20191008-1

We believe that the bug you reported is fixed in the latest version of
gnome-shell-extension-easyscreencast, 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.
Samuel Henrique  (supplier of updated 
gnome-shell-extension-easyscreencast 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, 09 Oct 2019 01:11:28 +0100
Source: gnome-shell-extension-easyscreencast
Architecture: source
Version: 1.0.2+git20191008-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Samuel Henrique 
Closes: 941880
Changes:
 gnome-shell-extension-easyscreencast (1.0.2+git20191008-1) unstable; 
urgency=medium
 .
   * New upstream version 1.0.2+git20191008
   * Bump Standards-Version to 4.4.1
   * d/control: Update Dependency's version requirement (closes: #941880)
   * d/p/makefile.patch: Update patch
   * d/p/deprecations.patch: Add patch in PR state upstream for 3.30+ support
   * d/p/supported-gnome-versions.patch: New patch to update supported versions
   * d/p/value-changed.patch: New patch for gnome 3.34 support
Checksums-Sha1:
 393c11a5328e15c90472355e4c92e5dc49220d49 2392 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1.dsc
 82d31fc11779dc46171faf803027d9d2172cc4fe 254182 
gnome-shell-extension-easyscreencast_1.0.2+git20191008.orig.tar.gz
 904f9448cebbf0b5dedec33604ad848ca50e657e 4932 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1.debian.tar.xz
 bc5375ffe210da2964cc4120bb921dc2e1d89df4 6098 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1_amd64.buildinfo
Checksums-Sha256:
 8eff3501003cb2bd868a36cabbb1d83106e4f07cabca31e8fa4e99eda8d16e00 2392 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1.dsc
 f8cc709ddf779404f0a852733a92c67dcb690ca99c4f301ef5fff1eec3197f60 254182 
gnome-shell-extension-easyscreencast_1.0.2+git20191008.orig.tar.gz
 a1ee06133872862586d7f3204560573f43ec5c1829f707e57c5bde328ebdf2e4 4932 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1.debian.tar.xz
 6d2a59a11f4bde95f011327be40b571dcfd4809ad95454d4dc1a8bac87e435e7 6098 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1_amd64.buildinfo
Files:
 60e1b8cb527daf080142cfcb3b31585c 2392 gnome optional 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1.dsc
 d7e212eac14c1155c73ea2fb3ee01b93 254182 gnome optional 
gnome-shell-extension-easyscreencast_1.0.2+git20191008.orig.tar.gz
 2541c855ffbd8f01aa2513df81e42195 4932 gnome optional 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1.debian.tar.xz
 e8a3cda1935aa48abf43a323144e9f09 6098 gnome optional 
gnome-shell-extension-easyscreencast_1.0.2+git20191008-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAl2dJgoACgkQu6n6rcz7
RwfjGBAAnJH7JJIb0r3PrDFE8hri12Tcx/4mcuSlPlv46Of5/RFYh86T9XMNrYtv
5qNEwEmrCY81PctLGJ5oZxiKgoIXTdX3cbQ3CPnnFMpfncjxX2jsbCSzv2k/fxVk
sb71D6rxiK4V+NzJqFIl6b2Yeoj4+Bu2o/nnvdfFVYfcm6Co0m9+dFVwxfjN3ySh
hf5BZdLOjrRrukg7LfljR29kjZC/7KvZyLPySODVxqdAEe7bZf8cbD+9ERPXQoZQ
kQM7KxQBB1I9ns72r9OgbIlTbLHvhkyY6NkZtt4pL70N3pcpHVrx3taj6ak7ZExD
h8pjuV/CiLOiyyXPpQ4Y7cqMM4NzKnjhEH4IMAvjmVqNOXocpCwGJbazJButeLKP
EKgmgIsOoUzVSf87G1PWSTSlG8lFgCuVj6pEo+QGJJ679Z0qDi5P5OQ6JuRwEhsx
+vDWPZRezE4u1R+CboO6xT50TUk7nbvpt5uyJiuDb6tPDaoR134YJcjTmUrDW+3k
HSBZZHqTLIS

Bug#941908: Latest upgrade to 3.34.0-2 solved this problem

[william l-k]

We had 5 computer affected by this problem. Every one of them booted
normally into the Gnome shell (one took two tries) after a full-
upgrade.

So as far as I can tell, this problem is solved.

Thanks for the hard work. One day after I submitted the report is
pretty good, even if the changes were made to fix a different bug.

Regards,
William

Bug#941908: marked as done (gnome: unable to start gnome-shell, cursor only with no login)

[Debian Bug Tracking System]

Your message dated Tue, 8 Oct 2019 21:42:39 -0400
with message-id 

and subject line Re: gnome: unable to start gnome-shell, cursor only with no 
login
has caused the Debian Bug report #941908,
regarding gnome: unable to start gnome-shell, cursor only with no login
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.)


-- 
941908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome
Version: 1:3.30+2
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

I would be shocked if only systems that I installed are having this problem. It
sure seems like any computer running gnome will break with one of the recent
updates...

Description:

I spend all weekend troubleshooting my sons laptop over the phone. We are all
on Debian testing. We also all had unattended upgrades running. His system is
barely working and needs to have a new installation. Switching to lxqt and ssdm
we were able to get a graphical environment, but there were freezes at times
that reisub couldn't solve requiring hard reset.

Problem: Instead of getting the authentication screen, the system has the
cursor appear (which moves around just fine so the system isn't frozen), but
never reaches a working gnome session. I have tried every suggestion regarding
similar past problems to no avail. We can reach a tty, but are unable to repair
the system without reverting to a prior snapshot (if it exists). Some of what I
tried:

General description of attempted solutions:

-looked for driver problem which is unlikely given the large differences in set
ups between affected machines.

-  pam-auth-update --force
  systemctl restart gdm3

-manually removed /var/lib/gdm/.ICEauthority

-tried wayland=true and wayland=false

-purged the gnome destop and reinstalled. Same problem.

I suspect that reinstalling debian testing running gnome won't help him IF he
upgrades to the current version of whatever is killing gnome.

Other affected machines:

On Saturday, the same thing happened to my laptop. I had a recent snapshot and
restored. Once the merge completed, I took a new snapshot, upgraded, and
recreated the problem. Are laptops are not alike. He has a newer Lenova whereas
I have an older toshiba. His is running an intel chip, whereas mine is running
amd. Both have hdds.

Our entertainment center / home server has a phenom with a seperate graphics
card and developed the same problem due to unattended upgrades. This system had
auto-login set up and is running off an lvm setup on two pairs of raid 1 disks.
After fixing it once and taking a new snapshot unattended-upgrades upgraded
some packages and did a scheduled reboot (2am). After reverting to the
snapshot, this time I couldn't get the system to boot. lvm manager isn't
available early in the session and I don't think grub knew how to handle a
merging snapshot on this setup. I was able to get a shell on root using an
install usb, and once I mounted the efi boot directory and home (probably
didn't need that) and ran update-grub the boot problem was solved.

Our file server running off of an old aspire netbook with an amd chip. Upgraded
and has the same problem. I don't know when that one experienced a problem
because I access the machine via ssh and rarely need to see the physical
machine.

I've been killing unattended upgrades on any other computer until this is
solved.

I was able to get some problem indications via email off of the unrepaired
computer:

Sample one:

Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:52 prisma minissdpd[839]: peer 10.5.6.235:6 is not from a LAN
Oct 05 23:43:51 prisma minissdpd[839]: peer 10.9.5.109:42606 is not from a LAN
Oct 05 23:43:51 prisma minissdpd[839]: peer 10.9.6.86:58553 is not from a LAN
Oct 05 23:43:51 prisma minissdpd[839]: pee

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

[Debian Bug Tracking System]

Your message dated Wed, 09 Oct 2019 03:49:34 +
with message-id 
and subject line Bug#941524: fixed in gitmagic 20160304-1.1
has caused the Debian Bug report #941524,
regarding gitmagic: 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.)


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

Hi Sebastien,

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 gitmagic-20160304/debian/control gitmagic-20160304/debian/control
--- gitmagic-20160304/debian/control2016-03-04 07:01:30.0 -0800
+++ gitmagic-20160304/debian/control2019-10-01 13:21:20.0 -0700
@@ -6,7 +6,7 @@
 Build-Depends-Indep: asciidoc,
  docbook-utils,
  gawk,
- texlive-generic-recommended,
+ texlive-plain-generic,
  texlive-lang-cyrillic,
  tidy,
  xmlto
--- End Message ---
--- Begin Message ---
Source: gitmagic
Source-Version: 20160304-1.1

We believe that the bug you reported is fixed in the latest version of
gitmagic, 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.
Joao Eriberto Mota Filho  (supplier of updated gitmagic 
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: Tue, 08 Oct 2019 23:17:08 -0300
Source: gitmagic
Architecture: source
Version: 20160304-1.1
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Badia 
Changed-By: Joao Eriberto Mota Filho 
Closes: 941524
Changes:
 gitmagic (20160304-1.1) unstable; urgency=medium
 .
   [ Joao Eriberto Mota Filho ]
   * Non-maintainer upload.
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 12.
   * debian/control:
   - Bumped Standards-Version to 4.4.1.
   - Changed build dependency texlive-generic-recommended to
 texlive-plain-generic. Thanks to Steve Langasek
 . (Closes: #941524)
   - Updated Vcs-Git field.
 .
   [ Ondřej Nový ]
   * Non-maintainer upload.
   * d/control: Fix wrong Vcs-Browser.
   * d/copyright: Use https protocol in Format field.
Checksums-Sha1:
 85c1fd5c62270907948f763f4dfcd04de2be42cb 1975 gitmagic_20160304-1.1.dsc
 58279a136a0b62c534253c086a10fe8fbcbf7c69 4848 
gitmagic_20160304-1.1.debian.tar.xz
 465e6cbd9022c085f1109d961af8924364b44ae2 5266 
gitmagic_20160304-1.1_source.buildinfo
Checksums-Sha256:
 4d6bf5dae6822d87820fd62d7149afa4b1a184e1dcc0fa6547eca37446fe872a 1975 
gitmagic_20160304-1.1.dsc
 ec579550dbd6bb8158d6f8140b8b88c5dfed1ba12d721817433e2450a0eaa142 4848 
gitmagic_20160304-1.1.debian.tar.xz
 159580623b87cabd727d6a84458147f61bb5273193743b2589de404bba7c8bce 5266 
gitmagic_20160304-1.1_source.buildinfo
Files:
 9a6460c6ba518501c5ad65dc5f9c1294 1975 doc optional gitmagic_20160304-1.1.dsc
 28fa381f544bfcd40652488e86638f2c 4848 doc optional 
gitmagic_20160304-1.1.debian.tar.xz
 b54aa181bdc85d4147dd701ecdf3f407 5266 doc optional 
gitmagic_20160304-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl2dVeIACgkQ3mO5xwTr
6e9TZA//RrTqTS8+w0SpEG7nrBHDVCcQ4CkwyqMeyCTxp3cO0Yzi1/GtqlKybRTh
W4f5EfBXt/b9WwLTqX+sVSmnYk/m/nV6e6upicMfIwNBiV1Odnnw58ETRGwWH968
DuUqwqFWMPQ9VirPGYEOV9vb30rd75dBF/7v05Owx9G0qXJHj2mP6EjrVXkNgU62