Bug#977208: exim4 install failed

[Jörg Frings-Fürst]

Hello Andreas,

after 

 apt install libgnutls30=3.6.15-4

the missing libgnutls-dane0 can installed and all dependencies are
fixed.

So I close this bug.

Many thanks.

CU
Jörg



-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#977208: marked as done (exim4 install failed)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 08:31:51 +0100
with message-id 
and subject line Re: Bug#977208: exim4 install failed
has caused the Debian Bug report #977208,
regarding exim4 install failed
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.)


-- 
977208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exim4
Version: 4.94-9
Severity: grave

Hello,

on a fresh bullseye/sid installation I get:

[qoute]
# apt update && apt install exim4
Hit:1 https://wire-app.wire.com/linux/debian stable InRelease
Hit:2 https://linux.teamviewer.com/deb stable InRelease
Hit:3 https://repo.skype.com/deb stable InRelease
Hit:4 https://josm.openstreetmap.de/apt alldist InRelease
Hit:5 http://security.debian.org/debian-security bullseye-security InRelease
Hit:6 http://mirror.1und1.de/debian unstable InRelease
Hit:7 http://deb.debian.org/debian bullseye InRelease
Hit:8 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:10 https://download.jitsi.org stable/ InRelease
Hit:9 https://packagecloud.io/AtomEditor/atom/any any InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 exim4 : Depends: exim4-daemon-light (>= 4.94-9) but it is not installable or
  exim4-daemon-heavy (>= 4.94-9) but it is not installable or
  exim4-daemon-custom (>= 4.94-9) but it is not installable
E: Unable to correct problems, you have held broken packages.
[/quote]

But all packages have the right version:


[quote]
# apt policy exim4*
exim4-daemon-light:
  Installed: (none)
  Candidate: 4.94-9+b1
  Version table:
 4.94-9+b1 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    300 http://mirror.1und1.de/debian unstable/main amd64 Packages
exim4-daemon-heavy:
  Installed: (none)
  Candidate: 4.94-9+b1
  Version table:
 4.94-9+b1 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    300 http://mirror.1und1.de/debian unstable/main amd64 Packages
exim4-daemon-custom:
  Installed: (none)
  Candidate: (none)
  Version table:

exim4:
  Installed: (none)
  Candidate: 4.94-9
  Version table:
 4.94-9 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    300 http://mirror.1und1.de/debian unstable/main amd64 Packages
[/quote]

If you need some more infos ask me.


CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 exim4 depends on:
ii  debconf [debconf-2.0] 
1.5.74
ii  exim4-base
4.94-9+b1
pn  exim4-daemon-light | exim4-daemon-heavy | exim4-daemon-custom 


exim4 recommends no packages.

exim4 suggests no packages.




signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Hello Andreas,

after 

 apt install libgnutls30=3.6.15-4

the missing libgnutls-dane0 can installed and all dependencies are
fixed.

So I close this bug.

Many thanks.

CU
Jörg



-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old

Bug#974580: marked as done (bambootracker FTBFS on 32bit)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 07:18:19 +
with message-id 
and subject line Bug#974580: fixed in bambootracker 0.4.5+git20121209-1
has caused the Debian Bug report #974580,
regarding bambootracker FTBFS on 32bit
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.)


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

https://buildd.debian.org/status/package.php?p=bambootracker&suite=sid

