Bug#945317: xcftools NMU for CVE-2019-5086 and CVE-2019-5087

[Hugo Lefeuvre]

Hi Salvatore and Markus,

On Thu, Feb 11, 2021 at 06:32:42AM +0100, Salvatore Bonaccorso wrote:
[...]
> On Thu, Feb 11, 2021 at 03:03:19AM +0100, Markus Koschany wrote:
> [...]
> > Am Mittwoch, den 10.02.2021, 22:03 +0100 schrieb Salvatore Bonaccorso:
> > [...]
> > > 
> > > I'm not fully in favor to have all the (build-)rdeps forced out of
> > > Debian, that would likely not be a benefit as seems unfair to the
> > > castle-game-engine, game-data-packager and neurodebian packages, but
> > > still think having out xcftools out of bullseye would be the right
> > > thing.
> > > 
> > 
> > I believe it makes sense to remove xcftools from Debian because there is a 
> > lack
> > of upstream support and development but I wouldn't be too aggressive about 
> > the
> > removal at the moment. My intention is to send a patch to fix the open CVE 
> > in
> > stable to you when we have addressed the remaining 32 bit issues.
> 
> Yes that sounds fine. Admittely it was for us in dsa-needed only
> because Hugo initially aimed to adress it across all suites top-down.
> It might just be an option to include a fix once it is stable enough
> via a point release. But we can look at it once you have a fix as well
> for the 32bit issues.
> 
> So thanks for working on it!

Thanks from my part too! Unfortunately I am struggling to find
time for Debian currently. I makes me feel bad, and I hope that I
will be able to come back soon.

Do you know if xcftools is only used as a build dependency, or is
it used by some end users directly? The popcon is not that low
and my fear is that, even after removing it from Debian, users
would continue to use it, installing from somewhere else,
effectively being at even higher risk than with the Debian
archive's (semi-) patched version.

Of course if we can't offer any support I guess it's still better
to get rid of it than giving a false impression of
support/security.

Best,
Hugo

-- 
Hugo Lefeuvre (hle)|www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C


signature.asc
Description: PGP signature

Bug#982622: marked as done (r-cran-matrixstats might need Breaks: r-bioc-matrixgenerics (<< 1.2.1))

[Debian Bug Tracking System]

Your message dated Wed, 17 Feb 2021 07:04:35 +
with message-id 
and subject line Bug#982622: fixed in r-cran-matrixstats 0.58.0-2
has caused the Debian Bug report #982622,
regarding r-cran-matrixstats might need Breaks: r-bioc-matrixgenerics (<< 1.2.1)
to be marked as done.

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

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


-- 
982622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982622
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-cran-matrixstats
Version: 0.58.0-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-bioc-matrixgenerics/10405220/log.gz

...
> test_check("MatrixGenerics")
══ Failed tests 
── Failure (test-api_compatibility.R:89:2): colAvgsPerRowSet works  
`matrixStats_formals` not identical to `MatrixGenerics_default_method_formals`.
Names: 1 string mismatch
Length mismatch: comparison on first 7 components
Component 7: 'is.NA' value mismatch: 0 in current 1 in target
── Error (test-api_compatibility.R:360:2): colMads works  ──
Error: Argument 'center' should be of the same length as number of columns of 
'x': 6 != 8
Backtrace:
█
 1. ├─MatrixGenerics::colMads(...) test-api_compatibility.R:360:8
 2. └─MatrixGenerics::colMads(...)
 3.   └─MatrixGenerics:::.local(...)
 4. └─matrixStats::colMads(...)
── Error (test-api_compatibility.R:593:2): colSds works  ───
Error: Argument 'center' should be of the same length as number of columns of 
'x': 6 != 8
Backtrace:
█
 1. ├─MatrixGenerics::colSds(...) test-api_compatibility.R:593:8
 2. └─MatrixGenerics::colSds(...)
 3.   └─MatrixGenerics:::.local(x, rows, cols, na.rm, center, ...)
 4. └─matrixStats::colSds(...)
 5.   └─matrixStats::colVars(...)
── Error (test-api_compatibility.R:678:2): colVars works  ──
Error: Argument 'center' should be of the same length as number of columns of 
'x': 6 != 8
Backtrace:
█
 1. ├─MatrixGenerics::colVars(...) test-api_compatibility.R:678:8
 2. └─MatrixGenerics::colVars(...)
 3.   └─MatrixGenerics:::.local(x, rows, cols, na.rm, center, ...)
 4. └─matrixStats::colVars(...)
── Error (test-api_compatibility.R:698:2): colWeightedMads works  ──
Error: Argument 'center' should be of the same length as number of columns of 
'x': 1 != 6
Backtrace:
█
 1. ├─MatrixGenerics::colWeightedMads(...) test-api_compatibility.R:698:8
 2. └─MatrixGenerics::colWeightedMads(...)
 3.   └─matrixStats::colWeightedMads(...)
── Failure (test-api_compatibility.R:856:2): rowAvgsPerColSet works  ───
`matrixStats_formals` not identical to `MatrixGenerics_default_method_formals`.
Names: 1 string mismatch
Length mismatch: comparison on first 7 components
Component 7: 'is.NA' value mismatch: 0 in current 1 in target
── Error (test-api_compatibility.R:1127:2): rowMads works  ─
Error: Argument 'center' should be of the same length as number of rows of 'x': 
16 != 12
Backtrace:
█
 1. ├─MatrixGenerics::rowMads(...) test-api_compatibility.R:1127:8
 2. └─MatrixGenerics::rowMads(...)
 3.   └─MatrixGenerics:::.local(...)
 4. └─matrixStats::rowMads(...)
── Error (test-api_compatibility.R:1360:2): rowSds works  ──
Error: Argument 'center' should be of the same length as number of rows of 'x': 
16 != 12
Backtrace:
█
 1. ├─MatrixGenerics::rowSds(...) test-api_compatibility.R:1360:8
 2. └─MatrixGenerics::rowSds(...)
 3.   └─MatrixGenerics:::.local(x, rows, cols, na.rm, center, ...)
 4. └─matrixStats::rowSds(...)
 5.   └─matrixStats::rowVars(...)
── Error (test-api_compatibility.R:1445:2): rowVars works  ─
Error: Argument 'center' should be of the same length as number of rows of 'x': 
16 != 12
Backtrace:
█
 1. ├─MatrixGenerics::rowVars(...) test-api_compatibility.R:1445:8
 2. └─MatrixGenerics::rowVars(...)
 3.   └─MatrixGenerics:::.local(x, rows, cols, na.rm, center, ...)
 4. └─matrixStats::rowVars(...)
── Error (test-api_compatibility.R:1466:2): rowWeightedMads works  ─
Error: Argument 'center' should be of the same length as number of rows of 'x': 
1 != 6
Backtrace:
█
 1. ├─MatrixGenerics::rowWeightedMads(...) test-api_compatibility.R:1466:8
 2. └─MatrixGenerics::rowWeightedMads(...)
 3.   └─matrixStats::rowWeightedMads(...)

[ FAIL 10 | WARN 0 | SKIP 0 | PASS 300 ]
Error: Test failures
Execution halted
autopkgtest [18:11:11]: test pkg-r-autopkgtest: ---]
autopkgtest [18:11:11]: test pkg-r-autopkgtest:  - - - - - - - - -

Bug#982946: python3-pyudev: pyudev.glib import crashes in Python 3

[Adam Sloboda]

Package: python3-pyudev
Version: 0.22.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The source code in the package does not include fixes for Python 3 compat.

It was fixed in the main branch of github repository long time ago:

https://github.com/pyudev/pyudev/blob/master/src/pyudev/glib.py

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

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

Versions of packages python3-pyudev depends on:
ii  libudev1 247.3-1
ii  python3  3.9.1-1
ii  python3-six  1.15.0-2

python3-pyudev recommends no packages.

python3-pyudev suggests no packages.

-- no debconf information

Bug#971681: r-cran-openmx regression on arm, will not migrate to testing due to failing autopkgtests

[Andreas Tille]

Hi Joshua,

On Fri, Feb 12, 2021 at 01:03:23PM -0500, Joshua N Pritikin wrote:
> > I submitted a new release to CRAN yesterday. It usually takes a few days 
> > to correct any lingering issues and get it approved.
> 
> CRAN peeps said that v2.19.1 is accepted. I know the package info page 
> isn't updated yet, but I expect that to happen soon.

Openmx version 2.18.1 made it finally to Debian testing and thus is a
release candidate.  We are currently in freeze for the next stable
release.  So any bump to a new upstream version should be very well
thought.  Could you give any reason why we should better release with
openmx 2.19.1 that is worth the risk that some new issues arrise?

Kind regards and thanks for the information anyway

  Andreas.

-- 
http://fam-tille.de

Bug#982914: marked as done (chai: broken-symlink /usr/share/doc/chai -> libjs-chai, missing-copyright-file)

[Debian Bug Tracking System]

Your message dated Wed, 17 Feb 2021 06:49:35 +
with message-id 
and subject line Bug#982914: fixed in node-chai 4.2.0+ds+~4.2.14-3
has caused the Debian Bug report #982914,
regarding chai: broken-symlink /usr/share/doc/chai -> libjs-chai, 
missing-copyright-file
to be marked as done.

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

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


-- 
982914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982914
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chai
Version: 4.2.0+ds+~4.2.14-2
Severity: serious
Justification: Policy 2.3
User: debian...@lists.debian.org
Usertags: adequate broken-symlink missing-copyright-file
X-Debbugs-Cc: t...@mirbsd.de

chai: broken-symlink /usr/share/doc/chai -> libjs-chai
chai: broken-symlink /usr/share/nodejs/chai/dist -> ../../javascript/chai
chai: missing-copyright-file /usr/share/doc/chai/copyright

And indeed:

$ ll -d /usr/share/doc/chai /usr/share/doc/libjs-chai
ls: cannot access '/usr/share/doc/libjs-chai': No such file or directory
lrwxrwxrwx 1 root root 10 Feb 16 07:05 /usr/share/doc/chai -> libjs-chai

/usr/share/doc/PKGNAME can only ever be a symlink to another
binary package’s if the other binary package is built from
the same source *and* version, AND if the link target’s package
is a Depends.


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

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages chai depends on:
ii  node-assertion-error  1.1.0-1
ii  node-check-error  1.0.2-3
ii  node-deep-eql 4.0.0-4
ii  node-get-func-name2.0.0+dfsg-1.1
ii  node-pathval  1.1.1-1
ii  node-type-detect  4.0.8-2
ii  nodejs12.20.2~dfsg-2

chai recommends no packages.

