On Thu, 11 May 2023 at 02:43, Andres Salomon wrote:
>
> On Sat, 11 Mar 2023 11:04:15 + James Addison
> wrote:
> > Package: nodejs
> > Followup-For: Bug #1030284
> > X-Debbugs-Cc: t...@debian.org
> >
> > Guidance received from the V8 project (
On Thu, 11 May 2023 at 23:54, Thorsten Glaser wrote:
>
> James Addison dixit:
>
> >On Thu, 11 May 2023 at 02:43, Andres Salomon wrote:
>
> >> For ARM64, he says that raising the stack limit is not safe for v8
> >> *embedded inside WebView*, and therefore not a
On Fri, 12 May 2023 at 16:54, Thorsten Glaser wrote:
>
> Yes, but given the usual ulimit, the new limit would be 4+ times
> the old one, much much harder to reach.
That does sound promising.
I've followed up on this discussion with the relevant upstream NodeJS
thread, and beyond there to the rel
On Fri, 12 May 2023 at 23:23, James Addison wrote:
>
> On Fri, 12 May 2023 at 16:54, Thorsten Glaser wrote:
> >
> > Yes, but given the usual ulimit, the new limit would be 4+ times
> > the old one, much much harder to reach.
>
> That does sound promising.
>
>
On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote:
>
> James Addison dixit:
>
> >I'm going to stay involved with this thread, but I think that it is
> >upon you to develop or provide further guidance towards a patch if
> >it's something you'd like to
On Sat, 13 May 2023 at 11:14, James Addison wrote:
>
> On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote:
> >
> > James Addison dixit:
> >
> > >I'm going to stay involved with this thread, but I think that it is
> > >upon you to develop or provid
On Sat, 13 May 2023 at 12:15, James Addison wrote:
>
> On Sat, 13 May 2023 at 11:14, James Addison wrote:
> >
> > On Sat, 13 May 2023 at 02:18, Thorsten Glaser wrote:
> > >
> > > James Addison dixit:
> > >
> > > >I'm going to stay
-than checks can be
problematic
* places comparison constants on the lhs for safety
I'll post test results when they are available.
Cheers,
James
Description: Request an rlimit-determined stack size from V8
Author: James Addison
Bug-Debian: https://bugs.debian.org/1030284
--- /dev/null
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@mirbsd.de
Hmm.. although the build itself succeeded, there was a unit test failure that
appears related to the change:
not ok 3213 sequential/test-fs-stat-sync-overflow
---
duration_ms: 1.111
severity: fail
exitcode: 1
stack: |-
node:ass
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@mirbsd.de
It does seem to (continue to) function, at least on x86:
~/dygraphs-2.2.0$ NODE_PATH=/usr/share/nodejs
../nodejs-18.13.0+dfsg1/out/Release/node /usr/bin/babeljs --config-file
$PWD/babel.config.json --compact false --source-maps inline -d
Followup-For: Bug #1030284
I decline to participate further with this bugreport, although others are
welcome to pick up from the patches I've submitted (please don't merge them
as-is; modify them to apply corrections).
Followup-For: Bug #1030545
X-Debbugs-Cc: ben...@debian.org, dipak.zo...@ibm.com
Hi Hilko (plus Dipak, fix author on cc for awareness),
Debian kernel package 5.10.179-1 that includes a fix for this has been accepted
into the stable-security (bullseye-security) suite today, and should resolve
this
Followup-For: Bug #1030545
(adding a message in 'quiet' mode with a self-correction)
I wrote:
> Hi Hilko (plus Dipak, fix author on cc for awareness),
My mistake there: Sumanth was the patch author for this change I believe.
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: a...@debian.org, bi...@debian.org
I'm having trouble reconciling these two log lines during the upgrade without
systemd:
ls: cannot access '/etc/systemd/system/multi-user.target.wants': No such file
or directory
...
(deb-systemd-h
On Sun, 14 May 2023 15:21:24 -0400, Ted wrote:
> On Sun, May 14, 2023 at 06:03:59PM +0200, Michael Biebl wrote:
> > > Please reassign it there together with instructions how to fix it, i.e.
> > > what should be done in the maintainer scripts.
>
> Can someone send the instructions on how to fix this
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org
I've been 'approximately' testing this locally on bookworm by:
* Editing the Install.WantedBy in /lib/systemd/system
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org
Would a 'move /etc/systemd/system/default.target.wants/e2scrub_reap.service
to /etc/systemd/system/m
Followup-For: Bug #1035543
On Fri, 05 May 2023 11:04:29 +0200, Andreas wrote:
> If I install systemd into the bullseye chroot and upgrade that to
> bookworm, both systemd and e2fsprogs are still installed, but
> /etc/systemd/system/multi-user.target.wants/e2scrub_reap.service
> does *NOT* get c
Followup-For: Bug #1035543
On Wed, 31 May 2023 09:55:13 +0100, James wrote:
> On Fri, 05 May 2023 11:04:29 +0200, Andreas wrote:
> > If I install systemd into the bullseye chroot and upgrade that to
> > bookworm, both systemd and e2fsprogs are still installed, but
> > /etc/systemd/system/multi-
Followup-For: Bug #1035543
X-Debbugs-Cc: ty...@mit.edu, bi...@debian.org, hel...@subdivi.de,
jspri...@debian.org, ans...@debian.org, a...@debian.org,
debian.bugrep...@wodny.org, debian-rele...@lists.debian.org
[ re-introducing the larger cc list audience, plus debian-release ]
Would reverting t
Package: e2fsprogs
Followup-For: Bug #1035543
Control: tags -1 patch
>From 9ad481148456520f15f92973cdd0cf6caa16a088 Mon Sep 17 00:00:00 2001
From: James Addison
Date: Thu, 1 Jun 2023 13:20:29 +0100
Subject: [PATCH] Revert "e2scrub: use WantedBy=multi-user.target in
e2scrub_reap.servic
Package: e2fsprogs
Followup-For: Bug #1035543
X-Debbugs-Cc: jspri...@debian.org
On Thu, 1 Jun 2023 13:53:18 +0200, Jochen wrote:
> * James Addison [2023-06-01 12:44]:
> >Would reverting the Install.WantedBy modification[1][2], restoring
> >e2scrub_reap
> >enablement usin
On Thu, 1 Jun 2023 at 15:48, Theodore Ts'o wrote:
>
> In addition to Bookworm being hard frozen, I question the importance
> of this patch, the bug priority, and whether the title is correct.
> After all, at least with respect to e2fsprogs systemd unit *will*
> still be enabled. It will just be e
Followup-For: Bug #1035871
X-Debbugs-Cc: elb...@debian.org
[ not a maintainer, but I have tested the behaviour of this bug ]
On Thu, 1 Jun 2023 11:57:46 +0200, Paul wrote:
> On Wed, 10 May 2023 13:54:11 +0200 Andreas Beckmann wrote:
> > fonts-unifont does no longer ship unifont.ttf or other *.tt
Package: nsscache
Followup-For: Bug #1028454
Hi Thomas,
It looks like the functionality from python3-mock upstream[1] has been included
into Python >= 3.3. Would it make sense for nsswitch to migrate from mox3 to
the stdlib implementation instead of python3-mock?
Thanks,
James
[1] - https://gi
Package: python3.10
Followup-For: Bug #1030530
Perhaps a strange or seemingly off-topic question, but: is it fair to assume
that Python 3.11's improved (typical) performance characteristics should likely
result in similar-scale energy consumption reductions?
(I'd be likely, although cannot guara
Source: openjfx
Followup-For: Bug #1026962
Could the following build-related scripting be something to do with it?
-
https://salsa.debian.org/java-team/openjfx/-/blob/debian/11.0.11+1-1.1/modules/javafx.web/src/main/native/Tools/Scripts/webkitdirs.pm#L494-499
-
https://salsa.debian.org/jav
Source: pytorch-vision
Version: 0.14.1-1
Followup-For: Bug #1030736
For this version, the control file contains[1] 'X-Python3-Version: 3.10, 3.11'.
Adding that configuration to the *dh-python* source package (as a test), the
'Depends' entry for the resulting .deb file contains:
Depends: python
Source: python-pycdlib
Followup-For: Bug #1030535
Control: tags -1 fixed-upstream
Dear Maintainer,
This Python3.11 compatibility issue (along with a few similar fixups) is
resolved in version 1.13.0 of pycdlib (latest at the time-of-writing is 1.14.0).
Thanks,
James
Source: pysdl2
Followup-For: Bug #1030676
Control: forwarded -1 https://github.com/py-sdl/py-sdl2/issues/227
Control: tags -1 fixed-upstream
It looks like this has been fixed upstream in version 0.9.12 of the library.
Package: nodejs
Followup-For: Bug #1030284
Hi Thorsten,
Are you able to determine whether https://github.com/nodejs/node/issues/41163
(and/or any of the guidance within that thread) seems relevant to this bug?
If so, your repro example could be useful to help upstream/contributors to
develop and
Source: pysdl2
Followup-For: Bug #1030676
On Tue, 07 Feb 2023 at 21:07:50 +, Simon McVittie wrote:
> I have intentionally not uploaded those versions to unstable when doing
> team-uploads to stop it from regressing and blocking libsdl2, because
> I have no good way to test them: nothing in Deb
Source: qemu
Followup-For: Bug #1030545
For anyone else looking into this bug: it seemed to me that 'qcow2.c' is a
likely candidate for this infinite looping[1] behaviour to originate from.
The fact that metadata preallocation is enabled when it occurs could be
relevant information too.
(my gues
Source: qemu
Followup-For: Bug #1030545
(ack - that does seem like an unusually-timed coincidence. continuing on with
some unrelated investigation, though...)
There's a commit[1] from Y2019 that appears to describe a similar set of
circumstances - iothreads blocked forever for a bunch of backend
Source: qemu
Followup-For: Bug #1030545
> In the build logs for libguestfs, I see last successful builds were done
> on 5.10.0-20-s390x kernel, and on 5.10.0-21-s390x, all builds fails.
> 5.10.0-21-s390x is the one running on zelenka too.
Sorry for what I now worry may have been distractions in m
Source: qemu
Followup-For: Bug #1030545
After further investigation, the absence of the 'getenforce' binary in
the libguestfs build-deps appears to be a non-issue (and in hindsight was not
relevant in a 'src:qemu' bug thread, anyway). There is a comment[1] in
the source mentioning that failures t
Package: python3-zstandard
Followup-For: Bug #1031293
X-Debbugs-Cc: b...@debian.org, gregory.sz...@gmail.com
Hi Adrian, Gregory,
Reading the comment above the version check, it seems to indicate that Gregory
isn't particularly enthusiastic to provide support for environments where
there's a misma
Source: python-zstandard
Followup-For: Bug #1031443
Control: reassign -1 python3-zstandard 0.19.0-3
Control: affects -1 + src:python-zstandard
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031293
Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint
Source: python-scrapy
Followup-For: Bug #1031449
Control: package -1 python3-zstandard 0.19.0-3
Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 + src:libzstd src:python-scrapy src:rpmlint
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031293
Control: affects -1 + src:python-zstandard
Source: python-scrapy
Followup-For: Bug #1031449
Control: reassign -1 python3-zstandard 0.19.0-3
Control: affects -1 + src:libzstd src:python-scrapy src:python-zstandard
src:rpmlint
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 - src:python-scrapy src:rpmlint
Control: affects -1 + src:python-scrapy src:rpmlint
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031449
Control: affects -1 - src:rpmlint src:python-zstandard src:python-scrapy
Control: affects -1 + src:rpmlint src:python-scrapy src:python-zstandard
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 - src:rpmlint
Control: affects -1 + src:rpmlint
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031443
Control: affects -1 = src:python-scrapy src:libzstd src:rpmlint
src:python-zstandard
Control: merge -1 1031293
Package: python3-zstandard
Followup-For: Bug #1031443
Control: forcemerge -1 1031293 1031449
Package: openjdk-17-jre-headless
Followup-For: Bug #1029342
Looking at codesearch[1] for the word 'jexec', most of the contexts that appear
are from one of a few categories:
* The code of OpenJDK itself
* Scripts/code intended to run in FreeBSD environments (where 'jexec' is
used to run
Source: feynmf
Followup-For: Bug #1029439
Hi Thorsten,
I'm not completely sure yet (my TeX-foo isn't that great), but I have narrowed
the cause of the problem down.
It looks like the problem is something to do with the '\textlogo' command that
is used when the 'mflogo.sty' TeX package is availab
Package: python3-dateutil
Followup-For: Bug #1003044
I'm unable to replicate a matplotlib failure so far when using:
* python3-dateutil 2.8.2-1
* python3-matplotlib 3.6.3-1+b1
The repro step attempted was to open a Python interpreter session and to enter:
from matplotlib.dates import Dat
Package: python3-dateutil
Followup-For: Bug #1003044
Control: tags -1 moreinfo
On Tue, 21 Feb 2023 00:35:16 +, James Addison wrote:
> The repro step attempted was to open a Python interpreter session and to
> enter:
> from matplotlib.dates import DateFormatter
>
> (that su
Source: feynmf
Followup-For: Bug #1029439
Assuming that we want to keep the feynmf sources as-is (I think we do;
feynmf.dtx hasn't changed[1] since 1996, a sign of stability), then this bug
seems like a regression in another component.
Looking at the build logs for a failure-to-build[2] in this t
Source: feynmf
Followup-For: Bug #1029439
X-Debbugs-Cc: debian-tex-ma...@lists.debian.org
Control: tags -1 help
I'm adding the 'help' tag to this bug, and am cc'ing the debian-tex-maint list,
because it feels like extra brainpower could aid in figuring this one out more
quickly.
A brief recap of
Package: python3-dateutil
Followup-For: Bug #1003044
X-Debbugs-Cc: michael.pfu...@sartorius.com
Control: retitle -1 internal 'getzoneinfofile_stream' method emits a warning
message
Control: forwarded -1 https://github.com/dateutil/dateutil/issues/903
Control: tags -1 moreinfo
On Tue, 21 Feb 2023
On Wed, 22 Feb 2023 at 22:51, Hilmar Preuße wrote:
>
> On 2/21/23 22:00, James Addison wrote:
> Sorry, I'm not of any help here. At the first glance we look at a syntax
> error in the feynmf.dtx file however I'm wondering why this did not pop
> within the last > 25
Source: feynmf
Followup-For: Bug #1029439
My current best guess is that this commit line in latex3 that added a
dependency on 'hypdoc' to the 'latex/base/doc.sty' file could be the cause -
note that GitHub may not expand the 'doc.sty' file by default in some web
browsers due to their filtering of
On Thu, 23 Feb 2023 at 12:53, James Addison wrote:
>
> pass: texlive-base (2022.20220605-1) unstable; urgency=low
> fail: texlive-base (2022.20220923-2) unstable; urgency=medium
>
> It should be possible to look at the differences between those (and
> maybe the relate
Source: feynmf
Followup-For: Bug #1029439
Control: tags -1 patch
Source: feynmf
Followup-For: Bug #1029439
Control: tags -1 - help
Source: feynmf
Followup-For: Bug #1029439
On Fri, 24 Feb 2023 12:08:03 +0100, Jochen wrote:
> Fair point, attached is an alternative patch that works with the current
> doc package version.
I can confirm that the package builds successfully with this patch applied
as an alternative. The logo in
Package: nodejs
Followup-For: Bug #1030284
On Wed, 15 Feb 2023 14:54:03 +0100, Jérémy wrote:
> While waiting for the proper fix you describe, I propose to set higher
> constants
> for V8_DEFAULT_STACK_SIZE_KB - especially for arm64.
That sounded good to me when I read it a week ago, but now I'm n
Source: qemu
Followup-For: Bug #1030545
Control: tags -1 - help
Control: tags -1 + pending
Source: gcc-11
Followup-For: Bug #1004184
X-Debbugs-Cc: frederic-emmanuel.pi...@synchrotron-soleil.fr
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104914
Hi Frederic: I'm linking a forwarded GCC GNU bug report that I _think_ is the
upstream report matching this bug. I found
Package: nodejs
Followup-For: Bug #1030284
Control: forwarded -1 https://github.com/nodejs/node/issues/41163
Package: fakeroot
Followup-For: Bug #1030638
Hi josch,
Are you able to confirm whether the repro environment(s) for this bugreport
used emulated and/or native (non-emulated) 32-bit systems?
To explain my question: a qemu bug[1] that I was reading about a while ago
highlights that there are some
Package: libheif1
Version: 1.14.2-1
Followup-For: Bug #1029668
X-Debbugs-Cc: debian-multime...@lists.debian.org
The inability to read HEIC content using applications that depend on libheif1
could be a symptom of a more general codec-loading problem in that package:
Version 1.14.0 of upstream libh
Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@debian.org,
reply+aagshfqluldiwi3obwdg6lgb7if7fevbnhheauz...@reply.github.com
mirabilos gesagt:
> We know the default ulimits for users in Debian, and they are higher
> than the 1 MiB assumed by v8, by quite some factor, so this won’t
Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@debian.org
> My plan is to rebuild / retest reverse deps before hard freeze.
That's a good plan.
Do you know whether any of those tests include cases that spin up large (as in:
may consume more than 50% of a system's memory) numbers o
Source: python-bottle
Followup-For: Bug #1028743
Control: forwarded -1 https://github.com/bottlepy/bottle/issues/1410
Source: qemu
Followup-For: Bug #1030545
Control: block -1 by 1031753
Package: d-i.debian.org
Followup-For: Bug #1031923
Control: forcemerge 1031622 -1
Package: gcc-10
Version: 10.4.0-7
Followup-For: Bug #1023666
Bug #1004184 implies that gcc-11 cannot build correct mips64 code for a key
Debian package (source: matplotlib) without buildflag adjustments. However,
gcc-10 does emit correct code for the same package and architecture.
Should that be
Package: libkf5globalaccel-bin
Followup-For: Bug #1000955
X-Debbugs-Cc: lopi...@debian.org
Hi Filippo,
On Wed, 1 Dec 2021 12:12:44 +0100, Filippo wrote:
> Should I install other packages to fix the problem? What can I do to help?
Two ideas related to this part of your report:
> Note that I also
On Tue, Feb 28, 2023, 17:55 Thorsten Glaser wrote:
> Can you test it? I don’t have the bandwidth for that right now…
Should be able to, yep - I seem to remember seeing some repro instructions
from you on the GitHub thread and will give those a try in an emulator/vm.
That'd be great, thank you - my local (emulated) aarch64 build of
nodejs is proving to be much more time consuming than I expected.
On Tue, 28 Feb 2023 at 23:21, Jérémy Lal wrote:
>
>
>
> Le mar. 28 févr. 2023 à 19:06, James Addison a écrit :
>>
>> On Tue, Feb 28
If reproducible: would this bug be a good candidate for upload of a
fix to 'experimental' so that it can be alpha-tested by others?
On Wed, 1 Mar 2023 at 02:55, Jérémy Lal wrote:
>
>
>
> Le mer. 1 mars 2023 à 02:30, Thorsten Glaser a écrit :
>>
>> Jérémy Lal dixit:
>>
>> >I can build nodejs on a
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: yy.y.ja...@gmail.com
I'd like to contribute by testing d-i with Japanese input (I'm not a Japanese
speaker, but can offer some time to help).
My plan is to:
1. run the graphical d-i install of a fresh GNOME 43 system
2. s
Package: python3-tk
Followup-For: Bug #1031909
Some notes from inspecting (but not yet testing) the relevant scripts:
* There is an open merge request intended to fix a bug when too-many-files
are encountered by the lib2to3 'prerm' script:
* https://salsa.debian.org/cpython-team/python
Package: python3-django-hyperkitty
Followup-For: Bug #1031928
X-Debbugs-Cc: h...@hjp.at
Control: tags -1 moreinfo
Hi Peter,
I'd like to gain some experience with configuring email infrastructure, and
this bug seems like a good opportunity to learn.
I haven't yet been able to reproduce the self-c
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: ken...@xdump.org
On Thu, 02 Mar 2023 22:07:16 +0900 Kentaro Hayashi wrote:
> On Wed, 01 Mar 2023 16:47:22 +0000 James Addison wrote:
> > My plan is to:
> >
> > 1. run the graphical d-i install of a
necessarily long path through this. I'd been
looking for a reason to try the latest Debian installer (and may have learned
one or two things about it along the way, but I'll save any of that for
separate threads).
On Wed, 01 Mar 2023 16:47:22 + James Addison wrote:
> 2. select &
Package: python3-django-hyperkitty
Followup-For: Bug #1031928
Control: tags -1 - moreinfo
Control: tags -1 + confirmed
Control: severity -1 important
On Thu, 2 Mar 2023 20:30:04 +0100, Peter J. Holzer wrote:
> On 2023-03-02 19:53:12 +0100, Peter J. Holzer wrote:
> > So it seems that my suspicion t
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: s...@debian.org, z...@debian.org, ken...@xdump.org,
yy.y.ja...@gmail.com, iwama...@debian.org, gunna...@debian.org,
debian-i...@lists.debian.org, debian-japan...@lists.debian.org,
m...@packages.debian.org, ibus-an...@packages
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
(comment to bug-thread only)
If it's true that the cause is that 'tasksel' and 'gnome-initial-setup'
are mismatched, then we could apply a fix in either one.
Given that we have an existing patch available for 'gnome-initial-desktop',
I've
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
I also noticed that some of gnome-desktop's default locale-to-input-source
mappings provide multiple entries, delimited by the '+' character:
https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/43.2/libgnome-desktop/default-input-sources.h#
Package: pulseaudio
Followup-For: Bug #1032255
Control: retitle -1 pulseaudio: application restart required to restore sound
Control: severity -1 normal
Control: tags -1 moreinfo
Hi Dave,
Are there any clues (error messages, service start/stops, or things like that)
in the affected system's journ
Package: libgnome-desktop-4-2
Followup-For: Bug #1029821
X-Debbugs-Cc: gunna...@debian.org
On Fri, 3 Mar 2023 15:10:30 +0100, Gunnar wrote:
> On 2023-03-03 13:21, James Addison wrote:
> > I also noticed that some of gnome-desktop's default locale-to-input-source
> > mappi
Followup-For: Bug #1030284
There is one part of this patch that worries me, and it is the line:
> -//See issue crbug.com/405338
I'm not able to access that bug: neither anonymously nor when logged into my
gmail account. The comment would seem to indicate that it contains relevant
context ab
Followup-For: Bug #1028743
Control: tags -1 fixed-upstream
Note for maintainers: the patch attached to this bug has been merged into the
upstream 'release-0.12' branch and is included in the 0.12.5 release.
(so hopefully it is possible to drop the patch from packaging for that version
onwards)
T
Followup-For: Bug #1003044
On Tue, 21 Feb 2023 14:46:01 -0500, morph wrote:
> On Sun, Jan 29, 2023 at 9:45 AM Felix Geyer wrote:
> > How exactly does this break matplotlib?
> it produces output on stderr, which many tools consider it an error
> and fails build.
On Fri, 3 Mar 2023 15:05:03 -0500,
Package: nodejs
Followup-For: Bug #1030284
Echoing some notes and findings from the GitHub issue thread:
* https://crbug.com/405338 seems inaccessible to at least two people
* https://codereview.chromium.org/555943003 was initially proposed to resolve
that bug
* https://codereview.chr
Package: python3-dateutil
Followup-For: Bug #1003044
X-Debbugs-Cc: debian-le...@lists.debian.org
(adding debian-legal on cc for any sanity-checks available)
To recap: we have a bug, #1003044, that is rated 'grave', and so it is
considered release-critical for Debian bookworm, although without a w
Followup-For: Bug #1005886
Control: reassign -1 debian-cd
Control: retitle -1 debian-cd: bookworm net-install CD hangs on "Detecting
Network Hardware"
Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@debian.org
Guidance received from the V8 project (a vendored dependency in the upstream
NodeJS codebase) on the v8-dev mailing list is, in summary/interpretation:
* It is not yet safe to increase the stack size limit on ARM64 systems
Package: nodejs
Followup-For: Bug #1030284
X-Debbugs-Cc: t...@mirbsd.de
On Thu, 02 Feb 2023 01:56:10 +, Thorsten wrote:
> I consider this an architecture-specific release-critical bug. Maybe
> having a reproducer and access to a porterbox will allow a nodejs
> maintainer to track this down.
B
Followup-For: Bug #1000955
Control: severity -1 normal
A summary of a side-discussion between Filippo and myself about this bug:
* Although the bug doesn't appear reproducible today, the cause hasn't been
confirmed.
* We both agreed that it makes sense for bugs to continue to stay open u
Source: pylint
Followup-For: Bug #1032544
X-Debbugs-Cc: w...@wrar.name, lu...@debian.org
> This may be related, or just a duplicate, to #1032043, fixed in the newer
> version which is already in testing.
Yep, agreed that the updated testing package upload fixes this.
(it looks like the testing d
Package: python3-tk
Followup-For: Bug #1031909
Dear Maintainer,
Please find a merge request on Salsa to resolve this issue for future versions
of python3-tk at
https://salsa.debian.org/cpython-team/python3-stdlib/-/merge_requests/5
This has been tested by installing the previous version of the
Followup-For: Bug #1031909
Control: tags -1 patch
1 - 100 of 154 matches
Mail list logo
