Processed: src:xfsdump: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.1.9
Bug #960078 [src:xfsdump] src:xfsdump: fails to migrate to testing for too long
Marked as fixed in versions xfsdump/3.1.9.
Bug #960078 [src:xfsdump] src:xfsdump: fails to migrate to testing for too long
Marked Bug as done
> block -1 by 953537
Bug #960078 {Done: Paul Gevers } [src:xfsdump] src:xfsdump: 
fails to migrate to testing for too long
960078 was not blocked by any bugs.
960078 was not blocking any bugs.
Added blocking bug(s) of 960078: 953537

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

Bug#960078: src:xfsdump: fails to migrate to testing for too long

[Paul Gevers]

Source: xfsdump
Version: 3.1.6+nmu2
Severity: serious
Control: close -1 3.1.9
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 953537

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:xfsdump in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=xfsdump




signature.asc
Description: OpenPGP digital signature

Bug#960077: src:gpgme1.0: fails to migrate to testing for too long

[Paul Gevers]

Source: gpgme1.0
Version: 1.13.1-6
Severity: serious
Control: close -1 1.13.1-7
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 953800

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:gpgme1.0 in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=gpgme1.0




signature.asc
Description: OpenPGP digital signature

Processed: src:gpgme1.0: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.13.1-7
Bug #960077 [src:gpgme1.0] src:gpgme1.0: fails to migrate to testing for too 
long
Marked as fixed in versions gpgme1.0/1.13.1-7.
Bug #960077 [src:gpgme1.0] src:gpgme1.0: fails to migrate to testing for too 
long
Marked Bug as done
> block -1 by 953800
Bug #960077 {Done: Paul Gevers } [src:gpgme1.0] 
src:gpgme1.0: fails to migrate to testing for too long
960077 was not blocked by any bugs.
960077 was not blocking any bugs.
Added blocking bug(s) of 960077: 953800

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

Bug#947720: sollya ftbfs with libfplll6

[Paul Gevers]

Hi,

On 09-05-2020 00:17, Sudip Mukherjee wrote:
> Hi Paul,
> 
> On Fri, May 8, 2020 at 9:36 PM Paul Gevers  wrote:
>>
>> Hi Sudip,
>>
>> On 08-05-2020 01:08, Sudip Mukherjee wrote:
>>> Can you please retest and confirm.
>>
>> I have given it back on arm64. Please ping me if that build succeeds.
>>
>> https://buildd.debian.org/status/package.php?p=sollya
> 
> Thanks. That build succeeded. And I have done the same for amd64 also
> which has also succeeded.

I have given back all other archs as well. Please feel free to close
this bug when the release architectures are all build.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#960073: Package:python-pyqt5 Run the example code with Trace and crash (SIGABRT)

[pengzongli]

Package:python-pyqt5
Version: 5.11.3+dfsg-1+b3_arm64
Severity: serious
Hi Experts,

Hope this email finds you well.
I am Peng Zongli, I'm sorry to bother you.
When ever I run the example code on the arm machine,It results in the 
error below:


/ Could not initialize GLX/
/Aborted (core dumped)/
but when I run the same example code on the x86 machine(Debian 8.3.0-6), 
there is no error.




Debian Release: (gcc version 9.2.1 20191102 (Debian 9.2.1-17))
Architecture: arm (64)
Kernel: Linux 4.19.34-2-arm64


python vesion 2.7.16
python-pyqt5-dbg (5.11.3+dfsg-1+b3)
python-pyqt5.qtwebengine-dbg (5.11.3+dfsg-1+b3)
Qt5 vesion 5.11.3
GLX version: 1.4
Sip vesion 4.19.14



the example code:

/from PyQt5.QtWidgets import QApplication/
/from PyQt5.QtCore import QT_VERSION_STR/
/from PyQt5.Qt import PYQT_VERSION_STR/
/from sip import SIP_VERSION_STR/
//
/if __name__=='__main__':/
/    import sys/
/app=QApplication(sys.argv) /
/    print("Qt5 Version Number is: {0}".format(QT_VERSION_STR))/
/    print("PyQt5 Version is: {}".format(PYQT_VERSION_STR))/
/    print("Sip Version is: {}".format(SIP_VERSION_STR)) /
//
/    sys.exit(app.exec_())/

it gives a Python traceback and crash:


/uos@uos-PC:~/Downloads$ gdb python/
/GNU gdb (Debian 8.2.1-2+b1) 8.2.1/
/Copyright (C) 2018 Free Software Foundation, Inc./
/License GPLv3+: GNU GPL version 3 or later 
//http://gnu.org/licenses/gpl.html> 
/

/This is free software: you are free to change and redistribute it./
/There is NO WARRANTY, to the extent permitted by law./
/Type "show copying" and "show warranty" for details./
/This GDB was configured as "aarch64-linux-gnu"./
/Type "show configuration" for configuration details./
/For bug reporting instructions, please see:/
///http://www.gnu.org/software/gdb/bugs/>. 
/

/Find the GDB manual and other documentation resources online at:/
/    //http://www.gnu.org/software/gdb/documentation/>. 
/



/For help, type "help"./
/Type "apropos word" to search for commands related to "word".../
/Reading symbols from python...Reading symbols from 
/usr/lib/debug/.build-id/d2/abd686c8e3ff7962791dfefbc4ef85235040d3.debug...done./

/done./
/(gdb) /
/(gdb) r testExample.py /
/Starting program: /usr/bin/python testExample.py/
/[Thread debugging using libthread_db enabled]/
/Using host libthread_db library 
"/lib/aarch64-linux-gnu/libthread_db.so.1"./

/[New Thread 0xe5d541e0 (LWP 4622)]/
/[New Thread 0xe515e1e0 (LWP 4623)]/
/Could not initialize GLX/


/Thread 1 "python" received signal SIGABRT, Aborted./
/__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50/
/50../sysdeps/unix/sysv/linux/raise.c: 没有那个文件或目录./
/(gdb) /
/(gdb) py-list /
/   4    #ifrom PyQt5.QtWebEngineWidgets import QWebEngineView/
/   5    #from sip import SIP_VERSION_STR/
/   6 /
/   7    if __name__=='__main__':/
/   8        import sys/
/  >9 app=QApplication(sys.argv) /
/  10 #print("Qt5 Version Number is: {0}".format(QT_VERSION_STR))/
/  11 #print("PyQt5 Version is: {}".format(PYQT_VERSION_STR))/
/  12 #print("Sip Version is: {}".format(SIP_VERSION_STR)) /
/  13        print ("hello")/
/  14 /
/(gdb) /
/(gdb) bt/
/#0 0xf7d32714 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:50/

/#1 0xf7d208e8 in __GI_abort () at abort.c:79/
/#2 0xf5beff2c in qt_message_fatal (context=..., 
message=...) at global/qlogging.cpp:1840/
/#3 0xf5beff2c in QMessageLogger::fatal(char const*, ...) const 
(this=this@entry=0xd2d8, msg=msg@entry=0xe5540d38 "Could not 
initialize GLX") at global/qlogging.cpp:880/
/#4 0xe553e4cc in QGLXContext::init(QXcbScreen*, 
QPlatformOpenGLContext*) (this=0xe0006070, screen=0x7c8210, 
share=)/
/    at 
../../../../../../include/QtCore/../../src/corelib/global/qlogging.h:91/
/#5 0xe553bb20 in 
QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const 
(this=, context=0xe00056c0) at 
qxcbglxintegration.cpp:186/
/#6 0xe5f870d0 in 
QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const 
(this=, context=0xe00056c0) at qxcbintegration.cpp:283/
/#7 0xf61cec08 in QOpenGLContext::create() (this=0xe00056c0) 
at 
../../include/QtGui/5.11.3/QtGui/private/../../../../../src/gui/kernel/qguiapplication_p.h:105/
/#8 0xef4e3af4 in QtWebEngineCore::initialize() () at 
/lib/aarch64-linux-gnu/libQt5WebEngineCore.so.5/
/#9 0xf5dd00f0 in qt_call_pre_routines () at 
../../include/QtCore/../../src/corelib/tools/qlist.h:540/
/#10 0xf5dd00f0 in QCoreApplicationPrivate::init() 
(this=this@entry=0x7cb3f0) at kernel/qcoreapplication.cpp:865/
/#11 0xf618b7e8 in QGuiApplicationPrivate::init() 
(this=this@entry=0x7cb3f0) at kernel/qguiapplication.cpp:1419/
/#12 0xf675d354 in QApplicationPrivate::init() 

Bug#952167: marked as done (astroidmail: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j1 test ARGS\+=-j1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sat, 09 May 2020 02:34:04 +
with message-id 
and subject line Bug#952167: fixed in astroidmail 0.15-3.1
has caused the Debian Bug report #952167,
regarding astroidmail: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
make -j1 test ARGS\+=-j1 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.)


-- 
952167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astroidmail
Version: 0.15-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 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 '/<>/obj-x86_64-linux-gnu'
> Running tests...
> /usr/bin/ctest --force-new-ctest-process -j1
> Test project /<>/obj-x86_64-linux-gnu
>   Start  1: generic
>  1/18 Test  #1: generic ..   Passed1.11 sec
>   Start  2: compose
>  2/18 Test  #2: compose ..***Failed1.30 sec
> Source dir: /<>
> Build dir:  /<>/obj-x86_64-linux-gnu
> Running: test_composed_message..
> /<>/obj-x86_64-linux-gnu 
> /<>/obj-x86_64-linux-gnu/tests
> [] [] [M] [info] cf: loading test config.
> [] [] [M] [debug] cf: using home and config_dir directory: 
> /<>/obj-x86_64-linux-gnu/tests/test_home
> [] [] [M] [info] cf: test config, loading defaults.
> [] [] [M] [info] date: init.
> [] [] [M] [info] db path: 
> /<>/obj-x86_64-linux-gnu/tests/mail/test_mail
> [] [] [M] [debug] searches: loading history..
> [] [] [M] [info] ac: initializing accounts..
> [] [] [M] [info] ac: setup account: charlie for Charlie Root (default: true)
> [] [] [M] [info] plugins: starting manager..
> [] [] [M] [warning] plugins: setting GI_TYPELIB_PATH: 
> /<>/obj-x86_64-linux-gnu
> [] [] [M] [debug] plugin: adding path: 
> /<>/obj-x86_64-linux-gnu/tests/test_home/plugins
> [] [] [M] [debug] plugins: refreshing..
> [] [] [M] [debug] plugins: found 2 plugins.
> [] [] [M] [debug] plugins: loading: basic plugin
> [] [] [M] [debug] plugins: loaded: basic plugin
> [] [] [M] [debug] plugins: registering astroid plugin..
> [] [] [M] [debug] plugins: loading: threadindexplugin
> [] [] [M] [debug] plugins: loaded: threadindexplugin
> [] [] [M] [debug] plugins: registering threadindex plugin..
> [] [] [M] [debug] plugins: activating astroid plugin: basic plugin
> [] [] [M] [info] global actions: set up.
> [] [] [M] [info] poll: setting up.
> [] [] [M] [debug] poll: interval: 0
> [] [] [M] [info] poll: periodic polling disabled.
> [] [] [M] [debug] cm: initialize..
> [] [] [M] [debug] cm: deinitialized.
> [] [] [M] [debug] actions: cleaning up remaining actions..
> [] [] [M] [info] cf: loading test config.
> [] [] [M] [debug] cf: using home and config_dir directory: 
> /<>/obj-x86_64-linux-gnu/tests/test_home
> [] [] [M] [info] cf: test config, loading defaults.
> [] [] [M] [info] date: init.
> [] [] [M] [info] db path: 
> /<>/obj-x86_64-linux-gnu/tests/mail/test_mail
> [] [] [M] [debug] searches: loading history..
> [] [] [M] [info] ac: initializing accounts..
> [] [] [M] [info] ac: setup account: charlie for Charlie Root (default: true)
> [] [] [M] [info] plugins: starting manager..
> [] [] [M] [error] plugins: GI_TYPELIB_PATH already set, not touching..
> [] [] [M] [debug] plugin: adding path: 
> /<>/obj-x86_64-linux-gnu/tests/test_home/plugins
> [] [] [M] [debug] plugins: refreshing..
> [] [] [M] [debug] plugins: found 2 plugins.
> [] [] [M] [debug] plugins: loading: basic plugin
> [] [] [M] [debug] plugins: loaded: basic plugin
> [] [] [M] [debug] plugins: registering astroid plugin..
> [] [] [M] [debug] plugins: loading: threadindexplugin
> [] [] [M] [debug] plugins: loaded: threadindexplugin
> [] [] [M] [debug] plugins: registering threadindex plugin..
> [] [] [M] [debug] plugins: activating astroid plugin: basic plugin
> [] [] [M] [info] global actions: set up.
> [] [] [M] [info] poll: setting up.
> [] [] [M] [debug] poll: interval: 0
> [] [] [M] [info] poll: periodic polling disabled.
> [] [] [M] [debug] cm: initialize..
> [] [] [M] [trace] cm: writing utf-8 text to message body: This is test: æøå.
>  > testing
> testing
> ...
> [] [] [M] [debug] cm: build..
> [] [] [M] [debug] cm: finalize..
> [] [] [M] [info] cm: wrote tmp file: /tmp/astroid-compose-lRzUwO
> [] [] [M] [debug] cm: deinitialized.
> [] [] [M] [info] msg: loading message from file: 
> [] [] [M] [debug] chunk (0): content-type: text/plain
> [] [] [M] [debug] chunk: preferred.
> [] [] 

Bug#938108: python-pyxenstore: Python2 removal in sid/bullseye

[Thomas Goirand]

On 5/8/20 9:35 PM, Moritz Mühlenhoff wrote:
> On Fri, Aug 30, 2019 at 07:45:40AM +, Matthias Klose wrote:
>> Package: src:python-pyxenstore
>> Version: 0.0.2-1
>> Severity: normal
>> Tags: sid bullseye
>> User: debian-pyt...@lists.debian.org
>> Usertags: py2removal
>>
>> Python2 becomes end-of-live upstream, and Debian aims to remove
>> Python2 from the distribution, as discussed in
>> https://lists.debian.org/debian-python/2019/07/msg00080.html
>>
>> Your package either build-depends, depends on Python2, or uses Python2
>> in the autopkg tests.  Please stop using Python2, and fix this issue
>> by one of the following actions.
> 
> Hi,
> python-pyxenstore is dead upstream and there are no reverse deps, let's 
> remove?
> 
> Cheers,
> Moritz

By all means, yes, remove this.
I believe it is in Debian when I attempted to package XCP (aka: xen-api,
aka xen-server, etc.), and that's long gone from Debian.

Thomas

Processed: found 938261 in 1.0.0+dfsg1-1, found 953615 in 1.0.9-1

[Debian Bug Tracking System]

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

> found 938261 1.0.0+dfsg1-1
Bug #938261 {Done: Sandro Tosi } [src:python-werkzeug] 
python-werkzeug: Python2 removal in sid/bullseye
Marked as found in versions python-werkzeug/1.0.0+dfsg1-1 and reopened.
> found 953615 1.0.9-1
Bug #953615 [borgbackup] borgbackup: index corruption / data loss
Marked as found in versions borgbackup/1.0.9-1.
> thanks
Stopping processing here.

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

Bug#959900: marked as done (keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 23:03:46 +
with message-id 
and subject line Bug#959900: fixed in keystone 2:17.0.0~rc2-1
has caused the Debian Bug report #959900,
regarding keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692
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.)


-- 
959900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: keystone
Version: 2:14.0.1-2
Severity: grave
Tags: patch security

kay reported a vulnerability in Keystone's EC2 credentials API. Keystone
is the identity service used by OpenStack for authentication (authN)
 and high-level authorization (authZ). Any user authenticated within a
limited scope (trust/oauth/application credential) can create an EC2
credential with an escalated permission, such as obtaining "admin" while
the user is on a limited "viewer" role.

