Package: kupfer
Version: 327-1
Severity: grave
Tags: upstream fixed-upstream
Justification: renders package unusable
Dear Maintainer,
It appears a recent change in Debian has broken the ability of kupfer to run
commands (thereby making kupfer non-functional),
as covered in https://github.com/kupf
Control: reassign -1 gcc-14 14.1.0-1
Control: retitle -1 gcc-14: miscompiles code on s390x at -O2
Control: tag -1 upstream
Control: severity -1 normal
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116799
On Wed, Sep 18, 2024 at 02:40:11PM GMT, James McCoy wrote:
> On Wed,
I'm trying to narrow down what gcc-14 change introduced the problem.
Other big-endian platforms aren't seeing the same problem, so it seems
more like a compiler problem than a code problem to me.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
scripts/devscripts/ has been generated.
Thanks for the analysis and patch. I ended up applying the same change
as part of fixing #1079650.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
The test failures with this symptom:
ResourceWarning: Unclosed
are related to the anyio bump to 4.4.0 - see:
https://github.com/encode/starlette/discussions/2603
no fix committed upstream yet.
On Sat, Aug 31, 2024 at 08:08:02AM GMT, Paul Gevers wrote:
> Hi,
>
> On 31-08-2024 02:48, James McCoy wrote:
> > I wasn't able to reproduce this on amdahl. I attempted to reproduce it
> > locally via qemu and also couldn't reproduce it there.
>
> It seems it&
e 2
> 57s make: *** [debian/rules:8: autopkgtest] Error 25
I wasn't able to reproduce this on amdahl. I attempted to reproduce it
locally via qemu and also couldn't reproduce it there.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
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
looks like the
> last successful test probablly used 1.66 and the
> first failing test probablly used 1.70.
>From https://github.com/paholg/typenum/issues/211 it looks like it may
be related to https://github.com/rust-lang/rust/issues/114479.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
-DMSGPACK=1 -o src/webdis.o src/webdis.c
It's missing "-Wdate-time -D_FORTIFY_SOURCE=2" and the include
directories.
The relevant lines from debian/rules are
export DEB_BUILD_MAINT_OPTIONS=hardening=+bindnow
include /usr/share/dpkg/buildflags.mk
CFLAGS += $(CPPFLAGS)
The build is working in testing, so this regression is due to a recent change.
I've narrowed down the cause of the issue to a change in one of the following
packages:
- libxml2:
- build works with 2.9.14+dfsg-1.3+b3
- build fails with 2.12.7+dfsg-3+b1
- libxml2-utils:
- build works with 2.
tags 1065923 patch
thanks
On Sun, 10 Mar 2024 18:15:58 -0100 Graham Inggs wrote:
In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.
Searching through the code shows that distutils is not used, and is only
mentioned in comments.
Thank you Matthijs!
en moved out of Incoming.
> > The following information may help to resolve the situation:
> >
> > The following packages have unmet dependencies:
> > sbuild-build-depends-main-dummy : Depends:
> > librust-smithay-client-toolkit-dev (< 0.17~) but 0.18.1-1 is to be installed
> > E: Unable to correct problems, you have held broken packages.
> > apt-get failed.
I've uploaded rust-smithay-client-toolkit-0.16 to NEW, which will
address this until wlgreet can be ported to newer versions.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
ather than fix this directly in unstable's current alacritty package,
I'm going to finish the work to get the version in experimental uploaded
to unstable. This will address the issue, since experimental's
alacritty uses copypasta 0.10.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Package: between
Version: 6+dfsg1-4
Severity: grave
Tags: upstream
Justification: renders package unusable
X-Debbugs-Cc: jvalle...@mailbox.org
Dear Maintainer,
* What led up to the situation?
I installed between and tried to run it.
* What exactly did you do (or not do) that was effectiv
Upstream is currently working on this. For the time being adding
-D_LARGEFILE64_SOURCE fixes this bug
David JamesFrom 9b718bbf7f94899e7643563e9f30a6665d1e8b39 Mon Sep 17 00:00:00 2001
From: Castor216
Date: Tue, 4 Jun 2024 19:22:49 +0100
Subject: [PATCH] add -D_LARGEFILE64_SOURCE to CFLAGS
---
d
You may be interested in these upstream commits;
b01478d ("Fix some parts of macro expansion are not guarded")
0194b80 ("strerror and memset require string.h")
the peer address in the kernel at all (and may just ignore the
server's IPCP requests - I have not checked) and so avoids these issues.
JamesFrom 416b65c3f23d795707ed122f06c54eebd515bc3b Mon Sep 17 00:00:00 2001
From: James Cowgill
Date: Sat, 11 May 2024 13:59:17 +0100
Subject: [PATCH] Modify PPP peer address to avoid wrong rout
ge transition while being aware of a potential problem.
Thanks,
James
[1] - https://github.com/OpenTTD/OpenTTD/pull/10513
[2] - https://github.com/OpenTTD/OpenTTD/pull/12603
On Thu, 04 Apr 2024 19:01:58 +0200 Jonas Smedegaard wrote:
Quoting James Valleroy (2024-04-04 16:13:07)
> On 3/28/24 4:08 AM, Petter Reinholdtsen wrote:
> > [James Valleroy 2024-02-12]
> >> Here is a patch that fixes the build:
> >
> > Btw, did you mean TEMPFILE=$
On 3/28/24 4:08 AM, Petter Reinholdtsen wrote:
[James Valleroy 2024-02-12]
Here is a patch that fixes the build:
Thank you. Can you explain why changing the output from package.json to
mktemp and then moving the result to package.json will solve the build
problem? I fail to understand how
Upstream here. ocrmypdf does not actually require pypdf2 or pypdf for its
test suite anymore. That dependency was removed long before v15.2.0, so it
should be safe to remove the offending line from debian/tests/control.
-James Barlow
On Mon, Mar 25, 2024 at 6:06 AM Scott Kitterman
wrote:
>
Control: tag -1 pending
Hello,
Bug #1066715 in pcsxr reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/games-team/pcsxr/-/commit/31203d2510b77e3b807211f96034da593
Hi,
I have pushed a autolog 0.42.1 which should build correctly when
`-Werror=implicit-function-declaration` is used.
https://github.com/JKDingwall/autolog/releases/tag/0.42.1
Regards,
James
atch]
> > 9 | strcpy(buf, string);
> > | ^~
> > hello.c:9:5: note: include '' or provide a declaration of 'strcpy'
> > cc1: some warnings being treated as errors
> > make[2]: *** [Makefile:11: all] Error 1
Attached patch fixes these i
stop
/1e77b861739a56510aa1afa6e3ea1b24ab0cbd56
Add Breaks against neovim and emacs-libvterm
Closes: #1065731
Signed-off-by: James McCoy
(this message was generated automatically
Package: libvterm0
Version: 0.3.3-2
Severity: serious
Justification: Policy 8.6.2
The missing Breaks can allow partial upgrades and therefore break
the package, since the ABI changed.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-deb
Not sure if this helps, but I keep package lists of each build. Here is
a diff of 2/24 build (works) vs 3/24 (broken).
https://spins.tuxfamily.org/package-list-diff.txt I dont know if any
changes would break compiz, but at least its more info.
Jim
On 3/6/24 11:25, Steve Langasek wrote:
On We
Hi
This address is listed as a maintainer on the Compiz package search page.
0.8.18 black screens on boot after a recent update when building a iso with
livebuild. I have been building the xfce-Compiz iso for about 4 months
without issue. The xfce (testing amd64) iso is built without errors, but it
I did try this change but it the package test doesn't pass right now. I
think that supermin fails to understand virtual dependencies when
resolving packages and so fails to install various things. Maybe
once the time_t transition has completed and the affected packages are
binNMUed this should resolve itself?
James
Hi taffit,
On Tue, 5 Sep 2023 01:29:12 +0530 David =?iso-8859-1?Q?Pr=E9vot?=
wrote:
Hi James,
Le Wed, Jun 28, 2023 at 03:42:21PM -0300, Athos Ribeiro a écrit :
> Source: php-oscarotero-gettext
> Version: 4.8.7-1
[…]
> We are about to start the symfony 6 transition in unstable. Duri
to suggest fixing the cause of
this (the non-C90-compliant code in Python3.12 headers).
I'm intentionally not making it a blocker here, because other approaches are
possible, but am mentioning it for awareness.
Regards,
James
; else \
> > check_rb; \
> > fi
> > :86:in
> > `require':
> > /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/libsvn_swig_ruby-1.so.1:
> > undefined symbol: SWIG_snprintf -
> > /<>/BUILD/subversion/bindings/swig/ruby/.ext/svn/ext/core.so
> > (LoadError)
This is a bug in the bindings generated by SWIG, which is fixed in 4.2.1
but not yet uploaded. Reassigning.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
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
tags 1058552 patch
thanks
Here is a patch that fixes the build:
From: James Valleroy
Date: Sun, 11 Feb 2024 07:40:16 -0500
Subject: Use a temp file for package.json contents
---
Makefile | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index c9e03c2
dule packages aren't generally named according to the
SONAME (for reasons I'm not clear on).
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
t any "obvious"
renamings of lua packages on your list are probably misleading.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
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.
the patch author) and Broonie (as
zlib maintainer in Debian).
Regards,
James
[1] - https://bugs.launchpad.net/ubuntu/+source/burp/+bug/2046149
diff --git a/debian/changelog b/debian/changelog
index 1974a93..c18448e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+burp (3.1.4
perhaps it's safe to remove the conditional from
the Debian source package too?
The test failure can be found in the test regressions currently blocking the
migration of zlib 1.3 to Debian testing in debci[4][5].
Regards,
James
[1] - https://sources.debian.org/src/burp/3.1.4-3/utest/test_fzp.c/
is after
rebuilding with the patch in #997264):
libc6 (>= 2.14)
libgcc-s1 (>= 3.0)
libsfml-audio2.5
libsfml-graphics2.5
libsfml-network2.5
libsfml-system2.5
libsfml-window2.5
libstdc++6 (>= 13.1)
Fixing the CMakeLists.txt file should be enough to fix this because
dpkg-shlibdeps should be able to work it out from there.
James
Package: timeshift
Version: 22.11.2-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: truescore149...@gmail.com
Dear Maintainer,
User cant make BTRFS snapshots without "@" subvolume (debian uses "@rootfs"),
but user can make RSYNC snapshot. The problem is that when you t
om commit 9afbfb4d646cd240e97dbaae109f12bfc853112c)
Signed-off-by: James McCoy
Closes: #1052945
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1052945
close 1052799 1.2.2-1
thanks
rust-xcb (1.2.2-1) unstable; urgency=medium
t package a couple of the more useful/maintained ones and then just
RM vim-scripts.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
from testing.
There was already a bug noting that this still depends on gtk2. Merging
with that one and keeping its Severity: normal.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
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
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
tags 1035005 patch
thanks
The attached patch fixes this issue. I tested by unpacking the package into a
Debian bullseye VM where uwsgi-plugin-jvm-openjdk-11 was already installed.
--
James
From 84fe0c6bbf87399eb651b3768f6599bc08a83a78 Mon Sep 17 00:00:00 2001
From: James Valleroy
Date: Thu
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.
bug.
(note: I'm uncertain when/whether that update may be applied to zelenka, the
porterbox host, however)
Thanks,
James
[1] - https://tracker.debian.org/media/packages/l/linux/changelog-5.10.179-1
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
ommit/537cabca710f64b838d3b8b1dc986db596fb29d4
Closes: #1034875
Signed-off-by: James McCoy
(this message was generated automatically)
--
Greetings
https://bugs.debian.org/1034875
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 (
.
For bookworm, I'm going to stop installing kitty-open.desktop, by default.
Install, I will ship it under /usr/share/doc/kitty/examples and add a
note to README.Debian about it.
[0]:
https://github.com/kovidgoyal/kitty/commit/537cabca710f64b838d3b8b1dc986db596fb29d4
Cheers,
--
James
GPG Key:
x27;ve not used this particular
functionality of Kitty, so I'm not sure how this will change the usual
user experience.
However, I think this is a safer default and provides more information
to the user.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
Keeping the full text for Kovid's benefit.
On Wed, Apr 26, 2023 at 02:50:47PM +0200, Raphael Hertzog wrote:
> Package: kitty
> Version: 0.26.5-4
> Severity: serious
> Tags: security
> X-Debbugs-Cc: Debian Security Team
>
> Hello,
>
> I was reading https://lists.debian.org/20230425190728.ga1471.
tags 1011900 patch
thanks
I opened an MR to fix this issue:
https://salsa.debian.org/pkg-privacy-team/monkeysphere/-/merge_requests/1
OpenPGP_signature
Description: OpenPGP digital signature
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
uggested fix).
The (untested) patch I've attached here applies the suggested change to
src:gtk+3.0 (and was created from version gtk+3.0-3.24.37 of it).
I don't yet have an environment prepared to build and test it, but will try to
create one soon.
Thanks,
James
[1] - https://gitla
.0.9 and 3.0.13 if I read the upstream
history correctly.
(revert patch attached for convenience, although I'm not yet going to add the
corresponding tag to this bug until we confirm whether it's useful)
And if that headerfile does seem relevant: this issue may affect src:shim too
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
e policy baseline or changing to i586 are beyond my
skills (certainly in time for bookworm), so I'm offering the best option that I
can.
Thanks again,
James
[1] -
https://sources.debian.org/src/rustc/1.63.0%2Bdfsg1-2/debian/README.Debian/#L28-L32
[2] - https://sources.debian.org/src/rustc/
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
tk:amd64 (3.11.2-2) ...
With the fix applied, the following output appears:
Unpacking python3-tk:amd64 (3.11.2-2) over (3.10.8-1) ...
Setting up python3-tk:amd64 (3.11.2-2) ...
Thanks,
James
[1] -
https://salsa.debian.org/cpython-team/python3-stdlib/-/blob/3.10.8-1/debian/python3-tk.postinst.in#L9-21
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"
d to just ship the bundled timezone database with the package:
On Wed, 22 Feb 2023 11:52:25 +, James wrote:
> That may not be an option for us (at least without more work to find and
> package the sources of the relevant zoneinfo database): tz data content was
> removed from src:python-d
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,
on
onwards)
Thanks,
James
1 - 100 of 1016 matches
Mail list logo
