Processed: Bug#975360 marked as pending in node-webassemblyjs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #975360 [node-webassemblyjs] node-webassemblyjs: contains source-less code
Added tag(s) pending.

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

Bug#975360: marked as pending in node-webassemblyjs

[Xavier Guimard]

Control: tag -1 pending

Hello,

Bug #975360 in node-webassemblyjs 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/js-team/node-webassemblyjs/-/commit/851c4181d0ae07dac8cb25cdd164df68df3c80d5


No more embed wabt (source unavailable). This will break 
@webassemblyjs/wasm-parser and wast-loader, and then reduce jest features

Closes: #975360


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/975360

Processed: tagging 975365, found 975365 in 1.2.1-1

[Debian Bug Tracking System]

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

> tags 975365 + upstream
Bug #975365 [musl] musl: CVE-2020-28928
Added tag(s) upstream.
> found 975365 1.2.1-1
Bug #975365 [musl] musl: CVE-2020-28928
Marked as found in versions musl/1.2.1-1.
> thanks
Stopping processing here.

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

Bug#975334: marked as done (xeus-python: FTBFS with Python 3.9 as default)

[Debian Bug Tracking System]

Your message dated Sat, 21 Nov 2020 07:42:08 +0200
with message-id 

and subject line Re: Bug#975334: xeus-python ftbfs
has caused the Debian Bug report #975334,
regarding xeus-python: FTBFS with Python 3.9 as default
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.)


-- 
975334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975334
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xeus-python
Version: 0.8.6-2
Severity: serious
Tags: ftbfs sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

Hi Maintainer

Since the upload of python3-defaults with Python 3.9 as the default
version, xeus-python FTBFS.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=xeus-python


CMake Error in CMakeLists.txt:
  Imported target "pybind11_json" includes non-existent path
"/usr/include/python3.8"
  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:
  * The path was deleted, renamed, or moved to another location.
  * An install or uninstall procedure did not complete successfully.
  * The installation package was faulty and references files it does not
  provide.
--- End Message ---
--- Begin Message ---
Hi Gordon

On Fri, 20 Nov 2020 at 19:24, Gordon Ball  wrote:
> I'll make a new upload of pybind11-json-dev then giveback this package.

Thanks!  I saw the upload of pybind11-json and have given back
xeus-python.  There are already some successful builds.

Regards
Graham--- End Message ---

Bug#975365: musl: CVE-2020-28928

[Roberto C. Sanchez]

Package: musl
Severity: grave
Tags: security

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

The following vulnerability was published for musl.

CVE-2020-28928[0]:
wcsnrtombs destination buffer overflow

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-28928
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28928

Please adjust the affected versions in the BTS as needed.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIYZ1DR4ae5UL01q7ldFmTdL1kUIFAl+4oRoACgkQldFmTdL1
kUL5nhAAwJuNKh1eQodFdOANhHFe9Bi8q7Cf9/RFqONVhoUpD8cna7ANY472sfy/
0xZKPatOXvWBFJTyUTs2Z/AhNGy4+TomF4v0DQydo8PmZRY0SRkyqpdOr1bHEFx7
YbBX1XdBJLfCq4Uj8T+kGDSZvueqtdDIe8fGoGKnQD2UFKc9JSXBRZ0CZzwxyGda
feEsYfU/dFiP1aJgVv86WqJw5KYOtKEgmKmcur5PkfUfdrqL3wqR1JlP0OfxsT9H
SjGBVkmlUINWMfrKBZRirYTJUKFPxLPJDZNOB5dqvENVMxigEeIgGRYvPfJxK4P5
dc+1ayAUFBbwUq2k4Vs9TR+E6spyEbodwZXHUXCBchQb6+V8uVTa6Xd6Egvkah7E
xoIMnbre/5vlaWRJH09NaKhFKsE6eXMTv4boPdCC0IprGWIvo99PwuAFLrmpD7pK
TOQMt1XFts0nddMHtD2oVDiepT0NUhNFtUxzO05ZWZMC5eFDlCfiOgPjiFQV7/6U
UXSkEiB41Z5MHXmIJEKBD4gHutu0+nq/hhCsCKAO4vNbbHio2QE6zu7Yi9nKZlpt
aa7IZPWlgcw7yp2hBrz1ENSEPUWhpYUsUL6mq9HiqqWA7wrujbWzDOCvxEQg/TrU
BkyzFVZdMk3wFcjxy6bQipMlY4A5rq6yRPNflSUhHup8Gxoyfzs=
=Badk
-END PGP SIGNATURE-

Bug#968965: xen: FTBFS woes in sid

[Elliott Mitchell]

On Fri, Nov 20, 2020 at 08:02:26PM +0100, Hans van Kranenburg wrote:
> So,
> 
> On 9/21/20 4:16 PM, Hans van Kranenburg wrote:
> > [...]
> > 
> > gcc-Wl,-z,relro -Wl,-z,now -pthread -Wl,-soname
> > -Wl,libxentoolcore.so.1 -shared -Wl,--version-script=libxentoolcore.map
> > -o libxentoolcore.so.1.0 handlereg.opic
> > /usr/bin/ld: i386:x86-64 architecture of input file `handlereg.opic' is
> > incompatible with i386 output
> > /usr/bin/ld: handlereg.opic: file class ELFCLASS64 incompatible with
> > ELFCLASS32
> > /usr/bin/ld: final link failed: file in wrong format
> > collect2: error: ld returned 1 exit status
> 
> This one is caused by "debian/rules: Combine shared Make args". I
> reverted that change for now.
> 
> When retrying the i386 build, I run into yet another failure, sigh:
> 
>  >8 
> 
> dh_install: warning: Cannot find (any matches for)
> "usr/lib/debug/usr/lib/xen-*/boot/*" (tried in ., debian/tmp)
> 
> dh_install: warning: xen-utils-4.14 missing files:
> usr/lib/debug/usr/lib/xen-*/boot/*
> dh_install: error: missing files, aborting
> 
>  >8 
> 
> I can only find CONFIG_PV_SHIM=n in the build log. What is going on
> here? Attached is the build log.
> 
> My WIP branch is here (including the make-patches commit, it's ready to
> build). I also forwarded the thing to latest stable-4.14.
> 
> https://salsa.debian.org/xen-team/debian-xen/-/commits/knorrie/4.14/

I was going to type, "That can't be true!  Both sections are identical,
so that commit *couldn't* have done it!"

Being the careful sort, look closer.  Look closer.  Then realize if one
reads fast they look identical, but they're getting *slightly* different
values for ${XEN_TARGET_ARCH}.  Mainly for $(make_args_xen),
${XEN_TARGET_ARCH} gets $(xen_arch_$(flavour)), but for
$(make_args_tools), ${XEN_TARGET_ARCH} gets $(xen_arch_$(DEB_HOST_ARCH)).

Three of us and we didn't spot that difference.  Should still combine
${XEN_COMPILE_ARCH} which remains identical for both values.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445

Processed: tagging 975344, found 975320 in 5.5.0+dfsg-1, found 975312 in 0.8.1-1, found 973741 in 1.22.4-3 ...

[Debian Bug Tracking System]

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

> tags 975344 + sid bullseye
Bug #975344 [libapache2-mod-auth-kerb] FTBFS with krb5 1.18: significant use of 
internal
Added tag(s) sid and bullseye.
> found 975320 5.5.0+dfsg-1
Bug #975320 [calibre] breaks unrelated packages
Marked as found in versions calibre/5.5.0+dfsg-1.
> found 975312 0.8.1-1
Bug #975312 [src:aravis] aravis: Please reupload source-only
Marked as found in versions aravis/0.8.1-1.
> found 973741 1.22.4-3
Bug #973741 [node-yarnpkg] gitlab: Yarn hasn't been able to find a cache folder 
it can use
There is no source info for the package 'node-yarnpkg' at version '1.22.4-3' 
with architecture ''
Unable to make a source version for version '1.22.4-3'
Marked as found in versions 1.22.4-3.
> tags 975173 + experimental
Bug #975173 [src:git] git: FTBFS: test failed
Added tag(s) experimental.
> found 974594 0.12.0+repack-2
Bug #974594 {Done: Xavier Guimard } [node-snapdragon] 
node-snapdragon-node: missing Breaks+Replaces: node-snapdragon (<= 
0.12.0+repack-2)
Marked as found in versions node-snapdragon/0.12.0+repack-2.
> thanks
Stopping processing here.

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

Processed: clojure bugs created by cljx

[Debian Bug Tracking System]

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

> block 974706 by 974709
Bug #974706 [src:prismatic-schema-clojure] This package isn't complete, as the 
cjlx parts aren't packaged
974706 was not blocked by any bugs.
974706 was not blocking any bugs.
Added blocking bug(s) of 974706: 974709
> block 975218 by 974706
Bug #975218 [src:comidi-clojure] comidi-clojure: FTBFS: Syntax error 
(FileNotFoundException) compiling at (bidi/schema.cljc:1:1).
975218 was not blocked by any bugs.
975218 was not blocking any bugs.
Added blocking bug(s) of 975218: 974706
> block 975221 by 974706
Bug #975221 [src:puppetlabs-ring-middleware-clojure] 
puppetlabs-ring-middleware-clojure: FTBFS: Syntax error (FileNotFoundException) 
compiling at (puppetlabs/ring_middleware/utils.clj:1:1).
975221 was not blocked by any bugs.
975221 was not blocking any bugs.
Added blocking bug(s) of 975221: 974706
> thanks
Stopping processing here.

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

Bug#975362: src:node-rollup-plugin-json: contains source-less wasm code

[Jonas Smedegaard]

Package: src:node-rollup-plugin-json
Version: 4.1.0+~4.0.0-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains compiled webassembly code from project wabt.

A corresponding lintian override has the comment "Unused files",
but that's not ok: Used or not, all code must include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4DAUACgkQLHwxRsGg
ASE2eg/9EC4MIn/cDpQUfTiv153JqRLEtH36B3Py6X8jiqhLzTGvwrQ8aorGOIdp
1MBg/af3FbaZ3cuQtr560yhOvRqB1Lk1hNRH6uDMJpQ98fEJ5cnz8ryG2MnheUKv
57Xp9mGukN/4vxAA+pOva2HnHbZZfsO3IIRsoPmZSXHI7uv67jRBLlk0kQvzcitH
ffVcvXjsnsTqfjtwYjwk0n0nzXt1Df38P3eeTwC0kb8JTnPmJv37Z8rPYirExwPX
NzSUY85Xd5uEJfosfGbOdbkUSlyjtqzMCMXUFxD9TsgbwYUTSZBpOnCchb6FRDND
FbkukwjYFQtcSfwiLtKy8CXIOnJUVCaGDGJHvLrmGxnDqu2jHsB0TOiACGRSGGFA
loAqgXRgothqcTC1HaNdF+Klh+tzIT+hB3MPnXEUr+xeKeveu6hj7TlHj6fwGpex
yziA54ig3Og4gYvMjGiE9FgXSGNuVgW32R7YtDTh+n/fiS4ZnupeR7BxrxXAggHB
+L/4FRNRsruqeaHKiD+C9+rN2kbmDox5ixy9I/o/0hIwhRrKRRjeDu3iDaGKQ59h
i5Xd1PE7I7fwVOolnUELp7bOfy1wZVGauu2YA5JWmf8x3dakA1WehwRzZmc4nT6N
1+eVmvr5r0qGRkYBD/tzFyGeD0oT0yCgwKZJuaiEN9rsA8kIVhg=
=deJF
-END PGP SIGNATURE-

Bug#975361: src:node-rollup-plugin-buble: contains source-less code

[Jonas Smedegaard]

Package: src:node-rollup-plugin-buble
Version: 0.21.3+~0.19.8-2
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

files below packages/wasm/ are source-less compiled wabt code.

Lintian warns about this, but is suppressed with comment "Unused files".
That is wrong: A Debian source package *must* include source.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4ChEACgkQLHwxRsGg
ASFB1hAAn3pcGUDsrTKqMftFl/W4amljA7NdP4ROtZ1L+ipgG9Ua+x4MRdnDGvEW
ostgZJvQVwJK5NSm3OU7rM6hkrmwAC4Aotj/eJMIjTbT4mfo5KyfBedjZgOkzPcI
I5G7tGhXVQ69381rq6S5pYfLWxgR1hVuvohjYb2ko8N4cBqAESDIzVnYgCPhxaQJ
TyNahaQwQZzK3UaR1lgysP7a+MiKrZuQJSU5gYNOxNv8Zn8vFSQ+2K10BVFZHy2r
6Y65eZUP9NcmGsAG3DVYBnZXrBiTd+GMdAP0cXncslVCsbSmOLU+Yn8fJPkrHjH8
RiwJLZiVsh5nbRRMFPuCS657E5KOKYNnOU8g0X5u3Zs/UsPOA0KA4Vy6bz2MYHmD
d08Fy9XA2vRzgfzUXQ+gSd7zBn2kV5fAOQwGkyMrms02FEZACUS0yP4dHF3yb1LF
5aHtcT3QvfTsnjJ56Y8PeXWkzfzBXIZBo2N3Oaf/7XoFTvMX3tGbUgs0mF8O4/0+
Eq8wE3IfbuviI2jvI2RRTyMXMNE1qarKSZ1LVvtS1ZTn52CUv+TvV9tdhzQX5EmB
EooeozVer1NugJ49Osd99L04vclxKaw3LqbFwhfNjyhivsasiVxJ8VXwXkmxtx7a
T5Oq81DuddD5EElOOdhqabai/xSfH5E+NAEcUPYdEAWV6aaIxsg=
=7UD4
-END PGP SIGNATURE-

Bug#975360: node-webassemblyjs: contains source-less code

[Jonas Smedegaard]

Package: node-webassemblyjs
Version: 1.9.1+dfsg+~cs7.7.13-1
Severity: serious
Justification: Policy 2.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

source contains convenience code copy of wabt.js
which consist almost purely of compiled wabt code.

Furthermore, lintian warnings about this issue is wrongly suppressed.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+4B6EACgkQLHwxRsGg
ASEG+hAApEZ5/tEVl+sCMLRbCGzXgdu5az0zuSBYnxjIbJlz75gkWPyMC8JxK+A3
8L2+TRPDIX5EoTAAdojwfqeXygKs8E9sl07POw50//Srw9m+tbvVNn1KL8fun6hm
B0k1GKIWuwoVF92kRUE5rT5ySab7Cx8krEO4fsxB+038O+1wWCTGvApzWh8c1lhU
t9uIuJG0w9mPtHheI44VKaez/ZelJk/qZ3k5Acf+0AjU8E1IGXfkz8P5rrW2H9h7
t+MwJhFPydR/2IcuSYP2jBVqOXJojYHYO78dQQyuSzosYh7WfoO3/FEZdNaAd9WX
Vc+4EVCpi9qfMrlE/eNqdGG0LMd92dr8SvB9Pa6lPLUCMSj5iAyM5N+anKR4u9FH
KL340LkiSf7d0oeRn9sn4NcZlDoDVx7eY3qVBYsmIMIv0mVvt042OfOHqxs2z2fZ
6YqJh6cNx4GLjsLmXsDR+uvz3dnTIIaHYGyf1G0i69a3UYI/D+tkabFO9IKzPTjc
qwh1+By1pXswgN+aTwGnetYOrRF5mXA3RZAVt+tvapVoiX7Q0HlhsACyXeLL55Df
Wnwt1wfkY6wqDTWPXZf06VS0/7v10+emPE5AtL4edsiGcSIUlabVSsOEHMI/R8EL
zP+unlUb54F5ZwLF9Qxtyvr9kR5Ok7xjGxSGbRsYOUjMtwQ2xR8=
=5FNY
-END PGP SIGNATURE-

Bug#975137: marked as done (apt-cacher-ng: FTBFS: collect2: fatal error: ld terminated with signal 11 [Segmentation fault])

[Eduard Bloch]

reopen 975137
reassign 975137 binutils
thanks

Hi,

first I assumed that it's a GOLD issue but looking at
https://buildd.debian.org/status/package.php?p=apt%2dcacher%2dng
shows the real drama. Half of architecture builds fail due to some
obscure segfault of ld linker.

Please investigate.

Best regards,
Eduard.

Processed: bug 972238 is forwarded to http://www.polypux.org/projects/read-edid/ pyrophobic...@gmail.com

[Debian Bug Tracking System]

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

> forwarded 972238 http://www.polypux.org/projects/read-edid/ 
> pyrophobic...@gmail.com
Bug #972238 [src:read-edid] read-edid FTBFS with gcc-10
Set Bug forwarded-to-address to 'http://www.polypux.org/projects/read-edid/ 
pyrophobic...@gmail.com'.
> thanks
Stopping processing here.

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

Bug#975320: Processed: Re: Bug#975284: calibre: crashes on start

[Norbert Preining]

Hi Matthias,

On Fri, 20 Nov 2020, Matthias Klose wrote:
> packaging bug. calibre-bin is rebuilt for 3.9, but you are still calling 3.8.
> You really should use dh_python3 and ${python3:Substvars}.

I am not sure what you are referring to, but we don't call 3.8. We call
/usr/bin/python3
which per python3-minimal seems to be a link to python3.8 on my system.

Could you please explain why you think this is a build error?
We don't set any specific python version and rely on /usr/bin/python3 to
be correct. If this is not the case, please fix it on your side.

I refrain from playing bug reassigning ping pong and hope for an
explanation.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#972749: xen-tools: bullseye: /updates -> -security

[Paul Wise]

On Fri, 2020-11-20 at 23:12 +0200, Adrian Bunk wrote:

> But based on the further discussion in this bug, some hardcoding
> might be the only easily available short-term solution for bullseye?

Sure, short-term hardcoding is fine, although short-term hardcoding
usually turns into long-term hardcoding surprisingly quickly ;)

So perhaps leave this bug open or clone and retitle it as a reminder to
switch from hardcoding to the new mechanism when that happens.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#973201: marked as done (pyzabbix: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.9 3.8" returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 23:03:38 +
with message-id 
and subject line Bug#973201: fixed in pyzabbix 0.8.2-1
has caused the Debian Bug report #973201,
regarding pyzabbix: FTBFS: dh_auto_test: error: pybuild --test -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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh /usr/share/openstack-pkg-tools/pkgos.make --buildsystem=pybuild --with 
> python3
> dh: error: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose 
> from: binary binary-arch binary-indep build build-arch build-indep clean 
> install install-arch install-indep)
> dh build --buildsystem=pybuild --with python3
>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_pyzabbix/build/pyzabbix
> copying pyzabbix/__init__.py -> 
> /<>/.pybuild/cpython3_3.9_pyzabbix/build/pyzabbix
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.8_pyzabbix/build/pyzabbix
> copying pyzabbix/__init__.py -> 
> /<>/.pybuild/cpython3_3.8_pyzabbix/build/pyzabbix
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild pybuild:284: cp -r /<>/tests 
> /<>/.pybuild/cpython3_3.9_pyzabbix/build/
> I: pybuild base:217: cd 
> /<>/.pybuild/cpython3_3.9_pyzabbix/build; python3.9 -m unittest 
> discover -v tests
> test_host_delete (test_api.TestPyZabbix) ... 
> /usr/lib/python3/dist-packages/httpretty/core.py:485: ResourceWarning: 
> unclosed file <_io.BufferedRandom name=4>
>   self.fd = FakeSockFile()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> /usr/lib/python3/dist-packages/httpretty/core.py:485: ResourceWarning: 
> unclosed file <_io.BufferedRandom name=5>
>   self.fd = FakeSockFile()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> ERROR
> test_host_get (test_api.TestPyZabbix) ... 
> /usr/lib/python3/dist-packages/httpretty/core.py:485: ResourceWarning: 
> unclosed file <_io.BufferedRandom name=6>
>   self.fd = FakeSockFile()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> /usr/lib/python3/dist-packages/httpretty/core.py:485: ResourceWarning: 
> unclosed file <_io.BufferedRandom name=7>
>   self.fd = FakeSockFile()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> ERROR
> test_login (test_api.TestPyZabbix) ... 
> /usr/lib/python3/dist-packages/httpretty/core.py:485: ResourceWarning: 
> unclosed file <_io.BufferedRandom name=8>
>   self.fd = FakeSockFile()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> /usr/lib/python3/dist-packages/httpretty/core.py:485: ResourceWarning: 
> unclosed file <_io.BufferedRandom name=9>
>   self.fd = FakeSockFile()
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> ERROR
> 
> ==
> ERROR: test_host_delete (test_api.TestPyZabbix)
> --
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/httpretty/core.py", line 1638, in 
> wrapper
> return test(*args, **kw)
>   File 
> "/<>/.pybuild/cpython3_3.9_pyzabbix/build/tests/test_api.py", 
> line 96, in test_host_delete
> result = zapi.host.delete("22982", "22986")
>   File 
> "/<>/.pybuild/cpython3_3.9_pyzabbix/build/pyzabbix/__init__.py", 
> line 155, in fn
> return self.parent.do_request(
>   File 
> "/<>/.pybuild/cpython3_3.9_pyzabbix/build/pyzabbix/__init__.py", 
> line 100, in do_request
> response = self.session.post(
>   File "/usr/lib/python3/dist-packages/requests/sessions.py", line 578, in 
> post
> return self.request('POST', url, data=data, json=json, **kwargs)
>   File 

Bug#972053: marked as done (CVE-2019-20161 CVE-2019-20162 CVE-2019-20163 CVE-2019-20165 CVE-2019-20170 CVE-2019-20208 CVE-2019-20628 CVE-2019-20629 CVE-2019-20630 CVE-2019-20631 CVE-2019-20632 CVE-202

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 23:00:12 +
with message-id 
and subject line Bug#972053: fixed in gpac 1.0.1+dfsg1-1
has caused the Debian Bug report #972053,
regarding CVE-2019-20161 CVE-2019-20162 CVE-2019-20163 CVE-2019-20165 
CVE-2019-20170 CVE-2019-20208 CVE-2019-20628 CVE-2019-20629 CVE-2019-20630 
CVE-2019-20631 CVE-2019-20632 CVE-2020-11558 CVE-2020-6630 CVE-2020-6631
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.)


-- 
972053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gpac
Version: 0.5.2-426-gc5ad4e4+dfsg5-5
Severity: grave
Tags: security
X-Debbugs-Cc: Debian Security Team 

CVE-2019-20161:
https://github.com/gpac/gpac/issues/1320
https://github.com/gpac/gpac/commit/7a09732d4978586e6284e84caa9c301b2fa5e956

CVE-2019-20162:
https://github.com/gpac/gpac/issues/1327
https://github.com/gpac/gpac/commit/3c0ba42546c8148c51169c3908e845c308746c77

CVE-2019-20163:
https://github.com/gpac/gpac/issues/1335
https://github.com/gpac/gpac/commit/5250afecbc770c8f26829e9566d5b226a3c5fa80 
(chunk #4)

CVE-2019-20165:
https://github.com/gpac/gpac/issues/1338
https://github.com/gpac/gpac/commit/5250afecbc770c8f26829e9566d5b226a3c5fa80 
(chunk #1)

CVE-2019-20170:
https://github.com/gpac/gpac/issues/1328
https://github.com/gpac/gpac/commit/16856430287cc10f495eb241910b4dc45b193e03

CVE-2019-20171:
https://github.com/gpac/gpac/issues/1337
https://github.com/gpac/gpac/commit/72cdc5048dead86bb1df7d21e0b9975e49cf2d97
https://github.com/gpac/gpac/commit/2bcca3f1d4605100bb27d3ed7be25b53cddbc75c

CVE-2019-20208:
https://github.com/gpac/gpac/issues/1348
https://github.com/gpac/gpac/commit/bcfcb3e90476692fe0d2bb532ea8deeb2a77580e 
(chunk #1)

CVE-2019-20628:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/commit/98b727637e32d1d4824101d8947e2dbd573d4fc8
https://github.com/gpac/gpac/issues/1269

CVE-2019-20629:
https://github.com/gpac/gpac/commit/2320eb73afba753b39b7147be91f7be7afc0eeb7
https://github.com/gpac/gpac/issues/1264

CVE-2019-20630:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1268

CVE-2019-20631:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1270

CVE-2019-20632:
https://github.com/gpac/gpac/commit/1ab4860609f2e7a35634930571e7d0531297e090
https://github.com/gpac/gpac/issues/1271

CVE-2020-11558:
https://github.com/gpac/gpac/commit/6063b1a011c3f80cee25daade18154e15e4c058c
https://github.com/gpac/gpac/issues/1440

CVE-2020-6630:
https://github.com/gpac/gpac/issues/1377
https://github.com/gpac/gpac/commit/c7e46e948ebe2d4a532539c7e714cdf655b84521

CVE-2020-6631:
https://github.com/gpac/gpac/issues/1378
https://github.com/gpac/gpac/commit/c7e46e948ebe2d4a532539c7e714cdf655b84521
  
While individual commits refs are listed above, this should really be fixed
via a new upstream release for bullseye, after all the current base version
is from 2015
--- End Message ---
--- Begin Message ---
Source: gpac
Source-Version: 1.0.1+dfsg1-1
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated gpac package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Nov 2020 18:36:39 -0500
Binary: gpac gpac-dbgsym gpac-modules-base gpac-modules-base-dbgsym libgpac10 
libgpac10-dbgsym libgpac-dev
Source: gpac
Architecture: amd64 source
Version: 1.0.1+dfsg1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Reinhard Tartler 
Closes: 782093 931088 932242 940882 972053
Description: 
 gpac   - GPAC Project on Advanced Content - utilities
 gpac-modules-base - GPAC Project on Advanced Content - modules
 libgpac10  - GPAC Project on Advanced Content - shared libraries
 libgpac-dev - GPAC Project on Advanced Content - development files

Bug#972771: marked as done (openstructure ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 23:00:16 +
with message-id 
and subject line Bug#972771: fixed in openstructure 2.2.0~rc-1
has caused the Debian Bug report #972771,
regarding openstructure ftbfs with python3.9
to be marked as done.

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

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


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

openstructure ftbfs with python3.9 (python3-defaults from experimental), looks
like it still looks for 3.8

https://people.debian.org/~ginggs/python3.9-default/openstructure_2.1.0-1build1_amd64-2020-10-23T01:33:06Z.build

[...]
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Found SQLITE3: /usr/lib/x86_64-linux-gnu/libsqlite3.so
-- Found FFTW: /usr/lib/x86_64-linux-gnu/libfftw3f.so
-- Found TIFF: /usr/lib/x86_64-linux-gnu/libtiff.so (found version "4.1.0")
-- Searching for python module PyQt5 for /usr/bin/python3.8
-- Found python module PyQt5
-- Searching for python module PyQt5.sip for /usr/bin/python3.8
-- Found python module PyQt5.sip
--- End Message ---
--- Begin Message ---
Source: openstructure
Source-Version: 2.2.0~rc-1
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated openstructure package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 19 Nov 2020 06:37:26 -0500
Source: openstructure
Binary: libost-base2.2 libost-base2.2-dbgsym libost-bindings2.2 
libost-bindings2.2-dbgsym libost-conop2.2 libost-conop2.2-dbgsym libost-db2.2 
libost-db2.2-dbgsym libost-geom2.2 libost-geom2.2-dbgsym libost-gfx2.2 
libost-gfx2.2-dbgsym libost-gui2.2 libost-gui2.2-dbgsym libost-img-alg2.2 
libost-img-alg2.2-dbgsym libost-img2.2 libost-img2.2-dbgsym libost-info2.2 
libost-info2.2-dbgsym libost-io2.2 libost-io2.2-dbgsym libost-mol-alg2.2 
libost-mol-alg2.2-dbgsym libost-mol2.2 libost-mol2.2-dbgsym libost-seq-alg2.2 
libost-seq-alg2.2-dbgsym libost-seq2.2 libost-seq2.2-dbgsym openstructure 
openstructure-dbgsym python3-ost python3-ost-dbgsym
Architecture: source amd64
Version: 2.2.0~rc-1
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Andrius Merkys 
Description:
 libost-base2.2 - Open-Source Computational Structural Biology Framework
 libost-bindings2.2 - Open-Source Computational Structural Biology Framework
 libost-conop2.2 - Open-Source Computational Structural Biology Framework
 libost-db2.2 - Open-Source Computational Structural Biology Framework
 libost-geom2.2 - Open-Source Computational Structural Biology Framework
 libost-gfx2.2 - Open-Source Computational Structural Biology Framework
 libost-gui2.2 - Open-Source Computational Structural Biology Framework
 libost-img-alg2.2 - Open-Source Computational Structural Biology Framework
 libost-img2.2 - Open-Source Computational Structural Biology Framework
 libost-info2.2 - Open-Source Computational Structural Biology Framework
 libost-io2.2 - Open-Source Computational Structural Biology Framework
 libost-mol-alg2.2 - Open-Source Computational Structural Biology Framework
 libost-mol2.2 - Open-Source Computational Structural Biology Framework
 libost-seq-alg2.2 - Open-Source Computational Structural Biology Framework
 libost-seq2.2 - Open-Source Computational Structural Biology Framework
 openstructure - Open-Source Computational Structural Biology Framework
 python3-ost - Open-Source Computational Structural Biology Framework - Python 3
Closes: 972771
Changes:
 openstructure (2.2.0~rc-1) unstable; urgency=medium
 .
   * New upstream version 2.2.0~rc (Closes: #972771).
   * Refreshing and describing patches.
   * Bumping Standards-Version (no changes).
   * Bumping debhelper-compat (no changes).
Checksums-Sha1:
 00807be8820475397149b11172b89d8b3f4dc414 3399 openstructure_2.2.0~rc-1.dsc
 

Bug#961841: marked as done (fontforge FTBFS on 64bit big endian: test failures)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 23:00:11 +
with message-id 
and subject line Bug#961841: fixed in fontforge 1:20201107~dfsg-1
has caused the Debian Bug report #961841,
regarding fontforge FTBFS on 64bit big endian: test failures
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.)


-- 
961841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fontforge
Version: 1:20190801~dfsg-5
Severity: serious
Tags: ftbfs

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

...
 75: Ligatures and Fractions Table Lookups (with FontForge) FAILED 
(testsuite.at:147)
 76: Ligatures and Fractions Table Lookups (with Python) FAILED 
(testsuite.at:147)
 77: libnameslist checks (with FontForge)FAILED (testsuite.at:148)
 78: libnameslist checks (with Python)   FAILED (testsuite.at:148)
...
ERROR: 71 tests were run,
4 failed unexpectedly.
...


debian-s390 is Cc'ed.
--- End Message ---
--- Begin Message ---
Source: fontforge
Source-Version: 1:20201107~dfsg-1
Done: Anthony Fok 

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated fontforge package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 18 Nov 2020 01:42:18 -0700
Source: fontforge
Binary: fontforge fontforge-common fontforge-dbgsym fontforge-doc 
fontforge-extras fontforge-extras-dbgsym fontforge-nox fontforge-nox-dbgsym 
libfontforge4 libfontforge4-dbgsym python3-fontforge python3-fontforge-dbgsym
Architecture: source all amd64
Version: 1:20201107~dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Anthony Fok 
Description:
 fontforge  - font editor
 fontforge-common - font editor (common files)
 fontforge-doc - documentation for fontforge
 fontforge-extras - font editor - extra programs
 fontforge-nox - font editor - non-X version
 libfontforge4 - font editor - runtime library
 python3-fontforge - font editor - Python bindings
Closes: 948231 961640 961841 963194
Changes:
 fontforge (1:20201107~dfsg-1) unstable; urgency=medium
 .
   [ Jonas Smedegaard ]
   * New upstream version 20200314~dfsg (Closes: #963194)
 + Fixes two security vulnerabilities:
   - CVE-2020-5395 (use-after-free in SFD_GetFontMetaData in sfd.c)
   - CVE-2020-5496 (heap-based buffer overflow in the Type2NotDefSplines()
 function in splinesave.c)
   that were found in FontForge 20190801 (Closes: #948231)
   * copyright: update overage
   * use buildsystem cmake+ninja (not autotools);
 build-depend on cmake ninja-build
 (not libltdl-dev autoconf-archive)
   * stop build-depend on chrpath
 (unused since 1:20160404~dfsg-1)
   * update install paths
 (upstream installs appdata in correct path now)
   * drop patches 0003 0004 2002 3000:
 obsoleted by new upstream release
   * update (and reduce) patch 2003
   * add patches cherry-picked upstream to fix a range of issues
 Fixes "FTBFS on 64-bit big endian: test failures" (Closes: #961841)
   * bump library API major version to 4
   * drop libgdraw package:
 upstream no longer provides that as shared library
   * stop ship python simple/* scripts:
 No longer installed upstream
   * Temporarily omit installing scripts for fontforge-extras,
 seemingly not built upstream
   * build sphinx documentation;
 build-depend on dh-sequence-sphinxdoc
   * stop ship extra libraries libgunicode.so libgutils.so:
 upstream no longer provides those as shared library
 .
   [ Hideki Yamane ]
   * specify dh 13
   * fix to add ${DEB_HOST_MULTIARCH} for libfontforge.so path
   * Add python3-sphinx for document build for GUI build
   * Add more build options MAINTAINER_TOOLS and WRITE_PFM
 .
   [ Anthony Fok ]
   * New upstream version 20201107~dfsg (FontForge 20th Anniversary Edition)
 + Display issues on Wayland are now fixed (Closes: #961640)
   * Remove cherry-picked upstream patches as they are 

Bug#666707: marked as done (hfsprogs is not DFSG-Free)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 23:00:12 +
with message-id 
and subject line Bug#666707: fixed in hfsprogs 540.1.linux3-2
has caused the Debian Bug report #666707,
regarding hfsprogs is not DFSG-Free
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.)


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

Hello.

hfsprogs license is "Apple Public Source License" (Version 2).
This license is not DFSG-Free.  

Suggests:

1. hfsprogs move to non-free.
2. remove hfsprogs.  

Thanks.

References:

http://packages.debian.org/changelogs/pool/main/h/hfsprogs/hfsprogs_332.25-8/hfsprogs.copyright
http://wiki.debian.org/DFSGLicenses#Apple_Public_Source_License_.28APSL.29
http://lists.debian.org/debian-legal/2004/06/msg00573.html 


-- System Information:
Debian Release: 6.0.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686-bigmem (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages hfsprogs depends on:
ii  libbsd0 0.2.0-1  utility functions from BSD systems
ii  libc6   2.11.3-3 Embedded GNU C Library: Shared lib
ii  libssl0.9.8 0.9.8o-4squeeze7 SSL shared libraries

hfsprogs recommends no packages.

hfsprogs suggests no packages.


--- End Message ---
--- Begin Message ---
Source: hfsprogs
Source-Version: 540.1.linux3-2
Done: John Paul Adrian Glaubitz 

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

Debian distribution maintenance software
pp.
John Paul Adrian Glaubitz  (supplier of updated 
hfsprogs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 17 Nov 2020 11:16:06 +0100
Source: hfsprogs
Binary: hfsprogs hfsprogs-dbgsym
Architecture: source amd64
Version: 540.1.linux3-2
Distribution: unstable
Urgency: medium
Maintainer: John Paul Adrian Glaubitz 
Changed-By: John Paul Adrian Glaubitz 
Description:
 hfsprogs   - mkfs and fsck for HFS and HFS+ file systems
Closes: 666707
Changes:
 hfsprogs (540.1.linux3-2) unstable; urgency=medium
 .
   * Change Section to non-free/otherosfs in debian/control (Closes: #666707)
   * Set XS-Autobuild to yes in debian/control
   * Remove unused target override_dh_auto_clean in debian/rules
   * Remove unused target override_dh_auto_test in debian/rules
Checksums-Sha1:
 e0ce51126c02ed30802df3cc797a324e356d0a42 1974 hfsprogs_540.1.linux3-2.dsc
 edf695e9b8d36aa7a13e976c8e19746b26dd52ec 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 4d9067d5451a5b60e3b6b0b27ebcbc29a88eb10f 15492 
hfsprogs_540.1.linux3-2.debian.tar.xz
 e965e67775408c8b471f04e597880189277ead9f 405924 
hfsprogs-dbgsym_540.1.linux3-2_amd64.deb
 2698916a0bbf78505d8ee5d7e61e2fc4b18f35ef 6236 
hfsprogs_540.1.linux3-2_amd64.buildinfo
 76ca91003de6857349ba4094c2cfeb53ad12352c 144692 
hfsprogs_540.1.linux3-2_amd64.deb
Checksums-Sha256:
 c5c87b734cd7080eb48b62822cc2e8e526971be30d20ae089d20b4957a8ea268 1974 
hfsprogs_540.1.linux3-2.dsc
 b01b203a97f9a3bf36a027c13ddfc59292730552e62722d690d33bd5c24f5497 411205 
hfsprogs_540.1.linux3.orig.tar.gz
 769e947e177866458108b288fdc63950ad06bd159b5f9aa849de35dca98676de 15492 
hfsprogs_540.1.linux3-2.debian.tar.xz
 e090bd480541e79bfe1e871df816a2570904e874da238c163e1b85ba222167ab 405924 
hfsprogs-dbgsym_540.1.linux3-2_amd64.deb
 6643cc92c49725f1167b4749a5d34fec9df868c69c820a7d082112e90daa1e4a 6236 
hfsprogs_540.1.linux3-2_amd64.buildinfo
 a90b2a06a8ef474adeb8c6802f72b0dca40607f81b3bd7515e90f1d39f27767d 144692 
hfsprogs_540.1.linux3-2_amd64.deb
Files:
 cb59e9273c14925af1ee475dcd444e57 1974 non-free/otherosfs optional 
hfsprogs_540.1.linux3-2.dsc
 0435afc389b919027b69616ad1b05709 411205 non-free/otherosfs optional 
hfsprogs_540.1.linux3.orig.tar.gz
 32c149ab81f9586268a9fdc40c13f106 15492 non-free/otherosfs optional 
hfsprogs_540.1.linux3-2.debian.tar.xz
 

Processed: fixing out of order mail delivery

[Debian Bug Tracking System]

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

> tag 975142 -unreproducible
Bug #975142 [gcc-10] internal compiler error: ‘verify_type’ failed
Removed tag(s) unreproducible.
> thanks
Stopping processing here.

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

Processed: Move where the bugs are

[Debian Bug Tracking System]

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

> reassign 975219 gfortran-10 10.2.0-17
Bug #975219 [src:elkcode] elkcode: FTBFS: internal compiler error: in 
lookup_field_for_decl, at tree-nested.c:288
Bug reassigned from package 'src:elkcode' to 'gfortran-10'.
No longer marked as found in versions elkcode/6.3.2-2.
Ignoring request to alter fixed versions of bug #975219 to the same values 
previously set
Bug #975219 [gfortran-10] elkcode: FTBFS: internal compiler error: in 
lookup_field_for_decl, at tree-nested.c:288
Marked as found in versions gcc-10/10.2.0-17.
> affects 975219 src:elkcode
Bug #975219 [gfortran-10] elkcode: FTBFS: internal compiler error: in 
lookup_field_for_decl, at tree-nested.c:288
Added indication that 975219 affects src:elkcode
> reassign 975153 gcc-10 10.2.0-17
Bug #975153 [src:peg] peg: FTBFS: src/peg.peg-c:5:1: internal compiler error: 
in notice_source_line, at final.c:3237
Bug reassigned from package 'src:peg' to 'gcc-10'.
No longer marked as found in versions peg/0.1.18-1.
Ignoring request to alter fixed versions of bug #975153 to the same values 
previously set
Bug #975153 [gcc-10] peg: FTBFS: src/peg.peg-c:5:1: internal compiler error: in 
notice_source_line, at final.c:3237
Marked as found in versions gcc-10/10.2.0-17.
> affects 975153 src:peg
Bug #975153 [gcc-10] peg: FTBFS: src/peg.peg-c:5:1: internal compiler error: in 
notice_source_line, at final.c:3237
Added indication that 975153 affects src:peg
> thanks
Stopping processing here.

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

Processed: Re: [Debian-med-packaging] Bug#975142: lambda-align2: FTBFS: lambda.cpp:100:1: error: type variant with ‘TYPE_ALIAS_SET_KNOWN_P’

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible
Bug #975142 [gcc-10] internal compiler error: ‘verify_type’ failed
Added tag(s) unreproducible.

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

Bug#975142: [Debian-med-packaging] Bug#975142: lambda-align2: FTBFS: lambda.cpp:100:1: error: type variant with ‘TYPE_ALIAS_SET_KNOWN_P’

[Étienne Mollier]

Control: tag -1 unreproducible

Hi Lucas,

Lucas Nussbaum, on 2020-11-19 10:35:39 +0100:
> > /<>/src/lambda.cpp: At global scope:
> > /<>/src/lambda.cpp:100:1: error: type variant with 
> > ‘TYPE_ALIAS_SET_KNOWN_P’
> >   100 | }
> >   | ^
> >   > type  > asm_written public type_6 HI
> > size 
> > unit-size 
[...]

I triggered a rebuild of lambda-align because I was very curious
about that peculiar error, but I failed to reproduce it on my
end with today's update of a clean chroot (2020-11-20).  The end
result also passed autopkgtest without issues.  Could it have
been a transient error?

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#975142: [Debian-med-packaging] Bug#975142: lambda-align2: FTBFS: lambda.cpp:100:1: error: type variant with ‘TYPE_ALIAS_SET_KNOWN_P’

[Étienne Mollier]

Control: tag -1 -unreproducible
Control: tag -1 confirmed

Withdrawing the unreproducible tag, I pulled plain lambda-align
instead of lambda-align2.  The issue occurs on my end as well.

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.


signature.asc
Description: PGP signature

Processed: Re: [Debian-med-packaging] Bug#975142: lambda-align2: FTBFS: lambda.cpp:100:1: error: type variant with ‘TYPE_ALIAS_SET_KNOWN_P’

[Debian Bug Tracking System]

Processing control commands:

> tag -1 -unreproducible
Bug #975142 [gcc-10] internal compiler error: ‘verify_type’ failed
Ignoring request to alter tags of bug #975142 to the same tags previously set
> tag -1 confirmed
Bug #975142 [gcc-10] internal compiler error: ‘verify_type’ failed
Added tag(s) confirmed.

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

Bug#972779: marked as done (zeroc-ice ftbfs with python3.9)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 21:38:44 +
with message-id 
and subject line Bug#972779: fixed in zeroc-ice 3.7.4-2
has caused the Debian Bug report #972779,
regarding zeroc-ice ftbfs with python3.9
to be marked as done.

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

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


-- 
972779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:zeroc-ice
Version: 3.7.4-1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

zeroc-ice ftbfs with python3.9 (python3-defaults from experimental):

https://people.debian.org/~ginggs/python3.9-default/zeroc-ice_3.7.4-1build1_amd64-2020-10-23T04:32:29Z.build

modules/IcePy/Init.cpp: In function ‘PyObject* PyInit_IcePy()’:
modules/IcePy/Init.cpp:147:24: error: ‘void PyEval_InitThreads()’ is
deprecated [-Werror=deprecated-declarations]
  147 | PyEval_InitThreads();
  |^
In file included from /usr/include/python3.9/Python.h:145,
 from modules/IcePy/Config.h:23,
 from modules/IcePy/BatchRequestInterceptor.h:8,
 from modules/IcePy/Init.cpp:5:
/usr/include/python3.9/ceval.h:130:37: note: declared here
  130 | Py_DEPRECATED(3.9) PyAPI_FUNC(void) PyEval_InitThreads(void);
  | ^~
--- End Message ---
--- Begin Message ---
Source: zeroc-ice
Source-Version: 3.7.4-2
Done: =?utf-8?q?Jos=C3=A9_Guti=C3=A9rrez_de_la_Concha?= 

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

Debian distribution maintenance software
pp.
José Gutiérrez de la Concha  (supplier of updated zeroc-ice 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 20 Nov 2020 19:19:30 +0100
Source: zeroc-ice
Architecture: source
Version: 3.7.4-2
Distribution: unstable
Urgency: medium
Maintainer: José Gutiérrez de la Concha 
Changed-By: José Gutiérrez de la Concha 
Closes: 972779
Changes:
 zeroc-ice (3.7.4-2) unstable; urgency=medium
 .
   * Fix ftbfs with python3.9 (Closes: #972779)
Checksums-Sha1:
 453c68fe8fa1cfcdd0867757f4c7c40b76f97fa6 3607 zeroc-ice_3.7.4-2.dsc
 99b0de2b2543d13742e97f81e29780cc0fa43b37 28092 zeroc-ice_3.7.4-2.debian.tar.xz
 49268a71ead3a4adbd8d43761c0c28afc056aa0e 14072 
zeroc-ice_3.7.4-2_source.buildinfo
Checksums-Sha256:
 0cb656f9553d408669a1cfa7ec86988518e918392dd0aa8c704a652510e2bbee 3607 
zeroc-ice_3.7.4-2.dsc
 4633cf9e94bf999c03dfcc57992499f136cb9ca1ceaf23e729c737667ed593c6 28092 
zeroc-ice_3.7.4-2.debian.tar.xz
 36efe0e149438a1225fdf415a2093189f9f46ef72cd63d17f6c16b06ea8968fa 14072 
zeroc-ice_3.7.4-2_source.buildinfo
Files:
 70b4c3f76b955de3e6e77ef7cb28eb1b 3607 devel optional zeroc-ice_3.7.4-2.dsc
 00bd41f0fb6dc516823aabafe619830e 28092 devel optional 
zeroc-ice_3.7.4-2.debian.tar.xz
 5e3db862381e3806002a079cec5e22df 14072 devel optional 
zeroc-ice_3.7.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEx3JzEQ5l2SHrR25CgB+R4qj4AXIFAl+4M5kACgkQgB+R4qj4
AXI0Qg/9Gll6bY9jPFcrZ7v+adqv+0lLghWOLHGHYVlI+GLqGKAsUFvOIJdo6zc/
pQRjVLrPrh6PzEwc1mi8pPsqsl30yuew6U0flRQ2tpYVgxJsap5mypcT8g5VledQ
J6xYtiEgauoRdl6c1IBMiXnowg/wD7ks/tNnQXqLXltLhzbzOFq3mwzagVkktVm1
rAaIS9A2lRz7EnI/R/c1w7SQmHb2BMIjcj2XyYTQuPhv/vsVARQQB16y5klPc8Ho
VUVKde1+41P1HI6AziTs6i8UCVupDa0UBj6mtnHczAHyCA4vtEnfQBDE9Mhk1nyJ
hroeMmp5jf+ZzMsIuwnC4HjepVb7FkxZl2nj/kN4ehaTN2CI7l8scTTsd1KWvOMD
GmlVvfvA2oRplBHjRnBfrCh2kdq6n5PXQtrWyt4s3xBE3Oq0BAAbp93SP2Op4esZ
Vtmil/3u5pzfMuS+Jb8d5CuGi51w1M+k3gxiQ4ci6RqbygiWHeMXX+bZOOTGBMVs
abwv2ttmnm8fJOujP4oo+91SmVvvOkMzGGSmwhBUl7eIAu9VTHdBSTBAYJfMI9Bc
0jbYGSrfVTz2cp1rDUzowEnmtFRXNeCKD80X5oBlVqmhohuQ+ZtxKCDv2RhYaWdd
mTmnoQ3XGVTvuG/3A4gne3zvoi9nd+JThHZLVi1hlZtKM0ScwzM=
=8aah
-END PGP SIGNATURE End Message ---

Bug#972126: libopendbx: Please remove support for long-unmaintained sqlite 2

[David Bürgin]

Attempt to fix here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975353

Processed: tagging 971829

[Debian Bug Tracking System]

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

> tags 971829 + patch fixed-upstream
Bug #971829 [python3-pyopencl] python3-pyopencl: Random runtime error in the 
C++ layer (crash the program)
Added tag(s) patch and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#972749: xen-tools: bullseye: /updates -> -security

[Adrian Bunk]

On Fri, Oct 23, 2020 at 01:39:11PM +0800, Paul Wise wrote:
>...
> It is much better to use distro-info than to hard-code the release
> version numbers.
>...

But based on the further discussion in this bug, some hardcoding might 
be the only easily available short-term solution for bullseye?

> bye,
> pabs

cu
Adrian

Processed: tagging 975344

[Debian Bug Tracking System]

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

> tags 975344 + upstream
Bug #975344 [libapache2-mod-auth-kerb] FTBFS with krb5 1.18: significant use of 
internal
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 975344 is forwarded to https://sourceforge.net/p/modauthkerb/bugs/62/

[Debian Bug Tracking System]

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

> forwarded 975344 https://sourceforge.net/p/modauthkerb/bugs/62/
Bug #975344 [libapache2-mod-auth-kerb] FTBFS with krb5 1.18: significant use of 
internal
Set Bug forwarded-to-address to 
'https://sourceforge.net/p/modauthkerb/bugs/62/'.
> thanks
Stopping processing here.

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

Processed: found 975344 in 5.4-2.4

[Debian Bug Tracking System]

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

> found 975344 5.4-2.4
Bug #975344 [libapache2-mod-auth-kerb] FTBFS with krb5 1.18: significant use of 
internal
Marked as found in versions libapache-mod-auth-kerb/5.4-2.4.
> thanks
Stopping processing here.

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

Processed: Re: Bug#975344: libkrb5-3: ABI breakage in 1.18: krb5_rc_resolve_full missing

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libapache2-mod-auth-kerb
Bug #975344 [libkrb5-3] libkrb5-3: ABI breakage in 1.18: krb5_rc_resolve_full 
missing
Bug reassigned from package 'libkrb5-3' to 'libapache2-mod-auth-kerb'.
No longer marked as found in versions krb5/1.18.2-1.
Ignoring request to alter fixed versions of bug #975344 to the same values 
previously set
> found -1  libapache2-mod-auth-kerb/5.4-2.4
Bug #975344 [libapache2-mod-auth-kerb] libkrb5-3: ABI breakage in 1.18: 
krb5_rc_resolve_full missing
The source libapache2-mod-auth-kerb and version 5.4-2.4 do not appear to match 
any binary packages
Marked as found in versions libapache2-mod-auth-kerb/5.4-2.4.
> retitle -1  FTBFS with krb5 1.18: significant use of internal
Bug #975344 [libapache2-mod-auth-kerb] libkrb5-3: ABI breakage in 1.18: 
krb5_rc_resolve_full missing
Changed Bug title to 'FTBFS with krb5 1.18: significant use of internal' from 
'libkrb5-3: ABI breakage in 1.18: krb5_rc_resolve_full missing'.

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

Bug#975344: libkrb5-3: ABI breakage in 1.18: krb5_rc_resolve_full missing

[Sam Hartman]

control: reassign -1 libapache2-mod-auth-kerb
control: found -1  libapache2-mod-auth-kerb/5.4-2.4
control: retitle -1  FTBFS with krb5 1.18: significant use of internal
APIs and data structures
control: affects -1 libkrb5-3

Hi.
Kerberos 5 1.18 significantly refactors the replay cache implementation.
Unfortunately, if you take a look at src/mit-internals.h in the
mod-auth-kerb sources, you'll find that the functioning of mod-auth-kerb
depends on several internal APIs and internal data structures including
the donot_replay structure and the  APIs related to replay cache
resolution.

I appreciate the comments about the bugs in krb5 1.3 that lead to this
situation, but I'll note that krb5 1.3 hasn't been in Debian since 2005.
It's sort of unfortunate that things haven't been fixed on the
libapache2-mod-auth-kerb side in the intervening 15 years:-)


This is definitely going to require changes on the
libapache2-mod-auth-kerb side.


signature.asc
Description: PGP signature

Bug#975137: marked as done (apt-cacher-ng: FTBFS: collect2: fatal error: ld terminated with signal 11 [Segmentation fault])

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 19:48:33 +
with message-id 
and subject line Bug#975137: fixed in apt-cacher-ng 3.5-2
has caused the Debian Bug report #975137,
regarding apt-cacher-ng: FTBFS: collect2: fatal error: ld terminated with 
signal 11 [Segmentation fault]
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.)


-- 
975137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apt-cacher-ng
Version: 3.5-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> /usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now 
> -Wl,-fuse-ld=gold -Wl,--threads -Wl,--as-needed -Wl,-O1 -Wl,--discard-all 
> -Wl,--no-undefined -Wl,--build-id=sha1 -Wl,--gc-sections 
> CMakeFiles/apt-cacher-ng.dir/apt-cacher.cc.o -o ../apt-cacher-ng  
> -Wl,-rpath,/<>/obj-x86_64-linux-gnu: ../libsupacng.so -latomic 
> -levent -levent_pthreads -levent -lwrap -lz -lbz2 -llzma -lssl -lcrypto 
> -lsystemd -lpthread -levent_pthreads -lwrap -lz -lbz2 -llzma -lssl -lcrypto 
> -lsystemd -lpthread 
> collect2: fatal error: ld terminated with signal 11 [Segmentation fault]
> compilation terminated.
> make[3]: *** [source/CMakeFiles/apt-cacher-ng.dir/build.make:107: 
> apt-cacher-ng] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/apt-cacher-ng_3.5-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: apt-cacher-ng
Source-Version: 3.5-2
Done: Eduard Bloch 

We believe that the bug you reported is fixed in the latest version of
apt-cacher-ng, 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.
Eduard Bloch  (supplier of updated apt-cacher-ng 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, 20 Nov 2020 19:15:22 +0100
Source: apt-cacher-ng
Architecture: source
Version: 3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Eduard Bloch 
Changed-By: Eduard Bloch 
Closes: 975137
Changes:
 apt-cacher-ng (3.5-2) unstable; urgency=medium
 .
   * Disable use of gold linker to avoid linker crash; this has been observed
 on mipsel before and probably also affects amd64 (closes: #975137)
Checksums-Sha1:
 f4fe7f0b896ddbdeb5fb006b2e49557581f43e98 2208 apt-cacher-ng_3.5-2.dsc
 120d1642d6f3144527ec6295ec59af4b44d69f7a 49652 
apt-cacher-ng_3.5-2.debian.tar.xz
 3803120c2067e91dfeaab7bcb8bcbb04135d62da 9022 
apt-cacher-ng_3.5-2_source.buildinfo
Checksums-Sha256:
 661dea731d47ea8ee35158b90b67e432bbbe2f8a6c8d8f061f58745d25447cc4 2208 
apt-cacher-ng_3.5-2.dsc
 c00ad391c7d4358bcf035fd1b7d8c277a11e97c8316d4b024773d236262d66d0 49652 
apt-cacher-ng_3.5-2.debian.tar.xz
 7b2d8a84afa52075438e9c6a50d73d67c964e1461250347daf4dbef5079575cc 9022 
apt-cacher-ng_3.5-2_source.buildinfo
Files:
 14233658bbb5c982c0eee868dc56f569 2208 net optional apt-cacher-ng_3.5-2.dsc
 5f033f6fba4c30580a40db52fa3e117d 49652 net optional 
apt-cacher-ng_3.5-2.debian.tar.xz
 c87195738e6066d06152befec0e91ee2 9022 net optional 
apt-cacher-ng_3.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEZI3Zj0vEgpAXyw40aXQOXLNf7DwFAl+4GEcACgkQaXQOXLNf
7DxyHRAAqR4Ra/rCyxYWbY6Ee5DveQgIp6zIDQ/gM+KmePy/0+OHKYCz8MCc5ZIc
rgej1gMBqgINTAm8nMrQwyxektqbmJ4Q2Eqlu4ff9ua192apiT4bG5bHYWuU0tIh
1IHbo2xUNdPst95MZOhTRnRFNMl0pyRuPiEa/RBM5JqBtaAyks+ORKDupBsYZ9dA
ganoKfBzLXOV9up93e9JpqSIHw29mrSmtpA8xAsg8IRYqBF932KND/iuFSLxm004

Processed: Re: Bug#974982: transition: krb5

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 975344
Bug #974982 [release.debian.org] transition: krb5
974982 was not blocked by any bugs.
974982 was not blocking any bugs.
Added blocking bug(s) of 974982: 975344

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

Bug#951508: marked as done (lmod: broken on all architectures except x86_64 (wrong search path))

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 19:02:08 +
with message-id 
and subject line Bug#951508: fixed in lmod 6.6-0.3+deb10u1
has caused the Debian Bug report #951508,
regarding lmod: broken on all architectures except x86_64 (wrong search path)
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.)


-- 
951508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lmod
Version: 6.6-0.3
Severity: important

Description:

Whe using lmod on powerpc system, it show the below errors:
/usr/bin/lua: /usr/share/lua/5.2/posix/init.lua:29: module 'posix.ctype' not 
found:
no field package.preload['posix.ctype']
no file '/usr/local/share/lua/5.2/posix/ctype.lua'
no file '/usr/local/share/lua/5.2/posix/ctype/init.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype/init.lua'
no file '/usr/share/lua/5.2/posix/ctype.lua'
no file '/usr/share/lua/5.2/posix/ctype/init.lua'
no file './posix/ctype.lua'
no file '/usr/local/lib/lua/5.2/posix/ctype.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix/ctype.so'
no file '/usr/lib/lua/5.2/posix/ctype.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './posix/ctype.so'
no file '/usr/local/lib/lua/5.2/posix.so'
no file '/usr/lib/x86_64-linux-gnu/lua/5.2/posix.so'
no file '/usr/lib/lua/5.2/posix.so'
no file '/usr/local/lib/lua/5.2/loadall.so'
no file './posix.so'

One of the search path is /usr/lib/x86_64-linux-gnu/lua/5.2/ instead of 
/usr/lib/powerpc64le-linux-gnu/lua/5.2/, where the file can be found


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 4.14.158-power8-aufs-1 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lmod depends on:
ii  lua-filesystem  1.6.3-1
ii  lua-json1.3.3-2
ii  lua-posix   33.4.0-3
ii  lua-term0.07-0.1
ii  lua5.2  5.2.4-1.1+b3
ii  tcl 8.6.0+9

lmod recommends no packages.

lmod suggests no packages.

-- Configuration Files:
/etc/lmod/modulespath [Errno 116] Stale file handle: '/etc/lmod/modulespath'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lmod
Source-Version: 6.6-0.3+deb10u1
Done: Lucas Nussbaum 

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

Debian distribution maintenance software
pp.
Lucas Nussbaum  (supplier of updated lmod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Oct 2020 13:24:01 +0100
Source: lmod
Architecture: source
Version: 6.6-0.3+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Aaron Zauner 
Changed-By: Lucas Nussbaum 
Closes: 951508
Changes:
 lmod (6.6-0.3+deb10u1) buster; urgency=medium
 .
   * Change Architecture: to any. Closes: #951508
 This is required because lmod now gets LUA_PATH and LUA_CPATH at
 compile time (to deal with users overriding those variables).
 See https://github.com/TACC/Lmod/issues/112
 There was an upstream report that this breaks Raspian, which was rejected,
 so it is unlikely that upstream will return to the current behaviour.
 See https://github.com/TACC/Lmod/issues/338
 Thanks to Baptiste Jonglez for finding the relevant upstream bug reports.
 The same change was just uploaded as an NMU to unstable (in 6.6-0.4).
Checksums-Sha1:
 802d6a8590997afe23bdcb90d0b8f6a894adcebf 1906 lmod_6.6-0.3+deb10u1.dsc
 feb1a4ca978dbb7b9a32fc18c641cc0e2b716b8f 4936 
lmod_6.6-0.3+deb10u1.debian.tar.xz
 6628dbe334f24ead272460428f2ee1878980ccd5 5950 
lmod_6.6-0.3+deb10u1_source.buildinfo
Checksums-Sha256:
 

Bug#970898: marked as done (katarakt FTBFS: octal parsing of poppler version)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 19:30:56 +0100
with message-id <22332666.YAabUgFi5P@kjartansson>
and subject line Fixed in unstable
has caused the Debian Bug report #970898,
regarding katarakt FTBFS: octal parsing of poppler version
to be marked as done.

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

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


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

katarakt fails to build from source. A build ends with:

| g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -Wextra -fPIC -DQT_DEPRECATED_WARNINGS 
-DPOPPLER_VERSION_MAJOR=20 -DPOPPLER_VERSION_MINOR=09 -DPOPPLER_VERSION_MICRO=0 
-DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_WIDGETS_LIB 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -I. 
-I/usr/include/poppler/qt5 -I/usr/include/poppler 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtXml 
-I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o resourcemanager.o 
src/resourcemanager.cpp
| : error: invalid digit "9" in octal constant
| src/util.h:11:59: note: in expansion of macro ‘POPPLER_VERSION_MINOR’
|11 | #define POPPLER_VERSION ((POPPLER_VERSION_MAJOR << 16) | 
(POPPLER_VERSION_MINOR << 8) | (POPPLER_VERSION_MICRO))
|   |   
^
| src/resourcemanager.cpp:121:5: note: in expansion of macro ‘POPPLER_VERSION’
|   121 | #if POPPLER_VERSION >= POPPLER_VERSION_CHECK(0, 18, 0)
|   | ^~~
| : error: invalid digit "9" in octal constant
| src/util.h:11:59: note: in expansion of macro ‘POPPLER_VERSION_MINOR’
|11 | #define POPPLER_VERSION ((POPPLER_VERSION_MAJOR << 16) | 
(POPPLER_VERSION_MINOR << 8) | (POPPLER_VERSION_MICRO))
|   |   
^
| src/resourcemanager.cpp:124:5: note: in expansion of macro ‘POPPLER_VERSION’
|   124 | #if POPPLER_VERSION >= POPPLER_VERSION_CHECK(0, 22, 0)
|   | ^~~
| : error: invalid digit "9" in octal constant
| src/util.h:11:59: note: in expansion of macro ‘POPPLER_VERSION_MINOR’
|11 | #define POPPLER_VERSION ((POPPLER_VERSION_MAJOR << 16) | 
(POPPLER_VERSION_MINOR << 8) | (POPPLER_VERSION_MICRO))
|   |   
^
| src/resourcemanager.cpp:127:5: note: in expansion of macro ‘POPPLER_VERSION’
|   127 | #if POPPLER_VERSION >= POPPLER_VERSION_CHECK(0, 24, 0)
|   | ^~~
| src/resourcemanager.cpp: In member function ‘QDomDocument* 
ResourceManager::get_toc() const’:
| src/resourcemanager.cpp:483:18: warning: ‘QDomDocument* 
Poppler::Document::toc() const’ is deprecated [-Wdeprecated-declarations]
|   483 |  return doc->toc();
|   |  ^
| In file included from src/resourcemanager.h:11,
|  from src/resourcemanager.cpp:10:
| /usr/include/poppler/qt5/poppler-qt5.h:1709:37: note: declared here
|  1709 | Q_DECL_DEPRECATED QDomDocument *toc() const;
|   | ^~~
| src/layout/layout.cpp: In member function ‘virtual void 
Layout::activate_link(int, float, float)’:
| src/layout/layout.cpp:349:12: warning: enumeration value ‘OCGState’ not 
handled in switch [-Wswitch]
|   349 | switch (l->linkType()) {
|   |^
| src/layout/layout.cpp:349:12: warning: enumeration value ‘Hide’ not handled 
in switch [-Wswitch]
| make[2]: *** [Makefile:635: resourcemanager.o] Error 1
| make[2]: *** Waiting for unfinished jobs
| make[2]: Leaving directory '/<>'
| dh_auto_build: error: make -j8 returned exit code 2
| make[1]: *** [debian/rules:13: override_dh_auto_build] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:7: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Also reproducible by reproducible builds in bullseye:
https://tests.reproducible-builds.org/debian/rbuild/bullseye/amd64/katarakt_0.2-2.rbuild.log.gz

Also seen by crossqa in unstable:
http://crossqa.debian.net/build/katarakt_0.2-2_armhf_20200925023420.log

Helmut
--- End 

Processed: affects 975142

[Debian Bug Tracking System]

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

> affects 975142 src:lambda-align2
Bug #975142 [gcc-10] internal compiler error: ‘verify_type’ failed
Added indication that 975142 affects src:lambda-align2
> thanks
Stopping processing here.

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

Bug#975344: libkrb5-3: ABI breakage in 1.18: krb5_rc_resolve_full missing

[Damyan Ivanov]

Package: libkrb5-3
Version: 1.18.2-1
Severity: serious
Justification: Policy 8.6.2

Hi,

libkrb5-3 version 1.18.2-1 breaks apache2 when the kerberos authentication 
module is enabled. The error message is:

 apache2: Syntax error on line 146 of /etc/apache2/apache2.conf: Syntax error 
 on line 1 of /etc/apache2/mods-enabled/auth_kerb.load: Cannot load 
 /usr/lib/apache2/modules/mod_auth_kerb.so into server: 
 /usr/lib/apache2/modules/mod_auth_kerb.so: undefined symbol: 
 krb5_rc_resolve_full, version krb5_3_MIT

The error is gone when libkrb5-3 (along with dependencies) is downgraded to 
1.17-10.

Listing symbols with nm confirms the missing symbol.

1.17-10:
 $ nm -D  /usr/lib/x86_64-linux-gnu/libkrb5.so.3   | grep krb5_rc_resolve_full
 0006a410 T krb5_rc_resolve_full@@krb5_3_MIT
 $

1.18.2-1:
 $ nm -D  /usr/lib/x86_64-linux-gnu/libkrb5.so.3   | grep krb5_rc_resolve_full
 $

I think this is the reason for the failing CI runs on ppc64el for squid¹ and 
bind9². The other architecture strangely don't fail -- probably because the 
test sets are different -- there is no 'apache2' in the passing logs.

 ¹ https://ci.debian.net/data/autopkgtest/testing/ppc64el/s/squid/8297228/log.gz
 ² https://ci.debian.net/data/autopkgtest/testing/ppc64el/b/bind9/8297196/log.gz

Removing a symbol deserves a soname bump, per Policy 8.6.2, thus the severity.

Looking at 88f4594e6a34c7b88bcd06ab06be2738113c226b in the packaging repository 
I see a lot of removed symbols.

krb5_rc_resolve_full disappears upstream with 
dcb853ac32779b173f39e19c0f24b0087de85771. I assume dependencies like 
libapache2-mod-auth-kerb will need to adapt to the changes.


Cheers,
Damyan

Bug#975334: xeus-python ftbfs

[Gordon Ball]

Thanks for reporting.

This is a problem with pybind11-json-dev, which embeds the python
include path that it is built with, but does not currently declare a
dependency on the appropriate libpython3 version. (Not that declaring it
would be completely sufficient either, since as an arch:all it wouldn't
get binNMU'd anyway).

I'll make a new upload of pybind11-json-dev then giveback this package.

Bug#975134: marked as done (wpewebkit: FTBFS: ../Source/WebCore/platform/network/ResourceResponseBase.cpp:440:6: error: type precision mismatch in switch statement)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 16:37:05 +
with message-id 
and subject line Bug#975134: fixed in wpewebkit 2.30.3-1
has caused the Debian Bug report #975134,
regarding wpewebkit: FTBFS: 
../Source/WebCore/platform/network/ResourceResponseBase.cpp:440:6: error: type 
precision mismatch in switch statement
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.)


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

Hi,

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

Relevant part (hopefully):
> ninja: build stopped: subcommand failed.
> dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v 
> returned exit code 1
> make: *** [debian/rules:68: binary] Error 25

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/wpewebkit_2.30.2-1_unstable.log

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

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

We believe that the bug you reported is fixed in the latest version of
wpewebkit, 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.
Alberto Garcia  (supplier of updated wpewebkit 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, 20 Nov 2020 16:59:13 +0100
Source: wpewebkit
Architecture: source
Version: 2.30.3-1
Distribution: unstable
Urgency: high
Maintainer: Debian WebKit Maintainers 

Changed-By: Alberto Garcia 
Closes: 975134
Changes:
 wpewebkit (2.30.3-1) unstable; urgency=high
 .
   * New upstream release (Closes: #975134).
Checksums-Sha1:
 4131a9db8c6de8153f39abe8306655014b2152a9 3208 wpewebkit_2.30.3-1.dsc
 2ed723f779513205449e0c5b7c080eb19d635aee 21104624 wpewebkit_2.30.3.orig.tar.xz
 e8dc69f158d3cc8f6e4396cbd731ec80871c571c 195 wpewebkit_2.30.3.orig.tar.xz.asc
 18d476a66b9867a6dbb93705583503ad86f2905d 39652 wpewebkit_2.30.3-1.debian.tar.xz
 ecc9ab405461bb1652f2af6587eb3e7d2638625d 13310 
wpewebkit_2.30.3-1_source.buildinfo
Checksums-Sha256:
 467397f715b592e1b09f63017227edd5be7bbc1fc11b8e7cb927fddbf7ba3325 3208 
wpewebkit_2.30.3-1.dsc
 f2dfc1a6279810353f601bb9bd0d8ef671b41b38352d679b93d01631c2bf7b4b 21104624 
wpewebkit_2.30.3.orig.tar.xz
 ae0cf2612b227548f5e70a23fc7574f2ec76fde78a9052227f8cf681da60432f 195 
wpewebkit_2.30.3.orig.tar.xz.asc
 9d588374344060236e28d297d2229b08eb466ea317e0ec8febb58b4db5006505 39652 
wpewebkit_2.30.3-1.debian.tar.xz
 685dc079d33584efe0857d074ecd808f18346e40ee7c5534f796cc007ecb2299 13310 
wpewebkit_2.30.3-1_source.buildinfo
Files:
 aecada0e4e998558a80f79eae5bc3f59 3208 libs optional wpewebkit_2.30.3-1.dsc
 75f6ef1819b182043a25b916272ebec6 21104624 libs optional 
wpewebkit_2.30.3.orig.tar.xz
 64987fafb74efbbf191e26ef9f34473d 195 libs optional 
wpewebkit_2.30.3.orig.tar.xz.asc
 5687b8db83aebf5637a6c3e865b888e1 39652 libs optional 
wpewebkit_2.30.3-1.debian.tar.xz
 abca982f9d6a8cc9f6cf174a80ec99d6 13310 libs optional 
wpewebkit_2.30.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYrwugQBKzlHMYFizAAyEYu0C2AIFAl+36RcACgkQAAyEYu0C
2AKuHg/+IFm8oQrZc7Ia47H67jddx3cFW+kDHkqOsSBY+bUVhFqc1an1TH4Nzn8O
k2ZRQOo6rTjHOu6/Az3XRktmduGQRgafte1W9Tczt5vt8c43yOFEam7dxNg7Pewj
rT0yGTknZcjlw1owX84o3PF6/l0FGZDNHU/ZupAEu4xMC0f/4Yreohs/5fzrYw3U
kcE5aSb0FLM6pcLOdeP1eFwCkwJiQdloPEXckYGl4j03qOfIu5zH5+/CSN3jirdm
6w8flum8niFUpwENSrPOvx7C6kP4a3PsHiOkHQ/S6BluA/9114TU15sh8hq71Z3K
pF3ALvCygndAQ3OXsFePas1uVNk5WwZbZfKsJrr8S4nVkdsO0vhvrILC/Sj+lais
x5HtyRkaCHlufPYHz+CtzinfxHYlK5wxtQdZzejnEEUTtcGcwGR9cvlXEOmMiZ4E

Bug#960650: marked as done (InspIRCd Security Advisories 2019-02 and 2020-01)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 15:54:11 +
with message-id 
and subject line Bug#960650: fixed in inspircd 3.8.0-1
has caused the Debian Bug report #960650,
regarding InspIRCd Security Advisories 2019-02 and 2020-01
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.)


-- 
960650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: inspircd
Version: 3.4.0-2

InspIRCd v3.6.0 was recently released with a security fix for a crash bug.

https://docs.inspircd.org/security/2020-01/

Please can you update your package to this version.

Thanks,

~ Sadie
--- End Message ---
--- Begin Message ---
Source: inspircd
Source-Version: 3.8.0-1
Done: Filippo Giunchedi 

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

Debian distribution maintenance software
pp.
Filippo Giunchedi  (supplier of updated inspircd 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, 20 Nov 2020 15:56:44 +0100
Source: inspircd
Architecture: source
Version: 3.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Filippo Giunchedi 
Changed-By: Filippo Giunchedi 
Closes: 951339 953259 960650
Changes:
 inspircd (3.8.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #960650)
   * List all wanted extras, and fail if their dependencies are missing.
   * Restore missing extras (Closes: #953259)
   * Point VCS control fields to salsa.d.o repo
   * Set myself as Maintainer
   * Link httpd module with http_parser (Closes: #951339)
Checksums-Sha1:
 05e78b7f9b9208baa58c451f4efb9bf000e0e2d9 2158 inspircd_3.8.0-1.dsc
 6ea1708084632175e56ba5bab2b7ca4b70eb4aea 849843 inspircd_3.8.0.orig.tar.gz
 1e903c57d18bb2174c58a57158da4342765a723d 13896 inspircd_3.8.0-1.debian.tar.xz
 d6d48220c543b6f6daddf1def7fecc54603d6a6c 7600 inspircd_3.8.0-1_amd64.buildinfo
Checksums-Sha256:
 8d54a5aed56ff9b1e4a991e0668d5f184d3c4723ad4c50f542f3041bd4005fce 2158 
inspircd_3.8.0-1.dsc
 2f847c6a091332faa7a647291f92ff3ed571b17967c85198d34c816c40e47e04 849843 
inspircd_3.8.0.orig.tar.gz
 8459e1892b6ba5a7df8372faeaaecf06eda73d432cc11e37cde2b1e9ef36a017 13896 
inspircd_3.8.0-1.debian.tar.xz
 3c4bb7a1ea8a5a4bf09c20ca1272a55d1103be17a987e55b7254540d30c9d794 7600 
inspircd_3.8.0-1_amd64.buildinfo
Files:
 641a175c8652ddd4ccca1d2695899c59 2158 net optional inspircd_3.8.0-1.dsc
 884f011df9df52b2aeb2ed9ad2f17026 849843 net optional inspircd_3.8.0.orig.tar.gz
 f6ccb08a9f21cadf2418bd16dcf2e6da 13896 net optional 
inspircd_3.8.0-1.debian.tar.xz
 1dc5478996feb8893b795fee50497d1e 7600 net optional 
inspircd_3.8.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEESpRSzEXGrZapQW7YaWZyoGTcEJQFAl+321ATHGZpbGlwcG9A
ZGViaWFuLm9yZwAKCRBpZnKgZNwQlFdnD/4iNSbqMfrVDZ0954M1GKkFCSl65eBT
P33spL3Dzu+e9KchDpuxyvbDV266u+5KBskmNEtc9tAw3qC4EwVZn5/p9w0s89Tr
EPsKuwGuJPBBbbC93GbnXPHFUznw9QjxuV7OBi6MRiZKAQN4IRr1mOcNBvCNWrZf
9XQGIPqFgioSrgvOviez35IEY5bQewJPFLdFPwMecfCmkacQi5a0DRI/R209ANZc
y44esoDSqB4e+UfnWNT2lSca/XuyLIkvAqiTZyLIxhH/KVLBJV7BW31Lh/p2vYga
S2veKWxwwCV0pRMT3iD77yxDoCPX8aLCkEQlIDPj0952SBXMZDh7jd9YVwI0FHw/
oEL1mHDSrSMB/ERjhsavuQS5dEIEpidO5MID5+aLJNb9kJP0ZYRB400inbqYFF+c
VpxpC73wUCeX8voMXObFb/QAqHhtuM7gK5ftJ0mPEmmQc0Kac0rShKAH4MScEYKa
iLnWdp+/A1vkBstwGVS+P5ez2OQfMwcYJLXg4wn6QvoA13V/bPp2yJgXv2BlNhJT
a5KZXWEgOV2VH7YMz/t0zEpO6ZqRyD1n46PC4ZXRCAwZklbfM9AjKkOWFnTTRlGG
ZT4Sq34ISzDtlLG7aOF1Nj539YF8Bf+zgo5felZQsPn89grOQEoA46XQMpBsDx1K
tomCu6nySQvuVQ==
=wWQx
-END PGP SIGNATURE End Message ---

Bug#975334: xeus-python: FTBFS with Python 3.9 as default

[Graham Inggs]

Source: xeus-python
Version: 0.8.6-2
Severity: serious
Tags: ftbfs sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: python3.9

Hi Maintainer

Since the upload of python3-defaults with Python 3.9 as the default
version, xeus-python FTBFS.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://buildd.debian.org/status/package.php?p=xeus-python


CMake Error in CMakeLists.txt:
  Imported target "pybind11_json" includes non-existent path
"/usr/include/python3.8"
  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:
  * The path was deleted, renamed, or moved to another location.
  * An install or uninstall procedure did not complete successfully.
  * The installation package was faulty and references files it does not
  provide.

Processed: Re: lambda-align2: FTBFS: lambda.cpp:100:1: error: type variant with ‘TYPE_ALIAS_SET_KNOWN_P’

[Debian Bug Tracking System]

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

> reassign 975142 gcc-10
Bug #975142 [src:lambda-align2] lambda-align2: FTBFS: lambda.cpp:100:1: error: 
type variant with ‘TYPE_ALIAS_SET_KNOWN_P’
Bug reassigned from package 'src:lambda-align2' to 'gcc-10'.
No longer marked as found in versions lambda-align2/2.0.0-7.
Ignoring request to alter fixed versions of bug #975142 to the same values 
previously set
> retitle 975142 internal compiler error: ‘verify_type’ failed
Bug #975142 [gcc-10] lambda-align2: FTBFS: lambda.cpp:100:1: error: type 
variant with ‘TYPE_ALIAS_SET_KNOWN_P’
Changed Bug title to 'internal compiler error: ‘verify_type’ failed' from 
'lambda-align2: FTBFS: lambda.cpp:100:1: error: type variant with 
‘TYPE_ALIAS_SET_KNOWN_P’'.
> stop
Stopping processing here.

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

Bug#975142: lambda-align2: FTBFS: lambda.cpp:100:1: error: type variant with ‘TYPE_ALIAS_SET_KNOWN_P’

[Michael R. Crusoe]

reassign 975142 gcc-10

retitle 975142 internal compiler error: ‘verify_type’ failed

stop

On Thu, 19 Nov 2020 10:35:39 +0100 Lucas Nussbaum  wrote:

> Hi,
>
> During a rebuild of all packages in sid, your package failed to build

> on amd64.

Thanks. The author replies:


> An internal compiler error always means that something is broken in
the compiler and that needs to be reported upstream.


-- 

Michael R. Crusoe




signature.asc
Description: OpenPGP digital signature

Bug#975320: Processed: Re: Bug#975284: calibre: crashes on start

[Matthias Klose]

On 11/20/20 3:32 PM, Matthias Klose wrote:
> Control: reassign -1 calibre
> Control: severity -1 serious
> 
> On 11/20/20 1:27 PM, Debian Bug Tracking System wrote:
>> Processing commands for cont...@bugs.debian.org:
>>
>>> clone 975284 -1
>> Bug #975284 [calibre] calibre: crashes on start
>> Bug 975284 cloned as bug 975320
>>> reassign -1 python3
>> Bug #975320 [calibre] calibre: crashes on start
>> Bug reassigned from package 'calibre' to 'python3'.
>> No longer marked as found in versions calibre/5.5.0+dfsg-1.
>> Ignoring request to alter fixed versions of bug #975320 to the same values 
>> previously set
>>> retitle -1 breaks unrelated packages
>> Bug #975320 [python3] calibre: crashes on start
>> Changed Bug title to 'breaks unrelated packages' from 'calibre: crashes on 
>> start'.
>>> thanks
>> Stopping processing here.
>>
>> Please contact me if you need assistance.
>>
> 
> packaging bug. calibre-bin is rebuilt for 3.9, but you are still calling 3.8.
> You really should use dh_python3 and ${python3:Substvars}.

${python3:Depends} even

Processed: Re: Processed: Re: Bug#975284: calibre: crashes on start

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 calibre
Bug #975320 [python3] breaks unrelated packages
Bug reassigned from package 'python3' to 'calibre'.
Ignoring request to alter found versions of bug #975320 to the same values 
previously set
Ignoring request to alter fixed versions of bug #975320 to the same values 
previously set
> severity -1 serious
Bug #975320 [calibre] breaks unrelated packages
Severity set to 'serious' from 'grave'

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

Bug#975320: Processed: Re: Bug#975284: calibre: crashes on start

[Matthias Klose]

Control: reassign -1 calibre
Control: severity -1 serious

On 11/20/20 1:27 PM, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
>> clone 975284 -1
> Bug #975284 [calibre] calibre: crashes on start
> Bug 975284 cloned as bug 975320
>> reassign -1 python3
> Bug #975320 [calibre] calibre: crashes on start
> Bug reassigned from package 'calibre' to 'python3'.
> No longer marked as found in versions calibre/5.5.0+dfsg-1.
> Ignoring request to alter fixed versions of bug #975320 to the same values 
> previously set
>> retitle -1 breaks unrelated packages
> Bug #975320 [python3] calibre: crashes on start
> Changed Bug title to 'breaks unrelated packages' from 'calibre: crashes on 
> start'.
>> thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.
> 

packaging bug. calibre-bin is rebuilt for 3.9, but you are still calling 3.8.
You really should use dh_python3 and ${python3:Substvars}.

Bug#867505: closing 867505

[Barak A. Pearlmutter]

close 867505 0.2.8-1
thanks

Processed: closing 867505

[Debian Bug Tracking System]

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

> close 867505 0.2.8-1
Bug #867505 [src:mps-youtube] mps-youtube FTBFS with python 3.6 as supported 
version
Marked as fixed in versions mps-youtube/0.2.8-1.
Bug #867505 [src:mps-youtube] mps-youtube FTBFS with python 3.6 as supported 
version
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#975284: calibre: crashes on start

[gregor herrmann]

On Fri, 20 Nov 2020 21:22:00 +0900, Norbert Preining wrote:

> > ImportError: /usr/lib/calibre/calibre/plugins/progress_indicator.so:
> > undefined symbol: _Py_FatalErrorFunc

JFTR, this looks similar for pure commandline usage:

% calibre catalog
Traceback (most recent call last):
  File "/usr/bin/calibre", line 20, in 
sys.exit(calibre())
  File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre
main(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 509, in main
app, opts, args = init_qt(args)
  File "/usr/lib/calibre/calibre/gui2/main.py", line 122, in init_qt
app = Application(args, override_program_name=override, 
windows_app_uid=MAIN_APP_UID)
  File "/usr/lib/calibre/calibre/gui2/__init__.py", line 885, in __init__
from calibre_extensions import progress_indicator
ImportError: /usr/lib/calibre/calibre/plugins/progress_indicator.so: undefined 
symbol: _Py_FatalErrorFunc


Or from a script, which adds more parameters to the `calibre catalog'
call:

Traceback (most recent call last):
  File "/usr/bin/calibredb", line 19, in 
from calibre.db.cli.main import main
  File "/usr/lib/calibre/calibre/db/cli/main.py", line 12, in 
from calibre.db.legacy import LibraryDatabase
  File "/usr/lib/calibre/calibre/db/legacy.py", line 18, in 
from calibre.db.backend import DB, set_global_state as 
backend_set_global_state
  File "/usr/lib/calibre/calibre/db/backend.py", line 36, in 
from calibre.utils.img import save_cover_data_to
  File "/usr/lib/calibre/calibre/utils/img.py", line 26, in 
from calibre_extensions import imageops
ImportError: /usr/lib/calibre/calibre/plugins/imageops.so: undefined symbol: 
_Py_FatalErrorFunc


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Red Hot Chili Peppers: This Velvet Glove


signature.asc
Description: Digital Signature

Bug#975324: rclone: CVE-2020-28924: generating weak passwords

[Salvatore Bonaccorso]

Source: rclone
Version: 1.53.1-2
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/rclone/rclone/issues/4783
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for rclone.

CVE-2020-28924[0]:
| An issue was discovered in Rclone before 1.53.3. Due to the use of a
| weak random number generator, the password generator has been
| producing weak passwords with much less entropy than advertised. The
| suggested passwords depend deterministically on the time the second
| rclone was started. This limits the entropy of the passwords
| enormously. These passwords are often used in the crypt backend for
| encryption of data. It would be possible to make a dictionary of all
| possible passwords with about 38 million entries per password length.
| This would make decryption of secret material possible with a
| plausible amount of effort. NOTE: all passwords generated by affected
| versions should be changed.


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-28924
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28924
[1] https://github.com/rclone/rclone/issues/4783