The details and patches are available here:
https://bugs.launchpad.net/keystone/+bug/1872735
--- End Message ---
--- Begin Message ---
Source: keystone
Source-Version: 2:17.0.0~rc2-1
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated keystone package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 09 May 2020 00:14:15 +0200
Source: keystone
Architecture: source
Version: 2:17.0.0~rc2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 952795 959900
Changes:
 keystone (2:17.0.0~rc2-1) unstable; urgency=medium
 .
   * New upstream release.
 - Includes fixes for multiple CVE: CVE-2020-12689 CVE-2020-12690
   CVE-2020-12691 CVE-2020-12692 (Closes: #959900).
   * Uploading to unstable.
   * Update it.po debconf translation (Closes: #952795).
Checksums-Sha1:
 b08e584056ecfaaa5a0b27ac6104ad44bf9573d8 3578 keystone_17.0.0~rc2-1.dsc
 5eafbc4b57f9153bdbfdcf9146c9ed6268d02d4e 1037756 
keystone_17.0.0~rc2.orig.tar.xz
 d5a73cb5a41bbda9c10978f62b25aed5ac9e0458 38860 
keystone_17.0.0~rc2-1.debian.tar.xz
 fd2963f545dcdbe4f99166d79e9856daea73dfdb 16426 
keystone_17.0.0~rc2-1_amd64.buildinfo
Checksums-Sha256:
 f73330b2d7466edf12314310e54decdbc8e142a9c2e8138e9868729d455d9b5c 3578 
keystone_17.0.0~rc2-1.dsc
 a9d2b8ba2774af332ddafc2c299294d15c461089bf253d1a5ed37ad65ce188ba 1037756 
keystone_17.0.0~rc2.orig.tar.xz
 2a7b01672c5561f4bcbbb84a6a1522e7e617927e45a112663ea98006fbfba755 38860 
keystone_17.0.0~rc2-1.debian.tar.xz
 bf573b9de5870b49b17002789488c6f206c166220bc7ed9485c915490897523d 16426 
keystone_17.0.0~rc2-1_amd64.buildinfo
Files:
 f427f37f5cbd4184543acc9159717475 3578 net optional keystone_17.0.0~rc2-1.dsc
 27ec09253c2ae4ba7e7a7a6aee8060e4 1037756 net optional 
keystone_17.0.0~rc2.orig.tar.xz
 38c55d80637ef520fca640c6de7becc5 38860 net optional 
keystone_17.0.0~rc2-1.debian.tar.xz
 d914b09c553e53b311bac52282eff1f4 16426 net optional 
keystone_17.0.0~rc2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl614TkACgkQ1BatFaxr
Q/4vSw/9F2m5H2yr+9K+4aXGyHYDZbQ7yxxeb8xICC6P60Zvr6omXVnzEjzxlxuK
zj2ijvfqQPfxSSRN5izwmecaMZ6Xf1nlMpsx8wgSrTiHjybGJS3UJd+/s6oYLv2c
Pn90D1Tabb0eZHsN0m/DjxrKjZj5A5v7X3MKZisqOU9EDQEjwlBtBwKEj6UuHZS/
c5rh7/t8/YC/B5gcWDX8eK0v+p0+uuWsWQLgM55RtpB+jsyuHwUvH8N47RQtU8Ua
rDVpXfxfYIuqekWata96yQTLmZ7MCdzv04WGT+mHRTC0FOOGA8DxBf7va69YcWxI
3X7lzgClLXAKUOrDSkFKmNjgT7bwx+sdRTApjVLZpP9eEPxu3gcEVBBOdRSj8I4E
0GXBQjbACueb8LmIvMFsbjY/j6yPtxdF6WDiFeoR5KVqsTOvGVpf6gq6WVEhRZww
TI9Ov9uOTd9/ERvjCOYtVRAvxLg9i8Ungl0tpkS1+VO+c68KNf53jUbQu37TfSzR
o5RjDaIhnfsJOUlfNrPANPg/48R4SlmhzOdjFku6D5Pxca217mWlwQkV1vTGpNMY
tPFJ9bLra9Ot3PSbpTk/gxYQoLe26qV2nUx1PlBbpvf+szyGWzBlbUzbEAoO6DpR
aD0FiMR90J9hjc1UItr2Lha1/sRXxCs8y6UkrqYVoN2dNMLsWXg=
=O6BE
-END PGP SIGNATURE End Message ---

Processed: Bug#959900 marked as pending in keystone

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #959900 [src:keystone] keystone: CVE-2020-12689 CVE-2020-12690 
CVE-2020-12691 CVE-2020-12692
Ignoring request to alter tags of bug #959900 to the same tags previously set

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

Bug#959900: marked as pending in keystone

[Thomas Goirand]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/keystone/-/commit/d25246ef22950fdd4e81a978c2e7bc29b6686c95


Packaging 17.0.0_rc2 to unstable:
  * New upstream release.
- Includes fixes for multiple CVE: CVE-2020-12689 CVE-2020-12690
  CVE-2020-12691 CVE-2020-12692 (Closes: #959900).
  * Uploading to unstable.
  * Update it.po debconf translation (Closes: #952795).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/959900

Processed: tagging 945625, bug 945625 is forwarded to st...@electron9.net

[Debian Bug Tracking System]

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

> tags 945625 + upstream
Bug #945625 [src:cicero] cicero: Python2 removal in sid/bullseye
Added tag(s) upstream.
> forwarded 945625 st...@electron9.net
Bug #945625 [src:cicero] cicero: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to 'st...@electron9.net'.
> thanks
Stopping processing here.

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

Bug#947720: sollya ftbfs with libfplll6

[Sudip Mukherjee]

Hi Paul,

On Fri, May 8, 2020 at 9:36 PM Paul Gevers  wrote:
>
> Hi Sudip,
>
> On 08-05-2020 01:08, Sudip Mukherjee wrote:
> > Can you please retest and confirm.
>
> I have given it back on arm64. Please ping me if that build succeeds.
>
> https://buildd.debian.org/status/package.php?p=sollya

Thanks. That build succeeded. And I have done the same for amd64 also
which has also succeeded.


-- 
Regards
Sudip

Bug#945705: selenium-firefoxdriver: Python2 removal in sid/bullseye

[Scott Talbert]

On Fri, 29 Nov 2019, Sascha Girrulat wrote:


Source: selenium-firefoxdriver
Version: 3.14.1-1
Severity: normal
Tags: sid bullseye


Hi,

the firefoxdriver supports only firefox version up to 52.0 and does not
   work with the current version of firefox anymore. That's why the
removal is fine.

I'm sorry, i thought that the removal is already done but for some
reasons the package is still there.


Hi,

So you want to remove selenium-firefoxdriver package from Debian?

Regards,
Scott

Bug#959955: Packaging libsis-jhdf5-java -- help needed

[Andreas Tille]

Hi Pierre,

On Fri, May 08, 2020 at 10:24:47PM +0200, Pierre Gruet wrote:
> 
> Absolutely. This is part of the complementary tasks I was planning to do
> (my Salsa push of yesterday was only to fix the RC bug). h5ar was not in
> the previous packaging of libsis-jhdf5-java.

If you think you might be able to care for the h5ar binary issue in the
next couple of days I would delay the upload to fix the RC bug.  I guess
this will not have any practical drawback if the propagation of this
package to testing will be delayed some more days.
 
> I have seen that creating a man page should be easy, and while running
> h5ar as you did, I saw there was an issue with that version.txt file
> (easy to fix) and another one with the jar file, which is currently not
> built as it has not been part of the package libsis-jhdf5-java up to now.
> I will thus try to patch the gradle build script (or to edit d/rules) to
> build this new jar, and I need to learn a bit more about gradle to do
> so, which I am doing those days :-)

I can confirm that you can't prevent learning something when dealing
with Debian packages. ;-)

> Curiously, the jar is provided by upstream, there exists a task to build
> it in its gradle script, but it is not built by jh_build.

Sounds strange.

> Thanks for having looked at this!

You are welcome - the basic work was done by you.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#947720: sollya ftbfs with libfplll6

[Paul Gevers]

Hi Sudip,

On 08-05-2020 01:08, Sudip Mukherjee wrote:
> Can you please retest and confirm.

I have given it back on arm64. Please ping me if that build succeeds.

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

Paul



signature.asc
Description: OpenPGP digital signature

Bug#960057: src:upx-ucl: fails to migrate to testing for too long: autopkgtest failure

[Paul Gevers]

Source: upx-ucl
Version: 3.95-2
Severity: serious
Control: close -1 3.96-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:upx-ucl in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=upx-ucl




signature.asc
Description: OpenPGP digital signature

Processed: src:upx-ucl: fails to migrate to testing for too long: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.96-1
Bug #960057 [src:upx-ucl] src:upx-ucl: fails to migrate to testing for too 
long: autopkgtest failure
Marked as fixed in versions upx-ucl/3.96-1.
Bug #960057 [src:upx-ucl] src:upx-ucl: fails to migrate to testing for too 
long: autopkgtest failure
Marked Bug as done

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

Processed: src:tasksel: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.59
Bug #960056 [src:tasksel] src:tasksel: fails to migrate to testing for too long
Marked as fixed in versions tasksel/3.59.
Bug #960056 [src:tasksel] src:tasksel: fails to migrate to testing for too long
Marked Bug as done

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

Bug#960056: src:tasksel: fails to migrate to testing for too long

[Paul Gevers]

Source: tasksel
Version: 3.58
Severity: serious
Control: close -1 3.59
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s), kibi,

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:tasksel in
its current version in unstable has been trying to migrate for 60 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=tasksel




signature.asc
Description: OpenPGP digital signature

Processed: src:reactphp-socket: fails to migrate to testing for too long: arch:all uploaded

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.3.0-1
Bug #960054 [src:reactphp-socket] src:reactphp-socket: fails to migrate to 
testing for too long: arch:all uploaded
Marked as fixed in versions reactphp-socket/1.3.0-1.
Bug #960054 [src:reactphp-socket] src:reactphp-socket: fails to migrate to 
testing for too long: arch:all uploaded
Marked Bug as done

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

Processed: src:libqtdbustest: fails to migrate to testing for too long

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.2+bzr42+repack1-9
Bug #960053 [src:libqtdbustest] src:libqtdbustest: fails to migrate to testing 
for too long
Marked as fixed in versions libqtdbustest/0.2+bzr42+repack1-9.
Bug #960053 [src:libqtdbustest] src:libqtdbustest: fails to migrate to testing 
for too long
Marked Bug as done

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

Bug#960053: src:libqtdbustest: fails to migrate to testing for too long

[Paul Gevers]

Source: libqtdbustest
Version: 0.2+bzr42+repack1-5
Severity: serious
Control: close -1 0.2+bzr42+repack1-9
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:libqtdbustest
in its current version in unstable has been trying to migrate for 60
days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=libqtdbustest




signature.asc
Description: OpenPGP digital signature

Bug#960054: src:reactphp-socket: fails to migrate to testing for too long: arch:all uploaded

[Paul Gevers]

Source: reactphp-socket
Version: 1.1.0-1
Severity: serious
Control: close -1 1.3.0-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:reactphp-socket in its current version in unstable has been trying
to migrate for 60 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

Your package is only blocked because the arch:all binary package(s)
aren't built on a buildd. Unfortunately the Debian infrastructure
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will
shortly do a no-changes source-only upload to DELAYED/15, closing this
bug. Please let me know if I should delay or cancel that upload.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=reactphp-socket




signature.asc
Description: OpenPGP digital signature

Bug#889748: marked as done (diagnostics FTBFS: FAIL: stacktrace)

[Debian Bug Tracking System]

Your message dated Fri, 8 May 2020 22:35:26 +0300
with message-id <20200508193526.GA8672@localhost>
and subject line Re: diagnostics FTBFS: FAIL: stacktrace
has caused the Debian Bug report #889748,
regarding diagnostics FTBFS: FAIL: stacktrace
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.)


-- 
889748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diagnostics
Version: 0.3.3-12
Severity: serious

Some recent change in unstable makes diagnostics FTBFS:

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

...
/usr/bin/make  check-TESTS
make[11]: Entering directory 
'/build/1st/diagnostics-0.3.3/diagnostics/extensions/stacktrace'
make[12]: Entering directory 
'/build/1st/diagnostics-0.3.3/diagnostics/extensions/stacktrace'
FAIL: stacktrace

Testsuite summary for diagnostics 0.3.3

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See diagnostics/extensions/stacktrace/test-suite.log
Please report to christ...@schallhart.net

Makefile:904: recipe for target 'test-suite.log' failed
make[12]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
On Thu, May 07, 2020 at 09:29:47PM +0100, Sudip Mukherjee wrote:
> Hi,
> 
> I tried to build it and did not get any failure.
>...
> Can you please retest this and confirm..

Confirmed, it seems something fixed it:
https://tests.reproducible-builds.org/debian/history/diagnostics.html

> Regards
> Sudip

cu
Adrian--- End Message ---

Bug#938108: python-pyxenstore: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:45:40AM +, Matthias Klose wrote:
> Package: src:python-pyxenstore
> Version: 0.0.2-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests.  Please stop using Python2, and fix this issue
> by one of the following actions.

Hi,
python-pyxenstore is dead upstream and there are no reverse deps, let's remove?

Cheers,
Moritz

Bug#936206: binplist: Python2 removal in sid/bullseye

[Moritz Mühlenhoff]

On Fri, Aug 30, 2019 at 07:11:38AM +, Matthias Klose wrote:
> Package: src:binplist
> Version: 0.1.5-2
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
> 
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the distribution, as discussed in
> https://lists.debian.org/debian-python/2019/07/msg00080.html
> 
> Your package either build-depends, depends on Python2, or uses Python2
> in the autopkg tests.  Please stop using Python2, and fix this issue
> by one of the following actions.

https://github.com/google/binplist/issues/6 is without any update since 2016 
and there
are no reverse deps, let's remove?

Cheers,
Moritz

Bug#938092: marked as done (python-pysam: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 19:04:59 +
with message-id 
and subject line Bug#938092: fixed in python-pysam 0.15.4+ds-3
has caused the Debian Bug report #938092,
regarding python-pysam: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
938092: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938092
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pysam
Version: 0.15.2+ds-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-pysam

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: python-pysam
Source-Version: 0.15.4+ds-3
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-pysam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 20:27:35 +0200
Source: python-pysam
Architecture: source
Version: 0.15.4+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 938092
Changes:
 python-pysam (0.15.4+ds-3) unstable; urgency=medium
 .
   * Remove Python2 package
 Closes: #938092
   * Remove unneeded debian/gbp.conf
   * Standards-Version: 4.5.0 (routine-update)
   * Add salsa-ci file (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * Set upstream metadata fields: Bug-Submit.
Checksums-Sha1:
 cdb6ed05bf278492b76713fe1338c11496987e90 2425 python-pysam_0.15.4+ds-3.dsc
 6bcd9900b37e200d13a85fd8bf86dca2cd860b58 373652 
python-pysam_0.15.4+ds-3.debian.tar.xz
 8b20cfe5646ec5a4ad85cbf5b900ce769d1c76f2 8242 
python-pysam_0.15.4+ds-3_amd64.buildinfo
Checksums-Sha256:
 dc1a620f37d1202f5ba2cecbbf4ebf14d15ac5bc2eaf1624a1a029207d52c17f 2425 

Bug#954645: marked as done (behave: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 19:03:41 +
with message-id 
and subject line Bug#954645: fixed in behave 1.2.6-2
has caused the Debian Bug report #954645,
regarding behave: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i 
python{version} -p "3.7 3.8" returned exit code 13
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.)


-- 
954645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: behave
Version: 1.2.6-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200321 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_auto_build -i
> I: pybuild base:217: /usr/bin/python3.7 setup.py build 
> running build
> running build_py
> copying setuptools_behave.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build
> creating /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/step_registry.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/configuration.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/tag_expression.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/parser.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/__main__.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/model_describe.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/i18n.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/tag_matcher.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/matchers.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/json_parser.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/textutil.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/log_capture.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/_types.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/fixture.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/userdata.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/model_core.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/runner_util.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/runner.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/importer.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/model.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/capture.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> copying behave/_stepimport.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave
> creating /<>/.pybuild/cpython3_3.7_behave/build/behave/reporter
> copying behave/reporter/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/reporter
> copying behave/reporter/junit.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/reporter
> copying behave/reporter/summary.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/reporter
> copying behave/reporter/base.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/reporter
> creating /<>/.pybuild/cpython3_3.7_behave/build/behave/api
> copying behave/api/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/api
> copying behave/api/async_step.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/api
> creating /<>/.pybuild/cpython3_3.7_behave/build/behave/contrib
> copying behave/contrib/formatter_missing_steps.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/contrib
> copying behave/contrib/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/contrib
> copying behave/contrib/scenario_autoretry.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/contrib
> copying behave/contrib/substep_dirs.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/contrib
> creating /<>/.pybuild/cpython3_3.7_behave/build/behave/formatter
> copying behave/formatter/_builtins.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/formatter
> copying behave/formatter/progress.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/formatter
> copying behave/formatter/plain.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/formatter
> copying behave/formatter/__init__.py -> 
> /<>/.pybuild/cpython3_3.7_behave/build/behave/formatter
> copying behave/formatter/json.py -> 
> 

Bug#954645: marked as pending in behave

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #954645 in behave 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/python-team/modules/behave/-/commit/674c8ea1328bfc84754d85fc156c2870e53af654


Merge branch 'master' into 'master'

Add python3-path and python3-pytest to Build-Depends, Closes: #954645.

See merge request python-team/modules/behave!2


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954645

Processed: Bug#954645 marked as pending in behave

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954645 [src:behave] behave: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.7 3.8" returned exit code 13
Added tag(s) pending.

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

Processed: Bug#954645 marked as pending in behave

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #954645 [src:behave] behave: FTBFS: dh_auto_test: error: pybuild --test 
--test-nose -i python{version} -p "3.7 3.8" returned exit code 13
Ignoring request to alter tags of bug #954645 to the same tags previously set

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

Bug#954645: marked as pending in behave

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #954645 in behave 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/python-team/modules/behave/-/commit/15bb8b78186e713871d6cc8e7dc3b99e9201b205


* d/control: Added python3-path and python3-pytest to Build-Depends, thanks
to Sebastiaan Couwenberg. Closes: #954645.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/954645

Bug#955403: Set severity to important (Was: bedtools ftbfs, failing tests on armel, armhf, i386, mipsel)

[Andreas Tille]

Control: severity -1 important

The builds for the failed architectures are requested for removal.  So
the bug is set to severity important to move on with architectures that
are used in practical applications without creating noise in form of
lots of testing removal warnings of rdepends.

Kind regards
Andreas.

-- 
http://fam-tille.de

Processed: Set severity to important (Was: bedtools ftbfs, failing tests on armel, armhf, i386, mipsel)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #955403 [src:bedtools] bedtools ftbfs, failing tests on armel, armhf, i386, 
mipsel
Severity set to 'important' from 'serious'

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

Processed: severity of 959885 is serious, tagging 959885

[Debian Bug Tracking System]

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

> severity 959885 serious
Bug #959885 [inkscape] inkscape: crashes when called without X server
Severity set to 'serious' from 'important'
> tags 959885 + upstream
Bug #959885 [inkscape] inkscape: crashes when called without X server
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#959994: codeville: Consider removing this package

[Michael Janssen (Debian)]

Hello.

