Bug#978957: marked as done (gvmd: Version in testing FTBFS against libgvm-dev in sid manage.c:4179:16: error: too few arguments to function 'osp_target_new')

[Debian Bug Tracking System]

Your message dated Fri, 1 Jan 2021 08:09:55 +0100
with message-id 
and subject line Re: Bug#978957: gvmd: Version in testing FTBFS against 
libgvm-dev in sid manage.c:4179:16: error: too few arguments to function 
'osp_target_new'
has caused the Debian Bug report #978957,
regarding gvmd: Version in testing FTBFS against libgvm-dev in sid 
manage.c:4179:16: error: too few arguments to function 'osp_target_new'
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.)


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

Hello,

this is mainly a tracking bug for other people wondering about failing
CI in testing. - I will do a versioned close, once I have a bugnumber.

gvmd 9.0.1 (testing) seems to be incompatible with libgvm-dev as present
in sid since the prototype for 'osp_target_new' has changed.

cu Andreas

[ 13%] Building C object src/CMakeFiles/gvmd.dir/manage.c.o
cd /dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu/src && /usr/lib/ccache/cc 
-DBINDIR=\"/usr/bin\" -DCACERT=\"/var/lib/gvm/CA/cacert.pem\" 
-DCA_DIR=\"/var/lib/gvm/gvmd/trusted_certs\" 
-DCLIENTCERT=\"/var/lib/gvm/CA/clientcert.pem\" 
-DCLIENTKEY=\"/var/lib/gvm/private/CA/clientkey.pem\" -DGMP_VERSION=\"9.0\" 
-DGVMD_CERT_DATABASE_VERSION=6 -DGVMD_DATABASE_VERSION=221 
-DGVMD_DATA_DIR=\"/usr/share/gvm/gvmd\" -DGVMD_SCAP_DATABASE_VERSION=16 
-DGVMD_STATE_DIR=\"/var/lib/gvm/gvmd\" -DGVMD_VERSION=\"9.0.1\" 
-DGVM_CERT_DATA_DIR=\"/var/lib/gvm/cert-data\" 
-DGVM_CERT_RES_DIR=\"/usr/share/gvm/cert\" -DGVM_DATA_DIR=\"/usr/share/gvm\" 
-DGVM_LIB_INSTALL_DIR=\"/usr/lib\" -DGVM_LOG_DIR=\"/var/log/gvm\" 
-DGVM_NVT_DIR=\"/var/lib/openvas/plugins/\" 
-DGVM_OS_NAME=\"Linux-5.9.0-5-amd64\" -DGVM_RUN_DIR=\"/var/run/gvm\" 
-DGVM_SCAP_DATA_DIR=\"/var/lib/gvm/scap-data\" 
-DGVM_SCAP_RES_DIR=\"/usr/share/gvm/scap\" -DGVM_STATE_DIR=\"/var/lib/gvm\" 
-DGVM_SYSCONF_DIR=\"/etc/gvm\" -DPREFIX=\"/usr\" 
-DSCANNERCERT=\"/var/lib/gvm/CA/servercert.pem\" 
-DSCANNERKEY=\"/var/lib/gvm/private/CA/serverkey.pem\" -I/usr/include/gvm 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/p11-kit-1 
-I/usr/include/uuid -I/usr/include/postgresql 
-I/usr/include/postgresql/13/server -g -O2 
-fdebug-prefix-map=/dev/shm/gvmd-9.0.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -D_BSD_SOURCE 
-D_ISOC99_SOURCE -D_SVID_SOURCE -D_DEFAULT_SOURCE -D_FILE_OFFSET_BITS=64 -O3 
-DNDEBUG -Wformat -Wformat-security -D_FORTIFY_SOURCE=2 -fstack-protector 
-Wredundant-decls -o CMakeFiles/gvmd.dir/manage.c.o -c 
/dev/shm/gvmd-9.0.1/src/manage.c
/dev/shm/gvmd-9.0.1/src/manage.c: In function 'launch_osp_openvas_task':
/dev/shm/gvmd-9.0.1/src/manage.c:4179:16: error: too few arguments to function 
'osp_target_new'
 4179 |   osp_target = osp_target_new (hosts_str, ports_str, exclude_hosts_str);
  |^~
In file included from /dev/shm/gvmd-9.0.1/src/manage.h:40,
 from /dev/shm/gvmd-9.0.1/src/manage.c:50:
/usr/include/gvm/osp/osp.h:203:1: note: declared here
  203 | osp_target_new (const char *, const char *, const char *, int, int, 
int);
  | ^~
/dev/shm/gvmd-9.0.1/src/manage.c:4413:18: error: 'osp_start_scan_opts_t' has no 
member named 'parallel'
 4413 |   start_scan_opts.parallel = 1;
  |  ^
make[3]: *** [src/CMakeFiles/gvmd.dir/build.make:137: 
src/CMakeFiles/gvmd.dir/manage.c.o] Error 1
make[3]: Leaving directory '/dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:178: src/CMakeFiles/gvmd.dir/all] Error 2
make[2]: Leaving directory '/dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:185: all] Error 2
make[1]: Leaving directory '/dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:6: binary] Error 25
--- End Message ---
--- Begin Message ---
Version: 20.8.0+git2020-1

On 2021-01-01 Andreas Metzler  wrote:
> Package: gvmd
> Version: 9.0.1-4.1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)

> Hello,

> this is mainly a tracking bug for other people wondering about failing
> CI in testing. - I will do a versioned close, once I have a bugnumb

Bug#978957: gvmd: Version in testing FTBFS against libgvm-dev in sid manage.c:4179:16: error: too few arguments to function 'osp_target_new'

[Andreas Metzler]

Package: gvmd
Version: 9.0.1-4.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello,

this is mainly a tracking bug for other people wondering about failing
CI in testing. - I will do a versioned close, once I have a bugnumber.

gvmd 9.0.1 (testing) seems to be incompatible with libgvm-dev as present
in sid since the prototype for 'osp_target_new' has changed.

cu Andreas

[ 13%] Building C object src/CMakeFiles/gvmd.dir/manage.c.o
cd /dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu/src && /usr/lib/ccache/cc 
-DBINDIR=\"/usr/bin\" -DCACERT=\"/var/lib/gvm/CA/cacert.pem\" 
-DCA_DIR=\"/var/lib/gvm/gvmd/trusted_certs\" 
-DCLIENTCERT=\"/var/lib/gvm/CA/clientcert.pem\" 
-DCLIENTKEY=\"/var/lib/gvm/private/CA/clientkey.pem\" -DGMP_VERSION=\"9.0\" 
-DGVMD_CERT_DATABASE_VERSION=6 -DGVMD_DATABASE_VERSION=221 
-DGVMD_DATA_DIR=\"/usr/share/gvm/gvmd\" -DGVMD_SCAP_DATABASE_VERSION=16 
-DGVMD_STATE_DIR=\"/var/lib/gvm/gvmd\" -DGVMD_VERSION=\"9.0.1\" 
-DGVM_CERT_DATA_DIR=\"/var/lib/gvm/cert-data\" 
-DGVM_CERT_RES_DIR=\"/usr/share/gvm/cert\" -DGVM_DATA_DIR=\"/usr/share/gvm\" 
-DGVM_LIB_INSTALL_DIR=\"/usr/lib\" -DGVM_LOG_DIR=\"/var/log/gvm\" 
-DGVM_NVT_DIR=\"/var/lib/openvas/plugins/\" 
-DGVM_OS_NAME=\"Linux-5.9.0-5-amd64\" -DGVM_RUN_DIR=\"/var/run/gvm\" 
-DGVM_SCAP_DATA_DIR=\"/var/lib/gvm/scap-data\" 
-DGVM_SCAP_RES_DIR=\"/usr/share/gvm/scap\" -DGVM_STATE_DIR=\"/var/lib/gvm\" 
-DGVM_SYSCONF_DIR=\"/etc/gvm\" -DPREFIX=\"/usr\" 
-DSCANNERCERT=\"/var/lib/gvm/CA/servercert.pem\" 
-DSCANNERKEY=\"/var/lib/gvm/private/CA/serverkey.pem\" -I/usr/include/gvm 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/p11-kit-1 
-I/usr/include/uuid -I/usr/include/postgresql 
-I/usr/include/postgresql/13/server -g -O2 
-fdebug-prefix-map=/dev/shm/gvmd-9.0.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -D_BSD_SOURCE 
-D_ISOC99_SOURCE -D_SVID_SOURCE -D_DEFAULT_SOURCE -D_FILE_OFFSET_BITS=64 -O3 
-DNDEBUG -Wformat -Wformat-security -D_FORTIFY_SOURCE=2 -fstack-protector 
-Wredundant-decls -o CMakeFiles/gvmd.dir/manage.c.o -c 
/dev/shm/gvmd-9.0.1/src/manage.c
/dev/shm/gvmd-9.0.1/src/manage.c: In function 'launch_osp_openvas_task':
/dev/shm/gvmd-9.0.1/src/manage.c:4179:16: error: too few arguments to function 
'osp_target_new'
 4179 |   osp_target = osp_target_new (hosts_str, ports_str, exclude_hosts_str);
  |^~
In file included from /dev/shm/gvmd-9.0.1/src/manage.h:40,
 from /dev/shm/gvmd-9.0.1/src/manage.c:50:
/usr/include/gvm/osp/osp.h:203:1: note: declared here
  203 | osp_target_new (const char *, const char *, const char *, int, int, 
int);
  | ^~
/dev/shm/gvmd-9.0.1/src/manage.c:4413:18: error: 'osp_start_scan_opts_t' has no 
member named 'parallel'
 4413 |   start_scan_opts.parallel = 1;
  |  ^
make[3]: *** [src/CMakeFiles/gvmd.dir/build.make:137: 
src/CMakeFiles/gvmd.dir/manage.c.o] Error 1
make[3]: Leaving directory '/dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:178: src/CMakeFiles/gvmd.dir/all] Error 2
make[2]: Leaving directory '/dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:185: all] Error 2
make[1]: Leaving directory '/dev/shm/gvmd-9.0.1/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:6: binary] Error 25

Processed: tagging 978952, severity of 978952 is normal

[Debian Bug Tracking System]

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

> tags 978952 + moreinfo
Bug #978952 [wsjtx] wsjtx: No audio on transmit
Added tag(s) moreinfo.
> severity 978952 normal
Bug #978952 [wsjtx] wsjtx: No audio on transmit
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#978952: wsjtx: No audio on transmit

[tony mancill]

On Fri, Jan 01, 2021 at 04:08:57AM +, Hilary Snaden wrote:
> Package: wsjtx
> Version: 2.3.0~rc2+repack-1+b1
> Severity: grave
> Justification: renders package unusable
> 
> There is no audio output to any of the listed devices (I have tried them 
> all). This was also the case with version 2.2.2,
> 
> Operation in receive mode is mostly satisfactory.

Hi,

Please provide more information about your setup so we can try to
determine if this is an issue with the software or with your local
configuration.  That you had the same issue with 2.2.2 leads me to
suspect latter.  Both 2.3.0-rc2 and 2.2.2 wsjtx have been working fine
for me.

I am changing the severity of this bug from grave [1], as that severity
has the potential to remove the package from the archive for all users.

Thank you,
tony

[1] https://www.debian.org/Bugs/Developer#severities


signature.asc
Description: PGP signature

Bug#978954: pepperflashplugin-nonfree: should not be part of next stable Debian release

[Ying-Chun Liu (PaulLiu)]

Package: pepperflashplugin-nonfree
Version: 1.8.7
Severity: grave
Justification: renders package unusable

Dear Maintainer,

flash has been EOL today. Browsers are starting to block flash.
I think we should block this package goes into next release?

Yours,
Paul

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

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_TW:en_US
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pepperflashplugin-nonfree depends on:
ii  binutils 2.35.1-6
ii  ca-certificates  20200601
ii  libgcc-s110.2.1-3
ii  libstdc++6   10.2.1-3
ii  wget 1.20.3-1+b3

pepperflashplugin-nonfree recommends no packages.

Versions of packages pepperflashplugin-nonfree suggests:
ii  chromium   83.0.4103.116-3.1+b2
pn  ttf-dejavu 
pn  ttf-mscorefonts-installer  
pn  ttf-xfree86-nonfree

-- no debconf information


signature.asc
Description: PGP signature

Bug#974546: marked as done (klatexformula FTBFS: error: invalid use of incomplete type ‘class QPainterPath’)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 02:19:02 +
with message-id 
and subject line Bug#974546: fixed in klatexformula 4.1.0-1
has caused the Debian Bug report #974546,
regarding klatexformula FTBFS: error: invalid use of incomplete type ‘class 
QPainterPath’
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.)


-- 
974546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: klatexformula
Version: 4.0.0-4
Severity: serious
Tags: ftbfs

klatexformula fails to build from source in unstable:

| [ 27%] Building CXX object 
src/klftools/CMakeFiles/klftools.dir/klfflowlistwidget.cpp.o
| cd /<>/obj-x86_64-linux-gnu/src/klftools && /usr/bin/c++ 
-DKLF_SRC_BUILD -DKLF_VERSION_MAJ=4 -DKLF_VERSION_MIN=0 -DKLF_VERSION_REL=0 
-DKLF_VERSION_STRING=\"4.0.0\" -DKLF_WS=\"x11\" -DKLF_WS_X11 -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_XML_LIB -Dklftools_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/src/klftools 
-I/<>/src/klftools -isystem /usr/include/x86_64-linux-gnu/qt5 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -fPIC -o 
CMakeFiles/klftools.dir/klfflowlistwidget.cpp.o -c 
/<>/src/klftools/klfflowlistwidget.cpp
| In file included from /<>/src/klftools/klfflowlistwidget.cpp:29:
| /<>/src/klftools/klfflowlayout.h:65:96: warning: ‘constexpr 
QFlags::QFlags(QFlags::Zero) [with Enum = Qt::AlignmentFlag; 
QFlags::Zero = int QFlags::Private::*]’ is deprecated: 
Use default constructor instead [-Wdeprecated-declarations]
|65 |   virtual void addWidget(QWidget *w, int hstretch = 0, int vstretch = 
0, Qt::Alignment align = 0);
|   |   
 ^
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qglobal.h:1304,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtGui/qtguiglobal.h:43,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qtwidgetsglobal.h:43,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:43,
|  from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
|  from /<>/src/klftools/klfflowlistwidget.cpp:24:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qflags.h:123:80: note: declared here
|   123 | QT_DEPRECATED_X("Use default constructor instead") 
Q_DECL_CONSTEXPR inline QFlags(Zero) noexcept : i(0) {}
|   |   
 ^~
| In file included from /<>/src/klftools/klfflowlistwidget.cpp:31:
| /<>/src/klftools/klfflowlistwidget_p.h:286:16: error: field 
‘box’ has incomplete type ‘QPainterPath’
|   286 |   QPainterPath box;
|   |^~~
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qbrush.h:49,
|  from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpalette.h:46,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:48,
|  from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
|  from /<>/src/klftools/klfflowlistwidget.cpp:24:
| /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix.h:54:7: note: forward 
declaration of ‘class QPainterPath’
|54 | class QPainterPath;
|   |   ^~~~
| In file included from /<>/src/klftools/klfflowlistwidget.cpp:31:
| /<>/src/klftools/klfflowlistwidget_p.h:287:16: error: field 
‘crossbox’ has incomplete type ‘QPainterPath’
|   287 |   QPainterPath crossbox;
|   |^~~~
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qbrush.h:49,
|  from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpalette.h:46,
|  from 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:48,
|  from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QWidget:1,
|  from /<>/src/klftools/klfflowlistwidget.cpp:24:
| /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix.h:54:7: note: forward 
declaration of ‘class QPainterPath’
|54 | class QPainterPath;
|   |   ^~~~
| In file included from /<>/src/klftools/klfflowlistwidget.cpp:31:
| /<>/src/klftools/klfflowlistwidget_p.h: In member function 
‘virtual void KLFFlowListI

Bug#960454: chromium: Make Chromium ask before downloading and enabling DRM

[Christoph Anton Mitterer]

Hey.


Just wondered:


1) Since this is a binary blob who, by it's nature, is made for
surveillance, it's IMO more a rather serious security issue than just a
DFSG-policy problem.
No one really knows what exactly Google ships there.

So maybe people should be told about this more actively in a DSA or
NEWS.Debian entry?



2) To my great surprise (and shock - due to the compromise) I found the
binaries downloaded last July, even though I never used chromium on any
site that uses EME or things like that.
Which makes this behaviour even more suspicious.



3) AFAIU, now the Debian package no longer downloads it automatically
(with widevine-cdm-cu.patch), but many people will still have it
silently in place (and presumably executed). Which is again kinda a
point for (1).



4) This problem of browsers downloading their own closed-source and
possibly compromised stuff has already surfaced in the past.
Wouldn't it be safer to completely remove the code doing at all?
Right now we have widevine-cdm-cu.patch which is fine for just this,
and as soon as Google would add something new it would probably get
downloaded&executed again until someone notices by chance.


In general, I think it's pretty bad if software circumvents secure APT
do download further software:

- there is no central security support (just imagine an attacked simply
blocks any time chromium tries to upgrade the binary blobs) and
people will not even notice if upgrades from within the software fail.

- it's not taken into account by tools like check_apt either

- unless someone knows that Chromium puts software in .config it will
stay there forever and not begin removed or so when the chromium
package would be removed

- an evil Google could just selectively distribute hacked versions of
their binaries - something which is more or less impossible when all
software comes via secure APT

- doing package upgrade really in a secure way (i.e. preventing
blocking attacks, downgrade attacks, or just not using
outdated/insecure algorithms) is actually not that easy and I've seen
many downloader packages doing it wrong - with secure APT there's one
central place where all this is handled (securely)



Cheers,
Chris.

Processed: tagging 974546, tagging 974856

[Debian Bug Tracking System]

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

> tags 974546 + pending
Bug #974546 [src:klatexformula] klatexformula FTBFS: error: invalid use of 
incomplete type ‘class QPainterPath’
Added tag(s) pending.
> tags 974856 + pending
Bug #974856 [sponsorship-requests] RFS: klatexformula/4.1.0-1 [RC] -- GUI to 
easily get an image from a LaTeX formula or equation
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#957320: marked as done (gtkpod: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 01:18:55 +
with message-id 
and subject line Bug#957320: fixed in gtkpod 2.1.5-8
has caused the Debian Bug report #957320,
regarding gtkpod: ftbfs with GCC-10
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.)


-- 
957320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gtkpod
Version: 2.1.5-7
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/gtkpod_2.1.5-7_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
  |   ^
context_menus.c: In function ‘add_edit_track_details’:
context_menus.c:270:5: warning: ‘GtkStock’ is deprecated 
[-Wdeprecated-declarations]
  270 | return hookup_menu_item(menu, _("Edit Track Details"), 
GTK_STOCK_PREFERENCES, G_CALLBACK (edit_track_details), NULL);
  | ^~