...
midi/RtMidi/RtMidi.cpp: In function ‘void* alsaMidiHandler(void*)’:
midi/RtMidi/RtMidi.cpp:1664:26: error: comparison of integer expressions of 
different signedness: ‘unsigned int’ and ‘__syscall_slong_t’ {aka ‘long int’} 
[-Werror=sign-compare]
 1664 |   if ( x.tv_nsec < y.tv_nsec ) {
  |~~^~~
...


The best solution would be to use librtmidi-dev instead of
an own copy.

The quick workaround would be to stop forcing errors
in CPP_WARNING_FLAGS in BambooTracker/BambooTracker.pro
--- End Message ---
--- Begin Message ---
Source: bambootracker
Source-Version: 0.4.5+git20121209-1
Done: =?utf-8?q?G=C3=BCrkan_Myczko?= 

We believe that the bug you reported is fixed in the latest version of
bambootracker, 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.
Gürkan Myczko  (supplier of updated bambootracker package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 09 Dec 2020 07:48:47 +0100
Source: bambootracker
Architecture: source
Version: 0.4.5+git20121209-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Gürkan Myczko 
Closes: 974580
Changes:
 bambootracker (0.4.5+git20121209-1) unstable; urgency=medium
 .
   * New upstream version.
   * d/control: build-depends librtmidi-dev added. (Closes: #974580)
Checksums-Sha1:
 644875b51a9d41025d058053d53dcb844afa2194 2167 
bambootracker_0.4.5+git20121209-1.dsc
 6eacd4b4e2ab04dfb6ab56be055223d554a3e69c 3311177 
bambootracker_0.4.5+git20121209.orig.tar.gz
 36b86d0bdcd7e3d6d531365c62c237df59a1e65b 9216 
bambootracker_0.4.5+git20121209-1.debian.tar.xz
 721199220938d27b741da42eb29d3fb41b0d789c 12087 
bambootracker_0.4.5+git20121209-1_source.buildinfo
Checksums-Sha256:
 2c01965e5f4da86a01b9c5a23330a6675f7f1dcb85aeaa95b4904f83afbc02cb 2167 
bambootracker_0.4.5+git20121209-1.dsc
 fd91a8f66c23e3eea7bd379606a47d11dcfad0f1c142fb89819a6d35781043c6 3311177 
bambootracker_0.4.5+git20121209.orig.tar.gz
 3ed1e81375e5c6adbb4278bc77cc577389517783e43a93547f808ddf5e8a45c6 9216 
bambootracker_0.4.5+git20121209-1.debian.tar.xz
 ec8b5ae56e77c7780560e6db3ee1641913256d248b39a2ea4499053abec6dbdd 12087 
bambootracker_0.4.5+git20121209-1_source.buildinfo
Files:
 92f130e5639574c340612c6ad881858d 2167 sound optional 
bambootracker_0.4.5+git20121209-1.dsc
 e78937a64c19b868ef3a0bfa2b4da92c 3311177 sound optional 
bambootracker_0.4.5+git20121209.orig.tar.gz
 f245df257d8123378de8196419a9b64a 9216 sound optional 
bambootracker_0.4.5+git20121209-1.debian.tar.xz
 de809857c00ad06bc1f240609cd24968 12087 sound optional 
bambootracker_0.4.5+git20121209-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl/Vuj8ACgkQweDZLphv
fH4vmA/+MaZQ77qlaCKmtyzZHHvrVi+paTE+Ovaf8JkFZewxrVWLEgh3lXJeO3q2
iaewTM8pLeqJ6xvj6DcriyvAL5tv8KmQMtsfcZ1u71NjjXEqFmnKzzKa+N3fVpbQ
W/Gg2zCs1nnDoT6KrBYb/shRxAw+GdWNtCEDFfTumw5KKTvLHyipsg+8HpC8GdG2
qQXeJGZfZr9hZOKIBlGRV10a9D6gD+or3Cy6RF5eoiCqxgJEJE67+hrzykzoVMU3
hK7GwGds2ayMHt4bMAUMXtQvpvWqmjSe+sKAY8A0Yeff0aP7KjRA7cOtc2jX9wQf
3sSaRC0LynbLYO0ksiGzgf/PEPgdUe1gw6FHk7/RUlxwhPcQtj9qOMkUvRF/Zcn9
PngqD74xchiHE5wFKGl8FsxdpriaLsf1um1v5jexTTklUnm3PXIFLb1MXPwF9+CI
ypyASCxkRoZcQGW9Q8mR8Vf3GR+Cjpyn5VkgeuacdmDev1yEYsCwiQVMbWVyy1LJ
PUsR6nJMhFqSR5OCK2cDgcXnzld34hi2zncJ1M4x9B0146M370OV1qKahUENgAuP
lYKLTsYBx6z3mWSUMk1yyHt4s8qo46ReCs5GAc9mVRHDGxJUjHCRbg334VlNR3bZ
Ydgc4ObcxFhMb+nGj4SaNquT0y9DzOuhP5abkMsIm/ZWtRQslSw=
=fCmN
-END PGP SIGNATURE End Message ---

Bug#976735: spyder needs source upload for Python 3.9 transition

[Julian Gilbey]

On Mon, Dec 07, 2020 at 05:38:26PM +0200, Adrian Bunk wrote:
> Package: spyder
> Version: 3.3.6+dfsg1-5
> Severity: serious
> 
> Since binNMUs are not possible for binary-all packages,
> a source upload is needed for the Python 3.9 transition.
> 
> In a more general note, does /usr/bin/spyder3 have to use
> the versioned interpreter instead of python3?

The versioned interpreter can be avoided by removing '{interpreter} '
from the definition of PYBUILD_AFTER_INSTALL in debian/rules.

Best wishes,

   Julian

Bug#977252: build against boost1.74 causes symbols file changes, ABI change?

[Matthias Klose]

Package:src:libkolabxml
Version: 1.2.0-1
Severity: serious
Tags: sid bullseye ftbfs

the build against boost1.74 causes symbols file changes on all architectures. Is
this an ABI change, or should the symbol files just be adjusted? See

https://buildd.debian.org/status/fetch.php?pkg=libkolabxml&arch=arm64&ver=1.2.0-1%2Bb2&stamp=1607766571&raw=0

Bug#977208: exim4 install failed

[Jörg Frings-Fürst]

Hello Andreas,

Am Samstag, dem 12.12.2020 um 16:27 +0100 schrieb Andreas Metzler:
> On 2020-12-12 Jörg Frings-Fürst  wrote:
> > Package: exim4
> > Version: 4.94-9
> > Severity: grave
> 
> > Hello,
> 
> > on a fresh bullseye/sid installation I get:
> 
> > [qoute]
> > # apt update && apt install exim4
> > Hit:1 https://wire-app.wire.com/linux/debian stable InRelease
> [...]
> 
> Please, try apt dist-upgrade first.
> 

It is the same:

[quote]
# apt update && apt dist-upgrade && apt install exim4
Hit:1 https://linux.teamviewer.com/deb stable InRelease
Hit:2 https://repo.skype.com/deb stable InRelease 
Hit:3 https://josm.openstreetmap.de/apt alldist InRelease 
Hit:4 https://wire-app.wire.com/linux/debian stable InRelease 
Hit:5 http://mirror.1und1.de/debian unstable InRelease
Hit:6 http://deb.debian.org/debian bullseye InRelease 
Hit:7 http://security.debian.org/debian-security bullseye-security
InRelease 
Hit:8 http://dl.google.com/linux/chrome/deb stable InRelease  
Hit:9 https://download.jitsi.org stable/ InRelease
Hit:10 https://packagecloud.io/AtomEditor/atom/any any InRelease
Reading package lists... Done
Building dependency tree   
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 exim4 : Depends: exim4-daemon-light (>= 4.94-9) but it is not
installable or
  exim4-daemon-heavy (>= 4.94-9) but it is not
installable or
  exim4-daemon-custom (>= 4.94-9) but it is not
installable
E: Unable to correct problems, you have held broken packages.
[/quote]

> cu Andreas
> 

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#976382: marked as done (FTBFS against octave 6: plplot_octaveOCTAVE_wrap.cxx:1768:10: error: ‘oct_mach_info’ has not been declared)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 06:35:10 +
with message-id 
and subject line Bug#976382: fixed in plplot 5.15.0+dfsg-17
has caused the Debian Bug report #976382,
regarding FTBFS against octave 6: plplot_octaveOCTAVE_wrap.cxx:1768:10: error: 
‘oct_mach_info’ has not been declared
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.)


-- 
976382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:plplot
Version: 5.15.0+dfsg-16
Severity: important
Tags: ftbfs fixed-in-experimental
Control: fixed -1 5.15.0+dfsg-16+gnat10

Dear Maintainer,

plplot FTBFS against octave 6.1.0, which currently sits in experimental. A
build log is attached.

The problem comes from swig, which is not (yet) compatible with octave 6. The
problem has been reported upstream, and it is unclear when it will be fixed:
https://github.com/swig/swig/issues/1893

I see that the problem has been fixed in the version of plplot that stands in
experimental (by simply dropping the octave bindings). I nevertheless opened
this bug report for facilitating the tracking of the octave 6 transition.

The severity of this bug report will be raised once octave 6.1.0 is uploaded
to unstable.

Thanks for your work,

--
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org
--- End Message ---
--- Begin Message ---
Source: plplot
Source-Version: 5.15.0+dfsg-17
Done: =?utf-8?q?Rafael_Laboissi=C3=A8re?= 

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

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

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

Debian distribution maintenance software
pp.
Rafael Laboissière  (supplier of updated plplot package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Dec 2020 16:50:17 -0300
Source: plplot
Architecture: source
Version: 5.15.0+dfsg-17
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Rafael Laboissière 
Closes: 976382
Changes:
 plplot (5.15.0+dfsg-17) unstable; urgency=medium
 .
   * Upload to unstable. This version does not ship octave-plplot
 (Closes: #976382)
   * Allow proper development with libraries libcsiro(csa|nn)
 + d/control: Add dependencies on libcsiro(csa|nn)0
 + d/libplplot-dev.install: Include header files csa.h and nn.h
   * Add symbols files for all non-C++ shared library shipped in the package
   * d/p/python3-interpreter-in-examples.patch: New patch
   * Override Lintian warnings no-symbols-control-file for
 d/lib*.symbols files containing C++ mangled symbols
   * d/control: Bump Standards-Version to 4.5.1 (no changes needed)
Checksums-Sha1:
 6403b142dca95b0d69691f6b61002481843f5aa6 4411 plplot_5.15.0+dfsg-17.dsc
 00288b5354a5043687b3eb30eddf4042a488c0d1 66332 
plplot_5.15.0+dfsg-17.debian.tar.xz
 3acc6f779c22fc52d87df70d2b5494688a955bf6 36947 
plplot_5.15.0+dfsg-17_amd64.buildinfo
Checksums-Sha256:
 0b8620f9a76626b45458f015c3213b87996e1fefafe96f6035576f3789f411d3 4411 
plplot_5.15.0+dfsg-17.dsc
 9b6b11f83a9a0e96c9b1bbd6d9660d37f6125a16838704862acdb73c463bca60 66332 
plplot_5.15.0+dfsg-17.debian.tar.xz
 7a62701018e9e80c766fed03bbb915f76353509a38790c52adc7abf0a4b089e2 36947 
plplot_5.15.0+dfsg-17_amd64.buildinfo
Files:
 7f6f5f8962c177c3987e20c5004f178c 4411 math optional plplot_5.15.0+dfsg-17.dsc
 876f740fd27f873213882350c5a27d8a 66332 math optional 
plplot_5.15.0+dfsg-17.debian.tar.xz
 1d574146324adbba6992e5b9641f6072 36947 math optional 
plplot_5.15.0+dfsg-17_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAl/VrtsACgkQISSqGYN4
XJCqXQ/8CrCv9ZdUJV/fU3XUOX6WCRTTCwXuF1Khc+Kl6rYFudQyvoudtp6s2h8b
BvfE9sTDLe7p8SZ+nSvZSfpNciIW19GRAWOlG7Rbzguzo3801b+/HifYgdSQcnca
D+X0/fIMxBc02Awwq5BD3oRy1bZDmzXBFFgWQBzyzdtjK9VqWf992T4M7quoQryJ
k12jxANLu224v47MFAKvW9vAbCi7qjiqUaElZRIttGBWuMc+nU7Jl0HYz7LIFH8F
sUI82RWfb9wSMshVjxJG4e1JPbZANRCXkRy5o0zyUYMueYVwkKKF/IuQcvP3nAK2
2n6Fi1M1OGLw7Ug3wS2d11Vf1sWaZ/zzrUVUXx2+6XXN6SUcqRActuTXTfAc9WST
2LyyHmsLWMs1oZPS8LO1EGQttxMxZecX+GxWtLqag8mfMcpNiCUmVk+LnrM0W

Bug#969063: marked as done (fgetty: shared binary linked against libc6, but no dependency)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 05:48:31 +
with message-id 
and subject line Bug#969063: fixed in fgetty 0.7-7
has caused the Debian Bug report #969063,
regarding fgetty: shared binary linked against libc6, but no dependency
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.)


-- 
969063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fgetty
Version: 0.7-6
Severity: serious
Tags: patch
Justification: Policy 8.6

Hi,

fgetty ships a few static binaries, but also one shared binary linked
against glibc:

| $ ldd ./bin/checkpassword.login
| linux-vdso.so.1 (0x7ffdd0be6000)
| libcrypt.so.1 => /usr/lib/x86_64-linux-gnu/libcrypt.so.1 
(0x7f9cc1429000)
| libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f9cc1264000)
| /lib64/ld-linux-x86-64.so.2 (0x7f9cc14a5000)

However the fgetty package doesn't depend on any package. This is
because ${shlibs:Depends} is missing in the debian/control file.

This patch fixes the issue:

--- fgetty-0.7/debian/control
+++ fgetty-0.7/debian/control
@@ -10,7 +10,7 @@

 Package: fgetty
 Architecture: any
-Depends: ${misc:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends}
 Built-Using: ${Built-Using}
 Description: very small, efficient, console-only getty and login
  fgetty is a small, efficient, console-only getty for Linux.  It is derived


Regards,
Aurelien

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: fgetty
Source-Version: 0.7-7
Done: Lorenzo Puliti 

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

Debian distribution maintenance software
pp.
Lorenzo Puliti  (supplier of updated fgetty package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Dec 2020 22:45:28 +0100
Source: fgetty
Architecture: source
Version: 0.7-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Lorenzo Puliti 
Closes: 969063
Changes:
 fgetty (0.7-7) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Francisco M Neto  ]
   * Add minimal metadata file
   * Add two superficial autopkgtests
   * Bump DH version to 13
   * Set Rules-Requires-Root to no
   * Fix spelling error in patch-link-checkpassword
   * Set maintainer to QA Group (see #947640)
 .
   [ Lorenzo Puliti ]
   * Bump SV to 4.5.1, no changes required
   * d/control: Add shlibs:Depends (Closes: #969063)
 +  Thanks to Aurelien Jarno 
   * Cleanup unused lintian overrides
Checksums-Sha1:
 f7439449ff41800fc8c5f7cd22d96d54e7e1c9cc 2060 fgetty_0.7-7.dsc
 6e7257ffcce804d4e25c992854f3e9446c6e90e7 9184 fgetty_0.7-7.debian.tar.xz
 65293ff50cf6275fc8693ea6fd6043ad5b435ef5 5517 fgetty_0.7-7_source.buildinfo
Checksums-Sha256:
 98f526a23247cc920b20665777019cf6eb366940dd4a1bfda32055319ffe3b59 2060 
fgetty_0.7-7.dsc
 527cfae3b7ddd6c4fb3369b4271792cd096ef2b1d5b5293883821c4923913c29 9184 
fgetty_0.7-7.debian.tar.xz
 a3eb9ac20adbf008f204c6842fee2a936be96be3a6f9a97f946c07170918ea4e 5517 
fgetty_0.7-7_source.buildinfo
Files:
 2c91f25c967c6f28c8913a57e83db418 2060 admin optional fgetty_0.7-7.dsc
 c885f2cb10e92be9dbc7ac37ce749440 9184 admin optional fgetty_0.7-7.debian.tar.xz
 0d65ea2d0ad4ca24dd0e6dbe1f56e186 5517 admin optional 
fgetty_0.7-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl/VpfwACgkQweDZLphv
fH6iZg/+KaDB8WxE7wqFN1oadVNBAJ5kmGLt+1O+2PBQurSofvzoI+Hg2wtYxRAM
UgY7/vBuAJ6J195yGIP1KcaN7WeAU534stt1vKNYu7LPncDR85erdQHi6ixWT662
Hb2/UiEe/hODtQjtez65llLKRAhCiiyO2x00V/PXTUPGNLfg8mO4Pf8q6jt/DVaI
y/IJSmeJyxkDABDiwvKtpDQDdh7Az194jn8K0BrYb5IRuiIbuk+/VruzfcJ7TVSN
uvxsXoJBty8hjkFBaKKd5Aegsvt+CISoMmyrbmnnaoUSJ1xA7WhpybY+26RcqDlj
UaEug6BifTxkpPB+N1rj9+Iy1D0sTChxaTcg6nr5BFFTbpXa8Y4lk2fASURL2CMe
WAHf6ftU3C6NxSK7Rmb2cy+80AWkx6Ssh6YJSWXeskN6JbkSvY2G2YSJm9TtGNyh
4RLgOYboGVX8H1rkJsi2vlDV2DJyI7ok2EasVWCuce/1p8gJCw

Bug#973459: uim: FAIL: test-composer.scm

[Takatsugu Nokubi]

I made a simple patch to skip test-composer:
https://salsa.debian.org/debian/uim/-/commit/3cd351b6f2b15fb3161e1d00ed4c8ba26925429b
(Oh, I forgot to fix description of the patch)


2020年12月13日(日) 10:36 :

> Control: forwarded -1 https://github.com/uim/uim/issues/167
>
> On Sat, Dec 12, 2020 at 02:50:52PM +0100, Sebastian Ramacher wrote:
> > And it failed already twice for the Qt 5.15.2 transition, so I'm raising
> > the severity. Please investigate and fix this issue.
>
> Current upstream (not original authors who cannot get in touch) says
> it is difficult to investigate it.
>
> Nokubi-san, would we skip test-composer.scm for now?
>
> On my just grepping, composer.scm is only required by test-composer.scm.
> So it is no problem to skip test-composer.scm.
> --
> Regards,
> dai
>
> GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E
>

Bug#977170: marked as done (python3-unrardll needs a manual upload to drop Python 3.8 support)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 04:34:17 +
with message-id 
and subject line Bug#977170: fixed in unrardll 0.1.4-2
has caused the Debian Bug report #977170,
regarding python3-unrardll needs a manual upload to drop Python 3.8 support
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.)


-- 
977170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-unrardll
Version: 0.1.4-1
Severity: serious

Sources+binaries might be easier than a manual binNMU.
--- End Message ---
--- Begin Message ---
Source: unrardll
Source-Version: 0.1.4-2
Done: Norbert Preining 

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

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

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated unrardll package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Dec 2020 18:18:58 +0900
Source: unrardll
Binary: python3-unrardll python3-unrardll-dbgsym
Architecture: source amd64
Version: 0.1.4-2
Distribution: unstable
Urgency: medium
Maintainer: Norbert Preining 
Changed-By: Norbert Preining 
Description:
 python3-unrardll - Python wrapper for the unrar shared library
Closes: 977170
Changes:
 unrardll (0.1.4-2) unstable; urgency=medium
 .
   * Bump standards version, no changes necessary.
   * Rebuild for Python bump (Closes: #977170)
Checksums-Sha1:
 c91eb274d3c5168207264ea630ab86e1122a5256 1849 unrardll_0.1.4-2.dsc
 4edc55e12d36c24ba6cafeb4c011ad877cbe1c69 4992 unrardll_0.1.4-2.debian.tar.xz
 57b99b399042e77308aac24ee4ca0d5d6d8e4f63 26188 
python3-unrardll-dbgsym_0.1.4-2_amd64.deb
 6393b05ada26f531a0fb823702511a6a2dc3d493 12176 
python3-unrardll_0.1.4-2_amd64.deb
 62dcaedc82c4635ce0b8d1609628964f532b0c21 7327 unrardll_0.1.4-2_amd64.buildinfo
Checksums-Sha256:
 61308cdb31a2daca38ad3b2ecf37e68f265bc29caf6e75c174dcabf9e5e1c40e 1849 
unrardll_0.1.4-2.dsc
 17f9b80e1b8376c1524893eff3f6f21970e961619ac49605b0d7c311971748e6 4992 
unrardll_0.1.4-2.debian.tar.xz
 cd6cfce668bee842c4a91a067f8e057e9bf9249595bf2119d5fe99e822642ddf 26188 
python3-unrardll-dbgsym_0.1.4-2_amd64.deb
 1ba18368ed77ce1259e53966c45a1a71549e1c7f1fd139e748031d36bd706513 12176 
python3-unrardll_0.1.4-2_amd64.deb
 d8a0be6f5d3f66a2044b60bf8540180865e8680b3dfcc95163e127a808c48be8 7327 
unrardll_0.1.4-2_amd64.buildinfo
Files:
 6fd395709d77c1443238e39d20ab5240 1849 contrib/python optional 
unrardll_0.1.4-2.dsc
 5a99c8aca938ae70e5372bef3dbe7f20 4992 contrib/python optional 
unrardll_0.1.4-2.debian.tar.xz
 44a4b9f15a0740187e88420e981e40ad 26188 contrib/debug optional 
python3-unrardll-dbgsym_0.1.4-2_amd64.deb
 42d91ae4bcef3a5ee94f222004b783d1 12176 contrib/python optional 
python3-unrardll_0.1.4-2_amd64.deb
 87381a2238d6d601dbaf0101d25408ce 7327 contrib/python optional 
unrardll_0.1.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl/VlHEACgkQ2A4JsIcU
AGYdUwf6A3GFPH56zJbJPIGT2FwA4OItpnZf5wq4wNfYbNJFEQ5QRWwzCaXX9MUu
W1eX1o9in9kDAtBiNaxg/4VM2OwJDrkGarSTrg2vYAvF0T31gk00iKHtD9oOebDW
6ZJ+ox/TgFJIo0C4v/oIe3RqfPnyNEtfSjkmYH+OHXc4u4CDNM4kUGEOYczEE5gY
ESXYG62zKZHxAnYTW5DjCSL5Vx+Yivun92GMfUoJIHYW1JKHZ1Mz32D1o5RMBiYk
+dgMb49f8dNMgU85xV9sy4YH7x22QCjP/I9enwV9e7Go4UYGDpJVRMcf1O71Zhrk
fE7ec8pZi45dTMzBmJSoN70hhowwZQ==
=KLYj
-END PGP SIGNATURE End Message ---

Bug#977246: lutris should depend on python3-dbus

[Ernesto Domato]

Package: lutris
Version: 0.5.8.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: edo...@gmail.com

Hi,

The lutris package should depends on python3-dbus to work, or at least on my
recently installed system (were I didn't had python3-dbus installed) it refused
to work with this error:

Traceback (most recent call last):
  File "/usr/games/lutris", line 54, in 
from lutris.gui.application import Application  # pylint: disable=no-name-
in-module
  File "/usr/lib/python3/dist-packages/lutris/gui/application.py", line 37, in

from lutris.game import Game
  File "/usr/lib/python3/dist-packages/lutris/game.py", line 15, in 
from lutris.config import LutrisConfig
  File "/usr/lib/python3/dist-packages/lutris/config.py", line 8, in 
from lutris import settings, sysoptions
  File "/usr/lib/python3/dist-packages/lutris/sysoptions.py", line 13, in

from lutris.util.display import DISPLAY_MANAGER, SCREEN_SAVER_INHIBITOR,
USE_DRI_PRIME
  File "/usr/lib/python3/dist-packages/lutris/util/display.py", line 19, in

from lutris.util.graphics.displayconfig import MutterDisplayManager
  File "/usr/lib/python3/dist-packages/lutris/util/graphics/displayconfig.py",
line 4, in 
import dbus
ModuleNotFoundError: No module named 'dbus'

After installing python3-dbus it started working without problems.

Greets.
Ernesto



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

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

Versions of packages lutris depends on:
ii  cabextract   1.9-3
ii  curl 7.72.0-1
ii  fluid-soundfont-gs   3.1-5.1
ii  gir1.2-gnomedesktop-3.0  3.38.2-1
ii  gir1.2-gtk-3.0   3.24.24-1
ii  gir1.2-notify-0.70.7.9-2
ii  gir1.2-webkit2-4.0   2.30.3-1
ii  mesa-utils   8.4.0-1+b1
ii  p7zip16.02+dfsg-8
ii  psmisc   23.3-1
ii  python3  3.9.0-4
ii  python3-distro   1.5.0-1
ii  python3-gi   3.38.0-1+b2
ii  python3-magic2:0.4.15-5
ii  python3-pil  8.0.1-1+b1
ii  python3-requests 2.25.0+dfsg-1
ii  python3-setproctitle 1.2.1-1+b1
ii  python3-yaml 5.3.1-3+b1
ii  unzip6.0-25
ii  x11-xserver-utils7.7+8

Versions of packages lutris recommends:
ii  gvfs-backends1.46.1-1
pn  libwine-development  
ii  python3-evdev1.3.0+dfsg-1+b3
pn  winetricks   

Versions of packages lutris suggests:
ii  gamemode  1.6-1+b1

-- no debconf information

Processed: closing 975759

[Debian Bug Tracking System]

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

> close 975759
Bug #975759 [src:rust-hmac] rust-hmac: FTBFS: unsatisfiable build-dependencies: 
librust-digest-0.8+default-dev but it is not installable
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#957420: marked as done (lib3mf: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Sun, 13 Dec 2020 02:36:55 +
with message-id 
and subject line Bug#957420: fixed in lib3mf 1.8.1+ds-3.1
has caused the Debian Bug report #957420,
regarding lib3mf: 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.)


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

[...]
  
(arch=!ia64)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE17_M_emplace_uniqueIJS6_IS5_S5_S6_ISt17_Rb_tree_iteratorIS8_EbEDpOT_@Base
 1.8.0
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 1.8.0+ds
+#MISSING: 1.8.1+ds-3# 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS7_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 1.8.0+ds
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 1.8.0+ds
  (arch=!alpha !armel !armhf !hurd-i386 !i386 !kfreebsd-i386 !mips !mipsel 
!powerpc !powerpcspe !ppc64 
!s390x)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 1.8.0
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE4findERS7_@Base
 1.8.0+ds
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE7_M_copyINSE_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS8_EPKSI_PSt18_Rb_tree_node_baseRT_@Base
 1.8.0+ds
+#MISSING: 1.8.1+ds-3# 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE7_M_copyINSE_11_Alloc_nodeEEEPSt13_Rb_tree_nodeIS8_EPKSI_PSt18_Rb_tree_node_baseRT_@Base
 1.8.0+ds
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 1.8.0+ds
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EEC1ERKSE_@Base
 1.8.1+ds-3
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EEC2ERKSE_@Base
 1.8.1+ds-3
  
(optional=templinst|arch=ia64)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_St10shared_ptrIN3NMR14CModelMetaDataEEESt10_Select1stISC_ESt4lessIS5_ESaISC_EE16_M_insert_uniqueIS6_IS5_SB_EEES6_ISt17_Rb_tree_iteratorISC_EbEOT_@Base
 1.8.0
  
(arch=!ia64)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_St10shared_ptrIN3NMR14CModelMetaDataEEESt10_Select1stISC_ESt4lessIS5_ESaISC_EE17_M_emplace_uniqueIJS6_IS5_SB_S6_ISt17_Rb_tree_iteratorISC_EbEDpOT_@Base
 1.

Processed: Re: Bug#973459: uim: FAIL: test-composer.scm

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/uim/uim/issues/167
Bug #973459 [src:uim] uim: FAIL: test-composer.scm
Set Bug forwarded-to-address to 'https://github.com/uim/uim/issues/167'.

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

Bug#973459: uim: FAIL: test-composer.scm

[dai]

Control: forwarded -1 https://github.com/uim/uim/issues/167

On Sat, Dec 12, 2020 at 02:50:52PM +0100, Sebastian Ramacher wrote:
> And it failed already twice for the Qt 5.15.2 transition, so I'm raising
> the severity. Please investigate and fix this issue.

Current upstream (not original authors who cannot get in touch) says
it is difficult to investigate it.

Nokubi-san, would we skip test-composer.scm for now?

On my just grepping, composer.scm is only required by test-composer.scm.
So it is no problem to skip test-composer.scm.
-- 
Regards,
dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E


signature.asc
Description: PGP signature

Bug#977243: ceph FTBFS with Boost 1.74

[Adrian Bunk]

Source: ceph
Version: 14.2.15-3
Severity: serious
Tags: ftbfs

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

...
In file included from /<>/src/rgw/rgw_http_client.cc:16:
/<>/src/common/async/completion.h: In instantiation of ‘void 
ceph::async::detail::CompletionImpl::destroy_defer(std::tuple&&) [with Executor1 = 
boost::asio::io_context::basic_executor_type, 0>; Handler 
= boost::asio::detail::coro_handler,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > > >, void>; T = void; Args = {boost::system::error_code}]’:
/<>/src/common/async/completion.h:188:8:   required from here
/<>/src/common/async/completion.h:194:29: error: 
‘boost::asio::executor_work_guard,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >, void>::executor_type’ {aka ‘class 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >’} has no member named ‘defer’; did you mean ‘prefer’?
  194 | w.second.get_executor().defer(std::move(f), alloc2);
  | ^
  | prefer
/<>/src/common/async/completion.h: In instantiation of ‘void 
ceph::async::detail::CompletionImpl::destroy_dispatch(std::tuple&&) [with Executor1 = 
boost::asio::io_context::basic_executor_type, 0>; Handler 
= boost::asio::detail::coro_handler,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > > >, void>; T = void; Args = {boost::system::error_code}]’:
/<>/src/common/async/completion.h:196:8:   required from here
/<>/src/common/async/completion.h:202:29: error: 
‘boost::asio::executor_work_guard,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >, void>::executor_type’ {aka ‘class 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >’} has no member named ‘dispatch’
  202 | w.second.get_executor().dispatch(std::move(f), alloc2);
  | ^~~~
/<>/src/common/async/completion.h: In instantiation of ‘void 
ceph::async::detail::CompletionImpl::destroy_post(std::tuple&&) [with Executor1 = 
boost::asio::io_context::basic_executor_type, 0>; Handler 
= boost::asio::detail::coro_handler,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > > >, void>; T = void; Args = {boost::system::error_code}]’:
/<>/src/common/async/completion.h:204:8:   required from here
/<>/src/common/async/completion.h:210:29: error: 
‘boost::asio::executor_work_guard,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >, void>::executor_type’ {aka ‘class 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >’} has no member named ‘post’
  210 | w.second.get_executor().post(std::move(f), alloc2);
  | ^~~~
make[3]: *** [src/rgw/CMakeFiles/rgw_common.dir/build.make:479: 
src/rgw/CMakeFiles/rgw_common.dir/rgw_http_client.cc.o] Error 1

Processed: severity of 888995 is serious

[Debian Bug Tracking System]

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

> severity 888995 serious
Bug #888995 [src:dbus-cpp] dbus-cpp: async_execution_load_test fails sometimes 
(randomly?)
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: fixed 974874 in 3.38.1-1

[Debian Bug Tracking System]

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

> fixed 974874 3.38.1-1
Bug #974874 {Done: Paul Gevers } [src:geary] src:geary: 
fails to migrate to testing for too long: autopkgtest regression
Marked as fixed in versions geary/3.38.1-1.
> thanks
Stopping processing here.

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

Processed: bug 977224 is forwarded to https://github.com/pokerth/pokerth/issues/395, tagging 977224

[Debian Bug Tracking System]

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

> forwarded 977224 https://github.com/pokerth/pokerth/issues/395
Bug #977224 [src:pokerth] pokerth FTBFS with Boost 1.74
Set Bug forwarded-to-address to 'https://github.com/pokerth/pokerth/issues/395'.
> tags 977224 + patch
Bug #977224 [src:pokerth] pokerth FTBFS with Boost 1.74
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#976915: service-wrapper-java: FTBFS on ppc64el: [exec] wrapper.c:(.text+0x3598): undefined reference to `pow'

[Markus Koschany]

On Wed, 9 Dec 2020 09:41:34 +0100 Lucas Nussbaum  wrote:
> Source: service-wrapper-java
> Version: 3.5.30-1
> Severity: serious
> Justification: FTBFS on ppc64el
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on ppc64el. At the same time, it did not fail on amd64.

In this case I believe the RC severity is correct because the arch:any or jni
version of the package FTBFS on ppc64el. We should try to fix the problem on
ppc64el or, if upstream doesn't support ppc64el, remove the architecture from
the list of supported architectures in debian/control.

Markus



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

Bug#977231: libusb-1.0-0: upgrading to 2:1.0.24-1 breaks iPhone/iPad detection and communication

[Yves-Alexis Perez]

On Sat, 2020-12-12 at 21:31 +0100, Aurelien Jarno wrote:
> 
> Indeed, I do not have such a device. As a first step, it would be nice
> if you can set the environment variable LIBUSB_DEBUG=99 and run lsusb.
> That should give us an idea why the device is ignored.

Here are two logs (with .22 an .24). Not much differences that I can see,
besides the max iso packet length.

Regards,
-- 
Yves-Alexis
[timestamp] [threadID] facility level [function call] 

[ 0.05] [3e62] libusb: debug [libusb_init] created default context
[ 0.65] [3e62] libusb: debug [libusb_init] libusb v1.0.22.11312
[ 0.000100] [3e62] libusb: debug [find_usbfs_path] found usbfs at 
/dev/bus/usb
[ 0.000122] [3e62] libusb: debug [get_kernel_version] reported kernel 
version is 5.9.0-4-amd64
[ 0.000130] [3e62] libusb: debug [op_init] bulk continuation flag supported
[ 0.000137] [3e62] libusb: debug [op_init] zero length packet flag supported
[ 0.000144] [3e62] libusb: debug [op_init] max iso packet length is 
(likely) 49152 bytes
[ 0.000162] [3e62] libusb: debug [op_init] sysfs can relate devices
[ 0.000170] [3e62] libusb: debug [op_init] sysfs has complete descriptors
[ 0.000484] [3e63] libusb: debug [linux_udev_event_thread_main] udev event 
thread entering.
[ 0.008973] [3e62] libusb: debug [linux_get_device_address] getting address 
for device: usb1 detached: 0
[ 0.008997] [3e62] libusb: debug [linux_get_device_address] scan usb1
[ 0.009080] [3e62] libusb: debug [linux_get_device_address] bus=1 dev=1
[ 0.009088] [3e62] libusb: debug [linux_enumerate_device] busnum 1 devaddr 
1 session_id 257
[ 0.009095] [3e62] libusb: debug [linux_enumerate_device] allocating new 
device for 1/1 (session 257)
[ 0.009284] [3e62] libusb: debug [linux_get_device_address] getting address 
for device: 1-1 detached: 0
[ 0.009295] [3e62] libusb: debug [linux_get_device_address] scan 1-1
[ 0.009364] [3e62] libusb: debug [linux_get_device_address] bus=1 dev=11
[ 0.009372] [3e62] libusb: debug [linux_enumerate_device] busnum 1 devaddr 
11 session_id 267
[ 0.009378] [3e62] libusb: debug [linux_enumerate_device] allocating new 
device for 1/11 (session 267)
[ 0.009449] [3e62] libusb: debug [linux_get_parent_info] Dev 0x62f5a7d478d0 
(1-1) has parent 0x62f5a7d47060 (usb1) port 1
[ 0.009572] [3e62] libusb: debug [linux_get_device_address] getting address 
for device: 1-3 detached: 0
[ 0.009581] [3e62] libusb: debug [linux_get_device_address] scan 1-3
[ 0.009643] [3e62] libusb: debug [linux_get_device_address] bus=1 dev=2
[ 0.009650] [3e62] libusb: debug [linux_enumerate_device] busnum 1 devaddr 
2 session_id 258
[ 0.009656] [3e62] libusb: debug [linux_enumerate_device] allocating new 
device for 1/2 (session 258)
[ 0.009712] [3e62] libusb: debug [linux_get_parent_info] Dev 0x62f5a7d474e0 
(1-3) has parent 0x62f5a7d47060 (usb1) port 3
[ 0.009843] [3e62] libusb: debug [linux_get_device_address] getting address 
for device: 1-3.4 detached: 0
[ 0.009851] [3e62] libusb: debug [linux_get_device_address] scan 1-3.4
[ 0.009916] [3e62] libusb: debug [linux_get_device_address] bus=1 dev=4
[ 0.009923] [3e62] libusb: debug [linux_enumerate_device] busnum 1 devaddr 
4 session_id 260
[ 0.009929] [3e62] libusb: debug [linux_enumerate_device] allocating new 
device for 1/4 (session 260)
[ 0.009984] [3e62] libusb: debug [linux_get_parent_info] Dev 0x62f5a7d47650 
(1-3.4) has parent 0x62f5a7d474e0 (1-3) port 4
[ 0.010115] [3e62] libusb: debug [linux_get_device_address] getting address 
for device: 1-3.4.2 detached: 0
[ 0.010123] [3e62] libusb: debug [linux_get_device_address] scan 1-3.4.2
[ 0.010187] [3e62] libusb: debug [linux_get_device_address] bus=1 dev=6
[ 0.010194] [3e62] libusb: debug [linux_enumerate_device] busnum 1 devaddr 
6 session_id 262
[ 0.010200] [3e62] libusb: debug [linux_enumerate_device] allocating new 
device for 1/6 (session 262)
[ 0.010257] [3e62] libusb: debug [linux_get_parent_info] Dev 0x62f5a7d46f20 
(1-3.4.2) has parent 0x62f5a7d47650 (1-3.4) port 2
[ 0.010395] [3e62] libusb: debug [linux_get_device_address] getting address 
for device: 1-3.4.2.3 detached: 0
[ 0.010402] [3e62] libusb: debug [linux_get_device_address] scan 1-3.4.2.3
[ 0.010468] [3e62] libusb: debug [linux_get_device_address] bus=1 dev=7
[ 0.010475] [3e62] libusb: debug [linux_enumerate_device] busnum 1 devaddr 
7 session_id 263
[ 0.010498] [3e62] libusb: debug [linux_enumerate_device] allocating new 
device for 1/7 (session 263)
[ 0.010558] [3e62] libusb: debug [linux_get_parent_info] Dev 0x62f5a7d28c10 
(1-3.4.2.3) has parent 0x62f5a7d46f20 (1-3.4.2) port 3
[ 0.010724] [3e62] libusb: debug [linux_get_device_address] getting address 
for device: 1-3.4.2.4 detached: 0
[ 0.010733] [3e62] libusb: debug [linux_get_device_address] s

Bug#973848: chromium: Unsupported version, many security bugs unfixed

[Michel Le Bihan]

Hello,

Thank you for your reply. libvpx got updated in Debian, but I can't use
it because it's missing a lib. I also had issues with harfbuzz, so I'm
using bundled versions of those libs as you are. I also used your ozone
patch because it is match cleaner than mine. With that I was able to
build Chromium, but with many lint errors and many missing patches.

BTW, have you tried opening a bug upstream or submitting your ozone
patch upstream?

Michel Le Bihan

On Wed, 9 Dec 2020 04:34:39 + Jeff Blake  wrote:
> On Tue, 08 Dec 2020 12:33:57 +0100 Michel Le Bihan  wrote:
> > Hello,
> > 
> > I started work on updating the chromium package (you can see my work
> > here:
> > https://salsa.debian.org/mimi8/chromium/-/commit/af70b14701aaf6bdb34e23af01657676e27ba5d4
> > ), but got stuck because `libvpx` is too old in Debian testing. It
> > needs to be updated before I can continue work.
> > 
> > Michel Le Bihan
> > 
> > 
> > 
> 
> I've managed to successfully update the ungoogled-chromium debian package 
> [1], which is based upon 
> the official debian package.
> 
> Until libvpx is updated (or a new release is made) you could use Chromium's 
> bundled version of libvpx [2].
> 
> Feel free to have a look around my repo, as you might well encounter some of 
> the same problems that 
> I had in getting things to build.
> 
> 
> Jeff Blake 
> 
> 
> [1] https://github.com/berkley4/ungoogled-chromium-debian/commits/87.0.4280.88
> 
> [2] 
> https://github.com/berkley4/ungoogled-chromium-debian/commit/05ffc529e685817aac8a9c5bb419daba17204a66
> 
> 
> 

Bug#973089: marked as done (qiskit-ibmq-provider: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 22:21:04 +
with message-id 
and subject line Bug#973089: fixed in qiskit-ibmq-provider 0.4.6-3
has caused the Debian Bug report #973089,
regarding qiskit-ibmq-provider: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.9 3.8" returned exit code 13
to be marked as done.

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

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


-- 
973089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qiskit-ibmq-provider
Version: 0.4.6-2
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 qiskit-ibmq-provider
> dpkg-buildpackage: info: source version 0.4.6-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Diego M. Rodriguez 
> 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> dpkg-source: info: using options from 
> qiskit-ibmq-provider-0.4.6/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build' 
> (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
> I: pybuild base:217: python3.8 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.8_qiskit-ibmq-provider/build' 
> (and everything under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.8' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using options from 
> qiskit-ibmq-provider-0.4.6/debian/source/options: 
> --extend-diff-ignore=^[^/]*[.]egg-info/
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building qiskit-ibmq-provider using existing 
> ./qiskit-ibmq-provider_0.4.6.orig.tar.gz
> dpkg-source: info: building qiskit-ibmq-provider in 
> qiskit-ibmq-provider_0.4.6-2.debian.tar.xz
> dpkg-source: info: building qiskit-ibmq-provider in 
> qiskit-ibmq-provider_0.4.6-2.dsc
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python3.9 setup.py config 
> running config
> I: pybuild base:217: python3.8 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit
> creating 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers
> creating 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/ibmqbackend.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/ibmqfactory.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/backendjoblimit.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/accountprovider.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/version.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/exceptions.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/apiconstants.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> copying qiskit/providers/ibmq/ibmqbackendservice.py -> 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq
> creating 
> /<>/.pybuild/cpython3_3.9_qiskit-ibmq-provider/build/qiskit/providers/ibmq/api
> copying q

Bug#977235: sentencepiece FTBFS on armel/mipsel: undefined reference to `__atomic_fetch_add_8'

[Adrian Bunk]

Source: sentencepiece
Version: 0.1.94-1
Severity: serious
Tags: ftbfs patch

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

...
/usr/bin/c++ -O3 -Wall -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -rdynamic 
CMakeFiles/spm_export_vocab.dir/spm_export_vocab_main.cc.o -o spm_export_vocab  
-Wl,-rpath,/<>/obj-arm-linux-gnueabi/src: 
libsentencepiece.so.0.0.0 -lpthread
/usr/bin/ld: libsentencepiece.so.0.0.0: undefined reference to 
`__atomic_fetch_add_8'
collect2: error: ld returned 1 exit status
make[4]: *** [src/CMakeFiles/spm_export_vocab.dir/build.make:107: 
src/spm_export_vocab] Error 1


Fix/Workaround:

--- debian/rules.old2020-12-12 21:58:13.187467694 +
+++ debian/rules2020-12-12 21:59:46.848833951 +
@@ -12,6 +12,9 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel mipsel m68k powerpc sh4))
+  export DEB_LDFLAGS_MAINT_APPEND += -Wl,--no-as-needed -latomic 
-Wl,--as-needed
+endif
 
 %:
dh $@ --with python3 --buildsystem=cmake

Bug#922214: bug #922214 regarding libpng12-0_1.2.50 - grave

[bug . reporter]

Dear Maintainer

I have two machines, one with this bug, and one without. 
#922214
I've tried a few things including dpkg-repack and a 
rebuild from source. The only thing that works is an 
install of the version 1.2.49-3 and manual linking 
to the newer code. 

The difference in the two machines may be that my 
/usr directory is on a separate partition. Hence this: 

lrwxrwxrwx   1 root root 7 Oct 14 15:40 lib -> usr/lib

drwxr-xr-x  12 root root  4096 Jan 29  2020 usr

Regards

Richard

Processed: Re: jnr-unixsocket: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #976948 [src:jnr-unixsocket] jnr-unixsocket: FTBFS on ppc64el 
(arch:all-only src pkg): dh_auto_test: error: 
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test 
returned exit code 1
Severity set to 'normal' from 'serious'

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

Bug#976948: jnr-unixsocket: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.hom

[Markus Koschany]

Control: severity -1 normal

I'm lowering the severity to normal as discussed on the debian-java mailing
list. The package builds fine on amd64 but it appears a test fails on ppc64el.

Markus


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

Bug#977227: marked as done (mir FTBFS: error: ‘find’ is not a member of ‘std’)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 20:49:06 +
with message-id 
and subject line Bug#977227: fixed in mir 1.8.0+dfsg1-12
has caused the Debian Bug report #977227,
regarding mir FTBFS: error: ‘find’ is not a member of ‘std’
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.)


-- 
977227: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mir
Version: 1.8.0+dfsg1-11
Severity: serious
Tags: ftbfs

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

...
/<>/src/miral/cursor_theme.cpp: In lambda function:
/<>/src/miral/cursor_theme.cpp:60:37: error: ‘find’ is not a 
member of ‘std’; did you mean ‘bind’?
   60 | auto const j = std::find(i, std::end(themes), ':');
  | ^~~~
  | bind
...
--- End Message ---
--- Begin Message ---
Source: mir
Source-Version: 1.8.0+dfsg1-12
Done: Mike Gabriel 

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

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

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mir package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 12 Dec 2020 20:14:00 +0100
Source: mir
Architecture: source
Version: 1.8.0+dfsg1-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Mir Team 
Changed-By: Mike Gabriel 
Closes: 977227
Changes:
 mir (1.8.0+dfsg1-12) unstable; urgency=medium
 .
   * debian/patches:
 + Add 0004_Add-missing-include.patch and 0005_Fix-compiler-errors.patch.
   Fixes FTBFS after Boost 1.74 transition. (Closes: #977227).
Checksums-Sha1:
 0c5064332926211c5ab8a065d2ce7522c876fe9b 5682 mir_1.8.0+dfsg1-12.dsc
 2efe3f0889187e046fd269f2ce3e0b97dcdfe8b5 67360 mir_1.8.0+dfsg1-12.debian.tar.xz
 5ee74770c393790fedc6b1f406d74ceb0419e8b5 16283 
mir_1.8.0+dfsg1-12_source.buildinfo
Checksums-Sha256:
 069a63cf72358dfb779d0456c964d18851b0acc8e5a1acbaa6432185297e63cd 5682 
mir_1.8.0+dfsg1-12.dsc
 f920b3a83707b528c35386b5bdc4f1e8b8b10434c2c12289e570cf490e1012cd 67360 
mir_1.8.0+dfsg1-12.debian.tar.xz
 9e10692240610f9bc54b545561133cbf4c4688b193e1e30bfc8c5320798ee272 16283 
mir_1.8.0+dfsg1-12_source.buildinfo
Files:
 06377dab9de0af28679c416441d3ca5b 5682 x11 optional mir_1.8.0+dfsg1-12.dsc
 047f5f661a6c6dfad0603ec79a868d08 67360 x11 optional 
mir_1.8.0+dfsg1-12.debian.tar.xz
 99d4ec0b3862a077f164f430cd3152d4 16283 x11 optional 
mir_1.8.0+dfsg1-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAl/VJ/wVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsx9fYP/2uEnbFHQxz/iXoycwOtMBm/klO+
gtFeIGx3RobG+nr+wONWWnBTpDXBm0pv5YusYcnuoIja4ld9NLZ64w8t1gUddtYQ
8G/va7bJ4/LV6sWDEKS2+252g7umTbDgU+aFsc+PO+Sz9B9hY/aR7n8KMswzZjiz
xiFuPpN+oeRM5SJ7HiEPRLGqXGZBBMespAD7+jYHvq3Tr1AJt0Q0+yBiYA8H1i3y
zsYrmce15rgrJJQC8QQ6hoNFW9RZXqoy5CNxDSp7amUX1UHtssl0TX7wk0qwO3Fy
UPLTxAKToQWF79f0YrSQ1sDPEu2olgfOZvrYOnM7Kmro8F6lKoa2uX/Z+AUVUtCN
Dl/4+7Qfg0TqSCVlyxptuH2e6E4M4a9HXseF64G8zilkqPyOOkdwCYP+LYma0Mdt
WqXmOwUjQSoS8eebuwVncH1yGrGaN97+rvGNETgsD1AdBqBDbJ2SJzJiWYHiAXZf
r0KDjcBWQVzmsa6HRHsqINcTj9BiqMqN1PnqUUwBvxSMS7xplhsGdPgpPxIrC6Ne
Wi7t3yT3N3Jl6JAM0mpvP6K00sruPIFQ0k4CEBdFGFhDciUnlxyRLo5V93/Wv6Px
ZUnienOucoga85XKM4DfUhjDG8lPbhLRkIvoTSyaQMoEn6He5jibv6ms3sdrGHnd
5+01ludrxwjwJIb9
=xwh7
-END PGP SIGNATURE End Message ---

Bug#976595: marked as done (minidlna: CVE-2020-28926)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 20:32:08 +
with message-id 
and subject line Bug#976595: fixed in minidlna 1.2.1+dfsg-2+deb10u1
has caused the Debian Bug report #976595,
regarding minidlna: CVE-2020-28926
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.)


-- 
976595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: minidlna
Version: 1.2.1+dfsg-2
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1.2.1+dfsg-1

Hi,

The following vulnerability was published for minidlna.

CVE-2020-28926[0]:
| ReadyMedia (aka MiniDLNA) before versions 1.3.0 allows remote code
| execution. Sending a malicious UPnP HTTP request to the miniDLNA
| service using HTTP chunked encoding can lead to a signedness bug
| resulting in a buffer overflow in calls to memcpy/memmove.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-28926
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28926
[1] 
https://sourceforge.net/p/minidlna/git/ci/9fba41008adebc1da0f4f6c6e27ae422ace3fe4a

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: minidlna
Source-Version: 1.2.1+dfsg-2+deb10u1
Done: Alexander GQ Gerasiov 

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

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

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

Debian distribution maintenance software
pp.
Alexander GQ Gerasiov  (supplier of updated minidlna package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 05 Dec 2020 20:21:18 +0300
Source: minidlna
Binary: minidlna minidlna-dbgsym
Architecture: source amd64
Version: 1.2.1+dfsg-2+deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Alexander GQ Gerasiov 
Changed-By: Alexander GQ Gerasiov 
Description:
 minidlna   - lightweight DLNA/UPnP-AV server targeted at embedded systems
Closes: 976594 976595
Changes:
 minidlna (1.2.1+dfsg-2+deb10u1) buster-security; urgency=high
 .
   * Add 0011-upnphttp-Disallow-negative-HTTP-chunk-lengths.patch
 CVE-2020-28926 (Closes: #976595).
   * Add 0012-upnphttp-Validate-SUBSCRIBE-callback-URL.patch
 CVE-2020-12695 (Closes: #976594).
Checksums-Sha1:
 74230032c27929524d4257a3aec6a43880d641ac 1738 minidlna_1.2.1+dfsg-2+deb10u1.dsc
 a25d04d2b93e0a1467113e55adcd57591b1da887 157380 minidlna_1.2.1+dfsg.orig.tar.xz
 89f829e76eaf436195b57425d76d3d189917352d 26032 
minidlna_1.2.1+dfsg-2+deb10u1.debian.tar.xz
 7f08ea865085ab8030e4405b4a776d08004378fc 287104 
minidlna-dbgsym_1.2.1+dfsg-2+deb10u1_amd64.deb
 f3ef20be109415372eda143d4d1b474a2c62fe31 8912 
minidlna_1.2.1+dfsg-2+deb10u1_amd64.buildinfo
 46c287c5f5c77d6745b551f181160eed0e0c17c3 151356 
minidlna_1.2.1+dfsg-2+deb10u1_amd64.deb
Checksums-Sha256:
 724a0e23f30958fd7a73405e586cf3b65cdb482683a2f42bae787311dc34ba58 1738 
minidlna_1.2.1+dfsg-2+deb10u1.dsc
 72f688c4dd0412fb7a9389bf4ade3bad773924eae9cb31f510440414af3785a0 157380 
minidlna_1.2.1+dfsg.orig.tar.xz
 c6c885584758c4989c87dccaac7337f83f26c70b1fb7ac5ba82cf04ce8d0d3b2 26032 
minidlna_1.2.1+dfsg-2+deb10u1.debian.tar.xz
 bab3ccb80c52cc8d6335ba9f4487b18c9f13ea8b78fff971e31f70af1c8bb6b2 287104 
minidlna-dbgsym_1.2.1+dfsg-2+deb10u1_amd64.deb
 09a7101d610ba3d04a08f7494f41dc3abf09e14e3a6e8cf2f6f9f53df6c04235 8912 
minidlna_1.2.1+dfsg-2+deb10u1_amd64.buildinfo
 82b25675abac7c845b461b722fb6718f8644e52367bce2a12573fe16cb4821bf 151356 
minidlna_1.2.1+dfsg-2+deb10u1_amd64.deb
Files:
 ed60ae77ef2d38ee782f4ba2efb32338 1738 net optional 
minidlna_1.2.1+dfsg-2+deb10u1.dsc
 e80278115a6a4cf75fd5524f8f0ee5dc 157380 net optional 
minidlna_1.2.1+dfsg.orig.tar.xz
 895248eaf9990d418c9ec368d609ce6a 26032 net optional 
minidlna_1.2.1+dfsg-2+deb10u1.debian.tar.xz
 5869a93a4fce992daee48588b14230d2 287104 debug optional 
minidlna-dbgsym_1.2.1+dfsg-2+deb10u1_amd64.deb
 94aa10bd12d6f59afc7e3c2cd0ccb0cb 8912 net optional 
minidlna_1.2.1+dfsg-2+deb10u1_amd64

Processed: Re: Bug#977231: libusb-1.0-0: upgrading to 2:1.0.24-1 breaks iPhone/iPad detection and communication

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #977231 [libusb-1.0-0] libusb-1.0-0: upgrading to 2:1.0.24-1 breaks 
iPhone/iPad detection and communication
Severity set to 'serious' from 'important'

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

Bug#977230: bagel FTBFS with Boost 1.74

[Adrian Bunk]

Source: bagel
Version: 1.2.2-1
Severity: serious
Tags: ftbfs bullseye sid

https://buildd.debian.org/status/fetch.php?pkg=bagel&arch=amd64&ver=1.2.2-1%2Bb2&stamp=1607773477&raw=0

...
/usr/include/boost/property_tree/ptree_serialization.hpp: In function ‘void 
boost::property_tree::detail::load_children(Archive&, 
boost::property_tree::basic_ptree&)’:
/usr/include/boost/property_tree/ptree_serialization.hpp:66:24: error: 
‘library_version_type’ in namespace ‘bsa’ does not name a type
   66 | const bsa::library_version_type library_version(
  |^~~~
...

Bug#977229: kcollectd FTBFS with Boost 1.74

[Adrian Bunk]

Source: kcollectd
Version: 0.11.99.0-1
Severity: serious
Tags: ftbfs

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

...
/<>/kcollectd/gui.cc: In function ‘void 
recurseTree(QTreeWidgetItem*, const boost::filesystem::directory_iterator&)’:
/<>/kcollectd/gui.cc:179:10: error: ‘stack’ is not a member of 
‘std’
  179 | std::stack stack;
  |  ^
...

Bug#977228: libzypp FTBFS: MediaSetAccess_test (SEGFAULT)

[Adrian Bunk]

Source: libzypp
Version: 17.7.0-1.2
Severity: serious
Tags: ftbfs

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

...
24: Test command: 
/<>/obj-x86_64-linux-gnu/tests/zypp/MediaSetAccess_test 
"--catch_system_errors=no"
24: Test timeout computed to be: 1000
24: Running 8 test cases...
24:
24: *** No errors detected
24: 
24/79 Test #24: MediaSetAccess_test ..***Exception: SegFault  1.22 
sec
...
99% tests passed, 1 tests failed out of 79

Total Test time (real) =  46.64 sec

The following tests FAILED:
 24 - MediaSetAccess_test (SEGFAULT)
Errors while running CTest
make[4]: *** [tests/CMakeFiles/ctest.dir/build.make:79: tests/CMakeFiles/ctest] 
Error 8

Bug#977227: mir FTBFS: error: ‘find’ is not a member of ‘std’

[Adrian Bunk]

Source: mir
Version: 1.8.0+dfsg1-11
Severity: serious
Tags: ftbfs

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

...
/<>/src/miral/cursor_theme.cpp: In lambda function:
/<>/src/miral/cursor_theme.cpp:60:37: error: ‘find’ is not a 
member of ‘std’; did you mean ‘bind’?
   60 | auto const j = std::find(i, std::end(themes), ':');
  | ^~~~
  | bind
...

Bug#977226: openmw FTBFS: error: ‘for_each’ is not a member of ‘std’

[Adrian Bunk]

Source: openmw
Version: 0.46.0-1
Severity: serious
Tags: ftbfs

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

...
In file included from 
/<>/components/detournavigator/makenavmesh.hpp:4,
 from 
/<>/components/detournavigator/makenavmesh.cpp:1:
/<>/components/detournavigator/offmeshconnectionsmanager.hpp: In 
member function ‘std::vector 
DetourNavigator::OffMeshConnectionsManager::get(const TilePosition&)’:
/<>/components/detournavigator/offmeshconnectionsmanager.hpp:84:18:
 error: ‘for_each’ is not a member of ‘std’
   84 | std::for_each(itByTilePosition->second.begin(), 
itByTilePosition->second.end(),
  |  ^~~~
...

Bug#977225: openscad FTBFS with Boost 1.74

[Adrian Bunk]

Source: openscad
Version: 2019.05-3
Severity: serious
Tags: ftbfs

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

...
src/import.cc:53:10: fatal error: boost/detail/endian.hpp: No such file or 
directory
   53 | #include 
  |  ^
compilation terminated.
make[2]: *** [Makefile:3559: objects/src/import.o] Error 1

Bug#977224: pokerth FTBFS with Boost 1.74

[Adrian Bunk]

Source: pokerth
Version: 1.1.2-1
Severity: serious
Tags: ftbfs

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

...
/usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of 
declaring the Bind placeholders (_1, _2, ...) in the global namespace is 
deprecated. Please use  + using namespace 
boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the 
current behavior.’
   36 | BOOST_PRAGMA_MESSAGE(
  | ^~~~
src/net/common/serveracceptwebhelper.cpp: In member function ‘virtual void 
ServerAcceptWebHelper::Listen(unsigned int, bool, const string&, 
boost::shared_ptr)’:
src/net/common/serveracceptwebhelper.cpp:61:109: error: ‘_1’ was not declared 
in this scope
   61 |  
m_webSocketServer->set_validate_handler(boost::bind(boost::mem_fn(&ServerAcceptWebHelper::validate),
 this, _1));
  | 
^~
...

Bug#977222: dolfin: FTBFS: error: ‘min_element’ is not a member of ‘std’; did you mean ‘tuple_element’?

[Sebastian Ramacher]

Source: dolfin
Version: 2019.2.0~git20200629.946dbd3+lfs-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

dolfin failed to build with:
| cd "/<>/obj-x86_64-linux-gnu/dolfin" && /usr/bin/c++ 
-DDOLFIN_VERSION=\"2019.2.0.dev0\" -DHAS_CHOLMOD -DHAS_HDF5 -DHAS_MPI 
-DHAS_PETSC -DHAS_SCOTCH -DHAS_SLEPC -DHAS_UMFPACK -DHAS_ZLIB -DNDEBUG 
-Ddolfin_EXPORTS -I"/<>" -I"/<>/obj-x86_64-linux-gnu" 
-isystem /usr/lib/python3/dist-packages/ffc/backends/ufc -isystem 
/usr/include/eigen3 -isystem /usr/include/hdf5/openmpi -isystem 
/usr/include/suitesparse -isystem /usr/include/scotch -isystem 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem 
/usr/lib/x86_64-linux-gnu/openmpi/include -isystem 
/usr/lib/petscdir/petsc3.14/x86_64-linux-gnu-real/include -isystem 
/usr/lib/slepcdir/slepc3.14/x86_64-linux-gnu-real/include -fpermissive -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -g -DNDEBUG -fPIC -std=c++11 -o 
CMakeFiles/dolfin.dir/geometry/MeshPointIntersection.cpp.o -c 
"/<>/dolfin/geometry/MeshPointIntersection.cpp"
| /<>/dolfin/geometry/IntersectionConstruction.cpp: In static 
member function ‘static std::vector 
dolfin::IntersectionConstruction::intersection_segment_segment_2d(const 
dolfin::Point&, const dolfin::Point&, const dolfin::Point&, const 
dolfin::Point&)’:
| /<>/dolfin/geometry/IntersectionConstruction.cpp:442:24: error: 
‘min_element’ is not a member of ‘std’; did you mean ‘tuple_element’?
|   442 |   const auto it = std::min_element(oo.begin(), oo.end());
|   |^~~
|   |tuple_element
| make[4]: *** [dolfin/CMakeFiles/dolfin.dir/build.make:1203: 
dolfin/CMakeFiles/dolfin.dir/geometry/IntersectionConstruction.cpp.o] Error 1

https://buildd.debian.org/status/fetch.php?pkg=dolfin&arch=amd64&ver=2019.2.0%7Egit20200629.946dbd3%2Blfs-3%2Bb2&stamp=1607782416&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: tagging 938754

[Debian Bug Tracking System]

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

> tags 938754 + ftbfs
Bug #938754 [src:undertaker] undertaker: Python2 removal in sid/bullseye
Bug #966796 [src:undertaker] undertaker: Unversioned Python removal in 
sid/bullseye
Added tag(s) ftbfs.
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: affects 947569

[Debian Bug Tracking System]

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

> affects 947569 src:uwsgi-plugin-mongo
Bug #947569 [src:mongo-cxx-driver-legacy] FTBFS with scons 3.1.2-1
Added indication that 947569 affects src:uwsgi-plugin-mongo
> thanks
Stopping processing here.

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

Bug#977221: geophar FTBFS: Please add appropriate interpreter package to Build-Depends

[Adrian Bunk]

Source: geophar
Version: 18.08.6+dfsg1-6
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=geophar&arch=all&ver=18.08.6%2Bdfsg1-6&stamp=1607764687&raw=0

...
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
E: Please add appropriate interpreter package to Build-Depends, see pybuild(1) 
for details.this: $VAR1 = bless( {
 'builddir' => undef,
 'py3def' => '3.9',
 'parallel' => '4',
 'pypydef' => '',
 'sourcedir' => '.',
 'py3vers' => '',
 'pyvers' => '',
 'pydef' => '',
 'cwd' => '/<>'
   }, 'Debian::Debhelper::Buildsystem::pybuild' );
deps: $VAR1 = [
  'python3-all',
  'python3-sympy',
  'python3-numpy',
  'python3-matplotlib',
  'python3-dbus',
  'python3-sip',
  'python3-scipy',
  'python3-pyqt5.qsci',
  'python3-pyqt5.qtsvg'
];
make[1]: *** [debian/rules:15: override_dh_auto_clean] Error 25

Bug#976926: golang-github-coreos-bbolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short go.etcd.io/bbolt returned exit

[Andreas Henriksson]

Hello!

On Wed, Dec 09, 2020 at 10:03:39AM +0100, Lucas Nussbaum wrote:
> Source: golang-github-coreos-bbolt
> Version: 1.3.5-1
> Severity: serious
> Justification: FTBFS on ppc64el
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on ppc64el. At the same time, it did not fail on amd64.
[...]
> > === RUN   TestBucket_Stats
> > bucket_test.go:1222: unexpected BranchPageN: 0
> > --- FAIL: TestBucket_Stats (9.56s)
[...]

Apparently bbolt is a fork of boltdb, so please see my comments
on the equivalent bug report againt boltdb:
https://bugs.debian.org/976907


Relevant part:
 It seems the test-suite makes assumptions related to calculations that
 involve os.Getpagesize() (which gives 4096 on amd64 and 65536 on
 ppc64el, which is 16 times larger).
 Changing the 500 number to 8000 (16 times larger) in
 TestBucket_Stats(...) (in bucket_test.go:1143) gives the expected
 BranchPageN == 1  (however after that it then says 
 "unexpected LeafPageN: 6" with this modification).

 In my opinion it's pretty clear that these are test-suite only
 issues and not issues in the actual product.


I would thus personally just disable the test-suite on !amd64 if no
porter is interested in fixing the testsuite (unless we agree this
issue simply can be downgraded to non-RC).

Regards,
Andreas Henriksson

Bug#976907: golang-github-boltdb-bolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short github.com/boltdb/bolt github.co

[Andreas Henriksson]

Hello again,

So after wasting my time here I finally realized that apparently
boltdb is archived upstream. It will not receive any fixes.

Apparently golang-github-coreos-bbolt is a maintained feature-extended
fork. We should likely encurage moving to that and get boltdb removed
from debian.

The timeout waiting for db.mmaplock that occurred in boltdb is
apparently already fixed in bbolt, see:
https://github.com/etcd-io/bbolt/commit/e06ec0a754bc30c2e17ad871962e71635bf94d45

The pagesize issue seems to plague them both still though.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976926
for the bug report against bbolt.

Regards,
Andreas Henriksson

Bug#976907: golang-github-boltdb-bolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short github.com/boltdb/bolt github.co

[Andreas Henriksson]

Hello again,

On Sat, Dec 12, 2020 at 05:59:37PM +0100, Andreas Henriksson wrote:
> Hello all,
> 
> 1 down, 1 to go info below.
> 
> On Wed, Dec 09, 2020 at 10:03:31AM +0100, Lucas Nussbaum wrote:
> [...]
> > > === RUN   TestBucket_Stats
> > > bucket_test.go:1172: unexpected BranchPageN: 0
> > > --- FAIL: TestBucket_Stats (6.41s)
[...]

Now also quickly looked into this one. It seems the test-suite
makes assumptions related to calculations that involve
os.Getpagesize() (which gives 4096 on amd64 and 65536 on ppc64el,
which is 16 times larger).
Changing the 500 number to 8000 (16 times larger) in
TestBucket_Stats(...) (in bucket_test.go:1143) gives the expected
BranchPageN == 1 (however after that it then says 
"unexpected LeafPageN: 6" with this modification).

Anyway, this makes me loose interest in pursuing this further.
In my opinion it's pretty clear that these are test-suite only
issues and not issues in the actual product.

Unless someone else wants to pursue fixing up the test-suite for ppc64le
needs, my offer to "fix" this will be to simply disable it on !amd64
architectures (unless we agree on simply downgrading this issue to non-RC).

Regards,
Andreas Henriksson

Bug#977219: anytun: FTBFS with boost 1.74

[Sebastian Ramacher]

Source: anytun
Version: 0.3.7-1.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

anytun FTBFS with boost 1.74:

| g++ -g -Wall -Werror -Wno-error=unused-variable -O2 -DLOG_SYSLOG -DLOG_FILE 
-DLOG_STDOUT -DUSE_GCRYPT syncServer.cpp -c -o syncServer.o
| In file included from /usr/include/boost/bind.hpp:30,
|  from syncServer.h:49,
|  from syncServer.cpp:46:
| /usr/include/boost/bind.hpp:36:1: note: ‘#pragma message: The practice of 
declaring the Bind placeholders (_1, _2, ...) in the global namespace is 
deprecated. Please use  + using namespace 
boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the 
current behavior.’
|36 | BOOST_PRAGMA_MESSAGE(
|   | ^~~~
| In file included from /usr/include/boost/asio/executor.hpp:342,
|  from /usr/include/boost/asio.hpp:86,
|  from syncServer.h:56,
|  from syncServer.cpp:46:
| /usr/include/boost/asio/impl/executor.hpp: In instantiation of ‘void 
boost::asio::executor::impl< ,  
>::on_work_started() [with Executor = 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >; Allocator = std::allocator]’:
| /usr/include/boost/asio/impl/executor.hpp:77:8:   required from here
| /usr/include/boost/asio/impl/executor.hpp:79:15: error: ‘class 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >’ has no member named ‘on_work_started’
|79 | executor_.on_work_started();
|   | ~~^~~
| /usr/include/boost/asio/impl/executor.hpp: In instantiation of ‘void 
boost::asio::executor::impl< ,  
>::on_work_finished() [with Executor = 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >; Allocator = std::allocator]’:
| /usr/include/boost/asio/impl/executor.hpp:82:8:   required from here
| /usr/include/boost/asio/impl/executor.hpp:84:15: error: ‘class 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >’ has no member named ‘on_work_finished’
|84 | executor_.on_work_finished();
|   | ~~^~~~
| /usr/include/boost/asio/impl/executor.hpp: In instantiation of ‘void 
boost::asio::executor::impl< ,  
>::dispatch(boost::asio::executor::function&&) [with Executor = 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >; Allocator = std::allocator; boost::asio::executor::function = 
boost::asio::detail::executor_function]’:
| /usr/include/boost/asio/impl/executor.hpp:92:8:   required from here
| /usr/include/boost/asio/impl/executor.hpp:94:15: error: ‘class 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >’ has no member named ‘dispatch’
|94 | executor_.dispatch(BOOST_ASIO_MOVE_CAST(function)(f), allocator_);
|   | ~~^~~~
| /usr/include/boost/asio/impl/executor.hpp: In instantiation of ‘void 
boost::asio::executor::impl< ,  
>::post(boost::asio::executor::function&&) [with Executor = 
boost::asio::execution::any_executor,
 boost::asio::execution::detail::blocking::never_t<0>, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 >, 
boost::asio::execution::prefer_only
 > >; Allocator = std::allocator; boost::asio::executor::function = 
boost::asio::detail::executor_function]’:
| /usr/include/boost/asio/impl/executor.hpp:97:8:   required from here
| /usr/include/boost/asio/impl/executor.hpp:99:15: error: ‘class 
boost::asio::execu

Bug#976907: golang-github-boltdb-bolt: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_test: error: cd obj-powerpc64le-linux-gnu && go test -vet=off -v -p 160 -short github.com/boltdb/bolt github.co

[Andreas Henriksson]

Hello all,

1 down, 1 to go info below.

On Wed, Dec 09, 2020 at 10:03:31AM +0100, Lucas Nussbaum wrote:
> Source: golang-github-boltdb-bolt
> Version: 1.3.1-7
> Severity: serious
> Justification: FTBFS on ppc64el
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on ppc64el. At the same time, it did not fail on amd64.
[...]
> > === RUN   TestBucket_Stats
> > bucket_test.go:1172: unexpected BranchPageN: 0
> > --- FAIL: TestBucket_Stats (6.41s)

^--- I've not looked into this one yet.

[...]
> > === RUN   TestTx_Commit_ErrTxNotWritable
> > panic: test timed out after 10m0s
[...]

^-- this one is solved by adding `tx.Rollback()` last in
TestTx_Commit_ErrTxNotWritable function (in tx_test.go:65).
In other words, this is a test-suite bug (not a bug in the actual
product code).

The reasoning goes that tx.Commit() is expected to
return error bolt.ErrTxNotWritable, which it does -- but this
means it's holding a reader lock on db.mmaplock.
After the test function finishes the deferred function
db.MustClose() runs and calls into things that tries
to take a read-write lock of db.mmaplock which times out.
The added tx.Rollback() on a read-only tx basically only
removes the transaction and releases the db.mmaplock.

I have no idea why this would not also trigger on any other arch.

Regards,
Andreas Henriksson

Bug#976922: marked as done (systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 15:51:27 +
with message-id 
and subject line Bug#976922: fixed in systemd-bootchart 233-3
has caused the Debian Bug report #976922,
regarding systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 
check VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
976922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976922
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: systemd-bootchart
Version: 233-2
Severity: serious
Justification: FTBFS on ppc64el
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201209 ftbfs-bullseye ftbfs-ppc64el

Hi,

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

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> Making check in .
> make --no-print-directory check-TESTS
> FAIL: tests/run
> =
>systemd-bootchart 233: ./test-suite.log
> =
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: tests/run
> ===
> 
> 1..3
> Segmentation fault
> not ok 1 - ./systemd-bootchart -o /tmp/tmp.cNy0lVrga8 -n 2 -r
> Segmentation fault
> not ok 2 - ./systemd-bootchart -o /tmp/tmp.cNy0lVrga8 -n 10 -r
> Segmentation fault
> not ok 3 - ./systemd-bootchart -o /tmp/tmp.cNy0lVrga8 -n 10 -r -p
> # Failed 3 out of 3 tests
> FAIL tests/run (exit status: 1)
> 
> 
> Testsuite summary for systemd-bootchart 233
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See ./test-suite.log
> Please report to http://github.com/systemd/systemd-bootchart/issues
> 
> make[4]: *** [Makefile:1515: test-suite.log] Error 1
> make[3]: *** [Makefile:1623: check-TESTS] Error 2
> make[2]: *** [Makefile:1859: check-am] Error 2
> make[1]: *** [Makefile:1400: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/12/09/systemd-bootchart_233-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!

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

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

About the archive rebuild: The rebuild was done on a Power8 cluster part of the
Grid'5000 testbed. Hardware specs: 
https://www.grid5000.fr/w/Grenoble:Hardware#drac
--- End Message ---
--- Begin Message ---
Source: systemd-bootchart
Source-Version: 233-3
Done: Michael Biebl 

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated systemd-bootchart package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 12 Dec 2020 16:00:36 +0100
Source: systemd-bootchart
Architecture: source
Version: 233-3
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers 

Changed-By: Michael Biebl 
Closes: 976922
Changes:
 systemd-bootchart (233-3) unstable; urgency=medium
 .
   * Switch to debhelper-compat and bump compat level to 13
   * Switch to dh_installsystemd
   * Bump Standards-Ve

Bug#956779: marked as done (redshift: Depends on deprecated libappindicator)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 15:51:00 +
with message-id 
and subject line Bug#956779: fixed in redshift 1.12-3
has caused the Debian Bug report #956779,
regarding redshift: Depends on deprecated libappindicator
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.)


-- 
956779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: redshift
Version: 1.12-2
Tags: sid bullseye
Severity: important
Control: block 895037 by -1
User: pkg-ayatana-de...@lists.alioth.debian.org
Usertags: ayatana-appindicator

This package Depends on gir1.2-appindicator3-0.1, which is deprecated and
unmaintained. The supported replacement appears to be
gir1.2-ayatanaappindicator3-0.1.

Please see #895037 and
https://wiki.debian.org/Ayatana/IndicatorsTransition for more details
of this deprecation.

This bug might get escalated to 'serious' severity (making it
release-critical) if the maintainers of the Ayatana stack are serious about
getting libappindicator removed from Debian before bullseye.

smcv
--- End Message ---
--- Begin Message ---
Source: redshift
Source-Version: 1.12-3
Done: nicoo 

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

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

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

Debian distribution maintenance software
pp.
nicoo  (supplier of updated redshift package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Dec 2020 16:29:52 +0100
Source: redshift
Architecture: source
Version: 1.12-3
Distribution: unstable
Urgency: medium
Maintainer: nicoo 
Changed-By: nicoo 
Closes: 754430 940737 947848 956779
Changes:
 redshift (1.12-3) unstable; urgency=medium
 .
   * Take over maintainership, by request of previous maintainer (rrs@)
   * Remove uploader (Franziska Lichtblau) at their request
 .
   * d/patches:
 + Add wayland support. (Closes: #947848)
 + Replace libappindicator with ayatana-appindicator. (Closes: #956779)
   The former is going to be removed for the bullseye release.
 + src/redshift.c: Fix typo in error message.
 + data/appdata:
   - Update Appstream metadata format
   - Link to a local copy of the screenshot, rather than http://jonls.dk
 .
   * gtk-redshift: Drop transitional package (Closes: #940737)
   * redshift
 + Install missing manpage.
 + Install AppArmor profile.
   * redshift-gtk:
 + Remove menu file (policy violation)
   Per the tech-ctte decision on #741573, it is prohibited to ship
   both a desktop and menu file.
 + Add manpage (symlink) for the gtk-redshift binary.
 + Clarify description (Closes: #754430)
 .
   * Switch to debhelper compatibility level 13
   * Comply with policy 4.5.1 (was 3.9.3)
 + d/control: Set Rules-Requires-Root to 'no'
 + d/copyright: Use the DEP-5 machine-readable format
 + d/rules: Set DH_VERBOSE by default
 .
   * Setup CI for the packaging repository, and BTS integration.
   * d/control: Use a canonical Vcs-Browser URL
   * d/copyright: Add missing copyrights and licenses
 + Remove explicit invocation of dh-autoreconf and corresponding 
dependencies
   * d/watch
 + Update to uscan v4
 + Point to current upstream (moved from Launchpad to Github after v1.10)
 .
   * gbp pq: Disable patch numbering
   * gbp dch: Do not include commit ids
   * wrap-and-sort -st d/control and d/*.install.
 This made the dependency lists easier to deal with.
Checksums-Sha1:
 a03c178da295748f728c7578895845e5ab90edec 2051 redshift_1.12-3.dsc
 2285851f2759a9ddc3a05b4ee420563f91971961 355000 redshift_1.12-3.debian.tar.xz
 bbe1c80913e3e3234383cf231b997d3abf51c25d 9486 redshift_1.12-3_amd64.buildinfo
Checksums-Sha256:
 c5b7d3bada116e3af605bcd96f9431222c6b69e835d3b7dd886f31678fdce274 2051 
redshift_1.12-3.dsc
 bc988539aad54854c8f9ebccbf113db80d7f0462448a11426916822e8cd10429 355000 
redshift_1.12-3.debian.tar.xz
 020bfc1072810b7e9d3d2c3d684e95f2dba75f62cea6e5c0a5521839ae2aaae6 9486 
redshift_1.12-3_amd64.buildinfo
Files:
 e8f7eed595c6711ad5a4e6f648d29f6c 2051 x11 optional redshift_1.12-3.dsc
 e0b98ce7396

Bug#970933: marked as done (geary: autopkgtest regression: Expected: geary: 3.38.0.1 Got: geary: 3.38.0)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 15:49:36 +
with message-id 
and subject line Bug#970933: fixed in geary 3.38.1-1
has caused the Debian Bug report #970933,
regarding geary: autopkgtest regression: Expected: geary: 3.38.0.1 Got: geary: 
3.38.0
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.)


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

Dear maintainer(s),

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

   passfail
geary  from testing3.38.0.1-3
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? By the way, geary also
FTBFS on s390x.

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

https://ci.debian.net/data/autopkgtest/testing/amd64/g/geary/7180319/log.gz

autopkgtest [06:10:02]: test version: [---
Expected: geary: 3.38.0.1
 Got: geary: 3.38.0
autopkgtest [06:10:03]: test version: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: geary
Source-Version: 3.38.1-1
Done: Laurent Bigonville 

We believe that the bug you reported is fixed in the latest version of
geary, 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.
Laurent Bigonville  (supplier of updated geary package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 12 Dec 2020 16:35:37 +0100
Source: geary
Architecture: source
Version: 3.38.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Closes: 970933 972520
Changes:
 geary (3.38.1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #972520, #970933)
   * debian/control.in: The Provides stanza must be in the binary package part,
 not the source one
Checksums-Sha1:
 29da929ad666ee51639a0ca059057f2e2bc77ead 2602 geary_3.38.1-1.dsc
 a3f9448704f95b2dd4e965ce9643493bfd4ffe4d 2511732 geary_3.38.1.orig.tar.xz
 9cf01393c3b45686111ad703cdd676ccafedce20 13748 geary_3.38.1-1.debian.tar.xz
 a62d9d34b68b9689a7caac54eaebe7b83b0054e2 16282 geary_3.38.1-1_source.buildinfo
Checksums-Sha256:
 1eefa04fed9f47589580200b2eb19f666b551182131b7671db105e5b599892a3 2602 
geary_3.38.1-1.dsc
 e72e212798536657d5100e1e1a4a67f3836d6f0235340aae53e576f2a774e812 2511732 
geary_3.38.1.orig.tar.xz
 43bf344b6de4f55251cf2d295150215acd16fba7c1f36b9b0a8da2ab477dc5f6 13748 
geary_3.38.1-1.debian.tar.xz
 90bcf0d80247cfc810830fa0d9b65af981d1b5b2b705b74018348e8eb83a0f69 16282 
geary_3.38.1-1_source.buildinfo
Files:
 92cd19c23895cda134dc7e33195b5d16 2602 mail optional geary_3.38.1-1.dsc
 d095f766b72ca7c08d85064fcef5cc23 2511732 mail optional geary_3.38.1.orig.tar.xz
 e4d7cec4ee2f2e2671ced1467b626068 13748 mail optional 
geary_3.38.1-1.debian.tar.xz
 2f8a8101b598e6b8d7d1979d0db71831 16282 mail optional 
geary_3.38.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAl/U424RHGJpZ29uQGRl
Ymlhbi5vcmcACgkQH8WJHrqwQ9W1Gwf+J/ZFQJK8c+nLQ3GW57iWFGjPdFZ4vNsl
vvyuJ1VFhRoYqWRwUr0FxXIX6hDuDN4MG39iqRgiJCuqKUSkS8JRPjlTdfHUo+Na
YuJ7btxb+aLwaVKvq2HlrggmaKPeHZkp98wM8zktYgwA26LtzhSYIsEc9NGbvFso
vHfGTro2UcFhCI6GgVKyyvsWuYOvl3qMtjnRkaFn39wLV7cYFMtYOJblOjZx5CPX
CtHjmfp1at0BMva6A+RP0+sMN9wMetQlQVZd+GwazMjmrWcG1kyEAJlumLtH5k+t
NerSsNAQDbznBnIp40g/Vm/NJpjtBcuLKpZh9p5/xaHVGV6R3QTMrQ==
=O3k4
-END PGP SIGNATURE

Processed: Forwarded and severity

[Debian Bug Tracking System]

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

> forwarded 977139 https://github.com/BestImageViewer/geeqie/issues/832
Bug #977139 [geeqie] geeqie: fails immediatly after start
Set Bug forwarded-to-address to 
'https://github.com/BestImageViewer/geeqie/issues/832'.
> severity 977139 normal
Bug #977139 [geeqie] geeqie: fails immediatly after start
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#970933: marked as pending in geary

[Laurent Bigonville]

Control: tag -1 pending

Hello,

Bug #970933 in geary 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/geary/-/commit/3e29004d68de382f22e4a5f1c8a90326ed063a9f


New upstream release (Closes: #972520, #970933)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/970933

Processed: Bug#970933 marked as pending in geary

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #970933 [src:geary] geary: autopkgtest regression: Expected: geary: 
3.38.0.1 Got: geary: 3.38.0
Added tag(s) pending.

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

Bug#977139: geeqie: fails immediatly after start

[Andreas Ronnquist]

On Fri, 11 Dec 2020 19:34:09 +0300
Ilya Ovchinnikov  wrote:

>On 11.12.2020 19:17, Andreas Ronnquist wrote:
>> On Fri, 11 Dec 2020 17:50:07 +0300
>> Ilya Ovchinnikov  wrote:
>>   
>>> Package: geeqie
>>> Version: 1:1.6-2
>>> Severity: grave
>>> Justification: renders package unusable

 8< 

>
>> I am guessing you are running X? (You can quickly find out by the
>> command
>> 
>> echo $XDG_SESSION_TYPE
>> in the terminal.)  
>
>x11
>

>[Detaching after vfork from child process 990936]
>[Thread 0x7fffceffd700 (LWP 990929) exited]
>^C
>Thread 1 "geeqie" received signal SIGINT, Interrupt.
>0x7617a39f in poll () from /lib/x86_64-linux-gnu/libc.so.6
>(gdb) bt
>#0  0x7617a39f in poll () at /lib/x86_64-linux-gnu/libc.so.6
>#1  0x77230e1e in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
>#2  0x7723117b in g_main_loop_run () at
>/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3  0x77a407a5 in
>gtk_main () at /lib/x86_64-linux-gnu/libgtk-3.so.0 #4
>0x555c9916 in  () #5  0x760add0a in __libc_start_main
>() at /lib/x86_64-linux-gnu/libc.so.6 #6  0x555ca54a in  ()
>(gdb)

Are you really sure that it is crashing? I have discovered that I can
reproduce your problem - I see the geeqie window flashing and
disappearing, and then press Ctrl+C in gdb to get the same backtrace.
What is happening is that geeqie is simply moved to another workspace
(probably the last workspace it was present on), and doesn't crash at
all. (I thought that it crashed, just like you). When you see this
behaviour, please check so geeqie isn't running on any workspace (which
I suspect it still does).

It sure fooled me! :)

/Andreas
gus...@debian.org

Bug#977195: marked as done (libboost-all-dev is missing a dependency on libboost-nowide-dev)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 15:33:39 +
with message-id 
and subject line Bug#977195: fixed in boost-defaults 1.74.0.3
has caused the Debian Bug report #977195,
regarding libboost-all-dev is missing a dependency on libboost-nowide-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.)


-- 
977195: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977195
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:boost-defaults
Version: 1.74.0.2
Severity: serious

libboost-all-dev is missing a dependency on the newly introduced
libboost-nowide-dev.

please also bump debhelper and standards versions with a new upload.
--- End Message ---
--- Begin Message ---
Source: boost-defaults
Source-Version: 1.74.0.3
Done: Anton Gladky 

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

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

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated boost-defaults package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Dec 2020 16:09:11 +0100
Source: boost-defaults
Architecture: source
Version: 1.74.0.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Anton Gladky 
Closes: 977195
Changes:
 boost-defaults (1.74.0.3) unstable; urgency=medium
 .
   * [eb1b305] Trim trailing whitespace.
   * [1ed5ff0] Bump debhelper from deprecated 9 to 13.
   * [493770d] Set debhelper-compat version in Build-Depends.
   * [439bbcb] Set compat-level 13.
   * [8b85958] Set Standards-Version 4.5.1. No changes
   * [cac9988] Add dependency on libboost-nowide-dev. (Closes: #977195)
Checksums-Sha1:
 6827758241870ebef2674549e6ccc4753d2beb17 4726 boost-defaults_1.74.0.3.dsc
 ee10e469091a6f9d67b551b50a550e70f54f72dc 12296 boost-defaults_1.74.0.3.tar.xz
 5a27e7e28fe25eec83848a4979cb2713ab0a8ae9 6368 
boost-defaults_1.74.0.3_source.buildinfo
Checksums-Sha256:
 64744c40e244f924391f45420261acbff4e8ca986d6ce341f98c9dbc07270281 4726 
boost-defaults_1.74.0.3.dsc
 2a7037ef5a80673115562a692581e72d6c0c8eeded3dd981a13bad8664161e23 12296 
boost-defaults_1.74.0.3.tar.xz
 c1c32bf9366280b7cc8ca01b30674c4e11dbf53f4472936085bbfaf509c07ff4 6368 
boost-defaults_1.74.0.3_source.buildinfo
Files:
 2e98e1a8ced92bcb87fd3e7b8b1a443a 4726 libs optional boost-defaults_1.74.0.3.dsc
 93e2fb1bbf0c3bd180d4596b3aeaff4a 12296 libs optional 
boost-defaults_1.74.0.3.tar.xz
 152be0a3ecd1569fa2bc4c8326da297b 6368 libs optional 
boost-defaults_1.74.0.3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl/U4AgACgkQ0+Fzg8+n
/wZeuhAAkXMSc8R02D6UT4LDqC9ca8Rx8b9C9H3SH67GHdm3Kr50DL4YvEbqAxVB
Dqmsk3HWymfZxhvS7BmFsoS+FMH2ihB9K40sYW/YQwQy5X+Y4z6J4xyZ3kGgCBRm
7Yn4z2SdZ8GSvMsZidcbW8Hoq5mv7hGAOdC0u+/vOc3/RsLI2gbJMVtHaL4Gi8+h
xpQ6H1e8jIJIdtZZZAh+4XesIwzhTLQl5LjinPZ22mya2kVeuugWK0yPG+UElVfy
l/sBFiwLkpvMT64uIeUlSxDDvivTt4O3WHqSwT+9jPWuWpJOO6emNEcnx7hZx2MX
rcIsVcTS98S46NOTA3xliFRKEk42kgRfoGXnJ+msYEFrXe1x5l50gNmI9VdrI3Eb
Vd1TpMOQ5ZPFPBg11CdKMCbERXRMWBNqpy2g1xVdEVbOl9aRwlyR2bOqzhWb1ood
pY/XKBlCl31zeu7ImdX8h5ug2e5uvYg4LV8TnPBvdR6EZwCO9cP1/koRvdRJqgXO
TetsFJ/BEJzriThWl6effORsNn24LcE5xBjVMA9G+soGAVBZSnJG2UsjAEy78ci2
2m/UAeZgRcWT5bCnTmXIwgWM17qf+J4JjRRcZ/iPXbq8VGeOAkh0jXnd3br9saxO
tH+OGEMWq05UZyirfSMKrBvVJVRMLIPIGrns3iZgYtQkT7CqUv4=
=Tlpi
-END PGP SIGNATURE End Message ---

Processed: Bug#976922 marked as pending in systemd-bootchart

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976922 [src:systemd-bootchart] systemd-bootchart: FTBFS on ppc64el: 
dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Added tag(s) pending.

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

Bug#976922: marked as pending in systemd-bootchart

[Michael Biebl]

Control: tag -1 pending

Hello,

Bug #976922 in systemd-bootchart 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/systemd-team/systemd-bootchart/-/commit/a796667942e8ef5f5285317cdbb301d2994156e5


Increase max PID and CPU constants

The numbers were insufficient for modern servers.
Also avoid crash in svg_ps_bars which might be happening due to the
previous low max pids number.

Patches cherry-picked from
https://github.com/systemd/systemd-bootchart/pull/37

Closes: #976922


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976922

Bug#977208: exim4 install failed

[Andreas Metzler]

On 2020-12-12 Jörg Frings-Fürst  wrote:
> Package: exim4
> Version: 4.94-9
> Severity: grave

> Hello,

> on a fresh bullseye/sid installation I get:

> [qoute]
> # apt update && apt install exim4
> Hit:1 https://wire-app.wire.com/linux/debian stable InRelease
[...]

Please, try apt dist-upgrade first.

cu Andreas

Bug#977208: exim4 install failed

[Jörg Frings-Fürst]

Package: exim4
Version: 4.94-9
Severity: grave

Hello,

on a fresh bullseye/sid installation I get:

[qoute]
# apt update && apt install exim4
Hit:1 https://wire-app.wire.com/linux/debian stable InRelease
Hit:2 https://linux.teamviewer.com/deb stable InRelease
Hit:3 https://repo.skype.com/deb stable InRelease
Hit:4 https://josm.openstreetmap.de/apt alldist InRelease
Hit:5 http://security.debian.org/debian-security bullseye-security InRelease
Hit:6 http://mirror.1und1.de/debian unstable InRelease
Hit:7 http://deb.debian.org/debian bullseye InRelease
Hit:8 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:10 https://download.jitsi.org stable/ InRelease
Hit:9 https://packagecloud.io/AtomEditor/atom/any any InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 exim4 : Depends: exim4-daemon-light (>= 4.94-9) but it is not installable or
  exim4-daemon-heavy (>= 4.94-9) but it is not installable or
  exim4-daemon-custom (>= 4.94-9) but it is not installable
E: Unable to correct problems, you have held broken packages.
[/quote]

But all packages have the right version:


[quote]
# apt policy exim4*
exim4-daemon-light:
  Installed: (none)
  Candidate: 4.94-9+b1
  Version table:
 4.94-9+b1 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    300 http://mirror.1und1.de/debian unstable/main amd64 Packages
exim4-daemon-heavy:
  Installed: (none)
  Candidate: 4.94-9+b1
  Version table:
 4.94-9+b1 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    300 http://mirror.1und1.de/debian unstable/main amd64 Packages
exim4-daemon-custom:
  Installed: (none)
  Candidate: (none)
  Version table:

exim4:
  Installed: (none)
  Candidate: 4.94-9
  Version table:
 4.94-9 500
    500 http://deb.debian.org/debian bullseye/main amd64 Packages
    300 http://mirror.1und1.de/debian unstable/main amd64 Packages
[/quote]

If you need some more infos ask me.


CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema: SYR8SJXB
Wire: @joergfringsfuerst
Skype: joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Kernel: Linux 5.9.0-4-amd64 (SMP w/6 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 exim4 depends on:
ii  debconf [debconf-2.0] 
1.5.74
ii  exim4-base
4.94-9+b1
pn  exim4-daemon-light | exim4-daemon-heavy | exim4-daemon-custom 


exim4 recommends no packages.

exim4 suggests no packages.




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

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Michael Biebl]

Am 12.12.20 um 10:12 schrieb Lucas Nussbaum:

On 11/12/20 at 15:08 +0100, Michael Biebl wrote:



https://github.com/systemd/systemd-bootchart/pull/37
specifically
https://github.com/systemd/systemd-bootchart/pull/37/commits/65320230f5fcb02e81df5131a4dc03092558c263

Could you give this PR a try?


Hi,

This branch fixes the crash.


Thanks a lot, Lucas.

Regards,
Michael

Bug#932197: Bug#937144: Request to join the Neurodebian group

[Yaroslav Halchenko]

On Thu, 30 Apr 2020, Moritz Mühlenhoff wrote:

> > Thanks for the hint.  While this could possibly speet up the upload of
> > nipype I for myself are fine with waiting for the new Build-Depends.
> > Anybody who wants to speed up things is kindly invited to add this patch
> > and upload.

> What's the status here? python-etelemetry is now in the archive and testing.

FWIW: I just uploaded rdflib 5.0.0 (recent nipype needs that
version if any) and pushed initial changes to nipype's packaging git for
1.6.0 . Will try to find more time over weekend to finalize packaging
update (if no other new depends etc) -- needed for heudiconv package
(currently present  nipype version incorrectly handles some DWIs, FYI
for those who care ;)).

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW:   http://www.linkedin.com/in/yarik

Processed: Bug#956779 marked as pending in redshift

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #956779 [src:redshift] redshift: Depends on deprecated libappindicator
Added tag(s) pending.

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

Bug#956779: marked as pending in redshift

[nicoo]

Control: tag -1 pending

Hello,

Bug #956779 in redshift 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/debian/redshift/-/commit/656cfb27c115be8741bd4c86c680bd48e1eb7d2c


Replace libappindicator with ayatana-appindicator

The former is going to be removed for the bullseye release.

Closes: #956779


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/956779

Bug#977205: imagemagick: CVE-2020-29599

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.11.24+dfsg-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for imagemagick.

A very extensive blogpost[1] explains the issue, and note that the
provided POC though does only work so far in ImageMagick7 the issue is
present as well in legacy ImageMagick 6, affected versions should be
around 6.9.8-1 onwards.

The required fixes for ImageMagick6 are referenced in the
security-tracker.

As a side node: For buster the issue is mitigated as the recent DSA
included the 200-disable-ghostscript-formats.patch patch and disables
ghostscript handled formats. As a hardening measure against those
issue it might be ideal to ship the disabling as well in bullseye.

CVE-2020-29599[0]:
| ImageMagick before 6.9.11-40 and 7.x before 7.0.10-40 mishandles the
| -authenticate option, which allows setting a password for password-
| protected PDF files. The user-controlled password was not properly
| escaped/sanitized and it was therefore possible to inject additional
| shell commands via coders/pdf.c.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-29599
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29599
[1] 
https://insert-script.blogspot.com/2020/11/imagemagick-shell-injection-via-pdf.html

Regards,
Salvatore

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

Kernel: Linux 5.10.0-rc6-amd64 (SMP w/8 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.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

Bug#977185: nheko: switch to Boost 1.74

[Matthias Klose]

please consider using the unversioned build dependency, like any other package
is doing it.

Processed: Re: Bug#973459: uim: FAIL: test-composer.scm

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #973459 [src:uim] uim: FAIL: test-composer.scm
Severity set to 'serious' from 'important'

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

Bug#975593: marked as done (python-mapnik: FTBFS against boost_1.74)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 12:50:18 +
with message-id 
and subject line Bug#975593: fixed in mapnik 3.0.23+ds-3
has caused the Debian Bug report #975593,
regarding python-mapnik: FTBFS against boost_1.74
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.)


-- 
975593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-mapnik
Version: 1:0.0~20200224-7da019cf9-2
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most relevant
part is probably this:

/usr/include/boost/spirit/home/karma/nonterminal/rule.hpp:140:9: error: static 
assertion failed: Const/reference qualifiers on Karma rule attribute are 
meaningless
  140 | BOOST_STATIC_ASSERT_MSG(
  | ^~~
error: command '/usr/bin/c++' failed with exit code 1

It is planned to push boost_1.74 as the default version in Debian/Bullseye.

[1] 
http://qa-logs.debian.net/2020/10/27-boost/boost/python-mapnik_0.0~20200224-7da019cf9-2_unstable_boost.log

Best regards

Anton

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

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

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+8J9YRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/wZ0YxAAmZvzsgAVA8mkgzStbF/gCqavZ1zBYUQm
byC0mKUvGIPDvma9L1fxa3S/49vdTkkPnRdMx21KYcjmHVArg5SJ08uqQdF4X4EN
uQbBrw0skFemSQR+zWoWBWcmERQRipJTuKHyGm6U7ttpn5zxj4GNtxVGgOrMZRS7
jzhpoXJ3l3agQkqmAq3BJLxUaFZNpqJcWoqm8YjhVjD9cfPus7cYxKJKKnj0PlqP
/Z1fw9CqgfRoNu8Jn2stp/eKql8rwWnF8CvRFpuEBx/1jpVyXMJUevJ8AaXc10Ga
HSLw4VaD7kObGgZXpWTsdk0i65L2gXkpraNaq9ZjKbV85v9bf+kIfxZUoBQ1uV3E
l5NWlqd0xmVclIlzSSNdPKsR9W+Sac1j1+iSTHecYmvEGUYAfnwc4JQE4N+XIT5B
X725LBI60fgQTnNO2u+WyzHM8u0BBFEzcuLsgkiI4XJiNeQHPF2pJHJK1cVWpQZX
z6jDJwjRUI9c1xBhx19ZUrBYyGTgOZkLihW6+DP6QEGfF2acXLongRH1pT5A7CcF
VKyqP/sS5ueljiqgEUyoe8Nn+T/oyF4jPjMwmAw3YB7ZBqWqfR7TnCbP+C2sio2I
rWoW8kDlOLhkR1VMQk3O3xjoMSGc78bBZvZQGTglor5Cz9jf23l+qQ7XS7rv/fte
H5w/EeS8LCM=
=rPNd
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: mapnik
Source-Version: 3.0.23+ds-3
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated mapnik package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Dec 2020 13:05:32 +0100
Source: mapnik
Architecture: source
Version: 3.0.23+ds-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 975593
Changes:
 mapnik (3.0.23+ds-3) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.5.1, no changes.
   * Add upstream patch for Boost 1.73 compatibility.
 (closes: #975593)
Checksums-Sha1:
 e75b76cec9c1939f99452a18086a130c33a47988 3014 mapnik_3.0.23+ds-3.dsc
 bf64215a1df7c2aafbb932801541f81f8b3cda8c 21328 mapnik_3.0.23+ds-3.debian.tar.xz
 79dbe9d41b10ffe5b7078d3e2ebf4c3885c2126f 15614 
mapnik_3.0.23+ds-3_amd64.buildinfo
Checksums-Sha256:
 009b9eb110b2f2da76eda44dfb515c99a4e5108539cf9f91e94de79988770cc3 3014 
mapnik_3.0.23+ds-3.dsc
 cf60f50e14d065dd3ee10b0aecdfbc3a2bdc4549be53e550143cac551f431adc 21328 
mapnik_3.0.23+ds-3.debian.tar.xz
 8f7416709fb4b0bfd0c39f66d6536314e940d6eb55c8b4dc079a0cab97757129 15614 
mapnik_3.0.23+ds-3_amd64.buildinfo
Files:
 62aa0322ff0a86ce03ce3198b13afe72 3014 libs optional mapnik_3.0.23+ds-3.dsc
 df510b0bd0ff1807d81264efcb7a48c1 21328 libs optional 
mapnik_3.0.23+ds-3.debia

Processed: affects 975593

[Debian Bug Tracking System]

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

> affects 975593 src:python-mapnik
Bug #975593 [src:mapnik] python-mapnik: FTBFS against boost_1.74
Added indication that 975593 affects src:python-mapnik
> thanks
Stopping processing here.

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

Processed: Re: Bug#975593: python-mapnik: FTBFS against boost_1.74

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:mapnik
Bug #975593 [python-mapnik] python-mapnik: FTBFS against boost_1.74
Bug reassigned from package 'python-mapnik' to 'src:mapnik'.
No longer marked as found in versions 1:0.0~20200224-7da019cf9-2.
Ignoring request to alter fixed versions of bug #975593 to the same values 
previously set
> found -1 mapnik/3.0.23+ds-2
Bug #975593 [src:mapnik] python-mapnik: FTBFS against boost_1.74
Marked as found in versions mapnik/3.0.23+ds-2.
> tags -1 pending
Bug #975593 [src:mapnik] python-mapnik: FTBFS against boost_1.74
Added tag(s) pending.

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

Bug#975593: python-mapnik: FTBFS against boost_1.74

[Sebastiaan Couwenberg]

Control: reassign -1 src:mapnik
Control: found -1 mapnik/3.0.23+ds-2
Control: tags -1 pending

This turns out to be an issue in mapnik, Fedora has a patch for
boost1.73 which fixes the python-mapnik FTBFS.

Kind Regards,

Bas

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

Processed: Bug#973648 marked as pending in glade

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #973648 [libgladeui-2-13] libgladeui-2-13: missing Breaks+Replaces: 
libgladeui-2-6
Added tag(s) pending.

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

Bug#973648: marked as pending in glade

[Laurent Bigonville]

Control: tag -1 pending

Hello,

Bug #973648 in glade 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/glade/-/commit/06857d4b765437a7102155214bb6f48a168a8f5e


debian/control.in: Add Breaks/Replaces against libgladeui-2-6 (Closes: #973648)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973648

Bug#977195: libboost-all-dev is missing a dependency on libboost-nowide-dev

[Matthias Klose]

Package: src:boost-defaults
Version: 1.74.0.2
Severity: serious

libboost-all-dev is missing a dependency on the newly introduced
libboost-nowide-dev.

please also bump debhelper and standards versions with a new upload.

Bug#975430: marked as done (libcutl: FTBFS against boost_1.74)

[Debian Bug Tracking System]

Your message dated Sat, 12 Dec 2020 11:19:25 +
with message-id 
and subject line Bug#975430: fixed in libcutl 1.10.0+ds1-4
has caused the Debian Bug report #975430,
regarding libcutl: FTBFS against boost_1.74
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.)


-- 
975430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcutl
Version: 1.10.0+ds1-3
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most relevant
part is probably this:

libtool: compile:  g++ -DHAVE_CONFIG_H -I.. -I.. -DLIBCUTL_DYNAMIC_LIB 
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c fs/auto-remove.cxx 
-o fs/auto-remove.o >/dev/null 2>&1
In file included from 
/usr/include/boost/config/detail/select_stdlib_config.hpp:24,
 from /usr/include/boost/config.hpp:44,
 from /usr/include/boost/regex/config.hpp:44,
 from /usr/include/boost/regex.hpp:28,
 from re/re.cxx:12:
../version:1:1: error: expected unqualified-id before numeric constant

It is planned to push boost_1.74 as the default version in Debian/Bullseye.

[1] 
http://qa-logs.debian.net/2020/10/27-boost/boost/libcutl_1.10.0+ds1-3_unstable_boost.log

Best regards

Anton

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

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

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+6IBcRHGdsYWRrQGRl
Ymlhbi5vcmcACgkQ0+Fzg8+n/wadJQ/+O9lthxA71MdhAabBrKCQ3Gp5SOoqUrf3
Wo90RYBvpjiZHFrrMTR5jddv/hc+DGszc2i+pjLkmXprzIbtMg6w3udXQrt4JGba
9XyENQmvmbRwIxZSmtT8l0suVjrMIFGxbxBzDC8jEXvMWsmEGRh437BH19kFPUCl
Vn14rhZ6Ho/rQvyPCOd7x9XfqChJNLSb1Pa74gniMXx+KDzs0ndidH8zlgyZ4wqb
pmrgYdPhDXfis9b9CmuV0GbATyEFiLS94AQzkY2RITCXTxqak5sxC9FRvvSx1m4u
km0AUzoh82ZvBaUw7EYRH1NyfpVhmAXSl8DdxoowenpLCmrRjMHZ3uu2CUGuMY1B
3+06+vDTZxt2LACBEsTm4Bvu+37ZArNCXkWlmKOUiZxoSMMXav+aDjNYvKhIOQiN
pZ4B+KTjHRr9yPuOioiFLP/IMQFgzunfd8VUYBBBYhrWw1udfnFUyAacfmBnEdIT
EInjfr3kI5+4x9YVw41cixXUv3Auumijn+jXkYA/2hKNhyjS+Ug2sd452HW6GnoJ
KfuuUyAAvBS/UxDNkomilXYtmORjbFbtLep3YuN8MReowbPfVsF9L8oaq8Kebbkl
k38g39CtCCJcSZB4rZwPr0d/Q258Gm2WfzpOjZHr2DDSAJ7zcv8TaWXPZKfYYZzn
Dudol5MXmwk=
=Eylv
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libcutl
Source-Version: 1.10.0+ds1-4
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated libcutl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 12 Dec 2020 11:01:47 +0100
Source: libcutl
Architecture: source
Version: 1.10.0+ds1-4
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 975430
Changes:
 libcutl (1.10.0+ds1-4) unstable; urgency=medium
 .
   * Empty version file for package build time (closes: #975430).
   * Update debhelper level to 13 .
   * Update Standards-Version to 4.5.1 .
Checksums-Sha1:
 049c282b5f569a53cfb11ee5ff891f3d7e64cf37 1934 libcutl_1.10.0+ds1-4.dsc
 8e6fd4ee7cbc65583a3ef27e043cd886287b1a56 8340 
libcutl_1.10.0+ds1-4.debian.tar.xz
Checksums-Sha256:
 6b4090577cd218a0ec00f12227af8107ef26efd08f4e0de973ac77a487ae4609 1934 
libcutl_1.10.0+ds1-4.dsc
 834e618caf28ade2680cf591e5eb085f38e23353923849c360fdd90120d43cd4 8340 
libcutl_1.10.0+ds1-4.debian.tar.xz
Files:
 7ff

Processed: tagging 976922

[Debian Bug Tracking System]

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

> tags 976922 = patch
Bug #976922 [src:systemd-bootchart] systemd-bootchart: FTBFS on ppc64el: 
dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2
Added tag(s) patch; removed tag(s) unreproducible, bullseye, ftbfs, and sid.
> thanks
Stopping processing here.

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

Bug#976509: golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/

[Andreas Henriksson]

On Sat, Dec 12, 2020 at 10:32:15AM +0100, Lucas Nussbaum wrote:
> Hi Andreas,
> 
> Is the above problem going to be a problem at runtime as well?

It depends on which part of /proc you use and how it deviates on
your architecture, but yes... eventually you'll hit something that
errors out in parsing or worse returns an answer that's just wildly
wrong/unexpected.

> If so, I wonder if you should make this package "Architecture: amd64"
> instead of "Architecture: all".
[...]

In theory, the right question is probably what anyone is willing to
support. Debian usually takes the naive approach of assuming porters
will fix up any issues once they're found, but that's not really how
things turn out in practise.

(Also if we limit the archs, what is the correct subset? The ones where
the testsuite succeeds? The ones where it actually works? The ones which
someone is actually promising to support?)

The practical problem is that if the arch field is changed
what happens to the entire reverse dependency tree that has
accumulated? Getting one thing removed from the archive is hard
and painful enough

Regards,
Andreas Henriksson

Bug#975672: xylib: FTBFS against boost_1.74

[Marcin Wojdyr]

This was fixed in the latest release upstream:
https://github.com/wojdyr/xylib/releases
but unfortunately I'm no longer able to maintain the Debian package.
The only package that depends on xylib is fityk. Perhaps fityk
maintainers could help.

Best wishes,
Marcin

Bug#936604: FYI: Python 3 migration of distributuion

[Moritz Muehlenhoff]

On Sat, Dec 12, 2020 at 03:21:06PM +0900, Osamu Aoki wrote:
> Hi,
> 
> It's a fork with a new upstream with some issues.  (Not supported by
> the old upstream)
> 
> Anyway, I switched out from getmail to other MUA.
> 
> No one seems to take over this package maintenance.
> 
> So please remove this package.

Ack, will file an RM bug.

> I am not going to package the new getmail6.

getmail6 _is_ packaged already :-)

https://packages.qa.debian.org/g/getmail6.html

Cheers,
Moritz

Bug#976935: inkscape: FTBFS on ppc64el: make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 'share/templates/default_templates.timestamp'. Stop.

[Lucas Nussbaum]

On 11/12/20 at 16:42 +0100, Mattia Rizzolo wrote:
> Control: tag -1 unreproducible
> 
> On Wed, Dec 09, 2020 at 09:36:42AM +0100, Lucas Nussbaum wrote:
> > During a rebuild of all packages in sid, your package failed to build
> > on ppc64el. At the same time, it did not fail on amd64.
> > 
> > I'm marking this bug as severity:serious since your package currently has
> > ppc64el binary packages in unstable (so this is a regression).
> 
> That's surprising.
> 
> > > make[3]: Entering directory '/<>/obj-powerpc64le-linux-gnu'
> > > make[3]: *** No rule to make target 'po/zh_TW.gmo', needed by 
> > > 'share/templates/default_templates.timestamp'.  Stop.
> > > make[3]: Leaving directory '/<>/obj-powerpc64le-linux-gnu'
> > > make[2]: *** [CMakeFiles/Makefile2:6529: 
> > > share/templates/CMakeFiles/default_templates.dir/all] Error 2
> 
> TBH, such a failure reeks of parallelism-induced inconsistency in the
> makefile.  which is surprising since this package uses cmake…
> 
> > The full build log is available from:
> >http://qa-logs.debian.net/2020/12/09/inkscape_1.0.1-2_unstable.log
> > 
> > If you fail to reproduce this, please provide a build log and diff it with 
> > me
> > so that we can identify if something relevant changed in the meantime.
> 
> Indeed I tried on plummer.d.o and I couldn't reproduce this.
> Attached is my build log, but I couldn't really spot anything due to the
> re-ordered log lines.
> Anyway, that .gmo is correctly produced.
> 
> Do you have any hint as to what might have caused such failure on your
> hand?

Hi,

I tried again under the same conditions (just to make sure it wasn't
transient) and could reproduce the failure.

I also tried after disabling SMT (so the machine has only 20 visible
CPUs) and it succeeded.

Still with SMT disabled, I tried with forcing
DEB_BUILD_OPTIONS=parallel=200, and it failed. Can you reproduce it like
that?

Lucas

Bug#976509: golang-github-shirou-gopsutil: FTBFS: dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu github.com/shirou/

[Lucas Nussbaum]

On 11/12/20 at 22:43 +0100, Andreas Henriksson wrote:
> Hello Lucas Nussbaum,
> 
> On Sat, Dec 05, 2020 at 02:23:54PM +0100, Lucas Nussbaum wrote:
> > Source: golang-github-shirou-gopsutil
> > Version: 2.19.11-3
> > Severity: serious
> > Justification: FTBFS on arm64
> > Tags: bullseye sid ftbfs
> > Usertags: ftbfs-20201205 ftbfs-bullseye
> > 
> > Hi,
> > 
> > During a rebuild of all packages in sid, your package failed to build
> > on arm64 (I don't know if it also fails on amd64).
> [...]
> > > === RUN   TestCpuInfo
> > > cpu_test.go:90: could not get CPU Info: 
> > > {"cpu":0,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"0","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > > cpu_test.go:90: could not get CPU Info: 
> > > {"cpu":1,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"1","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > > cpu_test.go:90: could not get CPU Info: 
> > > {"cpu":2,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"2","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > > cpu_test.go:90: could not get CPU Info: 
> > > {"cpu":3,"vendorId":"","family":"","model":"","stepping":0,"physicalId":"","coreId":"3","cores":1,"modelName":"","mhz":0,"cacheSize":0,"flags":["fp","asimd","evtstrm","aes","pmull","sha1","sha2","crc32","atomics","fphp","asimdhp","cpuid","asimdrdm","lrcpc","dcpop","asimddp","ssbs"],"microcode":""}
> > > --- FAIL: TestCpuInfo (0.00s)
> [...]
> > > FAIL
> > > FAIL  github.com/shirou/gopsutil/cpu  0.047s
> [...]
> > > FAIL
> > > dh_auto_test: error: cd obj-aarch64-linux-gnu && go test -vet=off -v -p 4 
> > > github.com/shirou/gopsutil github.com/shirou/gopsutil/cpu 
> > > github.com/shirou/gopsutil/disk github.com/shirou/gopsutil/docker 
> > > github.com/shirou/gopsutil/host 
> > > github.com/shirou/gopsutil/internal/common 
> > > github.com/shirou/gopsutil/load github.com/shirou/gopsutil/mem 
> > > github.com/shirou/gopsutil/net github.com/shirou/gopsutil/process 
> > > returned exit code 1
> > 
> > The full build log is available from:
> >
> > http://qa-logs.debian.net/2020/12/05/golang-github-shirou-gopsutil_2.19.11-3_unstable.log
> [...]
> 
> With the above log I will, without ever looking deeper at the problem,
> claim that gopsutil parsing of /proc/cpuinfo does not work on your
> architecture of choice.
> 
> I've briefly dug into this package in the past[1] and unless my memory
> serves me wrong my conclusion was that gopsutil's assumptions about
> /proc is not intended to be portable between architectures at all.
> On the other hand /proc looking wildly different between architectures
> on linux is kind of a problem that each architecture that is not the
> most popular one is setting themselves up for problems with. Not even
> using the same syntax in /proc/cpuinfo (or even using same keywords
> as used on mainstream archs, but give them a different meaning!).
> 
> I would personally expect that porters steps up if they want a
> particular piece of software ported to their arch, but I doubt that will
> happen. I also very much doubt anyone else will port to a wide range of
> architectures, or even a single one - plus maintain it.
> 
> I can thus suggest one "solution":
> Disable the testsuite on !amd64 and just let it build without actually
> ever having a chance of working except possibly by chance.
> (We all did this for so many years while kfreebsd was still a testing
> migration blocker, so it's not like my suggestion is a new idea.)

Hi Andreas,

Is the above problem going to be a problem at runtime as well?
If so, I wonder if you should make this package "Architecture: amd64"
instead of "Architecture: all".

If the problem is only at build time (but the package works fine, when
installed, on all architectures), it might be better to leave it as is,
and just document in a bug that it can only be build on amd64. For
example:
retitle 976509 golang-github-shirou-gopsutil: FTBFS when building
arch:all on arch != amd64
severity 976509 minor

Lucas

Bug#976922: systemd-bootchart: FTBFS on ppc64el: dh_auto_test: error: make -j160 check VERBOSE=1 returned exit code 2

[Lucas Nussbaum]

On 11/12/20 at 15:08 +0100, Michael Biebl wrote:
> Am 11.12.20 um 09:09 schrieb Lucas Nussbaum:
> > On 10/12/20 at 22:12 +0100, Michael Biebl wrote:
> > > Am 10.12.20 um 22:10 schrieb John Paul Adrian Glaubitz:
> > > > Hi Michael!
> > > > 
> > > > On 12/10/20 8:42 PM, Michael Biebl wrote:
> > > > > 
> > > > > Testsuite summary for systemd-bootchart 233
> > > > > 
> > > > > # TOTAL: 1
> > > > > # PASS:  1
> > > > > # SKIP:  0
> > > > > # XFAIL: 0
> > > > > # FAIL:  0
> > > > > # XPASS: 0
> > > > > # ERROR: 0
> > > > > 
> > > > 
> > > > Did the test machine you used actually have that many cores?
> > > 
> > > No idea
> > 
> > I tried building with SMT off (so the machine only has 20 visible
> > cores). I could reproduce the failure. (I disabled SMT at runtime using
> > ppc64_cpu --smt=off)
> > 
> > It also fails when running 'make check VERBOSE=1' (so it's not caused by
> > parallelism).
> > 
> > It crashes with:
> > (gdb) r -o /tmp/tmp.k64Np1I2cr -n 10 -r -p
> > Starting program: /root/systemd-bootchart-233/systemd-bootchart -o 
> > /tmp/tmp.k64Np1I2cr -n 10 -r -p
> > [Thread debugging using libthread_db enabled]
> > Using host libthread_db library 
> > "/lib/powerpc64le-linux-gnu/libthread_db.so.1".
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x00014d04 in svg_ps_bars (interval=, 
> > graph_start=2775.3698308829998, ps_first=0x1000505d0, n_cpus=1,
> >  n_samples=10, head=0x100050770, of=0x1000503f0) at src/svg.c:1187
> > 1187i = ps->sample->next->sampledata->counter;
> > (gdb) bt
> > #0  0x00014d04 in svg_ps_bars (interval=, 
> > graph_start=2775.3698308829998, ps_first=0x1000505d0,
> >  n_cpus=1, n_samples=10, head=0x100050770, of=0x1000503f0) at 
> > src/svg.c:1187
> 
> This looks a lot like
> 
> https://github.com/systemd/systemd-bootchart/pull/37
> specifically
> https://github.com/systemd/systemd-bootchart/pull/37/commits/65320230f5fcb02e81df5131a4dc03092558c263
> 
> Could you give this PR a try?

Hi,

This branch fixes the crash.

Lucas

Processed: Raising the bug's severity

[Debian Bug Tracking System]

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

> severity 975430 serious
Bug #975430 [libcutl] libcutl: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975588 serious
Bug #975588 [openms] openms: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975593 serious
Bug #975593 [python-mapnik] python-mapnik: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975660 serious
Bug #975660 [scram] scram: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975665 serious
Bug #975665 [slic3r-prusa] slic3r-prusa: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975666 serious
Bug #975666 [sslsniff] sslsniff: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975667 serious
Bug #975667 [supercollider] supercollider: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975672 serious
Bug #975672 [xylib] xylib: FTBFS against boost_1.74
Severity set to 'serious' from 'important'
> severity 975863 serious
Bug #975863 [leatherman] leatherman: /usr/include/boost/nowide/ are shipped by 
boost_1.74
Ignoring request to change severity of Bug 975863 to the same value.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975430
975588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975588
975593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975593
975660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975660
975665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975665
975666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975666
975667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975667
975672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975672
975863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#975863: Raising the bug's severity

[Anton Gladky]

severity 975430 serious
severity 975588 serious
severity 975593 serious
severity 975660 serious
severity 975665 serious
severity 975666 serious
severity 975667 serious
severity 975672 serious
severity 975863 serious
thanks

boost1.74 is already default in unstable. Thus raising the bug's severity.

Cheers

Anton

Bug#977185: nheko: switch to Boost 1.74

[Sebastian Ramacher]

Source: nheko
Version: 0.7.2-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

nheko currently hardcodes its boost build dependencies with an explicit
version. Since the default boost version is now 1.74 and we are trying
to remove boost 1.71 before the release of bullseye, please switch to
1.74 or to the unversioned boost packages.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#970580: licenseutils: Memory access error

[handsome_feng]

Tags: patch


Hi,

I found this error is caused by the gpl url redirected from
https://www.gnu.org/licenses/gpl-1.0 to
https://www.gnu.org/licenses/old-licenses/gpl-1.0,


so I added the CURLOPT_FOLLOWLOCATION to tell libcurl to follow redirection.


Regards,

handsome_feng

--- a/src/url-downloader.c
+++ b/src/url-downloader.c
@@ -82,6 +82,7 @@ download (struct lu_state_t *state, char
   curl_easy_setopt (state->curl, CURLOPT_HTTPGET, 1);
   curl_easy_setopt (state->curl, CURLOPT_URL, url);
   curl_easy_setopt (state->curl, CURLOPT_WRITEDATA, fileptr);
+  curl_easy_setopt (state->curl, CURLOPT_FOLLOWLOCATION, 1L);
   curl_easy_perform(state->curl);
   fflush (fileptr);
   fsync (fileno (fileptr));


OpenPGP_0x9BB850C013111F0C.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature