Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On 1/9/22 00:56, Andres Salomon wrote: On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official build, so those DCHECKs shouldn't even be compiled in. It also supports wayland automatically, in case that's related to your slowdowns. https://salsa.debian.org/dilinger/chromium/-/tree/v97 I wanted to do this, but could it be that this version is for some reason taking much more space than the previous one? Here I have ~40 GB free, and v96 built just fine (though I wasn't looking when it was running), but now this failed already twice due to ENSPC. I'll try looking for someplace more spacy but it's odd :) Yeah, I think it's the debugging info; it's also breaking lld. It's a result of enabling official build, I'm working on it. In debian/rules, along with is_official_build=true, you can set symbol_level=#. With is_official_build=false (which is the way it used to build), it used level 0. The default for is_official_build=true is level 2, which results in a lot more space (it used 50gb on my last build) and also means I run out of ram linking the final chrome binary on my 8gb build machine. I'm not sure what we should use, as I'm not sure if 0 will break any of the dbgsym packaging yet. I'm currently trying a build with symbol_level=1. Fedora doesn't set it, and instead manually patches BUILD.gn to -g0. Ungoogled-chromium sets it to 1. Arch sets it to 0 if strip is set. Mint sets it to 0.
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On 1/8/22 15:57, Mattia Rizzolo wrote: On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: If you want to try with chromium 97; it now builds as an official build, so those DCHECKs shouldn't even be compiled in. It also supports wayland automatically, in case that's related to your slowdowns. https://salsa.debian.org/dilinger/chromium/-/tree/v97 I wanted to do this, but could it be that this version is for some reason taking much more space than the previous one? Here I have ~40 GB free, and v96 built just fine (though I wasn't looking when it was running), but now this failed already twice due to ENSPC. I'll try looking for someplace more spacy but it's odd :) Yeah, I think it's the debugging info; it's also breaking lld. It's a result of enabling official build, I'm working on it.
Bug#1000336: Upgrading tbb
Hi Mo, thanks a lot. I asked on IRC for priorisation of this package. Kind regards Andreas. Am Sat, Jan 08, 2022 at 08:30:57PM -0500 schrieb M. Zhou: > Hi all, > > The good news is that I managed to upgrade onetbb. It > is in the NEW queue now: > https://ftp-master.debian.org/new/onetbb_2021.4.0-1~exp1.html > All changes have been pushed onto salsa (master branch). > > SOVERSION was bumped from 2 to 12 so NEW is inevitable. > There are also some non-trivial API changes. So I guess the > transition won't be easy. > > On Wed, 2021-12-29 at 23:27 -0800, Diane Trout wrote: > On Thu, 2021-12-23 at 11:03 -0500, M. Zhou wrote: > > Hi all, > > > > I'm back. > > > > I've just finished my final exams so I could do something during > > the holiday. That TBB repository is still work-in-progress and > > FTBFS from the master branch is something expected. I will finalize > > it soon. Andreas said in previous posts that we prefer a faster > > NEW queue process. I understand that but we cannot bypass NEW > > process > > this time as upstream has bumped the SONAME. So I'm changing the > > source name as well following the upstream since NEW is inevitable. > > > > As for llvmlite, the latest upstream RC release v0.38.0rc1 seems > > to support python 3.10 . Should I upload the RC release? > > > > BTW, what else should I do? I've been out of sync from the mailing > > list for a long while. > > > Have you managed to make much progress? > > I fiddled with the packaging and got it to build and trying to run > the > autopkgtests with 2021.4.0-1 > > What'd help me is to have a package I could build locally and test > numba against. If you got it working could you commit what you have > to > a salsa branch and let me know where it is? > > Thanks, > Diane > > > > -- http://fam-tille.de
Bug#1000263: marked as done (causes tt-rss to break after php8 ugprade)
Your message dated Sun, 09 Jan 2022 03:33:37 +
with message-id
and subject line Bug#1000263: fixed in php-gettext 1.0.12-5
has caused the Debian Bug report #1000263,
regarding causes tt-rss to break after php8 ugprade
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.)
--
1000263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000263
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tt-rss
Version: 21~git20210204.b4cbc79+dfsg-1
Severity: serious
Since upgrade from php packages 7.4 to 8.1, tt-rss is unusable. Logs
contain several occurrences of:
[Sat Nov 20 17:11:06.950555 2021] [php:error] [pid 2895803] [client
127.0.0.1:40988] PHP Fatal error: Uncaught ValueError:
mb_convert_encoding(): Argument #2 ($to_encoding) must be a valid
encoding, "" given in
/usr/share/php/php-php-gettext/gettext.inc:181\nStack trace:\n#0
/usr/share/php/php-php-gettext/gettext.inc(181):
mb_convert_encoding()\n#1
/usr/share/php/php-php-gettext/gettext.inc(278): _encode()\n#2
/usr/share/php/php-php-gettext/gettext.inc(285): _gettext()\n#3
/usr/share/tt-rss/www/include/functions.php(102): __()\n#4
/usr/share/tt-rss/www/include/functions.php(141): get_translations()\n#5
/usr/share/tt-rss/www/classes/userhelper.php(124): startup_gettext()\n#6
/usr/share/tt-rss/www/index.php(31): UserHelper::login_sequence()\n#7
{main}\n thrown in /usr/share/php/php-php-gettext/gettext.inc on line 181
I'm not sure if the culprit is tt-rss or php-php-gettext package.
On https://www.php.net/manual/en/function.mb-convert-encoding.php:
8.0.0 mb_convert_encoding() will now throw a ValueError when
to_encoding is passed an invalid encoding.
So, it really is a misusage of mb_convert_encoding() either by tt-rss or
by php-php-gettext.
php-php-gettext: 1.0.12-4
--- End Message ---
--- Begin Message ---
Source: php-gettext
Source-Version: 1.0.12-5
Done: James Valleroy
We believe that the bug you reported is fixed in the latest version of
php-gettext, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1000...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
James Valleroy (supplier of updated php-gettext 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, 08 Jan 2022 21:29:33 -0500
Source: php-gettext
Architecture: source
Version: 1.0.12-5
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers
Changed-By: James Valleroy
Closes: 1000263
Changes:
php-gettext (1.0.12-5) unstable; urgency=medium
.
* Team upload.
* Use default_charset instead of mbstring.internal_encoding
(Closes: #1000263)
* Set Standards-Version to 4.6.0
Checksums-Sha1:
204149eb2803a2c1c65ed3f1b97be6c8d3b5f32f 2068 php-gettext_1.0.12-5.dsc
0b69efac6ef16ba49391971cf5a2e9687efd3b86 15016
php-gettext_1.0.12-5.debian.tar.xz
8ce7d044c9ed298fdd77e83f1592fa42ee137790 7762
php-gettext_1.0.12-5_amd64.buildinfo
Checksums-Sha256:
d947727f92e5ec4387548e36768e6cecd14762b0bc371b09dc4c997f93602d71 2068
php-gettext_1.0.12-5.dsc
0fa7724e49d538af303936bee324c574d35b505e7cb2f389961c2a3b5c7c7901 15016
php-gettext_1.0.12-5.debian.tar.xz
906920001d55d090d86329c4c25de355bd4909f8139759b6db90bee971e61a6f 7762
php-gettext_1.0.12-5_amd64.buildinfo
Files:
6b8585c66f03c6a9b7b1076b3d940df9 2068 php optional php-gettext_1.0.12-5.dsc
10678aedc0d96b8ed551cddb1b73e956 15016 php optional
php-gettext_1.0.12-5.debian.tar.xz
1e9f056b3bf94beaf7f80b85fe884024 7762 php optional
php-gettext_1.0.12-5_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJKBAEBCgA0FiEEfWrbdQ+RCFWJSEvmd8DHXntlCAgFAmHaUqQWHGp2YWxsZXJv
eUBtYWlsYm94Lm9yZwAKCRB3wMdee2UICPPpEACWtKs8GroAohbf6j23J1AkbQWf
Jby4jqVSZI0CMRqC8/vaPuoJ3nwYwAbo5ZP3bI6rmwuEYjNDWaY7V+DEcfaoqFYZ
Qoo0t3vnX2oARigTpmiA4OEfKOTM272RrUo7+DlXZwfD5SaMmnZjCHRbGBFXiJB2
mzcm1zywERomNhhlqm7JRa2j6oiBsE79KhI8mCKQwwiJ9MUvdE4TGaIvqhFdlLlX
aQ1R9avpdPVADq7Aww3Dq3kI2GrKQQ/uExznSioexKQ1iILhgdH4cMcCURHbM6i9
u2dDA6Tt3kDW5uKQTumkRLtNcL9X27yXl8IbWf0TCZQL3oD1Ty6yof/jMLA65NhM
6MnAptpcKxMe3hCrKjPpQ0jObYiDiZJM/ir5wUDgKrqQmJ2ObW9QNJaXsZq84iaJ
w7BMUCODJ6IiNIses8+BW4pgt5DiMAPrOyM+Hr588lV/2v0SeDgzIvETm4LBDMlC
t9ZhqE/seLN1
Bug#975238: marked as done (python-cement: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)
Your message dated Sun, 09 Jan 2022 02:52:31 +
with message-id
and subject line Bug#1003284: Removed package(s) from unstable
has caused the Debian Bug report #975238,
regarding python-cement: FTBFS: E: Build killed with signal TERM after 150
minutes of inactivity
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.)
--
975238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-cement
Version: 2.10.0-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
>
> Traceback (most recent call last):
> File
> "/<>/.pybuild/cpython3_3.9_cement/build/tests/ext/reload_config_tests.py",
> line 93, in test_signal_handling
> self.app.close()
> File
> "/<>/.pybuild/cpython3_3.9_cement/build/cement/core/foundation.py",
> line 950, in close
> for res in self.hook.run('pre_close', self):
> File
> "/<>/.pybuild/cpython3_3.9_cement/build/cement/core/hook.py",
> line 150, in run
> res = hook[2](*args, **kwargs)
> File
> "/<>/.pybuild/cpython3_3.9_cement/build/cement/ext/ext_reload_config.py",
> line 267, in kill_watcher
> if NOTIFIER.isAlive():
> AttributeError: 'ThreadedNotifier' object has no attribute 'isAlive'
>
> Ran 302 tests in 18.056s
>
> FAILED (SKIP=17, errors=3)
> E: Build killed with signal TERM after 150 minutes of inactivity
The full build log is available from:
http://qa-logs.debian.net/2020/11/19/python-cement_2.10.0-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Version: 2.10.0-2+rm
Dear submitter,
as the package python-cement 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/1003284
The version of this package that was in Debian prior to this removal
can still be found using http://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#954554: marked as done (python-asynctest: incompatible with Python 3.8)
Your message dated Sun, 09 Jan 2022 02:55:31 + with message-id and subject line Bug#1003364: Removed package(s) from unstable has caused the Debian Bug report #954554, regarding python-asynctest: incompatible with Python 3.8 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.) -- 954554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954554 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-asynctest Version: 0.13.0-4 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200321 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > python3 -m unittest --verbose test > test_exhaust_callbacks_cascading_callbacks (test.test_helpers.TestExhaust) > ... /<>/test/test_helpers.py:12: DeprecationWarning: The loop > argument is deprecated since Python 3.8, and scheduled for removal in Python > 3.10. > return (yield from asyncio.wait_for(coro, loop=self.loop, timeout=1)) > ok > test_exhaust_callbacks_nothing_to_wait (test.test_helpers.TestExhaust) ... ok > test_exhaust_callbacks_one_callback (test.test_helpers.TestExhaust) ... ok > test_CoroutineMock_inherits_from_Mock > (test.test_mock.TestMockInheritanceModel) ... ok > test_MagicMock_inherits_from_Mock (test.test_mock.TestMockInheritanceModel) > ... ok > test_MagicMock_is_not_CoroutineMock (test.test_mock.TestMockInheritanceModel) > ... ok > test_Mock_inherits_from_NonCallableMock > (test.test_mock.TestMockInheritanceModel) ... ok > test_Mock_is_not_CoroutineMock (test.test_mock.TestMockInheritanceModel) ... > ok > test_NonCallableMagicMock_inherits_from_NonCallableMock > (test.test_mock.TestMockInheritanceModel) ... ok > test_advance (test.test_case.Test_ClockedTestCase) ... ok > test_advance_with_run_until_complete (test.test_case.Test_ClockedTestCase) > ... ok > test_callbacks_are_called_on_time (test.test_case.Test_ClockedTestCase) ... ok > test_negative_advance (test.test_case.Test_ClockedTestCase) ... ok > test_setUp (test.test_case.Test_ClockedTestCase_async_setUp) ... ok > test_setUp (test.test_case.Test_ClockedTestCase_setUp) ... ok > test_asyncio_iscoroutinefunction (test.test_mock.Test_CoroutineMock) ... ok > test_called_CoroutineMock_returns_MagicMock > (test.test_mock.Test_CoroutineMock) ... > /<>/asynctest/mock.py:599: DeprecationWarning: "@coroutine" > decorator is deprecated since Python 3.8, use "async def" instead > def proxy(): > ok > test_exception_side_effect_raises_in_coroutine > (test.test_mock.Test_CoroutineMock) ... > /<>/asynctest/mock.py:594: DeprecationWarning: "@coroutine" > decorator is deprecated since Python 3.8, use "async def" instead > result = asyncio.coroutine(_raise)(e) > ok > test_mock_has_correct_name (test.test_mock.Test_CoroutineMock) ... ok > test_mock_returns_coroutine_according_to_spec > (test.test_mock.Test_CoroutineMock) ... ok > test_returns_coroutine (test.test_mock.Test_CoroutineMock) ... ok > test_returns_coroutine_from_return_value (test.test_mock.Test_CoroutineMock) > ... ok > test_returns_coroutine_from_side_effect (test.test_mock.Test_CoroutineMock) > ... ok > test_returns_coroutine_from_side_effect_being_a_coroutine > (test.test_mock.Test_CoroutineMock) ... > /<>/test/test_mock.py:176: DeprecationWarning: "@coroutine" > decorator is deprecated since Python 3.8, use "async def" instead > mock.side_effect = asyncio.coroutine(lambda: 'ProbeValue') > ok > test_returns_coroutine_from_side_effect_being_an_iterable > (test.test_mock.Test_CoroutineMock) ... ok > test_returns_coroutine_with_return_value_being_a_coroutine > (test.test_mock.Test_CoroutineMock) ... > /<>/test/test_mock.py:163: DeprecationWarning: "@coroutine" > decorator is deprecated since Python 3.8, use "async def" instead > coroutine = asyncio.coroutine(lambda: 'ProbeValue') > ok > test_assert_any_wait (test.test_mock.Test_CoroutineMock_awaited) ... ok > test_assert_awaited (test.test_mock.Test_CoroutineMock_awaited) ... ok > test_assert_awaited_once (test.test_mock.Test_CoroutineMock_awaited) ... ok > test_assert_awaited_once_with (test.test_mock.Test_CoroutineMock_awaited) ... > ok > test_assert_awaited_with (test.test_mock.Test_CoroutineMock_awaited) ... ok > test_assert_has_awaits (test.test_mock.Test_CoroutineMock_awaited) ... ok > test_assert_not_awaited (test.test_mock.Test_CoroutineMock_awaited) ... ok > test_await_args (test.test_mock.Test_CoroutineMock_awaited) ... ok > test_await_args_list (test.test_mock.Test_CoroutineMock_a
Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies
> I am eager to revert mistune (and therefore django-hyperkitty) back to > previous versions, and to open bugs against reverse deps, with new > uploads in experimental for both mistune and django-hyperkitty. this would be great indeed, thanks! > I consider a delay between bug opening and making them RC on the > reverse-deps of a month, which, added to the removal delay, means around > mid-march I'll probably reupload mistune 2.0.0 and django-hyperkitty in > unstable. from what i have seen, many of the downstream projects developers were rather surprised by the sudden release of a mistune 2.0 version, and they were uncertain how to move forward in a proper way, given the vast number of differences and incompatible changes. There also seems to be a complete lack of guidance from mistune upstream on how to port projects from 0.8.x to 2.x: do you think any effort will be spent by mistune upstream to provide any such documentation? without it, i'm afraid 1 month is not enough (anecdotally, the 2.x upload in unstable was a little more than a month ago, and i dont think any upstream project mas ported to it, so that should provide some guidance on how long to wait to make it RC) > Last but not least, do you have appropriate tooling to file bugs against > mistune reverse deps a bit more efficiently than "mail by mail"? `mass-bug` from devscripts -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Bug#1000336: Upgrading tbb
Hi all, The good news is that I managed to upgrade onetbb. It is in the NEW queue now: https://ftp-master.debian.org/new/onetbb_2021.4.0-1~exp1.html All changes have been pushed onto salsa (master branch). SOVERSION was bumped from 2 to 12 so NEW is inevitable. There are also some non-trivial API changes. So I guess the transition won't be easy. On Wed, 2021-12-29 at 23:27 -0800, Diane Trout wrote: On Thu, 2021-12-23 at 11:03 -0500, M. Zhou wrote: > Hi all, > > I'm back. > > I've just finished my final exams so I could do something during > the holiday. That TBB repository is still work-in-progress and > FTBFS from the master branch is something expected. I will finalize > it soon. Andreas said in previous posts that we prefer a faster > NEW queue process. I understand that but we cannot bypass NEW > process > this time as upstream has bumped the SONAME. So I'm changing the > source name as well following the upstream since NEW is inevitable. > > As for llvmlite, the latest upstream RC release v0.38.0rc1 seems > to support python 3.10 . Should I upload the RC release? > > BTW, what else should I do? I've been out of sync from the mailing > list for a long while. Have you managed to make much progress? I fiddled with the packaging and got it to build and trying to run the autopkgtests with 2021.4.0-1 What'd help me is to have a package I could build locally and test numba against. If you got it working could you commit what you have to a salsa branch and let me know where it is? Thanks, Diane
Processed: your mail
Processing commands for cont...@bugs.debian.org: > block 976811 by 1000263 Bug #976811 [release.debian.org] transition: php8.1 976811 was blocked by: 977337 1000619 980567 977389 1000650 1000647 977378 1002218 1002242 977379 977376 1000574 977388 977186 977340 977384 977401 1000653 977385 978151 977658 977377 977403 1000642 1002232 1000568 1000637 990322 1000596 978457 1002215 1000474 1000655 977400 977404 1003007 1002504 1000593 1000654 977687 977396 1002020 1000571 976811 was blocking: 1000585 977373 Added blocking bug(s) of 976811: 1000263 > thanks Stopping processing here. Please contact me if you need assistance. -- 976811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976811 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > retitle 1000263 causes tt-rss to break after php8 ugprade Bug #1000263 [php-php-gettext] package broken after php8 upgrade Changed Bug title to 'causes tt-rss to break after php8 ugprade' from 'package broken after php8 upgrade'. > owner 1000263 ! Bug #1000263 [php-php-gettext] causes tt-rss to break after php8 ugprade Owner recorded as James Valleroy . > thanks Stopping processing here. Please contact me if you need assistance. -- 1000263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): move 1000263 to php-php-gettext
Processing commands for cont...@bugs.debian.org: > reassign 1000263 php-php-gettext 1.0.12-4 Bug #1000263 [tt-rss] package broken after php8 upgrade Bug reassigned from package 'tt-rss' to 'php-php-gettext'. No longer marked as found in versions tt-rss/21~git20210204.b4cbc79+dfsg-1. Ignoring request to alter fixed versions of bug #1000263 to the same values previously set Bug #1000263 [php-php-gettext] package broken after php8 upgrade Marked as found in versions php-gettext/1.0.12-4. > retitle causes tt-rss to break after php8 ugprade Unknown command or malformed arguments to command. > owner ! Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On 2022-01-08 19:44, Laurent Bigonville wrote: On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that restriction or is it really broken with higher versions? They're conservative with their official releases. From scipy/pyproject.toml: "This to prevent that a future backwards-incompatible release will break the source build of a SciPy release.". It's more relevant for local user pip builds in a virtualenv, keeping the virtualenv constrained to known-good package versions. It's not so crucial for Debian since we maintain our own package self-consistency. In fact the upper bound is only applied upstream to the release versions. The development version has no upper bound (still set at "pybind11>=2.4.3") So it should be safe to remove the upper bound for us. It's a pity apt-rdepends doesn't support reverse build-dependencies yet, it would make it simpler to keep track of these things when testing new releases. Drew
Bug#954554: python-asynctest: FTBFS, maybe-RM
X-Debbugs-CC: jo...@jones.dk andrew.shad...@collabora.co.uk Hi, I just checked the condition in Debian Sid, and it looks like no package still depends or build-depends on package python3-asynctest. As a result, I am going to submit a RM bug to have this package removed soon. Thanks, Boyuan Yang On Mon, 29 Jun 2020 20:38:29 +0100 "Rebecca N. Palmer" wrote: > Is the above intended as a proposal to remove asynctest? > > The rdeps in Debian are hypercorn, python-aioresponses, and (for > autopkgtest only) python-fakeredis. > > hypercorn upstream have stopped using it: > https://gitlab.com/pgjones/hypercorn/-/commit/80e2ad5db107c42d42471ea64764d2b42202349c > > The other two still list it in upstream requirements*. In the case of > aioresponses, this has been reported as a bug, with no reply as yet: > https://github.com/pnuckowski/aioresponses/issues/162 > > Skipping the affected tests is probably an option, though obviously a > non-ideal one. signature.asc Description: This is a digitally signed message part
Bug#1001591: [Pkg-matrix-maintainers] Bug#1002380: drops attributes used by reverse dependencies
Jonas Smedegaard wrote on 22/12/2021 at 23:52:11+0100: > [[PGP Signed Part:No public key for 2C7C3146C1A00121 created at > 2021-12-22T23:52:06+0100 using RSA]] > Quoting Pierre-Elliott Bécue (2021-12-22 21:42:41) >> >> Jonas Smedegaard wrote on 22/12/2021 at 21:55:13+0100: >> >> > [[PGP Signed Part:No public key for 2C7C3146C1A00121 created at >> > 2021-12-22T21:55:09+0100 using RSA]] >> > Quoting Pierre-Elliott Bécue (2021-12-22 17:08:46) >> >> Jonas Smedegaard wrote on 22/12/2021 at >> >> 12:37:21+0100: >> >> > Releasing a new major release of mistune has caused several >> >> > packages to no longer be usable at all. >> >> > >> >> > I consider this a serious issue, and have raised severity >> >> > accordingly. >> >> > >> >> > At least python-m2r have no support for mistune v2 in sight (and >> >> > its newer fork - python-m2r2 - does not either). Concretely I >> >> > propose to revert this by a (messy) 2.0.0+really0.8.4 release >> >> > until reverse dependencies can use the newer major version of >> >> > mistune. >> >> > >> >> > It seems that a release of python3-django-hyperkitty requiring >> >> > mistune v2 has already been uploaded to unstable as well. That >> >> > is very unfortunate, and will need to be rolled back as well. >> >> > Mailman maintainers cc'ed. >> >> > >> >> > Please in future make sure to check reverse dependencies *before* >> >> > releasing a major new upstream release to unstable, because >> >> > reversal is messy (complicates package versioning). >> >> > >> >> > >> >> > Kind regards, and thanks for maintaining mistune, >> >> >> >> The issue is that many reverse dependencies of mistune are not >> >> maintained. >> > >> > I assume (in good faith) that you did not mean to say that the >> > _Debian_ packages reverse depending on mistune are all unmaintained. >> >> I'm not sure that there is anything to assume. I wrote "many reverse >> dependencies of mistune are not maintained", and making it mean "the >> _Debian_ packages reverse depending on mistune are all unmaintained" >> would require some hard work. >> >> > Please note that I did not propose to wait until _upstreams_ of >> > reverse dependencies can use newer major version of mistune. >> >> Well, I was under the impression that >> >> >>> Concretely I propose to revert this by a (messy) 2.0.0+really0.8.4 >> >>> release until reverse dependencies can use the newer major version >> >>> of mistune. >> >> meant indeed to wait until the reverse dependencies were sorted out >> which generally requires to wait until upstream fixes the issue >> (except if one likes big quilt patches and maintaining the software's >> code on their own). > > That is precisely what I did *not* imply (so it seems it was good that I > mentioned my non-assumption since apparently you _did_ assume stuff). > > Let me try avoid false assumptions by expanding: > > I propose to revert this by a (messy) 2.0.0+really0.8.4 release until > reverse dependencies somehow (with or without upstream cooperation) can > use the newer major version of mistune (or, if taking unreasonably long, > kick any reverse dependencies from testing). > > >> > My proposal is to *collaborate* with your peers in Debian now - not >> > continue(!) to make choices without coordination with those packages >> > directly affected by those choices. >> >> Maybe you wanted to suggest that I should *collaborate* more, but you >> did not write that and, as I tend to try not to assume what one says, >> writes or means, I did not read that. > > Sorry! > > I did indeed mean to encourage more collaboration, and apologize if that > failed to get across. > > >> >> If I follow your opinion on this, the following issues arise: >> >> >> >> 1. There is no proper way for software to be mistune 0.8.4 and >> >> mistune 2.0.0 compatible at the same way, so the reverse >> >> dependencies won't be able to update without mistune 2.0.0 >> >> being in unstable >> > >> > Not sure what you imply by "proper". >> >> appropriate, suitable, relevant, reasonable, … >> >> > There are alternatives to abruptly abandoning support for existing >> > functionaling packages already in Debian testing. >> >> Note that since the upload, autopkgtests for the involved >> reverse-dependencies were failing and therefore mistune was not >> planned to migrate from unstable to testing. There was therefore no >> chance mistune would break these packages in testing, and I was not >> pressing anyone to sort that out. >> >> Now that a serious bug against mistune is opened, even if these >> autopkgtests get sorted out because these very reverse-dependencies >> are updated, mistune will not migrate anyway (which will prevent to >> break other reverse-dependencies). > > Yes, I am aware, and that is what I describe as "abruptly": Now that > mistune v1 is gone, there is no way to work on any package depending on > that except for switching to v2. > > ...which is the reason I
Processed: Re: vip-manager: test failure with some network configurations
Processing control commands: > severity -1 serious Bug #993620 [vip-manager] vip-manager: test failure with some network configurations Severity set to 'serious' from 'normal' -- 993620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Thu, Jan 06, 2022 at 02:55:20AM -0500, Andres Salomon wrote: > If you want to try with chromium 97; it now builds as an official build, so > those DCHECKs shouldn't even be compiled in. It also supports wayland > automatically, in case that's related to your slowdowns. > > https://salsa.debian.org/dilinger/chromium/-/tree/v97 I wanted to do this, but could it be that this version is for some reason taking much more space than the previous one? Here I have ~40 GB free, and v96 built just fine (though I wasn't looking when it was running), but now this failed already twice due to ENSPC. I'll try looking for someplace more spacy but it's odd :) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#995212: chromium: Update to version 94.0.4606.61 (security-fixes)
On Fri, Jan 07, 2022 at 06:34:06AM -0300, Leandro Cunha wrote: > > > I also haven't heard from anyone on the chromium team yet - should I > > > add myself as an uploader and do a normal (non-NMU) upload? Do any of > > > them care? > > > > Without hearing from them, adding yourself to Uploaders would be > > inappropriate. > > If there is no response from someone on the team and someone wants to continue > the work, how is it done? I was thinking about it when I read this email. https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#non-maintainer-uploads-nmus https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging Plus, I suppose, the technical committee has the power to enforce maintainer changes (though I don't think this has been used in… at least a decade?). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: Re: downgrading severity
Processing control commands: > severity -1 serious Bug #1001668 [src:timew] timew: autopkgtest failure on ppc64el Severity set to 'serious' from 'normal' -- 1001668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001668 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1002326: python-schema-salad: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13]
Control: blocked -1 by 1001591
- Weitergeleitete Nachricht von Sandro Tosi -
Date: Fri, 7 Jan 2022 21:01:30 -0500
From: Sandro Tosi
To: Andreas Tille , 1002...@bugs.debian.org
Cc: "Michael R. Crusoe"
Subject: Re: Bug#1002326: python-schema-salad: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned
exit code 13
another victim of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001591
--
http://fam-tille.de
Bug#984058: marked as done (igraph: ftbfs with GCC-11)
Your message dated Sat, 8 Jan 2022 21:03:43 +0100 with message-id <742e4b31-4523-c045-22fd-824139d83...@rezozer.net> and subject line igraph: ftbfs with GCC-11: fixed has caused the Debian Bug report #984058, regarding igraph: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984058 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:igraph Version: 0.8.5+ds1-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/igraph_0.8.5+ds1-1_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] Thread-safety tests 247: Simple error handling test :skipped (mt.at:26) 248: Thread-safe ARPACK: skipped (mt.at:31) Spectral coarse graining 249: Solving the SCG problem (igraph_scg_grouping) : ok 250: Solving the SCG problem, adjacency matrix (igraph_scg_grouping) : ok 251: Solving the SCG problem, stochastic matrix (igraph_scg_grouping) : ok 252: Solving the SCG problem, laplacian matrix (igraph_scg_grouping) : ok 253: SCG semi-projectors, symmetric (igraph_scg_semiprojectors) : ok 254: SCG semi-projectors, stochastic (igraph_scg_semiprojectors) : ok 255: SCG semi-projectors, laplacian (igraph_scg_semiprojectors) : ok 256: SCG of a graph, adjacency matrix (igraph_scg) : ok 257: SCG of a graph, stochastic matrix (igraph_scg) : ok 258: SCG of a graph, laplacian matrix (igraph_scg) : ok Random number generators 259: Random seed:ok 260: RNG reproducibility:ok 261: MT19937 RNG on 64 bit machines: ok 262: Exponentially distributed random numbers: ok 263: Random sampling from consecutive sequence: ok 264: Fisher-Yates shuffle: ok Quick sort 265: Regular qsort (igraph_qsort): ok 266: qsort with extra argument (igraph_qsort_r): ok Maximum matchings 267: Maximum bipartite matching (igraph_maximum_bipartite_matching): ok Embeddings 268: Adjacency spectral embedding (igraph_adjacency_spectral_embedding): ok ## - ## ## Test results. ## ## - ## ERROR: 266 tests were run, 9 failed unexpectedly. 2 tests were skipped. ## -- ## ## testsuite.log was created. ## ## -- ## Please send `tests/testsuite.log' and all information you think might help: To: Subject: [igraph 0.8.5] testsuite: 65 69 77 85 166 178 189 199 231 failed You may investigate any problem if you feel able to do so, in which case the test suite provides a good starting point. Its output may be found below `tests/testsuite.dir'. make[3]: *** [Makefile:503: check-local] Error 1 make[3]: Leaving directory '/<>/_build/tests' make[2]: *** [Makefile:366: check-am] Error 2 make[2]: Leaving directory '/<>/_build/tests' make[1]: *** [Makefile:499: check-recursive] Error 1 make[1]: Leaving directory '/<>/_build' dh_auto_test: error: cd _build && make -j4 check VERBOSE=1 returned exit code 2 make: *** [debian/rules:8: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subproces
Processed: src:view3dscene: fails to migrate to testing for too long: FTBFS on armel
Processing control commands:
> close -1 4.0.0-2
Bug #1003357 [src:view3dscene] src:view3dscene: fails to migrate to testing for
too long: FTBFS on armel
Marked as fixed in versions view3dscene/4.0.0-2.
Bug #1003357 [src:view3dscene] src:view3dscene: fails to migrate to testing for
too long: FTBFS on armel
Marked Bug as done
> block -1 by 1002961
Bug #1003357 {Done: Paul Gevers } [src:view3dscene]
src:view3dscene: fails to migrate to testing for too long: FTBFS on armel
1003357 was not blocked by any bugs.
1003357 was not blocking any bugs.
Added blocking bug(s) of 1003357: 1002961
--
1003357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1003357: src:view3dscene: fails to migrate to testing for too long: FTBFS on armel
Source: view3dscene Version: 3.18.0-4 Severity: serious Control: close -1 4.0.0-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1002961 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:view3dscene has been trying to migrate for 62 days [2]. Hence, I am filing this bug. (Yes, I know this is due to cge being unable to rebuild *and* the fpc transition). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=view3dscene OpenPGP_signature Description: OpenPGP digital signature
Bug#999249: Package will now be considered for auto-removal
Hello! On 1/8/22 20:35, Graham Inggs wrote: > The release team no longer [1] considers popcon a criterion for > inclusion in the list of key packages [2]. > > This email is a courtesy reminder of this bug, and should prevent > instant auto-removal once the rule is changed in britney. discover has an installation count of nearly 200.000. Do we really remove a package that is being installed on so many machines? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Bug#1003354: src:jupyter-client: fails to migrate to testing for too long: autopkgtest regression
Source: jupyter-client Version: 6.1.12-1 Severity: serious Control: close -1 7.1.0-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1000271 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:jupyter-client has been trying to migrate for 62 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=jupyter-client OpenPGP_signature Description: OpenPGP digital signature
Processed: src:jupyter-client: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 7.1.0-1
Bug #1003354 [src:jupyter-client] src:jupyter-client: fails to migrate to
testing for too long: autopkgtest regression
Marked as fixed in versions jupyter-client/7.1.0-1.
Bug #1003354 [src:jupyter-client] src:jupyter-client: fails to migrate to
testing for too long: autopkgtest regression
Marked Bug as done
> block -1 by 1000271
Bug #1003354 {Done: Paul Gevers } [src:jupyter-client]
src:jupyter-client: fails to migrate to testing for too long: autopkgtest
regression
1003354 was not blocked by any bugs.
1003354 was not blocking any bugs.
Added blocking bug(s) of 1003354: 1000271
--
1003354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003354
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002521: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#999730: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#1002192: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#1002360: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#1002143: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#1001841: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#1000896: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#998516: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#999249: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#999037: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#998999: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#997763: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#997652: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#997601: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#997406: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#997287: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#997367: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#997194: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#993882: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#993716: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#993350: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#993033: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#991541: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#991449: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#984953: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#984714: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#984272: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#984366: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#978926: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#971783: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#965613: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#965865: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#965883: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#948739: Package will now be considered for auto-removal
Hi Maintainer The release team no longer [1] considers popcon a criterion for inclusion in the list of key packages [2]. This email is a courtesy reminder of this bug, and should prevent instant auto-removal once the rule is changed in britney. Regards Graham [1] http://meetbot.debian.net/debian-release/2021/debian-release.2021-01-27-19.07.html [2] https://udd.debian.org/cgi-bin/key_packages.yaml.cgi
Bug#1002065: scipy build-depenencies unsatisfiable in testing/unstable
On Tue, 21 Dec 2021 11:09:02 + Peter Michael Green wrote: > scipy build-depends on python3-pybind11 (<< 2.8) but testing and unstable > have version 2.8.1-3 FTR, the package builds fine with python3-pybind11 2.9 Could you drop that restriction or is it really broken with higher versions? Kind regards, Laurent Bigonville
Processed: reassign 1002065 to src:scipy, merging 1002065 1002144
Processing commands for cont...@bugs.debian.org: > reassign 1002065 src:scipy Bug #1002065 [scipy] scipy build-depenencies unsatisfiable in testing/unstable Bug reassigned from package 'scipy' to 'src:scipy'. No longer marked as found in versions 1.7.1-2. Ignoring request to alter fixed versions of bug #1002065 to the same values previously set > merge 1002065 1002144 Bug #1002065 [src:scipy] scipy build-depenencies unsatisfiable in testing/unstable Bug #1002065 [src:scipy] scipy build-depenencies unsatisfiable in testing/unstable Marked as found in versions scipy/1.7.1-2. Added tag(s) ftbfs, bookworm, and sid. Bug #1002144 [src:scipy] scipy: FTBFS: unsatisfiable build-dependency: python3-pybind11 (< 2.8) but 2.8.1-3 is to be installed Merged 1002065 1002144 > thanks Stopping processing here. Please contact me if you need assistance. -- 1002065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002065 1002144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): merging 1002065 1002144
Processing commands for cont...@bugs.debian.org: > merge 1002065 1002144 Bug #1002065 [scipy] scipy build-depenencies unsatisfiable in testing/unstable Unable to merge bugs because: package of #1002144 is 'src:scipy' not 'scipy' Failed to merge 1002065: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1002065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002065 1002144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:android-platform-dalvik: fails to migrate to testing for too long: uploader built arch:all binaries
Processing control commands: > close -1 10.0.0+r36-2 Bug #1003347 [src:android-platform-dalvik] src:android-platform-dalvik: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions android-platform-dalvik/10.0.0+r36-2. Bug #1003347 [src:android-platform-dalvik] src:android-platform-dalvik: fails to migrate to testing for too long: uploader built arch:all binaries Marked Bug as done -- 1003347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003347 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003347: src:android-platform-dalvik: fails to migrate to testing for too long: uploader built arch:all binaries
Source: android-platform-dalvik Version: 10.0.0+r36-1 Severity: serious Control: close -1 10.0.0+r36-2 Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:android-platform-dalvik has been trying to migrate for 63 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=android-platform-dalvik OpenPGP_signature Description: OpenPGP digital signature
Bug#1003345: ruby-sqlite3: FTBFS with SQLite3 3.37.0+
Source: ruby-sqlite3
Version: 1.4.2-3
Severity: serious
Tags: patch
Hi,
SQLite3 3.37.0 and onwards changed its inner working. Now table column
data types are stored as a value and always returned as uppercase
text. This breaks your package as it relies on the old behavior, when
this was stored as text and returned in a case it was defined.
As I broke it, I've created a fix for you, patch is attached.
Sorry for the inconvenience,
Laszlo/GCS
Description: SQLite3 3.37.0+ use uppercase column tupe names
Starting with SQLite3 3.37.0 it stores column type names as a value and
always displayed in uppercase letters.
Previously it stored type names as text with the same case as it was given.
This breaks testing where the column type is defined in lowercase and
expects it to be given back as-is.
Fix this with using type names in uppercase.
Author: Laszlo Boszormenyi (GCS)
Forwarded: no
Last-Update: 2022-01-08
---
--- ruby-sqlite3-1.4.2.orig/test/test_database.rb
+++ ruby-sqlite3-1.4.2/test/test_database.rb
@@ -268,12 +268,12 @@ module SQLite3
def test_table_info
db = SQLite3::Database.new(':memory:', :results_as_hash => true)
- db.execute("create table foo ( a integer primary key, b text )")
+ db.execute("create table foo ( a INTEGER primary key, b TEXT )")
info = [{
"name" => "a",
"pk" => 1,
"notnull"=> 0,
-"type" => "integer",
+"type" => "INTEGER",
"dflt_value" => nil,
"cid"=> 0
},
@@ -281,7 +281,7 @@ module SQLite3
"name" => "b",
"pk" => 0,
"notnull"=> 0,
-"type" => "text",
+"type" => "TEXT",
"dflt_value" => nil,
"cid"=> 1
}]
--- ruby-sqlite3-1.4.2.orig/test/test_integration.rb
+++ ruby-sqlite3-1.4.2/test/test_integration.rb
@@ -34,11 +34,11 @@ class TC_Database_Integration < SQLite3:
def test_table_info_without_defaults_for_version_3_3_8_and_higher
@db.transaction do
- @db.execute "create table no_defaults_test ( a integer default 1, b integer )"
+ @db.execute "create table no_defaults_test ( a INTEGER default 1, b INTEGER )"
data = @db.table_info( "no_defaults_test" )
- assert_equal({"name" => "a", "type" => "integer", "dflt_value" => "1", "notnull" => 0, "cid" => 0, "pk" => 0},
+ assert_equal({"name" => "a", "type" => "INTEGER", "dflt_value" => "1", "notnull" => 0, "cid" => 0, "pk" => 0},
data[0])
- assert_equal({"name" => "b", "type" => "integer", "dflt_value" => nil, "notnull" => 0, "cid" => 1, "pk" => 0},
+ assert_equal({"name" => "b", "type" => "INTEGER", "dflt_value" => nil, "notnull" => 0, "cid" => 1, "pk" => 0},
data[1])
end
end
--- ruby-sqlite3-1.4.2.orig/test/test_integration_resultset.rb
+++ ruby-sqlite3-1.4.2/test/test_integration_resultset.rb
@@ -4,7 +4,7 @@ class TC_ResultSet < SQLite3::TestCase
def setup
@db = SQLite3::Database.new(":memory:")
@db.transaction do
- @db.execute "create table foo ( a integer primary key, b text )"
+ @db.execute "create table foo ( a INTEGER primary key, b TEXT )"
@db.execute "insert into foo ( b ) values ( 'foo' )"
@db.execute "insert into foo ( b ) values ( 'bar' )"
@db.execute "insert into foo ( b ) values ( 'baz' )"
@@ -118,7 +118,7 @@ class TC_ResultSet < SQLite3::TestCase
end
def test_types
-assert_equal [ "integer", "text" ], @result.types
+assert_equal [ "INTEGER", "TEXT" ], @result.types
end
def test_columns
Bug#1003344: restfuldb: FTBFS with SQLite3 3.37.0+
Source: restfuldb
Version: 0.15.2+dfsg-2
Severity: serious
Tags: patch
Hi,
SQLite3 3.37.0 and onwards changed its inner working. Now table column
data types are stored as a value and always returned as uppercase
text. This breaks your package as it relies on the old behavior, when
this was stored as text and returned in a case it was defined.
As I broke it, I've created a fix for you, patch is attached. Couldn't
make it work with older SQLite3 versions thus you will need to build
depend on SQLite3 3.37.0 and newer.
Sorry for the inconvenience,
Laszlo/GCS
Description: SQLite3 3.37.0+ use uppercase column tupe names
Starting with SQLite3 3.37.0 it stores column type names as a value and
always displayed in uppercase letters.
Previously it stored type names as text with the same case as it was given.
This breaks testing where the column type is defined in lowercase and
expects it to be given back as-is.
Fix this with using type names in uppercase.
Author: Laszlo Boszormenyi (GCS)
Forwarded: no
Last-Update: 2022-01-08
---
--- restfuldb-0.15.2+dfsg.orig/tests/cases/Database.pm_007.sh
+++ restfuldb-0.15.2+dfsg/tests/cases/Database.pm_007.sh
@@ -31,8 +31,8 @@ trap "exit 1" HUP INT QUIT TERM
TMP_DB_MAIN="${TMP_DIR}/test.db"
-sqlite3 ${TMP_DB_MAIN} "create table parent(id int, name text)"
-sqlite3 ${TMP_DB_MAIN} "create table child(id int, parent_id int, FOREIGN KEY(parent_id) REFERENCES parent(id))"
+sqlite3 ${TMP_DB_MAIN} "create table parent(id INT, name TEXT)"
+sqlite3 ${TMP_DB_MAIN} "create table child(id INT, parent_id INT, FOREIGN KEY(parent_id) REFERENCES parent(id))"
sqlite3 ${TMP_DB_MAIN} "insert into parent values (1, 'first entry')"
sqlite3 ${TMP_DB_MAIN} "insert into parent values (2, 'second entry')"
sqlite3 ${TMP_DB_MAIN} "insert into child values (1, 1)"
--- restfuldb-0.15.2+dfsg.orig/tests/outputs/Database.pm_001.out
+++ restfuldb-0.15.2+dfsg/tests/outputs/Database.pm_001.out
@@ -1,11 +1,11 @@
$VAR1 = {
- 'image' => 'blob'
+ 'image' => 'BLOB'
};
$VAR1 = {
- 'caption' => 'text',
- 'description' => 'text',
- 'id' => 'integer',
- 'image' => 'blob'
+ 'caption' => 'TEXT',
+ 'description' => 'TEXT',
+ 'id' => 'INTEGER',
+ 'image' => 'BLOB'
};
-
$VAR1 = {
@@ -13,10 +13,10 @@ $VAR1 = {
'authors' => 'varchar',
'cdate' => 'date',
'ctime' => 'time',
- 'id' => 'integer',
- 'revision_id' => 'integer',
- 'title' => 'text',
- 'year' => 'integer'
+ 'id' => 'INTEGER',
+ 'revision_id' => 'INTEGER',
+ 'title' => 'TEXT',
+ 'year' => 'INTEGER'
};
$VAR1 = {
'PublicID' => '12',
--- restfuldb-0.15.2+dfsg.orig/tests/outputs/Database.pm_007.out
+++ restfuldb-0.15.2+dfsg/tests/outputs/Database.pm_007.out
@@ -5,7 +5,7 @@ $VAR1 = [
'coltype' => 'id',
'length' => undef,
'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
'value' => 1
},
'parent_id' => {
@@ -29,14 +29,14 @@ $VAR1 = [
'coltype' => 'id',
'length' => undef,
'resolver' => undef,
- 'sqltype' => 'int',
+ 'sqltype' => 'INT',
'value' => 1
},
'name' => {
'coltype' => undef,
'length' => undef,
'resolver' => undef,
- 'sqltype' => 'text',
+ 'sqltype' => 'TEXT',
'value' => 'first entry'
}
},
@@ -66,7 +66,7 @@ $VAR1 = [
},
'length' => undef,
'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
'value' => 1
}
},
@@ -89,7 +89,7 @@ $VAR1 = [
'coltype' => 'id',
'length' => undef,
'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
'value' => 1
},
'parent_id' => {
@@ -109,7 +109,7 @@ $VAR1 = [
}, 'Database::ForeignKey' ),
'length' => undef,
'resolver' => undef,
-'sqltype' => 'int',
+'sqltype' => 'INT',
'value' => 2
}
},
--- restfuldb-0.15.2+dfsg.orig/tests/outputs/Database.pm_012.out
+++ restfuldb-0.15.2+dfsg/tests/outputs/Database.pm_012.out
@@ -12,28 +12,28 @@ $VAR1 = [
'coltype' => 'id',
'length' => undef,
'resolver' => undef,
-'sqltype' => 'integer',
+'sqltype' => 'INTEGER',
'value' => 1
},
'locality' => {
'coltype' => undef,
'length' => undef,
'resolver' => undef,
-'sqltype' => 'text',
+'sqltype' => 'TEXT',
'value' => 'New Caledonia'
},
'mine' => {
'coltype' => undef,
'length' => undef,
'resolver' => undef,
-'sqltype' => 'text',
+'sqltype' => 'TEXT',
'value' => 'Mea'
},
'name' => {
'coltype' => undef,
'length' => undef,
'resolver' => undef,
-'sqltype' => 'text',
+
Bug#1003012: Fixing #1003012 in bullseye (was: Re: Bug#1003012: closed by Salvatore Bonaccorso (Re: Accepted bash 5.1-6 (source) into unstable))
Hi Salvatore, > > Thanks for the quick fix! > > Just in avoidance of doubt, thanks goes to Matthias, I just fixed the > BTS metadata as the bug was not closed along with the upload. Thanks to Matthias then! :) > >From a security team perspective, we do not plan to release the fix as > a DSA via the security-archive, but a fix would be welcome to be > included in the next bullseye point release. > > Apart the patch "014" for this issue, maybe it makes sense to pick up > as well other of the applied patches (have not looked at the others). Upstream did this; bash-5.1.16 includes this patch and other recent patches. > Matthias, would you prepare such an update? TTBOMK the next bullseye > release will be around february 2022, according to the planning of the > release team. OK, that's too late for me, so I'm patching it myself. Thanks for the info. Frank
Bug#975191: marked as done (rust-js-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)
Your message dated Sat, 08 Jan 2022 14:35:29 +
with message-id
and subject line Bug#975191: fixed in rust-js-sys 0.3.55-1
has caused the Debian Bug report #975191,
regarding rust-js-sys: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo
build returned exit code 101
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.)
--
975191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-js-sys
Version: 0.3.35-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201119 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --buildsystem cargo
>dh_update_autotools_config -O--buildsystem=cargo
>dh_autoreconf -O--buildsystem=cargo
>dh_auto_configure -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: linking /usr/share/cargo/registry/* into
> /<>/debian/cargo_registry/
>dh_auto_build -O--buildsystem=cargo
>dh_auto_test -O--buildsystem=cargo
> debian cargo wrapper: options, profiles, parallel: ['parallel=4'] [] ['-j4']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose',
> '-j4', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling proc-macro2 v1.0.18
>Compiling unicode-xid v0.2.0
>Compiling log v0.4.11
>Compiling syn v1.0.12
> Running `CARGO_PKG_HOMEPAGE= CARGO_PKG_VERSION_MAJOR=1
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_VERSION_PATCH=18 CARGO_PKG_VERSION=1.0.18 CARGO_PKG_AUTHORS='Alex
> Crichton :David Tolnay '
> CARGO_PKG_REPOSITORY='https://github.com/alexcrichton/proc-macro2'
> CARGO=/usr/bin/cargo CARGO_PKG_NAME=proc-macro2
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/proc-macro2-1.0.18
> CARGO_PKG_VERSION_PRE= CARGO_PKG_DESCRIPTION='A substitute implementation of
> the compiler'\''s `proc_macro` API to decouple
> token-based libraries from the procedural macro use case.
> ' CARGO_PKG_VERSION_MINOR=0 rustc --crate-name build_script_build
> --edition=2018
> /<>/debian/cargo_registry/proc-macro2-1.0.18/build.rs
> --error-format=json --json=diagnostic-rendered-ansi --crate-type bin
> --emit=dep-info,link -C debuginfo=2 --cfg 'feature="default"' --cfg
> 'feature="proc-macro"' -C metadata=f24012b07c8998d9 -C
> extra-filename=-f24012b07c8998d9 --out-dir
> /<>/target/debug/build/proc-macro2-f24012b07c8998d9 -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO_PKG_HOMEPAGE='https://github.com/unicode-rs/unicode-xid'
> CARGO_PKG_VERSION_MAJOR=0
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION=0.2.0
> CARGO_PKG_AUTHORS='erick.tryzelaar :kwantam
> '
> CARGO_PKG_REPOSITORY='https://github.com/unicode-rs/unicode-xid'
> CARGO=/usr/bin/cargo CARGO_PKG_NAME=unicode-xid
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/unicode-xid-0.2.0
> CARGO_PKG_VERSION_PRE= CARGO_PKG_DESCRIPTION='Determine whether characters
> have the XID_Start
> or XID_Continue properties according to
> Unicode Standard Annex #31.
> ' CARGO_PKG_VERSION_MINOR=2 rustc --crate-name unicode_xid
> /<>/debian/cargo_registry/unicode-xid-0.2.0/src/lib.rs
> --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type
> lib --emit=dep-info,metadata,link -C debuginfo=2 --cfg 'feature="default"' -C
> metadata=39e1a0a5acc1b765 -C extra-filename=-39e1a0a5acc1b765 --out-dir
> /<>/target/debug/deps -L
> dependency=/<>/target/debug/deps --cap-lints warn`
> Running `CARGO_PKG_HOMEPAGE= CARGO_PKG_VERSION_MAJOR=0
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib'
> CARGO_PKG_VERSION_PATCH=11 CARGO_PKG_VERSION=0.4.11 CARGO_PKG_AUTHORS='The
> Rust Project Developers'
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang/log' CARGO=/usr/bin/cargo
> CARGO_PKG_NAME=log
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/log-0.4.11
> CARGO_PKG_VERSION_PRE= CARGO_PKG_DESCRIPTION='A lightweight logging facade
> for Rust
> ' CARGO_PKG_VERSION_MINOR=4 rustc --crate-name build_script_build
> /<>/debian/cargo_registry/log-0.4.11/build.rs
> --error-format=json --json=diagnostic-rendered-ansi --crate-type bin
> --emit=dep-
Bug#1002849: marked as done (python3-sage: missing Breaks+Replaces: sagemath-common (<< 9.4))
Your message dated Sat, 08 Jan 2022 14:36:33 + with message-id and subject line Bug#1002849: fixed in sagemath 9.4-3 has caused the Debian Bug report #1002849, regarding python3-sage: missing Breaks+Replaces: sagemath-common (<< 9.4) 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.) -- 1002849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-sage Version: 9.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-sage_9.4-2_amd64.deb ... Unpacking python3-sage (9.4-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-sage_9.4-2_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/sage/__init__.py', which is also in package sagemath-common 9.2-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-sage_9.4-2_amd64.deb cheers, Andreas sagemath-common=9.2-2_python3-sage=9.4-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: sagemath Source-Version: 9.4-3 Done: Tobias Hansen We believe that the bug you reported is fixed in the latest version of sagemath, 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 1002...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tobias Hansen (supplier of updated sagemath 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: Sat, 08 Jan 2022 11:50:35 + Source: sagemath Architecture: source Version: 9.4-3 Distribution: unstable Urgency: medium Maintainer: Debian Math Team Changed-By: Tobias Hansen Closes: 1002849 Changes: sagemath (9.4-3) unstable; urgency=medium . * Add Breaks+Replaces: sagemath-common (<< 9.4-1) for python3-sage. (Closes: #1002849) * Build-Depend on and Recommend cysignals-tools to obtain backtraces during build. * Set autopkgtest restriction allow-stderr. * Allow up to 100 test failures during build. * debian/watch: Check github releases rather than tags page, the latter may contain only prereleases on page 1. Checksums-Sha1: ef5ef6e89dacd66a37d00ebd366bfba98009c0cd 4808 sagemath_9.4-3.dsc e69bf20a28ce3edb87cde52145cc5b09d142e1fa 67720 sagemath_9.4-3.debian.tar.xz 2ee59e10dd20f58680161f09429422506d465747 24829 sagemath_9.4-3_source.buildinfo Checksums-Sha256: f55b88ccc9bab510b5cab100f1384039c1a6a0787336cb6feb3f3c39f862eadf 4808 sagemath_9.4-3.dsc 76792b7bf36f14be082728a2edc7575168fa37aa07d2a9dad934a744b6c82ece 67720 sagemath_9.4-3.debian.tar.xz 54682eb255912a8358668a3f08972fe67d0b353592bfe668a9034eaa3a7de211 24829 sagemath_9.4-3_source.buildinfo Files: 6c4f2ac9c8dc8f56569f7bd0a11460b9 4808 math optional sagemath_9.4-3.dsc b499aedfa382ba3c49f0a475f1461d43 67720 math optional sagemath_9.4-3.debian.tar.xz d3e2a0caea4e01365982aa0cbda07068 24829 math optional sagemath_9.4-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEoH46ol3M2u2mYo0kjIIWnY7OzSoFAmHZmR8ACgkQjIIWnY7O zSpbDA/+Ju7LN1jgIPrs1cjuyyMXBdg8gRLNbQ7xwQZ2oJhDjTcDRN6kSuHL9oQY m2W5wd7crTGhB8bq1DCKMJB+lkuv0JvnwWW03OVkgfr5qyhySm1si5RjgutTB48C 38lbIr2HaUKHP6aJCOILFqxWJ68BcRNwc2HCn8NpDj2jCQgT2Pc9gBv108yMwuGI o/0ssZIR/wLknhluNM3ZTkDQi8vBvyNOajiB18jOoccOEjT1hfO+6CW1QjpHq5DV DC0fjhF9UUmlVPD52WBDLl/5V6tvD98AdPGwa4YfRy3kUNXe2l5RegK8JuLK1zg+ nVjOXrjsvS4n70Cr4QkfuvqDTgWCBVWBr0/bawBc9NXVMJK2+k6hmY4PW2xhO69D DA1mUwZVWDExLnCft2CAR/QOrD/tBcNzbQKASatKvcc+nveB43IpTpwWqXDInOQy VAMhuHlV0iAo5tJRkr
Processed: severity
Processing commands for cont...@bugs.debian.org: > severity 1002569 important Bug #1002569 [src:rsplib] rsplib: FTBFS on mipsel Severity set to 'important' from 'serious' > End of message, stopping processing here. Please contact me if you need assistance. -- 1002569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#999286: marked as done (scalable-cyrfonts: missing required debian/rules targets build-arch and/or build-indep)
Your message dated Sat, 08 Jan 2022 13:34:27 + with message-id and subject line Bug#999286: fixed in scalable-cyrfonts 4.18 has caused the Debian Bug report #999286, regarding scalable-cyrfonts: 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.) -- 999286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scalable-cyrfonts Version: 4.17+nmu1 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: scalable-cyrfonts Source-Version: 4.18 Done: Anton Zinoviev We believe that the bug you reported is fixed in the latest version of scalable-cyrfonts, 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. Anton Zinoviev (supplier of updated scalable-cyrfonts 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: Sat, 08 Jan 2022 14:39:36 +0200 Source: scalable-cyrfonts Architecture: source Version: 4.18 Distribution: unstable Urgency: medium Maintainer: Anton Zinoviev Changed-By: Anton Zinoviev Closes: 719147 965808 999286 Changes: scalable-cyrfonts (4.18) unstable; urgency=medium . * Raise Standards-Version to 4.5.0. * Raise debhelper compat level to 13, closes: #965808. * Add build-arch target in debian/rules, closes: #999286. * scalable-cyrfonts-tex: fix typo in package description, thanks to Sergey Alyoshin, closes: #719147. Checksums-Sha1: 15ee656ff70c8193dd84e134707f04c46e1aaafc 1734 scalable-cyrfonts_4.18.dsc b16ac1e88877959d552cdfb3258ec2f6f8f8b159 8743878 scalable-cyrfonts_4.18.tar.gz 453bacfc3878428ef0d0b2d305fd54a1db7981db 11002 scalable-cyrfonts_4.18_source.buildinfo Checksums-Sha256: 607f41a5209de4d36b6129deead624f60e91e5572afeefb48d1c8027a7f0b224 1734 scalable-cyrfonts_4.18.dsc 8c3ed235d39f5d2bbb979dc563f926274e98a7600c61e8d79100455490501b8f 8743878 scalable-cyrfonts_4.18.tar.gz 368e320ee6b6346659703d94de4a9ca7b98858778b5a12973ab269bdb1cb5576 11002 scalable-cyrfonts_4.18_source.buildinfo Files: f0d332247032c5f643c175b18d7628cd 1734 text optional scalable-cyrfonts_4.18.dsc 24041d7dafadbc7e5341e70478e7d023 8743878 text optional scalable-cyrfonts_4.18.tar.gz 115f90acda582345c95b43d08e1b9216 11002 text optional scalable-cyrfonts_4.18_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEicc1SOihLZMLEYmNk7cW45P7GKYFAmHZjLAACgkQk7cW45P7 GKaythAAnJn26B/R8bZc/eXUcfg2aNAZssgjNedSvtn92sKN9z33Xi3b2udopE07 Z9bBUEDQ5PBH9RDLhwhsxaDtlBq9dSOlq2zAzVK/1u94A13zqIyz9Dp9L6KX3kQI JusT3g4IgSXdVhXCiaYrTd2H5YYPvhVheb59B71Cd+Owwy/LDyiqWKZr0IK+xVXA nGuCrrATjI7qp0xWtlraUWjXUaw8oxcyh1jEBRay/4lT1+bYxcVwtYtB/7bS2W6y 5vrZh2Wt4FlQX8mh3jZUj6jwCiGxMdsXJX769+jb9DkKh9rnPlng44v8QHzgp+el 7avuq3ZAdnEtmlHqJexsAUpHtQTfC3rU4z36A0GbewYf2yIENiVFPm4WlSnSWI8y HxJ/3IexRlbMm5NZ9jH25vzIDD+bEd2VjjCIFcSVix2nXnO3j5HjMqwDD750B6bm GMYxQIztpQwkuM7x3a49PF+HnluHkucsGx9gdGtzX3WpisGsY5bBYP0l5gOVOuWB CLhz8/qJ8BkkzhCn0zahz0/ypBfL4IbSvLgNAQ75LeXLheS0ts4iF6tiu+fzd0Cd UUI/5+razGRTNIqvortlcSq1luBB/snJSk6yQJuf17mVLTFMd+Cz74fDT7zw3SgG 8P4U8vrSe6tF9/31tQsLY1O8+bl8PiGkIdNLBvXUG3sp6J5ofZo= =OiBv -END PGP SIGNATURE End Message ---
Bug#965808: marked as done (scalable-cyrfonts: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 08 Jan 2022 13:34:27 + with message-id and subject line Bug#965808: fixed in scalable-cyrfonts 4.18 has caused the Debian Bug report #965808, regarding scalable-cyrfonts: 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.) -- 965808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scalable-cyrfonts Version: 4.17 Severity: normal Usertags: compat-5-6-removal Hi, The package scalable-cyrfonts 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: scalable-cyrfonts Source-Version: 4.18 Done: Anton Zinoviev We believe that the bug you reported is fixed in the latest version of scalable-cyrfonts, 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. Anton Zinoviev (supplier of updated scalable-cyrfonts 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: Sat, 08 Jan 2022 14:39:36 +0200 Source: scalable-cyrfonts Architecture: source Version: 4.18 Distribution: unstable Urgency: medium Maintainer: Anton Zinoviev Changed-By: Anton Zinoviev Closes: 719147 965808 999286 Changes: scalable-cyrfonts (4.18) unstable; urgency=medium . * Raise Standards-Version to 4.5.0. * Raise debhelper compat level to 13, closes: #965808. * Add build-arch target in debian/rules, closes: #999286. * scalable-cyrfonts-tex: fix typo in package description, thanks to Sergey Alyoshin, closes: #719147. Checksums-Sha1: 15ee656ff70c8193dd84e134707f04c46e1aaafc 1734 scalable-cyrfonts_4.18.dsc b16ac1e88877959d552cdfb3258ec2f6f8f8b159 8743878 scalable-cyrfonts_4.18.tar.gz 453bacfc3878428ef0d0b2d305fd54a1db7981db 11002 scalable-cyrfonts_4.18_source.buildinfo Checksums-Sha256: 607f41a5209de4d36b6129deead624f60e91e5572afeefb48d1c8027a7f0b224 1734 scalable-cyrfonts_4.18.dsc 8c3ed235d39f5d2bbb979dc563f926274e98a7600c61e8d79100455490501b8f 8743878 scalable-cyrfonts_4.18.tar.gz 368e320ee6b6346659703d94de4a9ca7b98858778b5a12973ab269bdb1cb5576 11002 scalable-cyrfonts_4.18_source.buildinfo Files: f0d332247032c5f643c175b18d7628cd 1734 text optional scalable-cyrfonts_4.18.dsc 24041d7dafadbc7e5341e70478e7d023 8743878 text optional scalable-cyrfonts_4.18.tar.gz 115f90acda582345c95b43d08e1b9216 11002 text optional scalable-cyrfonts_4.18_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEicc1SOihLZMLEYmNk7cW45P7GKYFAmHZjLAACgkQk7cW45P7 GKaythAAnJn26B/R8bZc/eXUcfg2aNAZssgjNedSvtn92sKN9z33Xi3b2udopE07 Z9bBUEDQ5PBH9RDLhwhsxaDtlBq9dSOlq2zAzVK/1u94A13zqIyz9Dp9L6KX3kQI JusT3g4IgSXdVhXCiaYrTd2H5YYPvhVheb59B71Cd+Owwy/LDyiqWKZr0IK+xVXA nGuCrrATjI7qp0xWtlraUWjXUaw8oxcyh1jEBRay/4lT1+bYxcVwtYtB/7bS2W6y 5vrZh2Wt4FlQX8mh3jZUj6jwCiGxMdsXJX769+jb9DkKh9rnPlng44v8QHzgp+el 7avuq3ZAdnEtmlHqJexsAUpHtQTfC3rU4z36A0GbewYf2yIENiVFPm4WlSnSWI8y HxJ/3IexRlbMm5NZ9jH25vzIDD+bEd2VjjCIFcSVix2nXnO3j5HjMqwDD750B6bm GMYxQIztpQwkuM7x3a49PF+HnluHkucsGx9gdGtzX3WpisGsY5bBYP0l5gOVOuWB CLhz8/qJ8BkkzhCn0zahz0/ypBf
Processed: bug 1000650 is forwarded to https://github.com/sebastianbergmann/phploc/commit/c21b0521f0d87ddc328b62dccafe2f90b62cfbe3.patch ...
Processing commands for cont...@bugs.debian.org: > forwarded 1000650 > https://github.com/sebastianbergmann/phploc/commit/c21b0521f0d87ddc328b62dccafe2f90b62cfbe3.patch Bug #1000650 [phploc] phploc: Failing testsuite with PHP 8.1 Set Bug forwarded-to-address to 'https://github.com/sebastianbergmann/phploc/commit/c21b0521f0d87ddc328b62dccafe2f90b62cfbe3.patch'. > tags 1000650 + patch fixed-upstream Bug #1000650 [phploc] phploc: Failing testsuite with PHP 8.1 Added tag(s) patch and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1000650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1003191: marked as done (mmdebstrap fails when identifying suite by codename)
Your message dated Sat, 08 Jan 2022 12:33:59 + with message-id and subject line Bug#1003191: fixed in mmdebstrap 0.8.3-1 has caused the Debian Bug report #1003191, regarding mmdebstrap fails when identifying suite by codename 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.) -- 1003191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mmdebstrap Severity: serious Version: 0.8.2-1 Hi, Quoting Benjamin Drung (2022-01-05 20:59:37) > I saw that the autopkgtests for bdebstrap fails for mmdebstrap 0.8.2-1 > on Ubuntu jammy: > https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html > > amd64 log: > https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/b/bdebstrap/20220101_132038_11625@/log.gz > > E: nothing got downloaded > W: listening on child socket failed: Undefined subroutine > &Devel::Cover::get_coverage called at /usr/bin/mmdebstrap line 105. > > I haven't investigated further. this is a problem introduced with 0.8.2 and fixing it properly requires a new apt release with this commit in it: https://salsa.debian.org/apt-team/apt/-/commit/c6bd75f906c9c782e739ec99f2983407500811bf On Debian you can work around this by using 'stable', 'unstable', 'testing' instead of 'bullseye' or 'sid'. Thanks! cheers, josch signature.asc Description: signature --- End Message --- --- Begin Message --- Source: mmdebstrap Source-Version: 0.8.3-1 Done: Johannes Schauer Marin Rodrigues We believe that the bug you reported is fixed in the latest version of mmdebstrap, 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. Johannes Schauer Marin Rodrigues (supplier of updated mmdebstrap 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, 08 Jan 2022 13:13:04 +0100 Source: mmdebstrap Architecture: source Version: 0.8.3-1 Distribution: unstable Urgency: medium Maintainer: Johannes Schauer Marin Rodrigues Changed-By: Johannes Schauer Marin Rodrigues Closes: 1000823 1003191 1003237 Changes: mmdebstrap (0.8.3-1) unstable; urgency=medium . * new upstream release - allow identifying a suite by codename again (closes: #1003191) * debian/control: bump apt version constraint to 2.3.14 * debian/control: add libdpkg-perl to Recommends (closes: #1000823) * debian/copyright: add disclaimer of warranty and limitation of liability (closes: #1003237) * add debian/README.Debian * debian/copyright: fixup my name Checksums-Sha1: 24b0a9607e60ab4aa6e34ac6328b152b076cb01a 2313 mmdebstrap_0.8.3-1.dsc 8ff5d89604f9292ae71bdac4530228b1911afd18 110286 mmdebstrap_0.8.3.orig.tar.gz e3097d0479a88addfef26b0d4c9ebdaa6ca19959 10632 mmdebstrap_0.8.3-1.debian.tar.xz Checksums-Sha256: 0179abe5f3f4e4c64d2b3ab9a2de3d377deb3b3be21d4e180a531a98c0b8aed1 2313 mmdebstrap_0.8.3-1.dsc 8f4ce5af476f8947387971ab1edbedc3f79d4b3d3cfb2c4138d02897a215b42a 110286 mmdebstrap_0.8.3.orig.tar.gz 227081ab2c5f1a8cffe4f5a2f63f532e71b04dcafc2301ac5cde63e7a52f8540 10632 mmdebstrap_0.8.3-1.debian.tar.xz Files: cede32b2cf71721d8e82327f7c285b8b 2313 admin optional mmdebstrap_0.8.3-1.dsc d9c7c0b6aa38c4c05f7f673b028d985a 110286 admin optional mmdebstrap_0.8.3.orig.tar.gz e5f3f916d20b7cd7c90721e5f1926bc6 10632 admin optional mmdebstrap_0.8.3-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAmHZf/YACgkQ8sulx4+9 g+EzTQ/+OtShDBlNSCPgzMzLfKLyz6QQhXNljP1HoWGK+3s9/Gxi3OrwLgqDZ+J4 rTIHIyxwkDyuUS3d9qfvgTylz3RA1m2WWbgBs5QmHo652fpc7pa3gvCZ/uvRvzv6 CtxDZy3zn6dBBZv10i7YfVlLmUyL0Fd66k39FRPsVsEucVIXwgMKmQ1k6y9S2oTK hT2TSFfMkVlRtrcDr1YVmXFG3ioM4DnxiYiSlHFUCKUmOiWi2ffNHVCz2wgxAqH3 X3bdM51xcJ4z6Ujh69axnFBADHtFJ6wGBMGcvfenIM9vwXkCm7bsNUYEteUhcEoN IvzQpZlwiwbsDt6XXx0+kTKsmdLrDq3w8iti55npAvlDwoBG4twQBWR6WgOrhky0 kIybZwyHeTQzI4sBv88goBWq7SKNHa7Tl9JtlHYIWpCXPrM4zp9ydykl5btrQ9ox TUBFi+869y1eC8AhirEgtaccf83mKaArdncKYZNWNNWzSmlBSwwtvMuY4wuDbx19 Tq3pai3nD4XXlLQVmjiuZyWhX98KwCCwM9SST/4iSVR5iKPwqOkfSGUZ4qPSaPwQ CnGjDF/t+Rr5Gfixw7h1rURu/XnerRiS99sByuM+Enuj
Bug#1002986: libguestfs-tools: Depends on guestfs-tools that is not in the archive
> It looks like libguestfs-tools version 1:1.46.2-1 in depending on > guestfs-tools that is not in the archive making the package > uninstalable Just wanted to note that upstream we have split up the old, very large, libguestfs git "monorepo", splitting out: guestfs-tools (https://github.com/rwmjones/guestfs-tools) - All the C and OCaml tools like virt-df, virt-customize, etc. except for guestfish, virt-v2v and virt-p2v. virt-v2v (https://github.com/libguestfs/virt-v2v) - Conversion from VMware to KVM. virt-p2v (https://github.com/libguestfs/virt-p2v) - Conversion from physical machines to KVM. libguestfs (https://github.com/libguestfs/libguestfs) - Now it's just the library and language bindings (including guestfish because that is -- kind of -- a set of shell script bindings) FWIW here are the new Fedora packages in case you want to see how we decided to arrange the subpackages and dependencies. https://src.fedoraproject.org/rpms/libguestfs/tree/rawhide https://src.fedoraproject.org/rpms/guestfs-tools/tree/rawhide https://src.fedoraproject.org/rpms/virt-v2v/tree/rawhide https://src.fedoraproject.org/rpms/virt-p2v/tree/rawhide Another thing to say is that we're planning eventually to move all the git repos to gitlab because it's a more free software friendly solution compared to github. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top
Bug#997197: marked as done (clfft: FTBFS: generator.transpose.cpp:1092:95: error: taking address of rvalue [-fpermissive])
Your message dated Sat, 08 Jan 2022 11:03:37 +
with message-id
and subject line Bug#997197: fixed in clfft 2.12.2-3.2
has caused the Debian Bug report #997197,
regarding clfft: FTBFS: generator.transpose.cpp:1092:95: error: taking address
of rvalue [-fpermissive]
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.)
--
997197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clfft
Version: 2.12.2-3.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/library && /usr/bin/c++
> -DCLFFT_EXPORTS -DclFFT_EXPORTS
> -I/<>/obj-x86_64-linux-gnu/include
> -I/<>/src/library/../include -pthread -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wall -pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
> -MD -MT library/CMakeFiles/clFFT.dir/generator.transpose.cpp.o -MF
> CMakeFiles/clFFT.dir/generator.transpose.cpp.o.d -o
> CMakeFiles/clFFT.dir/generator.transpose.cpp.o -c
> /<>/src/library/generator.transpose.cpp
> In file included from /usr/include/CL/cl.h:20,
> from /<>/src/library/../include/clFFT.h:33,
> from /<>/src/library/private.h:29,
> from /<>/src/library/generator.stockham.h:25,
> from /<>/src/library/generator.stockham.cpp:20:
> /usr/include/CL/cl_version.h:22:104: note: ‘#pragma message: cl_version.h:
> CL_TARGET_OPENCL_VERSION is not defined. Defaulting to 300 (OpenCL 3.0)’
>22 | #pragma message("cl_version.h: CL_TARGET_OPENCL_VERSION is not
> defined. Defaulting to 300 (OpenCL 3.0)")
> |
> ^
> In file included from /<>/src/library/repo.h:23,
> from /<>/src/library/generator.stockham.h:26,
> from /<>/src/library/generator.stockham.cpp:20:
> /<>/src/library/plan.h: In constructor ‘FFTPlan::FFTPlan()’:
> /<>/src/library/plan.h:504:26: warning:
> ‘FFTPlan::blockComputeType’ will be initialized after [-Wreorder]
> 504 | BlockComputeType blockComputeType;
> | ^~~~
> /<>/src/library/plan.h:462:25: warning: ‘clfftPlanHandle
> FFTPlan::planTX’ [-Wreorder]
> 462 | clfftPlanHandle planTX;
> | ^~
> /<>/src/library/plan.h:528:9: warning: when initialized here
> [-Wreorder]
> 528 | FFTPlan ()
> | ^~~
> /<>/src/library/plan.h:526:33: warning:
> ‘FFTPlan::nonSquareKernelOrder’ will be initialized after [-Wreorder]
> 526 | NON_SQUARE_KERNEL_ORDER nonSquareKernelOrder;
> | ^~~~
> /<>/src/library/plan.h:515:21: warning: ‘clfftPlanHandle
> FFTPlan::plHandle’ [-Wreorder]
> 515 | clfftPlanHandle plHandle;
> | ^~~~
> /<>/src/library/plan.h:528:9: warning: when initialized here
> [-Wreorder]
> 528 | FFTPlan ()
> | ^~~
> /<>/src/library/plan.h:515:21: warning: ‘FFTPlan::plHandle’ will
> be initialized after [-Wreorder]
> 515 | clfftPlanHandle plHandle;
> | ^~~~
> /<>/src/library/plan.h:506:14: warning: ‘bool
> FFTPlan::hasPreCallback’ [-Wreorder]
> 506 | bool hasPreCallback;
> | ^~
> /<>/src/library/plan.h:528:9: warning: when initialized here
> [-Wreorder]
> 528 | FFTPlan ()
> | ^~~
> /<>/src/library/plan.h: In destructor ‘FFTPlan::~FFTPlan()’:
> /<>/src/library/plan.h:602:25: warning: deleting object of
> abstract class type ‘FFTAction’ which has non-virtual destructor will cause
> undefined behavior [-Wdelete-non-virtual-dtor]
> 602 | delete action;
> | ^
> In file included from /<>/src/library/repo.h:26,
> from /<>/src/library/generator.stockham.h:26,
> from /<>/src/library/generator.stockham.cpp:20:
> /<>/src/library/../statTimer/statisticalTimer.GPU.h: In
> constructor ‘StatData::StatData(clfftPlanHandle, FFTPlan*, cl_kernel,
> cl_uint, _cl_event**, const std::vector&, const
> std::vector&)’:
> /<>/src/library/../statTimer/statisticalTimer.GPU.h:39:18:
> warning: ‘StatData::deltaNanoSec’ will be initialized after [-Wreorder]
>39 | cl_ul
Bug#997229: marked as done (gulkan: FTBFS: ../src/gulkan-texture.c:50:18: error: incompatible types when assigning to type ‘VkFormat’ from type ‘void *’)
Your message dated Sat, 08 Jan 2022 11:03:46 + with message-id and subject line Bug#997229: fixed in gulkan 0.15.1-2.1 has caused the Debian Bug report #997229, regarding gulkan: FTBFS: ../src/gulkan-texture.c:50:18: error: incompatible types when assigning to type ‘VkFormat’ from type ‘void *’ 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.) -- 997229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gulkan Version: 0.15.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -Isrc/libgulkan-0.15.so.0.15.1.p -Isrc -I../src -I/usr/include/cairo > -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/x86_64-linux-gnu > -I/usr/include/graphene-1.0 -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include > -I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c11 > -Wno-overlength-strings -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -mfpmath=sse -msse -msse2 -pthread > -DGULKAN_COMPILATION -MD -MQ > src/libgulkan-0.15.so.0.15.1.p/gulkan-texture.c.o -MF > src/libgulkan-0.15.so.0.15.1.p/gulkan-texture.c.o.d -o > src/libgulkan-0.15.so.0.15.1.p/gulkan-texture.c.o -c ../src/gulkan-texture.c > In file included from /usr/include/vulkan/vulkan.h:11, > from ../src/gulkan-texture.h:16, > from ../src/gulkan-texture.c:9: > ../src/gulkan-texture.c: In function ‘gulkan_texture_init’: > ../src/gulkan-texture.c:50:18: error: incompatible types when assigning to > type ‘VkFormat’ from type ‘void *’ >50 | self->format = VK_NULL_HANDLE; > | ^~ > [2/66] cc -Isrc/libgulkan-0.15.so.0.15.1.p -Isrc -I../src > -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/graphene-1.0 > -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include > -I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c11 > -Wno-overlength-strings -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -mfpmath=sse -msse -msse2 -pthread > -DGULKAN_COMPILATION -MD -MQ > src/libgulkan-0.15.so.0.15.1.p/gulkan-instance.c.o -MF > src/libgulkan-0.15.so.0.15.1.p/gulkan-instance.c.o.d -o > src/libgulkan-0.15.so.0.15.1.p/gulkan-instance.c.o -c ../src/gulkan-instance.c > [3/66] cc -Isrc/libgulkan-0.15.so.0.15.1.p -Isrc -I../src > -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/graphene-1.0 > -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include > -I/<>/obj-x86_64-linux-gnu -fdiagnostics-color=always > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c11 > -Wno-overlength-strings -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -mfpmath=sse -msse -msse2 -pthread > -DGULKAN_COMPILATION -MD -MQ src/libgulkan-0.15.so.0.15.1.p/gulkan-client.c.o > -MF src/libgulkan-0.15.so.0.15.1.p/gulkan-client.c.o.d -o > src/libgulkan-0.15.so.0.15.1.p/gulkan-client.c.o -c ../src/gulkan-client.c > [4/66] cc -Isrc/libgulkan-0.15.so.0.15.1.p -Isrc -I../src > -I/usr/include/cairo -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/graphene-1.0 > -I/usr/lib/x86_64-linux-gnu/graphene-1.0/include > -I/<>/obj-x86_64-linux-gnu -fdiagnostics-col
Bug#965461: marked as done (configure-debian: Removal of obsolete debhelper compat 5 and 6 in bookworm)
Your message dated Sat, 08 Jan 2022 11:03:41 + with message-id and subject line Bug#965461: fixed in configure-debian 1.0.3+nmu2 has caused the Debian Bug report #965461, regarding configure-debian: 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.) -- 965461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: configure-debian Version: 1.0.3 Severity: normal Usertags: compat-5-6-removal Hi, The package configure-debian 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: configure-debian Source-Version: 1.0.3+nmu2 Done: Adrian Bunk We believe that the bug you reported is fixed in the latest version of configure-debian, 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. Adrian Bunk (supplier of updated configure-debian 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, 06 Jan 2022 16:26:12 +0200 Source: configure-debian Architecture: source Version: 1.0.3+nmu2 Distribution: unstable Urgency: medium Maintainer: David Nusinow Changed-By: Adrian Bunk Closes: 965461 Changes: configure-debian (1.0.3+nmu2) unstable; urgency=medium . * Non-maintainer upload. * debian/compat: 5 -> 7. (Closes: #965461) Checksums-Sha1: 172f67eff98de6f89f50ca60e48c8911d87f8cc1 1456 configure-debian_1.0.3+nmu2.dsc 73acd2f04e8fdc73e1a5d86c9a71b760c39a954e 21488 configure-debian_1.0.3+nmu2.tar.gz Checksums-Sha256: 9f6afa708c94ec6bca74e36dd7b452e28bef4455bc01fa179c5ab00708edd0c4 1456 configure-debian_1.0.3+nmu2.dsc 81341d12d25baaf57c89bf28df3eacfa437dbf40fd2dca1d1c04a5044415b3b1 21488 configure-debian_1.0.3+nmu2.tar.gz Files: c1077b219bda7b359347d01ec7101718 1456 admin optional configure-debian_1.0.3+nmu2.dsc 541df5a9777cf88e9e9d6124ae6feaf2 21488 admin optional configure-debian_1.0.3+nmu2.tar.gz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmHW/JIACgkQiNJCh6LY mLGZJA/9FuHSuFGxBO+41taEqCW4jZcjyC+hAi+OIUvrnguWjJj7yBDs22zOmo4c Vgu0aGYfdQQEI0QK4Q3rSLvrsnMya8godftemG3n+YizldfvTPQ+TpnMAURKnT7H J3qYUBJbhrObsYJl0rOBUjOf7u4C8nuMVHOkhv5eyq+PO1xmBVSW97bLeLLZ8wXB c6sM+306p8JuK6Kn4xkt6orbK2J3C9uYl8IaJZ+ZhRMs+liQkDmQ10rRIiMgFujT LbBWpd/I+igYvW4As5x9z4wfCLb+XSIzWjOJwjD57oOJHJYMOTYkvEEIopxywIJP GpzbDkMuAshKD4VodTG2BH9Rse3o4jAJ2EWpawKwU4rWpGNmYuOLahPrVbTk7vhQ j79dauUuz/4RIl+3J92hoYwCkQdA1Gqxkj4HpI+CTHpbZ25SgxxlUZ1R7K03TLaW 7WAe5j7p5S/3TG+CpipviqkvJ9sT/pKMo07YGpqu8KaNS9v61xNamhUmz0G4Ak2D ds2jSNc6/TzWWYXhAW+G0xF0KhbcgMU8TbFbK2Et/Wnfaj8R+nRYYxJ0bMH/AqPu MpkpwRghmxk674ziMSZ45PC9fDnUsp6CritsjNkn02GujFoxePJRvUKY2VDaQmiY zviIoHEeOSgLHYCcYYuCNw+Ocr2rJm0kjknA64BSVtijmYUaRyQ= =1Km/ -END PGP SIGNATURE End Message ---
Bug#998365: libstdc++-arm-none-eabi-newlib: Version of libstdc++-arm-none-eabi-newlib and gcc-arm-none-eabi must match or the C++ libraries can't be found
On Wed, Nov 03, 2021 at 12:04:42AM +0100, David Given wrote: > Ah, I've just spotted (via the automatically reported bug data...) that > there is such a constraint but it's only at a Recommends level. I think > this should be upgraded to a Depends. > >... > > Versions of packages libstdc++-arm-none-eabi-newlib recommends: > > ii binutils-arm-none-eabi 2.37-7+15 > > ii gcc-arm-none-eabi 15:8-2019-q3-1+b1 >... The Recommends is unversioned, upgrading it unversioned to a Depends wouldn't help. cu Adrian
Bug#992592: lightdm does not start / work any more after system upgrade
Am 08.01.22 um 03:10 schrieb xiao sheng wen(肖盛文): If you want use nodm, only run apt-get install nodm in enough. lightdm and nodm can co-exist in the same machine. When install nodm after lightdm, It'll display a prompt let user choise "Default display manager". You may choice nodm to use. Yes - thanks. But a package that does not work and is useless can be purged.
Bug#1003037:
It seems that this is an issue in gcc has observed when compiling tensorflow https://zenn.dev/nbo/scraps/8f1505e365d961
Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
Control: severity -1 normal -- Ondřej Surý (He/Him) > On 4. 12. 2021, at 17:14, Matthew Vernon wrote: > > Hi, > >> On 22/11/2021 09:16, Ondřej Surý wrote: >> >> I analysed the problem in: >> https://github.com/PhilipHazel/pcre2/issues/56 > > Thanks! I've had a read of that, and AIUI it's a behaviour change (matching > that of perl) rather than an ABI change? > > >> I guess bumping the version in the symbols file like this should do the >> trick: > >> - pcre2_set_compile_extra_options_8@Base 10.32 >> + pcre2_set_compile_extra_options_8@Base 10.38 > > Making this change will cause some things that will work fine with 10.32 to > incorrectly state a dependency on >=10.38, yes? But leaving things as-is > means that some code that uses a particular flag will not work if compiled > with >=10.38 and run against <10.38? > > I think that probably means on balance we should make the change you suggest, > but I wanted to check I'd understood correctly :) > > Regards, > > Matthew
Processed: Re: Bug#999693: php8.1: Regular expression functions warn "Compilation failed" and return null
Processing control commands: > severity -1 normal Bug #999693 [php8.1-common] php8.1: Regular expression functions warn "Compilation failed" and return null Severity set to 'normal' from 'grave' -- 999693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
