date:20201110

Processing control commands:

> tag -1 pending
Bug #974050 [python3-biom-format] python3-biom-format: ships 
/usr/lib/python3/dist-packages/.coverage
Added tag(s) pending.

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

Bug#948706: closed by Debian FTP Masters (reply to Julian Gilbey ) (Bug#948706: fixed in greylistd 0.9.0)

2020-11-10 Thread Julian Gilbey

Dear Dominic,

I've just uploaded version 0.9.0.1, which differs from 0.9.0 only in
having a new changelog entry.  Except that I only just realised what
the problem is - I uploaded the .deb files with it.  So I'll go and
upload a 0.9.0.2 version now.  That should sort out the problem; I
don't think it's possible to re-upload a source-only version after a
.deb has been uploaded.

I'm not planning to adopt this package; unfortunately I don't have
time to take on anything more.

Best wishes,

   Julian

On Tue, Nov 10, 2020 at 12:30:16AM +, Dominic Hargreaves wrote:
> On Mon, Nov 09, 2020 at 11:43:27PM +0100, Chris Hofstaedtler wrote:
> > Hello Julian,
> > 
> > * Debian Bug Tracking System  [201109 22:41]:
> > > This is an automatic notification regarding your Bug report
> > > which was filed against the greylistd package:
> > > 
> > > #948706: greylistd: python3 version fails to start - conversion from 
> > > python2 very broken
> > ...
> > > Changed-By: Julian Gilbey 
> > 
> > Could I kindly ask you to upload a new .1 version, source-only, to
> > allow migration to testing?
> > 
> > Right now, the migration tracker says:
> >   Not built on buildd: arch all binaries uploaded by jdg, a new source-only 
> > upload is needed to allow migration
> 
> Adding Julian to CC and +1 to this request.
> 
> Julian - thanks for your work on this package! Do you have any plans to
> adopt it?
> 
> Cheers
> Dominic

Processed: block 974029 with 961154 961155

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

> block 974029 with 961154 961155
Bug #974029 [src:perl] perl: add breaks on packages which were missing 
libpod-parser-perl deps
974029 was not blocked by any bugs.
974029 was not blocking any bugs.
Added blocking bug(s) of 974029: 961155 and 961154
> thanks
Stopping processing here.

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

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

2020-11-10 Thread gregor herrmann

On Tue, 10 Nov 2020 08:18:27 +0100, Andreas Tille wrote:

> On Tue, Nov 10, 2020 at 07:42:45AM +0100, Maarten L. Hekkelman wrote:
> > Sorry, long story. To make it short.
> > - Keep mrc, no problem there
> > - Upgrade libzeep to version 5

libzeep is already at version 5 in unstable but has some issues:
https://tracker.debian.org/pkg/libzeep
https://bugs.debian.org/src:libzeep

> > - Kick out mrs until it is upgraded to use libzeep 5
> I'd recommend to file an RC critical bug against mrs and give some
> explanation (may be by simply copying the relevant parts of your
> explanation.)  

Adding this explanations would indeed be helpful, besides that, mrs
already has one RC bug:

https://tracker.debian.org/pkg/mrs
https://bugs.debian.org/974016


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
   `-   BOFH excuse #103:  operators on strike due to broken coffee machine

Bug#967194: marked as done (pam-python: Unversioned Python removal in sid/bullseye)

Your message dated Tue, 10 Nov 2020 10:19:00 +
with message-id 
and subject line Bug#967194: fixed in pam-python 1.0.8-1
has caused the Debian Bug report #967194,
regarding pam-python: Unversioned Python removal in sid/bullseye
to be marked as done.

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

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


-- 
967194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967194
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pam-python
Version: 1.0.7-1.1
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned

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

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

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

Please check for dependencies, build dependencies AND autopkg tests.

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

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

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

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

Debian distribution maintenance software
pp.
Russell Stuart  (supplier of updated pam-python 
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,  5 Nov 2020 20:47:48 +1000
Source: pam-python
Binary: libpam-python libpam-python-dbgsym libpam-python-doc
Architecture: source amd64 all
Version: 1.0.8-1
Distribution: unstable
Urgency: high
Maintainer: Russell Stuart 
Changed-By: Russell Stuart 
Description:
 libpam-python - Enables PAM modules to be written in Python
 libpam-python-doc - Documentation for the bindings provided by libpam-python
Closes: 967194
Changes:
 pam-python (1.0.8-1) unstable; urgency=high
 .
   * New upstream.
   * Move to explicit python2 versioning.  Closes: #967194.
Checksums-Sha1:
 ea475f6c4f147148fa6825b26e31404d78ff2c58 1978 pam-python_1.0.8-1.dsc
 5d9df3dac47e4bab0ce01777ac95f0e4e6fe70d7 48186 pam-python_1.0.8.orig.tar.gz
 a38fad91eacc750b3417864e484c9487e2e88229 14556 pam-python_1.0.8-1.debian.tar.xz
 2e0ddaa3861cda699c9b01b5d83444db45a2b4d9 49412 
libpam-python-dbgsym_1.0.8-1_amd64.deb
 bac4933cda44423cef808155f88e77a29d5db261 38496 
libpam-python-doc_1.0.8-1_all.deb
 9893a7ba3a0dd6409f0d3b35152efe5eb3a05cf7 29940 libpam-python_1.0.8-1_amd64.deb
 a7f58ee8b0c3febf7512b82d972ae7636339335e 8234 
pam-python_1.0.8-1_amd64.buildinfo
Checksums-Sha256:
 ab4dd06e33b5cd0ef1bd72f36daee87cae29d769077e4343f68468b8c614078a 1978 
pam-python_1.0.8-1.dsc
 12499bab65dc332c7d09151fc8d08b8d2735e5ea2182a6d1bb1c9fe6af83542d 48186 
pam-python_1.0.8.orig.tar.gz
 6b9a08d60aba15c1fbe7f2dca4376f4f390ee650dc47c3052dd80fffc8d86741 14556 
pam-python_1.0.8-1.debian.tar.xz
 7cc0543c99b94cca5fc1ad3cf72ba4bd4b0da879cc0793f3ed6ccd106ef094d6 49412 
libpam-python-dbgsym_1.0.8-1_amd64.deb
 9b16819acf3ac98b2381a372939411628b63f50d585d7f6ad02dbdcaf1fd761b 38496 
libpam-python-doc_1.0.8-1_all.deb
 372c7686b225e93ea0f51be0dd7c5429bb707e440507f9034533ec603c2f4750 29940 
libpam-python_1.0.8-1_amd64.deb
 401387a913dca9212d037fa0f1470db6b32afad2add1e119c931ed12ef87f867 8234 
pam-python_1.0.8-1_amd64.buildinfo
Files:
 792d50b31fb4c021ba5e958abd226151 1978 admin optional pam-python_1.0.8-1.dsc
 99c43a31eb204aca680a12b9ccc85751 48186 admin optional 
pam-python_1.0.8.orig.tar.gz
 7604675e73ee1e7dc5b3c3e165b02f6f 14556 admin optional 
pam-python_1.0.8-1.debian.tar.xz
 ea7389e8f827974f6d9fb5ac8c939e03 4941

Processed: tulip ftbfs with python3.9

Processing control commands:

> tags -1 + fixed-upstream
Bug #972917 [src:tulip] tulip ftbfs with python3.9
Added tag(s) fixed-upstream.
> forwarded -1 https://github.com/Tulip-Dev/tulip/issues/176
Bug #972917 [src:tulip] tulip ftbfs with python3.9
Set Bug forwarded-to-address to 'https://github.com/Tulip-Dev/tulip/issues/176'.

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

Bug#972917: tulip ftbfs with python3.9

2020-11-10 Thread Graham Inggs

Control: tags -1 + fixed-upstream
Control: forwarded -1 https://github.com/Tulip-Dev/tulip/issues/176


This is fixed in upstream commit
https://github.com/Tulip-Dev/tulip/commit/a870cfb6dff961c52538cf7989c029cca262b80c

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

2020-11-10 Thread Maarten L. Hekkelman


Hi Andreas,

To avoid confusion, we're talking about three tools here: libzeep, mrc 
and mrs.


mrc is a simple resource compiler, is now compatible and bug free, 
builds on all architectures and should be kept. I believe it is very 
useful, using it I can create downloadable, portable applications that 
need additional static data without the need for installer scripts.


libzeep version 5 is the latest incarnation of a library I've been 
working on for 12 years now. It has evolved into a toolbox to build web 
applications in C++ inspired by the popular Java Spring framework and 
Thymeleaf template processor. It also contains a full XML and a JSON 
library. Using this library I could e.g. convert a pipeline to process 
genomics data into an interactive web application, the python scripts 
took up to 4 hours for each run, now you can do the same analysis in 
less than 5 seconds. I have a couple of applications based on libzeep 
that I would like to add to Debian, most of them tools used in 
crystallography and genomics research. But also a content management system.


And then we have MRS. This is a retrieval system, a web application 
capable of indexing and then searching terabytes of text based databanks 
on a single machine. Mostly used in the medical and biological world. It 
is used e.g. on mini computers that are sent into Africa where internet 
access is limited, that way large databanks like EMBL are still 
available. But I stopped development in 2012 when I switched jobs. I 
continued development of libzeep on which MRS is based but someone else 
took over development of MRS. A year ago I did a consultancy job fixing 
MRS which basically came down to reverting most of the attempted 
'improvements' after I left.


Currently I'm working at the Netherlands Cancer Institute, here I write 
both software used in crystallography as well as a genomics analysis 
tool. Many of the crystallographic tools are moving into open source 
right now. We would have liked to include those in the CCP4 
distribution, but unfortunately my code is way too new (C++17) to work 
in that environment. Next to that we would like to include our tools in 
Debian (DSSP already is, but that application needs an update), but if 
that won't work, I will set up a private repository to distribute our 
binaries.


I know libzeep is not very popular, that's because I never bothered much 
to find an audience. But I can't live without it myself, a lot of my 
tools are based on it one way or another. Libzeep is also quite mature 
and has been used in many tools in a production environment for many 
years now.


Sorry, long story. To make it short.
- Keep mrc, no problem there
- Upgrade libzeep to version 5
- Kick out mrs until it is upgraded to use libzeep 5

regards, -maarten

Op 09-11-2020 om 20:49 schreef Andreas Tille:

Hi Maarten,

On Mon, Nov 09, 2020 at 07:22:30PM +0100, Maarten L. Hekkelman wrote:

I'm sorry, but mrs as it is currently in Debian is not compatible with
libzeep version 5. It needs a major rewrite. Libzeep is a spin off project
of mrs and has evolved a lot since then.

So either libzeep should be kept at version 3 or mrs should be removed. If
mrs and libzeep are kept, I will not be able to release my other tools based
on libzeep in Debian.

You are the Uploader and the only competent person to decide.  If I
understood the issue correctly it came up right after mrc was added to
the Build-Depends.  Wouldn't it be an option to just de-couple both
again.
  

Upgrading mrs is of course the best option, but I won't have time to do that
soon.

So please draw a sensible decision.  Libzeep was according to popcon[1]
never installed by more than 10 users - currently the vote (active users)
is at zero.  Feel free to decided what *you* personally love to see in
Debian (but decreasing a version number is usually not nice).

Kind regards

  Andreas.

[1] https://qa.debian.org/popcon.php?package=libzeep
  

regards, -maarten

Op 09-11-2020 om 16:19 schreef Niko Tyni:

On Mon, Nov 09, 2020 at 09:17:25AM +0200, Juhani Numminen wrote:

Source: mrs
Version: 6.0.5+dfsg-8
Severity: serious
Tags: ftbfs sid
Justification: fails to build from source (but built successfully in the past)
| Checking for libzeep...libzeep is not installed, either install the package 
libzeep-dev
| or download libzeep from ftp://ftp.cmbi.ru.nl/pub/software/libzeep
| and run configure again.
| make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2

Looks to me like libzeep-dev is broken because the build
doesn't pass --enable-shared to ./configure.

Probably the override_dh_auto_configure-arch and
override_dh_auto_configure-indep targets in src:libzeep debian/rules
are not effective because of the earlier override_dh_auto_configure
target. But I didn't actually test any of this.

Hope this helps,

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

http://www.hekkelman.com/



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

http://www.h

Bug#974107: Segfault when running isenkram-lookup

2020-11-10 Thread Petter Reinholdtsen

[Matthias Klumpp]
> Can you give me some context for this code? If this is a warning
> coming from libappstream, it means that it somehow got fed a null
> pointer instead of a valid AsProvided object into its list, which
> shouldn't happen - is your code doing that? Are you feeding it some
> special metadata? What is the component name where this is failing?

Not quite sure what you are looking for.  Just running isenkram-lookup
from isenkram-cli seem to trigger the error.  The code in question is in
/usr/lib/python3/dist-packages/isenkram/lookup.py, method
pkgs_handling_appstream_modaliases().

-- 
Happy hacking
Petter Reinholdtsen

Bug#974050: marked as done (python3-biom-format: ships /usr/lib/python3/dist-packages/.coverage)

Your message dated Tue, 10 Nov 2020 11:03:59 +
with message-id 
and subject line Bug#974050: fixed in python-biom-format 2.1.9-2
has caused the Debian Bug report #974050,
regarding python3-biom-format: ships /usr/lib/python3/dist-packages/.coverage
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.)


-- 
974050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-biom-format
Version: 2.1.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships the python
coverage file: /usr/lib/python3/dist-packages/.coverage
causing file conflicts with other packages doing the same mistake.


Andreas
--- End Message ---
--- Begin Message ---
Source: python-biom-format
Source-Version: 2.1.9-2
Done: cru...@debian.org (Michael R. Crusoe)

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

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

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated python-biom-format 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Nov 2020 10:43:29 +0100
Source: python-biom-format
Architecture: source
Version: 2.1.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Closes: 974050
Changes:
 python-biom-format (2.1.9-2) unstable; urgency=medium
 .
   * Team upload.
   * remove .coverage files. Closes: #974050
Checksums-Sha1:
 1ea80b6e9b2a7baa5676016553862878ea8c41d9 2564 python-biom-format_2.1.9-2.dsc
 e3e80ef13e5d36d807ec682d304edbab4d5d2106 10480 
python-biom-format_2.1.9-2.debian.tar.xz
 0fc919f39f562866defbdba42ab76049c54aa6ba 10135 
python-biom-format_2.1.9-2_source.buildinfo
Checksums-Sha256:
 3578f79e368ca5b507f8f6a7d545d2f2a795482fa989a20e95b504ec4bfec621 2564 
python-biom-format_2.1.9-2.dsc
 042cffd02c84186f71423785068506f8b6248dd911a9c664e7e2e8f81d9bfdf6 10480 
python-biom-format_2.1.9-2.debian.tar.xz
 d9845677da03c63f4a248349953a7b08288bbddbee89727b637e42c275d342a6 10135 
python-biom-format_2.1.9-2_source.buildinfo
Files:
 192c6067d611ec82ed181be127229ac4 2564 python optional 
python-biom-format_2.1.9-2.dsc
 48a56f6014ff9dc248fb6b913b7e8170 10480 python optional 
python-biom-format_2.1.9-2.debian.tar.xz
 afc08a779b956122c3d906d03204687d 10135 python optional 
python-biom-format_2.1.9-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAl+qYNMACgkQPCZ2P2xn
5uL8tw//dqREk1NSbB0HYoTUu21aMP4t0o2lALN+qg6fW7srbcaEjI3RGmjQzx99
un+SrWh1o8fBuMS3e3qfildomG154PUW2cL/Cdlx5x3Coc5/nnPrNs3R2ocYV0ug
ppp4/8hkrbE+GwW2I6F8ePfAXgZvkNzMQGe5gr/7z/qu27eFCr4bLyjaR+LASgGh
nRgGVt10J9gzyJQs9XiNXRDBcnF+ddBP2y3+o/maHBJXyj20ILdnRg1k4IWDWnB3
k50mgPnyJT4LBc2hgj663B7d25eryAHUlHYViuoap0nYEZ4f8RIkE0pRGQMGJQSP
zWpa624YuqRhNaTGMtI+SyI0d09UC+qAbobCWbPPhD2CAQthHSYqPEvv10KvbLVA
XUrL0Gp3TA4wOi1LeuyMosO3Rp3xqWQOFWMJ+0ypTKpzxpjzUILyOD1uVNaM6Uo/
jjK0oZIYVNPtICSyRMndiHmLBVpXgaQ9n/MKROZbNaQGIlkZ1/BdgPUl7exD4u1e
NKMpw3jpRzLU7JlN2UKGOAjcTbj7gh03bircWUfVTrI3UzU1VjaGTWzO2FeqWYG+
GVzzSa7STomU59YmTy6W0YCtMXIuoGDgeDrEl5QSHVZkI1j44eI4mFBGgnK93jo4
rvk5JpmJqG7zRnjVbIBChpS7cSbbJsmDuhRiWnjqN3wzDvhWauY=
=o8Mb
-END PGP SIGNATURE End Message ---

Bug#972334: closed by Debian FTP Masters (reply to Sylvestre Ledru ) (Bug#972334: fixed in llvm-toolchain-11 1:11.0.0-5)

2020-11-10 Thread Sebastian Ramacher

Control: reopen -1

On 2020-11-07 20:51:03 +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:llvm-toolchain-11 package:
> 
> #972334: llvm-toolchain-11: autopkgtest failure on i386: 
> integration-test-suite-test FAIL non-zero exit status 2
> 
> It has been closed by Debian FTP Masters  
> (reply to Sylvestre Ledru ).

autopkgtests of 1:11.0.0-5 on i386 also failed
https://ci.debian.net/data/autopkgtest/testing/i386/l/llvm-toolchain-11/8026381/log.gz

Cheers

> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP Masters 
>  (reply to Sylvestre Ledru 
> ) by
> replying to this email.
> 
> 
> -- 
> 972334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972334
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Sat, 07 Nov 2020 20:48:53 +
> From: Debian FTP Masters 
> To: 972334-cl...@bugs.debian.org
> Subject: Bug#972334: fixed in llvm-toolchain-11 1:11.0.0-5
> Reply-To: Sylvestre Ledru 
> Message-Id: 
> 

> Date: Fri, 16 Oct 2020 12:09:53 +0200
> From: Sebastian Ramacher 
> To: Debian Bug Tracking System 
> Subject: llvm-toolchain-11: autopkgtest failure on i386:
>  integration-test-suite-test FAIL non-zero exit status 2
> Message-ID: <20201016100953.ga5...@ramacher.at>
> 
> Source: llvm-toolchain-11
> Version: 1:11.0.0-2
> Severity: serious
> 
> The autopkgtest for i386 currently fail:
> | 
> | Failed Tests (4):
> |   LLVM regression suite :: basic_lldb.c
> |   LLVM regression suite :: basic_lldb2.cpp
> |   LLVM regression suite :: test_asan_lc.c
> |   LLVM regression suite :: test_tsan.c
> |
> |
> | Testing Time: 13.96s
> |   Unsupported:  3
> |   Passed : 18
> |   Failed :  4
> 
> See
> https://ci.debian.net/data/autopkgtest/testing/i386/l/llvm-toolchain-11/7487758/log.gz
> for the full log
> 
> Cheers
> -- 
> Sebastian Ramacher


-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: Re: Bug#972334 closed by Debian FTP Masters (reply to Sylvestre Ledru ) (Bug#972334: fixed in llvm-toolchain-11 1:11.0.0-5)

Processing control commands:

> reopen -1
Bug #972334 {Done: Sylvestre Ledru } 
[src:llvm-toolchain-11] llvm-toolchain-11: autopkgtest failure on i386: 
integration-test-suite-test FAIL non-zero exit status 2
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions llvm-toolchain-11/1:11.0.0-5.

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

Bug#973723: libcharls-dev ships libcharls.so which is also in libdcmtk-dev

2020-11-10 Thread DCMTK Team


Dear Mathieu,


Would it make sense to rename the customized charls included as a
convenient copy in dcmtk as 'libdcmcharls.so' instead of simply
'libcharls.so' ?


Yes, I agree that it would make sense to rename the DCMTK specific version of 
libcharls
to avoid naming conflicts with a system-wide charls installation.


Here is a suggested patch for cmake based build system to handle
renaming of charls to dcmcharls.


Thank you for the patch. We will rename the library to "dcmtkcharls"
(instead of "dcmcharls", as your patch suggests) to make the naming
consistent with the renamed OpenSSL libraries we use on Windows,
but otherwise I will commit your patch so that the naming conflict
will be gone in the upcoming DCMTK 3.6.6 release.


Best regards,
Dr. Marco Eichelberg

--
DCMTK Team, OFFIS e.V., Escherweg 2, 26121 Oldenburg, Germany
E-Mail: i...@dcmtk.org, URL: http://www.dcmtk.org

Registergericht: Amtsgericht Oldenburg VR 1956
Vorstand: Prof. Dr. Sebastian Lehnhoff (Vorsitzender), Prof. Dr. techn. Susanne 
Boll-Westermann,
Prof. Dr.-Ing. Axel Hahn, Prof. Dr.-Ing. Andreas Hein, Prof. Dr.-Ing. Wolfgang 
H. Nebel

-> Nächste DICOM-Schulung vom 23. bis 24. November 2020, Online
-> Next DICOM courses in English 27 to 28 October 2020, Online
-> Nächste HL7-Schulung vom 25.-26. November 2020, Online

Processed: severity of 937234 is serious

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

> severity 937234 serious
Bug #937234 [src:pam-python] pam-python: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: varnish-modules: diff for NMU version 0.16.0-2.1

Processing control commands:

> tags 971142 + pending
Bug #971142 [src:varnish-modules] varnish-modules: FTBFS: 
vmod_bodyaccess.c:205:2: error: ‘VSB_delete’ is deprecated 
[-Werror=deprecated-declarations]
Bug #971521 [src:varnish-modules] varnish-modules: autopkgtest needs update for 
new version of varnish: Depends on old ABI
Added tag(s) pending.
Added tag(s) pending.

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

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

Control: tags 971142 + pending

Dear maintainer,

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

cu
Adrian
diff -Nru varnish-modules-0.16.0/debian/changelog varnish-modules-0.16.0/debian/changelog
--- varnish-modules-0.16.0/debian/changelog	2020-07-22 12:11:28.0 +0300
+++ varnish-modules-0.16.0/debian/changelog	2020-11-10 10:21:35.0 +0200
@@ -1,3 +1,11 @@
+varnish-modules (0.16.0-2.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Backport upstream fix for FTBFS with Varnish 6.5.
+(Closes: #971142)
+
+ -- Adrian Bunk   Tue, 10 Nov 2020 10:21:35 +0200
+
 varnish-modules (0.16.0-2) unstable; urgency=medium
 
   * Fix FTBFS issue with Varnish ABI dependency (Closes: #963452)
diff -Nru varnish-modules-0.16.0/debian/patches/0001-Update-call-from-VSB_delete-to-VSB_destroy-see-c502f.patch varnish-modules-0.16.0/debian/patches/0001-Update-call-from-VSB_delete-to-VSB_destroy-see-c502f.patch
--- varnish-modules-0.16.0/debian/patches/0001-Update-call-from-VSB_delete-to-VSB_destroy-see-c502f.patch	1970-01-01 02:00:00.0 +0200
+++ varnish-modules-0.16.0/debian/patches/0001-Update-call-from-VSB_delete-to-VSB_destroy-see-c502f.patch	2020-11-10 10:20:57.0 +0200
@@ -0,0 +1,49 @@
+From fed6c862118ca34374b0284a1838cc49cea5b4d1 Mon Sep 17 00:00:00 2001
+From: Xavier De Cock 
+Date: Mon, 19 Oct 2020 17:03:50 +0200
+Subject: Update call from VSB_delete to VSB_destroy see
+ c502f536077668e5a88a2383458ab829873c80e5
+
+---
+ src/vmod_bodyaccess.c | 4 ++--
+ src/vmod_saintmode.c  | 2 +-
+ 2 files changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/src/vmod_bodyaccess.c b/src/vmod_bodyaccess.c
+index 8899257..b173397 100644
+--- a/src/vmod_bodyaccess.c
 b/src/vmod_bodyaccess.c
+@@ -154,7 +154,7 @@ vmod_hash_req_body(VRT_CTX)
+ 	txtbody.e = txtbody.b + VSB_len(vsb);
+ 	SHA256_Update(ctx->specific, txtbody.b, txtbody.e - txtbody.b);
+ 	VSLbt(ctx->vsl, SLT_Hash, txtbody);
+-	VSB_delete(vsb);
++	VSB_destroy(&vsb);
+ }
+ 
+ VCL_INT
+@@ -227,7 +227,7 @@ vmod_rematch_req_body(VRT_CTX, struct vmod_priv *priv_call, VCL_STRING re)
+ 	i = VRE_exec(priv_call->priv, VSB_data(vsb), VSB_len(vsb), 0, 0, NULL,
+ 	0, NULL);
+ 
+-	VSB_delete(vsb);
++	VSB_destroy(&vsb);
+ 
+ 	if (i > 0)
+ 		return (1);
+diff --git a/src/vmod_saintmode.c b/src/vmod_saintmode.c
+index b0e4ac6..7009bfb 100644
+--- a/src/vmod_saintmode.c
 b/src/vmod_saintmode.c
+@@ -186,7 +186,7 @@ vmod_status(VRT_CTX, struct vmod_priv *priv)
+ 	if (p == NULL)
+ 		VSLb(ctx->vsl, SLT_VCL_Log,
+ 		"saintmode.vmod_status: workspace overflow");
+-	VSB_delete(vsb);
++	VSB_destroy(&vsb);
+ 	return (p);
+ }
+ 
+-- 
+2.20.1
+
diff -Nru varnish-modules-0.16.0/debian/patches/series varnish-modules-0.16.0/debian/patches/series
--- varnish-modules-0.16.0/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ varnish-modules-0.16.0/debian/patches/series	2020-11-10 10:21:30.0 +0200
@@ -0,0 +1 @@
+0001-Update-call-from-VSB_delete-to-VSB_destroy-see-c502f.patch

Bug#971433: libcharls-dev: Problem with latest unstable install

2020-11-10 Thread Pablo Modernell

apt --fix-broken install
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Corrigiendo dependencias... Listo
El paquete indicado a continuación se instaló de forma automática y ya no
es necesario.
  libbrlapi0.7
Utilice «apt autoremove» para eliminarlo.
Se instalarán los siguientes paquetes adicionales:
  libcharls-dev
Se actualizarán los siguientes paquetes:
  libcharls-dev
1 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados.
Se necesita descargar 0 B/20,6 kB de archivos.
Se utilizarán 6.144 B de espacio de disco adicional después de esta
operación.
¿Desea continuar? [S/n] s
Leyendo lista de cambios... Hecho.
(Leyendo la base de datos ... 173515 ficheros o directorios instalados
actualmente.)
Preparando para desempaquetar .../libcharls-dev_2.1.0+dfsg-6_amd64.deb ...
Desempaquetando libcharls-dev:amd64 (2.1.0+dfsg-6) sobre (2.1.0+dfsg-3) ...
dpkg: error al procesar el archivo
/var/cache/apt/archives/libcharls-dev_2.1.0+dfsg-6_amd64.deb (--unpack):
 intentando sobreescribir `/usr/lib/x86_64-linux-gnu/libcharls.so', que
