Bug#974551: linphone: missing build-dependency on python-pystache

[Ralf Treinen]

Source: linphone
Version: 3.12.0-3.1
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

linphone build-depends on python-pystache. However, sid has only
python3-pystache.

-Ralf.

Processed: Re: Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libcharls-dev needs Breaks: libdcmtk-dev (<< 3.6.5-1~)
Bug #974544 [libcharls-dev] libcharls-dev needs Breaks+Replaces: libdcmtk-dev 
(<< 3.6.5-1~)
Changed Bug title to 'libcharls-dev needs Breaks: libdcmtk-dev (<< 3.6.5-1~)' 
from 'libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)'.

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

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

[Matthijs]

Unfortunately, my machine crashed again last night. No special activity, no 
stressing things going on - just full 100% standstill.

Nothing visible in either syslog or kern.log. On screen just the regular login 
prompt (no GUI, just terminal login) but the cursor was absent and the system 
didn't react to keyboard.

So, also unfortunately, no error log or crash information at all. So don't know 
if the crashes I experience are in any way related to this kernel bug #968335

Any suggestions how I can get any further information out of this system in 
future crashes?

Kind regards,
Matthijs

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Mathieu Malaterre]

Control: retitle -1 libcharls-dev needs Breaks: libdcmtk-dev (<< 3.6.5-1~)

On Thu, Nov 12, 2020 at 8:13 AM Adrian Bunk  wrote:
>
> On Thu, Nov 12, 2020 at 08:09:11AM +0100, Mathieu Malaterre wrote:
> > On Thu, Nov 12, 2020 at 8:06 AM Adrian Bunk  wrote:
> > >
> > > Control: reopen -1
> > >
> > > On Thu, Nov 12, 2020 at 08:02:07AM +0100, Mathieu Malaterre wrote:
> > > > Control: fixed -1 2.1.0+dfsg-7
> > > >
> > > > https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/control#L22
> > > >
> > > > dcmtk 3.6.5 ships a convenient copy of CharLS with SOVERSION=1, while
> > > > libcharls-dev is SOVERSION=2, so I'll not add the Replaces.
> > >
> > > The conflict is on the unversioned libcharls.so symlink.
> >
> > Could you confirm you saw that dcmtk 3.6.5-1 does *not* ship
> > libcharls.so anymore ?
>
> https://buildd.debian.org/status/logs.php?pkg=odin=2.0.4-0.2%2Bb1=amd64

OK, I understand the issue now.

Thanks

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Adrian Bunk]

On Thu, Nov 12, 2020 at 08:09:11AM +0100, Mathieu Malaterre wrote:
> On Thu, Nov 12, 2020 at 8:06 AM Adrian Bunk  wrote:
> >
> > Control: reopen -1
> >
> > On Thu, Nov 12, 2020 at 08:02:07AM +0100, Mathieu Malaterre wrote:
> > > Control: fixed -1 2.1.0+dfsg-7
> > >
> > > https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/control#L22
> > >
> > > dcmtk 3.6.5 ships a convenient copy of CharLS with SOVERSION=1, while
> > > libcharls-dev is SOVERSION=2, so I'll not add the Replaces.
> >
> > The conflict is on the unversioned libcharls.so symlink.
> 
> Could you confirm you saw that dcmtk 3.6.5-1 does *not* ship
> libcharls.so anymore ?

https://buildd.debian.org/status/logs.php?pkg=odin=2.0.4-0.2%2Bb1=amd64

> Thanks for your help

cu
Adrian

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Mathieu Malaterre]

On Thu, Nov 12, 2020 at 8:06 AM Adrian Bunk  wrote:
>
> Control: reopen -1
>
> On Thu, Nov 12, 2020 at 08:02:07AM +0100, Mathieu Malaterre wrote:
> > Control: fixed -1 2.1.0+dfsg-7
> >
> > https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/control#L22
> >
> > dcmtk 3.6.5 ships a convenient copy of CharLS with SOVERSION=1, while
> > libcharls-dev is SOVERSION=2, so I'll not add the Replaces.
>
> The conflict is on the unversioned libcharls.so symlink.

Could you confirm you saw that dcmtk 3.6.5-1 does *not* ship
libcharls.so anymore ?

Thanks for your help

Processed: Re: Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #974544 {Done: Mathieu Malaterre } [libcharls-dev] 
libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions charls/2.1.0+dfsg-7.

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

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Adrian Bunk]

Control: reopen -1

On Thu, Nov 12, 2020 at 08:02:07AM +0100, Mathieu Malaterre wrote:
> Control: fixed -1 2.1.0+dfsg-7
> 
> https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/control#L22
> 
> dcmtk 3.6.5 ships a convenient copy of CharLS with SOVERSION=1, while
> libcharls-dev is SOVERSION=2, so I'll not add the Replaces.

The conflict is on the unversioned libcharls.so symlink.

cu
Adrian

Processed: Re: Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 2.1.0+dfsg-7
Bug #974544 [libcharls-dev] libcharls-dev needs Breaks+Replaces: libdcmtk-dev 
(<< 3.6.5-1~)
Marked as fixed in versions charls/2.1.0+dfsg-7.

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

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Mathieu Malaterre]

Control: fixed -1 2.1.0+dfsg-7

https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/control#L22

dcmtk 3.6.5 ships a convenient copy of CharLS with SOVERSION=1, while
libcharls-dev is SOVERSION=2, so I'll not add the Replaces.

Bug#974544: marked as done (libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~))

[Debian Bug Tracking System]

Your message dated Thu, 12 Nov 2020 08:02:07 +0100
with message-id 

and subject line Re: Bug#974544: libcharls-dev needs Breaks+Replaces: 
libdcmtk-dev (<< 3.6.5-1~)
has caused the Debian Bug report #974544,
regarding libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)
to be marked as done.

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

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


-- 
974544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcharls-dev
Version: 2.1.0+dfsg-6
Severity: serious

See #973723.
--- End Message ---
--- Begin Message ---
Control: fixed -1 2.1.0+dfsg-7

https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/control#L22

dcmtk 3.6.5 ships a convenient copy of CharLS with SOVERSION=1, while
libcharls-dev is SOVERSION=2, so I'll not add the Replaces.--- End Message ---

Processed: severity of 959550 is normal

[Debian Bug Tracking System]

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

> severity 959550 normal
Bug #959550 [src:dask.distributed] dask.distributed: FTBFS: dh_sphinxdoc: 
error: 
debian/python-distributed-doc/usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js
 is missing
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#974543: Acknowledgement (segmentation fault on launch)

[Mika Hanhijärvi]

I am able to work around this problem on Debian Buster by adding the line:

|imports.gi.versions.GtkSource = "3.0";|


to the beginning of the file:

|
|

|/usr/share/sushi/js/viewers/text.js|

|
|

Bug#974107: Segfault when running isenkram-lookup

[Gunnar Hjalmarsson]

Attached please find the stdout from Ubuntu's autopkgtest when running 
the test-command-line script in amd64.


--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj


test-command-line-stdout.gz
Description: application/gzip

Bug#974037: Fails to build on mipsel

[Adrian Bunk]

Control: severity -1 important
Control: tags -1 ftbfs

On Mon, Nov 09, 2020 at 11:40:14AM +0100, Guido Günther wrote:
> Package: src:rust-gtk
> Version: 0.7.0-1
> Severity: serious

It is not RC when the package was never built on an architecture.

> rust-gtk fails to build on mipsel like:
> 
> https://buildd.debian.org/status/fetch.php?pkg=rust-gtk=mipsel=0.7.0-1=1596355821=0
> 
> The relevant bit seems to be
> 
> terminate called after throwing an instance of 'std::bad_alloc'
>  what():  std::bad_alloc
> error: could not compile `gtk`.
> 
> So i wonder if that can be handled by a give back on a machine with more
> RAM?

The buildds where it was tried have either 4 GB or 8 GB RAM.
Which is not the problem when you are running out of address space.

Address space available for a program (like a compiler instance)
on the 32bit release architectures:
2 GB mipsel
3 GB armel/armhf
4 GB i386 built on amd64

With g++ the most common workaround is building with -g1,
I don't have experience how to work around excessive memory
usage in rust.

> Cheers,
>  -- Guido

cu
Adrian

Processed: Re: Bug#974037: Fails to build on mipsel

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #974037 [src:rust-gtk] Fails to build on mipsel
Severity set to 'important' from 'serious'
> tags -1 ftbfs
Bug #974037 [src:rust-gtk] Fails to build on mipsel
Added tag(s) ftbfs.

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

Bug#971521: marked as done (varnish-modules: autopkgtest needs update for new version of varnish: Depends on old ABI)

[Debian Bug Tracking System]

Your message dated Thu, 12 Nov 2020 05:48:31 +
with message-id 
and subject line Bug#971142: fixed in varnish-modules 0.16.0-2.1
has caused the Debian Bug report #971142,
regarding varnish-modules: autopkgtest needs update for new version of varnish: 
Depends on old ABI
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.)


-- 
971142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: varnish-modules
Version: 0.16.0-2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, varn...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:varnish

Dear maintainer(s),

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

   passfail
varnishfrom testing6.5.1-1
varnish-modulesfrom testing0.16.0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. I'm not sure
if varnish-modules just need a rebuild, or if there need to be more changes.

Currently this regression is blocking the migration of varnish to
testing [1]. Please fix the situation.

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

https://ci.debian.net/data/autopkgtest/testing/amd64/v/varnish-modules/7232545/log.gz

Investigating (0) varnish-modules:amd64 < none -> 0.16.0-2 @un puN Ib >
Broken varnish-modules:amd64 Depends on libvarnishapi2:amd64 < none |
6.5.1-1 @un uH > (>= 6.1.0)
  Considering libvarnishapi2:amd64 0 as a solution to
varnish-modules:amd64 
  Re-Instated libvarnishapi2:amd64



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: varnish-modules
Source-Version: 0.16.0-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated varnish-modules 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, 10 Nov 2020 10:21:35 +0200
Source: varnish-modules
Architecture: source
Version: 0.16.0-2.1
Distribution: unstable
Urgency: low
Maintainer: Varnish Package Maintainers 
Changed-By: Adrian Bunk 
Closes: 971142
Changes:
 varnish-modules (0.16.0-2.1) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Backport upstream fix for FTBFS with Varnish 6.5.
 (Closes: #971142)
Checksums-Sha1:
 f44aa6c0f04b77efb2dbf33db37b0631dfbb630f 2214 varnish-modules_0.16.0-2.1.dsc
 9fa6ad02e2d15816340805c30f7fc82d6297e077 6424 
varnish-modules_0.16.0-2.1.debian.tar.xz
Checksums-Sha256:
 a4e845507773efc59cde101fcbe36473fd81bbfd622cabf5bcfee7d8718890ca 2214 
varnish-modules_0.16.0-2.1.dsc
 adb6f63f8089aa55efa892c6f2527fef5468538d1ae583a2a7b206306af3829e 6424 
varnish-modules_0.16.0-2.1.debian.tar.xz
Files:
 f1d40c5b665d93d90d2cffea1cd740c5 2214 web optional 
varnish-modules_0.16.0-2.1.dsc
 69af7576f2c72e35c98b2fe0f9ca6e20 6424 web optional 
varnish-modules_0.16.0-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl+qjXsACgkQiNJCh6LY
mLHV0Q//S+usx+Vraa1cf8vXc3iCbnu0phuSIKi1e53ttW41kFcbmKteNGeBeLLF
mM5Lo2KPRWGrWTTTmuojKYcy5t6xKA2a06jwjQno1iqk4E5QFgdmeBp2kWlo6T5i
SM+ZWEbOj0+oC2mCH3uydHa01osQwP/arGf6nNBOWOGhAYCIzUHeqfMxjPMuEtt+
CtcnhPyjNiqtgaVSRLnf9g4qjIVuEz6URX4SrE9lGtHPHAgz5ZYVJrFBt+ZnVEch
kC8CX9LhHoOVzywfyZv4dhJPCQYztHM9yxKucerhi70J8BRLY2kKph6BsE48GEvA
8stTbHKXh2SxCT/om/KsgQobk5TjRjIrhtaGpL/QJVI5h4cyzDdLCAR41YH6u8W8
56Qj1MuzMd8mFTullNMW8O5Cvr4bHRTMqj35Bvc7ABrurxbYH864u5bA2QMUNuBt
XMcdxtKkLyqXwaChyqptP48zOnZ+uhE5nCAd9ri5SPULqALsPAvnvV1cZK0Ik8ET

Bug#971142: marked as done (varnish-modules: FTBFS: vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Thu, 12 Nov 2020 05:48:31 +
with message-id 
and subject line Bug#971142: fixed in varnish-modules 0.16.0-2.1
has caused the Debian Bug report #971142,
regarding varnish-modules: FTBFS: vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ 
is deprecated [-Werror=deprecated-declarations]
to be marked as done.

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

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


-- 
971142: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971142
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: varnish-modules
Version: 0.16.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200926 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
>  -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/varnish  -I../src/foreign 
> -Wall -Werror -Wall -Wno-format-y2k -Wstrict-prototypes -Wmissing-prototypes 
> -Werror=missing-field-initializers -Wpointer-arith -Wreturn-type 
> -Wwrite-strings -Wcast-qual -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
> -Wchar-subscripts -Wnested-externs -Wextra -Wno-sign-compare -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o vmod_bodyaccess.lo vmod_bodyaccess.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/varnish -I../src/foreign -Wall -Werror 
> -Wall -Wno-format-y2k -Wstrict-prototypes -Wmissing-prototypes 
> -Werror=missing-field-initializers -Wpointer-arith -Wreturn-type 
> -Wwrite-strings -Wcast-qual -Wswitch -Wshadow -Wunused-parameter -Wcast-align 
> -Wchar-subscripts -Wnested-externs -Wextra -Wno-sign-compare -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -c vmod_bodyaccess.c  -fPIC -DPIC -o 
> .libs/vmod_bodyaccess.o
> vmod_bodyaccess.c: In function ‘vmod_hash_req_body’:
> vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated 
> [-Werror=deprecated-declarations]
>   205 |  VSB_delete(vsb);
>   |  ^~
> In file included from /usr/include/varnish/cache/cache_varnishd.h:36,
>  from vmod_bodyaccess.c:37:
> /usr/include/varnish/vsb.h:79:8: note: declared here
>79 | void   VSB_delete(struct vsb *) v_deprecated_;
>   |^~
> vmod_bodyaccess.c: In function ‘vmod_rematch_req_body’:
> vmod_bodyaccess.c:278:2: error: ‘VSB_delete’ is deprecated 
> [-Werror=deprecated-declarations]
>   278 |  VSB_delete(vsb);
>   |  ^~
> In file included from /usr/include/varnish/cache/cache_varnishd.h:36,
>  from vmod_bodyaccess.c:37:
> /usr/include/varnish/vsb.h:79:8: note: declared here
>79 | void   VSB_delete(struct vsb *) v_deprecated_;
>   |^~
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:917: vmod_bodyaccess.lo] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/09/26/varnish-modules_0.16.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: varnish-modules
Source-Version: 0.16.0-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated varnish-modules 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, 10 Nov 2020 10:21:35 +0200
Source: varnish-modules
Architecture: source
Version: 0.16.0-2.1
Distribution: unstable
Urgency: low
Maintainer: Varnish Package Maintainers 
Changed-By: Adrian Bunk 
Closes: 971142
Changes:
 varnish-modules (0.16.0-2.1) unstable; 

Bug#971142: varnish-modules: diff for NMU version 0.16.0-2.1

[Adrian Bunk]

On Wed, Nov 11, 2020 at 11:02:24AM +0100, Stig Sandbeck Mathisen wrote:
> Adrian Bunk  writes:
> 
> > Control: tags 971142 + pending
> >
> > Dear maintainer,
> >
> > I've prepared an NMU for varnish-modules (versioned as 0.16.0-2.1) and
> > uploaded it to DELAYED/14. Please feel free to tell me if I should
> > cancel it.
> 
> Hello Adrian,

Hi Stig,

> Thank you for taking the time to do a package upload with a patch for
> this bug. Feel free to leave in the delayed queue, or upload immediately
> if you have the time.

thanks, rescheduled for immediate upload.

cu
Adrian

Bug#974546: klatexformula FTBFS: error: invalid use of incomplete type ‘class QPainterPath’

[Helmut Grohne]

Source: klatexformula
Version: 4.0.0-4
Severity: serious
Tags: ftbfs

klatexformula fails to build from source in unstable:

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

Bug#974545: fraqtive FTBFS: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined

[Helmut Grohne]

Source: fraqtive
Version: 0.4.8-11
Severity: serious
Tags: ftbfs

fraqtive fails to build from source in unstable:

| g++ -c -pipe -g -Wall -Wextra -D_REENTRANT -fPIC -DHAVE_SSE2 -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I. 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I../tmp -I../tmp 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
../tmp/debug/configurationdata.o configurationdata.cpp
| configurationdata.cpp: In member function ‘bool 
ConfigurationData::checkAccess(const QString&)’:
| configurationdata.cpp:183:70: warning: ‘QStringList QString::split(QChar, 
QString::SplitBehavior, Qt::CaseSensitivity) const’ is deprecated: Use 
Qt::SplitBehavior variant instead [-Wdeprecated-declarations]
|   183 | QStringList pathParts = path.split( '/', QString::SkipEmptyParts 
);
|   |  ^
| In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qhashfunctions.h:44,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:47,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/qvariant.h:45,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QVariant:1,
|  from configurationdata.h:22,
|  from configurationdata.cpp:19:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:610:17: note: declared here
|   610 | QStringList split(QChar sep, SplitBehavior behavior,
|   | ^
| g++ -c -pipe -g -Wall -Wextra -D_REENTRANT -fPIC -DHAVE_SSE2 -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_XML_LIB -DQT_CORE_LIB -I. -I. 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I../tmp -I../tmp 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
../tmp/debug/datafunctions.o datafunctions.cpp
| datafunctions.cpp: In function ‘QPolygonF 
DataFunctions::interpolateCubic(const QPolygonF&)’:
| datafunctions.cpp:128:26: error: aggregate ‘QPainterPath path’ has incomplete 
type and cannot be defined
|   128 | QPainterPath path;
|   |  ^~~~
| make[2]: *** [Makefile:1161: ../tmp/debug/datafunctions.o] Error 1
| make[2]: Leaving directory '/<>/src'
| make[1]: *** [Makefile:47: sub-src-make_first] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:16: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

This seems to be recent and caused by some other package being updated.

Helmut

Bug#973939: closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#973939: fixed in ismrmrd 1.4.2.1-3)

[Adrian Bunk]

Control: reopen -1

On Wed, Nov 11, 2020 at 11:33:06AM +, Debian Bug Tracking System wrote:
>...
>  ismrmrd (1.4.2.1-3) unstable; urgency=medium
>...
>* Fix binary-all FTBFS
>  Closes: #973939
>...

Unfortunately this did not work:
https://buildd.debian.org/status/fetch.php?pkg=ismrmrd=all=1.4.2.1-3=1605091989=0

cu
Adrian

Processed: Re: Bug#973939 closed by Debian FTP Masters (reply to Andreas Tille ) (Bug#973939: fixed in ismrmrd 1.4.2.1-3)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #973939 {Done: Andreas Tille } [src:ismrmrd] ismrmrd: 
binary-all FTBFS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ismrmrd/1.4.2.1-3.

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

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

[Adrian Bunk]

Package: libcharls-dev
Version: 2.1.0+dfsg-6
Severity: serious

See #973723.

Bug#974543: segmentation fault on launch

[Mika Hanhijärvi]

Package: gnome-sushi
Version: 3.30.0-2
Severity: grave

Hello

Sushi does not seem to work on Debian Buster. If I select e.g. some mp3 file in
Nautilus filemanager and press the space bar then nothing happens. The same
happens if I select file of some other type. I also get this error in the
/var/log/syslog

Nov 12 06:16:13 miksuh-laptop kernel: [10482.886638] sushi-start[11917]:
segfault at 0 ip 7ff7a1aaf64f sp 7ffe20adb3c0 error 6 in
libgjs.so.0.0.0[7ff7a1a75000+67000]
Nov 12 06:16:13 miksuh-laptop kernel: [10482.886648] Code: 00 e8 a5 7c fc ff 4c
8b 04 24 48 8d 0d 5d 41 03 00 48 8b 7c 24 18 89 c6 31 d2 31 c0 e8 4a 9e fc ff
48 8b 7b 18 e8 11 8e fc ff <41> c7 07 01 00 00 00 e9 82 00 00 00 0f 1f 44 00 00
48 8b bb 78 01

When I try to launch sushi from the command line it segfaults with the followin
error:

Gjs-Message: 06:06:08.541: JS WARNING: [/usr/share/sushi/js/viewers/text.js
26]: Requiring Gdk but it has 2 versions available; use imports.gi.versions to
pick one
Gjs-Message: 06:06:08.563: JS WARNING: [/usr/share/sushi/js/viewers/text.js
30]: Requiring GtkSource but it has 2 versions available; use
imports.gi.versions to pick one

(sushi-start:11595): Gjs-WARNING **: 06:06:08.564: JS ERROR: Error: Requiring
Sushi, version none: Requiring namespace 'GtkSource' version '3.0', but '4' is
already loaded
@/usr/share/sushi/js/viewers/text.js:33:7

Segmentation fault


This seems to be the same bug as reported upstream here:

https://gitlab.gnome.org/GNOME/sushi/-/issues/12






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

Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_CRAP
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), 
LANGUAGE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-sushi depends on:
ii  gir1.2-clutter-1.0  1.26.2+dfsg-10
ii  gir1.2-clutter-gst-3.0  3.0.26-2
ii  gir1.2-evince-3.0   3.30.2-3+deb10u1
ii  gir1.2-gdkpixbuf-2.02.38.1+dfsg-1
ii  gir1.2-glib-2.0 1.58.3-2
ii  gir1.2-gst-plugins-base-1.0 1.14.4-2
ii  gir1.2-gstreamer-1.01.14.4-1
ii  gir1.2-gtk-3.0  3.24.5-1
ii  gir1.2-gtkclutter-1.0   1.8.4-4
ii  gir1.2-gtksource-3.03.24.9-2
ii  gir1.2-pango-1.01.42.4-8~deb10u1
ii  gir1.2-webkit2-4.0  2.28.4-1~deb10u1
ii  gstreamer1.0-plugins-good   1.14.4-1
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4
ii  libclutter-1.0-01.26.2+dfsg-10
ii  libclutter-gst-3.0-03.0.26-2
ii  libclutter-gtk-1.0-01.8.4-4
ii  libevdocument3-43.30.2-3+deb10u1
ii  libevview3-33.30.2-3+deb10u1
ii  libfreetype62.9.1-3+deb10u2
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libgirepository-1.0-1   1.58.3-2
ii  libgjs0g1.54.3-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgstreamer-plugins-base1.0-0  1.14.4-2
ii  libgstreamer1.0-0   1.14.4-1
ii  libgtk-3-0  3.24.5-1
ii  libgtksourceview-3.0-1  3.24.9-2
ii  libharfbuzz0b   2.3.1-1
ii  libmusicbrainz5-2   5.1.0+git20150707-9
ii  libpango-1.0-0  1.42.4-8~deb10u1
ii  libpangocairo-1.0-0 1.42.4-8~deb10u1
ii  libx11-62:1.6.7-1+deb10u1
ii  nautilus3.30.5-2

gnome-sushi recommends no packages.

Versions of packages gnome-sushi suggests:
ii  gstreamer1.0-libav  1.15.0.1+git20180723+db823502-2

-- no debconf information

Bug#974428: in.telnetd crashes on running Nessus security scan

[parameswaran krishnamurthy]

The same crash is observed in the following package too.

package: telnetd-ssl
version: 0.17.41+0.2-3.2+b1

Bug#973639: marked as done (libgromacs6: missing Breaks+Replaces: libgromacs5)

[Debian Bug Tracking System]

Your message dated Thu, 12 Nov 2020 02:38:09 +
with message-id 
and subject line Bug#973639: fixed in gromacs 2021~beta2-1
has caused the Debian Bug report #973639,
regarding libgromacs6: missing Breaks+Replaces: libgromacs5
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.)


-- 
973639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgromacs6
Version: 2021~beta1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../libgromacs6_2021~beta1-1_amd64.deb ...
  Unpacking libgromacs6:amd64 (2021~beta1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgromacs6_2021~beta1-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libgmxapi.so.0.1.0', which is 
also in package libgromacs5:amd64 2020.4-2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libgromacs6_2021~beta1-1_amd64.deb
 
Shared libraries with independent soversions shouldn't be bundled in the same
binary package.


cheers,

Andreas


libgromacs5=2020.4-2_libgromacs6=2021~beta1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gromacs
Source-Version: 2021~beta2-1
Done: Nicholas Breen 

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

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

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

Debian distribution maintenance software
pp.
Nicholas Breen  (supplier of updated gromacs 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: Wed, 11 Nov 2020 16:29:01 -0800
Source: gromacs
Architecture: source
Version: 2021~beta2-1
Distribution: experimental
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Nicholas Breen 
Closes: 973639
Changes:
 gromacs (2021~beta2-1) experimental; urgency=medium
 .
   * New upstream beta release.
 - Remove versioning-for-nblib.patch, incorporated in this release.
 - libnblib SONAME corrected to 0.2.0.  (Closes: #973639)
   * Set GMX_PREFER_STATIC_LIBS=OFF to avoid statically linking zlib in
 the MPI targets.
Checksums-Sha1:
 17bd2164778605583e07f9d19af233a40ef917f1 2648 gromacs_2021~beta2-1.dsc
 d1611c1bcecdcb3f12f1257be8c145093116fa9a 30133767 
gromacs_2021~beta2.orig.tar.gz
 984ca3cb8028722128d06c2a50a9313a2f502d28 38144 
gromacs_2021~beta2-1.debian.tar.xz
 da26eae19629d48608b9591c84e0f30b1b12bc1d 9472 
gromacs_2021~beta2-1_source.buildinfo
Checksums-Sha256:
 431ee5f1d02754b98ef9f02d34dc692d69ff0cd01890c1cd2b4ca1bc67a2bac6 2648 
gromacs_2021~beta2-1.dsc
 9ca2080e72cd87d02e2e72daeb10895b065908de2eea201eac3359fa59f0397e 30133767 
gromacs_2021~beta2.orig.tar.gz
 f3e67a9cc67a811a48a38c0f71d36ba0a05329378c3bb87e6592147dfdbfd859 38144 
gromacs_2021~beta2-1.debian.tar.xz
 ad86c640a88e1e298f8a6aa3f47b4d3e51ad997a8fa4796fc418679ed2863c6a 9472 
gromacs_2021~beta2-1_source.buildinfo
Files:
 0d3cc6d292a6ede6194f19b505c1a5f9 2648 science optional gromacs_2021~beta2-1.dsc
 17a487d9e9a6e454ab196545ec330cb8 30133767 science optional 
gromacs_2021~beta2.orig.tar.gz
 86c8cb529eb0588995f52e7b7da24116 38144 science optional 
gromacs_2021~beta2-1.debian.tar.xz
 982de738620a6b238255a4eca4f2c382 9472 science optional 
gromacs_2021~beta2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCAAwFiEEhD5fph5gYziYdtLl7kr9aexlEI8FAl+smLASHG5icmVlbkBk
ZWJpYW4ub3JnAAoJEO5K/WnsZRCPsC8QAIXnCUR9scGezfbVpM5jheXSxehqvyCa
YRlDQDbbAg4F6EbDZVRJpElkhp8MYZeDFoqrPKY4nb230ZdUdaP0oj+mLRdJN+JH
hM3Kvp5DnfipwGfA93brilWHTHyJGVLj8+CvQ3CCRRvk/JU+mN98bq25p8oG++EO

Bug#958609: marked as done (udevil: Build-Depends on deprecated dh-systemd which is going away)

[Debian Bug Tracking System]

Your message dated Thu, 12 Nov 2020 01:04:52 +
with message-id 
and subject line Bug#958609: fixed in udevil 0.4.4-3
has caused the Debian Bug report #958609,
regarding udevil: Build-Depends on deprecated dh-systemd which is going away
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.)


-- 
958609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958609
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: udevil
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal

Hi,

your package udevil declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transitional package.

For bullseye we intend to drop this empty transitional package.

Once we drop dh-systemd, this bug report will become RC.

Please update your package accordingly. The change should be as simple as
replacing the build dependency on dh-systemd with a build dependency on
debhelper (>= 9.20160709).

Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Source: udevil
Source-Version: 0.4.4-3
Done: =?utf-8?q?Mateusz_=C5=81ukasik?= 

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

Debian distribution maintenance software
pp.
Mateusz Łukasik  (supplier of updated udevil package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 01 Nov 2020 20:28:30 +0100
Source: udevil
Architecture: source
Version: 0.4.4-3
Distribution: unstable
Urgency: medium
Maintainer: Mateusz Łukasik 
Changed-By: Mateusz Łukasik 
Closes: 958609
Changes:
 udevil (0.4.4-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Use secure copyright file specification URI.
   * debian/copyright: use spaces rather than tabs to start continuation
 lines.
   * Depend on newer debhelper (>= 9.20160709) rather than dh-systemd.
 (Closes: #958609)
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Drop unnecessary dh arguments: --with=systemd
 .
   [ Mateusz Łukasik ]
   * Bump dh version to 13 and drop compat file.
   * Bump Standards-Version to 4.5.0. (no changes needed)
Checksums-Sha1:
 7330b450a773199d46d5013f6eabbdc697ccfe39 1856 udevil_0.4.4-3.dsc
 99f28d2e4c224805685df0fd0d880ea9477fbf9c 14636 udevil_0.4.4-3.debian.tar.xz
 f316ff84c6d721f4c88544b17da1158f2aab016d 7414 udevil_0.4.4-3_source.buildinfo
Checksums-Sha256:
 f4a1c94c5ecd4631aad287e7ad574729cc336a92ecb220cf67d10d25d29775bf 1856 
udevil_0.4.4-3.dsc
 66f16c86c0e1f4b70c62a7c9e63f3f28436ebbe32cb78b4bc03fae16b9f25a95 14636 
udevil_0.4.4-3.debian.tar.xz
 4799a2ff55452366775eec02e9b035b17c5fe7974b139734870e689091868f56 7414 
udevil_0.4.4-3_source.buildinfo
Files:
 b71df25fda95e212f96a0666ccd45e04 1856 utils optional udevil_0.4.4-3.dsc
 5fb7f4a77aee6f06c6a569de43482578 14636 utils optional 
udevil_0.4.4-3.debian.tar.xz
 0e2a4aa22838b713d6c796f0eca578df 7414 utils optional 
udevil_0.4.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl+shGwACgkQweDZLphv
fH5GeQ//WwzLvRrb+JOS9hFCJnWE7Amx+aT226yHihsAPlmziWd8VcbwIaVRMgqb
BH37Ww6bFxe/ghHn+rqjUiay03smMsMSjeiK/Oo85SSdZJUya16+/M37InYkGZ9j
s7ViJcYJkCGilGk4X6dLOm9/JfIHEJ9HHpsE7b2cwgQXBHq7cZz6QTnSNLJ+z3Zy
Io8CDwjO5UTTbfqb5DUORE3DLyTlRGBVWOGk84suTEpmkXUHIrAT/7Hji9qLZ48u
NQo01p86OAHduhSI5VgQh+Q82mqK/OLZM69Q4DwzUX79CjoUsXI4H+wOhO161Tnb
FzRw8jX+FMNZ1+a688HYLE3S0Y7avs7CaDut/OtyGmhGNEEK18Om/aavGUlfswv1
ISoLzEUU2b4sDzxNsZ0INw/KY2SmE03sGYsE1MW1xjuVROiADYFrqrpRoP3fPLtY
Llds2zYgYi0py+p8TKo3J08yDKC58fPaCGkcjEHe7aVuDsJHX6NCiaZWIw3YqADc
oFDRUoQY1Lu/z3KYqQTe+Ededc+LgzjNzMTiUk5IE+HcxEZiiLzNouZg0/4m7nD8
WF+A4N2JeEOybvvSGofKleinpQAjjo583LCto+uI++Hg3VU6Ua1C4B93geQC8ymI
2cm8WxoK82swjo99420kLE7NPUkqTJs+rWmK7eLRwWq5mN+rEQs=
=3nhd
-END PGP SIGNATURE End Message ---

Bug#957633: marked as done (openbox-menu: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 12 Nov 2020 01:04:14 +
with message-id 
and subject line Bug#957633: fixed in openbox-menu 0.8.0+hg20161009-2
has caused the Debian Bug report #957633,
regarding openbox-menu: ftbfs with GCC-10
to be marked as done.

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

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


-- 
957633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openbox-menu
Version: 0.8.0+hg20161009-1
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/openbox-menu_0.8.0+hg20161009-1_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from tests/../src/openbox-menu.h:25,
 from tests/context_tests.c:4:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37,
 from /usr/include/gtk-2.0/gtk/gtkwidget.h:36,
 from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35,
 from /usr/include/gtk-2.0/gtk/gtkbin.h:35,
 from /usr/include/gtk-2.0/gtk/gtkwindow.h:36,
 from /usr/include/gtk-2.0/gtk/gtkdialog.h:35,
 from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:33,
 from tests/../src/openbox-menu.h:25,
 from tests/utils_tests.c:6:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  | ^~~~
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:23,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from tests/../src/openbox-menu.h:25,
 from tests/utils_tests.c:6:
/usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here
  679 | {
  | ^
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from tests/../src/openbox-menu.h:25,
 from tests/context_tests.c:4:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: 
Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |   ^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from tests/context_tests.c:1:
/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
In file included from 

Bug#974538:

[Ben Wagner]

It's quite interesting to submit a bug report without a working window
manager, but I think this may be related to the commit
https://salsa.debian.org/qt-kde-team/kde/kscreenlocker/-/commit/2320b40c8d6f3ba316c83a31bdba79dc8db6d208
not listing the symbol
_ZN12ScreenLocker7KSldApp30greeterClientConnectionChangedEvy . I am
not sure if there are any other symbols which might be needed.

Bug#974096: marked as done (golang-github-c-bata-go-prompt: autopkgtest regression: cannot use (type *unix.Termios) as type *syscall.Termios in argument to termios.Tcgetattr)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 21:33:42 +
with message-id 
and subject line Bug#974096: fixed in golang-github-pkg-term 1.1.0-2
has caused the Debian Bug report #974096,
regarding golang-github-c-bata-go-prompt: autopkgtest regression: cannot use 
 (type *unix.Termios) as type *syscall.Termios in argument to 
termios.Tcgetattr
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.)


-- 
974096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-c-bata-go-prompt
Version: 0.2.3+git20181109.b6d2b43-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of golang-github-c-bata-go-prompt the autopkgtest
of golang-github-c-bata-go-prompt fails in testing when that autopkgtest
is run with the binary packages of golang-github-c-bata-go-prompt from
unstable. It passes when run with only packages from testing. In tabular
form:

 passfail
golang-github-c-bata-go-prompt   from testing
   0.2.3+git20181109.b6d2b43-2
all others   from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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=golang-github-c-bata-go-prompt

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-c-bata-go-prompt/8063701/log.gz

autopkgtest [17:45:47]: test dh-golang-autopkgtest: [---
[info] Testing github.com/c-bata/go-prompt...
[info] Source code installed by binary package, overriding
dh_auto_configure...
dh build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--buildsystem=golang
   dh_autoreconf -O--buildsystem=golang
   debian/rules override_dh_auto_configure
make[1]: Entering directory
'/tmp/autopkgtest-lxc.wizha90b/downtmp/autopkgtest_tmp'
mkdir -p "obj-x86_64-linux-gnu"
cp -a /usr/share/gocode/src "obj-x86_64-linux-gnu"
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.wizha90b/downtmp/autopkgtest_tmp'
   dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install -trimpath -v -p 48
github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer
internal/unsafeheader
internal/race
math/bits
unicode/utf8
runtime/internal/sys
golang.org/x/sys/internal/unsafeheader
runtime/cgo
sync/atomic
unicode
internal/cpu
runtime/internal/atomic
runtime/internal/math
internal/bytealg
internal/testlog
math
runtime
internal/reflectlite
sync
errors
sort
internal/oserror
io
strconv
syscall
bytes
strings
reflect
regexp/syntax
internal/syscall/unix
internal/syscall/execenv
time
regexp
internal/poll
internal/fmtsort
encoding/binary
os
golang.org/x/sys/unix
os/signal
github.com/mattn/go-runewidth
path/filepath
fmt
io/ioutil
github.com/pkg/term/termios
log
os/user
github.com/c-bata/go-prompt
# github.com/c-bata/go-prompt
src/github.com/c-bata/go-prompt/input_posix.go:67:45: cannot use
 (type *unix.Termios) as type *syscall.Termios in argument
to termios.Tcgetattr
src/github.com/c-bata/go-prompt/input_posix.go:75:52: cannot use 
(type *unix.Termios) as type *syscall.Termios in argument to
termios.Tcsetattr
src/github.com/c-bata/go-prompt/input_posix.go:83:59: cannot use
 (type *unix.Termios) as type *syscall.Termios in argument
to termios.Tcsetattr
dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v
-p 48 github.com/c-bata/go-prompt github.com/c-bata/go-prompt/completer
returned exit code 2
make: *** [debian/rules:4: build] Error 25
autopkgtest [17:45:52]: test dh-golang-autopkgtest: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-pkg-term
Source-Version: 1.1.0-2
Done: =?utf-8?q?Alo=C3=AFs_Micard?= 

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

Bug#974538: libkscreenlocker5: kwin cannot start due to missing libkscreenunlocker5 symbols

[Ben Wagner]

Package: libkscreenlocker5
Version: 5.19.5-4
Severity: serious
Justification: Policy 8.1
X-Debbugs-Cc: bunge...@chromium.org


$ kwin --replace
kwin: symbol lookup error: /lib/x86_64-linux-gnu/libkwin.so.5: undefined
symbol: _ZN12ScreenLocker7KSldApp30greeterClientConnectionChangedEvy
$ ldd /lib/x86_64-linux-gnu/libkwin.so.5
libKScreenLocker.so.5 => /lib/x86_64-linux-gnu/libKScreenLocker.so.5
(0x7f0adc697000)



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

Kernel: Linux 5.9.0-1-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libkscreenlocker5 depends on:
ii  kpackagetool5  5.74.0-2
ii  libc6  2.31-4
ii  libkf5configcore5  5.74.0-2
ii  libkf5configgui5   5.74.0-2
ii  libkf5coreaddons5  5.74.0-2
ii  libkf5crash5   5.74.0-2
ii  libkf5declarative5 5.74.0-2
ii  libkf5globalaccel-bin  5.74.0-2
ii  libkf5globalaccel5 5.74.0-2
ii  libkf5i18n55.74.0-3
ii  libkf5idletime55.74.0-2
ii  libkf5notifications5   5.74.0-2
ii  libkf5package5 5.74.0-2
ii  libkf5quickaddons5 5.74.0-2
ii  libkf5waylandclient5   4:5.74.0-2
ii  libkf5waylandserver5   4:5.74.0-2
ii  libkf5windowsystem55.74.0-2
ii  libkf5xmlgui5  5.74.0-2+b1
ii  libpam0g   1.3.1-5
ii  libqt5core5a   5.15.1+dfsg-2
ii  libqt5dbus55.15.1+dfsg-2
ii  libqt5gui5 5.15.1+dfsg-2
ii  libqt5network5 5.15.1+dfsg-2
ii  libqt5qml5 5.15.1+dfsg-3
ii  libqt5quick5   5.15.1+dfsg-3
ii  libqt5widgets5 5.15.1+dfsg-2
ii  libqt5x11extras5   5.15.1-2
ii  libseccomp22.4.4-1+b1
ii  libstdc++6 10.2.0-16
ii  libwayland-client0 1.18.0-2~exp1.1
ii  libwayland-server0 1.18.0-2~exp1.1
ii  libx11-6   2:1.6.12-1
ii  libxcb-keysyms10.4.0-1+b2
ii  libxcb11.14-2
ii  libxi6 2:1.7.10-1
ii  psmisc 23.3-1

Versions of packages libkscreenlocker5 recommends:
ii  kde-config-screenlocker  5.19.5-4

libkscreenlocker5 suggests no packages.

-- no debconf information

Bug#944791: marked as done (fst-dev: clashes with libfst-dev: /usr/include/fst/fst.h)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 21:19:13 +
with message-id 
and subject line Bug#944791: fixed in fst 0.115.0-2
has caused the Debian Bug report #944791,
regarding fst-dev: clashes with libfst-dev: /usr/include/fst/fst.h
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.)


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

Hi,

during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.

src:fst (builds fst-dev) and src:openfst (builds libfst-dev) are two
unrelated packages. You probably need to talk to upstream to properly
rename something to avoid this clash.

cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: fst
Source-Version: 0.115.0-2
Done: =?utf-8?q?IOhannes_m_zm=C3=B6lnig_=28Debian/GNU=29?= 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated fst 
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: Wed, 11 Nov 2020 21:57:56 +0100
Source: fst
Architecture: source
Version: 0.115.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 944791
Changes:
 fst (0.115.0-2) unstable; urgency=medium
 .
   * Move fst-headers into pluginterfaces/ (Closes: #944791)
   * Install a pkg-config file
   * Add salsa-ci configuration
   * Bump dh-compat to 13
   * Bump standards version to 4.5.0
Checksums-Sha1:
 b2877f1a5c513533c01d459397664f3f8146f426 2052 fst_0.115.0-2.dsc
 e4ec40290832cd308755ae590fd75c7303a2cca3 2500 fst_0.115.0-2.debian.tar.xz
Checksums-Sha256:
 4110cf14fe50172c4db04a8ba1203329ad5a7d13d04c31a2cea940a94307c2b5 2052 
fst_0.115.0-2.dsc
 37ecc745a04987972804f80bfba855fcdd9b5aa6451791cf7bf04136ff7ad986 2500 
fst_0.115.0-2.debian.tar.xz
Files:
 6e833ffb8ae12f3fb372e48bd99f2780 2052 libdevel optional fst_0.115.0-2.dsc
 9ef0e3a958fb73191225ebef8df91f58 2500 libdevel optional 
fst_0.115.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJKBAEBCAA0FiEEdAXnRVdICXNIABVttlAZxH96NvgFAl+sUQAWHGZvcnVtQHVt
bGFldXRlLm11ci5hdAAKCRC2UBnEf3o2+IvLD/9Un/vMjBTEpaSzZgaLK+1/p1gI
e3xGmFbomIyOxE2j/W4iJ74tsTvqTRTKWabIuE4GhekGgJroz3N14DUqwrFy6uZX
RXKt8ndJNZc7sLvROAClufxtfRCggVLK3A9Ig0KAWB+0WOtwEvz7eNuWncZJ3Cau
KoM/Eb94zPNcyxUYVVBLzT2zetVvKcYiYGOKeC+D/hfG8sZlH5dVGhAENu5S8KrO
aVOOBGn//XBotDpXCMhdv+t5jZTTHJGWMpA1OaztuRMV3VQ/FzmD6jrnGKUe4g0s
tPHBn7TGxQ6mjtRnIk89HfkBQXtwQFmCALzxeI7FzfvAwXxdrNJiLJPj7RhK/F33
pAbD5WrLB2vPDggCnE2U9ter1CdSfPgs0MCs758Nebh0C+ZwAgD5oAWsOO46tBBm
tIwJgEEGI/6Jk1ayOuK7kquwH5TvmBBneP5UqFHqCshTr/rSUgJBygx4me8QTYAp
Ie1vlW7s+EZ/ti2hRP3MA34MbSzwiF8yB2DlKKScMzwqAPL9F4ltccpMNMc4P4as
g1pYshwcMgbM/ZuakvV71/2PjkTsuG5YgfjzLhT+KjpWpQuCluoc+F/l52/sFDor
Qe/SmxE3WQEdcfT+SM+FX+2kp3nrrc6zFkjLGhPkAQkLHCQxY7plKaWOW/Vf1SNN
wr27lDYyWdrPe/y9uA==
=Xxdc
-END PGP SIGNATURE End Message ---

Bug#974104: marked as done (merkaartor FTBFS: error: field ‘thePath’ has incomplete type ‘QPainterPath’)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 21:19:28 +
with message-id 
and subject line Bug#974104: fixed in merkaartor 0.18.4+ds-5
has caused the Debian Bug report #974104,
regarding merkaartor FTBFS: error: field ‘thePath’ has incomplete type 
‘QPainterPath’
to be marked as done.

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

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


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

merkaartor fails to build from source in unstable, A build ends with:

| g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DACCEPT_USE_OF_DEPRECATED_PROJ_API_H -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/gdal -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-DACCEPT_USE_OF_DEPRECATED_PROJ_API_H -Wdate-time -D_FORTIFY_SOURCE=2 
-std=gnu++11 -frtti -Wall -Wextra -Wno-reorder -D_REENTRANT -fPIC 
-DVERSION=0.18.4 -DREVISION=0.18.4-64bit -DPRODUCT=Merkaartor -DUSE_LIBPROXY 
-D_TTY_POSIX_ -DUSE_GPS -DUSE_GPSD_LIB 
-DPLUGINS_DIR=/usr/lib/merkaartor/plugins -DSHARE_DIR=/usr/share/merkaartor 
-DTRANSDIR_MERKAARTOR=/usr/share/merkaartor/translations 
-DTRANSDIR_SYSTEM=/usr/share/qt5/translations/ -DGEOIMAGE -DQT_NO_DEBUG 
-DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_XML_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. 
-I../3rdparty/qtsingleapplication-2.6_1-opensource/src -I. -I../include 
-I../interfaces -Icommon -IBackend -IPaintStyle -IPaintStyle -IFeatures 
-ILayers -IPreferences -ISync -ICommands -IInteractions -IDocks -IQMapControl 
-IImportExport -IRender -Iqextserialport -IGPS -ITools -ITagTemplate 
-INameFinder -IUtils -IQToolBarDialog -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtSvg 
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtConcurrent 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -Irelease -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o release/Global.o 
common/Global.cpp
| In file included from Features/Feature.h:7,
|  from Features/Features.h:2,
|  from Backend/MemoryBackend.h:4,
|  from common/Global.h:19,
|  from common/Global.cpp:13:
| common/Coord.h: In function ‘Coord operator/(const Coord&, qreal)’:
| common/Coord.h:95:41: warning: ‘QTextStream& 
QTextStreamFunctions::endl(QTextStream&)’ is deprecated: Use Qt::endl 
[-Wdeprecated-declarations]
|95 | qDebug()<<"Error: divide by 0"< QList::toSet() const [with T = 
unsigned int]’ is deprecated: Use QSet(list.begin(), list.end()) instead. 
[-Wdeprecated-declarations]
|92 | retList.unite(list.toSet());
|   |  ^
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:52,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtDebug:1,
|  from common/Coord.h:9,
|  from Features/Feature.h:7,
|  from Features/Features.h:2,
|  from Backend/MemoryBackend.h:4,
|  from common/Global.h:19,
|  from common/Global.cpp:13:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qset.h:406:30: note: declared here
|   406 | Q_OUTOFLINE_TEMPLATE QSet QList::toSet() const
|   |  ^~~~
| common/Global.cpp:94:53: warning: ‘QSet QList::toSet() const [with T = 
unsigned int]’ is deprecated: Use QSet(list.begin(), list.end()) instead. 
[-Wdeprecated-declarations]
|94 | retList = tagList[tagKeys.indexOf(k)].toSet();
|   | ^
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qdebug.h:52,
|  from /usr/include/x86_64-linux-gnu/qt5/QtCore/QtDebug:1,
|  from common/Coord.h:9,
|  from Features/Feature.h:7,
|  from Features/Features.h:2,
|  from Backend/MemoryBackend.h:4,
|  from common/Global.h:19,
|  from common/Global.cpp:13:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qset.h:406:30: note: declared here
|   406 | Q_OUTOFLINE_TEMPLATE QSet QList::toSet() const
|   |  ^~~~
| 

Bug#944791: marked as pending in fst

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/multimedia-team/fst/-/commit/104f33ce4cff3e00b2b8a4af5759d644cd19c53e


Move fst-headers into pluginterfaces/

Closes: #944791


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/944791

Processed: Bug#944791 marked as pending in fst

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #944791 [fst-dev] fst-dev: clashes with libfst-dev: /usr/include/fst/fst.h
Added tag(s) pending.

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

Bug#974089: marked as done (colord: FTBFS i386: colord-test-private ABRT)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 20:34:24 +
with message-id 
and subject line Bug#974089: fixed in colord 1.4.5-2
has caused the Debian Bug report #974089,
regarding colord: FTBFS i386: colord-test-private ABRT
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.)


-- 
974089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: colord
Version: 1.4.5-1
Severity: serious
Justification: FTBFS

Dear Maintainer,

colord 1.4.5-1 fails to build from source on (at least) i386.

 Summary of Failures:

 1/4 colord-test-private FAIL   2.94s (killed by signal 6 SIGABRT)

Thanks.

Mark
--- End Message ---
--- Begin Message ---
Source: colord
Source-Version: 1.4.5-2
Done: Christopher James Halse Rogers 

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

Debian distribution maintenance software
pp.
Christopher James Halse Rogers  (supplier of updated colord 
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: Wed, 11 Nov 2020 17:29:01 +1100
Source: colord
Architecture: source
Version: 1.4.5-2
Distribution: unstable
Urgency: medium
Maintainer: Christopher James Halse Rogers 
Changed-By: Christopher James Halse Rogers 
Closes: 974089
Changes:
 colord (1.4.5-2) unstable; urgency=medium
 .
   * debian/patches/fix-float-comparison-in-tests.patch:
 - Don't assert exact floating point equality for the cd_icc_get_version
   tests. Fixes FTBFS on i386 (and hopefully armel & s390x).
   (Closes: #974089)
Checksums-Sha1:
 8d5f1bd9def7b83a61933f9f808c471c876e8c36 3150 colord_1.4.5-2.dsc
 44b9ca5b2ad1df8fe8e9ccd4b1699b940db93fbe 30372 colord_1.4.5-2.debian.tar.xz
 a6b081ba837a134c0ef66e9dcb90e90a29517f9e 10057 colord_1.4.5-2_source.buildinfo
Checksums-Sha256:
 0705ce876295b7f957a581ea4d98d1b508276fcaa77b048a5441ebb811cc23a0 3150 
colord_1.4.5-2.dsc
 af14573ff21da696b4e84cc1eab9b55ab66ddeec7929decebb1b50ba3a839f1d 30372 
colord_1.4.5-2.debian.tar.xz
 5035707fb82e30b2ca388175353f7bc1b81c391a2ec0ff112eb66025e45bf063 10057 
colord_1.4.5-2_source.buildinfo
Files:
 0ae7332cc62caaf86c4a00577ea60811 3150 graphics optional colord_1.4.5-2.dsc
 e8b0c31687a1bc792fed59a5a34353da 30372 graphics optional 
colord_1.4.5-2.debian.tar.xz
 be38cab962479216e036f838b34c524e 10057 graphics optional 
colord_1.4.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEERyS4b0fgKRXe6kniPr1EkD7bBJYFAl+sRiwACgkQPr1EkD7b
BJajcQ//dyNriiqckUIUQIW0CWsm5A7+9eWgus1EIFaN53xrK0jQY5aOK5M1jSGa
tEtI1vgBM/XoAN0tEYFD/992wia1583D2UNFvvSDvNFn2qc7TZSHg681IPfvSmtV
rlAm4Lq6xxE9eew+KiJHNiVk3NuuedA0LzyBfBvEXHWhTRi25JrNCEgqsN8dVOba
QTKB8jAM9DjLmhp8RwpafkmEZl8tAy+j1OxKW365y8ybb4EVtK0tiaS1cfMIeaS/
a0ZZJ8V8pyF9x1e2AStSY8UmVD2Ex+X0P2Aw3LZSVr4M6ofHXXeaETMkKxqLswpR
tAQ667SVLbOyh4Ms48+UeUaPx6OYCWHFzjkII6ALeAVp3ITVpKuKb6R78QTM6oxt
Ot0aLWvej4U7P6owCV5CHj3e3ROal9poc1p18j4BdIdObu/kC3HpS6RXMC7FUSOP
WwZZKYy5qwq5g8qEop+QDfv9BHrayP2HO8D4VmDtDq8jUIXr768CI8kzgswXZmTT
7PPbguyL2wU49UhbEXrRhP6YkpblRK8qIeA/9+ifGFkz0UFLOfyQUB4ZLuoXI3ec
H5gUBQ1Kp7RqV5wF1QukHTgD8K8vtGga1yihCV+D+5l2GIGDhdjJeDGVzC3JJaIR
TZiMgbfbRW1l1zT17kJtY4BTIYvGJ3+Npxc7yycrrgNQUAz0SjE=
=io0m
-END PGP SIGNATURE End Message ---

Bug#973472: fetchmail: Fails to connect using SSL

[Kurt Roeckx]

On Tue, Nov 10, 2020 at 08:54:22PM +0100, László Böszörményi (GCS) wrote:
> On Fri, Nov 6, 2020 at 9:09 AM Michal Palenik  wrote:
> > for those stumbling on this via searching, the workaround mentioned
> > above is:
> [...]
> > apt -t unstable install libssl1.1:amd64
>  Thanks for possibly the best solution. Meanwhile OpenSSL 1.1.1h-1
> migrated to testing; closing this bug report.

That is not a fix. Fetchmail should not be checking the version.

The libssl1.1 package will ensure that the correct versioned
depenencies are there.

There might be cases that an older version than the one you
compiled against might not work, when not using Debian's
dependencies system, but in that case you'll get a linker
error.


Kurt

Processed: reopening 973472

[Debian Bug Tracking System]

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

> reopen 973472
Bug #973472 {Done: László Böszörményi (GCS) } [fetchmail] 
fetchmail: Fails to connect using SSL
Bug #973630 {Done: László Böszörményi (GCS) } [fetchmail] 
fetchmail: OpenSSL library mismatch
Bug reopened
Ignoring request to alter fixed versions of bug #973472 to the same values 
previously set
Ignoring request to alter fixed versions of bug #973630 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#974532: src:libctl: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: libctl
Version: 4.5.0-4
Severity: serious
Control: close -1 4.5.0-5
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 970233

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:libctl 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=libctl




signature.asc
Description: OpenPGP digital signature

Processed: src:libctl: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: ipband: diff for NMU version 0.8.1-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 957369 + patch
Bug #957369 [src:ipband] ipband: ftbfs with GCC-10
Added tag(s) patch.
> tags 957369 + pending
Bug #957369 [src:ipband] ipband: ftbfs with GCC-10
Added tag(s) pending.

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

Bug#957369: ipband: diff for NMU version 0.8.1-5.1

[Sudip Mukherjee]

Control: tags 957369 + patch
Control: tags 957369 + pending
--

Dear maintainer,

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

--
Regards
Sudip

diff -Nru ipband-0.8.1/debian/changelog ipband-0.8.1/debian/changelog
--- ipband-0.8.1/debian/changelog   2016-12-06 14:13:55.0 +
+++ ipband-0.8.1/debian/changelog   2020-11-11 19:11:52.0 +
@@ -1,3 +1,10 @@
+ipband (0.8.1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-10. (Closes: #957369)
+
+ -- Sudip Mukherjee   Wed, 11 Nov 2020 19:11:52 
+
+
 ipband (0.8.1-5) unstable; urgency=low
 
   * Step up to Standards version 3.9.8, no changes.
diff -Nru ipband-0.8.1/debian/patches/07_fix_gcc-10.patch 
ipband-0.8.1/debian/patches/07_fix_gcc-10.patch
--- ipband-0.8.1/debian/patches/07_fix_gcc-10.patch 1970-01-01 
01:00:00.0 +0100
+++ ipband-0.8.1/debian/patches/07_fix_gcc-10.patch 2020-11-11 
19:02:50.0 +
@@ -0,0 +1,123 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee 
+Bug-Debian: https://bugs.debian.org/957369
+Forwarded: no
+
+---
+
+--- ipband-0.8.1.orig/ipband.h
 ipband-0.8.1/ipband.h
+@@ -174,40 +174,40 @@ Global variables
+ extern char pcap_version[];
+ 
+ /* Internal use */
+-intisig_m;/* Interupt flag for capture loop */
+-intpreload_m; /* Subnets are preloaded flag */
+-char   *pcapdev_m;/* Device to listen to */
+-pcap_t *pcapfile_m;   /* Pcap input file descriptor */
+-intpcapoffset_m;  /* IP header offset */
+-time_t started_m; /* Time when we started */
++extern intisig_m; /* Interupt flag for capture 
loop */
++extern intpreload_m;  /* Subnets are preloaded flag */
++extern char   *pcapdev_m; /* Device to listen to */
++extern pcap_t *pcapfile_m;/* Pcap input file descriptor */
++extern intpcapoffset_m;   /* IP header offset */
++extern time_t started_m;  /* Time when we started */
+ 
+-ll_srvc_t *ll_tcp_cache;  /* Resolved tcp services cache */
+-ll_srvc_t *ll_udp_cache;  /* Resolved udp services cache */
++extern ll_srvc_t *ll_tcp_cache;   /* Resolved tcp services cache */
++extern ll_srvc_t *ll_udp_cache;   /* Resolved udp services cache */
+ 
+ 
+ /* Variables holding option values */
+-intdebug_m;   /* Debug option */
+-intdo_html;   /* Generate HTML output */
+-char   *filtercmd_m;  /* Pcap filter string */
+-char   *repfname_m;   /* Subnet report output file */
+-char   *htmlfname_m;  /* HTML report output file */
+-char   *htmltitle_m;  /* HTML Title */
+-intmask_m;/* Network aggregation mask bits */
+-intcycle_m;   /* Number of sec to average data */
+-intrcycle_m;  /* How long in sec bandwidth
++extern intdebug_m;/* Debug option */
++extern intdo_html;/* Generate HTML output */
++extern char   *filtercmd_m;   /* Pcap filter string */
++extern char   *repfname_m;/* Subnet report output file */
++extern char   *htmlfname_m;   /* HTML report output file */
++extern char   *htmltitle_m;   /* HTML Title */
++extern intmask_m; /* Network aggregation mask bits */
++extern intcycle_m;/* Number of sec to average 
data */
++extern intrcycle_m;   /* How long in sec bandwidth
+  threshold may be exceeded */
+-float  thresh_m;  /* Bandwidth threshold in kBps */
+-intfork_m;/* Fork flag */
+-inttop_m; /* No of top connections in report */
+-char   *config_m; /* Config file name */
+-char   *mailto_m; /* E-mail address for reporting */
+-char   *mailfoot_m;   /* Footer file for e-mail report */
+-char   *mtastring_m;  /* MTA command string */
+-intreport_aggr_m; /* Flag to report aggr exceed time */
+-intpromisc_m; /* Use promiscious mode? */
+-int*iplist_m; /* List of local networks */
+-intniplist_m; /* Number of local networks */
+-intlenadj_m;  /* IP packet length adjustment in bytes */
++extern float  thresh_m;   /* Bandwidth threshold in kBps */
++extern intfork_m; /* Fork flag */
++extern inttop_m;  /* No of top connections in report */
++extern char   *config_m;  /* Config file name */
++extern char   *mailto_m;  /* E-mail address for reporting */
++extern char   *mailfoot_m;/* Footer file for e-mail report */
++extern char   *mtastring_m;   /* MTA command string */

Bug#974096: golang-github-c-bata-go-prompt: autopkgtest regression: cannot use (type *unix.Termios) as type *syscall.Termios in argument to termios.Tcgetattr

[Paul Gevers]

Hi Aloïs,

On 10-11-2020 23:31, Aloïs Micard wrote:
> I've now read the documentation here [1].

Hmm, I don't think that page describes your situation. [POLICY] looks
more appropriate.

[POLICY]
https://www.debian.org/doc/debian-policy/ch-relationships.html#packages-which-break-other-packages-breaks

> Just to confirm, does the following changes
> looks goods to you?
> 
> - I'll add the following to d/control of golang-github-pkg-term
> 
> ```
> Breaks: golang-github-c-bata-go-prompt (<<0.2.3+git20181109.b6d2b43-2),
> golang-github-jaguilar-vt100 (<<0.0~git20201024.81de19c-1)
> ```

Yes. Depending on how you support backports or other schemes, you could
add a tilde (~) at the end.

> (the version indicated here are the newest that haven't migrated to
> testing)

I assume you have the right version.

> - And made a new release + upload it to unstable.
> 
> To sum up:
> 
> Is declaring that new version of golang-github-pkg-term breaks
> old version of golang-github-c-bata-go-prompt &
> golang-github-jaguilar-vt100
> enough to make the 3 packages migrate to testing?

If nothing else is broken, yes. The migration software will trigger the
autopkgtests together with such a relation.

Paul

Bug#972070: bluez-obexd: Failure to browse files, Failed to execute program org.bluez.obex: No such file or directory

[Jan]

I noticed the same bug when file transfer via BT would not work anymore. Some 
research brought up a very similar, resolved bug in the Gentoo bug tracker [1]. 
The cause of the problem appears to be a non-working placeholder in the binary 
path of the obex service file 
(/usr/share/dbus-1/services/org.bluez.obex.service):

> Exec=@libexecdir@/obexd

instead of

> Exec=/usr/lib/bluetooth/obexd


[1] https://bugs.gentoo.org/show_bug.cgi?id=698394#c6


Regards, Jan

Processed: closing 973087

[Debian Bug Tracking System]

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

> close 973087 2.4.11-3
Bug #973087 [src:python-fs] python-fs: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.8" --test-pytest 
"--test-args=--ignore tests/test_ftpfs.py" returned exit code 13
Marked as fixed in versions python-fs/2.4.11-3.
Bug #973087 [src:python-fs] python-fs: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.9 3.8" --test-pytest 
"--test-args=--ignore tests/test_ftpfs.py" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#973087: closing 973087

[Michael Hudson-Doyle]

close 973087 2.4.11-3
thanks

I fixed this in version 2.4.11-3 but forgot to include the bug in the
changelog.

Bug#971433: marked as done (libcharls-dev: Problem with latest unstable install)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 18:03:33 +
with message-id 
and subject line Bug#971433: fixed in dcmtk 3.6.5-1
has caused the Debian Bug report #971433,
regarding libcharls-dev: Problem with latest unstable install
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.)


-- 
971433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcharls-dev
Version: 2.0.0+dfsg-1+b1
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


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

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

Versions of packages libcharls-dev depends on:
ii  libcharls2  2.1.0+dfsg-1

libcharls-dev recommends no packages.

libcharls-dev suggests no packages.

-- no debconf information


aife@elektrum:~$ sudo apt --fix-broken install
A ler as listas de pacotes... Pronto
A construir árvore de dependências   
A ler a informação de estado... Pronto
A corrigir dependências... Feito
The following additional packages will be installed:
  libcharls-dev
Serão actualizados os seguintes pacotes:
  libcharls-dev
1 pacotes actualizados, 0 pacotes novos instalados, 0 a remover e 11 não 
actualizados.
1 pacotes não totalmente instalados ou removidos.
É necessário obter 20,0 kB de arquivos.
Após esta operação, serão utilizados 75,8 kB adicionais de espaço em disco.
Deseja continuar? [S/n] 
Obter:1 http://ftp.debian.org/debian sid/main amd64 libcharls-dev amd64 
2.1.0+dfsg-1 [20,0 kB]
Obtidos 20,0 kB em 0s (118 kB/s)
A ler os changelogs... Feito
(A ler a base de dados ... 1744146 ficheiros e directórios actualmente 
instalados.)
A preparar para desempacotar .../libcharls-dev_2.1.0+dfsg-1_amd64.deb ...
A descompactar libcharls-dev:amd64 (2.1.0+dfsg-1) sobre (2.0.0+dfsg-1+b1) ...
dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/libcharls-dev_2.1.0+dfsg-1_amd64.deb (--unpack):
 a tentar sobre-escrever '/usr/lib/x86_64-linux-gnu/libcharls.so', que também 
está no pacote libdcmtk-dev 3.6.4-2.1+b1
Foram encontrados erros enquanto processava:
 /var/cache/apt/archives/libcharls-dev_2.1.0+dfsg-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


/usr/lib/x86_64-linux-gnu/libcharls.so is also present in package  libdcmtk-dev 
3.6.4-2.1+b1 

gives broken install

thx!

Andre
--- End Message ---
--- Begin Message ---
Source: dcmtk
Source-Version: 3.6.5-1
Done: Gert Wollny 

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated dcmtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Nov 2020 15:08:59 +0100
Source: dcmtk
Architecture: source
Version: 3.6.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Closes: 971412 971433
Changes:
 dcmtk (3.6.5-1) unstable; urgency=medium
 .
   * debian/control: switch to comat level 10
   * d/rules: don't install libcharls.so Closes: #971433
 Closes: #971412
   * d/control: cme fix dpkg
   * d/compat: remove obsolete file
Checksums-Sha1:
 fb058ddc73643b657b1970e7884d4d9ce3771d9f 2209 dcmtk_3.6.5-1.dsc
 58c243bb324e6ebca20c0d4f57abdab72916a2dc 29348 dcmtk_3.6.5-1.debian.tar.xz
 9cfa413f0ac0535d540c0a18f11d5d11bc1632ba 8622 

Bug#973723: marked as done (libcharls-dev ships libcharls.so which is also in libdcmtk-dev)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 18:03:33 +
with message-id 
and subject line Bug#971433: fixed in dcmtk 3.6.5-1
has caused the Debian Bug report #971433,
regarding libcharls-dev ships libcharls.so which is also in libdcmtk-dev
to be marked as done.

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

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


-- 
971433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcharls-dev
Version: 2.1.0+dfsg-6
Severity: serious

Unpacking libcharls-dev:amd64 (2.1.0+dfsg-6) over (2.1.0+dfsg-5) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-46o0f4/00-libcharls-dev_2.1.0+dfsg-6_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libcharls.so', which is also in 
package libdcmtk-dev 3.6.4-2.1+b1
--- End Message ---
--- Begin Message ---
Source: dcmtk
Source-Version: 3.6.5-1
Done: Gert Wollny 

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

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated dcmtk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Nov 2020 15:08:59 +0100
Source: dcmtk
Architecture: source
Version: 3.6.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Gert Wollny 
Closes: 971412 971433
Changes:
 dcmtk (3.6.5-1) unstable; urgency=medium
 .
   * debian/control: switch to comat level 10
   * d/rules: don't install libcharls.so Closes: #971433
 Closes: #971412
   * d/control: cme fix dpkg
   * d/compat: remove obsolete file
Checksums-Sha1:
 fb058ddc73643b657b1970e7884d4d9ce3771d9f 2209 dcmtk_3.6.5-1.dsc
 58c243bb324e6ebca20c0d4f57abdab72916a2dc 29348 dcmtk_3.6.5-1.debian.tar.xz
 9cfa413f0ac0535d540c0a18f11d5d11bc1632ba 8622 dcmtk_3.6.5-1_source.buildinfo
Checksums-Sha256:
 1ef6c1fb0e37e3790a98651f327de1e552abd50810f1ac3ff3ce8da8df7c5cad 2209 
dcmtk_3.6.5-1.dsc
 bded759fc99c737b2c9cc3601f4daaf0b227f8ad762d3505b59c5602b8692f3d 29348 
dcmtk_3.6.5-1.debian.tar.xz
 dae7717a57f1bd62729e987c0e17b9b3de7f82de05541520370c7812414c4f35 8622 
dcmtk_3.6.5-1_source.buildinfo
Files:
 5178f740d01c79916044baf279984148 2209 science optional dcmtk_3.6.5-1.dsc
 cb25176d770e9875131d645167cfb979 29348 science optional 
dcmtk_3.6.5-1.debian.tar.xz
 73c401c85ec55886bf545368bc18e50a 8622 science optional 
dcmtk_3.6.5-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEELtRZww6NuKjZPKd6l/LU/KCfME4FAl+sJIYACgkQl/LU/KCf
ME71tw//Vctvr//p7mX/H3nXr+O1FDZ6rQi7eGwFT8ycGB83ablNcxLPmIiV8Ker
ZavmcDqaizjYlqwlc/uQXnV072IgikDj33VCqeSqwhNL6obfPx0imUaM53OIUW3V
gXbSRJDIaVECymS2Bo0KXc7RiohAdP/HcFQpAtSDKSV/QJAot3peEGXH1Patjksb
ygjfz/ZM4sauIQpT/XvksUa5SGxhtiSIowP3jC/xeFV+4FZnq2iTgSVn0Jz0xfCE
20gEaC08ari3RejzaPD7GUQM6Z3KuZaABIXO2ah6VvgXhK4N/9zckkr6brkVVHqj
QDKowH/hpVzOb44pthTy/NCtL+DHLSSDE37625PdcQTmG9LyrLWrwSToYzRiEoN6
+BakTobGq6wVa+pPwSWykYlgnFqk6eaXTwf6KBxtmYkDSsf+AKajdet06W7on8v4
A3B27CQXsvc0rvkmZh5+Us2mUjN0pMPyzwnq4e8D1CepotHcXji3VvS2UYQVmlGh
hqdwxEBo2ygE3Etekcpq6ECkzMy8SEmDOBIdJ+IZ6VB2Irl1z9By6BP7oIBvULKL
xzhobF0LHmQnQwZANfto/hWJaVZ7TQr3nSawn+n9zElbD50JKQ9wD4FBPHKJ/xV/
fKp2sBkH8x2rByZ6wswvrGRgjgZQOhSE31cL+MS1oRXQ4/QSsgM=
=FvuS
-END PGP SIGNATURE End Message ---

Processed: Bug#974430 marked as pending in plasma-workspace

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974430 [plasma-workspace-wayland] plasma-workspace-wayland: Undefined 
symbols: Need rebuild ?
Added tag(s) pending.

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

Bug#974430: marked as pending in plasma-workspace

[Scarlett Gately Moore]

Control: tag -1 pending

Hello,

Bug #974430 in plasma-workspace 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/qt-kde-team/kde/plasma-workspace/-/commit/7c1dddb3c1f1ae1fae5e52c55154a3ca817033ce


Fix "Undefined symbols: Need rebuild ?" tighten dependencies with kwin* 
dependencies. (Closes: #974430)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974430

Processed: Bug#971433 marked as pending in dcmtk

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971433 [src:dcmtk] libcharls-dev: Problem with latest unstable install
Bug #973723 [src:dcmtk] libcharls-dev ships libcharls.so which is also in 
libdcmtk-dev
Added tag(s) pending.
Added tag(s) pending.

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

Bug#971433: marked as pending in dcmtk

[Gert Wollny]

Control: tag -1 pending

Hello,

Bug #971433 in dcmtk 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/med-team/dcmtk/-/commit/d92d18c445d1a28521584ca1e7f3049b3dfad33d


d/rules: don't install libcharls.so Closes: #971433

Signed-off-by: Gert Wollny 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971433

Bug#972070: bluez-obexd: Failure to browse files, Failed to execute program org.bluez.obex: No such file or directory

[Christopher Schramm]

That seems to be the problem here, yes.

Although it was fixed upstream in 5.51 via 
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/obexd/src/obex.service.in?id=78bce480093799c287ac8561b9407fa48796a130, 
the Debian package ships the unreplaced @libexecdir@ in 
/usr/share/dbus-1/services/org.bluez.obex.service as the source package 
patches in its own org.bluez.obex.service.in instead of the up-to-date 
obex.service.in.

Bug#973227: marked as done (dh-cmake: FTBFS: AttributeError: 'Changelog' object has no attribute 'get_version')

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 16:48:47 +
with message-id 
and subject line Bug#973227: fixed in dh-cmake 0.6.1
has caused the Debian Bug report #973227,
regarding dh-cmake: FTBFS: AttributeError: 'Changelog' object has no attribute 
'get_version'
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.)


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

Hi,

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

Relevant part (hopefully):
> dpkg-buildpackage
> -
> 
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package dh-cmake
> dpkg-buildpackage: info: source version 0.6
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Alastair McKinstry 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean  --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 28, in 
> version=debian_version_to_python_version(get_current_version()),
>   File "/<>/setup.py", line 17, in get_current_version
> return str(changelog.get_version())
> AttributeError: 'Changelog' object has no attribute 'get_version'
> E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1: 
> python3.9 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p "3.9 3.8" 
> returned exit code 13
> make: *** [debian/rules:6: clean] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/dh-cmake_0.6_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: dh-cmake
Source-Version: 0.6.1
Done: Alastair McKinstry 

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

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

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated dh-cmake 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: Wed, 11 Nov 2020 16:01:35 +
Source: dh-cmake
Architecture: source
Version: 0.6.1
Distribution: unstable
Urgency: medium
Maintainer: Kitware Debian Maintainers 
Changed-By: Alastair McKinstry 
Closes: 970392 973227
Changes:
 dh-cmake (0.6.1) unstable; urgency=medium
 .
   [ Kyle Edwards ]
   * Use changelog.version in setup.py (closes: #973227)
   * Install README.md in /usr/share/doc/dh-cmake (closes: #970392)
Checksums-Sha1:
 3b10e7dd0ace6653e22703ef940c4743b0b71558 1839 dh-cmake_0.6.1.dsc
 790252bd3b7a97d66021bd3fcf99d33cfb9a6ff9 24304 dh-cmake_0.6.1.tar.xz
Checksums-Sha256:
 43c1aa0c060a0f0b396937f82992deb402c1432af7df5e6cd104a270add22b2a 1839 
dh-cmake_0.6.1.dsc
 45163e834c6d3078e8f1422fd5823bd14e69da3c7d82380c1a04861ec8a88fa3 24304 
dh-cmake_0.6.1.tar.xz
Files:
 1c4c813dd07c447c85efc1204acd51b2 1839 devel optional dh-cmake_0.6.1.dsc
 7d7501369468c9b7005f5b8646dba409 24304 devel optional dh-cmake_0.6.1.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAl+sERUACgkQy+a7Tl2a
06Xdkg//Q6Q7hAc6VVdewsaQ+UegFeCpEbIPvPBy+EWFqajmSNHuG9kCJt31C4tY
oQUUPGebBoQdtwHjdQuy9EbDNWWCmbmiydlzDg2uTqohAg8FHNpl0ioPaORlwn8A
3DsFJkPqLswB2pErENIMZSH6G2H1oG3PLYSvG8n++Dz9q/hfUQj9a4aVzFQFmSDx
GhDOC369KficYL0V7bBoj4avmKJqjq7U9HFYCbg+VDm4bckxdSwYxdMQIsQWUmKp
0Ta4W6eaR/9BtTgMDTPAgzHV3B+riisXkp2m3U2bSRp5se9PYEbYI+32OO4RUKKE
Zz5KSolq3b/0Vy39Q5vTHjnSOW1lbTFFDicliLehfd+zmSFxsu7t4o1G4+FVqIze

Bug#974430: plasma-workspace-wayland: Undefined symbols: Need rebuild ?

[Bastien Roucariès]

Package: plasma-workspace-wayland
Version: 4:5.17.5-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

This package crash. Log contains the following error, that point to a missing
deps or a missing rebuild:
/usr/lib/x86_64-linux-gnu/libkwin.so.5: undefined symbol:
_ZN12ScreenLocker7KSldApp30greeterClientConnectionChangedEv

Thanks



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

Kernel: Linux 5.9.0-1-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-workspace-wayland depends on:
ii  kwayland-integration  5.17.5-3
iu  kwin-wayland  4:5.19.5-3
ii  libc6 2.31-4
ii  libkf5configcore5 5.74.0-2
ii  libqt5core5a  5.15.1+dfsg-2
ii  libqt5dbus5   5.15.1+dfsg-2
ii  libstdc++610.2.0-16
ii  plasma-workspace  4:5.17.5-4
ii  qtwayland55.15.1-3

plasma-workspace-wayland recommends no packages.

plasma-workspace-wayland suggests no packages.

-- no debconf information

Bug#974428: in.telnetd crashes on running Nessus security scan

[parameswaran krishnamurthy]

Package: telnetd
Version: 0.17-41
Severity: serious


Problem Statement:

The in.telnetd process is seen to crash on running Nessus security scan.

in.telnetd version:
telnetd_0.17-41_amd64.deb (Debian stretch image)

/etc/inetd.conf:
telnet  stream  tcp6   nowait  telnetd /usr/sbin/tcpd  /usr/sbin/in.telnetd

Possible root cause:

The telnetd process invokes netflush() to flush() data

root@OS10:# #154080 0x7f681f34a8d9 in _IO_new_do_write (fp=,
data=, to_do=1350) at fileops.c:502
root@OS10:# #154081 0x7f681f348978 in _IO_new_file_sync
(fp=0x55a7d9b45150) at fileops.c:882
root@OS10:# #154082 0x7f681f33e03c in __GI__IO_fflush
(fp=0x55a7d9b45150) at iofflush.c:40
root@OS10:# #154083 0x55a7d97f95a0 in netflush () at utility.c:325
root@OS10:# #154084 0x55a7d97f95d6 in ttloop () at utility.c:81
root@OS10:# #154085 0x55a7d97f5c55 in getterminaltype
(name=0x7ffe09676c70 "") at telnetd.c:484
root@OS10:# #154086 doit (who_len=16, who=0x7ffe09676bf0) at telnetd.c:722
root@OS10:# #154087 main (argc=, argv=, env=) at telnetd.c:402

2)Error is encountered while flushing.This results in invocation of
cleanup function

oot@OS10:# #154071 0x7f681f34c4cc in _IO_flush_all_lockp
(do_lock=do_lock@entry=0) at genops.c:792
root@OS10:# #154072 0x7f681f34c695 in _IO_cleanup () at genops.c:957
root@OS10:# #154073 0x7f681f30c8e3 in __run_exit_handlers
(status=0, listp=, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:96
root@OS10:# #154074 0x7f681f30c99a in __GI_exit (status=) at exit.c:105
root@OS10:# #154075 0x55a7d97f8fd2 in cleanup (sig=sig@entry=0) at
sys_term.c:736
root@OS10:# #154076 0x55a7d97f92d0 in netwritebuf () at utility.c:288
root@OS10:~# #154077 0x55a7d97f94be in netwrite (cookie=,

3)The cleanup function invokes exit(0), which in turn trigger flushing
again. The flushing encounters the error again ,resulting in
continuous loop.

root@OS10:# #154070 0x7f681f34a8d9 in _IO_new_do_write (fp=,
data=, to_do=1350) at fileops.c:502
root@OS10:# #154071 0x7f681f34c4cc in _IO_flush_all_lockp
(do_lock=do_lock@entry=0) at genops.c:792
root@OS10:# #154072 0x7f681f34c695 in _IO_cleanup () at genops.c:957
root@OS10:# #154073 0x7f681f30c8e3 in __run_exit_handlers
(status=0, listp=, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:96
root@OS10:# #154074 0x7f681f30c99a in __GI_exit (status=) at exit.c:105
root@OS10:# #154075 0x55a7d97f8fd2 in cleanup (sig=sig@entry=0) at
sys_term.c:736

Back trace

Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/in.telnetd...Reading symbols from
/usr/lib/debug/.build-id/f7/8762784cef671474d6d52981133d7b47d721a9.debug...done.
done.
[New LWP 14372]
Core was generated by `in.telnetd'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 getutline_r_file (line=0x7ffd5faa11d0, buffer=0x7ffd5faa1350,
result=0x7ffd5faa11b8) at ../login/utmp_file.c:344
344 ../login/utmp_file.c: No such file or directory.
(gdb) bt
#0 getutline_r_file (line=0x7ffd5faa11d0, buffer=0x7ffd5faa1350,
result=0x7ffd5faa11b8) at ../login/utmp_file.c:344
#1 0x7f3154c310e9 in __getutline_r
(line=line@entry=0x7ffd5faa11d0, buffer=buffer@entry=0x7ffd5faa1350,
result=result@entry=0x7ffd5faa11b8) at getutline_r.c:39
#2 0x7f3154eb42b0 in logout (line=line@entry=0x563f3af744a5
"pts/3") at logout.c:45
#3 0x563f39db1fb5 in cleanup (sig=sig@entry=0) at sys_term.c:734
#4 0x563f39db22d0 in netwritebuf () at utility.c:288
#5 0x563f39db24be in netwrite (cookie=,
buf=0x563f3af768f0
"\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374\377\377\374"...,
len=) at utility.c:1250
#6 0x7f3154b7b65e in _IO_cookie_write (fp=0x563f3af72150, buf=,
size=1536) at iofopncook.c:72
#7 0x7f3154b85b62 in new_do_write (fp=0x563f3af72150,
data=0x563f3af762f0

Bug#973216: marked as done (kio-extras: FTBFS: ld: CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10): undefined refe

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 15:19:00 +
with message-id 
and subject line Bug#973216: fixed in kio-extras 4:20.08.3-1
has caused the Debian Bug report #973216,
regarding kio-extras: FTBFS: ld: 
CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10):
 undefined reference to `typeinfo for TagLib::RIFF::AIFF::File'
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.)


-- 
973216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kio-extras
Version: 4:19.12.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:/usr/include/c++/10/bits/stl_function.h:386:
>  more undefined references to 
> `TagLib::ByteVector::operator<(TagLib::ByteVector const&) const' follow
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10):
>  undefined reference to `typeinfo for TagLib::RIFF::AIFF::File'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x20):
>  undefined reference to `TagLib::RIFF::AIFF::File::tag() const'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x28):
>  undefined reference to `TagLib::RIFF::AIFF::File::audioProperties() const'
> /usr/bin/ld: 
> CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTVN6TagLib4RIFF4AIFF7FileExtE[_ZTVN6TagLib4RIFF4AIFF7FileExtE]+0x30):
>  undefined reference to `TagLib::RIFF::AIFF::File::save()'
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/kio-extras_19.12.3-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: kio-extras
Source-Version: 4:20.08.3-1
Done: Pino Toscano 

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

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

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

Debian distribution maintenance software
pp.
Pino Toscano  (supplier of updated kio-extras 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, 11 Nov 2020 16:06:19 +0100
Source: kio-extras
Architecture: source
Version: 4:20.08.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Pino Toscano 
Closes: 960306 973216
Changes:
 kio-extras (4:20.08.3-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Sandro Knauß ]
   * Bump compat level to 13.
   * Add Rules-Requires-Root field to control.
   * New upstream release (20.04.1):
 - fixes CVE-2020-12755 (Closes: #960306)
   * Update build-deps and deps with the info from cmake.
 .
   [ Pino Toscano ]
   * New upstream release:
 - fixes build (Closes: #973216)
   * Update the build dependencies according to the upstream build system:
 - add libtirpc-dev for the NFS kioslave
 - add libkdsoap-dev for the SMB kioslave
   * Remove the explicit as-needed linking, as it is done by binutils now.
   * Re-export upstream signing key without extra signatures.
   * Set field Upstream-Contact in debian/copyright.
   * Remove obsolete fields Contact, Name from debian/upstream/metadata (already
 present in machine-readable debian/copyright).
Checksums-Sha1:
 fbaea79d1d195577b66329610276407a64ff6f96 3275 kio-extras_20.08.3-1.dsc
 

Bug#957354: marked as done (ibutils: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 14:46:46 +
with message-id 
and subject line Bug#957354: fixed in ibutils 1.5.7+0.2.gbd7e502-3
has caused the Debian Bug report #957354,
regarding ibutils: ftbfs with GCC-10
to be marked as done.

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

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


-- 
957354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ibutils
Version: 1.5.7+0.2.gbd7e502-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/ibutils_1.5.7+0.2.gbd7e502-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
  | ^~
ibis_gsi_mad_ctrl.c: In function ‘ibis_gsi_sync_mad_batch_callback’:
ibis_gsi_mad_ctrl.c:843:15: warning: variable ‘p_mad’ set but not used 
[-Wunused-but-set-variable]
  843 | ib_mad_t *p_mad;
  |   ^
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/tcl8.6 -I/usr/include/infiniband -I/usr/include 
-DOSM_VENDOR_INTF_OPENIB -DOSM_BUILD_OPENIB -D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 
-O2 -Wall -fno-strict-aliasing -fPIC -DIBIS_VERSION=\"1.5.7\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ibis_gsi_mad_ctrl.c -o ibis_gsi_mad_ctrl.o 
>/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tcl8.6 -I/usr/include/infiniband 
-I/usr/include  -DOSM_VENDOR_INTF_OPENIB  -DOSM_BUILD_OPENIB 
-D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 -O2 -Wall -fno-strict-aliasing -fPIC 
-DIBIS_VERSION=\"1.5.7\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o ibpm.lo ibpm.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/tcl8.6 -I/usr/include/infiniband -I/usr/include 
-DOSM_VENDOR_INTF_OPENIB -DOSM_BUILD_OPENIB -D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 
-O2 -Wall -fno-strict-aliasing -fPIC -DIBIS_VERSION=\"1.5.7\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ibpm.c  -fPIC -DPIC -o .libs/ibpm.o
In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33,
 from /usr/include/string.h:26,
 from ibpm.c:46:
/usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE 
are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
  185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
_DEFAULT_SOURCE"
  |   ^~~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/tcl8.6 -I/usr/include/infiniband -I/usr/include 
-DOSM_VENDOR_INTF_OPENIB -DOSM_BUILD_OPENIB -D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 
-O2 -Wall -fno-strict-aliasing -fPIC -DIBIS_VERSION=\"1.5.7\" -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ibpm.c -o ibpm.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..   
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tcl8.6 -I/usr/include/infiniband 
-I/usr/include  -DOSM_VENDOR_INTF_OPENIB  -DOSM_BUILD_OPENIB 
-D_XOPEN_SOURCE=600 -D_BSD_SOURCE=1 -O2 -Wall -fno-strict-aliasing -fPIC 
-DIBIS_VERSION=\"1.5.7\" -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o ibsac.lo ibsac.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 

Bug#933928: Where can I find the Python3 port (#29)

[Sophie Abby]

Dear Andreas,

A major release of MacSyFinder (version 2), Python 3 compliant, will be
released in the next few weeks. It's been developed for now on a private
git repo, but soon will be versed to github. We'll come back to you as soon
as it is done!

All the best,

Sophie

On Wed, Nov 11, 2020 at 8:29 AM Andreas Tille 
wrote:

> Any progress here? If we do not get a Python3 port until end of November
> the package will be removed from Debian. :-(
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> ,
> or unsubscribe
> 
> .
>


-- 
Sophie ABBY


-- 
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/gem-pasteur/macsyfinder/issues/29#issuecomment-725313829

Processed: tagging 974211

[Debian Bug Tracking System]

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

> tags 974211 =
Bug #974211 [bash] bash 5.1rc1 emits bracketed paste escape sequences for dumb 
terminals
Removed tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Processed: fixed 974211 in bash/5.1~rc2-1

[Debian Bug Tracking System]

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

> fixed 974211 bash/5.1~rc2-1
Bug #974211 [bash] bash 5.1rc1 emits bracketed paste escape sequences for dumb 
terminals
Marked as fixed in versions bash/5.1~rc2-1.
> thanks
Stopping processing here.

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

Processed: Re: metakernel's autopkg tests fail

[Debian Bug Tracking System]

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

> reassign 974211 bash 5.1~rc1-1
Bug #974211 [src:metakernel] metakernel's autopkg tests fail
Bug reassigned from package 'src:metakernel' to 'bash'.
No longer marked as found in versions metakernel/0.27.4-1.
Ignoring request to alter fixed versions of bug #974211 to the same values 
previously set
Bug #974211 [bash] metakernel's autopkg tests fail
Marked as found in versions bash/5.1~rc1-1.
> retitle 974211 bash 5.1rc1 emits bracketed paste escape sequences for dumb 
> terminals
Bug #974211 [bash] metakernel's autopkg tests fail
Changed Bug title to 'bash 5.1rc1 emits bracketed paste escape sequences for 
dumb terminals' from 'metakernel's autopkg tests fail'.
> notfound 974211 bash/5.1~rc2-1
Bug #974211 [bash] bash 5.1rc1 emits bracketed paste escape sequences for dumb 
terminals
Ignoring request to alter found versions of bug #974211 to the same values 
previously set
> forwarded 974211 
> https://lists.gnu.org/archive/html/bug-bash/2020-11/msg00017.html
Bug #974211 [bash] bash 5.1rc1 emits bracketed paste escape sequences for dumb 
terminals
Set Bug forwarded-to-address to 
'https://lists.gnu.org/archive/html/bug-bash/2020-11/msg00017.html'.
> affects 974211 metakernel
Bug #974211 [bash] bash 5.1rc1 emits bracketed paste escape sequences for dumb 
terminals
Added indication that 974211 affects metakernel
> thanks
Stopping processing here.

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

Bug#974211: metakernel's autopkg tests fail

[Joe Nahmias]

reassign 974211 bash 5.1~rc1-1
retitle 974211 bash 5.1rc1 emits bracketed paste escape sequences for dumb 
terminals
notfound 974211 bash/5.1~rc2-1
forwarded 974211 
https://lists.gnu.org/archive/html/bug-bash/2020-11/msg00017.html
affects 974211 metakernel
thanks

Hello,

Thanks for the report.  This is an issue with bash 5.1~rc1 and was fixed
in bash 5.1~rc2.  I note that it passed in debci when I retried after the
new version of bash migrated to testing:
https://ci.debian.net/data/autopkgtest/testing/amd64/m/metakernel/8078921/log.gz

--Joe

Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"

[Maarten L. Hekkelman]

Hi Juhani,

Bug #974074 is in fact a bug in MRS. However, the bug report does 
contain a useful observation, the usage of the various 
override_dh_auto_configure rules in libzeep is incorrect and no shared 
library is created.


Now the question is, is a shared library really required? If so I will 
have to go back to the drawing board and redesign the makefiles in the 
upstream project to create proper shared libraries, including a version 
numbering scheme.


regards, -maarten


Op 11-11-2020 om 09:13 schreef Juhani Numminen:

On Tue, 10 Nov 2020 23:03:57 +0100 Sebastian Ramacher  
wrote:

Hi Marten

On 2020-11-10 07:42:45 +0100, Maarten L. Hekkelman wrote:
...

Sorry, long story. To make it short.
- Keep mrc, no problem there
- Upgrade libzeep to version 5


Thanks for the detailed explanation. The first two steps are almost done
The current versions of mrc and libzeep should be able to migrate soon
as their RC bugs have been fixed.
...

Right, but one RC bug is not fixed yet: libzeep packages are missing the
shared library altogether; the .so files are not there.

For that we have bug #974074, and see gregor's message for suggested fix.
It seems he is confident in the first diff of that mail, while the latter diff
is more speculative.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974074#19


Regards,
Juhani




--
Maarten L. Hekkelman
Cataloniëstraat 3
6663NJ Lent

http://www.hekkelman.com/
+31 24 348 0192

Bug#970230: freeipa FTBFS on non-nodejs architectures

[Sam Morris]

Package: src:freeipa
Followup-For: Bug #970230
Control: tag -1 + patch

This should let freeipa build on armel again:

$ diff -u debian/rules.old debian/rules
--- debian/rules.old2020-11-11 13:26:32.112603329 +
+++ debian/rules2020-11-11 13:26:37.020620794 +
@@ -99,7 +99,7 @@
-exec sed -i -e '1 s|^#!.*\bpython[^ ]*|#!/usr/bin/python3|' {} \;

 override_dh_missing:
-   dh_missing --fail-missing
+   dh_missing

 ifneq ($(ONLY_CLIENT), 1)
 override_dh_installsystemd:

-- System Information:
Debian Release: 10.6
  APT prefers stable-updates
  APT policy: (535, 'stable-updates'), (535, 'stable'), (520, 'testing'), (510, 
'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-9-686-pae (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Processed: Re: freeipa FTBFS on non-nodejs architectures

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch
Bug #970230 [src:freeipa] freeipa FTBFS on non-nodejs architectures
Added tag(s) patch.

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

Processed: tagging 973216

[Debian Bug Tracking System]

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

> tags 973216 + pending
Bug #973216 [src:kio-extras] kio-extras: FTBFS: ld: 
CMakeFiles/audiothumbnail.dir/audiocreator.cpp.o:(.data.rel.ro._ZTIN6TagLib4RIFF4AIFF7FileExtE[_ZTIN6TagLib4RIFF4AIFF7FileExtE]+0x10):
 undefined reference to `typeinfo for TagLib::RIFF::AIFF::File'
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#957354 marked as pending in ibutils

[Debian Bug Tracking System]

Processing control commands:

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

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

Bug#957354: marked as pending in ibutils

[Benjamin Drung]

Control: tag -1 pending

Hello,

Bug #957354 in ibutils 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/hpc-team/ibutils/-/commit/e7c7a4aa62b91ed37df08383cc46fb4b3b416f1d


Fix build failure with GCC 10

Closes: #957354
Signed-off-by: Benjamin Drung 


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/957354

Processed: Actually execute the commands

[Debian Bug Tracking System]

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

> reassign 965180 libc6
Bug #965180 {Done: Adrian Bunk } [openssh-server] 
openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!
Bug reassigned from package 'openssh-server' to 'libc6'.
No longer marked as found in versions openssh/1:7.9p1-10+deb10u2.
Ignoring request to alter fixed versions of bug #965180 to the same values 
previously set
> unarchive 965932
Bug #965932 {Done: Aurelien Jarno } [libc6] libc6: breaks 
openssh-server/buster
Unarchived Bug 965932
> forcemerge 965932 965180
Bug #965932 {Done: Aurelien Jarno } [libc6] libc6: breaks 
openssh-server/buster
Bug #965180 {Done: Adrian Bunk } [libc6] openssh-server: 
Incompatible with libc6=2.31-1, doesn't allow to login!
Marked as fixed in versions glibc/2.31-2.
Marked as found in versions glibc/2.31-1.
Merged 965180 965932
> thanks
Stopping processing here.

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

Bug#965180: marked as done (openssh-server: Incompatible with libc6=2.31-1, doesn't allow to login!)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 15:02:26 +0200
with message-id <2020130226.GA29935@localhost>
and subject line Re: Bug#965180: openssh-server: Incompatible with 
libc6=2.31-1, doesn't allow to login!
has caused the Debian Bug report #965180,
regarding openssh-server: Incompatible with libc6=2.31-1, doesn't allow to 
login!
to be marked as done.

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

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


-- 
965180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-server
Version: 1:7.9p1-10+deb10u2
Severity: critical
Justification: breaks the whole system


Updating libc on stable breaks sshd; it dies with a SIGSYS on 
clock_nanosleep.

https://www.openssh.com/releasenotes.html says
  - Allow clock_nanosleep() in sandbox (recent glibc) bz3093

and indeed updating openssh-server to 1:8.3p1-1 makes it work again.

Please update OpenSSH on stable!!
--- End Message ---
--- Begin Message ---
Control: reassign -1 libc6
Control: unarchive 965932
Control: forcemerge 965932 -1

On Fri, Jul 17, 2020 at 02:13:52PM +0200, Philipp Marek wrote:
> sorry, my fault.
> 
> I "had to" upgrade ffmpeg at some time in the past;
> 
> i   ffmpegDepends libavformat58 (= 7:4.3-2)
> i A libavformat58 Depends libgnutls30 (>= 3.6.14)
> 
> i   libgnutls30 Depends libc6 (>= 2.25)
> 
> and so I had a newer libc than stable.
> 
> Sorry about the confusion; perhaps a "Conflicts" might be a good idea,
> though.
>...

A Breaks has in the meantime be added to libc6,
merging with #965932 where this was done.

cu
Adrian--- End Message ---

Bug#974086: marked as done (gnome-desktop3: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 13:03:21 +
with message-id 
and subject line Bug#974086: fixed in gnome-desktop3 3.38.1-2
has caused the Debian Bug report #974086,
regarding gnome-desktop3: autopkgtest regression
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.)


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

Dear maintainer(s),

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

   passfail
gnome-desktop3 from testing3.38.1-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 to testing [1]. Can
you please investigate the situation and fix it?

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=gnome-desktop3

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gnome-desktop3/8034675/log.gz

autopkgtest [20:11:12]: test installed-tests: [---
Running as: uid=1000(debci) gid=1000(debci) groups=1000(debci)
passwd entry: debci:x:1000:1000::/home/debci:/bin/sh
group entry: debci:x:1000:
Environment:
ADTTMP=/tmp/autopkgtest-lxc.1dpe8hnx/downtmp/autopkgtest_tmp
ADT_ARTIFACTS=/tmp/autopkgtest-lxc.1dpe8hnx/downtmp/installed-tests-artifacts
AUTOPKGTEST_ARTIFACTS=/tmp/autopkgtest-lxc.1dpe8hnx/downtmp/installed-tests-artifacts
AUTOPKGTEST_TMP=/tmp/autopkgtest-lxc.1dpe8hnx/downtmp/autopkgtest_tmp
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
DEBIAN_FRONTEND=noninteractive
DEB_BUILD_OPTIONS=parallel=2
G_MESSAGES_DEBUG=all
HOME=/home/debci
LANG=C.UTF-8
LOGNAME=debci
MAIL=/var/mail/debci
NO_AT_BRIDGE=1
OLDPWD=/
PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
PWD=/tmp/autopkgtest-lxc.1dpe8hnx/downtmp/build.HGT/src
SHELL=/bin/bash
SHLVL=2
USER=debci
XDG_RUNTIME_DIR=/tmp/autopkgtest-lxc.1dpe8hnx/downtmp/autopkgtest_tmp
XDG_SESSION_CLASS=background
XDG_SESSION_ID=c1
XDG_SESSION_TYPE=unspecified
_=/tmp/autopkgtest-lxc.1dpe8hnx/downtmp/build.HGT/src/debian/tests/installed-tests
dpkg-architecture: warning: cannot determine CC system type, falling
back to default (native compilation)
gnome-desktop/wall-clock.test
(/usr/lib/x86_64-linux-gnu/libgnome-desktop-3-19/installed-tests)
gnome-desktop/wallclock-reftest.test
(/usr/lib/x86_64-linux-gnu/libgnome-desktop-3-19/installed-tests)
run-with-locales: en_US.UTF-8...
Character set: UTF-8
Source file: en_US
Output: /tmp/tmp.d8Ah9E245D/en_US.utf8
run-with-locales: he_IL.UTF-8...
Character set: UTF-8
Source file: he_IL
Output: /tmp/tmp.d8Ah9E245D/he_IL.utf8
run-with-locales: ja_JP.UTF-8...
Character set: UTF-8
Source file: ja_JP
Output: /tmp/tmp.d8Ah9E245D/ja_JP.utf8
(gnome-desktop-testing-runner:4075): GLib-GIO-DEBUG: 20:11:17.424:
_g_io_module_get_default: Found default implementation local (GLocalVfs)
for ?gio-vfs?
1..2
# Running test: gnome-desktop/wallclock-reftest.test
# FAIL: gnome-desktop/wallclock-reftest.test (Child process killed by
signal 6)
not ok - gnome-desktop/wallclock-reftest.test
# Running test: gnome-desktop/wall-clock.test
# FAIL: gnome-desktop/wall-clock.test (Child process killed by signal 6)
not ok - gnome-desktop/wall-clock.test
# SUMMARY: total=2; passed=0; skipped=0; failed=2; user=0.1s;
system=0.0s; maxrss=63848
# FAIL: gnome-desktop/wallclock-reftest.test (Child process killed by
signal 6)
# FAIL: gnome-desktop/wall-clock.test (Child process killed by signal 6)
autopkgtest [20:11:17]: test installed-tests: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gnome-desktop3
Source-Version: 3.38.1-2
Done: Simon McVittie 

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

Bug#974104: merkaartor FTBFS: error: field ‘thePath’ has incomplete type ‘QPainterPath’

[Jerome BENOIT]

On Tue, 10 Nov 2020 06:10:41 +0100 Sebastiaan Couwenberg  
wrote:
> This is likely caused by the recent update to Qt 5.15.1, and seems to be
> fixed upstream:
> 
>  
> https://github.com/openstreetmap/merkaartor/commit/e72553a7ea2c7ba0634cc3afcd27a9f7cfef089c
> 
> Jerome, will you take care of this?

I will soon.
Best,
Jerome

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

-- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B



signature.asc
Description: OpenPGP digital signature

Processed: Bug#974086 marked as pending in gnome-desktop3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #974086 [src:gnome-desktop3] gnome-desktop3: autopkgtest regression
Added tag(s) pending.

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

Bug#974086: marked as pending in gnome-desktop3

[Simon McVittie]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/gnome-team/gnome-desktop/-/commit/afb9a0688c0292a274d914528fe2342103852520


d/p/Update-Hebrew-translation.patch: Update Hebrew translation

In particular this fixes an autopkgtest failure where U+2236 RATIO was
wrongly translated to U+003A COLON, and also fixes the hour and minute
in the GNOME Shell clock being reversed in the Hebrew locale.

Closes: #974086


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974086

Bug#970763: marked as done (wminput immedinately exits with Segmentation Fault on use)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 12:18:20 +
with message-id 
and subject line Bug#970763: fixed in cwiid 0.6.91-2
has caused the Debian Bug report #970763,
regarding wminput immedinately exits with Segmentation Fault on use
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.)


-- 
970763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wminput
Version: 0.6.91-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

With the most recent version of wminput, the application fails to start
immediately, raising a Segmentation Fault. This occurrs on both of my
machines that currently track Debian Testing. It does not matter what
command-line arguments are used, even --version causes this behaviour.

I attempted to rebuild the package with debug symbols in order to get a
useful stack trace. While I was able to build and install the package +
dbgsym packages, the backtrace in gdb was not useful. Here it is for
reference anyways:

$ gdb wminput
GNU gdb (Debian 9.2-1) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

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 "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from wminput...
Reading symbols from
/usr/lib/debug/.build-id/87/07b22dc522a1bffe98fc49614410ec12d85b05.debug...
(gdb) run
Starting program: /usr/bin/wminput 

Program received signal SIGSEGV, Segmentation fault.
0x0001 in ?? ()
(gdb) bt
#0  0x0001 in ?? ()
#1  0x7fffe4b2 in ?? ()
#2  0x in ?? ()

And here is LDD's output:

$ ldd /usr/bin/wminput
linux-vdso.so.1 (0x7ffc5dbc2000)
libcwiid.so.1 => /usr/lib/libcwiid.so.1 (0x7f3439bdb000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f3439bd5000)
libbluetooth.so.3 => /usr/lib/x86_64-linux-gnu/libbluetooth.so.3 
(0x7f3439bb)
libpython3.8.so.1.0 => /usr/lib/x86_64-linux-gnu/libpython3.8.so.1.0 
(0x7f3439667000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f3439645000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f343948)
/lib64/ld-linux-x86-64.so.2 (0x7f3439c4c000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x7f3439451000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f3439434000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7f343942f000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f34392eb000)

I'm hoping this should be trivial for anyone else to reproduce. 
If you'd like me to try anything else, please let me know.

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

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

Versions of packages wminput depends on:
ii  libbluetooth3  5.54-1
ii  libc6  2.31-3
ii  libcwiid1  0.6.91-1+b1
ii  libpython3.8   3.8.5-2
ii  python3-cwiid  0.6.91-1+b1

wminput recommends no packages.

wminput suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cwiid
Source-Version: 0.6.91-2
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  

Bug#974211: metakernel's autopkg tests fail

[Matthias Klose]

Package: src:metakernel
Version: 0.27.4-1
Severity: serious
Tags: sid bullseye

see
https://ci.debian.net/data/autopkgtest/testing/amd64/m/metakernel/8026145/log.gz

=== FAILURES ===
 test_ls_path_complete _

def test_ls_path_complete():
kernel = get_kernel()
comp = kernel.do_complete('! ls ~/.ipytho', len('! ls ~/.ipytho'))
>   assert comp['matches'] == ['ipython/'], comp
E   AssertionError: {'cursor_end': 14, 'cursor_start': 8, 'matches':
['\x1b[?2004h', '\x1b[?2004l', 'ipython/'], 'status': 'ok'}
E   assert ['\x1b[?2004h...', 'ipython/'] == ['ipython/']
E At index 0 diff: '\x1b[?2004h' != 'ipython/'
E Left contains 2 more items, first extra item: '\x1b[?2004l'
E Use -v to get the full diff

test_metakernel.py:85: AssertionError
_ REPLWrapTestCase.test_existing_spawn _

self = 

def test_existing_spawn(self):
child = pexpect.spawnu("bash", timeout=5, echo=False)
repl = replwrap.REPLWrapper(child, re.compile('[$#]'),
"PS1='{0}' PS2='{1}' "
"PROMPT_COMMAND='' TERM='dumb'")

res = repl.run_command("echo $HOME")
>   assert res.startswith('/'), res
E   AssertionError: [?2004l
/home/debci
E [?2004h
E   assert False
E+  where False = ('/')
E+where 
= '\x1b[?2004l\r/home/debci\r\n\x1b[?2004h'.startswith

/usr/lib/python3/dist-packages/metakernel/tests/test_replwrap.py:73: 
AssertionError
___ REPLWrapTestCase.test_multiline 

self = 

def test_multiline(self):
bash = replwrap.bash()
res = bash.run_command("echo '1 2\n3 4'")
>   self.assertEqual(res.strip().splitlines(), ['1 2', '3 4'])
E   AssertionError: Lists differ: ['\x1b[?2004l', '\x1b[?2004h\x1b[?2004l',
'1 2', '3 4', '\x1b[?2004h'] != ['1 2', '3 4']
E
E   First differing element 0:
E   '\x1b[?2004l'
E   '1 2'
E
E   First list contains 3 additional elements.
E   First extra element 2:
E   '1 2'
E
E   - ['\x1b[?2004l', '\x1b[?2004h\x1b[?2004l', '1 2', '3 4', '\x1b[?2004h']
E   + ['1 2', '3 4']

/usr/lib/python3/dist-packages/metakernel/tests/test_replwrap.py:52: 
AssertionError
=== warnings summary ===
/usr/lib/python3/dist-packages/metakernel/magics/tests/test_latex_magic.py:8
  /usr/lib/python3/dist-packages/metakernel/magics/tests/test_latex_magic.py:8:
DeprecationWarning: invalid escape sequence \d
kernel.do_execute("%latex x_1 = \dfrace{a}{b}")

/usr/lib/python3/dist-packages/metakernel/magics/tests/test_latex_magic.py:14
  /usr/lib/python3/dist-packages/metakernel/magics/tests/test_latex_magic.py:14:
DeprecationWarning: invalid escape sequence \d
kernel.do_execute("""%%latex

/usr/lib/python3/dist-packages/metakernel/tests/test_parser.py:74
  /usr/lib/python3/dist-packages/metakernel/tests/test_parser.py:74:
DeprecationWarning: invalid escape sequence \
assert "Test\ Dir/" in info['path_matches'], info['path_matches']

/usr/lib/python3/dist-packages/metakernel/tests/test_parser.py:104
  /usr/lib/python3/dist-packages/metakernel/tests/test_parser.py:104:
DeprecationWarning: invalid escape sequence \
assert "Test\ Dir/" in info['path_matches'], info['path_matches']

/usr/lib/python3/dist-packages/metakernel/tests/test_parser.py:116
  /usr/lib/python3/dist-packages/metakernel/tests/test_parser.py:116:
DeprecationWarning: invalid escape sequence \
assert 'Test\ Dir/' in info['path_matches'], info

/usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127
  /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/metakernel/.pytest_cache/v/cache/stepwise
self.warn("could not create cache path {path}", path=path)

/usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127
  /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/metakernel/.pytest_cache/v/cache/nodeids
self.warn("could not create cache path {path}", path=path)

/usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127
  /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:127:
PytestCacheWarning: could not create cache path
/usr/lib/python3/dist-packages/metakernel/.pytest_cache/v/cache/lastfailed
self.warn("could not create cache path {path}", path=path)

-- Docs: https://docs.pytest.org/en/latest/warnings.html
=== 3 failed, 78 passed, 8 warnings in 39.85 seconds ===

Bug#974210: pytorch's autopkg tests fail

[Matthias Klose]

Package: src:pytorch
Version: 1.6.0-5
Severity: serious
Tags: sid bullseye

https://ci.debian.net/packages/p/pytorch

these look all like:

autopkgtest [23:22:49]: test 41_of_47__pytest__test_namedtensor: cd test/ ;
python3 run_test.py -pt -i test_namedtensor -v
autopkgtest [23:22:49]: test 41_of_47__pytest__test_namedtensor:
[---
Traceback (most recent call last):
  File "run_test.py", line 17, in 
from torch.utils import cpp_extension
  File "/usr/lib/python3/dist-packages/torch/utils/cpp_extension.py", line 8, in

import setuptools
ModuleNotFoundError: No module named 'setuptools'



Please also build the package for all supported python3 versions.

Bug#974045: marked as done (libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4))

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 10:40:17 +
with message-id 
and subject line Bug#973938: fixed in ismrmrd 1.4.2.1-3
has caused the Debian Bug report #973938,
regarding libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
to be marked as done.

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

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


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

Hi,

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

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

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

  Preparing to unpack .../libismrmrd1.4_1.4.2.1-2_amd64.deb ...
  Unpacking libismrmrd1.4:amd64 (1.4.2.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libismrmrd1.4_1.4.2.1-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4', which is 
also in package libismrmrd1.3:amd64 1.4.0-1+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libismrmrd1.4_1.4.2.1-2_amd64.deb

The versioned constraint (>= 1.4) is unusual but correct in this case,
since the SONAME bump in 1.4 was not accompanied by the mandatory package
rename. Packages built against 1.4.0 have a dependency on
libismrmrd1.3 (>= 1.4.0), thus the oldstable version libismrmrd1.3 (1.3.3-1+b1)
cannot be used to satisfy that and it can be kept co-installable with
libismrmrd1.4


cheers,

Andreas


libismrmrd1.3=1.4.0-1+b2_libismrmrd1.4=1.4.2.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ismrmrd
Source-Version: 1.4.2.1-3
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ismrmrd 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, 11 Nov 2020 11:02:18 +0100
Source: ismrmrd
Architecture: source
Version: 1.4.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 973938 973939 974045
Changes:
 ismrmrd (1.4.2.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Add missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
 Closes: #973938, #974045
   * Fix binary-all FTBFS
 Closes: #973939
Checksums-Sha1:
 4f4a9a2d6e51e6723d8285a846584a19f66a2888 2401 ismrmrd_1.4.2.1-3.dsc
 d92ec02d44e01f6c2bae059a9acdcf2d1a0d360d 7260 ismrmrd_1.4.2.1-3.debian.tar.xz
 c5afecdf3df6fdb76d25b1fe43ed16a3d454d724 9741 ismrmrd_1.4.2.1-3_amd64.buildinfo
Checksums-Sha256:
 06e50a79b3f5496cbfd18bb719f2f8de6f747aea4cf62f5226089e08cde50700 2401 
ismrmrd_1.4.2.1-3.dsc
 e09f50ea0b47818a6f6cffcba3e2be73c1c7730d5af5af3bdc5b0bb0930fa31b 7260 
ismrmrd_1.4.2.1-3.debian.tar.xz
 c503be1b2a38d0d01e232303794d7f33afa4cfc24896649512d2a17700551947 9741 
ismrmrd_1.4.2.1-3_amd64.buildinfo
Files:
 c3050a95e403e9ab8181b6a3b4a3b3f6 2401 science optional ismrmrd_1.4.2.1-3.dsc
 08b2171504a3eeb17333f8cde9836b74 7260 science optional 
ismrmrd_1.4.2.1-3.debian.tar.xz
 7f8d3581c31e76db0b1a2bd86741 9741 science optional 
ismrmrd_1.4.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+ru+8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHWRg//V7ARAu1PLp6Vnd8pH39SewHxGTYdFS6W
JSOPyEEBBF/yWFYFPhKgyjsemsoYT6F4Zcp0ixjqOHQ5eHJ1d8oym4OHr6HRVaMg
roZqXRhv5mM/bFF0yaAkaT4B2FTumRdE35JcWn+EasuTOJ963yvON+k0DfmxW5CD
tOtN0TlHJ3GB4RqdKP6bLWjYBXeVkbQl2to+M78zGKS4Uufbcwax0z9s2zEeVuC9
sGj5cHRDR8VgxGT7HU5Y+MxCRp+H4A02orYevJu/FmTQFAzyiAmws4XhBfUEuTzj
2S8iM86+jAOmWR4TTVE9N2oHzK4ncaq0WYsMFn6EJMvcwFWau+jk0xVs49XGMGTm

Bug#973939: marked as done (ismrmrd: binary-all FTBFS)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 10:40:17 +
with message-id 
and subject line Bug#973939: fixed in ismrmrd 1.4.2.1-3
has caused the Debian Bug report #973939,
regarding ismrmrd: binary-all FTBFS
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.)


-- 
973939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ismrmrd
Version: 1.4.2.1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ismrmrd=all=1.4.2.1-2=1604772139=0

...
   dh_auto_install -i
cd obj-x86_64-linux-gnu && make -j4 install 
DESTDIR=/<>/debian/tmp AM_UPDATE_INFO_DIR=no "INSTALL=install 
--strip-program=true"
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
make  -f CMakeFiles/Makefile2 preinstall
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make[2]: Nothing to be done for 'preinstall'.
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
Install the project...
/usr/bin/cmake -P cmake_install.cmake
-- Install configuration: "None"
-- Installing: /<>/debian/tmp/usr/include/ismrmrd/version.h
-- Installing: 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4.2
-- Installing: 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4
-- Set runtime path of 
"/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4.2" to ""
-- Installing: 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libismrmrd.so
CMake Error at cmake_install.cmake:103 (file):
  file INSTALL cannot find
  "/<>/obj-x86_64-linux-gnu/libismrmrd.a":
  No such file or directory.


make[1]: *** [Makefile:119: install] Error 1
--- End Message ---
--- Begin Message ---
Source: ismrmrd
Source-Version: 1.4.2.1-3
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ismrmrd 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, 11 Nov 2020 11:02:18 +0100
Source: ismrmrd
Architecture: source
Version: 1.4.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 973938 973939 974045
Changes:
 ismrmrd (1.4.2.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Add missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
 Closes: #973938, #974045
   * Fix binary-all FTBFS
 Closes: #973939
Checksums-Sha1:
 4f4a9a2d6e51e6723d8285a846584a19f66a2888 2401 ismrmrd_1.4.2.1-3.dsc
 d92ec02d44e01f6c2bae059a9acdcf2d1a0d360d 7260 ismrmrd_1.4.2.1-3.debian.tar.xz
 c5afecdf3df6fdb76d25b1fe43ed16a3d454d724 9741 ismrmrd_1.4.2.1-3_amd64.buildinfo
Checksums-Sha256:
 06e50a79b3f5496cbfd18bb719f2f8de6f747aea4cf62f5226089e08cde50700 2401 
ismrmrd_1.4.2.1-3.dsc
 e09f50ea0b47818a6f6cffcba3e2be73c1c7730d5af5af3bdc5b0bb0930fa31b 7260 
ismrmrd_1.4.2.1-3.debian.tar.xz
 c503be1b2a38d0d01e232303794d7f33afa4cfc24896649512d2a17700551947 9741 
ismrmrd_1.4.2.1-3_amd64.buildinfo
Files:
 c3050a95e403e9ab8181b6a3b4a3b3f6 2401 science optional ismrmrd_1.4.2.1-3.dsc
 08b2171504a3eeb17333f8cde9836b74 7260 science optional 
ismrmrd_1.4.2.1-3.debian.tar.xz
 7f8d3581c31e76db0b1a2bd86741 9741 science optional 
ismrmrd_1.4.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+ru+8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHWRg//V7ARAu1PLp6Vnd8pH39SewHxGTYdFS6W
JSOPyEEBBF/yWFYFPhKgyjsemsoYT6F4Zcp0ixjqOHQ5eHJ1d8oym4OHr6HRVaMg
roZqXRhv5mM/bFF0yaAkaT4B2FTumRdE35JcWn+EasuTOJ963yvON+k0DfmxW5CD
tOtN0TlHJ3GB4RqdKP6bLWjYBXeVkbQl2to+M78zGKS4Uufbcwax0z9s2zEeVuC9
sGj5cHRDR8VgxGT7HU5Y+MxCRp+H4A02orYevJu/FmTQFAzyiAmws4XhBfUEuTzj
2S8iM86+jAOmWR4TTVE9N2oHzK4ncaq0WYsMFn6EJMvcwFWau+jk0xVs49XGMGTm
x7gi+xeA/+6kZcfBjaUUbVYWHxTpPuFLK/SeNuldlOFKeduuwBU9XrKa71LuDWqd
pu+EeyP3ZbC5w1AhFoQpgAXbfKH02SR5g6l849OTGVPZtJ4hUyVGIIvWAT0rpd9Q
vK1RGnCMKYErBHKcxAvzhgSBQkv0zMUsfsiCeKyMZlUVvlGgDgmy/gmoXihQoid/

Bug#973938: marked as done (libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4))

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 10:40:17 +
with message-id 
and subject line Bug#973938: fixed in ismrmrd 1.4.2.1-3
has caused the Debian Bug report #973938,
regarding libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
to be marked as done.

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

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


-- 
973938: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973938
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libismrmrd1.4
Version: 1.4.2.1-2
Severity: serious

Unpacking libismrmrd1.4:amd64 (1.4.2.1-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-onDkpV/15-libismrmrd1.4_1.4.2.1-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4', which is 
also in package libismrmrd1.3:amd64 1.4.0-1+b2
--- End Message ---
--- Begin Message ---
Source: ismrmrd
Source-Version: 1.4.2.1-3
Done: Andreas Tille 

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ismrmrd 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, 11 Nov 2020 11:02:18 +0100
Source: ismrmrd
Architecture: source
Version: 1.4.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 973938 973939 974045
Changes:
 ismrmrd (1.4.2.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Add missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
 Closes: #973938, #974045
   * Fix binary-all FTBFS
 Closes: #973939
Checksums-Sha1:
 4f4a9a2d6e51e6723d8285a846584a19f66a2888 2401 ismrmrd_1.4.2.1-3.dsc
 d92ec02d44e01f6c2bae059a9acdcf2d1a0d360d 7260 ismrmrd_1.4.2.1-3.debian.tar.xz
 c5afecdf3df6fdb76d25b1fe43ed16a3d454d724 9741 ismrmrd_1.4.2.1-3_amd64.buildinfo
Checksums-Sha256:
 06e50a79b3f5496cbfd18bb719f2f8de6f747aea4cf62f5226089e08cde50700 2401 
ismrmrd_1.4.2.1-3.dsc
 e09f50ea0b47818a6f6cffcba3e2be73c1c7730d5af5af3bdc5b0bb0930fa31b 7260 
ismrmrd_1.4.2.1-3.debian.tar.xz
 c503be1b2a38d0d01e232303794d7f33afa4cfc24896649512d2a17700551947 9741 
ismrmrd_1.4.2.1-3_amd64.buildinfo
Files:
 c3050a95e403e9ab8181b6a3b4a3b3f6 2401 science optional ismrmrd_1.4.2.1-3.dsc
 08b2171504a3eeb17333f8cde9836b74 7260 science optional 
ismrmrd_1.4.2.1-3.debian.tar.xz
 7f8d3581c31e76db0b1a2bd86741 9741 science optional 
ismrmrd_1.4.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+ru+8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHWRg//V7ARAu1PLp6Vnd8pH39SewHxGTYdFS6W
JSOPyEEBBF/yWFYFPhKgyjsemsoYT6F4Zcp0ixjqOHQ5eHJ1d8oym4OHr6HRVaMg
roZqXRhv5mM/bFF0yaAkaT4B2FTumRdE35JcWn+EasuTOJ963yvON+k0DfmxW5CD
tOtN0TlHJ3GB4RqdKP6bLWjYBXeVkbQl2to+M78zGKS4Uufbcwax0z9s2zEeVuC9
sGj5cHRDR8VgxGT7HU5Y+MxCRp+H4A02orYevJu/FmTQFAzyiAmws4XhBfUEuTzj
2S8iM86+jAOmWR4TTVE9N2oHzK4ncaq0WYsMFn6EJMvcwFWau+jk0xVs49XGMGTm
x7gi+xeA/+6kZcfBjaUUbVYWHxTpPuFLK/SeNuldlOFKeduuwBU9XrKa71LuDWqd
pu+EeyP3ZbC5w1AhFoQpgAXbfKH02SR5g6l849OTGVPZtJ4hUyVGIIvWAT0rpd9Q
vK1RGnCMKYErBHKcxAvzhgSBQkv0zMUsfsiCeKyMZlUVvlGgDgmy/gmoXihQoid/
qDM1eP5n5X95B6OIBeLILrdWk70eKHqIiQewQmb2MZTU39z0M5rJiqbH5AilV/+d
PqXupNifBfKj6gDzn6O3cXtx50CdwvfqSw8PyY+hlq2JCK5g0/jqxmtVDDCyZmTB
HoFEIrjQUI4=
=10Bn
-END PGP SIGNATURE End Message ---

Bug#974045: marked as done (libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4))

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 10:40:17 +
with message-id 
and subject line Bug#974045: fixed in ismrmrd 1.4.2.1-3
has caused the Debian Bug report #974045,
regarding libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
to be marked as done.

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

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


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

Hi,

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

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

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

  Preparing to unpack .../libismrmrd1.4_1.4.2.1-2_amd64.deb ...
  Unpacking libismrmrd1.4:amd64 (1.4.2.1-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libismrmrd1.4_1.4.2.1-2_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4', which is 
also in package libismrmrd1.3:amd64 1.4.0-1+b2
  Errors were encountered while processing:
   /var/cache/apt/archives/libismrmrd1.4_1.4.2.1-2_amd64.deb

The versioned constraint (>= 1.4) is unusual but correct in this case,
since the SONAME bump in 1.4 was not accompanied by the mandatory package
rename. Packages built against 1.4.0 have a dependency on
libismrmrd1.3 (>= 1.4.0), thus the oldstable version libismrmrd1.3 (1.3.3-1+b1)
cannot be used to satisfy that and it can be kept co-installable with
libismrmrd1.4


cheers,

Andreas


libismrmrd1.3=1.4.0-1+b2_libismrmrd1.4=1.4.2.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ismrmrd
Source-Version: 1.4.2.1-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ismrmrd 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, 11 Nov 2020 11:02:18 +0100
Source: ismrmrd
Architecture: source
Version: 1.4.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 973938 973939 974045
Changes:
 ismrmrd (1.4.2.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Add missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
 Closes: #973938, #974045
   * Fix binary-all FTBFS
 Closes: #973939
Checksums-Sha1:
 4f4a9a2d6e51e6723d8285a846584a19f66a2888 2401 ismrmrd_1.4.2.1-3.dsc
 d92ec02d44e01f6c2bae059a9acdcf2d1a0d360d 7260 ismrmrd_1.4.2.1-3.debian.tar.xz
 c5afecdf3df6fdb76d25b1fe43ed16a3d454d724 9741 ismrmrd_1.4.2.1-3_amd64.buildinfo
Checksums-Sha256:
 06e50a79b3f5496cbfd18bb719f2f8de6f747aea4cf62f5226089e08cde50700 2401 
ismrmrd_1.4.2.1-3.dsc
 e09f50ea0b47818a6f6cffcba3e2be73c1c7730d5af5af3bdc5b0bb0930fa31b 7260 
ismrmrd_1.4.2.1-3.debian.tar.xz
 c503be1b2a38d0d01e232303794d7f33afa4cfc24896649512d2a17700551947 9741 
ismrmrd_1.4.2.1-3_amd64.buildinfo
Files:
 c3050a95e403e9ab8181b6a3b4a3b3f6 2401 science optional ismrmrd_1.4.2.1-3.dsc
 08b2171504a3eeb17333f8cde9836b74 7260 science optional 
ismrmrd_1.4.2.1-3.debian.tar.xz
 7f8d3581c31e76db0b1a2bd86741 9741 science optional 
ismrmrd_1.4.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+ru+8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHWRg//V7ARAu1PLp6Vnd8pH39SewHxGTYdFS6W
JSOPyEEBBF/yWFYFPhKgyjsemsoYT6F4Zcp0ixjqOHQ5eHJ1d8oym4OHr6HRVaMg
roZqXRhv5mM/bFF0yaAkaT4B2FTumRdE35JcWn+EasuTOJ963yvON+k0DfmxW5CD
tOtN0TlHJ3GB4RqdKP6bLWjYBXeVkbQl2to+M78zGKS4Uufbcwax0z9s2zEeVuC9
sGj5cHRDR8VgxGT7HU5Y+MxCRp+H4A02orYevJu/FmTQFAzyiAmws4XhBfUEuTzj
2S8iM86+jAOmWR4TTVE9N2oHzK4ncaq0WYsMFn6EJMvcwFWau+jk0xVs49XGMGTm

Bug#973938: marked as done (libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4))

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 10:40:17 +
with message-id 
and subject line Bug#974045: fixed in ismrmrd 1.4.2.1-3
has caused the Debian Bug report #974045,
regarding libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
to be marked as done.

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

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


-- 
974045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974045
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libismrmrd1.4
Version: 1.4.2.1-2
Severity: serious

Unpacking libismrmrd1.4:amd64 (1.4.2.1-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-onDkpV/15-libismrmrd1.4_1.4.2.1-2_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libismrmrd.so.1.4', which is 
also in package libismrmrd1.3:amd64 1.4.0-1+b2
--- End Message ---
--- Begin Message ---
Source: ismrmrd
Source-Version: 1.4.2.1-3
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated ismrmrd 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, 11 Nov 2020 11:02:18 +0100
Source: ismrmrd
Architecture: source
Version: 1.4.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Closes: 973938 973939 974045
Changes:
 ismrmrd (1.4.2.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Add missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
 Closes: #973938, #974045
   * Fix binary-all FTBFS
 Closes: #973939
Checksums-Sha1:
 4f4a9a2d6e51e6723d8285a846584a19f66a2888 2401 ismrmrd_1.4.2.1-3.dsc
 d92ec02d44e01f6c2bae059a9acdcf2d1a0d360d 7260 ismrmrd_1.4.2.1-3.debian.tar.xz
 c5afecdf3df6fdb76d25b1fe43ed16a3d454d724 9741 ismrmrd_1.4.2.1-3_amd64.buildinfo
Checksums-Sha256:
 06e50a79b3f5496cbfd18bb719f2f8de6f747aea4cf62f5226089e08cde50700 2401 
ismrmrd_1.4.2.1-3.dsc
 e09f50ea0b47818a6f6cffcba3e2be73c1c7730d5af5af3bdc5b0bb0930fa31b 7260 
ismrmrd_1.4.2.1-3.debian.tar.xz
 c503be1b2a38d0d01e232303794d7f33afa4cfc24896649512d2a17700551947 9741 
ismrmrd_1.4.2.1-3_amd64.buildinfo
Files:
 c3050a95e403e9ab8181b6a3b4a3b3f6 2401 science optional ismrmrd_1.4.2.1-3.dsc
 08b2171504a3eeb17333f8cde9836b74 7260 science optional 
ismrmrd_1.4.2.1-3.debian.tar.xz
 7f8d3581c31e76db0b1a2bd86741 9741 science optional 
ismrmrd_1.4.2.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+ru+8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHWRg//V7ARAu1PLp6Vnd8pH39SewHxGTYdFS6W
JSOPyEEBBF/yWFYFPhKgyjsemsoYT6F4Zcp0ixjqOHQ5eHJ1d8oym4OHr6HRVaMg
roZqXRhv5mM/bFF0yaAkaT4B2FTumRdE35JcWn+EasuTOJ963yvON+k0DfmxW5CD
tOtN0TlHJ3GB4RqdKP6bLWjYBXeVkbQl2to+M78zGKS4Uufbcwax0z9s2zEeVuC9
sGj5cHRDR8VgxGT7HU5Y+MxCRp+H4A02orYevJu/FmTQFAzyiAmws4XhBfUEuTzj
2S8iM86+jAOmWR4TTVE9N2oHzK4ncaq0WYsMFn6EJMvcwFWau+jk0xVs49XGMGTm
x7gi+xeA/+6kZcfBjaUUbVYWHxTpPuFLK/SeNuldlOFKeduuwBU9XrKa71LuDWqd
pu+EeyP3ZbC5w1AhFoQpgAXbfKH02SR5g6l849OTGVPZtJ4hUyVGIIvWAT0rpd9Q
vK1RGnCMKYErBHKcxAvzhgSBQkv0zMUsfsiCeKyMZlUVvlGgDgmy/gmoXihQoid/
qDM1eP5n5X95B6OIBeLILrdWk70eKHqIiQewQmb2MZTU39z0M5rJiqbH5AilV/+d
PqXupNifBfKj6gDzn6O3cXtx50CdwvfqSw8PyY+hlq2JCK5g0/jqxmtVDDCyZmTB
HoFEIrjQUI4=
=10Bn
-END PGP SIGNATURE End Message ---

Bug#974192: marked as done (mpfrc++: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 11:23:10 +
with message-id 
and subject line Bug#974192: fixed in mpfrc++ 3.6.8+ds-2
has caused the Debian Bug report #974192,
regarding mpfrc++: invalid maintainer address
to be marked as done.

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

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


-- 
974192: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974192
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mpfrc++
Version: 3.6.8+ds-1
Severity: serious
X-Debbugs-Cc: Jerome Benoit 

The maintainer address is invalid, see below.

Ansgar

> This message was created automatically by mail delivery software.
>
> A message that you sent could not be delivered to one or more of its
> recipients. This is a permanent error. The following address(es) failed:
>
>   debian-science-maintain...@lists.alioth.debian.net
> Unrouteable address
>
> Reporting-MTA: dns; muffat.debian.org
>
> Action: failed
> Final-Recipient: rfc822;debian-science-maintain...@lists.alioth.debian.net
> Status: 5.0.0
--- End Message ---
--- Begin Message ---
Source: mpfrc++
Source-Version: 3.6.8+ds-2
Done: Jerome Benoit 

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

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated mpfrc++ 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, 11 Nov 2020 11:04:12 +
Source: mpfrc++
Architecture: source
Version: 3.6.8+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jerome Benoit 
Closes: 974192
Changes:
 mpfrc++ (3.6.8+ds-2) unstable; urgency=medium
 .
   * SBF: correct Maintainer address (Closes: #974192).
Checksums-Sha1:
 216e63d95022a918e3ad6d736896427ce41487fb 2750 mpfrc++_3.6.8+ds-2.dsc
 1d08e60c25a1d8d52cda8ddcb7df5cc57e267b39 4144 mpfrc++_3.6.8+ds-2.debian.tar.xz
 cc7af48c0226bcaab04f5e7b5a1d7be3a24a7e69 6768 
mpfrc++_3.6.8+ds-2_source.buildinfo
Checksums-Sha256:
 a8c51a23a844cf9dfb44779f520fdcd8a9209a82b4052378522dd0ffa87971b9 2750 
mpfrc++_3.6.8+ds-2.dsc
 6366eca186a6b7a6e7b6269d5fc23fa7ef5bb97bb230358cf8edbb41646f0089 4144 
mpfrc++_3.6.8+ds-2.debian.tar.xz
 447028c879cd7e2d9ebd2bf84a42fa5a44d869d70021019359750cf15edbe105 6768 
mpfrc++_3.6.8+ds-2_source.buildinfo
Files:
 dd7d6f671639507ef330533f1d27130d 2750 math optional mpfrc++_3.6.8+ds-2.dsc
 6e4b97057d13af4c59cb89dcaa55665a 4144 math optional 
mpfrc++_3.6.8+ds-2.debian.tar.xz
 379551229c13b6180ac39e245ff79171 6768 math optional 
mpfrc++_3.6.8+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQRJBAEBCgAzFiEEriiuFXEN/x2H5adiP5IZpn82xosFAl+rxlgVHGNhbGN1bHVz
QHJlem96ZXIubmV0AAoJED+SGaZ/NsaLnRcgAMTTjtm1HLKuG6aZkdiVIhUzSu0X
iS6XJVA0u0sETzL1pF2ZHV36N6bqf2lAZQrWFkB8+U/q4xr2/aDiAnqzHrIq9hQ4
28SSUiDVDDMKN8ACAx+3baP1JZqEwmma9OZXeh4omJTQEzQybAbjC1s6Qp57dU0h
41e+n+4ZV82jpWObHGQW+fLoQcFKdCNI/L3vXad19svMf4o71u5omgpBb4F2KwHb
R6MwUIiPfhpFwyYFONlcy4ulI4mN5u7syU80G33KXnSA+BDWUXRnofgOBHzGpBG7
g5GeaGBKVg+siNrsND7td0B49x818lkntooojUmShVXrKPA+Spev/9nTtcmct33V
XXIq6ReFhTzlqRQf3mac3v9U6BJuW2bUs8vMK1+ojCKbpnTVVXB+n95HtDi0pNLq
Y3iYzPRPTbIlKvwNsJQomaWMm01cHbVtt/mvdTBZsizgAEp/0lgIZZ00ggxsnHzs
0sp9NOOv3/fGNhTGyEgRnGBy/HEG12eMGZe49QGPJlQuAnuCiAp/sC8mZE5Ih+TP
O+k7XNi9A21V5HDdiANr5Z0O1fRS+gwKdl++z1GDWi7E9DhBm/yFeOxAedsvjO9C
b7Khp9KlI7hdqWaV7warI6I6bZwklQ6iIwgpHpVBHOP9AbLsLwggyRzrTknds1Yl
FoDAvbS7Z+FmI2XyDW5U53JHcb5Qkb7mHzlBsMH1CAgO8wBQ7ovCk9K1FAB41NFx
+86buoyXX65lpj+buSDl0LJRq83oS884diVp4qEMMU44UC8UQVjXBgfcJfLf7ylp
dJA7kPCboTk15PfMcPNpb6A4IalzWmw5qjPJC7EW7L4cpFxGaR1b5T2TkW3iCXpP
oB2Et2B4i781iA/DI8zPdLgKneo8ZijmVnIIXZxMKKkh8PLygFfYN8lZpSsO6iRT
tJuI6CpAxQsSVUEjTXnmvy381hN297YLvrmHDCUA9OjqWp4qw+oLVPWRgj8SeCqJ
iHBU52lpAdIilGu7Vb/344LxsTs+nGPr6veaBeoGmy5BAgmiuaVflOz839dVq/bz
u43036VPKoTv8x42XxhamxgNDR6iLuJGk/mtIYJtSJOIGYUJjLvNEVjJBFEEVquM
HB5NnDk27OIVXZ9cxCONb93y1T8Frp+ch9d8BI94DnjkGHupEIIvJj5rPOE+JsKa
WWi6Y018trch27MNJoQSLKqFe5xKgBEpQIFoaiqgm/3UMVNj+8kzF5hKQ3Jn/I5x
1BV+iW1Ppfj2eFY0UlVG/0WYsiXMzIbYDjNuMn1+dcMquc0W+DLdMMzkYJpQTTrn
J36PIrNplHn98eGmcHnxynaNiWVDyBIFByjSuFit6nX8Ut8nmaBj4XqMDBw=
=80XI
-END PGP 

Processed: Re: Bug#974086: gnome-desktop3: autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/180
Bug #974086 [src:gnome-desktop3] gnome-desktop3: autopkgtest regression
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/180'.

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

Bug#974086: gnome-desktop3: autopkgtest regression

[Simon McVittie]

Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-desktop/-/issues/180

On Mon, 09 Nov 2020 at 20:47:28 +0100, Paul Gevers wrote:
> With a recent upload of gnome-desktop3 the autopkgtest of gnome-desktop3
> fails in testing when that autopkgtest is run with the binary packages
> of gnome-desktop3 from unstable.

It also fails in a pure unstable environment. This seems to be because
the Hebrew (Israel) translation breaks the test's assumptions; I'm trying
an updated translation from upstream.

smcv

Bug#972912: marked as done (ldb ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 10:40:44 +
with message-id 
and subject line Bug#972912: fixed in ldb 2:2.2.0-1
has caused the Debian Bug report #972912,
regarding ldb ftbfs with python3.9
to be marked as done.

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

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


-- 
972912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ldb
Version: 2.1.4-2
Severity: serious
Tags: sid bullseye ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.9

ldb ftbfs with python3.9; to reproduce, you can use the repositories found at:

deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./

see
https://people.debian.org/~ginggs/python3.9-default/ldb_2.1.4-2build1_amd64-2020-10-25T18:36:18Z.build

[...]
dh_makeshlibs -Xldb. -ppython3-ldb -- -c4
dpkg-gensymbols: error: new libraries appeared in the symbols file:
libpyldb-util.cpython-39-x86-64-linux-gnu.so.2
dpkg-gensymbols: error: some libraries disappeared in the symbols file:
libpyldb-util.cpython-38-x86-64-linux-gnu.so.2
dpkg-gensymbols: warning: debian/python3-ldb/DEBIAN/symbols doesn't match
completely debian/python3-ldb.symbols.amd64
--- debian/python3-ldb.symbols.amd64 (python3-ldb_2:2.1.4-2build1_amd64)
+++ dpkg-gensymbolsDn1MuN   2020-10-25 18:40:30.188308298 +
@@ -1,63 +1,63 @@
-libpyldb-util.cpython-38-x86-64-linux-gnu.so.2 python3-ldb #MINVER#
-
PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.1.4@PYLDB_UTIL.CPYTHON_38_X86_64_LINUX_GNU_2.1.4
2:2.1.4
- PYLDB_UTIL_1.1.10@PYLDB_UTIL_1.1.10 2:2.0.7
- PYLDB_UTIL_1.1.11@PYLDB_UTIL_1.1.11 2:2.0.7
- PYLDB_UTIL_1.1.12@PYLDB_UTIL_1.1.12 2:2.0.7
- PYLDB_UTIL_1.1.13@PYLDB_UTIL_1.1.13 2:2.0.7
- PYLDB_UTIL_1.1.14@PYLDB_UTIL_1.1.14 2:2.0.7
- PYLDB_UTIL_1.1.15@PYLDB_UTIL_1.1.15 2:2.0.7
- PYLDB_UTIL_1.1.16@PYLDB_UTIL_1.1.16 2:2.0.7
- PYLDB_UTIL_1.1.17@PYLDB_UTIL_1.1.17 2:2.0.7
- PYLDB_UTIL_1.1.18@PYLDB_UTIL_1.1.18 2:2.0.7
- PYLDB_UTIL_1.1.19@PYLDB_UTIL_1.1.19 2:2.0.7
- PYLDB_UTIL_1.1.20@PYLDB_UTIL_1.1.20 2:2.0.7
- PYLDB_UTIL_1.1.21@PYLDB_UTIL_1.1.21 2:2.0.7
- PYLDB_UTIL_1.1.22@PYLDB_UTIL_1.1.22 2:2.0.7
- PYLDB_UTIL_1.1.23@PYLDB_UTIL_1.1.23 1.5.4
- PYLDB_UTIL_1.1.24@PYLDB_UTIL_1.1.24 1.5.4
- PYLDB_UTIL_1.1.25@PYLDB_UTIL_1.1.25 1.5.4
- PYLDB_UTIL_1.1.26@PYLDB_UTIL_1.1.26 1.5.4
- PYLDB_UTIL_1.1.27@PYLDB_UTIL_1.1.27 1.5.4
- PYLDB_UTIL_1.1.28@PYLDB_UTIL_1.1.28 1.5.4
- PYLDB_UTIL_1.1.29@PYLDB_UTIL_1.1.29 1.5.4
- PYLDB_UTIL_1.1.2@PYLDB_UTIL_1.1.2 2:2.0.7
- PYLDB_UTIL_1.1.30@PYLDB_UTIL_1.1.30 1.5.4
- PYLDB_UTIL_1.1.31@PYLDB_UTIL_1.1.31 1.5.4
- PYLDB_UTIL_1.1.3@PYLDB_UTIL_1.1.3 2:2.0.7
- PYLDB_UTIL_1.1.4@PYLDB_UTIL_1.1.4 2:2.0.7
- PYLDB_UTIL_1.1.5@PYLDB_UTIL_1.1.5 2:2.0.7
- PYLDB_UTIL_1.1.6@PYLDB_UTIL_1.1.6 2:2.0.7
- PYLDB_UTIL_1.1.7@PYLDB_UTIL_1.1.7 2:2.0.7
- PYLDB_UTIL_1.1.8@PYLDB_UTIL_1.1.8 2:2.0.7
- PYLDB_UTIL_1.1.9@PYLDB_UTIL_1.1.9 2:2.0.7
- PYLDB_UTIL_1.2.0@PYLDB_UTIL_1.2.0 1.5.4
- PYLDB_UTIL_1.2.1@PYLDB_UTIL_1.2.1 1.5.4
- PYLDB_UTIL_1.2.2@PYLDB_UTIL_1.2.2 1.5.4
- PYLDB_UTIL_1.2.3@PYLDB_UTIL_1.2.3 1.5.4
- PYLDB_UTIL_1.3.0@PYLDB_UTIL_1.3.0 1.5.4
- PYLDB_UTIL_1.3.1@PYLDB_UTIL_1.3.1 1.5.4
- PYLDB_UTIL_1.3.2@PYLDB_UTIL_1.3.2 1.5.4
- PYLDB_UTIL_1.4.0@PYLDB_UTIL_1.4.0 1.5.4
- PYLDB_UTIL_1.4.1@PYLDB_UTIL_1.4.1 1.5.4
- PYLDB_UTIL_1.5.0@PYLDB_UTIL_1.5.0 1.5.4
- PYLDB_UTIL_1.5.1@PYLDB_UTIL_1.5.1 1.5.4
- PYLDB_UTIL_1.5.2@PYLDB_UTIL_1.5.2 1.5.4
- PYLDB_UTIL_1.5.3@PYLDB_UTIL_1.5.3 1.5.4
- PYLDB_UTIL_1.6.0@PYLDB_UTIL_1.6.0 2:2.0.7
- PYLDB_UTIL_1.6.1@PYLDB_UTIL_1.6.1 2:2.0.7
- PYLDB_UTIL_1.6.2@PYLDB_UTIL_1.6.2 2:2.0.7
- PYLDB_UTIL_1.6.3@PYLDB_UTIL_1.6.3 2:2.0.7
- PYLDB_UTIL_2.0.0@PYLDB_UTIL_2.0.0 2:2.0.7
- PYLDB_UTIL_2.0.1@PYLDB_UTIL_2.0.1 2:2.0.7
- PYLDB_UTIL_2.0.2@PYLDB_UTIL_2.0.2 2:2.0.7
- PYLDB_UTIL_2.0.3@PYLDB_UTIL_2.0.3 2:2.0.7
- PYLDB_UTIL_2.0.4@PYLDB_UTIL_2.0.4 2:2.0.7
- PYLDB_UTIL_2.0.5@PYLDB_UTIL_2.0.5 2:2.0.7
- PYLDB_UTIL_2.1.0@PYLDB_UTIL_2.1.0 2:2.1.0
- PYLDB_UTIL_2.1.1@PYLDB_UTIL_2.1.1 2:2.1.1
- PYLDB_UTIL_2.1.2@PYLDB_UTIL_2.1.2 2:2.1.2
- PYLDB_UTIL_2.1.3@PYLDB_UTIL_2.1.3 2:2.1.3
- PYLDB_UTIL_2.1.4@PYLDB_UTIL_2.1.4 2:2.1.4
- pyldb_Dn_FromDn@PYLDB_UTIL_1.1.2 2:2.0.7
- pyldb_Object_AsDn@PYLDB_UTIL_1.1.2 2:2.0.7
- pyldb_check_type@PYLDB_UTIL_2.1.0 2:2.1.0
+libpyldb-util.cpython-39-x86-64-linux-gnu.so.2 python3-ldb #MINVER#
+
PYLDB_UTIL.CPYTHON_39_X86_64_LINUX_GNU_2.1.4@PYLDB_UTIL.CPYTHON_39_X86_64_LINUX_GNU_2.1.4
2:2.1.4-2build1
+ PYLDB_UTIL_1.1.10@PYLDB_UTIL_1.1.10 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.11@PYLDB_UTIL_1.1.11 2:2.1.4-2build1
+ PYLDB_UTIL_1.1.12@PYLDB_UTIL_1.1.12 2:2.1.4-2build1
+ 

Processed: retitle 973938 to libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)

[Debian Bug Tracking System]

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

> retitle 973938 libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 1.4)
Bug #973938 [libismrmrd1.4] libismrmrd1.4: Missing Breaks+Replaces: 
libismrmrd1.3
Bug #974045 [libismrmrd1.4] libismrmrd1.4: missing Breaks+Replaces: 
libismrmrd1.3 (>= 1.4)
Changed Bug title to 'libismrmrd1.4: missing Breaks+Replaces: libismrmrd1.3 (>= 
1.4)' from 'libismrmrd1.4: Missing Breaks+Replaces: libismrmrd1.3'.
Ignoring request to change the title of bug#974045 to the same title
> thanks
Stopping processing here.

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

Processed: forcibly merging 973938 974045

[Debian Bug Tracking System]

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

> forcemerge 973938 974045
Bug #973938 [libismrmrd1.4] libismrmrd1.4: Missing Breaks+Replaces: 
libismrmrd1.3
Bug #974045 [libismrmrd1.4] libismrmrd1.4: missing Breaks+Replaces: 
libismrmrd1.3 (>= 1.4)
Merged 973938 974045
> thanks
Stopping processing here.

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

Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"

[Andreas Tille]

On Wed, Nov 11, 2020 at 11:09:32AM +0100, Maarten L. Hekkelman wrote:
> Hi Juhani,
> 
> Bug #974074 is in fact a bug in MRS. However, the bug report does contain a
> useful observation, the usage of the various override_dh_auto_configure
> rules in libzeep is incorrect and no shared library is created.
> 
> Now the question is, is a shared library really required?

Yes, definitely.

> If so I will have
> to go back to the drawing board and redesign the makefiles in the upstream
> project to create proper shared libraries, including a version numbering
> scheme.

Usually a library package should feature both:  Shared is mandatory and
static recommended.  The shared library should have a proper SOVERSION.

Kind regards

   Andreas.

> regards, -maarten
> 
> 
> Op 11-11-2020 om 09:13 schreef Juhani Numminen:
> > On Tue, 10 Nov 2020 23:03:57 +0100 Sebastian Ramacher 
> >  wrote:
> > > Hi Marten
> > > 
> > > On 2020-11-10 07:42:45 +0100, Maarten L. Hekkelman wrote:
> > > ...
> > > > Sorry, long story. To make it short.
> > > > - Keep mrc, no problem there
> > > > - Upgrade libzeep to version 5
> > > > 
> > > Thanks for the detailed explanation. The first two steps are almost done
> > > The current versions of mrc and libzeep should be able to migrate soon
> > > as their RC bugs have been fixed.
> > > ...
> > Right, but one RC bug is not fixed yet: libzeep packages are missing the
> > shared library altogether; the .so files are not there.
> > 
> > For that we have bug #974074, and see gregor's message for suggested fix.
> > It seems he is confident in the first diff of that mail, while the latter 
> > diff
> > is more speculative.
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974074#19
> > 
> > 
> > Regards,
> > Juhani
> > 
> > 
> 
> -- 
> Maarten L. Hekkelman
> Cataloniëstraat 3
> 6663NJ Lent
> 
> http://www.hekkelman.com/
> +31 24 348 0192
> 
> 

-- 
http://fam-tille.de

Bug#973405: fakeroot on amd64 stopped supporting armel, armhf and mipsel chroots

[Johannes Schauer]

Hi,

Quoting Johannes Schauer (2020-11-10 09:49:59)
> On Fri, 30 Oct 2020 09:28:22 +0100 Johannes Schauer  wrote:
> > The offending commit is:
> > > commit 2a53909e732b19ccbaf6d1534e932dff74fa757e (refs/bisect/bad)
> > > Author: Vasyl Gello 
> > > Date:   Fri Oct 2 03:48:45 2020 +
> > > 
> > > Use fixed-width members in fake_msg
> > > 
> > >  * Also usevthe same padding on all architectures
> > >  * Fixes cross-architecture SysV IPC connection failures
> > >(i.e using system-wide fakeroot in chroot-ed jails)
> > 
> > If I revert that commit on the current master branch, then everything works
> > fine again, thus I'm tagging this bug with "patch".
> > 
> > Please either fix this issue or revert the commit until you have a solution
> > that doesn't break this use-case. It currently makes the mmdebstrap
> > autopkgtest fail and thus will block it from migration to testing (thus
> > raising severity).
> 
> since there has been no activity on this RC bug for 10 days, I made a NMU with
> a delay of seven days. Please chime in if you'd like me to cancel the upload. 
> I
> attached the debdiff of my NMU to this message.

additionally, I prepared an autopkgtest (attached) which is able to test the
functionality that broke. Unfortunately, neither salsaci nor debci support
binfmt_misc, which is necessary for qemu-user mode. That's why the test is run
inside a qemu virtual machine. Since neither salsaci nor debci support kvm, the
test is way too slow to run on either. Consider this script an option for once
binfmt_misk or kvm is available on our infrastructure. But even without it, you
can run the script yourself on your own machine. Since it's using qemu, you
don't need superuser privileges either.

To still regularly test for this bug, I created a jenkins job running a script
doing nearly the same as the attached script. The main difference is, that it
only takes the fakeroot packages from the archive and does not support
crosscompiling the foreign architecture binaries. As you can see, the test
correctly reports "failed architectures:  armel armhf mipsel s390x".

https://jenkins.debian.net/job/fakeroot-foreign-worker/20/consoleFull

Once this bug is fixed, the job should succeed.

Thanks!

cheers, josch#!/bin/sh

# Copyright 2019 Johannes 'josch' Schauer 
#
# Permission is hereby granted, free of charge, to any person obtaining a copy
# of this software and associated documentation files (the "Software"), to deal
# in the Software without restriction, including without limitation the rights
# to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
# copies of the Software, and to permit persons to whom the Software is
# furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in all
# copies or substantial portions of the Software.

# This script tests, whether fakeroot can be used to create foreign
# architecture chroots. This is to find bugs like #973405 early.
#
# Currently, there is no machine level isolation for autopkgtest jobs as run by
# salsaci and debci. Foreign architecture fakeroot relies on qemu binfmt
# support which is not provided by either. We thus first build a virtual
# machine and then run the tests inside of it.
#
# If the package is not yet released, foreign architecture versions of the
# libfakeroot binary will be cross-compiled on-the-fly.
#
# If the package is released and this test is run on unstable, then M-A version
# skews are ignored
#
# If the package is released and this test is run anywhere else, then
# uninstallable foreign architecture libraries will be an error.

set -exu

if [ "$(dpkg --print-architecture)" != "amd64" ]; then
# creating the bootable qemu machine is only supported for amd64
echo "W: Architecture isn't amd64, skipping test." >&2
exit 77
fi

# the archive with the highest priority where the base-files package comes from
# determines whether we are on stable, testing or unstable
DEFAULT_DIST=$(cat << END | python3 -
import apt_pkg, sys
apt_pkg.init()
c = apt_pkg.Cache(None)
d = apt_pkg.DepCache(c)
s = apt_pkg.SourceList()
s.read_main_list()

highest_prio = -1
highest_archive = None
for pkgfile, _ in d.get_candidate_ver(c["base-files"]).file_list:
	print("processing: %s"%pkgfile, file=sys.stderr)
	index = s.find_index(pkgfile)
	if index is None:
		print("index is none -- skipping", file=sys.stderr)
		continue
	if not index.is_trusted:
		print("index is not trusted -- skipping", file=sys.stderr)
		continue
	archive = pkgfile.archive
	if archive not in ["stable", "testing", "unstable"]:
		print("index archive %s is %s -- skipping"%(index, archive), file=sys.stderr)
		continue
	prio = d.policy.get_priority(pkgfile)
	if prio > highest_prio:
		highest_prio = prio
		highest_archive = archive
if highest_archive is None:
	print("highest priority apt archive is neither stable, testing or unstable", file=sys.stderr)
	for f in c.file_list:
		

Processed: Bug#972912 marked as pending in ldb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #972912 [src:ldb] ldb ftbfs with python3.9
Added tag(s) pending.

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

Bug#971142: varnish-modules: diff for NMU version 0.16.0-2.1

[Stig Sandbeck Mathisen]

Adrian Bunk  writes:

> Control: tags 971142 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for varnish-modules (versioned as 0.16.0-2.1) and
> uploaded it to DELAYED/14. Please feel free to tell me if I should
> cancel it.

Hello Adrian,

Thank you for taking the time to do a package upload with a patch for
this bug. Feel free to leave in the delayed queue, or upload immediately
if you have the time.

-- 
Stig Sandbeck Mathisen
Debian Developer

Bug#972912: marked as pending in ldb

[Mathieu Parent]

Control: tag -1 pending

Hello,

Bug #972912 in ldb 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/samba-team/ldb/-/commit/6216bd5b2f22538334a7e51ca9e0c1cfda5b3cf7


Generate python3-ldb.symbols to build on all python3 versions (Closes: #972912)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/972912

Bug#974207: psi-plus: FTBFS with Qt 5.15

[Andreas Beckmann]

Source: psi-plus
Version: 1.4.554-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

psi-plus recently started to FTBFS due to some Qt problems:

/build/psi-plus-1.4.1231/src/plugins/generic/screenshotplugin/screenshot.cpp: 
In member function 'virtual void GrabAreaWidget::paintEvent(QPaintEvent*)':
/build/psi-plus-1.4.1231/src/plugins/generic/screenshotplugin/screenshot.cpp:176:26:
 error: aggregate 'QPainterPath path' has incomplete type and cannot be defined
  176 | QPainterPath path;
  |  ^~~~

The attached buildlog is from experimental, but the sid version has the same 
problems.


Andreas


psi-plus_1.4.1231-1.log.gz
Description: application/gzip

Bug#966914: marked as done (sambamba: FTBFS: collect2: error: ld returned 1 exit status)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 09:34:43 +
with message-id 
and subject line Bug#966914: fixed in sambamba 0.7.1-5
has caused the Debian Bug report #966914,
regarding sambamba: FTBFS: collect2: error: ld returned 1 exit status
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.)


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

Hi,

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

Relevant part (hopefully):
> ldc2  -of=sambamba sambamba.p/sambamba_main.d.o sambamba.p/sambamba_depth.d.o 
> sambamba.p/sambamba_fixbins.d.o sambamba.p/sambamba_flagstat.d.o 
> sambamba.p/sambamba_index.d.o sambamba.p/sambamba_markdup2.d.o 
> sambamba.p/sambamba_markdup.d.o sambamba.p/sambamba_merge.d.o 
> sambamba.p/sambamba_pileup.d.o sambamba.p/sambamba_slice.d.o 
> sambamba.p/sambamba_sort.d.o sambamba.p/sambamba_subsample.d.o 
> sambamba.p/sambamba_utils_common_bed.d.o 
> sambamba.p/sambamba_utils_common_file.d.o 
> sambamba.p/sambamba_utils_common_filtering.d.o 
> sambamba.p/sambamba_utils_common_intervaltree.d.o 
> sambamba.p/sambamba_utils_common_ldc_gc_workaround.d.o 
> sambamba.p/sambamba_utils_common_overwrite.d.o 
> sambamba.p/sambamba_utils_common_pratt_parser.d.o 
> sambamba.p/sambamba_utils_common_progressbar.d.o 
> sambamba.p/sambamba_utils_common_queryparser.d.o 
> sambamba.p/sambamba_utils_common_readstorage.d.o 
> sambamba.p/sambamba_utils_common_tmpdir.d.o 
> sambamba.p/sambamba_utils_view_alignmentrangeprocessor.d.o 
> sambamba.p/sambamba_utils_view_headerserializer.d.o 
> sambamba.p/sambamba_validate.d.o sambamba.p/sambamba_view.d.o 
> sambamba.p/utils_lz4.d.o sambamba.p/utils_strip_bcf_header.d.o 
> sambamba.p/utils_version_.d.o sambamba.p/cram_exception.d.o 
> sambamba.p/cram_htslib.d.o sambamba.p/cram_reader.d.o 
> sambamba.p/cram_reference.d.o sambamba.p/cram_slicereader.d.o 
> sambamba.p/cram_wrappers.d.o sambamba.p/cram_writer.d.o 
> sambamba.p/thirdparty_mergesort.d.o sambamba.p/thirdparty_unstablesort.d.o 
> sambamba.p/_build_sambamba-s4fhbx_sambamba-0.7.1_obj-x86_64-linux-gnu_utils_ldc_version_info_.d.o
>  -L=--allow-shlib-undefined -link-defaultlib-shared -O -g -release -wi -L=-z 
> -L=relro -L=/usr/lib/x86_64-linux-gnu/libbiod.a 
> -L=/usr/lib/x86_64-linux-gnu/libz.a -L=/usr/lib/x86_64-linux-gnu/libhts.a 
> -L=-z -L=relro -L=-z -L=now -L=-flto -fvisibility=hidden 
> -L=/usr/lib/x86_64-linux-gnu/libbz2.a 
> -L=/usr/lib/x86_64-linux-gnu/libdeflate.a -L=-lm -L=-lpthread 
> -L=/usr/lib/x86_64-linux-gnu/liblzma.a 
> /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/liblz4.so 
> /usr/lib/x86_64-linux-gnu/libcurl.so /usr/lib/x86_64-linux-gnu/libcrypto.so 
> /usr/lib/x86_64-linux-gnu/liblzma.so -L=-rpath 
> -L=/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu
>  -L=-rpath-link -L=/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu 
> -L=-rpath-link -L=/usr/lib/x86_64-linux-gnu
> lto1: fatal error: bytecode stream in file 
> ‘/usr/lib/x86_64-linux-gnu/libhts.a’ generated with GCC compiler older than 
> 10.0
> compilation terminated.
> lto-wrapper: fatal error: /usr/bin/cc returned 1 exit status
> compilation terminated.
> /usr/bin/ld.gold: fatal error: lto-wrapper failed
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/sambamba_0.7.1-4_unstable.log

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

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: sambamba
Source-Version: 0.7.1-5
Done: =?utf-8?q?=C3=89tienne_Mollier?= 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated sambamba 

Bug#961154: debarchiver: diff for NMU version 0.11.5+nmu1

[Ola Lundqvist]

Thank you

On Tue, 10 Nov 2020 at 23:51, Dominic Hargreaves  wrote:

> Control: tags 961154 + patch
> Control: tags 961154 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for debarchiver (versioned as 0.11.5+nmu1) and
> uploaded it to DELAYED/0. Please feel free to tell me if I
> should delay it longer.
>
> Regards.
>
>

-- 
 --- Inguza Technology AB --- MSc in Information Technology 
|  o...@inguza.como...@debian.org|
|  http://inguza.com/Mobile: +46 (0)70-332 1551 |
 ---

Bug#974043: marked as done (hnswlib: baseline ABI violation: built with -march=native)

[Debian Bug Tracking System]

Your message dated Wed, 11 Nov 2020 09:04:33 +
with message-id 
and subject line Bug#974043: fixed in hnswlib 0.4.0-3
has caused the Debian Bug report #974043,
regarding hnswlib: baseline ABI violation: built with -march=native
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.)


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

Dear maintainer,

>From the build logs, this package is built using the -march=native
GCC option. This means the CPU features are determined at build time and
depends on the build host. Those features are not necessarily available
on the users hardware, thus rendering the program unusable from them.
This is a baseline ABI violation.

Regards,
Aurelien
--- End Message ---
--- Begin Message ---
Source: hnswlib
Source-Version: 0.4.0-3
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated hnswlib 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, 11 Nov 2020 03:36:36 +0530
Source: hnswlib
Architecture: source
Version: 0.4.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Nilesh Patra 
Closes: 974043
Changes:
 hnswlib (0.4.0-3) unstable; urgency=medium
 .
   * Team Upload.
   [ Andreas Tille ]
   * Fix syntax
 .
   [ Nilesh Patra ]
   * Remove -march=native flags (Closes: #974043)
   * Limit archs for testing
Checksums-Sha1:
 52f355a01ed1b371fae8f713243972466c641af4 2150 hnswlib_0.4.0-3.dsc
 227a2b69ae43c314e5f5e4cf21d39ff3fc75d29a 10364 hnswlib_0.4.0-3.debian.tar.xz
 ab8eb52bc9a800e1f33aca1ea796c5abcd202157 7606 hnswlib_0.4.0-3_amd64.buildinfo
Checksums-Sha256:
 63bf0b15b72dc3436ab18ddcfa25df46b623f1896e0b45b4bcd902b703adab2a 2150 
hnswlib_0.4.0-3.dsc
 37f5635180fc1f3eed7839c6d14c1d3faf62ee9204398f3a5279a5ac3344e0af 10364 
hnswlib_0.4.0-3.debian.tar.xz
 d3b20391bd19d56560b02eec55e923e468159c0ea1c078bb92b451a08950b000 7606 
hnswlib_0.4.0-3_amd64.buildinfo
Files:
 873af1031d9032ebb3800e92bf55aa91 2150 science optional hnswlib_0.4.0-3.dsc
 0d9fb2c6515f0a7113d0c8b79c4151cd 10364 science optional 
hnswlib_0.4.0-3.debian.tar.xz
 9c50a91f28b5750c4f5f38a0fa78b73a 7606 science optional 
hnswlib_0.4.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAl+rpgkUHG5wYXRyYTk3
NEBnbWFpbC5jb20ACgkQALrnSzQzafEq2w/9HyK6OXXuJ0+ipBXDA7GqUqh3f6pA
PHUP1a9ZpkcAhBvT0foe0AxUHVMsCE8Xjm4dzPM0p0yISAprfd8aqkNreN3XJRjl
mB1W2ON2JPVcEzPchBIXjRXPaIJBwsS69x5i8E/D3Mf5XbHIUSGZ+GCQ0VQlEWmy
NWCyD8ZOJQ+eqtQZyk7dq4TqX4NalPsvqgjJFcxGAB/ZAttDo5CwvmS3FiVcSACk
WxBP/haErqC1OVbK10XJ6R5rCqY3Y0OrjOaUaF4pTxnhsfr67AYVc6VHMc4373OU
GTnzCULNh5Ut6a7K3SwYBYxnXbF4beqYHhVMdDrNnXCv0N+rspRx3rownATg0wa0
uJbHIpXoxWU/eeXL2Qgp2qAI3IfOMDFVwDI+SospYwQpo87X00xUqhLqWW1zuUB8
B92e0QipgkWF0eo+SSw8qivEA6JwQLQLnM17GYBgI3NXnqMXFRkjS9dvuSdWsMAp
mbjv1fZO3+wCVzlbJ84tY29120wSdUwpRb4yyOXzi2aXSzYoukjzU7v4172Z3fFk
If7mfbnpjpVtoIN6xJjvM5DIbDLqdC22Fqjk1yPlQWQNyUUVNPgQMjzWzIuPlLJa
o1TSXUV+KBdcPBjgMNHe4l7kKEnqi2BU1exw9YpVCMZ2Gt7gStc4y/DdCcndp97o
O3AzWGCLu9Spdgk=
=tVQV
-END PGP SIGNATURE End Message ---

Bug#974197: rust-hdrhistogram: unsatisfiable build-dependency

[Ralf Treinen]

Source: rust-hdrhistogram
Version: 6.3.4-2
Severity: serious
User: trei...@debian.org
Usertags: edos-uninstallable

Hi,

rust-hdrhistogram build-depends on
librust-base64-0.11+default-dev | librust-base64-0.10+default-dev.
However, neither of these exists in sid or in the NEW queue.

-Ralf.