Regards,
Salvatore

Processed: severity of 974637 is normal

[Debian Bug Tracking System]

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

> severity 974637 normal
Bug #974637 [ftp.debian.org] RM: biosig4c++ -- ROM; replaced by biosig
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#919348: xfce4-screensaver in Debian Bullseye

[Marek Straka]

There is release 0.1.11 
https://gitlab.xfce.org/apps/xfce4-screensaver/-/blob/xfce4-screensaver-0.1.11/NEWS

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Alois Wohlschlager]

Am Freitag, den 20.11.2020, 09:13 + schrieb Niko Tyni:
> I don't think this is related to the recent perl 5.30 -> 5.32
> transition.
> The report is about a buster -> bullseye upgrade, and perl in
> bullseye
> was still at 5.30 at the time.
> 
> In any case, the report says perl (presumably perl-base as well) was
> still at the buster version when the breakage happened, so it didn't
> have the libcrypt1 dependency.

This is indeed the case. perl-base was only upgraded to the bullseye
version after I manually fixed the breakage. (Indeed, when I wrote
"Perl" I actually meant "perl-base", but perl itself was also at the
buster version FWIW.)

> FWIW the breakage can be reproduced just by manually unpacking the
> new
> libc6 on a buster system.
> 
> I don't know why it hasn't been encountered earlier.