chai suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-chai
Source-Version: 4.2.0+ds+~4.2.14-3
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-chai package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 17 Feb 2021 07:28:36 +0100
Source: node-chai
Architecture: source
Version: 4.2.0+ds+~4.2.14-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 982914
Changes:
 node-chai (4.2.0+ds+~4.2.14-3) unstable; urgency=medium
 .
   * Team upload
   * Remove link between chai and libjs-chai (Closes: #982914)
   * Declare compliance with policy 4.5.1
   * Add ctype=nodejs to component(s)
Checksums-Sha1: 
 58a335008bf256a004efc0b5ea640b09e7afcf43 2616 node-chai_4.2.0+ds+~4.2.14-3.dsc
 b9534bb6ea2d178822096d1913d5c1617cb669a8 7280 
node-chai_4.2.0+ds+~4.2.14-3.debian.tar.xz
Checksums-Sha256: 
 777142d9aa9c20eab7cc66f2aa806e2fe41760e3b1f1b195a57d7e04614ee905 2616 
node-chai_4.2.0+ds+~4.2.14-3.dsc
 f48e8c0fd7c0127fb8728400a92ec6a311b1c94a9f468b17fc8ce0d5ca91e5f7 7280 
node-chai_4.2.0+ds+~4.2.14-3.debian.tar.xz
Files: 
 69841ebfded44395424817f2067a6cf7 2616 javascript optional 
node-chai_4.2.0+ds+~4.2.14-3.dsc
 3fbbcc868a0b930828daea42b134d0ea 7280 javascript optional 
node-chai_4.2.0+ds+~4.2.14-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmAsuJ0ACgkQ9tdMp8mZ
7um00A//VVE25jfH7fEeh6zsSCJTJa+IaYcLyodwGeZQJFUc6JSF9mI+Shnu3H6j
9muGRUK20Vfyh6eIXQ1EOOjp2Qxg4J4PpMxD6eQz36T72pQRtpp1Y3GDHE7nEUnS
3O/qUyu+TK9h8tFl2CAxUNBcGuIGsPMfZ1oG4eI+DyQY4KsCWlTsMTSzWGH+36bI
OpUUY6htQ8zuepZ/S0pylUMbpInZfsUjU0T/ovGufbIlnRhbWGEiKE/whcwAA8n7
apYP6eKKn1Y7oZyQLJzWZYfwTS1jpUs1MFTQUtiTKF4YCMcZU0tBP1r02SdaoUFR
7N42lCpi5E3zWbRXTVIQD87K8nsDP0PRfMFIgR

Processed: Bug#982914 marked as pending in node-chai

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982914 [chai] chai: broken-symlink /usr/share/doc/chai -> libjs-chai, 
missing-copyright-file
Ignoring request to alter tags of bug #982914 to the same tags previously set

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

Bug#982914: marked as pending in node-chai

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-chai/-/commit/8716796d0bbc4b77aa1e41fddc0a3fcc608b02e5


Remove link between chai and libjs-chai

Closes: #982914


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982914

Bug#980680: marked as done (tqdm: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Wed, 17 Feb 2021 06:34:13 +
with message-id 
and subject line Bug#980680: fixed in tqdm 4.56.2-1
has caused the Debian Bug report #980680,
regarding tqdm: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.9 returned exit code 13
to be marked as done.

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

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


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/cli.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/__init__.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/__main__.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_utils.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/autonotebook.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_monitor.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/keras.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/notebook.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/std.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_version.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/gui.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_tqdm_pandas.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/asyncio.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_tqdm.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/auto.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_main.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_tqdm_notebook.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/_tqdm_gui.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/utils.py -> /<>/.pybuild/cpython3_3.9/build/tqdm
> creating /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/contrib/bells.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/contrib/__init__.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/contrib/concurrent.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/contrib/telegram.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/contrib/discord.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/contrib/itertools.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/contrib/utils_worker.py -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm/contrib
> copying tqdm/tqdm.1 -> /<>/.pybuild/cpython3_3.9/build/tqdm
> copying tqdm/completion.sh -> 
> /<>/.pybuild/cpython3_3.9/build/tqdm
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:232: cd /<>/.pybuild/cpython3_3.9/build; 
> python3.9 -m pytest --verbose -k 'not test_comppath and not test_imap and not 
> test_manpath'
> = test session starts 
> ==
> platform linux -- Python 3.9.1+, pytest-6.0.2, py-1.10.0, pluggy-0.13.0 -- 
> /usr/bin/python3.9
> cachedir: .pytest_cache
> rootdir: /<>, configfile: setup.cfg
> collecting ... collected 105 items / 3 deselected / 102 selected
> 
> tests/tests_asyncio.py::test_generators <- 
> .pybuild/cpython3_3.9/build/tests/py37_asyncio.py PASSED [  0%]
> tests/tests_asyncio.py::test_range <- 
> .pybuild/cpython3_3.9/build/tests/py37_asyncio.py FAILED [  1%]
> tests/tests_asyncio.py::test_nested <- 
> .pybuild/cpython3_3.9/build/tests/py37_asyncio.py PASSED [  2%]
> tests/tests_asyncio.py::test_coroutines <- 
> .pybuild/cpython3_3.9/build/tests/py37_asyncio.py PASSED [  3%]
> tests/tests_asyncio.py::test_as_completed <- 
> .pybuild/cpython3_3.9/build/tests/py37_asyncio.py PASSED [  4%]
> tests/tests_concurrent.py::test_thread_map PASSED[  
> 5%]
> tests/tests_concurrent.py::test_process_map PASSED   [  
> 6%]
> tests/tests_concurrent.py::test_chunksize_warning PASSED [  
> 7%]
> tests/tests_cont

Bug#982914: marked as pending in node-chai

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/node-chai/-/commit/0aae0396351724b0b18b00628e4fdd00371d74df


Remove link between chai and libjs-chai

Closes: #982914


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982914

Processed: Bug#982914 marked as pending in node-chai

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982914 [chai] chai: broken-symlink /usr/share/doc/chai -> libjs-chai, 
missing-copyright-file
Added tag(s) pending.

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

Bug#980680: marked as pending in tqdm

[Sandro Tosi]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/tqdm/-/commit/53e6eefdf86bacebf5d539eba8b84e5ba322e580


New upstream release; Closes: #980680


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/980680

Processed: Bug#980680 marked as pending in tqdm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #980680 [src:tqdm] tqdm: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) pending.

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

Bug#982786: growlight: autopkgtest regression

[nick black]

hurrah, it would appear that 1.2.31 is running successfully on
the autopkgtest servers (all show as passed save ppc64el, which
shows as passed here: 
https://ci.debian.net/packages/g/growlight/testing/ppc64el/).

Processed: severity of 826002 is important

[Debian Bug Tracking System]

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

> severity 826002 important
Bug #826002 [git-remote-hg] drops all Debian backports tags: error: * Ignoring 
funny ref 'refs/tags/0.5.2~bpo70+1' locally
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#982435: [screen-devel] [bug #60030] Screen segfaults by displaying some UTF-8 character combination

[Axel Beckert]

Dear Utkarsh,

Utkarsh Gupta wrote:
> Sure thing, once you give a go-ahead, I'll edit the changelog entry
> and shall push that to the salsa repository.

Ok, thanks!

> > existing jessie branch in git. (It has no commit besides those being
> > part of the master branch. Not sure why I or someone else has created
> > it already.)
> 
> There's no "jessie" branch on salsa, at least.

Hmmm.

$ git branch -av | fgrep jessie
 * jessie80eaffb Upload to unstable as 4.2.1-3
   remotes/origin/jessie 80eaffb Upload to unstable as 4.2.1-3

Might be because the remote "origin" originally pointed to Alioth and
I just edited .git/config manually instead of doing the "remote
rename/add" dance since the Alioth remote won't come back.

> So I created one with the latest dsc (4.2.1-3+deb8u1) and added 2
> commits on top of it.

Thanks for the effort, but this seems to have a separate git root
(why?!?) instead of being simply based on the tag debian/4.2.1-3 which
points to commit 80eaffbae4363a79987e0e9fc07d1df96e0abd83.

I fixed it by cherry-picking and applying your relevant commits — with
proper commit messages _NOT_ including the whole (!) debian/changelog
in the commit message but just the relevant entry — on top of the old
jessie branch and force pushed it.

(And unless "gbp dch" is used, I prefer to keep debian/changelog in
sync with the packaging changes and not adding debian/changelog
entries in a separate commit. But I didn't merge those two commits of
yours as I wasn't sure about the reasons for that and it's a
style/workflow thing and might subject to taste.)

> By importing the dsc and creating a branch out of it, the commit history,
> I am afraid, is lost.

I don't see why this is necessary nor how this could have happened at
all. The task would have been so simple:

$ git checkout -b jessie debian/4.2.1-3
$ gbp import-dsc --ignore-branch ../screen_4.2.1-3.dsc
$ git push -u origin jessie
$ git push --tags

> Do you want to restore all that?

I already fixed it (except for tags, but you didn't seem to have
pushed the one expected tag anyways), because I was annoyed even
before I read that far in your mail.

https://salsa.debian.org/debian/screen/-/commits/jessie/ now has a
proper history again.

> I'll be happy to do that after checking out from master and then
> applying +deb8u1 changes and then pushing mine on top of it, but I
> don't see any value to it, really.

Huh, "no value"?!? Sorry, but a proper versioning is _essential_.

Regards, Axel (not amused)
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


signature.asc
Description: PGP signature

Processed: found 971255 in 8.1.0-3, fixed 971255 in 8.3.2-1

[Debian Bug Tracking System]

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

> found 971255 8.1.0-3
Bug #971255 [kopanocore] kopanocore: autopkgtest fails on assuming 
/etc/init.d/mysql exists
There is no source info for the package 'kopanocore' at version '8.1.0-3' with 
architecture ''
Unable to make a source version for version '8.1.0-3'
Marked as found in versions 8.1.0-3.
> fixed 971255 8.3.2-1
Bug #971255 [kopanocore] kopanocore: autopkgtest fails on assuming 
/etc/init.d/mysql exists
There is no source info for the package 'kopanocore' at version '8.3.2-1' with 
architecture ''
Unable to make a source version for version '8.3.2-1'
Marked as fixed in versions 8.3.2-1.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Wed, 17 Feb 2021 00:49:38 +
with message-id 
and subject line Bug#958597: fixed in pmacct 1.7.6-2
has caused the Debian Bug report #958597,
regarding pmacct: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.

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

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


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

Hi,

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

For bullseye we intend to drop this empty transitional package.

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

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

Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Source: pmacct
Source-Version: 1.7.6-2
Done: Chris Hofstaedtler 

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

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

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated pmacct 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, 16 Feb 2021 22:52:12 +
Source: pmacct
Architecture: source
Version: 1.7.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Chris Hofstaedtler 
Closes: 958597
Changes:
 pmacct (1.7.6-2) unstable; urgency=medium
 .
   * QA upload.
   * [6349554] Update Vcs-* URLs so people know where the sources are
   * [808e1ac] Remove build dependency on obsolete dh-systemd.
 Thanks to Adrian Bunk  (Closes: #958597)
Checksums-Sha1:
 123b8cb6c504bd00811d4110dc0b75dd9ff7f2d5 2078 pmacct_1.7.6-2.dsc
 6ee43a9391d8808a5a37367981b521e5819dda50 12892 pmacct_1.7.6-2.debian.tar.xz
 2d3a53ae58fbfcabf7fa49d0e33d2df2ef104caf 5910 pmacct_1.7.6-2_source.buildinfo
Checksums-Sha256:
 f62ab3dc49ac68e05f62b66d51563f377698abafc73a5138f27962209eb1002d 2078 
pmacct_1.7.6-2.dsc
 f811951a84dd3dca631d3fceafa98c6559a9f6b18df9e4cfb61915fb41e66089 12892 
pmacct_1.7.6-2.debian.tar.xz
 5767fc80f83f5c4a03efd351f5b7e5f42b3e9f56ca00f69fb892aec1f225 5910 
pmacct_1.7.6-2_source.buildinfo
Files:
 70a8ef7fa87f6b7cc68c2121df732be1 2078 net optional pmacct_1.7.6-2.dsc
 de4c16d6bf5cead37ab794643518df63 12892 net optional 
pmacct_1.7.6-2.debian.tar.xz
 d3b432099502ab568831d2fa874d37e0 5910 net optional 
pmacct_1.7.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmAsY8MACgkQXBPW25MF
LgM5ZxAAkyDS2AMu6eNaD4NtFabhuaKw+UHquqVo2a5fAoCxLG93gZcZDS/NIBWI
ZrqR7vtGnrjOJUDcF2ysXg+MiUzDPWZ4TZUhWWh4yYc3XOhbovuV9wSMqlYZyRHs
201S4SaHoEB/PVJSkQPcbA8xqi7XDIv0xrpE9WONj6BHf6NqtdOugkIjT7K3LL+C
iY+2mNcbOOfhAunZg9utJQsOngd522uycTAqmFRymlZWHK+r4UrC79PSICRqHCZV
CMjkpkEHYX4VuRTjQrOnaJVwOkV416pjGeexJkAwhXH1vo2/Jo3Ty/drO6m4QRWO
EXyW+vNeCPg9SH9AVqTON8o5l9QLFxUFjAktxyJAK7WNEoU+MyjE6GM2ebyLPKMb
cVyKR4KhfzrtrunopycdeVYqVQsTsq+ebPgpWrcx23VhhVdTUCJlYev0+3uvTClB
LgBBYe4fAPmdz9M/8Id/6VdwbpQeuj/0oGJM9XMWWjuHtO2jSl7IwFldVzx0Hnq+
+R6fQYTUpNocjNpYk4sDKRXVyg1lxW7kj3rtkjRu7qFcaRCOBBofKui++39VpaJc
EI9IzMHEuxcsgFk/ZByPkB5hmsMj4J5D0pBw1NrvpdnRMb6ci5KAGxjmm78ipFOw
2HVn0fJmyQFPO6alqN3MvHTHCmrAuh2jmgavHX/Iku6NRhMv6Q4=
=zK9z
-END PGP SIGNATURE End Message ---

Bug#982494: acpica-unix FTBFS armhf, mips64el possible patch

[Chris Hofstaedtler]

I've uploaded a possible patch to experimental, to avoid introducing
new build failures on other archs.

Diff below.


diff -Nru 
acpica-unix-20200925/debian/patches/0001-Add-in-basic-infrastructure-for-big-endian-support.patch
 
acpica-unix-20200925/debian/patches/0001-Add-in-basic-infrastructure-for-big-endian-support.patch
--- 
acpica-unix-20200925/debian/patches/0001-Add-in-basic-infrastructure-for-big-endian-support.patch
   2020-10-30 01:15:48.0 +
+++ 
acpica-unix-20200925/debian/patches/0001-Add-in-basic-infrastructure-for-big-endian-support.patch
   2021-02-16 23:24:40.0 +
@@ -30,7 +30,7 @@
  9 files changed, 242 insertions(+)
  create mode 100644 source/components/utilities/utendian.c
 
-Index: acpica-unix2-20200925/generate/unix/acpibin/Makefile
+Index: acpica-unix-20200925/generate/unix/acpibin/Makefile
 ===
 --- acpica-unix2-20200925.orig/generate/unix/acpibin/Makefile
 +++ acpica-unix2-20200925/generate/unix/acpibin/Makefile
@@ -106,7 +106,7 @@
 ===
 --- /dev/null
 +++ acpica-unix2-20200925/source/components/utilities/utendian.c
-@@ -0,0 +1,205 @@
+@@ -0,0 +1,225 @@
 
+/**
 + *
 + * Module Name: utendian -- byte swapping support for other-endianness
@@ -263,7 +263,27 @@
 +return Result;
 +}
 +#else
-+UINT64 AcpiUtReadUint64 (void *SrcPtr) { return *(UINT64 *)SrcPtr; }
++UINT64 AcpiUtReadUint64 (void *SrcPtr) {
++#if defined(ACPI_MISALIGNMENT_NOT_SUPPORTED)
++UINT64 Result = 0;
++UINT8  *Dst = (UINT8 *)&Result;
++UINT8  *Src = (UINT8 *)SrcPtr;
++
++Dst[7] = Src[7];
++Dst[6] = Src[6];
++Dst[5] = Src[5];
++Dst[4] = Src[4];
++Dst[3] = Src[3];
++Dst[2] = Src[2];
++Dst[1] = Src[1];
++Dst[0] = Src[0];
++
++return Result;
++
++#else
++return *(UINT64 *)SrcPtr;
++#endif
++}
 +#endif
 +
 
+/***
diff -Nru acpica-unix-20200925/debian/patches/fix_ftbfs_mips64el.patch 
acpica-unix-20200925/debian/patches/fix_ftbfs_mips64el.patch
--- acpica-unix-20200925/debian/patches/fix_ftbfs_mips64el.patch
1970-01-01 00:00:00.0 +
+++ acpica-unix-20200925/debian/patches/fix_ftbfs_mips64el.patch
2021-02-16 23:24:38.0 +
@@ -0,0 +1,13 @@
+Index: acpica-unix-20200925/source/include/platform/aclinux.h
+===
+--- acpica-unix-20200925.orig/source/include/platform/aclinux.h
 acpica-unix-20200925/source/include/platform/aclinux.h
+@@ -217,7 +217,7 @@
+ 
+ #if defined(__ia64__)|| (defined(__x86_64__) && !defined(__ILP32__)) ||\
+ defined(__aarch64__) || defined(__PPC64__) ||\
+-defined(__s390x__) ||\
++defined(__s390x__) || defined(__mips64) ||\
+ (defined(__riscv) && (defined(__LP64__) || defined(_LP64)))
+ #define ACPI_MACHINE_WIDTH  64
+ #define COMPILER_DEPENDENT_INT64long
diff -Nru acpica-unix-20200925/debian/patches/series 
acpica-unix-20200925/debian/patches/series
--- acpica-unix-20200925/debian/patches/series  2020-10-30 01:15:48.0 
+
+++ acpica-unix-20200925/debian/patches/series  2021-02-16 23:24:29.0 
+
@@ -61,3 +61,4 @@
 armv7-str-fixes.patch
 dbtest.patch
 ull-32bit.patch
+fix_ftbfs_mips64el.patch

Processed: severity of 981888 is important

[Debian Bug Tracking System]

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

> severity 981888 important
Bug #981888 [src:iwyu] iwyu FTBFS on mipsel: Linking CXX executable 
bin/include-what-you-use fails
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: found 982685 in 2.9.11~20110321-16, retitle 982685 to sl-modem: Depends on removed package execstack ...

[Debian Bug Tracking System]

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

> found 982685 2.9.11~20110321-16
Bug #982685 [sl-modem] sl-modem: Depends on removed package
There is no source info for the package 'sl-modem' at version 
'2.9.11~20110321-16' with architecture ''
Unable to make a source version for version '2.9.11~20110321-16'
Marked as found in versions 2.9.11~20110321-16.
> retitle 982685 sl-modem: Depends on removed package execstack
Bug #982685 [sl-modem] sl-modem: Depends on removed package
Changed Bug title to 'sl-modem: Depends on removed package execstack' from 
'sl-modem: Depends on removed package'.
> reassign 982926 wnpp
Bug #982926 [emilua] ITP Emilua
Warning: Unknown package 'emilua'
Bug reassigned from package 'emilua' to 'wnpp'.
Ignoring request to alter found versions of bug #982926 to the same values 
previously set
Ignoring request to alter fixed versions of bug #982926 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#982696: [PATCH] drm-info: FTBFS: tables.c:247:2: error: duplicate case value

[Evangelos Ribeiro Tzaras]

Hi,

On 2/16/21 6:20 PM, Dennis Filder wrote:

The attached patch drm-info-fourcc_py.patch fixes the issue by
ensuring case labels are not printed twice.


Thanks for providing a patch! Applied in [0]


I also noticed that d/watch hardcodes "drm_info" with an underscore in
the filenamemangle expression which was probably not intended.
drm-info-watchfile.patch consists of what I found in the uscan
manpage.


Again thanks for the patch! Applied in [1]


Regards,
Dennis.



@Birger: Could you upload the updated package?

[0] 
https://salsa.debian.org/swaywm-team/drm-info/-/commit/cdeeb4ee2d850dfcb5939b69ff9e5a89ad5a183d
[1] 
https://salsa.debian.org/swaywm-team/drm-info/-/commit/799b20d6ebf388bc9e2a607efa117f52bc4d2b63


Cheers

Bug#982696: drm-info: FTBFS: tables.c:247:2: error: duplicate case value

[Evangelos Ribeiro Tzaras]

Hi,

On 2/13/21 6:03 PM, Lucas Nussbaum wrote:

Source: drm-info
Version: 2.2.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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



thanks for your report!


Relevant part (hopefully):

cc -Idrm_info.p -I. -I.. -I/usr/include/libdrm -I/usr/include/json-c 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-std=c11 -D_POSIX_C_SOURCE=200809L -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-MD -MQ drm_info.p/meson-generated_.._tables.c.o -MF 
drm_info.p/meson-generated_.._tables.c.o.d -o drm_info.p/meson-generated_.._tables.c.o -c 
tables.c
tables.c: In function ‘modifier_str’:
tables.c:247:2: error: duplicate case value
   247 |  case DRM_FORMAT_MOD_LINEAR:
   |  ^~~~
tables.c:245:2: note: previously used here
   245 |  case DRM_FORMAT_MOD_LINEAR:
   |  ^~~~
tables.c:251:2: error: duplicate case value
   251 |  case DRM_FORMAT_MOD_SAMSUNG_16_16_TILE:
   |  ^~~~
tables.c:241:2: note: previously used here
   241 |  case DRM_FORMAT_MOD_SAMSUNG_16_16_TILE:
   |  ^~~~
[4/6] cc -Idrm_info.p -I. -I.. -I/usr/include/libdrm -I/usr/include/json-c 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-std=c11 -D_POSIX_C_SOURCE=200809L -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-MD -MQ drm_info.p/json.c.o -MF drm_info.p/json.c.o.d -o drm_info.p/json.c.o -c ../json.c
[5/6] cc -Idrm_info.p -I. -I.. -I/usr/include/libdrm -I/usr/include/json-c 
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra 
-std=c11 -D_POSIX_C_SOURCE=200809L -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
-MD -MQ drm_info.p/pretty.c.o -MF drm_info.p/pretty.c.o.d -o drm_info.p/pretty.c.o -c 
../pretty.c
ninja: build stopped: subcommand failed.
dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j4 -v 
returned exit code 1
make: *** [debian/rules:6: binary] Error 25




Applying the patches generously provided by Dennis Filder I can build in 
a up to date schroot.



The full build log is available from:
http://qa-logs.debian.net/2021/02/13/drm-info_2.2.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!

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

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

About the archive rebuild: The rebuild was done on 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.



Cheers

Bug#982786: marked as done (growlight: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 23:03:30 +
with message-id 
and subject line Bug#982786: fixed in growlight 1.2.31-1
has caused the Debian Bug report #982786,
regarding growlight: 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.)


-- 
982786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: growlight
Version: 1.2.28-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/g/growlight/10443325/log.gz

...
autopkgtest [11:04:28]: test blockdev: echo "blockdev -v" | growlight-readline 
-v
autopkgtest [11:04:28]: test blockdev: [---
growlight 1.2.27
libblkid 2.36.1, libpci 0x30700, libdm 1.02.175 (2021-01-08)
No ZFS support in this build.
Watching /sys/class/block/ on fd 1
scanning /sys/class/block/ on 8...
sdd -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0/block/sdd
sdf -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:5/end_device-0:5/target0:0:5/0:0:5:0/block/sdf
Numa node 1 (/sys/devices/pci:80/:80:01.0/:82:00.0//numa_node)
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Partition 1 at sdd1
Partition 1 at sdf1
Couldn't open /dev/sdd (No such file or directory)
Couldn't open /dev/sdf (No such file or directory)
sdg3 -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg/sdg3
sdb -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:1/end_device-0:1/target0:0:1/0:0:1:0/block/sdb
sdg -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg
sdg1 -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg/sdg1
Numa node 0 (/sys/devices/pci:00/:00:1f.2//numa_node)
/sys/class/block/ blocks on 15 devices for up to 1s
Controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode]
Not recursing on partition sdg3
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode]
Not recursing on partition sdg1
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Controller: Intel Corporation C610/X99 series chipset 6-Port SATA 
Controller [AHCI mode]
sdf1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:5/end_device-0:5/target0:0:5/0:0:5:0/block/sdf/sdf1
dm-0 -> ../../devices/virtual/block/dm-0
Controller: Virtual devices
sde -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:4/end_device-0:4/target0:0:4/0:0:4:0/block/sde
Partition 1 at sdb1
Model: INTEL SSDSCKJB15 revision 0121 S/N n/a type 0
sdd1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:3/end_device-0:3/target0:0:3/0:0:3:0/block/sdd/sdd1
Couldn't open /dev/sdb (No such file or directory)
sdc1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:2/end_device-0:2/target0:0:2/0:0:2:0/block/sdc/sdc1
Partition 3 at sdg3
sdb1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:1/end_device-0:1/target0:0:1/0:0:1:0/block/sdb/sdb1
sdc -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:2/end_device-0:2/target0:0:2/0:0:2:0/block/sdc
Couldn't get blkid probe for /dev/dm-0 (No such file or directory), retrying...
sde1 -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:4/end_device-0:4/target0:0:4/0:0:4:0/block/sde/sde1
Partition 1 at sdg1
sda -> 
../../devices/pci:80/:80:01.0/:82:00.0/host0/port-0:0/end_device-0:0/target0:0:0/0:0:0:0/block/sda
sdg2 -> 
../../devices/pci:00/:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdg/sdg2
Partition 2 at sdg2
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Couldn't open /dev/sdg (No such file or directory)
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Not recursing on partition sdf1
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3
Model: Micron_5100_MTFD revision U037 S/N n/a type 0
Not recursing on partition sdd1
Partition

Bug#977542: marked as done (golang-github-revel-revel: Depends on network in tests)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 22:33:39 +
with message-id 
and subject line Bug#977542: fixed in golang-github-revel-revel 1.0.0-2
has caused the Debian Bug report #977542,
regarding golang-github-revel-revel: Depends on network in tests
to be marked as done.

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

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


-- 
977542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-github-revel-revel
Version: 1.0.0-1

golang-github-revel-revel fails to run tests if the network doesn't provide
working DNS. Technically, this is a policy violation. Please disable the
relevant test or make it independent of the network.

=== RUN   TestGetCustom
--- FAIL: TestGetCustom (10.01s)
panic: Get "http://httpbin.org/get": dial tcp: lookup httpbin.org:
Temporary failure in name resolution [recovered]
panic: Get "http://httpbin.org/get": dial tcp: lookup httpbin.org:
Temporary failure in name resolution

goroutine 36 [running]:
testing.tRunner.func1.1(0x910c60, 0xc7c000)
/usr/lib/go-1.15/src/testing/testing.go:1072 +0x30d
testing.tRunner.func1(0xc000107c80)
/usr/lib/go-1.15/src/testing/testing.go:1075 +0x41a
panic(0x910c60, 0xc7c000)
/usr/lib/go-1.15/src/runtime/panic.go:969 +0x1b9
github.com/revel/revel/testing.(*TestRequest).MakeRequest(0xc000268b90)
/<>/_build/src/github.com/revel/revel/testing/testsuite.go:268
+0x4aa
github.com/revel/revel/testing.(*TestRequest).Send(0xc000268b90)
/<>/_build/src/github.com/revel/revel/testing/testsuite.go:259
+0x268
github.com/revel/revel/testing.TestGetCustom(0xc000107c80)
/<>/_build/src/
github.com/revel/revel/testing/testsuite_test.go:78 +0xc5
testing.tRunner(0xc000107c80, 0x9a2dd0)
/usr/lib/go-1.15/src/testing/testing.go:1123 +0xef
created by testing.(*T).Run
/usr/lib/go-1.15/src/testing/testing.go:1168 +0x2b3
FAIL github.com/revel/revel/testing 10.024s

Cheers,
Sven
--- End Message ---
--- Begin Message ---
Source: golang-github-revel-revel
Source-Version: 1.0.0-2
Done: Reinhard Tartler 

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

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

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated 
golang-github-revel-revel 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, 16 Feb 2021 16:33:48 -0500
Source: golang-github-revel-revel
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Reinhard Tartler 
Closes: 977542
Changes:
 golang-github-revel-revel (1.0.0-2) unstable; urgency=medium
 .
   * Team Upload
   * Skip TestGetCustom which requires network access (Closes: #977542)
Checksums-Sha1:
 07b7de1dc385296879c25af0e23faa82a0c32f9f 2812 
golang-github-revel-revel_1.0.0-2.dsc
 5e4dc060b14edbdfb9c1d9d3c633b89ff2a76614 37512 
golang-github-revel-revel_1.0.0-2.debian.tar.xz
Checksums-Sha256:
 b0792fb215137e3c49828b08b6067a16658a2355cd08501d17a775cc9f314640 2812 
golang-github-revel-revel_1.0.0-2.dsc
 fea3a257f9ec2771ce0eaa54daa8b7591acf94072a8e4da2d2b0f329be595915 37512 
golang-github-revel-revel_1.0.0-2.debian.tar.xz
Files:
 4c5ca7d33e48520930d2051d17c91b8b 2812 golang optional 
golang-github-revel-revel_1.0.0-2.dsc
 49b4123a157266a3f8ee7187f743c8ee 37512 golang optional 
golang-github-revel-revel_1.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmAsRBIUHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJss+KxAAoJNoWozPQLEc9TGU3k/6JNLmwa8J
2D5WBzh5nPnOOpXNoRUKBhmp7yE9AKpq4Ii7kqbTwlWfFH874mbhljfzPl39Pve+
vjU7NgOhnb2byaIRnFIKVvuseujjosaXysgg6gMSxIaM3q45ix98LtSipKghayVh
xSTjsAF45W9teheOMnVnRXMmvCEGrLytBlOI1N5kmu6By+kOwmtJR56RvERjzxUH
aFOj1ZmcvG3ASqIq4gWmNA98NJCdFLi874KArIL6pZG3cxB0+Gn8lwaYe57HkwSw
48ZVdWybwDiCYzh6ZBAQA2pUYIYgSPnEd/CKZx1iNKMj4Y531bf6A96LRMN7oK/L
B5ZDdm/7beyCb2i+brtOZp3vl4fTvU/lhMnWzFfnr4CINLZR1rLOha9GHYPp2cdL
08wzIpfitVH0n13u2V2Bv1MUuc3j5tyL10usAhNeKQLMSBF6d45vVZwjPr8oNn+w
erPtSMNCapqRrQH8nX/9gYRS05aQOAQWGa6pGQwMAAQdOh42/wbnqDzvqJEyNCgQ
v3ssvRMM60naeLGCPdU+kEcJptM/d

Bug#982613: marked as done (NetworkManager triggers assert in python-dbusmock test suite)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 22:18:48 +
with message-id 
and subject line Bug#982613: fixed in network-manager 1.29.90-2
has caused the Debian Bug report #982613,
regarding NetworkManager triggers assert in python-dbusmock test suite
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.)


-- 
982613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982613
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager
Version: 1.29.90-1
Severity: serious

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

...
test_add_connection (__main__.TestNetworkManager) ... ok
test_add_remove_settings (__main__.TestNetworkManager) ... ok
test_add_update_settings (__main__.TestNetworkManager) ... ok
test_connectivity_state (__main__.TestNetworkManager) ... ok
test_eth_and_wifi (__main__.TestNetworkManager) ... ok
test_get_conn_by_uuid (__main__.TestNetworkManager) ... ok
test_global_state (__main__.TestNetworkManager) ... ok
test_networking (__main__.TestNetworkManager) ... ok
test_one_eth_connected (__main__.TestNetworkManager) ... ok
test_one_eth_disconnected (__main__.TestNetworkManager) ... ok
test_one_wifi_with_accesspoints (__main__.TestNetworkManager) ... **
libnm:ERROR:libnm/nm-client.c:2863:_dbus_handle_obj_changed_dbus: assertion 
failed: (dbobj->obj_state >= NML_DBUS_OBJ_STATE_ON_DBUS)
Bail out! libnm:ERROR:libnm/nm-client.c:2863:_dbus_handle_obj_changed_dbus: 
assertion failed: (dbobj->obj_state >= NML_DBUS_OBJ_STATE_ON_DBUS)
ERROR
test_remove_connection (__main__.TestNetworkManager) ... ok
test_settings_secrets (__main__.TestNetworkManager) ... ok
test_two_eth (__main__.TestNetworkManager) ... ok
test_two_wifi_with_accesspoints (__main__.TestNetworkManager) ... ok
test_update_connection (__main__.TestNetworkManager) ... ok
test_wifi_with_active_connection (__main__.TestNetworkManager) ... ok
test_wifi_with_connection (__main__.TestNetworkManager) ... ok
test_wifi_without_access_points (__main__.TestNetworkManager) ... ok

==
ERROR: test_one_wifi_with_accesspoints (__main__.TestNetworkManager)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.bwcca9__/downtmp/build.HQy/src/tests/test_networkmanager.py",
 line 171, in test_one_wifi_with_accesspoints
subprocess.check_call(['nmcli', 'dev', 'wifi', 'connect', 'AP_3', 
'password', 's3kr1t'])
  File "/usr/lib/python3.9/subprocess.py", line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['nmcli', 'dev', 'wifi', 'connect', 
'AP_3', 'password', 's3kr1t']' died with .

--
Ran 19 tests in 3.200s

FAILED (errors=1)
autopkgtest [05:28:01]: test upstream: ---]
autopkgtest [05:28:01]: test upstream:  - - - - - - - - - - results - - - - - - 
- - - -
upstream FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.29.90-2
Done: Michael Biebl 

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager 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, 16 Feb 2021 22:54:54 +0100
Source: network-manager
Architecture: source
Version: 1.29.90-2
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Closes: 982613
Changes:
 network-manager (1.29.90-2) unstable; urgency=medium
 .
   * Add iproute2 to Build-Depends.
 Required by the test suite. Mark as  accordingly.
   * Cherry-pick fixes from upstream nm-1-30 branch
 - Fixes assertion when running the python-dbusmock test suite
   (Closes: #982613)
 - Replaces our custom polkit-agent-helper-1 patch
Checksums-Sha1:
 df3a317630bb3aad18e3e08da823affbaf351a7e 3095 net

Bug#977542: golang-github-revel-revel: Depends on network in tests

[Reinhard Tartler]

Got it.

On Tue, Feb 16, 2021 at 4:03 PM Sebastian Ramacher 
wrote:

> Control: severity -1 serious
>
> [...]
> Tests are executed as part of the binary target:
>
> dh binary --no-act  | grep auto_test
>dh_auto_test
>
> So the "no required targets may attmept network access" rule applies.
> Raising the severity accordingly. Please disable the tests that access
> the network.
>

Thanks for getting back to me. I've just made a sourceful upload that
disables the problematic test.

-- 
regards,
Reinhard

Processed: Re: Bug#982920: w3m-el: does not work with Emacs 27

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #982920 [w3m-el] w3m-el: does not work with Emacs 27
Severity set to 'important' from 'grave'
> tags -1 + unreproducible
Bug #982920 [w3m-el] w3m-el: does not work with Emacs 27
Added tag(s) unreproducible.

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

Bug#982920: w3m-el: does not work with Emacs 27

[Tatsuya Kinoshita]

Control: severity -1 important
Control: tags -1 + unreproducible

On 2021-02-16 at 16:14 +0100, Francesco Potortì wrote:
> ii  emacs-lucid [emacs]  1:27.1+1-3-dbg

BTW, is it your own build package?  If so, could you please try the
official binary package?

I've found a similar issue in Emacs bug #34094.

  - https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34094

It seems related to Emacs portable dumper.

> load-history-filename-element: Wrong type argument: stringp, (require . info)

I've grep'd w3m-el and emacs, and found that load-history-filename-element
is only used by eval-after-load in emacs.  Probably, eval-after-load
is unusable because load-history is broken in your emacs.

A workaround may be `(require 'ffap)`, because `(eval-after-load "ffap"`
is in w3m.el, though your emacs is still problematic.

Thanks,
-- 
Tatsuya Kinoshita


pgp8K7JhU4_LT.pgp
Description: PGP signature

Bug#977542: marked as pending in golang-github-revel-revel

[Reinhard Tartler]

Control: tag -1 pending

Hello,

Bug #977542 in golang-github-revel-revel 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/go-team/packages/golang-github-revel-revel/-/commit/f3a1c0a862806c283f7c0c6e09d5842396860336


Skip TestGetCustom which requires network access

Closes: #977542


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977542

Processed: Bug#977542 marked as pending in golang-github-revel-revel

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977542 [golang-github-revel-revel] golang-github-revel-revel: Depends on 
network in tests
Ignoring request to alter tags of bug #977542 to the same tags previously set

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

Bug#982730: marked as done (freedict: FTBFS: xsltCopyText: text allocation failed)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 22:04:38 +
with message-id 
and subject line Bug#982730: fixed in freedict 2021.01.05-2
has caused the Debian Bug report #982730,
regarding freedict: FTBFS: xsltCopyText: text allocation 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.)


-- 
982730: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982730
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freedict
Version: 2021.01.05-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 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 '/<>/jpn-deu'
> mkdir -p build/tei/
> /usr/share/freedict/teiaddphonetics -o build/tei/jpn-deu-phonetics.tei 
> jpn-deu.tei
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> hun-eng: Processed 4 of 139935 entries (29%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> hun-eng: Processed 45000 of 139935 entries (32%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> hun-eng: Processed 5 of 139935 entries (36%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> hun-eng: Processed 55000 of 139935 entries (39%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> deu-eng: Processed 135000 of 463244 entries (29%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> eng-deu: Processed 13 of 408553 entries (32%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> hun-eng: Processed 6 of 139935 entries (43%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> hun-eng: Processed 65000 of 139935 entries (46%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> hun-eng: Processed 7 of 139935 entries (50%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> deu-eng: Processed 14 of 463244 entries (30%).
> Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No 
> such file or directory
> Platform dictd supports this dictionary module.
> xsltproc --novalid --xinclude --stringparam dictname jpn-deu --path 
> /<>/jpn-deu/ /usr/share/freedict/xsl/tei2c5.xsl 
> build/tei/jpn-deu-phonetics.tei >build/dictd/jpn-deu.c5
> eng-deu: Processed 135000 of 408553 entries (33%).
> jpn-deu: Processed 5000 of 109546 entries (5%).
> hun-eng: Processed 75000 of 139935 entries (54%).
> jpn-deu: Processed 1 of 109546 entries (9%).
> jpn-deu: Processed 15000 of 109546 entries (14%).
> hun-eng: Processed 8 of 139935 entries (57%).
> jpn-deu: Processed 2 of 109546 entries (18%).
> hun-eng: Processed 85000 of 139935 entries (61%).
> deu-eng: Processed 145000 of 46324

Bug#982746: marked as done (live-build: autopkgtest failure on arm64, armhf and ppc64el: Failed to prepare session write run)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 21:50:40 +
with message-id 
and subject line Bug#982746: fixed in live-build 1:20210216
has caused the Debian Bug report #982746,
regarding live-build: autopkgtest failure on arm64, armhf and ppc64el: Failed 
to prepare session write run
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.)


-- 
982746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: live-build
Version: 1:20210122
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 live-build, great.
However, it fails on amd64, armhf and ppc64el. Currently this failure is
blocking the migration to testing [1]. Can you please investigate the
situation and fix it?

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

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

Paul

[1] https://qa.debian.org/excuses.php?package=live-build

https://ci.debian.net/data/autopkgtest/testing/arm64/l/live-build/9928393/log.gz

xorriso : NOTE : Environment variable SOURCE_DATE_EPOCH encountered with
value 1611350229
Drive current: -outdev 'stdio:live-image-arm64.hybrid.iso'
Media current: stdio file, overwriteable
Media status : is blank
Media summary: 0 sessions, 0 data blocks, 0 data, 19.7g free
xorriso : NOTE : -as mkisofs: Ignored option '-cache-inodes'
xorriso : WARNING : -volid text problematic as automatic mount point name
xorriso : WARNING : -volid text is too long for Joliet (30 > 16)
xorriso : WARNING : -volid text does not comply to ISO 9660 / ECMA 119 rules
Added to ISO image: directory '/'='/binary'
xorriso : UPDATE :  22 files added in 1 seconds
xorriso : UPDATE :  22 files added in 1 seconds
xorriso : NOTE : Copying to System Area: 432 bytes from file
'/usr/lib/ISOLINUX/isohdpfx.bin'
libisofs: MISHAP : Cannot patch isolinux boot image
xorriso : FAILURE : Failed to prepare session write run
xorriso : NOTE : -return_with SORRY 32 triggered by problem severity FAILURE
E: An unexpected failure occurred, exiting...
P: Begin unmounting filesystems...
P: Saving caches...
Reading package lists...
Building dependency tree...
Reading state information...
autopkgtest [06:09:10]: test build-default-image: ---]



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: live-build
Source-Version: 1:20210216
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated live-build 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, 16 Feb 2021 21:25:05 +0000
Source: live-build
Architecture: source
Version: 1:20210216
Distribution: unstable
Urgency: medium
Maintainer: Debian Live 
Changed-By: Luca Boccassi 
Closes: 982746
Changes:
 live-build (1:20210216) unstable; urgency=medium
 .
   [ Raphaël Hertzog ]
   * Add symlinks to support kali releases
 .
   [ Roland Clobus ]
   * Reproducible fix for glibc
 .
   [ Ryan Finnie ]
   * binary_syslinux: Do not modify grub theme.txt if grub/splash.png
 exists
   * Restore_package_cache: Handle existing but empty packages directory
 .
   [ Roland Clobus ]
   * The local LIVE_BUILD wins over the system live-build for the list of
 udeb inclusions. Only copy when the distribution is known
   * The local LIVE_BUILD wins over the system live-build for the list of
 udeb exclusions
   * lilo is not available any more in Bullseye (and newer), see #973850
   * Adding symlink for udeb data for bullseye
 .
   [ Luca Boccassi ]
   * Fix build on architecture without syslinux (Closes: #982746)
   * autopkgtest: restrict to amd64 and i386 for now
 .
   [ Roland Clobus ]
   * mkfs.msd

Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)

[Andreas Henriksson]

On Tue, Feb 16, 2021 at 10:35:53PM +0100, Andreas Henriksson wrote:
> Control: notfound -1 20201218-3
> Control: found -1 20210208-1
> 
> On Tue, Feb 16, 2021 at 08:20:47AM +0100, maximilian attems wrote:
> [...]
> > right it was replaced by newer cypress version and there should be
> > a symlink of that guy from the older name:
> > 
> >  Link: brcm/brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin
> > 
> > Could you please test latest 2021 upstream package with this symlink?
> 
> It seems the bug report was filed against the (working) testing version
> when (as said in subject) the problem is really in the 2021 unstable
> version. Adjusted bug metadata accordingly. (I've confirmed by checking
> the content of both versions myself.)
> 
> It seems the reason that brcm/brcmfmac43340-sdio.bin symlink is missing
> is this:
> 
> The symlink first gets installed in debian/build/install ... then
... the rest on my analysis was completly wrong.

Actually I think the problem is this commit:
https://salsa.debian.org/kernel-team/firmware-nonfree/-/commit/9c597cb850e77c2bff39378503849a92ff522353

Regards,
Andreas Henriksson

Processed: Re: Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 20201218-3
Bug #982757 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] 
brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)
No longer marked as found in versions firmware-nonfree/20201218-3.
> found -1 20210208-1
Bug #982757 [firmware-brcm80211] firmware-brcm80211: [REGRESSION] 
brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)
Marked as found in versions firmware-nonfree/20210208-1.

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

Bug#982757: firmware-brcm80211: [REGRESSION] brcm/brcmfmac43340-sdio.bin missing in sid (20210208-1)

[Andreas Henriksson]

Control: notfound -1 20201218-3
Control: found -1 20210208-1

On Tue, Feb 16, 2021 at 08:20:47AM +0100, maximilian attems wrote:
[...]
> right it was replaced by newer cypress version and there should be
> a symlink of that guy from the older name:
> 
>  Link: brcm/brcmfmac43340-sdio.bin -> ../cypress/cyfmac43340-sdio.bin
> 
> Could you please test latest 2021 upstream package with this symlink?

It seems the bug report was filed against the (working) testing version
when (as said in subject) the problem is really in the 2021 unstable
version. Adjusted bug metadata accordingly. (I've confirmed by checking
the content of both versions myself.)

It seems the reason that brcm/brcmfmac43340-sdio.bin symlink is missing
is this:

The symlink first gets installed in debian/build/install ... then
debian/rules.gen (generated by debian/bin/gencontrol.py)
does *not* install it into debian/firmware-brcm80211 .
The reason seems to be that the filename is not listed in
debian/firmware-brcm80211.metainfo.xml
(The cypress filename the symlink points to is however listed
and that gets installed as expected.)

HTH

Regards,
Andreas Henriksson

Bug#957527: marked as done (mdocml: FTBFS: make: echo: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 21:34:06 +
with message-id 
and subject line Bug#957527: fixed in mdocml 1.14.5-1
has caused the Debian Bug report #957527,
regarding mdocml: FTBFS: make: echo: No such file or directory
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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
  521 | (void)fchdir(startdir);
  |   ^~~~
main.c:569:9: warning: ignoring return value of ‘fchdir’ declared with 
attribute ‘warn_unused_result’ [-Wunused-result]
  569 |   (void)fchdir(startdir);
  | ^~~~
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
mdoc_man.o mdoc_man.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
mdoc_markdown.o mdoc_markdown.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o out.o 
out.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o tag.o 
tag.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o tree.o 
tree.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_err.o compat_err.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_fts.o compat_fts.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_getline.o compat_getline.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_getsubopt.o compat_getsubopt.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_isblank.o compat_isblank.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_mkdtemp.o compat_mkdtemp.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_ohash.o compat_ohash.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_progname.o compat_progname.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_reallocarray.o compat_reallocarray.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_recallocarray.o compat_recallocarray.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
compat_strcasestr.o compat_strcasestr.c
cc -g -O2 -fd

Bug#963406: marked as done (mdocml: FTBFS: make: echo: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 21:34:06 +
with message-id 
and subject line Bug#957527: fixed in mdocml 1.14.5-1
has caused the Debian Bug report #957527,
regarding mdocml: FTBFS: make: echo: No such file or directory
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.)


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

Hi,

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

Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   ./configure --build=x86_64-linux-gnu --prefix=/usr 
> --includedir=\${prefix}/include --mandir=\${prefix}/share/man 
> --infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
> --disable-option-checking --disable-silent-rules 
> --libdir=\${prefix}/lib/x86_64-linux-gnu 
> --libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
> --disable-maintainer-mode --disable-dependency-tracking
> file config.log: writing...
> make: echo: No such file or directory
> make: *** [/tmp/GmjayNyT:2: all] Error 127

The full build log is available from:
   http://qa-logs.debian.net/2020/06/20/mdocml_1.14.4-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated mdocml 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, 16 Feb 2021 14:09:53 -0700
Source: mdocml
Architecture: source
Version: 1.14.5-1
Distribution: unstable
Urgency: medium
Maintainer: Michael Stapelberg 
Changed-By: Bdale Garbee 
Closes: 957527
Changes:
 mdocml (1.14.5-1) unstable; urgency=medium
 .
   [Bdale Garbee]
   * merge proposed NMU content with work on new upstream version
 .
   [Michael Stapelberg]
   * New upstream version 1.14.5
   * cherry-pick assertion fix from disc...@mandoc.bsd.lv mailing list
 .
   [Francisco Vilmar Cardoso Ruviaro]
   * Add debian/patches/fix-ftbfs-with-gcc-10.patch,
 thanks to Ivo De Decker . (Closes: #957527)
   * Update debian/rules to fix FTCBFS.
Checksums-Sha1:
 4a298cb3e162f014698d2f923671eac81862af9c 1807 mdocml_1.14.5-1.dsc
 a59b05ad8012aafaee08d70f22f2ece3402b9b8c 651846 mdocml_1.14.5.orig.tar.gz
 65df413851c8c58afb4cd9d565c5a7a1c8e28788 6908 mdocml_1.14.5-1.debian.tar.xz
 e64f905e751882b5f264599dec352e83be4b84ca 5863 mdocml_1.14.5-1_amd64.buildinfo
Checksums-Sha256:
 bbd66af4ac6cab656f6c8cbec5c95bb1313aa28c2f7aea9823e30c1fc5264cc5 1807 
mdocml_1.14.5-1.dsc
 8219b42cb56fc07b2aa660574e6211ac38eefdbf21f41b698d3348793ba5d8f7 651846 
mdocml_1.14.5.orig.tar.gz
 4a488a042b4936510579aa6b2e284e588573601af616ab60786bab7f2bbc383a 6908 
mdocml_1.14.5-1.debian.tar.xz
 7f69c18501e00ec9dbeac4e8e933719c406a7cb553c43283ef3756d004fa0a8c 5863 
mdocml_1.14.5-1_amd64.buildinfo
Files:
 34a99e77a93b925a3e5da47fa979 1807 doc optional mdocml_1.14.5-1.dsc
 83557d7a94679c7dbf58d7391c919c48 651846 doc optional mdocml_1.14.5.orig.tar.gz
 ecdc4f4fd1e990742f6764c554441cb1 6908 doc optional 
mdocml_1.14.5-1.debian.tar.xz
 0b76d3de9fd96954d95fa7d42bbcbdfa 5863 doc optional 
mdocml_1.14.5-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAmAsNoEACgkQtwRxBYML
n6HfZg/+P/xeFBIxqQBon+MhX582/MlkbkhC1BbW3BNjQTvn4OBTcYpgBkjb3hff
ipc1/k7h/ySKnMcAT79SPDoPGj3w6Z6FYW41ZooBT5Ut4hh7ek6TR7/7Ye6grSZC
Qq

Bug#952219: marked as done (libhtml-calendarmonth-perl: FTBFS: dh_auto_test: error: make -j1 test TEST_VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 21:31:55 +
with message-id 
and subject line Bug#982900: Removed package(s) from unstable
has caused the Debian Bug report #952219,
regarding libhtml-calendarmonth-perl: FTBFS: dh_auto_test: error: make -j1 test 
TEST_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.)


-- 
952219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhtml-calendarmonth-perl
Version: 2.04-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200222 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/00_basic.t ... 
> 1..3
> ok 1 - use HTML::CalendarMonth;
> ok 2 - use HTML::CalendarMonth::Locale;
> ok 3 - use HTML::CalendarMonth::DateTool;
> ok
> t/01_autodetect.t .. 
> 1..145
> ok 1 - auto-detected a datetool
> ok 2 - (2010/01 Sun 1st day) using auto-select (timelocal)
> ok 3 - (2010/01 Mon 1st day) using auto-select (timelocal)
> ok 4 - (2010/02 Sun 1st day) using auto-select (timelocal)
> ok 5 - (2010/02 Mon 1st day) using auto-select (timelocal)
> ok 6 - (2010/03 Sun 1st day) using auto-select (timelocal)
> ok 7 - (2010/03 Mon 1st day) using auto-select (timelocal)
> ok 8 - (2010/04 Sun 1st day) using auto-select (timelocal)
> ok 9 - (2010/04 Mon 1st day) using auto-select (timelocal)
> ok 10 - (2010/05 Sun 1st day) using auto-select (timelocal)
> ok 11 - (2010/05 Mon 1st day) using auto-select (timelocal)
> ok 12 - (2010/06 Sun 1st day) using auto-select (timelocal)
> ok 13 - (2010/06 Mon 1st day) using auto-select (timelocal)
> ok 14 - (2010/07 Sun 1st day) using auto-select (timelocal)
> ok 15 - (2010/07 Mon 1st day) using auto-select (timelocal)
> ok 16 - (2010/08 Sun 1st day) using auto-select (timelocal)
> ok 17 - (2010/08 Mon 1st day) using auto-select (timelocal)
> ok 18 - (2010/09 Sun 1st day) using auto-select (timelocal)
> ok 19 - (2010/09 Mon 1st day) using auto-select (timelocal)
> ok 20 - (2010/10 Sun 1st day) using auto-select (timelocal)
> ok 21 - (2010/10 Mon 1st day) using auto-select (timelocal)
> ok 22 - (2010/11 Sun 1st day) using auto-select (timelocal)
> ok 23 - (2010/11 Mon 1st day) using auto-select (timelocal)
> ok 24 - (2010/12 Sun 1st day) using auto-select (timelocal)
> ok 25 - (2010/12 Mon 1st day) using auto-select (timelocal)
> ok 26 - (2011/01 Sun 1st day) using auto-select (timelocal)
> ok 27 - (2011/01 Mon 1st day) using auto-select (timelocal)
> ok 28 - (2011/02 Sun 1st day) using auto-select (timelocal)
> ok 29 - (2011/02 Mon 1st day) using auto-select (timelocal)
> ok 30 - (2011/03 Sun 1st day) using auto-select (timelocal)
> ok 31 - (2011/03 Mon 1st day) using auto-select (timelocal)
> ok 32 - (2011/04 Sun 1st day) using auto-select (timelocal)
> ok 33 - (2011/04 Mon 1st day) using auto-select (timelocal)
> ok 34 - (2011/05 Sun 1st day) using auto-select (timelocal)
> ok 35 - (2011/05 Mon 1st day) using auto-select (timelocal)
> ok 36 - (2011/06 Sun 1st day) using auto-select (timelocal)
> ok 37 - (2011/06 Mon 1st day) using auto-select (timelocal)
> ok 38 - (2011/07 Sun 1st day) using auto-select (timelocal)
> ok 39 - (2011/07 Mon 1st day) using auto-select (timelocal)
> ok 40 - (2011/08 Sun 1st day) using auto-select (timelocal)
> ok 41 - (2011/08 Mon 1st day) using auto-select (timelocal)
> ok 42 - (2011/09 Sun 1st day) using auto-select (timelocal)
> ok 43 - (2011/09 Mon 1st day) using auto-select (timelocal)
> ok 44 - (2011/10 Sun 1st day) using auto-select (timelocal)
> ok 45 - (2011/10 Mon 1st day) using auto-select (timelocal)
> ok 46 - (2011/11 Sun 1st day) using auto-select (timelocal)
> ok 47 - (2011/11 Mon 1st day) using auto-select (timelocal)
> ok 48 - (2011/12 Sun 1st day) using auto-select (timelocal)
> ok 49 - (2011/12 Mon 1st day) using auto-select (timelocal)
> ok 50 - (2012/01 Sun 1st day) using auto-select (timelocal)
> ok 51 - (2012/01 Mon 1st day) using auto-select (timelocal)
> ok 52 - (2012/02 Sun 1st day) using auto-select (timelocal)
> ok 53 - (2012/02 Mon 1st day) using auto-select (timelocal)
> ok 54 - (2012/03 Sun 1st day) using auto-select (timelocal)
> ok 55 - (2012/03 Mon 1st day) using auto-select (timelocal)
> ok 56 - (2012/04 Sun 1st day) using auto-select (timelocal)
> ok 57 -

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

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 21:05:27 +
with message-id 
and subject line Bug#982726: fixed in lepton-eda 1.9.13-4
has caused the Debian Bug report #982726,
regarding lepton-eda: 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.)


-- 
982726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lepton-eda
Version: 1.9.13-3
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210213 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> make[6]: Entering directory '/<>/liblepton/scheme'
> 
> ** (process:6207): WARNING **: 05:47:55.449: The module (geda attrib) is 
> deprecated. Please don't use it any more.
>   It has been replaced by the (lepton attrib) module.
> 
> Loading: "unit-tests/geda-deprecated.scm"
> PASS: get-attribute-name-value (1)
> 
> PASS: get-attribute-angle (1)
> PASS: get-attribute-angle (2)
> PASS: get-object-attributes (1)
> PASS: get-attrib-value-by-attrib-name (1)
> PASS: get-attrib-value-by-attrib-name (2)
> PASS: get-object-type (1)
> PASS: get-object-type (2)
> PASS: get-object-type (3)
> PASS: get-line-width (1)
> PASS: get-page-filename (1)
> PASS: set-page-filename (1)
> 
> ** (process:6208): WARNING **: 05:47:55.495: The module (geda config) is 
> deprecated. Please don't use it any more.
>   It has been replaced by the (lepton config) module.
> 
> Loading: "unit-tests/geda-attrib-basic.scm"
> PASS: geda:parse-attrib (1)
> PASS: geda:parse-attrib (2)
> PASS: geda:parse-attrib (3)
> PASS: geda:parse-attrib (4)
> PASS: geda:parse-attrib (5)
> PASS: geda:parse-attrib (6)
> PASS: geda:parse-attrib (7)
> PASS: geda:parse-attrib (8)
> 
> PASS: geda:attach-attrib (1)
> PASS: geda:attach-attrib (2)
> PASS: geda:attach-attrib (3)
> PASS: geda:attach-attrib (4)
> PASS: geda:attach-attrib (5)
> PASS: geda:attach-attrib (6)
> PASS: geda:attach-attrib (7)
> PASS: geda:attach-attrib (8)
> PASS: geda:attach-attrib (9)
> PASS: geda:attach-attrib (10)
> PASS: geda:attach-attrib (11)
> PASS: geda:attach-attrib (12)
> PASS: geda:attach-attrib (13)
> PASS: geda:attach-attrib (14)
> PASS: geda:attach-attrib (15)
> PASS: geda:attach-attrib (16)
> PASS: geda:attach-attrib (17)
> PASS: geda:attach-attrib (18)
> PASS: geda:attach-attrib (19)
> PASS: geda:attach-attrib (20)
> PASS: geda:attach-attrib (21)
> PASS: geda:attach-attrib (22)
> PASS: geda:attach-attrib (23)
> PASS: geda:attach-attrib (24)
> PASS: geda:attach-attrib (25)
> PASS: geda:attach-attrib (26)
> 
> PASS: geda:attach-attrib/page (1)
> PASS: geda:attach-attrib/page (2)
> PASS: geda:attach-attrib/page (3)
> PASS: geda:attach-attrib/page (4)
> PASS: geda:attach-attrib/page (5)
> PASS: geda:attach-attrib/page (6)
> PASS: geda:attach-attrib/page (7)
> PASS: geda:attach-attrib/page (8)
> PASS: geda:attach-attrib/page (9)
> 
> PASS: geda:detach-attrib (1)
> PASS: geda:detach-attrib (2)
> PASS: geda:detach-attrib (3)
> PASS: geda:detach-attrib (4)
> 
> PASS: geda:inherited-attribs (1)
> PASS: geda:inherited-attribs (2)
> PASS: geda:inherited-attribs (3)
> PASS: geda:inherited-attribs (4)
> 
> PASS: geda:attrib-inherited? (1)
> PASS: geda:attrib-inherited? (2)
> PASS: geda:attrib-inherited? (3)
> PASS: geda:attrib-inherited? (4)
> 
> PASS: geda:set-attrib-value! (1)
> PASS: geda:set-attrib-value! (2)
> 
> 
> Loading: "unit-tests/geda-config.scm"
> PASS: geda:default-config-context (1)
> PASS: geda:default-config-context (2)
> PASS: geda:default-config-context (3)
> PASS: geda:default-config-context (4)
> PASS: geda:default-config-context (5)
> 
> PASS: geda:system-config-context (1)
> PASS: geda:system-config-context (2)
> PASS: geda:system-config-context (3)
> PASS: geda:system-config-context (4)
> 
> PASS: geda:user-config-context (1)
> PASS: geda:user-config-context (2)
> PASS: geda:user-config-context (3)
> PASS: geda:user-config-context (4)
> 
> ERROR:
>  Unexpected exception on loading file "unit-tests/geda-config.scm":
> In ice-9/boot-9.scm:
>   1736:10 18 (with-exception-handler _ _ #:unwind? _ # _)
> In unknown file:
>   17 (apply-smob/0 #)
> In ice-9/boot-9.scm:
> 718:2 16 (call-with-prompt _ _ #)
> In ice-9/eval.scm:
> 619:8 15 (_ #(#(#)))
> In unknown file:
>   14 (%with-toplevel # #)
> In ice-9/eval.scm:
> 619:8 13 (_ #(#(#(#(#(#(#(#(#(#(#(…) …) …) …) …) …) …) …) …) …) …))
> 619:8 12 (_ #(#(#(#(#(#(#(#(#(#(#(…) …) …) …) …) …) …) …) 

Processed: Re: golang-github-revel-revel: Depends on network in tests

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #977542 [golang-github-revel-revel] golang-github-revel-revel: Depends on 
network in tests
Severity set to 'serious' from 'important'

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

Bug#982435: [screen-devel] [bug #60030] Screen segfaults by displaying some UTF-8 character combination

[Utkarsh Gupta]

Hi Axel,

On Tue, Feb 16, 2021 at 11:12 PM Axel Beckert  wrote:
> I'm running these patches (as in git) now for about 1.5 days on
> Stretch and Buster in production. I'd say if I don't find any
> regression until Wednesday evening (i.e. in 1 day), feel free to
> finalise the packages as needed (the're currently all sporting
> "UNRELEASED" in the debian/changelog) and release them.
>
> Please push your changes and tags into the git repo. It's in
> collab-maint^Wthe "debian" group, so you should have write access.

Sure thing, once you give a go-ahead, I'll edit the changelog entry
and shall push that to the salsa repository.

> If you want to prepare a Jessie ELTS update, feel free to use the
> existing jessie branch in git. (It has no commit besides those being
> part of the master branch. Not sure why I or someone else has created
> it already.)

There's no "jessie" branch on salsa, at least. So I created one with
the latest dsc (4.2.1-3+deb8u1) and added 2 commits on top of it. By
importing the dsc and creating a branch out of it, the commit history,
I am afraid, is lost. Do you want to restore all that? I'll be happy
to do that after checking out from master and then applying +deb8u1
changes and then pushing mine on top of it, but I don't see any value
to it, really. But with your maintainer hat on, if you want me to do
that, I'll do so! :)

The jessie branch atm looks like this:
https://salsa.debian.org/debian/screen/-/tree/jessie

Please let me know if you have any questions or suggestions or if you
hoped to see something else than this? :)


- u

Bug#982625: marked as done (fails to authenticate with "TypeError: sequence item 2: expected str instance, bytes found" error)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 20:33:33 +
with message-id 
and subject line Bug#982625: fixed in offlineimap3 
0.0~git20210105.00d395b+dfsg-3
has caused the Debian Bug report #982625,
regarding fails to authenticate with "TypeError: sequence item 2: expected str 
instance, bytes found" error
to be marked as done.

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

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


-- 
982625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: offlineimap
Version: 7.3.3+dfsg1-1+0.0~git20210105.00d395b+dfsg-2
Severity: serious

In Debian testing offlineimap plain authentication over SSL started to fail for
me in the following way:

$ offlineimap -c ~/.config/offlineimap/offlineimaprc -u basic --info
OfflineIMAP 7.3.0
  Licensed under the GNU GPL v2 or any later version (with an OpenSSL 
exception)
imaplib2 v3.05, Python v3.9.1+, OpenSSL 1.1.1i  8 Dec 2020
  imaplib2: 3.05
Remote repository 'Censored: type 'IMAP'
Host: mail.example.org Port: None SSL: True
Establishing connection to mail.example.org:993 (Censored)
Traceback (most recent call last):
  File "/usr/bin/offlineimap", line 22, in 
oi.run()
  File "/usr/share/offlineimap3/offlineimap/init.py", line 88, in run
self.__serverdiagnostics(options)
  File "/usr/share/offlineimap3/offlineimap/init.py", line 518, in 
__serverdiagnostics
account.serverdiagnostics()
  File "/usr/share/offlineimap3/offlineimap/accounts.py", line 197, in 
serverdiagnostics
self.ui.serverdiagnostics(remote_repo, 'Remote')
  File "/usr/share/offlineimap3/offlineimap/ui/UIBase.py", line 450, in 
serverdiagnostics
conn = repository.imapserver.acquireconnection()
  File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 592, in 
acquireconnection
self.__authn_helper(imapobj)
  File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 449, in 
__authn_helper
if func(imapobj):
  File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 375, in 
__authn_plain
imapobj.authenticate('PLAIN', self.__plainhandler)
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 691, in 
authenticate
typ, dat = self._simple_command('AUTHENTICATE', mechanism.upper())
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 1684, in 
_simple_command
return self._command_complete(self._command(name, *args), kw)
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 1404, in _command
literal = literator(data, rqb)
  File "/usr/lib/python3/dist-packages/imaplib2.py", line 2247, in process
ret = self.mech(self.decode(data))
  File "/usr/share/offlineimap3/offlineimap/imapserver.py", line 217, in 
__plainhandler
retval = NULL.join((authz, authc, passwd))
TypeError: sequence item 2: expected str instance, bytes found

The server in question has a valid letsencrypt certificate, which I can use and
authenticate fine with other clients.

Not sure if the problem is actually in offlineimap or in imaplib2, but no
relevant bugs seems to be reported against the latter either.

Thanks for maintaining offlineimap,
Cheers

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

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

Versions of packages offlineimap depends on:
ii  offlineimap3  0.0~git20210105.00d395b+dfsg-2

offlineimap recommends no packages.

offlineimap suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: offlineimap3
Source-Version: 0.0~git20210105.00d395b+dfsg-3
Done: Sudip Mukherjee 

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

Debian distribution maintenance software
pp.
Sudip Mukherjee  (supplier of updated offlineimap3 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please

Processed: missed meta code

[Debian Bug Tracking System]

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

> tag 980680 patch
Bug #980680 [src:tqdm] tqdm: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.9 returned exit code 13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#980638: unattended-upgrades: FTBFS: AssertionError: False is not true : Can not find 'Removing unused kernel packages: linux-image-4.05.0-1021-kvm

[Paul Gevers]

control: tags -1 patch

Found upstream:

https://github.com/mvo5/unattended-upgrades/pull/282

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: unattended-upgrades: FTBFS: AssertionError: False is not true : Can not find 'Removing unused kernel packages: linux-image-4.05.0-1021-kvm

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #980638 [src:unattended-upgrades] unattended-upgrades: FTBFS: 
AssertionError: False is not true : Can not find 'Removing unused kernel 
packages: linux-image-4.05.0-1021-kvm
Added tag(s) patch.

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

Bug#980680: tqdm: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

[Paul Gevers]

tags -1 patch

It's a hack, disabling the test:
https://salsa.debian.org/python-team/packages/tqdm/-/merge_requests/1

If nothing happens, I'll NMU in the near future.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#982746: marked as pending in live-build

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #982746 in live-build 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/live-team/live-build/-/commit/b968e2c0f7625f679bbbe6db12feb30f4b7f3598


Fix build on architecture without syslinux

Don't run xorriso with -isohybrid-mbr if LB_BOOTLOADER_BIOS is
not set to syslinux

Closes: #982746


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982746

Processed: Bug#982746 marked as pending in live-build

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982746 [src:live-build] live-build: autopkgtest failure on arm64, armhf 
and ppc64el: Failed to prepare session write run
Added tag(s) pending.

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

Bug#982859: marked as done (libcmis-dev: allowable-actions.hxx uses non-existing file boost/shared_ptr.hpp)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 19:19:10 +
with message-id 
and subject line Bug#982859: fixed in libcmis 0.5.2-3
has caused the Debian Bug report #982859,
regarding libcmis-dev: allowable-actions.hxx uses non-existing file 
boost/shared_ptr.hpp
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.)


-- 
982859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcmis-dev
Version: 0.5.2-2+b2
Severity: serious

Configuring upstream's LibreOffice fails with an obscure error:

checking whether g++ supports C++17... configure: error: no
Error running configure at ./autogen.sh line 316.

In the config.log file:

configure:18900: checking whether g++ supports C++17
configure:18962: g++ -c  -std=c++17 -Werror -DSYSTEM_LIBCMIS -isystem 
/usr/include/libcmis-0.5 -isystem /usr/include/x86_64-linux-gnu -isystem 
/usr/include/libxml2  conftest.cpp >&5
In file included from /usr/include/libcmis-0.5/libcmis/libcmis.hxx:33,
 from conftest.cpp:93:
/usr/include/libcmis-0.5/libcmis/allowable-actions.hxx:34:10: fatal error: 
boost/shared_ptr.hpp: No such file or directory
   34 | #include 
  |  ^~

Indeed, /usr/include/libcmis-0.5/libcmis/allowable-actions.hxx
from libcmis-dev has:

#include 

and there's no such file.

Now, I don't know whether this file is really needed, in which case
I suppose that there is a missing dependency on libboost1.74-dev
(currently).

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

Kernel: Linux 5.10.0-1-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.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 libcmis-dev depends on:
ii  libcmis-0.5-5v5  0.5.2-2+b2
ii  libcurl4-gnutls-dev  7.74.0-1.1
ii  libxml2-dev  2.9.10+dfsg-6.3+b1

libcmis-dev recommends no packages.

libcmis-dev suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: libcmis
Source-Version: 0.5.2-3
Done: Rene Engelhard 

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libcmis 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, 16 Feb 2021 20:03:30 +0100
Source: libcmis
Architecture: source
Version: 0.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 982859
Changes:
 libcmis (0.5.2-3) unstable; urgency=medium
 .
   * depend on libcmis-dev (closes: #982859)
Checksums-Sha1:
 561df948f1dc170b1d0dc0eaf3e01a2c44cdc7f6 2157 libcmis_0.5.2-3.dsc
 9c549a27359969c83755eaee570b7a9df56daa5b 4692 libcmis_0.5.2-3.debian.tar.xz
 b3695f462efebfcaeaa9d7b49dda3bf9bc98 5728 libcmis_0.5.2-3_source.buildinfo
Checksums-Sha256:
 09c68a765b20dc30308dd20c1a4e317b1d6d01bb6c963fb701bd5daf636c0546 2157 
libcmis_0.5.2-3.dsc
 fa651f06436117c0ac3334a2f9dd72149786707ad9f3bee8e17b0f6a80d68687 4692 
libcmis_0.5.2-3.debian.tar.xz
 5f7dbf49be3ba033bd66abefa51dd02ecf37dfba9c5e1cde8d4d7eee2cf7a4c2 5728 
libcmis_0.5.2-3_source.buildinfo
Files:
 c0e853005a40e635845ca5a4776cf592 2157 libs optional libcmis_0.5.2-3.dsc
 584ce41fb439c96be5ced16952fe4203 4692 libs optional 
libcmis_0.5.2-3.debian.tar.xz
 2fc95e601a428c950d25a247d9732494 5728 libs optional 
libcmis_0.5.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuF

Bug#982859: libcmis-dev: allowable-actions.hxx uses non-existing file boost/shared_ptr.hpp

[Rene Engelhard]

Hi,

Am 15.02.21 um 15:56 schrieb Vincent Lefevre:
> Now, I don't know whether this file is really needed, in which case
> I suppose that there is a missing dependency on libboost1.74-dev
> (currently).

Hmm, yes.

Looks like libcmis-dev needs a Depends: libboost-dev...


Regards,


Rene

Processed: Re: Bug#982172 closed by Debian FTP Masters (reply to Michael Banck ) (Bug#982172: fixed in cp2k 8.1-7)

[Debian Bug Tracking System]

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

> # otherwise the bts gets confused
> reassign 982172 src:cp2k 8.1-5
Bug #982172 {Done: Michael Banck } [src:libint2, src:cp2k] 
libint2 breaks cp2k autopkgtest
Bug reassigned from package 'src:libint2, src:cp2k' to 'src:cp2k'.
No longer marked as found in versions libint2/2.6.0-11 and cp2k/8.1-5.
No longer marked as fixed in versions cp2k/8.1-7.
Bug #982172 {Done: Michael Banck } [src:cp2k] libint2 breaks 
cp2k autopkgtest
Marked as found in versions cp2k/8.1-5.
> fixed 982172 8.1-7
Bug #982172 {Done: Michael Banck } [src:cp2k] libint2 breaks 
cp2k autopkgtest
Marked as fixed in versions cp2k/8.1-7.
> # I wonder if libint2 should add a breaks to prevent partial upgrades
> affects 982172 src:libint2
Bug #982172 {Done: Michael Banck } [src:cp2k] libint2 breaks 
cp2k autopkgtest
Added indication that 982172 affects src:libint2
> thanks
Stopping processing here.

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

Processed: python-pymetar: diff for NMU version 1.2-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 835340 + pending
Bug #835340 [python-pymetar] python-pymetar: http://weather.noaa.gov/ no longer 
available
Ignoring request to alter tags of bug #835340 to the same tags previously set
> tags 938076 + pending
Bug #938076 [src:python-pymetar] python-pymetar: Python2 removal in sid/bullseye
Bug #966784 [src:python-pymetar] python-pymetar: Unversioned Python removal in 
sid/bullseye
Ignoring request to alter tags of bug #938076 to the same tags previously set
Ignoring request to alter tags of bug #966784 to the same tags previously set

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

Processed: python-pymetar: diff for NMU version 1.2-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 835340 + pending
Bug #835340 [python-pymetar] python-pymetar: http://weather.noaa.gov/ no longer 
available
Added tag(s) pending.
> tags 938076 + pending
Bug #938076 [src:python-pymetar] python-pymetar: Python2 removal in sid/bullseye
Bug #966784 [src:python-pymetar] python-pymetar: Unversioned Python removal in 
sid/bullseye
Added tag(s) pending.
Added tag(s) pending.

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

Bug#982850: duperemove: first run fails errror 13?

[Dennis Filder]

Control: tag -1 moreinfo

This doesn't look like a bug to me.  Notice that the database is 5 GB
in size, and the indexes aren't even created yet.  You just need more
diskspace.  Try running duperemove on a subset of your files to see
how much space the DB needs for that and extrapolate from there.

You could also politely ask the developer on github whether he'd
consider adding a feature that more accurately computes the projected
diskspace; I cobbled together this awk program using the formula
mentioned in the manpage which should already be close after some
tweaking:

find /home -type f -printf '%s %p\n' \
| awk -M -e '{h+=$1;c+=length($0)-length($1)-1;};' \
 -e 'END{printf "%i bytes\n", 90*(int(h/(128*1024))+1)+c}'

If you want to investigate this further, try to run the command again
like this (install package strace if you haven't already) and post the
last 30 or so lines:

strace -f duperemove -r -A -h --skip-zeroes \
--hashfile=/var/cache/duperemove-home-user /home/user/

Otherwise you should watch how the disk space situation develops while
duperemove is running:

while sleep 10; do df -h /var ; done | tee /tmp/df.log

Regards,
Dennis.

Processed: duperemove: first run fails errror 13?

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #982850 [duperemove] duperemove: first run fails errror 13?
Added tag(s) moreinfo.

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

Bug#982927: Support for 6.x has ceased, newer branches no longer FLOSS

[Moritz Muehlenhoff]

Package: otrs
Severity: serious

The 6.x branch is EOLed:
https://otrs.com/release-notes/attention-security-risk-with-otrs-6/

Since the 7.x and 8.x branches don't have source available (and
no FLOSS version of 7.x was announced), we should not include
it in bullseye I guess.

There are some forks announced, but not sure what comes out of
it in reality: https://forums.otterhub.org/viewtopic.php?t=41628

Cheers,
Moritz

Bug#958912: marked as done (devscripts: missing ubuntu release info breaks autopkgtest)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 17:48:26 +
with message-id 
and subject line Bug#958912: fixed in devscripts 2.21.1
has caused the Debian Bug report #958912,
regarding devscripts: missing ubuntu release info breaks autopkgtest
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.)


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

Hi,

It seems the autopkgtest for devscript fails when the current ubuntu version
is unknown:

https://ci.debian.net/data/autopkgtest/testing/amd64/d/devscripts/5161251/log.gz

testUbuntuIncrement
ASSERT:error output of dch --no-conf -c "/tmp/shunit.VOe8J9/tmp/changelog" 
--vendor Ubuntu -i "Version test."\n expected:<> but was:

testUbuntuRebuild
ASSERT:error output of dch --no-conf -c "/tmp/shunit.VOe8J9/tmp/changelog" 
--vendor Ubuntu -R "Version test."\n expected:<> but was:


When the name of the current ubunto release is unknown, this test should
probaby be skipped, instead of failing, as it is not an issue with devscripts.


The trigger for this issue is in the releasedate for a new ubuntu release,
which is included in the latest distro-info-data, which is not yet in testing
(it will probably migrate in a few days).

However, this is a bug in the devscript test. The devscripts autopkgtest
shouldn't start failing if the data for ubuntu is outdated or missing in
testing, stable, oldstable, ...

Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Source: devscripts
Source-Version: 2.21.1
Done: Mattia Rizzolo 

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated devscripts 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, 16 Feb 2021 17:45:53 +0100
Source: devscripts
Architecture: source
Version: 2.21.1
Distribution: unstable
Urgency: medium
Maintainer: Devscripts Maintainers 
Changed-By: Mattia Rizzolo 
Closes: 955049 955123 955307 958750 958912 961861 961862 977809
Changes:
 devscripts (2.21.1) unstable; urgency=medium
 .
   [ Mattia Rizzolo ]
   * setup.py:
 + Produce a __init__.py at build time, containing the Devscripts version.
   * uscan:
 + Set the umask while running `svn export`, so as to produce a
   reproducible tarball with mode=svn.
   * tests:
 + Undefine some variables that might affect the tests.
 + Run again all tests on hurd, glibc 2.31-6 fixed sem_open().
 + test_debrepro, test_uscan_ftp, test_uscan_svn: skip the tests on
   kfreebsd, as support for the required sem_open() is lacking.
 + test_uscan_mangle: do not call helperWatch multiple times in a test, to
   prevent leftover background processes.
 + test_debchange: skip Ubuntu tests when there is no known development
   release, like right after an Ubuntu release.  Closes: #958912
   * d/control:
 + Remove Pierre-Elliott Bécue from Uploaders;
   thank you for all your past contributions!
   * d/lintian-overrides:
 + Update to match the newer lintian output.
   * d/copyright:
 + Fix some issues spotted by lintian.
 .
   [ Xavier Guimard ]
   * salsa:
 + Fix bash completion.
   * uscan:
 + Dicrease checksum message from warning to verbose.
 + Fix verbosity when USCAN_VERBOSE=yes
 .
   [ Baptiste Beauplat ]
   * namechck:
 + Remove some dead URLs.  MR: !215
 .
   [ Michel Le Bihan ]
   * debchange:
 + Warn when DEBEMAIL and EMAIL are not set.  Closes: #977809
 .
   [ Johannes Schauer ]
   * debbisect (MR: !214):
 + Fix installation path of the internal scripts.
 + Use os.path.lexist instead of os.path.exist when checking symlinks.
 + Set the PATH environment variable to a sensible default if it's not set.
 + Automatically retry a download aborted by snapshot.d.o after 10 seconds.
 + Instead of appending, seek to the correct position in the output file.
   * debrebuild (MR: !212):
 + Unconditionally se

Bug#982730: freedict: FTBFS: Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No such file or directory

[Sebastian Humenda]

Hi

Dennis Filder schrieb am 16.02.2021, 18:26 +0100:
>The build process ran out of memory when processing
>build/dictd/eng-deu.c5 at 31% and 34% completion as these dictionaries
>are just so large. 

I was asking upfront on debian-admin whether the actual  limits would be
known, but nobody knew.

>The only real chance at a quick solution IMHO is
>--max-parallel=1 and hoping that it works. 

It should, it's around 9G of RAM that is required. I'll prepare an upload.

>Upstream devs should consider using chunking the way Docbook offers
>it.

Not sure how Docbook is required, but it's IMHO hard to chunk since the
expressions span the whole dictionary. In any case, the problem is known
upstream, there's just a lack of helping hands :).

Thanks
Sebastian

Bug#982435: [screen-devel] [bug #60030] Screen segfaults by displaying some UTF-8 character combination

[Axel Beckert]

Hi Utkarsh,

Utkarsh Gupta wrote:
> > What so far was in git in the stretch and buster branches was
> > incomplete and did FTBFS for multiple reasons. (Just pushed a bunch of
> > fixes. It at least builds now on both releases.)
> >
> > And in Stretch the patch didn't even apply properly and needed manual
> > massaging. So at least for Stretch (and Jessie) this needs additional
> > testing.
> 
> Oh sure! I'll hold off any work until uploads in other releases have
> been settled down.

I'm running these patches (as in git) now for about 1.5 days on
Stretch and Buster in production. I'd say if I don't find any
regression until Wednesday evening (i.e. in 1 day), feel free to
finalise the packages as needed (the're currently all sporting
"UNRELEASED" in the debian/changelog) and release them.

Please push your changes and tags into the git repo. It's in
collab-maint^Wthe "debian" group, so you should have write access.

If you want to prepare a Jessie ELTS update, feel free to use the
existing jessie branch in git. (It has no commit besides those being
part of the master branch. Not sure why I or someone else has created
it already.)

I can also send you signed git commit hashes of my most recent commits
in these branches if you prefer that to be on the safe side.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#982730: freedict: FTBFS: Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No such file or directory

[Dennis Filder]

Control: tag -1 + moreinfo
Control: retitle -1 freedict: FTBFS: xsltCopyText: text allocation failed
X-Debbugs-CC: lu...@debian.org

The build process ran out of memory when processing
build/dictd/eng-deu.c5 at 31% and 34% completion as these dictionaries
are just so large.  The only real chance at a quick solution IMHO is
--max-parallel=1 and hoping that it works.  Otherwise you're gonna
need a build host with 3-4 times as much RAM.

Upstream devs should consider using chunking the way Docbook offers
it.

Processed: freedict: FTBFS: Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #982730 [src:freedict] freedict: FTBFS: Failed to create secure directory 
(/sbuild-nonexistent/.config/pulse): No such file or directory
Added tag(s) moreinfo.
> retitle -1 freedict: FTBFS: xsltCopyText: text allocation failed
Bug #982730 [src:freedict] freedict: FTBFS: Failed to create secure directory 
(/sbuild-nonexistent/.config/pulse): No such file or directory
Changed Bug title to 'freedict: FTBFS: xsltCopyText: text allocation failed' 
from 'freedict: FTBFS: Failed to create secure directory 
(/sbuild-nonexistent/.config/pulse): No such file or directory'.

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

Bug#982696: [PATCH] drm-info: FTBFS: tables.c:247:2: error: duplicate case value

[Dennis Filder]

Control: tag -1 + patch upstream

The attached patch drm-info-fourcc_py.patch fixes the issue by
ensuring case labels are not printed twice.

I also noticed that d/watch hardcodes "drm_info" with an underscore in
the filenamemangle expression which was probably not intended.
drm-info-watchfile.patch consists of what I found in the uscan
manpage.

Regards,
Dennis.


drm-info-fourcc_py.patch.gz
Description: application/gzip


drm-info-watchfile.patch.gz
Description: application/gzip

Processed: [PATCH] drm-info: FTBFS: tables.c:247:2: error: duplicate case value

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch upstream
Bug #982696 [src:drm-info] drm-info: FTBFS: tables.c:247:2: error: duplicate 
case value
Added tag(s) patch and upstream.

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

Bug#982920: w3m-el: does not work with Emacs 27

[Tatsuya Kinoshita]

On 2021-02-16 at 16:14 +0100, Francesco Potortì wrote:
> Loading w3m...
> load-history-filename-element: Wrong type argument: stringp, (require . info)

Unreproducible for me.  Could you please provide backtrace?

# rm /usr/share/emacs/site-lisp/w3m/*.elc
$ emacs
M-x toggle-debug-on-error RET
M-x w3m RET
$ emacs --no-init-file
M-x w3m RET

If `emacs --no-init-file` works, the trigger may be in your init file.

> Since the version on testing is from 2018, I guess it just needs upgrade
> to the current one, which supports Emacs 27 as stated at
> https://github.com/emacs-w3m/emacs-w3m

w3m-el-snapshot 1.4.632+0.20210201.2305.54c3ccd-1 is available.

Thanks,
-- 
Tatsuya Kinoshita


pgp_xM8Is7KNh.pgp
Description: PGP signature

Bug#982924: what-is-python: The python-is-python3 and python-dev-is-python3 packages should not exist

[Zack Weinberg]

Source: what-is-python
Version: 3.8.6-3
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: za...@panix.com

Any system where the unqualified command names ‘python’ and/or
‘python-config’, or the well-known pathname /usr/bin/python, refer to
Python 3, is misconfigured.  These names need to be **permanently**
reserved for the legacy Python 2 interpreter, even after Debian ceases
to ship Python 2, or you risk breaking unpackaged software that has
not yet been ported to Python 3.  Unpackaged Python-2-only software
will continue to exist indefinitely—I am *certain* that I will still
need a Python 2 interpreter ten years from now, and I fully expect my
grandchildren will occasionally trip over Python-2-only software even
a hundred years from now.

(I am aware that PEP 394 explicitly licenses ‘python’ to run the
Python 3 interpreter.  PEP 394 is wrong.  It is my understanding that
the authors of PEP 394 felt they could not declare various
distributions (e.g. arch), that had already made ‘python’ run the v3
interpreter, to be buggy—but they should have.)

Please remove the python-is-python3 and python-dev-is-python3 packages
from Debian, and document in Debian’s Python policy that the
unqualified command names ‘python’ and ‘python-config’ and the
pathname /usr/bin/python are **permanently** reserved for the Python 2
interpreter.

I cannot overstate how much I mean **permanently**.  Forever.

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

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

Processed: libsass-python FTBFS: possible issue in libsass_3.6.4+20201122-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #980628 [src:libsass-python] libsass-python: FTBFS: tests failed
Severity set to 'important' from 'serious'

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

Bug#980628: libsass-python FTBFS: possible issue in libsass_3.6.4+20201122-1

[Frédéric Bonnard]

Control: severity -1 important

--

As explained upstream, the behaviour of the tests changed after
libsass's commit "fix how we count unicode characters" that
libsass_3.6.4+20201122-1 pulled.
But upstream's libsass-python doesn't not support non-release of
libsass and they wouldn't help on our issue till libsass 3.6.5 goes out.
I'd trust the "fix how we count unicode characters" and thus, I guess,
the tests may need to be changed.
For the time being, I'll lower the severity of the bug.


F.


signature.asc
Description: PGP signature

Bug#982786: growlight: autopkgtest regression

[Nick Black]

ok, the good news is that with 1.2.30, we're no longer seeing
the segfault. the bad news is that we error out due to an
inability to load up notcurses without a TERM variable.

the proper fix for this is to avoid using notcurses in any case
where we're not connected to a tty. i can get this done today,
but it will be a slightly more invasive patch (~20 lines, i
would guess). it'll still be tightly targeted at this problem.

once again, this is a use case that doesn't really reflect how
the tool would be used, and while it's a real regression, it is
being highlit primarily due to how the autopkgtests are run. i
don't want to disable the autopkgtests, but i also don't want to
get bounced from the release due to this.

my plan is to address this today, cut it as 1.2.31, and upload
it to unstable. sorry for the churn during soft freeze. =[

Bug#982921: python3-packaging: missing dependency on python3-distutils

[Richard Schütz]

Package: python3-packaging
Version: 20.9-1
Severity: serious
Justification: Policy 3.5

Dear Maintainer,

python3-packaging needs python3-distutils to work correctly:

Traceback (most recent call last):
  […]
from packaging.specifiers import SpecifierSet
  File "/usr/lib/python3/dist-packages/packaging/specifiers.py", line 14, in 

from .utils import canonicalize_version
  File "/usr/lib/python3/dist-packages/packaging/utils.py", line 9, in 
from .tags import Tag, parse_tag
  File "/usr/lib/python3/dist-packages/packaging/tags.py", line 7, in 
import distutils.util
ModuleNotFoundError: No module named 'distutils.util'


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

Kernel: Linux 5.10.0-3-cloud-amd64 (SMP w/8 CPU threads)
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 python3-packaging depends on:
ii  python33.9.1-1
ii  python3-pyparsing  2.4.7-1

python3-packaging recommends no packages.

python3-packaging suggests no packages.

-- no debconf information

Bug#982920: w3m-el: does not work with Emacs 27

[Francesco Potortì]

Package: w3m-el
Version: 1.4.632+0.20181112-8
Severity: grave
X-Debbugs-Cc: none, Francesco Potortì 

Loading w3m...
load-history-filename-element: Wrong type argument: stringp, (require . info)

Since the version on testing is from 2018, I guess it just needs upgrade
to the current one, which supports Emacs 27 as stated at
https://github.com/emacs-w3m/emacs-w3m


-- 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.10.0-3-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 w3m-el depends on:
ii  dpkg 1.20.7.1
ii  emacs1:27.1+1-3-dbg
ii  emacs-lucid [emacs]  1:27.1+1-3-dbg
ii  emacsen-common   3.0.4
ii  install-info 6.7.0.dfsg.2-6
ii  w3m  0.5.3+git20210102-2

Versions of packages w3m-el recommends:
ii  apel  10.8+0.20201106-1
ii  flim  1:1.14.9+0.20201117-2

Versions of packages w3m-el suggests:
ii  bzip21.0.8-4
ii  imagemagick  8:6.9.11.60+dfsg-1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1
ii  libmoe1.51.5.8-5+b1
ii  markdown 1.0.1-10.1
ii  namazu2  2.0.21-23
ii  perl-doc 5.32.1-2
ii  poppler-utils [xpdf-utils]   20.09.0-3.1
pn  ppthtml  
ii  wv   1.2.9-4.2+b2
pn  xlhtml   

-- no debconf information

Bug#982790: wlroots: started transition during soft freeze

[nicoo]

Hi Sebastian,


On Sun, Feb 14, 2021 at 02:49:27PM +0100, Sebastian Ramacher wrote:
> The upload of 0.12.0-2 just started a transition. Note that we are in
> soft freeze and hence transitions are no longer acceptable for bullseye.

Apologies for this: I had discussed this on #debian-devel on 2020-02-04
with (amongst others) elbrus, at which time I pinged the maintainers of
wlroots on IRC, but waited 10 days before the upload and missed that
the soft freeze window had started.

The delay & forgetting was mostly due to some mess elsewhere in Debian
eating up all my energy; I can tell you privately if it's relevant, but
it might suffice to say that antiharassment@ and DAM were involved. >_>'


> The purpose of this bug is to block wlroots from migrating to testing.

Makes sense.


> Please either revert to 0.11.0 or keep this bug open until after the
> release of bullseye.

Would it still be possible (assuming that's also Guido's preferred
solution) to request an unblock?

I uploaded at the same time a version of sway that works with it (which I've
been running for >1 month, so it's been tested) and confirmed that phox builds
against wlroots 0.12 too.  Guido mentionned he is running phox against wlroots
0.12, so that is tested too.


For reference, the ABI breakage & soname change is due to wlroots making
some part of its API private, and removing obsolete & unstable functionality
(functions wlr_xdg_*_v6_*), which account for the largest part of the diff.
I attached the debdiff, and upstream's changelog is there:
  https://github.com/swaywm/wlroots/releases/tag/0.12.0

I believe that having the same ABI and API as upstream's in Bullseye would make
maintaining wlroots easier, but I'll of course yield to Guido's opinion on this.


Again, apologies to everyone involved for the poor coordination; as I
mentionned, I'm recovering from dealing with something else, but I still
should have held back on kicking off this transition & re-checked with
everyone involved.


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#980042: marked as done (mailutils: movemail doesn't remove extracted emails)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 14:53:43 +
with message-id 
and subject line Bug#980042: fixed in mailutils 1:3.11.1-5
has caused the Debian Bug report #980042,
regarding mailutils: movemail doesn't remove extracted emails
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.)


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

Dear maintainer,

Since I upgraded mailutils from 1:3.10-3+b1 to 1:3.11.1-2 a couple of
days ago, movemail doesn't remove extracted emails anymore from the
source mbox file (I do *not* use option --keep-messages).

Example:

  1) Verify that /var/mail/$USER is empty.

  2) echo Bla | mail -s "Test movemail" $USER

  3) 'ls -l /var/mail/$USER' now reports size 573 bytes (it contains the
 test email sent in step 2).

  4) /usr/bin/movemail.mailutils /var/mail/$USER /tmp/extracted-mail

  5) No error reported, test email was properly extracted to
 /tmp/extracted-mail, but /var/mail/$USER is still 573 bytes long.

This has the following consequence when I use my mail client (Gnus,
which can use movemail to read mbox files): since the upgrade to
mailutils 1:3.11.1-2, *every time I check my mail box*, new copies of
every email stored in /var/mail/$USER are retrieved. A nightmare...

I verified yesterday that the following downgrade of mailutils fixes the
problem:

  [REMOVE, NOT USED] libmailutils8:amd64 1:3.11.1-2
  [INSTALL, DEPENDENCIES] libmailutils7:amd64 1:3.10-3+b1
  [DOWNGRADE] mailutils:amd64 1:3.11.1-2 -> 1:3.10-3+b1
  [DOWNGRADE] mailutils-common:amd64 1:3.11.1-2 -> 1:3.10-3

Today, I upgraded to the latest version in unstable (1:3.11.1-4).
Unfortunately, this caused the problem to reappear, hence this report.

Thanks for your work, kind regards.

Florent

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

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

Versions of packages mailutils depends on:
ii  libc6 2.31-9
ii  libcrypt1 1:4.4.17-1
ii  libfribidi0   1.0.8-2
ii  libgnutls30   3.7.0-5
ii  libgsasl7 1.10.0-3
ii  libldap-2.4-2 2.4.56+dfsg-1
ii  libmailutils8 1:3.11.1-4
ii  libncurses6   6.2+20201114-2
ii  libpam0g  1.4.0-2
ii  libreadline8  8.1-1
ii  libtinfo6 6.2+20201114-2
ii  libunistring2 0.9.10-4
ii  mailutils-common  1:3.11.1-4

Versions of packages mailutils recommends:
ii  postfix [mail-transport-agent]  3.5.6-1

Versions of packages mailutils suggests:
pn  mailutils-doc  
pn  mailutils-mh   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mailutils
Source-Version: 1:3.11.1-5
Done: Jordi Mallach 

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated mailutils 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, 09 Feb 2021 16:17:12 +0100
Source: mailutils
Architecture: source
Version: 1:3.11.1-5
Distribution: unstable
Urgency: medium
Maintainer: Jordi Mallach 
Changed-By: Jordi Mallach 
Closes: 980042
Changes:
 mailutils (1:3.11.1-5) unstable; urgency=medium
 .
   * Enable PostgreSQL support now that OpenSSL is considered a system
 library by Debian ftpmaster.
   * Add upstream patch to fix expunging of mboxes on read-only directories
 (like Debian's /var/mail). Thanks to Pierrick Chanteux for the analysis
 (closes: #980042).
   * Add patch to fix PostgreSQL include dir.
Checksums-Sha1:
 9731890dedbc03cbd4b8e553a162ffce2b9e4afe 3228 mailutils_3.11.1-5.dsc
 2c9762927deeec4c254fb45c1d513e5a64e75b16 37904 mailutils_3.11.1-5.debian.tar.xz
 144301362cb4ebd6ac42b6

Bug#980144: marked as done (mailutils: movemail does not remove start mailbox when moving)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 14:53:43 +
with message-id 
and subject line Bug#980042: fixed in mailutils 1:3.11.1-5
has caused the Debian Bug report #980042,
regarding mailutils: movemail does not remove start mailbox when moving
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.)


-- 
980042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mailutils
Version: 1:3.11.1-4
Severity: grave
X-Debbugs-Cc: none, Francesco Potortì 
File: /usr/bin/movemail.mailutils

By chance, I installed mailutis from the unstable branch and I
discovered that movemail does not work (while 1:3.10-3 works).

This is 
mailutils (1:3.11.1-4) unstable; urgency=medium

When called like

movemail --emacs inbox outbox

it copies inbox to outbox rather than moving it, i.e. it does not delete
outbox even after successful operation

-- 
Francesco Potortì (ricercatore)Voice:  +39.050.621.3058
ISTI - Area della ricerca CNR  Mobile: +39.348.8283.107
via G. Moruzzi 1, I-56124 Pisa Skype:  wnlabisti
(gate 20, 1st floor, room C71) Web:http://fly.isti.cnr.it
--- End Message ---
--- Begin Message ---
Source: mailutils
Source-Version: 1:3.11.1-5
Done: Jordi Mallach 

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated mailutils 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, 09 Feb 2021 16:17:12 +0100
Source: mailutils
Architecture: source
Version: 1:3.11.1-5
Distribution: unstable
Urgency: medium
Maintainer: Jordi Mallach 
Changed-By: Jordi Mallach 
Closes: 980042
Changes:
 mailutils (1:3.11.1-5) unstable; urgency=medium
 .
   * Enable PostgreSQL support now that OpenSSL is considered a system
 library by Debian ftpmaster.
   * Add upstream patch to fix expunging of mboxes on read-only directories
 (like Debian's /var/mail). Thanks to Pierrick Chanteux for the analysis
 (closes: #980042).
   * Add patch to fix PostgreSQL include dir.
Checksums-Sha1:
 9731890dedbc03cbd4b8e553a162ffce2b9e4afe 3228 mailutils_3.11.1-5.dsc
 2c9762927deeec4c254fb45c1d513e5a64e75b16 37904 mailutils_3.11.1-5.debian.tar.xz
 144301362cb4ebd6ac42b672af91a878ccdc3f2f 15545 
mailutils_3.11.1-5_amd64.buildinfo
Checksums-Sha256:
 1bb8495f38d61e4965560d9eb5a9b86e992c113b8728f0e584e352329ecd4543 3228 
mailutils_3.11.1-5.dsc
 b15c61e5cb4740d3df396e595fb4de5ade2688c048c452fdcc837da8acc5e841 37904 
mailutils_3.11.1-5.debian.tar.xz
 cdf57c13d01da4c4782600ce8cd571183bbc9273896901708e371d404773c9d4 15545 
mailutils_3.11.1-5_amd64.buildinfo
Files:
 8156c83801597afc6663311ec784b1d6 3228 mail optional mailutils_3.11.1-5.dsc
 57726c215ee8eb051fa6b16d3dd52a06 37904 mail optional 
mailutils_3.11.1-5.debian.tar.xz
 91ead578054c863f7d6f94825bdbb97d 15545 mail optional 
mailutils_3.11.1-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAmAr2DkACgkQJVAvb8vj
ywSdlBAAvLgLObQVJoRGkSAqvVowavSg6BBHjHZ1aDPrLOOFE1WHp5P0TtZXidI6
WewHLtJ8juouR4nZghFegJEaWdYgUCTk9AlyNwg4aA7YzHx50FAyOrUL1TM83nY3
lYpLPxQFSHsnRdJ+5ZbE6FjO8qm+GmuTjjJRz2OqUdKcqezmf1YuJLMA77X2j1wd
Qk3AUQI19T0mslNh7qALCXjKtX/1quSpIF+u13WWUdFmOCT+WI0YGwH1E3QPPlBc
UMI7kxakq9jxFgMLriOWSa8nfHuy3CSrOOVhdqAvbep++UC/ZPezVGBakVVdhvfg
bvBk9+xMYB07GJIWROtJwwgLdMe7QLFOp1n/Ha6vAsb5YeAB1mKTjH5bzzFZaVUx
8jVxiVlycWvbrHx1PBuV48y3LZvJL65Fsudd8mFgi1QWxeI2Wo0uSBvlvgKMn/Qt
jWcnGZTbmQGiV/vvxP+Vp0w09wemANqFjy0hp/3RaY/V/jjugljooD/0JDAOsPyI
dOw9tRQxYXpeF41htGx/YA6754GKD1ZKd5YVdKABJotOwhkcpOQM/mlIur1lo6oc
RYAvEwIlTzg1QxWgUtOZj9NLf2rureJ/8sInP4JMQZAFc9/Q0dVBwNMrlzwfSCFJ
D3sk522z32jOB3bE0QG5pKqV8UJ35AWux6uw2doz1umaTs5EKr4=
=pbTf
-END PGP SIGNATURE End Message ---

Processed: severity of 982586 is grave

[Debian Bug Tracking System]

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

> severity 982586 grave
Bug #982586 [src:otrs2] otrs2: CVE-2021-21435
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#982914: chai: broken-symlink /usr/share/doc/chai -> libjs-chai, missing-copyright-file

[Thorsten Glaser]

Package: chai
Version: 4.2.0+ds+~4.2.14-2
Severity: serious
Justification: Policy 2.3
User: debian...@lists.debian.org
Usertags: adequate broken-symlink missing-copyright-file
X-Debbugs-Cc: t...@mirbsd.de

chai: broken-symlink /usr/share/doc/chai -> libjs-chai
chai: broken-symlink /usr/share/nodejs/chai/dist -> ../../javascript/chai
chai: missing-copyright-file /usr/share/doc/chai/copyright

And indeed:

$ ll -d /usr/share/doc/chai /usr/share/doc/libjs-chai
ls: cannot access '/usr/share/doc/libjs-chai': No such file or directory
lrwxrwxrwx 1 root root 10 Feb 16 07:05 /usr/share/doc/chai -> libjs-chai

/usr/share/doc/PKGNAME can only ever be a symlink to another
binary package’s if the other binary package is built from
the same source *and* version, AND if the link target’s package
is a Depends.


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

Kernel: Linux 5.9.0-4-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages chai depends on:
ii  node-assertion-error  1.1.0-1
ii  node-check-error  1.0.2-3
ii  node-deep-eql 4.0.0-4
ii  node-get-func-name2.0.0+dfsg-1.1
ii  node-pathval  1.1.1-1
ii  node-type-detect  4.0.8-2
ii  nodejs12.20.2~dfsg-2

chai recommends no packages.

chai suggests no packages.

-- no debconf information

Processed: fixed 976216 in 2:1.20.4-1+deb10u2

[Debian Bug Tracking System]

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

> fixed 976216 2:1.20.4-1+deb10u2
Bug #976216 {Done: Timo Aaltonen } [src:xorg-server] 
xorg-server: CVE-2020-25712 CVE-2020-14360
Marked as fixed in versions xorg-server/2:1.20.4-1+deb10u2.
> thanks
Stopping processing here.

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

Bug#982172: marked as done (libint2 breaks cp2k autopkgtest)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 12:48:39 +
with message-id 
and subject line Bug#982172: fixed in cp2k 8.1-7
has caused the Debian Bug report #982172,
regarding libint2 breaks cp2k autopkgtest
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.)


-- 
982172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libint2, cp2k
Control: found -1 libint2/2.6.0-11
Control: found -1 cp2k/8.1-5
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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

   passfail
libint2from testing2.6.0-11
cp2k   from testing8.1-5
all others from testingfrom testing

Normally I copy some of the output at the bottom of this report,
however, the report is unconventional and I didn't spot the actual
failure. Please follow the link for the full report.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cp2k/10281856/log.gz




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: cp2k
Source-Version: 8.1-7
Done: Michael Banck 

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

Debian distribution maintenance software
pp.
Michael Banck  (supplier of updated cp2k 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, 16 Feb 2021 13:30:35 +0100
Source: cp2k
Architecture: source
Version: 8.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Michael Banck 
Closes: 982172
Changes:
 cp2k (8.1-7) unstable; urgency=medium
 .
   * debian/control (Build-Depends): Bump libint2-dev version to 2.6.0-11
 (Closes: #982172).
Checksums-Sha1:
 70954f122cbe5c78421bda618eabd892439d3e75 2188 cp2k_8.1-7.dsc
 cc1db0e6d0806317723ceb1a76bca72f14c60c99 15136 cp2k_8.1-7.debian.tar.xz
 f37f10a1ad7c9c52677058eb1df46f3dcd79e6fd 8133 cp2k_8.1-7_source.buildinfo
Checksums-Sha256:
 c3f62ab5a4af69e9564d8411d8c908167152197c7d9e15414678295b9b964bca 2188 
cp2k_8.1-7.dsc
 7c4844d1f2ab65f728cd7c147f3556a7c479dc9d5c65f6c13886393e42f5712f 15136 
cp2k_8.1-7.debian.tar.xz
 e7152389a416ef190537d7bbd69b67f700a62c81a530e6a3034fab163e4ef249 8133 
cp2k_8.1-7_source.buildinfo
Files:
 7f579f8e57d870bcc3c2ebdb393f54f1 2188 science optional cp2k_8.1-7.dsc
 9e84a80b330232662c0fb611a6ca1f48 15136 science optional 
cp2k_8.1-7.debian.tar.xz
 c25ccc1b4d4dc5ca9efbef5b5164cdd7 8133 science optional 
cp2k_8.1-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEnKh3dJ+rLk+paGLs3GhqJ7Q0gbAFAmAruwMACgkQ3GhqJ7Q0
gbB85g//coxzJzTfmjXz4K78ktNIT9z90fQ1A81M5CpMWpu/nrYKuPnALGXt5ZqP
8lX2ZkjsdNt3Z5UhJU5LCbgVg1cpQCZi4LAZpQRqYAtOfY7J0tOUJAVCklvTs65T
FDRKIBZ97pvfMxeVAat9qdnSKlGSysB7RhBhduol+ZIGIMzssjzj8w41p9ziShZx
bimGN9YLEIiUCMGOJjBmlMbUu2pID6odSLJrq9ONxUc3dxFVI0rGKNuBf8HcUmJ4
J9cZ7ehOU8JqiJW22IeMfuXASxcGrzRcNnGDipxRBxdKR1ACiR6BI7qMt8OLCM6a
q4Vumgu04bqwvgnhiuRyDiqTNOwGhcZwsGbbEOY5Cso1aQEdwVms+e25Pt02C9xX
495QfyDPpSin/E6jEcLemfclcVyYMD/rNdIvx07sRKs9YMMY4E7WFyLSUpKxEiqc
NuAVmbHaFBmWBBWl+urBKNoX+KPAR7YptgalQUuD8kYR74RUczGaX1X91226nYpn
tdrTxgMrMBT20BqLzU/lCDstu+4iAyj3pZemEl8xzF/QPU6PN1f4R4sV1VpRBxPa
+2hV7E7nKxHMHkIk8/yCNdIHojjvCT7Y+arDe1jQcvVZNsPZLYCDWAiu67KkTnkD
ANUXNOVXx4aToomcbHFAurgHw7OdWnwRvx3A

Bug#981662: marked as done (xfsprogs-udeb depends on libinih1, not libinih1-udeb)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 12:48:50 +
with message-id 
and subject line Bug#981662: fixed in xfsprogs 5.10.0-4
has caused the Debian Bug report #981662,
regarding xfsprogs-udeb depends on libinih1, not libinih1-udeb
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.)


-- 
981662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfsprogs
Version: 5.10.0-2
Severity: serious
Tags: d-i

Hi folks,

It appears that the latest version of xfsprogs (5.10.0) has just grown
a dependency on libinih1, and there isn't a udeb version of libinih to
meet that dependency. This means that xfs support in d-i just
broke. When trying to create an XFS filesystem we now get:

Error msg: "The xfs file system creation in partition #4 of /dev/nvme0n1
failed".
When trying from 2nd console, there seems to be a lib missing:
mkfs.xfs /dev/nvme0n1p4
mkfs.xfs: error while loading shared libraries: libinih.so.1: cannot open
shared object file: No such file or directory

There currently is not a libinih1-udeb package; maybe that's the right
fix. I don't know xfsprogs well enough to know if there are other
options (e.g. maybe disabling the libinih1 dependency from the udeb
build).


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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: xfsprogs
Source-Version: 5.10.0-4
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated xfsprogs 
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, 16 Feb 2021 13:31:30 +0100
Source: xfsprogs
Architecture: source
Version: 5.10.0-4
Distribution: unstable
Urgency: high
Maintainer: XFS Development Team 
Changed-By: Bastian Germann 
Closes: 981662
Changes:
 xfsprogs (5.10.0-4) unstable; urgency=high
 .
   * Source-only reupload (Closes: #981662)
Checksums-Sha1:
 bdad02aac22258f7d03aaafc7de910309e861d62 2047 xfsprogs_5.10.0-4.dsc
 37b74a2bceb4d6eba1b2c7f3cfcb33a62bd31f41 13924 xfsprogs_5.10.0-4.debian.tar.xz
 32d0b8d03beaf56a1e74fca13f31466cf3fc6ec9 6545 
xfsprogs_5.10.0-4_source.buildinfo
Checksums-Sha256:
 839e28e8d8fcb932013f50a371cf8a4ba29016a36238e4880c2a593b81ce9211 2047 
xfsprogs_5.10.0-4.dsc
 616a7730b773c60e0877694e419374174027a8cb540029509093a40da178bdbc 13924 
xfsprogs_5.10.0-4.debian.tar.xz
 c3a87d3e6d1b60eff9bb9989c471239fc7bbc373f02b525bf553cac8ad52dd09 6545 
xfsprogs_5.10.0-4_source.buildinfo
Files:
 62e8be79f08484553689fcbd3153e015 2047 admin optional xfsprogs_5.10.0-4.dsc
 7fd577f89a73a18a91630b02cb42bc25 13924 admin optional 
xfsprogs_5.10.0-4.debian.tar.xz
 1d0b1ab28fa60d8ca7c44d68462a60f9 6545 admin optional 
xfsprogs_5.10.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHPBAEBCgA5FiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmAru/AbHGJhc3RpYW5n
ZXJtYW5uQGZpc2hwb3N0LmRlAAoJEB9ceotFVkMU2DMMAK4reAI4MtsyfII66TMQ
M5f91mFFkbWLB5AMLuYlf+gP58x7WHcxCRzby6IagBTSRxPHx5s8mNNiy4P1NSfE
QXufjFQ50/iJEafVm+wBJBoqvVZkupoNuqEo1LgYciI/s0YqWDQ/s94ybdwnE6Fd
eabskKy+ag54KBXzBbZUY5u5OpZ4UMqPI1uniFnBQ/4rmlQetXn+RYalMoir5u+8
QEVbxheLUy7virdVgvM676sbdJxvoTR2DFF/VfrReG3kfAyz08KS7B9fzxgrn9lr
QBrLtsZU9Deo8ueXZr3pSqpUG+kDMGrJKAAog6Ptgue+2FxPttoxc0pA79DDwaxR
K4TsInZUNwIy2M4UOuN+/R7gmChjzUcW/ecn0IxSxzDQkWiL5DK7fgV8TUBoBjml
g4Em8kU1F2x3ZjCePp0hTS5PlQ2Ra9DcvNHZNifTV21L/ffFzKpHFkC/pa/E6P7v
n5oERP2pwkG2jiZOkJqVFKjfpY/+569SpYVuCXBjZRfEvg==
=j5hW
-END PGP SIGNATURE End Message ---

Bug#982172: marked as pending in cp2k

[Michael Banck]

Control: tag -1 pending

Hello,

Bug #982172 in cp2k 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/debichem-team/cp2k/-/commit/c4accae5950a6540f4ee4d3741e484572f369b4c


* debian/control (Build-Depends): Bump libint2-dev version to 2.6.0-11
(Closes: #982172).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/982172

Processed: Bug#982172 marked as pending in cp2k

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #982172 [src:libint2, src:cp2k] libint2 breaks cp2k autopkgtest
Added tag(s) pending.

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

Bug#982435: [screen-devel] [bug #60030] Screen segfaults by displaying some UTF-8 character combination

[Utkarsh Gupta]

Hi Axel,

On Mon, Feb 15, 2021 at 12:13 PM Axel Beckert  wrote:
> Please slow down!
>
> What so far was in git in the stretch and buster branches was
> incomplete and did FTBFS for multiple reasons. (Just pushed a bunch of
> fixes. It at least builds now on both releases.)
>
> And in Stretch the patch didn't even apply properly and needed manual
> massaging. So at least for Stretch (and Jessie) this needs additional
> testing.

Oh sure! I'll hold off any work until uploads in other releases have
been settled down.


- u

Bug#980642: marked as done (diagnostics: FTBFS: configure: error: invalid ltdl library directory: '/usr/lib/x86_64-linux-gnu')

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 11:03:49 +
with message-id 
and subject line Bug#980642: fixed in diagnostics 0.3.3-12.1
has caused the Debian Bug report #980642,
regarding diagnostics: FTBFS: configure: error: invalid ltdl library directory: 
'/usr/lib/x86_64-linux-gnu'
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.)


-- 
980642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: diagnostics
Version: 0.3.3-12
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20210120 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> checking for dlfcn.h... yes
> checking whether libtool supports -dlopen/-dlpreopen... yes
> checking for ltdl.h... yes
> checking whether lt_dlinterface_register is declared... yes
> checking for lt_dladvise_preload in -lltdl... yes
> configure: error: invalid ltdl library directory: '/usr/lib/x86_64-linux-gnu'
> make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'

The full build log is available from:
   http://qa-logs.debian.net/2021/01/20/diagnostics_0.3.3-12_unstable.log

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

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

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

About the archive rebuild: The rebuild was done on 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: diagnostics
Source-Version: 0.3.3-12.1
Done: Mattia Rizzolo 

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated diagnostics 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, 16 Feb 2021 11:43:01 +0100
Source: diagnostics
Architecture: source
Version: 0.3.3-12.1
Distribution: unstable
Urgency: medium
Maintainer: Michael Tautschnig 
Changed-By: Mattia Rizzolo 
Closes: 865142 980642
Changes:
 diagnostics (0.3.3-12.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS due to using a convenience copy of ltdl.  Closes: #980642
 Thanks to Dennis Filder  for the patch.
   * Drop explicit Build-Depends on automake1.11, the default automake version
 is good for this package.  Closes: #865142
Checksums-Sha1:
 1e9df863ce0435e251f91ab0382c8f74b36ef952 1960 diagnostics_0.3.3-12.1.dsc
 8d72ef3f8aa838d3f9cbf7a2298b71bfbd8a9518 13828 
diagnostics_0.3.3-12.1.debian.tar.xz
 f619836092ef8f44fa34c0b13007eb7fe7c7ff31 6499 
diagnostics_0.3.3-12.1_amd64.buildinfo
Checksums-Sha256:
 8162f4617400a742ae48680ddcdb25d75e786c6a0462e4e11881e02a16a8b9d6 1960 
diagnostics_0.3.3-12.1.dsc
 50f7bf804e9753317a669e80bc67a609dad3ddef07385342f98f720c1f046461 13828 
diagnostics_0.3.3-12.1.debian.tar.xz
 dba39c151e08140f32bf8556cf21938a9be570662f6ebb75db264f50c3a8d577 6499 
diagnostics_0.3.3-12.1_amd64.buildinfo
Files:
 a756cd7593d66363b07fed1a546da795 1960 libs extra diagnostics_0.3.3-12.1.dsc
 cebc70aa39a4bf7b82e495652f5316fe 13828 libs extra 
diagnostics_0.3.3-12.1.debian.tar.xz
 ebd09ca2ca615ced00c51d789fceb5f5 6499 libs extra 
diagnostics_0.3.3-12.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmArojQACgkQCBa54Yx2
K63l8BAAtrOvzAtnzneSh5GRsda1IzIQjwAN8ok7LKraS2nI8qPCFKqA20FBiUk4
Kw/qiC89SnhNjFGy5ZDDp6iaYEkOBRzXbA0cM3G9DHUKMuXO/CDZxPwi5Vg/R9yL
V+WsaRCr4uMqQVuGn3Uin0LM+2uwf2G9zsashZGctFiKUp1OUJ7cKDzTD8TPbQnP
6eoovxaRpIUeAZYfGFRjtjOMwjkZzVlrnjSBlAGHtfaHtMxR1YVqQy5CyJqjuDed
1oP0hP

Bug#980642: diagnostics: diff for NMU version 0.3.3-12.1

[Mattia Rizzolo]

Dear maintainer,

I've prepared an NMU for diagnostics (versioned as 0.3.3-12.1). The diff
is attached to this message.

Since this package is in the LowNMU list, it's already uploaded.

Regards.


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
More about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for diagnostics-0.3.3 diagnostics-0.3.3

 changelog |   10 ++
 control   |2 +-
 patches/no-ltdl-convenience.patch |   25 +
 patches/series|1 +
 rules |1 -
 5 files changed, 37 insertions(+), 2 deletions(-)

diff -Nru diagnostics-0.3.3/debian/changelog diagnostics-0.3.3/debian/changelog
--- diagnostics-0.3.3/debian/changelog	2016-12-04 09:54:25.0 +0100
+++ diagnostics-0.3.3/debian/changelog	2021-02-16 11:43:01.0 +0100
@@ -1,3 +1,13 @@
+diagnostics (0.3.3-12.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS due to using a convenience copy of ltdl.  Closes: #980642
+Thanks to Dennis Filder  for the patch.
+  * Drop explicit Build-Depends on automake1.11, the default automake version
+is good for this package.  Closes: #865142
+
+ -- Mattia Rizzolo   Tue, 16 Feb 2021 11:43:01 +0100
+
 diagnostics (0.3.3-12) unstable; urgency=low
 
   * Bump Standards Version to 3.9.8 (no changes)
diff -Nru diagnostics-0.3.3/debian/control diagnostics-0.3.3/debian/control
--- diagnostics-0.3.3/debian/control	2016-12-04 09:54:25.0 +0100
+++ diagnostics-0.3.3/debian/control	2021-02-16 11:40:47.0 +0100
@@ -1,7 +1,7 @@
 Source: diagnostics
 Priority: extra
 Maintainer: Michael Tautschnig 
-Build-Depends: dpkg-dev (>= 1.16.0~), debhelper (>= 9), automake1.11 | automake (>= 1:1.9), pkg-config, libtool, libltdl-dev (>= 2.4.2-1~), libace-dev (>= 5.7.7-3) [!hurd-i386], dh-autoreconf
+Build-Depends: dpkg-dev (>= 1.16.0~), debhelper (>= 9), automake, pkg-config, libtool, libltdl-dev (>= 2.4.2-1~), libace-dev (>= 5.7.7-3) [!hurd-i386], dh-autoreconf
 Standards-Version: 3.9.8
 Section: libs
 Homepage: http://forsyte.at/software/diagnostics
diff -Nru diagnostics-0.3.3/debian/patches/no-ltdl-convenience.patch diagnostics-0.3.3/debian/patches/no-ltdl-convenience.patch
--- diagnostics-0.3.3/debian/patches/no-ltdl-convenience.patch	1970-01-01 01:00:00.0 +0100
+++ diagnostics-0.3.3/debian/patches/no-ltdl-convenience.patch	2021-02-16 11:32:47.0 +0100
@@ -0,0 +1,25 @@
+Description: Disable AC_LIBLTDL_CONVENIENCE and use the distro's ltdl
+ For some reason configure.ac enables AC_LIBLTDL_CONVENIENCE which is
+ rather pointless in a distro that comes with its own ltdl and also
+ interferes with the build (#980642).  This patch disables that.
+Author: Dennis Filder 
+Bug-Debian: https://bugs.debian.org/980642
+Last-Update: 2021-02-10
+
+--- diagnostics-0.3.3/configure.ac
 diagnostics-0.3.3/configure.ac
+@@ -29,9 +29,11 @@ AC_PROG_LN_S
+ AC_PROG_MAKE_SET
+ AC_PROG_AWK
+ # new libtool versions:
+-# LT_INIT
+-# LTDL_INIT
+-AC_LIBLTDL_CONVENIENCE
++LT_INIT
++LTDL_INIT
++
++#AC_LIBLTDL_CONVENIENCE # disabled as this is pointless/redundant in
++#   # a distro shipping its own ltdl (see also: #652201)
+ AC_WITH_LTDL
+ AC_PROG_LIBTOOL
+ 
diff -Nru diagnostics-0.3.3/debian/patches/series diagnostics-0.3.3/debian/patches/series
--- diagnostics-0.3.3/debian/patches/series	2016-12-04 09:54:25.0 +0100
+++ diagnostics-0.3.3/debian/patches/series	2021-02-16 11:32:11.0 +0100
@@ -4,3 +4,4 @@
 gcc-warns-successfully
 gcc-6-destructor-is-noexcept
 test-run-cleanup
+no-ltdl-convenience.patch
diff -Nru diagnostics-0.3.3/debian/rules diagnostics-0.3.3/debian/rules
--- diagnostics-0.3.3/debian/rules	2014-07-07 13:42:50.0 +0200
+++ diagnostics-0.3.3/debian/rules	2021-02-16 11:33:00.0 +0100
@@ -27,7 +27,6 @@
 		--prefix=/usr --mandir=\$${prefix}/share/man \
 		--infodir=\$${prefix}/share/info \
 		--disable-update-makefiles \
-		--with-ltdl-include=/usr/include --with-ltdl-lib=/usr/lib/$(DEB_HOST_MULTIARCH) \
 		CXXFLAGS="$(CXXFLAGS)" # LDFLAGS="-Wl,-z,defs"
 
 override_dh_auto_test:


signature.asc
Description: PGP signature

Bug#982702: marked as done (qrouter: FTBFS: graphics.c:9:10: fatal error: X11/Intrinsic.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 10:18:45 +
with message-id 
and subject line Bug#982702: fixed in qrouter 1.4.71-2
has caused the Debian Bug report #982702,
regarding qrouter: FTBFS: graphics.c:9:10: fatal error: X11/Intrinsic.h: No 
such file or directory
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.)


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

Hi,

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

Relevant part (hopefully):
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -m64 -fPIC -fPIC -DPACKAGE_NAME=\"\" 
> -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SETENV=1 
> -DHAVE_PUTENV=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_SYS_MMAN_H=1 -DTCL_QROUTER=1 -DLINUX=1 -DSYSV=1 -DVERSION=\"1.4\" 
> -DREVISION=\"71\" -DUSE_TCL_STUBS -DUSE_TK_STUBS \
>   -DQROUTER_PATH=\"/usr/lib/qrouter\" 
> -I/usr/include/tcl8.6/tk-private/generic -I/usr/include/tcl8.6 -c graphics.c 
> -o graphics.o
> graphics.c:9:10: fatal error: X11/Intrinsic.h: No such file or directory
> 9 | #include 
>   |  ^
> compilation terminated.
> make[1]: *** [Makefile:160: graphics.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/02/13/qrouter_1.4.71-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!

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

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

About the archive rebuild: The rebuild was done on 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: qrouter
Source-Version: 1.4.71-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated qrouter 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, 16 Feb 2021 15:24:45 +0530
Source: qrouter
Architecture: source
Version: 1.4.71-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Nilesh Patra 
Closes: 971500 982702
Changes:
 qrouter (1.4.71-2) unstable; urgency=medium
 .
   * Team Upload.
   [ Juhani Numminen ]
   * Add Build-Depends: libxt-dev. qrouter needs it for compilation and
 it used to be pulled in by tk8.6-dev. Closes: #982702
 .
   [ Nilesh Patra ]
   * Mark autopkgtest as superficial (Closes: #971500)
Checksums-Sha1:
 b3513c39dfd1e23f99797de4f02ddf9e9c073364 2025 qrouter_1.4.71-2.dsc
 25bde675f72a2ed3a3b3a8707ac3f03ea8288207 7288 qrouter_1.4.71-2.debian.tar.xz
 a597c8cae2c038f273a83598df51d23b41bb5db9 7492 qrouter_1.4.71-2_amd64.buildinfo
Checksums-Sha256:
 8f8af891cba2bcb715962c706acbf8bd67d909655be874b2eeff1f16d17ea28b 2025 
qrouter_1.4.71-2.dsc
 0fad16e1692ba4b4805896aa3aad2e1f183ce2311ea4add0de1175d6eddbf8d8 7288 
qrouter_1.4.71-2.debian.tar.xz
 87d8a8e68fd31bb434f49e23687661da05c8c0cec157f09b100e7da7a6b151d8 7492 
qrouter_1.4.71-2_amd64.buildinfo
Files:
 c60e40de2b41c2865744eee

Bug#982702: marked as done (qrouter: FTBFS: graphics.c:9:10: fatal error: X11/Intrinsic.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 16 Feb 2021 10:04:04 +
with message-id 
and subject line Bug#982702: fixed in qrouter 1.4.71-1.1
has caused the Debian Bug report #982702,
regarding qrouter: FTBFS: graphics.c:9:10: fatal error: X11/Intrinsic.h: No 
such file or directory
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.)


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

Hi,

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

Relevant part (hopefully):
> gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -m64 -fPIC -fPIC -DPACKAGE_NAME=\"\" 
> -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" 
> -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SETENV=1 
> -DHAVE_PUTENV=1 -DHAVE_VA_COPY=1 -DHAVE___VA_COPY=1 -DHAVE_SYS_TYPES_H=1 
> -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 
> -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 
> -DHAVE_SYS_MMAN_H=1 -DTCL_QROUTER=1 -DLINUX=1 -DSYSV=1 -DVERSION=\"1.4\" 
> -DREVISION=\"71\" -DUSE_TCL_STUBS -DUSE_TK_STUBS \
>   -DQROUTER_PATH=\"/usr/lib/qrouter\" 
> -I/usr/include/tcl8.6/tk-private/generic -I/usr/include/tcl8.6 -c graphics.c 
> -o graphics.o
> graphics.c:9:10: fatal error: X11/Intrinsic.h: No such file or directory
> 9 | #include 
>   |  ^
> compilation terminated.
> make[1]: *** [Makefile:160: graphics.o] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2021/02/13/qrouter_1.4.71-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!

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

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

About the archive rebuild: The rebuild was done on 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: qrouter
Source-Version: 1.4.71-1.1
Done: Juhani Numminen 

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

Debian distribution maintenance software
pp.
Juhani Numminen  (supplier of updated qrouter 
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, 16 Feb 2021 11:10:16 +0200
Source: qrouter
Architecture: source
Version: 1.4.71-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Juhani Numminen 
Closes: 982702
Changes:
 qrouter (1.4.71-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add Build-Depends: libxt-dev. qrouter needs it for compilation and
 it used to be pulled in by tk8.6-dev. Closes: #982702
Checksums-Sha1:
 931dc143af8973fcc3561074496bacc4fdc93b16 2004 qrouter_1.4.71-1.1.dsc
 2fd6942612a40d67cf176dda4e172d7abb1dc959 7260 qrouter_1.4.71-1.1.debian.tar.xz
 a9c736faf28025e58fa604b4be4e5a8bafa7af20 7220 
qrouter_1.4.71-1.1_source.buildinfo
Checksums-Sha256:
 343c489e2ffd26acd743b56472fe241bf4fef852f2ba1d3f25b251938064054a 2004 
qrouter_1.4.71-1.1.dsc
 86179537001074ad9757a49f75130e32681ffa1890daa2424237943a3081f0f0 7260 
qrouter_1.4.71-1.1.debian.tar.xz
 a84125fc3a402bb230116da4bcc817c7e32c3c86085564b5202b5d70941421f0 7220 
qrouter_1.4.71-1.1_source.buildinfo
Files:
 cb6050bcdd22cfce06d835b38bbfd348 2004 electronics optional 
qrouter_1.4.71-1.1.dsc
 a7ce

Bug#982904: mumble: CVE-2021-27229

[Salvatore Bonaccorso]

Source: mumble
Version: 1.3.3-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/mumble-voip/mumble/pull/4733
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for mumble.

CVE-2021-27229[0]:
| Mumble before 1.3.4 allows remote code execution if a victim navigates
| to a crafted URL on a server list and clicks on the Open Webpage text.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-27229
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-27229
[1] https://github.com/mumble-voip/mumble/pull/4733
[2] 
https://github.com/mumble-voip/mumble/commit/e59ee87abe249f345908c7d568f6879d16bfd648

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#982865: meson: diff for NMU version 0.57.0+really0.56.2-0.1

[Sebastian Ramacher]

Hi

On 2021-02-15 23:51:12, Jussi Pakkanen wrote:
> On Mon, 15 Feb 2021 at 23:21, Sebastian Ramacher  wrote:
> 
> > Silently breaking hardening build flags of roughly 430 packages is
> > definitely a large and disruptive change.
> 
> The rc was uploaded to experimental a week ago so that people could
> use it to flush out problems like these. Apparently no-one did. Would
> it be possible to set up an automatic gating system of some kind for
> build-essential packages so these sort of things will never happen
> again in the future?

I guess you could do some or all of the following:
* Add a autopkgtest to meson that builds a package. This test could also
  check whether all flags from dpkg-buildflags are preserved during the
  build with blhc. After some time the autopkgtest results for the
  package in experimental would appear at
  https://release.debian.org/britney/pseudo-excuses-experimental.html.
* Not automatic, but you could talk to lucas to run a test build of all
  reverse dependencies on AWS. Again check with blhc if all flags are
  preserved.

But even if all of the above would have been done, uploading a new
upstream version of a build system to unstable would have been
inappropriate at this stage.

Cheers
-- 
Sebastian Ramacher

Bug#942988: displaycal: Python2 removal in sid/bullseye

[Christian Marillat]

On 05 mai 2020 20:50, Florian Höch  wrote:

> Hey, just letting you know upstream is indeed still alive.
>
> As you have noticed, things take longer than expected, and not all is
> due to the move to Python3. While I appreciate the offer to help, at
> the moment it would make things harder to juggle for me.

Argyll is scheduled to be removed from Debian https://bugs.debian.org/966416
and displaycal will also removed.

Could you tell us if displaycal will be ready for python 3 one day ?

Christian