Processed: Re: dh-virtualenv: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
Processing commands for cont...@bugs.debian.org: > severity 997383 minor Bug #997383 [src:dh-virtualenv] dh-virtualenv: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Severity set to 'minor' from 'serious' > tags 997383 fixed-upstream Bug #997383 [src:dh-virtualenv] dh-virtualenv: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 997383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997383 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997383: dh-virtualenv: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
severity 997383 minor
tags 997383 fixed-upstream
thanks
Hi,
On Sat, 23 Oct 2021 21:49:56 +0200 Lucas Nussbaum wrote:
> Exception occurred:
> File "/<>/doc/conf.py", line 30, in setup
> app.add_stylesheet('css/custom.css')
> AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
> The full traceback has been saved in /tmp/sphinx-err-qj3dzcul.log, if you
want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
message can be provided next time.
> A bug report can be filed in the tracker at
. Thanks!
> make[1]: *** [debian/rules:28: override_dh_installdocs] Error 1
From what I can tell, the add_stylesheet removal was delayed upstream
and as a result dh-virtualenv no longer FTBFS in sid, so I'm downgrading
the severity to minor.
Fixing the deprecation warning should be as simple as cherry-picking
,
which I can do as a NMU if that's wanted.
-- Kunal
Processed (with 1 error): your mail
Processing commands for cont...@bugs.debian.org: > notfound swi-prolog 8.4.2+dfsg-2 Unknown command or malformed arguments to command. > reassign 1006384 logol 1.7.9+dfsg-1 Bug #1006384 [src:swi-prolog, src:logol] swi-prolog breaks logol autopkgtest: Program exited with wrong status code Bug reassigned from package 'src:swi-prolog, src:logol' to 'logol'. No longer marked as found in versions swi-prolog/8.4.2+dfsg-2 and logol/1.7.9+dfsg-1. Ignoring request to alter fixed versions of bug #1006384 to the same values previously set Bug #1006384 [logol] swi-prolog breaks logol autopkgtest: Program exited with wrong status code Marked as found in versions logol/1.7.9+dfsg-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984053: fix for etl: ftbfs with GCC-11
I fixed this issue upstream and attached the patch here.
Upstream commit:
https://github.com/synfig/synfig/commit/e2f89aac473ba9016582d35f9fac74e61e99ec8c
From e2f89aac473ba9016582d35f9fac74e61e99ec8c Mon Sep 17 00:00:00 2001
From: rodolforg
Date: Mon, 28 Feb 2022 22:46:15 -0300
Subject: [PATCH] ETL test: avoid clash between ETL::hermite and std::hermite (#2547)
---
ETL/test/angle.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ETL/test/angle.cpp b/ETL/test/angle.cpp
index 60042ef..3cc52b1 100644
--- a/ETL/test/angle.cpp
+++ b/ETL/test/angle.cpp
@@ -201,7 +201,7 @@ int angle_test()
affine_combo combo;
- hermite hermie(a,b,b.dist(a),b.dist(a));
+ etl::hermite hermie(a,b,b.dist(a),b.dist(a));
for(f=0;f<1.001;f+=0.1)
{
--
libgit2 1.1.0
Bug#1006633: procmail is unmaintained and a security liability
Package: procmail Version: 3.22-26 Severity: critical Tags: security X-Debbugs-Cc: Debian Security Team procmail is a security liability and completely unmaintained upstream. there are viable alternatives, and it should be removed from debian. details below. # unmaintained procmail is unmaintained. the "Final release", according to Wikipedia[1], dates back to September 10, 2001 (3.22). this is the release that is shipped with Debian, although we do have *26* debian-specific uploads on top of that (3.22-26, in all suites since buster). [1]: https://en.wikipedia.org/wiki/Procmail that release entered Debian on 2001-11-21, now twenty (!) years ago, and presumably shipped with Debian 3.0 "woody": https://tracker.debian.org/news/269157/installed-procmail-322-1-i386-source/ the upstream website has been down since about 2016, according to a quick tour around archive.org. it currently returns an empty JSON document, mysteriously. (reported as #805864 in 2015, no change since.) in effect, we are maintaining a fork of this dead software. # security liability by default, procmail is installed suid root:mail. there's no debconf or preseed that can change that, although you could, in theory, do a dpkg-divert to workaround that, but I doubt anyone deploying procmail these days does that. the last maintainer of procmail explicitly advised us (in #769938) and other projects (e.g. OpenBSD, in [2]) to stop shipping it. [2]: https://marc.info/?l=openbsd-ports=141634350915839=2 Quote: > Executive summary: delete the procmail port; the code is not safe > and should not be used as a basis for any further work. That Debian bug report is still open, and concerns a NULL pointer dereference. I do not know if it is exploitable. Strangely, the original procmail author (Stephen R. van den Berg, presumably) wrote in that bug report *last year* saying that was "Fixed in upcoming 3.23 release", which has been targeted for release for all of those last 20 years. # alternatives there are plenty of modern alternatives to procmail, typically part of the mail server. Dovecot has its own LDA which implements the standard Sieve language (RFC 5228, published in 2008, 7 years after procmail's death). Courier has "maildrop" which has its own filtering mechanism. then the tmux author, in 2007, wrote fdm as a fetchmail and procmail replacement. but procmail, of course, doesn't just ship procmail (that would be too easy). it ships `mailstat(1)` which we could probably ignore because it only parses procmail log files. but more importantly, it also ships: lockfile - conditional semaphore-file creator formail - mail (re)formatter lockfile already has somewhat acceptable (if TOCTOU is something you like) in the form of `flock(1)`, part of util-linux (which is Essential). it might not be a direct drop-in replacement, but it should be close enough. formail is similar: the courier `maildrop` package ships `reformail(1)` which is, presumably, a rewrite of formail. it's unclear if it's a drop-in replacement, but it should probably possible to port uses of formail to it easily. # conclusion there is really, absolutely, no reason to keep procmail in Debian at this point. it's a great part of our computing history, and it should be kept forever in our museums and historical archive, but not in main, and certainly not in bookworm or even sid. it's just a bomb waiting to go off. -- System Information: Debian Release: 11.2 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), (1, 'unstable'), (1, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads) Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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 procmail depends on: ii libc6 2.31-13+deb11u2 Versions of packages procmail recommends: ii postfix [mail-transport-agent] 3.5.6-1+b1 procmail suggests no packages.
Bug#983972: marked as done (aqsis: ftbfs with GCC-11)
Your message dated Mon, 28 Feb 2022 23:33:33 +
with message-id
and subject line Bug#983972: fixed in aqsis 1.8.2-13
has caused the Debian Bug report #983972,
regarding aqsis: ftbfs with GCC-11
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.)
--
983972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aqsis
Version: 1.8.2-12
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/aqsis_1.8.2-12_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 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-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
57 | template class auto_ptr;
|^~~~
/<>/thirdparty/partio/src/src/lib/io/PTC.cpp: In function ‘bool
Partio::writePTC(const char*, const Partio::ParticlesData&, bool)’:
/<>/thirdparty/partio/src/src/lib/io/PTC.cpp:237:10: warning:
‘template class std::auto_ptr’ is deprecated: use 'std::unique_ptr'
instead [-Wdeprecated-declarations]
237 | std::auto_ptr output(
| ^~~~
In file included from /usr/include/c++/11/memory:76,
from
/<>/thirdparty/partio/src/src/lib/io/PTC.cpp:47:
/usr/include/c++/11/bits/unique_ptr.h:57:28: note: declared here
57 | template class auto_ptr;
|^~~~
[ 75%] Building CXX object
libs/shadervm/CMakeFiles/aqsis_shadervm.dir/__/__/thirdparty/partio/src/src/lib/io/ZIP.cpp.o
cd /<>/obj-x86_64-linux-gnu/libs/shadervm && /usr/bin/c++
-DAQSIS_SHADERVM_EXPORTS -DBOOST_ALL_NO_LIB -DBOOST_FILESYSTEM_DYN_LINK
-DBOOST_REGEX_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DPARTIO_USE_ZLIB
-Daqsis_shadervm_EXPORTS -I/<>/include
-I/<>/obj-x86_64-linux-gnu/include -I/usr/include/OpenEXR
-I/<>/libs/shadervm/shaderexecenv
-I/<>/thirdparty/partio/src/src/lib
-I/<>/libs/pointrender -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -pipe -Wall
-Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -o
CMakeFiles/aqsis_shadervm.dir/__/__/thirdparty/partio/src/src/lib/io/ZIP.cpp.o
-c /<>/thirdparty/partio/src/src/lib/io/ZIP.cpp
/<>/thirdparty/partio/src/src/lib/io/ZIP.cpp: In destructor
‘virtual Partio::ZipStreambufCompress::~ZipStreambufCompress()’:
/<>/thirdparty/partio/src/src/lib/io/ZIP.cpp:358:23: error:
‘streampos’ is not a member of ‘std::ios’ {aka ‘std::basic_ios’}
358 | std::ios::streampos final_position=ostream.tellp();
| ^
/<>/thirdparty/partio/src/src/lib/io/ZIP.cpp:363:27: error:
‘final_position’ was not declared in this scope
363 | ostream.seekp(final_position);}
| ^~
/<>/thirdparty/partio/src/src/lib/io/ZIP.cpp: In destructor
‘virtual Partio::ZipFileWriter::~ZipFileWriter()’:
/<>/thirdparty/partio/src/src/lib/io/ZIP.cpp:453:15: error:
‘streampos’ is not a member of ‘std::ios’ {aka ‘std::basic_ios’}
453 | std::ios::streampos final_position=ostream.tellp();
| ^
/<>/thirdparty/partio/src/src/lib/io/ZIP.cpp:455:15: error:
‘streampos’ is not a member of ‘std::ios’ {aka ‘std::basic_ios’}
455 | std::ios::streampos
Bug#1005778: pypandoc: diff for NMU version 1.7.2+ds0-1.1
> However, I don't think that adding lmodern to the package Depends is the > right solution, as that would lead to parts of tex (admittely, a small > part, but still) having to be installed on the system, which is not > required by pandoc itself. > The right solution, I believe, is to add lmodern to the tests/control > Depends, and I've just realized that I prepared that in git, but I never > actually did the upload (ups), and was wondering why it wasn't > working. agreed, so long as it's not required by most outputs (i.e. you can run pypandoc without it and it works). > I will do the upload myself in the next few days, since I have an > up-to-date copy of the repo locally (and salsa is down). alrightie. this was my NM application bug; i guess i will find another one. have a good day! signature.asc Description: PGP signature
Bug#1005932: marked as done (nvidia-graphics-drivers-tesla-450: incompatible with xorg-server video ABI 25)
Your message dated Mon, 28 Feb 2022 20:33:55 + with message-id and subject line Bug#1005932: fixed in nvidia-graphics-drivers-tesla-450 450.172.01-2 has caused the Debian Bug report #1005932, regarding nvidia-graphics-drivers-tesla-450: incompatible with xorg-server video ABI 25 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.) -- 1005932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-graphics-drivers-tesla-418 Version: 418.226.00-1 Severity: serious xorg-server's video ABI was recently bumped, and nvidia-graphics-drivers-tesla-418 only declares compatibility for up to v24. Cheers, Julien --- End Message --- --- Begin Message --- Source: nvidia-graphics-drivers-tesla-450 Source-Version: 450.172.01-2 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-graphics-drivers-tesla-450, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-graphics-drivers-tesla-450 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: Mon, 28 Feb 2022 21:03:12 +0100 Source: nvidia-graphics-drivers-tesla-450 Architecture: source Version: 450.172.01-2 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 1005932 Changes: nvidia-graphics-drivers-tesla-450 (450.172.01-2) unstable; urgency=medium . * Backport pde_data changes from 510.39.01 to fix kernel module build for Linux 5.17. * Add xorg-video-abi-25 (Xorg Xserver 21) as alternative dependency. (Closes: #1005932) * dkms.conf: Use a BUILD_EXCLUSIVE equivalent hack to skip build for -rt kernels, not supported upstream. * Declare Testsuite: autopkgtest-pkg-dkms. Checksums-Sha1: 983813f458610c534ff1b7403e9ccb20435f604f 7439 nvidia-graphics-drivers-tesla-450_450.172.01-2.dsc f6c53c3d83e02191c59043bd37b9de002a1d10bb 200232 nvidia-graphics-drivers-tesla-450_450.172.01-2.debian.tar.xz 1ec0db0b92b9a066ad8e2ee6c7fa5113329d6e35 7939 nvidia-graphics-drivers-tesla-450_450.172.01-2_source.buildinfo Checksums-Sha256: bdbb1234a1ba364c0e88146b4036aebccfc5af3a2f7f629689e59dd69b5403a8 7439 nvidia-graphics-drivers-tesla-450_450.172.01-2.dsc 0eb7ead6f724e9784d9de06a45b84fc9b57b71d2dfef237ed4217d2732a9a3ef 200232 nvidia-graphics-drivers-tesla-450_450.172.01-2.debian.tar.xz 1a5f5ed371ff98567e56b987ccb3baf21d89c757a211df87d309b609c9364ccb 7939 nvidia-graphics-drivers-tesla-450_450.172.01-2_source.buildinfo Files: 7469cf7bb163615428f7346e3a919e7a 7439 non-free/libs optional nvidia-graphics-drivers-tesla-450_450.172.01-2.dsc ad779205fe741c0956f6477a7e267f89 200232 non-free/libs optional nvidia-graphics-drivers-tesla-450_450.172.01-2.debian.tar.xz 24289090ce842b7a055bc7f626440090 7939 non-free/libs optional nvidia-graphics-drivers-tesla-450_450.172.01-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmIdK0wQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCCCGD/4nllLTnXFix9vEIu45fWf0evyshb/J3Vf0 +VUOrrLcD30K0rNH3FjT9fxoUT7aJasIdNuZ2i6OHrb1J1ZvDTTTcxkwy1oI2tdf 3Pn3UXSTdE2t3KoDd4aN3qwuv/D8nUz708uNRQZMHgCdyb5K6xnrfkVOa/JKgiWN dBZy+aLvh/NKXiR3yvVXsgshAbK9EV8H36IUHUJK6mbawg5fzGUXMKepTSzjj6pQ 2LdWScYbNBD1pFhSn4Li8wQfjil7Ov5lrBXaknhKowiaW6OMZOHd1F96Y3MttpI9 ABJjQshQgRdyf7pmAcXklmiVZ2UazryB38HrvyLT/U2Oq8AwF5hy8vQLkRdPZqQe P4FlLn6mWBczHCTqv1WSebSpMLywBJ3kzCXDIcpo4ok2nqdsV0Io2jwHB1M2meZs YlpXWBVALbnwAUk62TKM2bLlaQ4QdiCsXKef34QNGXcKrgjjoKennM+fKqH7GuG3 g1UIxLf9kGWjdngcdC0nsYBbBWs6PW+Dm9Rx5cBPYk4oE6b9EMZDm++sTt7dlf7h z1Sq8asiMBATNaMQ7xRHeGtz5K5AnfjdedAboOktqXiMuIJgTol5CoWyJwEqTuZ6 e9yB0a23AJvRtA0jotVbaySSO9/77QcJcO6dJ1Ew0zDL93S8mpphhntIdKBL5Tu3 AEiHwy0gQQ== =HEPl -END PGP SIGNATURE End Message ---
Processed: src:ats2-lang: fails to migrate to testing for too long: uploader built arch:all binaries
Processing control commands: > close -1 0.4.2-1 Bug #1006624 [src:ats2-lang] src:ats2-lang: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions ats2-lang/0.4.2-1. Bug #1006624 [src:ats2-lang] src:ats2-lang: fails to migrate to testing for too long: uploader built arch:all binaries Marked Bug as done -- 1006624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006624: src:ats2-lang: fails to migrate to testing for too long: uploader built arch:all binaries
Source: ats2-lang Version: 0.4.0-1 Severity: serious Control: close -1 0.4.2-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:ats2-lang has been trying to migrate for 63 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=ats2-lang OpenPGP_signature Description: OpenPGP digital signature
Bug#1006623: src:lsp-plugins: fails to migrate to testing for too long: FTBFS on armhf
Source: lsp-plugins Version: 1.1.30-1 Severity: serious Control: close -1 1.1.31-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1003904 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:lsp-plugins has been trying to migrate for 62 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=lsp-plugins OpenPGP_signature Description: OpenPGP digital signature
Processed: src:lsp-plugins: fails to migrate to testing for too long: FTBFS on armhf
Processing control commands:
> close -1 1.1.31-1
Bug #1006623 [src:lsp-plugins] src:lsp-plugins: fails to migrate to testing for
too long: FTBFS on armhf
Marked as fixed in versions lsp-plugins/1.1.31-1.
Bug #1006623 [src:lsp-plugins] src:lsp-plugins: fails to migrate to testing for
too long: FTBFS on armhf
Marked Bug as done
> block -1 by 1003904
Bug #1006623 {Done: Paul Gevers } [src:lsp-plugins]
src:lsp-plugins: fails to migrate to testing for too long: FTBFS on armhf
1006623 was not blocked by any bugs.
1006623 was not blocking any bugs.
Added blocking bug(s) of 1006623: 1003904
--
1006623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005778: pypandoc: diff for NMU version 1.7.2+ds0-1.1
On 2022-02-28 at 10:20:10 -0500, nick black wrote: > lmodern needed be listed as a regular Depends, not just a > Build-Depends, in order for the autopkgtests to successfully > run. I have added it, and verified that this fixes the > autopkgtests on the testing distribution. Thanks for working on it! However, I don't think that adding lmodern to the package Depends is the right solution, as that would lead to parts of tex (admittely, a small part, but still) having to be installed on the system, which is not required by pandoc itself. The right solution, I believe, is to add lmodern to the tests/control Depends, and I've just realized that I prepared that in git, but I never actually did the upload (ups), and was wondering why it wasn't working. I will do the upload myself in the next few days, since I have an up-to-date copy of the repo locally (and salsa is down). sorry. -- Elena ``of Valhalla'' signature.asc Description: PGP signature
Processed: src:httpie: fails to migrate to testing for too long: uploader built arch:all binary
Processing control commands: > close -1 2.6.0-1 Bug #1006620 [src:httpie] src:httpie: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions httpie/2.6.0-1. Bug #1006620 [src:httpie] src:httpie: fails to migrate to testing for too long: uploader built arch:all binary Marked Bug as done -- 1006620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005899: mplayer: should not release with bookworm
> On 28 Feb 2022, at 19:12, Ian Jackson wrote: > It seems to me that at #1004579 (ffmpeg 5.0) and #939032 (giflib) > would need to be addressed, These are definitely fixed in 1.5, and the fix for giflib should be not hard to cherry-pick for 1.4 if there is a need. > and #958865 (crash on theora) really ought > to be fixed too. I could never reproduce it, but it could be I never tested 1.4 Debian build. But chances are this is fixed by 1.5 at least. > If we had a maintainer who is able to deal with > those, and also deal with some of the outstanding bug gardening, then > we could conclude that mplayer ought to stay. I am completely unfamiliar with the Debian processes and doubt I have time to learn (and interacting with the bug tracker seems supremely painful and confusing to me). So I also don't know what exactly is needed. But if it's just about debugging/fixing bugs or finding patches to cherry-pick I am here, and as said the lists are also there, as is MPlayer's trac bug tracker (though not that actively monitored, so would need to ping me for a fast response). Best regards, Reimar
Bug#1006620: src:httpie: fails to migrate to testing for too long: uploader built arch:all binary
Source: httpie Version: 2.4.0-1 Severity: serious Control: close -1 2.6.0-1 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:httpie has been trying to migrate for 62 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=httpie OpenPGP_signature Description: OpenPGP digital signature
Bug#1006537: dask: autopkgtest failure on 32 bit, mismatch in size of data structure.
On Sun, 2022-02-27 at 08:34 +, Peter Michael Green wrote: > Package: dask > Version: 2022.01.0+dfsg-1 > Severity: serious > > The autopkgtest for dask is once-again failing on 32-bit > architectures, > this is blocking the fix for > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005962 > from migrating to testing. > Drat! I'd thought I'd found an upstream fix for that. And right now there's some problem where a dask dependency isn't installable in 32-bit as it depends on something still in NEW. The following packages have unmet dependencies: python3-fonttools : Depends: python3-unicodedata2 (>= 14.0.0) but it is not installable or python3-all (>= 3.11.0) but 3.9.8-1 is to be installed E: Unable to correct problems, you have held broken packages. So debugging it is a bit challenging at the moment. Diane
Bug#1005899: mplayer: should not release with bookworm
On 2022-02-28 18:12:27, Ian Jackson wrote: > This bug came to my attention as a user of mplayer, due to the testing > autoremoval which is the consequence of an RC bug. > > I tried Sebastian Ramacher's suggested alternative of `mpv` and, > speaking entirely personally, it would do OK for me as a replacement > for mplayer. It seems to have many of the same advantages over other > programs (eg vlc), for me. > > But: > > I have to say that I found the original report in this bug rather > unfriendly in tone. Removing things is usually regrettable - at the > very least, there will usually be people who are going to be upset. > And an RC bug like this has very high visibility and will draw the > attention of people without much of the context. As I am effectively its last maintainer, the original bug report describes mplayers state in Debian: it is not maintained. And it hasn't been since 2018 (or even 2016 which saw the last maintainer upload). > A message which was kinder about mplayer, and which more positively > spoke of the advantages of mpv, would have avoided darkening my day > today. > > > I had a look at the bug list in Debian and it doesn't seem to have > insuperable problems. I'm not able to commit substantial amounts of > time but I wouldn't want this package to fall out of Debian just > because no-one with the appropriate permissions is available to > support people who want to do the actual maintenance. So I hereby > volunteer to sponsor uploads. > > It seems to me that at #1004579 (ffmpeg 5.0) and #939032 (giflib) > would need to be addressed, and #958865 (crash on theora) really ought > to be fixed too. If we had a maintainer who is able to deal with > those, and also deal with some of the outstanding bug gardening, then > we could conclude that mplayer ought to stay. Please feel free to take over. Cheers -- Sebastian Ramacher
Bug#1000980: kubernetes: Please upgrade to golang-1.17
On Tue, 8 Feb 2022 18:02:54 + Janos LENART wrote: > I'll get on this. Thanks. Janos, Any updates on this? There is a patch as well in this email[1] Can you please apply and upload? [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000980#31 Regards, Nilesh signature.asc Description: PGP signature
Bug#1005899: mplayer: should not release with bookworm
This bug came to my attention as a user of mplayer, due to the testing autoremoval which is the consequence of an RC bug. I tried Sebastian Ramacher's suggested alternative of `mpv` and, speaking entirely personally, it would do OK for me as a replacement for mplayer. It seems to have many of the same advantages over other programs (eg vlc), for me. But: I have to say that I found the original report in this bug rather unfriendly in tone. Removing things is usually regrettable - at the very least, there will usually be people who are going to be upset. And an RC bug like this has very high visibility and will draw the attention of people without much of the context. A message which was kinder about mplayer, and which more positively spoke of the advantages of mpv, would have avoided darkening my day today. I had a look at the bug list in Debian and it doesn't seem to have insuperable problems. I'm not able to commit substantial amounts of time but I wouldn't want this package to fall out of Debian just because no-one with the appropriate permissions is available to support people who want to do the actual maintenance. So I hereby volunteer to sponsor uploads. It seems to me that at #1004579 (ffmpeg 5.0) and #939032 (giflib) would need to be addressed, and #958865 (crash on theora) really ought to be fixed too. If we had a maintainer who is able to deal with those, and also deal with some of the outstanding bug gardening, then we could conclude that mplayer ought to stay. Thanks, Ian. -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Processed: [bts-link] source package src:elpy
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:elpy > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #975535 (http://bugs.debian.org/975535) > # Bug title: elpy's autopkg tests fail with Python 3.9 > # * https://github.com/jorgenschaefer/elpy/issues/1856 > # * remote status changed: open -> closed > # * closed upstream > tags 975535 + fixed-upstream Bug #975535 [src:elpy] elpy's autopkg tests fail with Python 3.9 Added tag(s) fixed-upstream. > usertags 975535 - status-open Usertags were: status-open. There are now no usertags set. > usertags 975535 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 975535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package src:yasm
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:yasm > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #997338 (http://bugs.debian.org/997338) > # Bug title: yasm: FTBFS: configure: error: Standard (ANSI/ISO C89) header > files are required. > # * https://github.com/yasm/yasm/pull/178 > # * remote status changed: (?) -> closed > # * closed upstream > tags 997338 + fixed-upstream Bug #997338 [src:yasm] yasm: FTBFS: configure: error: Standard (ANSI/ISO C89) header files are required. Added tag(s) fixed-upstream. > usertags 997338 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 997338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002198: marked as done (python-mkdocs: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)
Your message dated Mon, 28 Feb 2022 17:03:36 +
with message-id
and subject line Bug#1002198: fixed in python-mkdocs 1.2.3-1
has caused the Debian Bug report #1002198,
regarding python-mkdocs: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p "3.10 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.)
--
1002198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mkdocs
Version: 1.1.2+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:237: /usr/bin/python3.10 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs
> copying mkdocs/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs
> copying mkdocs/plugins.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs
> copying mkdocs/__main__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs
> copying mkdocs/exceptions.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs
> copying mkdocs/theme.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/commands
> copying mkdocs/commands/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/commands
> copying mkdocs/commands/build.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/commands
> copying mkdocs/commands/new.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/commands
> copying mkdocs/commands/serve.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/commands
> copying mkdocs/commands/gh_deploy.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/commands
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/themes
> copying mkdocs/themes/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/themes
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/themes/mkdocs
> copying mkdocs/themes/mkdocs/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/themes/mkdocs
> creating
> /<>/.pybuild/cpython3_3.10/build/mkdocs/themes/readthedocs
> copying mkdocs/themes/readthedocs/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/themes/readthedocs
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/utils
> copying mkdocs/utils/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/utils
> copying mkdocs/utils/filters.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/utils
> copying mkdocs/utils/ghp_import.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/utils
> copying mkdocs/utils/meta.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/utils
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/config
> copying mkdocs/config/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/config
> copying mkdocs/config/config_options.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/config
> copying mkdocs/config/defaults.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/config
> copying mkdocs/config/base.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/config
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/structure
> copying mkdocs/structure/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/structure
> copying mkdocs/structure/pages.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/structure
> copying mkdocs/structure/nav.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/structure
> copying mkdocs/structure/toc.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/structure
> copying mkdocs/structure/files.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/structure
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/contrib
> copying mkdocs/contrib/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/contrib
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/contrib/search
> copying mkdocs/contrib/search/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/contrib/search
> copying mkdocs/contrib/search/search_index.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/contrib/search
> creating /<>/.pybuild/cpython3_3.10/build/mkdocs/tests
> copying mkdocs/tests/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/tests
> copying mkdocs/tests/cli_tests.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/tests
> copying mkdocs/tests/build_tests.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/tests
> copying mkdocs/tests/base.py ->
> /<>/.pybuild/cpython3_3.10/build/mkdocs/tests
> copying mkdocs/tests/integration.py ->
>
Processed: severity of 1006500 is important
Processing commands for cont...@bugs.debian.org: > severity 1006500 important Bug #1006500 [firmware-bnx2x] Missing bnx2x firmware 7.13.21.0 renders NIC unusable with Linux 5.16 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1006500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: BTS handling for buster-pu uploads
Processing commands for cont...@bugs.debian.org:
> unarchive 951289
Bug #951289 {Done: Emmanuel Bouthenot } [src:weechat]
weechat: CVE-2020-8955
Unarchived Bug 951289
> unarchive 966647
Bug #966647 {Done: Ricardo Mones } [src:libetpan] libetpan:
CVE-2020-15953
Unarchived Bug 966647
> found 966647 1.9.3-2
Bug #966647 {Done: Ricardo Mones } [src:libetpan] libetpan:
CVE-2020-15953
Marked as found in versions libetpan/1.9.3-2.
> unarchive 987853
Bug #987853 {Done: Balint Reczey } [src:wireshark]
wireshark: CVE-2021-22207
Unarchived Bug 987853
> found 987853 2.6.20-0+deb10u1
Bug #987853 {Done: Balint Reczey } [src:wireshark]
wireshark: CVE-2021-22207
Marked as found in versions wireshark/2.6.20-0+deb10u1.
> unarchive 973770
Bug #973770 {Done: Andreas Tille } [src:cimg] cimg:
CVE-2020-25693
Unarchived Bug 973770
> found 973770 2.4.5+dfsg-1
Bug #973770 {Done: Andreas Tille } [src:cimg] cimg:
CVE-2020-25693
Marked as found in versions cimg/2.4.5+dfsg-1.
> unarchive 977764
Bug #977764 {Done: Fabian Greffrath } [src:flac] flac:
CVE-2020-0499
Unarchived Bug 977764
> found 977764 1.3.2-3
Bug #977764 {Done: Fabian Greffrath } [src:flac] flac:
CVE-2020-0499
Marked as found in versions flac/1.3.2-3.
> unarchive 939668
Bug #939668 {Done: Eric Dorland } [src:opensc] opensc:
CVE-2019-15945
Unarchived Bug 939668
> unarchive 939669
Bug #939669 {Done: Eric Dorland } [src:opensc] opensc:
CVE-2019-15946
Unarchived Bug 939669
> unarchive 947383
Bug #947383 {Done: Eric Dorland } [src:opensc] opensc:
CVE-2019-19479
Unarchived Bug 947383
> unarchive 972037
Bug #972037 {Done: Eric Dorland } [opensc] CVE-2020-26570
Unarchived Bug 972037
> unarchive 972036
Bug #972036 {Done: Eric Dorland } [opensc] CVE-2020-26571
Unarchived Bug 972036
> unarchive 972035
Bug #972035 {Done: Eric Dorland } [opensc] CVE-2020-26572
Unarchived Bug 972035
> found 972037 0.19.0-1
Bug #972037 {Done: Eric Dorland } [opensc] CVE-2020-26570
Marked as found in versions opensc/0.19.0-1.
> found 972036 0.19.0-1
Bug #972036 {Done: Eric Dorland } [opensc] CVE-2020-26571
Marked as found in versions opensc/0.19.0-1.
> found 972035 0.19.0-1
Bug #972035 {Done: Eric Dorland } [opensc] CVE-2020-26572
Marked as found in versions opensc/0.19.0-1.
> unarchive 942067
Bug #942067 {Done: Michael Biebl } [src:rsyslog] rsyslog:
CVE-2019-17041
Unarchived Bug 942067
> unarchive 942065
Bug #942065 {Done: Michael Biebl } [src:rsyslog] rsyslog:
CVE-2019-17042
Unarchived Bug 942065
> found 942067 8.1901.0-1
Bug #942067 {Done: Michael Biebl } [src:rsyslog] rsyslog:
CVE-2019-17041
Marked as found in versions rsyslog/8.1901.0-1.
> found 942065 8.1901.0-1
Bug #942065 {Done: Michael Biebl } [src:rsyslog] rsyslog:
CVE-2019-17042
Marked as found in versions rsyslog/8.1901.0-1.
> unarchive 941697
Bug #941697 {Done: Romain Francoise } [src:libpcap]
libpcap: CVE-2018-16301 CVE-2019-15165
Unarchived Bug 941697
> found 941697 1.8.1-6
Bug #941697 {Done: Romain Francoise } [src:libpcap]
libpcap: CVE-2018-16301 CVE-2019-15165
Marked as found in versions libpcap/1.8.1-6.
> unarchive 935553
Bug #935553 {Done: Bertrand Marc } [src:libextractor]
libextractor: CVE-2019-15531
Unarchived Bug 935553
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
935553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935553
939668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939668
939669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939669
941697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941697
942065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942065
942067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942067
947383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947383
951289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951289
966647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966647
972035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972035
972036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972036
972037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972037
973770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973770
977764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977764
987853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=987853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: pypandoc: diff for NMU version 1.7.2+ds0-1.1
Processing control commands:
> tags 1005778 + patch
Bug #1005778 {Done: Paul Gevers } [src:pypandoc]
src:pypandoc: fails to migrate to testing for too long: autopkgtest failure
Added tag(s) patch.
> tags 1005778 + pending
Bug #1005778 {Done: Paul Gevers } [src:pypandoc]
src:pypandoc: fails to migrate to testing for too long: autopkgtest failure
Added tag(s) pending.
--
1005778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1005778: pypandoc: diff for NMU version 1.7.2+ds0-1.1
Control: tags 1005778 + patch
Control: tags 1005778 + pending
Dear maintainer,
I've prepared an NMU for pypandoc (versioned as 1.7.2+ds0-1.1) and
it will be uploaded by my Account Manager, Sebastian Ramacher.
Please feel free to tell me if he should delay it.
lmodern needed be listed as a regular Depends, not just a
Build-Depends, in order for the autopkgtests to successfully
run. I have added it, and verified that this fixes the
autopkgtests on the testing distribution.
hack on, nick
diff -Nru pypandoc-1.7.2+ds0/debian/changelog pypandoc-1.7.2+ds0/debian/changelog
--- pypandoc-1.7.2+ds0/debian/changelog 2021-12-29 05:19:10.0 -0500
+++ pypandoc-1.7.2+ds0/debian/changelog 2022-02-28 10:12:41.0 -0500
@@ -1,3 +1,11 @@
+pypandoc (1.7.2+ds0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add dependency on lmodern for runtime to fix autopkgtests.
+Closes: #1005778
+
+ -- Nick Black Mon, 28 Feb 2022 10:12:41 -0500
+
pypandoc (1.7.2+ds0-1) unstable; urgency=medium
* New upstream release.
diff -Nru pypandoc-1.7.2+ds0/debian/control pypandoc-1.7.2+ds0/debian/control
--- pypandoc-1.7.2+ds0/debian/control 2021-12-29 05:19:10.0 -0500
+++ pypandoc-1.7.2+ds0/debian/control 2022-02-28 10:10:24.0 -0500
@@ -27,6 +27,7 @@
Package: python3-pypandoc
Architecture: all
Depends:
+ lmodern,
pandoc,
${misc:Depends},
${python3:Depends}
Bug#1006369: re-installation Buster 10.10
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 there is the follow-up report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006442 -BEGIN PGP SIGNATURE- iF0EARECAB0WIQTF9uNaslvnJpWt8kXn6sEfJS3nCwUCYhzblgAKCRDn6sEfJS3n C9CQAJ91gxj3o33yl4/XpLLB7Fsx0TNUTwCfRpyG/qUu3n1D7W2OEee6fs+IsOw= =ZX4M -END PGP SIGNATURE-
Bug#1005594: marked as done (rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0:)
Your message dated Mon, 28 Feb 2022 11:18:43 + with message-id and subject line Bug#1005594: fixed in gstreamer-editing-services1.0 1.20.0-2 has caused the Debian Bug report #1005594, regarding rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1005594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rygel Version: 0.40.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220212 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -Dsystemd-user-units-dir=/usr/lib/systemd/user \ > -Dapi-docs=true \ > -Dintrospection=disabled \ > -Dexamples=false \ > -Dplugins=external,gst-launch,media-export,mpris,playbin,ruih,tracker3 > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu > -Dsystemd-user-units-dir=/usr/lib/systemd/user -Dapi-docs=true > -Dintrospection=disabled -Dexamples=false > -Dplugins=external,gst-launch,media-export,mpris,playbin,ruih,tracker3 > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: rygel > Project version: 0.40.3 > C compiler for the host machine: cc (gcc 11.2.0 "cc (Debian 11.2.0-16) > 11.2.0") > C linker for the host machine: cc ld.bfd 2.38 > Vala compiler for the host machine: valac (valac 0.54.6) > Host machine cpu family: x86_64 > Host machine cpu: x86_64 > Program build-aux/meson/install-gtkdoc.py found: YES (/usr/bin/python3 > /<>/build-aux/meson/install-gtkdoc.py) > Program valadoc found: YES (/usr/bin/valadoc) > Found pkg-config: /usr/bin/pkg-config (0.29.2) > Run-time dependency gtk-doc found: YES 1.33.1 > Run-time dependency gupnp-1.2 found: YES 1.4.3 > Run-time dependency gee-0.8 found: YES 0.20.5 > Run-time dependency gssdp-1.2 found: YES 1.4.0.1 > Run-time dependency glib-2.0 found: YES 2.70.3 > Run-time dependency gio-2.0 found: YES 2.70.3 > Run-time dependency gio-unix-2.0 found: YES 2.70.3 > Run-time dependency gmodule-2.0 found: YES 2.70.3 > Run-time dependency libxml-2.0 found: YES 2.9.12 > Run-time dependency gupnp-av-1.0 found: YES 0.14.0 > Run-time dependency gupnp-dlna-2.0 found: YES 0.12.0 > Run-time dependency libsoup-2.4 found: YES 2.74.2 > Run-time dependency libmediaart-2.0 found: YES 1.9.5 > Run-time dependency sqlite3 found: YES 3.37.2 > Run-time dependency gstreamer-1.0 found: YES 1.20.0 > Run-time dependency gstreamer-pbutils-1.0 found: YES 1.20.0 > Run-time dependency gstreamer-base-1.0 found: YES 1.20.0 > Run-time dependency gstreamer-audio-1.0 found: YES 1.20.0 > Run-time dependency gstreamer-video-1.0 found: YES 1.20.0 > Run-time dependency gstreamer-tag-1.0 found: YES 1.20.0 > Did not find CMake 'cmake' > Found CMake: NO > Run-time dependency gst-editing-services-1.0 found: NO > > ../meson.build:99:0: ERROR: Could not generate cargs for > gst-editing-services-1.0: > Package python-3.9-embed was not found in the pkg-config search path. > Perhaps you should add the directory containing `python-3.9-embed.pc' > to the PKG_CONFIG_PATH environment variable > Package 'python-3.9-embed', required by 'gst-editing-services-1.0', not found > > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2022-02-12T22:39:48.797864 > Main binary: /usr/bin/python3 > Build Options: -Dsystemd-user-units-dir=/usr/lib/systemd/user -Dapi-docs=true > -Dintrospection=disabled -Dexamples=false > -Dplugins=external,gst-launch,media-export,mpris,playbin,ruih,tracker3 > -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var > -Dsysconfdir=/etc -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.61.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > Project name: rygel > Project version: 0.40.3 > Sanity testing C compiler: cc > Is cross compiler: False. > Sanity check compiler command line: cc sanitycheckc.c -o sanitycheckc.exe -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
Processed: Re: rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0:
Processing commands for cont...@bugs.debian.org: > reassign 1005594 libges-1.0-dev 1.20.0-1 Bug #1005594 [src:rygel] rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0: Bug reassigned from package 'src:rygel' to 'libges-1.0-dev'. No longer marked as found in versions rygel/0.40.3-1. Ignoring request to alter fixed versions of bug #1005594 to the same values previously set Bug #1005594 [libges-1.0-dev] rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0: Marked as found in versions gstreamer-editing-services1.0/1.20.0-1. > affects 1005594 src:rygel Bug #1005594 [libges-1.0-dev] rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0: Added indication that 1005594 affects src:rygel > thanks Stopping processing here. Please contact me if you need assistance. -- 1005594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1005594: rygel: FTBFS: ../meson.build:99:0: ERROR: Could not generate cargs for gst-editing-services-1.0:
reassign 1005594 libges-1.0-dev 1.20.0-1 affects 1005594 src:rygel thanks On Sun, 13 Feb 2022 08:31:17 +0100 Lucas Nussbaum wrote: > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > [...] > > Package 'python-3.9-embed', required by 'gst-editing-services-1.0', not found This is an issue with gstreamer-editing-services1.0 libges-1.0-dev package should depends against libpython3-dev (or libpython3.X-dev) as the .pc file requires it I'm not sure how to automatically calculate that we need libpython3.9-dev vs libpython3.10-dev for example
Processed: Bug#1006053 marked as pending in eslint
Processing control commands: > tag -1 pending Bug #1006053 [eslint] node-regexpp: FTBFS: Cannot find type definition file for 'eslint'. Added tag(s) pending. -- 1006053: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006053 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1006053: marked as pending in eslint
Control: tag -1 pending Hello, Bug #1006053 in eslint 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/eslint/-/commit/33993c07f998e9c5f4c897af9e00c6dc4b11c8e1 fix install all typescript types; closes: bug#1006053, thanks to Lucas Nussbaum (this message was generated automatically) -- Greetings https://bugs.debian.org/1006053
Processed: tagging 1006547
Processing commands for cont...@bugs.debian.org: > tags 1006547 + sid bookworm experimental Bug #1006547 [src:diaspora-installer] diaspora-installer: incompatible with ruby3.0 Added tag(s) experimental, sid, and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1006547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006547 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