I found out by now that the problem actually has been encountered
earlier(#946599, where it broke libc's maintainer scripts). In my case,
it broke the check-support-status hook providd by debian-security-
support. (I'm not sure whether it's such a great idea for dpkg to run
hooks when dependencies are broken, but that's what was happening on my
system.)

> > 
> Yeah, I missed the libcrypt1 -> libc6 dependency. That prevents this
> option. (I wonder if the circular dependency is a factor in apt
> choosing
> the upgrade order that results in this breakage.)

I'm not sure what's going on here, as libcrypt1's libc6 Depends should
be satisfied by the buster version. So it seems to me like installing
libcrypt1 before upgrading libc6 should be strictly better than doing
it the other way round, even purely in terms of satisfaction of
dependencies.

Maybe it's worth investigating why apt decides to proceed the "wrong"
way anyway, should I try setting up a VM to reproduce the problem?

> > > Another option might be to have the new libc6 Conflict with old
> > > versions
> > > of Essential:yes packages that need libcrypt1, forcing those
> > > Essential:yes
> > > packages to get upgraded first. A quick check based on libcrypt1
> > > reverse
> > > dependencies in sid shows perl-base, login and util-linux. I'm
> > > not sure
> > > if this list is exhaustive, though.

Having libc6 Conflict with one of those packages should be enough,
right?

--
Alois



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

Processed: Re: Bug#975284: calibre: crashes on start

[Debian Bug Tracking System]

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

> clone 975284 -1
Bug #975284 [calibre] calibre: crashes on start
Bug 975284 cloned as bug 975320
> reassign -1 python3
Bug #975320 [calibre] calibre: crashes on start
Bug reassigned from package 'calibre' to 'python3'.
No longer marked as found in versions calibre/5.5.0+dfsg-1.
Ignoring request to alter fixed versions of bug #975320 to the same values 
previously set
> retitle -1 breaks unrelated packages
Bug #975320 [python3] calibre: crashes on start
Changed Bug title to 'breaks unrelated packages' from 'calibre: crashes on 
start'.
> thanks
Stopping processing here.

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

Bug#975284: calibre: crashes on start

[Norbert Preining]

clone 975284 -1
reassign -1 python3
retitle -1 breaks unrelated packages
thanks

Hi

On Fri, 20 Nov 2020, Hor Jiun Shyong wrote:
> After upgrading to version 5.5.0+dfsg-1,  calibre crashes on start.

ACtually, this is independent of the upgrade, but an effect of some
python3 upgrade, I guess the 3.8 to 3.9 transition, as 5.5.0 was working
before.

Cloning and reassigning to Python, that should not happen or some
library transition with rebuild should be done.

Python maintainers, please advise on what steps are necessary to fix the
breakage. Thanks.

> ImportError: /usr/lib/calibre/calibre/plugins/progress_indicator.so:
> undefined symbol: _Py_FatalErrorFunc

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: forwarded GCC issue

[Debian Bug Tracking System]

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

> forwarded 975219 https://gcc.gnu.org/PR97927
Bug #975219 [src:elkcode] elkcode: FTBFS: internal compiler error: in 
lookup_field_for_decl, at tree-nested.c:288
Set Bug forwarded-to-address to 'https://gcc.gnu.org/PR97927'.
> thanks
Stopping processing here.

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

Bug#975312: aravis: Please reupload source-only

[Bastian Germann]

Source: aravis
Severity: serious
Version: aravis/0.8.1-1

aravis 0.8.1-1 does not migrate to bullseye, because it was uploaded
with all and amd64 binaries. While the amd64 binary was replaced by a
BinNMU, the all binary sticks around. Please reupload a source-only version.

Bug#975202: (no subject)

[Jerome Robert]

This is because pikepdf < 1.19.0 is incompatible with bybind11 2.6. This was 
fixed in 
https://github.com/pikepdf/pikepdf/commit/5394b7855eb87f637316432b2b597294adcb974e

Bug#975239: marked as done (python-pynvim: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 09:49:56 +
with message-id 
and subject line Bug#975237: fixed in python-pynvim 0.4.2-1
has caused the Debian Bug report #975237,
regarding python-pynvim: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
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.)