I agree with this assessment.  If you can submit it immediately, that would
be fine with me.

Marie Janssen --- Jamuraa --- jamu...@base0.net --- jamu...@debian.org

On Thu, May 7, 2020 at 8:48 PM Boyuan Yang  wrote:

> Source: codeville
> Severity: serious
> Version: 0.8.0-2.1
> Tags: sid  bullseye
> X-Debbugs-CC: jamu...@debian.org
>
> Dear Debian codeville maintainer,
>
> It seems that package codevilla has a dead upstream since at least 2014.
> It is
> a discontinued VCS thus it doesn't make any sense to keep it in Debian
> archive. Besides, this software is now affected by python2 removal.
>
> As a result, I am proposing to have this package removed from Debian. I
> will
> submit a removal request to FTP Masters 7 days later (after May 14, 2020).
> If
> you have any thoughts, please let me know *immediately*.
>
> --
> Best Regards,
> Boyuan Yang
>

Processed: severity of 954999 is important

[Debian Bug Tracking System]

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

> severity 954999 important
Bug #954999 [eclipse-titan] eclipse-titan still encodes an upper dependency on 
gcc
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#959390: marked as done (adwaita-icon-theme breaks gtk+3.0 autopkgtest: gtk+/icontheme.test (Child process killed by signal 5))

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 16:03:46 +
with message-id 
and subject line Bug#959390: fixed in gtk+3.0 3.24.20-1
has caused the Debian Bug report #959390,
regarding adwaita-icon-theme breaks gtk+3.0 autopkgtest: gtk+/icontheme.test 
(Child process killed by signal 5)
to be marked as done.

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

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


-- 
959390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: adwaita-icon-theme, gtk+3.0
Control: found -1 adwaita-icon-theme/3.36.1-1
Control: found -1 gtk+3.0/3.24.18-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of adwaita-icon-theme the autopkgtest of gtk+3.0
fails in testing when that autopkgtest is run with the binary packages
of adwaita-icon-theme from unstable. It passes when run with only
packages from testing. In tabular form:

   passfail
adwaita-icon-theme from testing3.36.1-1
gtk+3.0from testing3.24.18-1
all others from testingfrom testing

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

Currently this regression is blocking the migration of
adwaita-icon-theme to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package?

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

Paul

[1] https://qa.debian.org/excuses.php?package=adwaita-icon-theme

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gtk+3.0/5236284/log.gz

# Running test: gtk+/icontheme.test
# FAIL: gtk+/icontheme.test (Child process killed by signal 5)
not ok - gtk+/icontheme.test



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gtk+3.0
Source-Version: 3.24.20-1
Done: Sebastien Bacher 

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

Debian distribution maintenance software
pp.
Sebastien Bacher  (supplier of updated gtk+3.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 16:32:53 +0200
Source: gtk+3.0
Binary: libgtk-3-0 libgtk-3-0-udeb libgtk-3-common libgtk-3-bin libgtk-3-dev 
libgtk-3-doc gtk-3-examples gir1.2-gtk-3.0 gtk-update-icon-cache libgail-3-0 
libgail-3-dev libgail-3-doc
Architecture: source
Version: 3.24.20-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Sebastien Bacher 
Description:
 gir1.2-gtk-3.0 - GTK graphical user interface library -- gir bindings
 gtk-3-examples - example files for GTK 3
 gtk-update-icon-cache - icon theme caching utility
 libgail-3-0 - GNOME Accessibility Implementation Library -- shared libraries
 libgail-3-dev - GNOME Accessibility Implementation Library -- development files
 libgail-3-doc - documentation files of the Gail library
 libgtk-3-0 - GTK graphical user interface library
 libgtk-3-0-udeb - GTK graphical user interface library - minimal runtime (udeb)
 libgtk-3-bin - programs for the GTK graphical user interface library
 libgtk-3-common - common files for the GTK graphical user interface library
 libgtk-3-dev - development files for the GTK library
 libgtk-3-doc - documentation for the GTK graphical user interface library
Closes: 959390
Changes:
 gtk+3.0 (3.24.20-1) unstable; urgency=medium
 .
   * Upload to unstable
 .
   [ Simon McVittie ]
   * New upstream release
   * Depend on librsvg2-common for tests.
 The unit tests expect that gdk-pixbuf can load SVG files. This is
 provided by librsvg2-common, which used to be pulled in by
 adwaita-icon-theme. (Closes: #959390)
Checksums-Sha1:
 b192b08bc3e6f88102563f3702476469e4d2b792 3931 gtk+3.0_3.24.20-1.dsc
 56b853392d4198326dfc6b6104edccb757b8e94b 22726768 gtk+3.0_3.24.20.orig.tar.xz
 

Bug#960041: python-tornado4: Pending removal

[Gordon Ball]

Source: python-tornado4
Severity: serious
Justification: Policy 7.2

This package is an old fork of the tornado binary package, which appears
to have been created for src:salt.

There are no longer any rdepends (salt ceased to depend upon it after
3000+dfsg1-1), so unless there are objections this package will be
dropped.

Bug#955319: marked as done (libtoxcore: autopkgtest regression: Test #2: bootstrap ........................***Timeout 120.00 sec)

[Debian Bug Tracking System]

Your message dated Fri, 8 May 2020 23:39:14 +0800
with message-id 

and subject line 
has caused the Debian Bug report #955319,
regarding libtoxcore: autopkgtest regression: Test #2: bootstrap 
***Timeout 120.00 sec
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.)


-- 
955319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955319
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtoxcore
Version: 0.2.9-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Since 2019-10 the autopkgtest of libtoxcore is failing on all releases.
I copied some of the output at the bottom of this report.

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

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libtoxcore/4730969/log.gz

Running tests...
Test project /tmp/autopkgtest-lxc.ikepvlvi/downtmp/build.FcP/src/cmake-build
  Start  1: TCP
 1/42 Test  #1: TCP ..   Passed   16.25 sec
  Start  2: bootstrap
 2/42 Test  #2: bootstrap ***Timeout 120.00 sec
  Start  3: conference
 3/42 Test  #3: conference ...   Passed   18.22 sec
  Start  4: conference_double_invite
 4/42 Test  #4: conference_double_invite .   Passed1.18 sec
  Start  5: conference_peer_nick
 5/42 Test  #5: conference_peer_nick .   Passed1.84 sec
  Start  6: conference_simple
 6/42 Test  #6: conference_simple    Passed   10.10 sec
  Start  7: conference_two
 7/42 Test  #7: conference_two ...   Passed0.00 sec
  Start  8: crypto
 8/42 Test  #8: crypto ...   Passed0.77 sec
  Start  9: dht
 9/42 Test  #9: dht ..   Passed8.51 sec
  Start 10: encryptsave
10/42 Test #10: encryptsave ..   Passed2.26 sec
  Start 11: file_transfer
11/42 Test #11: file_transfer    Passed   26.45 sec
  Start 12: file_saving
12/42 Test #12: file_saving ..   Passed0.14 sec
  Start 13: friend_connection
13/42 Test #13: friend_connection    Passed1.13 sec
  Start 14: friend_request
14/42 Test #14: friend_request ...   Passed   11.65 sec
  Start 15: invalid_tcp_proxy
15/42 Test #15: invalid_tcp_proxy    Passed   30.05 sec
  Start 16: invalid_udp_proxy
16/42 Test #16: invalid_udp_proxy    Passed   30.03 sec
  Start 17: lan_discovery
17/42 Test #17: lan_discovery    Passed   10.02 sec
  Start 18: lossless_packet
18/42 Test #18: lossless_packet ..   Passed1.16 sec
  Start 19: lossy_packet
19/42 Test #19: lossy_packet .   Passed1.14 sec
  Start 20: messenger
20/42 Test #20: messenger    Passed0.00 sec
  Start 21: network
21/42 Test #21: network ..   Passed0.00 sec
  Start 22: onion
22/42 Test #22: onion    Passed   11.62 sec
  Start 23: overflow_recvq
23/42 Test #23: overflow_recvq ...   Passed6.59 sec
  Start 24: overflow_sendq
24/42 Test #24: overflow_sendq ...   Passed1.28 sec
  Start 25: reconnect
25/42 Test #25: reconnect    Passed7.18 sec
  Start 26: save_friend
26/42 Test #26: save_friend ..   Passed   10.12 sec
  Start 27: save_load
27/42 Test #27: save_load    Passed   23.66 sec
  Start 28: send_message
28/42 Test #28: send_message .   Passed1.09 sec
  Start 29: set_name
29/42 Test #29: set_name .   Passed   11.25 sec
  Start 30: set_status_message
30/42 Test #30: set_status_message ...   Passed   11.45 sec
  Start 31: skeleton
31/42 Test #31: skeleton .   Passed0.00 sec
  Start 32: tcp_relay
32/42 Test #32: tcp_relay ***Timeout 120.00 sec
  Start 33: tox_many
33/42 Test #33: tox_many .   Passed   13.60 sec
  Start 34: tox_many_tcp
34/42 Test #34: tox_many_tcp .   Passed   12.52 sec
  Start 35: tox_one
35/42 Test #35: tox_one ..   Passed0.01 sec
  

Processed: Bug#959390 marked as pending in gtk+3.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #959390 [src:adwaita-icon-theme, src:gtk+3.0] adwaita-icon-theme breaks 
gtk+3.0 autopkgtest: gtk+/icontheme.test (Child process killed by signal 5)
Ignoring request to alter tags of bug #959390 to the same tags previously set

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

Bug#959390: marked as pending in gtk+3.0

[Sebastien Bacher]

Control: tag -1 pending

Hello,

Bug #959390 in gtk+3.0 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/gtk3/-/commit/cc3d2e7851cea7dbeb7d92a6cd8402415cf0e98c


Depend on librsvg2-common for tests

The unit tests expect that gdk-pixbuf can load SVG files. This is
provided by librsvg2-common, which used to be pulled in by
adwaita-icon-theme.

Closes: #959390


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/959390

Bug#944020: Help with this for TAILS

[debianbugs]

Hello-

I'm doing some work with the Tails team working to get Trezor python-trezor and 
python-libusb1 back-ported to Buster. These packages can then be put into 
testing for Tails to use. Currently this all hinges on getting debian bug 
944020 > fixed, as per the 
discussion over with the Tails team: 
https://redmine.tails.boum.org/code/issues/17461#change-116459 
 
> . 

I am inquiring to see if there is anything I can do to help expedite 944020 and 
get the process moving along.

Regards

Bug#959981: Trademark concerns with Chef/Cinc package included in Debian and Ubuntu

[Antonio Terceiro]

Hello,

This is my attemp at a more detailed response after sleeping on it.

On Thu, May 07, 2020 at 11:40:38AM -0700, Lance Albertson wrote:
> All,
> 
> I'm a member of the Cinc Project [1] which rebuilds and rebrands various
> Chef projects to comply with Chef Trademark Policy [2]. We have worked
> closely with Chef to ensure Cinc Client complies with this policy.
> 
> A member of our community notified us today that it appears that Ubuntu [3]
> and Debian [4] are both including a package called "chef" which seems to
> pull in the Cinc source code but doesn't fully comply with the Chef
> Trademark Policy. We are concerned that this use of the Cinc Client in the
> manner it's currently presented will create an issue for us and you in the
> future unless this gets resolved quickly.
> 
> Specifically, we are concerned with the following:
> 
> 1. The package name should be cinc and not chef as Chef is trademarked and
> also causes users to think they are installing Chef when they are
> installing Cinc

Well other packages depend on chef packages by name, so renaming the
package might be tricky.

> 2. The package should have proper attributions to include the Cinc Project
> including pointing any issues related to the package to our issue page, and
> not Chef2
> 2. Running "chef-client" (or other similar commands) does not tell the user
> that it's actually using Cinc Client as our package does properly

Fair enough.

> 3. All of the trademark renaming we did in our Cinc Client distribution
> seems to have been removed and

Yes, I got the source from the git repository directly and missed the
"patching" process you do to make releases. Not making source releases
makes downstream work harder than it should be.

> retains all of the Chef related paths (i.e.  /etc/chef when it should
> be /etc/cinc). This will cause confusion for users who are expecting
> Cinc.

For fresh installs that should not be a problem.

How do you suggest to handle upgrades? If a user of Debian 10 (released
before this new Trademark Policy) upgrades, should /etc/chef be renamed
to /etc/cinc? Or will cinc still use that for backwards compatibility?

Is there any other path change.

> We would like to work with the Debian/Ubuntu maintainers to ensure you're
> following compliance and also ensuring our distribution works well on
> Debian/Ubuntu. However we also want to ensure you don't get into any legal
> trouble with Chef. I am sure most of these changes weren't done
> intentionally and was a mistake.
> 
> Feel free to reach out to us via the #community-distros channel on the Chef
> Community Slack, or you can reach me directly via IRC on Freenode as
> "Ramereth".  I've also cc'd Benny Vasquez who is a community manager at
> Chef who can answer any questions relating to this and provide any
> additional feedback.

Can you please provide a source release that has everything that is
needed? In particular, it would be useful to:

- make cinc-wrapper part of cinc itself instead of an implementation
  detail in the cinc-project/distribution/client repository

- publish a source release containing that alongside the binary packages
  you upload to http://downloads.cinc.sh/files/

I just sent a merge request that should do the later:
https://gitlab.com/cinc-project/distribution/client/-/merge_requests/37


signature.asc
Description: PGP signature

Bug#951969: marked as done (social-auth-app-django: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" --system=custom "--test-args={interpreter} ./manage.py test" returned exi

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 14:36:42 +
with message-id 
and subject line Bug#951969: fixed in social-auth-app-django 3.1.0-2.1
has caused the Debian Bug report #951969,
regarding social-auth-app-django: FTBFS: dh_auto_test: error: pybuild --test -i 
python{version} -p "3.8 3.7" --system=custom "--test-args={interpreter} 
./manage.py test" returned exit code 13
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.)


