Bug#1071335: upstream commits

2024-05-17 Thread James Cameron
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")

Bug#1069693: ppp >=2.5.0 breaks network-manager-fortisslvpn

2024-05-11 Thread James Cowgill
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 route --- src/nm-fortisslvpn-service.c | 30 ++ 1

Bug#1070208: openttd: cmake licensing concern for openttd 14.0 source package

2024-05-01 Thread James Addison
aware of a potential problem. Thanks, James [1] - https://github.com/OpenTTD/OpenTTD/pull/10513 [2] - https://github.com/OpenTTD/OpenTTD/pull/12603

Bug#1058552: [Pkg-javascript-devel] Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input

2024-04-05 Thread James Valleroy
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=$

Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input

2024-04-04 Thread James Valleroy
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

Bug#1061264: ocrmypdf: Uses deprecated/to be removed pypdf2 in autopkgtest

2024-03-26 Thread James Barlow
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

Bug#1066715: marked as pending in pcsxr

2024-03-26 Thread James Cowgill
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:

Bug#1066269: autolog: FTBFS: autolog.c:613:9: error: implicit declaration of function ‘re_comp’; did you mean ‘regcomp’? [-Werror=implicit-function-declaration]

2024-03-18 Thread James Dingwall
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

Bug#1066261: lintian: FTBFS: hello.c:9:5: error: implicit declaration of function 'strcpy' [-Werror=implicit-function-declaration]

2024-03-16 Thread James McCoy
gt; > | ^~ > > 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 issues. This is also available as MR!496 on Salsa. Cheers, -- James

Bug#1063754:

2024-03-12 Thread james
stop

Bug#1065731: marked as pending in libvterm

2024-03-09 Thread James McCoy
/1e77b861739a56510aa1afa6e3ea1b24ab0cbd56 Add Breaks against neovim and emacs-libvterm Closes: #1065731 Signed-off-by: James McCoy (this message was generated automatically

Bug#1065731: libvterm0: Missing Breaks for rdeps that were built against libvterm 0.1

2024-03-09 Thread James McCoy
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,

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread James Bielefeldt
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

Bug#1065666: Compiz 0.8.18 appears to be broken in testing

2024-03-08 Thread James Bielefeldt
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

Bug#1065610: libguestfs0t64: All appliance dependencies lost during time_t transition

2024-03-07 Thread James Cowgill
d 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

Bug#1039733: php-oscarotero-gettext: FTBFS with symfony 6: make[1]: *** [debian/rules:18: override_dh_auto_test] Error 1

2024-02-29 Thread James Valleroy
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

Bug#1057442: onboard ftbfs with Python 3.12

2024-02-27 Thread James Addison
uggest 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

Bug#1064680: subversion: FTBFS: :86:in `require': /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/li

2024-02-25 Thread James McCoy
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

Bug#1036828: debian-cd: wrong firmware archives built and published for D-I releases?

2024-02-24 Thread James Addison
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

Bug#1036828: debian-cd: wrong firmware archives built and published for D-I releases?

2024-02-24 Thread James Addison
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

Bug#1058552: science.js: FTBFS: SyntaxError: Error parsing /<>/package.json: Unexpected end of JSON input

2024-02-12 Thread James Valleroy
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

Bug#1062674: lua-compat53: NMU diff for 64-bit time_t transition

2024-02-07 Thread James McCoy
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

Bug#1063254: lua-luv: identified for time_t transition but no ABI in shlibs

2024-02-05 Thread James McCoy
mings of lua packages on your list are probably misleading. Cheers, -- James GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB

Bug#1060802: stellarium: FTBFS on armel, ppc64el, s390x: unsatisfiable Build-Depends: qtwebengine5-dev (>= 5.15)

2024-01-31 Thread James Addison
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 |

Bug#1057880: burp: FTBFS with zlib 1.3 due to 'make check' failure