-- 
975237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pynvim
Version: 0.4.1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> collecting ... collected 68 items
> 
> test/test_buffer.py::test_repr PASSED[  
> 1%]
> test/test_buffer.py::test_get_length PASSED  [  
> 2%]
> test/test_buffer.py::test_get_set_del_line PASSED[  
> 4%]
> test/test_buffer.py::test_get_set_del_slice PASSED   [  
> 5%]
> test/test_buffer.py::test_vars PASSED[  
> 7%]
> test/test_buffer.py::test_api PASSED [  
> 8%]
> test/test_buffer.py::test_options PASSED [ 
> 10%]
> test/test_buffer.py::test_number PASSED  [ 
> 11%]
> test/test_buffer.py::test_name PASSED[ 
> 13%]
> test/test_buffer.py::test_valid PASSED   [ 
> 14%]
> test/test_buffer.py::test_append PASSED  [ 
> 16%]
> test/test_buffer.py::test_mark PASSED[ 
> 17%]
> test/test_buffer.py::test_invalid_utf8 
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   http://qa-logs.debian.net/2020/11/19/python-pynvim_0.4.1-2_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-pynvim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 20 Nov 2020 10:18:31 +0100
Source: python-pynvim
Architecture: source
Version: 0.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Thomas Goirand 
Closes: 975237
Changes:
 python-pynvim (0.4.2-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Thomas Goirand ]
   * Team upload.
   * New upstream release:
 - Works with python3-msgpack >= 1.x (Closes: #975237).
   * Add a debian/salsa-ci.yml.
Checksums-Sha1:
 679313adfee80329b6c6fd8949c537e6acffebc6 2314 python-pynvim_0.4.2-1.dsc
 27066c7d2db969523461090bc3e002e19fd777e9 42234 python-pynvim_0.4.2.orig.tar.gz
 870e7abd2a8a531335730fd82798889b713a5fbc 4256 
python-pynvim_0.4.2-1.debian.tar.xz
 3b329d19bac4faa9063877c82914ddfc2fb94eb8 7611 
python-pynvim_0.4.2-1_amd64.buildinfo
Checksums-Sha256:
 bad78c1e8f76b0e5d903788ccbfa40b4783b2d20379a04f006bfa09c4faf67cf 2314 
python-pynvim_0.4.2-1.dsc
 6bc6204d465de5888a0c5e3e783fe01988b032e22ae87875912280bef0e40f8f 42234 
python-pynvim_0.4.2.orig.tar.gz
 d5e373b846c0ccdf7a426230070bd97105afcec588049f9d4d924315baefafc1 4256 
python-pynvim_0.4.2-1.debian.tar.xz
 

Bug#975237: marked as done (python-pynvim update for new python-msgpack)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 09:49:56 +
with message-id 
and subject line Bug#975237: fixed in python-pynvim 0.4.2-1
has caused the Debian Bug report #975237,
regarding python-pynvim update for new python-msgpack
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.)