-- 
951969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: social-auth-app-django
Version: 3.1.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20200222 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="{interpreter} ./manage.py test"
> I: pybuild base:217: python3.8 ./manage.py test
> Creating test database for alias 'default'...
> ..E
> ==
> ERROR: test_html (tests.test_strategy.TestStrategy)
> --
> Traceback (most recent call last):
>   File "/<>/tests/test_strategy.py", line 73, in test_html
> result = self.strategy.render_html(html='xoxo')
>   File "/<>/social_django/strategy.py", line 98, in render_html
> template = loader.get_template(tpl)
>   File "/usr/lib/python3/dist-packages/django/template/loader.py", line 15, 
> in get_template
> return engine.get_template(template_name)
>   File "/usr/lib/python3/dist-packages/django/template/backends/django.py", 
> line 34, in get_template
> return Template(self.engine.get_template(template_name), self)
>   File "/usr/lib/python3/dist-packages/django/template/engine.py", line 143, 
> in get_template
> template, origin = self.find_template(template_name)
>   File "/usr/lib/python3/dist-packages/django/template/engine.py", line 125, 
> in find_template
> template = loader.get_template(name, skip=skip)
>   File "/usr/lib/python3/dist-packages/django/template/loaders/cached.py", 
> line 54, in get_template
> template = super().get_template(template_name, skip)
>   File "/usr/lib/python3/dist-packages/django/template/loaders/base.py", line 
> 18, in get_template
> for origin in self.get_template_sources(template_name):
>   File "/usr/lib/python3/dist-packages/django/template/loaders/cached.py", 
> line 65, in get_template_sources
> yield from loader.get_template_sources(template_name)
>   File 
> "/usr/lib/python3/dist-packages/django/template/loaders/filesystem.py", line 
> 36, in get_template_sources
> name = safe_join(template_dir, template_name)
>   File "/usr/lib/python3/dist-packages/django/utils/_os.py", line 32, in 
> safe_join
> final_path = abspath(join(base, *paths))
>   File "/usr/lib/python3.8/posixpath.py", line 90, in join
> genericpath._check_arg_types('join', a, *p)
>   File "/usr/lib/python3.8/genericpath.py", line 152, in _check_arg_types
> raise TypeError(f'{funcname}() argument must be str, bytes, or '
> TypeError: join() argument must be str, bytes, or os.PathLike object, not 
> 'NoneType'
> 
> --
> Ran 55 tests in 0.642s
> 
> FAILED (errors=1)
> Destroying test database for alias 'default'...
> System check identified no issues (0 silenced).
> E: pybuild pybuild:341: test: plugin custom failed with: exit code=1: 
> python3.8 ./manage.py test
> dh_auto_test: error: pybuild --test -i python{version} -p "3.8 3.7" 
> --system=custom "--test-args={interpreter} ./manage.py test" returned exit 
> code 13

The full build log is available from:
   
http://qa-logs.debian.net/2020/02/22/social-auth-app-django_3.1.0-2_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: social-auth-app-django
Source-Version: 3.1.0-2.1
Done: Adrian Bunk 

We believe that the bug you reported is fixed in the latest version of
social-auth-app-django, which is due to be installed in the Debian FTP archive.

A summary of 

Bug#959402: marked as done (yaml-cpp: FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 14:36:48 +
with message-id 
and subject line Bug#959402: fixed in yaml-cpp 0.6.3-2
has caused the Debian Bug report #959402,
regarding yaml-cpp: FTBFS on mipsel
to be marked as done.

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

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


-- 
959402: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yaml-cpp
Version: 0.6.3-1
Severity: grave
Justification: FTBFS

Dear Debian yaml-cpp maintainer,

Unfortunately yaml-cpp currently FTBFS on mipsel architecture. Build logs
indicate that it might be caused by the exhaustion of memory:

as: out of memory allocating 7161456 bytes after a total of 573444096 bytes
/tmp/cc7NTJLR.s: Assembler messages:
/tmp/cc7NTJLR.s: Fatal error: can't close CMakeFiles/run-
tests.dir/integration/gen_emitter_test.cpp.o: memory exhausted
make[4]: *** [test/CMakeFiles/run-tests.dir/build.make:102:
test/CMakeFiles/run-tests.dir/integration/gen_emitter_test.cpp.o] Error 1


I'm not sure what's the best way of solving this issue. Maybe we need some
test-builds on porterbox?

-- 
Best,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: yaml-cpp
Source-Version: 0.6.3-2
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated yaml-cpp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 15:42:46 +0200
Source: yaml-cpp
Binary: libyaml-cpp0.6 libyaml-cpp-dev
Architecture: source
Version: 0.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Simon Quigley 
Changed-By: Gianfranco Costamagna 
Description:
 libyaml-cpp-dev - YAML parser and emitter for C++ - development files
 libyaml-cpp0.6 - YAML parser and emitter for C++
Closes: 959402
Changes:
 yaml-cpp (0.6.3-2) unstable; urgency=medium
 .
   * Team upload (salsa.d.o namespace)
   * Fix mipsel build by lowering to parallel=2 there (Closes: #959402)
Checksums-Sha1:
 c3538e62fd6fcfb8654ed7769e9fecb30f8bb6dc 1913 yaml-cpp_0.6.3-2.dsc
 d6adc486861456b909c1e5299bc1c8fb43de0412 10544 yaml-cpp_0.6.3-2.debian.tar.xz
 694a746d670083bb80c2832be14d0b4d30aa31a5 8662 yaml-cpp_0.6.3-2_source.buildinfo
Checksums-Sha256:
 d324a26ab7fdee8d46ebba524c6757655622b3064f9fe7aaf7e00d21c4731c72 1913 
yaml-cpp_0.6.3-2.dsc
 092afb566e80ffaaccedbc73ee1439e1ddf1820ec940746f79121a468aa8c9e5 10544 
yaml-cpp_0.6.3-2.debian.tar.xz
 50596a3c8ba447fb075e9f666f99bb5d9fe7e58e0affe0af419a0bcaa3a3ed92 8662 
yaml-cpp_0.6.3-2_source.buildinfo
Files:
 2080b3993414d7b1b6e056445fd5a81c 1913 devel optional yaml-cpp_0.6.3-2.dsc
 17d8547643e6c5f3041745323d3a2984 10544 devel optional 
yaml-cpp_0.6.3-2.debian.tar.xz
 4ee60dbd712f3e4b15ee3a5acceb871c 8662 devel optional 
yaml-cpp_0.6.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl61Yt8ACgkQ808JdE6f
XdkzLg/+M7PkUQq1TPwyvmX0NTfyTXC4dCT0m9E1dnChaECiudsPYC5tzahtaqVo
GlFrPMc0PpWZSD7wYHeiwyiahQNf9wGwauBMLttWqffzjewKt9UHpLOpJGk2anLd
/KJrtppMeLug24q0mVSDcFP9+GJt3ubYOg34HTi+kxGMOZmCvlWqQWgVPe1zsWXV
bIhHawirxg7Tg7mbMmPUKZIp+1/+WaYq2OD1VRv1pFmsWZOsfPvp7ZZboO5k47aZ
mZxKt8lLKaorDpF54YdG7GL17fvskBz+veLCayxVM05q37DmYWlfnRW3G40hDrgM
FTCXrh9J1YNYYDGk9VY847ANFBlPSAT3F1n1LsA2qodzj26pLCZdlC9g6X+1/AjZ
JHHWs+dgW/LdFCW3YfYr/njwQri6ojfWeIFG+OUb4RM2Q8RwpmmXDTeKqy/NPNyy
lgmd9hnkk271gjxKNEmlIlriDOmJA2supBAOguJ3fFMw6N+Hgnoi1WVI8ds418p1
E5DBj56XYk1Of7vuimA/r5hLh20hT6Fh90qFv23SvAvrGWXAMqQnQzdT5ELa7roC
y5Kl5HbsaG72J+70l61VsN52xRdTsTExT7qp1GfYajEZPVEt5tgBTEBQGhHYPQIn
nY9wRxHVIs8HKpcUdHao+2O6WBXBe7Ox8hS9aElXxP7VQa43i0c=
=4HbA
-END PGP SIGNATURE End Message ---

Bug#960038: haskell-bz2: Failed to migrate to testing for too long

[Boyuan Yang]

Source: haskell-bz2
Version: 0.1.1.1-1
Severity: serious
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
X-Debbugs-CC: cl...@debian.org

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug. Your package src:haskell-bz2 in its current
version in unstable has been trying to migrate for 61 days. Hence, I am
filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

Currently your package only needs another source-only upload to be able to
migrate to Testing; please refer to https://wiki.debian.org/SourceOnlyUpload
to see how to make a source-only upload.

Regards,
Boyuan Yang

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html


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

Bug#951620: marked as done (clips: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 10:30:17 -0400
with message-id 
and subject line Re: clips: fails to migrate to testing for too long
has caused the Debian Bug report #951620,
regarding clips: fails to migrate to testing for too long
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.)


-- 
951620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clips
Version: 6.24-3.2
Severity: serious
Control: fixed -1 6.30-4
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug. Your package src:clips in its current
version in unstable has been trying to migrate for 834 days. Hence, I am
filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 6.30-4.1

The new NMU has fixed this bug and entered Testing. Closing the bug now.

-- 
Regards,
Boyuan Yang

On Tue, 18 Feb 2020 22:54:44 +0100 Paul Gevers  wrote:
> Source: clips
> Version: 6.24-3.2
> Severity: serious
> Control: fixed -1 6.30-4
> Tags: sid bullseye
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
> 
> Dear maintainer(s),
> 
> As recently announced [1], the Release Team now considers packages that
> are out-of-sync between testing and unstable for more than 60 days as
> having a Release Critical bug. Your package src:clips in its current
> version in unstable has been trying to migrate for 834 days. Hence, I am
> filing this bug.
> 
> If a package is out of sync between unstable and testing for a longer
> period, this usually means that bugs in the package in testing cannot be
> fixed via unstable. Additionally, blocked packages can have impact on
> other packages, which makes preparing for the release more difficult.
> Finally, it often exposes issues with the package and/or
> its (reverse-)dependencies. We expect maintainers to fix issues that
> hamper the migration of their package in a timely manner.
> 
> This bug will trigger auto-removal when appropriate. As with all new
> bugs, there will be at least 30 days before the package is auto-removed.
> 
> If you believe your package is unable to migrate to testing due to
> issues beyond your control, don't hesitate to contact the Release Team.
> 
> Paul
> 
> [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
> 
> 


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

Bug#944020: Help?

[Michael Robinson]

Hello-

I'm doing some work with the Tails team working to get Trezor python-trezor and 
python-libusb1 back-ported to Buster. These packages can then be put into 
testing for Tails to use. Currently this all hinges on getting debian bug 
944020  fixed, as per 
the discussion over with the Tails team: 
https://redmine.tails.boum.org/code/issues/17461#change-116459 
 . 

I am inquiring to see if there is anything I can do to help expedite 944020 and 
get the process moving along.

Regards

Bug#919348: xfce4-screensaver is now supprted in xfce4-session

[Marek Straka]

xfce4-screensaver is now supported in xfce4-session 
https://gitlab.xfce.org/xfce/xfce4-session/-/blob/xfce-4.14/NEWS

Bug#949461: repo is an empty package in unstable/testing, failing it's autopkg tests

[Roger Shimizu]

Dear Marcos,

Thanks for your email and contribution!

> An update to this package, based on salsa's repository, is available in
> https://github.com/marado/repo . It bumps repo's version to the latest,
> as well as fixes the empty package issue.

However we usually don't update so much stuff in one ticket.
I think you'd better open merge-request on salsa if you want those
patches be merged.

PS. I saw this issue is already resolved by one merge-request.
So I uploaded the package. You should be able to see it in testing in
a few days (usually 2).

Looking forward to your activity on salsa!

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

Bug#949461: marked as done (repo is an empty package in unstable/testing, failing it's autopkg tests)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 13:49:46 +
with message-id 
and subject line Bug#949461: fixed in repo 1.13.7-2
has caused the Debian Bug report #949461,
regarding repo is an empty package in unstable/testing, failing it's autopkg 
tests
to be marked as done.

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

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


-- 
949461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: repo
Version: 1.13.7-1
Severity: serious
Tags: sid bullseye

https://packages.debian.org/sid/all/repo/filelist

/usr/bin/repo
/usr/share/bash-completion/completions/repo
/usr/share/doc/repo/README.Debian
/usr/share/doc/repo/changelog.Debian.gz
/usr/share/doc/repo/copyright
/usr/share/doc/repo/manifest-format.md.gz
/usr/share/doc/repo/repo-hooks.md.gz
/usr/share/man/man1/repo.1.gz

autopkgtest [16:16:37]: test command1: (! repo help) && repo init --quiet
--depth=1 -u https://android.googlesource.com/platform/manifest -b 
android-2.3.7_r1
autopkgtest [16:16:37]: test command1: [---
usage: repo COMMAND [ARGS]

repo is not yet installed.  Use "repo init" to install it here.

The most commonly used repo commands are:

  init  Install repo in the current working directory
  help  Display detailed help on a command

For access to the full online help, install repo ("repo init").

autopkgtest [16:16:38]: test command1: ---]
--- End Message ---
--- Begin Message ---
Source: repo
Source-Version: 1.13.7-2
Done: Roger Shimizu 

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

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated repo 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, 08 May 2020 22:05:19 +0900
Source: repo
Architecture: source
Version: 1.13.7-2
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Roger Shimizu 
Closes: 949461
Changes:
 repo (1.13.7-2) unstable; urgency=medium
 .
   * Team upload.
   * Change autopkgtest to not negate repo help return code.
 Thanks to Michel Le Bihan for merge-request on salsa.
 (Closes: #949461)
   * debian/control: Add Rules-Requires-Root: no
   * Add debian/upstream/metadata.
   * debian/tests/control: Add ca-certificates to dependency.
Checksums-Sha1:
 705ab878e7982453cf611a1a67f23457d70726cf 2019 repo_1.13.7-2.dsc
 a6d17069dff85ce6b8850d99e026c5a053cc94b4 7544 repo_1.13.7-2.debian.tar.xz
 a495da8ba6ade79f818dddaaa864570e9b24cc1a 5260 repo_1.13.7-2_source.buildinfo
Checksums-Sha256:
 1c68d988ae3875cf4bfdb3540dc42345422c02570ceb3a738adca0599c8feeff 2019 
repo_1.13.7-2.dsc
 7bc30273d2ae32b46208290ef0bc1a75b234afef6b24851cf70fddb5bf3f7343 7544 
repo_1.13.7-2.debian.tar.xz
 9d5cceff288d41a2fa1bec68fa7e8b764f1623c868f31eb7b745a124bb7ed085 5260 
repo_1.13.7-2_source.buildinfo
Files:
 4ba37e3f4cd8eb883c82d9719263509c 2019 contrib/devel optional repo_1.13.7-2.dsc
 134bb00ac28899a2a9be68ee084d43c8 7544 contrib/devel optional 
repo_1.13.7-2.debian.tar.xz
 1e4a651029ebb6fe96de81d372ce4b27 5260 contrib/devel optional 
repo_1.13.7-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEECjKtvoA5m+cWOFnspHhrDacDNKgFAl61XnYQHHJvc2hAZGVi
aWFuLm9yZwAKCRCkeGsNpwM0qGFRD/0TuBZcvjmlICzBgj491UG+JF/5cpBLY0rw
5kL+RZSezG0e4G3/7TGQZuHPt0RpUrlqV7LF3A+YTauxAvQVzu/ITfwafMznHZcP
+LhkU8Kfp9E6VYH/rAIX2JMzgweZcIL5i9notface+HY2mpY0LQPKffFHHmkBqEs
48PXekvlGX8J9UT3TD/qlrQkMW63oMcpNYLQP4OaJjkGcdzsiWDKzvI5WTrl/2NR
/URqja5iEhy7Es6/sZxmzsC0IBIQ8gBz8I4hB6Xdd0qcx56vAaotkO4n8oUuw+21
+0SDBOSTzsWSK0v7o94OhGIAbVN88Ti6Jk4mf5nbUcuFk+jf5Xp9uBL1TopXCAHg
l89qE9rmfgDGzdzy1vhX+51gb43W2Wny/SU9qSB0SsWs1PbxNdxaQ5hAuG3nLTVu
ZQadd1O+qSO/Tq8G1Dl7EGLUr767GzKCuCJzlA/1yFvjm9KO5pvdc8R8rIljm+NA
A+YvWqj72JFSMtVfp2UTAYqwmmYxks/zHKFYSEn3yV5IBJO1bo9OG6bcDVRnVLHB
iSUbGtTfJPQ87V0G0sicxSfABcBHt7Zx3DZYagALgTDAcQ1LCP415nbv9n40kK+a
tShDPpUddkestKRhpdHNxFNs5Ov0Mk/Kz3OFtzttd7SZcf1kDG+747OOhOkTtx6y
TnGaPm9jnA==
=lWeV
-END PGP SIGNATURE End Message ---

Bug#959546: marked as done (rabbitmq-server: FTBFS: build-dependency not installable: elixir (>= 1.6.6))

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 13:33:47 +
with message-id 
and subject line Bug#959701: fixed in elixir-lang 1.10.3.dfsg-1
has caused the Debian Bug report #959701,
regarding rabbitmq-server: FTBFS: build-dependency not installable: elixir (>= 
1.6.6)
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.)


-- 
959701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rabbitmq-server
Version: 3.7.18-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 10), dh-python, elixir (>= 1.6.6), 
> erlang-base (>= 1:19.3), erlang-crypto (>= 1:19.3), erlang-dev (>= 1:19.3), 
> erlang-edoc (>= 1:19.3), erlang-eldap (>= 1:19.3), erlang-erl-docgen (>= 
> 1:19.3), erlang-eunit (>= 1:19.3), erlang-inets (>= 1:19.3), erlang-mnesia 
> (>= 1:19.3), erlang-nox (>= 1:19.3), erlang-os-mon (>= 1:19.3), 
> erlang-parsetools (>= 1:19.3), erlang-public-key (>= 1:19.3), 
> erlang-runtime-tools (>= 1:19.3), erlang-src (>= 1:19.3), erlang-ssl (>= 
> 1:19.3), erlang-syntax-tools (>= 1:19.3), erlang-tools (>= 1:19.3), 
> erlang-xmerl (>= 1:19.3), locales-all, python3-all, python3-simplejson, 
> rsync, unzip, xmlto, xsltproc, zip, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 10), dh-python, elixir (>= 
> 1.6.6), erlang-base (>= 1:19.3), erlang-crypto (>= 1:19.3), erlang-dev (>= 
> 1:19.3), erlang-edoc (>= 1:19.3), erlang-eldap (>= 1:19.3), erlang-erl-docgen 
> (>= 1:19.3), erlang-eunit (>= 1:19.3), erlang-inets (>= 1:19.3), 
> erlang-mnesia (>= 1:19.3), erlang-nox (>= 1:19.3), erlang-os-mon (>= 1:19.3), 
> erlang-parsetools (>= 1:19.3), erlang-public-key (>= 1:19.3), 
> erlang-runtime-tools (>= 1:19.3), erlang-src (>= 1:19.3), erlang-ssl (>= 
> 1:19.3), erlang-syntax-tools (>= 1:19.3), erlang-tools (>= 1:19.3), 
> erlang-xmerl (>= 1:19.3), locales-all, python3-all, python3-simplejson, 
> rsync, unzip, xmlto, xsltproc, zip, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [547 B]
> Get:5 copy:/<>/apt_archive ./ Packages [633 B]
> Fetched 2143 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: elixir (>= 1.6.6) but it is not 
> going to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/05/01/rabbitmq-server_3.7.18-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: elixir-lang
Source-Version: 1.10.3.dfsg-1
Done: Evgeny Golyshev 

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

Bug#959458: marked as done (matchbox-panel: Build-Depends on obsolete package linux-kernel-headers)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 13:34:12 +
with message-id 
and subject line Bug#959458: fixed in matchbox-panel 0.9.3-11
has caused the Debian Bug report #959458,
regarding matchbox-panel: Build-Depends on obsolete package linux-kernel-headers
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.)


-- 
959458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:matchbox-panel
Version: 0.9.3-10
Severity: serious

linux-kernel-headers was removed from unstable in 2007 (I think).  It
is now effectively a virtual package provided by linux-libc-dev, but
it's not a documented virtual package name and I would like to stop
providing it.

linux-libc-dev is (transitively) build-essential, so you do not need to
Build-Depend on it at all.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: matchbox-panel
Source-Version: 0.9.3-11
Done: Moray Allan 

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