2023-12-22 Thread James Addison
Source: burp Followup-For: Bug #1057880 X-Debbugs-Cc: kapo...@melix.org Thank you, Jérémy.

Bug#1057880: burp: FTBFS with zlib 1.3 due to 'make check' failure

2023-12-14 Thread James Addison
(as 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

Bug#1057880: burp: FTBFS with zlib 1.3 due to 'make check' failure

2023-12-09 Thread James Addison
nal 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/#L182 [2] - https://sources.debian.org/src/b

Bug#1057114: seriousproton: Does not link against or depend on all needed libraries

2023-11-29 Thread James Cowgill
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

Bug#1056608: timeshift: Timeshift cant restore RSYNC snapshots if your system installed on BTRFS with wrong subvolume

2023-11-23 Thread James Morgan
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

Bug#1052945: marked as pending in neovim

2023-09-29 Thread James McCoy
) Signed-off-by: James McCoy Closes: #1052945 (this message was generated automatically) -- Greetings https://bugs.debian.org/1052945

Bug#1052799: closing 1052799

2023-09-26 Thread James McCoy
close 1052799 1.2.2-1 thanks rust-xcb (1.2.2-1) unstable; urgency=medium

Bug#1051063: vim-scripts: no license assumption must be non-free

2023-09-21 Thread James McCoy
ple 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

Bug#1050396: RM: pangoterm -- RoQA; low popcon; depends on gtk2

2023-08-23 Thread James McCoy
ed 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

Bug#1035871: flare-engine: broken symlink: /usr/share/games/flare/mods/default/fonts/unifont-10.0.06.ttf -> ../../../../../fonts/truetype/unifont/unifont.ttf

2023-06-02 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-06-01 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-06-01 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-06-01 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-06-01 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-05-31 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-05-31 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-05-30 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-05-29 Thread James Addison
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-05-26 Thread James Addison
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

Bug#1035005: [PATCH] Add Replaces on uwsgi-plugin-jvm-openjdk-11 (Closes: #1035005)

2023-05-19 Thread James Valleroy
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

Bug#1035543: init-system-helpers: new systemd units may not get enabled on upgrades from bullseye if systemd is installed

2023-05-16 Thread James Addison
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 ...

Bug#1030545: qemu-(img|system-s390x) hang on s390x bullseye kernel

2023-05-16 Thread James Addison
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#1030545: qemu-(img|system-s390x) hang on s390x bullseye kernel

2023-05-13 Thread James Addison
this 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

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
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).

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
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

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
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: |-

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
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 +++ nodejs

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
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 invo

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
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 provide fur

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-13 Thread James Addison
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 have implemente

Bug#1034875: marked as pending in kitty