-- 
975237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-msgpack, python-pynvim
Control: found -1 python-msgpack/1.0.0-4
Control: found -1 python-pynvim/0.4.1-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update timeout

Dear maintainer(s),

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

   passfail
python-msgpack from testing1.0.0-4
python-pynvim  from testing0.4.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test times
out after 2:47 hours (instead of the regular 1 minute run).

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

On top of that, due to the additional stress on our infrastructure, I'll
also block the python-pynvim autopkgtest until this bug is marked fixed
(or when I'm contacted otherwise).

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=python-msgpack

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pynvim/8246311/log.gz

autopkgtest [06:11:51]: test python3-pynvim: [---
/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py:9:
DeprecationWarning: the imp module is deprecated in favour of importlib;
see the module's documentation for alternative uses
  import imp
= test session starts
==
platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
-- /usr/bin/python3.9
cachedir: .pytest_cache
rootdir: /tmp/autopkgtest-lxc.jlon07vw/downtmp/autopkgtest_tmp
collecting ... collected 68 items

test/test_buffer.py::test_repr PASSED
[  1%]
test/test_buffer.py::test_get_length PASSED
[  2%]
test/test_buffer.py::test_get_set_del_line PASSED
[  4%]
test/test_buffer.py::test_get_set_del_slice PASSED
[  5%]
test/test_buffer.py::test_vars PASSED
[  7%]
test/test_buffer.py::test_api PASSED
[  8%]
test/test_buffer.py::test_options PASSED
[ 10%]
test/test_buffer.py::test_number PASSED
[ 11%]
test/test_buffer.py::test_name PASSED
[ 13%]
test/test_buffer.py::test_valid PASSED
[ 14%]
test/test_buffer.py::test_append PASSED
[ 16%]
test/test_buffer.py::test_mark PASSED
[ 17%]
test/test_buffer.py::test_invalid_utf8 autopkgtest [08:58:31]: ERROR:
timed out on command "su -s /bin/bash debci -c set -e; export USER=`id
-nu`; . /etc/profile >/dev/null 2>&1 || true;  . ~/.profile >/dev/null
2>&1 || true;
buildtree="/tmp/autopkgtest-lxc.jlon07vw/downtmp/build.uXp/src"; mkdir
-p -m 1777 --
"/tmp/autopkgtest-lxc.jlon07vw/downtmp/python3-pynvim-artifacts"; export
AUTOPKGTEST_ARTIFACTS="/tmp/autopkgtest-lxc.jlon07vw/downtmp/python3-pynvim-artifacts";
export ADT_ARTIFACTS="$AUTOPKGTEST_ARTIFACTS"; mkdir -p -m 755
"/tmp/autopkgtest-lxc.jlon07vw/downtmp/autopkgtest_tmp"; export
AUTOPKGTEST_TMP="/tmp/autopkgtest-lxc.jlon07vw/downtmp/autopkgtest_tmp";
export ADTTMP="$AUTOPKGTEST_TMP"; export DEBIAN_FRONTEND=noninteractive;
export LANG=C.UTF-8; export DEB_BUILD_OPTIONS=parallel=2; unset LANGUAGE
LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE   LC_MONETARY LC_MESSAGES
LC_PAPER LC_NAME LC_ADDRESS   LC_TELEPHONE LC_MEASUREMENT
LC_IDENTIFICATION LC_ALL;rm -f /tmp/autopkgtest_script_pid; set -C; echo
$$ > /tmp/autopkgtest_script_pid; set +C; trap "rm -f
/tmp/autopkgtest_script_pid" EXIT INT QUIT PIPE; cd "$buildtree"; chmod
+x
/tmp/autopkgtest-lxc.jlon07vw/downtmp/build.uXp/src/debian/tests/python3-pynvim;
touch /tmp/autopkgtest-lxc.jlon07vw/downtmp/python3-pynvim-stdout
/tmp/autopkgtest-lxc.jlon07vw/downtmp/python3-pynvim-stderr;
/tmp/autopkgtest-lxc.jlon07vw/downtmp/build.uXp/src/debian/tests/python3-pynvim
2> >(tee 

Processed: Re: Don't upload scilab

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #971902 [src:scilab] FTBFS against libmatio 1.5.18
Added tag(s) pending.

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

Bug#971902: Don't upload scilab

[Sébastien Villemot]

Control: tags -1 + pending

Le vendredi 20 novembre 2020 à 10:46 +0100, Julien Puydt a écrit :

> please push your commit but don't upload :
> 
> - I'll report upstream and forward your patch ;
> 
> - I'll take the occasion to do some little things on the package, so
> I'll upload when I'll be done (probably before next monday).

Ok, I’ve pushed the patch.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org



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

Bug#971902: Don't upload scilab

[Julien Puydt]

Hi,

please push your commit but don't upload :

- I'll report upstream and forward your patch ;

- I'll take the occasion to do some little things on the package, so
I'll upload when I'll be done (probably before next monday).

Thanks!

JP

Bug#959621: marked as done (python-kubernetes: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 09:40:52 +
with message-id 
and subject line Bug#959621: fixed in python-kubernetes 12.0.1-1
has caused the Debian Bug report #959621,
regarding python-kubernetes: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
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.)


-- 
959621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-kubernetes
Version: 7.0.0~a1-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> base64.decodestring(self._data.encode()))
> 
> .pybuild/cpython3_3.8_kubernetes/build/kubernetes/config/kube_config_test.py::TestKubeConfigLoader::test_list_kube_config_contexts
> .pybuild/cpython3_3.8_kubernetes/build/kubernetes/config/kube_config_test.py::TestKubeConfigLoader::test_load_kube_config
> .pybuild/cpython3_3.8_kubernetes/build/kubernetes/config/kube_config_test.py::TestKubeConfigLoader::test_new_client_from_config
>   
> /<>/.pybuild/cpython3_3.8_kubernetes/build/kubernetes/config/kube_config.py:434:
>  YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as 
> the default Loader is unsafe. Please read https://msg.pyyaml.org/load for 
> full details.
> config_dict=yaml.load(f),
> 
> .pybuild/cpython3_3.8_kubernetes/build/kubernetes/config/kube_config_test.py::TestKubeConfigLoader::test_oidc_with_refresh
> .pybuild/cpython3_3.8_kubernetes/build/kubernetes/config/kube_config_test.py::TestKubeConfigLoader::test_oidc_with_refresh_nocert
>   /usr/lib/python3/dist-packages/oauthlib/oauth2/rfc6749/clients/base.py:479: 
> DeprecationWarning: Please switch to the public method 
> populate_token_attributes.
> warnings.warn("Please switch to the public method "
> 
> -- Docs: https://docs.pytest.org/en/latest/warnings.html
>  61 passed, 37 warnings in 1.29 seconds 
> 
> E: Build killed with signal TERM after 150 minutes of inactivity

The full build log is available from:
   
http://qa-logs.debian.net/2020/05/01/python-kubernetes_7.0.0~a1-2_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-kubernetes 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, 20 Nov 2020 09:16:10 +0100
Source: python-kubernetes
Architecture: source
Version: 12.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Thomas Goirand 
Closes: 954381 959621 973072
Changes:
 python-kubernetes (12.0.1-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
   * d/control: Update Maintainer field with new Debian Python Team
 contact address.
   * d/control: Update Vcs-* fields with new Debian Python Team Salsa
 layout.
 .
   [ Debian Janitor ]
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
   * Update standards version to 4.5.0, no changes needed.
 .
   [ Thomas Goirand ]
   * New upstream release (Closes: #954381).
 - Fixes FTBFS (Closes: #959621, #973072).
   * Use git to generate upstream tarball, as the PyPi module doesn't include
 the test folder. Using the gen-orig-xz in debian/rules, as using the
 repack function of debian/watch doesn't make sense (why downloading a
 tarball that would 

Bug#973239: marked as done (python-fixtures: FTBFS: ValueError: not enough values to unpack (expected 2, got 1))

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 10:36:11 +0100
with message-id <7ae25ff6-4366-cc3c-267c-258240f4b...@debian.org>
and subject line Fixed
has caused the Debian Bug report #973239,
regarding python-fixtures: FTBFS: ValueError: not enough values to unpack 
(expected 2, got 1)
to be marked as done.

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

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


-- 
973239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fixtures
Version: 3.0.0-3
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):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> set -x ; set -e ; for i in 3.9 3.8 ; do \
>   python$i -m testtools.run fixtures.test_suite ; \
> done
> + set -e
> + python3.9 -m testtools.run fixtures.test_suite
> /usr/lib/python3.9/runpy.py:127: RuntimeWarning: 'testtools.run' found in 
> sys.modules after import of package 'testtools', but prior to execution of 
> 'testtools.run'; this may result in unpredictable behaviour
>   warn(RuntimeWarning(msg))
> Tests running...
> ==
> ERROR: 
> fixtures.tests._fixtures.test_monkeypatch.TestMonkeyPatch.test_patch_classmethod_with_boundmethod
> --
> Traceback (most recent call last):
>   File "/<>/fixtures/tests/_fixtures/test_monkeypatch.py", line 
> 223, in test_patch_classmethod_with_boundmethod
> slf, cls = C.foo_cls()
> TypeError: bar_two_args() missing 1 required positional argument: 'arg'
> ==
> ERROR: 
> fixtures.tests._fixtures.test_monkeypatch.TestMonkeyPatch.test_patch_classmethod_with_classmethod
> --
> Traceback (most recent call last):
>   File "/<>/fixtures/tests/_fixtures/test_monkeypatch.py", line 
> 191, in test_patch_classmethod_with_classmethod
> cls, target_class = C.foo_cls()
> ValueError: not enough values to unpack (expected 2, got 1)
> 
> Ran 128 tests in 2.017s
> FAILED (failures=2)
> make[1]: *** [debian/rules:21: override_dh_auto_test] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/python-fixtures_3.0.0-3_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Fixed, somehow this bug didn't close itself after upload.--- End Message ---

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Niko Tyni]

On Fri, Nov 20, 2020 at 09:30:23AM +0100, Aurelien Jarno wrote:
> On 2020-11-16 16:39, Niko Tyni wrote:
> > On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote:
> > > On 2020-11-13 18:23 +0100, Niels Thykier wrote:
> > > 
> > > > Control: reassign -1 perl-base
> > > > Control: affects -1 upgrade-reports
> > > > Control: severity -1 grave
> > > >
> > > > Hi Perl team,
> > > >
> > > > I have reassigned this bug to perl because perl-base being essential
> > > > must remain functional during an upgrade and AFAICT perl-base fails in
> > > > this case here.
> > > >
> > > > If it is a direct linkage, then you might be needing a Pre-Depends.  If
> > > > it is an indirect linkage then I am not sure how to fix it. :-/
> > > 
> > > I don't think perl-base is doing anything wrong here, it already uses
> > > Pre-Depends.  AFAICS the problem is that libcrypt.so.1 can temporarily
> > > go missing if libc6 2.31-4 is unpacked before libcrypt1, breaking the
> > > assumption that binaries from essential packages are always usable.
> 
> I don't understand what happened there. Sure there has been the perl
> transition, but the fact that perl depends on libcrypt1, it is the case
> for more than 6 months.

I don't think this is related to the recent perl 5.30 -> 5.32 transition.
The report is about a buster -> bullseye upgrade, and perl in bullseye
was still at 5.30 at the time.

In any case, the report says perl (presumably perl-base as well) was
still at the buster version when the breakage happened, so it didn't
have the libcrypt1 dependency.

FWIW the breakage can be reproduced just by manually unpacking the new
libc6 on a buster system.

I don't know why it hasn't been encountered earlier.

> > As to the fix, I suspect we need a pre-dependency from libc6 to libcrypt1
> > for one release cycle, so that libc6 cannot be unpacked before libcrypt1
> > is fully installed.
> 
> This has been tried, that works for upgrade, but then apt refuses to
> allow new installation of libc6+libxcrypt1, which makes it impossible to
> install foreign-arch versions on an existing system.

Yeah, I missed the libcrypt1 -> libc6 dependency. That prevents this
option. (I wonder if the circular dependency is a factor in apt choosing
the upgrade order that results in this breakage.)

> > Another option might be to have the new libc6 Conflict with old versions
> > of Essential:yes packages that need libcrypt1, forcing those Essential:yes
> > packages to get upgraded first. A quick check based on libcrypt1 reverse
> > dependencies in sid shows perl-base, login and util-linux. I'm not sure
> > if this list is exhaustive, though.
> 
> This is something we can try indeed.

It looks like perl-base 5.30.0-10 was the first version to acquire the
pre-dependency on libcrypt1.
-- 
Niko

Bug#974873: marked as done (postgresql-rum: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Fri, 20 Nov 2020 09:44:52 +0100
with message-id <20201120084452.ga783...@msg.df7cb.de>
and subject line Re: Bug#974873: postgresql-rum: autopkgtest failure
has caused the Debian Bug report #974873,
regarding postgresql-rum: autopkgtest failure
to be marked as done.

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

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


-- 
974873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgresql-rum
Version: 1.3.7-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

postgresql-rum is currently unable to migrate due to autopkgtest
regressions on arm64 and ppc64el:
| --- Test multicolumn index
| -RESET enable_indexscan;
| -RESET enable_indexonlyscan;
| -RESET enable_bitmapscan;
| -SET enable_seqscan = off;
| -DROP INDEX tstsh_idx;
| -CREATE INDEX tstsh_id_idx ON tsts USING rum (t rum_tsvector_addon_ops, id, d)
| - WITH (attach = 'd', to = 't');
| -EXPLAIN (costs off)
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND id = 1::int ORDER BY d <=> 
'2016-05-16 14:21:25' LIMIT 5;
| -QUERY PLAN   
  
| 

| - Limit
| -   ->  Index Scan using tstsh_id_idx on tsts
| - Index Cond: ((t @@ '''wr'' & ''qh'''::tsquery) AND (id = 1))
| - Order By: (d <=> 'Mon May 16 14:21:25 2016'::timestamp without time 
zone)
| -(4 rows)
| -
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND id = 1::int ORDER BY d <=> 
'2016-05-16 14:21:25' LIMIT 5;
| -ERROR:  doesn't support order by over pass-by-reference column
| -EXPLAIN (costs off)
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND id = 355::int ORDER BY d <=> 
'2016-05-16 14:21:25' LIMIT 5;
| -QUERY PLAN   
  
| 

| - Limit
| -   ->  Index Scan using tstsh_id_idx on tsts
| - Index Cond: ((t @@ '''wr'' & ''qh'''::tsquery) AND (id = 355))
| - Order By: (d <=> 'Mon May 16 14:21:25 2016'::timestamp without time 
zone)
| -(4 rows)
| -
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND id = 355::int ORDER BY d <=> 
'2016-05-16 14:21:25' LIMIT 5;
| -ERROR:  doesn't support order by over pass-by-reference column
| -EXPLAIN (costs off)
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND d = '2016-05-11 
11:21:22.326724'::timestamp ORDER BY d <=> '2016-05-16 14:21:25' LIMIT 5;
| -QUERY PLAN   
 
| 
---
| - Limit
| -   ->  Index Scan using tstsh_id_idx on tsts
| - Index Cond: ((t @@ '''wr'' & ''qh'''::tsquery) AND (d = 'Wed May 11 
11:21:22.326724 2016'::timestamp without time zone))
| - Order By: (d <=> 'Mon May 16 14:21:25 2016'::timestamp without time 
zone)
| -(4 rows)
| -
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND d = '2016-05-11 
11:21:22.326724'::timestamp ORDER BY d <=> '2016-05-16 14:21:25' LIMIT 5;
| -ERROR:  doesn't support order by over pass-by-reference column
| -EXPLAIN (costs off)
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND d = '2000-05-01'::timestamp 
ORDER BY d <=> '2016-05-16 14:21:25' LIMIT 5;
| -QUERY PLAN   
  
| 

| - Limit
| -   ->  Index Scan using tstsh_id_idx on tsts
| - Index Cond: ((t @@ '''wr'' & ''qh'''::tsquery) AND (d = 'Mon May 01 
00:00:00 2000'::timestamp without time zone))
| - Order By: (d <=> 'Mon May 16 14:21:25 2016'::timestamp without time 
zone)
| -(4 rows)
| -
| -SELECT id, d FROM tsts WHERE t @@ 'wr' AND d = '2000-05-01'::timestamp 
ORDER BY d <=> '2016-05-16 14:21:25' LIMIT 5;
| -ERROR:  doesn't support order by over pass-by-reference column
| +FATAL:  failed to load summary 
"/usr/lib/postgresql/13/lib/bitcode/rum.index.bc": Invalid summary version 9. 
Version should be in the range [1-8].
| +server closed the connection unexpectedly
| + This probably means the server terminated abnormally
| + before or while processing the request.
| +connection to server was lost

https://ci.debian.net/data/autopkgtest/testing/arm64/p/postgresql-rum/8183353/log.gz

And also 

Bug#974552: upgrade-reports: libc6/libcrypt split breaks perl during buster->bullseye upgrade

[Aurelien Jarno]

Hi,

On 2020-11-16 16:39, Niko Tyni wrote:
> On Fri, Nov 13, 2020 at 08:48:19PM +0100, Sven Joachim wrote:
> > On 2020-11-13 18:23 +0100, Niels Thykier wrote:
> > 
> > > Control: reassign -1 perl-base
> > > Control: affects -1 upgrade-reports
> > > Control: severity -1 grave
> > >
> > > Hi Perl team,
> > >
> > > I have reassigned this bug to perl because perl-base being essential
> > > must remain functional during an upgrade and AFAICT perl-base fails in
> > > this case here.
> > >
> > > If it is a direct linkage, then you might be needing a Pre-Depends.  If
> > > it is an indirect linkage then I am not sure how to fix it. :-/
> > 
> > I don't think perl-base is doing anything wrong here, it already uses
> > Pre-Depends.  AFAICS the problem is that libcrypt.so.1 can temporarily
> > go missing if libc6 2.31-4 is unpacked before libcrypt1, breaking the
> > assumption that binaries from essential packages are always usable.

I don't understand what happened there. Sure there has been the perl
transition, but the fact that perl depends on libcrypt1, it is the case
for more than 6 months.

> Indeed. As perl-base isn't upgraded yet at that point, there's nothing
> we can do on that side.
> 
> Apparently the new libc6 is still considered to satisfy the old perl-base
> pre-dependency even when it (libc6) is only unpacked and its dependencies
> are not yet satisfied. This seems similar to this paragraph from Debian
> policy, section 7.2:
> 
> When a package declaring a pre-dependency is about to be unpacked
> the pre-dependency can be satisfied if the depended-on package
> is either fully configured, or even if the depended-on package(s)
> are only in the “Unpacked” or the “Half-Configured” state,
> provided that they have been configured correctly at some point
> in the past (and not removed or partially removed since). In this
> case, both the previously-configured and currently “Unpacked”
> or “Half-Configured” versions must satisfy any version clause
> in the Pre-Depends field.
> 
> The libc6 package has been configured correctly in the past, when
> it still contained libcrypt1.
> 
> As to the fix, I suspect we need a pre-dependency from libc6 to libcrypt1
> for one release cycle, so that libc6 cannot be unpacked before libcrypt1
> is fully installed.

This has been tried, that works for upgrade, but then apt refuses to
allow new installation of libc6+libxcrypt1, which makes it impossible to
install foreign-arch versions on an existing system.

> Another option might be to have the new libc6 Conflict with old versions
> of Essential:yes packages that need libcrypt1, forcing those Essential:yes
> packages to get upgraded first. A quick check based on libcrypt1 reverse
> dependencies in sid shows perl-base, login and util-linux. I'm not sure
> if this list is exhaustive, though.

This is something we can try indeed.

Aurelien

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