Debian distribution maintenance software
pp.
Moray Allan  (supplier of updated matchbox-panel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 13:01:37 +0100
Source: matchbox-panel
Architecture: source
Version: 0.9.3-11
Distribution: unstable
Urgency: medium
Maintainer: Moray Allan 
Changed-By: Moray Allan 
Closes: 930958 959458
Changes:
 matchbox-panel (0.9.3-11) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure.
 Closes: #930958.
 .
   [ Moray Allan ]
   * Update Build-Depends.
   * Drop Build-Depends on obsolete package linux-kernel-headers.
 Closes: #959458.
   * Update standards version.
   * Enable bindnow hardening option.
Checksums-Sha1:
 95bef89457e3618c6e3301c5b18d9d3fe8f091db 1837 matchbox-panel_0.9.3-11.dsc
 b2b833565f94513448d49551e14e58031cd05a1b 7988 
matchbox-panel_0.9.3-11.debian.tar.xz
 7dee28908c0fa00d4976bc52efc2d6054e16875c 10081 
matchbox-panel_0.9.3-11_amd64.buildinfo
Checksums-Sha256:
 2cbc998da1c41ca6a15eca8291e16816dfaa1e63372e5c5ded4a3081aa40263c 1837 
matchbox-panel_0.9.3-11.dsc
 b0a1a6720f50e019a8c8898902c15cf0a2d175f920fb6b87a126f9f3c0ce8e20 7988 
matchbox-panel_0.9.3-11.debian.tar.xz
 f094bfdfb9de932d85928f7cdeaa5ce406420b40bf5c14b47363dff39b35d80c 10081 
matchbox-panel_0.9.3-11_amd64.buildinfo
Files:
 e016c438a866c3258c95bfbfa30b7ca4 1837 embedded optional 
matchbox-panel_0.9.3-11.dsc
 5e36a5d2171a309bd42fbff021568833 7988 embedded optional 
matchbox-panel_0.9.3-11.debian.tar.xz
 d26809d5954a8093c0c12b28fd581235 10081 embedded optional 
matchbox-panel_0.9.3-11_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE6zLWdjjE49iqJAPwvr2TMzX8FAsFAl61WhgRHG1vcmF5QGRl
Ymlhbi5vcmcACgkQvr2TMzX8FAvXLA/+PMJbz4RIkisHb8LGduJb4nEJk5bY8dze
TFqXRYu2smKsn50vUkEAh9wDeoZx34Xo3PzemYBf1j7j0ORocVqM+vbO6rzGL9co
uU99ZmQKXONrAWlAujZKGg1KVPLYANtZNK3kv63J4X05TH793ZbIoDZtSY3TQo4A
EzSa7j7SNdmmzfCa6Qp5Z4PXql9XbmoOz8rJBnjDIZ+BQKhrGdMXs2gigP0WpxTs
U5oUulwA/tPeSvJ7ZKUCezXCE7FRUF65vxPR/FGe2BM62glP6PMcFom3nsugMPUM
pN1VPhhilnNA2tWchV5nZ05QIUTOe9jzHID7fAN8+3EE0s17JnnQrgOBrBAk5iox
BiR03PtU+sIB+hIEZklNcTBVTu0MnnEd4MeG2JShRN5um9gqKTUp8ITmcjdlcRWj
1ql0RvwshkBPSeD7SmtZDi38vPD9jGy73xdgUs15VYkgoCjLHFJ8cs2aPjSLhLzi
estZyMc0UKFCdZzbeajW0O1Se8ZGNcb+7EsQxzScocjPqJdgGi4g6D4I5zSsZXvo
1rWFdB/AM9hDDHyocEL/csQV19o06Sf8m1WykBb1VyVXmD5kBJXNa3JiFYawGZGg
YJ7c2HFMvZ9uE/NaV7nsJU4bGH3qHDqNky+EWRnJRJ/G3UbpBGrLf9sfojbugxOR
iq8lmagErQc=
=voZt
-END PGP SIGNATURE End Message ---

Bug#959701: marked as done (elixir-lang: incompatible with erlang 22)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 13:33:47 +
with message-id 
and subject line Bug#959701: fixed in elixir-lang 1.10.3.dfsg-1
has caused the Debian Bug report #959701,
regarding elixir-lang: incompatible with erlang 22
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.)


-- 
959701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: erlang, elixir-lang
Control: found -1 erlang/1:22.3.2+dfsg-1
Control: found -1 elixir-lang/1.9.1.dfsg-1.3
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

With a recent upload of erlang the autopkgtest of elixir-lang fails in
testing when that autopkgtest is run with the binary packages of erlang
from unstable. It passes when run with only packages from testing. In
tabular form:

   passfail
erlang from testing1:22.3.2+dfsg-1
elixir-langfrom testing1.9.1.dfsg-1.3
all others from testingfrom testing

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

Currently this regression is blocking the migration of erlang to testing
[1]. Due to the nature of this issue, I filed this bug report against
both packages. Can you please investigate the situation and reassign the
bug to the right package?

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/e/elixir-lang/5145669/log.gz

Finished in 119.8 seconds (9.2s on load, 110.6s on tests)
9 doctests, 618 tests, 0 failures

Randomized with seed 214091
Killed
autopkgtest [21:16:46]: test run-all: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: elixir-lang
Source-Version: 1.10.3.dfsg-1
Done: Evgeny Golyshev 

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

Debian distribution maintenance software
pp.
Evgeny Golyshev  (supplier of updated elixir-lang package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 06 May 2020 20:33:40 +0300
Source: elixir-lang
Architecture: source
Version: 1.10.3.dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Evgeny Golyshev 
Changed-By: Evgeny Golyshev 
Closes: 959160 959701 959988
Changes:
 elixir-lang (1.10.3.dfsg-1) unstable; urgency=medium
 .
   * New upstream release (closes: #959701, #959160, #959988).
   * Remove patches/remove-test-executes-rpc-instructions.patch.
   * Require Erlang 21.0 or later.
Checksums-Sha1:
 38b738dabb8c9e6dcb2050a24a16b07d298a4d63 2185 elixir-lang_1.10.3.dfsg-1.dsc
 444cd788791b585a878b1b52e3cd50b5a4c0d689 1198816 
elixir-lang_1.10.3.dfsg.orig.tar.xz
 2bde031facc772a41e066ea79819f1ae81cd4b9c 7320 
elixir-lang_1.10.3.dfsg-1.debian.tar.xz
 c44ab288995fe0c1acad8bcd8a636e2a579adafe 7416 
elixir-lang_1.10.3.dfsg-1_source.buildinfo
Checksums-Sha256:
 f6f254a11bb746f20a300cfeddaa2446febe97ac3558cd33ee7b5b04a78197ee 2185 
elixir-lang_1.10.3.dfsg-1.dsc
 3c9ba3026abbea63943f1502a645de6ed0af4d760e375e982c0478e7611e3d7e 1198816 
elixir-lang_1.10.3.dfsg.orig.tar.xz
 8d4a6c84c6e219e6a28c2e6ca7d6dac56b9f3e0a782b5912bca9789fe5e98214 7320 
elixir-lang_1.10.3.dfsg-1.debian.tar.xz
 48e375b2e1ced87a6f026e601ecc1b3d2fb318f4b7366d0316051001deb6aaca 7416 
elixir-lang_1.10.3.dfsg-1_source.buildinfo
Files:
 4877cb2024783bd4ad6a15e53b95a170 2185 interpreters optional 
elixir-lang_1.10.3.dfsg-1.dsc
 702f09fb95f09c4e465a332a163e0a5f 1198816 interpreters optional 
elixir-lang_1.10.3.dfsg.orig.tar.xz
 1e5a2f263768afbcfc78f5e8d45e88cd 7320 interpreters optional 
elixir-lang_1.10.3.dfsg-1.debian.tar.xz
 2ea1ad5c08f42acbf33f9eee8c6309b6 7416 interpreters optional 
elixir-lang_1.10.3.dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: retitle 959900 to keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 CVE-2020-12692

[Debian Bug Tracking System]

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

> retitle 959900 keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 
> CVE-2020-12692
Bug #959900 [src:keystone] CVE pending / OSSA-2020-004: EC2 and credential 
endpoints are not protected from a scoped context
Changed Bug title to 'keystone: CVE-2020-12689 CVE-2020-12690 CVE-2020-12691 
CVE-2020-12692' from 'CVE pending / OSSA-2020-004: EC2 and credential endpoints 
are not protected from a scoped context'.
> thanks
Stopping processing here.

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

Processed: tagging 960011, bug 960011 is forwarded to https://github.com/leto/math--gsl/issues/167

[Debian Bug Tracking System]

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

> tags 960011 + upstream
Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported 
version: 2.6 at Build.PL line 80)
Bug #960014 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS with gsl 2.6
Ignoring request to alter tags of bug #960011 to the same tags previously set
Ignoring request to alter tags of bug #960014 to the same tags previously set
> forwarded 960011 https://github.com/leto/math--gsl/issues/167
Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported 
version: 2.6 at Build.PL line 80)
Bug #960014 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS with gsl 2.6
Changed Bug forwarded-to-address to 
'https://github.com/leto/math--gsl/issues/167' from 
'https://github.com/leto/math--gsl/issues/173'.
Changed Bug forwarded-to-address to 
'https://github.com/leto/math--gsl/issues/167' from 
'https://github.com/leto/math--gsl/issues/173'.
> thanks
Stopping processing here.

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

Processed: found 959900 in 2:16.0.0-6

[Debian Bug Tracking System]

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

> found 959900 2:16.0.0-6
Bug #959900 [src:keystone] keystone: CVE-2020-12689 CVE-2020-12690 
CVE-2020-12691 CVE-2020-12692
Marked as found in versions keystone/2:16.0.0-6.
> thanks
Stopping processing here.

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

Processed: bug 960011 is forwarded to https://github.com/leto/math--gsl/issues/173, tagging 960011

[Debian Bug Tracking System]

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

> forwarded 960011 https://github.com/leto/math--gsl/issues/173
Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported 
version: 2.6 at Build.PL line 80)
Bug #960014 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS with gsl 2.6
Set Bug forwarded-to-address to 'https://github.com/leto/math--gsl/issues/173'.
Set Bug forwarded-to-address to 'https://github.com/leto/math--gsl/issues/173'.
> tags 960011 + upstream
Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported 
version: 2.6 at Build.PL line 80)
Bug #960014 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS with gsl 2.6
Added tag(s) upstream.
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#945481: Bump minimum version of ruby-molinillo dependency in ruby-bundler

[Andreas Beckmann]

Followup-For: Bug #945481
Control: tag -1 pending
Control: block -1 with 960020

Hi,

I've backported the fix to buster, uploaded to DELAYED/10 and filed a
buster-pu request (#960020) (the debdiff can be found there, too).


Andreas

Processed: Re: Bump minimum version of ruby-molinillo dependency in ruby-bundler

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #945481 {Done: Debian FTP Masters } 
[bundler] Bump minimum version of ruby-molinillo dependency in ruby-bundler
Added tag(s) pending.
> block -1 with 960020
Bug #945481 {Done: Debian FTP Masters } 
[bundler] Bump minimum version of ruby-molinillo dependency in ruby-bundler
945481 was not blocked by any bugs.
945481 was not blocking any bugs.
Added blocking bug(s) of 945481: 960020

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

Processed: Re: scap-security-guide: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #938438 [src:scap-security-guide] scap-security-guide: Python2 removal in 
sid/bullseye
Severity set to 'serious' from 'normal'

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

Bug#958577: Uploaded fix to delay/2

[Felipe Sateler]

Thank you. Feel free to upload directly to unstable.

Saludos,
Felipe Sateler

On Fri, May 8, 2020, 04:57 Thomas Goirand  wrote:

> Hi,
>
> Since nobody seem to care, I uploaded the fix to delay/2:
>
> --- a/debian/control
> +++ b/debian/control
> @@ -19,7 +19,7 @@
>
>  Package: python3-docker
>  Architecture: all
> -Depends: ${misc:Depends}, ${python3:Depends}
> +Depends: python3-distutils, ${misc:Depends}, ${python3:Depends}
>  Description: Python 3 wrapper to access docker.io's control socket
>   This package contains oodles of routines that aid in controlling
>   docker.io over it's socket control, the same way the docker.io
>
> Cheers,
>
> Thomas Goirand (zigo)
>
>

Bug#959201: marked as done (jami-daemon: dring does not start due to a symbol lookup error)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 11:33:30 +
with message-id 
and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1
has caused the Debian Bug report #959201,
regarding jami-daemon: dring does not start due to a symbol lookup error
to be marked as done.

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

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


-- 
959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jami-daemon
Version: 20190215.1.f152c98~ds1-1+b1
Severity: grave
Justification: renders package unusable

Hi,

Jami fails to connect to its daemon dring because it cannot start due to a
symbol lookup error:

/usr/lib/ring/dring: symbol lookup error: /usr/lib/ring/dring: undefined
symbol: _ZN4YAML6detail9node_data12empty_scalarB5cxx11E

Cheers,
Bruno



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

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.utf-8), LANGUAGE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set 
to de_DE.utf-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages jami-daemon depends on:
ii  libargon2-10~20171227-0.2
ii  libasound2 1.2.2-2.1
ii  libavcodec58   7:4.2.2-1+b1
ii  libavdevice58  7:4.2.2-1+b1
ii  libavfilter7   7:4.2.2-1+b1
ii  libavformat58  7:4.2.2-1+b1
ii  libavutil567:4.2.2-1+b1
ii  libc6  2.30-4
ii  libdbus-c++-1-0v5  0.9.0-8.1
ii  libgcc-s1 [libgcc1]10-20200418-1
ii  libgcc11:10-20200418-1
ii  libgnutls303.6.13-2
ii  libixml10  1:1.8.4-2
ii  libjsoncpp11.7.4-3.1
ii  libnatpmp1 20150609-7+b2
ii  libnettle7 3.5.1+really3.5.1-2
ii  libpcre3   2:8.39-12+b1
ii  libpulse0  13.0-5
ii  librestbed0 [librestbed0]  4.0~dfsg1-5
ii  libsecp256k1-0 0.1~20170810-2
ii  libstdc++6 10-20200418-1
ii  libswresample3 7:4.2.2-1+b1
ii  libswscale57:4.2.2-1+b1
ii  libudev1   245.5-2
ii  libupnp13  1:1.8.4-2
ii  libuuid1   2.34-0.1
ii  libyaml-cpp0.6 0.6.3-1
ii  zlib1g 1:1.2.11.dfsg-2

jami-daemon recommends no packages.

jami-daemon suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: yaml-cpp
Source-Version: 0.6.3-1.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated yaml-cpp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 13:15:00 +0200
Source: yaml-cpp
Binary: libyaml-cpp0.6 libyaml-cpp-dev
Architecture: source
Version: 0.6.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Simon Quigley 
Changed-By: Gianfranco Costamagna 
Description:
 libyaml-cpp-dev - YAML parser and emitter for C++ - development files
 libyaml-cpp0.6 - YAML parser and emitter for C++
Closes: 959201
Changes:
 yaml-cpp (0.6.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Revert ABI changes in new release (Closes: #959201)
 - debian/patches/revert-774f25800e6f19f4b927023c85d1389af322da5e.patch:
Checksums-Sha1:
 35c6f37846586e995e8e1c1542c5d2b0e5a80cf0 1921 yaml-cpp_0.6.3-1.1.dsc
 48be635f1c98d01c8e22175a89b159b2137f2d5a 10440 yaml-cpp_0.6.3-1.1.debian.tar.xz
 e3a9e7e6e3c64037ae3173a4334a07edb3620971 8670 
yaml-cpp_0.6.3-1.1_source.buildinfo
Checksums-Sha256:
 d0e99fd5614e03ab32b7dda5bbace8af5c9faf704646f53552adaf1a8415330f 1921 
yaml-cpp_0.6.3-1.1.dsc
 

Bug#959586: marked as done (openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]')

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 11:33:30 +
with message-id 
and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1
has caused the Debian Bug report #959201,
regarding openimageio: FTBFS: ld: /usr/lib/libOpenColorIO.so.1: undefined 
reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
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.)


-- 
959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openimageio
Version: 2.1.13.0~dfsg0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now 
> CMakeFiles/filter_test.dir/filter_test.cpp.o  -o ../../bin/filter_test  
> -Wl,-rpath,"/<>/build/lib" ../../lib/libOpenImageIO.so.2.1.13 
> /usr/lib/x86_64-linux-gnu/libImath.so /usr/lib/x86_64-linux-gnu/libIex.so 
> /usr/lib/x86_64-linux-gnu/libHalf.so 
> /usr/lib/x86_64-linux-gnu/libIlmThread.so -lpthread 
> /usr/lib/x86_64-linux-gnu/libIlmImf.so /usr/lib/x86_64-linux-gnu/libImath.so 
> /usr/lib/x86_64-linux-gnu/libIex.so /usr/lib/x86_64-linux-gnu/libHalf.so 
> /usr/lib/x86_64-linux-gnu/libIlmThread.so -lpthread 
> /usr/lib/x86_64-linux-gnu/libIlmImf.so /usr/lib/x86_64-linux-gnu/libz.so 
> /usr/lib/x86_64-linux-gnu/libopencv_core.so 
> /usr/lib/x86_64-linux-gnu/libopencv_imgproc.so 
> /usr/lib/x86_64-linux-gnu/libopencv_videoio.so 
> /usr/bin/ld: /usr/lib/libOpenColorIO.so.1: undefined reference to 
> `YAML::detail::node_data::empty_scalar[abi:cxx11]'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   
http://qa-logs.debian.net/2020/05/01/openimageio_2.1.13.0~dfsg0-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: yaml-cpp
Source-Version: 0.6.3-1.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated yaml-cpp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 13:15:00 +0200
Source: yaml-cpp
Binary: libyaml-cpp0.6 libyaml-cpp-dev
Architecture: source
Version: 0.6.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Simon Quigley 
Changed-By: Gianfranco Costamagna 
Description:
 libyaml-cpp-dev - YAML parser and emitter for C++ - development files
 libyaml-cpp0.6 - YAML parser and emitter for C++
Closes: 959201
Changes:
 yaml-cpp (0.6.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Revert ABI changes in new release (Closes: #959201)
 - debian/patches/revert-774f25800e6f19f4b927023c85d1389af322da5e.patch:
Checksums-Sha1:
 35c6f37846586e995e8e1c1542c5d2b0e5a80cf0 1921 yaml-cpp_0.6.3-1.1.dsc
 48be635f1c98d01c8e22175a89b159b2137f2d5a 10440 yaml-cpp_0.6.3-1.1.debian.tar.xz
 e3a9e7e6e3c64037ae3173a4334a07edb3620971 8670 
yaml-cpp_0.6.3-1.1_source.buildinfo
Checksums-Sha256:
 d0e99fd5614e03ab32b7dda5bbace8af5c9faf704646f53552adaf1a8415330f 1921 
yaml-cpp_0.6.3-1.1.dsc
 6609a82225d6f4ecdb74e2c27a6edcaeef46eea0a3a5669a0b7c556843f09579 10440 
yaml-cpp_0.6.3-1.1.debian.tar.xz
 c9f7423cad80871600745de29fb24998b49b6e86010643d969d9ac09164e97a8 8670 
yaml-cpp_0.6.3-1.1_source.buildinfo
Files:
 6edbff4c315e15d5b7b3b84ad6b0362b 1921 devel optional yaml-cpp_0.6.3-1.1.dsc
 0c829fbf339c5b760fc6c00b6b8ffadd 10440 devel optional 
yaml-cpp_0.6.3-1.1.debian.tar.xz
 

Bug#959556: marked as done (olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]')

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 11:33:30 +
with message-id 
and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1
has caused the Debian Bug report #959201,
regarding olive-editor: FTBFS: ld: /usr/lib/libOpenColorIO.so: undefined 
reference to `YAML::detail::node_data::empty_scalar[abi:cxx11]'
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.)


-- 
959201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: olive-editor
Version: 20200210-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++  -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2  -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
> CMakeFiles/olive-editor.dir/olive-editor_autogen/mocs_compilation.cpp.o 
> CMakeFiles/olive-editor.dir/core.cpp.o CMakeFiles/olive-editor.dir/main.cpp.o 
> CMakeFiles/olive-editor.dir/audio/audiomanager.cpp.o 
> CMakeFiles/olive-editor.dir/audio/bufferaverage.cpp.o 
> CMakeFiles/olive-editor.dir/audio/outputdeviceproxy.cpp.o 
> CMakeFiles/olive-editor.dir/audio/outputmanager.cpp.o 
> CMakeFiles/olive-editor.dir/audio/sampleformat.cpp.o 
> CMakeFiles/olive-editor.dir/audio/tempoprocessor.cpp.o 
> CMakeFiles/olive-editor.dir/codec/ffmpeg/ffmpegcommon.cpp.o 
> CMakeFiles/olive-editor.dir/codec/ffmpeg/ffmpegdecoder.cpp.o 
> CMakeFiles/olive-editor.dir/codec/ffmpeg/ffmpegencoder.cpp.o 
> CMakeFiles/olive-editor.dir/codec/oiio/oiiodecoder.cpp.o 
> CMakeFiles/olive-editor.dir/codec/decoder.cpp.o 
> CMakeFiles/olive-editor.dir/codec/encoder.cpp.o 
> CMakeFiles/olive-editor.dir/codec/frame.cpp.o 
> CMakeFiles/olive-editor.dir/codec/waveinput.cpp.o 
> CMakeFiles/olive-editor.dir/codec/waveoutput.cpp.o 
> CMakeFiles/olive-editor.dir/common/bezier.cpp.o 
> CMakeFiles/olive-editor.dir/common/debug.cpp.o 
> CMakeFiles/olive-editor.dir/common/filefunctions.cpp.o 
> CMakeFiles/olive-editor.dir/common/flipmodifiers.cpp.o 
> CMakeFiles/olive-editor.dir/common/qtversionabstraction.cpp.o 
> CMakeFiles/olive-editor.dir/common/rational.cpp.o 
> CMakeFiles/olive-editor.dir/common/threadedobject.cpp.o 
> CMakeFiles/olive-editor.dir/common/timecodefunctions.cpp.o 
> CMakeFiles/olive-editor.dir/common/timerange.cpp.o 
> CMakeFiles/olive-editor.dir/config/config.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/about/about.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/actionsearch/actionsearch.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/export/export.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/export/exportaudiotab.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/export/exportvideotab.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/footageproperties/streamproperties/streamproperties.cpp.o
>  
> CMakeFiles/olive-editor.dir/dialog/footageproperties/streamproperties/audiostreamproperties.cpp.o
>  
> CMakeFiles/olive-editor.dir/dialog/footageproperties/streamproperties/videostreamproperties.cpp.o
>  CMakeFiles/olive-editor.dir/dialog/footageproperties/footageproperties.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/keyframeproperties/keyframeproperties.cpp.o
>  CMakeFiles/olive-editor.dir/dialog/loadsave/loadsave.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesgeneraltab.cpp.o
>  
> CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesbehaviortab.cpp.o
>  CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesdisktab.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesappearancetab.cpp.o
>  
> CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesqualitytab.cpp.o
>  
> CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencesaudiotab.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferenceskeyboardtab.cpp.o
>  CMakeFiles/olive-editor.dir/dialog/preferences/tabs/preferencestab.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/preferences/keysequenceeditor.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/preferences/preferences.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/projectproperties/projectproperties.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/rendercancel/rendercancel.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/sequence/sequence.cpp.o 
> CMakeFiles/olive-editor.dir/dialog/speedduration/speedduration.cpp.o 
> CMakeFiles/olive-editor.dir/node/audio/pan/pan.cpp.o 
> CMakeFiles/olive-editor.dir/node/audio/volume/volume.cpp.o 
> 

Bug#959657: marked as done (olive-editor: Does not start: symbol lookup error)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 11:33:30 +
with message-id 
and subject line Bug#959201: fixed in yaml-cpp 0.6.3-1.1
has caused the Debian Bug report #959201,
regarding olive-editor: Does not start: symbol lookup error
to be marked as done.

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

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


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

Package: olive-editor
Version: 20200210-1
Severity: grave
Justification: renders package unusable

olive-editor: symbol lookup error: /lib/libOpenColorIO.so.1: undefined 
symbol:

_ZN4YAML6detail9node_data12empty_scalarB5cxx11E

Clearly the dependencies are not tight enough, and the package needs to be
rebuilt for the current library versions.



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

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) (ignored: 
LC_ALL set to de_DE.utf-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) 
(ignored: LC_ALL set to de_DE.utf-8)

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages olive-editor depends on:
ii  ffmpeg 7:4.2.2-1+b1
ii  frei0r-plugins 1.7.0-1
ii  libavcodec58   7:4.2.2-1+b1
ii  libavfilter7   7:4.2.2-1+b1
ii  libavformat58  7:4.2.2-1+b1
ii  libavutil56    7:4.2.2-1+b1
ii  libc6  2.30-4
ii  libgcc-s1  10-20200418-1
ii  libopencolorio1v5  1.1.1~dfsg0-6+b1
ii  libopenimageio2.1  2.1.13.0~dfsg0-1
ii  libqt5core5a   5.12.5+dfsg-10
ii  libqt5gui5 5.12.5+dfsg-10
ii  libqt5multimedia5  5.12.5-1+b1
ii  libqt5multimedia5-plugins  5.12.5-1+b1
ii  libqt5widgets5 5.12.5+dfsg-10
ii  libstdc++6 10-20200418-1
ii  libswresample3 7:4.2.2-1+b1
ii  libswscale5    7:4.2.2-1+b1

olive-editor recommends no packages.

olive-editor suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: yaml-cpp
Source-Version: 0.6.3-1.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated yaml-cpp 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 13:15:00 +0200
Source: yaml-cpp
Binary: libyaml-cpp0.6 libyaml-cpp-dev
Architecture: source
Version: 0.6.3-1.1
Distribution: unstable
Urgency: medium
Maintainer: Simon Quigley 
Changed-By: Gianfranco Costamagna 
Description:
 libyaml-cpp-dev - YAML parser and emitter for C++ - development files
 libyaml-cpp0.6 - YAML parser and emitter for C++
Closes: 959201
Changes:
 yaml-cpp (0.6.3-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Revert ABI changes in new release (Closes: #959201)
 - debian/patches/revert-774f25800e6f19f4b927023c85d1389af322da5e.patch:
Checksums-Sha1:
 35c6f37846586e995e8e1c1542c5d2b0e5a80cf0 1921 yaml-cpp_0.6.3-1.1.dsc
 48be635f1c98d01c8e22175a89b159b2137f2d5a 10440 yaml-cpp_0.6.3-1.1.debian.tar.xz
 e3a9e7e6e3c64037ae3173a4334a07edb3620971 8670 
yaml-cpp_0.6.3-1.1_source.buildinfo
Checksums-Sha256:
 d0e99fd5614e03ab32b7dda5bbace8af5c9faf704646f53552adaf1a8415330f 1921 
yaml-cpp_0.6.3-1.1.dsc
 6609a82225d6f4ecdb74e2c27a6edcaeef46eea0a3a5669a0b7c556843f09579 10440 
yaml-cpp_0.6.3-1.1.debian.tar.xz
 c9f7423cad80871600745de29fb24998b49b6e86010643d969d9ac09164e97a8 8670 
yaml-cpp_0.6.3-1.1_source.buildinfo
Files:
 6edbff4c315e15d5b7b3b84ad6b0362b 1921 devel optional yaml-cpp_0.6.3-1.1.dsc
 0c829fbf339c5b760fc6c00b6b8ffadd 10440 devel optional 
yaml-cpp_0.6.3-1.1.debian.tar.xz
 69a1b8e635805b95552468035e0fcf65 8670 devel optional 
yaml-cpp_0.6.3-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#958034: marked as done (python-zeroconf: FTBFS: tests fail without networking)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 11:18:38 +
with message-id 
and subject line Bug#958034: fixed in python-zeroconf 0.25.0-2
has caused the Debian Bug report #958034,
regarding python-zeroconf: FTBFS: tests fail without networking
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.)


-- 
958034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-zeroconf
Version: 0.25.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

python-zeroconf/experimental FTBFS under pbuilder which defaults to
disable networking during the build. This causes some tests to fail:

==
ERROR: test_launch_and_close (zeroconf.test.Framework)
--
Traceback (most recent call last):
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/test.py", 
line 501, in test_launch_and_close
rv = r.Zeroconf(interfaces=r.InterfaceChoice.Default)
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2135, in __init__
self._listen_socket, self._respond_sockets = create_sockets(
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2064, in create_sockets
respond_socket = add_multicast_member(cast(socket.socket, listen_socket), 
i, apple_p2p=apple_p2p)
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2011, in add_multicast_member
listen_socket.setsockopt(socket.IPPROTO_IP, socket.IP_ADD_MEMBERSHIP, 
_value)
OSError: [Errno 19] No such device

==
ERROR: test_launch_and_close_v4_v6 (zeroconf.test.Framework)
--
Traceback (most recent call last):
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/test.py", 
line 509, in test_launch_and_close_v4_v6
rv = r.Zeroconf(interfaces=r.InterfaceChoice.Default, 
ip_version=r.IPVersion.All)
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2135, in __init__
self._listen_socket, self._respond_sockets = create_sockets(
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2064, in create_sockets
respond_socket = add_multicast_member(cast(socket.socket, listen_socket), 
i, apple_p2p=apple_p2p)
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2008, in add_multicast_member
listen_socket.setsockopt(_IPPROTO_IPV6, socket.IPV6_JOIN_GROUP, _value)
OSError: [Errno 19] No such device

==
ERROR: test_launch_and_close_v6_only (zeroconf.test.Framework)
--
Traceback (most recent call last):
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/test.py", 
line 517, in test_launch_and_close_v6_only
rv = r.Zeroconf(interfaces=r.InterfaceChoice.Default, 
ip_version=r.IPVersion.V6Only)
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2135, in __init__
self._listen_socket, self._respond_sockets = create_sockets(
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2064, in create_sockets
respond_socket = add_multicast_member(cast(socket.socket, listen_socket), 
i, apple_p2p=apple_p2p)
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/__init__.py",
 line 2008, in add_multicast_member
listen_socket.setsockopt(_IPPROTO_IPV6, socket.IPV6_JOIN_GROUP, _value)
OSError: [Errno 19] No such device


==
FAIL: test_integration_with_listener_ipv6 (zeroconf.test.ServiceTypesQuery)
--
Traceback (most recent call last):
  File 
"/build/python-zeroconf-0.25.0/.pybuild/cpython3_3.8/build/zeroconf/test.py", 
line 907, in test_integration_with_listener_ipv6
assert type_ in service_types, service_types
AssertionError: ()

--
Ran 52 tests in 87.246s

FAILED (failures=1, errors=3)
E: pybuild pybuild:352: test: plugin distutils failed with: exit code=1: cd 

Processed: Bug#958034 marked as pending in python-zeroconf

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #958034 [src:python-zeroconf] python-zeroconf: FTBFS: tests fail without 
networking
Added tag(s) pending.

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

Bug#958034: marked as pending in python-zeroconf

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #958034 in python-zeroconf 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/python-team/modules/python-zeroconf/-/commit/d9419216d934c0bf0c7b7607eb3d11730079eded


* Allow the tests to fail, as they do fail in the buildd env because of no
networking, and that's what the package tests. Note that I don't think
there's external connectivity, so it should still be policy compliant.
(Closes: #958034)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/958034

Processed: forcibly merging 960010 960013

[Debian Bug Tracking System]

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

> forcemerge 960010 960013
Bug #960010 [src:freefem++] freefem++: FBTFS (error: multiple definition of 
‘enum CBLAS_SIDE’)
Bug #960010 [src:freefem++] freefem++: FBTFS (error: multiple definition of 
‘enum CBLAS_SIDE’)
Added tag(s) bullseye, ftbfs, and sid.
Bug #960013 [src:freefem++] freefem++: FTBFS with gsl 2.6
959133 was blocked by: 960014 960011 960010
959133 was not blocking any bugs.
Added blocking bug(s) of 959133: 960013
Merged 960010 960013
> thanks
Stopping processing here.

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

Processed: forcibly merging 960011 960014

[Debian Bug Tracking System]

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

> forcemerge 960011 960014
Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported 
version: 2.6 at Build.PL line 80)
Bug #960011 [src:libmath-gsl-perl] libmath-gsl-perl: FBTFS (unsupported 
version: 2.6 at Build.PL line 80)
Added tag(s) ftbfs, sid, and bullseye.
Bug #960014 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS with gsl 2.6
959133 was blocked by: 960011 960010
959133 was not blocking any bugs.
Added blocking bug(s) of 959133: 960014
Merged 960011 960014
> thanks
Stopping processing here.

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

Bug#959973: marked as done (pgcli: does not work due to prompt_toolkit incompatibility)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 10:18:58 +
with message-id 
and subject line Bug#959973: fixed in pgcli 3.0.0-1
has caused the Debian Bug report #959973,
regarding pgcli: does not work due to prompt_toolkit incompatibility
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.)


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

```
borisov@glossy:~ $ pgcli 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 584, in 
_build_master
ws.require(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 901, in 
require
needed = self.resolve(parse_requirements(requirements))
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 792, in 
resolve
raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (prompt-toolkit 3.0.5 
(/usr/lib/python3/dist-packages), 
Requirement.parse('prompt_toolkit<3.0.0,>=2.0.6'), {'pgcli'})

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/pgcli", line 6, in 
from pkg_resources import load_entry_point
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3259, 
in 
def _initialize_master_working_set():
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3242, 
in _call_aside
f(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 3271, 
in _initialize_master_working_set
working_set = WorkingSet._build_master()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 586, in 
_build_master
return cls._build_from_requirements(__requires__)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 599, in 
_build_from_requirements
dists = ws.resolve(reqs, Environment())
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 787, in 
resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'prompt_toolkit<3.0.0,>=2.0.6' 
distribution was not found and is required by pgcli
```

```
borisov@glossy:~ $ sudo aptitude install python3-prompt-toolkit
[sudo] password for borisov:
python3-prompt-toolkit is already installed at the requested version (3.0.5-2)
python3-prompt-toolkit is already installed at the requested version (3.0.5-2)
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
```

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

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

Versions of packages pgcli depends on:
ii  python3 3.8.2-3
ii  python3-click   7.0-3
ii  python3-configobj   5.0.6-4
ii  python3-humanize2.3.0-1
ii  python3-pgspecial   1.9.0-2
ii  python3-pkg-resources   46.1.3-1
ii  python3-prompt-toolkit  3.0.5-2
ii  python3-psycopg22.8.5-1
ii  python3-pygments2.3.1+dfsg-3
ii  python3-setproctitle1.1.10-1+b4
ii  python3-sqlparse0.3.1-1
ii  python3-tabulate0.8.2-1.1
ii  python3-terminaltables  3.1.0-3

pgcli recommends no packages.

pgcli suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pgcli
Source-Version: 3.0.0-1
Done: Lennart Weller 

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

Debian distribution maintenance software
pp.
Lennart Weller  (supplier of updated pgcli package)

