Bug#1039607: libjansi-java: causes maven to always output escape character
On Sat, Jul 15, 2023 at 03:56:01PM +0200, Emmanuel Bourg wrote: > On 08/07/2023 20:22, tony mancill wrote: > > > Emmanuel, do you recall what prompted the change? > > I think the issue is that when Maven runs in pbuilder, the TTY isn't > detected and colors get disabled (batch mode isn't used for Debian builds > though). If anything is changed please ensure that building with pdebuild > preserves the colors. Looking at the sources (finally), jansi already supports a mode to "force" [1] escape sequences, even when the output is not a terminal. I propose that we revert the patch and update the Java build tooling to set the property as desired for our builds. Once I get this tested and the property configured, I'll upload to experimental. Thanks, tony [1] https://salsa.debian.org/java-team/jansi/-/blob/738159f052f027fc0816c95ecc38a424f8aa3637/src/main/java/org/fusesource/jansi/AnsiConsole.java#L83-86
Bug#1059381: inkscape: Crashes when setting circle radius in document with tiny scale (huge viewBox extents)
Package: inkscape Version: 1.2.2-2+b1 Severity: normal Dear Maintainer, I have a document containing a circle. I think the actual radius of the circle is 3.985 cm, but Inkscape shows a radius value of 0.000 cm. When I try changing the radius of the circle, Inkscape crashes with the message: Inkscape encountered an internal error and will close now. Automatic backups of unsaved documents were done to the following locations: ... This is printed to standard error: --- terminate called after throwing an instance of 'Geom::Exception' what(): lib2geom exception: assertion failed: B.isFinite() (./src/2geom/sbasis-to-bezier.cpp:485) Emergency save activated! Emergency save document locations: [... omitted ...].svg Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at https://inkscape.org/report with a detailed description of the steps leading to the crash, so we can fix it. --- Also: if I draw a new circle in this document and try setting the radius values the same way, the same symptoms occur. The issue also occurs in the upstream Inkscape AppImage (version 1.3.2 (091e20e, 2023-11-25)), so I've already reported it upstream as well: https://gitlab.com/inkscape/inbox/-/issues/9723 However, in the newer AppImage version, Inkscape doesn't crash, but prints a similar message to standard error and behaves incorrectly (scales the circle to be too large). I don't know if the difference in behavior is because of changes between versions 1.2.2 and 1.3.2, or if it is because of build options chosen by Debian to favor a crash instead of trying to proceed through a failed assertion. There may not be much point in this Debian bug report since what is essentially the same issue appears upstream, but hopefully this helps Debian users who are experiencing the issue and might be searching bug reports. I hope any upstream fix can be expedited for Debian stable users in the next point release. The issue occurs specifically in this document (attached), which was originally generated by the SVG plot function in pcbnew 6.0.11 (the KiCad PCB Editor). I performed some edits to the SVG document with Inkscape and hit this issue on one circle in particular. This is a cut-down test case, with all objects other than the circle deleted. My guess is that the large viewBox extents (`0 0 297002200 210007200`) that pcbnew chose for the root `` element are triggering this issue. It seems like pcbnew chose these viewBox extents for the convenience of using nanometer values when writing the document, and letting the `viewBox` and `width`/`height` attributes scale the object sizes and positions to the right real distance units. The document is probably valid, but I'm not an SVG expert; I don't know if the specification warns against or forbids huge values. There's no indication to Inkscape users that there's anything unusual with the document scaling through normal editing. All the object sizes and positions look fine. You have to check the Document Properties or read the SVG file to notice this issue (or run into this Inkscape issue). The issue seems to follow the document. For a simple document like this one with just one layer, I can adjust the viewBox extents to work around the bug: 1. Select all objects and cut to the clipboard. 2. Open Document Properties. 3. Choose a reasonable Scale value. It was previously set to 0.01 cm per user unit in this document, so I chose 1 cm per user unit. 4. Paste In Place to restore the objects. Or, more simply: 1. Select all objects and copy to the clipboard. 2. Create a new document. 3. Paste In Place to transfer the objects. -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages inkscape depends on: ii lib2geom1.2.0 1.2.2-3 ii libatkmm-1.6-1v5 2.28.3-1 ii libboost-filesystem1.74.0 1.74.0+ds1-21 ii libc6 2.36-9+deb12u3 ii libcairo-gobject2 1.16.0-7 ii libcairo2 1.16.0-7 ii libcairomm-1.0-1v5 1.14.4-2 ii libcdr-0.1-1 0.1.6-2+b2 ii libfontconfig1 2.14.1-4 ii libfreetype6 2.12.1+dfsg-5 ii libgc1 1:8.2.2-3 ii libgcc-s1 12.2.0-14 ii libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1 ii libglib2.0-0 2.74.6-2 ii libglibmm-2.4-1v5 2.66.5-2 ii libgomp1 12.2.0-14 ii libgsl27 2.7.1+dfsg-5 ii libgspell-1-2 1.12.0-1+b2 ii libgtk-3-0
Bug#896016: strace: please make the build reproducible
Source: strace Followup-For: Bug #896016 X-Debbugs-Cc: la...@debian.org, reproducible-b...@lists.alioth.debian.org Looking at the Reproducible Builds build history[1] for strace on Debian, all _successful_ builds I see between Y2019 and today, across all four architectures listed (amd64, arm64, armhf, i386) have produced reproducible results. As a result of that, I agree that the Apr 2018 fix[2] (released Jun 2018) mentioned by Chris has provided reproducibility for strace. Unfortunately there are plenty of FTBFS failures -- mostly test timeouts on some architectures, alongside libfaketime errors that seem to affect i386 -- but those seem like separate problems. Perhaps we could close this bug? [1] - https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/strace.html [2] - https://github.com/strace/strace/commit/fc8294cbc2ac907737d85abca55b854bd426ab50
Bug#1059383: neomutt: conffiles not removed: /etc/neomuttrc.d/smime.rc /etc/neomuttrc.d/gpg.rc
Package: neomutt
Version: 20231103+dfsg1-1
Severity: normal
User: debian...@lists.debian.org
Usertags: obsolete-conffile adequate
The recent upgrade did not deal with obsolete conffiles properly.
Please use the dpkg-maintscript-helper support provided by
dh_installdeb to remove these obsolete conffiles on upgrade.
https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
https://manpages.debian.org/man/1/dh_installdeb
This bug report brought to you by adequate:
https://bonedaddy.net/pabs3/log/2013/02/23/inadequate-software/
$ p=neomutt ; adequate $p ; dpkg-query -W -f='${Conffiles}\n' $p | grep obsolete
neomutt: obsolete-conffile /etc/neomuttrc.d/smime.rc
neomutt: obsolete-conffile /etc/neomuttrc.d/gpg.rc
/etc/neomuttrc.d/smime.rc d25e75a8d59c32061f275fb823da07a1 obsolete
/etc/neomuttrc.d/gpg.rc fa01d034c3ba43eb0899bcca8e8b4903 obsolete
-- System Information:
Debian Release: trixie/sid
APT prefers testing-debug
APT policy: (900, 'testing-debug'), (900, 'testing'), (800,
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700,
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages neomutt depends on:
hi libc6 2.37-12
ii libgnutls30 3.8.2-1
ii libgpgme11 1.18.0-4+b1
ii libgsasl18 2.2.0-2
ii libgssapi-krb5-2 1.20.1-5
ii libidn2-0 2.3.4-1+b1
ii liblmdb0 0.9.31-1
ii liblua5.4-0 5.4.6-1
ii liblz4-1 1.9.4-1
ii libncursesw6 6.4+20231209-1
ii libnotmuch5 0.38.2-1
ii libpcre2-8-0 10.42-4
ii libsqlite3-0 3.44.2-1
ii libtinfo6 6.4+20231209-1
ii libtokyocabinet9 1.4.48-15
ii libzstd1 1.5.5+dfsg2-2
ii sensible-utils 0.0.20
ii zlib1g 1:1.3.dfsg-3
Versions of packages neomutt recommends:
ii locales 2.37-12
ii mailcap 3.70+nmu1
Versions of packages neomutt suggests:
ii aspell 0.60.8-6
ii ca-certificates 20230311
ii exim4-daemon-light [mail-transport-agent] 4.97-2
ii gnupg 2.2.40-1.1
ii ispell 3.4.05-1
ii openssl 3.1.4-2
pn urlview
Versions of packages neomutt is related to:
ii neomutt 20231103+dfsg1-1
-- no debconf information
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Bug#1059352: src:apt: fails to migrate to testing for too long: autopkgtest regression on armhf
Hi Julian, On 23-12-2023 20:40, Julian Andres Klode wrote: I know this is automated but I feel lije it would be sensible to scan It's *mostly* automated. the logs for well known bugs so that you don't end up filing bugs against every package broken by valgrind's missing support for the new NOP sequences in binutils. I do *some* minor triaging, but I didn't know this to be a common problem. Where do you think I should have picked this up? Anyways, this bug is already closed (when I submitted) and because apt is a key package, it doesn't even do anything against apt, so the bug serves mostly for tracking purposes. Paul OpenPGP_signature.asc Description: OpenPGP digital signature