context_menus.c: In function ‘add_copy_track_to_filesystem’:
context_menus.c:293:15: warning: ‘GtkStock’ is deprecated 
[-Wdeprecated-declarations]
  293 |   GTK_STOCK_SAVE_AS,
  |   ^
In file included from autodetection.c:39:
misc.h:86:1: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead 
[-Wdeprecated-declarations]
   86 | float get_ms_since (GTimeVal *old_time, gboolean update);
  | ^
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/glib-2.0/glib/gi18n-lib.h:21,
 from autodetection.c:34:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-DPACKAGE_DATA_DIR=\"/usr/share\" -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" 
-DPACKAGE_PLUGIN_DIR=\"/usr/lib/x86_64-linux-gnu\" -DPACKAGE_SRC_DIR=\".\" 
-DGTKPOD_PLUGIN_DIR=\"/usr/lib/x86_64-linux-gnu/gtkpod\" 
-DGTKPOD_DATA_DIR=\"/usr/share/gtkpod/data\" 
-DGTKPOD_DOC_DIR=\"/usr/share/gtkpod/doc\" 
-DGTKPOD_UI_DIR=\"/usr/share/gtkpod/data/ui\" 
-DGTKPOD_GLADE_DIR=\"/usr/share/gtkpod/data/glade\" 
-DGTKPOD_IMAGE_DIR=\"/usr/share/gtkpod/icons\" 
-DGTKPOD_SCRIPT_DIR=\"/usr/share/gtkpod/scripts\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -Wno-pointer-sign -std=gnu99 
-Werror-implicit-function-declaration -Werror=format-security -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/ca
 iro -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount 
-I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 
-I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid 
-I/usr/include/freetype

Bug#978325: marked as done (libgit-repository-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 00:34:19 +
with message-id 
and subject line Bug#978325: fixed in libgit-repository-perl 1.324-2
has caused the Debian Bug report #978325,
regarding libgit-repository-perl: FTBFS: dh_auto_test: error: make -j4 test 
TEST_VERBOSE=1 returned exit code 2
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.)


-- 
978325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgit-repository-perl
Version: 1.324-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/00-compile.t . 
> 1..4
> ok 1 - Git/Repository.pm loaded ok
> ok 2 - Git/Repository/Command.pm loaded ok
> ok 3 - Git/Repository/Plugin.pm loaded ok
> ok 4 - Test/Git.pm loaded ok
> ok
> # 
> # Versions for all modules listed in MYMETA.json (including optional ones):
> # 
> # === Configure Requires ===
> # 
> # Module  Want Have
> # ---  
> # ExtUtils::MakeMaker  any 7.44
> # 
> # === Build Requires ===
> # 
> # Module  Want Have
> # ---  
> # ExtUtils::MakeMaker  any 7.44
> # 
> # === Test Requires ===
> # 
> # Module   Want Have
> # --- - 
> # ExtUtils::MakeMaker   any 7.44
> # File::Pathany 2.16
> # File::Specany 3.78
> # IO::Handleany 1.42
> # IPC::Open3any 1.21
> # Test::Moreany 1.302175
> # Test::Requires::Git 1.0051.008
> # constant  any 1.33
> # lib   any 0.65
> # overload  any 1.31
> # 
> # === Test Recommends ===
> # 
> # Module Want Have
> # --  
> # CPAN::Meta 2.120900 2.150010
> # 
> # === Runtime Requires ===
> # 
> # Module Want Have
> # - - 
> # Carpany 1.50
> # Cwd any 3.78
> # Exporterany 5.74
> # File::Spec  any 3.78
> # File::Spec::Functions   any 3.78
> # File::Temp  any   0.2309
> # Git::Version::Compare 1.0011.004
> # IO::Handle  any 1.42
> # Scalar::Utilany 1.55
> # System::Command   1.1181.121
> # Test::Builder   any 1.302175
> # namespace::cleanany 0.27
> # strict  any 1.11
> # warningsany 1.47
> # 
> t/00-report-prereqs.t .. 
> 1..1
> ok 1
> ok
> # Testing _is_git with /usr/bin/git from /<>
> # Testing _is_git with ../../../usr/bin/git from /<>
> t/05-try_git.t . 
> 1..36
> ok 1 - _is_git( this-command-unlikely-to-even-exist-or-be-git ) fails with 
> bad git command
> ok 2 - run() fails with bad git command
> ok 3 - ... with expected error message
> ok 4 - _is_git( 
> /<>/this-command-unlikely-to-even-exist-or-be-git ) fails with 
> bad git command
> ok 5 - run() fails with bad git command
> ok 6 - ... with expected error message
> ok 7 - _is_git( ../this-command-unlikely-to-even-exist-or-be-git ) fails with 
> bad git command
> ok 8 - run() fails with bad git command
> ok 9 - ... with expected error message
> ok 10 - _is_git( /usr/bin/perl ) fails with bad git command
> ok 11 - run() fails with bad git command
> ok 12 - ... with expected error message
> ok 13 - _is_git( git ) fails with bad git command
> ok 14 - run() fails with bad git command
> ok 15 - ... with expected error message
> ok 16 - _is_git( t ) fails with bad git command
> ok 17 - run() fails with bad git command
> ok 18 - ... with expected error message
> ok 19 - _is_git( /usr/bin/git ) 
> ok 20 - _is_git( ../../../usr/bin/git ) 
> ok 21 - real -> /usr/bin/git
> ok 22 - symlink to git
> ok 23 - link -> target
> ok 24 - dangling symlink
> ok 25 - link -> target/
> ok 26 - symlink to a dir
> ok 27 - sub/link -> /usr/bin/git 
> ok 28 - symlink to git
> ok 29 - real -> /usr/bin/git
> ok 30 - symlink to git
> ok 31 - link -> target
> ok 32 - dangling symlink
> ok 33 - li

Bug#978375: marked as done (gkdebconf: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.20)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 00:33:23 +
with message-id 
and subject line Bug#978375: fixed in gkdebconf 2.1.1
has caused the Debian Bug report #978375,
regarding gkdebconf: FTBFS: error: gettext infrastructure mismatch: using a 
Makefile.in.in from gettext version 0.19 but the autoconf macros are from 
gettext version 0.20
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.)


-- 
978375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gkdebconf
Version: 2.1.0
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> Making all in po
> make[3]: Entering directory '/<>/po'
> *** error: gettext infrastructure mismatch: using a Makefile.in.in from 
> gettext version 0.19 but the autoconf macros are from gettext version 0.20
> make[3]: *** [Makefile:168: stamp-po] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/gkdebconf_2.1.0_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: gkdebconf
Source-Version: 2.1.1
Done: Håvard Flaget Aasen 

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