(This message was generated automatically at their request; if you
believe that there 

Processed (with 1 error): reassign 952481 to texlive-lang, fixed 952481 in 2019.20200302-1, reassign 950146 to src:enchant-2 ...

[Debian Bug Tracking System]

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

> reassign 952481 texlive-lang 2019.20200218-1
Bug #952481 {Done: Norbert Preining } [texlive-base] 
texlive: mktexpk fails to create tcrm1000
Bug reassigned from package 'texlive-base' to 'texlive-lang'.
No longer marked as found in versions texlive-base/2019.20200218-1.
No longer marked as fixed in versions texlive-lang/2019.20200302-1.
Bug #952481 {Done: Norbert Preining } [texlive-lang] 
texlive: mktexpk fails to create tcrm1000
There is no source info for the package 'texlive-lang' at version 
'2019.20200218-1' with architecture ''
Unable to make a source version for version '2019.20200218-1'
Marked as found in versions 2019.20200218-1.
> fixed 952481 2019.20200302-1
Bug #952481 {Done: Norbert Preining } [texlive-lang] 
texlive: mktexpk fails to create tcrm1000
There is no source info for the package 'texlive-lang' at version 
'2019.20200302-1' with architecture ''
Unable to make a source version for version '2019.20200302-1'
Marked as fixed in versions 2019.20200302-1.
> reassign 950146 src:enchant-2
Bug #950146 {Done: Simon McVittie } [src:enchant] Upgrade 
enchant to minimally 2.2.7
Bug reassigned from package 'src:enchant' to 'src:enchant-2'.
No longer marked as found in versions enchant/1.6.0-11.3.
No longer marked as fixed in versions enchant-2/2.2.7+repack1-1.
> fixed 950146 2.2.7+repack1-1
Bug #950146 {Done: Simon McVittie } [src:enchant-2] Upgrade 
enchant to minimally 2.2.7
Marked as fixed in versions enchant-2/2.2.7+repack1-1.
> notfound 929061 1.13.0-1
Bug #929061 {Done: Daniel Kahn Gillmor } [src:gpgme1.0] 
gpgme1.0: autopkgtest regression: python3.6 dependency
No longer marked as found in versions gpgme1.0/1.13.0-1.
> tags 890171 - buster
Bug #890171 {Done: Debian FTP Masters } 
[src:sushi] sushi: Please switch to python-gobject-2/python-gi
Removed tag(s) buster.
> tags 942618 + sid bullseye
Bug #942618 {Done: Boyuan Yang } [vilistextum] vilistextum: 
Maintainer email address not working
Added tag(s) sid and bullseye.
> notfound 953361 2.22.6+dfsg0-3
Bug #953361 {Done: Thorsten Alteholz } [src:gengetopt] 
gengetopt: FTBFS on i386: test failures
No longer marked as found in versions gengetopt/2.22.6+dfsg0-3.
> found 953361 2.22.6+dfsg0-4
Bug #953361 {Done: Thorsten Alteholz } [src:gengetopt] 
gengetopt: FTBFS on i386: test failures
Marked as found in versions gengetopt/2.22.6+dfsg0-4.
> reassign 940879 src:mariadb-10.4
Bug #940879 {Done: =?utf-8?b?T3R0byBLZWvDpGzDpGluZW4=?= } 
[mariadb-10.3] Link with libedit instead of readline5
Bug reassigned from package 'mariadb-10.3' to 'src:mariadb-10.4'.
Ignoring request to alter found versions of bug #940879 to the same values 
previously set
No longer marked as fixed in versions mariadb-10.4/1:10.4.12-1~exp2.
> fixed 940879 1:10.4.12-1~exp2
Bug #940879 {Done: =?utf-8?b?T3R0byBLZWvDpGzDpGluZW4=?= } 
[src:mariadb-10.4] Link with libedit instead of readline5
Marked as fixed in versions mariadb-10.4/1:10.4.12-1~exp2.
> notfixed 921569 1.6.7-1
Bug #921569 {Done: Antonio Terceiro } 
[python-django-extensions] Please stop suggesting python-keyczar
No longer marked as fixed in versions python-django-extensions/1.6.7-1.
> fixed 921569 2.1.4-2
Bug #921569 {Done: Antonio Terceiro } 
[python-django-extensions] Please stop suggesting python-keyczar
There is no source info for the package 'python-django-extensions' at version 
'2.1.4-2' with architecture ''
Unable to make a source version for version '2.1.4-2'
Marked as fixed in versions 2.1.4-2.
> tags 879035 - buster
Bug #879035 {Done: Debian FTP Masters } 
[src:gourmet] gourmet: port to gir1.2-poppler-0.18
Removed tag(s) buster.
> tags 912962 - buster
Bug #912962 {Done: Debian FTP Masters } 
[obex-data-server] obex-data-server: recommends transitional python-gobject, 
and indirectly, deprecated python-gobject-2
Removed tag(s) buster.
> tags 949822 - bullseye
Failed to alter tags of Bug 949822: Not altering archived bugs; see unarchive.

> tags 890148 - buster
Bug #890148 {Done: Debian FTP Masters } 
[src:gespeaker] gespeaker: Please switch to python-gobject-2/python-gi
Removed tag(s) buster.
> tags 50 =
Bug #50 {Done: Osamu Aoki } [src:debian-history] build 
dep package list needs trimming
Removed tag(s) stretch, wheezy, and jessie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
50: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=50
879035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879035
890148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890148
890171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890171
912962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912962
921569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921569
929061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929061
940879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940879
942618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942618
950146: 

Bug#960014: libmath-gsl-perl: FTBFS with gsl 2.6

[Graham Inggs]

Source: libmath-gsl-perl
Version: 0.40-1
Severity: serious
Tags: ftbfs bullseye sid

Hi Maintainer

In a recent rebuild for the gsl 2.6 transition, libmath-gsl-perl FTBFS
on all architectures [1].
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=libmath-gsl-perl


   dh_auto_configure -a
perl Build.PL --installdirs vendor --config "optimize=-g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2"
--config "ld=x86_64-linux-gnu-gcc -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now"
Checking for GSL using gsl-config
Found GSL 2.6 (via gsl-config) installed in /usr
Checking if x86_64-linux-gnu-gcc supports "-Wall"...yes
Checking if x86_64-linux-gnu-gcc supports "-Wno-sometimes-uninitialized"...yes
Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes
Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-value"...yes
Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes
Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-variable"...yes
Checking if x86_64-linux-gnu-gcc supports "-Wno-gnu"...yes
Checking if x86_64-linux-gnu-gcc supports "-g"...unsupported version:
2.6 at Build.PL line 80.
yes
dh_auto_configure: error: perl Build.PL --installdirs vendor --config
"optimize=-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -Wl,-z,relro -Wl,-z,now" returned
exit code 25

Bug#960013: freefem++: FTBFS with gsl 2.6

[Graham Inggs]

Source: freefem++
Version: 3.61.1+dfsg1-5
Severity: serious
Tags: ftbfs bullseye sid

Hi Maintainer

In a recent rebuild for the gsl 2.6 transition, freefem++ FTBFS on all
architectures.
I 've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=freefem%2B%2B


./ff-c++ -auto MUMPS_seq.cpp
eval ./ff-c++ MUMPS_seq.cpp -ldmumps_seq -lzmumps_seq
-lmumps_common_seq -lpord_seq -lmpiseq_seq -lblas -lmpiseq_seq
/usr/lib/gcc/x86_64-linux-gnu/9/libgfortran.so
/usr/lib/gcc/x86_64-linux-gnu/9/libquadmath.so -DAdd_ -lpthread
g++ -Wl,-z,relro -Wl,--as-needed -c -fPIC -g
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DNDEBUG -O3 -mmmx -mavx
-DBAMG_LONG_LONG -DNCHECKPTR -fPIC -g
-fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DNDEBUG -O3 -mmmx -mavx
-DBAMG_LONG_LONG -DNCHECKPTR -fPIC -Wdate-time -D_FORTIFY_SOURCE=2
-I./include '-DAdd_' 'MUMPS_seq.cpp'
In file included from /usr/include/gsl/gsl_blas_types.h:28,
 from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
 from /usr/include/gsl/gsl_matrix.h:4,
 from /usr/include/gsl/gsl_eigen.h:24,
 from /usr/include/gsl/gsl_sf_mathieu.h:26,
 from /usr/include/gsl/gsl_sf.h:31,
 from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:46:6: error: multiple definition of ‘enum
CBLAS_ORDER’
   46 | enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102};
  |  ^~~
In file included from ./include/MatriceCreuse_tpl.hpp:19,
 from ./include/ff++.hpp:32,
 from gsl.cpp:30:
/usr/include/x86_64-linux-gnu/cblas.h:49:14: note: previous definition here
   49 | typedef enum CBLAS_ORDER {CblasRowMajor=101,
CblasColMajor=102} CBLAS_ORDER;
  |  ^~~
In file included from /usr/include/gsl/gsl_blas_types.h:28,
 from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
 from /usr/include/gsl/gsl_matrix.h:4,
 from /usr/include/gsl/gsl_eigen.h:24,
 from /usr/include/gsl/gsl_sf_mathieu.h:26,
 from /usr/include/gsl/gsl_sf.h:31,
 from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:47:6: error: multiple definition of ‘enum
CBLAS_TRANSPOSE’
   47 | enum CBLAS_TRANSPOSE {CblasNoTrans=111, CblasTrans=112,
CblasConjTrans=113};
  |  ^~~
In file included from ./include/MatriceCreuse_tpl.hpp:19,
 from ./include/ff++.hpp:32,
 from gsl.cpp:30:
/usr/include/x86_64-linux-gnu/cblas.h:50:14: note: previous definition here
   50 | typedef enum CBLAS_TRANSPOSE {CblasNoTrans=111,
CblasTrans=112, CblasConjTrans=113, CblasConjNoTrans=114}
CBLAS_TRANSPOSE;
  |  ^~~
In file included from /usr/include/gsl/gsl_blas_types.h:28,
 from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
 from /usr/include/gsl/gsl_matrix.h:4,
 from /usr/include/gsl/gsl_eigen.h:24,
 from /usr/include/gsl/gsl_sf_mathieu.h:26,
 from /usr/include/gsl/gsl_sf.h:31,
 from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:48:6: error: multiple definition of ‘enum
CBLAS_UPLO’
   48 | enum CBLAS_UPLO {CblasUpper=121, CblasLower=122};
  |  ^~
In file included from ./include/MatriceCreuse_tpl.hpp:19,
 from ./include/ff++.hpp:32,
 from gsl.cpp:30:
/usr/include/x86_64-linux-gnu/cblas.h:51:14: note: previous definition here
   51 | typedef enum CBLAS_UPLO  {CblasUpper=121, CblasLower=122}
CBLAS_UPLO;
  |  ^~
In file included from /usr/include/gsl/gsl_blas_types.h:28,
 from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
 from /usr/include/gsl/gsl_matrix.h:4,
 from /usr/include/gsl/gsl_eigen.h:24,
 from /usr/include/gsl/gsl_sf_mathieu.h:26,
 from /usr/include/gsl/gsl_sf.h:31,
 from gsl.cpp:32:
/usr/include/gsl/gsl_cblas.h:49:6: error: multiple definition of ‘enum
CBLAS_DIAG’
   49 | enum CBLAS_DIAG {CblasNonUnit=131, CblasUnit=132};
  |  ^~
In file included from ./include/MatriceCreuse_tpl.hpp:19,
 from ./include/ff++.hpp:32,
 from gsl.cpp:30:
/usr/include/x86_64-linux-gnu/cblas.h:52:14: note: previous definition here
   52 | typedef enum CBLAS_DIAG  {CblasNonUnit=131, CblasUnit=132}
CBLAS_DIAG;
  |  ^~
In file included from /usr/include/gsl/gsl_blas_types.h:28,
 from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
 from /usr/include/gsl/gsl_matrix.h:4,
 from /usr/include/gsl/gsl_eigen.h:24,
 from /usr/include/gsl/gsl_sf_mathieu.h:26,
 from 

Bug#960011: libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80)

[Bas Couwenberg]

Source: libmath-gsl-perl
Version: 0.40-1
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 959133 by -1

Dear Maintainer,

Your package FTBFS during the gsl transition:

 dh build-arch
dh_update_autotools_config -a
dh_autoreconf -a
dh_auto_configure -a
perl Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now"
 Checking for GSL using gsl-config
 Found GSL 2.6 (via gsl-config) installed in /usr
 Checking if x86_64-linux-gnu-gcc supports "-Wall"...yes
 Checking if x86_64-linux-gnu-gcc supports "-Wno-sometimes-uninitialized"...yes
 Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes
 Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-value"...yes
 Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-function"...yes
 Checking if x86_64-linux-gnu-gcc supports "-Wno-unused-variable"...yes
 Checking if x86_64-linux-gnu-gcc supports "-Wno-gnu"...yes
 Checking if x86_64-linux-gnu-gcc supports "-g"...unsupported version: 2.6 at 
Build.PL line 80.
 yes
 dh_auto_configure: error: perl Build.PL --installdirs vendor --config 
"optimize=-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro 
-Wl,-z,now" returned exit code 25
 make: *** [debian/rules:9: build-arch] Error 25
 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

https://buildd.debian.org/status/fetch.php?pkg=libmath-gsl-perl=amd64=0.40-1%2Bb2=1588896435=0

Kind Regards,

Bas

Processed: libmath-gsl-perl: FBTFS (unsupported version: 2.6 at Build.PL line 80)

[Debian Bug Tracking System]

Processing control commands:

> block 959133 by -1
Bug #959133 [release.debian.org] release.debian.org: Transition for gsl
959133 was blocked by: 960010
959133 was not blocking any bugs.
Added blocking bug(s) of 959133: 960011

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

Processed: freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’)

[Debian Bug Tracking System]

Processing control commands:

> block 959133 by -1
Bug #959133 [release.debian.org] release.debian.org: Transition for gsl
959133 was not blocked by any bugs.
959133 was not blocking any bugs.
Added blocking bug(s) of 959133: 960010

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

Bug#960010: freefem++: FBTFS (error: multiple definition of ‘enum CBLAS_SIDE’)

[Bas Couwenberg]

Source: freefem++
Version: 3.61.1+dfsg1-5
Severity: serious
Justification: makes the package in question unusable or mostly so
Control: block 959133 by -1

Dear Maintainer,

Your package FTBFS during the gsl transition.

The builog shows many errors like this:

 In file included from /usr/include/gsl/gsl_blas_types.h:28,
  from /usr/include/gsl/gsl_matrix_complex_long_double.h:29,
  from /usr/include/gsl/gsl_matrix.h:4,
  from /usr/include/gsl/gsl_eigen.h:24,
  from /usr/include/gsl/gsl_sf_mathieu.h:26,
  from /usr/include/gsl/gsl_sf.h:31,
  from gsl.cpp:32:
 /usr/include/gsl/gsl_cblas.h:46:6: error: multiple definition of ‘enum 
CBLAS_ORDER’
46 | enum CBLAS_ORDER {CblasRowMajor=101, CblasColMajor=102};
   |  ^~~

https://buildd.debian.org/status/fetch.php?pkg=freefem%2B%2B=amd64=3.61.1%2Bdfsg1-5%2Bb3=1588901371=0

Kind Regards,

Bas

Bug#932779: lirc: Fails to install due to missing /etc/lirc/lirc_options.conf

[Sebastien Bacher]

The package has been broken by the 5.1 and 5.2 SRUs, Ccing Nicolas and
Tobias who did those changes.

* The package before -5.1 were handling those conffiles by doing

debian/rules

    # Don't overwrite existing config files.
    for f in lircd.conf lircmd.conf irexec.lircrc lirc_options.conf; do \
        mv debian/tmp/etc/lirc/$$f debian/tmp/etc/lirc/$$f.dist; \
    done

debian/postinst

for f in lircd.conf lircmd.conf irexec.lircrc lirc_options.conf; do
    test -e /etc/lirc/$f || cp /etc/lirc/${f}.dist /etc/lirc/$f || :
done

The special handling seems to come from the fact that the format changed
from old lirc versions


* Nicolas in -5.1 replaces the special handling by restoring them as
conffiles and removed the postinst/rules hacks and added a .maintscript

* Tobias did another SRU in -5.2 removing the .maintscript to avoid
conffile prompts and restored the debian/rules hack renoming those
.conf, but he didn't restore the postinst snippet than assured the files
existed on new installations, leading to configurations files not
existing and lircd segfaulting


There are a few possible options there now that I can see
- restore the .postinst 'test -e /etc/lirc/$f || cp /etc/lirc/${f}.dist
/etc/lirc/$f || :' calls
- reverse the logic, and ship the conffile with the normal name but move
old existing pre 0.10 ones to .old or something in the preinst
- restore the 'prompt for conffile change even when no change' bug, it's
not ideal but better than just segfaulting and failing installation


Thoughts?

Cheers,
Sebastien Bacher

Bug#937769: uploaded ripe-atlas, beaker

[Gordon Ball]

I've [team-]uploaded beaker and ripe-atlas-cousteau, and filed bugs
against kombu and pagure (on the basis that they are both have recent
activity). They've been added as blockers to this bug.

Apart from python-oslo.* changes already in experimental, I think that
means all the reverse[-build]-depends are now either already uploaded or
have bugs filed.

Bug#939826: marked as done (bustle: ftbfs with new cabal)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 09:03:55 +
with message-id 
and subject line Bug#939826: fixed in bustle 0.7.5-2
has caused the Debian Bug report #939826,
regarding bustle: ftbfs with new cabal
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.)


-- 
939826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bustle
Version: 0.7.5-1
Severity: serious
Forwarded: https://gitlab.freedesktop.org/bustle/bustle/issues/13

Bustle FTBFS with new cabal, I updated to the latest release, but something is 
still missing

G.
--- End Message ---
--- Begin Message ---
Source: bustle
Source-Version: 0.7.5-2
Done: Gianfranco Costamagna 

We believe that the bug you reported is fixed in the latest version of
bustle, which is due to be installed in the Debian FTP archive.

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated bustle 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 08 May 2020 10:52:24 +0200
Source: bustle
Binary: bustle bustle-pcap
Architecture: source
Version: 0.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Gianfranco Costamagna 
Description:
 bustle - D-Bus activity visualiser
 bustle-pcap - D-Bus traffic capture tool for the pcap format
