Bug#1000972: marked as done (ruby-jaeger-client: Depends on ruby-thrift:amd64 which isn't available on other architectures)
Your message dated Wed, 08 Dec 2021 07:48:56 + with message-id and subject line Bug#1000972: fixed in ruby-jaeger-client 1.2.0-2 has caused the Debian Bug report #1000972, regarding ruby-jaeger-client: Depends on ruby-thrift:amd64 which isn't available on other architectures 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.) -- 1000972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-jaeger-client Version: 1.2.0-1 Severity: serious Justification: uninstallable ruby-jaeger-client is on my radar because it doesn't migrate for a long time. I was very puzzled by the output of britney: > ruby-jaeger-client/amd64 has unsatisfiable dependency > ruby-jaeger-client/arm64 has unsatisfiable dependency Turns out this is probably a bug in britney, but it does point out an issue on all architectures but amd64. ruby-jaeger-client has a arch specifier in its depends: ruby-thrift:amd64. As I couldn't find this in the d/control file, I guess it's a tool chain issue (or a logical flow inside this package). You can see the uninstallability in action on ci.debian.net where all architectures fail in unstable except amd64. See below, grabbed from the arm64 Packages. Paul Package: ruby-jaeger-client Version: 1.2.0-1 Installed-Size: 183 Maintainer: Debian Ruby Team Architecture: all Depends: ruby:any, ruby-opentracing (>= 0.3), ruby-thrift:amd64 Description: OpenTracing Tracer implementation for Jaeger Homepage: https://github.com/salemove/jaeger-client-ruby Description-md5: a7ce2ef441d13cf5a973833acaa48379 Ruby-Versions: all Section: ruby Priority: optional Filename: pool/main/r/ruby-jaeger-client/ruby-jaeger-client_1.2.0-1_all.deb Size: 32476 MD5sum: 0d382dbd396d9496ce63cd2aa3360ec8 SHA256: 6df406498b9d15f095ece5355255c0a980ca70263c17bb0d3ab694261365d230 --- End Message --- --- Begin Message --- Source: ruby-jaeger-client Source-Version: 1.2.0-2 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-jaeger-client, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-jaeger-client 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, 08 Dec 2021 08:24:45 +0100 Source: ruby-jaeger-client Architecture: source Version: 1.2.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Daniel Leidert Closes: 1000972 Changes: ruby-jaeger-client (1.2.0-2) unstable; urgency=medium . * Team upload. * Rebuild with fixed gem2deb (closes: #1000972). Checksums-Sha1: 6eceb0b01a4e15d7cca78b4be9c3687d8fa3b01e 2195 ruby-jaeger-client_1.2.0-2.dsc 4bd7b53ed50849f2fc10b244ff25f2ca76bee56f 4072 ruby-jaeger-client_1.2.0-2.debian.tar.xz 020926a2dba355ecc730dd1ead64c744dc6c54d8 9701 ruby-jaeger-client_1.2.0-2_amd64.buildinfo Checksums-Sha256: dbd901918ed572086832a5c93c3d846e7d3211e094ff75e24b10fd7440f8c416 2195 ruby-jaeger-client_1.2.0-2.dsc 8cc015c455d58202bd663150202d2fe426b1b757693aa474564ea5a763e53565 4072 ruby-jaeger-client_1.2.0-2.debian.tar.xz 8c303b9abead8edb1b53fe614fcc65efe2b8c51bc2f83376d1f734d423ff40c3 9701 ruby-jaeger-client_1.2.0-2_amd64.buildinfo Files: 28339c458bcd45019a618c9a00059fc0 2195 ruby optional ruby-jaeger-client_1.2.0-2.dsc 9bbb0d5af8dae61d518df1c1d4021b67 4072 ruby optional ruby-jaeger-client_1.2.0-2.debian.tar.xz 2272561cc3f70793587e363582a14ed2 9701 ruby optional ruby-jaeger-client_1.2.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGwXhoACgkQS80FZ8KW 0F0QJw//c26XGMAZMRXJNgvNxs6N/5YmwwW243nZCIWgIecT37V70wO9Jz3Qg8pL 5SXHLG32tcSyQ8Nwtusodaj7Og1MjyAInaCa1PQFbc+FS6Ok6OEw08mIFDh3QCZg TtvVvzmC68WtrUsJsGiys8IlZxLrypNDS+zVbQcLki8ybee2YATNwIbevTL0Fxnk WLkajeaxvrYoeiu5IA+pnxycKwvq2Ojak3wpADe8bJCL0LnR+GJAlthRRg8KfuWW z+0vsBcuWyBXIfozAcGdhklilEAwKEyW/9zFBqityIYWOLzShuQsrxYqmo5RHQt4 YEO9X9aljjCq4hOhEVzmgfEjoWL4NBLE3UvUHrvnq/Xf4Xj9ktfl6JDcy2z0ErgZ OSCA075St4oV6fm8AgDJdeuUnVRSwOwdHMDF8RRoGRETjaiIlvNcu+ataykpF9r9
Bug#1001234: src:firefox-esr: fails to migrate to testing for too long: FTBFS on mipsel and unresolved RC bug
On Wed, Dec 08, 2021 at 09:07:24AM +0200, Martin-Éric Racine wrote: > Package: firefox-esr > Version: 78.15.0esr-1~deb11u1 > Followup-For: Bug #1001234 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > 91.4.0esr-1 was indeed uploaded. However, mipsel was not removed from the > list of architectures in the control file, so it attempted building. This > will likely prevent migration. I don't think removing the architecture from the control file would change anything wrt migration. > Better care in maintaining this package would be appreciated. CVE fixes have > yet to trickle into Testing or be uploaded to Stable-Updates for over 60 > days. That's not acceptable. For stable, it's not under my control. AFAIK, the necessary rust compiler is still not available yet. Mike
Bug#997620: marked as done (python-dexml: FTBFS: error in dexml setup command: use_2to3 is invalid.)
Your message dated Wed, 8 Dec 2021 08:33:02 +0100
with message-id <3da9c2f2-6a82-9a60-9b28-1a8b41937...@debian.org>
and subject line Re: python-dexml: FTBFS: error in dexml setup command:
use_2to3 is invalid.
has caused the Debian Bug report #997620,
regarding python-dexml: FTBFS: error in dexml setup command: use_2to3 is
invalid.
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.)
--
997620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-dexml
Version: 0.5.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in dexml setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:4: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-dexml_0.5.1-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
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 mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 0.5.1-3+rm
On Sat, 23 Oct 2021 23:15:50 +0200 Lucas Nussbaum wrote:
Source: python-dexml
Version: 0.5.1-3
During a rebuild of all packages in sid, your package failed to build
on amd64.
Removed from sid: https://bugs.debian.org/998621
Andreas--- End Message ---
Bug#1001312: kore: FTBFS with postgresql 14, with openssl 3
Package: kore Version: 4.1.0-4 Severity: serious Tags: patch Justification: ftbfs User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Hi Shih-Yuan, In Ubuntu, the kore source package is failing to build from source due to incompatibilities with both openssl 3 (currently in Debian experimental) and postgresql 14 (in Debian unstable): [...] src/config.c: In function ‘configure_tls_dhparam’: src/config.c:810:9: error: ‘PEM_read_bio_DHparams’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] 810 | tls_dhparam = PEM_read_bio_DHparams(bio, NULL, NULL, NULL); | ^~~ In file included from /usr/include/openssl/ssl.h:36, from include/kore/kore.h:35, from src/config.c:29: /usr/include/openssl/pem.h:469:1: note: declared here 469 | DECLARE_PEM_rw_attr(OSSL_DEPRECATEDIN_3_0, DHparams, DH) | ^~~ [...] (https://launchpad.net/ubuntu/+source/kore/4.1.0-4build1/+build/22583996) (Other errors follow this one) A patch to simply turn these errors back into warnings is sufficient to let the package build, and I think is a reasonable solution until upstream addresses these issues. Please see attached. Thanks for considering, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru kore-4.1.0/debian/rules kore-4.1.0/debian/rules --- kore-4.1.0/debian/rules 2020-09-25 08:41:16.0 -0700 +++ kore-4.1.0/debian/rules 2021-12-07 23:17:01.0 -0800 @@ -6,6 +6,8 @@ export TASKS=1 export PGSQL=1 export DEB_BUILD_MAINT_OPTIONS=hardening=+all +export DEB_CFLAGS_MAINT_APPEND = -Wno-error=deprecated-declarations \ + -Wno-error=discarded-qualifiers -Wno-error=switch %: dh $@
Processed: severity of 1000649 is important
Processing commands for cont...@bugs.debian.org: > # not yet release critical > severity 1000649 important Bug #1000649 [src:ruby-jaeger-client] ruby-jaeger-client FTBFS on IPV6-only buildds Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1000649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000649 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001234: src:firefox-esr: fails to migrate to testing for too long: FTBFS on mipsel and unresolved RC bug
Package: firefox-esr Version: 78.15.0esr-1~deb11u1 Followup-For: Bug #1001234 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 91.4.0esr-1 was indeed uploaded. However, mipsel was not removed from the list of architectures in the control file, so it attempted building. This will likely prevent migration. Better care in maintaining this package would be appreciated. CVE fixes have yet to trickle into Testing or be uploaded to Stable-Updates for over 60 days. That's not acceptable. Martin-Éric -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmGwWasACgkQrh+Cd8S0 17bKIA//QwVaZSjj17lL/tzje02i5CD1K4VNKTjSutNsQoJqa8YbBjSpbSl+qEsI Wwo0lYYFWA6D7I6dyQsErsLEHlC4V0QI/LbHC1aY097OAQf1zj/yGPIYlDyFOpxW oxOnWgSIXUwhNZbVdLm96kgjmHYPqZksJe9ZNqMwST8krtoRVnMdHlR0dqfZEYlq sskO6WPS4q52HzC8mmgzUY8aLcUQB36G1SbR4laQJHVH7NJoimQWVf2IwG5YOyZn A+OD0Gy8mN1E0dx4ALwxao8A6HrXik0uqiaSY2hbnxGy4tI+8JHgx5O1zq9fWvaI t6Hdnq77izrp7f+s/vozYK+GJaliz0HAJ9dUlogns4aYnbVppKV0bUMe/cAVP6Y0 4kPWuanKc5fetoa9bAYv1mcdhfD/ff7wVKHYGGVIrE+yW45S1eWoZ3R+FWzAuHx0 vHV2tgy+K25p09M078FHWal1SZkyzkgRrWnPEtLA5xppE9iNoiycanX4jOskSG2i 58P/x3vUfk/QqeeEkPLbwZGKjxNqSkCqZGiAsBHJXA+674vaHzm5dddWQQd2buNz iG67aB88yzfn0kcbZWlfoZWRqhDfXshnYA5pJ7jj0HC26Zc0C0uSC3ser/5KICtL WZwAfouqAIJPREp8l5VTaoN4W/8A+TL2EwpDiS7ZT8VYCdvhTn4= =HoFh -END PGP SIGNATURE-
Bug#1001311: certmonger: FTBFS with openssl 3
Source: certmonger Version: 0.79.14+git20211010-2 Severity: serious Tags: experimental User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy Hi Timo, certmonger FTBFS against openssl 3 with an undefined symbol error: [...] gcc -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -isystem /usr/include/mit-krb5 -I/usr/include/uuid -g -O2 -ffile-prefix-map=/<>/certmonger-0.79.14+git20211010=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -I/usr/include/libxml2 -I/usr/include/nss -I/usr/include/nspr -I/usr/include/x86_64-linux-gnu -g -O2 -ffile-prefix-map=/<>/certmonger-0.79.14+git20211010=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -fPIC -fPIC -pie -Wl,-z,relro,-z,now -o scep-submit scep_submit-scep.o scep_submit-submit-h.o scep_submit-util-m.o scep_submit-util-o.o scep_submit-submit-u.o scep_submit-util.o scep_submit-log.o scep_submit-pkcs7.o scep_submit-store-gen.o scep_submit-tm.o scep_submit-prefs.o scep_submit-prefs-o.o scep_submit-scep-o.o scep_submit-env-system.o -lcurl -lxml2 -lnss3 -lnssutil3 -lsmime3 -lssl3 -lplds4 -lplc4 -lnspr4 -lcrypto -ltalloc -luuid -lpopt ../../src/submit-h.c: In function ‘cm_submit_h_run’: ../../src/submit-h.c:257:17: warning: call to ‘_curl_easy_setopt_err_write_callback’ declared with attribute warning: curl_easy_setopt expects a curl_write_callback argument for this option [-Wattribute-warning] 257 | curl_easy_setopt(ctx->curl, CURLOPT_WRITEFUNCTION, | ^ /usr/bin/ld: /tmp/ccPXkLF2.ltrans0.ltrans.o: in function `main': ./build/src/../../src/util-o.c:54: undefined reference to `OPENSSL_init_ssl' collect2: error: ld returned 1 exit status [...] (https://launchpad.net/ubuntu/+source/certmonger/0.79.14+git20211010-2/+build/22293176) openssl 3 is currently in experimental, and is expected to ship with the next version of Debian. It is also the version of openssl to be used for the upcoming Ubuntu 22.04 LTS release. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Bug#1001307: ceres-solver: invalid Uploaders field: missing comma between Anton Gladky and Francois Mazen
Source: ceres-solver Version: 2.0.0+dfsg1-1~exp1 Severity: serious ceres-solver 2.0.0+dfsg1-1~exp1 introduced an invalid Uploaders field, that is missing a comma between Anton Gladky and Francois Mazen. $ apt-cache showsrc ceres-solver | grep -E '^$|^Version|^Uploaders' Version: 1.14.0-14 Uploaders: Philipp Huebner , Anton Gladky Version: 2.0.0+dfsg1-1~exp1 Uploaders: Anton Gladky Francois Mazen According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders This is causing the DDPO and BLS cron jobs to send error mails, please fix it as soon as possible. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#733094: uvcdynctrl still filling the disk
"Guvcview doesn't depend upon uvcdynctrl it just recommends it." Okay, but unless you disable "recommends", uvcdynctrl gets installed. Based on a little bit of research I performed, it is not recommended to disable "recommends" because recommended packages are usually needed for a more useful installation. Source of info for not disabling "recommends": https://unix.stackexchange.com/questions/122289/why-install-recommends-default-is-true Does guvcview function or function well enough without uvcdynctrl? *The following additional packages will be installed:** * * libguvcview-2.0-2 libportaudio2 libwebcam0 uvcdynctrl uvcdynctrl-data** * *The following NEW packages will be installed:** * * guvcview libguvcview-2.0-2 libportaudio2 libwebcam0 uvcdynctrl uvcdynctrl-data** * *0 upgraded, 6 newly installed, 0 to remove and 0 not upgraded.** * *Need to get 266 kB/386 kB of archives.** * *After this operation, 1,437 kB of additional disk space will be used.*
Bug#1001303: alure: FTBFS: -pthread: not found
Source: alure Version: 1.2-8 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy Dear maintainers, alure currently fails to build from source in sid because something in its build system produces a semicolon-separated list of build flags, which it then tries to pass directly on the commandline: [...] /usr/bin/c++ -DHAVE_CONFIG_H -D_GNU_SOURCE=1 -I/tmp/alure-1.2/include -I/tmp/alure-1.2/obj-x86_64-linux-gnu -I/usr/include/AL -g -O2 -ffile-prefix-map=/tmp/alure-1.2=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wextra -Wall -funswitch-loops -fvisibility=hidden -pthread -DALURE_STATIC_LIBRARY -fPIC -D_REENTRANT;-pthread;-D_REENTRANT;-D_DEFAULT_SOURCE;-D_XOPEN_SOURCE=600;-I/usr/include/dbus-1.0;-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include;-I/usr/include/libinstpatch-2;-I/usr/include/glib-2.0;-I/usr/lib/x86_64-linux-gnu/glib-2.0/include;-I/usr/include/opus;-I/usr/include/SDL2 -MD -MT CMakeFiles/alure-static.dir/src/codec_fluidsynth.o -MF CMakeFiles/alure-static.dir/src/codec_fluidsynth.o.d -o CMakeFiles/alure-static.dir/src/codec_fluidsynth.o -c /tmp/alure-1.2/src/codec_fluidsynth.cpp c++: fatal error: no input files compilation terminated. /bin/sh: 1: -pthread: not found /bin/sh: 1: -D_REENTRANT: not found /bin/sh: 1: -D_DEFAULT_SOURCE: not found /bin/sh: 1: -D_XOPEN_SOURCE=600: not found /bin/sh: 1: -I/usr/include/dbus-1.0: not found [...] I don't know what is causing this misbehavior of the build system; if I look at obj-x86_64-linux-gnu/CMakeCache.txt I see other variables using similar separators but these only seem to leak onto the commandline for the fluidsynth cflags: FLUIDSYNTH_CFLAGS:INTERNAL=-D_REENTRANT;-pthread;-D_REENTRANT;-D_DEFAULT_SOURCE;-D_XOPEN_SOURCE=600;-I/usr/include/dbus-1.0;-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include;-I/usr/include/libinstpatch-2;-I/usr/include/glib-2.0;-I/usr/lib/x86_64-linux-gnu/glib-2.0/include;-I/usr/include/opus;-I/usr/include/SDL2 -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: PGP signature
Processed: tagging 1001129, tagging 1000742
Processing commands for cont...@bugs.debian.org:
> tags 1001129 + sid bookworm
Bug #1001129 {Done: Daniel Leidert } [puppet] Ruby 3.0:
puppet/util.rb:469:in `uri_encode': undefined method `escape' for URI:Module
(NoMethodError)
Added tag(s) sid and bookworm.
> tags 1000742 + sid bookworm
Bug #1000742 {Done: Nilesh Patra } [python3-tabulate]
ImportError: cannot import name 'Iterable' from 'collections'
Added tag(s) sid and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1000742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000742
1001129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998679: marked as done (firefox-esr freezes shortly after start)
Your message dated Tue, 07 Dec 2021 22:12:02 +
with message-id
and subject line Bug#998679: fixed in firefox-esr 91.4.0esr-1
has caused the Debian Bug report #998679,
regarding firefox-esr freezes shortly after start
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.)
--
998679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox-esr
Version: 91.3.0esr-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after upgrading to esr91 I'm experiencing the same symptoms as
described in bug #998108 for firefox.
Regards,
GLG
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: DoH Roll-Out
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Don't track me Google
Location: ${PROFILE_EXTENSIONS}/dont-track-me-goo...@robwu.nl.xpi
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Proxy Failover
Location:
/home/gragnani/.mozilla/firefox/4k5qr2p9.default/features/{19dd109a-c7f4-40c6--790288660e5e}/proxy-failo...@mozilla.com.xpi
Status: enabled
Name: System theme theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled
Name: User-Agent Switcher and Manager
Location: ${PROFILE_EXTENSIONS}/{a6c4a591-f1b2-4f03-b3ff-767e5bedf4e7}.xpi
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: WebCompat Reporter
Location:
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
-- Addons package information
ii firefox-esr91.3.0esr-1 amd64Mozilla Firefox web browser -
Extended Support Release (ESR)
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.14.0-3-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages firefox-esr depends on:
ii debianutils 5.5-1
ii fontconfig 2.13.1-4.2
ii libatk1.0-0 2.36.0-2
ii libc62.32-4
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbus-1-3 1.12.20-3
ii libdbus-glib-1-2 0.112-2
ii libevent-2.1-7 2.1.12-stable-1
ii libffi8 3.4.2-3
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.11.0+dfsg-1
ii libgcc-s111.2.0-10
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libglib2.0-0 2.70.1-1
ii libgtk-3-0 3.24.30-3
ii libnspr4 2:4.32-1
ii libnss3 2:3.72-1
ii libpango-1.0-0 1.48.10+ds1-1
ii libstdc++6 11.2.0-10
ii libvpx7 1.11.0-2
ii libx11-6 2:1.7.2-2+b1
ii libx11-xcb1 2:1.7.2-2+b1
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.4-1
ii libxfixes3 1:5.0.3-2
ii
Bug#997363: libtorrent-rasterbar: FTBFS: configure: error: *** A compiler with support for C++17 language features is required.
On Saturday, December 04 2021, Petter Reinholdtsen wrote: > [Stefano Rivera] >> Presumably resolved in 2.0.0 in NEW, that doesn't use autoconf any more. > > Perhaps, but as NEW processing these days take a long time, as a user of > the library I would prefer a fix for 1.2.14-1 in the mean time. > > The easiest fix seem to be to bypass the c++ standard detector which > fail in configure.ac, causing the problematic test for C++17, while both > C++11 and C++14 would work, by adding --with-cxx-standard=14 like this: > > --- rules.orig2021-12-04 07:42:25.578757615 +0100 > +++ rules 2021-12-04 07:37:18.662074573 +0100 > @@ -13,7 +13,8 @@ > PYTHON3=$(shell py3versions -vr) > ALLPY=$(PYTHON3) > > -CONFIGURE_ARGS = --with-libiconv > --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) > +CONFIGURE_ARGS = --with-libiconv > --with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \ > + --with-cxx-standard=14 > > %: > dh $@ --with python3 > > It would also help a lot if the next upload is a source only upload. Thanks for the patch, Petter. I agree that it's a good compromise in order to make the package build again, especially considering that version 2 is already in NEW. I tried building libtorrent-rasterbar with your patch, but found that there was yet another problem happening: its Jamfile wasn't working with Python 3.10, which is already in the archive. I went ahead and filed a bug report, and the upstream was very quick in fixing it. Anyway, the package builds locally now, so I'm going to take the liberty to upload an NMU to DELAYED/5. Andrew, feel free to remove it from the queue if you'd like to tackle this upload yourself. If/when the NMU is accepted, I will "gbp push" what I have locally so that the git repo stays in sync. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible https://sergiodj.net/ signature.asc Description: PGP signature
Processed: dominate: needs update for python3.10: 'Callable' from 'collections' is removed
Processing control commands: > affects -1 src:python3-defaults Bug #1001295 [src:dominate] dominate: needs update for python3.10: 'Callable' from 'collections' is removed Added indication that 1001295 affects src:python3-defaults -- 1001295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001295 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001295: dominate: needs update for python3.10: 'Callable' from 'collections' is removed
Source: dominate Version: 2.3.1-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults Dear maintainer(s), With a recent upload of python3-defaults the autopkgtest of dominate fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 dominate from testing2.3.1-2 all others from testingfrom testing I copied some of the output at the bottom of this report. https://docs.python.org/3.9/library/collections.html says: """ Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9. """ Time to move on. Currently this regression is blocking the migration of python3-defaults to testing [1]. 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=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/d/dominate/17344293/log.gz Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/dominate/__init__.py", line 4, in from .document import document File "/usr/lib/python3/dist-packages/dominate/document.py", line 19, in from . import tags File "/usr/lib/python3/dist-packages/dominate/tags.py", line 21, in from .dom_tag import dom_tag, attr File "/usr/lib/python3/dist-packages/dominate/dom_tag.py", line 23, in from collections import defaultdict, namedtuple, Callable ImportError: cannot import name 'Callable' from 'collections' (/usr/lib/python3.10/collections/__init__.py) autopkgtest [20:14:07]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: django-mailman3: FTBFS with python3.10 added to supported python3 versions
Processing control commands: > affects -1 src:python3-defaults Bug #1001294 [src:django-mailman3] django-mailman3: FTBFS with python3.10 added to supported python3 versions Added indication that 1001294 affects src:python3-defaults -- 1001294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001292: deepdiff: needs update for python3.10: 'Mapping' from 'collections' is removed
Source: deepdiff Version: 3.3.0-2 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults Dear maintainer(s), With a recent upload of python3-defaults the autopkgtest of deepdiff fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 deepdiff from testing3.3.0-2 all others from testingfrom testing I copied some of the output at the bottom of this report. https://docs.python.org/3.9/library/collections.html says: """ Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9. """ Time to move on. Currently this regression is blocking the migration of python3-defaults to testing [1]. 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=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/d/deepdiff/17344291/log.gz Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/deepdiff/__init__.py", line 7, in from .diff import DeepDiff File "/usr/lib/python3/dist-packages/deepdiff/diff.py", line 19, in from collections import Mapping ImportError: cannot import name 'Mapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py) autopkgtest [20:14:06]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: deepdiff: needs update for python3.10: 'Mapping' from 'collections' is removed
Processing control commands: > affects -1 src:python3-defaults Bug #1001292 [src:deepdiff] deepdiff: needs update for python3.10: 'Mapping' from 'collections' is removed Added indication that 1001292 affects src:python3-defaults -- 1001292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001292 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001291: binoculars: autopkgtest tests for all supported python3 versions but vtk7 extensions don't exist for all
Source: binoculars
Version: 0.0.6-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python3-defaults
Dear maintainer(s),
With a recent upload of python3-defaults the autopkgtest of binoculars
fails in testing when that autopkgtest is run with the binary packages
of python3-defaults from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python3-defaults from testing3.9.8-1
binoculars from testing0.0.6-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. It seems
you're testing for all supported Python3 version in Debian, but one of
your dependencies doesn't provide the required extensions (bug #951300).
Either convince the maintainer of that package to build the extensions,
or only test with the default Python3 version.
Currently this regression is blocking the migration of python3-defaults
to testing [1].
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=python3-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/b/binoculars/17344284/log.gz
Testing with python3.10:
test_IO (test_cfg.TestCase) ... ok
test_id03 (unittest.loader._FailedTest) ... ERROR
test_metadata (unittest.loader._FailedTest) ... ERROR
==
ERROR: test_id03 (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_id03
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/vtk/vtkCommonCore.py", line 5,
in
from .vtkCommonCorePython import *
ModuleNotFoundError: No module named 'vtk.vtkCommonCorePython'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/loader.py", line 436, in
_find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python3.10/unittest/loader.py", line 377, in
_get_module_from_name
__import__(name)
File
"/tmp/autopkgtest-lxc.73x5fv_7/downtmp/autopkgtest_tmp/tests/test_id03.py",
line 1, in
from binoculars.backends import id03
File "/usr/lib/python3/dist-packages/binoculars/backends/id03.py",
line 10, in
from .. import backend, errors, util
File "/usr/lib/python3/dist-packages/binoculars/backend.py", line 1,
in
from . import util, errors, dispatcher
File "/usr/lib/python3/dist-packages/binoculars/dispatcher.py", line
9, in
from . import util, errors, space
File "/usr/lib/python3/dist-packages/binoculars/space.py", line 13,
in
from vtk import vtkImageData, vtkXMLImageDataWriter
File "/usr/lib/python3/dist-packages/vtk/__init__.py", line 41, in
from .vtkCommonCore import *
File "/usr/lib/python3/dist-packages/vtk/vtkCommonCore.py", line 9,
in
from vtkCommonCorePython import *
ModuleNotFoundError: No module named 'vtkCommonCorePython'
==
ERROR: test_metadata (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_metadata
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/vtk/vtkCommonCore.py", line 5,
in
from .vtkCommonCorePython import *
ModuleNotFoundError: No module named 'vtk.vtkCommonCorePython'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/loader.py", line 436, in
_find_test_path
module = self._get_module_from_name(name)
File "/usr/lib/python3.10/unittest/loader.py", line 377, in
_get_module_from_name
__import__(name)
File
"/tmp/autopkgtest-lxc.73x5fv_7/downtmp/autopkgtest_tmp/tests/test_metadata.py",
line 2, in
import binoculars.space
File "/usr/lib/python3/dist-packages/binoculars/space.py", line 13,
in
from vtk import vtkImageData, vtkXMLImageDataWriter
File "/usr/lib/python3/dist-packages/vtk/__init__.py", line 41, in
from .vtkCommonCore import *
File "/usr/lib/python3/dist-packages/vtk/vtkCommonCore.py", line 9,
in
from vtkCommonCorePython import *
ModuleNotFoundError: No module named 'vtkCommonCorePython'
--
Ran 3 tests in 0.022s
FAILED (errors=2)
ConfigFile{
[dispatcher]
destination = b'demo_{first}-{last}.hdf5'
overwrite = b'true'
type = b'local'
[projection]
resolution = b'0.002, 0.002, 1'
type = b'id03:hklprojection'
[input]
centralpixel = b'40, 255'
imagefolder =
Processed: binoculars: autopkgtest tests for all supported python3 versions but vtk7 extensions don't exist for all
Processing control commands: > affects -1 src:python3-defaults Bug #1001291 [src:binoculars] binoculars: autopkgtest tests for all supported python3 versions but vtk7 extensions don't exist for all Added indication that 1001291 affects src:python3-defaults -- 1001291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: convertdate: autopkgtest tests for all supported python3s but fails to install them
Processing control commands: > affects -1 src:python3-defaults Bug #1001290 [src:convertdate] convertdate: autopkgtest tests for all supported python3s but fails to install them Added indication that 1001290 affects src:python3-defaults -- 1001290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001290 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001290: convertdate: autopkgtest tests for all supported python3s but fails to install them
Source: convertdate Version: 2.3.2-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults Dear maintainer(s), With a recent upload of python3-defaults the autopkgtest of convertdate fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 convertdatefrom testing2.3.2-1 all others from testingfrom testing I copied some of the output at the bottom of this report. It seems the test tries to test for all supported Python3 versions, but fails to ensure all those versions are actually installed during the test. Currently this regression is blocking the migration of python3-defaults to testing [1]. 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=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/c/convertdate/17344289/log.gz + cp -r tests/ /tmp/autopkgtest-lxc.9wwlakm4/downtmp/autopkgtest_tmp + cd /tmp/autopkgtest-lxc.9wwlakm4/downtmp/autopkgtest_tmp/ + export PYTHONWARNINGS=d + py3versions -s + echo -- + echo Testing with python3.10 + echo -- + LC_ALL=C python3.10 -m unittest discover --verbose /tmp/autopkgtest-lxc.9wwlakm4/downtmp/build.aU4/src/debian/tests/python3-unittest: 11: python3.10: not found -- Testing with python3.10 -- autopkgtest [20:13:28]: test python3-unittest OpenPGP_signature Description: OpenPGP digital signature
Bug#997278: marked as done (pidgin-sipe: FTBFS: sipe-tls-tester.c:158:17: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Werror=deprecated-declarations])
Your message dated Tue, 07 Dec 2021 21:03:36 + with message-id and subject line Bug#997278: fixed in pidgin-sipe 1.25.0-2.1 has caused the Debian Bug report #997278, regarding pidgin-sipe: FTBFS: sipe-tls-tester.c:158:17: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead [-Werror=deprecated-declarations] 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.) -- 997278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pidgin-sipe Version: 1.25.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wall -Wextra > -Waggregate-return -Wcast-align -Wcast-function-type > -Wdeclaration-after-statement -Wdeprecated-declarations > -Wduplicate-decl-specifier -Winit-self -Wmaybe-uninitialized > -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith > -Wunused-but-set-variable -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -DLOCALEDIR=\"/usr/share/locale\" -I./../api -isystem /usr/include/mit-krb5 > -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freerdp2/ > -I/usr/include/winpr2 -I/usr/include/nss -I/usr/include/nspr -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o libsipe_core_crypto_la-sipe-cert-crypto-nss.lo > `test -f 'sipe-cert-crypto-nss.c' || echo './'`sipe-cert-crypto-nss.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -Werror -Wall -Wextra -Waggregate-return -Wcast-align > -Wcast-function-type -Wdeclaration-after-statement -Wdeprecated-declarations > -Wduplicate-decl-specifier -Winit-self -Wmaybe-uninitialized > -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith > -Wunused-but-set-variable -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -DLOCALEDIR=\"/usr/share/locale\" -I./../api -isystem /usr/include/mit-krb5 > -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freerdp2/ > -I/usr/include/winpr2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -c sipe-tls.c > -fPIC -DPIC -o .libs/libsipe_core_la-sipe-tls.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time > -D_FORTIFY_SOURCE=2 -Werror -Wall -Wextra -Waggregate-return -Wcast-align > -Wcast-function-type -Wdeclaration-after-statement -Wdeprecated-declarations > -Wduplicate-decl-specifier -Winit-self -Wmaybe-uninitialized > -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith > -Wunused-but-set-variable -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -DLOCALEDIR=\"/usr/share/locale\" -I./../api -isystem /usr/include/mit-krb5 > -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freerdp2/ > -I/usr/include/winpr2 -I/usr/include/nss -I/usr/include/nspr -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c sipe-cert-crypto-nss.c -fPIC -DPIC -o > .libs/libsipe_core_crypto_la-sipe-cert-crypto-nss.o > sipe-tls-tester.c: In function ‘read_tls_record’: > sipe-tls-tester.c:158:17: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' > instead [-Werror=deprecated-declarations] > 158 | record->msg = g_memdup(buffer, result); > | ^~ > In file included from /usr/include/glib-2.0/glib.h:82, > from sipe-tls-tester.c:61: > /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here > 257 | gpointer g_memdup (gconstpointer mem, > | ^~~~ > sipe-tls.c: In function ‘sipe_tls_prf’: > sipe-tls.c:430:9: error: ‘g_memdup’ is deprecated: Use 'g_memdup2' instead > [-Werror=deprecated-declarations] > 430 | guchar *secret2 = g_memdup(secret + secret_length - half, > half); > | ^~ > In file included from /usr/include/glib-2.0/glib.h:82, > from sipe-tls.c:41: > /usr/include/glib-2.0/glib/gstrfuncs.h:257:23: note: declared here > 257 |
Bug#1001289: colorclass: needs update for python3.10: 'Mapping' from 'collections' is removed
Source: colorclass Version: 2.2.0-2.1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:python3-defaults Dear maintainer(s), With a recent upload of python3-defaults the autopkgtest of colorclass fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.9.8-1 colorclass from testing2.2.0-2.1 all others from testingfrom testing I copied some of the output at the bottom of this report. https://docs.python.org/3.9/library/collections.html says: """ Deprecated since version 3.3, will be removed in version 3.10: Moved Collections Abstract Base Classes to the collections.abc module. For backwards compatibility, they continue to be visible in this module through Python 3.9. """ Time to move on. Currently this regression is blocking the migration of python3-defaults to testing [1]. Of course, python3-defaults shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in python3-defaults was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from python3-defaults should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. 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=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/c/colorclass/17344288/log.gz Testing with python3.10: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/colorclass/__init__.py", line 11, in from colorclass.codes import list_tags # noqa File "/usr/lib/python3/dist-packages/colorclass/codes.py", line 4, in from collections import Mapping ImportError: cannot import name 'Mapping' from 'collections' (/usr/lib/python3.10/collections/__init__.py) autopkgtest [20:13:20]: test autodep8-python3 OpenPGP_signature Description: OpenPGP digital signature
Processed: colorclass: needs update for python3.10: 'Mapping' from 'collections' is removed
Processing control commands: > affects -1 src:python3-defaults Bug #1001289 [src:colorclass] colorclass: needs update for python3.10: 'Mapping' from 'collections' is removed Added indication that 1001289 affects src:python3-defaults -- 1001289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001234: src:firefox-esr: fails to migrate to testing for too long: FTBFS on mipsel and unresolved RC bug
Hi Mike, On 06-12-2021 23:07, Mike Hommey wrote: The FTBFS on mipsel is not going to go away ever. The rust compiler needs more than 2GB of memory to compile a specific crate in Firefox, and processes on mipsel can only get 2GB memory. The only way around that would be to cross-compile, which Debian doesn't do as of today. We'll have to remove firefox-esr on mipsel. You'd want to file a removal bug against ftp.debian.org to achieve that. It won't happen automagically. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: tensorpipe: diff for NMU version 0.0~git20210304.369e855-2.1
Processing control commands: > tags 997774 + patch Bug #997774 [src:tensorpipe] tensorpipe: FTBFS: dh_missing: error: missing files, aborting Added tag(s) patch. > tags 997774 + pending Bug #997774 [src:tensorpipe] tensorpipe: FTBFS: dh_missing: error: missing files, aborting Added tag(s) pending. -- 997774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: update bts with right meta data
Processing commands for cont...@bugs.debian.org:
> reassign 1001238 src:gwcs 0.16.1-1
Bug #1001238 {Done: Ole Streicher } [src:astropy, src:gwcs]
astropy breaks gwcs autopkgtest: module 'astropy.modeling.utils' has no
attribute '_BoundingBox'
Bug reassigned from package 'src:astropy, src:gwcs' to 'src:gwcs'.
No longer marked as found in versions gwcs/0.16.1-1 and astropy/5.0-1.
No longer marked as fixed in versions gwcs/0.17.0-1.
Bug #1001238 {Done: Ole Streicher } [src:gwcs] astropy
breaks gwcs autopkgtest: module 'astropy.modeling.utils' has no attribute
'_BoundingBox'
Marked as found in versions gwcs/0.16.1-1.
> fixed 1001238 0.17.0-1
Bug #1001238 {Done: Ole Streicher } [src:gwcs] astropy
breaks gwcs autopkgtest: module 'astropy.modeling.utils' has no attribute
'_BoundingBox'
Marked as fixed in versions gwcs/0.17.0-1.
> affects 1001238 astropy
Bug #1001238 {Done: Ole Streicher } [src:gwcs] astropy
breaks gwcs autopkgtest: module 'astropy.modeling.utils' has no attribute
'_BoundingBox'
Added indication that 1001238 affects astropy
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997774: tensorpipe: diff for NMU version 0.0~git20210304.369e855-2.1
Control: tags 997774 + patch Control: tags 997774 + pending Dear maintainer, I've prepared an NMU for tensorpipe (versioned as 0.0~git20210304.369e855-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru tensorpipe-0.0~git20210304.369e855/debian/changelog tensorpipe- 0.0~git20210304.369e855/debian/changelog --- tensorpipe-0.0~git20210304.369e855/debian/changelog 2021-09-01 22:19:19.0 -0400 +++ tensorpipe-0.0~git20210304.369e855/debian/changelog 2021-12-07 15:09:03.0 -0500 @@ -1,3 +1,13 @@ +tensorpipe (0.0~git20210304.369e855-2.1) unstable; urgency=high + + * Non-maintainer upload. + * debian/not-installed: Also exclude the following files from +installation: (Closes: #997774) ++ usr/lib/*/cmake/GTest/GMockTargets-none.cmake ++ usr/lib/*/cmake/GTest/GMockTargets.cmake + + -- Boyuan Yang Tue, 07 Dec 2021 15:09:03 -0500 + tensorpipe (0.0~git20210304.369e855-2) unstable; urgency=medium * Upload to unstable. diff -Nru tensorpipe-0.0~git20210304.369e855/debian/not-installed tensorpipe- 0.0~git20210304.369e855/debian/not-installed --- tensorpipe-0.0~git20210304.369e855/debian/not-installed 2021-09-01 22:19:00.0 -0400 +++ tensorpipe-0.0~git20210304.369e855/debian/not-installed 2021-12-07 15:08:59.0 -0500 @@ -6,6 +6,8 @@ usr/lib/*/pkgconfig/gtest_main.pc usr/lib/*/pkgconfig/gtest.pc usr/lib/*/pkgconfig/gmock.pc +usr/lib/*/cmake/GTest/GMockTargets-none.cmake +usr/lib/*/cmake/GTest/GMockTargets.cmake usr/lib/*/cmake/GTest/GTestConfig.cmake usr/lib/*/cmake/GTest/GTestConfigVersion.cmake usr/lib/*/cmake/GTest/GTestTargets.cmake signature.asc Description: This is a digitally signed message part
Bug#997213: i2p: FTBFS: [javac] /<>/apps/jetty/java/src/net/i2p/jetty/I2PRequestLog.java:25: error: package javax.servlet.http does not exist
On Mon, 6 Dec 2021 21:11:13 +0200 Adrian Bunk wrote: The problem is a missing build dependency on libservlet3.1-java (this was previously hidden by libjetty9-java depending on libservlet3.1-java). I haven't checked whether a runtime dependency on libservlet3.1-java is also missing. cu Adrian Thanks Adrian, I'll fix it upstream, unfortunately the maintainer is not responsive and i2p in Debian is 1 year and 4 releases behind already.
Bug#976493: marked as done (ruby-psych: FTBFS: NameError: undefined method `default_specifications_dir' for class `#')
Your message dated Tue, 07 Dec 2021 19:03:50 +
with message-id
and subject line Bug#976493: fixed in ruby-psych 3.3.2-1
has caused the Debian Bug report #976493,
regarding ruby-psych: FTBFS: NameError: undefined method
`default_specifications_dir' for class `#'
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.)
--
976493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-psych
Version: 3.1.0+really3.1.0-1
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> JRUBY_HOME=/usr/share/jruby jruby -S rake compile
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> jnr.posix.JavaLibCHelper$ReflectiveAccess to method
> sun.nio.ch.SelChImpl.getFD()
> WARNING: Please consider reporting this to the maintainers of
> jnr.posix.JavaLibCHelper$ReflectiveAccess
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> NameError: undefined method `default_specifications_dir' for class
> `#'
> singleton class at
> /usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb:84
> at
> /usr/lib/ruby/vendor_ruby/rubygems/defaults/operating_system.rb:58
> require at org/jruby/RubyKernel.java:956
> at /usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1
> require at org/jruby/RubyKernel.java:956
> at /usr/share/jruby/lib/ruby/stdlib/rubygems.rb:1347
> load at org/jruby/RubyKernel.java:974
> at uri:classloader:/jruby/kernel/gem_prelude.rb:1
> make[1]: *** [debian/rules:12: override_dh_auto_build-indep] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/12/05/ruby-psych_3.1.0+really3.1.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.
--- End Message ---
--- Begin Message ---
Source: ruby-psych
Source-Version: 3.3.2-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-psych, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-psych 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, 07 Dec 2021 19:36:02 +0100
Source: ruby-psych
Architecture: source
Version: 3.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 959571 976493
Changes:
ruby-psych (3.3.2-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
.
[ Debian Janitor ]
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Add libbytelist-java and libjcodings-java.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add myself.
* d/javabuild: Add to build psych.jar with javahelper.
* d/ruby-tests.rake: Add missing
Bug#959571: marked as done (ruby-psych: FTBFS: LoadError: no such file to load -- psych)
Your message dated Tue, 07 Dec 2021 19:03:50 +
with message-id
and subject line Bug#959571: fixed in ruby-psych 3.3.2-1
has caused the Debian Bug report #959571,
regarding ruby-psych: FTBFS: LoadError: no such file to load -- psych
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.)
--
959571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-psych
Version: 3.1.0+really3.1.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200501 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> JRUBY_HOME=/usr/share/jruby jruby -S rake compile
> /usr/share/jruby/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:55:in
> `require':
> It seems your ruby installation is missing psych (for YAML output).
> To eliminate this warning, please install libyaml and reinstall your ruby.
> rake aborted!
> LoadError: no such file to load -- psych
> /<>/Rakefile:1:in `(root)'
> /<>/Rakefile:14:in `block in (root)'
> (See full trace by running task with --trace)
> make[1]: *** [debian/rules:12: override_dh_auto_build-indep] Error 1
The full build log is available from:
http://qa-logs.debian.net/2020/05/01/ruby-psych_3.1.0+really3.1.0-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: ruby-psych
Source-Version: 3.3.2-1
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-psych, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-psych 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, 07 Dec 2021 19:36:02 +0100
Source: ruby-psych
Architecture: source
Version: 3.3.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 959571 976493
Changes:
ruby-psych (3.3.2-1) unstable; urgency=medium
.
* Team upload.
* New upstream release.
.
[ Debian Janitor ]
* Bump debhelper from old 11 to 12.
* Set debhelper-compat version in Build-Depends.
* Set upstream metadata fields: Bug-Database, Bug-Submit.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root field.
(Standards-Version): Bump to 4.6.0.
(Build-Depends): Add libbytelist-java and libjcodings-java.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/copyright: Add Upstream-Contact field.
(Copyright): Add myself.
* d/javabuild: Add to build psych.jar with javahelper.
* d/ruby-tests.rake: Add missing options to run tests.
* d/rules: Enable gem installation layout. Build Java extension without
running jruby directly (closes: #976493, #959571).
* d/watch: Improve watch file.
* d/patches/: Refresh patches.
* d/upstream/metadata: Update and complete.
Checksums-Sha1:
df45b74af019be7ac9febf901e1ffe2cf0149c27 2251 ruby-psych_3.3.2-1.dsc
a31dec34722f5bcb7c4f3a295b051d33dcc20739 145989 ruby-psych_3.3.2.orig.tar.gz
b27a8bc9d0a0065fd3afa23a2e6d0cc64222e1cd 9536 ruby-psych_3.3.2-1.debian.tar.xz
ab19da7d3f219062606da625246a004796dd5d5b 13266
ruby-psych_3.3.2-1_amd64.buildinfo
Checksums-Sha256:
0e73b4a451f5258d678cf4d0d873f98fc047d82732a4ed6c166bbc5ed9af0b1f 2251
ruby-psych_3.3.2-1.dsc
c3b7e1ebdb41c9b3f224293cfd3a7d2731917822672b92bde6e3b56d28018217 145989
ruby-psych_3.3.2.orig.tar.gz
d602a174d43f35107bad9a651e02f16a7e2df25cb7e110ae6239aad235f57ce3 9536
ruby-psych_3.3.2-1.debian.tar.xz
9d4aa89e2f846f0c2125b2235a48d8d96853cc8a171cda7cc7e456768becd6d6 13266
ruby-psych_3.3.2-1_amd64.buildinfo
Files:
Bug#996409: marked as done (libstatgen breaks minimac4 autopkgtest: Segmentation fault)
Your message dated Tue, 07 Dec 2021 19:00:17 + with message-id and subject line Bug#996409: fixed in libstatgen 1.0.15-3~0exp0 has caused the Debian Bug report #996409, regarding libstatgen breaks minimac4 autopkgtest: Segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libstatgen, minimac4 Control: found -1 libstatgen/1.0.15-1 Control: found -1 minimac4/1.0.2-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libstatgen the autopkgtest of minimac4 fails in testing when that autopkgtest is run with the binary packages of libstatgen from unstable. It passes when run with only packages from testing. In tabular form: passfail libstatgen from testing1.0.15-1 minimac4 from testing1.0.2-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of libstatgen 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=libstatgen https://ci.debian.net/data/autopkgtest/testing/amd64/m/minimac4/15927915/log.gz autopkgtest [21:29:13]: test run-sample-analysis: [--- Minimac4 - Fast Imputation Based on State Space Reduction HMM (c) 2014 - Sayantan Das, Christian Fuchsberger, David Hinds Mary Kate Wing, Goncalo Abecasis Version: 1.0.2; Built: 2019-11-05 by Reproducible Command Line Options: Reference Haplotypes : --refHaps [refPanel.m3vcf.gz], --passOnly, --rsid, --referenceEstimates [ON], --mapFile [docs/geneticMapFile.b38.map.txt.gz] Target Haplotypes : --haps [targetStudy.vcf.gz] Output Parameters : --prefix [testRun], --estimate, --nobgzip, --vcfBuffer [200], --format [GT,DS], --allTypedSites, --meta, --memUsage Chunking Parameters : --ChunkLengthMb [20.00], --ChunkOverlapMb [3.00] Subset Parameters : --chr [], --start, --end, --window Approximation Parameters : --minimac3, --probThreshold [0.01], --diffThreshold [0.01], --topThreshold [0.01] Other Parameters : --log, --help, --cpus [5], --params PhoneHome : --noPhoneHome [ON], --phoneHomeThinning [50] URL = http://genome.sph.umich.edu/wiki/Minimac4 Starting Main Imputation/Estimation Analysis ... Performing preliminary check on input parameters... -- PRELIMINARY FILE CHECK -- Checking GWAS haplotype file : targetStudy.vcf.gz Gathering variant information ... Segmentation fault OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: libstatgen Source-Version: 1.0.15-3~0exp0 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of libstatgen, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated libstatgen 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:
Processed: Bug#976493 marked as pending in ruby-psych
Processing control commands: > tag -1 pending Bug #976493 [src:ruby-psych] ruby-psych: FTBFS: NameError: undefined method `default_specifications_dir' for class `#' Added tag(s) pending. -- 976493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#976493: marked as pending in ruby-psych
Control: tag -1 pending Hello, Bug #976493 in ruby-psych 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/ruby-team/ruby-psych/-/commit/e71781cff79f3af8d1a673fc5cb015b5e26675ac Re-enable Java extension * d/control (Build-Depends): Re-add jruby and java dependencies. Add libbytelist-java and libjcodings-java. * d/javabuild: Add to build psych.jar with javahelper. * d/rules: Build Java extension without running jruby directly (closes: #976493, #959571). (this message was generated automatically) -- Greetings https://bugs.debian.org/976493
Processed: Bug#959571 marked as pending in ruby-psych
Processing control commands: > tag -1 pending Bug #959571 [src:ruby-psych] ruby-psych: FTBFS: LoadError: no such file to load -- psych Added tag(s) pending. -- 959571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959571 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959571: marked as pending in ruby-psych
Control: tag -1 pending Hello, Bug #959571 in ruby-psych 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/ruby-team/ruby-psych/-/commit/e71781cff79f3af8d1a673fc5cb015b5e26675ac Re-enable Java extension * d/control (Build-Depends): Re-add jruby and java dependencies. Add libbytelist-java and libjcodings-java. * d/javabuild: Add to build psych.jar with javahelper. * d/rules: Build Java extension without running jruby directly (closes: #976493, #959571). (this message was generated automatically) -- Greetings https://bugs.debian.org/959571
Bug#995212: ungoogled-chromium? [was: Re: Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)]
On 06.12.21 20:43, Noah Meyerhans wrote: On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote: So what's happening with chromium in both sid and stable? I saw on d-release that it was removed from testing (#998676 and #998732), with a discussion about ending security support for it in stable. The problem really is lack of maintenance. In my opinion, chromium deserves an active *team* to support it in Debian. <...> The security team doesn't have the bandwidth to do it themselves, they need a team to help them. Sorry for a silly question, but whatʼs so wrong with the build done by linuxmint.com [1], so Debian needs a whole team to duplicate their effort? Itʼs for Debian 10 (i. e. oldstable) as of now, but works fine at Sid in my (limited) experience. Well, you can start with the fact that the Mint chromium source packages don't even include the chromium source, let alone the sources for all the other things they build (NodeJS, and more). The biggest difficulty, as far as I can tell from my look at Chromium from several months ago, is that our patch set [1] needs a lot of attention with every chromium release. Mint doesn't apply any patches at all to the source, at least none of any real complexity. One lesson we may take from Mint, though, is that it's not worth trying to patch Chromium as much as we'd like. Anything that we can do to simplify the Chromium packaging will help us keep the package up-to-date, which in turn will help us keep our users safer. In my opinion, we should be pretty aggressive about dropping as many of the Chromium patches as possible, even if that means we link against bundled/vendored dependencies. Legal/licensing considerations are still important and I don't know if we actually *can* ship builds based on the bundled stuff. But based on the number of patches we have to disable various things [2] or build against system dependencies [3], I can't help but think we'd have an easier time keeping this package fresh if we could drop some of those. noah 1. https://salsa.debian.org/chromium-team/chromium/-/blob/master/debian/patches/series 2. https://salsa.debian.org/chromium-team/chromium/-/tree/master/debian/patches/disable 3. https://salsa.debian.org/chromium-team/chromium/-/tree/master/debian/patches/system I'd also like to point out, that the ungoogled-chromium project has some overlap in goals with Debian and it'd possibly be interessing to join forces: https://github.com/ungoogled-software/ungoogled-chromium-debian (I have been running an ungoogled-chromium for a while (ca. a year ago?), however at that time their chrome wasn't extremely stable so I gave up again. Does anybody have experience using it recently?) *t
Bug#1001284: python-pysam: libhts-dev build dependency must be bumped to >= 1.14
Source: python-pysam Version: 0.18.0+ds-1~exp1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=python-pysam=amd64=0.18.0%2Bds-1~exp1=1638890599=0 ... samtools/bam_import.c.pysam.c: In function ‘import_fastq’: samtools/bam_import.c.pysam.c:182:35: error: ‘FASTQ_OPT_NAME2’ undeclared (first use in this function); did you mean ‘FASTQ_OPT_RNUM’? 182 | hts_set_opt(fp_in[i], FASTQ_OPT_NAME2, 1); | ^~~ ...
Processed: nbconvert is mistuned
Processing commands for cont...@bugs.debian.org: > forwarded 1001283 https://github.com/jupyter/nbconvert/issues/1685 Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: python3-mistune (<< 2) Set Bug forwarded-to-address to 'https://github.com/jupyter/nbconvert/issues/1685'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1001283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001283: python3-nbconvert: nbconvert Depends: python3-mistune (<< 2)
Package: python3-nbconvert
Version: 6.1.0-1
Severity: serious
Justification: FTBFS
Control: affects -1 src:mistune
setup.py for nbconvert declares the requirement
'mistune>=0.8.1,<2'
The upper bound is not enforecd in the debian packaging.
In this case it actually matters. mistune 2.0.0 has just been
uploaded, and nbconvert fails against it,
e.g. debci
https://ci.debian.net/data/autopkgtest/testing/amd64/n/nbconvert/17364189/log.gz
or using sphinx to build docs
e.g. rebuilding nbconvert:
debian/rules override_dh_sphinxdoc
make[1]: Entering directory '/home/drew/projects/python/build/nbconvert-6.1.0'
PYTHONPATH=. python3 -m sphinx -b html docs/source
debian/python-nbconvert-doc/usr/share/doc/python-nbconvert-doc/html
Running Sphinx v4.3.1
Configuration error:
There is a programmable error in your configuration file:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinx/config.py", line 329, in
eval_config_file
exec(code, namespace)
File "/projects/python/build/nbconvert-6.1.0/docs/source/conf.py", line 25,
in
exec(compile(f.read(), 'autogen_config.py', 'exec'), {})
File "autogen_config.py", line 11, in
File "/projects/python/build/nbconvert-6.1.0/nbconvert/__init__.py", line 4,
in
from .exporters import *
File
"/projects/python/build/nbconvert-6.1.0/nbconvert/exporters/__init__.py", line
3, in
from .html import HTMLExporter
File "/projects/python/build/nbconvert-6.1.0/nbconvert/exporters/html.py",
line 18, in
from nbconvert.filters.highlight import Highlight2HTML
File "/projects/python/build/nbconvert-6.1.0/nbconvert/filters/__init__.py",
line 6, in
from .markdown import *
File "/projects/python/build/nbconvert-6.1.0/nbconvert/filters/markdown.py",
line 13, in
from .markdown_mistune import markdown2html_mistune
File
"/projects/python/build/nbconvert-6.1.0/nbconvert/filters/markdown_mistune.py",
line 31, in
class MathBlockGrammar(mistune.BlockGrammar):
AttributeError: module 'mistune' has no attribute 'BlockGrammar'
make[1]: *** [debian/rules:26: override_dh_sphinxdoc] Error 2
So nbconvert FTBFS.
Marking Severity: serious for that reason.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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-nbconvert depends on:
ii python3 3.9.8-1
ii python3-bleach 4.1.0-1
ii python3-defusedxml 0.7.1-1
ii python3-entrypoints 0.3-9
ii python3-jinja2 3.0.1-2
ii python3-jupyter-core 4.9.1-1
ii python3-jupyterlab-pygments 0.1.2-7
ii python3-mistune 2.0.0-1
ii python3-nbclient 0.5.6-2
ii python3-nbformat 5.1.3-1
ii python3-pandocfilters1.5.0-1
ii python3-pygments 2.7.1+dfsg-2.1
ii python3-testpath 0.5.0+dfsg-1
ii python3-traitlets5.1.1-1
Versions of packages python3-nbconvert recommends:
ii pandoc 2.9.2.1-1+b2
ii python3-jupyter-client 7.1.0-1
Versions of packages python3-nbconvert suggests:
pn python-nbconvert-doc
ii texlive-fonts-recommended 2021.20211127-1
ii texlive-plain-generic 2021.20211127-1
ii texlive-xetex 2021.20211127-1
-- no debconf information
Processed: python3-nbconvert: nbconvert Depends: python3-mistune (<< 2)
Processing control commands: > affects -1 src:mistune Bug #1001283 [python3-nbconvert] python3-nbconvert: nbconvert Depends: python3-mistune (<< 2) Added indication that 1001283 affects src:mistune -- 1001283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001282: samtools: libhts-dev build dependency must be bumped to >= 1.14
Source: samtools Version: 1.14-1~exp1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=samtools=amd64=1.14-1~exp1=1638890648=0 ... bam_plcmd.c: In function ‘pileup_seq’: bam_plcmd.c:75:5: error: unknown type name ‘hts_base_mod_state’ 75 | hts_base_mod_state *m = p->cd.p; | ^~ ...
Bug#993505: marked as done (netgen-lvs FTBFS: configure: error: cannot find required auxiliary files: install-sh config.guess config.sub)
Your message dated Tue, 07 Dec 2021 17:04:11 +
with message-id
and subject line Bug#993505: fixed in netgen-lvs 1.5.133-1.1
has caused the Debian Bug report #993505,
regarding netgen-lvs FTBFS: configure: error: cannot find required auxiliary
files: install-sh config.guess config.sub
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.)
--
993505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netgen-lvs
Version: 1.5.133-1
Severity: serious
Tags: ftbfs
netgen-lvs fails to build from source. A build on amd64 ends as follows:
|dh_autoreconf
| autoreconf: warning: autoconf input should be named 'configure.ac', not
'configure.in'
| aclocal: warning: autoconf input should be named 'configure.ac', not
'configure.in'
| configure.in:9: warning: The macro `AC_CANONICAL_SYSTEM' is obsolete.
| configure.in:9: You should run autoupdate.
| ./lib/autoconf/general.m4:2081: AC_CANONICAL_SYSTEM is expanded from...
| configure.in:9: the top level
| configure.in:25: warning: The macro `AC_ISC_POSIX' is obsolete.
| configure.in:25: You should run autoupdate.
| ./lib/autoconf/specific.m4:550: AC_ISC_POSIX is expanded from...
| configure.in:25: the top level
| configure.in:149: warning: The macro `AC_HEADER_STDC' is obsolete.
| configure.in:149: You should run autoupdate.
| ./lib/autoconf/headers.m4:704: AC_HEADER_STDC is expanded from...
| configure.in:149: the top level
| configure.in:171: warning: The macro `AC_TRY_LINK' is obsolete.
| configure.in:171: You should run autoupdate.
| ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
| configure.in:171: the top level
| configure.in:184: warning: The macro `AC_TRY_LINK' is obsolete.
| configure.in:184: You should run autoupdate.
| ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from...
| configure.in:184: the top level
| configure.in:874: warning: $as_echo is obsolete; use AS_ECHO(["message"])
instead
| configure.in:1293: warning: AC_OUTPUT should be used without arguments.
| configure.in:1293: You should run autoupdate.
| configure.in:1293: warning: AC_C_BIGENDIAN should be used with
AC_CONFIG_HEADERS
|debian/rules override_dh_auto_configure
| make[1]: Entering directory '/<>'
| dh_auto_configure -- --libdir=\${prefix}/lib
| ./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 --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libdir=\${prefix}/lib
| configure: error: cannot find required auxiliary files: install-sh
config.guess config.sub
| dh_auto_configure: error: ./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 --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libdir=\${prefix}/lib
returned exit code 1
| make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:15: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Helmut
--- End Message ---
--- Begin Message ---
Source: netgen-lvs
Source-Version: 1.5.133-1.1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
netgen-lvs, 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 993...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated netgen-lvs package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 07 Nov 2021 20:50:30 +0200
Source: netgen-lvs
Architecture: source
Version: 1.5.133-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Electronics Team
Changed-By: Adrian Bunk
Closes: 993505
Changes:
netgen-lvs
Bug#1000792: gnuradio: unsatisfiable Build-Depends(-Arch) on s390x: libunwind-dev
Package: gnuradio Followup-For: Bug #1000792 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Control: tags -1 patch Hello, libunwind-dev also does not exist on riscv64. In Ubuntu, I've applied the attached patch to skip the libunwind-dev build-dependency on these two architectures, to not regress architecture support for gnuradio. I've confirmed the package builds without libunwind-dev. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru gnuradio-3.9.4.0/debian/control gnuradio-3.9.4.0/debian/control --- gnuradio-3.9.4.0/debian/control 2021-11-27 09:02:04.0 -0800 +++ gnuradio-3.9.4.0/debian/control 2021-12-07 07:26:17.0 -0800 @@ -35,7 +35,7 @@ libsoapysdr-dev, libthrift-dev (>= 0.13.0-5) [amd64 arm64 armel armhf i386], libuhd-dev (>= 4), - libunwind-dev, + libunwind-dev [!riscv64 !s390x], libusb-1.0-0-dev [!kfreebsd-any], libusb2-dev [kfreebsd-any], libvolk2-dev,
Processed: Re: Bug#1001009: Downloads external files on install
Processing control commands: > tags -1 - moreinfo + pending Bug #1001009 [dbab] Downloads external files on install Removed tag(s) moreinfo. Bug #1001009 [dbab] Downloads external files on install Added tag(s) pending. -- 1001009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001009: Downloads external files on install
Control: tags -1 - moreinfo + pending thanks This should fix it https://salsa.debian.org/debian/dbab/-/commit/4cd8db27cec918244a9fba3d698a7b0123c9f3f9 and the bug will be closed after a new release. On Tue, Dec 7, 2021 at 10:57 AM Andrey Rahmatullin wrote: > > On Sun, Dec 05, 2021 at 09:56:02AM -0500, Tong Sun wrote: > > Thanks Andrey, > > > > Two questions, > > > > By "moved to contrib", did you meant to change > > > > Section: net > > > > to > > > > Section: contrib > > > > in d/control? > Please read > https://www.debian.org/doc/debian-policy/ch-archive.html#archive-areas and > https://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections > > > Now, let's define what "package cannot function" actually means. If > > functions normally without this or similar unpackaged file, but the > > program is completely data driven, i.e., no ads sites from the list > > are blocked unless the list is there. > > > > So, strictly speaking, the package indeed cannot function without this > > or similar unpackaged file, right? And the solution is just above, > > right? > I don't know the current project consensus on this, if it exists. > If the software can only work with certain non-free files it should go > into contrib, if OTOH it can work with some user-provided files, or with > free files if those exist, it can stay in main. But downloading external > files in postinst is certainly not fit for main. > > -- > WBR, wRAR
Processed: Re: gnuradio: unsatisfiable Build-Depends(-Arch) on s390x: libunwind-dev
Processing control commands: > tags -1 patch Bug #1000792 [src:gnuradio] gnuradio: unsatisfiable Build-Depends(-Arch) on s390x: libunwind-dev Added tag(s) patch. -- 1000792: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998206: calendar: cronjob processes all users’ calendars as root, allowing information disclosure
> As
> I understand it, this is the POSIX way. Anyway, I'm going to prepare
> a
> patch.
I did some more testing and it seems this simple patch fixes the issue:
--- calendar.c 2021-12-07 17:53:16.044315761 +0100
+++ calendar.c 2021-12-07 08:59:20.293726904 +0100
@@ -190,6 +190,8 @@
case 0: /* child */
(void)setpgid(getpid(), getpid());
(void)setlocale(LC_ALL, "");
+ if (setgid(pw->pw_gid) != 0 ||
setuid(pw->pw_uid) != 0)
+ err(1, "unable to switch to
user %u group %u", pw->pw_uid, pw->pw_gid);
if (acstat) {
if (chdir(pw->pw_dir) ||
stat(calendarFile, )
!= 0 ||
Any comments?
@security team: Do you want me to prepare a fix for stable, too?
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De
Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Processed: Re: Bug#995769: dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1)
Processing control commands: > tags -1 help Bug #995769 [dbab] dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1) Added tag(s) help. -- 995769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995769 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995769: dbab: v1.5.7 package fail to upgrade from bullseye (1.5.01-1)
Control: tags -1 help thanks I tried but got problems after problems... On Sun, Nov 28, 2021 at 1:51 PM Boyuan Yang wrote: > > Hi, > > Getting package autoremoved from testing is not end-of-the-world -- once the > bug is fixed, it can get back to Debian Testing at any time. Meanwhile, the > previous bug is real and will need to be fixed sooner or later. > > I may get back to look into the bug later, bug I don't have enough time > recently. Feel free to find help from others, or I may get involved when I > have enough time. > > Thanks, > Boyuan Yang > > > 在 2021-11-28星期日的 11:35 -0500，Tong Sun写道： > > Hi Boyuan, please please help. > > > > -- Forwarded message - > > From: Tong Sun > > Date: Sun, Nov 28, 2021 at 11:33 AM > > Subject: Re: Bug#995769: dbab: v1.5.7 package fail to upgrade from > > bullseye (1.5.01-1) > > To: Boyuan Yang , <995...@bugs.debian.org> > > > > > > To Boyuan, or any mentors reading this issue. > > > > I've been trying to fix it myself, but all my previous attempts > > failed, because I don't understand what breaks and why, from the > > output of the package upgrade log. > > > > I've sent a help request to debian-mentors a few days ago, but nobody > > answers yet. > > > > My package is now marked for autoremoval from testing, with a wrong > > reason, and I don't know how to stop my package being autoremed from > > testing, and I got no answers/help on that either. > > > > Since I don't know how to fix it myself, and all my previous attempts > > failed, if nobody helps me by next weekend, I'll do the only thing > > that I know -- to change the severity of this bug to minor, because > > there is a simple solution to it as explained below. This will solve > > everything and win me the time it takes for me to do further > > investigation/testing. > > > > Really hope it won't be the case. > > Somebody help please. > > Thanks > > > > On Thu, Oct 7, 2021 at 9:31 PM Tong Sun wrote: > > > > > > On Tue, Oct 5, 2021 at 7:27 AM Boyuan Yang wrote: > > > > > > > Package dbab/1.5.7-1 has broken maintscript and cannot be properly > > > > upgraded > > > > from dbab/1.5.01-1 to dbab/1.5.7-1: > > > > > > Thanks for reporting. I'll try to fix it ASAP. > > > > > > In the meantime, for anyone who doesn't want to wait for the fix to be > > > published -- > > > do not do an upgrade -- remove the package completely, then do a fresh > > > install. > > > > > > thx >
Bug#962208: fix ftbfs with glibc 2.31
Control: tag -1 - bullseye On Thu, 4 Jun 2020 16:40:47 +0200 Matthias Klose wrote: fix ftbfs with glibc 2.31. patch at I cannot reproduce the FTBFS in bullseye (but in bookworm). Tagging accordingly. Andreas
Processed: Re: fix ftbfs with glibc 2.31
Processing control commands: > tag -1 - bullseye Bug #962208 [src:libtrace3] fix ftbfs with glibc 2.31 Bug #997242 [src:libtrace3] libtrace3: FTBFS: format_linux.c:1014:35: error: ‘SIOCGSTAMP’ undeclared (first use in this function); did you mean ‘SIOCGARP’? Removed tag(s) bullseye. Removed tag(s) bullseye. -- 962208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962208 997242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001009: Downloads external files on install
On Sun, Dec 05, 2021 at 09:56:02AM -0500, Tong Sun wrote: > Thanks Andrey, > > Two questions, > > By "moved to contrib", did you meant to change > > Section: net > > to > > Section: contrib > > in d/control? Please read https://www.debian.org/doc/debian-policy/ch-archive.html#archive-areas and https://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections > Now, let's define what "package cannot function" actually means. If > functions normally without this or similar unpackaged file, but the > program is completely data driven, i.e., no ads sites from the list > are blocked unless the list is there. > > So, strictly speaking, the package indeed cannot function without this > or similar unpackaged file, right? And the solution is just above, > right? I don't know the current project consensus on this, if it exists. If the software can only work with certain non-free files it should go into contrib, if OTOH it can work with some user-provided files, or with free files if those exist, it can stay in main. But downloading external files in postinst is certainly not fit for main. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1001276: ctfutils: library conflict on libctf.so.0 with libctf0
Control: reassign -1 binutils Control: retitle -1 binutils: Hijacks libctf library name on (k)FreeBSD On 7 Dec 2021, at 15:25, Jessica Clarke wrote: > > On 7 Dec 2021, at 15:09, Andreas Beckmann wrote: >> >> Package: ctfutils >> Version: 10.3~svn297264-2 >> Severity: serious >> >> Hi, >> >> there is a (potential) library conflict: >> >> ctfutils (src:ctfutils): /usr/lib/libctf.so.0 >> libctf0 (src:binutils): /usr/lib/$DEB_HOST_MULTIARCH/libctf.so.0 >> >> I don't know if the libraries could be used as replacements of each >> other, but if both packages are installed, only one of libraries will >> be used to resolve dependencies of other shared libraries or binaries. > > *sigh* What is the plan for building binutils on real FreeBSD? Because > that has a libctf (albeit, now at .2) in the base system that will > conflict. Is this just a GNU-written replacement we should disable in > binutils on kfreebsd-*? Presumably that’s what they do on FreeBSD… Regardless, this is binutils’s bug, it can’t just hijack libraries, especially those that are OS-provided system libraries like libctf. Jess
Bug#1001276: ctfutils: library conflict on libctf.so.0 with libctf0
On 7 Dec 2021, at 15:09, Andreas Beckmann wrote: > > Package: ctfutils > Version: 10.3~svn297264-2 > Severity: serious > > Hi, > > there is a (potential) library conflict: > > ctfutils (src:ctfutils): /usr/lib/libctf.so.0 > libctf0 (src:binutils): /usr/lib/$DEB_HOST_MULTIARCH/libctf.so.0 > > I don't know if the libraries could be used as replacements of each > other, but if both packages are installed, only one of libraries will > be used to resolve dependencies of other shared libraries or binaries. *sigh* What is the plan for building binutils on real FreeBSD? Because that has a libctf (albeit, now at .2) in the base system that will conflict. Is this just a GNU-written replacement we should disable in binutils on kfreebsd-*? Presumably that’s what they do on FreeBSD... Jess
Bug#1001276: ctfutils: library conflict on libctf.so.0 with libctf0
Package: ctfutils Version: 10.3~svn297264-2 Severity: serious Hi, there is a (potential) library conflict: ctfutils (src:ctfutils):/usr/lib/libctf.so.0 libctf0 (src:binutils): /usr/lib/$DEB_HOST_MULTIARCH/libctf.so.0 I don't know if the libraries could be used as replacements of each other, but if both packages are installed, only one of libraries will be used to resolve dependencies of other shared libraries or binaries. Andreas
Bug#1001273: gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Package: gcc-avr,gcc-sh-elf Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 1:5.4.0+Atmel3.6.2-2 Control: found -1 11.2.0-12+1 Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Preparing to unpack .../gcc-sh-elf_11.2.0-12+1_amd64.deb ... Unpacking gcc-sh-elf (11.2.0-12+1) ... dpkg: error processing archive /var/cache/apt/archives/gcc-sh-elf_11.2.0-12+1_amd64.deb (--unpack): trying to overwrite '/usr/lib/libcc1.so.0.0.0', which is also in package gcc-avr 1:5.4.0+Atmel3.6.2-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/gcc-sh-elf_11.2.0-12+1_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/libcc1.so /usr/lib/libcc1.so.0 /usr/lib/libcc1.so.0.0.0 But, maybe even worse, there is also libcc1-0 shipping /usr/lib//libcc1.so.0 /usr/lib//libcc1.so.0.0.0 This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see https://qa.debian.org/dose/file-overwrites.html gcc-avr=1:5.4.0+Atmel3.6.2-2_gcc-sh-elf=11.2.0-12+1.log.gz Description: application/gzip
Processed: gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so*
Processing control commands: > found -1 1:5.4.0+Atmel3.6.2-2 Bug #1001273 [gcc-avr,gcc-sh-elf] gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so* There is no source info for the package 'gcc-sh-elf' at version '1:5.4.0+Atmel3.6.2-2' with architecture '' Marked as found in versions gcc-avr/1:5.4.0+Atmel3.6.2-2. > found -1 11.2.0-12+1 Bug #1001273 [gcc-avr,gcc-sh-elf] gcc-avr,gcc-sh-elf: both ship /usr/lib/libcc1.so* There is no source info for the package 'gcc-avr' at version '11.2.0-12+1' with architecture '' Marked as found in versions gcc-sh-elf/1. -- 1001273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996640: marked as done (powertop FTBFS: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 07 Dec 2021 12:34:43 + with message-id and subject line Bug#996640: fixed in powertop 2.14-1 has caused the Debian Bug report #996640, regarding powertop FTBFS: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 996640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996640 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: powertop Version: 2.13-2 Severity: serious Tags: ftbfs powertop fails to build from source in unstable, because ncurses added format string annotations. A non-parallel build now ends as follows: | g++ -std=c++11 -DHAVE_CONFIG_H -I. -I.. -DLOCALEDIR=\"/usr/share/locale\" -I/usr/include/libnl3 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -I/usr/include/x86_64-linux-gnu -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wformat -Wshadow -fno-omit-frame-pointer -fstack-protector -I/usr/include/libnl3 -D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -I/usr/include/x86_64-linux-gnu -pthread -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o powertop-display.o `test -f 'display.cpp' || echo './'`display.cpp | display.cpp: In function ‘void show_tab(unsigned int)’: | display.cpp:128:26: error: format not a string literal and no format arguments [-Werror=format-security] | 128 | mvwprintw(bottom_line, 0,0, c); | | ~^ | cc1plus: some warnings being treated as errors | make[4]: *** [Makefile:1107: powertop-display.o] Error 1 | make[4]: Leaving directory '/<>/src' | make[3]: *** [Makefile:657: all] Error 2 | make[3]: Leaving directory '/<>/src' | make[2]: *** [Makefile:461: all-recursive] Error 1 | make[2]: Leaving directory '/<>' | make[1]: *** [Makefile:391: all] Error 2 | make[1]: Leaving directory '/<>' | dh_auto_build: error: make -j1 returned exit code 2 | make: *** [debian/rules:9: binary] Error 25 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Helmut --- End Message --- --- Begin Message --- Source: powertop Source-Version: 2.14-1 Done: Kan-Ru Chen (陳侃如) We believe that the bug you reported is fixed in the latest version of powertop, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kan-Ru Chen (陳侃如) (supplier of updated powertop package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 06 Dec 2021 00:48:34 +0900 Source: powertop Architecture: source Version: 2.14-1 Distribution: unstable Urgency: medium Maintainer: Kan-Ru Chen (陳侃如) Changed-By: Kan-Ru Chen (陳侃如) Closes: 996640 Changes: powertop (2.14-1) unstable; urgency=medium . [ Kan-Ru Chen ] * New upstream version 2.14 * Import patch to fix compatibility with ncurses 6.3 (Closes: #996640) * Import patches to fix autconf AX macros. * debian/powertop.install: Install powertop.service systemd unit from upstream. Checksums-Sha1: e666817da9acb551bc37de6fac063c208b245f5d 1996 powertop_2.14-1.dsc 3783086487352b5b51d4ca36d2c258dfbef6a60f 302578 powertop_2.14.orig.tar.gz f0e154b6c757cdf5592d5ae0c72a9d3904ca9384 21284 powertop_2.14-1.debian.tar.xz f35969131fa1ec0796e70f787d9207a2fc980a76 7542 powertop_2.14-1_amd64.buildinfo Checksums-Sha256: 905765bc494e3563bb76b907c6617236b71ed2fb316a729645ba2974ebac2206 1996 powertop_2.14-1.dsc 0e4cd0933a4f1fe04bfbf9d56efaabc841d9b04d391426f1a3469d6635a25f37 302578 powertop_2.14.orig.tar.gz af8c054d64280bd2a0d2ec0b96cba84329507c2371d2ed57b3c4e4410d15b204 21284 powertop_2.14-1.debian.tar.xz 9724f945d9d9956fc01266f4a2533a3d9e3729e8e9baed55484575193054aae1 7542 powertop_2.14-1_amd64.buildinfo Files: 2353a3f6c99f73e9d79b41f1f62cf7ae 1996 utils optional powertop_2.14-1.dsc 4a5fb8a23ea9fa6b50e4ee3d158965e1 302578 utils optional powertop_2.14.orig.tar.gz e3823eeb9c88fe70c5cf02693c4dfeeb 21284 utils optional powertop_2.14-1.debian.tar.xz 0e90e9b3d44dc2d072faba00e7e187a5 7542 utils optional powertop_2.14-1_amd64.buildinfo -BEGIN PGP SIGNATURE-
Processed: bug 984276 is forwarded to https://github.com/AcademySoftwareFoundation/OpenColorIO/pull/973
Processing commands for cont...@bugs.debian.org: > forwarded 984276 > https://github.com/AcademySoftwareFoundation/OpenColorIO/pull/973 Bug #984276 [src:opencolorio] opencolorio: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/AcademySoftwareFoundation/OpenColorIO/pull/973'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984276: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984276 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 997748 is forwarded to https://github.com/rpm-software-management/libcomps/commit/5eebd94a7ce855979eb014595256eee17ee6b359
Processing commands for cont...@bugs.debian.org: > forwarded 997748 > https://github.com/rpm-software-management/libcomps/commit/5eebd94a7ce855979eb014595256eee17ee6b359 Bug #997748 [src:libcomps] libcomps: FTBFS: There is a syntax error in your configuration file: Missing parentheses in call to 'print'. Did you mean print(os.environ['LD_LIBRARY_PATH'])? (conf.py, line 23) Set Bug forwarded-to-address to 'https://github.com/rpm-software-management/libcomps/commit/5eebd94a7ce855979eb014595256eee17ee6b359'. > thanks Stopping processing here. Please contact me if you need assistance. -- 997748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997748 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997657: marked as done (cgreen: FTBFS: Icon font not found for set: fas)
Your message dated Tue, 07 Dec 2021 10:35:44 + with message-id and subject line Bug#997657: fixed in ruby-prawn-icon 3.0.0-1.1 has caused the Debian Bug report #997657, regarding cgreen: FTBFS: Icon font not found for set: fas 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.) -- 997657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cgreen Version: 1.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/build' > [ 1%] asciidoctor-pdf cgreen-guide-en > cd /<>/build/doc && /usr/bin/asciidoctor-pdf -a toc -a > VERSION=1.3.0 -a docinfo -o cgreen-guide-en.pdf > /<>/doc/cgreen-guide-en.asciidoc > Icon font not found for set: fas > Use --trace for backtrace > make[4]: *** [doc/CMakeFiles/cgreen-guide-en-pdf.dir/build.make:77: > doc/cgreen-guide-en.pdf-pdf] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/cgreen_1.3.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: ruby-prawn-icon Source-Version: 3.0.0-1.1 Done: Daniel Leidert We believe that the bug you reported is fixed in the latest version of ruby-prawn-icon, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Leidert (supplier of updated ruby-prawn-icon 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, 07 Dec 2021 11:14:30 +0100 Source: ruby-prawn-icon Architecture: source Version: 3.0.0-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Extras Maintainers Changed-By: Daniel Leidert Closes: 997657 Changes: ruby-prawn-icon (3.0.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Use gem installation layout, so the font files can be found in the expected path (closes: #997657). * Enable tests and add ruby-pdf-inspector to build dependencies. Checksums-Sha1: 64e4f67223d3d291033de6804f8b55a88c80c156 2155 ruby-prawn-icon_3.0.0-1.1.dsc 0319992667b2041b8009be00de255ae6ca4729a6 3804 ruby-prawn-icon_3.0.0-1.1.debian.tar.xz 1498408356547a762f18b4e73f4e6595c220870f 9641 ruby-prawn-icon_3.0.0-1.1_amd64.buildinfo Checksums-Sha256: d36b21c58f8523e81440acba85ba017112772be3fd51cf8661fdd7bd0e00440e 2155 ruby-prawn-icon_3.0.0-1.1.dsc 8da420368204c8b6c15f5707a5182048467a5f09f58a65e3b1f9ce7452565dc4 3804 ruby-prawn-icon_3.0.0-1.1.debian.tar.xz cfa10dbee1a796be1e77400f088b5e046fcdab13e490551b7c26b7616ca3d643 9641 ruby-prawn-icon_3.0.0-1.1_amd64.buildinfo Files: 6c3bbaa348a93fb6a307e793996c0b85 2155 ruby optional ruby-prawn-icon_3.0.0-1.1.dsc 0b1d15c56e3d4fc1c008c9f04a3434e8 3804 ruby optional ruby-prawn-icon_3.0.0-1.1.debian.tar.xz cca10d0e9e70353ef9c8589d54a87042 9641 ruby optional ruby-prawn-icon_3.0.0-1.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGvNZsACgkQS80FZ8KW 0F0RmxAApuml+KqK8IptGDALphSNlS0MBrlexBn7DTEgf9+IT1c2qmlvpbTvUm3U H8SlOwShZVcQNwnwgR78OBI672DS3unx/pZCkFZ4kvZN1FkDrCsc/xebiPHWAUt8 EBum+AZvPup/SwNQVX4Z3hfHKCTMeX7QeEN65y8veHV2qJ7CuYVLzzAPO3fzYn9/ 1N0T8lTu/xzICJ9n/021Ib6gJ6ei7DbcOVislytIOxMenUfFcjwIn8Z6KEUdN617 lQngCKAizzj45jM3mvtUx68qHe8DZQnNg2K1kHjRZK9wboequY9j+rvSiyIRq6fc gq/vUix5sj+MxUXfbZ0BmaoV6/Lgslx+DLeOVzrRcDlF9P0hkSODO1dqI/3zkvv0 pf0n/wToFI6E0wxV/rkQWidm/gScKZnA19J/77yDeHoRN7yzeqHWCjSKSW4Zy+/P hqrwjiNhQmY5nd3EOyzwjKWKxtmhplVbq8m2VF8YQwSylsBYzoslZSMH3ePTo6zS
Processed: affects 997657, affects 997657
Processing commands for cont...@bugs.debian.org: > affects 997657 - cgreen Bug #997657 [ruby-prawn-icon] cgreen: FTBFS: Icon font not found for set: fas Removed indication that 997657 affects cgreen > affects 997657 + src:cgreen Bug #997657 [ruby-prawn-icon] cgreen: FTBFS: Icon font not found for set: fas Added indication that 997657 affects src:cgreen > thanks Stopping processing here. Please contact me if you need assistance. -- 997657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997657: NMU
Hi,
I've just uploaded an NMU to fix this issue. Please find attached the debdiff.
Please note that your Git repository is not in sync with the Debian archive. It
is missing version 3.0.0, this NMU applies to.
Regards, Daniel
--
Regards,
Daniel Leidert | https://www.wgdd.de/
GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D
GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78
https://www.fiverr.com/dleidert
https://www.patreon.com/join/dleidert
diff -Nru ruby-prawn-icon-3.0.0/debian/changelog ruby-prawn-icon-3.0.0/debian/changelog
--- ruby-prawn-icon-3.0.0/debian/changelog 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/changelog 2021-12-07 11:14:30.0 +0100
@@ -1,3 +1,12 @@
+ruby-prawn-icon (3.0.0-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use gem installation layout, so the font files can be found in the
+expected path (closes: #997657).
+ * Enable tests and add ruby-pdf-inspector to build dependencies.
+
+ -- Daniel Leidert Tue, 07 Dec 2021 11:14:30 +0100
+
ruby-prawn-icon (3.0.0-1) unstable; urgency=medium
* New upstream version
diff -Nru ruby-prawn-icon-3.0.0/debian/control ruby-prawn-icon-3.0.0/debian/control
--- ruby-prawn-icon-3.0.0/debian/control 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/control 2021-12-07 11:14:30.0 +0100
@@ -6,6 +6,7 @@
Build-Depends: debhelper-compat (= 13),
gem2deb,
rake,
+ ruby-pdf-inspector,
ruby-prawn (<< 3.0.0),
ruby-prawn (>= 1.1.0),
ruby-rspec
@@ -20,8 +21,8 @@
Package: ruby-prawn-icon
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
-Depends: ${ruby:Depends},
- ${misc:Depends}
+Depends: ${misc:Depends},
+ ${ruby:Depends}
Description: Provides icon fonts for PrawnPDF
Prawn::Icon provides various icon fonts including
FontAwesome, PaymentFont and Foundation Icons
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch
--- ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch 1970-01-01 01:00:00.0 +0100
+++ ruby-prawn-icon-3.0.0/debian/patches/0003-Remove-bundler-and-simplecov.patch 2021-12-07 11:14:30.0 +0100
@@ -0,0 +1,31 @@
+Author: Daniel Leidert
+Date: 2021-12-07
+Subject: Remove bundler and simplecov usage
+
+Forwarded: not-needed
+
+--- a/spec/spec_helper.rb
b/spec/spec_helper.rb
+@@ -5,11 +5,11 @@
+ # This is free software. Please see the LICENSE and COPYING files for details.
+ #
+ #
+-require 'simplecov'
+-SimpleCov.start
++#require 'simplecov'
++#SimpleCov.start
+
+-require "bundler"
+-Bundler.setup
++#require "bundler"
++#Bundler.setup
+
+ require "prawn/icon"
+ require 'pdf/inspector'
+@@ -22,4 +22,4 @@
+ RSpec.configure do |config|
+ config.include PDFHelper
+ config.include ParserHelper
+-end
+\ No newline at end of file
++end
diff -Nru ruby-prawn-icon-3.0.0/debian/patches/series ruby-prawn-icon-3.0.0/debian/patches/series
--- ruby-prawn-icon-3.0.0/debian/patches/series 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/patches/series 2021-12-07 11:14:30.0 +0100
@@ -1,2 +1,3 @@
0001-Clear-executable-bit-on-data-fonts-pf.patch
-0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+#0002-Access-data-files-from-usr-share-ruby-prawn-icon.patch
+0003-Remove-bundler-and-simplecov.patch
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install
--- ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-prawn-icon.install 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-data/fonts/[a-z]* /usr/share/ruby-prawn-icon/data/fonts/
diff -Nru ruby-prawn-icon-3.0.0/debian/ruby-tests.rake ruby-prawn-icon-3.0.0/debian/ruby-tests.rake
--- ruby-prawn-icon-3.0.0/debian/ruby-tests.rake 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/ruby-tests.rake 2021-12-07 11:14:30.0 +0100
@@ -1,4 +1,5 @@
-task default: %w[test]
+require 'gem2deb/rake/spectask'
-task :test do
+Gem2Deb::Rake::RSpecTask.new do |spec|
+ spec.pattern = './spec/**/*_spec.rb'
end
diff -Nru ruby-prawn-icon-3.0.0/debian/rules ruby-prawn-icon-3.0.0/debian/rules
--- ruby-prawn-icon-3.0.0/debian/rules 2021-10-10 20:37:56.0 +0200
+++ ruby-prawn-icon-3.0.0/debian/rules 2021-12-07 11:09:32.0 +0100
@@ -5,5 +5,7 @@
# Uncomment this to turn on verbose mode.
export DH_VERBOSE=1
+export DH_RUBY = --gem-install
+
%:
dh $@ --buildsystem=ruby --with ruby
signature.asc
Description: This is a digitally signed message part
Bug#1001242: weex FTBFS: dh_testroot: error: You must run this as root (or use fakeroot).
Hi! Sorry I thought that was required for all builds? Ludovic > dh_testroot > dh_testroot: error: You must run this as root (or use fakeroot). -- Ludovic Drolez. https://drolez.com/blog/ - Music and Tech Blog
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
Noah Meyerhans wrote: > The biggest difficulty, as far as I can tell from my look at Chromium from > several months ago, is that our patch set [1] needs a lot of attention with > every chromium release. And let me ask another silly question: where can we actually see a CI log for a failed build? buildd.d.o only features the latest successful one (for 93rd Chromium). signature.asc Description: PGP signature
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
Noah Meyerhans wrote: > On Sun, Dec 05, 2021 at 07:58:17PM +0300, Dmitry Alexandrov wrote: >> >> So what's happening with chromium in both sid and stable? I saw on >> >> d-release that it was removed from testing (#998676 and #998732), with a >> >> discussion about ending security support for it in stable. >> > >> > The problem really is lack of maintenance. In my opinion, chromium >> > deserves an active *team* to support it in Debian. <...> The security >> > team doesn't have the bandwidth to do it themselves, they need a team to >> > help them. >> >> Sorry for a silly question, but whatʼs so wrong with the build done by >> linuxmint.com [1], so Debian needs a whole team to duplicate their effort? >> Itʼs for Debian 10 (i. e. oldstable) as of now, but works fine at Sid in my >> (limited) experience. > > Well, you can start with the fact that the Mint chromium source packages > don't even include the chromium source, If the fact is that their ad-hoc downloader does not generate orig tarball, I fail to see much trouble here. They are using the same `chromium-browser-official` releases. > let alone the sources for all the other things they build (NodeJS, and more). Well, they actually do not build NodeJS, but use a blob from nodejs.org (just like Google does). Nothing good, of course, but I hope itʼs not the case that Chromium build fails when NodeJS is actually built from sources that are supposed to correspond to that blob? Or had nobody tried that? If the latter, why? Is there some policy, that mandates that preinstalled node(1) must be used? > One lesson we may take from Mint, though, is that it's not worth trying to > patch Chromium as much as we'd like. Anything that we can do to simplify the > Chromium packaging will help us keep the package up-to-date, which in turn > will help us keep our users safer. In my opinion, we should be pretty > aggressive about dropping as many of the Chromium patches as possible, even > if that means we link against bundled/vendored dependencies. Indeed. As a passer-by I really wonder why that path had been taken at all in the first place. If Chromium devs are into hard-pinning dependencies, they presumably have good reasons to do that. > Legal/licensing considerations are still important and I don't know if we > actually *can* ship builds based on the bundled stuff. I cannot imagine how it can be illegal for Debian what is legal for Google or Flathub in this case. Were there some prior discussions about that? signature.asc Description: PGP signature
Bug#984268: ogmtools: diff for NMU version 1:1.5-4.1
Thanks Adrian. On Tue, 9 Nov 2021 at 16:06, Adrian Bunk wrote: > Control: tags 984268 + patch > Control: tags 984268 + pending > > Dear maintainer, > > I've prepared an NMU for ogmtools (versioned as 1:1.5-4.1) and uploaded > it to DELAYED/15. Please feel free to tell me if I should cancel it. > > cu > Adrian > -- g. Marc
Processed: reassign 997657 to ruby-prawn-icon, affects 997657
Processing commands for cont...@bugs.debian.org: > reassign 997657 ruby-prawn-icon 3.0.0-1 Bug #997657 [src:cgreen] cgreen: FTBFS: Icon font not found for set: fas Bug reassigned from package 'src:cgreen' to 'ruby-prawn-icon'. No longer marked as found in versions cgreen/1.3.0-2. Ignoring request to alter fixed versions of bug #997657 to the same values previously set Bug #997657 [ruby-prawn-icon] cgreen: FTBFS: Icon font not found for set: fas Marked as found in versions ruby-prawn-icon/3.0.0-1. > affects 997657 + cgreen Bug #997657 [ruby-prawn-icon] cgreen: FTBFS: Icon font not found for set: fas Added indication that 997657 affects cgreen > thanks Stopping processing here. Please contact me if you need assistance. -- 997657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997657 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997657: Problem is in ruby-prawn-icon
Hi, the problem is actually in ruby-prawn-icon in the files /usr/lib/ruby/vendor_ruby/prawn/icon/font_data.rb and /usr/lib/ruby/vendor_ruby/prawn/icon/configuration.rb. In the first the path to the fonts relies on Icon.configuration.font_directory which is defined in the second and leads to the non-existent directory /usr/lib/ruby/data/fonts, whereas the fonts are actually in /usr/share/ruby-prawn-icon/data/fonts/. The quick fix might be to change to the gem installation layout. Otherwise the font_directory default must be adjusted. Reassigning to ruby-prawn-icon. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part