está también en el paquete libdcmtk-dev 3.6.4-2.1+b1
Se encontraron errores al procesar:
 /var/cache/apt/archives/libcharls-dev_2.1.0+dfsg-6_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- 


*--~--~-~--~~~---~--~~*

*--~--~-~--~~~---~--~~*

Processed: tagging 971177

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

> tags 971177 + fixed-upstream
Bug #971177 [src:intake] intake: FTBFS: TypeError: 'NoneType' object is not 
iterable
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Fixed upstream

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

> forwarded 971162 
> https://github.com/tidwall/buntdb/commit/14666ffbfc79b909a34eab739b45733bc9bc0184
Bug #971162 [src:golang-github-tidwall-buntdb] golang-github-tidwall-buntdb: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/tidwall/buntdb returned exit code 1
Set Bug forwarded-to-address to 
'https://github.com/tidwall/buntdb/commit/14666ffbfc79b909a34eab739b45733bc9bc0184'.
> tags 971162 patch fixed-upstream
Bug #971162 [src:golang-github-tidwall-buntdb] golang-github-tidwall-buntdb: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/tidwall/buntdb returned exit code 1
Added tag(s) fixed-upstream and patch.
> thanks
Stopping processing here.

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

Bug#974063: marked as pending in postgresql

Control: tag -1 pending

Hello,

Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/1f4f3c0a9d0b0c0c9bb9940af1a03ce4a778b08a


New upstream version.