Closes: 939826
Changes:
 bustle (0.7.5-2) unstable; urgency=medium
 .
   * Add upstream patches to make it build without gettext support
 (From NixOS) (Closes: #939826)
 - debian/patches/ee4b81cbc232d47ba9940f198b17452e71ff.patch:
 - debian/patches/aae6843f51f54679d440fb3813e61355dc8406b9.patch:
Checksums-Sha1:
 a6fbedfdd5639ac1b4ed136fffbad53f4f426698 2247 bustle_0.7.5-2.dsc
 9dc21a945fed1d8ddf3246bc23d38c7ac33fbd3e 6580 bustle_0.7.5-2.debian.tar.xz
 a2c6a46286dcc64f1ce34538350b9242d43519c9 9411 bustle_0.7.5-2_source.buildinfo
Checksums-Sha256:
 458a8438fd34be19b08a94f6e1966147ec6e19fe8f67c464ae57f5f0b75705b2 2247 
bustle_0.7.5-2.dsc
 739c4b52a2b2d51ba32eedde910a440b52aa1e9d2de8382dd32a7cfca49a44ed 6580 
bustle_0.7.5-2.debian.tar.xz
 863cadcb11c94cdc0a6974002116331a849cac10c2105ad41815eaf854e343e1 9411 
bustle_0.7.5-2_source.buildinfo
Files:
 49193ac3ab430cacfe92f0efedbc5fee 2247 devel optional bustle_0.7.5-2.dsc
 9bd7a7d30b8cb92629a755176ab1813d 6580 devel optional 
bustle_0.7.5-2.debian.tar.xz
 cea7c73ef55f2599b81f9c9e567197d1 9411 devel optional 
bustle_0.7.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl61HiwACgkQ808JdE6f
XdnDbhAAoFFp/tEO5EEjQ+VWJr0YtfmRrRlSXGUc2WaxDWqdxYGSQpaci3qbNnE/
CACtEQPsB/nGqHFgfw/AwcHVJdu+vPtgYkEEawBKnJYqpuEmAMhow5aIZ0ZvfAwt
Rssqb8ukPolpi0gpdpO/SFwVm/KOhwm9P1tHtdP4ErGm2XSwxNk+x6qLnPJBnRP1
ptsvhMusWbFywOToVuagTDBpnPiKnM++StZ2fUwQKmSH+GOQRQx9abZ1Ue5FgU8k
+QRYaWxoC91yHF85+/l4YB0ZwV2Gj0HX53FFQBHEGtPbGOHMBGllPCP5OtSkp8Aq
GZfjDBvCIVYfsm0OBT073eg0X/Bpw8ZccVlLT6sfToi2sl8T3sgavy4tIpkIseNs
mNVSHa8ckXfGwFXKr2T73s5LeHRLO/1/Lz6lZW8X6lpFOefiW4dfDAEqqcUb3YZp
WYsRu+WgD0L4NyFYju++yjj8pRK394VZH95pE2JCbc1+2DAoWFRHt1y2ud0gAYd6
ANq+CcLgVv2SsZkiKJrHkx+CB3zOkMbdb2mic8/IvZYTrymaOlAFjULNld38/Abn
hsETAFXY0v6a/akA0HBh5hpMf6Eyr0xNMH3gzjMtJAOQIe7rRNIFqzKySIhekZql
GMhUabXrSBOx6NqVXgGr1bQaTSlaZkut4e0yK7lGbsTbst4m8nU=
=6Och
-END PGP SIGNATURE End Message ---

Bug#958577: Uploaded fix to delay/2

[Thomas Goirand]

Hi,

Since nobody seem to care, I uploaded the fix to delay/2:

--- a/debian/control
+++ b/debian/control
@@ -19,7 +19,7 @@

 Package: python3-docker
 Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends}
+Depends: python3-distutils, ${misc:Depends}, ${python3:Depends}
 Description: Python 3 wrapper to access docker.io's control socket
  This package contains oodles of routines that aid in controlling
  docker.io over it's socket control, the same way the docker.io

Cheers,

Thomas Goirand (zigo)

Bug#956276: marked as done (runescape: downloads unverified binary and runs it)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 08:39:54 +
with message-id 
and subject line Bug#956276: fixed in runescape 0.8-1
has caused the Debian Bug report #956276,
regarding runescape: downloads unverified binary and runs it
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.)


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

Hi,

It seems runescape downloads a binary and runs it, without verifying its
integrity. At least the download happens using https, but no other
verification is done.

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: runescape
Source-Version: 0.8-1
Done: Carlos Donizete Froes 

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

Debian distribution maintenance software
pp.
Carlos Donizete Froes  (supplier of updated runescape 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Apr 2020 18:24:34 -0300
Source: runescape
Architecture: source
Version: 0.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Carlos Donizete Froes 
Closes: 956275 956276
Changes:
 runescape (0.8-1) unstable; urgency=medium
 .
   * New upstream release:
 - New redistributable icon, generated by the author (Closes: #956275);
 - Verify the download against a known hash, and warn the user about the
   purpose of the launcher (Closes: #956276).
   * debian/control:
 + Added in Depends: kdialog | zenity, java10-runtime, p7zip-full.
 - Removed in Build-Depends: default-jdk-headless | default-jdk.
 - Removed in Depends: default-jre-headless.
 + Long description with more details improved.
   * Added debian/docs.
   * debian/tests/control:
 + Added in Depends: kdialog | zenity, java10-runtime, p7zip-full.
 - Removed in Depends: default-jre-headless.
   * debian/watch: Fixed the requested URL in the uscan information.
Checksums-Sha1:
 230a34786d0aeca7430cb658211f26e0b0194145 2285 runescape_0.8-1.dsc
 bd25032fbe89bf0b7e03518645c24fe20eba279f 71185 runescape_0.8.orig.tar.bz2
 4c4b29f947c4e7b0801959d3f2931ca4acb9fca3 833 runescape_0.8.orig.tar.bz2.asc
 e95150373bcc99316c9252721b8a9966fbd48833 13316 runescape_0.8-1.debian.tar.xz
 6e4b6fe0497f1280e51b8f9e05d50b67a2a34edb 5805 runescape_0.8-1_source.buildinfo
Checksums-Sha256:
 697428158af70f64b6a566eb91f75725c385c35e087861c6e83e93f416bb627c 2285 
runescape_0.8-1.dsc
 0f1c409071cb81f061e1c536c1f8cda3a1c9be2a813cf7dc23d85a2815f6668c 71185 
runescape_0.8.orig.tar.bz2
 f76c65b76ab66ba758ad6492b4bba5f3742eac89029baada8eb82e2b1abdc383 833 
runescape_0.8.orig.tar.bz2.asc
 8ec2cf4217c92c19fbd56c64fa80fe0266d312410a9414cfe64900adc7f484c4 13316 
runescape_0.8-1.debian.tar.xz
 7148c1800893904541d8cd27dcc3ba6c1b5cc08577f88db8f49ddef372421d64 5805 
runescape_0.8-1_source.buildinfo
Files:
 d3bc1250f094f1416a8787c64fcd96a5 2285 non-free/games optional 
runescape_0.8-1.dsc
 c841c81267dc951040824a6aaa55641b 71185 non-free/games optional 
runescape_0.8.orig.tar.bz2
 4849356e06fe880a0715703ca26eed96 833 non-free/games optional 
runescape_0.8.orig.tar.bz2.asc
 3c0f11bd13ff5bdf2111ddc45f198079 13316 non-free/games optional 
runescape_0.8-1.debian.tar.xz
 568062ef73e853b06dc2ef955903efe8 5805 non-free/games optional 
runescape_0.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl61FCoACgkQgNMC9Yht
g5yHCA/9Ga8YdTmXG83NquSO5zQ+yiqWGef2kbiknbozvVjq6RHasYnRjaMn+kZ/
cC8FJATjf8IlM2XYFSuoOrsIYB9X8cQ3mJYLxOYaXOW8Nu3iB+xqHN55ciVt0XNN
ZFTUcDldRH1IZNSIj6kUu3k9kkjnTl9M7NOcVOsHQ3hMj08o1dK8+XVe43ZzwZO5
1Sx1w7Ni2Yb/yIgKLnwkzUQ/cFkmTbLV+IanvB9AHZRgBoCEdeB4mFlsFDf2Fd3u
/7wXLRVVnd4qiEQjnzWJMDyGyOqsf0suc+CiRCFyOtnOney1RIzWF6De2f8B3KIx
jKoyXblw5/bG79pTtLGz/owC7x6qCTCIXLl/FtJTbKRWwaU4iBmaDGhlrdXiva7G
joPsjAUwrxNjwYxRd8035y233/rJCL1ztWY07p7ogV/bmWsU+/1v1L8F0e/1/VS8
57v11AOwIlzw52ZURt6UzAefn1Wf/6Vq2dZLuXAd+UWYbjLZvZyHFUXxXf6JTmmg

Bug#956275: marked as done (runescape: license issue - runscape.png probably undistributable)

[Debian Bug Tracking System]

Your message dated Fri, 08 May 2020 08:39:54 +
with message-id 
and subject line Bug#956275: fixed in runescape 0.8-1
has caused the Debian Bug report #956275,
regarding runescape: license issue - runscape.png probably undistributable
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.)


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

Hi,

Runescape contains this file: src/runescape.png

The copyright file lists this as 'BSD-2-Clause'. What is this based on?

The term and conditions on the website (which are mentioned in
src/runschape.sh, but not in the copyright file), certainly are not BSD. So
the copyright file is wrong. I suspect it doesn't even allow distributing
runescape.png. If you think it does, please clarify why you think so in the
copyright file.

Also, it would be good to clarify (both in the copyright file and in the
package description) that this package only contains a download script that
downloads the game from the website and runs that, but doesn't contain the
actual game.

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: runescape
Source-Version: 0.8-1
Done: Carlos Donizete Froes 

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

Debian distribution maintenance software
pp.
Carlos Donizete Froes  (supplier of updated runescape 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 21 Apr 2020 18:24:34 -0300
Source: runescape
Architecture: source
Version: 0.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Carlos Donizete Froes 
Closes: 956275 956276
Changes:
 runescape (0.8-1) unstable; urgency=medium
 .
   * New upstream release:
 - New redistributable icon, generated by the author (Closes: #956275);
 - Verify the download against a known hash, and warn the user about the
   purpose of the launcher (Closes: #956276).
   * debian/control:
 + Added in Depends: kdialog | zenity, java10-runtime, p7zip-full.
 - Removed in Build-Depends: default-jdk-headless | default-jdk.
 - Removed in Depends: default-jre-headless.
 + Long description with more details improved.
   * Added debian/docs.
   * debian/tests/control:
 + Added in Depends: kdialog | zenity, java10-runtime, p7zip-full.
 - Removed in Depends: default-jre-headless.
   * debian/watch: Fixed the requested URL in the uscan information.
Checksums-Sha1:
 230a34786d0aeca7430cb658211f26e0b0194145 2285 runescape_0.8-1.dsc
 bd25032fbe89bf0b7e03518645c24fe20eba279f 71185 runescape_0.8.orig.tar.bz2
 4c4b29f947c4e7b0801959d3f2931ca4acb9fca3 833 runescape_0.8.orig.tar.bz2.asc
 e95150373bcc99316c9252721b8a9966fbd48833 13316 runescape_0.8-1.debian.tar.xz
 6e4b6fe0497f1280e51b8f9e05d50b67a2a34edb 5805 runescape_0.8-1_source.buildinfo
Checksums-Sha256:
 697428158af70f64b6a566eb91f75725c385c35e087861c6e83e93f416bb627c 2285 
runescape_0.8-1.dsc
 0f1c409071cb81f061e1c536c1f8cda3a1c9be2a813cf7dc23d85a2815f6668c 71185 
runescape_0.8.orig.tar.bz2
 f76c65b76ab66ba758ad6492b4bba5f3742eac89029baada8eb82e2b1abdc383 833 
runescape_0.8.orig.tar.bz2.asc
 8ec2cf4217c92c19fbd56c64fa80fe0266d312410a9414cfe64900adc7f484c4 13316 
runescape_0.8-1.debian.tar.xz
 7148c1800893904541d8cd27dcc3ba6c1b5cc08577f88db8f49ddef372421d64 5805 
runescape_0.8-1_source.buildinfo
Files:
 d3bc1250f094f1416a8787c64fcd96a5 2285 non-free/games optional 
runescape_0.8-1.dsc
 c841c81267dc951040824a6aaa55641b 71185 non-free/games optional 
runescape_0.8.orig.tar.bz2
 4849356e06fe880a0715703ca26eed96 833 non-free/games optional 
runescape_0.8.orig.tar.bz2.asc
 3c0f11bd13ff5bdf2111ddc45f198079 13316 non-free/games optional 
runescape_0.8-1.debian.tar.xz
 568062ef73e853b06dc2ef955903efe8 5805 non-free/games optional 
runescape_0.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAl61FCoACgkQgNMC9Yht
g5yHCA/9Ga8YdTmXG83NquSO5zQ+yiqWGef2kbiknbozvVjq6RHasYnRjaMn+kZ/

Processed: tagging 959801, notfound 959889 in 0.5.0, found 959889 in 0.5.0-1, found 912504 in 3.1-3.3 ...

[Debian Bug Tracking System]

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

> tags 959801 + sid
Bug #959801 {Done: Debian FTP Masters } 
[src:ropemode] ropemode: Consider removing it from Debian
Added tag(s) sid.
> notfound 959889 0.5.0
Bug #959889 {Done: Sandro Tosi } [sphinx-gallery] 
python3-sphinx-gallery: AttributeError: 'URLError' object has no attribute 'url'
There is no source info for the package 'sphinx-gallery' at version '0.5.0' 
with architecture ''
Unable to make a source version for version '0.5.0'
No longer marked as found in versions 0.5.0.
> found 959889 0.5.0-1
Bug #959889 {Done: Sandro Tosi } [sphinx-gallery] 
python3-sphinx-gallery: AttributeError: 'URLError' object has no attribute 'url'
There is no source info for the package 'sphinx-gallery' at version '0.5.0-1' 
with architecture ''
Unable to make a source version for version '0.5.0-1'
Marked as found in versions 0.5.0-1.
> found 912504 3.1-3.3
Bug #912504 [src:pysycache] pysycache: Please migrate to python3-pygame
Marked as found in versions pysycache/3.1-3.3.
> tags 912504 + sid bullseye
Bug #912504 [src:pysycache] pysycache: Please migrate to python3-pygame
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: affects 904742, tagging 872215, tagging 872113, tagging 872208

[Debian Bug Tracking System]

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

> affects 904742 + sat-xmpp-jp
Bug #904742 [jp] jp: name conflict of /usr/bin/jp with sat-xmpp-jp
Bug #954443 [jp] jp: name conflict of /usr/bin/jp with sat-xmpp-jp
Added indication that 904742 affects sat-xmpp-jp
Added indication that 954443 affects sat-xmpp-jp
> tags 872215 + sid bullseye
Bug #872215 [src:sosreport] sosreport: fdisk dependency needed
Added tag(s) bullseye and sid.
> tags 872113 - buster
Bug #872113 [src:waagent] waagent: fdisk dependency needed
Removed tag(s) buster.
> tags 872208 + sid bullseye
Bug #872208 [src:opensvc] opensvc: fdisk dependency needed
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

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

Processed: block kombu funcsigs

[Debian Bug Tracking System]

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

> block 937769 by 960002
Bug #937769 [src:python-funcsigs] python-funcsigs: Python2 removal in 
sid/bullseye
937769 was blocked by: 937144 959934 937558 937926 943135
937769 was blocking: 937695 938168 938756
Added blocking bug(s) of 937769: 960002
>
End of message, stopping processing here.

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

Bug#955535: httping: diff for NMU version 2.5-5.1

[Adrian Bunk]

Control: tags 955535 + patch
Control: tags 955535 + pending

Dear maintainer,

I've prepared an NMU for httping (versioned as 2.5-5.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru httping-2.5/debian/changelog httping-2.5/debian/changelog
--- httping-2.5/debian/changelog	2018-11-20 12:32:29.0 +0200
+++ httping-2.5/debian/changelog	2020-05-08 09:30:50.0 +0300
@@ -1,3 +1,11 @@
+httping (2.5-5.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Add needs-internet restrictions to autopkgtest. (Closes: #955535)
+  * Remove unnecessary test depends.
+
+ -- Adrian Bunk   Fri, 08 May 2020 09:30:50 +0300
+
 httping (2.5-5) unstable; urgency=medium
 
   * debian/tests/control: update the depends for ci.debian.net
diff -Nru httping-2.5/debian/tests/control httping-2.5/debian/tests/control
--- httping-2.5/debian/tests/control	2018-11-20 12:32:29.0 +0200
+++ httping-2.5/debian/tests/control	2020-05-08 09:30:50.0 +0300
@@ -3,10 +3,10 @@
 Restrictions: allow-stderr
 
 Test-Command: httping -c 2 https://debian.org
-Depends: @, openssl
-Restrictions: allow-stderr
+Depends: @
+Restrictions: allow-stderr, needs-internet
 
 Test-Command: httping -F -c 4 http://google.com
-Depends: @, @builddeps@
-Restrictions: allow-stderr
+Depends: @
+Restrictions: allow-stderr, needs-internet
 

Processed: httping: diff for NMU version 2.5-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 955535 + patch
Bug #955535 [src:httping] httping: flaky autopkgtest: PING google.com:80
Added tag(s) patch.
> tags 955535 + pending
Bug #955535 [src:httping] httping: flaky autopkgtest: PING google.com:80
Added tag(s) pending.

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

Processed: tagging 936153

[Debian Bug Tracking System]

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

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

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

Processed: tagging 938036

[Debian Bug Tracking System]

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

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

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