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
autom
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
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/onetb
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 d
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
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
> 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 t
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 AP
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
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
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 reque
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
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
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 Sig
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.debia
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.
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 woul
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
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 --
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
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: FTBF
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 u
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 ha
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
an
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
tes
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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/deb
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?
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 o
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
Stoppin
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-platf
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 u
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
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
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
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.
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 pr
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
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 me
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 yo
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/sebastianbergm
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 ha
> 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/rwmj
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 m
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
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 tha
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-non
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.
It seems that this is an issue in gcc has observed when compiling tensorflow
https://zenn.dev/nbo/scraps/8f1505e365d961
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
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
Conta
83 matches
Mail list logo