+ Fixes timetz regression test failures. (Closes: #974063)
* Show only log files on failure.
  regression.out regression.diffs
  initdb.log postmaster.log
  tmp_check/log/regress_log_001_*


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974063

Processed: Bug#974063 marked as pending in postgresql

Processing control commands:

> tag -1 pending
Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure
Added tag(s) pending.

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

Bug#974107: Segfault when running isenkram-lookup

2020-11-10 Thread Gunnar Hjalmarsson


Additional observations:

* The testing failure in Ubuntu started around October 31.

* The test-command-line script fails on amd64 and i386 but succeeds on
  other architectures.

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

Processed: libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3

Processing control commands:

> block 968912 with -1
Bug #968912 [release.debian.org] transition: perl 5.32
968912 was blocked by: 974055 974021 972275 974061 961155 968913 974063 961152 
972274 961208 961154 974016 964902 961157 960863 974058
968912 was not blocking any bugs.
Added blocking bug(s) of 968912: 974134

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

Bug#974134: libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3

2020-11-10 Thread Niko Tyni

Source: libdbd-csv-perl
Version: 0.5500-1
Severity: serious
Tags: patch fixed-upstream
Forwarded: 
https://github.com/perl5-dbi/DBD-CSV/commit/88c3ca044a3881eab62d6d2d38490351fd421386
Control: block 968912 with -1

libdbi-perl 1.643-3 cannot currently migrate to testing, as
it causes a test failure in libdbd-csv-perl.

  t/11_dsnlist.t  
  ok 1 - use DBI;
  ok 2 - Driver is CSV
  # 
  ok 3 - Connect
  ok 4 - ping
  ok 5 - data_sources
  ok 6 - more than one
  ok 7 - disconnect
  ok 8 - use . as f_dir
  ok 9 - disconnect
  DBI connect('f_dir=example','',...) failed: No such directory 'example at 
./t/lib.pl line 162.
  # Cannot connect: No such directory 'example
  # Tests were run but no plan was declared and done_testing() was not seen.
  # Looks like your test exited with 255 just after 9.
  Dubious, test returned 255 (wstat 65280, 0xff00)

[...]
  
  Test Summary Report
  ---
  t/11_dsnlist.t  (Wstat: 65280 Tests: 9 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
  Files=24, Tests=1558,  9 wallclock secs ( 0.33 usr  0.06 sys +  7.68 cusr  
0.77 csys =  8.84 CPU)
  Result: FAIL
 
This is presumably fixed upstream by

  
https://github.com/perl5-dbi/DBD-CSV/commit/88c3ca044a3881eab62d6d2d38490351fd421386

This seems to be a test-only issue, so a Breaks entry on the libdbi-perl
side is probably not needed (at least if a fixed libdbd-csv-perl is able
to migrate on its own.)

-- 
Niko Tyni   nt...@debian.org

Bug#974134: marked as pending in libdbd-csv-perl

2020-11-10 Thread Dominic Hargreaves

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libdbd-csv-perl/-/commit/d271e3f705c7167facf66a90beec8e107aaa85a4


Fix test failure with libdbi-perl 1.643-3 (Closes: #974134)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974134

Processed: Bug#974134 marked as pending in libdbd-csv-perl

Processing control commands:

> tag -1 pending
Bug #974134 [src:libdbd-csv-perl] libdbd-csv-perl: test suite fails with 
libdbi-perl 1.643-3
Added tag(s) pending.

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

Bug#973084: marked as pending in docker.io

2020-11-10 Thread Arnaud Rebillout

Control: tag -1 pending

Hello,

Bug #973084 in docker.io 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/docker-team/docker/-/commit/968a84186afa88241c56d501f40dfa97cf20dd8c


Fix FTBFS due to go-md2man v2 (Closes: #973084)

Import a bunch of upstream patches to handle the transition to
go-md2manv2.

In Debian at the moment, both golang-github-cpuguy83-go-md2man-dev and
golang-github-cpuguy83-go-md2man-v2-dev are available, however when it
comes to the binary, only go-md2man v2 is available.

Mixing both version, ie. building spf13/cobra against v1, and then using
go-md2man v2 to generate the manpages, does not work (the generated man
pages are wrong).

So the most straightforward solution here seems to patch, and completely
use go-md2man v2, both for build and then to generate the man pages.

It would be a bit easier if we wouldn't have to vendor spf13/cobra, and
I hope I can drop this vendoring bits soon.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973084

Processed: Bug#973084 marked as pending in docker.io

Processing control commands:

> tag -1 pending
Bug #973084 [src:docker.io] docker.io: FTBFS: 
vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package 
"github.com/cpuguy83/go-md2man/md2man"
Added tag(s) pending.

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

Bug#940536: marked as done (dhex: hangs on keyboard config screen)

Your message dated Tue, 10 Nov 2020 14:38:12 +
with message-id 
and subject line Bug#940536: fixed in dhex 0.69-2
has caused the Debian Bug report #940536,
regarding dhex: hangs on keyboard config screen
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.)


-- 
940536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940536
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dhex
Version: 0.69-1
Severity: important

Hi,

As described the program hangs on what it looks like some keyboard
configuration screen, which only can be exited by Ctrl-C. I tried also
pressing ESC as advertised, but is ignored:


Please press the following keys
(Press ESC if your keyboard does not have them)

Config file:/home/mones/.dhexrc

KEYESC:















The standard cancel key


Nothing else can be done with it, so this is completely useless.

Looking also at #889956 makes me wonder if this stuff wouldn't be better
removed from the archive.

regards,

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

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

Versions of packages dhex depends on:
ii  libc62.28-10
ii  libncurses6  6.1+20181013-2+deb10u1
ii  libtinfo66.1+20181013-2+deb10u1

dhex recommends no packages.

dhex suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dhex
Source-Version: 0.69-2
Done: Fabio Augusto De Muzio Tobich 

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

Debian distribution maintenance software
pp.
Fabio Augusto De Muzio Tobich  (supplier of updated dhex 
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, 09 Nov 2020 13:06:23 -0300
Source: dhex
Architecture: source
Version: 0.69-2
Distribution: unstable
Urgency: medium
Maintainer: Fabio Augusto De Muzio Tobich 
Changed-By: Fabio Augusto De Muzio Tobich 
Closes: 940536 973686
Changes:
 dhex (0.69-2) unstable; urgency=medium
 .
   * New maintainer. (Closes: #973686)
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 13.
   * debian/control:
   - Added Rules-Requires-Root: no.
   - Added Vcs-* fields in source stanza.
   - Bumped Standards-Version to 4.5.0.
   - Changed Homepage field to use a secure URI.
   * debian/copyright:
   - Added myself and Axel Beckert to packaging block.
   - Added Upstream-Contact field.
   - Updated years in packaging block.
   - Using a secure URI in Format and Source fields.
   * debian/patches/:
   - 010_fix-typos.patch: added to fix several typos and spelling errors.
   - 020_hardening-fix.patch: added to be possible to implement hardening.
   - cpu-load: removed, does not work with 0.69 and causes buggy behavior.
 (Closes: #940536, LP: #1814478)
   - fix-typos: removed, was replaced by 010_fix-typos.patch.
   - harden: removed, it doesn't work in 0.69.
   - series: updated to reflect the changes.
   * debian/rules:
   - Removed unnecessary DEB_LDFLAGS_MAINT_APPEND flags.
   - Removed unnecessary DEB_CFLAGS_MAINT_APPEND flags.
   * debian/salsa-ci.yml: added to provide CI tests for Salsa.
   * debian/tests/:
   - control: created to perform a trivial CI test.
   - files/sample.txt: added to be used on tests.
   * debian/upstream/metadata: created.
   * debian/watch:
   - Bumped to version 4.
   - Updated to use a secure URI with HTTPS protocol.
Checksums-Sha1:
 f65bf4f385aea54c169e6d9515d3d76a24fc4c9c 1820 dhex_0.69-2.dsc
 368918164cfb188f11cae12c8fc96caf5c6

Bug#970612: marked as done (golang-github-fogleman-gg: autopkgtest arm64 failure: context_test.go:31: expected hash: 56b842d814aee94b52495addae764a77 != actual hash: 8bc90640363d48e4ed2b9741a3a52ffa)

Your message dated Tue, 10 Nov 2020 14:38:18 +
with message-id 
and subject line Bug#970612: fixed in golang-github-fogleman-gg 1.3.0-3
has caused the Debian Bug report #970612,
regarding golang-github-fogleman-gg: autopkgtest arm64 failure: 
context_test.go:31: expected hash: 56b842d814aee94b52495addae764a77 != actual 
hash: 8bc90640363d48e4ed2b9741a3a52ffa
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.)


-- 
970612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970612
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-fogleman-gg
Version: 1.3.0-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always

Dear maintainer(s),

You recently added an autopkgtest to your package
golang-github-fogleman-gg, great. However, it fails on arm64. Currently
this failure is blocking the migration to testing [1]. Can you please
investigate the situation and fix it?
Paul

[1] https://qa.debian.org/excuses.php?package=golang-github-fogleman-gg

https://ci.debian.net/data/autopkgtest/testing/amd64/g/golang-github-fogleman-gg/6576326/log.gz




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: golang-github-fogleman-gg
Source-Version: 1.3.0-3
Done: Nilesh Patra 

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

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

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-fogleman-gg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Nov 2020 19:25:29 +0530
Source: golang-github-fogleman-gg
Architecture: source
Version: 1.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nilesh Patra 
Closes: 970612
Changes:
 golang-github-fogleman-gg (1.3.0-3) unstable; urgency=medium
 .
   * Disable couple of tests on arches other than amd64
 (Closes: #970612)
Checksums-Sha1:
 7326ee7e4e6c81df9408cc02c2d22141d84e3123 2320 
golang-github-fogleman-gg_1.3.0-3.dsc
 22730cc9850c9a1cade3355f5a8f59681aa7111b 3604 
golang-github-fogleman-gg_1.3.0-3.debian.tar.xz
 f52cec19c0d28fd3fea0dc4284171e1b76ad505f 6292 
golang-github-fogleman-gg_1.3.0-3_amd64.buildinfo
Checksums-Sha256:
 f3e405964e34ff612bfc293f83a302ee5c1e6ca22b272b89e7562f74625963fa 2320 
golang-github-fogleman-gg_1.3.0-3.dsc
 d24b457357cd0b4481192e4d20443d5a18e03dada7744b97a66657d742fa95da 3604 
golang-github-fogleman-gg_1.3.0-3.debian.tar.xz
 35f63c5fc8a669863c042c9b2ce2af873b390e18cee73cab548daeef9f490669 6292 
golang-github-fogleman-gg_1.3.0-3_amd64.buildinfo
Files:
 c820971b39e281fbdde466fd457bcf13 2320 devel optional 
golang-github-fogleman-gg_1.3.0-3.dsc
 0db2ce9f99dbbdaa0abe8551dd0231c3 3604 devel optional 
golang-github-fogleman-gg_1.3.0-3.debian.tar.xz
 4817a91d0b5e1ee0880823a1799bc2f9 6292 devel optional 
golang-github-fogleman-gg_1.3.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAl+qnK0UHG5wYXRyYTk3
NEBnbWFpbC5jb20ACgkQALrnSzQzafFNoA//RF7yxYtIFkBijdMatORRtWdkABVx
xcIUmrXexWdnfUsPv1UNHNKYE/47htqI3dWZ5cJuHVjKi3J9NGPvq8hTtzCQmVWE
SMUZxOGyTAgkpi7LhBhh5yfd/Tuna5KV6KrcQZT12LkqKcJJjgs1fyL3mHpN6Oqt
BuATikiK+dZRYRss71a3y2YQSnyrZdY9KaixKJKhtG9t6jnMQTyunkKEH11n1Mdw
jqYVhDOQ5dGEwAPQ45lbK/OfyRmOXPFTdp2L0ixLOndQalVxIg4gqNaC/2w8fmfH
8j6A090YeGPIVgVX0EQgimPeT+wRuqQrE/2hP6pRPhSKK6sEvB+C90gB9Z5jv5jX
KVPWaZt6zs9dbQ5t0MZy0R2vaaNKq6FNqR2YPNvyGDl7JHEF4dhBksq0Wneq7lUQ
oWM/gHUJq9DZwGG6jPmFSNQEH7lB5iKGLE3K2SAg70PrwlDiZSy+elWYQrGfOgqt
ddn6a7i9V3MIxcUk65xC0Cbv2Jm7EFc9x5TIvNh009VUzfJg6jU1StGwjwy18DmV
ZCQaDzOKY0sGP5/yNmekqn+Uw9DIiow0iG3P3q+XZobWahN0/e++Yq4YE0Q19BAR
5t0be8crc0XBdy9BIkSl6OGAijHymHGeJEOI+mM/gCc3tGByGZP1Q+/PPQXefEW7
wcqpJ2xsDgzmIDg=
=NHIo
-END PGP SIGNATURE End Message ---

Processed: Re: pgcli: Broken dependencies render package unusable

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

> severity 972598 grave
Bug #972598 [pgcli] pgcli: Broken dependencies render package unusable
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: Add the help tag

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

> tags 973526 +help
Bug #973526 [src:libzeep] libzeep: FTBFS: 2 failures are detected in the test 
module "HTTP_Test"
Added tag(s) help.
> kthxbye
Stopping processing here.

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

Processed: Bug#972776 marked as pending in talloc

Processing control commands:

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

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

Processed: Bug#974063 marked as pending in postgresql

Processing control commands:

> tag -1 pending
Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure
Ignoring request to alter tags of bug #974063 to the same tags previously set

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

Bug#974063: marked as pending in postgresql

Control: tag -1 pending

Hello,

Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/e89ba86c314546e047eb8082ecaa27b4d94270e3

New upstream version.

+ Fixes timetz regression test failures. (Closes: #974063)
+ Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers
within index expressions and materialized view queries (Noah Misch)
This is essentially a leak in the security restricted operation sandbox
mechanism. An attacker having permission to create non-temporary SQL
objects could parlay this leak to execute arbitrary SQL code as a
superuser.
The PostgreSQL Project thanks Etienne Stalmans for reporting this
problem. (CVE-2020-25695)
+ Fix usage of complex connection-string parameters in pg_dump,
pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane)
The -d parameter of pg_dump and pg_restore, or the --maintenance-db
parameter of the other programs mentioned, can be a connection string
containing multiple connection parameters rather than just a database
name. In cases where these programs need to initiate additional
connections, such as parallel processing or processing of multiple
databases, the connection string was forgotten and just the basic
connection parameters (database name, host, port, and username) were
used for the additional connections. This could lead to connection
failures if the connection string included any other essential
information, such as non-default SSL or GSS parameters. Worse, the
connection might succeed but not be encrypted as intended, or be
vulnerable to man-in-the-middle attacks that the intended connection
parameters would have prevented. (CVE-2020-25694)
+ When psql's \connect command re-uses connection parameters, ensure that
all non-overridden parameters from a previous connection string are
re-used (Tom Lane)
This avoids cases where reconnection might fail due to omission of
relevant parameters, such as non-default SSL or GSS options. Worse, the
reconnection might succeed but not be encrypted as intended, or be
vulnerable to man-in-the-middle attacks that the intended connection
parameters would have prevented. This is largely the same problem as
just cited for pg_dump et al, although psql's behavior is more complex
since the user may intentionally override some connection parameters.
(CVE-2020-25694)
+ Prevent psql's \gset command from modifying specially-treated variables
(Noah Misch)
\gset without a prefix would overwrite whatever variables the server
told it to. Thus, a compromised server could set specially-treated
variables such as PROMPT1, giving the ability to execute arbitrary shell
code in the user's session.
The PostgreSQL Project thanks Nick Cleaton for reporting this problem.
(CVE-2020-25696)
* Show more log files on failure.

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/974063

Bug#972776: marked as pending in talloc

2020-11-10 Thread Mathieu Parent

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/samba-team/talloc/-/commit/0a8d5765c733e3ff8ffe7287526b3e392cac


d/python3-talloc.symbols: generating so suffix (Closes: #972776)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/972776

Bug#970138: marked as done (fcitx5-skk: icon conflict with fcitx-skk)

Your message dated Tue, 10 Nov 2020 15:03:54 +
with message-id 
and subject line Bug#970138: fixed in fcitx5-skk 5.0.0-1
has caused the Debian Bug report #970138,
regarding fcitx5-skk: icon conflict with fcitx-skk
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.)


-- 
970138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fcitx5-skk
Version: 0.0~git20200615.d13e190-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package fcitx5-skk:amd64.
  Preparing to unpack .../24-fcitx5-skk_0.0~git20200615.d13e190-1_amd64.deb ...
  Unpacking fcitx5-skk:amd64 (0.0~git20200615.d13e190-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-UUXaxs/24-fcitx5-skk_0.0~git20200615.d13e190-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/share/icons/hicolor/64x64/apps/fcitx-skk.png', 
which is also in package fcitx-skk 0.1.4-1+b1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-UUXaxs/24-fcitx5-skk_0.0~git20200615.d13e190-1_amd64.deb

This is the only file shared between the two packages.


cheers,

Andreas


fcitx-skk=0.1.4-1+b1_fcitx5-skk=0.0~git20200615.d13e190-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fcitx5-skk
Source-Version: 5.0.0-1
Done: Shengjing Zhu 

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

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

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated fcitx5-skk package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Nov 2020 22:45:49 +0800
Source: fcitx5-skk
Architecture: source
Version: 5.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Shengjing Zhu 
Closes: 970138
Changes:
 fcitx5-skk (5.0.0-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Boyuan Yang ]
   * debian/: Add missing build-dep
   * fcitx5-skk: Depends on skkdic
 .
   [ Shengjing Zhu ]
   * New upstream release
   * Bump fcitx5 to 5.0.0
   * Rename icon to fcitx5-skk (Closes: #970138)
Checksums-Sha1:
 a21b438be397ef9fb8e966bc8c44c936c85c8d59 1510 fcitx5-skk_5.0.0-1.dsc
 edbbff212354189c54f8df0d21d36aa3cc83c133 39594 fcitx5-skk_5.0.0.orig.tar.gz
 3a6a9ae5f5e4aa875bea7ec5af1267fdc72c9fd4 2444 fcitx5-skk_5.0.0-1.debian.tar.xz
 38db5ef943bbfddda95fb730cfaeafdaff4b77e1 12268 
fcitx5-skk_5.0.0-1_amd64.buildinfo
Checksums-Sha256:
 5542e9de8844963e28dd9b568c70cac0db14f7ec8bb64042e800027c6e694c42 1510 
fcitx5-skk_5.0.0-1.dsc
 4daa08248f761a15e47eae5f8c6de79c6332cf7108200334497dc107a7c3532b 39594 
fcitx5-skk_5.0.0.orig.tar.gz
 b90ff3b81af8fa3609113b6e2e5911de67eeb7ffe2c560a85c03c37adb387c1e 2444 
fcitx5-skk_5.0.0-1.debian.tar.xz
 afeaa987517566a6910fe5d293101d29e8b55ea4c15ab6fac72894371e652a45 12268 
fcitx5-skk_5.0.0-1_amd64.buildinfo
Files:
 89e632f7549b21df510324582fc780d7 1510 utils optional fcitx5-skk_5.0.0-1.dsc
 bd69ecbcb92708fab47580b0029e8270 39594 utils optional 
fcitx5-skk_5.0.0.orig.tar.gz
 37e12a169ac35e024a78074c721451c9 2444 utils optional 
fcitx5-skk_5.0.0-1.debian.tar.xz
 8a61ca60a9495119863cd0503db466ec 12268 utils optional 
fcitx5-skk_5.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCX6qogRAcemhzakBkZWJp
YW4ub3JnAAoJEMSFSjgY4LAWmu0A/RYA2qEj5pOkcbm77GS2uNo5nOkaHbR/Mk1r
UMknrG27AQC9rvlRIIFCEAmAz3o3PIcwE1rpzewpUBrTSuofNjJiAw==
=JQRN
-END PGP SIGNATURE End Message ---

Bug#974134: marked as done (libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3)

Your message dated Tue, 10 Nov 2020 15:04:19 +
with message-id 
and subject line Bug#974134: fixed in libdbd-csv-perl 0.5500-2
has caused the Debian Bug report #974134,
regarding libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3
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.)


-- 
974134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974134
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdbd-csv-perl
Version: 0.5500-1
Severity: serious
Tags: patch fixed-upstream
Forwarded: 
https://github.com/perl5-dbi/DBD-CSV/commit/88c3ca044a3881eab62d6d2d38490351fd421386
Control: block 968912 with -1

libdbi-perl 1.643-3 cannot currently migrate to testing, as
it causes a test failure in libdbd-csv-perl.

  t/11_dsnlist.t  
  ok 1 - use DBI;
  ok 2 - Driver is CSV
  # 
  ok 3 - Connect
  ok 4 - ping
  ok 5 - data_sources
  ok 6 - more than one
  ok 7 - disconnect
  ok 8 - use . as f_dir
  ok 9 - disconnect
  DBI connect('f_dir=example','',...) failed: No such directory 'example at 
./t/lib.pl line 162.
  # Cannot connect: No such directory 'example
  # Tests were run but no plan was declared and done_testing() was not seen.
  # Looks like your test exited with 255 just after 9.
  Dubious, test returned 255 (wstat 65280, 0xff00)

[...]
  
  Test Summary Report
  ---
  t/11_dsnlist.t  (Wstat: 65280 Tests: 9 Failed: 0)
Non-zero exit status: 255
Parse errors: No plan found in TAP output
  Files=24, Tests=1558,  9 wallclock secs ( 0.33 usr  0.06 sys +  7.68 cusr  
0.77 csys =  8.84 CPU)
  Result: FAIL
 
This is presumably fixed upstream by

  
https://github.com/perl5-dbi/DBD-CSV/commit/88c3ca044a3881eab62d6d2d38490351fd421386

This seems to be a test-only issue, so a Breaks entry on the libdbi-perl
side is probably not needed (at least if a fixed libdbd-csv-perl is able
to migrate on its own.)

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libdbd-csv-perl
Source-Version: 0.5500-2
Done: Dominic Hargreaves 

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

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

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

Debian distribution maintenance software
pp.
Dominic Hargreaves  (supplier of updated libdbd-csv-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Nov 2020 14:22:54 +
Source: libdbd-csv-perl
Architecture: source
Version: 0.5500-2
Distribution: unstable
Urgency: high
Maintainer: Debian Perl Group 
Changed-By: Dominic Hargreaves 
Closes: 974134
Changes:
 libdbd-csv-perl (0.5500-2) unstable; urgency=high
 .
   * Team upload.
   * Fix test failure with libdbi-perl 1.643-3 (Closes: #974134)
Checksums-Sha1:
 4d3fe34b582480c70f2229778dfba4f83a5b76d3 2263 libdbd-csv-perl_0.5500-2.dsc
 dcbd6019d60453113fe8d59c0f2f17517ab929ec 6256 
libdbd-csv-perl_0.5500-2.debian.tar.xz
 c34ce58e089f200c0f29279da2f5e38a6d1d88b7 5568 
libdbd-csv-perl_0.5500-2_source.buildinfo
Checksums-Sha256:
 165be2142e382699cd0d00523408f95888662a998a7d7954fd33ebf846f6c77e 2263 
libdbd-csv-perl_0.5500-2.dsc
 60d33706bb37429b8ec011e0e7baa10e457f8898ee2ad316cfc531cac97b6c00 6256 
libdbd-csv-perl_0.5500-2.debian.tar.xz
 dd9a958a21f7ec1bac1a2c55b51a82cbe2cda7a0a4a4d18dc5fbfec01bd023a8 5568 
libdbd-csv-perl_0.5500-2_source.buildinfo
Files:
 9b82829ec4b87fe284f7781fec5121d2 2263 perl optional 
libdbd-csv-perl_0.5500-2.dsc
 8b39c4e522474cdeb0a0274c85a1c8c6 6256 perl optional 
libdbd-csv-perl_0.5500-2.debian.tar.xz
 f2070b62a2b9a2bfa556ebf2a859abdc 5568 perl optional 
libdbd-csv-perl_0.5500-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJBBAEBCAArFiEEy0llJ/kAnyscGnbawAV+cU1pT7IFAl+qoosNHGRvbUBlYXJ0
aC5saQAKCRDABX5xTWlPsnsuD/0SRIKdF6piMifRoaKqoC6u5O0S+2j+5EBaP8c6
lBg2XrzNYi4fEVWgHMhZXfcVC8T5zvixd2FI3P2MH9qiu9lw7Qf5j2VaYD9TPwCU
tOmscU5SHiKQ/hsgs0DXu/SOKViSac7sZBtM7iDSoIMBemfzJgqQxmpRqjIpFU4U
iXBQr+hZOHsTgXfJSd84TOMSjLzUD6yqG30MG9Jo0glUP8dSWq+2C/425nPnFFWH
C0EopjcDKUHqsYp707dVQ7V7toyvaL+xD7b++aGQNA+D27xcuhRt9keyWg2Ql6zH
NJGkiGcYXTuno3N7oBr3nZQdBVYFs3SS/TQb9JxgSVfh8TMNaM4eVe73yPh71xnp
EazFzAONSO

Processed: Bug#974063 marked as pending in postgresql

Processing control commands:

> tag -1 pending
Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure
Ignoring request to alter tags of bug #974063 to the same tags previously set

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

Bug#974063: marked as pending in postgresql

Control: tag -1 pending

Hello,

Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/81c484aa82ae21202e7219419fece8d4dbc291b6

New upstream version.

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/974063

Processed: Re: sylfilter: glib error prevent filter working

Processing control commands:

> tags -1 - a11y
Bug #962615 [sylfilter] sylfilter: glib error prevent filter working
Removed tag(s) a11y.
> notfound -1 0.8-6
Bug #962615 [sylfilter] sylfilter: glib error prevent filter working
No longer marked as found in versions sylfilter/0.8-6.
> severity -1 important
Bug #962615 [sylfilter] sylfilter: glib error prevent filter working
Severity set to 'important' from 'grave'

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

Bug#962615: sylfilter: glib error prevent filter working

2020-11-10 Thread Hideki Yamane

control: tags -1 - a11y
control: notfound -1 0.8-6
control: severity -1 important

 Not sure what reason, sylfilter's db was corrupt and it was not
 introduced in this version, and it doesn't always happen so
 downgrade severity.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread Juhani Numminen

Hi,

Maarten L. Hekkelman as the package maintainer asked for my help with bug 
#973526
but I have to forward his request to debian-mentors.

The package libzeep failed to build on amd64, apparently because of a SIGABRT 
during
its HTTP server test. 
https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=amd64&ver=5.0.0-3&stamp=1604607341&raw=0

>> [0;39;49m>> test/http-test.cpp
>> test/http-test.cpp: In member function ‘void connection_read::test_method()’:
>> test/http-test.cpp:74:17: note: ‘#pragma message: write test for avail/used’
>>74 | #pragma message "write test for avail/used"
>>   | ^~~
> building http-test
>> cd test; ./http-test 
>> Running 7 test cases...
>> started daemon at port 5923
>> terminate called after throwing an instance of 
>> 'boost::wrapexcept'
>>   what():  resolve: Host not found (authoritative)
>> unknown location(0): [4;31;49mfatal error: in "webapp_7": signal: SIGABRT 
>> (application abort requested)[0;39;49m
>> test/http-test.cpp(122): [1;36;49mlast checkpoint: "webapp_7" test 
>> entry[0;39;49m
>> started daemon at port 3364
>> terminate called recursively
>> unknown location(0): [4;31;49mfatal error: in "server_with_security_1": 
>> signal: SIGABRT (application abort requested)[0;39;49m
>> test/http-test.cpp(159): [1;36;49mlast checkpoint: "server_with_security_1" 
>> test entry[0;39;49m

There is an example of a successful build for arm64 log here:
https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=arm64&ver=5.0.0-3&stamp=1604618196&raw=0

What might the issue be and how to fix this FTBFS?


Regards,
Juhani Numminen

Bug#972776: marked as done (talloc ftbfs with python3.9)

Your message dated Tue, 10 Nov 2020 15:19:11 +
with message-id 
and subject line Bug#972776: fixed in talloc 2.3.1-2
has caused the Debian Bug report #972776,
regarding talloc 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.)


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

talloc ftbfs with python3.9 (python3-defaults from experimental). Looks like
hard-coding a specific python version.

https://people.debian.org/~ginggs/python3.9-default/talloc_2.3.1-1build1_amd64-2020-10-22T15:04:42Z.build

   debian/rules override_dh_install
make[1]: Entering directory '/<>'
DEB_PY3_INCDIR=/usr/include/python3.9 \
dh_install
dh_install: warning: Cannot find (any matches for)
"usr/lib/*/libpytalloc-util.cpython-38-*.so.*" (tried in ., debian/tmp)

dh_install: warning: python3-talloc missing files:
usr/lib/*/libpytalloc-util.cpython-38-*.so.*
dh_install: error: missing files, aborting
--- End Message ---
--- Begin Message ---
Source: talloc
Source-Version: 2.3.1-2
Done: Mathieu Parent 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Nov 2020 15:56:06 +0100
Source: talloc
Architecture: source
Version: 2.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Samba Maintainers 
Changed-By: Mathieu Parent 
Closes: 972776
Changes:
 talloc (2.3.1-2) unstable; urgency=medium
 .
   * d/python3-talloc.symbols: generating so suffix (Closes: #972776)
   * Update watch file format version to 4.
   * Move to debhelper-compat 13
   * d/copyright: Fix duplicate-globbing-patterns
Checksums-Sha1:
 a246fcb2dcb89aa6aa6e94599cd27a8f1c3e3dee 2253 talloc_2.3.1-2.dsc
 e18367239f1434a27475b2e50027c91bf96f0542 12652 talloc_2.3.1-2.debian.tar.xz
 31ff3207a9a720b194689527c54db4ca3611e893 6536 talloc_2.3.1-2_source.buildinfo
Checksums-Sha256:
 d01b04cd0cb2b864e08d7edfb59ee5a05e730b3c2e8f9f4cf20a521f6683f9fb 2253 
talloc_2.3.1-2.dsc
 201906ea696b47b915f3c31d248a654a1be14102f90937228f156f58cf68c509 12652 
talloc_2.3.1-2.debian.tar.xz
 d72c05b61bf05a4e7f714217352b529ed468160f6e286d684eb48117acefb2ca 6536 
talloc_2.3.1-2_source.buildinfo
Files:
 4b6e0a2cdf784a445c47ad382aa2d679 2253 devel optional talloc_2.3.1-2.dsc
 f4f08ba84e9e9ead7b7637b18742c92e 12652 devel optional 
talloc_2.3.1-2.debian.tar.xz
 39553979236d242e5d04e40bd195ec3e 6536 devel optional 
talloc_2.3.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEqqWLhC6ILPQU4Lqxp8cqHHgrjD8FAl+qqwYTHHNhdGhpZXVA
ZGViaWFuLm9yZwAKCRCnxyoceCuMP7VaD/9AtDcjcpWuWiCt4uE8QzQAhcC+Ye/o
3FBDMRVP4kLYjvvmTKhetp31jX7MqDHgYsOZsIPMcTnIkDryh9Ium/cg/TW2TtTq
knbUh50SZv66zK2l2C74837tx7O8XSRSKnpjL7DVnt+pDsTujHjEh9zqozE0CeF5
OrKVRfJM3EF2TlWOOgedfuPO8xgYIM8IBqbQSfcmaaf3vB8gBoQhESWrN/RkkG6Q
zX5ehf4dy8b8KWaiNdFi478pgw5yEg3Rz94RVnnyWt7fdKg49A9+3mZ3nc/ySJ7m
yd228e4u8WkuWMfi6D55gep5nma+2wv0GjP2yPyJUFSoLi07Kon0pN0BJojdRapv
TDsahHfEmR6M1t6r7WbEPhg1QBriivtgaWM/+7hxpM8uiTGevLg5Ej8d7BEm8nD0
NZxKgZ+mjmCeF2QsLW9uxlsDZ3jj9iy9hknnDH8AVpjTy+qdnatxJM/jansIk3wC
v4iBiI/DqNi/2J/ComCfm6551vx21jya31iSC2NXR0z5vusgJ1JHbiDCCNcqRZ0X
Oi+34N9HYJpbpd61jm5UzzcrqQF/4yp3mZlTn2/NfsOUxIlW/G0Y48x2w0LDRgpC
TI7lhiXlhJcSjf+uRU0BIU0yOSkoxH/q5k8+/YV0tJgEWacH+EiOjqkJTb5Jtmp7
3zdnlMwuNLkN+A==
=k3Qk
-END PGP SIGNATURE End Message ---

Bug#973526: marked as done (libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test")

Your message dated Tue, 10 Nov 2020 15:18:53 +
with message-id 
and subject line Bug#973526: fixed in libzeep 5.0.1-1
has caused the Debian Bug report #973526,
regarding libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test"
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.)


-- 
973526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libzeep
Version: 5.0.5-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

libzeep fails to build on the arch: all buildds with test failures:

| >>> building http-test
| cd test; ./http-test 
| Running 7 test cases...
| started daemon at port 1838
| terminate called after throwing an instance of 
'boost::wrapexcept'
|   what():  resolve: Host not found (authoritative)
| unknown location(0): [4;31;49mfatal error: in "webapp_7": signal: SIGABRT 
(application abort requested)[0;39;49m
| test/http-test.cpp(122): [1;36;49mlast checkpoint: "webapp_7" test 
entry[0;39;49m
| started daemon at port 5983
| terminate called recursively
| unknown location(0): [4;31;49mfatal error: in "server_with_security_1": 
signal: SIGABRT (application abort requested)[0;39;49m
| test/http-test.cpp(159): [1;36;49mlast checkpoint: "server_with_security_1" 
test entry[0;39;49m
|
| [1;31;49m*** 2 failures are detected in the test module "HTTP_Test"
| [0;39;49mmake[3]: *** [GNUmakefile:212: http-test] Error 201
| make[3]: Leaving directory '/<>/lib-http'

See
https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=all&ver=5.0.0-2&stamp=1603985119&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libzeep
Source-Version: 5.0.1-1
Done: maar...@hekkelman.com (Maarten L. Hekkelman)

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

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

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

Debian distribution maintenance software
pp.
Maarten L. Hekkelman  (supplier of updated libzeep 
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, 09 Nov 2020 10:04:29 +0100
Source: libzeep
Architecture: source
Version: 5.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Maarten L. Hekkelman 
Closes: 973526
Changes:
 libzeep (5.0.1-1) unstable; urgency=medium
 .
   * Fix writing HTML, proper empty elements
   * Fix endian issue in SHA algorithm
   * more robust http tests
   * Fix FTBFS: (Closes: #973526)
Checksums-Sha1:
 583c8d72492d113735b932e2873ecd910f0eb065 2263 libzeep_5.0.1-1.dsc
 e5b24e78075916c4fef4a2478d24e758c0740f39 1281655 libzeep_5.0.1.orig.tar.gz
 ac8006cd6ef9342b0cf8d7110a1dd9da9d364c90 5100 libzeep_5.0.1-1.debian.tar.xz
 78e314c78e159a4ab7f00531853a0fb94d93b327 9262 libzeep_5.0.1-1_amd64.buildinfo
Checksums-Sha256:
 67a874f4112c67083b9da9486e1dcf795683800efb8e99b04f7e406e918474af 2263 
libzeep_5.0.1-1.dsc
 45c37598ca7d9f2e5b2380ee3d1349a85e6a6b44e08c9ba0631bb13abd947c1b 1281655 
libzeep_5.0.1.orig.tar.gz
 8d9a2e0fc876410caa32a6b019a4929a79a9c35cf996ea256f89f7ba3b0b57df 5100 
libzeep_5.0.1-1.debian.tar.xz
 844f2b595c519bbf03ebfbdeca3315ed92201e9d3ff5313c8a72ed066696fbdd 9262 
libzeep_5.0.1-1_amd64.buildinfo
Files:
 9ad88b62166062d571efedb8975570da 2263 libs optional libzeep_5.0.1-1.dsc
 488d4d321ef99b42c6f62fa7dbd34bfd 1281655 libs optional 
libzeep_5.0.1.orig.tar.gz
 b4a47017eedef0e21a40363b64bc0e7d 5100 libs optional 
libzeep_5.0.1-1.debian.tar.xz
 213e91e91e5ae6656039a63a12f65222 9262 libs optional 
libzeep_5.0.1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+qqW0RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGQfg/6AxRmm1vjpc6fHMHmlYOydbWhH4Y8sS7f
wdIL3y6s9a3CaMU1fkJhGh8wS7OqGViutLeer/opBZGKsu1dS0X3PtUqCfrqG6KU
eme3LxVYUP/YBLwy38JKl0ntJ40pt1OhZ7JkpiJZwMNpSV9oMSjGJ6VOj4qRMtGN
b3LrKAwDEzmh4p/3vIoNPNiZ4GK+bQjy2BSjS8MVM/p+rBDSC3Oh/38WDSL8mQbo
st2LzgxqHzgiBMVpy4uu18bY8LVCpXE2rnVgIV4w/mbHa6Nl2D8L3Kp1+w4BG60l
zyTV87Wz

Bug#973084: marked as done (docker.io: FTBFS: vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package "github.com/cpuguy83/go-md2man/md2man")

Your message dated Tue, 10 Nov 2020 15:18:29 +
with message-id 
and subject line Bug#973084: fixed in docker.io 19.03.13+dfsg1-4
has caused the Debian Bug report #973084,
regarding docker.io: FTBFS: vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: 
cannot find package "github.com/cpuguy83/go-md2man/md2man"
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.)


-- 
973084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: docker.io
Version: 19.03.13+dfsg1-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[2]: Entering directory 
> '/<>/.gopath/src/github.com/docker/cli'
> ./scripts/build/dynbinary
> Building dynamically linked build/docker-linux-amd64
> scripts/docs/generate-man.sh
> vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package 
> "github.com/cpuguy83/go-md2man/md2man" in any of:
>   
> /<>/.gopath/src/github.com/docker/cli/vendor/github.com/cpuguy83/go-md2man/md2man
>  (vendor tree)
>   /usr/lib/go-1.15/src/github.com/cpuguy83/go-md2man/md2man (from $GOROOT)
>   /<>/.gopath/src/github.com/cpuguy83/go-md2man/md2man (from 
> $GOPATH)
> make[2]: *** [Makefile:76: manpages] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/docker.io_19.03.13+dfsg1-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 ---
Source: docker.io
Source-Version: 19.03.13+dfsg1-4
Done: Arnaud Rebillout 

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

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

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

Debian distribution maintenance software
pp.
Arnaud Rebillout  (supplier of updated docker.io 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Nov 2020 21:31:26 +0700
Source: docker.io
Architecture: source
Version: 19.03.13+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Arnaud Rebillout 
Changed-By: Arnaud Rebillout 
Closes: 973084
Changes:
 docker.io (19.03.13+dfsg1-4) unstable; urgency=medium
 .
   * Fix FTBFS due to go-md2man v2 (Closes: #973084)
Checksums-Sha1:
 f900ed5b402df75238dfa15103573e70461713a0 8670 docker.io_19.03.13+dfsg1-4.dsc
 3bd9eace3e4d8ff45a40023a0da60a2d4d28 53340 
docker.io_19.03.13+dfsg1-4.debian.tar.xz
 60466958b0b9b95ca55e072b3d04248a85a9a539 25803 
docker.io_19.03.13+dfsg1-4_amd64.buildinfo
Checksums-Sha256:
 2eb4ec07c8efc73b40c8606d8b1063e4a437f4910afc4f871bc92504e65ec565 8670 
docker.io_19.03.13+dfsg1-4.dsc
 b993b46325be0457fa09d93e0881fa7c4ee382d29d9ce3de3b05d89befcc718e 53340 
docker.io_19.03.13+dfsg1-4.debian.tar.xz
 eab00cfcccfe8b026386e49dc166f8f77c56199b1ce57ff10cbc29c3b1a89541 25803 
docker.io_19.03.13+dfsg1-4_amd64.buildinfo
Files:
 2b12b1a7f7958f54452e11c0ae5f283b 8670 admin optional 
docker.io_19.03.13+dfsg1-4.dsc
 3359489049913dbab36c7dd35df30b82 53340 admin optional 
docker.io_19.03.13+dfsg1-4.debian.tar.xz
 e8353c6911bd4cbd06bfd3ceaac06cac 25803 admin optional 
docker.io_19.03.13+dfsg1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAl+qqasXHGVsYm91bGFu
Z2Vyb0BnbWFpbC5jb20ACgkQ5yXoeRRgAhacVxAAmFAYtpKtjHChP3PSKeyA1ofY
olgbqOKjDJ97gGUCuZL8KPVIf3MICN5qwIH5LwFZZYY+HZttahpxvXKctDvzBulS
iZxvCZNYvScKGFkA94sysMKt7dYoUDm8huCuxU5IdhmqDRTJH/FbFfphTdykkvid
HtUoXKOQKaTy+RJRMM1Z61audT4YeKLTdY8eExiZM/JUT//6Okw5HkXSHO0VT/VU
UgZz1mccb6hv1J3Oen6BY3xOz6bK9vD2PFkc/bLmvcc6iOJwnPt8JrhzcPe4uAHe
8MIYCfJPoht6MwaJnRlSOdmEe8ECNdRxC9qZav15gEWTLFmZpZ+P+AQOAqizPXdx
tlAotncz7cdmNYQvrhNe4KgMrjpc3aBtpD3RivqAyzwSnlblDVUDGjjjcLZMHxY8
E1yniyP/sOWoHH

Bug#970136: marked as done (fcitx5-hangul: icon clashes with fcitx-hangul)

Your message dated Tue, 10 Nov 2020 15:18:37 +
with message-id 
and subject line Bug#970136: fixed in fcitx5-hangul 5.0.0-1
has caused the Debian Bug report #970136,
regarding fcitx5-hangul: icon clashes with fcitx-hangul
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.)


-- 
970136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fcitx5-hangul
Version: 0.0~git20200609.1c924d4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Preparing to unpack .../fcitx5-hangul_0.0~git20200609.1c924d4-1_amd64.deb ...
  Unpacking fcitx5-hangul:amd64 (0.0~git20200609.1c924d4-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/fcitx5-hangul_0.0~git20200609.1c924d4-1_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/share/icons/hicolor/48x48/status/fcitx-hanja-active.png', which is also 
in package fcitx-hangul:amd64 0.3.1-3
  Errors were encountered while processing:
   /var/cache/apt/archives/fcitx5-hangul_0.0~git20200609.1c924d4-1_amd64.deb

These files are shipped by both packages:

usr/share/icons/hicolor/48x48/status/fcitx-hanja-active.png
usr/share/icons/hicolor/48x48/status/fcitx-hanja-inactive.png
usr/share/icons/hicolor/64x64/apps/fcitx-hangul.png


cheers,

Andreas


fcitx-hangul=0.3.1-3_fcitx5-hangul=0.0~git20200609.1c924d4-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: fcitx5-hangul
Source-Version: 5.0.0-1
Done: Shengjing Zhu 

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

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

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

Debian distribution maintenance software
pp.
Shengjing Zhu  (supplier of updated fcitx5-hangul package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 10 Nov 2020 23:02:32 +0800
Source: fcitx5-hangul
Architecture: source
Version: 5.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Shengjing Zhu 
Closes: 970136
Changes:
 fcitx5-hangul (5.0.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
   * Bump fcitx5 to 5.0.0
   * Add appstream to Build-Depends
   * Rename icon with fcitx5 prefix (Closes: #970136)
Checksums-Sha1:
 7f59030bf842b85ef788e1babd4ec4ad2514d5c6 1507 fcitx5-hangul_5.0.0-1.dsc
 8192920953103c1130f7f08e2e8dc31279a3f33c 29136 fcitx5-hangul_5.0.0.orig.tar.gz
 af47990307c881dbaa98d86fb0e862b37b641897 3128 
fcitx5-hangul_5.0.0-1.debian.tar.xz
 a6ee6e38dbb460c31dd2b5c61adc92edb900808d 7747 
fcitx5-hangul_5.0.0-1_amd64.buildinfo
Checksums-Sha256:
 954e1d7d2b321280c70bf0094d559c0341a2ed97d6e5adb91ff293b3f47b7669 1507 
fcitx5-hangul_5.0.0-1.dsc
 929325424f450e7aa207ac87daff79c1c76ed67a545411fdb8b12f74c02d32da 29136 
fcitx5-hangul_5.0.0.orig.tar.gz
 c74437aee7d245ff52d1c75d001bb817cfb357b0c0430500dd6b43ec960529d0 3128 
fcitx5-hangul_5.0.0-1.debian.tar.xz
 fe85f86c5812939bfda988c4fa9a2d8ff4a9147d6610af808da867689e92d45a 7747 
fcitx5-hangul_5.0.0-1_amd64.buildinfo
Files:
 197acf4d68e2769815902b54691e9618 1507 utils optional fcitx5-hangul_5.0.0-1.dsc
 0214515e1009a3beea39c4b62e3a57eb 29136 utils optional 
fcitx5-hangul_5.0.0.orig.tar.gz
 74e48d33d69118dc0e05455704c41788 3128 utils optional 
fcitx5-hangul_5.0.0-1.debian.tar.xz
 ff6443e049006defea40c1505c8e0a4d 7747 utils optional 
fcitx5-hangul_5.0.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iIYEARYIAC4WIQTiXc95jUQrjt9HgU3EhUo4GOCwFgUCX6qsXxAcemhzakBkZWJp
YW4ub3JnAAoJEMSFSjgY4LAWe50A/jrYRG1Jcw4iZUqX6Zad6qcIEFzs9IgHtm33
O0nw0zBBAP9vP4HAsHhWBoOtkkX2eehoWCxH6OUgWe7OuF0Jfhs6Dg==
=fS4w
-END PGP SIGNATURE End Message ---

Bug#973115: marked as done (cfgrib: FTBFS: tests failed)

Your message dated Tue, 10 Nov 2020 15:18:20 +
with message-id 
and subject line Bug#973115: fixed in cfgrib 0.9.8.4-2
has caused the Debian Bug report #973115,
regarding cfgrib: FTBFS: tests failed
to be marked as done.

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

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


-- 
973115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973115
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfgrib
Version: 0.9.8.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):
> make[1]: Entering directory '/<>'
> for p in python3.9 python3.8; do \
> PY3VERNUM=`echo $p | sed -e 's/python//' `; \
>   pybuild --test --test-pytest -i $p -p $PY3VERNUM  ;  \
> done
> I: pybuild base:217: cd /<>/.pybuild/cpython3_3.9_cfgrib/build; 
> python3.9 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.9.0+, pytest-4.6.11, py-1.9.0, pluggy-0.13.0
> rootdir: /<>, inifile: setup.cfg
> collected 122 items / 1 skipped / 121 selected
> 
> tests/test_10_bindings.py    [ 
> 19%]
> tests/test_10_cfunits.py .   [ 
> 20%]
> tests/test_20_cfcoords.py .. [ 
> 25%]
> tests/test_20_main.py .  [ 
> 26%]
> tests/test_20_messages.py .  [ 
> 33%]
> tests/test_25_cfmessage.py . [ 
> 37%]
> tests/test_30_dataset.py ... [ 
> 53%]
> tests/test_40_xarray_store.py ...[ 
> 59%]
> tests/test_40_xarray_to_grib_regular_ll.py FF.FF [ 
> 63%]
> tests/test_50_datamodels.py ..   [ 
> 64%]
> tests/test_50_sample_data.py FFxxFFFxF   [ 
> 91%]
> tests/test_50_xarray_getitem.py ..   
> [100%]
> 
> === FAILURES 
> ===
> ___ test_canonical_dataarray_to_grib_with_grib_keys 
> 
> 
> canonic_da =  5, longitude: 6)>
> array([0., 0., 0., 0., 0., 0.],...   (latitude) float64 90.0 45.0 0.0 
> -45.0 -90.0
>   * longitude  (longitude) float64 0.0 60.0 120.0 180.0 240.0 300.0
> tmpdir = 
> local('/tmp/pytest-of-user42/pytest-5/test_canonical_dataarray_to_gr0')
> 
> def test_canonical_dataarray_to_grib_with_grib_keys(canonic_da, tmpdir):
> out_path = tmpdir.join('res.grib')
> grib_keys = {'gridType': 'regular_ll'}
> with open(str(out_path), 'wb') as file:
> >   xarray_to_grib.canonical_dataarray_to_grib(canonic_da, file, 
> > grib_keys=grib_keys)
> 
> tests/test_40_xarray_to_grib_regular_ll.py:30: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> cfgrib/xarray_to_grib.py:224: in canonical_dataarray_to_grib
> field_values = data_var.sel(**select).values.flat[:]
> /usr/lib/python3/dist-packages/xarray/core/dataarray.py:1143: in sel
> ds = self._to_temp_dataset().sel(
> /usr/lib/python3/dist-packages/xarray/core/dataset.py:2105: in sel
> pos_indexers, new_indexes = remap_label_indexers(
> /usr/lib/python3/dist-packages/xarray/core/coordinates.py:397: in 
> remap_label_indexers
> pos_indexers, new_indexes = indexing.remap_label_indexers(
> /usr/lib/python3/dist-packages/xarray/core/indexing.py:275: in 
> remap_label_indexers
> idxr, new_idx = convert_label_indexer(index, label, dim, method, 
> tolerance)
> /usr/lib/python3/dist-packages/xarray/core/indexing.py:196: in 
> convert_label_indexer
> indexer = index.get_loc(label_value, method=method, tolerance=tolerance)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> self = DatetimeIndex(['2018-01-01 00:00:00', '2018-01-01 12:00:00',
>'2018-01-02 00:00:00', '2018-01-02 12:00:00'],
>   dtype='datetime64[ns]', name='time', freq=None)
> key = 15147648000, method = None, tolerance = None
> 
> def get_loc(self, key, method=None, tolerance=None):
> """
> Get integer location for requested label
> 
> Returns
> ---
> loc : int
> """
> if not is_scalar(key):
>

Processed: unblock 974029 with 961154

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

> unblock 974029 with 961154
Bug #974029 [src:perl] perl: add breaks on packages which were missing 
libpod-parser-perl deps
974029 was blocked by: 961155 961154
974029 was not blocking any bugs.
Removed blocking bug(s) of 974029: 961154
> thanks
Stopping processing here.

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

Processed: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator

Processing control commands:

> block 968912 with -1
Bug #968912 [release.debian.org] transition: perl 5.32
968912 was blocked by: 961157 961154 972275 974134 974021 960863 968913 974055 
974063 964902 974016 961208 961155 974061 961152 972274 974058
968912 was not blocking any bugs.
Added blocking bug(s) of 968912: 974143
> affects -1 libelixirfm-perl
Bug #974143 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest 
regression with Perl 5.32: Useless use of /d modifier in transliteration 
operator
Added indication that 974143 affects libelixirfm-perl

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

Bug#974143: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator

2020-11-10 Thread Niko Tyni

Package: libencode-arabic-perl
Version: 14.2-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.32-transition
Control: block 968912 with -1
Control: affects -1 libelixirfm-perl

It looks like Perl 5.32 caused a regression in the libencode-arabic-perl
(and transitively libelixirfm-perl) autopkgtest checks. The failure
boils down to this:

  # perl -we 'use Encode::Arabic'
  Useless use of /d modifier in transliteration operator at (eval 5) line 6.
  Useless use of /d modifier in transliteration operator at (eval 7) line 6.
  Useless use of /d modifier in transliteration operator at (eval 9) line 6.

Running with 'perl -d' shows these come from

  Useless use of /d modifier in transliteration operator at (eval 
10)[/usr/share/perl5/Encode/Arabic/Habash.pm:163] line 6.
  Useless use of /d modifier in transliteration operator at (eval 
8)[/usr/share/perl5/Encode/Arabic/Parkinson.pm:157] line 6.
  Useless use of /d modifier in transliteration operator at (eval 
6)[/usr/share/perl5/Encode/Arabic/Buckwalter.pm:161] line 6.

Quoting 
https://perldoc.perl.org/perldiag#Useless-use-of-/d-modifier-in-transliteration-operator

  (W misc) You have used the /d modifier where the searchlist has the same 
length as the replacelist.

The difference between Perl versions seems to be that 5.32 has become
smarter about non-ASCII character ranges, as seen with

  # perl -we '$0 =~ tr/\x{0626}-\x{0628}/abc/d'

which warns with 5.32 but not with 5.30.

I'm guessing this changed somewhere around

 https://github.com/Perl/perl5/commits/f34acfecc286f2eff2450db713da005d888a7317

and it looks to me like this is not a regression in Perl and
Encode::Arabic needs to adapt.

Given the transliteration lists are built dynamically in the code, maybe
the thing to do is just to insert some "no warnings 'misc'" declarations
to suppress the warnings.

Alternatively, disabling the autopkgtest check would lower the severity
of this (but note that at least libelixirfm-perl would also need to
be changed.)

The autopkgtest regression makes this a blocker for Perl 5.32 transition.
-- 
Niko Tyni   nt...@debian.org

Processed: Bug#974063 marked as pending in postgresql

Processing control commands:

> tag -1 pending
Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure
Ignoring request to alter tags of bug #974063 to the same tags previously set

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

Processed: Bug#974063 marked as pending in postgresql

Processing control commands:

> tag -1 pending
Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure
Ignoring request to alter tags of bug #974063 to the same tags previously set

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

Bug#974063: marked as pending in postgresql

Control: tag -1 pending

Hello,

Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/d7e9faaf8ea6d925467863c0e1a64d3226ccb31f

New upstream version.

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/974063

Bug#974063: marked as pending in postgresql

Control: tag -1 pending

Hello,

Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/85c08a75f91f351236959a9cc237d985a59dda9c

New upstream version.

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/974063

Processed: Bug#974063 marked as pending in postgresql

Processing control commands:

> tag -1 pending
Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure
Ignoring request to alter tags of bug #974063 to the same tags previously set

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

Bug#974063: marked as pending in postgresql

Control: tag -1 pending

Hello,

Bug #974063 in postgresql 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/postgresql/postgresql/-/commit/91cba7b2b7a6e8dbbbf70fc63102180ab69715a8

New upstream version.

(this message was generated automatically)
--
Greetings

https://bugs.debian.org/974063

Bug#974144: Fails under wayland and fails trying to select a window

2020-11-10 Thread Daniel Leidert

Package: kazam
Version: 1.4.5-4
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I tried kazam. First the errors shown on the command line clearly indicate that
it is not supposed to work with wayland:

(kazam:89108): Wnck-WARNING **: 16:47:15.482: libwnck is designed to work in 
X11 only, no valid display found
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py", line 
111, in cb_button_press_event
screen.force_update()
AttributeError: 'NoneType' object has no attribute 'force_update'

This can be fixed by calling the program with the X11 backend set:

$ GDK_BACKEND=x11 kazam

(JFTR: If either libwnck or kazam is designed to work with x11 only it should
call gdk_set_allowed_backends() at some point).

But even after setting the backend it is impossible to choose a window:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/kazam/frontend/window_select.py", line 
116, in cb_button_press_event
if win.is_visible_on_workspace(workspace) and win.is_in_viewport(workspace):
TypeError: Argument 1 does not allow None as a value

The program actually looks pretty dysfunctional for me at this point. I don't
think this should be shipped with the next stable.

Regards, Daniel


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

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

Versions of packages kazam depends on:
ii  gir1.2-gst-plugins-base-1.0  1.18.1-1
ii  gir1.2-gstreamer-1.0 1.18.1-1
ii  gir1.2-keybinder-3.0 0.3.2-1+b1
ii  gir1.2-wnck-3.0  3.36.0-1
ii  gnome-session-canberra   0.30-7
ii  gstreamer1.0-plugins-base1.18.1-1
ii  gstreamer1.0-plugins-good1.18.1-1
ii  gstreamer1.0-plugins-ugly1.18.1-1
ii  gstreamer1.0-pulseaudio  1.18.1-1
ii  python3  3.8.6-1
ii  python3-cairo1.16.2-4+b1
ii  python3-dbus 1.2.16-4
ii  python3-gi   3.38.0-1+b1
ii  python3-gi-cairo 3.38.0-1+b1
ii  python3-xdg  0.26-3

Versions of packages kazam recommends:
ii  gstreamer1.0-libav  1.18.1-1

kazam suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qt0QACgkQS80FZ8KW
0F1lvQ//ZjHU323yYl2h77L0u5vD/9tpkDxF0nutm892nRHPEEkiJ3coiXDWCTHg
h2jY+lI7a6MwdcQRwYjF9kub2HAVAy4nJAjjOIjhsr8+R1OCSgsrwFhD3g7LBWrT
ermP3XuEUuzteY3L5Y3MYgZsyL+a8o+zsMteDeNX0WiFT5UPNvEwnk7Dbwji8FtU
UyVVdy+H0MdO8+DGC/WgAqbQOX9YMDakDSp45obgwDbjHzp0vIPHzi+wWNoJP/VF
0xxFWpt3Mru8yXLZVpqVK541Bm+HYaWW9qOC78ndV/5tK+OC7S/B3ElSaaL2zmaU
kwS9x+vGxpqCS38jr2ymGepurkJ3JoFyhSQn7yjnpqeDjbYcWjX/dDQtJes2LVHy
gPHabH5G12FPOcp/vIr8HGKdTbYrZCjGjnFxbqNQR0gHkty1gf0tmY60bx//F33I
AkXqMmFAJST3u9c4SMKDVTDxLsGT/PrIeCGoJF61BXbiwF6ic/AaVKRJtZV+wvLw
/HVIkNXRV4Q5+R6ALcESLxO4v98WlQFhXMlzPz6gBQMYmWWDe+7LhiETEjKAW7/X
VhgQFK7RJ34bMP2zgILD1QOCbyILryYImtt9URjdVz1KQJfi71IN9WkZsex+fxBW
0U7IeyL1dJOgkTnZ6sCkugg/ZWK5SxFcPm/YDpgE8Id/EwNYvD4=
=X7HN
-END PGP SIGNATURE-

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread Andrey Rahmatullin

On Tue, Nov 10, 2020 at 05:17:26PM +0200, Juhani Numminen wrote:
> Hi,
> 
> Maarten L. Hekkelman as the package maintainer asked for my help with bug 
> #973526
> but I have to forward his request to debian-mentors.
> 
> The package libzeep failed to build on amd64, apparently because of a SIGABRT 
> during
> its HTTP server test. 
> https://buildd.debian.org/status/fetch.php?pkg=libzeep&arch=amd64&ver=5.0.0-3&stamp=1604607341&raw=0
> 
> >> [0;39;49m>> test/http-test.cpp
> >> test/http-test.cpp: In member function ‘void 
> >> connection_read::test_method()’:
> >> test/http-test.cpp:74:17: note: ‘#pragma message: write test for 
> >> avail/used’
> >>74 | #pragma message "write test for avail/used"
> >>   | ^~~
> > building http-test
> >> cd test; ./http-test 
> >> Running 7 test cases...
> >> started daemon at port 5923
> >> terminate called after throwing an instance of 
> >> 'boost::wrapexcept'
> >>   what():  resolve: Host not found (authoritative)
Looks like it tries to resolve something, and that usually implies
Internet access, as otherwise you could just connect to localhost?
Accessing the Internet is forbidden during building.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#974147: Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead

2020-11-10 Thread Daniel Leidert

Package: gtk-recordmydesktop
Version: 0.3.8-4.1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The application fails to start in Sid due to /usr/bin/python not existing
(anymore). I've asked on the #deian-python channel and got told that using
/usr/bin/python is a bug and when using python2 you have to use
/usr/bin/python2 instead.

Regards, Daniel


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

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

Versions of packages gtk-recordmydesktop depends on:
ii  python   2.7.17-2.0tails1
ii  python-gtk2  2.24.0-5.1+b1
ii  python2.72.7.18-1
ii  recordmydesktop  0.3.8.1+svn602-1.1

gtk-recordmydesktop recommends no packages.

gtk-recordmydesktop suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qu+UACgkQS80FZ8KW
0F1s+BAAg+mpqVdtDmpr/tKXVc0INTotSQuoKGi+5jbUHYDS1hbD8yIYHe6u0buy
cRpJ4xQ1+A5humvFv1H2XtktVA6MG14tSxdC9oc3xuJm1AfDcRSp4JhjwWj9o9iw
7sjGBsE1GopdrQlQFiITnYoUwZ4kOciIEwOwGPb0bQq1iEKLkfanjLArdBrMSCE+
9DuYeAN38BJXj+SsfNKv2xUTo4pxum+vDLqAebtI3HTS+VGgPP8SRQjtICx6EDV/
YgStQHVu8i1kZepFCiL3bcd4ACZIvJDNEpTCVgKiAoSfxSwNmsU8ztmxZPBT/vhD
f6xKTmzzYd9a6jQzmISs59fug0pUq8Vj/ET7HfwzlR559+nVa82jmJnoYQbLZRZF
d+ALQ+OzsU69NVhlsM871B7zxvfn1eQGwRCZpnlOCC24KTRWqKI7qFi7sDDSBwr8
QywZjcz+Omh9EWMTIWJ9MYiAUE2hyEWIi8vi4nT0lM3pFXKAJ/lKIFhIn7ZQGDsP
LbXzUjwhV8jS48bmtxFHhPIF7AOMbL37NMOY1ZtowMcW9OrIU3CfESFOkGyneHnJ
Sonzu8xxvhng+D+Sqd6q8uQRMAX06JfPjBqnSmUkHmu5CITCEAaWER9OfPeK0ns/
IPvpUJgcv/GrkT2AiglJOUjLHLOYUvcsygri+DmP88XifaL2IVg=
=NnaI
-END PGP SIGNATURE-

Processed: block 895037 with 974146

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

> block 895037 with 974146
Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; 
AppIndicator based applications, please switch to Ayatana (App)Indicator(s)
895037 was blocked by: 956779 956762 906026 956770 956767 956764 956765 956777 
956769 956772 956781 956775 956774 956761 956766 956780 921339 956778 956776 
956773 956771 956782 956768
895037 was blocking: 895038
Added blocking bug(s) of 895037: 974146
> thanks
Stopping processing here.

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

Bug#965114: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency

2020-11-10 Thread Nilesh Patra

Control: severity -1 minor


On Tue, 10 Nov 2020 21:39:40 +0530 Nilesh Patra  wrote:
> sbuild (Debian sbuild) 0.79.1 (22 April 2020) on debian
>
>
++
> | golang-github-shenwei356-bwt 0.0~git20200418.ae79c98-2 (amd64) Tue, 10
Nov 2020 15:55:30 + |
> +===�

Processed: Re: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency

Processing control commands:

> severity -1 minor
Bug #965114 [golang-github-shenwei356-bwt] golang-github-shenwei356-bwt: FTBFS: 
unsatisfiable build dependency
Severity set to 'minor' from 'serious'

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

Bug#974147: marked as done (Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead)

Your message dated Tue, 10 Nov 2020 17:24:07 +0100
with message-id <460916417ee5208abee138ce2933da30f1cb60d0.ca...@debian.org>
and subject line Severity downgrade - not in Sid
has caused the Debian Bug report #974147,
regarding Script doesn't start due to /usr/bin/python being obsolete: must use 
/usr/bin/python2 instead
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.)


-- 
974147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gtk-recordmydesktop
Version: 0.3.8-4.1
Severity: grave

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The application fails to start in Sid due to /usr/bin/python not existing
(anymore). I've asked on the #deian-python channel and got told that using
/usr/bin/python is a bug and when using python2 you have to use
/usr/bin/python2 instead.

Regards, Daniel


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

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

Versions of packages gtk-recordmydesktop depends on:
ii  python   2.7.17-2.0tails1
ii  python-gtk2  2.24.0-5.1+b1
ii  python2.72.7.18-1
ii  recordmydesktop  0.3.8.1+svn602-1.1

gtk-recordmydesktop recommends no packages.

gtk-recordmydesktop suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl+qu+UACgkQS80FZ8KW
0F1s+BAAg+mpqVdtDmpr/tKXVc0INTotSQuoKGi+5jbUHYDS1hbD8yIYHe6u0buy
cRpJ4xQ1+A5humvFv1H2XtktVA6MG14tSxdC9oc3xuJm1AfDcRSp4JhjwWj9o9iw
7sjGBsE1GopdrQlQFiITnYoUwZ4kOciIEwOwGPb0bQq1iEKLkfanjLArdBrMSCE+
9DuYeAN38BJXj+SsfNKv2xUTo4pxum+vDLqAebtI3HTS+VGgPP8SRQjtICx6EDV/
YgStQHVu8i1kZepFCiL3bcd4ACZIvJDNEpTCVgKiAoSfxSwNmsU8ztmxZPBT/vhD
f6xKTmzzYd9a6jQzmISs59fug0pUq8Vj/ET7HfwzlR559+nVa82jmJnoYQbLZRZF
d+ALQ+OzsU69NVhlsM871B7zxvfn1eQGwRCZpnlOCC24KTRWqKI7qFi7sDDSBwr8
QywZjcz+Omh9EWMTIWJ9MYiAUE2hyEWIi8vi4nT0lM3pFXKAJ/lKIFhIn7ZQGDsP
LbXzUjwhV8jS48bmtxFHhPIF7AOMbL37NMOY1ZtowMcW9OrIU3CfESFOkGyneHnJ
Sonzu8xxvhng+D+Sqd6q8uQRMAX06JfPjBqnSmUkHmu5CITCEAaWER9OfPeK0ns/
IPvpUJgcv/GrkT2AiglJOUjLHLOYUvcsygri+DmP88XifaL2IVg=
=NnaI
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi there,

I missed that your package is neither in Sid nor Testing. So you can ignore the
bug and I'll close it.

Regards, Daniel
-- 
Regards,
Daniel Leidert  | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78

If you like my work consider sponsoring me via
https://www.patreon.com/join/dleidert


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

Bug#974143: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator

2020-11-10 Thread gregor herrmann

On Tue, 10 Nov 2020 15:26:43 +, Niko Tyni wrote:

> Given the transliteration lists are built dynamically in the code, maybe
> the thing to do is just to insert some "no warnings 'misc'" declarations
> to suppress the warnings.

Some random notes:

1) popcon:
installed: 9 = vote: 1 + old: 7 + recent: 1 + no_files: 0

2) The following trivial patch makes the autopkgtest pass:

#v+
--- a/lib/Encode/Arabic/Buckwalter.pm
+++ b/lib/Encode/Arabic/Buckwalter.pm
@@ -158,6 +158,9 @@
 
 undef &encoder;
 
+# https://bugs.debian.org/974143
+no warnings 'misc';
+
 eval q /
 
 sub encoder ($) {
--- a/lib/Encode/Arabic/Habash.pm
+++ b/lib/Encode/Arabic/Habash.pm
@@ -160,6 +160,9 @@
 
 undef &encoder;
 
+# https://bugs.debian.org/974143
+no warnings 'misc';
+
 eval q /
 
 sub encoder ($) {
--- a/lib/Encode/Arabic/Parkinson.pm
+++ b/lib/Encode/Arabic/Parkinson.pm
@@ -154,6 +154,9 @@
 
 undef &encoder;
 
+# https://bugs.debian.org/974143
+no warnings 'misc';
+
 eval q /
 
 sub encoder ($) {
#v-

3a) This also turns off other warnings (obviously, the whole 'misc'
category);
3b) but actually the code blocks end after this operation so there
shouldn't be much left of ignored warnings  …



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: Bettina Wegner: Meinetwegen


signature.asc
Description: Digital Signature

Bug#973123: marked as done (idzebra: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

Your message dated Tue, 10 Nov 2020 16:50:04 +
with message-id 
and subject line Bug#973123: fixed in idzebra 2.2.2-1
has caused the Debian Bug report #973123,
regarding idzebra: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
to be marked as done.

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

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


-- 
973123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: idzebra
Version: 2.1.4-4
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[4]: Entering directory '/<>/bfile'
> ../config/test-driver: line 107: 31001 Segmentation fault  "$@" > 
> $log_file 2>&1
> PASS: tstmfile1
> FAIL: tstbfile1
> PASS: tstbfile2
> =
>idzebra 2.1.4: bfile/test-suite.log
> =
> 
> # TOTAL: 3
> # PASS:  2
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: tstbfile1
> ===
> 
> 12:26:17-27/10 [log] tstbfile1.c:172 ok: 
> 12:26:17-27/10 [log] bfs
> 12:26:17-27/10 [log] tstbfile1.c:37 ok: 
> 12:26:17-27/10 [log] bf
> 12:26:17-27/10 [log] tstbfile1.c:45 ok: 
> 12:26:17-27/10 [log] bf
> FAIL tstbfile1 (exit status: 139)
> 
> 
> Testsuite summary for idzebra 2.1.4
> 
> # TOTAL: 3
> # PASS:  2
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See bfile/test-suite.log
> Please report to zebra-h...@indexdata.dk
> 
> make[4]: *** [Makefile:741: test-suite.log] Error 1
> make[4]: Leaving directory '/<>/bfile'
> make[3]: *** [Makefile:849: check-TESTS] Error 2
> make[3]: Leaving directory '/<>/bfile'
> make[2]: *** [Makefile:937: check-am] Error 2
> make[2]: Leaving directory '/<>/bfile'
> make[1]: *** [Makefile:481: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/idzebra_2.1.4-4_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Hugh McMaster  (supplier of updated idzebra package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Nov 2020 22:32:15 +1100
Source: idzebra
Architecture: source
Version: 2.2.2-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Danjean 
Changed-By: Hugh McMaster 
Closes: 973123
Changes:
 idzebra (2.2.2-1) unstable; urgency=medium
 .
   * New upstream version:
 - Upstream has removed the test 'tstbfile1', which failed intermittently,
   causing build failures (Closes: #973123).
 - Instances removed in idzebra 2.2.1 (not released in Debian) have been
   reinstated. These were bf_alloc, bf_free, bf_xopen and bf_xclose.
   * debian/control:
 - Build-Depend on libyaz-dev >= 5.29.0 and zlib1g-dev.
 - Sort package Depends lists and unify formatting.
 - Sort package stanzas.
 - Add Depends packages to libidzebra-2.0-dev.
   * Drop encoding.patch and idzebra-clean.patch. Both were accepted upstream.
   * Add a sup

Bug#943037: git-hub: Python2 removal in sid/bullseye

2020-11-10 Thread Leandro Lucarella

New major version is compatible with Python3, please see https://
github.com/sociomantic-tsunami/git-hub/releases/tag/v2.0.1 for the current 
latest release.

-- 
Leandro Lucarella (Luca)
https://llucax.com

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

Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Steinar H. Gunderson

Package: fonts-noto-mono
Version: 20201027-3
Severity: grave

Hi,

For unknown reasons, Noto Mono looks completely different after
I upgraded my unstable machines recently, to the point that it's
not the same font anymore (for one, it has serifs). This affects
multiple machines, both rxvt-unicode and gnome-terminal, both
X11 and Wayland, and goes away if I downgrade. Compare the stable
and unstable fonts below (the version of fonts-noto-mono installed
when urxvt started is the sole difference between the two windows):

  https://home.samfundet.no/~sesse/noto-mono.png

The upper (stable) also matches what the font looks like if I
look at https://www.google.com/get/noto/#mono-mono. You can see
some fragments of it in the screenshot; look at e.g. the lowercase
g.

gnome-terminal doesn't even list Noto Mono in its list of available
fonts, so I'm wondering if it does some sort of fallback and that
the font just is completely broken somehow.

Bug#974021: marked as done (kvirc FTBFS: error: aggregate ‘QPainterPath sP’ has incomplete type and cannot be defined)

Your message dated Tue, 10 Nov 2020 18:03:49 +
with message-id 
and subject line Bug#974021: fixed in kvirc 4:5.0.0+dfsg-4
has caused the Debian Bug report #974021,
regarding kvirc FTBFS: error: aggregate ‘QPainterPath sP’ has incomplete type 
and cannot be defined
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.)


-- 
974021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kvirc
Version: 4:5.0.0+dfsg-3
Severity: serious
Tags: ftbfs

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

...
/<>/src/modules/iograph/libkviiograph.cpp: In member function 
‘virtual void KviIOGraphWidget::paintEvent(QPaintEvent*)’:
/<>/src/modules/iograph/libkviiograph.cpp:225:15: error: aggregate 
‘QPainterPath sP’ has incomplete type and cannot be defined
  225 |  QPainterPath sP, rP;
  |   ^~
/<>/src/modules/iograph/libkviiograph.cpp:225:19: error: aggregate 
‘QPainterPath rP’ has incomplete type and cannot be defined
  225 |  QPainterPath sP, rP;
  |   ^~
make[3]: *** [src/modules/iograph/CMakeFiles/kviiograph.dir/build.make:98: 
src/modules/iograph/CMakeFiles/kviiograph.dir/libkviiograph.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: kvirc
Source-Version: 4:5.0.0+dfsg-4
Done: Dmitry Shachnev 

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

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

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated kvirc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Nov 2020 20:44:22 +0300
Source: kvirc
Architecture: source
Version: 4:5.0.0+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Dmitry Shachnev 
Closes: 974021
Changes:
 kvirc (4:5.0.0+dfsg-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Rik Mills ]
   * debian/patches: Add upstream_fix-build-with-Qt-5.15.patch
 (Closes: #974021).
Checksums-Sha1:
 7f4c3b39ccc84fa4384d467f9cd83ebedd9b3bc3 2633 kvirc_5.0.0+dfsg-4.dsc
 7d514f24c328d3e9becaadbafd07603f9ca62d8d 27208 kvirc_5.0.0+dfsg-4.debian.tar.xz
 388a2d195447b4b71898fcab70dfd5ae9e6b3ae1 18516 
kvirc_5.0.0+dfsg-4_source.buildinfo
Checksums-Sha256:
 d8303d3bbd2fd2fe16b705fc2c978789477d201f0986ddaf608de6bb01f14996 2633 
kvirc_5.0.0+dfsg-4.dsc
 9b373d953cbf2c3ba2bc7a4efe9f115eb0bc5d84bb4a259387e4b1d9be13265f 27208 
kvirc_5.0.0+dfsg-4.debian.tar.xz
 16586ff091cda32fb1032c01ab018236f922a69b87fc6870ef1a349152ddf356 18516 
kvirc_5.0.0+dfsg-4_source.buildinfo
Files:
 15814a63d2390ffb7a099fbd1fa0e798 2633 net optional kvirc_5.0.0+dfsg-4.dsc
 06814ca43c0ef9d8e17fdca586b852b6 27208 net optional 
kvirc_5.0.0+dfsg-4.debian.tar.xz
 f9ce401f9c3a764ca1bb486b2876050c 18516 net optional 
kvirc_5.0.0+dfsg-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAl+q0gATHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy7ldD/0Y2bZRhypKgCje+oW/iHb4gVagG+9V
lhPmBw6Qzf8ixoRbXTlPhbzVj/Wn+qYYPtaiMQHo395ecAe/CvgIdRf3yPX3QQr4
hHT89oTQ898wQ54tETxFUrIRYaQtUL6csLGvvfMgCQJC5bZ85zxhbMx3epiKjC1d
G5yJtru0xEHxAVPy+KjnUPPKRZ3dKHThgASVDeXdOFHiewwD+UC6wa6UZBDXRKU0
Lca61Ejowc42ELOuvUt8a37Nyd+ItkEwaotPni9aQLmq3iIAhVJvYiJug2uVektI
BSWqPTxog/XGNdFGhXK7b7xpUktQ+BVEOpZXhwKiEziUjCcRaJFD5+p59vLAQkTL
4pgNMrmTXvXYtD6chusPNrLu41ZRz5Ic1TN6Gusc9zigFiE83aozVN7LPpnfiJiY
YEFEfgitQ0nWYADNxavHWFMcenmL2dX/z5NatTF/3YzYrZkXBLsROYTx2U4tQkRj
wsXCCuSu/AD1zsyq6JAoXHazyVdydQmHdKkUQHKo9Fb9MTu9I6ZazJ6tyO5oTcQO
Rxg1ViAIK2lRpGRMF4vkkKnVZWlqsc49+wqgGtJsAzgMCHhhnSLw9BgU2wT4zrhO
fY8Gr/RttKoeh9DX50ebgK/2lHqmavU9CL6yEheggS6JLIrsGSsbAOtjFUdosSH7
vjnd2ZTNUaPj9Q==
=vJUY
-END PGP SIGNATURE End Message ---

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Jonas Smedegaard

Hi Steinar,

Quoting Steinar H. Gunderson (2020-11-10 18:42:02)
> Package: fonts-noto-mono
> Version: 20201027-3
> Severity: grave

Why the severity?

Visual changes does not seem reason release-critical to me.

"completely broken" need more than a vague suspicion, IMHO.


> For unknown reasons, Noto Mono looks completely different after I 
> upgraded my unstable machines recently, to the point that it's not the 
> same font anymore (for one, it has serifs). This affects multiple 
> machines, both rxvt-unicode and gnome-terminal, both X11 and Wayland, 
> and goes away if I downgrade. Compare the stable and unstable fonts 
> below (the version of fonts-noto-mono installed when urxvt started is 
> the sole difference between the two windows):
> 
>   https://home.samfundet.no/~sesse/noto-mono.png
> 
> The upper (stable) also matches what the font looks like if I look at 
> https://www.google.com/get/noto/#mono-mono. You can see some fragments 
> of it in the screenshot; look at e.g. the lowercase g.

Google dropped Noto Mono a few years ago.  We kept it alive, until 
recently when Google re-introduced Noto Mono.

The main goal of Noto fonts is large coverage, and second to that is 
coherent style across scripts.  I am not surprised that the 
re-introduced Noto Mono has changed visual style.  I would consider it a 
feature, not a bug.

Google does not maintain a changelog nor do they make proper releases, 
so we are left to guessing about their intents with these fonts.


> gnome-terminal doesn't even list Noto Mono in its list of available 
> fonts, so I'm wondering if it does some sort of fallback and that the 
> font just is completely broken somehow.

If Noto Mono fails to work at all, then that is indeed a severe bug - 
but I would consider that a _different_ bug than "looks completely 
different" as you've framed the subject of this bugreport.

I don't mind treating this bugreport _only_ being about this more severe 
issue, if you prefer - but if you weant to discuss both the visual style 
and the disappearance from some apps, then please file either as a 
separate bugreport.

I am not familiar with gnome-terminal, I only use urxvt myself.

urxvt can be told to use one specific font, but that only really works 
for X11 bitmap fonts - for tryetype fonts it can only beg fontconfig to 
prefer one, like this:

  rxvt-unicode -fn 'xft:Noto Mono'

This shows which actual fonts are most likely used:

  fc-match -s 'Noto Mono' | head -n 5


Thanks for reporting this,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#937234: pam-python/libpam-mklocaluser/debian-edu-config python3 migration.

2020-11-10 Thread Moritz Mühlenhoff

On Sat, Sep 19, 2020 at 06:00:05PM +0100, peter green wrote:
> The debian python maintainers are trying to phase out python 2.
> 
> python 2 has been granted a stay of execution as some important software 
> requires it to build.

In Bullseye Python 2 will only be supported for build deps (using Py2 to build 
the
code or run tests), given that the content of what we ship in a release is 
trusted/known.
This doesn't extend to run time dependencies (and libpam-python depends on 
libpython2.7).

I'll submit updates to debian-security-support and the bullseye release notes 
in the next days.

Cheers,
Moritz

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread gregor herrmann

On Tue, 10 Nov 2020 20:21:10 +0500, Andrey Rahmatullin wrote:

> > >>   what():  resolve: Host not found (authoritative)
> Looks like it tries to resolve something, and that usually implies
> Internet access, as otherwise you could just connect to localhost?
> Accessing the Internet is forbidden during building.

Or if the build ends up one of the ipv6-only buildds where resolving
"localhost" can also fail. (Last example I've encountered: #974033)
 

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: Bettina Wegner: Meinetwegen


signature.asc
Description: Digital Signature

Bug#973508: marked as done (bazel-bootstrap FTBFS)

Your message dated Tue, 10 Nov 2020 19:03:25 +
with message-id 
and subject line Bug#973508: fixed in bazel-bootstrap 3.4.0+ds-2
has caused the Debian Bug report #973508,
regarding bazel-bootstrap FTBFS
to be marked as done.

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

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


-- 
973508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bazel-bootstrap
Version: 3.4.0+ds-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bazel-bootstrap.html
https://buildd.debian.org/status/package.php?p=bazel-bootstrap&suite=sid

...
[1A[K[32m[1,619 / 1,622][0m Executing genrule //src:package-zip_nojdk; 3s 
local

[1A[K[31m[1mERROR: [0m/<>/src/BUILD:326:9: Executing genrule 
//src:package-zip_nojdk failed (Exit 1): bash failed: error executing command 
  (cd /tmp/bazel_6346MX9l/out/execroot/io_bazel && \
  exec env - \
CCACHE_DISABLE=1 \
CCACHE_TEMPDIR=/<>/debian/ccachetmp \

PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \
  /bin/bash -c 'source external/bazel_tools/tools/genrule/genrule-setup.sh; 
bazel-out/aarch64-dbg/bin/src/package-bazel-on-host-platform.sh 
bazel-out/aarch64-dbg/bin/src/package_nojdk.zip  
bazel-out/aarch64-dbg/bin/src/embedded_tools_nojdk.zip 
bazel-out/aarch64-dbg/bin/src/main/java/com/google/devtools/build/lib/bazel/BazelServer_deploy.jar
 bazel-out/aarch64-dbg/bin/src/install_base_key_nojdk 
bazel-out/aarch64-dbg/bin/src/platforms.zip 
bazel-out/aarch64-dbg/bin/src/main/java/com/google/devtools/build/lib/syntax/libcpu_profiler.so
 bazel-out/aarch64-dbg/bin/src/main/native/libunix.so 
bazel-out/aarch64-dbg/bin/src/main/tools/build-runfiles 
bazel-out/aarch64-dbg/bin/src/main/tools/process-wrapper 
src/main/tools/jdk.BUILD bazel-out/aarch64-dbg/bin/src/main/tools/linux-sandbox 
bazel-out/aarch64-dbg/bin/tools/osx/xcode-locator 
bazel-out/aarch64-dbg/bin/src/main/tools/daemonize')
Execution platform: //:default_host_platform
[32m[1,620 / 1,622][0m checking cached actions

[1A[Kcp: failed to access 
'/build/bazel-bootstrap-3.4.0+ds/output/usr/share/bazel': No such file or 
directory
[32m[1,620 / 1,622][0m checking cached actions

[1A[K[32mINFO: [0mElapsed time: 245.830s, Critical Path: 166.09s
[32m[1,620 / 1,622][0m checking cached actions

[1A[K[32mINFO: [0m1586 processes: 906 local, 680 worker.
[32m[1,620 / 1,622][0m checking cached actions

[1A[K[31m[1mFAILED:[0m Build did NOT complete successfully

[1A[K[31m[1mFAILED:[0m Build did NOT complete successfully
[0m
ERROR: Could not build Bazel
make[1]: *** [debian/rules:54: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: bazel-bootstrap
Source-Version: 3.4.0+ds-2
Done: Olek Wojnar 

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

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

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

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated bazel-bootstrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 08 Nov 2020 20:37:29 -0500
Source: bazel-bootstrap
Architecture: source
Version: 3.4.0+ds-2
Distribution: unstable
Urgency: high
Maintainer: Debian Bazel Team 
Changed-By: Olek Wojnar 
Closes: 973508
Changes:
 bazel-bootstrap (3.4.0+ds-2) unstable; urgency=high
 .
   * Fix sandbox path option
   * Change default system bazelrc file location for Debian Bazel
   * Remove Android dependency due to unavailability in Testing
 - Add remove-android-rules.patch
   * Remove phpsysinfo dependency
   * Fix build failure on buildds (Closes: #973508)
Checksums-Sha1:
 039f5c4cb1e07b0d00af8cf03dd24603f475ae90 3445 bazel-bootstrap_3.4.0+ds-2.dsc
 74d9a8a6a32d3399df1ce4b0125d6dab6c9b6915 25744 
bazel-bootstrap_3.4.0+ds-2.debian.tar.xz
 ad046992c173a18d60b17c8ca32c8a5807ea9d28 11101 
bazel-bootstrap_3.4.0+ds-2_amd64.buildinfo
Checksums-Sha256:
 6ef7434a0868a28122ab6f11044944fa6f0f434c9cf73caf2e5dc23c7d712004 3445 
bazel-bootstrap_3.4.0+ds-2.dsc
 5d76ecc7dfe2a2f6f9e1cfa99bcfd4580e807d6dcaf

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Steinar H. Gunderson

On Tue, Nov 10, 2020 at 07:46:55PM +0100, Jonas Smedegaard wrote:
> Why the severity?
> 
> Visual changes does not seem reason release-critical to me.
> 
> "completely broken" need more than a vague suspicion, IMHO.

Feel free to downgrade. The background for the severity: I installed the
package to get a specific font, and that font suddenly disappeared and
was replaced by a completely different font. For me, that's completely
broken. If it's by intention, well... perhaps I'll need to pin the old one
indefinitely, then.

> Google dropped Noto Mono a few years ago.  We kept it alive, until 
> recently when Google re-introduced Noto Mono.

Huh, OK. But why is the web font different from the .ttf, then?
It doesn't make a lot of sense.

If I download the .ttf from https://www.google.com/get/noto/,
it looks like the one in stable. And https://github.com/googlefonts/noto-fonts
doesn't list any “Noto Mono” at all except “Noto Sans Mono”. Where's this new
font coming from?

> This shows which actual fonts are most likely used:
> 
>   fc-match -s 'Noto Mono' | head -n 5

Looks fine for me:

kos:~> fc-match -s 'Noto Mono' | head -n 5  

NotoMono-Regular.ttf: "Noto Mono" "Regular"
Vera.ttf: "Bitstream Vera Sans" "Roman"
DejaVuSans.ttf: "DejaVu Sans" "Book"
DejaVuSans-Bold.ttf: "DejaVu Sans" "Bold"
DejaVuSans-Oblique.ttf: "DejaVu Sans" "Oblique"

> 
> 
> Thanks for reporting this,
> 
>  - Jonas
> 
-- 
Homepage: https://www.sesse.net/

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Jonas Smedegaard

Quoting Steinar H. Gunderson (2020-11-10 20:08:14)
> On Tue, Nov 10, 2020 at 07:46:55PM +0100, Jonas Smedegaard wrote:
> > Why the severity?
> > 
> > Visual changes does not seem reason release-critical to me.
> > 
> > "completely broken" need more than a vague suspicion, IMHO.
> 
> Feel free to downgrade. The background for the severity: I installed 
> the package to get a specific font, and that font suddenly disappeared 
> and was replaced by a completely different font. For me, that's 
> completely broken. If it's by intention, well... perhaps I'll need to 
> pin the old one indefinitely, then.

I am open to the alternative of packaging the old Noto Mono e.g. as 
package fonts-noto-mono-legacy which then conflicts with the new 
fonts-noto-mono package.

...if relevant to preserve two different visual styles.

I am a bit confused if we are tracking one or two bugs here...

Would you still find it relevant to pin the old font even if the new one 
works but simply uses different visual style?

Or rephrased: Is this bugreport not really about different look but 
instead _only_ about font disappearing altogether (and the different 
look just being a possible aid in locating the cause of that other 
bigger problem)?

> > Google dropped Noto Mono a few years ago.  We kept it alive, until 
> > recently when Google re-introduced Noto Mono.
> 
> Huh, OK. But why is the web font different from the .ttf, then? It 
> doesn't make a lot of sense.
> 
> If I download the .ttf from https://www.google.com/get/noto/, it looks 
> like the one in stable. And https://github.com/googlefonts/noto-fonts 
> doesn't list any “Noto Mono” at all except “Noto Sans Mono”. Where's 
> this new font coming from?

Source for Debian package is https://github.com/googlefonts/noto-fonts/ 
- but interestingly, the NotoMono fonts was renamed just 2 days after 
our latest snapshot - with a totally unrevealing commit message of 
"Published NotoTraditionalNushu hinted and unhinted static instances":
https://github.com/googlefonts/noto-fonts/commit/1eda585

Seems Google changed their mind regarding the reuse of font name, and we 
can go back to keeping the old legacy font alive...

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#973472: marked as done (fetchmail: Fails to connect using SSL)

Your message dated Tue, 10 Nov 2020 20:54:22 +0100
with message-id 

and subject line Re: Bug#973472: fetchmail: Fails to connect using SSL
has caused the Debian Bug report #973472,
regarding fetchmail: Fails to connect using SSL
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.)

-- 
973472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fetchmail
Version: 6.4.13-1
Severity: important

Dear Maintainer,

Connections using SSL fails with the following error message :

fetchmail: Loaded OpenSSL library 0x1010107f older than headers 0x1010108f, 
refusing to work.
fetchmail: xxx.domain.com: SSL connection failed.
fetchmail: socket error while fetching from y...@xxx.domain.com
fetchmail: Query status=2 (SOCKET)

It does not seesm that OpenSSL has been renctly updates on my system.

Best wishes,

Alex Bernier

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

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

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

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

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

Versions of packages fetchmail depends on:
ii  adduser   3.118
ii  debianutils   4.11.2
ii  libc6 2.31-4
ii  libcom-err2   1.45.6-1
ii  libgssapi-krb5-2  1.17-10
ii  libkrb5-3 1.17-10
ii  libssl1.1 1.1.1g-1
ii  lsb-base  11.1.0

Versions of packages fetchmail recommends:
ii  ca-certificates  20200601

Versions of packages fetchmail suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.94-8
pn  fetchmailconf  
pn  resolvconf 

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

On Fri, Nov 6, 2020 at 9:09 AM Michal Palenik  wrote:
> for those stumbling on this via searching, the workaround mentioned
> above is:
[...]
> apt -t unstable install libssl1.1:amd64
 Thanks for possibly the best solution. Meanwhile OpenSSL 1.1.1h-1
migrated to testing; closing this bug report.

Regards,
Laszlo/GCS--- End Message ---

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

2020-11-10 Thread Paul Gevers

Hi Aloïs,

On 10-11-2020 00:38, Aloïs Micard wrote:
> I've uploaded a new version of golang-github-pkg-term [1], and by
> doing so, broke the build of golang-github-c-bata-go-prompt [2] &
> golang-github-jaguilar-vt100 [3].

Ack. So, the new golang-github-pkg-term Breaks the version of
golang-github-c-bata-go-prompt and golang-github-jaguilar-vt100 in
testing? Then, declare that. Or doesn't "broke the build" imply that?

> I've updated the packaging of the later two, and uploaded them to
> unstable, where the build of the 3 packages now succeed [4][5][6].
> 
> But sadly, the migration to testing for golang-github-pkg-term
> won't happen because it would break the testing build of
> golang-github-pkg-term & golang-github-c-bata-go-prompt.
> 
> In the meantime, these packages won't migrate to testing because
> golang-github-pkg-term is not migrating.
> 
> I don't know what kind of fix I should made to allow these packages
> to migrate to testing.
> 
> Have you an idea?

Fix the package relations. If the new version of something breaks the
old version of something else, it should declare that with a versioned
Breaks.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#974036: marked as done (Fails to build on mips64el)

Your message dated Tue, 10 Nov 2020 19:55:16 +
with message-id 
and subject line Bug#974036: fixed in squeekboard 1.10.0-2
has caused the Debian Bug report #974036,
regarding Fails to build on mips64el
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.)


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

squeekboard fails to build on mips64el like:

[16/58] /usr/bin/meson --internal msgfmthelper 
data/sm.puri.Squeekboard.desktop.in data/sm.puri.Squeekboard.desktop desktop 
../data/../po
msgfmt: ../data/../po/LINGUAS does not exist
[54/58] cc -Isrc/squeekboard.p -Isrc -I../src -I. -I.. -I../eek -Idata 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/mips64el-linux-gnuabi64/glib-2.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/gnome-desktop-3.0 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/mips64el-linux-gnuabi64/dbus-1.0/include 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/fribidi 
-I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gsettings-desktop-schemas 
-I/usr/include/libfeedback-0.0 -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -std=gnu11 -Werror=implicit-function-declaration 
-Werror=implicit-fallthrough=3 -Werror=maybe-uninitialized 
-Werror=missing-field-initializers -Werror=incompatible-pointer-types 
-Werror=int-conversion -Werror=redundant-decls -Werror=parentheses 
-Wformat-nonliteral -Wformat-security -Winit-self -Wmaybe-uninitialized 
-Wold-style-definition -Wredundant-decls -Wstrict-prototypes -Wunused-function 
-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
'-DTHEMESDIR="/usr/share/squeekboard/themes"' 
'-DKEYBOARDSDIR="/usr/share/squeekboard/keyboards"' -DEEKBOARD_COMPILATION=1 
-DEEK_COMPILATION=1 -MD -MQ src/squeekboard.p/server-main.c.o -MF 
src/squeekboard.p/server-main.c.o.d -o src/squeekboard.p/server-main.c.o -c 
../src/server-main.c
[55/58] /<>/cargo_build.sh --rename test_layout 
tools/squeekboard-test-layout --bin test_layout
   Compiling rs v0.1.0 (/<>/_build)
Finished dev [unoptimized + debuginfo] target(s) in 29.06s
[56/58] /<>/cargo.sh test --no-run
   Compiling rs v0.1.0 (/<>/_build)
Finished test [unoptimized + debuginfo] target(s) in 59.83s
[57/58] cc  -o src/squeekboard 
src/squeekboard.p/meson-generated_xdg-shell-protocol.c.o 
src/squeekboard.p/meson-generated_wlr-layer-shell-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_virtual-keyboard-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_input-method-unstable-v2-protocol.c.o 
src/squeekboard.p/meson-generated_text-input-unstable-v3-protocol.c.o 
src/squeekboard.p/meson-generated_.._.._data_squeekboard-resources.c.o 
src/squeekboard.p/server-main.c.o -Wl,--as-needed -Wl,--no-undefined -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,--start-group 
src/liblibsqueekboard.a src/librs.a 
/usr/lib/mips64el-linux-gnuabi64/libgio-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libgobject-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libglib-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libgnome-desktop-3.so 
/usr/lib/mips64el-linux-gnuabi64/libgtk-3.so 
/usr/lib/mips64el-linux-gnuabi64/libgdk-3.so 
/usr/lib/mips64el-linux-gnuabi64/libpangocairo-1.0.so 
/usr/lib/mips64el-linux-gnuabi64/libpango-1.0.so 
/usr/lib/mips64el-linux-gnuabi64/libharfbuzz.so 
/usr/lib/mips64el-linux-gnuabi64/libatk-1.0.so 
/usr/lib/mips64el-linux-gnuabi64/libcairo-gobject.so 
/usr/lib/mips64el-linux-gnuabi64/libcairo.so 
/usr/lib/mips64el-linux-gnuabi64/libgdk_pixbuf-2.0.so 
/usr/lib/mips64el-linux-gnuabi64/libfeedback-0.0.so 
/usr/lib/mips64el-linux-gnuabi64/libwayland-client.so 
/usr/lib/mips64el-linux-gnuabi64/libxkbcommon.so -lm -lrt -ldl -lpthread 
-Wl,--end-group '-Wl,-rpath,$ORIGIN/' 
-Wl,-rpath-link,/<>/_build/src
FAILED: src/squeekboard 
cc  -o src/squeekboard src/squeekboard.p/meson-generated_xdg-shell-protocol.c.o 
src/squeekboard.p/meson-generated_wlr-layer-shell-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_virtual-keyboard-unstable-v1-protocol.c.o 
src/squeekboard.p/meson-generated_input-method-unstable-v2-protocol.c.o 
src/squeekboard.p/meson-generated

Bug#973630: marked as done (fetchmail: OpenSSL library mismatch)

Your message dated Tue, 10 Nov 2020 20:54:22 +0100
with message-id 

and subject line Re: Bug#973472: fetchmail: Fails to connect using SSL
has caused the Debian Bug report #973472,
regarding fetchmail: OpenSSL library mismatch
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.)

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

Dear Maintainer,

after the upgrade of today fetchmail is not anymore able to
use OpenSSL. Upon calling fetchmail from mutt I get the following
fatal error.

fetchmail: Query status=2 (SOCKET)
fetchmail: Loaded OpenSSL library 0x1010107f older than headers 0x1010108f,
refusing to work.

I think it's a kind of library mismatch.

Best regards

Giorgio

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

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

Versions of packages fetchmail depends on:
ii  adduser   3.118
ii  debianutils   4.11.2
ii  libc6 2.31-4
ii  libcom-err2   1.45.6-1
ii  libgssapi-krb5-2  1.17-10
ii  libkrb5-3 1.17-10
ii  libssl1.1 1.1.1g-1
ii  lsb-base  11.1.0

Versions of packages fetchmail recommends:
ii  ca-certificates  20200601

Versions of packages fetchmail suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.94-8
pn  fetchmailconf  
pn  resolvconf 

-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,

On Fri, Nov 6, 2020 at 9:09 AM Michal Palenik  wrote:
> for those stumbling on this via searching, the workaround mentioned
> above is:
[...]
> apt -t unstable install libssl1.1:amd64
 Thanks for possibly the best solution. Meanwhile OpenSSL 1.1.1h-1
migrated to testing; closing this bug report.

Regards,
Laszlo/GCS--- End Message ---

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Steinar H. Gunderson

On Tue, Nov 10, 2020 at 08:34:10PM +0100, Jonas Smedegaard wrote:
> Would you still find it relevant to pin the old font even if the new one 
> works but simply uses different visual style?

Yes. I find the new one fairly unreadable as a terminal font.

> Source for Debian package is https://github.com/googlefonts/noto-fonts/ 
> - but interestingly, the NotoMono fonts was renamed just 2 days after 
> our latest snapshot - with a totally unrevealing commit message of 
> "Published NotoTraditionalNushu hinted and unhinted static instances":
> https://github.com/googlefonts/noto-fonts/commit/1eda585
> 
> Seems Google changed their mind regarding the reuse of font name, and we 
> can go back to keeping the old legacy font alive...

It sounds they simply messed up the naming when uploading Noto Sans Mono,
and fixed it in that commit.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread Maarten L. Hekkelman


Op 10-11-2020 om 16:21 schreef Andrey Rahmatullin:

Running 7 test cases...
started daemon at port 5923
terminate called after throwing an instance of 
'boost::wrapexcept'
   what():  resolve: Host not found (authoritative)

Looks like it tries to resolve something, and that usually implies
Internet access, as otherwise you could just connect to localhost?
Accessing the Internet is forbidden during building.
The test case tried to resolve "127.0.0.1" as host. I've changed that to 
"localhost" since adding a flag for boost to only interpret the value as 
numeric is not easy to add to the code. I've seen hosts where localhost 
is mapped to some other IP address in the range 127.0.0.0/255 Could this 
be the case on the particular build machine where the test failed?


Anyway, I assume that using localhost will be sufficient to fix this 
problem. We'll see that shorly.


regards, -maarten

Bug#972137: marked as done (r-bioc-tcgabiolinks: autopkgtest regression)

Your message dated Tue, 10 Nov 2020 22:31:17 +0200
with message-id <20201110203117.GA26402@localhost>
and subject line Re: Bug#972137: r-bioc-tcgabiolinks: autopkgtest regression
has caused the Debian Bug report #972137,
regarding r-bioc-tcgabiolinks: autopkgtest regression
to be marked as done.

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

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

-- 
972137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-bioc-tcgabiolinks
Version: 2.16.4+dfsg-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Since 2020-10-08, the autopkgtest of r-bioc-tcgabiolinks has been failing [1].

I've copied what I hope is the relevant part of the log below.

Does this autopkgtest download data?  If so, please add the
'needs-internet' [2] restriction to debian/tests/control, or even skip
that particular test.

Regards
Graham

[1] https://ci.debian.net/packages/r/r-bioc-tcgabiolinks/testing/amd64/
[2] 
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst

── 1. Error: Preparing HT_HG-U133A as SE works (@test-prepare-download.R#193)  ─
failed to get URL after 3 tries:
  error: SSL certificate problem: unable to get local issuer certificate
Backtrace:
 1. TCGAbiolinks::GDCprepare(query, summarizedExperiment = TRUE)
 2. TCGAbiolinks:::readGeneExpressionQuantification(...)
 3. TCGAbiolinks:::makeSEfromGeneExpressionQuantification(...)
 4. TCGAbiolinks::get.GRCh.bioMart(genome)
--- End Message ---
--- Begin Message ---
Version: 2.18.0+dfsg-1

On Tue, Oct 13, 2020 at 08:36:21AM +0200, Graham Inggs wrote:
> Source: r-bioc-tcgabiolinks
> Version: 2.16.4+dfsg-1
> Severity: serious
> Tags: sid bullseye
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: regression
> 
> Hi Maintainer
> 
> Since 2020-10-08, the autopkgtest of r-bioc-tcgabiolinks has been failing [1].
>...

This seems to be fixed in the latest version:
https://ci.debian.net/packages/r/r-bioc-tcgabiolinks/

> Regards
> Graham
>...

cu
Adrian--- End Message ---

Bug#974150: marked as pending in fonts-noto

2020-11-10 Thread Jonas Smedegaard

Control: tag -1 pending

Hello,

Bug #974150 in fonts-noto 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/fonts-team/fonts-noto/-/commit/9d47c8ef51537acaf64a785e5cee96cf0d6132e1


revive legacy Noto Mono, closes: bug#974150, thanks to Steinar H. Gunderson


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974150

Bug#974162: plast: binary-all FTBFS

Source: plast
Version: 2.3.2+dfsg-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=plast&arch=all&ver=2.3.2%2Bdfsg-2&stamp=1605032084&raw=0

...
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: plast (1), plast-example (2)
 * dh_installdocs: plast (2), plast-example (0)
 * dh_installman: plast (1), plast-example (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:13: binary-indep] Error 25

Processed: Bug#974150 marked as pending in fonts-noto

Processing control commands:

> tag -1 pending
Bug #974150 [fonts-noto-mono] Noto Mono looks completely different after upgrade
Added tag(s) pending.

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

Processed: severity of 973254 is grave

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

> severity 973254 grave
Bug #973254 [src:pacemaker] pacemaker: CVE-2020-25654
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#974150: marked as done (Noto Mono looks completely different after upgrade)

Your message dated Tue, 10 Nov 2020 20:55:04 +
with message-id 
and subject line Bug#974150: fixed in fonts-noto 20201109-1
has caused the Debian Bug report #974150,
regarding Noto Mono looks completely different after upgrade
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.)


-- 
974150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974150
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-noto-mono
Version: 20201027-3
Severity: grave

Hi,

For unknown reasons, Noto Mono looks completely different after
I upgraded my unstable machines recently, to the point that it's
not the same font anymore (for one, it has serifs). This affects
multiple machines, both rxvt-unicode and gnome-terminal, both
X11 and Wayland, and goes away if I downgrade. Compare the stable
and unstable fonts below (the version of fonts-noto-mono installed
when urxvt started is the sole difference between the two windows):

  https://home.samfundet.no/~sesse/noto-mono.png

The upper (stable) also matches what the font looks like if I
look at https://www.google.com/get/noto/#mono-mono. You can see
some fragments of it in the screenshot; look at e.g. the lowercase
g.

gnome-terminal doesn't even list Noto Mono in its list of available
fonts, so I'm wondering if it does some sort of fallback and that
the font just is completely broken somehow.
--- End Message ---
--- Begin Message ---
Source: fonts-noto
Source-Version: 20201109-1
Done: Jonas Smedegaard 

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated fonts-noto package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Nov 2020 21:03:34 +0100
Source: fonts-noto
Architecture: source
Version: 20201109-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Jonas Smedegaard 
Closes: 974150
Changes:
 fonts-noto (20201109-1) unstable; urgency=medium
 .
   [ upstream ]
   * new "release"
 .
   [ Jonas Smedegaard ]
   * fix typo in changelog
   * adapt build routines for family Noto Mono renamed to Noto Sans Mono
   * revive legacy Noto Mono;
 closes: bug#974150, thanks to Steinar H. Gunderson
Checksums-Sha1:
 d6e126d3d7bd4693d25eb2e5ae96538241fb9db1 2722 fonts-noto_20201109-1.dsc
 ac55e08f05b88dadf35e56f1d24ac999a0182cb3 852308916 
fonts-noto_20201109.orig.tar.gz
 ce1124331652e7d06a73656bad94c1e7b7d90b85 109376 
fonts-noto_20201109-1.debian.tar.xz
 cb32e0a88e66cd4e663408dc4e71cfeb5e3dbdfc 8863 
fonts-noto_20201109-1_amd64.buildinfo
Checksums-Sha256:
 c2f711916b8921aa0989c75f224009c3550afd71933ded951542f860b6250cd6 2722 
fonts-noto_20201109-1.dsc
 95cb076a4e36665ec913dad6d7d446094076b250ab7f3434ed8d214dc9dcd5d8 852308916 
fonts-noto_20201109.orig.tar.gz
 1fd7d3ef863a7037fff393bd3c60f830e06b555d4cd1d62ab454934c26cdf21a 109376 
fonts-noto_20201109-1.debian.tar.xz
 adeae4db1f71f6078d0509b5aa1e30fd500871be08c37c49368867ca4e9eee29 8863 
fonts-noto_20201109-1_amd64.buildinfo
Files:
 16e14b25ad0325ac70b96023bf74f9a0 2722 fonts optional fonts-noto_20201109-1.dsc
 62cf6229e6aa06e9464ee4cb0d3bda63 852308916 fonts optional 
fonts-noto_20201109.orig.tar.gz
 b2478549fa856b451123511e9e2c7605 109376 fonts optional 
fonts-noto_20201109-1.debian.tar.xz
 dd708b5936697323416855f1bfcfe7aa 8863 fonts optional 
fonts-noto_20201109-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl+q+OQACgkQLHwxRsGg
ASE93RAApnXDPS80GfPsUxRQfOXv7kgg0NQxxRF27TZ178t+bKLnyJh+v0gVrkBm
Ec+42MiG/A7k5Cbo1nxa9+juiiaSHsMpFtWvyfWtHrIoCyyD6PoPUYla8rlNm+VS
XNCpgigN6oG+OFTTdzAzspsLaTZ3iRBXZRnRbKY/qZ/+kt/q71avUCrphtucOHwJ
NdiQad2pa9+Zw6GAFupQRCCpPa9zkCOPO0y0lP+DSaN//zD8vbeZtDucr4V470jx
kS4iXFUt7MjZ+F8js0wXBJp2UomH+GNsxEzPazZaGnSI8IiUCKwkDF4l3GbNsHlR
dNJJoAwrYNACkF9T8X0j7OLPnQsJDAWakg2r3Fj+g/qSnVerltBSrqjRNKFaEocm
abVsBKOxilw63ibw20gRSENnkkSKXRWI2Lzwtn2QTHjqgI1xRR6IpXrAwr8q96R4
QXsY2tLbJoibafefEdqKWfu+OztQrq8d8wreLA6PJkbsSdmPTWgNkMJcZ1Jfrnnc
NiqSH6NKsF2AxOlGvSFsv89x07BScPgD

Bug#964693: marked as done (qpxtool: FTBFS: include/device.h:434:12: error: ‘QIODevice’ has not been declared)

Your message dated Tue, 10 Nov 2020 20:56:41 +
with message-id 
and subject line Bug#964693: fixed in qpxtool 0.8.1-1
has caused the Debian Bug report #964693,
regarding qpxtool: FTBFS: include/device.h:434:12: error: ‘QIODevice’ has not 
been declared
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
> g++ -c -pipe -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -O2 -fPIC -DOFFT_64BIT -DHAVE_FOPEN64 -DHAVE_FSEEKO 
> -DUSE_LIBPNG   -O2 -D_REENTRANT -Wall -Wextra -fPIC -DQT_NO_DEBUG 
> -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
> -DQT_SQL_LIB -DQT_CORE_LIB -I. -I../lib/include -I. -Iinclude -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -Imoc 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o obj/resultsio.o 
> src/resultsio.cpp
> In file included from include/resultsio.h:18,
>  from src/resultsio.cpp:13:
> include/device.h:434:12: error: ‘QIODevice’ has not been declared
>   434 |  void save(QIODevice*);
>   |^
> include/device.h:437:12: error: ‘QIODevice’ has not been declared
>   437 |  void load(QIODevice*);
>   |^
> In file included from src/resultsio.cpp:13:
> include/resultsio.h:28:20: error: ‘QIODevice’ has not been declared
>28 |  inline void setIO(QIODevice *io) { this->io = io; };
>   |^
> include/resultsio.h:32:2: error: ‘QIODevice’ does not name a type; did you 
> mean ‘QPxIODevice’?
>32 |  QIODevice *io;
>   |  ^
>   |  QPxIODevice
> include/resultsio.h: In constructor ‘ResultsIO::ResultsIO(device*)’:
> include/resultsio.h:25:88: error: ‘io’ was not declared in this scope
>25 |  ResultsIO(device *dev)  :QThread((QObject*)dev) { this->dev = dev; 
> this->res = false; io = NULL; }
>   |   
>  ^~
> include/resultsio.h: In member function ‘void ResultsIO::setIO(int*)’:
> include/resultsio.h:28:43: error: ‘class ResultsIO’ has no member named ‘io’
>28 |  inline void setIO(QIODevice *io) { this->io = io; };
>   |   ^~
> src/resultsio.cpp: In member function ‘virtual void ResultsReader::run()’:
> src/resultsio.cpp:45:7: error: ‘io’ was not declared in this scope
>45 |  if (!io || !io->isOpen() || !io->isReadable()) { return; }
>   |   ^~
> src/resultsio.cpp:46:16: error: ‘io’ was not declared in this scope
>46 |  xml.setDevice(io);
>   |^~
> src/resultsio.cpp: In member function ‘virtual void ResultsWriter::run()’:
> src/resultsio.cpp:300:7: error: ‘io’ was not declared in this scope
>   300 |  if (!io || !io->isOpen() || !io->isWritable()) { return; }
>   |   ^~
> src/resultsio.cpp:302:16: error: ‘io’ was not declared in this scope
>   302 |  xml.setDevice(io);
>   |^~
> src/resultsio.cpp: In member function ‘virtual void ResultsReader::run()’:
> src/resultsio.cpp:251:5: warning: this statement may fall through 
> [-Wimplicit-fallthrough=]
>   251 | if (isQpxData && xml.name() == "qpxdata") {
>   | ^~
> src/resultsio.cpp:276:4: note: here
>   276 |case QXmlStreamReader::Invalid:
>   |^~~~
> make[3]: *** [Makefile.qmake:1091: obj/resultsio.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/07/09/qpxtool_0.8.0-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 ---
--- Beg

Bug#974167: fetchmail: OpenSSL reported error: key too small

2020-11-10 Thread Francesco Potortì

Package: fetchmail
Version: 6.4.13-1
Severity: grave
X-Debbugs-Cc: none, Francesco Potortì 

fetchmail can no longer download mail from some servers.  In the logfile
it reports:

fetchmail: OpenSSL reported: error:141A318A:SSL routines:tls_process_ske_dhe:dh 
key too small
fetchmail: SSL connection failed.
fetchmail: socket error while fetching from addr...@server.org
fetchmail: Query status=2 (SOCKET)
fetchmail: Server certificate verification error: Hostname mismatch
fetchmail: OpenSSL reported: error:141A318A:SSL routines:tls_process_ske_dhe:dh 
key too small


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

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

Versions of packages fetchmail depends on:
ii  adduser   3.118
ii  debianutils   4.11.2
ii  libc6 2.31-4
ii  libcom-err2   1.45.6-1
ii  libgssapi-krb5-2  1.17-10
ii  libkrb5-3 1.17-10
ii  libssl1.1 1.1.1h-1
ii  lsb-base  11.1.0

Versions of packages fetchmail recommends:
ii  ca-certificates  20200601

Versions of packages fetchmail suggests:
ii  exim4-daemon-light [mail-transport-agent]  4.94-8
pn  fetchmailconf  
ii  resolvconf 1.84

-- Configuration Files:
/etc/logcheck/ignore.d.server/fetchmail [Errno 13] Permission denied: 
'/etc/logcheck/ignore.d.server/fetchmail'
/etc/logcheck/ignore.d.workstation/fetchmail [Errno 13] Permission denied: 
'/etc/logcheck/ignore.d.workstation/fetchmail'

-- no debconf information

Bug#974168: bioperl-run: autopkgtest failure

Source: bioperl-run
Version: 1.7.3-4
Severity: serious

https://ci.debian.net/packages/b/bioperl-run/

...
# Can't locate File/Sort.pm in @INC (you may need to install the File::Sort 
module) (@INC contains: ../../.. /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
/usr/share/perl/5.30 /usr/local/lib/site_perl) at 
/usr/share/perl5/Bio/Tools/Run/BEDTools.pm line 197.
# BEGIN failed--compilation aborted at 
/usr/share/perl5/Bio/Tools/Run/BEDTools.pm line 197.
not ok 31 - /usr/bin/perl -wc /usr/share/perl5/Bio/Tools/Run/BEDTools.pm 
exited successfully
...


libfile-sort-perl is now in unstable, but after adding it to
dependencies and build dependencies the package build fails
with other test failures.

Processed: fixed 967194 1.0.8-1

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

> fixed 967194 1.0.8-1
Bug #967194 {Done: Russell Stuart } 
[src:pam-python] pam-python: Unversioned Python removal in sid/bullseye
Ignoring request to alter fixed versions of bug #967194 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#974169: packer FTBFS on IPV6-only buildds

Source: packer
Version: 1.6.4+dfsg-3
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=packer&arch=amd64&ver=1.6.4%2Bdfsg-3&stamp=1601828399&raw=0

...
--- FAIL: TestStepHTTPIPDiscover_Run (0.00s)
...
dh_auto_test: error: cd _build && go test -vet=off -v -p 4 
github.com/hashicorp/packer github.com/hashicorp/packer/builder 
github.com/hashicorp/packer/builder/alicloud/ecs 
github.com/hashicorp/packer/builder/amazon/chroot 
github.com/hashicorp/packer/builder/amazon/common 
github.com/hashicorp/packer/builder/amazon/ebs 
github.com/hashicorp/packer/builder/amazon/ebs/acceptance 
github.com/hashicorp/packer/builder/amazon/ebssurrogate 
github.com/hashicorp/packer/builder/amazon/ebsvolume 
github.com/hashicorp/packer/builder/amazon/instance 
github.com/hashicorp/packer/builder/azure/arm 
github.com/hashicorp/packer/builder/azure/chroot 
github.com/hashicorp/packer/builder/azure/common 
github.com/hashicorp/packer/builder/azure/common/client 
github.com/hashicorp/packer/builder/azure/common/constants 
github.com/hashicorp/packer/builder/azure/common/lin 
github.com/hashicorp/packer/builder/azure/common/logutil 
github.com/hashicorp/packer/builder/azure/common/template 
github.com/hashicorp/packer/builder/azure/dtl 
github.com/hashicorp/packer/builder/azure/pkcs12 
github.com/hashicorp/packer/builder/azure/pkcs12/rc2 
github.com/hashicorp/packer/builder/cloudstack 
github.com/hashicorp/packer/builder/digitalocean 
github.com/hashicorp/packer/builder/docker 
github.com/hashicorp/packer/builder/file 
github.com/hashicorp/packer/builder/googlecompute 
github.com/hashicorp/packer/builder/hcloud 
github.com/hashicorp/packer/builder/hyperv/common 
github.com/hashicorp/packer/builder/hyperv/iso 
github.com/hashicorp/packer/builder/hyperv/vmcx 
github.com/hashicorp/packer/builder/jdcloud 
github.com/hashicorp/packer/builder/lxc github.com/hashicorp/packer/builder/lxd 
github.com/hashicorp/packer/builder/ncloud 
github.com/hashicorp/packer/builder/null 
github.com/hashicorp/packer/builder/oneandone 
github.com/hashicorp/packer/builder/openstack 
github.com/hashicorp/packer/builder/oracle/classic 
github.com/hashicorp/packer/builder/oracle/common 
github.com/hashicorp/packer/builder/oracle/oci 
github.com/hashicorp/packer/builder/osc/bsu 
github.com/hashicorp/packer/builder/osc/bsusurrogate 
github.com/hashicorp/packer/builder/osc/bsuvolume 
github.com/hashicorp/packer/builder/osc/chroot 
github.com/hashicorp/packer/builder/osc/common 
github.com/hashicorp/packer/builder/parallels/common 
github.com/hashicorp/packer/builder/parallels/iso 
github.com/hashicorp/packer/builder/parallels/pvm 
github.com/hashicorp/packer/builder/profitbricks 
github.com/hashicorp/packer/builder/proxmox 
github.com/hashicorp/packer/builder/qemu 
github.com/hashicorp/packer/builder/scaleway 
github.com/hashicorp/packer/builder/tencentcloud/cvm 
github.com/hashicorp/packer/builder/triton 
github.com/hashicorp/packer/builder/vagrant 
github.com/hashicorp/packer/builder/virtualbox/common 
github.com/hashicorp/packer/builder/virtualbox/iso 
github.com/hashicorp/packer/builder/virtualbox/iso/acceptance 
github.com/hashicorp/packer/builder/virtualbox/ovf 
github.com/hashicorp/packer/builder/virtualbox/vm 
github.com/hashicorp/packer/builder/vmware/common 
github.com/hashicorp/packer/builder/vmware/iso 
github.com/hashicorp/packer/builder/vmware/vmx 
github.com/hashicorp/packer/builder/vsphere/clone 
github.com/hashicorp/packer/builder/vsphere/common 
github.com/hashicorp/packer/builder/vsphere/common/testing 
github.com/hashicorp/packer/builder/vsphere/driver 
github.com/hashicorp/packer/builder/vsphere/iso 
github.com/hashicorp/packer/command github.com/hashicorp/packer/common 
github.com/hashicorp/packer/common/adapter 
github.com/hashicorp/packer/common/bootcommand 
github.com/hashicorp/packer/common/chroot 
github.com/hashicorp/packer/common/filelock 
github.com/hashicorp/packer/common/iochan 
github.com/hashicorp/packer/common/json github.com/hashicorp/packer/common/net 
github.com/hashicorp/packer/common/powershell 
github.com/hashicorp/packer/common/powershell/hyperv 
github.com/hashicorp/packer/common/random 
github.com/hashicorp/packer/common/retry 
github.com/hashicorp/packer/common/shell 
github.com/hashicorp/packer/common/shell-local 
github.com/hashicorp/packer/common/shutdowncommand 
github.com/hashicorp/packer/common/template 
github.com/hashicorp/packer/common/uuid 
github.com/hashicorp/packer/communicator/none 
github.com/hashicorp/packer/communicator/ssh 
github.com/hashicorp/packer/communicator/winrm github.com/hashicorp/packer/fix 
github.com/hashicorp/packer/hcl2template 
github.com/hashicorp/packer/hcl2template/function 
github.com/hashicorp/packer/hcl2template/internal 
github.com/hashicorp/packer/hcl2template/repl 
github.com/hashicorp/packer/hcl2template/shim 
github.com/hashicorp/packer/helper/builder/localexec 
github.com/hashicorp/packer/helper/builder/testing 
github.com/hashicorp/packer/helper

Bug#974143: marked as pending in libencode-arabic-perl

2020-11-10 Thread Dominic Hargreaves

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/perl-team/modules/packages/libencode-arabic-perl/-/commit/c1bbdb128dd90782a302a1ed62a20d87d621fc3e


Suppress 'Useless use of /d modifier' warnings

The transliteration lists are dynamically created. Fixes autopkgtest
failures with perl 5.32 (Closes: #974143)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974143

Processed: Bug#974143 marked as pending in libencode-arabic-perl