Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

[Vincent Bernat]

Package: network-manager
Followup-For: Bug #947613

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hey!

I've got the same problem. Comparing the output of "journalctl -u
NetworkManager" on both versions, the only difference I am able to
spot is that with 1.22.2-1, I have these lines:

déc. 29 07:30:48 zoro NetworkManager[1333]:   [1577601048.8881] dhcp4 
(wlp3s0): activation: beginning transaction (timeout in 45 seconds)
déc. 29 07:30:48 zoro NetworkManager[1333]:   [1577601048.8938] dhcp4 
(wlp3s0): state changed unknown -> fail

While in 1.22.0-2, I have:

déc. 29 07:44:13 zoro NetworkManager[5959]:   [1577601853.3663] dhcp4 
(wlp3s0): activation: beginning transaction (timeout in 45 seconds)
déc. 29 07:44:13 zoro NetworkManager[5959]:   [1577601853.3860] dhcp4 
(wlp3s0): option dhcp_lease_time  => '86400'
déc. 29 07:44:13 zoro NetworkManager[5959]:   [1577601853.3863] dhcp4 
(wlp3s0): option domain_name  => 'home'
[...]

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

Kernel: Linux 5.4.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager depends on:
ii  adduser3.118
ii  dbus   1.12.16-2
ii  init-system-helpers1.57
ii  libaudit1  1:2.8.5-2+b1
ii  libbluetooth3  5.50-1+b1
ii  libc6  2.29-6
ii  libcurl3-gnutls7.67.0-2
ii  libglib2.0-0   2.62.3-2
ii  libgnutls303.6.11.1-2
ii  libjansson42.12-1
ii  libmm-glib01.10.4-0.1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.21-4
ii  libnm0 1.22.0-2
ii  libpam-systemd 244-3
ii  libpolkit-agent-1-00.105-26
ii  libpolkit-gobject-1-0  0.105-26
ii  libpsl50.20.2-2
ii  libreadline8   8.0-3
ii  libselinux13.0-1
ii  libsystemd0244-3
ii  libteamdctl0   1.29-1
ii  libudev1   244-3
ii  libuuid1   2.34-0.1
ii  policykit-10.105-26
ii  udev   244-3
ii  wpasupplicant  2:2.9-3+b1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1.1
ii  iptables 1.8.4-1
ii  modemmanager 1.10.4-0.1
ii  ppp  2.4.7-2+4.1+b1

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2
ii  libteam-utils1.29-1

- -- Configuration Files:
/etc/NetworkManager/NetworkManager.conf changed:
[main]
plugins=ifupdown,keyfile
dns=dnsmasq
monitor-connection-files=true
[keyfile]
unmanaged-devices=interface-name:docker0
[ifupdown]
managed=false


- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEErvI0h2bzccaJpzYAlaQv6DU1JfkFAl4IUSMSHGJlcm5hdEBk
ZWJpYW4ub3JnAAoJEJWkL+g1NSX54w0QAJCyATfvRu6DwWwZE1xvF4xnCFaPAbhl
90iLRubdSb8vBcU7Z5l1A1dtqndFdrx5mbs+iZmwROA+fM71nWfN084iAIiA/tfl
CGVVY5ORlw/ZfcUwhk1MtABwIJVlxt05UoHvqHrgB3W1KTSOFw8oKISOFA3gcgUA
MRpwAPbwj0mjr8XW2l+7v/E+qcxDfO4B0wFu44udv+xRKBLaDjs3bUC3jXAidDgX
EoLfSjvmHwZYYy4yEMnp2jFeiu3En9eCdt6pqIiN0Qo3wcg4OJe/e3yd4RJo2Lsr
Bm3Gdu3IPjxlCZuDOKBcxWkxQpgKweguxxui1sUslUNFxFmvz3C4S+KB3WH33fYR
JsMzEbG/aGDUPC2V+U3qthaPLaw7nJh94JLRgVUBqhyefwIFmCr2j1Xg972QAUvY
5XT4tcRd6JBmVCdPD9gwaa6eRBHGqErQCr0sx+qKks6TGK3Y/CVMn2qqsInxo9uy
iuwqBjcQq6HqWUIvNXOhnZJy1gOCvMqATKyI/yPPa6Dbp+wTyC7dGZNuja1y1qVb
pf7Cl6z480qFqc5kbiN3dHh++yXFjlkLn4CR6aDqXkoDIREdb4LLP59E6+PpM6ax
kACEsbdgZKtfegd5TbWRubDUNtqx+q4N+XEQiEPpuUeP8wFjCpKZ2v8y7X5lsY89
4zCuQ8SydOMK
=c1Pt
-END PGP SIGNATURE-

Processed: notfound 947613 in 1.22.0-2, found 947613 in 1.22.2-1

[Debian Bug Tracking System]

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

> notfound 947613 1.22.0-2
Bug #947613 [network-manager] network-manager: Wi-Fi not working (does not get 
IPv4 address) with 1.22.2-1
No longer marked as found in versions network-manager/1.22.0-2.
> found 947613 1.22.2-1
Bug #947613 [network-manager] network-manager: Wi-Fi not working (does not get 
IPv4 address) with 1.22.2-1
Marked as found in versions network-manager/1.22.2-1.
> thanks
Stopping processing here.

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

Bug#947468: marked as done (php-twig: missing Build-Depends: php-symfony-string)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 06:34:31 +
with message-id 
and subject line Bug#947468: fixed in php-twig 3.0.1-1
has caused the Debian Bug report #947468,
regarding php-twig: missing Build-Depends: php-symfony-string
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.)


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

Hi,

php-twig/experimental FTBFS due to failing to load some includes in the
tests:

   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/php-twig-3.0.0'
phpunit
PHP Warning:  require_once(Symfony/Component/String/autoload.php): failed to 
open stream: No such file or directory in 
/build/php-twig-3.0.0/extra/string-extra/src/autoload.php on line 2
PHP Fatal error:  require_once(): Failed opening required 
'Symfony/Component/String/autoload.php' (include_path='.:/usr/share/php') in 
/build/php-twig-3.0.0/extra/string-extra/src/autoload.php on line 2
make[1]: *** [debian/rules:78: override_dh_auto_test] Error 255
make[1]: Leaving directory '/build/php-twig-3.0.0'
make: *** [debian/rules:7: build] Error 2


Andreas


php-twig_3.0.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: php-twig
Source-Version: 3.0.1-1

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