Debian distribution maintenance software
pp.
Håvard Flaget Aasen  (supplier of updated gkdebconf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 10:57:24 +0100
Source: gkdebconf
Architecture: source
Version: 2.1.1
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Håvard Flaget Aasen 
Closes: 978115 978375
Changes:
 gkdebconf (2.1.1) unstable; urgency=low
 .
   * QA upload.
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Helge Kreutzmann ]
   * Update German translation (Closes: #978115)
 .
   [ Håvard Flaget Aasen ]
   * d/control:
 - Bump debhelper to 13
 - Update Standards-Version to 4.5.1
   * Rename d/NEWS.debian to d/NEWS and change distribution
 from unreleased to unstable.
   * Drop de_DE.po and es_ES.po translation, rely on de.po and es.po instead
   * Require gettext 0.21, update with gettextize (Closes: #978375)
Checksums-Sha1:
 d6adb406649a718626c28e1eafde7e22b3d8c750 1559 gkdebconf_2.1.1.dsc
 697f1dab6b148fa02bcaaf92104a5999f95909f8 165692 gkdebconf_2.1.1.tar.xz
 af881df3fdd69e41f4cbe6c85b61c4838611396c 13302 gkdebconf_2.1.1_source.buildinfo
Checksums-Sha256:
 c854b87884699a6f5e96506327eee6bef3b9d57a99c335c62b6df4ed868a52dc 1559 
gkdebconf_2.1.1.dsc
 a34185d4f99a89c616bdd08a4da02dae28a49d60a186908a89d1a6cfe6d3a132 165692 
gkdebconf_2.1.1.tar.xz
 5b0e948a22f44665b184d02099bad984c7835d3e0a5fe774ef31ec4b73166acb 13302 
gkdebconf_2.1.1_source.buildinfo
Files:
 a8bc996b75c27e505fe6832ce66991b7 1559 admin optional gkdebconf_2.1.1.dsc
 e3bcde4d842af3d708218fa947fd6b5d 165692 admin optional gkdebconf_2.1.1.tar.xz
 ff903f20763272802eac4c9fd67ae590 13302 admin optional 
gkdebconf_2.1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl/uaCYACgkQweDZLphv
fH6jZA/8D11m4jDmKcsGxAgSFIwnzem34gDonSTK5IzyCekYT9Gm+W9s4fYPG9rE
gmxgvs7r1Y55qjLUxDetHYcm68q0fV8P4xuAX6yfm0byxz3gFQt+CRQyK

Bug#976910: marked as done (python-blosc: FTBFS on ppc64el: KeyError: 'flags')

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 00:34:24 +
with message-id 
and subject line Bug#976910: fixed in python-blosc 1.9.2+ds1-3
has caused the Debian Bug report #976910,
regarding python-blosc: FTBFS on ppc64el: KeyError: 'flags'
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.)


-- 
976910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976910
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-blosc
Version: 1.9.2+ds1-1
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

During a rebuild of all packages in sid, your package failed to build
on ppc64el. At the same time, it did not fail on amd64.

I'm marking this bug as severity:serious since your package currently has
ppc64el binary packages in unstable (so this is a regression).

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-blosc
> dpkg-buildpackage: info: source version 1.9.2+ds1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Emmanuel Arias 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture ppc64el
>  debian/rules clean
> dh clean --with=python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
>   install -d 
> /<>/python-blosc-1.9.2\+ds1/debian/.debhelper/generated/_source/home
>   pybuild --clean -i python{version} -p 3.9
> I: pybuild base:232: python3.9 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 90, in 
> '-DDEACTIVATE_SSE2:BOOL=%s' % cmake_bool(('DISABLE_BLOSC_SSE2' in 
> os.environ) or (cpu_info is None) or ('sse2' not in cpu_info['flags'])),
> KeyError: 'flags'
> E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
> code 13
> make: *** [debian/rules:9: clean] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/09/python-blosc_1.9.2+ds1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on a Power8 cluster part of the
Grid'5000 testbed. Hardware specs: 
https://www.grid5000.fr/w/Grenoble:Hardware#drac
--- End Message ---
--- Begin Message ---
Source: python-blosc
Source-Version: 1.9.2+ds1-3
Done: Graham Inggs 

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

Debian distribution maintenance software
pp.
Graham Inggs  (supplier of updated python-blosc 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: Fri, 01 Jan 2021 00:03:56 +
Source: python-blosc
Architecture: source
Version: 1.9.2+ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Graham Inggs 
Closes: 976910
Changes:
 python-blosc (1.9.2+ds1-3) unstable; urgency=medium
 .
   * Team upload
   * Deactivate SSE2 and AVX2 if CPU has no flags (Closes: #976910)
   * Explicitly set PYBUILD_SYSTEM=distutils to avoid misdetection
   * Mark python-blosc-doc Multi-Arch: foreign
   * Bump Standards-Version to 4.5.1, no changes
Checksums-Sha1:
 c300421da7ec9e9c301db44d67e736eb33fa6659 2487 python-blosc_1.9.2+ds1-3.dsc
 044cd11abe3311165ca5252648b5741b9fc2c386 6932 
python-blosc_1.9.2+ds1-3.debian.tar.xz
Checksums-Sha256:
 81002f8b90a6093a0d43f64068480ef100efd0c95d236b40d9cb3969237bd863 2487 
python-blosc_1.9.2+ds1-3.dsc
 aa11bb1246a3e9cfe720f89763172461463a03d29c9d36b444e20a0a116e8410

Processed: Bug#978325 marked as pending in libgit-repository-perl

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978325 [src:libgit-repository-perl] libgit-repository-perl: FTBFS: 
dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2
Added tag(s) pending.

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

Bug#957912: marked as done (vinagre: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 00:20:09 +
with message-id 
and subject line Bug#957912: fixed in vinagre 3.22.0-8
has caused the Debian Bug report #957912,
regarding vinagre: ftbfs with GCC-10
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.)


-- 
957912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vinagre
Version: 3.22.0-7
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/vinagre_3.22.0-7_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html

[...]
At top level:
plugins/ssh/vinagre-ssh-plugin.c:184:1: warning: 
‘vinagre_ssh_plugin_class_finalize’ defined but not used [-Wunused-function]
  184 | vinagre_ssh_plugin_class_finalize (VinagreSshPluginClass *klass)
  | ^
plugins/ssh/vinagre-ssh-connection.c: In function ‘vinagre_ssh_connection_init’:
plugins/ssh/vinagre-ssh-connection.c:37:13: warning: G_ADD_PRIVATE
   37 |   conn->priv = G_TYPE_INSTANCE_GET_PRIVATE (conn, 
VINAGRE_TYPE_SSH_CONNECTION, VinagreSshConnectionPrivate);
  | ^~~
plugins/ssh/vinagre-ssh-connection.c: In function 
‘vinagre_ssh_connection_class_init’:
plugins/ssh/vinagre-ssh-connection.c:83:3: warning: ‘g_type_class_add_private’ 
is deprecated [-Wdeprecated-declarations]
   83 |   g_type_class_add_private (klass, sizeof 
(VinagreSshConnectionPrivate));
  |   ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:28,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gtk/gtk.h:30,
 from ./vinagre/vinagre-connection.h:26,
 from plugins/ssh/vinagre-ssh-connection.h:25,
 from plugins/ssh/vinagre-ssh-connection.c:24:
/usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here
 1308 | void g_type_class_add_private   (gpointer
g_class,
  |  ^~~~
plugins/ssh/vinagre-ssh-tab.c: In function ‘vinagre_ssh_tab_constructed’:
plugins/ssh/vinagre-ssh-tab.c:94:3: warning: ‘vte_terminal_spawn_sync’ is 
deprecated [-Wdeprecated-declarations]
   94 |   vte_terminal_spawn_sync (VTE_TERMINAL (ssh_tab->priv->vte),
  |   ^~~
In file included from /usr/include/vte-2.91/vte/vte.h:35,
 from plugins/ssh/vinagre-ssh-tab.c:24:
/usr/include/vte-2.91/vte/vtedeprecated.h:82:10: note: declared here
   82 | gboolean vte_terminal_spawn_sync(VteTerminal *terminal,
  |  ^~~
plugins/ssh/vinagre-ssh-tab.c: In function ‘vinagre_ssh_tab_class_init’:
plugins/ssh/vinagre-ssh-tab.c:123:3: warning: ‘g_type_class_add_private’ is 
deprecated [-Wdeprecated-declarations]
  123 |   g_type_class_add_private (object_class, sizeof 
(VinagreSshTabPrivate));
  |   ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
  

Bug#978622: marked as done (src:libcrypt-des-ede3-perl: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 00:18:44 +
with message-id 
and subject line Bug#978622: fixed in libcrypt-des-ede3-perl 0.01-2
has caused the Debian Bug report #978622,
regarding src:libcrypt-des-ede3-perl: invalid maintainer address
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.)


-- 
978622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcrypt-des-ede3-perl
Version: 0.0-1
Severity: serious
X-Debbugs-Cc: Holger Levsen , Florian Ragwitz 


The maintainer address is invalid, see below.  There is also a
"Diagnostic-Code: smtp;554 5.4.14 Hop count exceeded - possible mail
loop ATTR34 [DB5EUR01FT005.eop-EUR01.prod.protection.outlook.com]" that
Microsoft's emai^Wtelefax service included out of plain sight.

Ansgar

 Forwarded Message 
Subject: Undeliverable: libcrypt-des-ede3-perl_0.01-1.2_source.changes ACCEPTED 
into unstable
Date: Tue, 29 Dec 2020 00:49:06 +

> Your message to pm.al...@habitat-humanisme.org couldn't be delivered.
> pm.alamy wasn't found at habitat-humanisme.org.
> envelope    Office 365  pm.alamy
> Action Required Recipient
> Unknown To address
> 
> How to Fix It
> The address may be misspelled or may not exist. Try one or more of
> the following:
> 
>   *   Send the message again following these steps: In Outlook, open
> this non-delivery report (NDR) and choose Send Again from the Report
> ribbon. In Outlook on the web, select this NDR, then select the link
> "To send this message again, click here." Then delete and retype the
> entire recipient address. If prompted with an Auto-Complete List
> suggestion don't select it. After typing the complete address, click
> Send.
>   *   Contact the recipient (by phone, for example) to check that the
> address is correct.

Reporting-MTA: dns;DBBP189MB1195.EURP189.PROD.OUTLOOK.COM
Received-From-MTA: dns;EUR01-VE1-obe.outbound.protection.outlook.com
Arrival-Date: Tue, 29 Dec 2020 00:49:03 +

Final-Recipient: rfc822;pm.alamy@habitat-humanisme.org
Action: failed
Status: 5.4.14
Diagnostic-Code: smtp;554 5.4.14 Hop count exceeded - possible mail loop ATTR34 [DB5EUR01FT005.eop-EUR01.prod.protection.outlook.com]
Remote-MTA: dns;DB5EUR01FT005.mail.protection.outlook.com
X-Display-Name: Pierre-Matthieu Alamy


--- End Message ---
--- Begin Message ---
Source: libcrypt-des-ede3-perl
Source-Version: 0.01-2
Done: gregor herrmann 

We believe that the bug you reported is fixed in the latest version of
libcrypt-des-ede3-perl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 978...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libcrypt-des-ede3-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 01 Jan 2021 00:48:04 +0100
Source: libcrypt-des-ede3-perl
Architecture: source
Version: 0.01-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 523380 965631 978622
Changes:
 libcrypt-des-ede3-perl (0.01-2) unstable; urgency=medium
 .
   * Take over for the Debian Perl Group.
 Closes: #978622
   * debian/control: Added: Vcs-Git field (source stanza); Vcs-Browser
 field (source stanza); Homepage field (source stanza). Changed:
 Maintainer set to Debian Perl Group  (was: Pierre-Matthieu Alamy
 ).
   * Remove Pierre-Matthieu and Florian.
 Closes: #523380
   * debian/watch: use metacpan-based URL.
   * Mark package as autopkgtest-able.
   * Declare compliance with Debian Policy 4.5.1.
   * Set Rules-Requires-Root: no.
   * Drop unneeded version constraints from (build) dependencies.
   * Annotate test-only build dependencies with .
   * Switch to source format "3.0 (quilt)".
   * Bump debhelper-compat to 13.
 Closes: #965631
   * debian/watch: use uscan version 4.
   * debian/rules: use dh(1).
   * debian/copyright: use Copyright-Format 1.0.
   * Add /me to Uploaders.
Checksums-Sha1:
 06b1f819184509e33d9d57863d2bb3bb3a147969 2434 libcrypt-des-ede3-perl_0.01-2.dsc
 ecc7a2baf84e98c60398d490df8fedefaa37c142 2212 
libcrypt-

Bug#978325: marked as pending in libgit-repository-perl

[gregor herrmann]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libgit-repository-perl/-/commit/c5e0eca06ca27fdaa547634b1e49f4637e7c1ca6


Add patch to workaround Git v2.30.0's friendly hints

which cause test failures in t/24-errors.t.

Closes: #978325


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978325

Bug#978935: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

[Vincent Lefevre]

On 2020-12-31 20:22:56 +0100, Michael Biebl wrote:
> Am 31.12.20 um 18:37 schrieb Vincent Lefevre:
> > During the upgrade, network-manager disconnected, so that I completely
> > lost the network connection. Fortunately, I was in front of my machine,
> > but this means that a remote upgrade can make the machine unavailable!
> 
> I might be mistaken, but afaics, this has always been the case for WiFi
> connections (as it is not really possible to carry the state across daemon
> reexecs). Are you saying this is not the case?

I've been using NetworkManager only since July on my laptop.
I've checked my logs, and this was the first time I upgraded
NetworkManager over WiFi.

Before using NetworkManager, I've never had such an problem, IIRC.
When my machine was connected via WiFi, I was using wicd. I suppose
that it could handle the reconnection, or this would mean that
I upgraded it only over Ethernet (I don't remember).

The name of the active connection could be stored in a file, so that
a reexec'ed daemon could pick the information. By active connection,
I mean the last connection chosen by the user, under the condition
that the user has not explicitly disconnected.

> Ethernet connections should not be torn down on a daemon stop.
> 
> A remote upgrade over a WiFi connection without a side-band is not something
> I would encourage.

Perhaps, but anyway, this is not nice to disconnect the user (at least
leave the connection disconnected just after the restart) without an
explicit request. This can make some parts of the upgrade process fail
(e.g. how-can-i-help, which is run just after the upgrade and needs a
working connection).

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

Processed: Bug#957912 marked as pending in vinagre

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #957912 [src:vinagre] vinagre: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957912: marked as pending in vinagre

[Andreas Henriksson]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/vinagre/-/commit/62a378f51dc54aa25d8484214bf85e5984b6755a


Add upstream !8 as d/p/gcc-10.patch

Closes: #957912


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957912

Bug#964690: marked as done (signon-plugin-oauth2: FTBFS: oauth1plugin.cpp:147:51: error: ‘void QUrl::addQueryItem(const QString&, const QString&)’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Fri, 01 Jan 2021 00:04:20 +
with message-id 
and subject line Bug#964690: fixed in signon-plugin-oauth2 0.25-1
has caused the Debian Bug report #964690,
regarding signon-plugin-oauth2: FTBFS: oauth1plugin.cpp:147:51: error: ‘void 
QUrl::addQueryItem(const QString&, const QString&)’ is deprecated 
[-Werror=deprecated-declarations]
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.)


-- 
964690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: signon-plugin-oauth2
Version: 0.22-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200709 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> g++ -c -pipe -fno-exceptions -fno-rtti -Werror -g -O2 
> -fdebug-prefix-map=/<>/src=. -fstack-protector-strong -Wformat 
> -Werror=format-security -O2 -Wall -Wextra -D_REENTRANT -fPIC -DSIGNON_TRACE 
> -DQT_CORE_LIB -DQT_NO_DEBUG -DQT_PLUGIN -DQT_XMLPATTERNS_LIB -DQT_NETWORK_LIB 
> -DQT_CORE_LIB -I. -isystem /usr/include/signon-qt5 -isystem 
> /usr/include/signon-qt5/SignOn -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem /usr/include/signon-plugins 
> -isystem /usr/include/signon-plugins/SignOn -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -I. 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o oauth1plugin.o 
> oauth1plugin.cpp
> oauth1plugin.cpp: In member function ‘void 
> OAuth2PluginNS::OAuth1Plugin::sendOAuth1AuthRequest()’:
> oauth1plugin.cpp:147:51: error: ‘void QUrl::addQueryItem(const QString&, 
> const QString&)’ is deprecated [-Werror=deprecated-declarations]
>   147 | url.addQueryItem(OAUTH_TOKEN, d->m_oauth1Token);
>   |   ^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qurl.h:419,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qcborvalue.h:51,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qcborarray.h:43,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:38,
>  from oauth1plugin.h:27,
>  from oauth1plugin.cpp:26:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qurlquery.h:124:13: note: declared 
> here
>   124 | inline void QUrl::addQueryItem(const QString &key, const QString 
> &value)
>   | ^~~~
> oauth1plugin.cpp:150:60: error: ‘void QUrl::addQueryItem(const QString&, 
> const QString&)’ is deprecated [-Werror=deprecated-declarations]
>   150 | url.addQueryItem(SCREEN_NAME, d->m_oauth1ScreenName);
>   |^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qurl.h:419,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qcborvalue.h:51,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qcborarray.h:43,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:38,
>  from oauth1plugin.h:27,
>  from oauth1plugin.cpp:26:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qurlquery.h:124:13: note: declared 
> here
>   124 | inline void QUrl::addQueryItem(const QString &key, const QString 
> &value)
>   | ^~~~
> oauth1plugin.cpp:151:60: error: ‘void QUrl::addQueryItem(const QString&, 
> const QString&)’ is deprecated [-Werror=deprecated-declarations]
>   151 | url.addQueryItem(FORCE_LOGIN, d->m_oauth1ScreenName);
>   |^
> In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qurl.h:419,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qcborvalue.h:51,
>  from 
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qcborarray.h:43,
>  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtCore:38,
>  from oauth1plugin.h:27,
>  from oauth1plugin.cpp:26:
> /usr/include/x86_64-linux-gnu/qt5/QtCore/qurlquery.h:124:13: note: declared 
> here
>   124 | inline void QUrl::addQueryItem(const QString &key, const QString 
> &value)
>   | ^~~~
> oauth1plugin.cpp: In member function ‘QByteArray 
> OAuth2PluginNS::OAuth1Plugin::constructSignatureBaseString(const QString&, 
> const OAuth2PluginNS::OAuth1PluginData&, const QString&, const QString&)’:
> oauth1plugin.cpp:361:69: e

Bug#976477: marked as pending in jruby

[Louis-Philippe Véronneau]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/jruby/-/commit/05d3d3d3525c5f24f03f7bd4cd70e0dbe3006fd8


d/rules: fix where ruby2.7 libs are copied from for the testsuite. (Closes: 
#976477)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976477

Processed: tagging 964690

[Debian Bug Tracking System]

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

> tags 964690 + pending
Bug #964690 [src:signon-plugin-oauth2] signon-plugin-oauth2: FTBFS: 
oauth1plugin.cpp:147:51: error: ‘void QUrl::addQueryItem(const QString&, const 
QString&)’ is deprecated [-Werror=deprecated-declarations]
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#976477 marked as pending in jruby

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976477 [src:jruby] jruby: FTBFS: cp: cannot stat 
'/usr/lib/ruby/vendor_ruby/rake*': No such file or directory
Added tag(s) pending.

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

Bug#967159: marked as done (libaccounts-glib: Unversioned Python removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 21:18:40 +
with message-id 
and subject line Bug#967159: fixed in libaccounts-glib 1.25-1
has caused the Debian Bug report #967159,
regarding libaccounts-glib: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


-- 
967159: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967159
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libaccounts-glib
Version: 1.23-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

We will keep some Python2 package as discussed in
https://lists.debian.org/debian-python/2020/07/msg00039.html
but removing the unversioned python packages python-minimal, python,
python-dev, python-dbg, python-doc.

Your package either build-depends, depends on one of those packages.
Please either convert these packages to Python3, or if that is not
possible, replaces the dependencies on the unversioned Python
packages with one of the python2 dependencies (python2, python2-dev,
python2-dbg, python2-doc).

Please check for dependencies, build dependencies AND autopkg tests.

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: libaccounts-glib
Source-Version: 1.25-1
Done: Pino Toscano 

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated libaccounts-glib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 22:06:04 +0100
Source: libaccounts-glib
Architecture: source
Version: 1.25-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 936841 949177 953769 955848 967159
Changes:
 libaccounts-glib (1.25-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Aurélien COUDERC ]
   * Update debian/watch to match current gitlab.com tags page.
   * New upstream release (1.24). (Closes: #949177, #953769)
   * Adapt build to upstream changes:
 - Upstream build moved from autotools to meson.
 - Drop python2 support. (Closes: #936841, #967159)
 - Install gettext its and loc files.
   * Add Build-Depends-Package to symbols file.
   * Build with hardening=+all build hardening flag.
   * Switch to debhelper-compat build dependency, bump compatibility level to
 12.
   * Move Vcs-* control fields to Salsa.
   * Drop dbgsym migration rule, not needed anymore after 2 stable releases.
 .
   [ Pino Toscano ]
   * New upstream release.
   * Update the build dependencies according to the upstream build system:
 - bump meson to 0.48.0
 - bump libglib2.0-dev to 2.26
 - explicitly add valac, already used
 - replace python-gi-dev with python3-gi
 - drop intltool, and libtool, no more needed
   * Add the configuration for the CI on salsa.
   * Update install files.
   * Update symbols file.
   * Drop debian/not-installed, referring to non-existing files.
   * Drop debian/gbp.conf, as the packaging repository does not use
 git-buildpackage.
   * Add Rules-Requires-Root: no.
   * Bump Standards-Version to 4.5.1, no changes required.
   * Bump the debhelper compatibility to 13:
 - switch the debhelper-compat build dependency to 13
   * Use secure copyright file specification URI.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Drop the unused 'testsuite' autopkgtest.
   * Update lintian overrides.
   * Small updates to copyright.
   * Improve the references to the Glib types in the API documentation:
 - add libglib2.0-doc as Build-Depends-Indep
 - recommend libgl

Bug#949177: marked as done (libaccounts-glib: FTBFS: -Werror + -Wdeprecated-declarations)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 21:18:40 +
with message-id 
and subject line Bug#949177: fixed in libaccounts-glib 1.25-1
has caused the Debian Bug report #949177,
regarding libaccounts-glib: FTBFS: -Werror + -Wdeprecated-declarations
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.)


-- 
949177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949177
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libaccounts-glib
Version: 1.23-1
Severity: serious
Tags: ftbfs

Dear maintainer,

your package failed to rebuild in a standard sid/amd64 chroot.
Attached is the full build log, hopefully relevant excerpt follows:


libtool: compile:  gcc -DHAVE_CONFIG_H -I.. -I.. -I. 
-DG_LOG_DOMAIN=\"accounts-glib\" -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gio-unix-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/libxml2 -Wall -Werror -Wno-error=deprecated-declarations -g -O2 
-fdebug-prefix-map=/build/libaccounts-glib-1.23=. -fstack-protector-strong 
-Wformat -Werror=format-security -DDISABLE_WAL -c ag-account.c  -fPIC -DPIC -o 
.libs/libaccounts_glib_la-ag-account.o
ag-account.c: In function 'ag_account_init':
ag-account.c:827:13: error: G_ADD_PRIVATE [-Werror]
  827 |  AgAccountPrivate);
  | ^
ag-account.c: In function 'ag_account_class_init':
ag-account.c:1021:5: warning: 'g_type_class_add_private' is deprecated 
[-Wdeprecated-declarations]
 1021 | g_type_class_add_private (object_class, sizeof (AgAccountPrivate));
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from ag-manager.h:31,
 from ag-account.c:103:
/usr/include/glib-2.0/gobject/gtype.h:1308:10: note: declared here
 1308 | void g_type_class_add_private   (gpointer
g_class,
  |  ^~~~
cc1: all warnings being treated as errors
make[4]: *** [Makefile:671: libaccounts_glib_la-ag-account.lo] Error 1
make[4]: Leaving directory '/build/libaccounts-glib-1.23/libaccounts-glib'
make[3]: *** [Makefile:546: all] Error 2
make[3]: Leaving directory '/build/libaccounts-glib-1.23/libaccounts-glib'
make[2]: *** [Makefile:557: all-recursive] Error 1
make[2]: Leaving directory '/build/libaccounts-glib-1.23'
make[1]: *** [Makefile:444: all] Error 2
make[1]: Leaving directory '/build/libaccounts-glib-1.23'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:39: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
I: Using pkgname logfile
I: Current time: Fri Jan 17 19:16:03 UTC 2020
I: pbuilder-time-stamp: 1579288563
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [pkgs/libaccounts-glib_1.23-1.dsc]
I: copying [pkgs/libaccounts-glib_1.23.orig.tar.xz]
I: copying [pkgs/libaccounts-glib_1.23-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/home/mattia/.gnupg/trustedkeys.kbx': General error
gpgv: Signature made Wed Jul 12 18:01:17 2017 UTC
gpgv:using RSA key F8921D3A7404C86E11352215C7197699B29B232A
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on 
./libaccounts-glib_1.23-1.dsc
dpkg-source: info: extracting libaccounts-glib in libaccounts-glib-1.23
dpkg-source: info: unpacking libaccounts-glib_1.23.orig.tar.xz
dpkg-source: info: unpacking libaccounts-glib_1.23-1.debian.tar.xz
I: using fakeroot in build.
I: Installing the build-deps
I: -> Attempting to satisfy build-dependencies
Note, using file '/build/libaccounts-glib_1.23-1.dsc' to get the build 
dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev bsdmainutils ca-certificates check
  dbus debhelper d

Bug#978616: marked as done (mediastreamer2: doesn't build correct libraries with cmake?)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 21:05:03 +
with message-id 
and subject line Bug#978616: fixed in mediastreamer2 1:4.4.21-3
has caused the Debian Bug report #978616,
regarding mediastreamer2: doesn't build correct libraries with cmake?
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.)


-- 
978616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mediastreamer2
Version: 1:4.4.21-2
Severity: serious

Hello, looks like with autotools, the library provides libmediastreamer_base 
and libmediastreamer_voip,
while with cmake it doesn't.

the pkgconfig file is obviously wrong, but I don't know which solution you 
prefer (and if you are aware of this issue).

I propose two solutions:
1) implement the library split in cmake, and upstream it (this might be the 
preferred and easier solution to this issue)
2) patch pkgconfig file and cmake helpers to provide only one library to link.

if we choose 1, we should probably also change the ABI, so call it 
libmediastreamer11a or similar, to trigger a rebuild of reverse dependencies.

If you agree with 1) I can try to provide a patch as soon as possible.

thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: mediastreamer2
Source-Version: 1:4.4.21-3
Done: Bernhard Schmidt 

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated mediastreamer2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 18:22:27 +0100
Source: mediastreamer2
Architecture: source
Version: 1:4.4.21-3
Distribution: unstable
Urgency: medium
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Closes: 978616
Changes:
 mediastreamer2 (1:4.4.21-3) unstable; urgency=medium
 .
   * Amend pkgconfig patch with patching the resulting .pc file.
 Thanks again to Gianfranco Costamagna (Closes: #978616)
Checksums-Sha1:
 cacb61bc90c31d0b8eed3bc7be61379ffc5f280b 2927 mediastreamer2_4.4.21-3.dsc
 918016f347edf57f9c3e2317a90a553ab894824a 6408 
mediastreamer2_4.4.21-3.debian.tar.xz
 02ce9753a73964e6086dd09e801587a7db238413 15863 
mediastreamer2_4.4.21-3_amd64.buildinfo
Checksums-Sha256:
 67c2edfbfdedf3601e618394c3d030664daf86203e53ad803ec82c3770004f30 2927 
mediastreamer2_4.4.21-3.dsc
 a47820d4268f8caf538d42edbb200ef17878fc21685348dbf3eee4c385109f14 6408 
mediastreamer2_4.4.21-3.debian.tar.xz
 bd47117910439543573107acdd96ffba42bf16b347147487a3392715696d7944 15863 
mediastreamer2_4.4.21-3_amd64.buildinfo
Files:
 7ebaa2aef13a576576c1cf0f7c66b453 2927 libs optional mediastreamer2_4.4.21-3.dsc
 be41208a79eb547ab42f49dd725362c0 6408 libs optional 
mediastreamer2_4.4.21-3.debian.tar.xz
 80da38a1feb8d4eed33d9ec630ca7c6a 15863 libs optional 
mediastreamer2_4.4.21-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAl/uN2cRHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJPCtg//cLhvWMEuzQOT1j262EO/iYJpx15ouRPl
Za22nAM1eRQBkmxYccFS5P5dMr3MRnPgdaPHxfMzn1QmmWkOR+WhqR/lIQN7VBZ3
k40qX0rvD8E08hNsMJQCG7T4aA86CTae50wMc9AW/pTQGVmRMlgeYf7AeDtOYDop
h/PKUEoi00noagM5NkSuqUpT0GQeIBYQ5XhYH1hgj+PZdKXP6bZsUPDlCFuQmwZL
u8IgLKLs78COwNr3GLm0lbcPi38vqJLnui5YywjYa7AUGOR9UMAWL3dkN7ZX/Jn9
jHt/h8z8onIJpRRAFi+4jd5jKex/f4ri9TAl5j7+s6G4FHXNNNYBUww9Et7hpM41
YbQzRSAJ8F7TUyvW21cLfobufAJbqi4ITg2FMeA0IBToA6JOhtHVc4VnXZWcow6r
N+5pD0GCNHboiezgeF9EjW75NZmt1hDKdkYF4G4Rk3CHQYVU4veJB+sckSFCvgAU
Nrtn59cmTJadVZsju0JPzjTq2RWQK04QqSubgsEsc4Gvzxyy5GUGW4dXvuoBBbqX
VIRL3GAYj50y1LWQ9/SlSh+ZlLWehQTsc/gs2a4rmhzueAXxT0HZxaYDoMIz7fQS
QxdDq7nXdLpLjEsf9deFS5579hvI1cBkTG0oLXn5jfS1qrxVdRIM6tmN94eWvtm8
+/4jHojfUBk=
=mCPJ
-END PGP SIGNATURE End Message ---

Bug#978357: marked as done (gnome-todo: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc --l

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 21:03:27 +
with message-id 
and subject line Bug#978357: fixed in gnome-todo 3.28.1-6
has caused the Debian Bug report #978357,
regarding gnome-todo: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu 
&& LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload --buildtype=plain 
--prefix=/usr --sysconfdir=/etc --localstatedir=/var 
--libdir=lib/x86_64-linux-gnu returned exit code 1
to be marked as done.

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

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


-- 
978357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-todo
Version: 3.28.1-5
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build  --with gnome
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.56.0
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: gnome-todo
> Project version: 3.28.1
> Using 'CFLAGS' from environment with value: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 
> -Wl,-z,defs -Wl,--as-needed'
> Using 'CPPFLAGS' from environment with value: '-Wdate-time 
> -D_FORTIFY_SOURCE=2'
> C compiler for the host machine: cc (gcc 10.2.1 "cc (Debian 10.2.1-3) 10.2.1 
> 20201224")
> C linker for the host machine: cc ld.bfd 2.35.1
> Using 'CFLAGS' from environment with value: '-g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security'
> Using 'LDFLAGS' from environment with value: '-Wl,-z,relro -Wl,-z,now -Wl,-O1 
> -Wl,-z,defs -Wl,--as-needed'
> Using 'CPPFLAGS' from environment with value: '-Wdate-time 
> -D_FORTIFY_SOURCE=2'
> Host machine cpu family: x86_64
> Host machine cpu: x86_64
> Has header "dlfcn.h" : YES 
> Has header "inttypes.h" : YES 
> Has header "locale.h" : YES 
> Has header "memory.h" : YES 
> Has header "stdint.h" : YES 
> Has header "stdlib.h" : YES 
> Has header "strings.h" : YES 
> Has header "string.h" : YES 
> Has header "sys/stat.h" : YES 
> Has header "sys/types.h" : YES 
> Has header "unistd.h" : YES 
> Checking for function "dcgettext" : YES 
> Checking for function "gettext" : YES 
> Checking for function "iconv" : YES 
> Found pkg-config: /usr/bin/pkg-config (0.29.2)
> Run-time dependency glib-2.0 found: YES 2.66.4
> Run-time dependency gtk+-3.0 found: YES 3.24.24
> Run-time dependency gio-2.0 found: YES 2.66.4
> Run-time dependency gmodule-export-2.0 found: YES 2.66.4
> Run-time dependency goa-1.0 found: YES 3.38.0
> Run-time dependency libpeas-1.0 found: YES 1.28.0
> Library m found: YES
> Configuring config.h using configuration
> Run-time dependency libecal-2.0 found: YES 3.38.2
> Run-time dependency libedataserver-1.2 found: YES 3.38.2
> Run-time dependency libedataserverui-1.2 found: YES 3.38.2
> Run-time dependency libical found: YES 3.0.8
> Configuring eds.plugin using configuration
> Configuring background.plugin using configuration
> Configuring dark-theme.plugin using configuration
> Configuring scheduled-panel.plugin using configuration
> WARNING: Project targeting '>= 0.41.0' but tried to use feature introduced in 
> '0.50.0': install arg in configure_file.
> Configuring score.plugin using configuration
> Configuring today-panel.plugin using configuration
> Configuring unscheduled-panel.plugin using configuration
> Configuring todo-txt.plugin using configuration
> Did not find CMake 'cmake'
> Found CMake: NO
> Run-time dependency rest-0.7 found: NO (tried pkgconfig)
> 
> ../plugins/todoist/meson.build:11:0: ERROR: Dependency "rest-0.7" not found, 
> tried pkgconfig
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2020-12-26T18:39:21.241695
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.56.0
> Sou

Bug#978357: marked as pending in gnome-todo

[Andreas Henriksson]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gnome-todo/-/commit/e56c1f7ad205341e8b6f23dbe80640bf667f6716


Explicitly build-dep on librest-dev

rest-0.7 is referenced in meson.build but apparently
was not mentioned in build-dependencies as it should
(but probably worked before because some other build-dep
would pull it in, and now stopped doing so).
Since we directly reference it we should have a direct
build-depedency as well

Closes: #978357


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978357

Processed: Bug#978357 marked as pending in gnome-todo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978357 [src:gnome-todo] gnome-todo: FTBFS: dh_auto_configure: error: cd 
obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. --wrap-mode=nodownload 
--buildtype=plain --prefix=/usr --sysconfdir=/etc --localstatedir=/var 
--libdir=lib/x86_64-linux-gnu returned exit code 1
Added tag(s) pending.

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

Processed: tagging 936841, tagging 949177, tagging 953769, tagging 967159

[Debian Bug Tracking System]

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

> tags 936841 + pending
Bug #936841 [src:libaccounts-glib] libaccounts-glib: Python2 removal in 
sid/bullseye
Added tag(s) pending.
> tags 949177 + pending
Bug #949177 [src:libaccounts-glib] libaccounts-glib: FTBFS: -Werror + 
-Wdeprecated-declarations
Added tag(s) pending.
> tags 953769 + pending
Bug #953769 [libaccounts-glib] libaccounts-glib: New version 1.24 available
Added tag(s) pending.
> tags 967159 + pending
Bug #967159 [src:libaccounts-glib] libaccounts-glib: Unversioned Python removal 
in sid/bullseye
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#978356: marked as done (libcxx-serial: FTBFS: dh_missing: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 20:34:01 +
with message-id 
and subject line Bug#977844: fixed in libcxx-serial 1.2.1-4.1
has caused the Debian Bug report #977844,
regarding libcxx-serial: FTBFS: dh_missing: error: missing files, aborting
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.)


-- 
977844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcxx-serial
Version: 1.2.1-4
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_missing --fail-missing
> dh_missing: warning: usr/share/pkgconfig/cxx-serial.pc exists in debian/tmp 
> but is not installed to anywhere (related file: 
> "debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/cxx-serial.pc")
> dh_missing: error: missing files, aborting
> 
>   While detecting missing files, dh_missing noted some files with a 
> similar name to those
>   that were missing.  This error /might/ be resolved by replacing 
> references to the
>   missing files with the similarly named ones that dh_missing found - 
> assuming the content
>   is identical.
> 
>   As an example, you might want to replace:
>* debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/cxx-serial.pc
>   with:
>* usr/share/pkgconfig/cxx-serial.pc
>   in a file in debian/ or as argument to one of the dh_* tools called 
> from debian/rules.
>   (Note it is possible the paths are not used verbatim but instead 
> directories 
>   containing or globs matching them are used instead)
> 
>   Alternatively, add the missing file to debian/not-installed if it 
> cannot and should not
>   be used.
> 
>   The following debhelper tools have reported what they installed (with 
> files per package)
>* dh_install: libcxx-serial-dev (4), libcxx-serial1 (2)
>* dh_installdocs: libcxx-serial-dev (3), libcxx-serial1 (0)
>   If the missing files are installed by another tool, please file a bug 
> against it.
>   When filing the report, if the tool is not part of debhelper itself, 
> please reference the
>   "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
> for debhelper (10.6.3+).
> (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
>   Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
> when only a subset is built
>   If the omission is intentional or no other helper can take care of this 
> consider adding the
>   paths to debian/not-installed.
> make[1]: *** [debian/rules:21: override_dh_missing] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/libcxx-serial_1.2.1-4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libcxx-serial
Source-Version: 1.2.1-4.1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated libcxx-serial 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Dec 2020 20:38:16 +0100
Source: libcxx-serial
Architecture: source
Version: 1.2.1-4.1
Distribution: unstabl

Bug#977844: marked as done (src:libcxx-serial: libcxx-serial FTBFS with new catkin (patch attached))

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 20:34:01 +
with message-id 
and subject line Bug#977844: fixed in libcxx-serial 1.2.1-4.1
has caused the Debian Bug report #977844,
regarding src:libcxx-serial: libcxx-serial FTBFS with new catkin (patch 
attached)
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.)


-- 
977844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libcxx-serial
Version: 1.2.1-4
Severity: normal
Tags: ftbfs

Hi,

I've changed catkin to install pkg-config files to /usr/share and made
them arch independent. I've attached a patch for libcxx-serial to adopt
to those changes.

I will upload a package with the attached patch to DELAYED/10. Please
tell me if I should cancel it.

Cheers Jochen


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

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index 0d58d86..6abf8d6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libcxx-serial (1.2.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Adopt to catkin installing pkgconfig to share
+
+ -- Jochen Sprickerhof   Mon, 21 Dec 2020 20:38:16 +0100
+
 libcxx-serial (1.2.1-4) unstable; urgency=medium
 
   * Add missing build-deps libgmock-dev and pkg-config. Closes: #973112
diff --git a/debian/libcxx-serial-dev.install b/debian/libcxx-serial-dev.install
index a1fc515..72c088b 100644
--- a/debian/libcxx-serial-dev.install
+++ b/debian/libcxx-serial-dev.install
@@ -1,4 +1,3 @@
 usr/include/*
 usr/lib/*/lib*.so
-usr/lib/*/pkgconfig/*
-usr/share/cxx-serial
+usr/share
diff --git a/debian/rules b/debian/rules
index 00ebf56..87b46bd 100755
--- a/debian/rules
+++ b/debian/rules
@@ -8,7 +8,6 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
 override_dh_auto_configure:
dh_auto_configure -- \
-   -DPKGCONFIGDIR=/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig \
-DCMAKE_VERBOSE_MAKEFILE=ON
 
 override_dh_auto_test:
--- End Message ---
--- Begin Message ---
Source: libcxx-serial
Source-Version: 1.2.1-4.1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated libcxx-serial 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Dec 2020 20:38:16 +0100
Source: libcxx-serial
Architecture: source
Version: 1.2.1-4.1
Distribution: unstable
Urgency: medium
Maintainer: Alec Leamas 
Changed-By: Jochen Sprickerhof 
Closes: 977844
Changes:
 libcxx-serial (1.2.1-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adopt to catkin installing pkgconfig to share (Closes: #977844)
Checksums-Sha1:
 6bf857d5a31c70150952b1eec9ef92a356266bfb 2030 libcxx-serial_1.2.1-4.1.dsc
 3085fc21cb423937b25b5a6a7a15faa5aec7ea90 8464 
libcxx-serial_1.2.1-4.1.debian.tar.xz
 497677635448a459fd1d653d9aa5b0f6af3d041a 8031 
libcxx-serial_1.2.1-4.1_source.buildinfo
Checksums-Sha256:
 e2c7af050b01f0fb746981f6ffe22dd5cb7b6c97a6257543b18a66f9bc5ee90e 2030 
libcxx-serial_1.2.1-4.1.dsc
 9766989bb7c5ec232e45926cf6fc4db819b89e4b0fc7250e44a0ad450707d286 8464 
libcxx-serial_1.2.1-4.1.debian.tar.xz
 02f9328116f13e67ed0501aceaa2f42a2e52f3eb5ef5ccf9a30cfb22bfc63fee 8031 
libcxx-serial_1.2.1-4.1_source.buildinfo
Files:
 a9b5ae059144df31e81e2341e14d0ce2 2030 libs optional libcxx-serial_1.2.1-4.1.dsc
 495a9064ae3124353ea2ee188d611e00 8464 libs optional 
libcxx-serial_1.2.1-4.1.debian.tar.xz
 877549cf4fa9c7e957790019be350c55 8031 libs optional 
libcxx-serial_1.2.1-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl/g/g8UHGpzcHJpY2tl
QGRlYmlhbi5v

Bug#976546: marked as done (libmiglayout-java: FTBFS on arm64,ppc64el (arch:all-only src pkg): [ERROR] /<>/swt/src/main/java/net/miginfocom/swt/MigLayout.java:[527,33] cannot find symbol)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 19:48:55 +
with message-id 
and subject line Bug#976546: fixed in libmiglayout-java 5.1-3
has caused the Debian Bug report #976546,
regarding libmiglayout-java: FTBFS on arm64,ppc64el (arch:all-only src pkg): 
[ERROR] 
/<>/swt/src/main/java/net/miginfocom/swt/MigLayout.java:[527,33] 
cannot find symbol
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.)


-- 
976546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmiglayout-java
Version: 5.1-2
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibmiglayout-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by 
> com.google.inject.internal.cglib.core.$ReflectUtils$1 
> (file:/usr/share/maven/lib/guice.jar) to method 
> java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
> WARNING: Please consider reporting this to the maintainers of 
> com.google.inject.internal.cglib.core.$ReflectUtils$1
> WARNING: Use --illegal-access=warn to enable warnings of further illegal 
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> [INFO] Scanning for projects...
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] MiGLayout  
> [pom]
> [INFO] MiGLayout Core 
> [jar]
> [INFO] MiGLayout Swing
> [jar]
> [INFO] MiGLayout SWT  
> [jar]
> [INFO] MiGLayout JavaFX   
> [jar]
> [INFO] MiGLayout IDEUtil  
> [jar]
> [INFO] 
> [INFO] ---< com.miglayout:miglayout-parent 
> >---
> [INFO] Building MiGLayout 5.1-SNAPSHOT
> [1/6]
> [INFO] [ pom 
> ]-
> [INFO] 
> [INFO] --- maven-bundle-plugin:3.5.1:manifest (bundle-manifest) @ 
> miglayout-parent ---
> [WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle]
> [INFO] 
> [INFO] < com.miglayout:miglayout-core 
> >
> [INFO] Building MiGLayout Core 5.1-SNAPSHOT   
> [2/6]
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ 
> miglayout-core ---
> [WARNING] Using platform encoding (UTF-8 actually) to copy filtered 
> resources, i.e. build is platform dependent!
> [INFO] skip non existing resourceDirectory 
> /<>/core/src/main/resources
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ 
> miglayout-core ---
> [INFO] Changes detected - recompiling the module!
> [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. 
> build is platform dependent!
> [INFO] Compiling 18 source files to /<>/core/target/classes
> [INFO] /<>/core/src/main/java/net/miginfocom/layout/CC.java: 
> Some input files use or override a deprecated API.
> [INFO] /<>/core/src/main/java/net/miginfocom/layout/CC.java: 
> Recompile with -Xlint:deprecation for details.
> [INFO] 
> /<>/core/src/main/java/net/mi

Processed: Re: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #978935 [network-manager] network-manager: disconnect on upgrade
Added tag(s) moreinfo.

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

Bug#978935: [Pkg-utopia-maintainers] Bug#978935: network-manager: disconnect on upgrade

[Michael Biebl]

Control: tags -1 + moreinfo

Am 31.12.20 um 18:37 schrieb Vincent Lefevre:

Package: network-manager
Version: 1.28.0-1+b1
Severity: serious

During the upgrade, network-manager disconnected, so that I completely
lost the network connection. Fortunately, I was in front of my machine,
but this means that a remote upgrade can make the machine unavailable!


I might be mistaken, but afaics, this has always been the case for WiFi 
connections (as it is not really possible to carry the state across 
daemon reexecs). Are you saying this is not the case?

Ethernet connections should not be torn down on a daemon stop.

A remote upgrade over a WiFi connection without a side-band is not 
something I would encourage.


Michael



OpenPGP_signature
Description: OpenPGP digital signature

Bug#978939: zeekctl: missing Breaks+Replaces: broctl (<< 2)

[Andreas Beckmann]

Package: zeekctl
Version: 2.2.0+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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 .../zeekctl_2.2.0+ds1-1_all.deb ...
  Unpacking zeekctl (2.2.0+ds1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/zeekctl_2.2.0+ds1-1_all.deb (--unpack):
   trying to overwrite '/usr/bin/broctl', which is also in package broctl 1.4-1
  Errors were encountered while processing:
   /var/cache/apt/archives/zeekctl_2.2.0+ds1-1_all.deb


cheers,

Andreas


broctl=1.4-1_zeekctl=2.2.0+ds1-1.log.gz
Description: application/gzip

Processed: bug 978936 is forwarded to https://github.com/darktable-org/darktable/issues/7583

[Debian Bug Tracking System]

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

> forwarded 978936 https://github.com/darktable-org/darktable/issues/7583
Bug #978936 [darktable] darktable: FTBFS on arm64
Set Bug forwarded-to-address to 
'https://github.com/darktable-org/darktable/issues/7583'.
> thanks
Stopping processing here.

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

Bug#978936: darktable: FTBFS on arm64

[David Bremner]

Package: darktable
Version: 3.4.0-1
Severity: serious
Tags: upstream
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: -1 forwarded https://github.com/darktable-org/darktable/issues/7583

The new release requires xmmintrin.h in several places, and that
include file is only present (in Debian) on amd64.


https://buildd.debian.org/status/fetch.php?pkg=darktable&arch=arm64&ver=3.4.0-1&stamp=1608929069&raw=0


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

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

Versions of packages darktable depends on:
ii  libc62.31-6
ii  libcairo21.16.0-4
ii  libcolord-gtk1   0.1.26-2
ii  libcolord2   1.4.4-2
ii  libcups2 2.3.3op1-3
ii  libcurl3-gnutls  7.72.0-1
ii  libexiv2-27  0.27.3-3
ii  libgcc-s110.2.1-3
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.4-1
ii  libgomp1 10.2.1-3
ii  libgphoto2-6 2.5.26-2
ii  libgphoto2-port122.5.26-2
ii  libgraphicsmagick-q16-3  1.4+really1.3.36-1
ii  libgtk-3-0   3.24.24-1
ii  libilmbase25 2.5.3-2
ii  libjpeg62-turbo  1:2.0.5-1.1
ii  libjson-glib-1.0-0   1.6.0-2
ii  liblcms2-2   2.9-4+b1
ii  liblensfun1  0.3.2-5
ii  liblua5.3-0  5.3.3-1.1+b1
ii  libopenexr25 2.5.3-2
ii  libopenjp2-7 2.3.1-1
ii  libosmgpsmap-1.0-1   1.1.0-7
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  libpng16-16  1.6.37-3
ii  libpugixml1v51.11.4-1
ii  librsvg2-2   2.50.2+dfsg-1
ii  libsecret-1-00.20.4-1
ii  libsoup2.4-1 2.72.0-2
ii  libsqlite3-0 3.34.0-1
ii  libstdc++6   10.2.1-3
ii  libtiff5 4.2.0-1
ii  libwebp6 0.6.1-2+b1
ii  libx11-6 2:1.6.12-1
ii  libxml2  2.9.10+dfsg-6.3+b1
ii  libxrandr2   2:1.5.1-1
ii  zlib1g   1:1.2.11.dfsg-2

darktable recommends no packages.

darktable suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl/uD6kACgkQA0U5G1Wq
FSFD8A/+KlBt0LMrGwiDWI/p56Gcdg5EMMbPMG7G7E1LJBBMSyQ5EhEUjo+TQRhR
HRBzfEKPgkYJu+93XvDRVeITJtq9xIL1KTISWgcQRTIC71SDDHGtG7nvJTLVK/fD
7+PnVI3hTPoyNmg2WAK8PtX/TbsOcGNIsx3h173/vonGpL7PUMkhJOWNhH4u/OB8
R7NgusGmji5ylnaPFVNYHII0Ig4r2pBQa7crNiBbCCS7gLMV/BZbp+zbcsnFyLsR
Iynu2+I0S0lCHIEbMblwwz68eHoC0cwaJQ6ypcansMT/4v8pYWnByc9U9qZfc8yf
g4ZhQKBxofq3GRFY/k+CguIDXub1jBP23WWM7lWZgRL/l0BYQDybPvJ7kqCevDM3
xdJNA2/XZA7M6e0VlNR7V4wuuSaThhUusqE+FZebS2yfCfV2n4QdW74vBDV+E7dP
DqexnuS5Xig0lC/PZ5Eg49ZN4k65Qpf945UMjbHzSKNa45m4+wJLigxdvdMXBN0H
E0cdYwGecL0WAlzZNUtfLLEYG0zyZxijrWHV3DjysDf3AnxWcuS+3fFoy/aR/oNw
niQFX+M21HLUaqpJBTBs3xCZWMvmMK6vbETuWqEzSR18HDKIXnuTCkpNsZ23BnQ7
5OrPfb2eZZUWkfg9fhFS6lgv6Ysk/Liv7FJ9YVrR4V7XKx7m6Ow=
=HiaZ
-END PGP SIGNATURE-

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Daniele Tricoli]

Hello Sebastiaan,

On Thu, Dec 31, 2020 at 04:28:40PM +0100, Sebastiaan Couwenberg wrote:
> Thanks for quickly acting on this, but the problem is not limited to
> python3-requests. Several other reverse dependencies need to be updated
> for the new chardet as well. The autopkgtest failures include some of them:
> 
>  https://qa.debian.org/excuses.php?package=chardet

Oh, sorry my fault, I confused this bug for one of the bugs opened for requests.
Sorry for the noise and thanks for reopening!

Cheers and happy new year!

-- 
  Daniele Tricoli 'eriol'
  https://mornie.org


signature.asc
Description: PGP signature

Processed: [bts-link] source package src:apertium-br-fr

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:apertium-br-fr
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #978359 (http://bugs.debian.org/978359)
> # Bug title: apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on 
> the right beginning with whitespace)
> #  * https://github.com/apertium/apertium-br-fr/issues/4
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 978359 + fixed-upstream
Bug #978359 [src:apertium-br-fr] apertium-br-fr: FTBFS: Error: Invalid 
dictionary (hint: entry on the right beginning with whitespace)
Added tag(s) fixed-upstream.
> usertags 978359 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:pylint

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:pylint
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #973168 (http://bugs.debian.org/973168)
> # Bug title: pylint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
> -i python{version} -p "3.9 3.8" returned exit code 13
> #  * https://github.com/PyCQA/pylint/issues/3895
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 973168 + fixed-upstream
Bug #973168 [src:pylint] pylint: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
Added tag(s) fixed-upstream.
> usertags 973168 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 973168 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:apertium-eo-ca

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:apertium-eo-ca
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #978369 (http://bugs.debian.org/978369)
> # Bug title: apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on 
> the right beginning with whitespace)
> #  * https://github.com/apertium/apertium-eo-ca/issues/2
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 978369 + fixed-upstream
Bug #978369 [src:apertium-eo-ca] apertium-eo-ca: FTBFS: Error: Invalid 
dictionary (hint: entry on the right beginning with whitespace)
Added tag(s) fixed-upstream.
> usertags 978369 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#978749: marked as done (bound on python3-chardet < 3.1.0 prevents install & build)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 17:35:50 +
with message-id 
and subject line Bug#978749: fixed in requests 2.25.1+dfsg-2
has caused the Debian Bug report #978749,
regarding bound on python3-chardet < 3.1.0 prevents install & build
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.)


-- 
978749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.9.0
Severity: normal
X-Debbugs-Cc: pitsior...@gmail.com

As said in the title, today's upgrade of python3-chardet to 4.0.0 (in unstable)
wants to remove reportbug

The following packages were automatically installed and are no longer required:
  python-apt-common python3-apt python3-certifi python3-chardet python3-debian
  python3-debianbts python3-httplib2 python3-idna python3-pycurl
  python3-pysimplesoap python3-urllib3
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  python3-reportbug python3-requests reportbug
The following packages will be upgraded:
  python3-chardet
1 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
Need to get 0 B/99.0 kB of archives.
After this operation, 218 kB disk space will be freed.
Do you want to continue? [Y/n] n

Python3-chardet is a dependency of python3-requests, which in turn is a
dependency of python3-reportbug. It is that simple.

Thank you in advance and happy new year :)



-- Package-specific info:
** Environment settings:
INTERFACE="gtk"

** /home/jim/.reportbugrc:
reportbug_version "7.8.0"
mode standard
ui gtk
realname "jim_p"
email "pitsior...@gmail.com"
no-cc
list-cc-me
smtphost reportbug.debian.org

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

Kernel: Linux 5.9.0-5-amd64 (SMP w/2 CPU threads)
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 not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages reportbug depends on:
ii  apt2.1.12+deb11u1
ii  python33.9.0-4
ii  python3-reportbug  7.9.0
ii  sensible-utils 0.0.12+nmu1

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail
pn  debconf-utils 
pn  debsums   
pn  dlocate   
pn  emacs-bin-common  
ii  file  1:5.39-3
ii  gnupg 2.2.20-1
pn  python3-urwid 
pn  reportbug-gtk 
ii  ssmtp [mail-transport-agent]  2.64-9
ii  xdg-utils 1.1.3-2

Versions of packages python3-reportbug depends on:
ii  apt2.1.12+deb11u1
ii  file   1:5.39-3
ii  python33.9.0-4
ii  python3-apt2.1.7
ii  python3-debian 0.1.39
ii  python3-debianbts  3.1.0
ii  python3-requests   2.24.0+dfsg-1
ii  sensible-utils 0.0.12+nmu1

python3-reportbug suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: requests
Source-Version: 2.25.1+dfsg-2
Done: Daniele Tricoli 

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

Debian distribution maintenance software
pp.
Daniele Tricoli  (supplier of updated requests package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 17:55:39 +0100
Source: requests
Architecture: source
Version: 2.25.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Daniele Tricoli 
Closes: 978749
Changes:
 requests (2.25.1+dfsg-2) unstable; urgency=medium
 .
   * debian/control
 - Drop upper bound version for chardet and urllib3. Thanks to sramacher
   and myon for the suggestions. (Closes: #978749)
Checksums-Sha1:
 05963e0ba2c9cf654760707b221bb1d9abc7cf3a 2256 requests_2.25.1+dfsg-2.dsc
 265c7ec8

Bug#978935: network-manager: disconnect on upgrade

[Vincent Lefevre]

Package: network-manager
Version: 1.28.0-1+b1
Severity: serious

During the upgrade, network-manager disconnected, so that I completely
lost the network connection. Fortunately, I was in front of my machine,
but this means that a remote upgrade can make the machine unavailable!

In the journalctl output:

[...]
Dec 31 18:23:56 zira systemd[1]: Reloading.
Dec 31 18:23:56 zira systemd-fstab-generator[201684]: Swap unit generation 
disabled on kernel command line, ignoring fstab swap entry for 
/dev/mapper/zira--vg-swap_1.
Dec 31 18:23:56 zira systemd-fstab-generator[201684]: Failed to create unit 
file /run/systemd/generator/media-mem.mount, as it already exists. Duplicate 
entry in /etc/fstab?
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/dictd' lacks a native systemd unit file. Automatically generating 
a unit file for compatibility. Please update package to include a native 
systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/gpm' lacks a native systemd unit file. Automatically generating a 
unit file for compatibility. Please update package to include a native systemd 
unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/netplug' lacks a native systemd unit file. Automatically 
generating a unit file for compatibility. Please update package to include a 
native systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/mcelog' lacks a native systemd unit file. Automatically generating 
a unit file for compatibility. Please update package to include a native 
systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/shellinabox' lacks a native systemd unit file. Automatically 
generating a unit file for compatibility. Please update package to include a 
native systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/monit' lacks a native systemd unit file. Automatically generating 
a unit file for compatibility. Please update package to include a native 
systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/loadcpufreq' lacks a native systemd unit file. Automatically 
generating a unit file for compatibility. Please update package to include a 
native systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201693]: SysV service 
'/etc/init.d/cpufrequtils' lacks a native systemd unit file. Automatically 
generating a unit file for compatibility. Please update package to include a 
native systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd[201676]: 
/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 
1.
Dec 31 18:23:56 zira systemd[1]: /lib/systemd/system/smartmontools.service:10: 
Standard output type syslog is obsolete, automatically updating to journal. 
Please update your unit file, and consider removing the setting altogether.
Dec 31 18:23:56 zira systemd[1]: Reloading.
Dec 31 18:23:56 zira systemd-fstab-generator[201707]: Swap unit generation 
disabled on kernel command line, ignoring fstab swap entry for 
/dev/mapper/zira--vg-swap_1.
Dec 31 18:23:56 zira systemd-fstab-generator[201707]: Failed to create unit 
file /run/systemd/generator/media-mem.mount, as it already exists. Duplicate 
entry in /etc/fstab?
Dec 31 18:23:56 zira systemd-sysv-generator[201716]: SysV service 
'/etc/init.d/dictd' lacks a native systemd unit file. Automatically generating 
a unit file for compatibility. Please update package to include a native 
systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201716]: SysV service 
'/etc/init.d/gpm' lacks a native systemd unit file. Automatically generating a 
unit file for compatibility. Please update package to include a native systemd 
unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201716]: SysV service 
'/etc/init.d/netplug' lacks a native systemd unit file. Automatically 
generating a unit file for compatibility. Please update package to include a 
native systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201716]: SysV service 
'/etc/init.d/mcelog' lacks a native systemd unit file. Automatically generating 
a unit file for compatibility. Please update package to include a native 
systemd unit file, in order to make it more safe and robust.
Dec 31 18:23:56 zira systemd-sysv-generator[201716]: SysV service 
'/etc/init.d/shellinabox' lacks a native systemd unit file. Automatically 
genera

Bug#969372: Missing After=network-online.target

[Thomas Goirand]

Hi,

The above .service file looks ok, though it's missing this:

After=network-online.target

Cheers,

Thomas Goirand (zigo)

Bug#976891: Unable to find next sigaction in signal chain

[Hans-Christoph Steiner]

Now fastboot and aapt build and link but both report this error:

   Unable to find next sigaction in signal chain

Looks like some dynamically loaded code is missing, the error is in 
sigchainlib/sigchain.cc:


static void lookup_next_symbol(T* output, T wrapper, const char* name) {
  void* sym = dlsym(RTLD_NEXT, name);  // NOLINT glibc triggers 
cert-dcl16-c with RTLD_NEXT.

  if (sym == nullptr) {
sym = dlsym(RTLD_DEFAULT, name);
if (sym == wrapper || sym == sigaction) {
  fatal("Unable to find next %s in signal chain", name);
}
  }
  *output = reinterpret_cast(sym);
}

Bug#978749: requests: circular dependency makes requests unbuildable

[Thomas Goirand]

On 12/31/20 4:31 PM, Daniele Tricoli wrote:
> Nowadays for
> urllib3 upstream uses a range of versions, and I take care of both urllib3 and
> requests, so we should not have problems.

Oh, it's very nice that upstream changed their mind, after all of this
time. Thanks for sharing this info. I can clearly remember heated
discussions in the OpenStack list where they really stand on the opinion
they should vendor everything and that everyone suggesting otherwise was
a fool. :)

> Thomas thanks for spotting the missing "nodoc", I will fix also this but not
> with the upload that will close this bug.

Great! :)

> Many thanks, cheers and happy new year!

Happy new year too.

Cheers,

Thomas Goirand (zigo)

Processed: closing 978685

[Debian Bug Tracking System]

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

> close 978685 2.0.235-4
Bug #978685 [libjhlabs-filters-java] libjhlabs-filters-java: tries to overwrite 
/usr/share/doc-base/doc-base
Marked as fixed in versions libjhlabs-filters-java/2.0.235-4; no longer marked 
as fixed in versions 2.0.235-4.
Bug #978685 [libjhlabs-filters-java] libjhlabs-filters-java: tries to overwrite 
/usr/share/doc-base/doc-base
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#978684: marked as done (autopkgtest should test the installed package)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 16:18:40 +
with message-id 
and subject line Bug#978684: fixed in apk-parser 2.6.10+ds-4
has caused the Debian Bug report #978684,
regarding autopkgtest should test the installed package
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.)


-- 
978684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apk-parser
Severity: serious

Hi,

As pointed in the see autopkgtest specification [1] linked from the
release team documentation [2] “the tests must test the *installed*
version of the package”. The autopkgtest from this package only uses the
source package, and as such violates the specification. Displaying it as
an example in the wiki [3] may not be advisable.

Regards

David

1: 
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst
2: https://release.debian.org/bullseye/freeze_policy.html
3: https://wiki.debian.org/Java/Packaging#autopkgtest


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: apk-parser
Source-Version: 2.6.10+ds-4
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated apk-parser 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: Fri, 01 Jan 2021 01:03:59 +0900
Source: apk-parser
Architecture: source
Version: 2.6.10+ds-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Roger Shimizu 
Closes: 978684
Changes:
 apk-parser (2.6.10+ds-4) unstable; urgency=medium
 .
   * d/control: Remove unnecessary B-D
   * Revert "d/tests: Reuse dh_auto_test for autopkgtest"
 (Closes: #978684).
Checksums-Sha1:
 1b57a44c480ce74c82d95f8e05d09cc49760f910 2085 apk-parser_2.6.10+ds-4.dsc
 a27af011348c62fa367af350978d9c5d585d60dd 7340 
apk-parser_2.6.10+ds-4.debian.tar.xz
 71df792692a8423a97bc5465eb172b979112d208 12419 
apk-parser_2.6.10+ds-4_source.buildinfo
Checksums-Sha256:
 15af20bee22492b63aa481cebf78de7ec706dfeb267f5fcd380028ee47baec19 2085 
apk-parser_2.6.10+ds-4.dsc
 2d3cf750607d7d312a78af9ff4fde657df9553aebdd98ca42dc3345054741f92 7340 
apk-parser_2.6.10+ds-4.debian.tar.xz
 64596d8384d2e1ede9d0980aa3499bfdce4701ee5668f6f36aec6b0056b251bb 12419 
apk-parser_2.6.10+ds-4_source.buildinfo
Files:
 0ba648261b80d5740b2c7c78f0870a51 2085 java optional apk-parser_2.6.10+ds-4.dsc
 6165008ed7a4b71ecd78440e29b60366 7340 java optional 
apk-parser_2.6.10+ds-4.debian.tar.xz
 73e87b7c4b2b352be11fc9d5dd538c4e 12419 java optional 
apk-parser_2.6.10+ds-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl/t+B8QHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qJA2D/96fnalW38ujRPkAPgba9OoCMgrv1i2uAKR
qTYKtcPFU7HghAf3Q8l3HMt450EQb9iEq5HbLa2fEn9G+CnuZIO2XT0hhDcGQmMc
HEZEF7tH88865lVOtoRMY9JbhQ6sB2qx27QvC3yOS/9xrYBPyfnOY8olkQM/V5S7
9+g5I0UDFGE2D4OMmxwmc0pe1J1bKShupVokeLN+1lDNzKWUOKHz4wTlD8mWui1P
RDCAjOmO5YciOzS+Tl7XiQLqnjp+gM7qYg+pbY9+V1hDLk+W40tBEFgPDdZIKPyI
EQvmOq6Y2mxAr9baqo+Y2FlRy2jEH2N5yklvUsYI22v0CWz+uI6TtX5+M+5yO31M
gWragG0pWVwTqWoWZM13VD2/4uWtHWbY02WZDIJh1cC7Ol7Javd7Vj9uGIZ9HurE
qep1TUtdGLWNogsO2qDrAf3ic01s8x29TY44aOBu44e0Tl2U8NixZnyW6Filj6mG
PUgEcrkSibKEHYoSVpPPHsEYCfNntLOGOxeGeh1ACDu+c3YdHpdixE0lwUlnoVoQ
XIj1/XyN+X5+mLsfYf7e8x+ZtuErQIsn9KJjiN7/X79hBJf1v1MPLaizHmc26uAE
s7x99YO8HZa11+W+7vWWsUgfMHTedLGAH0cjIO9fLSqfb5zzisFhCch6mjQgY7GA
2M1XZ6TX+A==
=ipLK
-END PGP SIGNATURE End Message ---

Bug#978684: autopkgtest should test the installed package

[Roger Shimizu]

> As pointed in the see autopkgtest specification [1] linked from the
> release team documentation [2] “the tests must test the *installed*
> version of the package”. The autopkgtest from this package only uses the
> source package, and as such violates the specification. Displaying it as
> an example in the wiki [3] may not be advisable.

Thanks for spotting this!
I edited the wiki to add this is a bad example for autopkgtest.
And I'm going to remove the debian/tests folder on the next upload.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#978749: requests: circular dependency makes requests unbuildable

[Sebastian Ramacher]

On 2020-12-31 16:03:48 +0100, Thomas Goirand wrote:
> On 12/31/20 1:25 PM, Sebastian Ramacher wrote:
> > Hi Thomas
> > 
> > On 2020-12-31 13:06:37 +0100, Thomas Goirand wrote:
> >> Hi Sebastian,
> >>
> >> I'm challenging the fact that a circular dependency is a problem for
> >> arch:all packages. At least, it shouldn't be an RC bug, IMO.
> > 
> > If packages cannot be built on the buildds, they are RC-buggy.
> 
> Which is a different topic.
> 
> >> I also don't understand why you've renamed the original bug, which seems
> >> to be very different from the circular dependency you're describing. Can
> >> you explain why they are related, and why we shouldn't have 2 bugs?
> > 
> > The bug is that a build of requests is missing. The version that fixes
> > the uninstallability of python3-requests was already uploaded.
> 
> If I understand correctly, the issue was that requests had:
> 
> python3-chardet (>= 3.0.2), python3-chardet (<< 3.1.0)

No, the issue was that requests with a fixed dependency on
python3-chardet was not buildable because it build-depends on sphinx
which in turn depends on python3-requests which was not installable.

Cheers

> 
> as (build-)depends, which prevents using charted 4. This is very
> different from a circular dependency problem.
> 
> Cheers,
> 
> Thomas Goirand (zigo)

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://github.com/BelledonneCommunications/mediastreamer2/pull/27
Bug #978616 [src:mediastreamer2] mediastreamer2: doesn't build correct 
libraries with cmake?
Set Bug forwarded-to-address to 
'https://github.com/BelledonneCommunications/mediastreamer2/pull/27'.

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

Bug#978749: requests: circular dependency makes requests unbuildable

[Daniele Tricoli]

Hello Thomas, hello Sebastian!


Thomas, thanks for always caring about requests!

On Thu, Dec 31, 2020 at 04:03:48PM +0100, Thomas Goirand wrote:
> If I understand correctly, the issue was that requests had:
> 
> python3-chardet (>= 3.0.2), python3-chardet (<< 3.1.0)
> 
> as (build-)depends, which prevents using charted 4. This is very
> different from a circular dependency problem.

As discussed on IRC I'm going to drop the upper bounds for both chardet and
urllib3: they was introduced at the time when requests was vendoring all its
dependencies and it was more coupled especially with urllib3. Nowadays for
urllib3 upstream uses a range of versions, and I take care of both urllib3 and
requests, so we should not have problems. chardet is more mature and should not
be a problem at all.

For the severity of this issue, well I think that we all want Debian in the best
shape, so I don't care too much, it's something to be fixed! :)

Thomas thanks for spotting the missing "nodoc", I will fix also this but not
with the upload that will close this bug.

Many thanks, cheers and happy new year!

-- 
  Daniele Tricoli 'eriol'
  https://mornie.org


signature.asc
Description: PGP signature

Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

[Gianfranco Costamagna]

control: forwarded -1 
https://github.com/BelledonneCommunications/mediastreamer2/pull/27

thanks

G.

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Sebastiaan Couwenberg]

reopen 978739
thanks

On 12/31/20 4:13 PM, Daniele Tricoli wrote:
> On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote:
>> Package: chardet
>> Version: 4.0.0-1
>> Severity: serious
>> Justification: makes the package in question unusable or mostly so
>> Control: affects -1 src:requests src:qgis
>>
>> Dear Maintainer,
>>
>> Upgrading python3-chardet causes the removal of many packages:
>>
>>  The following packages will be REMOVED:
>>chrome-gnome-shell gnome-music pycsw pycsw-wsgi python3-astropy-helpers 
>> python3-boto3 python3-botocore python3-cupshelpers python3-gitlab 
>> python3-numpydoc python3-owslib python3-plotly python3-pycsw python3-pywps 
>> python3-qgis
>>python3-reportbug python3-requests python3-requests-oauthlib 
>> python3-s3transfer python3-sphinx python3-sphinx-astropy 
>> python3-sphinx-automodapi python3-sphinx-gallery pywps qgis 
>> qgis-plugin-grass reportbug system-config-printer
>>system-config-printer-common system-config-printer-udev 
>> torbrowser-launcher
>>  The following packages will be upgraded:
>>python3-chardet
>>  1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
>>
>> python3-requests does not support version 3.1.0 or higher:
>>
>>   python3-chardet (<< 3.1.0)
>>
>> With the freeze coming in a few months it may be wise to revert back to 
>> 3.0.x for bullseye.
>>
>> Otherwise the python3-chardet rdeps need to fixed before that time.
> 
> As soon as noticed the chardet upload I uploaded requests 2.25.1+dfsg-1 which
> fix the problem, but there was a time window during the propagation of the new
> version when the problem was reproducible.

Thanks for quickly acting on this, but the problem is not limited to
python3-requests. Several other reverse dependencies need to be updated
for the new chardet as well. The autopkgtest failures include some of them:

 https://qa.debian.org/excuses.php?package=chardet

> Happy new year!

The same to you!

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Debian Bug Tracking System]

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

> reopen 978739
Bug #978739 {Done: Daniele Tricoli } [chardet] chardet: 
Upgrading python3-chardet breaks many packages
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.25.1+dfsg-1.
> thanks
Stopping processing here.

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

Bug#978739: marked as done (chardet: Upgrading python3-chardet breaks many packages)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 16:13:05 +0100
with message-id <20201231151305.ju5ubbcepdwr52h4@mornie>
and subject line Re: Bug#978739: chardet: Upgrading python3-chardet breaks many 
packages
has caused the Debian Bug report #978739,
regarding chardet: Upgrading python3-chardet breaks many packages
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.)


-- 
978739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chardet
Version: 4.0.0-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: affects -1 src:requests src:qgis

Dear Maintainer,

Upgrading python3-chardet causes the removal of many packages:

 The following packages will be REMOVED:
   chrome-gnome-shell gnome-music pycsw pycsw-wsgi python3-astropy-helpers 
python3-boto3 python3-botocore python3-cupshelpers python3-gitlab 
python3-numpydoc python3-owslib python3-plotly python3-pycsw python3-pywps 
python3-qgis
   python3-reportbug python3-requests python3-requests-oauthlib 
python3-s3transfer python3-sphinx python3-sphinx-astropy 
python3-sphinx-automodapi python3-sphinx-gallery pywps qgis qgis-plugin-grass 
reportbug system-config-printer
   system-config-printer-common system-config-printer-udev torbrowser-launcher
 The following packages will be upgraded:
   python3-chardet
 1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.

python3-requests does not support version 3.1.0 or higher:

  python3-chardet (<< 3.1.0)

With the freeze coming in a few months it may be wise to revert back to 3.0.x 
for bullseye.

Otherwise the python3-chardet rdeps need to fixed before that time.

Kind Regards,

Bas
--- End Message ---
--- Begin Message ---
Version: 2.25.1+dfsg-1

Hello Bas,
thanks for the report!

On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote:
> Package: chardet
> Version: 4.0.0-1
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> Control: affects -1 src:requests src:qgis
> 
> Dear Maintainer,
> 
> Upgrading python3-chardet causes the removal of many packages:
> 
>  The following packages will be REMOVED:
>chrome-gnome-shell gnome-music pycsw pycsw-wsgi python3-astropy-helpers 
> python3-boto3 python3-botocore python3-cupshelpers python3-gitlab 
> python3-numpydoc python3-owslib python3-plotly python3-pycsw python3-pywps 
> python3-qgis
>python3-reportbug python3-requests python3-requests-oauthlib 
> python3-s3transfer python3-sphinx python3-sphinx-astropy 
> python3-sphinx-automodapi python3-sphinx-gallery pywps qgis qgis-plugin-grass 
> reportbug system-config-printer
>system-config-printer-common system-config-printer-udev torbrowser-launcher
>  The following packages will be upgraded:
>python3-chardet
>  1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
> 
> python3-requests does not support version 3.1.0 or higher:
> 
>   python3-chardet (<< 3.1.0)
> 
> With the freeze coming in a few months it may be wise to revert back to 3.0.x 
> for bullseye.
> 
> Otherwise the python3-chardet rdeps need to fixed before that time.

As soon as noticed the chardet upload I uploaded requests 2.25.1+dfsg-1 which
fix the problem, but there was a time window during the propagation of the new
version when the problem was reproducible.

Happy new year!

-- 
  Daniele Tricoli 'eriol'
  https://mornie.org


signature.asc
Description: PGP signature
--- End Message ---

Bug#978739: chardet: Upgrading python3-chardet breaks many packages

[Daniele Tricoli]

Version: 2.25.1+dfsg-1

Hello Bas,
thanks for the report!

On Thu, Dec 31, 2020 at 05:55:17AM +0100, Bas Couwenberg wrote:
> Package: chardet
> Version: 4.0.0-1
> Severity: serious
> Justification: makes the package in question unusable or mostly so
> Control: affects -1 src:requests src:qgis
> 
> Dear Maintainer,
> 
> Upgrading python3-chardet causes the removal of many packages:
> 
>  The following packages will be REMOVED:
>chrome-gnome-shell gnome-music pycsw pycsw-wsgi python3-astropy-helpers 
> python3-boto3 python3-botocore python3-cupshelpers python3-gitlab 
> python3-numpydoc python3-owslib python3-plotly python3-pycsw python3-pywps 
> python3-qgis
>python3-reportbug python3-requests python3-requests-oauthlib 
> python3-s3transfer python3-sphinx python3-sphinx-astropy 
> python3-sphinx-automodapi python3-sphinx-gallery pywps qgis qgis-plugin-grass 
> reportbug system-config-printer
>system-config-printer-common system-config-printer-udev torbrowser-launcher
>  The following packages will be upgraded:
>python3-chardet
>  1 upgraded, 0 newly installed, 31 to remove and 0 not upgraded.
> 
> python3-requests does not support version 3.1.0 or higher:
> 
>   python3-chardet (<< 3.1.0)
> 
> With the freeze coming in a few months it may be wise to revert back to 3.0.x 
> for bullseye.
> 
> Otherwise the python3-chardet rdeps need to fixed before that time.

As soon as noticed the chardet upload I uploaded requests 2.25.1+dfsg-1 which
fix the problem, but there was a time window during the propagation of the new
version when the problem was reproducible.

Happy new year!

-- 
  Daniele Tricoli 'eriol'
  https://mornie.org


signature.asc
Description: PGP signature

Processed (with 1 error): retitle 978749 bound on python3-chardet < 3.1.0 prevents install & build

[Debian Bug Tracking System]

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

> retitle 978749 bound on python3-chardet < 3.1.0 prevents install & build
Bug #978749 [src:requests] requests: circular dependency makes requests 
unbuildable
Changed Bug title to 'bound on python3-chardet < 3.1.0 prevents install & 
build' from 'requests: circular dependency makes requests unbuildable'.
> forcemerge 978749 978738
Bug #978749 [src:requests] bound on python3-chardet < 3.1.0 prevents install & 
build
Unable to merge bugs because:
package of #978738 is 'python3-requests' not 'src:requests'
Failed to forcibly merge 978749: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Bug#978749: requests: circular dependency makes requests unbuildable

[Thomas Goirand]

On 12/31/20 1:25 PM, Sebastian Ramacher wrote:
> Hi Thomas
> 
> On 2020-12-31 13:06:37 +0100, Thomas Goirand wrote:
>> Hi Sebastian,
>>
>> I'm challenging the fact that a circular dependency is a problem for
>> arch:all packages. At least, it shouldn't be an RC bug, IMO.
> 
> If packages cannot be built on the buildds, they are RC-buggy.

Which is a different topic.

>> I also don't understand why you've renamed the original bug, which seems
>> to be very different from the circular dependency you're describing. Can
>> you explain why they are related, and why we shouldn't have 2 bugs?
> 
> The bug is that a build of requests is missing. The version that fixes
> the uninstallability of python3-requests was already uploaded.

If I understand correctly, the issue was that requests had:

python3-chardet (>= 3.0.2), python3-chardet (<< 3.1.0)

as (build-)depends, which prevents using charted 4. This is very
different from a circular dependency problem.

Cheers,

Thomas Goirand (zigo)

Bug#978616: mediastreamer2: doesn't build correct libraries with cmake?

[Gianfranco Costamagna]

On Wed, 30 Dec 2020 17:18:41 +0100 Bernhard Schmidt  wrote:
> Dear Gianfranco,
> 
> Thanks for filing this bug report. I’m away for the next couple of days and 
> could not check, but wouldn’t just patching the pkgconfig file (your second 
> option) be a lot easier? Upstream merged both libraries and they probably 
> just forgot to change the pkgconfig file as well.
> 
> In the end linphone upstream does not seem to care much about other programs 
> using their library. 
> 

I did my assumption based on this:

[2.9.0] - 2013-05-27
Added
[...]
Changed
Split the libmediastreamer library in two libraries: libmediastreamer_base and 
libmediastreamer_voip. For VoIP support, both libraries must be linked to the 
executable.


So I thought that upstream was moving from 1 library into 2 different libs.
If upstream moved from 2 to 1, patching the pkgconfig file is indeed the right 
(and upstreamable) thing to do.

But according to git log, you seems to be right:

commit 50c9633712a57910612c4c58d237fbe5652843dd
Author: Ghislain MARY 
Date:   Mon Oct 15 10:51:37 2018 +0200

Build a single mediastreamer library (instead of mediastreamer_base and 
mediastreamer_voip) and a single mediastreamer2 framework for iOS.


So, ok for the easier approach!

Description: Fix pkgconfig linkage
Author: Gianfranco Costamagna 
Last-Update: 2020-12-31

--- mediastreamer2-4.4.21.orig/mediastreamer.pc.in
+++ mediastreamer2-4.4.21/mediastreamer.pc.in
@@ -7,5 +7,5 @@ Name: mediastreamer
 Description: A mediastreaming library for telephony applications
 Requires: ortp bctoolbox
 Version: @MEDIASTREAMER_VERSION@
-Libs: -L@libdir@ -lmediastreamer_base -lmediastreamer_voip
+Libs: -L@libdir@ -lmediastreamer
 Cflags: -I@includedir@ @MS_PUBLIC_CFLAGS@


This one should do the trick.
I'll upstream it in a pull request shortly!

G.

Processed: severity of 978753 is normal

[Debian Bug Tracking System]

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

> severity 978753 normal
Bug #978753 [src:linux] usercopy: Kernel memory exposure attempt
Bug #978752 [src:linux] usercopy: Kernel memory exposure attempt
Severity set to 'normal' from 'critical'
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.

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

Bug#978437: geoclue-2.0: regression in 2.5.7-1, no geolocation returned

[gregor herrmann]

On Thu, 31 Dec 2020 03:48:25 +0100, Laurent Bigonville wrote:

> The following line is actually the real problem, I did all my tests on
> laptop with wifi cards, I just tried on my desktop and I get the same error
> (and timeout as you)
> > (geoclue:10479): Geoclue-WARNING **: 16:26:35.098: Failed to create query: 
> > No WiFi devices available
> It looks like geoclue is not doing any request to the Mozilla Location
> Service is there is no wifi cards (or wifi network around) anymore

Thanks for the fix!

I can confirm that it works for me now as well \o/

(The interesting thing is that I did this on my laptop; admittedly
yesterday with Wifi turned off but I thought I had tried last week as
well after enabling Wifi but I might have fallen into some trap,
maybe the startup timeout …)


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#975793: marked as done (libsignon-glib: FTBFS: make[3]: *** No rule to make target '/usr/share/dbus-1/interfaces/com.google.code.AccountsSSO.SingleSignOn.AuthService.xml', needed by 'sso-auth-serv

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 13:48:36 +
with message-id 
and subject line Bug#975793: fixed in libsignon-glib 1.15-1
has caused the Debian Bug report #975793,
regarding libsignon-glib: FTBFS: make[3]: *** No rule to make target 
'/usr/share/dbus-1/interfaces/com.google.code.AccountsSSO.SingleSignOn.AuthService.xml',
 needed by 'sso-auth-service-gen.c'.  Stop.
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.)


-- 
975793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libsignon-glib
Version: 1.12-2.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201125 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[3]: Entering directory '/<>/libsignon-glib'
> glib-genmarshal --body --prefix=_signon_marshal signon-marshal.list > 
> signon-marshal.c
> INFO: Reading signon-marshal.list...
> glib-genmarshal --header --prefix=_signon_marshal signon-marshal.list > 
> signon-marshal.h
> INFO: Reading signon-marshal.list...
> ( cd . &&  glib-mkenums \
> --fhead "#ifndef __SIGNON_ENUM_TYPES_H__\n#define 
> __SIGNON_ENUM_TYPES_H__\n#include \n\nG_BEGIN_DECLS\n" \
> --fprod "/* enumerations from \"@filename@\" */\n" \
> --vhead "GType @enum_name@_get_type (void) G_GNUC_CONST;\n#define 
> SIGNON_TYPE_@ENUMSHORT@ (@enum_name@_get_type())\n" \
> --ftail "G_END_DECLS\n\n#endif /* __SIGNON_ENUM_TYPES_H__ */" \
> signon-auth-session.h signon-identity-info.h signon-errors.h ) >> 
> xgen-geth \
> && (cmp -s xgen-geth signon-enum-types.h || cp xgen-geth 
> signon-enum-types.h ) \
> && rm -f xgen-geth \
> && echo timestamp > stamp-signon-enum-types.h
> true
> ( cd . && glib-mkenums \
> --fhead "#include \"signon-enum-types.h\"\n" \
> --fhead "#include \"signon-identity-info.h\"\n" \
>   --fhead "#include \"signon-auth-session.h\"\n" \
>   --fhead "#define g_intern_static_string(s) (s)\n" \
> --fprod "\n/* enumerations from \"@filename@\" */" \
> --ftail "\n#define __SIGNON_ENUM_TYPES_C__\n" \
> --vhead "GType\n@enum_name@_get_type (void)\n{\n  static GType etype = 
> 0;\n  if (etype == 0) {\nstatic const G@Type@Value values[] = {" \
> --vprod "  { @VALUENAME@, \"@VALUENAME@\", \"@valuenick@\" }," \
> --vtail "  { 0, NULL, NULL }\n};\netype = 
> g_@type@_register_static (g_intern_static_string (\"@EnumName@\"), values);\n 
>  }\n  return etype;\n}\n" \
> signon-auth-session.h signon-identity-info.h ) > xgen-getc \
> && cp xgen-getc signon-enum-types.c  \
> && rm -f xgen-getc
> ( cd . && glib-mkenums \
> --fhead "#include \"signon-enum-types.h\"\n#include 
> \"signon-errors.h\"\n#include \"signoncommon.h\"\n#define 
> g_intern_static_string(s) (s)\n" \
> --fprod "\n/* enumerations from \"@filename@\" */" \
> --ftail "\n#define __SIGNON_ENUM_TYPES_C__\n" \
> --vhead "GType\n@enum_name@_get_type (void)\n{\n  static GType etype = 
> 0;\n  if (etype == 0) {\nstatic const G@Type@Value values[] = {" \
> --vprod "  { @VALUENAME@, SED@VALUENAME@, \"@valuenick@\" }," \
> --vtail "  { 0, NULL, NULL }\n};\netype = 
> g_@type@_register_static (g_intern_static_string (\"@EnumName@\"), values);\n 
>  }\n  return etype;\n}\n" \
> signon-errors.h ) | \
> /bin/sed -e 's/SEDSIGNON_ERROR_\([^,]*\)/SIGNOND_\1_ERR_NAME/' \
> > xgen-getc \
> && cp xgen-getc signon-errors-enum.c  \
> && rm -f xgen-getc
> make[3]: *** No rule to make target 
> '/usr/share/dbus-1/interfaces/com.google.code.AccountsSSO.SingleSignOn.AuthService.xml',
>  needed by 'sso-auth-service-gen.c'.  Stop.
> make[3]: Leaving directory '/<>/libsignon-glib'
> make[2]: *** [Makefile:504: all-recursive] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/11/25/libsignon-glib_1.12-2.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libsignon-glib
Source-Version: 1.15-1
Done: Pino Toscano 

We believe that the bug you reported is fixed in the latest version of
libsignon-glib, which is due to be installed in the Debi

Processed: Re: Bug#978753: usercopy: Kernel memory exposure attempt

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #978753 [src:linux] usercopy: Kernel memory exposure attempt
Bug #978752 [src:linux] usercopy: Kernel memory exposure attempt
Added tag(s) moreinfo.
Added tag(s) moreinfo.

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

Bug#978753: usercopy: Kernel memory exposure attempt

[Salvatore Bonaccorso]

Control: tags -1 + moreinfo

Hi Markus,

Thanks for your report.

On Thu, Dec 31, 2020 at 12:45:47PM +0200, Markus Bäcklund wrote:
> Package: src:linux-image-4.19.0-13-amd64
> Version: 4.19.160-2
> Severity: critical
> Justification: breaks the whole system
> 
> 
> 
> -- Package-specific info:
> ** Kernel log: boot messages should be attached
> 
> 
> -- System Information:
> Debian Release: 10.7
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.4.86 (SMP w/4 CPU cores)
> Kernel taint flags: TAINT_UNSIGNED_MODULE

5.4.86 is not a Debian kernel in buster and was tainted. Can you
please provide the kernel logs as well? This might give some better
clue.

Regards,
Salvatore

Bug#977552: marked as done (gnutls28: Time bomb in testpkcs11.sh triggered)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 13:19:32 +
with message-id 
and subject line Bug#977552: fixed in gnutls28 3.7.0-5
has caused the Debian Bug report #977552,
regarding gnutls28: Time bomb in testpkcs11.sh triggered
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.)


-- 
977552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnutls28
Version: 3.6.15-1
Severity: serious
Tags: upstream ftbfs
Justification: fails to build from source
Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1135

autopkgtests and build fail now due to an expired certificate

Not After : Dec 13 08:24:54 2020 GMT

cu Andreas
--- End Message ---
--- Begin Message ---
Source: gnutls28
Source-Version: 3.7.0-5
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated gnutls28 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 13:11:15 +0100
Source: gnutls28
Architecture: source
Version: 3.7.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 977552
Changes:
 gnutls28 (3.7.0-5) unstable; urgency=low
 .
   * Update from upstream GIT master, replace patches, add new ones.
 + 48_0001-Fix-non-empty-session-id-TLS13_APPENDIX_D4.patch added.
 + 50_0001-tests-Fix-tpmtool_test-due-to-changes-in-trousers.patch
--> 48_0002-tests-Fix-tpmtool_test-due-to-changes-in-trousers.patch
 + 50_0002-testpkcs11-use-datefudge-to-trick-certificate-expiry.patch
--> 48_0003-testpkcs11-use-datefudge-to-trick-certificate-expiry.patch
Closes: #977552
 + 45_opensslcompat_no_export_gl.diff
--> 48_0005-libgnutls-openssl-Clean-up-list-of-exported-symbols.patch.
 + 48_0006-Fix-a-common-typo-of-gnutls_priority_t.patch added.
   * Upload to unstable.
Checksums-Sha1: 
 7b58c6de6bdf591c0dec134046241a1369980d5c 3480 gnutls28_3.7.0-5.dsc
 59493c8d40c002dacaf0c7a455904dab84bf7dd0 70816 gnutls28_3.7.0-5.debian.tar.xz
Checksums-Sha256: 
 d2b1242f130cfd626dc57b285352f371f56d74df978801077cbe89c9394fc519 3480 
gnutls28_3.7.0-5.dsc
 acc933295f34c4ef01589a39afc9da6ae026e773b8c371d8d9b1fcff7cbd2fe6 70816 
gnutls28_3.7.0-5.debian.tar.xz
Files: 
 3b17c50f103158c6d1a446ef8bb35ad9 3480 libs optional gnutls28_3.7.0-5.dsc
 a759b05383b33fd91c1f00171068d695 70816 libs optional 
gnutls28_3.7.0-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAl/tzGgACgkQpU8BhUOC
FIS6lQ/+OUAU91F5d84phOgTj+w7nWm1ucpK5gPEgfLlQmyucnzfEdXs7Rteaid1
l8rV/irasyxV3uC8pd3+TXke9BE3yGyypPMjdsDc1donIXasOQIf+6spUedR2V+1
arW/HOJ2wWGVb1iXzALS3XVakDZ92/5J+BsGhw9zKNq3EtfR0op2u/FRlKWJ4Pc/
887d3Fum9v4et8fp+5ihzGJVvc2JTGNp6UfrtFCVKEldi29ClfaNZyPwZWzW9mYB
H3ApKmXovtV3yzvy2C+Yld8vJwnRm3Kd46yUtNggM8mEM1rwBLmijmj4IOEOW3pY
3qT0nfby6rzQcQirYknfMJ+F3S4voDTZIIhGNFAoCum5nBH4VPGpcK4uTmWSVo4R
/oiaWzK8LGlXSvO9G/FPSbpc/516T6Wcv/FT+HQzETyELBTYkDsT82MgebdpMbjr
bRmsb3DigTlNh5TItL+1oablYs12B6dJWWgDPHbMnbx+vReRsXkAPaRywWy9+n5i
FrYNV3sxi5dLiHGwdw1A8HBh/P5f2qOb6bzPlcJHoZZzzTXFqI+KZkpZrO7cA+zy
Q4zTUyleHZYz/gtwi04crv9wucNSktlQ9ZNragD3kEPUwtTSoazlvCxA1ZWHljAh
8BJeVqU0dz6X9pcH6doviv/zk27jdn0Uk/TnQFZg7u6d6pFjxtI=
=DsRZ
-END PGP SIGNATURE End Message ---

Bug#973651: marked as done (libqb-tools: missing Breaks+Replaces: libqb-dev (<< 2))

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 13:19:44 +
with message-id 
and subject line Bug#973651: fixed in libqb 2.0.2-1
has caused the Debian Bug report #973651,
regarding libqb-tools: missing Breaks+Replaces: libqb-dev (<< 2)
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.)


-- 
973651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973651
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqb-tools
Version: 2.0.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' 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 .../libqb-tools_2.0.1-1_amd64.deb ...
  Unpacking libqb-tools (2.0.1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libqb-tools_2.0.1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/sbin/qb-blackbox', which is also in package 
libqb-dev 1.0.6-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libqb-tools_2.0.1-1_amd64.deb
 

cheers,

Andreas


libqb-dev=1.0.6-2_libqb-tools=2.0.1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libqb
Source-Version: 2.0.2-1
Done: Ferenc Wágner 

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

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated libqb 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, 26 Dec 2020 16:07:32 +0100
Source: libqb
Architecture: source
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HA Maintainers 

Changed-By: Ferenc Wágner 
Closes: 973651
Changes:
 libqb (2.0.2-1) unstable; urgency=medium
 .
   * [afb0870] libqb-tools took over qb-blackbox from libqb-dev (<< 2)
 Thanks to Andreas Beckmann (Closes: #973651)
   * [744f11b] New upstream release (2.0.2)
   * [313b9f7] Remove upstreamed patches, refresh the rest
   * [cef7c9d] Update symbols file
   * [7b1a007] Update Standards-Version to 4.5.1 (no changes required)
   * [50ead69] New patch: Fix typos and inconsistencies in doxygen2man help text
   * [6f165b3] New patch: doxygen2man: ignore all-whitespace brief description
   * Upload to unstable
Checksums-Sha1:
 fe54b0a3d46efc24f0b9ab08aa3c7bc75005df68 2489 libqb_2.0.2-1.dsc
 5af7e2d4d9a9c5ebd3c9bac83ca47582f5e00a2b 498700 libqb_2.0.2.orig.tar.xz
 e4db063fe1fce788e1f82d8ffa92053127f9829c 833 libqb_2.0.2.orig.tar.xz.asc
 61d7621c33173a702bd8321596e9a0acbb76f4b0 17328 libqb_2.0.2-1.debian.tar.xz
 88a99e578c873947c80fefe9cfdbbbf33363070a 8859 libqb_2.0.2-1_amd64.buildinfo
Checksums-Sha256:
 5a4963598b9a2dced1c8d6bcad0285af96ea8ae509f5adf81eccbf637276a58b 2489 
libqb_2.0.2-1.dsc
 2fb50c0bec848e5ffeac73ae32a202e2f2e4c61eec9d3633a0f241b47ac05ad0 498700 
libqb_2.0.2.orig.tar.xz
 c830df4d6c43a02bb52f7143123ada45ddc84dd08e22c7fc8d9ab99163f77466 833 
libqb_2.0.2.orig.tar.xz.asc
 5a1a13d3e2b559d23b6fb7c516e8bbe3e8a07fbd60c26d81839e8aeb49f98af8 17328 
libqb_2.0.2-1.debian.tar.xz
 f65c9555d181a4479a7e222d5dd0c2d03a49810de20731f466e3c59d692ac2df 8859 
libqb_2.0.2-1_amd64.buildinfo
Files:
 6300b52b6ee245bdee5fdd1501deaf35 2489 libs optional libqb_2.0.2-1.dsc
 1078e1efe8e1b93fd7a596873968493d 498700 libs optional libqb_2.0.2.orig.tar.xz
 0c8c8ef838c731fa6eb3ce1d9601eb3b 833 libs optional libqb_2.0.2.orig.tar.xz.asc
 7a66b4c03d17845138be9fc019b483e5 17328 libs optional 
libqb_2.0.2-1.debian.tar.xz
 c0cc15314d0eda53b451f73a303bc736 8859 libs optional 
libqb_2.0.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEwddEx0RNIUL7eugtOsj3Fkd+2yMFAl/nWWMACgkQOsj3Fkd+
2yMwbg/+M3ey1kXCnMZCk+P4uu

Processed: tagging 975793

[Debian Bug Tracking System]

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

> tags 975793 + pending
Bug #975793 [src:libsignon-glib] libsignon-glib: FTBFS: make[3]: *** No rule to 
make target 
'/usr/share/dbus-1/interfaces/com.google.code.AccountsSSO.SingleSignOn.AuthService.xml',
 needed by 'sso-auth-service-gen.c'.  Stop.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#974608: gthumb uses internal libexiv2 functions to get the user comment

[Martin-Éric Racine]

Package: gthumb
Version: 3:3.8.3-0.1
Followup-For: Bug #974608

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Fixed upstream 1 hour ago:

https://gitlab.gnome.org/GNOME/gthumb/-/commit/3bdb4f94ba37b410ac07c25b5c83e587b55482fd

See also:

https://gitlab.gnome.org/GNOME/gthumb/-/issues/137
https://gitlab.gnome.org/GNOME/gthumb/-/issues/30

I haven't checked whether this can be backported to the 3.8.3 branch. Upgrading 
the Debian package to 3.11.1 might make more sense.

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

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

Versions of packages gthumb depends on:
ii  gsettings-desktop-schemas   3.28.1-1
ii  gthumb-data 3:3.8.3-0.1
ii  libbrasero-media3-1 3.12.2-5
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4
ii  libclutter-1.0-01.26.2+dfsg-10
ii  libclutter-gtk-1.0-01.8.4-4
ii  libexiv2-14 0.25-4+deb10u1
ii  libgcc1 1:8.3.0-6
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libgl1-mesa-dri 18.3.6-2+deb10u1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libgtk-3-0  3.24.5-1
ii  libjpeg62-turbo 1:1.5.2-2+deb10u1
ii  libjson-glib-1.0-0  1.4.4-2
ii  liblcms2-2  2.9-3
ii  libpango-1.0-0  1.42.4-8~deb10u1
ii  libpangocairo-1.0-0 1.42.4-8~deb10u1
ii  libpng16-16 1.6.36-6
ii  libraw190.19.2-2
ii  librsvg2-2  2.44.10-2.1
ii  libsecret-1-0   0.18.7-1
ii  libsoup2.4-12.64.2-2
ii  libstdc++6  8.3.0-6
ii  libtiff54.1.0+git191117-2~deb10u1
ii  libwebkit2gtk-4.0-372.30.4-1~deb10u1
ii  libwebp60.6.1-2
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages gthumb recommends:
ii  libgphoto2-6   2.5.22-3
ii  libgphoto2-port12  2.5.22-3

gthumb suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl/txdoACgkQrh+Cd8S0
17Z/Fg/+LtN/1HlY196Ud3lZKaZCbb4py9hYszATImYcOtY8/kzxWhMJXYPLEkEj
WiiN2TxzWgXNTJWc8GLIUDC/bFI3ePculd5nn9c1kiVxP4+2lLXANxnwGUJS0mLb
ssbNSO5asysFWYtV17b30qU6Nfc6FPmnbSbhpz24OfrKytRw/w+trtJCkv/6g18c
PcVD8N050uXaJX7+cwyzZ1kjXyEcAzL7uCuNPlu8O9kZcTm7+7cMD4nufBLtNW4a
cOC0/UigG/0L+hD//8sBq8FXdLrUvqStp1mffeGLy0k7yDFf9LMVO4kQmwLI6edQ
s7SFagRj23pUn7Ibvp3EQUgFfDe7IPujsFVsNLCpir/IVRQBoTUbhHPopKsGaJkJ
KddKqxT0DZ40yJVveDAN7EaIKSkSzoWJJ4F40vjYvMnW6XO+ZRIaOsbWgGaOVPdh
HBxga3g/8X0xzlhkenStqnxliyTjvHzAa0H7e0Ka610/9Kc/6GmMc1QpEDmYuCbM
jmmki3I3JWG5P6t+bo+8kMRhTr2wwohrL51kIctP6UqcN2YZphHLvjH+O736Q4IP
WqFNJxb4ntiPbVi6ETLlRo/vjbNynIE70TEp6QVWPn4j9kpsR/jKlX9ElnILQfqd
jBrTNMl15PDTahJZ01kmNAT5ZCygs9SKaOK0U02p50yjz6MO+qE=
=fi0x
-END PGP SIGNATURE-

Processed: tagging 974608

[Debian Bug Tracking System]

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

> tags 974608 + fixed-upstream
Bug #974608 [gthumb] gthumb uses internal libexiv2 functions to get the user 
comment
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#978272: marked as done (python-xopen: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 12:39:39 +
with message-id 
and subject line Bug#978272: fixed in python-xopen 1.0.1-2
has caused the Debian Bug report #978272,
regarding python-xopen: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
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.)


-- 
978272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-xopen
Version: 1.0.1-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package python-xopen
> dpkg-buildpackage: info: source version 1.0.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Nilesh Patra 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_xopen/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-xopen using existing 
> ./python-xopen_1.0.1.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  python-xopen-1.0.1/src/xopen/_version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-xopen_1.0.1-1.diff.Kq1TfT
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2020-12-26T18:44:13Z

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/python-xopen_1.0.1-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-xopen
Source-Version: 1.0.1-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated python-xopen package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 17:41:11 +0530
Source: python-xopen
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 978272
Changes:
 python-xopen (1.0.1-2) unstable; urgency=medium
 .
   * Clean _version.py pre-build
 (Closes: #978272)
   * Declare compliance with policy 4.5.1
Checksums-Sha1:
 592e5c40fad8f18c4c723ff09958df2623195595 2268 python-xopen_1.0.1-2.dsc
 edd11dada3d0a72458c2c46e35bb0eac01cd2f8f 3052 
python-xopen_1.0.1-2.debian.tar.xz
 8abaac4e2fc3dbcc16c145ccc7e7cd85bdff937c 6802 
python-xopen_1.0.1-2_amd64.buildinfo
Checksums-Sha256:
 a9a6fa5c5a3054

Processed: merge 978752 978753 (duplicate reports)

[Debian Bug Tracking System]

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

> merge 978752 978753
Bug #978752 [src:linux] usercopy: Kernel memory exposure attempt
Bug #978753 [src:linux] usercopy: Kernel memory exposure attempt
Merged 978752 978753
> thanks
Stopping processing here.

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

Processed: Re: Bug#978753: usercopy: Kernel memory exposure attempt

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:linux 4.19.160-2
Bug #978753 [src:linux-image-4.19.0-13-amd64] usercopy: Kernel memory exposure 
attempt
Warning: Unknown package 'src:linux-image-4.19.0-13-amd64'
Bug reassigned from package 'src:linux-image-4.19.0-13-amd64' to 'src:linux'.
No longer marked as found in versions linux-image-4.19.0-13-amd64/4.19.160-2.
Ignoring request to alter fixed versions of bug #978753 to the same values 
previously set
Bug #978753 [src:linux] usercopy: Kernel memory exposure attempt
Marked as found in versions linux/4.19.160-2.

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

Bug#978753: usercopy: Kernel memory exposure attempt

[Andrei POPESCU]

Control: reassign -1 src:linux 4.19.160-2

On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote:
> Package: src:linux-image-4.19.0-13-amd64
> Version: 4.19.160-2
> Severity: critical
> Justification: breaks the whole system
> 
> 
> 
> -- Package-specific info:
> ** Kernel log: boot messages should be attached
> 
> 
> -- System Information:
> Debian Release: 10.7
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.4.86 (SMP w/4 CPU cores)
> Kernel taint flags: 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 /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages linux-image-4.19.0-13-amd64 depends on:
> ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
> ii  kmod26-1
> ii  linux-base  4.6
> 
> Versions of packages linux-image-4.19.0-13-amd64 recommends:
> ii  apparmor 2.13.2-10
> ii  firmware-linux-free  3.4
> 
> Versions of packages linux-image-4.19.0-13-amd64 suggests:
> pn  debian-kernel-handbook  
> ii  grub-pc 2.02+dfsg1-20+deb10u2
> pn  linux-doc-4.19  
> 
> Versions of packages linux-image-4.19.0-13-amd64 is related to:
> pn  firmware-amd-graphics 
> pn  firmware-atheros  
> pn  firmware-bnx2 
> pn  firmware-bnx2x
> pn  firmware-brcm80211
> pn  firmware-cavium   
> pn  firmware-intel-sound  
> pn  firmware-intelwimax   
> pn  firmware-ipw2x00  
> pn  firmware-ivtv 
> pn  firmware-iwlwifi  
> pn  firmware-libertas 
> pn  firmware-linux-nonfree
> pn  firmware-misc-nonfree 
> pn  firmware-myricom  
> pn  firmware-netxen   
> pn  firmware-qlogic   
> pn  firmware-realtek  
> pn  firmware-samsung  
> pn  firmware-siano
> pn  firmware-ti-connectivity  
> pn  xen-hypervisor
> 
> -- no debconf information
> 
> 
> Caused system halt with message:
> 
> usercopy: Kernel memory exposure attempt detected from SLUB object 
> 'mm_struct(770:pm2-root.service)' (offset 272, size 320)!

-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Bug#978749: requests: circular dependency makes requests unbuildable

[Sebastian Ramacher]

Hi Thomas

On 2020-12-31 13:06:37 +0100, Thomas Goirand wrote:
> Hi Sebastian,
> 
> I'm challenging the fact that a circular dependency is a problem for
> arch:all packages. At least, it shouldn't be an RC bug, IMO.

If packages cannot be built on the buildds, they are RC-buggy.

> 
> If the problem is bootstraping (which isn't a problem, since that's
> arch:all), then a wishlist bug against requests so that it implements
> the "nodoc" build profile is probably a better way to go.
> 
> Please downgrade the severity.

That would be wrong. See https://release.debian.org/bullseye/rc_policy.txt

> I also don't understand why you've renamed the original bug, which seems
> to be very different from the circular dependency you're describing. Can
> you explain why they are related, and why we shouldn't have 2 bugs?

The bug is that a build of requests is missing. The version that fixes
the uninstallability of python3-requests was already uploaded.

Cheers

> 
> Cheers,
> 
> Thomas Goirand (zigo)

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#978753: usercopy: Kernel memory exposure attempt

[Markus Bäcklund]

Hello,

It probably was src:linux because it was in the original bug report I 
submitted a couple of minutes earlier. I included everything reportbug 
wanted me to include in the report.


I don't know if I can run the reportbug anymore, since I am now 
upgrading from 10 to 11.



Kind regards,

Markus

On 31/12/2020 13.52, Andrei POPESCU wrote:

On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote:

Package: src:linux-image-4.19.0-13-amd64
Version: 4.19.160-2
Severity: critical
Justification: breaks the whole system
  
Hello,


What package did you specify to reportbug? I'm asking because
'src:linux-image-4.19.0-13-amd64' doesn't exist (it should be either
'linux-image-4.19.0-13-amd64' or 'src:linux').

Also the report seems to be missing some (but not all?) information
reportbug normally collects about the kernel.

Do you get a different output if you run

 reportbug linux-image-4.19.0-13-amd64

?

Kind regards,
Andrei

Bug#976891: update

[Hans-Christoph Steiner]

fastboot is getting pretty close to working on amd64:

https://salsa.debian.org/eighthave/android-platform-system-core/-/jobs/1297944

Bug#978749: requests: circular dependency makes requests unbuildable

[Thomas Goirand]

Hi Sebastian,

I'm challenging the fact that a circular dependency is a problem for
arch:all packages. At least, it shouldn't be an RC bug, IMO.

If the problem is bootstraping (which isn't a problem, since that's
arch:all), then a wishlist bug against requests so that it implements
the "nodoc" build profile is probably a better way to go.

Please downgrade the severity.

I also don't understand why you've renamed the original bug, which seems
to be very different from the circular dependency you're describing. Can
you explain why they are related, and why we shouldn't have 2 bugs?

Cheers,

Thomas Goirand (zigo)

Bug#978753: usercopy: Kernel memory exposure attempt

[Andrei POPESCU]

On Jo, 31 dec 20, 12:45:47, Markus Bäcklund wrote:
> Package: src:linux-image-4.19.0-13-amd64
> Version: 4.19.160-2
> Severity: critical
> Justification: breaks the whole system
 
Hello,

What package did you specify to reportbug? I'm asking because 
'src:linux-image-4.19.0-13-amd64' doesn't exist (it should be either 
'linux-image-4.19.0-13-amd64' or 'src:linux').

Also the report seems to be missing some (but not all?) information 
reportbug normally collects about the kernel.

Do you get a different output if you run

reportbug linux-image-4.19.0-13-amd64

?

Kind regards,
Andrei
-- 
Looking after bugs assigned to unknown or inexistent packages


signature.asc
Description: PGP signature

Processed: affects 978739

[Debian Bug Tracking System]

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

> affects 978739 src:bleachbit src:hdmf src:isbg src:kytos-utils 
> src:python-discogs-client
Bug #978739 [chardet] chardet: Upgrading python3-chardet breaks many packages
Added indication that 978739 affects src:bleachbit, src:hdmf, src:isbg, 
src:kytos-utils, and src:python-discogs-client
> thanks
Stopping processing here.

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

Processed: tagging 978274

[Debian Bug Tracking System]

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

> tags 978274 + pending
Bug #978274 [src:bepasty] bepasty: FTBFS: dpkg-buildpackage: error: dpkg-source 
-b . subprocess returned exit status 2
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#963497: not a bug for that version

[Russell Coker]

close 963497
thanks

Run "setsebool allow_execmem 1" before running certbot and it will be fine.  
After running certbot you can run "setsebool allow_execmem 0".  Or you could 
run "setsebool -P allow_execmem 1" to make the change continue to apply after 
a reboot.

The 2:2.20161023.1-9 policy doesn't have support for certbot so it's working 
as designed.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#963495: not a bug

[Russell Coker]

close 963495
thanks

Run "setsebool allow_execmem 1" before running certbot and it will be fine.  
After running certbot you can run "setsebool allow_execmem 0".  Or you could 
run "setsebool -P allow_execmem 1" to make the change continue to apply after 
a reboot.

There is no good solution to this as we don't want to allow execmem by 
default.  Also this only happens if you have openssl python libraries 
installed (typically dragged in by certbot dependencies).  If you don't have 
them installed then reportbug doesn't need execmem access.

This is annoying, but we just have some unpleasant choices.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#978753: usercopy: Kernel memory exposure attempt

[Markus Bäcklund]

Package: src:linux-image-4.19.0-13-amd64
Version: 4.19.160-2
Severity: critical
Justification: breaks the whole system



-- Package-specific info:
** Kernel log: boot messages should be attached


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

Kernel: Linux 5.4.86 (SMP w/4 CPU cores)
Kernel taint flags: 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-13-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod26-1
ii  linux-base  4.6

Versions of packages linux-image-4.19.0-13-amd64 recommends:
ii  apparmor 2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-4.19.0-13-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02+dfsg1-20+deb10u2
pn  linux-doc-4.19  

Versions of packages linux-image-4.19.0-13-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information


Caused system halt with message:

usercopy: Kernel memory exposure attempt detected from SLUB object 
'mm_struct(770:pm2-root.service)' (offset 272, size 320)!

Bug#978752: usercopy: Kernel memory exposure attempt

[Markus Bäcklund]

Package: src:linux
Version: 4.19.160-2
Severity: critical
Justification: breaks the whole system



-- Package-specific info:
** Kernel log: boot messages should be attached


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

Kernel: Linux 5.4.86 (SMP w/4 CPU cores)
Kernel taint flags: 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-13-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod26-1
ii  linux-base  4.6

Versions of packages linux-image-4.19.0-13-amd64 recommends:
ii  apparmor 2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-4.19.0-13-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02+dfsg1-20+deb10u2
pn  linux-doc-4.19  

Versions of packages linux-image-4.19.0-13-amd64 is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Bug#978640: undefined symbol: _ZTIN3fmt2v612format_errorE

[Utkarsh Gupta]

Hi Hubert,

On Thu, Dec 31, 2020 at 3:21 AM Hubert Chathi  wrote:
> binNMU requested at
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978722
>
> Apparently waiting for an update to spdlog.

Awesome, thanks for processing this!


- u

Bug#968413: marked as done (failes to build on ppc64el with binutils 2.35)

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 10:18:27 +
with message-id 
and subject line Bug#968413: fixed in oss4 4.2-build2017-2
has caused the Debian Bug report #968413,
regarding failes to build on ppc64el with binutils 2.35
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.)


-- 
968413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oss4
Version: 4.2-build2017-1
Severity: serious
Tags: patch

/tmp/ccGBTa5R.s: Assembler messages:
/tmp/ccGBTa5R.s: Error: invalid attempt to declare external version name as 
default in symbol
`.snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4'

oss4 started failing to build on ppc64el with binutils 2.35 because it
was setting an undefined symbol as the default version. It was doing that
in order to support dot-symbols/function descriptors on ppc, which is not
used by userspace ABI since a while, and not supported with ABIv2, the one
used by ppc64el, at all.

As this header comes from alsa, I looked at its history and, for different
reasons, it has been fixed there already. So, sending a patch based on that one
here to fix the build.

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

Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: oss4
Source-Version: 4.2-build2017-2
Done: Samuel Thibault 

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated oss4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 31 Dec 2020 11:00:14 +0100
Source: oss4
Binary: liboss4-salsa-asound2 liboss4-salsa2 liboss4-salsa2-dbgsym oss4-base 
oss4-dev oss4-dkms oss4-gtk oss4-source
Architecture: source
Version: 4.2-build2017-2
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 liboss4-salsa-asound2 - OSS to Alsa compatibility library - binary 
compatibility symlink
 liboss4-salsa2 - OSS to Alsa compatibility library
 oss4-base  - Open Sound System - base package
 oss4-dev   - Open Sound System - development files
 oss4-dkms  - Open Sound System - DKMS module sources
 oss4-gtk   - Open Sound System - simple GTK2-based mixer control
 oss4-source - Open Sound System - drivers sources
Closes: 968413
Changes:
 oss4 (4.2-build2017-2) unstable; urgency=medium
 .
   [ Samuel Thibault ]
   * control: Fix VCS URLs.
   * rules: Rely on pre-initialized dpkg-architecture variables.
   * control: Bump Standards-Version to 4.5.0 (no change).
   * control: Silent lintian warning about weak dependency version.
   * control: make oss4-base depend on lsb-base for sourcing
 /lib/lsb/init-functions.
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Remove maintainer from uploaders.
   * Bump debhelper from deprecated 9 to 10.
   * Use canonical URL in Vcs-Browser, Vcs-Git.
 .
   [ Thadeu Lima de Souza Cascardo ]
   * Fix build on ppc64el with binutils 2.35 (Closes: #968413).
Checksums-Sha1:
 072d5ee1651d9d7baef4fc57cce02f6e1731154c 2484 oss4_4.2-build2017-2.dsc
 04c7a1408b8ff0e84df02e88652a9a91811c2b78 68736 
oss4_4.2-build2017-2.debian.tar.xz
Checksums-Sha256:
 1dff1233ae262091fc12ae3cea535335a5cce3aa713b593d6fb9b645d234ad07 2484 
oss4_4.2-build2017-2.dsc
 d91c0f91645883f759946e91c14716657fb60bf9cc919583cae33e431c1d7493 68736 
oss4_4.2-build2017-2.debian.tar.xz
Files:
 25a8673abc06d45f9be7f614a30a3c86 2484 sound optional oss4_4.2-build2017-2.dsc
 34907d0990678d0925e5cd01b1f1930a 68736 sound optional 
oss4_4.2-build2017-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEaBSUQh8zBGvGomB+DvXG2q7gS7IFAl/totEACgkQDvXG

Processed: Re: Bug#978749: reportbug: Updating python3-chardet to 4.0.0 wants to remove reportbug

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:requests 2.25.1+dfsg-1
Bug #978749 [reportbug] reportbug: Updating python3-chardet to 4.0.0 wants to 
remove reportbug
Bug reassigned from package 'reportbug' to 'src:requests'.
No longer marked as found in versions reportbug/7.9.0.
Ignoring request to alter fixed versions of bug #978749 to the same values 
previously set
Bug #978749 [src:requests] reportbug: Updating python3-chardet to 4.0.0 wants 
to remove reportbug
The source 'requests' and version '2.25.1+dfsg-1' do not appear to match any 
binary packages
Marked as found in versions requests/2.25.1+dfsg-1.
> retitle -1 requests: circular dependency makes requests unbuildable
Bug #978749 [src:requests] reportbug: Updating python3-chardet to 4.0.0 wants 
to remove reportbug
Changed Bug title to 'requests: circular dependency makes requests unbuildable' 
from 'reportbug: Updating python3-chardet to 4.0.0 wants to remove reportbug'.
> severity -1 serious
Bug #978749 [src:requests] requests: circular dependency makes requests 
unbuildable
Severity set to 'serious' from 'normal'

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

Processed: found 978071 in 2.9-3, tagging 978071

[Debian Bug Tracking System]

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

> found 978071 2.9-3
Bug #978071 {Done: Thorsten Alteholz } [src:entropybroker] 
entropybroker FTBFS with Crypto++ 8.3.0
Marked as found in versions entropybroker/2.9-3.
> tags 978071 + sid bullseye
Bug #978071 {Done: Thorsten Alteholz } [src:entropybroker] 
entropybroker FTBFS with Crypto++ 8.3.0
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: affects 975747

[Debian Bug Tracking System]

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

> affects 975747 zipalign
Bug #975747 [android-libbacktrace] android-platform-build: FTBFS: ld: 
/usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined reference to 
`unwindstack::RemoteMaps::GetMapsFile[abi:cxx11]() const'
Added indication that 975747 affects zipalign
> thanks
Stopping processing here.

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

Bug#978518: marked as done (openjdk-14: non-standard gcc/g++ used for build (gcc-9))

[Debian Bug Tracking System]

Your message dated Thu, 31 Dec 2020 08:48:58 +
with message-id 
and subject line Bug#978518: fixed in openjdk-14 14.0.2+12-2
has caused the Debian Bug report #978518,
regarding openjdk-14: non-standard gcc/g++ used for build (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.)


-- 
978518: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-14
Severity: important
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: non-standard-compiler, gcc-9, gcc-9-legacy

This package builds with a non standard compiler version; please check
if this package can be built with the default version of gcc/g++, or
with gcc-10/g++-10.  If the package cannot be built with GCC 10 because
of a compiler bug, please file a report for gcc-10.

Please keep this report open until the package uses the default
compiler version (or gcc-10) for the package build.

If the package cannot be built anymore, please file a bug report for
ftp.debian.org, asking for the removal of the package.
--- End Message ---
--- Begin Message ---
Source: openjdk-14
Source-Version: 14.0.2+12-2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-14 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 31 Dec 2020 08:17:29 +0100
Source: openjdk-14
Architecture: source
Version: 14.0.2+12-2
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Closes: 978518
Changes:
 openjdk-14 (14.0.2+12-2) unstable; urgency=medium
 .
   * Backport GCC 10 fixes, build using GCC 10. Closes: #978518.
   * Apply the NMU, patching the correct control file.
   * Move VCS to salsa.debian.org.
   * Bump standards version.
Checksums-Sha1:
 966bb10e7c1d7f2904c6291aee491ec3b8960240 4715 openjdk-14_14.0.2+12-2.dsc
 5bf94459d00c5b6d0e6f421402f6bd0a7aa5e523 173040 
openjdk-14_14.0.2+12-2.debian.tar.xz
 8e95d96ff1dfa4ed5065ed88bf893fd6fb99eaa6 6554 
openjdk-14_14.0.2+12-2_source.buildinfo
Checksums-Sha256:
 12b584f55f0699269b2a8c706f6ec1ce91bd7ba36c624be6aeaf6b4deed6a732 4715 
openjdk-14_14.0.2+12-2.dsc
 50578f62b593934ac809e133a25ea6a653403c9a7da7f016fe926aa84de7f86c 173040 
openjdk-14_14.0.2+12-2.debian.tar.xz
 527df5a944729e202a4c8c28c3b544efcb14dfd4093106838c0d6e6659e86aec 6554 
openjdk-14_14.0.2+12-2_source.buildinfo
Files:
 42b9d6d61d3a8f6e0395439149bf57c6 4715 java optional openjdk-14_14.0.2+12-2.dsc
 242363a206a682345f739ff8bb3ad9d0 173040 java optional 
openjdk-14_14.0.2+12-2.debian.tar.xz
 46f11abcf6b1326e939dda78ab429ef1 6554 java optional 
openjdk-14_14.0.2+12-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl/tixQQHGRva29AdWJ1
bnR1LmNvbQAKCRC9fqpgd4+m9StQD/0T8jhv3iNPE60B5ukACon/cbnnU70M14ZQ
V20ra0ulk4W4aoa3fiTCS7Yc5ZGoMgwSgB5lutAphEth2/azVzOi4aPq6BdBauNt
xXnKK7iav5+eEJYzsZDbPZzLq/I+ObUd8YQBDpH1wVKCCrX1u0L6VWHuEst75DfF
XHhFmdGqhnJ+mgSr9Jc/7N/bZxYcSkFw7V9rZZifd7Gm69VHgyYnFFnx+lqkmd5B
bsJL3gp1J7JLf/iGVckMUvT+zkXakRdDQ1fj2C6cQ9bLNOfULwMXIBAA3PFyOXBB
yvt4iYhg01Lwc73Ik62VcHJ6acziE7O+sTiifG4wh/6KmOUUYDUoYKeMDzFG5Src
P5vIz8O6yo1q9dUZ0ghFYwOe1lgkK0nDIK8UThNdEIc3vcqw4icRKdYF/meiHdtL
UFvfvqWBfhAPmFAELIMWNXd2iJ/wSQzEidLai1AUy992fBGT7XEw+VUjUy9cUAkF
LczE593furdHagTIICXnL0SX95a7glBTR2b/+x3p7A1CNjubnj9mx1C5KD5Z3fV2
bwhmwHNPWJcLgYEP6P5wDABuGUAe6MNDzt6zMCIaViopwSGmvX96BMSh9lJejkHZ
fTbnA3Tz7OVT4phk3QKMpbMqQ1cCAXB8EOj2BjJQF9nlj3w3ll0HJdZP+mTPAseX
eoVfuTCxgw==
=0I2o
-END PGP SIGNATURE End Message ---

Processed: upstream only supports x86

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #963058 [src:android-platform-art] android-platform-art ftbfs on arm64
Severity set to 'wishlist' from 'serious'
> retitle -1 port android-platform-art to ARM, etc.
Bug #963058 [src:android-platform-art] android-platform-art ftbfs on arm64
Changed Bug title to 'port android-platform-art to ARM, etc.' from 
'android-platform-art ftbfs on arm64'.

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

Bug#963058: upstream only supports x86

[Hans-Christoph Steiner]

Control: severity -1 wishlist
Control: retitle -1 port android-platform-art to ARM, etc.

Bug#963058: [Android-tools-devel] Bug#963058: still ftbfs on arm64

[Hans-Christoph Steiner]

It looks like upstream does not support anything but x86, and they've 
added assembly code.  So unless someone steps up to port that to ARM, 
the ARM binaries will be removed.

Processed: still ftbfs on arm64

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #963058 {Done: Hans-Christoph Steiner } 
[src:android-platform-art] android-platform-art ftbfs on arm64
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions android-platform-art/10.0.0+r36-1~stage1.
> found -1 10.0.0+r36-1~stage1
Bug #963058 [src:android-platform-art] android-platform-art ftbfs on arm64
Marked as found in versions android-platform-art/10.0.0+r36-1~stage1.

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

Bug#975747: android/libbacktrace.so.0: undefined reference to `unwindstack::RemoteMaps::GetMapsFile[abi:cxx11]() const'

[Damyan Ivanov]

Package: android-libbacktrace
Version: 1:10.0.0+r36-1~stage1.3
Followup-For: Bug #975747

Control: affects -1 zipalign

This seems to render zipalign unusable:

 $ zipalign
 zipalign: symbol lookup error: 
 /usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol: 
 _ZN11unwindstack12ElfInterfaceD2Ev



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

Kernel: Linux 5.9.0-5-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages android-libbacktrace depends on:
ii  android-libbase1:10.0.0+r36-1~stage1.3
ii  android-libcutils  1:10.0.0+r36-1~stage1.3
ii  android-liblog 1:10.0.0+r36-1~stage1.3
ii  android-libunwind  10.0.0+r36-4
ii  libc6  2.31-6
ii  libgcc-s1  10.2.1-3
ii  liblzma5   5.2.4-1+b1
ii  libstdc++6 10.2.1-3

android-libbacktrace recommends no packages.

android-libbacktrace suggests no packages.

-- no debconf information

Bug#963058: still ftbfs on arm64

[Matthias Klose]

Control: reopen -1
Control: found -1 10.0.0+r36-1~stage1

still ftbfs everywhere on non-ix86