2023-05-12 Thread James McCoy
/537cabca710f64b838d3b8b1dc986db596fb29d4 Closes: #1034875 Signed-off-by: James McCoy (this message was generated automatically) -- Greetings https://bugs.debian.org/1034875

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-12 Thread James Addison
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. > >

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-12 Thread James Addison
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

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-12 Thread James Addison
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

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-05-11 Thread James Addison
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 (

Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script

2023-05-08 Thread James McCoy
r 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: 4096R/91BF

Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script

2023-05-08 Thread James McCoy
ctionality 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

Bug#1034875: kitty: Should not handle application/x-sh mime type by executing the script

2023-05-03 Thread James McCoy
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

Bug#1011900: monkeysphere: FTBFS: ...Could not chdir to home directory /home/user42: No such file or directory

2023-04-29 Thread James Valleroy
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

Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box

2023-04-25 Thread James Addison
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

Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box

2023-04-24 Thread James Addison
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

Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box

2023-04-24 Thread James Addison
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

Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box

2023-04-22 Thread James Addison
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

Bug#1034289: inkscape: canvas stops updating completely when trying to edit a text box

2023-04-20 Thread James Addison
(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://gitlab.gnome.org/GNOME/gtk/-/issues

Bug#994274: syslinux: FTBFS with gnu-efi 3.0.13

2023-04-05 Thread James Addison
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. Thanks, James [1] - https

Bug#973414: rustc: produces non-baseline opcodes for compiler_builtins::int::udiv::__udivmoddi4 on i386

2023-04-03 Thread James Addison
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

Bug#973414: rustc: produces non-baseline opcodes for compiler_builtins::int::udiv::__udivmoddi4 on i386

2023-03-31 Thread James Addison
inly 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/1.63.0%2Bdfsg1-2/debian/rules/#L31 [3] - https://sources.debian.org/

Bug#1005886: debian-cd: bookworm net-install CD hangs on "Detecting Network Hardware"

2023-03-22 Thread James Addison
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

Bug#1031909: python3-tk: bytecode not removed on upgrade

2023-03-15 Thread James Addison
Followup-For: Bug #1031909 Control: tags -1 patch

Bug#1031909: python3-tk: bytecode not removed on upgrade

2023-03-15 Thread James Addison
) ... 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

Bug#1032544: pylint: FTBFS in testing: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13

2023-03-13 Thread James Addison
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

Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend

2023-03-13 Thread James Addison
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

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-11 Thread James Addison
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.

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-11 Thread James Addison
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

Bug#1005886: cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware"

2023-03-11 Thread James Addison
Followup-For: Bug #1005886 Control: reassign -1 debian-cd Control: retitle -1 debian-cd: bookworm net-install CD hangs on "Detecting Network Hardware"

Bug#1003044: internal 'getzoneinfofile_stream' method emits a warning message

2023-03-06 Thread James Addison
1: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-dateutil (the source of this package) to resolve > previous bug #665894, relat

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-06 Thread James Addison
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 *

Bug#1003044: internal 'getzoneinfofile_stream' method emits a warning message

2023-03-05 Thread James Addison
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

Bug#1028743: python-bottle: FTBFS: AssertionError: b'OK' != "URLError(ConnectionRefusedError(111, 'Connection refused'))"

2023-03-04 Thread James Addison
) Thanks, James

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-04 Thread James Addison
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

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

2023-03-03 Thread James Addison
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 > > mappings p

Bug#1032255: pulseaudio: sound keeps dying (on Tiger Lake)

2023-03-03 Thread James Addison
://wiki.debian.org/PulseAudio Cheers, James

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

2023-03-03 Thread James Addison
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:

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

2023-03-03 Thread James Addison
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

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

2023-03-02 Thread James Addison
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,

Bug#1031928: python3-django-hyperkitty: Javascript not loaded because of HTML error

2023-03-02 Thread James Addison
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

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

2023-03-02 Thread James Addison
sarily 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 'anthy' in 'gnom

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

2023-03-02 Thread James Addison
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

Bug#1031928: python3-django-hyperkitty: Javascript not loaded because of HTML error

2023-03-01 Thread James Addison
no mailing lists configured. Checking the HTML source of the page, I did see some tags -- including for 'popper.js' -- each of them had a closing tag, as expected. Could you provide any more information on configuration steps / settings that may be required to reproduce the problem? Thanks! James

Bug#1031909: python3-tk: bytecode not removed on upgrade

2023-03-01 Thread James Addison
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: *

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

2023-03-01 Thread James Addison
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.

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-03-01 Thread James Addison
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

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-02-28 Thread James Addison
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, 202

Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

2023-02-28 Thread James Addison
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.

Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend

2023-02-28 Thread James Addison
nal, and that could cause high CPU usage for that service. All a theory so far, but if you are able to replicate the behaviour (I realize it has been a while since your report) then I would suggest taking a look at the service logs in journalctl to see if there are any clues there, and let us know.

Bug#1023666: gcc-10 should not be shipped in bookworm

2023-02-28 Thread James Addison
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

  1   2   3   4   5   6   7   8   9   10   >