Debian distribution maintenance software
pp.
David Prévot  (supplier of updated php-twig 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: Sun, 29 Dec 2019 17:13:50 +1100
Source: php-twig
Architecture: source
Version: 3.0.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: David Prévot 
Closes: 946301 947468
Changes:
 php-twig (3.0.1-1) experimental; urgency=medium
 .
   [ Fabien Potencier ]
   * Prepare the 3.0.1 release
 .
   [ David Prévot ]
   * Add php-symfony-string build-dependency (Closes: #947468)
   * Update test dependencies
   * Set upstream metadata fields:
 Bug-Database, Repository, Repository-Browse, Bug-Submit
   * Breaks php-twig-extensions (Closes: #946301)
   * Ignore Intl testsuite for now
Checksums-Sha1:
 ae88604115a6428a4e6a2b47275adda4666a6943 2727 php-twig_3.0.1-1.dsc
 41395d4da90d7a6a3afbfd2d26575672e1d83b55 257978 php-twig_3.0.1.orig.tar.gz
 272beeafd01821d1b49c4ddf17cf25c9ef7db8b0 15132 php-twig_3.0.1-1.debian.tar.xz
 f101d4bcfce88824ce1cc130c6eb3b40b697fb92 12108 php-twig_3.0.1-1_amd64.buildinfo
Checksums-Sha256:
 e641d296274d17a7ba3e6408a07c015905f673d50eff2c79c52a24492271fd9f 2727 
php-twig_3.0.1-1.dsc
 34f24c8ee2132929a611d4eca75296ae0915569643a4332aa73f774e56029865 257978 
php-twig_3.0.1.orig.tar.gz
 9aa66f79fda8a312b28fbf0cce4bdb2c9f077a65329bab95f92fdd889b1e1f4d 15132 
php-twig_3.0.1-1.debian.tar.xz
 b36dbd166b35be0c4265b6aa8a259d016d30d3d807b172d5f43a6bc8ccd2a217 12108 
php-twig_3.0.1-1_amd64.buildinfo
Files:
 428490ebb67be025b7f20d07f70c6a39 2727 php optional php-twig_3.0.1-1.dsc
 30fa9c543dff0918a6cb2402e254ab1c 257978 php optional php-twig_3.0.1.orig.tar.gz
 812457d2d109fe713d210fb69aad12b4 15132 php optional 
php-twig_3.0.1-1.debian.tar.xz
 3adf37a9ae7f77e340bedffa50e674c5 12108 php optional 
php-twig_3.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFGBAEBCAAwFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAl4IRiYSHHRhZmZpdEBk
ZWJpYW4ub3JnAAoJEAWMHPlE9r08oL8H/ivYu7PUUWvCE15nunWhu7epCwcOfunh
n54Df8Pn027j7C3l6rLj2OFOOAiIYgbrillEf+ZizRNA21CA14T/fDECnNaW3qqD
aCdy1zduMu5gdsOk3pa9dmSBA1NgSMSRLKZGP0NRwsYlTKq0lMHt3mFKi+h1rQ5L
1WvBiXVz42RY+8b6vERm21XnHItzEUjSIqV9FFp+eYIDzbWpQDtpg8BHXNLfaDpe
aSzlJEHMdDNhOBpDo3Z/Sn1AqJn1KpH9DwAs0YpzCY+cBlZcDMkTS/t8Pyt1UzXW
mhUl1UDMYN/+ZrgArQQK6q3bQVbcKg5xWVYowbWIXJQx1ZVvrP8hL0U=
=w+pi
-END PGP SIGNATURE End Message ---

Bug#921904: Bug#946951: Bug#921904: win-iconv: FTBFS (wine: chdir to /tmp/wine-I6miLw/server-29-3583b06 : No such file or directory)

[Joe Nahmias]

On 12/27/2019 6:23 PM, Vincent Lefevre wrote:

On 2019-12-27 19:49:46 +, Joseph Nahmias wrote:

On Fri, Dec 27, 2019 at 07:27:42PM +, Joseph Nahmias wrote:

The attached patch works around the issue until that is fixed.


Of course, I forgot this patch... Take 2.


Wouldn't the use of wildcards be a security issue?

+   ln -s /tmp/.wine-`id -u`/server* /tmp/wine-*/

i.e. could you end up creating wrong symbolic links?


Attached is an updated patch that does the extra work to avoid the 
wildcards.



In any case, this seems rather ugly to me.


Not sure precisely what you are referring to as ugly here; but in my 
experience, band-aids are usually placed over something ugly, if that's 
what you mean... The proper fix would of course have to come from within 
wine itself.


--Joe
diff -Nru win-iconv-0.0.8/debian/changelog win-iconv-0.0.8/debian/changelog
--- win-iconv-0.0.8/debian/changelog2019-03-12 12:06:01.0 -0400
+++ win-iconv-0.0.8/debian/changelog2019-12-29 01:11:42.0 -0500
@@ -1,3 +1,12 @@
+win-iconv (0.0.8-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Work around #946951 by initializing WINEPREFIX and adding a symlink,
+closes: #921904.
+  * To speed up the build, don't install g++, only gcc is needed here.
+
+ -- Joe Nahmias   Sun, 29 Dec 2019 01:11:42 -0500
+
 win-iconv (0.0.8-3) unstable; urgency=medium
 
   * wrap-and-sort -ast
diff -Nru win-iconv-0.0.8/debian/control win-iconv-0.0.8/debian/control
--- win-iconv-0.0.8/debian/control  2019-03-12 12:06:01.0 -0400
+++ win-iconv-0.0.8/debian/control  2019-12-29 01:09:11.0 -0500
@@ -7,7 +7,7 @@
  debhelper-compat (= 12),
 Build-Depends-Indep:
  dpkg-dev (>= 1.17.14),
- mingw-w64,
+ gcc-mingw-w64,
  wine [i386 amd64]  ,
 Vcs-Git: https://salsa.debian.org/debian/win-iconv.git
 Vcs-Browser: https://salsa.debian.org/debian/win-iconv
diff -Nru win-iconv-0.0.8/debian/rules win-iconv-0.0.8/debian/rules
--- win-iconv-0.0.8/debian/rules2019-03-12 11:29:02.0 -0400
+++ win-iconv-0.0.8/debian/rules2019-12-29 01:03:56.0 -0500
@@ -3,11 +3,13 @@
 # we do not want stackprotector because there is no implementation on mingw32:
 export DEB_BUILD_MAINT_OPTIONS = hardening=-stackprotector
 
+DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
 ifeq ($(DEB_BUILD_ARCH),i386)
   TESTARCH=i686-w64-mingw32
 else ifeq ($(DEB_BUILD_ARCH), amd64)
   TESTARCH=x86_64-w64-mingw32
 endif
+export WINEPREFIX := $(CURDIR)/build-$(TESTARCH)/.wine
 
 %:
dh $@
@@ -30,9 +32,17 @@
  cd .. ; \
done
 
+override_dh_auto_test: T := $(CURDIR)/build-$(TESTARCH)/tmp
 override_dh_auto_test:
 ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 ifdef TESTARCH
-   cd build-$(TESTARCH) && WINEPREFIX=$(shell pwd)/build-$(TESTARCH)/.wine 
$(MAKE) CC=$(TESTARCH)-gcc AR=$(TESTARCH)-ar RANLIB=$(TESTARCH)-ranlib 
DLLTOOL=$(TESTARCH)-dlltool test
+   -wineboot -i
+   mkdir -p $(T)/`cat "${WINEPREFIX}/wineserver"`/
+   -ln -s /tmp/.wine-`id -u`/$$( \
+   printf "server-%x-%x" `stat --printf="%d %i" "${WINEPREFIX}"` \
+ ) $(T)/`cat "${WINEPREFIX}/wineserver"`/
+   $(MAKE) -C build-$(TESTARCH) CC=$(TESTARCH)-gcc AR=$(TESTARCH)-ar \
+   RANLIB=$(TESTARCH)-ranlib DLLTOOL=$(TESTARCH)-dlltool \
+   TMPDIR=$(T) test
 endif
 endif

Bug#945218: marked as done (moar segfaults during nqp build on mipsel)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 03:00:04 +
with message-id <20191229030004.GA12454@Macadamia>
and subject line fixed in 2019.11+dfsg-2
has caused the Debian Bug report #945218,
regarding moar segfaults during nqp build on mipsel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
945218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moarav
Version: 2019.07.1+dfsg-2
Severity: serious
Tags: ftbfs
Justification: ftbfs
Control: affects -1 nqp

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

The last upload of nqp failed to build on mipsel due to a segmentation fault in
/usr/bin/moar. Please investigate. This is holding back the migration of moarvm
to testing.

Paul

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

make[1]: Entering directory '/<>'
dh_auto_build
make -j1
make[2]: Entering directory '/<>'
mkdir -p -- 'gen/moar/stage1/gen'
'/usr/bin/perl' '/<>/tools/build/gen-cat.pl' moar stage1 
src/how/Archetypes.nqp src/how/RoleToRoleApplier.nqp 
src/how/NQPConcreteRoleHOW.nqp src/how/RoleToClassApplier.nqp 
src/how/NQPCurriedRoleHOW.nqp src/how/NQPParametricRoleHOW.nqp 
src/how/NQPClassHOW.nqp src/how/NQPNativeHOW.nqp src/how/NQPAttribute.nqp 
src/how/NQPModuleHOW.nqp src/how/EXPORTHOW.nqp  > 'gen/moar/stage1/nqpmo.nqp'
'/usr/bin/moar' --libpath=src/vm/moar/stage0 src/vm/moar/stage0/nqp.moarvm 
--bootstrap --setting=NULL --no-regex-lib --target=mbc --stable-sc=stage1 \
--output='gen/moar/stage1/nqpmo.moarvm' 'gen/moar/stage1/nqpmo.nqp'
Segmentation fault
make[2]: *** [Makefile:281: gen/moar/stage1/nqpmo.moarvm] Error 139
make[2]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make[1]: *** [debian/rules:18: override_dh_auto_build] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: build-arch] Error 2

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3WdBkACgkQnFyZ6wW9
dQrPLQgAwtvzw6J0t5+bkiGIJpECWAFn0qUJp6Fjk/xGZsxU3yKTrRLBMuXC1p2B
6gVK6lDH8Rs8SjCLgvko6ZuY7O7f40mIvazGIGYBGAqC0c3xxOnvabWMXmfoSRHo
w/I+YgQ5so7GYC3s94H6vs/UfZH2cmzJ7cASWk/sOQEDjjavLu7hcgTpHhUBmWPA
BdosodsYwiVqRkLsYtHRwFtep3MBl/l84Du5avHM/K4Jys+6MJt7Nsym+JRZeqTr
TlFxxGUKui8o6JcG9JnaaWnAZ8ZF4QT+vZvrmj5VWEbqWr+hjjtSxvPS8c/ZM7VO
b2KDSOIwN+Hy4NkarQiUm4+KzE9m7Q==
=NgCy
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 2019.11+dfsg-2--- End Message ---

Bug#947683: x2gothinclient-minidesktop: diversion removal misses '--rename'

[Andreas Beckmann]

Package: x2gothinclient-minidesktop
Version: 1.5.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies files from
another package in /usr. This is so wrong, I'm not even bothered to look
up the part of policy this violates ;-P

>From the attached log (scroll to the bottom...):

4m16.9s INFO: Warning: Package purging left files on system:
  /etc/systemd/system/display-manager.service -> 
/lib/systemd/system/lightdm.service not owned
  /etc/systemd/user/ owned by: systemd
  /usr/lib/x2go/ owned by: x2gothinclient-common
  /usr/lib/x2go/x2goclient   not owned
  /usr/share/applications/x2goclient.desktop.disabled-by-x2gotce not 
owned
  /usr/share/doc/perl-base/  owned by: perl-base
  /usr/share/fonts/opentype/ owned by: fonts-cantarell
  /usr/share/fonts/opentype/cantarell/   owned by: fonts-cantarell
  /var/lib/systemd/deb-systemd-user-helper-masked/   not owned

4m16.9s ERROR: FAIL: After purging files have disappeared:
  /usr/bin/x2goclientowned by: x2gothinclient-minidesktop, x2goclient
  /usr/lib/x86_64-linux-gnu/gio/ owned by: glib-networking:amd64, 
gvfs:amd64, dconf-gsettings-backend:amd64
  /usr/lib/x86_64-linux-gnu/gio/modules/ owned by: 
glib-networking:amd64, gvfs:amd64, dconf-gsettings-backend:amd64
  /usr/share/applications/x2goclient.desktop owned by: x2goclient

4m17.0s ERROR: FAIL: Installation and purging test.

The diversions are created with --rename, so the files are moved aside,
but diversion removal lacks --rename, and the files are not restored.


cheers,

Andreas


x2goclient=4.1.2.1-2_x2gothinclient-minidesktop=1.5.0.1-1.log.gz
Description: application/gzip

Bug#947673: marked as done (python3-pynvim: missing Breaks+Replaces: python3-neovim)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 02:44:44 +
with message-id 
and subject line Bug#947673: fixed in python-pynvim 0.4.0-4
has caused the Debian Bug report #947673,
regarding python3-pynvim: missing Breaks+Replaces: python3-neovim
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.)


-- 
947673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pynvim
Version: 0.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-pynvim_0.4.0-2_all.deb ...
  Unpacking python3-pynvim (0.4.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pynvim_0.4.0-2_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/neovim/__init__.py', 
which is also in package python3-neovim 0.3.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-pynvim_0.4.0-2_all.deb


cheers,

Andreas


python3-neovim=0.3.0-1_python3-pynvim=0.4.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-pynvim
Source-Version: 0.4.0-4

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

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated python-pynvim 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: Sat, 28 Dec 2019 21:13:57 -0500
Source: python-pynvim
Architecture: source
Version: 0.4.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: James McCoy 
Closes: 947673
Changes:
 python-pynvim (0.4.0-4) unstable; urgency=medium
 .
   * Declare python3-pyvim Breaks/Replaces python3-neovim.  (Closes: #947673)
Checksums-Sha1:
 fe51296cb9df739b729e10913bcf607fee393837 2535 python-pynvim_0.4.0-4.dsc
 d6643d18df7f01d397a5bffcbe2fa15720dad581 3772 
python-pynvim_0.4.0-4.debian.tar.xz
Checksums-Sha256:
 e374d1eba9ed7d9b1b167685b843d68c5e35283049f1ccbbb453bdc6423d4b51 2535 
python-pynvim_0.4.0-4.dsc
 80cdf28d0f5eabe359269a984ad9273db7a51a0edf5df9e511953ff822718729 3772 
python-pynvim_0.4.0-4.debian.tar.xz
Files:
 e1926db31cfdad520d68e7cac84ed88e 2535 python optional python-pynvim_0.4.0-4.dsc
 b24fc0e31fbba423700b272d3bc4a9bb 3772 python optional 
python-pynvim_0.4.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAl4IDb1fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu
QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9sapRAAy0oefImiKlQRKs4YNkU99gYzwWjU
jzozN5jDLH/kPDwTQZi1rpMqFcBTCHfJaX1RaBFk+Tc3Z9Y1mCeYZRHj8B52tuQB
k7GrOexwAOLH+1iTZH8P4IgR81p96/kKhodwEsPVZF5/tg62wEWqwmSKL4Yr5JrR
oOwip28hB0kfSzVi/ezxlEtRy+TxxalZp8Jb/BLnF8FN+6Mg7BXytwrd2BYGa1ub
FMhoStkYQGOTO2t/QVITOsq9YuBAfgAMJNTRs6WMrb2TNY1blTuzZ0fYeMajCnCH
DBbUedzK0NItVZ2fC8ZblAExeMEzTB2eZvhxMETGavoUpjY0q7ZC/MdswOGgd4/9
/5LtoLNF+MrSaM0PXS/xCc155IzEJaXYo/+MqiJQSFU35Frtqc83xdBqpj/L5OVQ
5tf1RJXC/x13s7g/1yZBMmtoR/KwJ4v7LNdT05b7e9G68X8j8n2Y1c5NGvbwa+EG
Os3WWeHMzk59RffQ0fgXlVUA7z/gAQTBTNF4twryaDAmarM+BgnosEovGJg7qskc
lFfafErqAicJQFit4moIZGPy7PFeAqSbwBP1+dIMsdngJh3OKm4BSY7bAzcYoO4u
XW8kJAu9Q1Q3Jdu0hzpVEda/gqpfW52JIhh+cf8eZDyFvsfeYarzZGcX34ZiW0ee
TmeqvcWgOMklYvM=
=R2xj
-END PGP SIGNATURE End Message ---

Bug#925803: marked as done (ploop: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 02:44:35 +
with message-id 
and subject line Bug#925803: fixed in ploop 1.15-7
has caused the Debian Bug report #925803,
regarding ploop: 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.)


-- 
925803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925803
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ploop
Version: 1.15-6
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/ploop_1.15-6_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 -j4 "INSTALL=install --strip-program=true" V=1
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>/include'
../gensym.sh libploop.h new-dynload.h
sed -e '1,/^struct ploop_functions {$/d' \
 -e '/\/\* struct ploop_functions \*\/$/,$d' dynload.h | \
grep -vE '^[[:space:]]*/\*.**/$' | \
grep -v '^  void \*padding\[' | \
sort > cur-dynload.h
diff -u cur-dynload.h new-dynload.h || \
( echo "*** API CHANGED, PLEASE UPDATE dynload.h"; exit 1 )
rm -f cur-dynload.h new-dynload.h
make[3]: Leaving directory '/<>/include'
make[3]: Entering directory '/<>/lib'
gcc -g -O0 -DDEBUG -g -O0 -DDEBUG -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I. -I../include 
-fno-strict-aliasing -Wall -Wstrict-prototypes -Werror -Wformat-security 
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Wdate-time 
-D_FORTIFY_SOURCE=2  -I. -I../include -fno-strict-aliasing -Wall 
-Wstrict-prototypes -Werror -Wformat-security -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/include/libxml2 -fPIC -fvisibility=hidden -M uuid.c delta_read.c 
delta_sysfs.c balloon_util.c check.c ploop.c xml.c logger.c balloon.c lock.c 
fsutils.c gpt.c crc32.c merge.c util.c pcopy.c ploop-copy.c di.c cleanup.c 
deprecated.c snapshot.c > .depend
gcc -g -O0 -DDEBUG -g -O0 -DDEBUG -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I. -I../include 
-fno-strict-aliasing -Wall -Wstrict-prototypes -Werror -Wformat-security 
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Wdate-time 
-D_FORTIFY_SOURCE=2  -I. -I../include -fno-strict-aliasing -Wall 
-Wstrict-prototypes -Werror -Wformat-security -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/include/libxml2 -fPIC -fvisibility=hidden -c uuid.c -o uuid.o
gcc -g -O0 -DDEBUG -g -O0 -DDEBUG -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I. -I../include 
-fno-strict-aliasing -Wall -Wstrict-prototypes -Werror -Wformat-security 
-D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Wdate-time 
-D_FORTIFY_SOURCE=2  -I. -I../include -fno-strict-aliasing -Wall 
-Wstrict-prototypes -Werror -Wformat-security -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64  -Wdate-time -D_FORTIFY_SOURCE=2  
-I/usr/include/libxml2 -fPIC -fvisibility=hidden -c delta_read.c -o delta_read.o
gcc -g -O0 -DDEBUG -g -O0 -DDEBUG -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -I. -I../include 
-fno-strict-aliasing -Wall -Wstrict-prototypes -Werror 

Bug#945423: marked as done (duplicity fails tests with Python 3.8)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 02:43:00 +
with message-id 
and subject line Bug#945423: fixed in duplicity 0.8.08-1
has caused the Debian Bug report #945423,
regarding duplicity fails tests with Python 3.8
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.)


-- 
945423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:duplicity
Version: 0.8.07-1
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.8

duplicity fails tests with Python 3.8, all architectures:

[...]
testing/unit/test_diffdir.py::DDTest::test_dirdelta_write_sig
  /<>/duplicity/librsync.py:232: DeprecationWarning:
PY_SSIZE_T_CLEAN will be required for '#' formats
eof, len_buf_read, cycle_out = self.sig_maker.cycle(self.buffer)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
= 10 failed, 410 passed, 10 skipped, 2628 warnings in 1288.64 seconds ==
/usr/lib/python3/dist-packages/setuptools/dist.py:472: UserWarning: Normalizing
'0.8.07' to '0.8.7'
  warnings.warn(
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:5: build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: duplicity
Source-Version: 0.8.08-1

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

Debian distribution maintenance software
pp.
Alexander Zangerl  (supplier of updated duplicity package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 29 Dec 2019 11:43:53 +1000
Source: duplicity
Architecture: source
Version: 0.8.08-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Zangerl 
Changed-By: Alexander Zangerl 
Closes: 945423
Changes:
 duplicity (0.8.08-1) unstable; urgency=medium
 .
   * new upstream release
   * upstream has disabled the test suite (closes: #945423)
Checksums-Sha1:
 2b703c15c862b64bfb4fd2d05bd927b52617c342 2045 duplicity_0.8.08-1.dsc
 7fdd1fd17821c48ffe5cd6230f4fc41b841d9e6d 1853805 duplicity_0.8.08.orig.tar.gz
 1f6e6bb970938c2680bef0b131eb9da1ea8fbb53 17256 duplicity_0.8.08-1.debian.tar.xz
 cdc63e20608dfc51e7804eba53b0a541d5460478 9536 
duplicity_0.8.08-1_amd64.buildinfo
Checksums-Sha256:
 2b1e31881863cc51ad176e669e6cd1678239c281a7d621525feb13f608e2e42c 2045 
duplicity_0.8.08-1.dsc
 0917e9ee23f9befad4d2819e42f5c6e8a2a2c7052f9e0a625b8278c8ac9e3df2 1853805 
duplicity_0.8.08.orig.tar.gz
 a56ab251942efb1c358bc7a195072675652346a8b995589c3fdd1dd3201c14ee 17256 
duplicity_0.8.08-1.debian.tar.xz
 567cb41ad82dbdf975d1dbc2d5cb68c919e36c73b3b0172c7e209a51351d041e 9536 
duplicity_0.8.08-1_amd64.buildinfo
Files:
 dad91265c62761588cc0b7f597d6ac47 2045 utils optional duplicity_0.8.08-1.dsc
 9012ed07ded291935927c701288177d8 1853805 utils optional 
duplicity_0.8.08.orig.tar.gz
 f43feb6847d735639fdf8639298a5259 17256 utils optional 
duplicity_0.8.08-1.debian.tar.xz
 c38e5ab27d9b73eff1d367db9cdcb5b7 9536 utils optional 
duplicity_0.8.08-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJeCAvrAAoJED06g4g30PqNFKgQAJCAOS7l1ELFEHTqv3JycSFi
T2slKMPKaB1wHRFzZpVuARt68jIoMOVjKAimyU+bQ+GfdnOlrcLmYmeV1bOm+mbw
+urLuJ94b3DJ/UENva3SxZANV6sBjZnz/REdURQjKtwbNprrAn9WYIMdbuqXwJFu
6FBWnzHt4uKvoGrxrQuHNJq9dYPWyvc/71ukjIM3rtYmUeVADoOmF9ZmMnJwWARF
yMQwU3B8gZt4PEX4TFG0G9rbQjBYDQiUr4bWmfnwtfs62JrC6n+4E4Aj0y+JmpCo
SxUH+6wSkBKAr9+PbVcrgUKMVWyGSbql9Ht2j0ga8rkgYboYzd1WiuWQad7rJZzN
ulgGPfgCxOD4qOOUogSI5wbflcHU04CxFIz42/mZNjIAwNpsuIS+BfvJrWJT33l+
tcQz5uXN3OFJtzPMqhPi2+L/7eovoFPJYLjLwau4qOhXK1TIq+CElc1ER3SNWcY4
Is1jmL5DCWOiQex+3mOsFXQm5Xtj1ZunOLMBCyN8sWOlDeOep5pu4YvsXa42Dt+L
tb12RPhEcza8VkLykneR0UEw05RJUnH3RD7HKnk0BOu40eh9szEjwkRpYNiHeZOr
zFbeVobkTxSX5cDMWc+F8Rv6fcDCFrV70f28iPtVvDwYVwEAxXKBUFlxFKF/O3eJ
KoVgECfBGrlvvNSBkR8Q
=YhdR
-END PGP SIGNATURE End Message ---

Bug#947681: libspring-java: build-depends on no longer available libjasperreports-java

[Andreas Beckmann]

Source: libspring-java
Version: 4.3.23~git20190308-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

libspring-java/experimental build-depends on the removed package
libjasperreports-java.


Andreas

Processed: Tag

[Debian Bug Tracking System]

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

> tag 947678 ftbfs
Bug #947678 [src:mlt] FTBFS: /usr/bin/ld: cannot find -lGL
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Tag

[Debian Bug Tracking System]

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

> tag 947679 ftbfs
Bug #947679 [src:qsynth] qsynth: FTBFS on s390x: lrelease error: Parse error 
... qsynth_sr.ts:734:29: Premature end of document.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

[Lisandro Damián Nicanor Pérez Meyer]

Source: qsynth
Version: 0.6.0-1
Severity: serious
Justification: FTBFS on s390x

Hi! Your package failed to build from source on s390x with the following error:

lrelease error: Parse error at src/translations/qsynth_sr.ts:734:29: Premature 
end of document.
make[1]: *** [Makefile:102: src/translations/qsynth_sr.qm] Error 1

The full build log can be found at:

https://buildd.debian.org/status/fetch.php?pkg=qsynth=s390x=0.6.0-1=1576518180=0

It is posible that the error might be solved with a give back.

Kinds regards, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#947678: FTBFS: /usr/bin/ld: cannot find -lGL

[Lisandro Damián Nicanor Pérez Meyer]

Source: mlt
Version: 6.18.0-3
Severity: serious
Justification: FTBFS on all archs

Hi! Your package failed to build form source on all archs:



The error seems to be:

g++ -shared -o ../libmltopengl.so factory.o consumer_xgl.o 
filter_glsl_manager.o filter_movit_blur.o filter_movit_convert.o 
filter_movit_crop.o filter_movit_deconvolution_sharpen.o 
filter_movit_diffusion.o filter_movit_flip.o filter_movit_glow.o 
filter_movit_lift_gamma_gain.o filter_movit_mirror.o filter_movit_opacity.o 
filter_movit_rect.o filter_movit_resample.o filter_movit_resize.o 
filter_movit_saturation.o filter_movit_vignette.o filter_movit_white_balance.o 
mlt_movit_input.o transition_movit_luma.o transition_movit_mix.o 
transition_movit_overlay.o -L../../framework -lmlt -lm -Wl,-z,relro -Wl,-z,now 
-Wl,--no-undefined -Wl,--as-needed -Wl,--no-undefined -Wl,--as-needed 
-Wl,--no-undefined -Wl,--as-needed -L../../mlt++ -lmlt++ -lmovit -lepoxy 
-lpthread -lGL -lX11
/usr/bin/ld: cannot find -lGL
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:61: ../libmltopengl.so] Error 1
make[3]: Leaving directory '/<>/src/modules/opengl'

Thanks for your work, Lisandro.

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

Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: notfound 947492 in kdiagram/2.6.1-1+b1, found 947492 in 2.6.1-1, tagging 947492, tagging 947490 ...

[Debian Bug Tracking System]

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

> notfound 947492 kdiagram/2.6.1-1+b1
Bug #947492 [src:kdiagram] FTBFS: on mips64el and mipsel: tests failing
The source kdiagram and version 2.6.1-1+b1 do not appear to match any binary 
packages
No longer marked as found in versions kdiagram/2.6.1-1+b1.
> found 947492 2.6.1-1
Bug #947492 [src:kdiagram] FTBFS: on mips64el and mipsel: tests failing
Marked as found in versions kdiagram/2.6.1-1.
> tags 947492 + sid bullseye
Bug #947492 [src:kdiagram] FTBFS: on mips64el and mipsel: tests failing
Added tag(s) bullseye and sid.
> tags 947490 + sid bullseye
Bug #947490 [src:kadu] FTBFS: CMake can't find X11
Added tag(s) sid and bullseye.
> tags 947513 + sid bullseye
Bug #947513 [src:luakit] luakit: build-depends on obsolete libunique-dev
Added tag(s) sid and bullseye.
> tags 885815 - buster
Bug #885815 [fcitx-config-gtk2] fcitx-configtool-gtk2: Depends on libunique
Removed tag(s) buster.
> tags 947514 + sid bullseye
Bug #947514 [src:midori] midori: build-depends on obsolete libunique-dev
Added tag(s) sid and bullseye.
> tags 947516 + sid bullseye
Bug #947516 {Done: Benjamin Barenblat } 
[src:transmission-remote-gtk] transmission-remote-gtk: build-depends on 
obsolete libunique-dev
Added tag(s) bullseye and sid.
> tags 947515 + sid bullseye
Bug #947515 {Done: Ricardo Mones } [src:quitcount] quitcount: 
build-depends on obsolete libunique-dev
Added tag(s) bullseye and sid.
> tags 947518 + sid bullseye
Bug #947518 [casparcg-server] casparcg-server: FTBFS: xf86vmode library not 
found - required for GLFW
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
885815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885815
947490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947490
947492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947492
947513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947513
947514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947514
947515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947515
947516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947516
947518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#875250: marked as done ([scim] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 00:06:18 +
with message-id 
and subject line Bug#875250: fixed in scim 1.4.18-2.2
has caused the Debian Bug report #875250,
regarding [scim] Future Qt4 removal from Buster
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.)


-- 
875250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scim
Version: 1.4.18-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: scim
Source-Version: 1.4.18-2.2

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
scim 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: Sat, 28 Dec 2019 20:45:08 -0300
Source: scim
Architecture: source
Version: 1.4.18-2.2
Distribution: unstable
Urgency: medium
Maintainer: Rolf Leggewie 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875250 875258
Changes:
 scim (1.4.18-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload. I took just one part of Tz-Hua's merge request
 because there was already an NMU in the archive. See #875250 for more
 details.
 .
   [ Tz-Huan Huang ]
   * Disable qt-immodules build. Closes: #875258, Closes: #875250
Checksums-Sha1:
 b2379a64f7e2deab1e7881968d8552f0d666efb6 2639 scim_1.4.18-2.2.dsc
 6d37c345dba0ad668d375bcb71f86054f5d5d512 27692 scim_1.4.18-2.2.debian.tar.xz
 3634ec5730099fe65afd0b25790d2087395e5a85 6680 scim_1.4.18-2.2_source.buildinfo
Checksums-Sha256:
 f12baf70ea5f3e185efbeab8d0f1ddea403a1f5b68d0443d328ac2e1de2dd21e 2639 
scim_1.4.18-2.2.dsc
 eedd10e878d4332650c7864cd102e570799a229b5392adf369740f199980fe20 27692 
scim_1.4.18-2.2.debian.tar.xz
 5db0c875a960d7bc1fb205f8f210b9f9c8272a8fa137870f7f1426b46e5382ba 6680 
scim_1.4.18-2.2_source.buildinfo
Files:
 914165b7f2d6a191cb119fb7945bb21a 2639 utils optional scim_1.4.18-2.2.dsc
 8cafeb99aa0e36f6dc3b069bf3fee03c 27692 utils optional 
scim_1.4.18-2.2.debian.tar.xz
 b412cd383da21a5fc94cba367f335c57 6680 utils optional 
scim_1.4.18-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#875258: marked as done ([scim] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 00:06:18 +
with message-id 
and subject line Bug#875258: fixed in scim 1.4.18-2.2
has caused the Debian Bug report #875258,
regarding [scim] Future Qt4 removal from Buster
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.)


-- 
875258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scim
Version: 1.4.18-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: scim
Source-Version: 1.4.18-2.2

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
scim 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: Sat, 28 Dec 2019 20:45:08 -0300
Source: scim
Architecture: source
Version: 1.4.18-2.2
Distribution: unstable
Urgency: medium
Maintainer: Rolf Leggewie 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875250 875258
Changes:
 scim (1.4.18-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload. I took just one part of Tz-Hua's merge request
 because there was already an NMU in the archive. See #875250 for more
 details.
 .
   [ Tz-Huan Huang ]
   * Disable qt-immodules build. Closes: #875258, Closes: #875250
Checksums-Sha1:
 b2379a64f7e2deab1e7881968d8552f0d666efb6 2639 scim_1.4.18-2.2.dsc
 6d37c345dba0ad668d375bcb71f86054f5d5d512 27692 scim_1.4.18-2.2.debian.tar.xz
 3634ec5730099fe65afd0b25790d2087395e5a85 6680 scim_1.4.18-2.2_source.buildinfo
Checksums-Sha256:
 f12baf70ea5f3e185efbeab8d0f1ddea403a1f5b68d0443d328ac2e1de2dd21e 2639 
scim_1.4.18-2.2.dsc
 eedd10e878d4332650c7864cd102e570799a229b5392adf369740f199980fe20 27692 
scim_1.4.18-2.2.debian.tar.xz
 5db0c875a960d7bc1fb205f8f210b9f9c8272a8fa137870f7f1426b46e5382ba 6680 
scim_1.4.18-2.2_source.buildinfo
Files:
 914165b7f2d6a191cb119fb7945bb21a 2639 utils optional scim_1.4.18-2.2.dsc
 8cafeb99aa0e36f6dc3b069bf3fee03c 27692 utils optional 
scim_1.4.18-2.2.debian.tar.xz
 b412cd383da21a5fc94cba367f335c57 6680 utils optional 
scim_1.4.18-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#875250: marked as done ([scim] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 00:06:18 +
with message-id 
and subject line Bug#875258: fixed in scim 1.4.18-2.2
has caused the Debian Bug report #875258,
regarding [scim] Future Qt4 removal from Buster
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.)


-- 
875258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875258
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scim
Version: 1.4.18-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: scim
Source-Version: 1.4.18-2.2

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
scim 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: Sat, 28 Dec 2019 20:45:08 -0300
Source: scim
Architecture: source
Version: 1.4.18-2.2
Distribution: unstable
Urgency: medium
Maintainer: Rolf Leggewie 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875250 875258
Changes:
 scim (1.4.18-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload. I took just one part of Tz-Hua's merge request
 because there was already an NMU in the archive. See #875250 for more
 details.
 .
   [ Tz-Huan Huang ]
   * Disable qt-immodules build. Closes: #875258, Closes: #875250
Checksums-Sha1:
 b2379a64f7e2deab1e7881968d8552f0d666efb6 2639 scim_1.4.18-2.2.dsc
 6d37c345dba0ad668d375bcb71f86054f5d5d512 27692 scim_1.4.18-2.2.debian.tar.xz
 3634ec5730099fe65afd0b25790d2087395e5a85 6680 scim_1.4.18-2.2_source.buildinfo
Checksums-Sha256:
 f12baf70ea5f3e185efbeab8d0f1ddea403a1f5b68d0443d328ac2e1de2dd21e 2639 
scim_1.4.18-2.2.dsc
 eedd10e878d4332650c7864cd102e570799a229b5392adf369740f199980fe20 27692 
scim_1.4.18-2.2.debian.tar.xz
 5db0c875a960d7bc1fb205f8f210b9f9c8272a8fa137870f7f1426b46e5382ba 6680 
scim_1.4.18-2.2_source.buildinfo
Files:
 914165b7f2d6a191cb119fb7945bb21a 2639 utils optional scim_1.4.18-2.2.dsc
 8cafeb99aa0e36f6dc3b069bf3fee03c 27692 utils optional 
scim_1.4.18-2.2.debian.tar.xz
 b412cd383da21a5fc94cba367f335c57 6680 utils optional 
scim_1.4.18-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#875258: marked as done ([scim] Future Qt4 removal from Buster)

[Debian Bug Tracking System]

Your message dated Sun, 29 Dec 2019 00:06:18 +
with message-id 
and subject line Bug#875250: fixed in scim 1.4.18-2.2
has caused the Debian Bug report #875250,
regarding [scim] Future Qt4 removal from Buster
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.)


-- 
875250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scim
Version: 1.4.18-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal


Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 


Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.

[OpenSSL 1.1 support] 

In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: scim
Source-Version: 1.4.18-2.2

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

Debian distribution maintenance software
pp.
Lisandro Damián Nicanor Pérez Meyer  (supplier of updated 
scim 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: Sat, 28 Dec 2019 20:45:08 -0300
Source: scim
Architecture: source
Version: 1.4.18-2.2
Distribution: unstable
Urgency: medium
Maintainer: Rolf Leggewie 
Changed-By: Lisandro Damián Nicanor Pérez Meyer 
Closes: 875250 875258
Changes:
 scim (1.4.18-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload. I took just one part of Tz-Hua's merge request
 because there was already an NMU in the archive. See #875250 for more
 details.
 .
   [ Tz-Huan Huang ]
   * Disable qt-immodules build. Closes: #875258, Closes: #875250
Checksums-Sha1:
 b2379a64f7e2deab1e7881968d8552f0d666efb6 2639 scim_1.4.18-2.2.dsc
 6d37c345dba0ad668d375bcb71f86054f5d5d512 27692 scim_1.4.18-2.2.debian.tar.xz
 3634ec5730099fe65afd0b25790d2087395e5a85 6680 scim_1.4.18-2.2_source.buildinfo
Checksums-Sha256:
 f12baf70ea5f3e185efbeab8d0f1ddea403a1f5b68d0443d328ac2e1de2dd21e 2639 
scim_1.4.18-2.2.dsc
 eedd10e878d4332650c7864cd102e570799a229b5392adf369740f199980fe20 27692 
scim_1.4.18-2.2.debian.tar.xz
 5db0c875a960d7bc1fb205f8f210b9f9c8272a8fa137870f7f1426b46e5382ba 6680 
scim_1.4.18-2.2_source.buildinfo
Files:
 914165b7f2d6a191cb119fb7945bb21a 2639 utils optional scim_1.4.18-2.2.dsc
 8cafeb99aa0e36f6dc3b069bf3fee03c 27692 utils optional 
scim_1.4.18-2.2.debian.tar.xz
 b412cd383da21a5fc94cba367f335c57 6680 utils optional 
scim_1.4.18-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#875250: Intend to port to Qt 5

[Lisandro Damián Nicanor Pérez Meyer]

And attached is the NMU patch.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
From 90c200f506436898e5d64766c0fb7a031e151cc9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Lisandro=20Dami=C3=A1n=20Nicanor=20P=C3=A9rez=20Meyer?=
 
Date: Sat, 28 Dec 2019 20:25:16 -0300
Subject: [PATCH] Drop Qt 4 support.

---
 debian/README.Debian| 58 -
 debian/README.Qt| 26 ---
 debian/changelog| 11 +++
 debian/control  | 34 ---
 debian/im-switch/scim-immodule  | 22 ++---
 debian/rules|  2 +-
 debian/scim-qt-immodule.install |  1 -
 debian/scim.docs|  1 -
 8 files changed, 42 insertions(+), 113 deletions(-)
 delete mode 100644 debian/README.Qt
 delete mode 100644 debian/scim-qt-immodule.install

diff --git a/debian/README.Debian b/debian/README.Debian
index 6f07b80..1e3d7b6 100644
--- a/debian/README.Debian
+++ b/debian/README.Debian
@@ -4,14 +4,14 @@
 
 SCIM is an older and mature input method platform, and supports many different
 input methods (IMs) to make input of complicated characters in X environment
-possible.  
+possible.
 
 There are SCIM plugin modules for many languages such as Japanese, Chinese,
 Korean, Arabic, and many Indic languages.
 
 Most description for the new IBus at
 http://www.debian.org/doc/manuals/debian-reference/ch08.en.html#_the_keyboard_input
-is applicable to this older SCIM.  
+is applicable to this older SCIM.
 
 (Older documents in Japanese and English are available at:
  http://wiki.debian.org/JapaneseEnvironmentE (English)
@@ -47,15 +47,11 @@ your language or favorite input method is supported.
 The packages scim-gtk-immodule-orig and scim-gtk-immodule provide GTK IM
 mode for SCIM.  For more details, please read README.GTK.
 
-The package scim-qt-immodule provides Qt IM mode for SCIM.  For more details,
-please read README.Qt.
-
 In summary, you should install package scim and one of the IM module package
 to start.  You may install scim-gtk-immodule-orig or scim-gtk-immodule if
-you use GTK+ applications and want to try the GTK IM mode; and you may
-install scim-qt-immodule if you use Qt applications and want to try the
-Qt IM mode. You shouldn't need to explicitly install any other package as
-they should be installed as necessary due to dependency.
+you use GTK+ applications and want to try the GTK IM mode. You shouldn't need
+to explicitly install any other package as they should be installed as
+necessary due to dependency.
 
 ---
 Locales
@@ -90,12 +86,12 @@ Using SCIM
 --
 
 After setting up locale, you can try using SCIM to input in your language.
-SCIM can be used in three modes: XIM mode, GTK IM mode and Qt IM mode.
+SCIM can be used in two modes: XIM mode and GTK IM mode.
 
 To use XIM (X Input Method) mode, you need to set the environment variable
 XMODIFIERS and GTK_IM_MODULE before starting your X application (you
 only need to set GTK_IM_MODULE/QT_IM_MODULE if the X application you want
-to run also uses GTK+/Qt).  Run the following commands in an X terminal
+to run also uses GTK+).  Run the following commands in an X terminal
 (such as xterm, gnome-terminal or konsole):
 $ XMODIFIERS="@im=SCIM"
 $ export XMODIFIERS
@@ -142,19 +138,6 @@ and automatically stop when you quit the program.  This may cause delay
 for program start/quit though, so it's always a good idea to explicitly
 start SCIM by "scim -d" command.
 
-Qt also has its own input method framework, so Qt/KDE programs can use SCIM
-in an additional mode, GTK IM mode.  SCIM's Qt IM mode is provided as a
-Qt IM module by the scim-qt-immodule package, and SCIM can automatically
-start if you choose this module.  So using GTK IM mode is simpler, just
-start a Qt/KDE program, right-click and choose "Input Methods -> SCIM
-Input Method" in the pop-up menu, and SCIM should automatically start if
-it's not started yet.  Now pressing Ctrl-space should also activate SCIM
-and you can start typing.  An alternative way to start Qt applications
-using SCIM at the Qt IM module is by using QT_IM_MODULE
-$ QT_IM_MODULE="scim"
-$ export QT_IM_MODULE
-$ qt-program
-
 --
 Autostart SCIM
 --
@@ -174,9 +157,8 @@ want to start SCIM automatically with GNOME:
 export GTK_IM_MODULE
 export QT_IM_MODULE
 scim -d
-Change the en_US.UTF-8 to your preferred locale, and change
-GTK_IM_MODULE/QT_IM_MODULE to
-"scim" if you want to use GTK/QT IM mode instead of XIM mode.
+Change the en_US.UTF-8 to your preferred locale, and change GTK_IM_MODULE to
+"scim" if you want to use GTK IM mode instead of XIM mode.
 
 The hard part is to figure out which configuration file to put these in.  One
 choice is to put it in ~/.xsession, and add your X session command at the end
@@ -185,7 +167,7 @@ you always need to modify this file to change X session, and the feature of
 choosing 

Bug#947053: pep8 uses python instead of python2 in the autopkg tests

[Emmanuel Arias]

Hello,

I've just to push to salsa the fix of this issue.

Please, can somebody help me to upload it?

Thanks!

Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com

Bug#925743: marked as done (libgadu: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 23:49:41 +
with message-id 
and subject line Bug#925743: fixed in libgadu 1:1.12.2-4
has caused the Debian Bug report #925743,
regarding libgadu: 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.)


-- 
925743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgadu
Version: 1:1.12.2-3
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/libgadu_1.12.2-3_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.

[...]
Build with libexpat.. : no
Build with libxml2... : yes
Build with perl.. : yes

configure complete, now type 'make'

make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
# Make sure the code is warning-free. We cannot set this for the whole
# file, because many temporary files generated by configure are not
# warning-free.
dh_auto_build -- CFLAGS="$(DEB_CFLAGS_MAINT_APPEND=-Werror dpkg-buildflags 
--get CFLAGS)"
make -j4 "CFLAGS=-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Werror"
make[2]: Entering directory '/<>'
make  all-recursive
make[3]: Entering directory '/<>'
Making all in include
make[4]: Entering directory '/<>/include'
make  all-am
make[5]: Entering directory '/<>/include'
cd .. ; sh protobufgen.sh
[libprotobuf WARNING google/protobuf/compiler/parser.cc:562] No syntax 
specified for the proto file: packets.proto. Please use 'syntax = "proto2";' or 
'syntax = "proto3";' to specify a syntax version. (Defaulted to proto2 syntax.)
make[5]: Leaving directory '/<>/include'
make[4]: Leaving directory '/<>/include'
Making all in src
make[4]: Entering directory '/<>/src'
cat "libgadu.sym.in" > "libgadu.sym"
echo "gg_is_gpl_compliant" >> "libgadu.sym"
make  all-am
make[5]: Entering directory '/<>/src'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I../include   -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../include 
-DGG_IGNORE_DEPRECATED -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Werror -c -o 
libgadu_la-common.lo `test -f 'common.c' || echo './'`common.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I../include   -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../include 
-DGG_IGNORE_DEPRECATED -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Werror -c -o 
libgadu_la-dcc.lo `test -f 'dcc.c' || echo './'`dcc.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I../include   -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../include 
-DGG_IGNORE_DEPRECATED -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Werror -c -o 
libgadu_la-dcc7.lo `test -f 'dcc7.c' || echo './'`dcc7.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. 
-I../include   -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I../include 
-DGG_IGNORE_DEPRECATED -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Werror -c -o 
libgadu_la-debug.lo `test -f 'debug.c' || echo './'`debug.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. 

Bug#875250: Intend to port to Qt 5

[Lisandro Damián Nicanor Pérez Meyer]

I'm about to upload an NMU just with the Qt 4 drop changes, as the
package has received another NMU in the meantime.

Tz-Huan and Benda: Rolf, the main maintainer, seems unactive since ~
april 2018. If you want you might consider using the salvaging process
to take over maintenance. If you are not DDs and need sponsoring
please ping me (I am normally slow, but I get to it at some point).

I'm also currently not applying the rest of the changes in the MR due
to the changes in the NMU already in the archive. If any of you wants
to update the MR after my upload and need a sponsor, please ping me.


Cheers, Lisandro.

Bug#947246: marked as done (nss FTBFS on armel: error "NEON intrinsics not available with the soft-float ABI. Please use -mfloat-abi=softfp or -mfloat-abi=hard")

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 23:35:40 +
with message-id 
and subject line Bug#947246: fixed in nss 2:3.48-1
has caused the Debian Bug report #947246,
regarding nss FTBFS on armel: error "NEON intrinsics not available with the 
soft-float ABI.  Please use -mfloat-abi=softfp or -mfloat-abi=hard"
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.)


-- 
947246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947246
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nss
Version: 2:3.47-1
Severity: serious
Tags: ftbfs
Justification: armel still is a release architecture
User: helm...@debian.org
Usertags: rebootstrap

Since 2:3.47-1, nss fails to build from source on armel (it also fails
to cross build to armel):

https://buildd.debian.org/status/fetch.php?pkg=nss=armel=2%3A3.47.1-1=1575421472=0
| cc -o OBJS/Linux_SINGLE_SHLIB/aes-armv8.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -pipe -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC   
-pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR -DLINUX -Dlinux -Wall 
-Wshadow -Werror -DXP_UNIX -DSHLIB_SUFFIX=\"so\" -DSHLIB_PREFIX=\"lib\" 
-DSHLIB_VERSION=\"3\" -DSOFTOKEN_SHLIB_VERSION=\"3\" -DRIJNDAEL_INCLUDE_TABLES 
-UDEBUG -DNDEBUG -D_REENTRANT -DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY 
-DNO_NSPR_10_SUPPORT -DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES 
-DFREEBL_NO_DEPEND -DFREEBL_LOWHASH -DUSE_HW_AES -DMP_ASSEMBLY_MULTIPLY 
-DMP_ASSEMBLY_SQUARE  -DMP_USE_UINT_DIGIT -DSHA_NO_LONG_LONG  -DKRML_NOUINT128 
-DMP_API_COMPATIBLE -I/usr/include/nspr -I/<>/dist/include 
-I/<>/dist/public/nss -I/<>/dist/private/nss -Impi 
-Iecl -Iverified  -std=gnu99 -march=armv8-a -mfpu=crypto-neon-fp-armv8 
aes-armv8.c
| In file included from aes-armv8.c:16:
| /usr/lib/gcc/arm-linux-gnueabi/9/include/arm_neon.h:31:2: error: #error "NEON 
intrinsics not available with the soft-float ABI.  Please use 
-mfloat-abi=softfp or -mfloat-abi=hard"
|31 | #error "NEON intrinsics not available with the soft-float ABI.  
Please use -mfloat-abi=softfp or -mfloat-abi=hard"
|   |  ^

Given that 3.45 still built on armel, this is an rc bug. Also note that
nss is required for bootstrapping architectures, so armel is not
currently bootstrappable.

Helmut
--- End Message ---
--- Begin Message ---
Source: nss
Source-Version: 2:3.48-1

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

Debian distribution maintenance software
pp.
Mike Hommey  (supplier of updated nss 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: Sun, 29 Dec 2019 07:40:46 +0900
Source: nss
Architecture: source
Version: 2:3.48-1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Closes: 947131 947246
Changes:
 nss (2:3.48-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #947131.
   * debian/control: Bump nspr build dependency to 4.24.
   * nss/lib/freebl/Makefile: Disable hardware AES on ARM softfloat to fix
 FTBFS on armel. Closes: #947246.
Checksums-Sha1:
 296f06f9186914e1c9a15878f6c5aa794cc62ed4 2146 nss_3.48-1.dsc
 4a1f06ba4bfa06da2df94a98c793b17942a58652 76481237 nss_3.48.orig.tar.gz
 a1a53c4aca38dfab4a642d9d04540438073a3b9b 20768 nss_3.48-1.debian.tar.xz
 f20020d93ea6d2090e23e615c29d744a4350c642 5122 nss_3.48-1_source.buildinfo
Checksums-Sha256:
 6689ae7b057f55165f3c1aec9ea0e827bd29cd2a777b7d74b4617ca744f8e87f 2146 
nss_3.48-1.dsc
 3f9c822a86a4e3e1bfe63e2ed0f922d8b7c2e0b7cafe36774b1c627970d0f8ac 76481237 
nss_3.48.orig.tar.gz
 c18f7f89c07f0ee0cda40ca321d1054f8e1073ce9de718bfdbdfb96564471325 20768 
nss_3.48-1.debian.tar.xz
 d884d6d63e5d8cecaa65333ad14de430c6ee3260ca065ceea4fdfbb7822457bf 5122 
nss_3.48-1_source.buildinfo
Files:
 1459f50e9dfaa4750f7fe6dc01a0abc1 2146 libs optional nss_3.48-1.dsc
 7855014d8653aec66106ad910487a9c9 76481237 libs optional nss_3.48.orig.tar.gz
 cb7046932ccfe39a3b04ce546a2aec39 20768 libs optional nss_3.48-1.debian.tar.xz
 dd90fc4dd95ef7d335800a8b6bc6e9f9 5122 

Bug#947673: python3-pynvim: missing Breaks+Replaces: python3-neovim

[Andreas Beckmann]

Package: python3-pynvim
Version: 0.4.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../python3-pynvim_0.4.0-2_all.deb ...
  Unpacking python3-pynvim (0.4.0-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-pynvim_0.4.0-2_all.deb (--unpack):
   trying to overwrite '/usr/lib/python3/dist-packages/neovim/__init__.py', 
which is also in package python3-neovim 0.3.0-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-pynvim_0.4.0-2_all.deb


cheers,

Andreas


python3-neovim=0.3.0-1_python3-pynvim=0.4.0-2.log.gz
Description: application/gzip

Bug#865800: marked as done (golang-github-smartystreets-go-aws-auth FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 23:04:53 +
with message-id 
and subject line Bug#865800: fixed in golang-github-smartystreets-go-aws-auth 
1.0.0-1
has caused the Debian Bug report #865800,
regarding golang-github-smartystreets-go-aws-auth FTBFS: test failure
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.)


-- 
865800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-smartystreets-go-aws-auth
Version: 0.0~git20160722.0.2043e6d-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-smartystreets-go-aws-auth 
FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-smartystreets-go-aws-auth.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-smartystreets-go-aws-auth.html

...

   dh_auto_test -O--buildsystem=golang
go test -v -p 16 github.com/smartystreets/go-aws-auth
=== RUN   TestIntegration

  Given real credentials from environment variables 
A request (with out-of-order query string) with to IAM should succeed 
(assuming Administrator Access policy) ⚠
A request to S3 should succeed ⚠
A request to EC2 should succeed ⚠
A request to SQS should succeed ⚠
A request to SES should succeed ⚠
A request to Route 53 should succeed ⚠
A request to SimpleDB should succeed ⚠
If S3Resource env variable is set 
  A URL-signed request to that S3 resource should succeed ⚠


0 total assertions (one or more sections skipped)

--- PASS: TestIntegration (0.01s)
=== RUN   TestSign

  Requests to services using Version 2 should be signed accordingly ✔✔


2 total assertions (one or more sections skipped)


  Requests to services using Version 3 should be signed accordingly ✔✔


4 total assertions (one or more sections skipped)


  Requests to services using Version 4 should be signed accordingly ✔✔✔


7 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 2 should be signed 
accordingly ✔✔


9 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 3 should be signed 
accordingly ✔✔


11 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 4 should be signed 
accordingly ✔✔✔


14 total assertions (one or more sections skipped)

--- PASS: TestSign (0.00s)
=== RUN   TestExpiration

  Credentials without an expiration can't expire ✔


15 total assertions (one or more sections skipped)


  Credentials that expire in 5 minutes aren't expired ✔


16 total assertions (one or more sections skipped)


  Credentials that expire in 1 minute are expired ✔


17 total assertions (one or more sections skipped)


  Credentials that expired 2 hours ago are expired ✔


18 total assertions (one or more sections skipped)

--- PASS: TestExpiration (0.00s)
=== RUN   TestCommonFunctions

  Service and region should be properly extracted from host strings 
✔✔


32 total assertions (one or more sections skipped)


  MD5 hashes should be properly computed and base-64 encoded ✔


33 total assertions (one or more sections skipped)


  SHA-256 hashes should be properly hex-encoded (base 16) ✔


34 total assertions (one or more sections skipped)


  Given a key and contents 
HMAC-SHA256 should be properly computed ✔
HMAC-SHA1 should be properly computed ✔


36 total assertions (one or more sections skipped)


  Strings should be properly concatenated with a delimiter ✔✔✔


39 total assertions (one or more sections skipped)


  URI components should be properly encoded ✔✔✔


42 total assertions (one or more sections skipped)


  URI query strings should be properly encoded ✔


43 total assertions (one or more sections skipped)

--- PASS: TestCommonFunctions (0.00s)
=== RUN   TestSignatureS3

  Given a GET request to Amazon S3 
The request should be prepared with a Date header ✔
The CanonicalizedAmzHeaders should be built properly ✔
The CanonicalizedResource should be built properly ✔
The string to sign should be correct ✔
The final signature string should be exactly correct ✔


48 total assertions (one or more sections skipped)


  Given a GET request for a resource on S3 for query string authentication 
The string to sign should be correct ✔
The signature of string to sign should be correct ✔
The finished signed URL should be correct ✔


51 total assertions (one or more sections skipped)

--- PASS: TestSignatureS3 

Bug#947363: marked as done (colord-kde: FTBFS XEventHandler.cpp:25:10: fatal error: xcb/randr.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 22:34:40 +
with message-id 
and subject line Bug#947363: fixed in colord-kde 0.5.0-4
has caused the Debian Bug report #947363,
regarding colord-kde: FTBFS XEventHandler.cpp:25:10: fatal error: xcb/randr.h: 
No such file or directory
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.)


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

Hi,

colord-kde/experimental FTBFS in a curent sid/experimental environment:

/build/colord-kde-0.5.0/colord-kded/XEventHandler.cpp:25:10: fatal error: 
xcb/randr.h: No such file or directory
   25 | #include 
  |  ^
compilation terminated.

Probably a direct Build-Depends: libxcb-randr0-dev is now needed while
this was previously pulled by some other B-D.


Andreas


colord-kde_0.5.0-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: colord-kde
Source-Version: 0.5.0-4

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated colord-kde 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: Sat, 28 Dec 2019 23:22:31 +0100
Source: colord-kde
Architecture: source
Version: 0.5.0-4
Distribution: experimental
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 947363
Changes:
 colord-kde (0.5.0-4) experimental; urgency=medium
 .
   * Team upload.
   * Add the configuration for the CI on salsa.
   * Explicitly add needed build dependencies: libxcb-randr0-dev
 (Closes: #947363), pkg-config, and gettext.
   * Bump the debhelper compatibility to 12:
 - switch the debhelper build dependency to debhelper-compat 12
 - remove debian/compat
   * Bump Standards-Version to 4.4.1, no changes required.
Checksums-Sha1:
 c7646339ac4f04f2e12ff71ab88998d6af458349 2435 colord-kde_0.5.0-4.dsc
 d406fed9ff4e750751e5f8ada19a12a5532f7af2 3088 colord-kde_0.5.0-4.debian.tar.xz
 4f3adfd62158c53e71bb986fbe1fbd4ec590e9d1 21359 
colord-kde_0.5.0-4_source.buildinfo
Checksums-Sha256:
 e4d241d2f9592c346f040f02d0f435fe71ff8492ec30828d5553c90ccdf1a338 2435 
colord-kde_0.5.0-4.dsc
 2cb48d10f84c5d80cca28163325d6ba9b5fde0bccf8432beb7fa9646dadeb7fd 3088 
colord-kde_0.5.0-4.debian.tar.xz
 4828f5d7e4167931b586fa66745383309575a25cf2668ca9d959520007a241f9 21359 
colord-kde_0.5.0-4_source.buildinfo
Files:
 4d1b0e7a46b751b73081d44637b2bedb 2435 kde optional colord-kde_0.5.0-4.dsc
 68ab5fc71045588d72c119ca07ee0436 3088 kde optional 
colord-kde_0.5.0-4.debian.tar.xz
 89cbc04676db2477c2cfa3f09736829c 21359 kde optional 
colord-kde_0.5.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl4H1coACgkQLRkciEOx
P032/Q//fYMLYansgC1nhAY03zWwLcyKpy6YQBRvHvghAODLI5siExSQJmH7QYLl
KXxFlO0HFzXCl96eg4guej+53eabb33ReamnWcqe51xO2ERN7FfzYlXtB1/hOz64
4iBeecIm0y3SFxSNPi6AflBUFFdz9OhpHY1NP0wOrkdU1LPcO/TfC2Vn7lQk0yrr
8rMxmRIUsRyKFlpWvP5/P0P0JWpon61EAtkdW8mZwUZvDgdnVzBrz9JqXvz/HDHe
Pj63lfrF9tNIvIR14FGE0moSZZpdPb1LBBFUtnwB605yA2XngdHWqlmRcxUgyzyq
yGze+zonmqjQY8djoxYFCtykI31TvM8DE1XKy+5cuM51eqMXQHHSXMjaxZ3imxtp
n3taaQ4AVzjBBJLGDl47Mlwc5EUTN3+mhVMRpd0Mu72QqdorBOC/G+IrQrde1kCx
ap5LPT8iy8kXyy/ITQyY1wLyWirpT04nzolH6wKVGlv4dUxsnE/7e1fxIeWLlyt9
X6csw3Mrsamddra0f0bMMkf2n8IAx1ZUTh2gC0ghkIBePXBkvczgys1vuNixeW8F
e0Ws0P3K+VOzOBkOlAUOxYBQFSTUYXjRC9cjQ07yGRrdIsVEegeYjWHaENwmg3EM
0JsuaBwq+L/JjzirgntQmLwf1KkYob6c1WtfFBkNFz29Wfsj/Xw=
=Pt2d
-END PGP SIGNATURE End Message ---

Processed: tagging 947363

[Debian Bug Tracking System]

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

> tags 947363 + pending
Bug #947363 [src:colord-kde] colord-kde: FTBFS XEventHandler.cpp:25:10: fatal 
error: xcb/randr.h: No such file or directory
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#925739: marked as done (libcommoncpp2: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 21:25:50 +
with message-id 
and subject line Bug#925739: fixed in libcommoncpp2 1.8.1-8
has caused the Debian Bug report #925739,
regarding libcommoncpp2: 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.)


-- 
925739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcommoncpp2
Version: 1.8.1-7
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/libcommoncpp2_1.8.1-7_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.

[...]
config.status: creating Makefile
config.status: creating commoncpp2.spec
config.status: creating tests/Makefile
config.status: creating commoncpp2.list
config.status: WARNING:  'commoncpp2.list.in' seems to ignore the --datarootdir 
setting
config.status: creating w32/ccgnu2.dsp
config.status: creating w32/ccext2.dsp
config.status: creating w32/ccgnu2.vcproj
config.status: creating w32/ccext2.vcproj
config.status: creating config.h
config.status: executing libtool commands
config.status: executing depfiles commands
   dh_auto_build -a
make -j4
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in inc
make[3]: Entering directory '/<>/inc'
Making all in cc++
make[4]: Entering directory '/<>/inc/cc++'
make[4]: Nothing to be done for 'all'.
make[4]: Leaving directory '/<>/inc/cc++'
make[4]: Entering directory '/<>/inc'
make[4]: Nothing to be done for 'all-am'.
make[4]: Leaving directory '/<>/inc'
make[3]: Leaving directory '/<>/inc'
Making all in src
make[3]: Entering directory '/<>/src'
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
-I../inc   -Wdate-time -D_FORTIFY_SOURCE=2 -I../src -DCCXX_EXPORT_LIBRARY  
-D_GNU_SOURCE -I../inc  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o thread.lo 
thread.cpp
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
-I../inc   -Wdate-time -D_FORTIFY_SOURCE=2 -I../src -DCCXX_EXPORT_LIBRARY  
-D_GNU_SOURCE -I../inc  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o mutex.lo 
mutex.cpp
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
-I../inc   -Wdate-time -D_FORTIFY_SOURCE=2 -I../src -DCCXX_EXPORT_LIBRARY  
-D_GNU_SOURCE -I../inc  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o semaphore.lo 
semaphore.cpp
/bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
-I../inc   -Wdate-time -D_FORTIFY_SOURCE=2 -I../src -DCCXX_EXPORT_LIBRARY  
-D_GNU_SOURCE -I../inc  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o threadkey.lo 
threadkey.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../inc -Wdate-time 
-D_FORTIFY_SOURCE=2 -I../src -DCCXX_EXPORT_LIBRARY -D_GNU_SOURCE -I../inc -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c mutex.cpp  -fPIC -DPIC -o .libs/mutex.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../inc -Wdate-time 
-D_FORTIFY_SOURCE=2 -I../src -DCCXX_EXPORT_LIBRARY -D_GNU_SOURCE -I../inc -g 
-O2 

Bug#947668: pcb-rnd: FTBFS on arm64, i386, ppc64el, s390x: out/elem_pins.gcode/elem_pins.gcode.bottom.cnc not as expected

[Simon McVittie]

Source: pcb-rnd
Version: 2.1.4-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

pcb-rnd FTBFS on arm64, i386, ppc64el and s390x due to gcode output
during tests not matching a reference version:

> gcode: ... diff -u ref/elem_pins.gcode/elem_pins.gcode.bottom.cnc 
> out/elem_pins.gcode/elem_pins.gcode.bottom.cnc
> --- ref/elem_pins.gcode/elem_pins.gcode.bottom.cnc2019-08-02 
> 17:38:47.0 +
> +++ out/elem_pins.gcode/elem_pins.gcode.bottom.cnc2019-11-06 
> 06:32:41.472049411 +
> @@ -55,8 +55,8 @@
>  G1 X0.34 Y0.191667
>  G1 X0.34 Y0.156667
>  G1 X0.391667 Y0.13
> -G1 X0.441667 Y0.13
> -G1 X0.465000 Y0.158333
> +G1 X0.44 Y0.13
> +G1 X0.465000 Y0.156667
>  G1 X0.465000 Y0.19
>  G1 X0.441667 Y0.215000
>  G1 X0.39 Y0.215000
> gcode: ... BROKEN

There are also many other mismatches on i386, possibly caused by i386's
80-bit extended-precision (the i387 FPU).

Logs:

https://buildd.debian.org/status/fetch.php?pkg=pcb-rnd=arm64=2.1.4-2=1573021974=0
https://buildd.debian.org/status/fetch.php?pkg=pcb-rnd=ppc64el=2.1.4-2=1573020793=0
https://buildd.debian.org/status/fetch.php?pkg=pcb-rnd=s390x=2.1.4-2=1576926721=0
https://buildd.debian.org/status/fetch.php?pkg=pcb-rnd=i386=2.1.4-2=1573020665=0

Processed: bug 938327 is forwarded to https://github.com/rabbitvcs/rabbitvcs/issues/279, tagging 938327 ...

[Debian Bug Tracking System]

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

> # rabbitvcs switched Python 2 -> 3 and pygtk -> gi at the same time
> forwarded 938327 https://github.com/rabbitvcs/rabbitvcs/issues/279
Bug #938327 [src:rabbitvcs] rabbitvcs: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 
'https://github.com/rabbitvcs/rabbitvcs/issues/279'.
> tags 938327 + fixed-upstream
Bug #938327 [src:rabbitvcs] rabbitvcs: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> forwarded 885476 https://github.com/rabbitvcs/rabbitvcs/issues/279
Bug #885476 [src:rabbitvcs] rabbitvcs: Depends on unmaintained pygtk
Set Bug forwarded-to-address to 
'https://github.com/rabbitvcs/rabbitvcs/issues/279'.
> tags 885476 + fixed-upstream
Bug #885476 [src:rabbitvcs] rabbitvcs: Depends on unmaintained pygtk
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#875250: Intend to port to Qt 5

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

El vie., 27 dic. 2019 18:28, Moritz Mühlenhoff  escribió:

> On Thu, Dec 05, 2019 at 11:50:53AM +0800, Benda Xu wrote:
> > Hi Moritz,
> >
> > I started to work on qt5 port of SCIM.  There is some remaining blocks.
> > I will work on it for another 10 days.
> >
> > I want to postpone to deadline to Dec 15, if that does not drag the QT5
> > migration too much.
> >
> > Thank you for your understanding!
>
> scim is now the last package keeping Qt4 in testing, can we please go ahead
> with the https://github.com/leggewie-DM/scim/pull/1 MR ? Qt5 support can
> still be re-added later, there's ample time before the bullseye freeze.
>


Considering that Benda acked the MR in case the port is not there by the
deadline, and that we are past it already, I'll do a 0 day NMU, I hope
tonight or maybe tomorrow.

Cheers, Lisandro.

>

Bug#947385: marked as done (openstack-cluster-installer-agent: missing Breaks+Replaces: openstack-cluster-installer (<< 24))

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 19:10:10 +
with message-id 
and subject line Bug#947385: fixed in openstack-cluster-installer 25
has caused the Debian Bug report #947385,
regarding openstack-cluster-installer-agent: missing Breaks+Replaces: 
openstack-cluster-installer (<< 24)
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.)


-- 
947385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openstack-cluster-installer-agent
Version: 24
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../openstack-cluster-installer-agent_24_all.deb ...
  Unpacking openstack-cluster-installer-agent (24) ...
  dpkg: error processing archive 
/var/cache/apt/archives/openstack-cluster-installer-agent_24_all.deb (--unpack):
   trying to overwrite '/usr/bin/openstack-cluster-installer-agent', which is 
also in package openstack-cluster-installer 23
  Errors were encountered while processing:
   /var/cache/apt/archives/openstack-cluster-installer-agent_24_all.deb


cheers,

Andreas


openstack-cluster-installer=23_openstack-cluster-installer-agent=24.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: openstack-cluster-installer
Source-Version: 25

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated 
openstack-cluster-installer 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: Fri, 27 Dec 2019 21:17:05 +0100
Source: openstack-cluster-installer
Architecture: source
Version: 25
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 947385
Changes:
 openstack-cluster-installer (25) unstable; urgency=medium
 .
   * oci-agent: Add missing Breaks+Replaces (<< 24~) (Closes: #947385).
Checksums-Sha1:
 15f6fbedc74cd7541e9e942c0c59b1c665bde704 2203 
openstack-cluster-installer_25.dsc
 065672c3664728ef533540e04f080bd740a95ff3 200968 
openstack-cluster-installer_25.tar.xz
 c63c1081dd330d9cee9ec680f5ad039988fad7f6 6817 
openstack-cluster-installer_25_amd64.buildinfo
Checksums-Sha256:
 e4074d626782d0cd4414fd050d9072c4f554d8ab7df175715582773c8cd90cf2 2203 
openstack-cluster-installer_25.dsc
 09385a91e598af6fe353df1e3c799847bac0530030ab3d8a0f571cd70f9afa07 200968 
openstack-cluster-installer_25.tar.xz
 08be6aa64164ab16933fb05604a92d51f57c359791aee12968d69d984047f721 6817 
openstack-cluster-installer_25_amd64.buildinfo
Files:
 b5ce659d4fe5960d8197db5019a8b200 2203 net optional 
openstack-cluster-installer_25.dsc
 0baf2fac60e8c6f7282d2d68d2bcf191 200968 net optional 
openstack-cluster-installer_25.tar.xz
 cfd795f914cdf8ace4308271e0e64015 6817 net optional 
openstack-cluster-installer_25_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl4HoNAACgkQ1BatFaxr
Q/4YbQ/+Ir5roobnaTuIKkMDdFIt7gWDDfcL6ZM/Q/bOj3tla9k5CEAXXU3gGGo7
U6aUdJ0iJfT8nVVwwRkRK/+JOSdGiwXcreJ1bj6VWkgxoXj5ZhHF7BScyo4B4cJP
+vwj3hCUoO0NXcMkn46tMsuj+JSlHo2dTmdTy7QBF2f75s8Ti0/uhu00+Thwjxzg
G2K+S+PjbooL2mo7trobmp2Yy0GrFXgZMsJV297eA2wsEULfEOY9JIzaaV9Gwxcn
FxlkPKy5CAfNLfO0vIgRUImhePYzs7FBhUjVTVjf6UCpmRf+0Nvfy38RjynoPZ6D
n19sZasLdCM/q676vCWRbMlgfcLB8flBDTnsnDn7m7ZIrBRFUAHrpQsPH/jndQRj
zR2QPCAQ9lIShasJUiexzMYovZDwTz0b1ncHi5PZZbab6fWsaRvVQX+Uflh51pPa
b0dQRy35Lop8Z9tlNfo4v84koozPiprdtjh1OOy/IWAoZArvx/LxIcOCvN+OXQE4
b7pl0Z+wX0wgpkoRMiGJbJ3JAG4/vBaLj+y/Ldhre1qjeu7b2UViMswM7posPU3G
0hwcZtNXpilOoQsgdtccKNODaSQNCfnZoj9k2AR8jz2no/r+DjS4aAVVpffif2of

Processed: tagging 936161

[Debian Bug Tracking System]

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

> tags 936161 + upstream
Bug #936161 [src:aubio] aubio: Python2 removal in sid/bullseye
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: tagging 938892

[Debian Bug Tracking System]

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

> tags 938892 + upstream
Bug #938892 [src:zookeeper] zookeeper: Python2 removal in sid/bullseye
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: block 945886 with 944365

[Debian Bug Tracking System]

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

> block 945886 with 944365
Bug #945886 [creduce] creduce: build-depends on package that is not in testing.
945886 was not blocked by any bugs.
945886 was not blocking any bugs.
Added blocking bug(s) of 945886: 944365
> thanks
Stopping processing here.

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

Processed: tagging 936981

[Debian Bug Tracking System]

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

> tags 936981 + fixed-upstream
Bug #936981 [src:mailnag] mailnag: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 937118

[Debian Bug Tracking System]

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

> tags 937118 + fixed-upstream
Bug #937118 [src:nbdkit] nbdkit: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 936243

[Debian Bug Tracking System]

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

> tags 936243 + fixed-upstream
Bug #936243 [src:brutespray] brutespray: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#947621: comitup: autopkgtest regression: 'NoneType' object has no attribute 'Reset'

[Paul Gevers]

Source: comitup
Version: 1.9-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of comitup the autopkgtest of comitup fails in
testing when that autopkgtest is run with the binary packages of comitup
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
comitupfrom testing1.9-2
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

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

Paul
PS: your arm64 test also fails, but that is no regression. You want to
fix that as well:
E   NotADirectoryError: [Errno 20] Not a directory:
'/sys/class/net/bonding_masters/phy80211/name'


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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/comitup/3790339/log.gz

=== FAILURES
===
__ test_avahi_establish_group
__

avahi_fxt = None

def test_avahi_establish_group(avahi_fxt):
old_group = mdns.group
mdns.establish_group()
>   assert mdns.group != old_group
E   AssertionError: assert  != 
E+  where  = mdns.group

test/test_mdns.py:35: AssertionError
___ test_avahi_clear_entries
___

avahi_fxt = None

@patch('comitup.mdns.establish_group', Mock())
def test_avahi_clear_entries(avahi_fxt):
isempty = Mock(return_value=False)
mdns.group = Mock()
mdns.group.IsEmpty = isempty

mdns.clear_entries()

assert isempty.called
>   assert mdns.group.Reset.called
E   AttributeError: 'NoneType' object has no attribute 'Reset'




signature.asc
Description: OpenPGP digital signature

Bug#947620: freedv ftbfs with libcodec2-0.9

[Paul Gevers]

Source: freedv
Version: 1.3.1-4
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye

Dear maintainer,

Your package is part of the  libcodec2-0.9 transition. I tried to binNMU
your package but it fails to build from source. Please have a look.

Paul

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

Tail of log for freedv on amd64:

make[3]: *** [src/CMakeFiles/freedv.dir/build.make:79:
src/CMakeFiles/freedv.dir/dlg_filter.cpp.o] Error 1
In file included from /<>/src/dlg_ptt.h:25,
 from /<>/src/dlg_ptt.cpp:22:
/<>/src/fdmdv2_main.h:74:10: fatal error: codec2.h: No such
file or directory
   74 | #include "codec2.h"
  |  ^~
compilation terminated.
make[3]: *** [src/CMakeFiles/freedv.dir/build.make:105:
src/CMakeFiles/freedv.dir/dlg_ptt.cpp.o] Error 1
make[3]: Leaving directory '/<>/Build'
make[2]: *** [CMakeFiles/Makefile2:98: src/CMakeFiles/freedv.dir/all]
Error 2
make[2]: Leaving directory '/<>/Build'
make[1]: *** [Makefile:133: all] Error 2
make[1]: Leaving directory '/<>/Build'
dh_auto_build: cd Build && make -j4 returned exit code 2
make: *** [debian/rules:6: build-arch] Error 255



signature.asc
Description: OpenPGP digital signature

Processed: tagging 937211

[Debian Bug Tracking System]

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

> tags 937211 + fixed-upstream
Bug #937211 [src:openscap] openscap: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 937150

[Debian Bug Tracking System]

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

> tags 937150 + fixed-upstream
Bug #937150 [src:nodeenv] nodeenv: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#947486: FTBFS due to failing test case TestDefaultCache

[Reinhard Tartler]

Thanks for this bug report.

Your snippet above unfortunately skips the actual error that is happening.
Here is the relevant error:

=== RUN   TestDefaultCache
time="2019-12-28T16:50:03Z" level=error
msg="/tmp/TestDefaultCache173385111/unwritable:
{name:\"unwritable\", size:4096, mode:0x8140,
modTime:time.Time{wall:0xac045b5, ext:63713148603, loc:(*tim\
e.Location)(0x9f64a0)}, sys:syscall.Stat_t{Dev:0x40, Ino:0x7e664e,
Nlink:0x2, Mode:0x4140, Uid:0x0, Gid:0x0, X__pad0:0, Rdev:0x0, Size:4096,
Blksize:4096, Blocks:8, Atim:syscall.Timespec{Sec:1577551803, Nsec:18\
0372917}, Mtim:syscall.Timespec{Sec:1577551803, Nsec:180372917},
Ctim:syscall.Timespec{Sec:1577551803, Nsec:180372917},
X__unused:[3]int64{0, 0, 0}}}"
--- FAIL: TestDefaultCache (0.00s)
default_test.go:151:
Error Trace:default_test.go:151
Error:  Object expected to be of type
*memory.cache, but was *boltdb.cache
Test:   TestDefaultCache
default_test.go:163:
Error Trace:default_test.go:163
Error:  Object expected to be of type
*memory.cache, but was *boltdb.cache
Test:   TestDefaultCache
FAIL
FAILgithub.com/containers/image/pkg/blobinfocache   0.004s


I believe this is because of an outdated version of the
https://tracker.debian.org/pkg/golang-github-coreos-bbolt package, at least
upstream explicitly references version 1.3.3. I've filed #947617 for this.


-- 
regards,
Reinhard

Processed (with 1 error): tagging 935767, forcibly merging 935767 938766

[Debian Bug Tracking System]

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

> tags 935767 - patch
Bug #935767 [uwsgi] Please remove Python 2 support and usage from uwsgi
Removed tag(s) patch.
> forcemerge 935767 938766
Bug #935767 [uwsgi] Please remove Python 2 support and usage from uwsgi
Unable to merge bugs because:
package of #938766 is 'src:uwsgi' not 'uwsgi'
Failed to forcibly merge 935767: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#942023: marked as done (gnome-shell-timer crashes in gnome 3.34)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 16:34:22 +
with message-id 
and subject line Bug#942023: fixed in gnome-shell-timer 0.3.20+20171025-4
has caused the Debian Bug report #942023,
regarding gnome-shell-timer crashes in gnome 3.34
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-timer
Version: 0.3.20+20171025-3
Severity: grave

Relevant messages in the system journal:

oct 09 11:36:18 ivust gnome-shell[2780]: JS WARNING: [/usr/share/gnome-
shell/extensions/ti...@olebowle.gmx.com/extension.js 41]: Requiring Gst but it
has 2 versions availab
oct 09 11:36:19 ivust gnome-shell[2780]: Extension "ti...@olebowle.gmx.com" had
error: TypeError: GObject_Object.prototype._init called on incompatible Object



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.9 (SMP w/6 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), 
LANGUAGE=ru:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-shell-timer depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.30.1-2
ii  gnome-shell  3.34.0-2
ii  python3  3.7.3-1

gnome-shell-timer recommends no packages.

gnome-shell-timer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-shell-timer
Source-Version: 0.3.20+20171025-4

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated gnome-shell-timer 
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: Sat, 28 Dec 2019 17:10:02 +0100
Source: gnome-shell-timer
Architecture: source
Version: 0.3.20+20171025-4
Distribution: unstable
Urgency: medium
Maintainer: Raphaël Hertzog 
Changed-By: Raphaël Hertzog 
Closes: 942023
Changes:
 gnome-shell-timer (0.3.20+20171025-4) unstable; urgency=medium
 .
   * Add patch to make it work with GNOME 3.34 (Closes: #942023)
   * Bump Standards-Version to 4.4.1
Checksums-Sha1:
 40237647a14bb6c5b82636599e47acd00b358482 1716 
gnome-shell-timer_0.3.20+20171025-4.dsc
 c539db32cc4f1bbeb80aec9947239862fea73838 6124 
gnome-shell-timer_0.3.20+20171025-4.debian.tar.xz
 9c974873d00a417a3859d9925ed80ca3f6ffc1e9 6477 
gnome-shell-timer_0.3.20+20171025-4_source.buildinfo
Checksums-Sha256:
 40fba52f6362ef444e3ad06e18e0b403067e5c47aa284a5e3d713c85874beda9 1716 
gnome-shell-timer_0.3.20+20171025-4.dsc
 89bb347ad0c889f66de214236567f691cc084be71a7bbc1e232a49eeeae4563b 6124 
gnome-shell-timer_0.3.20+20171025-4.debian.tar.xz
 6654495ad072165109345204816b93530dba843dd80f09eb25e4ffa8e3528dd1 6477 
gnome-shell-timer_0.3.20+20171025-4_source.buildinfo
Files:
 74f9ab49c4727735a0b949cc16c56369 1716 gnome optional 
gnome-shell-timer_0.3.20+20171025-4.dsc
 cf58ff1e98069f62c1cc3114f1fdcbd7 6124 gnome optional 
gnome-shell-timer_0.3.20+20171025-4.debian.tar.xz
 e748a94e123f19eb0457524c50185a2b 6477 gnome optional 
gnome-shell-timer_0.3.20+20171025-4_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl4HftIACgkQA4gdq+vC
mrlCPwf/YBAPy95i0D/B9OP0DGZygrLhC6ZnBq1O75rd0tXxWfjgRdC8XSj4BasR
U50tNpLzMB2efxYbtzBgxaJiLxLXhjr1Yfh9HUoPZ0MPTh8XMj+RJ/eOyQ0nOLo0
YpuCugz6jOacw8zmOhAPrNuNO9P511VsYSMK2I0i8F2J3XK5wwAD+BEFrNtGhDdW
+2ab65qQcDyWY/dcxDm+8yK5kvrLs7GiXxuXVOVi/huaFnUsyyALq9o9LrUZuk5L
XEj104wl9Njv7TihQtdMv8k19+FRaMz1ZLBXm/9u8UMsJ9PE8O33ThE4o33qEdU+
lIFYTJB6CaKKf3azWr473v+HerzdWA==
=BGZu
-END PGP SIGNATURE End Message ---

Bug#947516: marked as done (transmission-remote-gtk: build-depends on obsolete libunique-dev)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 16:19:58 +
with message-id 
and subject line Bug#947516: fixed in transmission-remote-gtk 1.4.1-2
has caused the Debian Bug report #947516,
regarding transmission-remote-gtk: build-depends on obsolete libunique-dev
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.)


-- 
947516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: transmission-remote-gtk
Version: 1.4.1-1
Severity: serious
Justification: inheriting severity from 895520
Control: block 895520 by -1

src:transmission-remote-gtk Build-Depends on libunique-dev, which is
obsolete and unmaintained upstream (see #895520 for more details). Its
Debian maintainers, the GNOME team, do not consider libunique to be
suitable for inclusion in the bullseye (Debian 11) stable release.

The transmission-remote-gtk binary package does not appear to have a
Depends on libunique-1.0-0, which suggests that the build-dependency is no
longer necessary. (Also, transmission-remote-gtk now depends on GTK 3, but
libunique is part of the older and incompatible GTK 2 stack, so I don't
think transmission-remote-gtk could be using libunique successfully.)

Please remove this build-dependency, so that the GNOME team can be a
step closer to removing libunique.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: transmission-remote-gtk
Source-Version: 1.4.1-2

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

Debian distribution maintenance software
pp.
Benjamin Barenblat  (supplier of updated 
transmission-remote-gtk 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: Sat, 28 Dec 2019 11:01:52 -0500
Source: transmission-remote-gtk
Architecture: source
Version: 1.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Barenblat 
Changed-By: Benjamin Barenblat 
Closes: 947516
Changes:
 transmission-remote-gtk (1.4.1-2) unstable; urgency=medium
 .
   * Delete unused build dependency on libunique-dev (closes: #947516).
Checksums-Sha1:
 c01b5f579a08f4bc76b57a356c9b334218135c88 2298 
transmission-remote-gtk_1.4.1-2.dsc
 f3611606141df3b2a41cc5c92c937932ec284652 7012 
transmission-remote-gtk_1.4.1-2.debian.tar.xz
 31ec75f2d7e4c30be19f4ff3a55cf1dc92d6403e 14870 
transmission-remote-gtk_1.4.1-2_amd64.buildinfo
Checksums-Sha256:
 4317a795e52c60058b6318753efe1020e69e8d00f46ae7ef2c581cd30506e47b 2298 
transmission-remote-gtk_1.4.1-2.dsc
 a3a7ac422b1bc9c85d93db181ee144e8eedbee8923e61e8e4825ea388c722c83 7012 
transmission-remote-gtk_1.4.1-2.debian.tar.xz
 cb0520e831544518dc12c704570ed0184358fe605888a85f6715b7c9f1758928 14870 
transmission-remote-gtk_1.4.1-2_amd64.buildinfo
Files:
 0341745074d302a7ec9c158823fdce3d 2298 net optional 
transmission-remote-gtk_1.4.1-2.dsc
 5d63d4d7e6602cf2ed93feafb3e79f10 7012 net optional 
transmission-remote-gtk_1.4.1-2.debian.tar.xz
 c1772611493375679e8b798e1ac07cfd 14870 net optional 
transmission-remote-gtk_1.4.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEQbf+q7LkywHKVTMA5ZUVm53A7cMFAl4Hfe0ACgkQ5ZUVm53A
7cNaEg//Qm5KWS021YSGEhzzYikoPaiZZ+nBPu2nSnm2Fl/vOm4GmXsBXQIHP9uI
iLeEq9vCZNXQ6RHls66daSYUVcCcUSSViBdoas6ytebF3jCcLGPzAL+6B0txlqAi
ZuRYBYoGRPFYh/doUO711kM0pajxx7nhrZ5qT8YrxfqYTijqKva3yw87xmdqma8S
f4jQ2zdZE4mxyxvtndpwNBd/WoSn+I2gumj6eCr9Xcz4cCh/dWrd+pOWkkIUFCor
ZkjXdw8d/h8twWcJN4JyPrq0g8KFJOGbQogwFJ1kQAQgUIebQ7eWWn1TaXYPJ1X9
crBrTgTqwj0lLZymzI6iHaHgd4o3YbgeW60JIeGhLPxaefWsVDH5W+0uI2sTHhdO
Z0XypTzW1NaXi0m9GflVzNrtd93NZrD/SniLhbRmseCRsz1DT3cuSzfjRP2tAXOV
O69l0H0YgWM0+sre2/WOu3Hrfmrc1qWgkcGZnHsXBk7PqPKC2731L5Uf6BJvltiA
FegsFO7px0VZOO9tQNAzqKjkDs7EnDSvOzwwtWDpuMMtRLX7EkNqIT3CSA4k0cyI
jB2+7XgJtw0mGlpaqfWPxGlxvoba7wN+0+iHqAtqvgZb4zotUN17cWIzIfW0rWAu
4z1PWUDeZxxMb0kFHrO/9ZmsT+08W8cw8CdrUnxV8RjhnQAgLmc=
=YQGh
-END PGP SIGNATURE End Message ---

Processed: tagging 938340

[Debian Bug Tracking System]

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

> tags 938340 + upstream
Bug #938340 [src:reclass] reclass: Python2 removal in sid/bullseye
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: tagging 938858

[Debian Bug Tracking System]

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

> tags 938858 + upstream
Bug #938858 [src:xxdiff] xxdiff: Python2 removal in sid/bullseye
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#947400: hkl FTBFS on arm64: sirius segfaults

[Bernhard Übelacker]

Dear Maintainer,
I tried to have a look and might have found something.

The crash happens because coroutine_stack_init returns NULL.
This is because of a buffer size check.

Building a package with doubled "DEFAULT_STATE_SIZE" went
through without crash (just tested on aarch64).
However, I am unfamiliar with that package, therefore cannot
estimate other consequences of that change.

Kind regards,
Bernhard


(gdb) bt
#0  0xe0e16e30 in generator_new_ (fn=fn@entry=0xe0e18ed8 
, retsize=48, retsize@entry=40) at 
generator/generator.c:36
#1  0xe0e194c0 in trajectory_gen (tconfig=...) at hkl2.c:250
#2  0xe0e19574 in Trajectory_solve (tconfig=..., gconfig=..., 
sconfig=..., move=1) at hkl2.c:292
#3  0xe0e18168 in main_1 () at sirius.c:161
#4  0xe0dee47c in main () at sirius.c:246

# Buster aarch64 qemu VM 2019-12-28 (running at a raspberry 3)


apt update
apt dist-upgrade


apt install systemd-coredump fakeroot htop git gdb
apt build-dep hkl



mkdir /home/benutzer/source/hkl/orig -p
cd/home/benutzer/source/hkl/orig
apt source hkl
cd


cd/home/benutzer/source/hkl
cp orig try1 -a
cd try1/hkl-5.0.0.2569
script -a "../dpkg-buildpackage_$(date +%Y-%m-%d_%H-%M-%S).log" -c 
"dpkg-buildpackage"



dmesg
journalctl --no-pager
coredumpctl list

coredumpctl gdb 9919

set width 0
set pagination off
bt
display/i $pc
info reg





make[4]: Entering directory 
'/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation/figures'
gcc -DHAVE_CONFIG_H -I. -I../..  -Wextra -D_DEFAULT_SOURCE -I../.. -I../../hkl 
-I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/aarch64-linux-gnu/glib-2.0/include 
-I/usr/include -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/home/benutzer/source/hkl/try1/hkl-5.0.0.2569=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o sirius.o 
sirius.c
sirius.c:244:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
  244 | main(void)
  | ^~~~
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -g -O2 
-fdebug-prefix-map=/home/benutzer/source/hkl/try1/hkl-5.0.0.2569=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wl,--whole-archive,../../hkl/.libs/libhkl.a,--no-whole-archive -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed -o sirius sirius.o ../../hkl/libhkl.la 
../../hkl/api2/libhkl2.la -lglib-2.0 -lgobject-2.0 -lglib-2.0 
-L/usr/lib/aarch64-linux-gnu -lgsl -lgslcblas -lm -lyaml 
libtool: link: gcc -g -O2 
-fdebug-prefix-map=/home/benutzer/source/hkl/try1/hkl-5.0.0.2569=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,--whole-archive 
-Wl,../../hkl/.libs/libhkl.a -Wl,--no-whole-archive -Wl,-z -Wl,relro -Wl,-z 
-Wl,now -Wl,--as-needed -o .libs/sirius sirius.o  ../../hkl/.libs/libhkl.so 
../../hkl/api2/.libs/libhkl2.a -lgobject-2.0 -lglib-2.0 
-L/usr/lib/aarch64-linux-gnu -lgsl -lgslcblas -lm -lyaml
cd . && ./sirius
make[4]: *** [Makefile:739: sirius-stamp] Segmentation fault (core dumped)
make[4]: Leaving directory 
'/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation/figures'
make[3]: *** [Makefile:459: all-recursive] Error 1
make[3]: Leaving directory 
'/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation'
make[2]: *** [Makefile:559: all-recursive] Error 1
make[2]: Leaving directory '/home/benutzer/source/hkl/try1/hkl-5.0.0.2569'
make[1]: *** [Makefile:443: all] Error 2
make[1]: Leaving directory '/home/benutzer/source/hkl/try1/hkl-5.0.0.2569'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:10: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Script done, file is ../dpkg-buildpackage_2019-12-28_15-26-39.log






root@debian:~# journalctl --no-pager
...
Dec 28 15:36:32 debian systemd[1]: Started Process Core Dump (PID 9933/UID 0).
Dec 28 15:36:34 debian systemd-coredump[9934]: Process 9919 (sirius) of user 
1000 dumped core.
   
   Stack trace of thread 9919:
   #0  0xe0e16e30 n/a 
(/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation/figures/.libs/sirius
 + 0x40e30)
   #1  0xe0e16e28 n/a 
(/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation/figures/.libs/sirius
 + 0x40e28)
   #2  0xe0e194c0 n/a 
(/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation/figures/.libs/sirius
 + 0x434c0)
   #3  0xe0e19574 n/a 
(/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation/figures/.libs/sirius
 + 0x43574)
   #4  0xe0e18168 n/a 
(/home/benutzer/source/hkl/try1/hkl-5.0.0.2569/Documentation/figures/.libs/sirius
 + 0x42168)
   #5  0xe0dee47c n/a 

Bug#947457: marked as done (critical bluestore data corruption)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 16:06:30 +
with message-id 
and subject line Bug#947457: fixed in ceph 14.2.4-5
has caused the Debian Bug report #947457,
regarding critical bluestore data corruption
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.)


-- 
947457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ceph-osd
Version: 14.2.4-4
Severity: grave
Tags: upstream fixed-upstream

A critical bluestore data corruption bug[0][1] affecting OSDs configured with
separate db and/or wal devices has been introduced in 14.2.3 and is affecting
both 14.2.3 and 14.2.4 upstream releases[2]. This bug has been fixed in
upstream version 14.2.5. Fix is simple[4] and can be easily applied/backported
to Debian release 14.2.4.

[0] https://tracker.ceph.com/issues/42223
[1] https://github.com/ceph/ceph/pull/31621
[2] 
https://lists.ceph.io/hyperkitty/list/ceph-annou...@ceph.io/message/X6TNSDQK5DVKO6XFJW3DMJAJV63PLDYM/
[3] https://ceph.io/releases/v14-2-5-nautilus-released/
[4] https://github.com/ceph/ceph/commit/117c8b5ca0130e02be98848b6c323812e271af27
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 14.2.4-5

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

Debian distribution maintenance software
pp.
Bernd Zeimetz  (supplier of updated ceph 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: Sat, 28 Dec 2019 15:54:51 +0100
Source: ceph
Architecture: source
Version: 14.2.4-5
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Bernd Zeimetz 
Closes: 947457
Changes:
 ceph (14.2.4-5) unstable; urgency=medium
 .
   [ Bernd Zeimetz ]
   * [453eaa4] Avoid using make -j 32 on powerpc.
 A lot of CPU do not always help.
 .
   [ Milan Kupcevic ]
   * [c6ec924] cherry pick critical bluestore data corruption fix
 (Closes: #947457)
 .
   [ Bernd Zeimetz ]
   * [e88fc21] Set -DWITH_BOOST_CONTEXT=OFF where necessary.
 [!s390x !mips64el !ia64 !m68k !ppc64 !riscv64 !sh4 !sparc64 !x32]
Checksums-Sha1:
 6f4690a16ac9a60a437df04c704ee6762fc759b7 5854 ceph_14.2.4-5.dsc
 a25fa358b04128c9f14012d3fe9dbb42d8b72d63 115996 ceph_14.2.4-5.debian.tar.xz
 4a929360565a9a469fcd1851e444d92e8606d9d1 21151 ceph_14.2.4-5_source.buildinfo
Checksums-Sha256:
 3343372577c5fd0e14a35668a54fa9969576a0ee67b3a5f82b7bb392bb09368c 5854 
ceph_14.2.4-5.dsc
 1cc7e35ab6557b0439ed6bc761046b100547f1746c9cd20251f3671b38d35cee 115996 
ceph_14.2.4-5.debian.tar.xz
 b411cfc1d0b71e8a2c9cf7c0c8c724c2a595301b36db22d705fed4a3f5b97dc7 21151 
ceph_14.2.4-5_source.buildinfo
Files:
 24bc6b44759c53fcd7038efb286d4d04 5854 admin optional ceph_14.2.4-5.dsc
 5fe13fb13093e29ca760fc6e6ade5c37 115996 admin optional 
ceph_14.2.4-5.debian.tar.xz
 9372dce7320adb6fef50b7b23d8d3143 21151 admin optional 
ceph_14.2.4-5_source.buildinfo
Original-Maintainer: Ceph Packaging Team 

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE7KHj8o4RJDLUhd2V6zYXGm/5Q18FAl4HdzMACgkQ6zYXGm/5
Q19eZxAAmPRN6avA181set2D/6ulEiK0VX/q2GVOv2vV57o/bYusKJ5La1kmGNgT
zcWiI82/o1GXtWzLSIM4Z8e4n1gVUYeswK61R0MTvkBgls/i0YdlNuYDkf1PgLGQ
ktu50CBuJi2AUAQy1F9bYnNm/TleUO39aJSm1gTnzuo5YammzZKy1+bhT1ISmASw
B6ShRK2AXoJdlnKDT3w0bxpl7HU3ubOoCCvPx75968n/yFX4Zmbc5T4NdbOHS2p7
4RDp0QaBMoKs3ch2Li3TuveIyxQLr7qY3CIxk6DRmlDMfWmhJo/k4LvKCmJ/abht
uMROxCLeYWG3RggOuyUmjC0Vp3nH71wYDA68nO7M2kbm/9nbFF8XogHkiclRrQFi
bolUiS0Ms8RIXQueym16rL4hpYJt0JCkODkhP6yaNX2EN3OdXRZPgR3La3kwMLKu
M0tU3WTmX/+V+W+X7stnVwad40GY3wrDxfqXSCvDppEY7s3LUIbSGakoGuxce+VZ
KvRQxWiT2sP4lpsNRS/fKvdQVn6NgZrLOe117lWYeEA4Ka2NJLykaFLBcLVY3Wgv
ipCs0k4zR6zbJdnMAiT7YnqC0OMVHB5i5Swvas1deD0kMqAoGis8OYG0hKL0wFYb
Amgt1FRkmA9LjH8+PVP3I7pzVIdCW/EdTGQ8dtPNEVRpYAXRm9U=
=kdCG
-END PGP SIGNATURE End Message ---

Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

[Eugen Dedu]

Package: network-manager
Version: 1.22.0-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have an Internet box and connect to it through Wi-Fi.

After upgrading network-manager to 1.22.2-1, my machine does not get
an IPv4 address anymore.  Specifically, ifconfig shows:

wlp1s0: flags=4163  mtu 1300
inet6 ...  prefixlen 64  scopeid 0x0
inet6 ...  prefixlen 64  scopeid 0x20
ether ...  txqueuelen 1000  (Ethernet)
RX packets 14389956  bytes 13801531443 (12.8 GiB)
RX errors 0  dropped 14956  overruns 0  frame 0
TX packets 3398391  bytes 958204966 (913.8 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

After downloading an older version of network-manager (from
snapshot.debian.org) and downgrading everything works fine:

root@snoopy:# dpkg -i *1.22.0-2*
dpkg: warning: downgrading gir1.2-nm-1.0:amd64 from 1.22.2-1 to 1.22.0-2
(Reading database ... 330245 files and directories currently installed.)
Preparing to unpack gir1.2-nm-1.0_1.22.0-2_amd64.deb ...
Unpacking gir1.2-nm-1.0:amd64 (1.22.0-2) over (1.22.2-1) ...
dpkg: warning: downgrading libnm0:amd64 from 1.22.2-1 to 1.22.0-2
Preparing to unpack libnm0_1.22.0-2_amd64.deb ...
Unpacking libnm0:amd64 (1.22.0-2) over (1.22.2-1) ...
dpkg: warning: downgrading network-manager from 1.22.2-1 to 1.22.0-2
Preparing to unpack network-manager_1.22.0-2_amd64.deb ...
Unpacking network-manager (1.22.0-2) over (1.22.2-1) ...
Setting up libnm0:amd64 (1.22.0-2) ...
Setting up network-manager (1.22.0-2) ...
Setting up gir1.2-nm-1.0:amd64 (1.22.0-2) ...
Processing triggers for libc-bin (2.29-6) ...
Processing triggers for systemd (244-3) ...
Processing triggers for dbus (1.12.16-2) ...
Processing triggers for man-db (2.9.0-2) ...

Best regards,
Eugen Dedu

http://eugen.dedu.free.fr


-- 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/8 CPU cores)
Kernel taint flags: TAINT_WARN
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 network-manager depends on:
ii  adduser3.118
ii  dbus   1.12.16-2
ii  init-system-helpers1.57
ii  libaudit1  1:2.8.5-2+b1
ii  libbluetooth3  5.50-1+b1
ii  libc6  2.29-6
ii  libcurl3-gnutls7.67.0-2
ii  libglib2.0-0   2.62.3-2
ii  libgnutls303.6.11.1-2
ii  libjansson42.12-1
ii  libmm-glib01.10.4-0.1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.21-4
ii  libnm0 1.22.0-2
ii  libpam-systemd 244-3
ii  libpolkit-agent-1-00.105-26
ii  libpolkit-gobject-1-0  0.105-26
ii  libpsl50.20.2-2
ii  libreadline8   8.0-3
ii  libselinux13.0-1
ii  libsystemd0244-3
ii  libteamdctl0   1.29-1
ii  libudev1   244-3
ii  libuuid1   2.34-0.1
ii  policykit-10.105-26
ii  udev   244-3
ii  wpasupplicant  2:2.9-3+b1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1.1
ii  iptables 1.8.4-1
ii  modemmanager 1.10.4-0.1
pn  ppp  

Versions of packages network-manager suggests:
ii  isc-dhcp-client  4.4.1-2
pn  libteam-utils

-- no debconf information

Processed: tagging 946563

[Debian Bug Tracking System]

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

> tags 946563 + pending
Bug #946563 [src:libxcrypt] there is no need for a versioned libxcrypt1-dev 
package
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

[Simon McVittie]

On Sat, 28 Dec 2019 at 15:49:45 +0100, Axel Beckert wrote:
> Simon McVittie wrote:
> > On Sun, 24 Dec 2017 at 09:31:29 -0500, Jeremy Bicha wrote:
> > > The way forward is to port your app to use GObject Introspection
> > > bindings.
> > 
> > This appears to be fixed in experimental along with #938823.
> 
> Why do you think so?

The python-gtk dependency went away, so it's certainly true to say that
the version in experimental no longer depends on the unmaintained package,
which is what the submitter of #885140 wanted :-)

(As a result the GUI doesn't work any more (#946380), which I agree is a
blocker for upload to unstable - but it's a step in the right direction.)

smcv

Processed: tagging 938766

[Debian Bug Tracking System]

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

> tags 938766 - patch
Bug #938766 [src:uwsgi] uwsgi: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #938766 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Re: Bug#947589: wicd-gtk: [experimental] wicd-gtk probably broken: no GTK dependency, still uses 'import gtk'

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 946380 -1
Bug #946380 [wicd-gtk] wicd-gtk does not find gtk modules
Bug #947589 [wicd-gtk] wicd-gtk: [experimental] wicd-gtk probably broken: no 
GTK dependency, still uses 'import gtk'
Severity set to 'grave' from 'important'
Merged 946380 947589
> tag -1 + confirmed
Bug #947589 [wicd-gtk] wicd-gtk: [experimental] wicd-gtk probably broken: no 
GTK dependency, still uses 'import gtk'
Bug #946380 [wicd-gtk] wicd-gtk does not find gtk modules
Added tag(s) confirmed.
Added tag(s) confirmed.

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

Processed (with 1 error): Re: [pkg-uWSGI-devel] Bug#938766: uwsgi: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -tag
Unknown tag/s: tag.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore.

Bug #938766 [src:uwsgi] uwsgi: Python2 removal in sid/bullseye
Requested to remove no tags; doing nothing.

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

Bug#938766: [pkg-uWSGI-devel] Bug#938766: uwsgi: Python2 removal in sid/bullseye

[Jonas Smedegaard]

Control: tags -1 -tag

Quoting Xavier (2019-12-28 14:40:07)
> it looks like a duplicate of https://bugs.debian.org/935767 which 
> provides a patch.

Yeah, but as the bugreport content reflects, that patch is too big a 
burden to carry downstream.

Removing patch tag to try better indicate that the patch is arguably 
incomplete.

 - Jonas

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

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


signature.asc
Description: signature

Processed: Re: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

[Debian Bug Tracking System]

Processing control commands:

> notfixed -1 1.7.4+tb2+2019.09.18git2e0ba579-1
Bug #885140 [src:wicd] wicd: Depends on unmaintained pygtk
No longer marked as fixed in versions wicd/1.7.4+tb2+2019.09.18git2e0ba579-1.

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

Bug#885140: [pkg-wicd-maint] Bug#885140: wicd: Depends on unmaintained pygtk

[Axel Beckert]

Control: notfixed -1 1.7.4+tb2+2019.09.18git2e0ba579-1

Hi Simon,

Simon McVittie wrote:
> On Sun, 24 Dec 2017 at 09:31:29 -0500, Jeremy Bicha wrote:
> > The way forward is to port your app to use GObject Introspection
> > bindings.
> 
> This appears to be fixed in experimental along with #938823.

Why do you think so? AFAIK upstream (Cc'ed) hasn't fixed that part
yet, see also https://bugs.debian.org/946380 (Guido: can you have a
look at that issue, i.e. Debian bug report #946380?)

> [...] it's the status of unstable that matters for the ability to
> remove pygtk; please close this bug in the first Python 3 upload of
> wicd to unstable.

Likely won't upload this to unstable until this is fixed.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#938099:

[Joel Rosdahl]

I think that it's time to remove python-pysqlite2 from Debian: Python
has had support for SQLite 3 since version 2.5 and there is
(understandably) no upstream activity for the Python wrapper.

Bug#938192:

[Joel Rosdahl]

I think that it's time to remove python-sqlite from Debian: it's a
module for the obsolete SQLite 2 API and there's (understandably) no
upstream activity.

Bug#947609: cmake-extras: testsuite autopkgtests failures

[Gianfranco Costamagna]

Source: cmake-extras
Version: 1.3+17.04.20170310-6
Severity: serious


Hello,
Looks like the testsuite has two major issues:
https://ci.debian.net/packages/c/cmake-extras/

intltool FAIL badpkg
this one fails because of:
E: Unable to locate package language-pack-en

this package seems to be existent only in Ubuntu...


however, the most important failure
is a regression between -5 and -6 upload, where the includechecker test has 
started to fail.

(Reading database ... 22283 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [02:03:48]: test includechecker: [---
=
Running build with cmake arguments: -DINCLUDE_CHECK_FORBIDDEN= 
-DINCLUDE_CHECK_ALLOWED= -DINCLUDE_CHECK_IGNORE=
-- The C compiler identification is GNU 9.2.1
-- The CXX compiler identification is GNU 9.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29") 
-- Checking for modules 'glib-2.0;gobject-2.0'
--   Found glib-2.0, version 2.62.3
--   Found gobject-2.0, version 2.62.3
-- Found IncludeChecker: /usr/share/cmake/IncludeChecker/include_checker.py   
-- Configuring done
-- Generating done
-- Build files have been written to: 
/tmp/autopkgtest-lxc.ntcm2688/downtmp/autopkgtest_tmp/tmp.pevHsVmMBa/build
Scanning dependencies of target good-header-test
[ 25%] Building CXX object 
test/demolib/CMakeFiles/good-header-test.dir/good-header-test.cpp.o
[ 50%] Linking CXX executable good-header-test
[ 50%] Built target good-header-test
Scanning dependencies of target bad-header-test
[ 75%] Building CXX object 
test/demolib/CMakeFiles/bad-header-test.dir/bad/bad-header-test.cpp.o
[100%] Linking CXX executable bad-header-test
[100%] Built target bad-header-test
Running tests...
Test project 
/tmp/autopkgtest-lxc.ntcm2688/downtmp/autopkgtest_tmp/tmp.pevHsVmMBa/build
Start 1: good-header-test
1/3 Test #1: good-header-test .   Passed0.00 sec
Start 2: bad-header-test
2/3 Test #2: bad-header-test ..   Passed0.00 sec
Start 3: demolib-include-check
3/3 Test #3: demolib-include-check ***Failed0.02 sec

67% tests passed, 1 tests failed out of 3

Total Test time (real) =   0.02 sec

The following tests FAILED:
  3 - demolib-include-check (Failed)
Errors while running CTest
make: *** [Makefile:73: test] Error 8
Failed: Unexpected exit value 2, expected 0
autopkgtest [02:03:50]: test includechecker: ---]
autopkgtest [02:03:50]: test includechecker:  - - - - - - - - - - results - - - 
- - - - - - -
includechecker   FAIL non-zero exit status 1

I don't have a solution for this issue

G.

Processed: Re: Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

[Debian Bug Tracking System]

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

> clone 946599 -1
Bug #946599 [libcrypt1] libcrypt1: failure to switch from libc6 to libcrypt1 
hoses the whole system
Bug 946599 cloned as bug 947606
> retitle -1 libcrypt1: wrong soname on alpha and ia64
Bug #947606 [libcrypt1] libcrypt1: failure to switch from libc6 to libcrypt1 
hoses the whole system
Changed Bug title to 'libcrypt1: wrong soname on alpha and ia64' from 
'libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system'.
> severity -1 important
Bug #947606 [libcrypt1] libcrypt1: wrong soname on alpha and ia64
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#938766: uwsgi: Python2 removal in sid/bullseye

[Xavier]

Hi,

it looks like a duplicate of https://bugs.debian.org/935767 which
provides a patch.

Cheers,
Xavier

Processed (with 1 error): your mail

[Debian Bug Tracking System]

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

> reassign 938098 ftp.debian.org
Bug #938098 [src:python-pysqlite1.1] python-pysqlite1.1: Python2 removal in 
sid/bullseye
Bug reassigned from package 'src:python-pysqlite1.1' to 'ftp.debian.org'.
No longer marked as found in versions python-pysqlite1.1/1.1.8a-8.
Ignoring request to alter fixed versions of bug #938098 to the same values 
previously set
> severity 938098 normal
Bug #938098 [ftp.debian.org] python-pysqlite1.1: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
> retitle 938098 RM: python-pysqlite1.1 -- removal triggered by the
Bug #938098 [ftp.debian.org] python-pysqlite1.1: Python2 removal in sid/bullseye
Changed Bug title to 'RM: python-pysqlite1.1 -- removal triggered by the' from 
'python-pysqlite1.1: Python2 removal in sid/bullseye'.
> Python2 removal; obsolete module for old libsqlite API; dead upstream
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.

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

Bug#947487: FTBFS: various C++ errors

[Sune Stolborg Vuorela]

Upstream master builds, but might also soon be adopted by KDE Frameworks

A quick fix is adding this line a nice place in toplevel CMakeLists.txt

set_property(TARGET tgt PROPERTY CXX_STANDARD 11)

Around line 35 looks like a nice location.

/Sune

On Friday, December 27, 2019 5:32:17 PM CET Lisandro Damián Nicanor Pérez 
Meyer wrote:
> Source: grantlee5
> Version: 5.1.0-2.1
> Severity: serious
> Justification: FTBFS in various architectures
> 
> Hi! While rebuilding your package due to a binNMU it failed to build from
> source:
> 
> https://buildd.debian.org/status/package.php?p=grantlee5
> 
> The forst error I see is:
> 
> from
> /<>/obj-x86_64-linux-gnu/templates/tests/pluginpointertest/mai
> n_app_autogen/mocs_compilation.cpp:2:
> /usr/include/c++/9/bits/c++0x_warning.h:32:2: error: #error This file
> requires compiler and library support for the ISO C++ 2011 standard. This
> support must be enabled with the -std=c++11 or -std=gnu++11 compiler
> options. 32 | #error This file requires compiler and library support \
> 
>   |  ^
> 
> Thanks for your work, Lisandro.
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500,
> 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1,
> 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64)
> Foreign Architectures: i386, arm64, armhf
> 
> Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8),
> LANGUAGE=es_AR:es (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled

Bug#947515: marked as done (quitcount: build-depends on obsolete libunique-dev)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 13:04:34 +
with message-id 
and subject line Bug#947515: fixed in quitcount 3.1.4-2
has caused the Debian Bug report #947515,
regarding quitcount: build-depends on obsolete libunique-dev
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.)


-- 
947515: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quitcount
Version: 3.1.4-1
Severity: serious
Justification: inheriting severity from 895520
Control: block 895520 by -1

src:quitcount Build-Depends on libunique-dev, which is obsolete and
unmaintained upstream (see #895520 for more details). Its Debian
maintainers, the GNOME team, do not consider libunique to be suitable
for inclusion in the bullseye (Debian 11) stable release.

The quitcount binary package does not appear to have a Depends on
libunique-1.0-0, which suggests that the build-dependency is no longer
necessary. (Also, quitcount now depends on GTK 3, but libunique is part
of the older and incompatible GTK 2 stack, so I don't think quitcount
could be using libunique successfully.)

Please remove this build-dependency, so that the GNOME team can be a
step closer to removing libunique.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: quitcount
Source-Version: 3.1.4-2

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated quitcount 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: Sat, 28 Dec 2019 13:29:49 +0100
Source: quitcount
Architecture: source
Version: 3.1.4-2
Distribution: unstable
Urgency: high
Maintainer: Ricardo Mones 
Changed-By: Ricardo Mones 
Closes: 947515
Changes:
 quitcount (3.1.4-2) unstable; urgency=high
 .
   [ Jeremy Bicha ]
   * Drop obsolete Build-Depends on libunique-dev (Closes: #947515)
 .
   [ Ricardo Mones ]
   * Fix appdata license (thanks lintian)
   * Update Standards-Version to 4.4.1 (no other changes)
   * Fix autotools-pkg-config-macro-not-cross-compilation-safe
Checksums-Sha1:
 8a921145a5c28a530b1151b81cdf9eef851d8181 1863 quitcount_3.1.4-2.dsc
 e02717b028e7aa993c0d2ecfaf4bc8446b0ffbca 11180 quitcount_3.1.4-2.debian.tar.xz
 fefafe9e526a355eb5a9df1b5fe813d06f2b8cd3 13597 
quitcount_3.1.4-2_amd64.buildinfo
Checksums-Sha256:
 8adbb661ad5dae442a2a0d6e550f713c3411a8d81204325e671ecaab057f4766 1863 
quitcount_3.1.4-2.dsc
 1cb8aeace3d624d7c6f2ea19b59cdae0d7021f2d11b0683827da46299f026ce7 11180 
quitcount_3.1.4-2.debian.tar.xz
 f751f45121ab861140995309c2afadb08b7c32d7287342bd89b237db2dac4984 13597 
quitcount_3.1.4-2_amd64.buildinfo
Files:
 76deed709d027e853fca020c735779da 1863 science optional quitcount_3.1.4-2.dsc
 5ea571e5d26771e45549cd737c2e67cb 11180 science optional 
quitcount_3.1.4-2.debian.tar.xz
 eed9dd2ccfe1b8062f8f573e3080b905 13597 science optional 
quitcount_3.1.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAl4HTSkACgkQHw8KiN5b
zKYyWBAAnyKgrkdnQ3ql4FNohY9xwDVmgBiASi7M2Ex88uBKJH91r6srYo23sFIM
Sh0qD17ddTNS4SKSoLrnc000OK/qiP5XVzLnreB5iNWUwgQGAn98J906jIDpzN36
mXQ4ogHxcG9PGiThQvgAj0rJzhtvF1ZS+e9AxGQoY95lXJmyuEEKfqVjmhiM/+Oy
FNgr/ihNSKRXbkTDzXcPBey2GH5L0+LAtBrKVBl8/LvVIeWC86C7rZEon1Hp+wMq
l9p0GrKV8wvwGc36eXmZ2OiDf27tgGrGg1Va6Psi8rmPuir6a4EwltrJYsW6JKbV
7jOZkGGIsCr0z/YIswMLpAkbi+kQH8ddIJxX5iEpb/uoKQeQIHs+4wrY5kq5eexV
trnhZjTCfqVmow2vCLj2d1hD+oqnQ+d99RZ44+IwhZoDqmAgu1kXXDiIi1XXh9jt
gddnk0jKXAftp2kC0Z79Yqiyr7LPuFwv2DdP4JXQM6n1dvTgXA8TJ22vhxK3+U9j
fia3dezLTDym9bxOv8USmchYJUmdr9saTyOMe22nxLd1aD7Xxxq7RVsnF0tH6zmB
uMF7vMFSt5hTkoHvy0bpxRz0/cW73HSURbhRZFP277m5akrPY0Kkx9aOvMVsThEr
KXD8nYTXZxcA0nki/syEqUHPU1ooyGKAfCiSGWrO28V2jXuh3rI=
=hjU2
-END PGP SIGNATURE End Message ---

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

[Aurelien Jarno]

Le 28 décembre 2019 13:31:01 GMT+01:00, John Paul Adrian Glaubitz 
 a écrit :
>Hello!
>
>Just as a heads-up: This problem isn't limited to x32, it also breaks
>on alpha
>and I'm currently flooded with sbuild build failure mails as setting up
>the
>build environment fails [1]:

Nope that's a different issue. The log shows that libcrypt1 is correctly 
installed before libc6.1 is configured.



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

Bug#946599: libcrypt1: failure to switch from libc6 to libcrypt1 hoses the whole system

[John Paul Adrian Glaubitz]

Hello!

Just as a heads-up: This problem isn't limited to x32, it also breaks on alpha
and I'm currently flooded with sbuild build failure mails as setting up the
build environment fails [1]:

Setting up libc6.1:alpha (2.29-6) ...
/usr/bin/perl: error while loading shared libraries: libcrypt.so.1.1: cannot 
open shared object file: No such file or directory
dpkg: error processing package libc6.1:alpha (--configure):
 installed libc6.1:alpha package post-installation script subprocess returned 
error exit status 127
Errors were encountered while processing:
 libc6.1:alpha
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt-get failed.

Maybe the Pre-Depends to libgcrypt1 was added for the libc6 package only but
not the libc6.1 package?

Adrian

> [1] 
> https://buildd.debian.org/status/fetch.php?pkg=gcc-10=alpha=10-20191217-1=1577462848=0

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

[Holger Levsen]

On Sat, Dec 28, 2019 at 12:16:23PM +0100, Nis Martensen wrote:
> On 27.12.2019 Holger Levsen wrote:
> > I do hope to do a final piuparts upload in 2019. We'll see if I manage 
> > during 36c3 ;)
> Just submitted a few more merge requests for the remaining issues I
> could find.

awesome, all merged, now deploying & testing. upload coming soon too.

> Good luck and have fun! :)

you too! :)


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

Processed: tagging 947515

[Debian Bug Tracking System]

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

> # fixed in 1a0dc62182bd438bc8ae408c67012ed7be602dd0 and merged in 
> ef1780cbc5c3c4ce30f60bfc94d6a02f570562ff
> tags 947515 + pending
Bug #947515 [src:quitcount] quitcount: build-depends on obsolete libunique-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#947597: gitless: autopkgtests fails with python-pygit2 (1.0.1-1)

[Ondřej Nový]

Package: gitless
Version: 0.8.8-1
Severity: serious

Hi,

autopkgtests of gitless package in unstable fails with new python-pygit2 
version 1.0.1-1.

Problem is with pinned pygit2 deps: pygit2<0.29

See:
https://ci.debian.net/data/autopkgtest/testing/amd64/g/gitless/3789221/log.gz
https://qa.debian.org/excuses.php?package=python-pygit2
https://sources.debian.org/src/gitless/0.8.8-1/debian/patches/relax-pygit2-dep.patch/#L16

Thanks for fixing,
Ondrej Novy

Processed: closing 945741

[Debian Bug Tracking System]

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

> close 945741 0.1.20171010-2
Bug #945741 [src:tcvt] tcvt: Python2 removal in sid/bullseye
Marked as fixed in versions tcvt/0.1.20171010-2.
Bug #945741 [src:tcvt] tcvt: Python2 removal in sid/bullseye
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#945741: closing 945741

[Ferenc Wágner]

close 945741 0.1.20171010-2
thanks

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

[Debian Bug Tracking System]

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

> tags 937552 +pending
Bug #937552 [src:pysvn] pysvn: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#937552: pysvn: Python2 removal in sid/bullseye

[peter green]

tags 937552 +pending
thanks

svn-workbench has now been kicked out of testing, so I have decided to go ahead 
with NMUing pysvn. During prep for the NMU I noticed the clean target was 
broken, so I fixed that too.

debdiff is attatched, NMU is in delayed/5


diff -Nru pysvn-1.9.9/debian/changelog pysvn-1.9.9/debian/changelog
--- pysvn-1.9.9/debian/changelog2019-10-31 01:10:08.0 +
+++ pysvn-1.9.9/debian/changelog2019-12-28 11:03:00.0 +
@@ -1,3 +1,12 @@
+pysvn (1.9.9-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Fix clean target
+  [Gianfranco Costamagna]
+  * Drop python2 package (Closes: #937552)
+
+ -- Peter Michael Green   Sat, 28 Dec 2019 11:03:00 +
+
 pysvn (1.9.9-2) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru pysvn-1.9.9/debian/control pysvn-1.9.9/debian/control
--- pysvn-1.9.9/debian/control  2019-10-31 01:10:08.0 +
+++ pysvn-1.9.9/debian/control  2019-12-28 11:02:36.0 +
@@ -10,10 +10,6 @@
  libaprutil1-dev,
  libneon27-gnutls-dev,
  libsvn-dev (>= 1.8.10),
- python-all-dbg,
- python-all-dev (>= 2.7.8),
- python-cxx-dev (>= 7.0.1),
- python-setuptools,
  python3-all (>= 3.4.2),
  python3-all-dev (>= 3.4.2),
  python3-setuptools (>= 5.5.1),
@@ -26,15 +22,6 @@
 Vcs-Git: https://salsa.debian.org/python-team/modules/pysvn.git
 Vcs-Browser: https://salsa.debian.org/python-team/modules/pysvn
 
-Package: python-svn
-Architecture: any
-Depends: ${misc:Depends}, ${python:Depends}, ${shlibs:Depends}
-Provides: python-pysvn
-Description: A(nother) Python interface to Subversion
- The pysvn module is a Python interface to the Subversion version
- control system.  This API exposes client interfaces for managing a
- working copy, querying a repository, and synchronizing the two.
-
 Package: python3-svn
 Architecture: any
 Depends: ${misc:Depends}, ${python3:Depends}, ${shlibs:Depends}
diff -Nru pysvn-1.9.9/debian/python-svn.dirs pysvn-1.9.9/debian/python-svn.dirs
--- pysvn-1.9.9/debian/python-svn.dirs  2019-10-31 01:10:08.0 +
+++ pysvn-1.9.9/debian/python-svn.dirs  1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/python2.7/dist-packages/pysvn
diff -Nru pysvn-1.9.9/debian/python-svn.doc-base 
pysvn-1.9.9/debian/python-svn.doc-base
--- pysvn-1.9.9/debian/python-svn.doc-base  2019-10-31 01:10:08.0 
+
+++ pysvn-1.9.9/debian/python-svn.doc-base  1970-01-01 00:00:00.0 
+
@@ -1,12 +0,0 @@
-Document: pysvn
-Title: pysvn - Python interface to Subversion
-Author: Barry A. Scott
-Abstract: This document contains the pysvn Programmer's Guide (covering the
- use of pysvn in a tutorial style with lots of examples) and the pysvn
- Programmer's Reference (detailed descriptions of all the classes, functions
- and variables of pysvn).
-Section: Programming/Python
-
-Format: HTML
-Index: /usr/share/doc/python-svn/pysvn.html
-Files: /usr/share/doc/python-svn/*.html
diff -Nru pysvn-1.9.9/debian/python-svn.docs pysvn-1.9.9/debian/python-svn.docs
--- pysvn-1.9.9/debian/python-svn.docs  2019-10-31 01:10:08.0 +
+++ pysvn-1.9.9/debian/python-svn.docs  1970-01-01 00:00:00.0 +
@@ -1,2 +0,0 @@
-Docs/*.html
-Docs/*.js
diff -Nru pysvn-1.9.9/debian/python-svn.examples 
pysvn-1.9.9/debian/python-svn.examples
--- pysvn-1.9.9/debian/python-svn.examples  2019-10-31 01:10:08.0 
+
+++ pysvn-1.9.9/debian/python-svn.examples  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-Examples/*
diff -Nru pysvn-1.9.9/debian/python-svn.install 
pysvn-1.9.9/debian/python-svn.install
--- pysvn-1.9.9/debian/python-svn.install   2019-10-31 01:10:08.0 
+
+++ pysvn-1.9.9/debian/python-svn.install   1970-01-01 00:00:00.0 
+
@@ -1,2 +0,0 @@
-Source/pysvn/python2/__init__.py   usr/lib/python2.7/dist-packages/pysvn/
-Source/pysvn/python2/_pysvn_2_7.so usr/lib/python2.7/dist-packages/pysvn/
diff -Nru pysvn-1.9.9/debian/rules pysvn-1.9.9/debian/rules
--- pysvn-1.9.9/debian/rules2019-10-31 01:10:08.0 +
+++ pysvn-1.9.9/debian/rules2019-12-28 11:03:00.0 +
@@ -8,27 +8,13 @@
 
 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH)
 
-PYVERS := $(shell pyversions -vr debian/control)
 PY3VERS := $(shell py3versions -vr debian/control)
 APR_INC= $(strip $(shell apr-config --includes | sed 's/-I//'))
 
-
-CONFIG_OPTS = --pycxx-src-dir=/usr/share/python${PYVERS}/CXX \
- --pycxx-dir=/usr/include/python${PYVERS} \
- --svn-lib-dir=/usr/lib/$(DEB_HOST_MULTIARCH) \
-  --apr-inc-dir=$(APR_INC) \
-  --apu-inc-dir=$(APR_INC) \
- --apr-lib-dir=/usr/lib/$(DEB_HOST_MULTIARCH) \
-  --norpath \
-  --platform=$(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
-
-
 %:
-   dh $@ --with=python2,python3 --buildsystem=pybuild
+   dh $@ --with=python3 --buildsystem=pybuild
 
 override_dh_auto_configure:
-   cd 

Bug#937293: [Piuparts-devel] Bug#919170: Bug#919170: Please update dependency to python3-debianbts

[Nis Martensen]

On 27.12.2019 Holger Levsen wrote:
> I do hope to do a final piuparts upload in 2019. We'll see if I manage during 
> 36c3 ;)

Just submitted a few more merge requests for the remaining issues I
could find.

Good luck and have fun! :)

Bug#946730: marked as done (libconfig-model-itself-perl: autopkgtest needs update for new version of libconfig-model-perl)

[Debian Bug Tracking System]

Your message dated Sat, 28 Dec 2019 10:51:11 +
with message-id 
and subject line Bug#946730: fixed in libconfig-model-itself-perl 2.019-1
has caused the Debian Bug report #946730,
regarding libconfig-model-itself-perl: autopkgtest needs update for new version 
of libconfig-model-perl
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.)


-- 
946730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libconfig-model-itself-perl
Version: 2.018-2
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:libconfig-model-perl
Control: affects -1 src:libconfig-model-tkui-perl

[X-Debbugs-CC: debian...@lists.debian.org,
libconfig-model-p...@packages.debian.org]

Dear maintainers,

With a recent upload of libconfig-model-perl the autopkgtest of
libconfig-model-itself-perl fails in testing when that autopkgtest is
run with the binary packages of libconfig-model-perl from unstable. It
passes when run with only packages from testing. In tabular form:
passfail
libconfig-model-perlfrom testing2.137-1
libconfig-model-itself-perl from testing2.018-2
all others  from testingfrom testing

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

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

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from libconfig-model-perl
should really add a versioned Breaks on the unfixed version of (one of
your) package(s). Note: the Breaks is nice even if the issue is only in
the autopkgtest as it helps the migration software to figure out the
right versions to combine in the tests.

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

Paul

[1] https://qa.debian.org/excuses.php?package=libconfig-model-perl

https://ci.debian.net/data/autopkgtest/testing/amd64/libc/libconfig-model-itself-perl/3660573/log.gz

not ok 6 - Compared the 2 full dumps

#   Failed test 'Compared the 2 full dumps'
#   at t/load_write_itself.t line 68.
#  got: '@@ -5,9 +5,11 @@
#  refer_to="! class"
#  computed_refer_to
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -20,6 +22,7 @@
#  value_type=uniline
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -32,6 +35,7 @@
#  value_type=uniline
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -44,6 +48,7 @@
#  value_type=enum
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -60,6 +65,7 @@
#  value_type=boolean
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -73,6 +79,7 @@
#  value_type=boolean
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -86,6 +93,7 @@
#  value_type=boolean
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -99,6 +107,7 @@
#  value_type=uniline
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -111,6 +120,7 @@
#  value_type=uniline
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -123,6 +133,7 @@
#  value_type=uniline
#  compute
#use_eval=0
# +  allow_override=0
#use_as_upstream_default=0 -
#  migrate_from
#use_eval=0 -
# @@ -140,6 +151,7 @@
#  value_type=enum
#  compute
#  

Bug#945741: tcvt: Python2 removal in sid/bullseye

[wferi]

wf...@niif.hu writes:

> Helmut Grohne  writes:
>
>> On Wed, Nov 27, 2019 at 11:58:53PM +, Sandro Tosi wrote:
>>
>>> - Convert your Package to Python3. This is the preferred option.
>>
>> Upstream here. While tcvt started on Python2, much of its development
>> actually happend on Python3, so just changing the #! should work.
>
> And I wanted to package it for Python3 in the first place.  I'm puzzled
> that it uses Python2 despite dh --with python3 and the python3 build
> dependency.  I'd be grateful for an explanation or some suggestions.

Maybe I expected too much of dh_python3.  Patching the interpreter name
to /usr/bin/python3 works of course, I'm just not sure it's best
practice.
-- 
Regards,
Feri

Processed: Re: Bug#885140: wicd: Depends on unmaintained pygtk

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.7.4+tb2+2019.09.18git2e0ba579-1
Bug #885140 [src:wicd] wicd: Depends on unmaintained pygtk
Marked as fixed in versions wicd/1.7.4+tb2+2019.09.18git2e0ba579-1.

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

Bug#885140: wicd: Depends on unmaintained pygtk

[Simon McVittie]

Control: fixed -1 1.7.4+tb2+2019.09.18git2e0ba579-1

On Sun, 24 Dec 2017 at 09:31:29 -0500, Jeremy Bicha wrote:
> The way forward is to port your app to use GObject Introspection
> bindings.

This appears to be fixed in experimental along with #938823. I'm not
closing the bug "properly" yet, because it's the status of unstable that
matters for the ability to remove pygtk; please close this bug in the first
Python 3 upload of wicd to unstable.

smcv

Processed: block 912946 with 885267 885287 885308 890157 937114 885135 878698 890168 885476 885527 885486 938637 885140

[Debian Bug Tracking System]

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

> block 912946 with 885267 885287 885308 890157 937114 885135 878698 890168 
> 885476 885527 885486 938637 885140
Bug #912946 [src:pygobject-2] pygobject-2: deprecated and unmaintained upstream
912946 was blocked by: 872707 890162 912953 912955 890148 912960 912959 912954 
885135 912964 885752 890168 890151 912965 912963 912962 885509 890157 912961 
912958 884935 890159 884986 890171 890169 890150 712457 890172 878698 770315 
912966
912946 was not blocking any bugs.
Added blocking bug(s) of 912946: 885267, 938637, 937114, 885140, 885527, 
885287, 885308, 885476, and 885486
> thanks
Stopping processing here.

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

Processed: block 912946 with 890148 890172 890151 890162 890168 890171 890150 890157 890169

[Debian Bug Tracking System]

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

> block 912946 with 890148 890172 890151 890162 890168 890171 890150 890157 
> 890169
Bug #912946 [src:pygobject-2] pygobject-2: deprecated and unmaintained upstream
912946 was blocked by: 912955 912962 884986 912954 885135 712457 770315 912953 
912966 912964 885752 878698 912960 912963 872707 912965 912958 912961 912959 
884935 885509 890159
912946 was not blocking any bugs.
Added blocking bug(s) of 912946: 890171, 890150, 890169, 890162, 890172, 
890157, 890148, 890168, and 890151
> thanks
Stopping processing here.

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