Bug#965600: marked as done (jack-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Fri, 30 Dec 2022 07:35:09 + with message-id and subject line Bug#965600: fixed in jack-tools 20131226-1.1 has caused the Debian Bug report #965600, regarding jack-tools: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: jack-tools Version: 20131226-1 Severity: normal Usertags: compat-5-6-removal Hi, The package jack-tools uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: jack-tools Source-Version: 20131226-1.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of jack-tools, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated jack-tools 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, 12 Dec 2022 03:22:18 +0800 Source: jack-tools Architecture: source Version: 20131226-1.1 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965600 Changes: jack-tools (20131226-1.1) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper version to 10. (Closes: #965600) Checksums-Sha1: 980e7cc704164d18c85066dc3e4681135ec851a3 2272 jack-tools_20131226-1.1.dsc 4da62ff2056f867591caa1035384b39cd0d90440 6564 jack-tools_20131226-1.1.debian.tar.xz 66618be830dbfe52cc2447334d7e5c546f292529 10330 jack-tools_20131226-1.1_source.buildinfo Checksums-Sha256: fe6e0d91efe32ba2f71de2f7a6e3bdada7870b62e3106136128a61609b809a43 2272 jack-tools_20131226-1.1.dsc ae8234b1024e799b8dbb2affa9ab5c28bfdb81a42fd9d9ce938501f5c89a5c84 6564 jack-tools_20131226-1.1.debian.tar.xz 7862b1d8aa9972f81549db8dde7be8c50312ec15ed9b133c32d85fc1d27c17a5 10330 jack-tools_20131226-1.1_source.buildinfo Files: 11ae29ce052c8c13d6dbc751143a324c 2272 sound optional jack-tools_20131226-1.1.dsc a7ccf8a7b4d2fa1383337b9b4a1894a2 6564 sound optional jack-tools_20131226-1.1.debian.tar.xz e6de85b46ee4e30660a4a2e52f3f5a5b 10330 sound optional jack-tools_20131226-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOhWggTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiG2/EADSHj8kXcWdYZ5vKQj94kDoWd8nqOLz ATcbSpOBb+KBWF76c2mc76QHuBvSyi86+LEbhD5Ubpn4qm1AW453yz/uo5VPqh+N Ps4U/1Xmshji+lqLnez1osQqyXV4wXb/s+kjzAJc45ZzQMaqP9vXw+GyeBq4rC85 uYUYa206Gl93R52VQW7WhamFljXr07xffkpcAr2d/TRlyu8g8rB4txDqnnwYRZi9 r701k03HHMuvhsfFMhssNqKrq9feJROFXIhNp8qjUg/J4AsebquWXpZdBrGcP9EQ 88huGtrK4ZPv/FPBchVee4L/G6nrU1x3WOtjOKFGE5l9jx/OowLr/VI6IFghab0V 2fxQSZJup1NfzijIK4OFz9+VIQfK6rnTBEZvs3okoPpTDQGIeTf+AYYCso3EIskt acZbtnqdqDe5Tewx3Oce+N4b+HsC30o2nPCjbMGlhm+3+WV8BsjkCPnsBdJpcje8 Pvlo031sw3q6AmX6rVTJeXNvKRrup/SliLAQK7GRDvD0qJW8N3K3U36bRqadFf2p 7AOTqw3pwPUKU9NjmOteh4C54fsdjK9ek5AdSCoWo85hgLWJuH8P3gnMIuW/pdrJ
Processed: found 1027153 in 1.4.3-0.1
Processing commands for cont...@bugs.debian.org: > found 1027153 1.4.3-0.1 Bug #1027153 [src:ruby-rails-html-sanitizer] ruby-rails-html-sanitizer: CVE-2022-23517 CVE-2022-23518 CVE-2022-23519 CVE-2022-23520 Marked as found in versions ruby-rails-html-sanitizer/1.4.3-0.1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#919058: its-tool: crashes when freeing bad xmlDocs
Hi Lars, On Thu, 25 Apr 2019 02:03:01 +0200 Lars Skovlund wrote: So far, there is no response on either the RedHat bug or on the respective GitHub issues. There is a new itstool version available, but it only includes the fixes that we've had available as long as this bug has been open. itstool in Debian is newer now that at the time of this discussion. From reading, it's not clear if you expect this bug to be closed now. Could you please check if this issue still exists in unstable and bookworm? Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1027305: python3-pyglossary: crashes with ModuleNotFoundError
Package: python3-pyglossary Version: 3.2.1-1.1 Severity: grave Justification: renders package unusable Hi, pyglossary is crashing with a simple invocation: $ pyglossary Traceback (most recent call last): File "/usr/lib/python3/dist-packages/pyglossary/plugins/babylon_bgl/bgl_reader.py", line 30, in GzipFile = __import__( ModuleNotFoundError: No module named 'pyglossary.plugin_lib.py310' If things didn't work well with BGL files, install Python 3.5 to 3.7 and try again Traceback (most recent call last): File "/usr/share/pyglossary/pyglossary.pyw", line 215, in log.setVerbosity(args.verbosity) AttributeError: 'RootLogger' object has no attribute 'setVerbosity' - exit 1 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-pyglossary depends on: ii python3 3.10.6-3+b1 Versions of packages python3-pyglossary recommends: ii gir1.2-gtk-3.03.24.35-3 ii python3-gi3.42.2-3 ii python3-gi-cairo 3.42.2-3 ii python3-html5lib 1.1-3 ii python3-icu 2.10.2-1+b2 ii python3-jinja23.0.3-2 ii python3-lxml 4.9.1-1+b2 ii python3-lzo 1.14-1+b2 python3-pyglossary suggests no packages. Regards, -- Raul Benencia
Bug#1005899: mplayer: should not release with bookworm
On 2022-12-30 01:48:56 +0100, Lorenzo wrote: > Hi Sebastian, > > Could you please clarify if this package should be maintained inside the > Debian-Multimedia Team or outside? I.e. an uploader or a new maintainer? Whatever the new maintainer prefers. The multimedia team always is happy to welcome new contributors. Cheers -- Sebastian Ramacher
Bug#1005899: mplayer: should not release with bookworm
Hi Sebastian, Could you please clarify if this package should be maintained inside the Debian-Multimedia Team or outside? I.e. an uploader or a new maintainer? Regards, Lorenzo On Wed, 16 Feb 2022 23:25:00 +0100 Sebastian Ramacher wrote: > Source: mplayer > Version: 2:1.4+ds1-3 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > Tags: sid bookworm > > Let's stop pretending that mplayer is maintained. The upstream mailing > list infrastructure is gone and development has been minimal over the > last couple of months and years. So I think we should not include > mplayer in bookworm. mpv is a worthy replacement for mplayer. > > Cheers > -- > Sebastian Ramacher
Processed: Re: Bug#1027176: u-boot-amlogic: broken non-EFI boot on odroid-c2
Processing control commands: > severity 1027176 serious Bug #1027176 [u-boot-amlogic] u-boot-amlogic: broken non-EFI boot on odroid-c2 Severity set to 'serious' from 'important' -- 1027176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027297: u-boot: guruplug/sheevaplug: FDT and ATAGS support not compiled in
Package: u-boot Version: 2022.04+dfsg-2 Severity: serious Control: fixed -1 2022.10+dfsg-2 X-Debbugs-Cc: vagr...@debian.org, m...@drkrebs.de, t...@cyrius.com, i...@debian.org At least two people have reported the same issue on sheevaplug and guruplug failing to boot with a message "FDT and ATAGS support not compiled in". I suspect this was fixed in 2022.10-rc5 upstream with this commit: https://source.denx.de/u-boot/u-boot/-/commit/a8a0c55f9d1cd0f4618288b25f63857373015391 arm: kirkwood: Add CONFIG_SUPPORT_PASSING_ATAGS Both tests confirm it working again with u-boot 2022.10+dfsg-2 and 2023.01~rc4+dfsg-1 from Debian. live well, vagrant signature.asc Description: PGP signature
Processed: u-boot: guruplug/sheevaplug: FDT and ATAGS support not compiled in
Processing control commands: > fixed -1 2022.10+dfsg-2 Bug #1027297 [u-boot] u-boot: guruplug/sheevaplug: FDT and ATAGS support not compiled in Marked as fixed in versions u-boot/2022.10+dfsg-2. -- 1027297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027297 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027296: ruby3.0: do not release with bookworm
Source: ruby3.0 Version: 3.0.4-8 Severity: serious X-Debbugs-Cc: sramac...@debian.org Following the transition to ruby3.1 as only supported ruby version, let's get ruby3.0 removed from bookworm. Cheers -- Sebastian Ramacher
Bug#1010608: openldap: Flaky test test063-delta-multiprovider
On Wed, Dec 28, 2022 at 10:32:30PM +0100, Paul Gevers wrote: Then not running the script at all is an improvement over the current situation. Flaky tests are bad. Until a better solution is found, how about skipping the test? Not ideal, but yeah, probably an improvement over shipping a flaky test in stable. Thanks for the reminder, I'll try to upload it soon.
Processed: your mail
Processing commands for cont...@bugs.debian.org: > severity 1027085 normal Bug #1027085 [src:zfs-linux] linux-image-5.10.0-20-amd64: failed to load zfs modules - after automatic update Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1026469 marked as pending in metakernel
Processing control commands: > tag -1 pending Bug #1026469 [src:metakernel] metakernel: FTBFS: FAILED metakernel/magics/tests/test_parallel_magic.py::test_parallel_magic Ignoring request to alter tags of bug #1026469 to the same tags previously set -- 1026469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026469: marked as pending in metakernel
Control: tag -1 pending Hello, Bug #1026469 in metakernel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/metakernel/-/commit/b2bbc242906139cf45929fa27104626143624043 skip flaky parallel_magic test Closes: #1026469 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026469
Bug#1003674: marked as done (php-sabre-vobject: (autopkgtest) needs update for php8.1: ValueError: Epoch doesn't fit in a PHP integer)
Your message dated Thu, 29 Dec 2022 22:19:51 + with message-id and subject line Bug#1003674: fixed in php-sabre-vobject 2.1.7-6.1 has caused the Debian Bug report #1003674, regarding php-sabre-vobject: (autopkgtest) needs update for php8.1: ValueError: Epoch doesn't fit in a PHP integer 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.) -- 1003674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: php-sabre-vobject Version: 2.1.7-6 Severity: serious X-Debbugs-CC: debian...@lists.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:php-defaults Dear maintainer(s), We are in the transition of replacing php7.4 with php8.1 [0]. With a recent upload of php-defaults the autopkgtest of php-sabre-vobject fails in testing when that autopkgtest is run with the binary packages of php-defaults from unstable on armhf and i386 (both 32 bits architectures). It passes when run with only packages from testing. In tabular form: passfail php-defaults from testing92 php-sabre-vobject from testing2.1.7-6 versioned deps from testingfrom unstable 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 php-defaults to testing [1]. https://www.php.net/ChangeLog-8.php list the changes since 7.4 and may help to identify what needs to be updated. php-commom added a whole set of versioned Breaks to make sure the right packages from current unstable are pulled in during testing. If the issue is caused by a missing breaks, please reasign this bug to php-common. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/976811 [1] https://qa.debian.org/excuses.php?package=php-defaults https://ci.debian.net/data/autopkgtest/testing/armhf/p/php-sabre-vobject/18255681/log.gz PHPUnit 9.5.11 by Sebastian Bergmann and contributors. Warning: Your XML configuration validates against a deprecated schema. Suggestion:Migrate your XML configuration using "--migrate-configuration"! ... 63 / 553 ( 11%) ... 126 / 553 ( 22%) ...R... 189 / 553 ( 34%) .R..E.. 252 / 553 ( 45%) ..RR..RR..R 315 / 553 ( 56%) RRR 378 / 553 ( 68%) RRR 441 / 553 ( 79%) RRR 504 / 553 ( 91%) RRR.. 553 / 553 (100%) Time: 00:00.087, Memory: 12.00 MB There was 1 error: 1) Sabre\VObject\RecurrenceIteratorTest::testYearly ValueError: Epoch doesn't fit in a PHP integer /usr/share/php/Sabre/VObject/RecurrenceIterator.php:687 /tmp/autopkgtest-lxc.20ggb02o/downtmp/build.CCT/src/tests/Sabre/VObject/RecurrenceIteratorTest.php:973 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: php-sabre-vobject Source-Version: 2.1.7-6.1 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of php-sabre-vobject, 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 1003...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated php-sabre-vobject package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Dec 2022 21:16:10 +0100 Source: php-sabre-vobject Architecture: source Version: 2.1.7-6.1 Distribution: unstable Urgency: medium Maintainer: Debian PHP PEAR Maintainers Changed-By: Anton Gladky Closes:
Bug#1026469: marked as pending in metakernel
Control: tag -1 pending Hello, Bug #1026469 in metakernel reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/metakernel/-/commit/b2bbc242906139cf45929fa27104626143624043 skip flaky parallel_magic test Closes: #1026469 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026469
Processed: Bug#1026469 marked as pending in metakernel
Processing control commands: > tag -1 pending Bug #1026469 [src:metakernel] metakernel: FTBFS: FAILED metakernel/magics/tests/test_parallel_magic.py::test_parallel_magic Added tag(s) pending. -- 1026469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Actually fixed earlier
Processing commands for cont...@bugs.debian.org:
> fixed 1017650 1.1.2-1
Bug #1017650 {Done: Ben Westover }
[src:rust-zram-generator] rust-zram-generator: BD-Uninstallable
Marked as fixed in versions rust-zram-generator/1.1.2-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1017650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}
On Thu, 29 Dec 2022, Scott Kitterman wrote:
On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote:
Control: tags -1 help
Hi,
I wonder whether someone might suggest a fix for
==
FAIL: test_schema_compatibility_type_mismatch
(avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_t
ype_mismatch)
--
Traceback (most recent call last):
File
"/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test
/test_compatibility.py", line 1039, in
test_schema_compatibility_type_mismatch self.assertIn(message,
result.messages)
AssertionError: 'reader type: null not compatible with writer type: int' not
found in {'reader type: SchemaType.NULL not compatible with writer type:
SchemaType.INT'}
--
Ran 421 tests in 8.358s
FAILED (failures=1, skipped=3)
Otherwise I will probably exclude Python3.11 from the build to fix this bug.
That's not an actual solution. If you close the bug on this basis it will
hide the issue and make it appear we are more ready to move to Python 3.11 as
the default (and probably only) Python version for Bookworm.
I didn't look at the actual code. Typically when something comes up Null is
means that something was not found. I would look at the code where SchemaType
is determined to see how it might come up with no SchemaType.
It looks like this has already been fixed upstream (although with a
non-obvious commit message):
https://github.com/apache/avro/commit/432f073c3cfb8ac7edb2793b797ab855c5a978dd
I just uploaded a fix.
Scott T.
Bug#1026605: marked as pending in python-avro
Control: tag -1 pending Hello, Bug #1026605 in python-avro reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-avro/-/commit/febc8ecea3d0c6ff366d5fe1a4d1f0dbc90bc2b9 Cherry-pick upstream fix for Python 3.11 tests (Closes: #1026605) (this message was generated automatically) -- Greetings https://bugs.debian.org/1026605
Processed: Bug#1026605 marked as pending in python-avro
Processing control commands:
> tag -1 pending
Bug #1026605 [src:python-avro] python-avro: FTBFS: AssertionError: 'reader
type: null not compatible with writer type: int' not found in {'reader type:
SchemaType.NULL not compatible with writer type: SchemaType.INT'}
Added tag(s) pending.
--
1026605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1017650: marked as done (rust-zram-generator: BD-Uninstallable)
Your message dated Thu, 29 Dec 2022 21:56:53 + with message-id and subject line Fixed in 1.1.2-2 has caused the Debian Bug report #1017650, regarding rust-zram-generator: BD-Uninstallable 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.) -- 1017650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-zram-generator Version: 0.3.2-1 Severity: serious Tags: ftbfs Justification: fails to build from source X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/package.php?p=rust-zram-generator=sid rust-zram-generator build-depends on missing: - librust-rust-ini-0.16+default-dev:amd64 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Control: fixed -1 1.1.2-2 OpenPGP_signature Description: PGP signature --- End Message ---
Bug#1027020: marked as done (davmail-server: fails to install: insserv: script davmail-server: service davmail already provided!)
Your message dated Thu, 29 Dec 2022 21:49:24 + with message-id and subject line Bug#1027020: fixed in davmail 6.0.1.3390-4 has caused the Debian Bug report #1027020, regarding davmail-server: fails to install: insserv: script davmail-server: service davmail already provided! 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.) -- 1027020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: davmail-server Version: 6.0.1.3390-3 Severity: serious Justification: fails to install -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 When trying to update davmail / install davmail-server I get: Setting up davmail-server (6.0.1.3390-3) ... insserv: script davmail-server: service davmail already provided! update-rc.d: error: no runlevel symlinks to modify, aborting! dpkg: error processing package davmail-server (--configure): installed davmail-server package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of davmail: davmail depends on davmail-server; however: Package davmail-server is not configured yet. dpkg: error processing package davmail (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: davmail-server davmail The reason seems to be that /etc/init.d/davmail is still around (and has "Provides. davmail") Cheers, gregor - -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'stable-security'), (500, 'oldoldstable'), (500, 'experimental'), (500, 'testing'), (500, 'stable'), (500, 'oldstable') merged-usr: no Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages davmail-server depends on: ii adduser 3.130 ii default-jre-headless [java9-runtime-headless] 2:1.17-73 hi init-system-helpers 1.64 ii libcommons-codec-java 1.15-1 ii libcommons-logging-java 1.2-3 ii libhtmlcleaner-java 2.26-1 ii libhttpclient-java4.5.14-1 ii libjackrabbit-java2.20.3-1 ii libjcifs-java 1.3.19-2 ii libjettison-java 1.5.1-1 ii libjna-java 5.12.1-1 ii liblog4j1.2-java 1.2.17-11 ii libmail-java 1.6.5-1 ii libslf4j-java 1.7.32-1 ii libstax2-api-java 4.1-1 ii libwoodstox-java 1:6.2.1-1 ii logrotate 3.21.0-1 ii openjdk-11-jre-headless [java9-runtime-headless] 11.0.17+8-2 ii openjdk-17-jre-headless [java9-runtime-headless] 17.0.5+8-2 ii sysvinit-utils [lsb-base] 3.06-2 davmail-server recommends no packages. davmail-server suggests no packages. - -- no debconf information -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmOpnRRfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbJJw/9GRQOGLvrW0NtOjU61Aa3MaPb6bkmPNsVUNwuIS71uRwU2hnnD40cWmvt R7/hQk8K2Csou/jYCLJRqh0o4PdKuF1weMJOKXF+IxxdmYAf9dmnAZCrOs8Y/wyx jrxMP9z6EO8/FBwxtqnBfEhszWILqRRu6Q6SUEg2+tZbiSnUTqGZ5EOPy/O4XMPx MRA5ZPmsaBtk5qAnSr4l6cONi3elExhlwwObD+cJOc4BQk/ckadHicCsaDdgL5dH Ow9dP2OHA7ZQ5CX6bq+Y7CBfMs6pLi6wi9UnQf6vNB7+B+vFqK1PLyPBwZ34TRid DX9QmjxKLmXsS7NgOPQJ6EY+EAcoTt3AMeR/jgn0Cg1PlySL5/AAjYjbKqucwpoz kLCm7MIq3hU2Qkf8s4tC9d5+5eNUb4nC88AHJphtl9jdvui6Panf3j6BkJEW7C1k 4oiM7742iF4R6Rp4VNJUyyGi0dGC9MFc1+EdXIUdopw3WPTcnCa4QZvz04X/RYEn ez7jRd9+7X/XPHaaCeHQ7jIZ6NDQez0H0VY43W/uJjNj0scJvTF0YVj16aCamo6y qZ31yIJVLg5BRi+bodlcpYuqvKbh/WphpYPjg+jF449cc0dAwYwUndB+P8Rrsrsk ZMkqModeqlDQWr7D3EbGARydFR5S9kEUC597DYguVK/Wpz0H+dQ= =+WAm -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: davmail Source-Version: 6.0.1.3390-4 Done: Alexandre Rossi We believe that the bug you reported is
Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}
On Thursday, December 29, 2022 4:13:20 PM EST Andreas Tille wrote:
> Control: tags -1 help
>
> Hi,
>
> I wonder whether someone might suggest a fix for
>
>
> ==
> FAIL: test_schema_compatibility_type_mismatch
> (avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_t
> ype_mismatch)
> --
> Traceback (most recent call last):
> File
> "/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test
> /test_compatibility.py", line 1039, in
> test_schema_compatibility_type_mismatch self.assertIn(message,
> result.messages)
> AssertionError: 'reader type: null not compatible with writer type: int' not
> found in {'reader type: SchemaType.NULL not compatible with writer type:
> SchemaType.INT'}
>
> --
> Ran 421 tests in 8.358s
>
> FAILED (failures=1, skipped=3)
>
>
> Otherwise I will probably exclude Python3.11 from the build to fix this bug.
That's not an actual solution. If you close the bug on this basis it will
hide the issue and make it appear we are more ready to move to Python 3.11 as
the default (and probably only) Python version for Bookworm.
I didn't look at the actual code. Typically when something comes up Null is
means that something was not found. I would look at the code where SchemaType
is determined to see how it might come up with no SchemaType.
Scott K
signature.asc
Description: This is a digitally signed message part.
Processed: Re: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'
Processing control commands:
> tags -1 help
Bug #1026605 [src:python-avro] python-avro: FTBFS: AssertionError: 'reader
type: null not compatible with writer type: int' not found in {'reader type:
SchemaType.NULL not compatible with writer type: SchemaType.INT'}
Added tag(s) help.
--
1026605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1026605: python-avro: FTBFS: AssertionError: 'reader type: null not compatible with writer type: int' not found in {'reader type: SchemaType.NULL not compatible with writer type: SchemaType.INT'}
Control: tags -1 help
Hi,
I wonder whether someone might suggest a fix for
==
FAIL: test_schema_compatibility_type_mismatch
(avro.test.test_compatibility.TestCompatibility.test_schema_compatibility_type_mismatch)
--
Traceback (most recent call last):
File
"/build/python-avro-1.11.1+dfsg/.pybuild/cpython3_3.11_avro/build/avro/test/test_compatibility.py",
line 1039, in test_schema_compatibility_type_mismatch
self.assertIn(message, result.messages)
AssertionError: 'reader type: null not compatible with writer type: int' not
found in {'reader type: SchemaType.NULL not compatible with writer type:
SchemaType.INT'}
--
Ran 421 tests in 8.358s
FAILED (failures=1, skipped=3)
Otherwise I will probably exclude Python3.11 from the build to fix this bug.
Kind regards
Andreas.
--
http://fam-tille.de
Bug#1026619: marked as done (python-fire: FTBFS: AttributeError: module 'asyncio' has no attribute 'coroutine')
Your message dated Thu, 29 Dec 2022 20:38:37 + with message-id and subject line Bug#1026619: fixed in python-fire 0.5.0-1 has caused the Debian Bug report #1026619, regarding python-fire: FTBFS: AttributeError: module 'asyncio' has no attribute 'coroutine' 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.) -- 1026619: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026619 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-fire Version: 0.4.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build -Spybuild --with python3 >dh_update_autotools_config -O-Spybuild >dh_autoreconf -O-Spybuild >dh_auto_configure -O-Spybuild > I: pybuild base:240: python3.11 setup.py config > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'license-file' will not be supported in future versions. > Please use the underscore name 'license_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: > SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use > license_files instead. > warnings.warn(msg, warning_class) > running config > I: pybuild base:240: python3.10 setup.py config > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'license-file' will not be supported in future versions. > Please use the underscore name 'license_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: > SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use > license_files instead. > warnings.warn(msg, warning_class) > running config >dh_auto_build -O-Spybuild > I: pybuild base:240: /usr/bin/python3.11 setup.py build > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'license-file' will not be supported in future versions. > Please use the underscore name 'license_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: > SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use > license_files instead. > warnings.warn(msg, warning_class) > running build > running build_py > creating /<>/.pybuild/cpython3_3.11/build/fire > copying fire/__init__.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/formatting.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/parser.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/docstrings_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/core.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/value_types.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/inspectutils.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/__main__.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/parser_fuzz_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/main_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/formatting_windows.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/trace.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/parser_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/formatting_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/decorators.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/helptext.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/decorators_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components_bin.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/fire_import_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/completion_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/core_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/inspectutils_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/interact.py -> /<>/.pybuild/cpython3_3.11/build/fire > copying fire/test_components_py3.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/fire_test.py -> > /<>/.pybuild/cpython3_3.11/build/fire > copying fire/custom_descriptions_test.py -> >
Bug#1026539: theano: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Hi Rebecca, given that there were some uploads to experimental I'm wondering what might be the best strategy to fix the bug - either in the version in unstable or in 1.1.2 and upload this to unstable. Kind regards Andreas. -- http://fam-tille.de
Processed: RC Bug #1026634: Forwarded upstream
Processing commands for cont...@bugs.debian.org:
> forwarded 1026634 https://github.com/aio-libs/yarl/issues/803
Bug #1026634 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Set Bug forwarded-to-address to 'https://github.com/aio-libs/yarl/issues/803'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026634: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026634
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'
Processing control commands: > tag -1 moreinfo Bug #1027112 [src:bazel-bootstrap] bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' Added tag(s) moreinfo. -- 1027112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027112 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027112: bazel-bootstrap: /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()'
Control: tag -1 moreinfo Hi Sebastian and thanks for the bug report. On 12/27/22 18:15, Sebastian Ramacher wrote: Source: bazel-bootstrap Version: 4.2.3+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=bazel-bootstrap=amd64=4.2.3%2Bds-1%2Bb1=1671977092=0 ␛[1A␛[K␛[31m␛[1mERROR: ␛[0m/<>/src/main/cpp/BUILD:91:10: Linking src/main/cpp/client failed: (Exit 1): gcc failed: error executing command (cd /tmp/bazel_hloBSNSM/out/execroot/io_bazel && \ exec env - \ CCACHE_DISABLE=1 \ CCACHE_TEMPDIR=/<>/debian/ccachetmp \ LC_ALL=C \ PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games \ PWD=/proc/self/cwd \ /usr/bin/gcc @bazel-out/k8-dbg/bin/src/main/cpp/client-2.params) Execution platform: //:default_host_platform ␛[32m[111 / 127]␛[0m 3 actions running //src/main/java/com/google/devtools/build/lib/bazel:BazelServer; 5s local JavacBootstrap .../devtools/build/singlejar/libbootstrap.jar; 2s local JavacBootstrap .../devtools/build/buildjar/libstarlark-deps.jar; 2s local ␛[1A␛[K ␛[1A␛[K ␛[1A␛[K ␛[1A␛[K/usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/grpcpp/completion_queue.h:119: error: undefined reference to 'absl::debian3::Mutex::~Mutex()' /usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 'absl::debian3::Mutex::Lock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' /usr/include/absl/synchronization/mutex.h:533: error: undefined reference to 'absl::debian3::Mutex::Lock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' /usr/include/absl/synchronization/mutex.h:550: error: undefined reference to 'absl::debian3::Mutex::Unlock()' collect2: error: ld returned 1 exit status ␛[32m[111 / 127]␛[0m 3 actions running I'm talking to László about this because it seems to be connected to the ongoing grpc transition. Hopefully we can figure something out soon! -Olek
Processed: found 1014539 in 3.1-8
Processing commands for cont...@bugs.debian.org: > found 1014539 3.1-8 Bug #1014539 [src:squirrel3] squirrel3: CVE-2022-30292 Marked as found in versions squirrel3/3.1-8. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 1014539 in 3.1-7
Processing commands for cont...@bugs.debian.org: > found 1014539 3.1-7 Bug #1014539 [src:squirrel3] squirrel3: CVE-2022-30292 Marked as found in versions squirrel3/3.1-7. > thanks Stopping processing here. Please contact me if you need assistance. -- 1014539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014539 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027137: marked as done (kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas")
Your message dated Thu, 29 Dec 2022 19:23:03 + with message-id and subject line Bug#1027137: fixed in kicad 6.0.10+dfsg-2 has caused the Debian Bug report #1027137, regarding kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas" 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.) -- 1027137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kicad Version: 6.0.10+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=kicad=amd64=6.0.10%2Bdfsg-1%2Bb2=1672197224=0 [ 31%] Building CXX object common/CMakeFiles/gal.dir/painter.cpp.o cd /<>/debian/build/common && /usr/bin/c++ -DGLM_FORCE_CTOR_INIT -DHAVE_STDINT_H -DKICAD_CONFIG_DIR=kicad -DKICAD_SCRIPTING_WXPYTHON -DKICAD_SPICE -DKICAD_USE_EGL -DKICAD_USE_OCC -DWXUSINGDLL -DWX_COMPATIBILITY -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -I/<>/include -I/<>/common/. -I/<>/common/./dialogs -I/<>/common/./widgets -I/<>/common/./dialog_about -I/<>/bitmaps_png -I/<>/3d-viewer -I/<>/pcbnew -I/<>/debian/build -I/<>/scripting -I/<>/thirdparty/nlohmann_json -I/<>/thirdparty/compoundfilereader -I/<>/debian/build/common -I/<>/libs/kimath/include -I/<>/thirdparty/clipper -I/<>/thirdparty/other_math -I/<>/thirdparty/rtree -I/<>/libs/kiplatform/include -isystem /<>/thirdparty/pybind11/include -isystem /<>/thirdparty/glew/include -isystem /usr/include/cairo -isystem /usr/include/pixman-1 -isystem /usr/include/opencascade -isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem /usr/include/wx-3.2 -isystem /usr/include/python3.10 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG -pthread -Wall -Wsuggest-override -Wduplicated-branches -Wduplicated-cond -Werror=vla -Wimplicit-fallthrough=5 -Werror=return-type -Wshadow -Wsign-compare -Wmissing-field-initializers -Wempty-body -Wreorder -Wmismatched-tags -Wno-psabi -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -std=c++14 -MD -MT common/CMakeFiles/gal.dir/painter.cpp.o -MF CMakeFiles/gal.dir/painter.cpp.o.d -o CMakeFiles/gal.dir/painter.cpp.o -c /<>/common/painter.cpp In file included from /<>/include/gal/opengl/shader.h:32, from /<>/include/gal/opengl/opengl_gal.h:35, from /<>/common/draw_panel_gal.cpp:42: /<>/include/gal/opengl/kiglew.h:47:14: error: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas" 47 | #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas" | ^ Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: kicad Source-Version: 6.0.10+dfsg-2 Done: Carsten Schoenert We believe that the bug you reported is fixed in the latest version of kicad, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Carsten Schoenert (supplier of updated kicad package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Dec 2022 18:43:50 +0100 Source: kicad Architecture: source Version: 6.0.10+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: Carsten Schoenert Closes: 1027137 Changes: kicad (6.0.10+dfsg-2) unstable; urgency=medium . * [5a3af46] Revert "d/rules: Turn option KICAD_USE_EGL on" wxWidgets 3.2 in Debian has now no EGL canvas support compiled in any more. More to the reasoning about the switch back can be found on https://bugs.debian.org/1020640 https://bugs.debian.org/1024147 (Closes: #1027137) Checksums-Sha1: e15b8b141f1a7c2b03d307b2513b95a3d1fc1f4a 4261 kicad_6.0.10+dfsg-2.dsc 4adc67042f651369b75ef3487d161d937db97cc7 59528 kicad_6.0.10+dfsg-2.debian.tar.xz 067c537b4643cf4d0d7d2ab48b8de2c1a9b14624 27383 kicad_6.0.10+dfsg-2_amd64.buildinfo Checksums-Sha256:
Processed: matplotlib: axes3d.quiver() fails when providing args to Line3DCollection
Processing control commands: > forwarded -1 https://github.com/matplotlib/matplotlib/issues/24842 Bug #1027285 [src:matplotlib] matplotlib: axes3d.quiver() fails when providing args to Line3DCollection Set Bug forwarded-to-address to 'https://github.com/matplotlib/matplotlib/issues/24842'. > block 1027170 by -1 Bug #1027170 [src:dolfin] dolfin: autopkgtest fail with matplotlib/3.6.2 1027170 was not blocked by any bugs. 1027170 was not blocking any bugs. Added blocking bug(s) of 1027170: 1027285 -- 1027170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027170 1027285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027285 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027285: matplotlib: axes3d.quiver() fails when providing args to Line3DCollection
Source: matplotlib Version: 3.6.2-3 Severity: serious Justification: debci Control: forwarded -1 https://github.com/matplotlib/matplotlib/issues/24842 Control: block 1027170 by -1 mplot3d.axes3d.quiver() accepts boths args and kwargs in its function definition. Both args (any remaining after the first 6 values) and kwargs are passed onwards to art3d.Line3DCollection at matplotlib/lib/mpl_toolkits/mplot3d/axes3d.py Line 2655 in 3393a4f: linec = art3d.Line3DCollection(lines, *args[argi:], **kwargs) But arguments for Line3DCollection are passed directly to LineCollection. In matplotlib PR#23076 appearing in matplotlib 3.6, LineCollection was changed so that it no longer accepts positional args. All excess arguments must now be provided in kwargs. This means axes3d.quiver() now fails with matplotlib 3.6. An example failure is in 3D plot tests from dolfin. The python backtrace running* this demo script (on a debian system) looks like Traceback (most recent call last): File "/projects/fenics/build/tests/dolfin/demo-python/undocumented/curl-curl/demo_curl-curl.py", line 172, in plot(J) File "/usr/lib/petsc/lib/python3/dist-packages/dolfin/common/plotting.py", line 440, in plot return _plot_matplotlib(object, mesh, kwargs) File "/usr/lib/petsc/lib/python3/dist-packages/dolfin/common/plotting.py", line 306, in _plot_matplotlib return mplot_function(ax, obj, **kwargs) File "/usr/lib/petsc/lib/python3/dist-packages/dolfin/common/plotting.py", line 218, in mplot_function return ax.quiver3D(*args, length=length, **kwargs) File "/usr/lib/python3/dist-packages/matplotlib/__init__.py", line 1427, in inner return func(ax, *map(sanitize_sequence, args), **kwargs) File "/usr/lib/python3/dist-packages/mpl_toolkits/mplot3d/axes3d.py", line 2567, in quiver linec = art3d.Line3DCollection(lines, *args[argi:], **kwargs) TypeError: LineCollection.__init__() takes 2 positional arguments but 3 were given The TypeError occurs because of the use of args, which, to reiterate, was removed in matplotlib 3.6 PR#23076. I gather that any options which were previously provided to axes3d.quiver and intended for use in Line3DCollection must now be provided in kwargs instead. quiver should no longer use args at all at l.2655. * Note, to run that dolfin demo to reproduce the error, dolfin/common/plotting.py also needed updating for matplotlib 3.6 near l.279: -ax = plt.gca(projection='3d') +ax = plt.axes(projection='3d') This patch will be applied to dolfin to close Bug#1027170. For matplotlib itself, I propose simply removing the use of args in axes3d.py l.2655: - linec = art3d.Line3DCollection(lines, *args[argi:], **kwargs) + linec = art3d.Line3DCollection(lines, **kwargs)
Bug#1017218: ruby-parallel: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity
Hi,
On Sun, 14 Aug 2022 09:20:57 +0200 Lucas Nussbaum wrote:
Source: ruby-parallel
Version: 1.22.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> # ./spec/spec_helper.rb:9:in `block (2 levels) in '
>
> Finished in 1 minute 44.28 seconds (files took 0.10294 seconds to load)
> 152 examples, 1 failure, 4 pending
>
> Failed examples:
>
> rspec './spec/parallel_spec.rb[1:10:30]' # Parallel.each does not call the finish hook when a worker fails with ractors
>
> /usr/bin/ruby3.0 -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.0" failed. Exiting.
> dh_auto_install: error: dh_ruby --install
/<>/debian/ruby-parallel returned exit code 1
> make: *** [debian/rules:7: binary] Error 25
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
> E: Build killed with signal TERM after 150 minutes of inactivity
While trying to find out which test was the potential culprit of this
issue (I guess something kept running instead of being killed/closed), I
ran into multiple different failures depending on my retry attempt (see
some below). So, it seems these tests are particularly sensitive to the
load of the system (I regularly hit timeouts). I think it's best to
disable the build test (and potentially also the autopkgtest, albeit I
haven't seen that fail very often yet).
Paul
PS, I tried the attached patch, but that seems to have pushed some times
out of reasonable limits as I was getting very different errors.
E.g. currently on reproducible-builds.org:
https://tests.reproducible-builds.org/debian/logs/bookworm/amd64/ruby-parallel_1.22.1-1.build2.log.gz
Failures:
1) Parallel.in_processes kills the processes when the main process
gets killed through ctrl+c
Failure/Error:
time_taken do
result = execute_start_and_kill "PROCESS", 0
result.should_not include "FINISHED"
end.should be <= 3
expected: <= 3
got:3.4196298122406006
# ./spec/parallel_spec.rb:103:in `block (3 levels) in (required)>'
# ./spec/spec_helper.rb:9:in `block (2 levels) in '
2) Parallel.in_processes kills the processes when the main process
gets killed through a custom interrupt
Failure/Error:
lambda {
t = Thread.new { ruby("spec/cases/parallel_start_and_kill.rb
#{command} 2>&1 && echo 'FINISHED'") }
sleep 1.5
kill_process_with_name('spec/cases/parallel_start_and_kill.rb', signal)
sleep 1
}.should change { `ps`.split("\n").size }.by amount
expected ``ps`.split("\n").size` to have changed by 0, but was
changed by 19
# ./spec/parallel_spec.rb:24:in `execute_start_and_kill'
# ./spec/parallel_spec.rb:111:in `block (4 levels) in (required)>'
# ./spec/parallel_spec.rb:11:in `time_taken'
# ./spec/parallel_spec.rb:110:in `block (3 levels) in (required)>'
# ./spec/spec_helper.rb:9:in `block (2 levels) in '
3) Parallel.in_processes kills the threads when the main process gets
killed through ctrl+c
Failure/Error:
lambda {
t = Thread.new { ruby("spec/cases/parallel_start_and_kill.rb
#{command} 2>&1 && echo 'FINISHED'") }
sleep 1.5
kill_process_with_name('spec/cases/parallel_start_and_kill.rb', signal)
sleep 1
}.should change { `ps`.split("\n").size }.by amount
expected ``ps`.split("\n").size` to have changed by 0, but was
changed by -20
# ./spec/parallel_spec.rb:24:in `execute_start_and_kill'
# ./spec/parallel_spec.rb:117:in `block (4 levels) in (required)>'
# ./spec/parallel_spec.rb:11:in `time_taken'
# ./spec/parallel_spec.rb:116:in `block (3 levels) in (required)>'
# ./spec/spec_helper.rb:9:in `block (2 levels) in '
4) Parallel.in_processes does not kill processes when the main
process gets sent an interrupt besides the custom interrupt
Failure/Error:
lambda {
t = Thread.new { ruby("spec/cases/parallel_start_and_kill.rb
#{command} 2>&1 && echo 'FINISHED'") }
sleep 1.5
kill_process_with_name('spec/cases/parallel_start_and_kill.rb', signal)
sleep 1
}.should change { `ps`.split("\n").size }.by amount
expected ``ps`.split("\n").size` to have changed by 4, but was
changed by -18
# ./spec/parallel_spec.rb:24:in `execute_start_and_kill'
# ./spec/parallel_spec.rb:124:in `block (4 levels) in (required)>'
# ./spec/parallel_spec.rb:11:in `time_taken'
# ./spec/parallel_spec.rb:123:in `block (3 levels) in (required)>'
#
Bug#999178: marked as done (libuninum: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 19:05:47 + with message-id and subject line Bug#999178: fixed in libuninum 2.7-1.2 has caused the Debian Bug report #999178, regarding libuninum: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999178: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999178 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libuninum Version: 2.7-1.1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: libuninum Source-Version: 2.7-1.2 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of libuninum, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated libuninum 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, 12 Dec 2022 17:56:29 +0800 Source: libuninum Architecture: source Version: 2.7-1.2 Distribution: unstable Urgency: low Maintainer: Bartosz Fenski Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965695 999178 Changes: libuninum (2.7-1.2) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper compat to 12 (Closes: #965695) * debian/rules: use dh. (Closes: #999178) * Port to DebSrc3.0 (quilt) format. * Add autopkgtest Checksums-Sha1: 8829a5d6bbe49c701fc2005c349624125859 1900 libuninum_2.7-1.2.dsc 593751d6d9f621b8b3fdfe25d8f18d8593f2b758 2992 libuninum_2.7-1.2.debian.tar.xz 796d31a466efff5536a6602472e5e9b60f526eea 6862 libuninum_2.7-1.2_source.buildinfo Checksums-Sha256: bb9790980f6ca93b7154400c0a274d3c7a91f8f4be7a8b505c856763b48a9e1e 1900 libuninum_2.7-1.2.dsc 2b86096dbaee3e8a19b70ef3e0f05ff049fa8e99295e923fb6c5af18431120c6 2992 libuninum_2.7-1.2.debian.tar.xz 4d2dfe3f8f15da44888f643cb950194cf1d955d2b9dd1d8159fb72f328ef283f 6862 libuninum_2.7-1.2_source.buildinfo Files: a639e6b259c63c542015e77283e1d529 1900 libs optional libuninum_2.7-1.2.dsc 48651ddfa6887f43b57e470ad29a45ca 2992 libs optional libuninum_2.7-1.2.debian.tar.xz 2d7a6b29fbd1b9cbe340c17d985fcefe 6862 libs optional libuninum_2.7-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgpcQTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiN8XD/sFp2Oj+9XNJoyb0YpNZ+uMo9m5X2w/ nI1MGHXd9afFyV9EjmpLR6VRPKfTRBEc/iukgatGX0acNFDwLG+EMLB1cRInKBLK 5fHtdBnTJjv8ehn+LqYkXnTGV7lN9Yrfc/Sop/pGKyPOh0rQXU12gLq54DrhNuDU h3xInFhwvbOGQtC+U265OUH30X7q13Vw8Dxq6ZhMLGYhtMHm80cWICnsiEhpDuY4 fffWgYm7603FJErc69DMZqQtDWsVyi9/O+ooRSocscvBIHML5qkyMS3BtAiaI2XA czWCqWwNK64lG981+EkeKILeY1daD9SiwFgPzI6dspcbIyIO4DIBbPtXHR/6z7gv KOv5uK2iJAzSkk/78ej/7Ypr9pPt0unSe7+KdhgYAp7Eqhok6aOLpdpSVoam23UF +BixAnpUql1sAqbK48WdRn/BSmSB+h79GNkrLZ1IlpiM8gcZi3DhqAyUvdkEVSv8 +aoA0/REEp7sSnBNtLijrhZXW/hU3cNZxLovixxQVhvRcOl6yNECTZxL/vB6k9iC dlCnxtA0LSuj8yEtgLsOxfreQhEHc6JUPJ9K2hZNpUcenOyP0ndrjn6ISDx0byLQ q6MmPlujzTNc65b3VHjMdQOYZCGqcjBudXDEoG6Al611cwa7CuGnVHVLgcbfcYJT Rvs8STNXKGg71w== =wIA0 -END PGP SIGNATURE End Message ---
Bug#999110: marked as done (tcd-utils: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 19:06:51 + with message-id and subject line Bug#999110: fixed in tcd-utils 20061127-2.1 has caused the Debian Bug report #999110, regarding tcd-utils: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcd-utils Version: 20061127-2 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: tcd-utils Source-Version: 20061127-2.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of tcd-utils, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated tcd-utils 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, 13 Dec 2022 08:10:54 +0800 Source: tcd-utils Architecture: source Version: 20061127-2.1 Distribution: unstable Urgency: low Maintainer: Peter S Galbraith Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965835 999110 Changes: tcd-utils (20061127-2.1) unstable; urgency=low . * Non-maintainer upload. * Use DebSrc3.0 (quilt) format. * Bump debhelper compat to 12 (Closes: #965835) * debian/rules: Use dh (Closes: #999110) Checksums-Sha1: 19e305a45d83340b29d7b2e94d24c0dddbbd0078 1751 tcd-utils_20061127-2.1.dsc d1db19bbebc29968412ad27d12204421d72da9de 2980 tcd-utils_20061127-2.1.debian.tar.xz 2280baf801805aa982b9a6372f992e1d071b9501 6824 tcd-utils_20061127-2.1_source.buildinfo Checksums-Sha256: 8cd869aa990442826e69f2018405106a4029cbbc33a2b6f538e1e35630f8eeb8 1751 tcd-utils_20061127-2.1.dsc e78e120e1548d6d5a24c403d9ac8bcb7bf152ff1a15c2a5d271926020264bd75 2980 tcd-utils_20061127-2.1.debian.tar.xz 62877b109b5bfbdf7c7ae3945d15c4efccf0c201fc11b541ccbdeadf7c005811 6824 tcd-utils_20061127-2.1_source.buildinfo Files: 785904b970b28a924e316180aa9e08e1 1751 science optional tcd-utils_20061127-2.1.dsc fd3f887d72c61ef5eaae83ed37ce6128 2980 science optional tcd-utils_20061127-2.1.debian.tar.xz 1a4c25f49a8ded45393c835aa51960ab 6824 science optional tcd-utils_20061127-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgpTETHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiC8kEACPOVCVyM3KcC/LsA82szr+aEabXfPn yfcXVtCCCiDaH+Z2skXhG96c/XZ4T0xfXRRVSb3eVMyaUDbLgnpLmCC999ZZXyOb vpo10JdZQaZN0T0S/QKSM7CKZ+77zGKgibZXErS1S+cIe58JjHpOzxAqLAkwzJgx O/DtZFyXoBWqrr0lrmTTZO2Y9veIGpfNnR2esEvZ1CVexDscWnzGsfc8MPbgQajC TKU6LzErSUI/0wjZG74kRhAzDj/SQW6bLHVyT6/6n+lX3SaBtt6Opcj7tbBdlLZd j3OVAkJM9E3Ui3jtv08Jwd8pbfyw68Kqo3NHePjnn7uTXOr7iywfC4ssDYi5++bF 8gbsFU4xkDvWxeibHttdFukBGKKZ/onM9z3ePNhEl7Sa3jQDSxTLO6wDL9+8Pu9n k1EigxGrE2S/dgmrzVmAC1Zw30ZGM4vi0DvAUPqqy0Hv6rhuZ012AR3vf5uQpvAE /hjhTlUDecmyegJ2GYayw1+HvxK0gpuNj6ChqLqFjndeani8/X5qCPtzpw8+Td39 pgIpGgStbCAA/2f4BnYBCA3cJE8t3Ybdh1qyvb6hUoEf7pgy+1HgLu31wq1eKxOW vTQ+UJ4nNct8x8nmrx/awBVxOahbxwn4mWgrIZ0GuhcqrN9UbO7WnsvLgKwM7E6u Nm2n5zdCX+03Iw== =O3gA -END PGP SIGNATURE End Message ---
Bug#965861: marked as done (vcheck: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 19:07:39 + with message-id and subject line Bug#965861: fixed in vcheck 1.2.1-7.2 has caused the Debian Bug report #965861, regarding vcheck: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965861 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vcheck Version: 1.2.1-7.1 Severity: normal Usertags: compat-5-6-removal Hi, The package vcheck uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: vcheck Source-Version: 1.2.1-7.2 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of vcheck, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated vcheck 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, 13 Dec 2022 08:01:53 +0800 Source: vcheck Architecture: source Version: 1.2.1-7.2 Distribution: unstable Urgency: low Maintainer: Dario Minnucci Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965861 Changes: vcheck (1.2.1-7.2) unstable; urgency=low . * Non-maintainer upload. * Bimp debhelper compat to 12. (Closes: #965861) Checksums-Sha1: fd1ef7fc5dc510fc67bc12c3aa35b7df84c3ebe7 1885 vcheck_1.2.1-7.2.dsc 0d376d0a7e6aeffc80ce701f386d4aa2a063b6bd 4324 vcheck_1.2.1-7.2.debian.tar.xz e1078765f68b118ada237a0c8404647384de0f68 7656 vcheck_1.2.1-7.2_source.buildinfo Checksums-Sha256: 793fee6cf0f5ef704bbc6316b617699ea270fdf902bef3a9a99748f58c378afa 1885 vcheck_1.2.1-7.2.dsc cd212580e343d33163776e9f7c87eb46d949be76b7f59b44dae5bdb02e02df8b 4324 vcheck_1.2.1-7.2.debian.tar.xz 4c65391fa3f9963b003beb12feb4760824a7e82e92da5c546cd4322cd5c8b5bc 7656 vcheck_1.2.1-7.2_source.buildinfo Files: 9eba041359e7a39ca7470aa608f16764 1885 utils optional vcheck_1.2.1-7.2.dsc c8b6dd796a8dc70be9b242c055f52a38 4324 utils optional vcheck_1.2.1-7.2.debian.tar.xz 5ed53a61e2252c6298e424f35f86c2f5 7656 utils optional vcheck_1.2.1-7.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgpl0THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiOjGD/4xC65tRkYc/jFM8wGTO0Y3eB/lhPXU iOMWhjMFWBHOoFJoS987uAn3AkHIbp4g5tfRVb/m1QSb46VXDz5nbWq7OcYVl89Z oMATJxg+WOdMDdlhUvXWms/0UmjXRVZNxiDkD0z+TQt2GIJ7R47/TRZ6lr1keKAF 9r/MMaqT/qoZwEy5SmWwLu3+XsII4cmLpuoFoF36py2C0c6Abz01rv0TrxWbY/+n A1hg2iH0rlj+B7hmeb4/d8an7YtE0SCwmtYZbvJgWhWAIDv1o5c15SvaFXQDkiXw qf2Tt90bMcZDDUzRaWEQx6zhAC7rQYNd3kQ0nBjUPnMYXSsSbKee4vqaxx0I0Z/5 XD7syW4zC9S2948A+rRvBx0ZSXk+NSfsEo4zqBqeZMMKvoU1XH8xBVihqWeJr6pm 448V4AGN0R5NPqsAk95ErcpugPs3IggzHTYErIviYThVT5H77kt7LqROnELffMRa VbkzDu9oJdBPFTo6xHjCAbLSuSJa33sKyEq57xte1Ld6e+G7A0bOwKXzssB3Tc9K /dOxcBMWUE7/rcATHCBe4KBRU+9+cL4E/hoHYMM3rallhavrvfun1FP87rwYX7mQ ofCn8caRoBICKJSylRLvmNKOAnp1madO70XZHfFG+tc+rbQAtCe8gSso5VSQxfnk UFDlF1z5hacaCg== =bjoX -END PGP SIGNATURE End Message ---
Bug#965835: marked as done (tcd-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 19:06:51 + with message-id and subject line Bug#965835: fixed in tcd-utils 20061127-2.1 has caused the Debian Bug report #965835, regarding tcd-utils: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tcd-utils Version: 20061127-2 Severity: normal Usertags: compat-5-6-removal Hi, The package tcd-utils uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: tcd-utils Source-Version: 20061127-2.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of tcd-utils, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated tcd-utils 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, 13 Dec 2022 08:10:54 +0800 Source: tcd-utils Architecture: source Version: 20061127-2.1 Distribution: unstable Urgency: low Maintainer: Peter S Galbraith Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965835 999110 Changes: tcd-utils (20061127-2.1) unstable; urgency=low . * Non-maintainer upload. * Use DebSrc3.0 (quilt) format. * Bump debhelper compat to 12 (Closes: #965835) * debian/rules: Use dh (Closes: #999110) Checksums-Sha1: 19e305a45d83340b29d7b2e94d24c0dddbbd0078 1751 tcd-utils_20061127-2.1.dsc d1db19bbebc29968412ad27d12204421d72da9de 2980 tcd-utils_20061127-2.1.debian.tar.xz 2280baf801805aa982b9a6372f992e1d071b9501 6824 tcd-utils_20061127-2.1_source.buildinfo Checksums-Sha256: 8cd869aa990442826e69f2018405106a4029cbbc33a2b6f538e1e35630f8eeb8 1751 tcd-utils_20061127-2.1.dsc e78e120e1548d6d5a24c403d9ac8bcb7bf152ff1a15c2a5d271926020264bd75 2980 tcd-utils_20061127-2.1.debian.tar.xz 62877b109b5bfbdf7c7ae3945d15c4efccf0c201fc11b541ccbdeadf7c005811 6824 tcd-utils_20061127-2.1_source.buildinfo Files: 785904b970b28a924e316180aa9e08e1 1751 science optional tcd-utils_20061127-2.1.dsc fd3f887d72c61ef5eaae83ed37ce6128 2980 science optional tcd-utils_20061127-2.1.debian.tar.xz 1a4c25f49a8ded45393c835aa51960ab 6824 science optional tcd-utils_20061127-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgpTETHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiC8kEACPOVCVyM3KcC/LsA82szr+aEabXfPn yfcXVtCCCiDaH+Z2skXhG96c/XZ4T0xfXRRVSb3eVMyaUDbLgnpLmCC999ZZXyOb vpo10JdZQaZN0T0S/QKSM7CKZ+77zGKgibZXErS1S+cIe58JjHpOzxAqLAkwzJgx O/DtZFyXoBWqrr0lrmTTZO2Y9veIGpfNnR2esEvZ1CVexDscWnzGsfc8MPbgQajC TKU6LzErSUI/0wjZG74kRhAzDj/SQW6bLHVyT6/6n+lX3SaBtt6Opcj7tbBdlLZd j3OVAkJM9E3Ui3jtv08Jwd8pbfyw68Kqo3NHePjnn7uTXOr7iywfC4ssDYi5++bF 8gbsFU4xkDvWxeibHttdFukBGKKZ/onM9z3ePNhEl7Sa3jQDSxTLO6wDL9+8Pu9n k1EigxGrE2S/dgmrzVmAC1Zw30ZGM4vi0DvAUPqqy0Hv6rhuZ012AR3vf5uQpvAE /hjhTlUDecmyegJ2GYayw1+HvxK0gpuNj6ChqLqFjndeani8/X5qCPtzpw8+Td39 pgIpGgStbCAA/2f4BnYBCA3cJE8t3Ybdh1qyvb6hUoEf7pgy+1HgLu31wq1eKxOW
Bug#1022312: marked as done (ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, '==').strip.should == "Progress: |==|")
Your message dated Thu, 29 Dec 2022 20:07:32 +0100 with message-id <5b902d0c-45f2-bc5b-edc2-a3998e793...@debian.org> and subject line Re: ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, '==').strip.should == "Progress: |==|" has caused the Debian Bug report #1022312, regarding ruby-parallel: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, '==').strip.should == "Progress: |==|" 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.) -- 1022312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-parallel Version: 1.22.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: `TITLE=true ruby spec/cases/progress.rb 2>&1`.sub(/=+/, > '==').strip.should == "Progress: |==|" > > expected: "Progress: |==|" > got: "Ignoring debug-1.4.0 because its extensions are not built. > Try: gem pristine debug --version 1.4.0\n...2.1.0 because its extensions are > not built. Try: gem pristine rbs --version 2.1.0\n\nProgress: |==|" (using ==) > Diff: > @@ -1,3 +1,6 @@ > +Ignoring debug-1.4.0 because its extensions are not built. Try: gem > pristine debug --version 1.4.0 > +Ignoring rbs-2.1.0 because its extensions are not built. Try: gem > pristine rbs --version 2.1.0 > + > Progress: |==| > # ./spec/parallel_spec.rb:681:in `block (3 levels) in ' > # ./spec/spec_helper.rb:9:in `block (2 levels) in ' > > Finished in 1 minute 18 seconds (files took 0.11327 seconds to load) > 152 examples, 34 failures, 4 pending > > Failed examples: > > rspec './spec/parallel_spec.rb[1:5:10]' # Parallel.map does not queue new > work when one fails in threads > rspec './spec/parallel_spec.rb[1:5:11]' # Parallel.map does not queue new > work when one raises Break in threads > rspec './spec/parallel_spec.rb[1:5:12]' # Parallel.map stops all workers when > a start hook fails with threads > rspec './spec/parallel_spec.rb[1:5:13]' # Parallel.map does not add new work > when a finish hook fails with threads > rspec './spec/parallel_spec.rb[1:5:14]' # Parallel.map does not call the > finish hook when a worker fails with threads > rspec './spec/parallel_spec.rb[1:5:15]' # Parallel.map does not call the > finish hook when a worker raises Break in threads > rspec './spec/parallel_spec.rb[1:5:16]' # Parallel.map does not call the > finish hook when a start hook fails with threads > rspec './spec/parallel_spec.rb[1:5:18]' # Parallel.map sets > Parallel.worker_number with 4 threads > rspec './spec/parallel_spec.rb[1:5:21]' # Parallel.map does not queue new > work when one fails in processes > rspec './spec/parallel_spec.rb[1:5:22]' # Parallel.map does not queue new > work when one raises Break in processes > rspec './spec/parallel_spec.rb[1:5:23]' # Parallel.map stops all workers when > a start hook fails with processes > rspec './spec/parallel_spec.rb[1:5:24]' # Parallel.map does not add new work > when a finish hook fails with processes > rspec './spec/parallel_spec.rb[1:5:25]' # Parallel.map does not call the > finish hook when a worker fails with processes > rspec './spec/parallel_spec.rb[1:5:26]' # Parallel.map does not call the > finish hook when a worker raises Break in processes > rspec './spec/parallel_spec.rb[1:5:27]' # Parallel.map does not call the > finish hook when a start hook fails with processes > rspec './spec/parallel_spec.rb[1:5:29]' # Parallel.map sets > Parallel.worker_number with 4 processes > rspec './spec/parallel_spec.rb[1:5:32]' # Parallel.map does not queue new > work when one fails in ractors > rspec './spec/parallel_spec.rb[1:5:33]' # Parallel.map does not queue new > work when one raises Break in ractors > rspec './spec/parallel_spec.rb[1:5:34]' # Parallel.map stops all workers when > a start hook fails with ractors > rspec './spec/parallel_spec.rb[1:5:35]' # Parallel.map does not add new work > when a finish hook fails with ractors > rspec './spec/parallel_spec.rb[1:5:36]' # Parallel.map does not call the > finish hook when a worker fails with ractors > rspec './spec/parallel_spec.rb[1:5:37]' # Parallel.map does not call the > finish hook when a worker raises Break in ractors > rspec
Bug#965695: marked as done (libuninum: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 19:05:47 + with message-id and subject line Bug#965695: fixed in libuninum 2.7-1.2 has caused the Debian Bug report #965695, regarding libuninum: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libuninum Version: 2.7-1.1 Severity: normal Usertags: compat-5-6-removal Hi, The package libuninum uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: libuninum Source-Version: 2.7-1.2 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of libuninum, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated libuninum 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, 12 Dec 2022 17:56:29 +0800 Source: libuninum Architecture: source Version: 2.7-1.2 Distribution: unstable Urgency: low Maintainer: Bartosz Fenski Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965695 999178 Changes: libuninum (2.7-1.2) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper compat to 12 (Closes: #965695) * debian/rules: use dh. (Closes: #999178) * Port to DebSrc3.0 (quilt) format. * Add autopkgtest Checksums-Sha1: 8829a5d6bbe49c701fc2005c349624125859 1900 libuninum_2.7-1.2.dsc 593751d6d9f621b8b3fdfe25d8f18d8593f2b758 2992 libuninum_2.7-1.2.debian.tar.xz 796d31a466efff5536a6602472e5e9b60f526eea 6862 libuninum_2.7-1.2_source.buildinfo Checksums-Sha256: bb9790980f6ca93b7154400c0a274d3c7a91f8f4be7a8b505c856763b48a9e1e 1900 libuninum_2.7-1.2.dsc 2b86096dbaee3e8a19b70ef3e0f05ff049fa8e99295e923fb6c5af18431120c6 2992 libuninum_2.7-1.2.debian.tar.xz 4d2dfe3f8f15da44888f643cb950194cf1d955d2b9dd1d8159fb72f328ef283f 6862 libuninum_2.7-1.2_source.buildinfo Files: a639e6b259c63c542015e77283e1d529 1900 libs optional libuninum_2.7-1.2.dsc 48651ddfa6887f43b57e470ad29a45ca 2992 libs optional libuninum_2.7-1.2.debian.tar.xz 2d7a6b29fbd1b9cbe340c17d985fcefe 6862 libs optional libuninum_2.7-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgpcQTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiN8XD/sFp2Oj+9XNJoyb0YpNZ+uMo9m5X2w/ nI1MGHXd9afFyV9EjmpLR6VRPKfTRBEc/iukgatGX0acNFDwLG+EMLB1cRInKBLK 5fHtdBnTJjv8ehn+LqYkXnTGV7lN9Yrfc/Sop/pGKyPOh0rQXU12gLq54DrhNuDU h3xInFhwvbOGQtC+U265OUH30X7q13Vw8Dxq6ZhMLGYhtMHm80cWICnsiEhpDuY4 fffWgYm7603FJErc69DMZqQtDWsVyi9/O+ooRSocscvBIHML5qkyMS3BtAiaI2XA czWCqWwNK64lG981+EkeKILeY1daD9SiwFgPzI6dspcbIyIO4DIBbPtXHR/6z7gv KOv5uK2iJAzSkk/78ej/7Ypr9pPt0unSe7+KdhgYAp7Eqhok6aOLpdpSVoam23UF +BixAnpUql1sAqbK48WdRn/BSmSB+h79GNkrLZ1IlpiM8gcZi3DhqAyUvdkEVSv8 +aoA0/REEp7sSnBNtLijrhZXW/hU3cNZxLovixxQVhvRcOl6yNECTZxL/vB6k9iC dlCnxtA0LSuj8yEtgLsOxfreQhEHc6JUPJ9K2hZNpUcenOyP0ndrjn6ISDx0byLQ
Bug#965523: marked as done (flobopuyo: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 19:04:47 + with message-id and subject line Bug#965523: fixed in flobopuyo 0.20-5.1 has caused the Debian Bug report #965523, regarding flobopuyo: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flobopuyo Version: 0.20-5 Severity: normal Usertags: compat-5-6-removal Hi, The package flobopuyo uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: flobopuyo Source-Version: 0.20-5.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of flobopuyo, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated flobopuyo 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, 12 Dec 2022 01:59:50 +0800 Source: flobopuyo Architecture: source Version: 0.20-5.1 Distribution: unstable Urgency: low Maintainer: Uwe Hermann Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965523 Changes: flobopuyo (0.20-5.1) unstable; urgency=low . * Non-maintainer upload. * Change source format to 3.0 (qulit) - Use quilt instead of simple-patchsys from cdbs. * Bump debhelper version to 9. (Closes: #965523) Checksums-Sha1: cc73517748327b03496a504407a8fb633f65ed96 1832 flobopuyo_0.20-5.1.dsc 7cfe0e031fe0c43ef31072a6a1ded9bc9ae1ef3b 10344 flobopuyo_0.20-5.1.debian.tar.xz c3c26fafeb0b46a87caacf3424726d12ff403ec8 11455 flobopuyo_0.20-5.1_source.buildinfo Checksums-Sha256: 93103f0247b297acc57450de2e675911e0dd115645b1b23c02e2335678e0e1b5 1832 flobopuyo_0.20-5.1.dsc a127e265dd79d52acc7ed4401dd6e9d91afb54258e266d39b4930c985f244adb 10344 flobopuyo_0.20-5.1.debian.tar.xz a498bcf5fad02588ea11d9d9a932c4cd0b0f73a11edf6b0ba6bdf582c6282552 11455 flobopuyo_0.20-5.1_source.buildinfo Files: 1edf7808c48b013ceae11ac91a163c1e 1832 games optional flobopuyo_0.20-5.1.dsc a2d831aff0d498f7608e0a307c8ca988 10344 games optional flobopuyo_0.20-5.1.debian.tar.xz 140072ad798ce038a3fd3e06129c79ff 11455 games optional flobopuyo_0.20-5.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgpKYTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiEDfEAC06HAgdtAP6H/Vib4t0tdWHsPqYAiJ 2vHqr59UZPEke4iYVu1qH60sIWn0iAxxJ2B3yyHOwR9FB1CW1jqyqBV31dYTKfDP hhBzk1hf/IGcBXOJKpBoR/zhiOvQHUxkoO/iwLdLLOSVyULkdEOwyv4hKlyg1bNV 5xEg8Si5EGxnnW4XuCxEw38RCTjt/wGEdo0yziOjASwrpc+nkBfToApdp7eEeq1B lpff4HsUHybJdjv3viT91pFCb6l+uEKz+wbiV1tU+qZlNA5AlNuQt8Msd2T+DBKT jrvHkMp7ZO3yGwuheZTg5zk2UcQ/KfH0/evsoUBExZsthq/0UXGqn2Qq77yDtbvx BSgf0ojHfXJaUNALNyBsFtc5L/zBUau1xo1Gb0zgQQxzwASyEA+22dNmoxBeQQ95 i9kuFxyDTge7TYZROAnmVfbwry783qK0YNUv0lvoqjRR9lSIhSlTDPxCLWUfYsCE VgEvzZiz9UDPKIl/foEhik5W52P/EczAbdC4/JuiNRTOL3j9chNp9ozvMZxH2I/A hiBSMFcbNv9jgjcWFRf9Gs5z7ANICC1QDFuQwnKWthL2HORMnTYOS7lx6SIiT/5q
Bug#999305: marked as done (iat: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 18:42:30 + with message-id and subject line Bug#999305: fixed in iat 0.1.3-7.1 has caused the Debian Bug report #999305, regarding iat: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: iat Version: 0.1.3-7 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: iat Source-Version: 0.1.3-7.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of iat, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated iat 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, 13 Dec 2022 06:09:17 +0800 Source: iat Architecture: source Version: 0.1.3-7.1 Distribution: unstable Urgency: low Maintainer: Dmitry E. Oboukhov Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965589 999305 Changes: iat (0.1.3-7.1) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper compat to 12. (Closes: #965589) * Port to DebSrc3.0 (quilt) * debian/rules: use dh (Closes: #999305) Checksums-Sha1: 165972a4e7a1046615b1189a938e079a109cab1d 1669 iat_0.1.3-7.1.dsc dc4ca6fe3e0a082ed055c53aa9139d0a99a0c658 5896 iat_0.1.3-7.1.debian.tar.xz 218b7e2b5d94c9258107a08584fafe0c6cd7780b 6737 iat_0.1.3-7.1_source.buildinfo Checksums-Sha256: 4244e73c815284157b0ae50156349fe6c29d011c9995ef39818ba648c5b34254 1669 iat_0.1.3-7.1.dsc 95df3e6b8a00c7d61dabecb999e0dc563d046702ec16f515c16a681e40ca6bab 5896 iat_0.1.3-7.1.debian.tar.xz f773276b9f16b7ca2b36d72500231f2896cab0701dced223bb5b8e964e2395f2 6737 iat_0.1.3-7.1_source.buildinfo Files: ed0722b49fcf3b93681a5adc69f91326 1669 otherosfs optional iat_0.1.3-7.1.dsc 9e285b865da30fef980af71acdcb58d7 5896 otherosfs optional iat_0.1.3-7.1.debian.tar.xz 7f219fdd97e57c358a1b5e3d05b88e6b 6737 otherosfs optional iat_0.1.3-7.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgotkTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiAh3D/9ND8LtqD6GyMqlN7M+wNKWk3FQ+cS4 RkGHqpvxyILi11rq14F+3W6k+loqhgONNEaJ/wniNzaftvFYC8JKzF8gLiiSPKGL /NwiVeLDRILVxn0u4DqPKUHBAdeLAXaVN0+zLS5wcGGExbA4AjKZj953QfLd5KB5 qyYGV/fLQfJnSCW4Ep648Yna6A4CdqOkyOmGlH5KaepT7s7aSLUCdhry/NWaLmhx Rlyv7atZxJwtzfa79L0hPV1+b6Egs2AZeZB6gQxT58Bwaov61bLTsv/7YxFeUbDN BmkgsQsYn7u0UMDB+/mBm9x6Xd81g+kUkuaBgJYqNpIQ4apFrW5EQgJr5VR9zVVP 5+bREwnrfrQVeVKShsCs8cFqitAqlU1ULaLUj/KBAXBeto4tpFgDFPLC4Ug8njKC 486dxDT2gPiFoaZDVSf40fZZ+WgEi8QkhLZcK2ndUyn+kIOfi2hJNHPSQ1+03oGk Q/lDWqk/Hai7+Mea0xMJRYoK//I7mIS/3skv8GXT/iYc8216ved5vWYiqZmLEhEJ Dm5yzcKbSwf8Uqu1mEtwrYVmlgKQ8Bk80ztVF4nT0XOBWcfwPO8rLpDv/+zExErC Z3elbI62t5k7mXlgDBGOmIeH4cGWuoVpcidFsGEeJYqMA8/rRxIX7I2OkdbkjI+Q YOimCHNG3NERAg== =VJgE -END PGP SIGNATURE End Message ---
Bug#999046: marked as done (netsend: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 18:43:52 + with message-id and subject line Bug#999046: fixed in netsend 0.0~svnr250-1.5 has caused the Debian Bug report #999046, regarding netsend: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999046 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netsend Version: 0.0~svnr250-1.4 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: netsend Source-Version: 0.0~svnr250-1.5 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of netsend, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated netsend 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, 13 Dec 2022 07:24:55 +0800 Source: netsend Architecture: source Version: 0.0~svnr250-1.5 Distribution: unstable Urgency: low Maintainer: Martin Peylo Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965747 999046 1011647 Changes: netsend (0.0~svnr250-1.5) unstable; urgency=low . * Non-maintainer upload. (Closes: #1011647) * Bump debhelper compat to 12 (Closes: #965747) * debian/rules: Use dh. (Closes: #999046) * Port to DebSrc3.0 (quilt). Checksums-Sha1: 0decd2ddfcae0a36afd7c242e6ace34259f9beb2 1789 netsend_0.0~svnr250-1.5.dsc 3b4b427641f2cd7e1d577ed2a860c09e01a4cfb4 3344 netsend_0.0~svnr250-1.5.debian.tar.xz 3c9c04f4e1b591ae6e76b68d309a4bd04bb06002 6777 netsend_0.0~svnr250-1.5_source.buildinfo Checksums-Sha256: 8657d6b6039b66114fb80890678906cf28655731e7fc84397d226348f7adc5bf 1789 netsend_0.0~svnr250-1.5.dsc 1a887c282ac7f69e0479bb22bdda899491e75120b475d98b8b0ea8914231618d 3344 netsend_0.0~svnr250-1.5.debian.tar.xz cdf2c2db6e43077eee46a935c18d9057bb545d1a771d5a485fe8a5d5e50196ba 6777 netsend_0.0~svnr250-1.5_source.buildinfo Files: de6a368919e1fb1337a02177aa9eefc7 1789 net optional netsend_0.0~svnr250-1.5.dsc a30ff293cb3a9979be714638fbc205d7 3344 net optional netsend_0.0~svnr250-1.5.debian.tar.xz 9692dc69312a2b2673a889b8aeb4ed9e 6777 net optional netsend_0.0~svnr250-1.5_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgo2ITHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiMGsEAC3rQxZXZnXtfrZmReW7GA0SHzn+v/K NcbiV+Fv2iizMeL+e2hBDC0aG/RotaouzDGE2wwKYpIP/fzPLyDaBLc5FoU/R0b1 YR1Y4hVOL1OFgEOOxQ8LQZSWXiJAQYClY3C89BQeXjMbRMXWKZ4/DV4fvQLpWtqP jALQM+dVjStjz6hfhun8KFNUqMgZaCFX2zHfs1IEjNaDmg41iTd8Ecz5PU4yf55+ OdbolUPkS41YjtdgSZNi1fqdvXHah1eTg2yX1EBkgNpET0Z4Bp+MkUedUgPwWzTB q+JDxF13Ad+zkDVVVXiqs9yJc/S2OE6PJU/6a79tzRMJF9BE6XomhPUDZlAQoDjM YhNWX9JV/qJm0SNyhlFfai1apzR36zVA/OdgW7i0PG43+O8h3Yem1Y61QB4qlSNq q5UMGvutk5F5VUmM+RVyumrasbZ9P+00Oe8uSyrLqxYoIEDhs3i4IjgZS8YqevEW YKBfVMwYIr4N+1h14HDIncHEfdi86X0wyV2B942+cmdjZ2s4i6wYsElNfS1Wwj+1 nM915imuBdKqAwBN0Dia+iK6WBySALEMjDIXx1JMeI/F3MFcpoKj7pFQzDZTG2vm /njAdd7zScIxgczRP0B8WHSW2UtROdch9fFxKv84kvKr7/mAVimnZhVRBDrK4tl3 58NMhO2fqGkTNg== =ub6N -END PGP SIGNATURE End Message ---
Bug#966862: marked as done (gramophone2: FTBFS: ld: /tmp/ccWY0lhU.o:./global.h:70: multiple definition of `midi'; /tmp/ccHnI4GU.o:./global.h:70: first defined here)
Your message dated Thu, 29 Dec 2022 18:42:14 +
with message-id
and subject line Bug#966862: fixed in gramophone2 0.8.13a-3.2
has caused the Debian Bug report #966862,
regarding gramophone2: FTBFS: ld: /tmp/ccWY0lhU.o:./global.h:70: multiple
definition of `midi'; /tmp/ccHnI4GU.o:./global.h:70: first defined here
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.)
--
966862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gramophone2
Version: 0.8.13a-3.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -O2 -Wl,-z,relro -o gramophone2 GRAMophone.c\
> grammyVM.c init.c midicode.c\
> midifile.c expcode.c debug.c errors.c\
> hash.c GRAMophone.tab.c -lm
> GRAMophone.c: In function ‘main’:
> GRAMophone.c:94:2: warning: implicit declaration of function ‘usageError’;
> did you mean ‘strerror’? [-Wimplicit-function-declaration]
>94 | usageError();
> | ^~
> | strerror
> GRAMophone.c:98:3: warning: implicit declaration of function ‘initGRAMophone’
> [-Wimplicit-function-declaration]
>98 | initGRAMophone();
> | ^~
> GRAMophone.c:99:3: warning: implicit declaration of function ‘yyparse’
> [-Wimplicit-function-declaration]
>99 | yyparse();
> | ^~~
> GRAMophone.c:102:59: warning: implicit declaration of function ‘grammyvm’
> [-Wimplicit-function-declaration]
> 102 | checkOption?(printf("the composition source is ok\n")):(grammyvm());
> | ^~~~
> grammyVM.c: In function ‘chomsky_generator’:
> grammyVM.c:711:11: warning: implicit declaration of function
> ‘mf_write_midi_event’ [-Wimplicit-function-declaration]
> 711 | if(!mf_write_midi_event(prev_duration, note_on,
> players[playerCount]->local_params[CHN], data, 2)) {
> | ^~~
> grammyVM.c: In function ‘lindenmayer_prod_generator’:
> grammyVM.c:1114:25: warning: implicit declaration of function ‘hash’
> [-Wimplicit-function-declaration]
> 1114 | buffer[counter++]=hash(string_buf, 0);
> | ^~~~
> grammyVM.c: In function ‘myputc’:
> grammyVM.c:1477:5: warning: type of ‘c’ defaults to ‘int’ [-Wimplicit-int]
> 1477 | int myputc(c) {
> | ^~
> grammyVM.c: In function ‘write_player_track’:
> grammyVM.c:1481:5: warning: type of ‘track’ defaults to ‘int’ [-Wimplicit-int]
> 1481 | int write_player_track(track) {
> | ^~
> grammyVM.c:1487:7: warning: implicit declaration of function
> ‘mf_write_meta_event’ [-Wimplicit-function-declaration]
> 1487 | if(!mf_write_meta_event(0, copyright_notice, copyright,
> strlen(copyright))) {
> | ^~~
> grammyVM.c:1491:3: warning: implicit declaration of function ‘mf_write_tempo’
> [-Wimplicit-function-declaration]
> 1491 | mf_write_tempo((long)6000/tempo);
> | ^~
> grammyVM.c:1514:5: warning: implicit declaration of function
> ‘print_local_params’ [-Wimplicit-function-declaration]
> 1514 | print_local_params(playerCount); //debug
> | ^~
> grammyVM.c: In function ‘grammyvm’:
> grammyVM.c:1548:4: warning: implicit declaration of function
> ‘print_composition_info’ [-Wimplicit-function-declaration]
> 1548 |print_composition_info(); //debug
> |^~
> grammyVM.c:1549:4: warning: implicit declaration of function
> ‘print_global_params’ [-Wimplicit-function-declaration]
> 1549 |print_global_params(); //debug
> |^~~
> init.c: In function ‘initGRAMophone’:
> init.c:66:5: warning: implicit declaration of function ‘sntx_err’; did you
> mean ‘stderr’? [-Wimplicit-function-declaration]
>66 | sntx_err(MEMORY_ERR, "");
> | ^~~~
> | stderr
> midicode.c: In function ‘gen_code’:
> midicode.c:31:6: warning: implicit declaration of function ‘hash’
> [-Wimplicit-function-declaration]
>31 | id=hash(idTemp, 0);
> | ^~~~
> midifile.c: In function ‘WriteVarLen’:
> midifile.c:98:3: warning: implicit declaration of function ‘eputc’; did you
> mean ‘putc’?
Bug#999156: marked as done (dbench: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 18:41:24 + with message-id and subject line Bug#999156: fixed in dbench 4.0-2.1 has caused the Debian Bug report #999156, regarding dbench: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dbench Version: 4.0-2 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: dbench Source-Version: 4.0-2.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of dbench, 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 999...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated dbench 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, 12 Dec 2022 22:43:32 +0800 Source: dbench Architecture: source Version: 4.0-2.1 Distribution: unstable Urgency: low Maintainer: Mattias Nordstrom Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965484 999156 Changes: dbench (4.0-2.1) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper compat to 12. (Closes: #965484) * debian/rules: use dh. (Closes: #999156) * Port to DebSrc3.0 (quilt) Checksums-Sha1: d10d46d1c1e679cb7ee10c5d59fe36450b068a31 1708 dbench_4.0-2.1.dsc 8a683b28da85db689ada2ef0d90a15a4a57a403c 4260 dbench_4.0-2.1.debian.tar.xz 8a46267646bea209303f8816ee80cc1cfec0dde7 6798 dbench_4.0-2.1_source.buildinfo Checksums-Sha256: f8ee8ff5e2b912609f62753005eef89179a1984cfc0dccd170e28188e34873d0 1708 dbench_4.0-2.1.dsc fb01e8d8f5ab1c0c62c7ad1a8282045fa2fef143e4a82a73bc57f5730ce5b842 4260 dbench_4.0-2.1.debian.tar.xz fe997eec8478721f37e325b4e5914a83adf120cb5fe5eb3384b7cfda0caf6c1d 6798 dbench_4.0-2.1_source.buildinfo Files: f73c3e4ee3df800c78e3a1a113c1865a 1708 utils optional dbench_4.0-2.1.dsc 600a6d4a535f8d967472816253280122 4260 utils optional dbench_4.0-2.1.debian.tar.xz f769fb9bb6f009e953765c14dd40 6798 utils optional dbench_4.0-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgniwTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiESpEACKs6timMCoy/29pErEtsT4QptUPT8R NsBV0xbWpa8X/ulp0UmmzPw/rNRK+2JrPWL/cVgxaIbE7f8NHZnzJbsxWR2WL1EM B4aBK1pn9cI5F5T1EaquJXr530rGpnriPHg23039kX2E81v7fasuymHiDPK0jngF swbnrQRyDgXVwOhQTrcW4bSSNKpHTBAP/OeFwdO3LdR54O6K552m1cgS6ihLU/tT nqzmRzVk1KXXYSw4hJuk/+q7E114VLUi6eVvas8rEPP4JBb0RdzUd+B14uoLD83o 7rbAcc34aMItfBkm2uoDNUSy4EoE1xhvuikxKv2nDiPA263fKk1+UeeWUXABNtWn xjbVCBPggWSEkPU/hqhi83ao7i5/bNrVvZGerhLftdeQUk0/eul7uZoAtOrUkRyO TiG+NhNDy2Iy1W3wpOq/0FMBW5KReVspHPtG9blhfCHavgJNiqiJwRJmZ0Bc6fhv rs6G3kMKVfMGCxv1f6LYlYzHkaRQQiYQj0HCy+FsahhHUSOHKtiBqSMTm2eX0KD9 FcXUANfE01doQp/b3j7gFpW/3uVmgisXoDZBqXsGwFM3nJsSTJOEo3Oiw6e91SZk UCU05JHmRMGaRhf/EzwFeKlOkQXjzJxChbXOliQj28OWMmTzkfDP6DIYG6SrH3qt +caj+vu8zSivBQ== =rPeH -END PGP SIGNATURE End Message ---
Bug#998958: marked as done (filler: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 18:41:42 + with message-id and subject line Bug#998958: fixed in filler 1.02-6.4 has caused the Debian Bug report #998958, regarding filler: missing required debian/rules targets build-arch and/or build-indep 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.) -- 998958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998958 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: filler Version: 1.02-6.3 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: filler Source-Version: 1.02-6.4 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of filler, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated filler 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: Sat, 10 Dec 2022 03:20:44 +0800 Source: filler Architecture: source Version: 1.02-6.4 Distribution: unstable Urgency: low Maintainer: James Damour (Suvarov454) Changed-By: Ying-Chun Liu (PaulLiu) Closes: 780484 965521 998958 Changes: filler (1.02-6.4) unstable; urgency=low . [ Ying-Chun Liu (PaulLiu) ] * Non-maintainer upload. * Bump debhelper to 12 (Closes: #965521) - debian/rules: port to use dh (Closes: #998958) * Port to DebSrc3.0 (quilt) . [ Jean-Michel Nirgal Vourgère ] * Distribute manpage (Closes: #780484) Checksums-Sha1: cdf3b66a6b3711a97a5b76832210fe92c97818ed 1777 filler_1.02-6.4.dsc 7199e83f6b2eff1f399b32e404b0b5365ff64cd6 8192 filler_1.02-6.4.debian.tar.xz 8edc136609cf807d74d22c813a0566a7a2ff8694 6745 filler_1.02-6.4_source.buildinfo Checksums-Sha256: c539502daf0a58920a0072b9fde65210151624a2a9ea7c05f82c086686f3db5c 1777 filler_1.02-6.4.dsc 2d11e67609e7ceca4d7bc060183b5cb9ddb947170ac48aba7aac45af6ed074b5 8192 filler_1.02-6.4.debian.tar.xz fbcc6d628a424be8e4f09f74c8ee5bb8c1ce1ca4a07ff0907f6be0125bb1e0e2 6745 filler_1.02-6.4_source.buildinfo Files: adf8bb7b4726ad1e278946ee92d562a1 1777 games optional filler_1.02-6.4.dsc bc2f3410804031797dcb626b84d733b5 8192 games optional filler_1.02-6.4.debian.tar.xz dc36e6d0578734a229750cae8aafc360 6745 games optional filler_1.02-6.4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgoQ8THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiEn1D/9HDGYen/IpJNKlTbdm9bXGD4YVHScG IUTtFL9kvzxsMh1HyNB1a4HtJxFc2QcH35cQ12DqoFsrU+0n20dgAD1UEQjEvT7T uzw6u5FaaLKCzGbYkVIlTgfRpOiTfVQRC35fe/GU3zva6tefANKu3F/tQN8eOt8O WXmMGHhy6qbDSfrRoDhUcnxc32wBUT6ASWlvHzvKVLY0XnR3PZ+TKuJTiTl5OWFo ExZvk2sAbj/8budkJPNAtvNpeL9QRFuYMyGyx4R657dN0+FSO5Byq0wUqPmINcoe Z8fmvubj4pgmKB2FP5QwSkOjLVlrlbGguKxVtIlz4YeuOGpx4iwjNuHOIygMhPmG 2lE0EL4SYeQb8RzFqh6iK5gOjM6iLPhC1f3u/iupwrYk9ITRHF3/SWq2qSyOx1RY BMWVFceUb3IezyCfx3wtOspo8ArVbM/sDCIZU+mvkRK/Un+wydKGKml3dGMrSpQg 1iWJqS+TwR6Ja7zI8R0vlRTYfW0vrO3auDjamLxnW6QzYSYbCws06YjZkcA0sEgU +dzCvtVSZn62hspkrGz6KfoYz00q2iPEQqbAAUTFQjo30bngHKeFgES7+VAZI72q Q6umEF0fS38jaEKicB2zKyH6RMPgRSPWhPXXAmi/C6XONa7De+upYZW8TpU9FonK JuT2ixMhV3Orbw== =ON15 -END PGP SIGNATURE End Message ---
Bug#998956: marked as done (efax-gtk: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 18:41:33 + with message-id and subject line Bug#998956: fixed in efax-gtk 3.2.8-2.3 has caused the Debian Bug report #998956, regarding efax-gtk: missing required debian/rules targets build-arch and/or build-indep 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.) -- 998956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998956 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: efax-gtk Version: 3.2.8-2.2 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Source: efax-gtk Source-Version: 3.2.8-2.3 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of efax-gtk, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated efax-gtk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Dec 2022 23:39:09 +0800 Source: efax-gtk Architecture: source Version: 3.2.8-2.3 Distribution: unstable Urgency: low Maintainer: Lior Kaplan Changed-By: Ying-Chun Liu (PaulLiu) Closes: 955830 965505 998956 Changes: efax-gtk (3.2.8-2.3) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper version to 12. (Closes: #965505) - Update debian/rules to use dh. (Closes: #998956) - Remove Build-Depends on autotools-dev * Add debian/patches/0002-fix-format-security.patch - Newer debhelper force format-security. Thus we need a patch. * Add debian/patches/0003-correct-gettext-version.patch - Update gettext version. * Remove unnecessarily Build-Depends on deprecated libdbus-glib-1-dev (Closes: #955830) Checksums-Sha1: 4bcb8f48df7822c121bc0dee9a8ca06144e41aff 1906 efax-gtk_3.2.8-2.3.dsc e6caa6ff7914058d7d9b0308350d5c9f88813d9c 7436 efax-gtk_3.2.8-2.3.debian.tar.xz a3119de930e462a0741f318b98de114de1b4988a 12424 efax-gtk_3.2.8-2.3_source.buildinfo Checksums-Sha256: 8f8a2bbc94031139a29ad9c2b3fc057cb95b1a02470170bc02f7727d3ad44c1e 1906 efax-gtk_3.2.8-2.3.dsc ceaa83a9f65ac82fce75008502b84a5133010319d6a549007d0860fd66d94ee0 7436 efax-gtk_3.2.8-2.3.debian.tar.xz f4acf4bfb0ad36a5d6141e41d6bc0a8a83d9a057784366686aff7c9bf9db71bb 12424 efax-gtk_3.2.8-2.3_source.buildinfo Files: d45317d546e42449bec673dadda83d06 1906 comm optional efax-gtk_3.2.8-2.3.dsc 30cb87618055acd8d6ff23be9ab576f7 7436 comm optional efax-gtk_3.2.8-2.3.debian.tar.xz 5e9ec19b57e74c8a626efd91ce50d527 12424 comm optional efax-gtk_3.2.8-2.3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgn98THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiDT3D/9hvG5AZpJiJpjpHVm0PzUV+xTCDfNh WcYu2hjRh/vNW8cAd1ephFDuLIlBJnD/OqFWIAElr9wj0G6cpC0Y2ymK0ftJZnlv +g1TZvhKJ5DpwYw+QfKYfw5jclMG9J9P98biVob4VdL2PNxnRuVS9XT/WvBIZ1/f RdHctppA53uSKzsKfdQnLf6sgHmMQnLsH3KKrvyjjqGLnOxgN1G1ikd+Y4adzps2 qOCoW+Q5IpdbjTaJDNd620IV3vteOamTycqLeAUXylNW1fnWbI0/srlqco3HcBeI 4qSISvd1NRkYlO3R+ZA4PEWN+Yk6Q6ZAljd4OkgbOaqvw8ajoZ5YqiC1dPo9TRnD K847pqXn4KUG7YsO3iFFoK5o25BUN/qUlPjxyf/pFq6DMekX8kbh+Ogrwlr4/PH2 7jKhwaQuBKKB8bZeRdJmX0XkUkInteS66xupkEOSGRk9wVtQGrnrnYM24WrIur1t 0wMa5e/jaOdWJWnOZoEp8+tEP27MPeOfp7YFQeKErzHUt8iFjJRvsyK96pmW3ukD myTgQNxYKhy0prKiKiKw70ZURk8+a24zgJJQlDOajgpOwxT2PeWJkxBjD1ND5prN IC5wEk/CNDfHJSY0eeelzQ2SwTn7Wk/MYpv2mPfdWZ8QSAikKnPWQjo74fZqD9fD 7Bad4qjvW2Y2dw==
Bug#965747: marked as done (netsend: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 18:43:52 + with message-id and subject line Bug#965747: fixed in netsend 0.0~svnr250-1.5 has caused the Debian Bug report #965747, regarding netsend: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965747 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: netsend Version: 0.0~svnr250-1.4 Severity: normal Usertags: compat-5-6-removal Hi, The package netsend uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: netsend Source-Version: 0.0~svnr250-1.5 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of netsend, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated netsend 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, 13 Dec 2022 07:24:55 +0800 Source: netsend Architecture: source Version: 0.0~svnr250-1.5 Distribution: unstable Urgency: low Maintainer: Martin Peylo Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965747 999046 1011647 Changes: netsend (0.0~svnr250-1.5) unstable; urgency=low . * Non-maintainer upload. (Closes: #1011647) * Bump debhelper compat to 12 (Closes: #965747) * debian/rules: Use dh. (Closes: #999046) * Port to DebSrc3.0 (quilt). Checksums-Sha1: 0decd2ddfcae0a36afd7c242e6ace34259f9beb2 1789 netsend_0.0~svnr250-1.5.dsc 3b4b427641f2cd7e1d577ed2a860c09e01a4cfb4 3344 netsend_0.0~svnr250-1.5.debian.tar.xz 3c9c04f4e1b591ae6e76b68d309a4bd04bb06002 6777 netsend_0.0~svnr250-1.5_source.buildinfo Checksums-Sha256: 8657d6b6039b66114fb80890678906cf28655731e7fc84397d226348f7adc5bf 1789 netsend_0.0~svnr250-1.5.dsc 1a887c282ac7f69e0479bb22bdda899491e75120b475d98b8b0ea8914231618d 3344 netsend_0.0~svnr250-1.5.debian.tar.xz cdf2c2db6e43077eee46a935c18d9057bb545d1a771d5a485fe8a5d5e50196ba 6777 netsend_0.0~svnr250-1.5_source.buildinfo Files: de6a368919e1fb1337a02177aa9eefc7 1789 net optional netsend_0.0~svnr250-1.5.dsc a30ff293cb3a9979be714638fbc205d7 3344 net optional netsend_0.0~svnr250-1.5.debian.tar.xz 9692dc69312a2b2673a889b8aeb4ed9e 6777 net optional netsend_0.0~svnr250-1.5_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgo2ITHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiMGsEAC3rQxZXZnXtfrZmReW7GA0SHzn+v/K NcbiV+Fv2iizMeL+e2hBDC0aG/RotaouzDGE2wwKYpIP/fzPLyDaBLc5FoU/R0b1 YR1Y4hVOL1OFgEOOxQ8LQZSWXiJAQYClY3C89BQeXjMbRMXWKZ4/DV4fvQLpWtqP jALQM+dVjStjz6hfhun8KFNUqMgZaCFX2zHfs1IEjNaDmg41iTd8Ecz5PU4yf55+ OdbolUPkS41YjtdgSZNi1fqdvXHah1eTg2yX1EBkgNpET0Z4Bp+MkUedUgPwWzTB q+JDxF13Ad+zkDVVVXiqs9yJc/S2OE6PJU/6a79tzRMJF9BE6XomhPUDZlAQoDjM YhNWX9JV/qJm0SNyhlFfai1apzR36zVA/OdgW7i0PG43+O8h3Yem1Y61QB4qlSNq q5UMGvutk5F5VUmM+RVyumrasbZ9P+00Oe8uSyrLqxYoIEDhs3i4IjgZS8YqevEW YKBfVMwYIr4N+1h14HDIncHEfdi86X0wyV2B942+cmdjZ2s4i6wYsElNfS1Wwj+1
Bug#965589: marked as done (iat: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 18:42:30 + with message-id and subject line Bug#965589: fixed in iat 0.1.3-7.1 has caused the Debian Bug report #965589, regarding iat: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: iat Version: 0.1.3-7 Severity: normal Usertags: compat-5-6-removal Hi, The package iat uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: iat Source-Version: 0.1.3-7.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of iat, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated iat 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, 13 Dec 2022 06:09:17 +0800 Source: iat Architecture: source Version: 0.1.3-7.1 Distribution: unstable Urgency: low Maintainer: Dmitry E. Oboukhov Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965589 999305 Changes: iat (0.1.3-7.1) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper compat to 12. (Closes: #965589) * Port to DebSrc3.0 (quilt) * debian/rules: use dh (Closes: #999305) Checksums-Sha1: 165972a4e7a1046615b1189a938e079a109cab1d 1669 iat_0.1.3-7.1.dsc dc4ca6fe3e0a082ed055c53aa9139d0a99a0c658 5896 iat_0.1.3-7.1.debian.tar.xz 218b7e2b5d94c9258107a08584fafe0c6cd7780b 6737 iat_0.1.3-7.1_source.buildinfo Checksums-Sha256: 4244e73c815284157b0ae50156349fe6c29d011c9995ef39818ba648c5b34254 1669 iat_0.1.3-7.1.dsc 95df3e6b8a00c7d61dabecb999e0dc563d046702ec16f515c16a681e40ca6bab 5896 iat_0.1.3-7.1.debian.tar.xz f773276b9f16b7ca2b36d72500231f2896cab0701dced223bb5b8e964e2395f2 6737 iat_0.1.3-7.1_source.buildinfo Files: ed0722b49fcf3b93681a5adc69f91326 1669 otherosfs optional iat_0.1.3-7.1.dsc 9e285b865da30fef980af71acdcb58d7 5896 otherosfs optional iat_0.1.3-7.1.debian.tar.xz 7f219fdd97e57c358a1b5e3d05b88e6b 6737 otherosfs optional iat_0.1.3-7.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgotkTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiAh3D/9ND8LtqD6GyMqlN7M+wNKWk3FQ+cS4 RkGHqpvxyILi11rq14F+3W6k+loqhgONNEaJ/wniNzaftvFYC8JKzF8gLiiSPKGL /NwiVeLDRILVxn0u4DqPKUHBAdeLAXaVN0+zLS5wcGGExbA4AjKZj953QfLd5KB5 qyYGV/fLQfJnSCW4Ep648Yna6A4CdqOkyOmGlH5KaepT7s7aSLUCdhry/NWaLmhx Rlyv7atZxJwtzfa79L0hPV1+b6Egs2AZeZB6gQxT58Bwaov61bLTsv/7YxFeUbDN BmkgsQsYn7u0UMDB+/mBm9x6Xd81g+kUkuaBgJYqNpIQ4apFrW5EQgJr5VR9zVVP 5+bREwnrfrQVeVKShsCs8cFqitAqlU1ULaLUj/KBAXBeto4tpFgDFPLC4Ug8njKC 486dxDT2gPiFoaZDVSf40fZZ+WgEi8QkhLZcK2ndUyn+kIOfi2hJNHPSQ1+03oGk Q/lDWqk/Hai7+Mea0xMJRYoK//I7mIS/3skv8GXT/iYc8216ved5vWYiqZmLEhEJ Dm5yzcKbSwf8Uqu1mEtwrYVmlgKQ8Bk80ztVF4nT0XOBWcfwPO8rLpDv/+zExErC Z3elbI62t5k7mXlgDBGOmIeH4cGWuoVpcidFsGEeJYqMA8/rRxIX7I2OkdbkjI+Q YOimCHNG3NERAg== =VJgE -END PGP SIGNATURE End Message ---
Bug#965521: marked as done (filler: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 18:41:42 + with message-id and subject line Bug#965521: fixed in filler 1.02-6.4 has caused the Debian Bug report #965521, regarding filler: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965521 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: filler Version: 1.02-6.3 Severity: normal Usertags: compat-5-6-removal Hi, The package filler uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: filler Source-Version: 1.02-6.4 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of filler, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated filler 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: Sat, 10 Dec 2022 03:20:44 +0800 Source: filler Architecture: source Version: 1.02-6.4 Distribution: unstable Urgency: low Maintainer: James Damour (Suvarov454) Changed-By: Ying-Chun Liu (PaulLiu) Closes: 780484 965521 998958 Changes: filler (1.02-6.4) unstable; urgency=low . [ Ying-Chun Liu (PaulLiu) ] * Non-maintainer upload. * Bump debhelper to 12 (Closes: #965521) - debian/rules: port to use dh (Closes: #998958) * Port to DebSrc3.0 (quilt) . [ Jean-Michel Nirgal Vourgère ] * Distribute manpage (Closes: #780484) Checksums-Sha1: cdf3b66a6b3711a97a5b76832210fe92c97818ed 1777 filler_1.02-6.4.dsc 7199e83f6b2eff1f399b32e404b0b5365ff64cd6 8192 filler_1.02-6.4.debian.tar.xz 8edc136609cf807d74d22c813a0566a7a2ff8694 6745 filler_1.02-6.4_source.buildinfo Checksums-Sha256: c539502daf0a58920a0072b9fde65210151624a2a9ea7c05f82c086686f3db5c 1777 filler_1.02-6.4.dsc 2d11e67609e7ceca4d7bc060183b5cb9ddb947170ac48aba7aac45af6ed074b5 8192 filler_1.02-6.4.debian.tar.xz fbcc6d628a424be8e4f09f74c8ee5bb8c1ce1ca4a07ff0907f6be0125bb1e0e2 6745 filler_1.02-6.4_source.buildinfo Files: adf8bb7b4726ad1e278946ee92d562a1 1777 games optional filler_1.02-6.4.dsc bc2f3410804031797dcb626b84d733b5 8192 games optional filler_1.02-6.4.debian.tar.xz dc36e6d0578734a229750cae8aafc360 6745 games optional filler_1.02-6.4_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgoQ8THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiEn1D/9HDGYen/IpJNKlTbdm9bXGD4YVHScG IUTtFL9kvzxsMh1HyNB1a4HtJxFc2QcH35cQ12DqoFsrU+0n20dgAD1UEQjEvT7T uzw6u5FaaLKCzGbYkVIlTgfRpOiTfVQRC35fe/GU3zva6tefANKu3F/tQN8eOt8O WXmMGHhy6qbDSfrRoDhUcnxc32wBUT6ASWlvHzvKVLY0XnR3PZ+TKuJTiTl5OWFo ExZvk2sAbj/8budkJPNAtvNpeL9QRFuYMyGyx4R657dN0+FSO5Byq0wUqPmINcoe Z8fmvubj4pgmKB2FP5QwSkOjLVlrlbGguKxVtIlz4YeuOGpx4iwjNuHOIygMhPmG 2lE0EL4SYeQb8RzFqh6iK5gOjM6iLPhC1f3u/iupwrYk9ITRHF3/SWq2qSyOx1RY BMWVFceUb3IezyCfx3wtOspo8ArVbM/sDCIZU+mvkRK/Un+wydKGKml3dGMrSpQg 1iWJqS+TwR6Ja7zI8R0vlRTYfW0vrO3auDjamLxnW6QzYSYbCws06YjZkcA0sEgU
Bug#965578: marked as done (hasciicam: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 18:42:22 + with message-id and subject line Bug#965578: fixed in hasciicam 1.1.2-1.1 has caused the Debian Bug report #965578, regarding hasciicam: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hasciicam Version: 1.1.2-1 Severity: normal Usertags: compat-5-6-removal Hi, The package hasciicam uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: hasciicam Source-Version: 1.1.2-1.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of hasciicam, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated hasciicam 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, 12 Dec 2022 02:40:02 +0800 Source: hasciicam Architecture: source Version: 1.1.2-1.1 Distribution: unstable Urgency: low Maintainer: Luca Bigliardi Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965578 Changes: hasciicam (1.1.2-1.1) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper compat to 9. (Closes: #965578) Checksums-Sha1: 6fd1b69a4fd34bf15563a7207621b187b9810c57 1947 hasciicam_1.1.2-1.1.dsc 95b91d29c39c59fdece211b0db080bb56242b589 6336 hasciicam_1.1.2-1.1.debian.tar.xz d0d9995d406ea21e49d4ebcd1f493fa325b79f65 7536 hasciicam_1.1.2-1.1_source.buildinfo Checksums-Sha256: 936730faa9dc3e91fb382b1d9fcc9c3549ccc2276a949b9b1da74757a45b9236 1947 hasciicam_1.1.2-1.1.dsc 5bb687880b0eb0f7882a2a3af151e1aca60efdc0160c78f61b453ef97aa0ecfa 6336 hasciicam_1.1.2-1.1.debian.tar.xz 4531f7ab99c5dece7846f44a91bf10396eecdd79045edc1d8424e5c1d63ee46d 7536 hasciicam_1.1.2-1.1_source.buildinfo Files: 41373aff820d33d4472c41b172421610 1947 graphics optional hasciicam_1.1.2-1.1.dsc 593705af855b8cd048527e2cdfb87104 6336 graphics optional hasciicam_1.1.2-1.1.debian.tar.xz 9a90d9e6468dd738fd326265cdf25937 7536 graphics optional hasciicam_1.1.2-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgol4THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiIOND/9PMupCrpETKT8WVCyvYBlgabF2rD7Q uPUGlTZfrn8ZlIc295Rvys5Uo4LQwezZg7gzJ9hlo8O86R0DHgeP3IXXbpPOPexC Z52iMOamZiEBRg0MImEgZY0Adik4sweLEGD22AZLhqE0/SsOCg51bjHgdPijkAKC 66oSVScTJmUTPkyuMG6EZFlrxvVGaUDvsnhyGPDHwe2J3zSh2ydFqG+w/tJKUJai anOaOkuc8Der7SQyb17EjiDcj9NjMLz+wfw/93P+LOVRsSsBLdOvsDHiJqQHhzOu HpCBypVgp8rvTy5Kv5bz+Oge3zOTHpIVnitMaDUP60fN2NVyUChRD/QLf3d2l86h jsPtXhC/cagatIiCb/s8wxXQ9x40DC62aHAEAhm9RXyuSNPW7bjEssZFxH2vVNdN W5to2xxwQ9MKu7v0XNGPBi7sPxAYOGn8yY6fW0c0th2hJ1mFHINfqiQeFIPVKP79 xIpn6w6Kb+1SAOGvo+U8wcG9Ndz5NcEt8XPvhec46fAxoytDBKkPSG7ThdgcpcXT EWaeZqxBZMbOyXlbcgU3J7VkPDComWtkqhhAODQFNcktQY1KQ7VBoFh0pk+r7Tw7 vGxiwcGdOF/YVc8kQ8pY3gJSITPdHa+dwrO45ShuvSxCosaFCgN4CXmj3iX2wcOw CtxFjZazy5FKaA== =t2lR -END PGP SIGNATURE End Message ---
Bug#965505: marked as done (efax-gtk: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 18:41:33 + with message-id and subject line Bug#965505: fixed in efax-gtk 3.2.8-2.3 has caused the Debian Bug report #965505, regarding efax-gtk: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965505 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: efax-gtk Version: 3.2.8-2.1 Severity: normal Usertags: compat-5-6-removal Hi, The package efax-gtk uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: efax-gtk Source-Version: 3.2.8-2.3 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of efax-gtk, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated efax-gtk package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 09 Dec 2022 23:39:09 +0800 Source: efax-gtk Architecture: source Version: 3.2.8-2.3 Distribution: unstable Urgency: low Maintainer: Lior Kaplan Changed-By: Ying-Chun Liu (PaulLiu) Closes: 955830 965505 998956 Changes: efax-gtk (3.2.8-2.3) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper version to 12. (Closes: #965505) - Update debian/rules to use dh. (Closes: #998956) - Remove Build-Depends on autotools-dev * Add debian/patches/0002-fix-format-security.patch - Newer debhelper force format-security. Thus we need a patch. * Add debian/patches/0003-correct-gettext-version.patch - Update gettext version. * Remove unnecessarily Build-Depends on deprecated libdbus-glib-1-dev (Closes: #955830) Checksums-Sha1: 4bcb8f48df7822c121bc0dee9a8ca06144e41aff 1906 efax-gtk_3.2.8-2.3.dsc e6caa6ff7914058d7d9b0308350d5c9f88813d9c 7436 efax-gtk_3.2.8-2.3.debian.tar.xz a3119de930e462a0741f318b98de114de1b4988a 12424 efax-gtk_3.2.8-2.3_source.buildinfo Checksums-Sha256: 8f8a2bbc94031139a29ad9c2b3fc057cb95b1a02470170bc02f7727d3ad44c1e 1906 efax-gtk_3.2.8-2.3.dsc ceaa83a9f65ac82fce75008502b84a5133010319d6a549007d0860fd66d94ee0 7436 efax-gtk_3.2.8-2.3.debian.tar.xz f4acf4bfb0ad36a5d6141e41d6bc0a8a83d9a057784366686aff7c9bf9db71bb 12424 efax-gtk_3.2.8-2.3_source.buildinfo Files: d45317d546e42449bec673dadda83d06 1906 comm optional efax-gtk_3.2.8-2.3.dsc 30cb87618055acd8d6ff23be9ab576f7 7436 comm optional efax-gtk_3.2.8-2.3.debian.tar.xz 5e9ec19b57e74c8a626efd91ce50d527 12424 comm optional efax-gtk_3.2.8-2.3_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgn98THHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiDT3D/9hvG5AZpJiJpjpHVm0PzUV+xTCDfNh WcYu2hjRh/vNW8cAd1ephFDuLIlBJnD/OqFWIAElr9wj0G6cpC0Y2ymK0ftJZnlv +g1TZvhKJ5DpwYw+QfKYfw5jclMG9J9P98biVob4VdL2PNxnRuVS9XT/WvBIZ1/f RdHctppA53uSKzsKfdQnLf6sgHmMQnLsH3KKrvyjjqGLnOxgN1G1ikd+Y4adzps2 qOCoW+Q5IpdbjTaJDNd620IV3vteOamTycqLeAUXylNW1fnWbI0/srlqco3HcBeI
Bug#965567: marked as done (gramophone2: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 18:42:14 + with message-id and subject line Bug#965567: fixed in gramophone2 0.8.13a-3.2 has caused the Debian Bug report #965567, regarding gramophone2: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gramophone2 Version: 0.8.13a-3.1 Severity: normal Usertags: compat-5-6-removal Hi, The package gramophone2 uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: gramophone2 Source-Version: 0.8.13a-3.2 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of gramophone2, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated gramophone2 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, 13 Dec 2022 05:48:33 +0800 Source: gramophone2 Architecture: source Version: 0.8.13a-3.2 Distribution: unstable Urgency: low Maintainer: Francesco Namuri Changed-By: Ying-Chun Liu (PaulLiu) Closes: 738279 760662 965567 966862 Changes: gramophone2 (0.8.13a-3.2) unstable; urgency=low . [ Ying-Chun Liu (PaulLiu) ] * Non-maintainer upload. * Bump debhelper compat to 10. (Closes: #965567) [ Lukas Märdian ] * Fix FTBFS by gcc-10 (Closes: #966862) [ Nicolas Sévelin-Radiguet ] * Fix FTBFS by clang (Closes: #760662) [ Andreas Moog ] * Include patches from Ubuntu (Closes: #738279) Checksums-Sha1: 56379322077c506b3996ab572ebb355232dba99c 1836 gramophone2_0.8.13a-3.2.dsc bfac27418390cb84f9a8be6b2d1c4e9b696d8b33 3820 gramophone2_0.8.13a-3.2.debian.tar.xz a4e0e6097314ba7d092f394f539abe8833699443 6911 gramophone2_0.8.13a-3.2_source.buildinfo Checksums-Sha256: f545401d23185418f9f8ddbee007b965b6e0eccc5ac700343b8357150479d39d 1836 gramophone2_0.8.13a-3.2.dsc 7e76cc19fd16f56fbf115e6aeb911b5ab74007c3b1ab4ea90a71ec452df92df3 3820 gramophone2_0.8.13a-3.2.debian.tar.xz 5726dbba86cc27a19c53a6a161a65dd56e54804351ea5b356a333a1e07b60f45 6911 gramophone2_0.8.13a-3.2_source.buildinfo Files: 30351ae6e9676bbee4ec1211e8e9f9f5 1836 sound optional gramophone2_0.8.13a-3.2.dsc ce531e8a86ae7cfb0cdefe2ac2d8b0b3 3820 sound optional gramophone2_0.8.13a-3.2.debian.tar.xz c4d27f658b48b6f533a1e055dfa5675c 6911 sound optional gramophone2_0.8.13a-3.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgocATHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiKSfD/9KUkgta2J4LBL0OvGuHgBFKdWshEDH jlAYy6BNwBNNTQbRBfUSXjraVCHKuC5Np+eaOV0xbVI4OE9HFzA4KCarsOQdviiy Skd8FvItqcM3EoZMLbPQnTOfeeAP8jKtBLE99rQBhaLbzkQYwkmlDIlgZL5ZKWVu 1TrPwfgPHa+El7iBueYQCoX32Er8Ke7YAteXR2MBd5+B69yJRl7XchF+7SZV6UOJ eq86TFnpDFc4usUh//+4hQNDFKVIQHYczIDvGQt+bGyrh+eYtintSIPRJwsYbe9k SSvsce4apeLknHv2xEJ+wYIViBBzVi6NtbWx504jwiqXPHv8pj3V924qFLeQtfAL craiIK28QVn/A2Sr8Xdia/Hq4DGEvmd3BwVcEhjOPy1VuVP5i/H7PAufRDIWC2oO
Bug#965484: marked as done (dbench: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 18:41:24 + with message-id and subject line Bug#965484: fixed in dbench 4.0-2.1 has caused the Debian Bug report #965484, regarding dbench: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dbench Version: 4.0-2 Severity: normal Usertags: compat-5-6-removal Hi, The package dbench uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Source: dbench Source-Version: 4.0-2.1 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of dbench, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated dbench 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, 12 Dec 2022 22:43:32 +0800 Source: dbench Architecture: source Version: 4.0-2.1 Distribution: unstable Urgency: low Maintainer: Mattias Nordstrom Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965484 999156 Changes: dbench (4.0-2.1) unstable; urgency=low . * Non-maintainer upload. * Bump debhelper compat to 12. (Closes: #965484) * debian/rules: use dh. (Closes: #999156) * Port to DebSrc3.0 (quilt) Checksums-Sha1: d10d46d1c1e679cb7ee10c5d59fe36450b068a31 1708 dbench_4.0-2.1.dsc 8a683b28da85db689ada2ef0d90a15a4a57a403c 4260 dbench_4.0-2.1.debian.tar.xz 8a46267646bea209303f8816ee80cc1cfec0dde7 6798 dbench_4.0-2.1_source.buildinfo Checksums-Sha256: f8ee8ff5e2b912609f62753005eef89179a1984cfc0dccd170e28188e34873d0 1708 dbench_4.0-2.1.dsc fb01e8d8f5ab1c0c62c7ad1a8282045fa2fef143e4a82a73bc57f5730ce5b842 4260 dbench_4.0-2.1.debian.tar.xz fe997eec8478721f37e325b4e5914a83adf120cb5fe5eb3384b7cfda0caf6c1d 6798 dbench_4.0-2.1_source.buildinfo Files: f73c3e4ee3df800c78e3a1a113c1865a 1708 utils optional dbench_4.0-2.1.dsc 600a6d4a535f8d967472816253280122 4260 utils optional dbench_4.0-2.1.debian.tar.xz f769fb9bb6f009e953765c14dd40 6798 utils optional dbench_4.0-2.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgniwTHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiESpEACKs6timMCoy/29pErEtsT4QptUPT8R NsBV0xbWpa8X/ulp0UmmzPw/rNRK+2JrPWL/cVgxaIbE7f8NHZnzJbsxWR2WL1EM B4aBK1pn9cI5F5T1EaquJXr530rGpnriPHg23039kX2E81v7fasuymHiDPK0jngF swbnrQRyDgXVwOhQTrcW4bSSNKpHTBAP/OeFwdO3LdR54O6K552m1cgS6ihLU/tT nqzmRzVk1KXXYSw4hJuk/+q7E114VLUi6eVvas8rEPP4JBb0RdzUd+B14uoLD83o 7rbAcc34aMItfBkm2uoDNUSy4EoE1xhvuikxKv2nDiPA263fKk1+UeeWUXABNtWn xjbVCBPggWSEkPU/hqhi83ao7i5/bNrVvZGerhLftdeQUk0/eul7uZoAtOrUkRyO TiG+NhNDy2Iy1W3wpOq/0FMBW5KReVspHPtG9blhfCHavgJNiqiJwRJmZ0Bc6fhv rs6G3kMKVfMGCxv1f6LYlYzHkaRQQiYQj0HCy+FsahhHUSOHKtiBqSMTm2eX0KD9 FcXUANfE01doQp/b3j7gFpW/3uVmgisXoDZBqXsGwFM3nJsSTJOEo3Oiw6e91SZk UCU05JHmRMGaRhf/EzwFeKlOkQXjzJxChbXOliQj28OWMmTzkfDP6DIYG6SrH3qt +caj+vu8zSivBQ== =rPeH -END PGP SIGNATURE End Message ---
Bug#1011647: marked as done (RM: netsend -- RoQA, RC-buggy, dead-upstream, unmaintained, low popcon)
Your message dated Thu, 29 Dec 2022 18:43:52 + with message-id and subject line Bug#1011647: fixed in netsend 0.0~svnr250-1.5 has caused the Debian Bug report #1011647, regarding RM: netsend -- RoQA, RC-buggy, dead-upstream, unmaintained, low popcon 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.) -- 1011647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011647 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: netsend Severity: serious Justification: RoQA Dear Maintainer, netsend is de-facto unmaintained as simce 2009 only NMU happened. Upstream disappeared, (as berlios disappeared) and I could not find a new place upstream moved to. Appearantly, there was a newer upstream version than that in Debian, according to #587082 and this version might be lost. It has no reverse dependencies in Debian. It is currently RC buggy with those two bugs: #965747 [S|⛺| ] [src:netsend] netsend: Removal of obsolete debhelper compat 5 and 6 in bookworm #999046 [S| | ] [src:netsend] netsend: missing required debian/rules targets build-arch and/or build-indep I therefore propose to RM the package. If you disagree, just close this bug, but please show the package some love. Especially, it is in need of an human maintainer (refering to Policy 5.6.3) If you agree, reassign the bug to ftp.debian.org If there is no answer, I will reassing the bug in exactly 3 months to ftp.debian.org to make the RM happen. -- tobi --- End Message --- --- Begin Message --- Source: netsend Source-Version: 0.0~svnr250-1.5 Done: Ying-Chun Liu (PaulLiu) We believe that the bug you reported is fixed in the latest version of netsend, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ying-Chun Liu (PaulLiu) (supplier of updated netsend 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, 13 Dec 2022 07:24:55 +0800 Source: netsend Architecture: source Version: 0.0~svnr250-1.5 Distribution: unstable Urgency: low Maintainer: Martin Peylo Changed-By: Ying-Chun Liu (PaulLiu) Closes: 965747 999046 1011647 Changes: netsend (0.0~svnr250-1.5) unstable; urgency=low . * Non-maintainer upload. (Closes: #1011647) * Bump debhelper compat to 12 (Closes: #965747) * debian/rules: Use dh. (Closes: #999046) * Port to DebSrc3.0 (quilt). Checksums-Sha1: 0decd2ddfcae0a36afd7c242e6ace34259f9beb2 1789 netsend_0.0~svnr250-1.5.dsc 3b4b427641f2cd7e1d577ed2a860c09e01a4cfb4 3344 netsend_0.0~svnr250-1.5.debian.tar.xz 3c9c04f4e1b591ae6e76b68d309a4bd04bb06002 6777 netsend_0.0~svnr250-1.5_source.buildinfo Checksums-Sha256: 8657d6b6039b66114fb80890678906cf28655731e7fc84397d226348f7adc5bf 1789 netsend_0.0~svnr250-1.5.dsc 1a887c282ac7f69e0479bb22bdda899491e75120b475d98b8b0ea8914231618d 3344 netsend_0.0~svnr250-1.5.debian.tar.xz cdf2c2db6e43077eee46a935c18d9057bb545d1a771d5a485fe8a5d5e50196ba 6777 netsend_0.0~svnr250-1.5_source.buildinfo Files: de6a368919e1fb1337a02177aa9eefc7 1789 net optional netsend_0.0~svnr250-1.5.dsc a30ff293cb3a9979be714638fbc205d7 3344 net optional netsend_0.0~svnr250-1.5.debian.tar.xz 9692dc69312a2b2673a889b8aeb4ed9e 6777 net optional netsend_0.0~svnr250-1.5_source.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAmOgo2ITHHBhdWxsaXVA ZGViaWFuLm9yZwAKCRBEFz+hPQWIiMGsEAC3rQxZXZnXtfrZmReW7GA0SHzn+v/K NcbiV+Fv2iizMeL+e2hBDC0aG/RotaouzDGE2wwKYpIP/fzPLyDaBLc5FoU/R0b1 YR1Y4hVOL1OFgEOOxQ8LQZSWXiJAQYClY3C89BQeXjMbRMXWKZ4/DV4fvQLpWtqP jALQM+dVjStjz6hfhun8KFNUqMgZaCFX2zHfs1IEjNaDmg41iTd8Ecz5PU4yf55+ OdbolUPkS41YjtdgSZNi1fqdvXHah1eTg2yX1EBkgNpET0Z4Bp+MkUedUgPwWzTB q+JDxF13Ad+zkDVVVXiqs9yJc/S2OE6PJU/6a79tzRMJF9BE6XomhPUDZlAQoDjM YhNWX9JV/qJm0SNyhlFfai1apzR36zVA/OdgW7i0PG43+O8h3Yem1Y61QB4qlSNq q5UMGvutk5F5VUmM+RVyumrasbZ9P+00Oe8uSyrLqxYoIEDhs3i4IjgZS8YqevEW YKBfVMwYIr4N+1h14HDIncHEfdi86X0wyV2B942+cmdjZ2s4i6wYsElNfS1Wwj+1 nM915imuBdKqAwBN0Dia+iK6WBySALEMjDIXx1JMeI/F3MFcpoKj7pFQzDZTG2vm /njAdd7zScIxgczRP0B8WHSW2UtROdch9fFxKv84kvKr7/mAVimnZhVRBDrK4tl3 58NMhO2fqGkTNg== =ub6N -END PGP SIGNATURE End Message
Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"
Hello Andreas, Am 29.12.22 um 18:00 schrieb Andreas Metzler: (Ideally the cmake setup should check wxWidgets's EGL-status and set KICAD_USE_EGL accordingly instead of failing at build-time.) KiCad upstream did have the same idea some time ago and added a wishlist report against wxWidgets. https://github.com/wxWidgets/wxWidgets/issues/22325 But given the development dynamics of wxWidgets I do not expect a quick solution for this. -- Regards Carsten
Processed: tagging 1026705
Processing commands for cont...@bugs.debian.org: > tags 1026705 + pending Bug #1026705 [src:python-kajiki] python-pecan: FTBFS: E AttributeError: 'code' object has no attribute 'co_endlinetable' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1026705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026499: rows: FTBFS: AssertionError: Lists differ: [] != ['iso', '8859']
Dear Maintainer, After adding python3-magic to B-D (and d/t/control Depends), your package builds fine in my sid chroot environment. Kind Regards
Bug#1026055: marked as done (lapack breaks openturns autopkgtest: undefined reference to `ztrsyl3_' (and 3 more))
Your message dated Thu, 29 Dec 2022 18:18:27 +0100 with message-id and subject line Re: Bug#1026055: lapack breaks openturns autopkgtest: undefined reference to `ztrsyl3_' (and 3 more) has caused the Debian Bug report #1026055, regarding lapack breaks openturns autopkgtest: undefined reference to `ztrsyl3_' (and 3 more) 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.) -- 1026055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lapack, openturns Control: found -1 lapack/3.11.0-2 Control: found -1 openturns/1.20-5 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of lapack the autopkgtest of openturns fails in testing when that autopkgtest is run with the binary packages of lapack from unstable. It passes when run with only packages from testing. In tabular form: passfail lapack from testing3.11.0-2 openturns from testing1.20-5 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 lapack 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=lapack https://ci.debian.net/data/autopkgtest/testing/amd64/o/openturns/29301955/log.gz /usr/bin/ld: /lib/x86_64-linux-gnu/liblapacke.so.3: undefined reference to `ztrsyl3_' /usr/bin/ld: /lib/x86_64-linux-gnu/liblapacke.so.3: undefined reference to `ctrsyl3_' /usr/bin/ld: /lib/x86_64-linux-gnu/liblapacke.so.3: undefined reference to `dtrsyl3_' /usr/bin/ld: /lib/x86_64-linux-gnu/liblapacke.so.3: undefined reference to `strsyl3_' collect2: error: ld returned 1 exit status autopkgtest [01:16:06]: test cxx-Ceres-test OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Le vendredi 16 décembre 2022 à 18:41 +0100, Jochen Sprickerhof a écrit : > * Sébastien Villemot [2022-12-16 16:26]: > > In the current system, in which the BLAS and LAPACK implementation are > > decided through the alternatives system, it’s not possible to solve the > > problem through versioned provides. Because even if the dependency on > > the versioned provides is satisfied, this does not prevent another > > flavour of LAPACK (not satisfying the dependency) to be installed and > > selected through the alternatives system. > > I think those alternatives names would need to be per ABI version (of > the virtual package) anyhow. > > > So indeed the only clean way of solving this issue seems to forbid > > coinstallability of several BLAS or LAPACK flavours. But the latter is > > considered as a feature, not as a bug. I agree that using the > > alternatives system for a shared library is a bit ugly and does not > > play well with our tooling, but that’s a choice that was made long ago > > and it also brings some flexibility for the user (it’s easy to switch > > from one implementation to the other). > > Is ease of switching the only reason for using the alternatives system > here? The other obvious solution is to use conflicting packages. Having shared libraries not co-installable may be manageable, but having -dev packages not co-installable is going to create some trouble. > Maybe we should rethink this decision as it really does not play well > with our tooling and you could just as well use apt to switch the > implementation. If you think there is a technically superior solution to the statu quo, you should send a message to debian-science@l.d.o which is the proper place to discuss such a change. Also, since atlas 3.10.3-13 has migrated to testing, I’m closing the present bug. -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄ https://www.debian.org signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#1027086: marked as done (ruby-rest-client: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error:)
Your message dated Thu, 29 Dec 2022 17:25:14 +
with message-id
and subject line Bug#1027086: fixed in ruby-rest-client 2.1.0-3
has caused the Debian Bug report #1027086,
regarding ruby-rest-client: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error:
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1027086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rest-client
Version: 2.1.0-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-rest-client failed to build.
Relevant part of the build log (hopefully):
> Failure/Error:
>Request.execute(options.merge(
>:method => :head,
>:url => url,
>:headers => headers,
>:log => log), &(block || @block))
>
># received :execute with unexpected
> arguments
> expected: ({:headers=>{"X-Something"=>"1"}, :log=>nil,
> :method=>:head, :password=>"mypass", :url=>"http://some/resource;,
> :user=>"jane"}) (keyword arguments)
> got: ({:headers=>{"X-Something"=>"1"}, :log=>nil,
> :method=>:head, :password=>"mypass", :url=>"http://some/resource;,
> :user=>"jane"}) (options hash)
> # ./lib/restclient/resource.rb:60:in `head'
> # ./spec/unit/resource_spec.rb:16:in `block (3 levels) in (required)>'
>
> Finished in 0.90862 seconds (files took 0.46198 seconds to load)
> 286 examples, 8 failures
>
> Failed examples:
>
> rspec ./spec/unit/request_spec.rb:506 # RestClient::Request class method
> execute wraps constructor
> rspec ./spec/unit/resource_spec.rb:39 # RestClient::Resource Resource
> delegation overrides resource headers
> rspec ./spec/unit/resource_spec.rb:19 # RestClient::Resource Resource
> delegation POST
> rspec ./spec/unit/resource_spec.rb:29 # RestClient::Resource Resource
> delegation PATCH
> rspec ./spec/unit/resource_spec.rb:9 # RestClient::Resource Resource
> delegation GET
> rspec ./spec/unit/resource_spec.rb:24 # RestClient::Resource Resource
> delegation PUT
> rspec ./spec/unit/resource_spec.rb:34 # RestClient::Resource Resource
> delegation DELETE
> rspec ./spec/unit/resource_spec.rb:14 # RestClient::Resource Resource
> delegation HEAD
>
> Randomized with seed 8137
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
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
ruby-rest-client.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-rest-client
Source-Version: 2.1.0-3
Done: Lucas Nussbaum
We believe that the bug you reported is fixed in the latest version of
ruby-rest-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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lucas Nussbaum (supplier of updated ruby-rest-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: Thu, 29 Dec 2022 18:02:51 +0100
Source: ruby-rest-client
Architecture: source
Version: 2.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Lucas Nussbaum
Closes: 1027086
Changes:
ruby-rest-client (2.1.0-3) unstable; urgency=medium
.
* add patch 0005-fix-expectations-for-rspec-3.12.patch. Closes: #1027086
Checksums-Sha1:
cc8cb7c8205b169e143d6c485c1795350865f7a8 2185 ruby-rest-client_2.1.0-3.dsc
323b31f1c9c7388b70a2feacb24ca42f324a325d 8220
ruby-rest-client_2.1.0-3.debian.tar.xz
b2310a8d99d9e7cbc535052bb678e19029c00e3a 14038
Bug#1003767: marked as done (libyang: autopkgtest failure (and tests the src:libyang2 packages))
Your message dated Thu, 29 Dec 2022 17:13:28 + with message-id and subject line Bug#1027275: Removed package(s) from unstable has caused the Debian Bug report #1003767, regarding libyang: autopkgtest failure (and tests the src:libyang2 packages) 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.) -- 1003767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003767 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libyang Version: 1.0.225-1.1 Severity: serious Tags: bookworm sid https://ci.debian.net/data/autopkgtest/testing/amd64/liby/libyang/18315507/log.gz ... The following additional packages will be installed: libyang-tools libyang2 libyang2-tools The following NEW packages will be installed: libyang-tools libyang2 libyang2-tools 0 upgraded, 3 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 486 kB of archives. After this operation, 1,353 kB of additional disk space will be used. Get:1 http://deb.debian.org/debian unstable/main amd64 libyang2 amd64 2.0.112-6 [397 kB] Get:2 http://deb.debian.org/debian unstable/main amd64 libyang2-tools amd64 2.0.112-6 [80.8 kB] Get:3 http://deb.debian.org/debian unstable/main amd64 libyang-tools all 2.0.112-6 [8,136 B] ... autopkgtest [18:35:29]: test yanglint: [--- cp: cannot stat '/usr/share/doc/libyang-tools/examples/ietf-interfaces.yang': No such file or directory autopkgtest [18:35:29]: test yanglint: ---] autopkgtest [18:35:29]: test yanglint: - - - - - - - - - - results - - - - - - - - - - yanglint FAIL non-zero exit status 1 autopkgtest [18:35:29]: test yanglint: - - - - - - - - - - stderr - - - - - - - - - - cp: cannot stat '/usr/share/doc/libyang-tools/examples/ietf-interfaces.yang': No such file or directory autopkgtest [18:35:29]: summary yanglint FAIL non-zero exit status 1 --- End Message --- --- Begin Message --- Version: 1.0.225-1.1+rm Dear submitter, as the package libyang has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027275 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1003766: marked as done (libyang must stop building libyang-tools)
Your message dated Thu, 29 Dec 2022 17:13:28 + with message-id and subject line Bug#1027275: Removed package(s) from unstable has caused the Debian Bug report #1003766, regarding libyang must stop building libyang-tools 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.) -- 1003766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003766 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libyang Version: 1.0.225-1.1 Severity: serious yang-tools is now built by src:libyang2. --- End Message --- --- Begin Message --- Version: 1.0.225-1.1+rm Dear submitter, as the package libyang has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027275 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#999208: marked as done (phamm: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Thu, 29 Dec 2022 17:08:59 + with message-id and subject line Bug#1027274: Removed package(s) from unstable has caused the Debian Bug report #999208, regarding phamm: missing required debian/rules targets build-arch and/or build-indep 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.) -- 999208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phamm Version: 0.6.8-1 Severity: important Justification: Debian Policy section 4.9 Tags: bookworm sid User: debian...@lists.debian.org Usertags: missing-build-arch-indep Dear maintainer, Your package does not include build-arch and/or build-indep targets in debian/rules. This is required by Debian Policy section 4.9, since 2012. https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules Please note that this is also a sign that the packaging of this software could benefit from a refresh. For example, packages using 'dh' cannot be affected by this issue. This mass bug filing was discussed on debian-devel@ in https://lists.debian.org/debian-devel/2021/11/msg00052.html . The severity of this bug will be changed to 'serious' after a month. Best, Lucas --- End Message --- --- Begin Message --- Version: 0.6.8-1+rm Dear submitter, as the package phamm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027274 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#985673: marked as done (CVE-2020-15400)
Your message dated Thu, 29 Dec 2022 17:08:28 + with message-id and subject line Bug#1027269: Removed package(s) from unstable has caused the Debian Bug report #985673, regarding CVE-2020-15400 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.) -- 985673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cakephp Severity: important Tags: security X-Debbugs-Cc: Debian Security Team The XSS issue mentioned here was assigned CVE-2020-15400: https://bakery.cakephp.org/2020/04/18/cakephp_406_released.html cakephp in bullseye is quite old compared to upstream, is it still useful, should it be in bullseye? Cheers, Moritz --- End Message --- --- Begin Message --- Version: 2.10.24-2+rm Dear submitter, as the package cakephp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027269 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#965772: marked as done (phamm: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 17:08:59 + with message-id and subject line Bug#1027274: Removed package(s) from unstable has caused the Debian Bug report #965772, regarding phamm: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 965772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phamm Version: 0.6.8-1 Severity: normal Usertags: compat-5-6-removal Hi, The package phamm uses debhelper with a compat level of 5 or 6, which is deprecated and scheduled for removal[1]. Please bump the debhelper compat at your earliest convenience /outside the freeze/! * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads with compat bumps during the freeze. If there is any risk that the fix for this bug might not migrate to testing before 2021-01-01[3] then please postpone the fix until after the freeze. At the time of filing this bug, compat 5 and 6 are expected to be removed "some time during the development cycle of bookworm". Thanks, ~Niels [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html [2] https://release.debian.org/bullseye/FAQ.html [3] The choice of 2021-01-01 as a "deadline" is set before the actual freeze deadline to provide a safe cut off point for most people. Mind you, it is still your responsibility to ensure that the upload makes it into testing even if you upload before that date. --- End Message --- --- Begin Message --- Version: 0.6.8-1+rm Dear submitter, as the package phamm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027274 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#924731: marked as done (phamm: CVE-2018-20806: Reflected XSS in Phamm login page)
Your message dated Thu, 29 Dec 2022 17:08:59 + with message-id and subject line Bug#1027274: Removed package(s) from unstable has caused the Debian Bug report #924731, regarding phamm: CVE-2018-20806: Reflected XSS in Phamm login page 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.) -- 924731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: phamm Version: 0.6.5-1 Severity: grave Tags: security upstream Forwarded: https://github.com/lota/phamm/issues/24 Hi, The following vulnerability was published for phamm. CVE-2018-20806[0]: | Phamm (aka PHP LDAP Virtual Hosting Manager) 0.6.8 allows XSS via the | login page (the /public/main.php action parameter). If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2018-20806 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20806 [1] https://github.com/lota/phamm/issues/24 Regards, Salvatore --- End Message --- --- Begin Message --- Version: 0.6.8-1+rm Dear submitter, as the package phamm has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027274 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1026993: marked as done (cakephp -- seriously outdated branch)
Your message dated Thu, 29 Dec 2022 17:08:28 + with message-id and subject line Bug#1027269: Removed package(s) from unstable has caused the Debian Bug report #1026993, regarding cakephp -- seriously outdated branch 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.) -- 1026993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026993 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cakephp Version: 2.10.24-2 The 2.10 branch is unmaintained upstream. As there are currently no direct users in Debian and no maintainer for this library/framework, it would seem unwise shipping it in the next stable release. When a real maintainer shows up and updates the package, please close this bug. Chris --- End Message --- --- Begin Message --- Version: 2.10.24-2+rm Dear submitter, as the package cakephp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027269 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#974586: marked as done (loganalyzer: depends on php5 to use mysql db as a backend.)
Your message dated Thu, 29 Dec 2022 17:06:51 +
with message-id
and subject line Bug#1027178: Removed package(s) from unstable
has caused the Debian Bug report #974586,
regarding loganalyzer: depends on php5 to use mysql db as a backend.
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.)
--
974586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974586
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: loganalyzer
Version: 4.1.5+dfsg-2
Severity: important
Tags: upstream
Dear Maintainer,
Loganalyzer make use of mysql_*() functions that have been deprecated in
php5.5 and that are not available in php7 (current stable).
The problem have been solved upstream from the LogAnalyzer v4.1.6
(v4-stable) version.
ex:
PHP Fatal error: Uncaught Error: Call to undefined function mysql_select_db()
in /usr/share/loganalyzer/install.php:382\nStack trace:\n#0 {main}\n thrown in
/usr/share/loganalyzer/install.php on line 382, ...
Thanks
E.
--
GPG key: 4096R/5E0195FAF2133176 2010-10-19 Enrico Rossi
--- End Message ---
--- Begin Message ---
Version: 4.1.5+dfsg-2.1+rm
Dear submitter,
as the package loganalyzer has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1027178
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#771187: marked as done (primesense-nite-nonfree: Package broken because openni.org is gone)
Your message dated Thu, 29 Dec 2022 17:07:59 + with message-id and subject line Bug#1027184: Removed package(s) from unstable has caused the Debian Bug report #771187, regarding primesense-nite-nonfree: Package broken because openni.org is gone 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.) -- 771187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: primesense-nite-nonfree Severity: important Hi, primesense-nite-nonfree is trying to download the Nite binaries from openni.org, which is no longer available [1]. This makes this package unusable. I've found copies of the .tar.bz2 here: http://www.mira-project.org/downloads/3rdparty/bin-linux/, but I can't verify that they are correct. Still it would be great to have Nite in Debian. Cheers Jochen [1] http://lists.ros.org/lurker/message/20140226.220235.dd108524.en.html --- End Message --- --- Begin Message --- Version: 0.1.1+rm Dear submitter, as the package primesense-nite-nonfree has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027184 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1026853: marked as done (rust-svgdom: (build-)depends on old version of rust-roxmltree)
Your message dated Thu, 29 Dec 2022 17:05:28 + with message-id and subject line Bug#1027141: Removed package(s) from unstable has caused the Debian Bug report #1026853, regarding rust-svgdom: (build-)depends on old version of rust-roxmltree 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.) -- 1026853: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026853 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rust-svgdom Version: 0.18.0-2 Severity: serious svgdom depends on version 0.7 of the roxmltree crate. Debian sid now has version 0.16. I tried bumping the dependency but it fails to build with the following errors. error[E0599]: no method named `write_buf` found for struct `Document` in the current scope --> benches/parser.rs:45:21 | 45 | doc.write_buf( ouput_data); | ^ method not found in `Document` ... 52 | do_write!(write_small, "benches/small.svg"); | --- in this macro invocation | = note: this error originates in the macro `do_write` (in Nightly builds, run with -Z macro-backtrace for more info) error[E0599]: no method named `write_buf` found for struct `Document` in the current scope --> benches/parser.rs:45:21 | 45 | doc.write_buf( ouput_data); | ^ method not found in `Document` ... 53 | do_write!(write_medium, "benches/medium.svg"); | - in this macro invocation | = note: this error originates in the macro `do_write` (in Nightly builds, run with -Z macro-backtrace for more info) error[E0599]: no method named `write_buf` found for struct `Document` in the current scope --> benches/parser.rs:45:21 | 45 | doc.write_buf( ouput_data); | ^ method not found in `Document` ... 54 | do_write!(write_large, "benches/large.svg"); | --- in this macro invocation | = note: this error originates in the macro `do_write` (in Nightly builds, run with -Z macro-backtrace for more info) --- End Message --- --- Begin Message --- Version: 0.18.0-2+rm Dear submitter, as the package rust-svgdom has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027141 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1002966: marked as done (selfhtml: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 17:07:31 + with message-id and subject line Bug#1027181: Removed package(s) from unstable has caused the Debian Bug report #1002966, regarding selfhtml: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 1002966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002966 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: selfhtml Version: 8.1.2-1 Severity: serious Tags: sid bookworm User: nthyk...@master.debian.org Usertags: compat-5-6-removal Hi, The package selfhtml uses debhelper with a compat level of 5 or 6, which is no longer supported [1]. Please bump the debhelper compat at your earliest convenience * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum Thanks, Andreas [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html --- End Message --- --- Begin Message --- Version: 8.1.2-1+rm Dear submitter, as the package selfhtml has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027181 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1002887: marked as done (primesense-nite-nonfree: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Thu, 29 Dec 2022 17:07:59 + with message-id and subject line Bug#1027184: Removed package(s) from unstable has caused the Debian Bug report #1002887, regarding primesense-nite-nonfree: Removal of obsolete debhelper compat 5 and 6 in bookworm 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.) -- 1002887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: primesense-nite-nonfree Version: 0.1.1 Severity: serious Tags: sid bookworm User: nthyk...@master.debian.org Usertags: compat-5-6-removal Hi, The package primesense-nite-nonfree uses debhelper with a compat level of 5 or 6, which is no longer supported [1]. Please bump the debhelper compat at your earliest convenience * Compat 13 is recommended (supported in stable-backports) * Compat 7 is the bare minimum Thanks, Andreas [1] https://lists.debian.org/debian-devel/2020/07/msg00065.html --- End Message --- --- Begin Message --- Version: 0.1.1+rm Dear submitter, as the package primesense-nite-nonfree has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027184 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1016963: Please test u-boot for dreamplug jetson-tk1 Bananapi Cubieboard2 Cubietruck
On Wed, 2022-12-28 at 16:30 -0800, Vagrant Cascadian wrote: > jetson-tk1 testing: 2022.04+dfsg-2+b1 ok unstable: 2022.10+dfsg-2 ok exp: 2023.01~rc4+dfsg-1 ok > Bananapi I don't seem to have a working setup for this any more, sorry. > Cubieboard2 testing: 2022.04+dfsg-2+b1 ok unstable: 2022.10+dfsg-2 ok exp: 2023.01~rc4+dfsg-1 ok I mentioned those successes on the wiki.
Processed: Re: Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"
Processing control commands: > tags -1 patch Bug #1027137 [src:kicad] kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas" Added tag(s) patch. -- 1027137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027137: kicad: FTBFS: #error "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL canvas"
Control: tags -1 patch On 2022-12-28 Sebastian Ramacher wrote: > Source: kicad > Version: 6.0.10+dfsg-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > X-Debbugs-Cc: sramac...@debian.org > https://buildd.debian.org/status/fetch.php?pkg=kicad=amd64=6.0.10%2Bdfsg-1%2Bb2=1672197224=0 [...] > /<>/include/gal/opengl/kiglew.h:47:14: error: #error > "KICAD_USE_EGL can only be used when wxWidgets is compiled with the EGL > canvas" >47 | #error "KICAD_USE_EGL can only be used when wxWidgets is > compiled with the EGL canvas" > | ^ Hello, wxWidgets has recently switched back to non-EGL (See https://bugs.debian.org/1024147 and https://bugs.debian.org/1020640), for kicad the build error is trivially fixable by changing -DKICAD_USE_EGL=ON \ back to -DKICAD_USE_EGL=OFF \ (Ideally the cmake setup should check wxWidgets's EGL-status and set KICAD_USE_EGL accordingly instead of failing at build-time.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Processed: bug 1027114 is forwarded to https://github.com/moby/moby/issues/44698
Processing commands for cont...@bugs.debian.org: > forwarded 1027114 https://github.com/moby/moby/issues/44698 Bug #1027114 [src:docker.io] docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) Set Bug forwarded-to-address to 'https://github.com/moby/moby/issues/44698'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026612: marked as done (libdebug: FTBFS: log.c:557:16: error: ‘facilitynames’ undeclared (first use in this function); did you mean ‘facility’?)
Your message dated Thu, 29 Dec 2022 16:51:04 + with message-id and subject line Bug#1026612: fixed in libdebug 0.5.3-7 has caused the Debian Bug report #1026612, regarding libdebug: FTBFS: log.c:557:16: error: ‘facilitynames’ undeclared (first use in this function); did you mean ‘facility’? 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.) -- 1026612: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdebug Version: 0.5.3-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -pipe -Wall -W -Wbad-function-cast > -Wcast-align -Wcast-qual -Wchar-subscripts -Winline -Wmissing-prototypes > -Wnested-externs -Wpointer-arith -Wredundant-decls -Wshadow > -Wstrict-prototypes -Wwrite-strings -Wall -Wno-trigraphs -pipe > -fno-strict-aliasing -fno-common -Wall -Wno-trigraphs -pipe > -fno-strict-aliasing -fno-common -fPIC -Wall -Wno-trigraphs -pipe > -fno-strict-aliasing -fno-common -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/local/include -I./include -DGETHOSTBYNAME -DGETSERVBYNAME > -I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME > -I/usr/local/include -I../include -DGETHOSTBYNAME -DGETSERVBYNAME -c -o > hex.o hex.c > log.c: In function ‘log_open_syslog’: > log.c:557:16: error: ‘facilitynames’ undeclared (first use in this function); > did you mean ‘facility’? > 557 |for (i = 0; facilitynames[i].c_name != NULL; i++) > |^ > |facility > log.c:557:16: note: each undeclared identifier is reported only once for each > function it appears in > make[3]: *** [: log.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/libdebug_0.5.3-6_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results 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 mark 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: libdebug Source-Version: 0.5.3-7 Done: Peter Pentchev We believe that the bug you reported is fixed in the latest version of libdebug, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Pentchev (supplier of updated libdebug package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 29 Dec 2022 18:09:40 +0200 Source: libdebug Architecture: source Version: 0.5.3-7 Distribution: unstable Urgency: medium Maintainer: Peter Pentchev Changed-By: Peter Pentchev Closes: 1026612 Changes: libdebug (0.5.3-7) unstable; urgency=medium . * Fix a FTBFS with recent glibc versions that do not expose the facility names for the syslog(3) functions by default. Closes: #1026612 * Catch up with a Lintian tag format change. * Add the year 2022 to my debian/* copyright notice. * Declare compliance with Policy 4.6.2 with no changes. Checksums-Sha1: 19dfe7e9068b79fabe9470cac500d78bd78dd767 2301 libdebug_0.5.3-7.dsc 6e782695154eb1b9e287486acae811a03c0b706e 9324 libdebug_0.5.3-7.debian.tar.xz Checksums-Sha256: bd56ca7fed8738ba0a90aa18648f6da77587a6bb29425d0b926b2669e55828d9 2301 libdebug_0.5.3-7.dsc 0d420c97d7a4a156a6111247513a8750f1db40b3f76f655627d5b4c41185d8d7 9324 libdebug_0.5.3-7.debian.tar.xz
Bug#1026312: marked as done (Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson)
Your message dated Thu, 29 Dec 2022 16:52:06 + with message-id and subject line Bug#1026312: fixed in meson 1.0.0-1.1 has caused the Debian Bug report #1026312, regarding Setuptools 65.5.0-1.1 breaks installing Python modules/extensions via meson 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.) -- 1026312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: setuptools Version: 65.5.0-1.1 Severity: important Hello, thank you for maintaining setuptools! After the 65.5.0-1.1 update, installing Python modules and extensions via meson makes them end up in /usr/local instead of /usr. More details are in this debian-devel thread: https://lists.debian.org/debian-devel/2022/12/msg00152.html This currently breaks wreport and dballe, and xraylib when I try to build its Python extensions. Enrico Fun fact: unless I missed something in sources.debian.net, there seems to be nobody else but me maintaining Debian packages which install Python modules via meson. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: meson Source-Version: 1.0.0-1.1 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of meson, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated meson 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: Sat, 24 Dec 2022 11:22:03 -0400 Source: meson Architecture: source Version: 1.0.0-1.1 Distribution: unstable Urgency: medium Maintainer: Jussi Pakkanen Changed-By: Stefano Rivera Closes: 1026312 Changes: meson (1.0.0-1.1) unstable; urgency=medium . * Non-maintainer upload. * Patch: Correctly select the Debian python scheme with modern distutils. Closes: #1026312. Checksums-Sha1: 02594a1fe932d83c88a7de97fe18150e97281a6c 2873 meson_1.0.0-1.1.dsc adfe8aeafd20a5b18fb56134beb1b4b9561448ab 16252 meson_1.0.0-1.1.debian.tar.xz dd6d7dea5d69c22eab09959eae2671b8a82beeeb 13738 meson_1.0.0-1.1_source.buildinfo Checksums-Sha256: 91ed7b347787e70df4a3572a1e658450c64d5aa5b5aaa247184120d32e1e467a 2873 meson_1.0.0-1.1.dsc 2f25ad81d7f857f5cae15a0f69f643003c4d7c839fe850ed57fd0ac80c07aa4e 16252 meson_1.0.0-1.1.debian.tar.xz 319365d322ff91681c4daa1330b441803056c97855f21253c15f9a6e0de9fc04 13738 meson_1.0.0-1.1_source.buildinfo Files: e85e4498973c7cdd0decfdf5ce6fa497 2873 devel optional meson_1.0.0-1.1.dsc 26901503996abf0cd6a1637a34a7cda9 16252 devel optional meson_1.0.0-1.1.debian.tar.xz 44fc91f12d697d8d3046efae830c14b9 13738 devel optional meson_1.0.0-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY6cmNhQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2LXDAQCTMqrx2mLiK1gzBM7sksmbV80lKidZ WBxtupXNQ8IVBQEAgVJT/nKN9ZJ6QXK3Ju7R1C0E4/avQhijgOH0j++vxAw= =9lgO -END PGP SIGNATURE End Message ---
Bug#1027089: marked as done (ruby-simplecov: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Coverage.start(start_arguments))
Your message dated Thu, 29 Dec 2022 16:28:04 +
with message-id
and subject line Bug#1027089: fixed in ruby-simplecov 0.22.0-1
has caused the Debian Bug report #1027089,
regarding ruby-simplecov: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error: Coverage.start(start_arguments)
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.)
--
1027089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-simplecov
Version: 0.21.2-2
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-simplecov failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: Coverage.start(start_arguments)
>
>Coverage received :start with unexpected arguments
> expected: ({:branches=>true, :lines=>true}) (keyword arguments)
> got: ({:branches=>true, :lines=>true}) (options hash)
> # ./lib/simplecov.rb:354:in `start_coverage_with_criteria'
> # ./lib/simplecov.rb:343:in `start_coverage_measurement'
> # ./spec/simplecov_spec.rb:340:in `block (3 levels) in '
>
> Finished in 4.22 seconds (files took 0.19229 seconds to load)
> 385 examples, 2 failures
>
> Failed examples:
>
> rspec ./spec/simplecov_spec.rb:329 # SimpleCov.start_coverage_measurement
> starts coverage in lines mode by default
> rspec ./spec/simplecov_spec.rb:335 # SimpleCov.start_coverage_measurement
> starts coverage with lines and branches if branches is activated
>
> Randomized with seed 22418
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --exclude-pattern
> ./spec/default_formatter_spec.rb,./spec/gemspec_spec.rb --format
> documentation failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> mv test_projects/monorepo/.gem2deb.Gemfile.lock
> test_projects/monorepo/Gemfile.lock
> mv test_projects/parallel_tests/.gem2deb.Gemfile.lock
> test_projects/parallel_tests/Gemfile.lock
> mv test_projects/rails/rspec_rails/.gem2deb.Gemfile.lock
> test_projects/rails/rspec_rails/Gemfile.lock
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
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
ruby-simplecov.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-simplecov
Source-Version: 0.22.0-1
Done: Lucas Nussbaum
We believe that the bug you reported is fixed in the latest version of
ruby-simplecov, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lucas Nussbaum (supplier of updated ruby-simplecov package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 29 Dec 2022 15:52:50 +0100
Source: ruby-simplecov
Architecture: source
Version: 0.22.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Lucas Nussbaum
Closes: 1027089
Changes:
ruby-simplecov (0.22.0-1) unstable; urgency=medium
.
* Team upload.
* Fix debian/watch
* New upstream version 0.22.0
* Add patch 0003-fix-keywords-arg-vs-hash-for-rspec3.12-see-bug-10270.patch.
Closes: #1027089
* Refresh packaging using dh-make-ruby
* Add patch 0004-Fix-requires-so-that-they-work-inside-autopkgtest.patch
* Remove redundant entry in Build-Depends
Checksums-Sha1:
ed113d0803e08207f78acc7abaeeb81884835fe7 2126 ruby-simplecov_0.22.0-1.dsc
538719e849d5f60cddacb2cd440a013b59d7f73b 115236
ruby-simplecov_0.22.0.orig.tar.gz
4918b15c9de80a3b7a18c7438eb533a47048dcd1 5632
ruby-simplecov_0.22.0-1.debian.tar.xz
f031cfcdef75b8009dc04bdf8717e1c87b351f61 13874
ruby-simplecov_0.22.0-1_source.buildinfo
Bug#1026691: marked as done (bandit: FTBFS: TypeError: load() missing 1 required positional argument: 'Loader')
Your message dated Thu, 29 Dec 2022 16:19:48 + with message-id and subject line Bug#1026691: fixed in bandit 1.6.2-2 has caused the Debian Bug report #1026691, regarding bandit: FTBFS: TypeError: load() missing 1 required positional argument: 'Loader' 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.) -- 1026691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bandit Version: 1.6.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > make[1]: pyversions: No such file or directory > py3versions: no X-Python3-Version in control file, using supported versions > for i in 3.11 3.10 ; do \ > python3 setup.py install -f --install-layout=deb > --root=/<>/debian/tmp ; \ > done > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'description-file' will not be supported in future versions. > Please use the underscore name 'description_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'author-email' will not be supported in future versions. > Please use the underscore name 'author_email' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'home-page' will not be supported in future versions. Please > use the underscore name 'home_page' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/command/easy_install.py:146: > EasyInstallDeprecationWarning: easy_install command is deprecated. Use build > and pip and other standards-based tools. > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/command/install.py:34: > SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and > pip and other standards-based tools. > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'description-file' will not be supported in future versions. > Please use the underscore name 'description_file' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'author-email' will not be supported in future versions. > Please use the underscore name 'author_email' instead > warnings.warn( > /usr/lib/python3/dist-packages/setuptools/dist.py:771: UserWarning: Usage of > dash-separated 'home-page' will not be supported in future versions. Please > use the underscore name 'home_page' instead > warnings.warn( > running install > [pbr] Generating AUTHORS > [pbr] AUTHORS complete (0.0s) > running build > running build_py > creating build > creating build/lib > creating build/lib/bandit > creating build/lib/bandit/cli > copying bandit/cli/__init__.py -> build/lib/bandit/cli > copying bandit/cli/main.py -> build/lib/bandit/cli > copying bandit/cli/config_generator.py -> build/lib/bandit/cli > copying bandit/cli/baseline.py -> build/lib/bandit/cli > creating build/lib/bandit/blacklists > copying bandit/blacklists/__init__.py -> build/lib/bandit/blacklists > copying bandit/blacklists/imports.py -> build/lib/bandit/blacklists > copying bandit/blacklists/calls.py -> build/lib/bandit/blacklists > copying bandit/blacklists/utils.py -> build/lib/bandit/blacklists > creating build/lib/bandit/formatters > copying bandit/formatters/__init__.py -> build/lib/bandit/formatters > copying bandit/formatters/csv.py -> build/lib/bandit/formatters > copying bandit/formatters/screen.py -> build/lib/bandit/formatters > copying bandit/formatters/yaml.py -> build/lib/bandit/formatters > copying bandit/formatters/json.py -> build/lib/bandit/formatters > copying bandit/formatters/text.py -> build/lib/bandit/formatters > copying bandit/formatters/html.py -> build/lib/bandit/formatters > copying bandit/formatters/custom.py -> build/lib/bandit/formatters > copying bandit/formatters/xml.py -> build/lib/bandit/formatters > copying bandit/formatters/utils.py -> build/lib/bandit/formatters > copying bandit/__init__.py -> build/lib/bandit > copying bandit/__main__.py -> build/lib/bandit > creating build/lib/bandit/core > copying bandit/core/__init__.py -> build/lib/bandit/core > copying bandit/core/meta_ast.py -> build/lib/bandit/core > copying bandit/core/node_visitor.py -> build/lib/bandit/core
Bug#1026722: gst-python1.0: FTBFS: dh_install: error: missing files, aborting
usr/lib/python* in .install misses items that now are installed to /usr/local/lib/*. This is #1026312. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026312 -- Andreas Rönnquist gus...@debian.org
Processed: we're trying to remove vtk7
Processing commands for cont...@bugs.debian.org: > # the other vtk7 blocking bugs are already serious, this one seems to > # have been missed. > severity 1013190 serious Bug #1013190 [openems] openems: Migration from vtk7 to vtk9 Severity set to 'serious' from 'wishlist' > thanks Stopping processing here. Please contact me if you need assistance. -- 1013190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> unblock 1026598 by 1026588
Bug #1026598 [src:aardvark-dns] aardvark-dns: FTBFS: unsatisfiable
build-dependencies: librust-trust-dns-proto-0.21+backtrace-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-https-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-native-tls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-rustls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-openssl-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-ring-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+mdns-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~)
1026598 was blocked by: 1026588
1026598 was not blocking any bugs.
Removed blocking bug(s) of 1026598: 1026588
> reassign 1026598 src:rust-trust-dns-server
Bug #1026598 [src:aardvark-dns] aardvark-dns: FTBFS: unsatisfiable
build-dependencies: librust-trust-dns-proto-0.21+backtrace-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-https-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-native-tls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-rustls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-openssl-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-ring-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+mdns-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~)
Bug reassigned from package 'src:aardvark-dns' to 'src:rust-trust-dns-server'.
No longer marked as found in versions aardvark-dns/1.0.3-1.
Ignoring request to alter fixed versions of bug #1026598 to the same values
previously set
> forcemerge 1026588 1026598
Bug #1026588 {Done: Adrian Bunk } [src:rust-trust-dns-server]
rust-trust-dns-server: FTBFS: unsatisfiable build-dependencies:
librust-trust-dns-client-0.21+default-dev
Bug #1026598 [src:rust-trust-dns-server] aardvark-dns: FTBFS: unsatisfiable
build-dependencies: librust-trust-dns-proto-0.21+backtrace-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-https-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-native-tls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-rustls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-openssl-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-ring-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+mdns-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~)
Marked Bug as done
Marked as fixed in versions rust-trust-dns-server/0.22.0-1.
Marked as found in versions rust-trust-dns-server/0.21.2-1.
Added tag(s) pending.
Merged 1026588 1026598
> affects 1026588 src:aardvark-dns
Bug #1026588 {Done: Adrian Bunk } [src:rust-trust-dns-server]
rust-trust-dns-server: FTBFS: unsatisfiable build-dependencies:
librust-trust-dns-client-0.21+default-dev
Bug #1026598 {Done: Adrian Bunk } [src:rust-trust-dns-server]
aardvark-dns: FTBFS: unsatisfiable build-dependencies:
librust-trust-dns-proto-0.21+backtrace-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-https-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-native-tls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dns-over-rustls-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-openssl-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+dnssec-ring-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+mdns-dev (>= 0.21.1-~~),
librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~)
Added indication that 1026588 affects src:aardvark-dns
Added indication that 1026598 affects src:aardvark-dns
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1026588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026588
1026598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: closing 1026588
Processing commands for cont...@bugs.debian.org: > close 1026588 0.22.0-1 Bug #1026588 [src:rust-trust-dns-server] rust-trust-dns-server: FTBFS: unsatisfiable build-dependencies: librust-trust-dns-client-0.21+default-dev Marked as fixed in versions rust-trust-dns-server/0.22.0-1. Bug #1026588 [src:rust-trust-dns-server] rust-trust-dns-server: FTBFS: unsatisfiable build-dependencies: librust-trust-dns-client-0.21+default-dev Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1026588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026588 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026691: marked as pending in bandit
Control: tag -1 pending Hello, Bug #1026691 in bandit 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/openstack-team/libs/bandit/-/commit/3ddb817ef3cade29619ae995da65c50e657fcbae Add use-yaml.safe_load.patch fixing FTBFS (Closes: #1026691). (this message was generated automatically) -- Greetings https://bugs.debian.org/1026691
Processed: Bug#1026691 marked as pending in bandit
Processing control commands: > tag -1 pending Bug #1026691 [src:bandit] bandit: FTBFS: TypeError: load() missing 1 required positional argument: 'Loader' Added tag(s) pending. -- 1026691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026691 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016963: Please test with helping rpi_arm64
Hi, On 12/29/22 00:55, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze approaches, this is getting to be... worrysome! If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... rpi_arm64 Tested `rpi_arm64` target with RPi 3 B 1GB and RPi 4 B 2GB. Tested versions below are able to work with USB keyboard, serial, hdmi output and boot the target OS to graphical UI: - U-Boot 2022.04+dfsg-2+b1 (May 14 2022 - 19:14:13 +) - U-Boot 2022.10+dfsg-2 (Dec 23 2022 - 23:18:44 +) - U-Boot 2023.01-rc4+dfsg-1 (Dec 24 2022 - 03:13:23 +) With the version from stable -- no HDMI for RPi4, all works for RPi3: - U-Boot 2021.01+dfsg-5 (May 23 2021 - 04:32:45 +) PS Tested `rpi_arm64` boot with the daily image image from ApertisOS since it is using that target by default, have graphical UI and works both with RPi3 and RPi4, so it is convenient to compare the U-Boot itself. -- Denis Pynkin Senior Software Engineer Collabora Ltd. Platinum Building, St John's Innovation Park, Cambridge CB4 0DS, UK Registered in England & Wales, no. 5513718
Bug#1024239: libequihash: baseline violation on i386 and FTBFS on !x86
Thanks, after consulting with upstream this should be fixed in new upstream https://github.com/stef/equihash/archive/refs/tags/v1.0.3.tar.gz which has https://github.com/stef/equihash/commit/0806afadf99837519469449c55dc425763e8eef7 . I'll upload a new package soonishlish. Bye, Joost On Wed, Nov 16, 2022 at 11:37:01AM +0200, Adrian Bunk wrote: > Source: libequihash > Version: 1.0.2-3 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/fetch.php?pkg=libequihash=arm64=1.0.2-3=1668331092=0 > > ... > make[1]: Entering directory '/<>' > g++ -c -Wall -g -O3 -std=c++17 -fstack-protector-strong -D_FORTIFY_SOURCE=2 > -fasynchronous-unwind-tables -fpic -Werror=format-security -Wl,-z,defs > -Wl,-z,relro -ftrapv -Wl,-z,noexecstack -march=native > -fstack-clash-protection -fcf-protection=full -o equihash.o equihash.cc > cc1plus: error: ‘-fcf-protection=full’ is not supported for this target > make[1]: *** [Makefile:16: equihash.o] Error 1 > > > -fcf-protection=full is an x86-only option not supported on > other architectures. > > -fcf-protection=full violates the i386 baseline, > please use it only on amd64.
Processed: limit source to ruby-simplecov, tagging 1027089
Processing commands for cont...@bugs.debian.org: > limit source ruby-simplecov Limiting to bugs with field 'source' containing at least one of 'ruby-simplecov' Limit currently set to 'source':'ruby-simplecov' > tags 1027089 + pending Bug #1027089 [src:ruby-simplecov] ruby-simplecov: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Coverage.start(start_arguments) Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027089: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027089 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026588: Fix pending in the NEW queue
On Thu, Dec 29, 2022 at 08:03:06AM -0500, Reinhard Tartler wrote: >Dear ftp-master, happy holidays! >Any chance you could fast-track this package so that I can fix 2 RC >bugs? I'm concerned that if not fixed in time, aardvark-dns would be >removed from testing, which would break podman and friends. >Thanks in advance! Marked for ACCEPT. While reviewing it, it looks like you have patches that aren't in the series file; that's usually an oversight - worth taking a look at, but it's not impacting its suitability for the archive. paultag, for the ftpteam -- ⢀⣴⠾⠻⢶⣦⠀ Paul Tagliamonte ⣾⠁⢠⠒⠀⣿⡁ https://people.debian.org/~paultag | https://pault.ag/ ⢿⡄⠘⠷⠚⠋Debian, the universal operating system. ⠈⠳⣄⠀⠀ 4096R / FEF2 EB20 16E6 A856 B98C E820 2DCD 6B5D E858 ADF3 signature.asc Description: PGP signature
Bug#1016963: Help with testing u-boot!
On Thursday, 29 December 2022 04:33:51 CET Rick Thomas wrote: > Rebooting while watching the serial console output says "U-Boot SPL > 2016.05-rc2+dfsg0~20160423~1-1 (Apr 24 2016 - 04:24:21)" So the firmware > does not correspond to what aptitude says. The main difference with your other Cubox-i output is the 'SPL' part. I have no clue about Cubox-i, but on Rockchip/Pine64 devices you (often) can boot from SPI, eMMC and SDcard and its preference is also in that order. So if you have u-boot on SPI (flash), then it'll use that (if it also preferences SPI above others). Which likely means that you could also completely remove the u-boot packages and that has no effect on your ability to boot the device. If you want to try newer u-boot versions, then you need to find out how to either update u-boot in SPI or how to clear the contents of SPI, so it would 'fall back' on u-boot found somewhere else, like SDcard. HTH signature.asc Description: This is a digitally signed message part.
Bug#1016963: Please test u-boot for a64-olinuxino
On 2022-12-28 21:12, Vagrant Cascadian wrote: On 2022-12-28, Vagrant Cascadian wrote: On 2022-12-22, Vagrant Cascadian wrote: On 2022-08-20, Vagrant Cascadian wrote: On 2022-08-10, Vagrant Cascadian wrote: This bug is just to delay migration to testing while more platforms get tested. If you have a relevent board, please consider testing and reporting the status: https://wiki.debian.org/U-boot/Status I have not received many test results for current or even remotely recent u-boot platforms in Debian, and u-boot has been blocked from migration to testing partly because of this. As the bookworm freeze approaches, this is getting to be... worrysome! If you have access to any of these boards, please consider testing u-boot versions as packaged in debian for versions from debian stable (2021.01*), testing (2022.04*), unstable (2022.10*) and experimental (2023.01-rc*) and updating the wiki page if successful and/or replying to 1016...@bugs.debian.org with a positive confirmation... ...and if not successful, filing bugs against the relevent u-boot-* packages and marking them as blocking 1016963. a64-olinuxino Sadly my a64-olinuxino board has died and I'm no longer able to test it.
Bug#1027273: openvswitch: CVE-2022-4337 CVE-2022-4338
Source: openvswitch Version: 3.1.0~git20221212.739bcf2-3 Severity: grave Tags: security upstream Forwarded: https://github.com/openvswitch/ovs/pull/405 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for openvswitch. Filling as RC to make sure the fix can reach bookworm release. CVE-2022-4337[0]: | Out-of-Bounds Read in Organization Specific TLV CVE-2022-4338[1]: | Integer Underflow in Organization Specific TLV If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-4337 https://www.cve.org/CVERecord?id=CVE-2022-4337 [1] https://security-tracker.debian.org/tracker/CVE-2022-4338 https://www.cve.org/CVERecord?id=CVE-2022-4338 [2] https://github.com/openvswitch/ovs/pull/405 [3] https://mail.openvswitch.org/pipermail/ovs-dev/2022-December/400596.html [4] https://www.openwall.com/lists/oss-security/2022/12/20/2 Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#1027093: marked as done (ruby-thor: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: result = Thor::LineEditor.readline(message, options))
Your message dated Thu, 29 Dec 2022 13:04:56 +
with message-id
and subject line Bug#1027093: fixed in ruby-thor 1.2.1-2
has caused the Debian Bug report #1027093,
regarding ruby-thor: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed:
Failure/Error: result = Thor::LineEditor.readline(message, options)
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.)
--
1027093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-thor
Version: 1.2.1-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-thor failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: result = Thor::LineEditor.readline(message, options)
>
> Thor::LineEditor received :readline with unexpected arguments
> expected: ("Overwrite foo? (enter \"h\" for help) [Ynaqdhm] ",
> {:add_to_history=>false}) (keyword arguments)
>got: ("Overwrite foo? (enter \"h\" for help) [Ynaqdhm] ",
> {:add_to_history=>false}) (options hash)
> #
> /usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib/rspec/support.rb:102:in
> `block in '
> #
> /usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib/rspec/support.rb:111:in
> `notify_failure'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/error_generator.rb:348:in
> `notify'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/error_generator.rb:332:in
> `__raise'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/error_generator.rb:55:in
> `raise_unexpected_message_args_error'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/message_expectation.rb:555:in
> `raise_unexpected_message_args_error'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/proxy.rb:216:in
> `message_received'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/proxy.rb:360:in
> `message_received'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/method_double.rb:91:in
> `proxy_method_invoked'
> #
> /usr/share/rubygems-integration/all/gems/rspec-mocks-3.12.1/lib/rspec/mocks/method_double.rb:67:in
> `block (2 levels) in define_proxy_method'
> # ./lib/thor/shell/basic.rb:460:in `ask_simply'
> # ./lib/thor/shell/basic.rb:85:in `ask'
> # ./lib/thor/shell/basic.rb:290:in `block in file_collision'
> # ./lib/thor/shell/basic.rb:289:in `loop'
> # ./lib/thor/shell/basic.rb:289:in `file_collision'
> # ./spec/shell/basic_spec.rb:492:in `block (4 levels) in (required)>'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:263:in
> `instance_exec'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:263:in
> `block in run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:511:in
> `block in with_around_and_singleton_context_hooks'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:468:in
> `block in with_around_example_hooks'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/hooks.rb:486:in
> `block in run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/hooks.rb:624:in
> `run_around_example_hooks_for'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/hooks.rb:486:in
> `run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:468:in
> `with_around_example_hooks'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:511:in
> `with_around_and_singleton_context_hooks'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example.rb:259:in
> `run'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:646:in
> `block in run_examples'
> #
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib/rspec/core/example_group.rb:642:in
> `map'
> #
>
Processed: Fix pending in the NEW queue
Processing control commands: > tag 1026588 pending Bug #1026588 [src:rust-trust-dns-server] rust-trust-dns-server: FTBFS: unsatisfiable build-dependencies: librust-trust-dns-client-0.21+default-dev Added tag(s) pending. > block 1026598 by 1026588 Bug #1026598 [src:aardvark-dns] aardvark-dns: FTBFS: unsatisfiable build-dependencies: librust-trust-dns-proto-0.21+backtrace-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+dns-over-https-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+dns-over-native-tls-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+dns-over-rustls-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+dnssec-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+dnssec-openssl-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+dnssec-ring-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+mdns-dev (>= 0.21.1-~~), librust-trust-dns-proto-0.21+default-dev (>= 0.21.1-~~) 1026598 was not blocked by any bugs. 1026598 was not blocking any bugs. Added blocking bug(s) of 1026598: 1026588 -- 1026588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026588 1026598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026588: Fix pending in the NEW queue
Control: tag 1026588 pending Control: block 1026598 by 1026588 I really should have mentioned this bug in debian/changelog before uploading. It is currently pending at https://ftp-master.debian.org/new/rust-trust-dns-server_0.22.0-1.html Dear ftp-master, happy holidays! Any chance you could fast-track this package so that I can fix 2 RC bugs? I'm concerned that if not fixed in time, aardvark-dns would be removed from testing, which would break podman and friends. Thanks in advance! -- regards, Reinhard
Bug#1027186: marked as done (Need to insist on policy query for tainted objects check)
Your message dated Thu, 29 Dec 2022 12:49:00 + with message-id and subject line Bug#1027186: fixed in dgit 10.4 has caused the Debian Bug report #1027186, regarding Need to insist on policy query for tainted objects check 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.) -- 1027186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027186 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dgit Version; 10.3 Severity: serious Control: block 944855 by -1 As per the deployment plan in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944855#29 it would be best if dgit 10.3 didn't migrate to testing until the corresponding infrastructure has been deployed and tested in the live environment. Ian. -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter. --- End Message --- --- Begin Message --- Source: dgit Source-Version: 10.4 Done: Ian Jackson We believe that the bug you reported is fixed in the latest version of dgit, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson (supplier of updated dgit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 29 Dec 2022 11:51:50 + Source: dgit Architecture: source Version: 10.4 Distribution: unstable Urgency: medium Maintainer: Ian Jackson Changed-By: Ian Jackson Closes: 944855 1027186 Changes: dgit (10.4) unstable; urgency=medium . * Tainted object handling: Require policy-client-query to be supported when talking to the Debian server, so this check is now properly implemented rather than best-effort. Closes: #944855, #1027186. [Completes work prompted by report from Felipe Sateler.] * git-debrebase(1): Be less scary about --experimental-merge-resolution. Checksums-Sha1: 7fbd20169308dae7758dc30bc96ab2980a9adbf3 1856 dgit_10.4.dsc 41598d6fa0baafa9149585fe32d9d1fa1ee6bc67 681718 dgit_10.4.tar.gz Checksums-Sha256: 2608a3134db41a6e1354bb01fe4ce68f062b972848e7fb6eba56ef21a94fb365 1856 dgit_10.4.dsc 1898c5806b30d14f361f383ebd7d5863bca31af054bcf0eaf4e96a3f25eae3ec 681718 dgit_10.4.tar.gz Files: 092670efafe38784e49579742e9457e1 1856 devel optional dgit_10.4.dsc b8c47f2c25b8f353479039211b75eb8d 681718 devel optional dgit_10.4.tar.gz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmOtiEgACgkQ4+M5I0i1 DTmT6Af/SHL+l43lGenktn+ofiU3HAUdz8QwJcjv+NBb0DbY0f2RF2TZCAd8xr+5 VtVYiMfyk/yde32puBI9R/clAYjXM3hpGi7pWNZGP3BFexhHgyQVaRfwf8ww/Nv/ 6lNmlAWa7wV1y9Ue+hAiqX/I+vV22ntEd2qOga5uargFGvrQ2y4H7XTeOew6QVU4 UpIHvwUcbrZvi1e1hKObP7wtufu5pILqYcVMr54jLW0vIAL7i9ikEDLytFdF1aJe s7B/eD3PhPQKNcgk83MAh6KqbxS4zH0X/ksF5e2dwCuLFfR/NngPBg+3/kyMwBiG MeHWlTsBhhgQPXWV42ByXFw6ouQWig== =8nzM -END PGP SIGNATURE End Message ---
