On Fri, 28 Mar 2025 at 22:30, Rebecca N. Palmer wrote:
> [ ... snip ... ]
> The part you refer to isn't the autopkgtest failure - pandas' pymysql
> and psycopg2 tests are known not to work in our test environments, so
> the main autopkgtest doesn't install these. To monitor this, an extra
> 'igno
(hello - I feel some responsibility for this bug, because I have been
eager for matplotlib 3.10 to be included in trixie)
Although I haven't attempted to run the autopkgtests locally for this
version of pandas, I have begun inspecting the source package and
build logs.
Of the existing Debian patc
addition, use the gimp-console command in preference to gimp,
because the former seems more reliable for non-interactive use.
.
Backported with minor adjustments from an upstream pull request.
Origin: https://github.com/OpenTTD/OpenGFX/pull/95
Bug-Debian: https://bugs.debian.org/1090256
Author: James
On Tue, 4 Mar 2025 at 22:26, Étienne Mollier wrote:
> [ ... snip ... ]
> > Please find attached a patch that rewrites the _helpers.pyx code to
> > construct the relevant objects natively as bytes (immutable), resolving
> > the runtime error while hopefully not degrading performance
> > significant
cts natively as bytes (immutable), resolving
the runtime error while hopefully not degrading performance
significantly.
Regards,
James
[1] -
https://sources.debian.org/src/python-sqt/0.8.0-8/sqt/_helpers.pyx/#L436-L437
Description: Avoid runtime typecasting of bytearray to bytes
Author: James Addi
Package: devscripts
Followup-For: Bug #1098681
Control: retitle -1 devscripts 2.25.3: autopkgtests fail to find the lzip
command
Control: tags -1 - ftbfs
My apologies - I now understand that autopkgtest failures are not categorized
as FTBFS, and am adjusting this bugreport accordingly.
Package: devscripts
Version: 2.25.3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
For bug #1061479 the devscripts package recently added support for lz
compression; the resulting source package appears to fail autopkg
Source: mate-desktop
Followup-For: Bug #1086464
Control: forwarded -1 https://github.com/mate-desktop/mate-desktop/issues/631
Associating this RC bug with an existing upstream bugreport for the same.
Package: libglx-mesa0
Followup-For: Bug #1092890
X-Debbugs-Cc: mity...@debian.org
Dear Maintainer, Dmitry,
This is conjecture, but I wondered whether an adjustment to the meson linkage
options for libgallium_dri[1] around the same time (not contained in the same
commit, but chronologically nearby
Source: openttd-opengfx
Followup-For: Bug #1090256
Control: forwarded -1 https://github.com/OpenTTD/OpenGFX/issues/94
Source: openttd-opengfx
Followup-For: Bug #1090256
Control: retitle -1 openttd-opengfx: FTBFS: script-fu errors with GIMP3
Dear Maintainer,
With the major upgrade to GIMP3 in Debian unstable, failures occur attempting
to build the composite GRF graphics files in openttd-opengfx.
So far I've iden
Writing with my apologies as the author/originator of this bug in the
upstream codebase (it is a side-effect of a copyright-related
changeset[1]).
I seemingly-independently wrote a patch today to resolve the cause
that I've opened as a pull request[2] upstream -- but I have to admit
that I _did_ r
Source: toulbar2
Followup-For: Bug #1080187
X-Debbugs-Cc: paolo.gre...@libpf.com
I don't have a fix for this bug yet, but I do want to mention that the
underfull hbox messages may be a distraction in the logs; I think the error
that causes the build to fail may be this line:
error: Could not cr
Package: debian-www
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: la...@debian.org
Dear Maintainer,
Visiting the www.debian.org homepage currently seems to display a Former Debian
Partners listing, instead of the expected homepage.
cc'ing Thomas as there are some recent e
On Wed, 9 Oct 2024 at 07:46, Johannes Schauer Marin Rodrigues
wrote:
> I think you just missed a dinstall. I forked your repo and successfully ran
> all
> the jobs from your pipeline:
>
> https://salsa.debian.org/josch/quadrilateralcowboy/-/pipelines/744459
Brilliant! Thank you. I'll be more p
Package: libc6-dev-amd64-cross
Followup-For: Bug #1081201
X-Debbugs-Cc: jo...@debian.org, d...@debian.org
Hi Josch, Matthias,
I noticed that cross-toolchain-base (72) has landed in unstable today, and I
was quietly hoping that that would resolve what I believe is the same build
problem during Sal
Source: gcc-11
Followup-For: Bug #1004184
Control: fixed -1 gcc-14/14.1.0-1
I haven't yet confirmed that the output of an O1/O2 build is corrected when
compiling on MIPS, but the relevant patches have arrived in gcc v14.1 and are
packaged in Debian, so I'm updating the tags on this bug to record t
Thank you Matthijs!
Source: openttd
Version: 14.0-1
Severity: serious
Tags: upstream
Justification: Policy 12.5
Control: forwarded -1 https://github.com/OpenTTD/OpenTTD/pull/12603
Dear Maintainer,
The build scripts for the initial version 14.0 release of OpenTTD include a
CMake file that determines whether and how t
Followup-For: Bug #1057442
X-Debbugs-Cc: tsu.y...@gmail.com
Hi Bo,
On Wed, 6 Dec 2023 17:31:52 +0800, Bo wrote:
> I think it is okay to remove `-Wdeclaration-after-statement` option
> which to support Arch linux build from code comment.
FYI: I've reported #1064028 against Python3.12 to suggest f
Followup-For: Bug #1036828
X-Debbugs-Cc: k...@debian.org
On Sat, 24 Feb 2024 11:01:31 +, I wrote:
> Should this bug be closed? (the logic to skip the experimental/sid firmware
> image build during non-testing builds is in place for both bookworm and
> trixie)
Nope, it looks like I've misund
Followup-For: Bug #1036828
X-Debbugs-Cc: k...@debian.org
Hi Cyril,
Should this bug be closed? (the logic to skip the experimental/sid firmware
image build during non-testing builds is in place for both bookworm and trixie)
Regards,
James
Source: stellarium
Followup-For: Bug #1060802
X-Debbugs-Cc: tom...@debian.org, mity...@debian.org
> stellarium 23.4-1 added a new build-dependency on qtwebengine5-dev, which
> prevents it from building on some release architectures (and all non-release
> ones).
Would 'qtwebengine5-dev | libqt5web
Source: burp
Followup-For: Bug #1057880
X-Debbugs-Cc: kapo...@melix.org
Thank you, Jérémy.
Source: burp
Followup-For: Bug #1057880
X-Debbugs-Cc: z...@debian.org, broo...@debian.org
Dear Maintainer,
Attached is a patch that includes the changes applied by Ubuntu[1] to remove
the problematic unit test version check from their source package.
For visibility, on cc are Shengjing Zhu (as t
Source: burp
Version: 3.1.4-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: j...@jp-hosting.net
Dear Maintainer,
The unit tests for 'burp' perform a version check[1] on zlib to decide[2]
between a choice of zip-related a
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
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
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
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
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
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
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
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
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
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
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
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.
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 #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 #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
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
-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
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
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 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 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 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 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 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 (
Package: libgtk-3-0
Version: 3.24.37-2
Followup-For: Bug #1034289
Control: severity -1 important
As mentioned previously: although this bug seemed RC-level in the context of
Inkscape, libgtk3 has a sizable set of dependent packages, so in that context,
and given that release-preparation time is fi
Package: libgtk-3-0
Followup-For: Bug #1034289
X-Debbugs-Cc: giuseppe.bilo...@gmail.com
Hi Giuseppe,
If possible: can you share some more information about your use-case for XIM
as an input method (either with Inkscape in particular, or more generally on
the relevant system(s)).
Thanks,
James
Followup-For: Bug #1034289
X-Debbugs-Cc: giuseppe.bilo...@gmail.com, debian-multime...@lists.debian.org
Control: reassign -1 libgtk-3-0
Control: affects -1 inkscape
Control: tags -1 patch
After testing the patch (that is based on a suggestion in an upstream GTK bug
discussion thread[1]), I can con
Package: inkscape
Version: 1.2.2-2+b1
Followup-For: Bug #1034289
After installing a fresh Debian bookworm system and installing the 'inkscape'
package (version 1.2.2-2+b1), I can confirm that this issue is reproducible; it
can be found by running:
$ GTK_IM_MODULE=xim inkscape
... and from ther
b.gnome.org/GNOME/gtk/-/issues/2560
[2] - https://gitlab.gnome.org/GNOME/gtk/-/issues/2560#note_757809
Description: gdkwindow: allow frame paint events to occur for non-toplevel
windows
.
Partially-reverts upstream commit fc569f1ac6ff108afc17f7f439480273826af3a6.
Author: James Addison
Bug: https://g
Followup-For: Bug #994274
X-Debbugs-Cc: lu...@schwaighofer.name, pk...@debian.org, timo.lindf...@iki.fi
Hi Lukas, Philipp, Timo,
Does reverting the removal[1] of 'efisetjmp.h' from 'efi.h' in src:gnu-efi
produce successful results?
That occurred between gnu-efi versions 3.0.9 and 3.0.13 if I rea
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
On Mon, 3 Apr 2023 23:07:35 +0200, Fierelier wrote:
> * In terms of confusion: I think using the Rust i586 toolchain, and
> building for i586 with Rust might be less confusing, because altering
> the i686 definitions for rustc will make i
Package: rustc
Followup-For: Bug #973414
X-Debbugs-Cc: fierel...@gmail.com
Hi Fierelier - thanks for your previous comment, here's my reply, slightly
later than I'd hoped:
On Wed, 29 Mar 2023 00:10:52 +0200, Fierelier wrote:
> - issue 1: i386, i486, i586, i686 are considered as Pentium 4 in LLVM,
Followup-For: Bug #1005886
X-Debbugs-Cc: powe...@gmail.com
Control: reassign -1 cdimage.debian.org
Control: retitle -1 cdimage.debian.org: bookworm net-install CD hangs on
"Detecting Network Hardware"
Sorry (both to you Tony, and also the Debian CD team) for confusion and wasting
time - I mistake
Followup-For: Bug #1031909
Control: tags -1 patch
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
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
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
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
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
Followup-For: Bug #1005886
Control: reassign -1 debian-cd
Control: retitle -1 debian-cd: bookworm net-install CD hangs on "Detecting
Network Hardware"
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
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
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,
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 #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
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
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
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: 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
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: 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
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: 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
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: 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: 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
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
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
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.
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
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: d-i.debian.org
Followup-For: Bug #1031923
Control: forcemerge 1031622 -1
Source: qemu
Followup-For: Bug #1030545
Control: block -1 by 1031753
Source: python-bottle
Followup-For: Bug #1028743
Control: forwarded -1 https://github.com/bottlepy/bottle/issues/1410
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
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: 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: 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: nodejs
Followup-For: Bug #1030284
Control: forwarded -1 https://github.com/nodejs/node/issues/41163
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
Source: qemu
Followup-For: Bug #1030545
Control: tags -1 - help
Control: tags -1 + pending
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: 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
Source: feynmf
Followup-For: Bug #1029439
Control: tags -1 - help
1 - 100 of 152 matches
Mail list logo
