Bug#1026881: x2go works on debian 12 release

[Peter Barth]

apparently, X2go works on the release version of debian 12.
I've tested with the desktop environment MATE.

glx keeps to be broken, (glxinfo, ... private request) but that seems
to be a known issue on almost all platforms (fedora, ubuntu).

imho, the bug report can be closed.

Bug#1039572: sl-modem-dkms: module fails to build for Linux 6.3

[أحمد المحمودي]

On Tue, Jun 27, 2023 at 06:51:04PM +0200, Andreas Beckmann wrote:
> WARNING: modpost: 
> /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/slamr.o: section 
> mismatch in reference: amrmo_pci_driver (section: .data) -> amrmo_pci_probe 
> (section: .init.text)
> /var/lib/dkms/sl-modem/2.9.11~20110321/build/drivers/.amrlibs.o.cmd: No such 
> file or directory
---end quoted text---

What does that mean ?

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

[forest . owlet]

Hi,

Here's a backtrace from the latest ntpsec coredump.

root@karita:/var/lib/systemd/coredump# export
DEBUGINFOD_URLS="https://debuginfod.debian.net;
root@karita:/var/lib/systemd/coredump# coredumpctl debug
  PID: 61726 (ntpd)
   UID: 110 (ntpsec)
   GID: 117 (ntpsec)
Signal: 11 (SEGV)
 Timestamp: Fri 2023-06-30 02:33:27 UTC (59min ago)
  Command Line: /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf
-g -N -u ntpsec:ntpsec
Executable: /usr/sbin/ntpd
 Control Group: /system.slice/ntpsec.service
  Unit: ntpsec.service
 Slice: system.slice
   Boot ID: 0e943a6b0cfe4fdd9e032c3d91c9d58d
Machine ID: 0e50b80b858599a4a8aa8383662e5bb4
  Hostname: karita
   Storage:
/var/lib/systemd/coredump/core.ntpd.110.0e943a6b0cfe4fdd9e032c3d91c9d58d.61726.168809240700.zst
(present)
  Size on Disk: 775.6K
   Message: Process 61726 (ntpd) of user 110 dumped core.

Module libnss_systemd.so.2 from deb
systemd-252.6-1.amd64
Stack trace of thread 61726:
#0  0x7f280d4e0ab3 aesni_set_encrypt_key
(libcrypto.so.3 + 0xe0ab3)
#1  0x7f280d6f3d45 cipher_hw_aesni_initkey
(libcrypto.so.3 + 0x2f3d45)
#2  0x7f280d7397fb cipher_generic_init_internal
(libcrypto.so.3 + 0x3397fb)
#3  0x7f280d7398cb ossl_cipher_generic_einit
(libcrypto.so.3 + 0x3398cb)
#4  0x7f280d60993b EVP_CipherInit_ex (libcrypto.so.3
+ 0x20993b)
#5  0x560b2e1246f3 AES_SIV_Init (ntpd + 0x4c6f3)
#6  0x560b2e1255df AES_SIV_Decrypt (ntpd + 0x4d5df)
#7  0x560b2e10f40d nts_unpack_cookie (ntpd +
0x3740d)
#8  0x560b2e10f85b extens_server_recv (ntpd +
0x3785b)
#9  0x560b2e0f78ce receive (ntpd + 0x1f8ce)
#10 0x560b2e0ed8ea read_network_packet (ntpd +
0x158ea)
#11 0x560b2e0ef3cf input_handler (ntpd + 0x173cf)
#12 0x560b2e0e819f mainloop (ntpd + 0x1019f)
#13 0x7f280d16718a __libc_start_call_main (libc.so.6
+ 0x2718a)
#14 0x7f280d167245 __libc_start_main_impl (libc.so.6
+ 0x27245)
#15 0x560b2e0e84e1 _start (ntpd + 0x104e1)
ELF object binary architecture: AMD x86-64

GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/ntpd...
Reading symbols from
/usr/lib/debug/.build-id/8b/c6f9398efb6b8c446b2d719831f5738d563c84.debug...
[New LWP 61726]

This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to
.gdbinit.
Downloading separate debug info for
/lib/x86_64-linux-gnu/libnss_systemd.so.2
Downloading separate debug info for /lib/x86_64-linux-gnu/libgcc_s.so.1
Downloading separate debug info for system-supplied DSO at
0x7ffc94772000
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/ntpd -p /run/ntpd.pid -c
/etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  aesni_set_encrypt_key () at crypto/aes/aesni-x86_64.s:4104
Download failed: Invalid argument.  Continuing without source file
./build_shared/crypto/aes/aesni-x86_64.s.
4104crypto/aes/aesni-x86_64.s: No such file or directory.
(gdb) bt
#0  aesni_set_encrypt_key () at crypto/aes/aesni-x86_64.s:4104
#1  0x7f280d6f3d45 in cipher_hw_aesni_initkey (dat=0x560b2f082b50,
key=, keylen=)
at ../providers/implementations/ciphers/cipher_aes_hw_aesni.inc:37
#2  0x7f280d7397fb in cipher_generic_init_internal
(ctx=0x560b2f082b50,
key=0x10 , keylen=16,
iv=0x0,
ivlen=0, params=0x0, enc=1)
at ../providers/implementations/ciphers/ciphercommon.c:218
#3  0x7f280d7398cb in ossl_cipher_generic_einit (vctx=,
key=, keylen=, iv=,
ivlen=, params=)
at ../providers/implementations/ciphers/ciphercommon.c:228
#4  0x7f280d60993b in EVP_CipherInit_ex (ctx=,
cipher=, impl=impl@entry=0x0, key=,
iv=iv@entry=0x0, 

Bug#1039956: ITP: subarch-select -- Select among binaries based upon x86 microarchitecture support

[Michael R. Crusoe]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: cru...@debian.org

Subject: ITP: subarch-select -- Select among binaries based upon x86 
microarchitecture support
Package: wnpp
Owner: Michael R. Crusoe 
Severity: wishlist

* Package name: subarch-select
  Version : 0.1
  Upstream Author : Erik Garrison 
* URL : https://github.com/ekg/subarch-select/
* License : Expat
  Programming Lang: C++
  Description : Select among binaries based upon x86 microarchitecture 
support
 Pick an executable based on CPU capabilities.
 .
 Call subarch-select with argument pairs that list CPU features
 (as in /proc/cpuinfo "flags"), and a path to execute if the flags are all
 matched. The first set of flags that match the system capabilities will select
 the given path. Arguments to the program should be passed after "--".
 .
 Also supports the x86-64 microarchitectures: x86-64-v2, x86-64-v3, v86-64-v4

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/subarch-select

Bug#1039955: fonts-liberation should provide /usr/share/fonts/truetype/liberation2 for backwards compatibility

[Nilesh Patra]

Package: fonts-liberation
Version: 1:2.1.5-2
Severity: important
X-Debbugs-Cc: ti...@debian.org, fab...@debian.org

Hi Fabian,

Thanks for your work on fonts-liberation.

As stated in recent transition[1], fonts-liberation package has taken
over liberation2 and the latter is now just an empty binary package for
transistional reason.

However, fonts-liberation2 used to vendor the files in 
/usr/share/fonts/truetype/liberation2/
as seen here[2] which has now been pruned[3]. This is breaking packages
that rely on usr/share/truetype/liberation2 for symlinking ttf files
and/or using them in code. One such example is r-cran-fontsliberation
which has now a bunch of broken symlinks.
For now, I've worked around this and pushed commits to salsa, but I'd
like this to be fixed properly.

Could you consider to vendor truetype/liberation2 as a symlink to
truetype/liberation?

[1]: https://lists.debian.org/debian-devel/2023/06/msg00220.html
[2]: https://packages.debian.org/bookworm/all/fonts-liberation2/filelist
[3]: https://packages.debian.org/sid/all/fonts-liberation/filelist

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_IN, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8), LANGUAGE=en_US.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information


signature.asc
Description: PGP signature

Bug#1038920: python3-certbot-dns-gandi: Update from Debian 11 -> 12 leaves certificate updates broken

[Harlan Lieberman-Berg]

On Fri, Jun 23, 2023 at 6:24 AM Norbert Preining  wrote:
> with the update of certbot and the DNS Gandi plugin, the command line
> arguments for requesting a certificate have changed.

Hello Norbert,

Thanks for letting me know.  I've spoken with upstream about this as
well, and to see what we can do in the future to ensure something like
this doesn't happen again. I've written up a draft preinst script that
should rewrite the config files to remove the problem.

Do you still have a host that's in the buggy state, or did you fix
them all with the workaround?  Because it's going to be fixed in a
preinst, I'd like more testing (and more eyes) on it than I normally
would, just for caution's sake.

Sincerely,

-- 
Harlan Lieberman-Berg
~hlieberman

Bug#888548: kismet: Update to a more recent version

[Christoph Anton Mitterer]

Hey.

Just wondered whether this package has been orphaned? 2022-08-R1 is out
since last year, making the current version outdate for ~6 years...
possibly also missing any security fixes then (at least any such fixes
which weren't recognised as security relevant).


Cheers,
Chris.

Bug#1039714: gobject-introspection: dh_girepository does not fetch all symbols from GIR files

[أحمد المحمودي]

On Wed, Jun 28, 2023 at 05:00:10PM +0200, Thomas Uhle wrote:
> 2. dh_girepository does not fetch the 41 symbols from HarfBuzz-0.0.gir
>that are compiled into libharfbuzz-gobject.so.0.  I have attached a
>small patch for it, so that the missing symbols are also dumped into
>the dummy C file that is temporarily generated and compiled for
>dh_shlibdeps.
>This updated version of dh_girepository would also find another 245
>symbols in Gio-2.0.gir for instance.
---end quoted text---

But why doesn't this bug show itself on sparc64 arch ?
Both gir1.2-harfbuzz and gir1.2-freedesktop depend on their respective 
library packages on sparc64 archs only.

-- 
‎أحمد المحمودي (Ahmed El-Mahmoudy)
 Digital design engineer
GPG KeyIDs: 4096R/A7EF5671 2048R/EDDDA1B7
GPG Fingerprints:
 6E2E E4BB 72E2 F417 D066  6ABF 7B30 B496 A7EF 5761
 8206 A196 2084 7E6D 0DF8  B176 BC19 6A94 EDDD A1B7


signature.asc
Description: PGP signature

Bug#1039954: ITP: gomuks -- Terminal based Matrix client written in Go

[Nilesh Patra]

Package: wnpp
Severity: wishlist
Owner: Nilesh Patra 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org

* Package name: gomuks
  Version : 0.3.0
  Upstream Authors: https://github.com/tulir/gomuks/issues
  URL : https://github.com/tulir/gomuks
* License : AGPL-3+
  Description : Terminal based Matrix client written in Go
 Gomuks is a terminal based Matrix client written in
 Golang which uses mautrix and mauview.


signature.asc
Description: PGP signature

Bug#1039743: Support phpunit 10

[Athos Ribeiro]

A fix proposal is available at
https://salsa.debian.org/php-team/pear/christianriesen-base32/-/merge_requests/2

--
Athos Ribeiro

Bug#1036351: I intend to adopt the binutils-msp430

[Thiago Marques]

retitle 1036351 ITA: binutils-msp430 -- Binary utilities supporting
TI's MSP430 targets


Hi,
I saw that the package is orphan, I'd like to adopt.
Regards,


-- 
*   Thiago Marques.*

Bug#1039102: debian-policy: make systemd units mandatory for packages shipping system services

[Luca Boccassi]

On Sun, 25 Jun 2023 11:21:53 -0700 Russ Allbery  wrote:
> Luca Boccassi  writes:
> 
> > systemd upstream will drop support for the transitional sysv
generator
> > in the near future. The transition is long finished, it's been at
least
> > a decade, and it's time for the tail of packages still shipping
only
> > init scripts but not units to be updated.
> 
> Has there already been a mass bug filing for packages that ship init
> scripts but not systemd unit files?
> 
> > Tentatively this should happen within Trixie's development cycle.
Of
> > course it's free software and generators are not that difficult to
> > maintain, so if someone wanted to lift the sysv generator out of
the
> > systemd repository and adapt it to be a standalone binary there's
> > nothing stopping them. But I wouldn't want the systemd package to
> > depend on such a backward compat tool, so packages needing this
> > hyptothetical package should depend explicitly on it. This is just
> > mentioned for completeness, it's been at least a decade and writing
a
> > unit file is beyond trivial so there shouldn't be any issue adding
the
> > few remaining ones.
> 
> > Once the policy is updated I plan to ask Lintian to bump the
severity
> > of the existing check:
> 
> > https://salsa.debian.org/lintian/lintian/-/merge_requests/407
> 
> Assuming the mass bug filing hasn't already happened and I missed it,
I
> think this is the wrong order.  This sort of large-scale breaking
change
> should always start with a mass bug filing against all affected
packages.
> I think the right process is:
> 
> * Raise this in debian-devel and propose a mass bug filing requiring
all
>   packages to add systemd unit files if they currently only have init
>   scripts.  This gives people the opportunity to object or take over
>   maintenance of the unit file generator and document how to depend
on it
>   if they wish to do that instead.  (I don't think that's a good
idea, but
>   we should let the discussion happen.)
> 
> * Unless something surprising happens in that discussion, do a mass
bug
>   filing for this transition and bump the Lintian severity at the
same
>   time.
> 
> * Once that has consensus and is underway, *then* change Policy to
reflect
>   this project decision.
> 
> If the mass bug filing already happened and I just didn't notice, my
> apologies.

This happened a few days ago and nobody complained (if we ignore
grumblings because of the fact that I used lintian.debian.org queries
which are hopelessly and silently out of date, sigh), and bugs are
filed, there have been a couple of uploads too already.

Can we go ahead, or do you want to wait a specified amount of time? If
so, how long (just so that I know when to come back)?

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1039926: svglite requires rebuild under R 4.3.*

[Dirk Eddelbuettel]

On 29 June 2023 at 10:22, Dirk Eddelbuettel wrote:
| 
| Package: r-cran-svglite
| Version: 2.1.1-1
| Severity: normal
| 
| R 4.3.0 brought (once again) a new graphics API which requires a rebuild for
| functionality that involves creating graphics device.  Once rebuilt the
| following will again work:
| 
| > getRversion()
| [1] ‘4.3.1’
| > packageVersion("svglite")
| [1] ‘2.1.1’

This accidentally omitted

library(svglite)

The package loads fine, but like the others will not create a graphics device
as it was built under the previous R 4.2.* series.

Dirk

| > svglite(tempfile())
| Error in svglite_(filename, bg, width, height, pointsize, standalone,  : 
|   Graphics API version mismatch
| > 
| 
| R Core decided again not to call this a breaking change, and I concur. We may
| want to look into a graphics api tag for the next release. For now, a simple
| rebuild should do.
| 
| Thanks, Dirk
| 
| --
| dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1039953: tikzDevice requires rebuild under R 4.3.*

[Dirk Eddelbuettel]

Package: r-cran-tikzdevice
Version: 0.12.4-1
Severity: normal

R 4.3.0 brought (once again) a new graphics API which requires a rebuild for
functionality that involves creating graphics device.  Once rebuilt the
following will again work:

> getRversion()
[1] ‘4.3.1’
> packageVersion("tikzDevice")
[1] ‘0.12.4’
> library(tikzDevice)
Warning message:
In fun(libname, pkgname) : 

tikzDevice: No appropriate LaTeX compiler could be found.
Access to LaTeX is required in order for the TikZ device
to produce output.

[... rest of warnings omitted; I ran this in a container without latex ...]
> tikz(tempfile())
Error in tikz(tempfile()) : Graphics API version mismatch
>

R Core decided again not to call this a breaking change, and I concur. We may
want to look into a graphics api tag for the next release. For now, a simple
rebuild should do.

Thanks, Dirk


-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1039744: Add support for phpunit 10

[Athos Ribeiro]

A fix proposal is available at
https://salsa.debian.org/php-team/pear/christianriesen-otp/-/merge_requests/3

--
Athos Ribeiro

Bug#1038813: aide 0.17.3-4+deb11u2 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1038813 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: aide
Version: 0.17.3-4+deb11u2

Explanation: fix handling of extended attributes on symlinks

Bug#1037182: bullseye-pu: package bmake/20200710-14+deb11u1

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Wed, Jun 07, 2023 at 11:23:29AM +0200, Andreas Beckmann wrote:
> add Conflict against unfixed bsdowl versions, i.e. the version from
> buster that may have survived the upgrade to bullseye since bsdowl is
> not part of bullseye.

Please go ahead.

Thanks,


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1039040: cups 2.3.3op2-3+deb11u3 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1039040 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: cups
Version: 2.3.3op2-3+deb11u3

Explanation: security fixes

Bug#1036314: mujs 1.1.0-1+deb11u3 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1036314 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: mujs
Version: 1.1.0-1+deb11u3

Explanation: security fix

Bug#1036046: debian-parl 1.9.27+deb11u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1036046 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: debian-parl
Version: 1.9.27+deb11u1

Explanation: rebuild using newer boxer-data

Bug#1036044: debian-design 3.0.22+deb11u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1036044 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: debian-design
Version: 3.0.22+deb11u1

Explanation: rebuild using newer boxer-data

Bug#1039933: bookworm-pu: package bepasty/1.0.0-1+deb12u1

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Thu, Jun 29, 2023 at 06:47:38PM +0200, Elena Grandi wrote:
> The upload is necessary to fix bug #1038452 (
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038452 ) in bepasty,
> a pastebin with support for multiple media types: because of an
> incompatibility with Pygments-2.12.0 that I didn't spot during the
> testing cycle (my fault) bepasty in bookworm is no longer able to
> display the rendered version of text uploads.

Please go ahead.

Thanks,


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1038000: bookworm-pu: package texlive-bin/2022.20220321.62855-5.1+deb12u1

[Hilmar Preuße]

On 6/28/23 09:01, Jonathan Wiltshire wrote:

Hi Jonathan,


When do you expect the bugs to be closed in unstable?


I've pushed the new texlive-bin and the context package to unstable.

Hilmar
--
Testmail

Bug#1039862: bookworm-pu: cpdb-libs/1.2.0-2+deb12u1

[Jonathan Wiltshire]

Control: tag -1 confirmed

On Wed, Jun 28, 2023 at 09:54:22PM +, Thorsten Alteholz wrote:
> The attached debdiff for cpdb-libs fixes CVE-2023-34095 Bookworm. This CVE
> has been marked as no-dsa by the security team.
> 
> The fix just restricts the usable buffer and should have no side effects.

Please go ahead.

Thanks,


-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1

Bug#1036300: curl 7.74.0-1.3+deb11u8 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1036300 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: curl
Version: 7.74.0-1.3+deb11u8

Explanation: security fixes

Bug#1039952: alacritty: broken rendering with Source Code Pro

[brian m. carlson]

Package: alacritty
Version: 0.11.0-4
Severity: normal
Tags: upstream fixed-upstream

If the user has configured Source Code Pro as the terminal font, then
text is rendered very tiny and squashed at the top of the window.

To reproduce:

1. Install texlive-fonts-extra.
2. mkdir -p ~/.fonts
3. ln -s /usr/share/texlive/texmf-dist/fonts/opentype/adobe ~/.fonts
4. Run fc-cache.
5. Modify the configuration file to contain this block:


font:
  normal:
family: Source Code Pro
style: Regular


6. Restart Alacritty if `live_config_reload` isn't specified.
7. Notice that the text is tiny and squashed at the top of the terminal
and you can't read anything at all.

I believe this is fixed in 0.12.0 and was tracked upstream at
https://github.com/alacritty/alacritty/issues/6048.  This will probably
be fixed simply by updating Alacritty to the latest version, so it would
be great if that could happen.

-- System Information:
Debian Release: trixie/sid
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-1-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages alacritty depends on:
ii  libc6   2.36-9
ii  libfontconfig1  2.14.1-4
ii  libfreetype62.12.1+dfsg-5
ii  libgcc-s1   13.1.0-6
ii  libxcb1 1.15-1

alacritty recommends no packages.

alacritty suggests no packages.

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1039951: libreoffice-writer: First and last inner vertical borders in tables are invisible across all rows in Hebrew locale

[Daniel Hevron Pereh]

Package: libreoffice-writer
Version: 4:7.4.5-3
Severity: normal
X-Debbugs-Cc: dhpe...@mailbox.org

Dear Maintainer,

This issue occures only when Formats -> Lacale setting is set to Hebrew, and 
the app is restarted for the setting to take affect.
On other tested locale (English) it doesn't happen.

Simply adding a table will create one with fully visible border lines except 
first and last inner vertical borders.
Trying to make them visible doesn't work. It applies to both rendered table and 
printed file or exported PDF.
The visibility issue is dynamic. If you delete cells with problematic border, 
it will switch to the new first/last inner border.

Tested current flatpak version 7.5.4.2. seems to fixed in it.

steps to reproduce: Change locale setting to Hebrew and restart. Simply add a 
table.


-- Package-specific info:
Configuration filePackage Exists Changed
/etc/libreoffice/registry/writer.xcd  libreoffice-writer  Yes No
All deployed bundled extensions:

Identifier: com.sun.star.comp.Calc.NLPSolver
  Version: 0.9
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: This extension integrates into Calc and offers new Solver 
engines to use for optimizing nonlinear programming models.

  bundled Packages: {
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver/help
  is registered: yes
  Media-Type: application/vnd.sun.star.help
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/nlpsolver/components.rdb
  is registered: yes
  Media-Type: application/vnd.sun.star.uno-components
  Description: 

  }

Identifier: com.sun.wiki-publisher
  Version: 1.2.0
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher
  is registered: yes
  Media-Type: application/vnd.sun.star.package-bundle
  Description: The Wiki Publisher enables you to create Wiki articles on 
MediaWiki servers without having to know the syntax of the MediaWiki markup 
language. Publish your new and existing documents transparently with the Writer 
to a wiki page.

  bundled Packages: {
  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/help
  is registered: yes
  Media-Type: application/vnd.sun.star.help
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcs
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-schema
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiEditor/
  is registered: yes
  Media-Type: application/vnd.sun.star.basic-library
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/components.rdb
  is registered: yes
  Media-Type: application/vnd.sun.star.uno-components
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Addons.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/ProtocolHandler.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/WikiExtension.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: 
vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/OptionsDialog.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Filter.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Types.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  URL: vnd.sun.star.expand:$BUNDLED_EXTENSIONS/wiki-publisher/Paths.xcu
  is registered: yes
  Media-Type: application/vnd.sun.star.configuration-data
  Description: 

  }

All deployed shared extensions:


All deployed user extensions:



Experimental features enabled:

Installed VCLplugs:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version  Architecture Description
+++----=
un  libreoffice-gtk3   (no description available)
ii  libreoffice-kf5  4:7.4.5-3amd64office productivity suite -- KDE 
Frameworks 5 integration
ii  libreoffice-qt5  4:7.4.5-3amd64office productivity suite -- Qt 
5 integration

Java (javaldx):

Bug#1039609: sudo 1.9.13p3-1+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1039609 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: sudo
Version: 1.9.13p3-1+deb12u1

Explanation: fix event log format

Bug#1039026: cups 2.4.2-3+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1039026 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: cups
Version: 2.4.2-3+deb12u1

Explanation: security fixes

Bug#1037078: dh-python 5.20230130+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1037078 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: dh-python
Version: 5.20230130+deb12u1

Explanation: re-introduce Breaks+Replaces on python2 needed to help apt in some 
upgrade scenarios

Bug#877512: slapd: enabled systemd integration (untested patch)

[Ryan Tandy]

On Wed, Jun 28, 2023 at 01:03:33PM -0700, Ryan Tandy wrote:
SLAPD_CONF is also used (at least) by anyone who still uses a 
slapd.conf file instead of cn=config. Using -f or -F depending on what 
SLAPD_CONF points to was the main reason I assumed we'd need a wrapper 
script. But that could also be replaced by a drop-in.


I remembered later that the maintainer scripts also need to know the 
location of the config, for upgrades. Currently they get it by reading 
SLAPD_CONF from /etc/default/slapd. Not sure whether it would be 
feasible to parse that out from the slapd command line in a systemd 
unit. Probably not in the general case... (but of course a determined 
person can find ways to break the current setup as well.)

Bug#1038616: bookworm-pu: package network-manager-strongswan/1.6.0-1+deb12u1

[Ian Jackson]

Harald Dunkel writes ("Bug#1038616: bookworm-pu: package 
network-manager-strongswan/1.6.0-1+deb12u1"):
> I made a mistake on the pu for network-manager-strongswan: I missed to
> set you on CC. I am very sorry.

No problem, it just meant you had to ping me ...

> AFAICT the upload to Bookworm has been approved. Would you mind to check?

Indeed so.  Now done.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1021339: New upstream (0.8+) available

[Samuel Henrique]

Upstream stopped providing .deb files after 0.8.3 :(

James, let me know if there's anything I can do to help packaging the
latest release, in case you have more than one package pending.

Thanks for maintaining nvim.

-- 
Samuel Henrique 

Bug#1039754: Support phpunit10

[Athos Ribeiro]

A fix is available through
https://salsa.debian.org/php-team/pear/matthiasmullie-path-converter/-/merge_requests/1

--
Athos Ribeiro

Bug#1039950: LoadError: cannot load such file -- spamcheck/spamcheck_pb

[Praveen Arimbrathodiyil]

Package: ruby-spamcheck
version: 1.10.1-1
severity: grave
Control: tags -1 help

When trying to install gitlab 15.11.6 (still in progress in salsa) it 
fails with


LoadError: cannot load such file -- spamcheck/spamcheck_pb

We need to build spamcheck_pb.rb using 
https://gitlab.com/gitlab-org/gl-security/security-engineering/security-automation/spam/spamcheck/-/blob/main/Makefile#L26


gitaly rules file has an example of how this is done for ruby-gitaly.


OpenPGP_0x8F53E0193B294B75.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1038693: qt6-declarative-dev: inappropriately included cmake file

[Lisandro Damián Nicanor Pérez Meyer]

As a workaround passing -DQT_SKIP_AUTO_PLUGIN_INCLUSION=ON solves this issue.

I need to check if we can propagate this variable from qtbase itself.

signature.asc
Description: This is a digitally signed message part.

Bug#1039105: Fails to start with Emacs 28

[Ian Jackson]

Control: severity -1 serious

This bug makes the package very hard to use.  It fails to work, by
default.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#877512: slapd: enabled systemd integration (untested patch)

[Moritz Mühlenhoff]

Am Wed, Jun 28, 2023 at 01:03:33PM -0700 schrieb Ryan Tandy:
> Hmm. So on upgrade I suppose we would want to automatically migrate those
> settings to a drop-in? That actually sounds doable; such a drop-in would
> probably not have to be a conffile.

Indeed, so my idea was that e.g. the systemd unit would default to User=openldap
and Group=openldap and then the postinst could check if /etc/default/slapd has
SLAPD_GROUP and/or SLAPD_USER set to something other than "openlap" and in that
case a drop-in would be generated with those settings. Similar for Kerberos etc.

> > The most commonly used option is probably SLAPD_OPTIONS, which could also
> > be read via an EnvironmentFile from /etc/default.
> 
> Right. Although if that's the only thing still being consumed, I'd be
> tempted to just let it go too. :)

Actually, that's a fair point, then there would be a clean cut so that it's
obvious that /etc/default/slapd is only relevant for folks not using systemd.
Again, SLAPD_OPTIONS could easily also be a drop-in after all.

> Thanks for the input, it really does help. :)

Glad to help!

Cheers,
Moritz

Bug#1039105: Fails to start with Emacs 28

[Ian Jackson]

Dirk Eddelbuettel writes ("Bug#1039105: Fails to start with Emacs 28"):
>   After updating my main machine (and the only one running vm along and
> exim4, dovecot, spamassassin and whatnot) to Ubuntu 23.04 with its Emacs 28.2
> (in an upgrade from 22.10 with Emacs 27.*), I found that vm (which I have
> been using all those years, still with some hooks and key-binding you emailed
> to in the mid-1990s (!!)) would no longer start.

Thanks for the report.  And thanks to the others for the further
information.

I can reproduce the problem and the suppression of byte compilation
does indeed fix it.

It's a bit funky to reproduce, because emacs likes to byte-compile
things when it's idle with the effect that naive "emacs --batch" runes
don't show the problem.

I'll do a stable update.  But first I am going to upload to sid,
as per the stable release policy.  And I'm adding a test, since I did
manage to get a reliable repro.

I confess I don't understand the upstream package very well.

Ian.

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1039949: RM: pads -- RoQA; dead upstream, unmaintained, depends on obsolete libs

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: p...@packages.debian.org
Control: affects -1 + src:pads

Please move pads. It's dead upstream, orphaned without a new maintainer since 
2015
and depends on the legacy PCRE.

Bug#1000118: generator-scripting-language: depends on obsolete pcre3 library

[Luca Boccassi]

Control: severity -1 wishlist
Control: tags -1 help

On Thu, 18 Nov 2021 11:49:04 + Matthew Vernon 
wrote:
> Source: generator-scripting-language
> Severity: important
> User: matthew-pcre...@debian.org
> Usertags: obsolete-pcre3
> 
> Dear maintainer,
> 
> Your package still depends on the old, obsolete PCRE3[0] libraries
> (i.e. libpcre3-dev). This has been end of life for a while now, and
> upstream do not intend to fix any further bugs in it. Accordingly, I
> would like to remove the pcre3 libraries from Debian, preferably in
> time for the release of Bookworm.
> 
> The newer PCRE2 library was first released in 2015, and has been in
> Debian since stretch. Upstream's documentation for PCRE2 is available
> here: https://pcre.org/current/doc/html/
> 
> Many large projects that use PCRE have made the switch now (e.g. git,
> php); it does involve some work, but we are now at the stage where
> PCRE3 should not be used, particularly if it might ever be exposed to
> untrusted input.

As already mentioned, this package is not used to process untrusted
input, it is a 'done' project that hasn't been touched in a decade and
just works as part of an existing toolchain. If someone provides a
patch, that is tested against such workflows to confirm that they are
not affected, then I'd merged it, upstream.

If push came to shove, I will simply vendor the existing pcre code.

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

[Richard Lewis]

I think you might be missing one md5sum - I found 4 versions in the git repos

#
for x in $(git log debian/header.txt | awk '/commit/{print $2}'); do
git show $x:debian/header.txt | md5sum ; done

d9206d89f2f8d85d346a23da90459862  -
a32fc12d69628d96756fd3af3f8b3ecd  -
dbc1e8d136180d247b572f6a19c4e92e  -
1bc54d3bfb0d1e61104d5780a318ced2  -
#

the top one being the current version, the middle two the same as you
found and the one at the end '1bc54...' is from a commit dated
2004-04-19 (which might mean when woody was stable, i think, although
this seems to be the date cvs2svn was run)

presumably, we can then remove all this in trixie (if anyone remembers)

On Wed, 28 Jun 2023 at 13:29, Andreas Beckmann  wrote:
>
> New version of the patch fixing a wrong checksum. Now logcheck upgrade
> paths starting from ancient releases look clean ;-)
>
> Andreas

Bug#1039533: Offer a way to just print the numbers, not also the units

[Adrian Mariano]

> But in fact, --terse should say:
> 
>-t, --terse
>   Print only a single conversion factor.  This option can be  used
>   when  calling  units  from another program so that the output is
>   easy to parse.  This option has the combined effect of these op‐
>   tions:   ‘--strict’  ‘--quiet’  ‘--one-line’  ‘--compact’.  When
>   combined with ‘--version’ it produces a display showing only the
>   program name and version number. And here we even strip
>   the units off:
> 
>   $ units --terse mile meters
>   1609.344

I think you're not fully understanding what's going on.  There is
no unit to "strip off".  If you don't use --terse, this is what happens:

adrian> units mile meters
* 1609.344
/ 0.00062137119

Note that no unit appears.  You get the other clutter, but no units,
because conversions DO NOT HAVE UNITS.  

Definitions have units.  You were trying to use a definition when you
should have been using a conversion.  In any case some additional
explanation and examples won't hurt, so I'll try to elaborate on this
in the manual.

For definitions, actually, the output can be even more cluttered:

adrian> units --terse mile
5280 ft = 1609.344 m

Bug#1039948: git: Error from "git bisect whatever" says "usage: git bisect--helper --bisect-reset" .

[наб]

Package: git
Version: 1:2.39.2-1.1
Severity: normal

Dear Maintainer,


$ git bisect abort
error: unknown subcommand: `abort'
usage: git bisect--helper --bisect-reset []
   or: git bisect--helper --bisect-terms [--term-good | --term-old | --term-bad 
| --term-new]
   or: git bisect--helper --bisect-start [--term-{new,bad}= 
--term-{old,good}=] [--no-checkout] [--first-parent] [ [...]] 
[--] [...]
   or: git bisect--helper --bisect-next
   or: git bisect--helper --bisect-state (bad|new) []
   or: git bisect--helper --bisect-state (good|old) [...]
   or: git bisect--helper --bisect-replay 
   or: git bisect--helper --bisect-skip [(|)...]
   or: git bisect--helper --bisect-visualize
   or: git bisect--helper --bisect-run ...

$ git bisect stop
error: unknown subcommand: `stop'
usage: git bisect--helper --bisect-reset []
   or: git bisect--helper --bisect-terms [--term-good | --term-old | --term-bad 
| --term-new]
   or: git bisect--helper --bisect-start [--term-{new,bad}= 
--term-{old,good}=] [--no-checkout] [--first-parent] [ [...]] 
[--] [...]
   or: git bisect--helper --bisect-next
   or: git bisect--helper --bisect-state (bad|new) []
   or: git bisect--helper --bisect-state (good|old) [...]
   or: git bisect--helper --bisect-replay 
   or: git bisect--helper --bisect-skip [(|)...]
   or: git bisect--helper --bisect-visualize
   or: git bisect--helper --bisect-run ...

$ git bisect reset
Updating files: 100% (95564/95564), done.
Previous HEAD position was 39a8804455fb Linux 4.0
Switched to branch 'binux'


I want to say this wasn't like this, and it properly said
  usage: git bisect reset []

And if not then it still ought to do that.

Best,
наб

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages git depends on:
ii  git-man  1:2.39.2-1.1
ii  libc62.36-9
ii  libcurl3-gnutls  7.88.1-10
ii  liberror-perl0.17029-2
ii  libexpat12.5.0-1
ii  libpcre2-8-0 10.42-1
ii  perl 5.36.0-7
ii  zlib1g   1:1.2.13.dfsg-1

Versions of packages git recommends:
ii  ca-certificates  20230311
ii  less 590-2
ii  openssh-client [ssh-client]  1:9.2p1-2
ii  patch2.7.6-7

Versions of packages git suggests:
ii  gettext-base  0.21-12
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-email 
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information


signature.asc
Description: PGP signature

Bug#1039947: ITP: flooxs -- The Florida Object-Oriented Process/Device/Reliability/Superconductor Simulator (FLOOXS) is an open source TCAD tool

[Thomas Weingartner]

Package: wnpp
Severity: wishlist
Owner: Thomas Weingartner 
X-Debbugs-Cc: debian-de...@lists.debian.org, t.weingart...@ufl.edu

  Package name: flooxs
  Version : v2022
  Upstream Contact: Thomas Weingartner 
  URL : 
http://www.flooxs.ece.ufl.edu/index.php/Installation_from_Debian_package#Install_the_package
  License : Custom, license is included in package
  Programming Lang: Tcl/Tk, C/C++
  Description : The Florida Object-Oriented 
Process/Device/Reliability/Superconductor Simulator (FLOOXS) is an open source 
TCAD tool.

FLOOXS is a Technology Computer Aided Design (TCAD) tool used for semiconductor 
process modeling and semiconductor device modeling that will descretize and 
solve a set of partial and ordinary differential equations on a 1, 2 or 3D mesh 
using numerical methods such as the Finite Element Method (FEM) and the Finite 
Volume Method (FVM). FLOOXS is built in C++, and uses several well-known math 
packages such as BLAS, LAPACK, and SuiteSparse to handle the linear algebra. 
The user-interface is command-line tcl (tool control language), a scripting 
language, with additional FLOOXS-specific Alagator commands added in.

This package is one of a small number of tools that provide an open source TCAD 
platform.
This package is not a dependency for other packages and no other package
provides similar functionality to my knowledge. We are a small team of
developers, but maintaining this package should not be an issue since we
release infrequent updates and are not used as a dependency for any
other packages. Getting flooxs into the debian package system (and
ultimately ubuntu) will allow students ease of install for educational
purposes.

Bug#1039931: suricata: Outdated Homepage: filed

[Sascha Steinbiss]

tags 1039931 + fixed pending
thanks

Hi Adrian,

thanks for letting me know.

[...]

debian/control:Homepage: https://www.suricata-ids.org/

This location does no longer exist, the new location is
https://oisf.net/


Actually, that's the organization that runs the project -- Suricata's 
new homepage location is: https://suricata.io


I will update this field in Git and upload it with the next regular upload.

Cheers
Sascha


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

[Richard Lewis]

On Tue, 27 Jun 2023, 22:01 Andreas Beckmann,  wrote:

> Control: tag -1 patch
>
> On 27/06/2023 19.21, Richard Lewis wrote:
> > header.txt has not been modified since 2015.
>
> I've found three versions (with sightly different spelling):
> * lenny
> * squeeze, wheezy, jessie
> * stretch .. today
>
> > it is a simple yext file that is installed with debian/logcheck.install
> >
> > the only change is that it used to be installed into /usr/share but got
> > moved to /etc to be a conffile in 2021. This didnt trigger any piuparts
> > issues and there was no change to the contents of header.txt.
>
> It has been copied during initial install only and was never upgraded.


thank-you - i  believe understand this now

for reasons unknown, when debian introduced header.txt in 2014 it shipped
header.txt in /usr/share/logcheck and copied it to /etc/logcheck in
postinst on initial install. Only the file in /etc is ever used.

editorial changes were then made, but these only made it into the copy in
/usr/share and no steps were taken to update the file in /etc. So those
upgrading have been using the old version, while new installs got the new
version. This is probably against the spirit of policy but it doesnt look
like anyone noticed.

In bookworm logcheck puts header.txt file directly into /etc/logcheck like
any other conffile. because the content hasnt changed since stretch, this
didnt cause immediate issues.

But people who first installed at an old version will get a confusing
conffile prompt on upgrade to bookworm even though they had never edited
the file and had upgraded to every stable release..wow!

thank-you for this i have learned something

Luckily the header.txt is purely cosmetic - so there shouldnt be other bugs
from this!

>

Bug#1039946: openjdk-21 FTCBFS: missing Build-Depends: libffi-dev:native

[Helmut Grohne]

Source: openjdk-21
Version: 21~28ea-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

openjdk-21 fails to cross build from source, because the native build
pass misses libffi. I'm attaching a patch for your convenience.

Helmut
diff --minimal -Nru openjdk-21-21~28ea/debian/changelog 
openjdk-21-21~28ea/debian/changelog
--- openjdk-21-21~28ea/debian/changelog 2023-06-26 07:48:49.0 +0200
+++ openjdk-21-21~28ea/debian/changelog 2023-06-28 09:55:10.0 +0200
@@ -1,3 +1,10 @@
+openjdk-21 (21~28ea-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Add libffi-dev:native to B-D. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 28 Jun 2023 09:55:10 +0200
+
 openjdk-21 (21~28ea-1) unstable; urgency=medium
 
   * OpenJDK 21 snapshot, Build 28.
diff --minimal -Nru openjdk-21-21~28ea/debian/control 
openjdk-21-21~28ea/debian/control
--- openjdk-21-21~28ea/debian/control   2023-06-16 06:36:19.0 +0200
+++ openjdk-21-21~28ea/debian/control   2023-06-28 09:55:08.0 +0200
@@ -12,7 +12,7 @@
   g++-12 ,
   openjdk-20-jdk-headless:native | openjdk-21-jdk-headless:native,
   libxtst-dev, libxi-dev, libxt-dev, libxaw7-dev, libxrender-dev, 
libcups2-dev, libasound2-dev, liblcms2-dev, libfreetype6-dev (>= 2.2.1), 
libxinerama-dev, libkrb5-dev, xsltproc, libpcsclite-dev, libxrandr-dev, 
libelf-dev, libfontconfig1-dev, libgtk2.0-0 | libgtk-3-0, libharfbuzz-dev,
-  libffi-dev,
+  libffi-dev, libffi-dev:native,
   zlib1g-dev:native, zlib1g-dev, libattr1-dev, libpng-dev, libjpeg-dev, 
libgif-dev, 
   libnss3-dev (>= 2:3.17.1),
   openjdk-21-jdk-headless ,
diff --minimal -Nru openjdk-21-21~28ea/debian/rules 
openjdk-21-21~28ea/debian/rules
--- openjdk-21-21~28ea/debian/rules 2023-06-26 07:39:35.0 +0200
+++ openjdk-21-21~28ea/debian/rules 2023-06-28 09:54:58.0 +0200
@@ -676,10 +676,11 @@
 
 pkg_ffidev = libffi-dev
 
-bd_zero = \
-   $(pkg_ffidev) [$(foreach a,$(hotspot_archs),!$(a))],
-bd_zero = \
-   $(pkg_ffidev),
+ifneq (,$(filter $(distrel),precise))
+  bd_zero = $(pkg_ffidev), $(pkg_ffidev):native,
+else
+  bd_zero = $(pkg_ffidev),
+endif
 
 bd_ant = ant, ant-optional,
 

Bug#1039945: python-reportlab: binary-any FTBFS

[Adrian Bunk]

Source: python-reportlab
Version: 4.0.4-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=python-reportlab=4.0.4-2

...
 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --buildsystem=pybuild
dh: error: unable to load addon sphinxdoc: Can't locate 
Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl) at (eval 13) line 1.
BEGIN failed--compilation aborted at (eval 13) line 1.

make: *** [debian/rules:10: clean] Error 25

Bug#1039944: O: pulseeffects -- Audio effects for PulseAudio applications

[Boyuan Yang]

Package: wnpp
Control: affects -1 src:pulseeffects

Since pulseeffects upstream (now named easyeffects) no longer provide support
for pulseaudio [1], I am orphaning this package.

[1] https://github.com/wwmm/easyeffects/tree/pulseaudio-legacy

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: pulseeffects
Binary: gstreamer1.0-adapter-pulseeffects, gstreamer1.0-autogain-pulseeffects, 
gstreamer1.0-convolver-pulseeffects, gstreamer1.0-crystalizer-pulseeffects, 
pulseeffects
Version: 4.8.7-1
Maintainer: Debian Multimedia Maintainers 
Uploaders: Boyuan Yang ,
Build-Depends: appstream-util, debhelper-compat (= 13), desktop-file-utils, 
itstool, libboost-filesystem-dev (>= 1.72), libboost-system-dev (>= 1.72), 
libbs2b-dev, libebur128-
dev, libglibmm-2.4-dev, libgstreamer-plugins-bad1.0-dev, libgstreamer1.0-dev, 
libgtk-3-dev, libgtkmm-3.0-dev, liblilv-dev, libpango1.0-dev, libpulse-dev, 
librubberband-dev,
libsamplerate0-dev, libsndfile1-dev, libzita-convolver-dev, meson, pkg-config, 
scour
Architecture: any
Standards-Version: 4.6.1
Format: 3.0 (quilt)
Files:
 d565d7db3000745cf014fd002acb2444 2748 pulseeffects_4.8.7-1.dsc
 71114584150022d1190188e247574535 2028489 pulseeffects_4.8.7.orig.tar.gz
 7e8bbd945c604057512084ca5ae4a60e 3832 pulseeffects_4.8.7-1.debian.tar.xz
Vcs-Browser: https://salsa.debian.org/debian/pulseeffects
Vcs-Git: https://salsa.debian.org/debian/pulseeffects.git
Checksums-Sha256:
 f3e8b8773e6414c7d6c4735e4a489719e6944ef511fa465c820edac5e733a3e9 2748 
pulseeffects_4.8.7-1.dsc
 d841f27df87b99747349be6b8de62d131422369908fcb57a81f39590437a8099 2028489 
pulseeffects_4.8.7.orig.tar.gz
 f02c88aa93a1783893e27c4987d7fd8db656366278c16abd0050eb80996c 3832 
pulseeffects_4.8.7-1.debian.tar.xz
Homepage: https://github.com/wwmm/pulseeffects
Package-List: 
 gstreamer1.0-adapter-pulseeffects deb sound optional arch=any
 gstreamer1.0-autogain-pulseeffects deb sound optional arch=any
 gstreamer1.0-convolver-pulseeffects deb sound optional arch=any
 gstreamer1.0-crystalizer-pulseeffects deb sound optional arch=any
 pulseeffects deb sound optional arch=any
Directory: pool/main/p/pulseeffects
Priority: extra
Section: misc

Package: pulseeffects
Version: 4.8.7-1
Installed-Size: 5587
Maintainer: Debian Multimedia Maintainers 
Architecture: amd64
Depends: gir1.2-gst-plugins-bad-1.0, gstreamer1.0-adapter-pulseeffects, 
gstreamer1.0-plugins-bad, gstreamer1.0-plugins-good, gstreamer1.0-pulseaudio, 
pulseaudio, dconf-
gsettings-backend | gsettings-backend, libatkmm-1.6-1v5 (>= 2.28.2), 
libboost-filesystem1.74.0 (>= 1.74.0), libc6 (>= 2.29), libcairomm-1.0-1v5 (>= 
1.12.0), libgcc-s1 (>=
3.0), libglib2.0-0 (>= 2.39.4), libglibmm-2.4-1v5 (>= 2.66.4), 
libgstreamer-plugins-base1.0-0 (>= 1.0.0), libgstreamer1.0-0 (>= 1.0.0), 
libgtk-3-0 (>= 3.0.0), libgtkmm-3.0-1v5
(>= 3.24.6), libpangomm-1.4-1v5 (>= 2.46.2), libpulse0 (>= 0.99.1), 
libsigc++-2.0-0v5 (>= 2.8.0), libsndfile1 (>= 1.0.20), libstdc++6 (>= 11)
Recommends: calf-plugins, gstreamer1.0-autogain-pulseeffects, 
gstreamer1.0-convolver-pulseeffects, gstreamer1.0-crystalizer-pulseeffects, 
liblilv-0-0, lsp-plugins-lv2 (>=
1.1.24~) | lsp-plugins (>= 1.1.24~), rubberband-ladspa, zam-plugins
Description-en: Audio effects for PulseAudio applications
 PulseEffects is an advanced system-wide equalizer that works with
 PulseAudio. It can apply system-wide effects to all running application
 or selected apps.
 .
 PulseEffects also provides many pre-defined sound effects for PulseAudio
 input and output.
Description-md5: b8d7dfc9b25713d68c3180a148bb5e00
Homepage: https://github.com/wwmm/pulseeffects
Tag: uitoolkit::gtk
Section: sound
Priority: optional
Filename: pool/main/p/pulseeffects/pulseeffects_4.8.7-1_amd64.deb
Size: 905536
MD5sum: 668f08df3eca37b460ed3237ff5b4c48
SHA256: f42cdb64e4c6cf421d8c3bbc7e46fd5bb1f0ff28795ae3f7ce1eccb82d96c7ed


Thanks,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#1039938: librust-aes-dev: impossible to install

[Jeremy Bícha]

Control: tags -1 +pending

Yes, this was caused by a too-early package removal request. I believe
the usual tools don't handle virtual dependencies when checking
whether a package is safe for removal.

The new version of rust-aes no longer uses aes-soft and will be
uploaded to Unstable soon.

Thank you,
Jeremy Bícha

Bug#1039939: librust-wyz-dev: impossible to install

[Alexander Kjäll]

Hi

The missing dependency is in new:

https://ftp-master.debian.org/new/rust-typemap_0.3.3-1.html

Maybe it would save everyone some time if you checked that before
filing these kind of bugs?

best regards
Alexander Kjäll

Bug#1039720: Acknowledgement (gnome-online-accounts: google account stop working files and calendar. Not able to re create online account.)

[Sergio Zamora]

Hi,


looks like this update *WebKitGTK 2.38 -> 2.40*  left the account 
unusable and then made it impossible to configure it again.



Regards.


On 28-06-23 12:03, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 
1039720:https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039720.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   sazamor...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian GNOME Maintainers

If you wish to submit further information on this problem, please
send it to1039...@bugs.debian.org.

Please do not send mail toow...@bugs.debian.org  unless you wish
to report a problem with the Bug-tracking system.

Bug#1039939: librust-wyz-dev: impossible to install

[Jeremy Bícha]

Control: tags -1 pending

rust-typemap, the required dependency is awaiting review in the NEW queue.

https://ftp-master.debian.org/new/rust-typemap_0.3.3-1.html

By the way, have you seen this report? Hovering over the architecture
provides a guess as to what dependency is missing.

Thank you,
Jeremy Bícha

Bug#1039943: ITP: linescroll -- simple tool to watch logfile throughput

[ed neville]

Package: wnpp
Severity: wishlist
Owner: ed neville 
X-Debbugs-Cc: debian-de...@lists.debian.org, ed-deb...@s5h.net

* Package name: linescroll
  Version : 0.1.2
  Upstream Contact: Ed Neville 
* URL : https://www.usenix.org.uk/content/linescroll.html
* License : GPL
  Programming Lang: Rust
  Description : simple tool to watch logfile throughput

Monitor log files for activity and display results via graph or 
statistics.

Useful for live comparisson of server access. E.g. cached vs uncached 
web access. Results can easily be displayed in a format suitable for 
email reports.

In need of sponsorship.

Bug#1039942: RM: labgrid -- ROM; package incomplete; upstream wish; orphaned; low popcon

[Bastian Germann]

Package: ftp.debian.org
Control: affects -1 + src:labgrid
X-Debbugs-Cc: labg...@packages.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove labgrid. I have not fully packaged it and have orphaned it.
Upstream has asked to remove the package from Debian because they doubt it is a 
good fit for Debian without the tools
that I have left out. It also has a low popcon.

Bug#1038041: unixodbc 2.3.11-2+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1038041 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: unixodbc
Version: 2.3.11-2+deb12u1

Explanation: add Breaks+Replaces against odbcinst1debian1

Bug#1039521: Summarizing my proposed changes about the Java part of protobuf

[Pierre Gruet]

Hello again,

Le 29/06/2023 à 21:22, László Böszörményi (GCS) a écrit :

On Thu, Jun 29, 2023 at 9:15 PM Pierre Gruet  wrote:

Le 29/06/2023 à 18:41, László Böszörményi (GCS) a écrit :

Do you have your proposed package somewhere? I would also like to
check it with the updated protobuf package before uploading.

You can find it in the public repo
 https://salsa.debian.org/pgt/protobuf

  Your package = genomicsdb but I guess it's in the med-team repo [1].

Cheers,
Laszlo/GCS
[1] https://salsa.debian.org/med-team/genomicsdb


Sorry, obviously I misread your request. Yes this is genomicsdb, located 
at [1]. You may get it and build it against protobuf with the changes I 
proposed and it should be OK!


Best,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1039521: Summarizing my proposed changes about the Java part of protobuf

[GCS]

On Thu, Jun 29, 2023 at 9:15 PM Pierre Gruet  wrote:
> Le 29/06/2023 à 18:41, László Böszörményi (GCS) a écrit :
> > Do you have your proposed package somewhere? I would also like to
> > check it with the updated protobuf package before uploading.
> You can find it in the public repo
> https://salsa.debian.org/pgt/protobuf
 Your package = genomicsdb but I guess it's in the med-team repo [1].

Cheers,
Laszlo/GCS
[1] https://salsa.debian.org/med-team/genomicsdb

Bug#1039521: Summarizing my proposed changes about the Java part of protobuf

[Pierre Gruet]

Hi Laszlo,

Thanks for looking at my proposal, I am glad you consider it fit!

Le 29/06/2023 à 18:41, László Böszörményi (GCS) a écrit :

Hi Pierre,

On Wed, Jun 28, 2023 at 4:39 PM Pierre Gruet  wrote:

- removing j2objc from the pom.xml so that rdeps don't look for this
Debian-unpackaged artifact (touches d/p/no_j2objc.patch);

  Thanks for all of your work on this! I see you added this as a patch,
but not included in the series file. Meaning it will not be applied.
It's just an oversight I guess. Other than that it looks good.


Sorry, indeed I provided you with an excerpt of a source debdiff, which 
might not be the most suitable way to do it.



Do you have your proposed package somewhere? I would also like to
check it with the updated protobuf package before uploading.



You can find it in the public repo
https://salsa.debian.org/pgt/protobuf
I initiated it with version 3.21.12-3 that is currently packaged, and 
made commits for each change I listed in my previous email. Hopefully 
this is more handy!
Despite what is in d/changelog, I did not intend to NMU, it was only a 
changelog entry to get a consistent package in order to run my tests 
locally.



Thanks,
Laszlo/GCS


Please tell me if I may do something else for you here.

Best,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1034356: gnome-shell: Frozen UI and massive log flodding

[H.-Dirk Schmitt]

Am Donnerstag, dem 22.06.2023 um 18:13 +0100 schrieb Simon McVittie:
> Control: affects -1 gnome-shell-extension-vertical-overview
> 
> On Thu, 13 Apr 2023 at 15:27:33 +0200, H.-Dirk Schmitt wrote:
> > After migration to bookworm on 2 different machines the gnome-shell
> > was frozen in the last week.
> > Via SSH – or switching to the good old console – I was able to see
> > that journald was running with 100% cpu at that time.
> 
> I see from the log messages that you have a non-default theme and
> several
> Shell extensions enabled. Can this be reproduced without any
> extensions?

The machines with problems are administered remotely – so I can't
disable extensions et.al. 

But I found 2 valuable hints that the issue can be mitigated with an
upgrade of gjs to 1.76.1
- https://github.com/pop-os/pop/issues/2893
- https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1868

Currently a newer version is in 'experimental' . 
I tried a backport, but the tests are failing.

31/71 gjs:JS / Regress ERROR    0.50s  
killed by signal 6 SIGABRT
45/71 gjs:JS / Encoding    FAIL 0.35s  
54/55 subtests passed


May you please cherry pick the fix - or provide a suitable backport
package?

Best Regards,

H.-Dirk Schmitt

Bug#1039941: debhelper: intermittent dh_missing error

[Sven Joachim]

Package: debhelper
Version: 13.11.4
Severity: normal

In the Salsa CI for ncurses a rather strange failure happens in the
reprotest job[1]:

,
| dh_missing -i --fail-missing
| dh_missing: warning: usr/lib32/libncurses.so exists in debian/tmp but is not 
installed to anywhere (related file: 
"debian/tmp/usr/lib/x86_64-linux-gnu/libncurses.so")
| dh_missing: warning: usr/lib32/libncursesw.so exists in debian/tmp but is not 
installed to anywhere (related file: 
"debian/tmp/usr/lib/x86_64-linux-gnu/libncursesw.so")
| dh_missing: error: missing files, aborting
|
|   While detecting missing files, dh_missing noted some files with a 
similar name to those
|   that were missing.  This error /might/ be resolved by replacing 
references to the
|   missing files with the similarly named ones that dh_missing found - 
assuming the content
|   is identical.
|
|   As an example, you might want to replace:
|* debian/tmp/usr/lib/x86_64-linux-gnu/libncurses.so
|   with:
|* usr/lib32/libncurses.so
|   in a file in debian/ or as argument to one of the dh_* tools called 
from debian/rules.
|   (Note it is possible the paths are not used verbatim but instead 
directories
|   containing or globs matching them are used instead)
|
|   Alternatively, add the missing file to debian/not-installed if it 
cannot and should not
|   be used.
|
|   The following debhelper tools have reported what they installed (with 
files per package)
|* dh_install: lib32ncurses-dev (21), lib32ncurses6 (8), lib32ncursesw6 
(8), lib32tinfo6 (4), lib64ncurses-dev (1), lib64ncurses6 (0), lib64ncursesw6 
(0), lib64tinfo6 (0), libncurses-dev (29), libncurses6 (8), libncursesw6 (8), 
libncursesw6-udeb (2), libtinfo6 (4), libtinfo6-udeb (2), ncurses-base (46), 
ncurses-bin (4), ncurses-doc (1), ncurses-examples (1), ncurses-term (1)
|* dh_installdocs: lib32ncurses-dev (0), lib32ncurses6 (0), 
lib32ncursesw6 (0), lib32tinfo6 (0), lib64ncurses-dev (0), lib64ncurses6 (0), 
lib64ncursesw6 (0), lib64tinfo6 (0), libncurses-dev (0), libncurses6 (0), 
libncursesw6 (0), libtinfo6 (0), ncurses-base (1), ncurses-bin (0), ncurses-doc 
(3), ncurses-examples (0), ncurses-term (0)
|   If the missing files are installed by another tool, please file a bug 
against it.
|   When filing the report, if the tool is not part of debhelper itself, 
please reference the
|   "Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
| (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
|   Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
|   If the omission is intentional or no other helper can take care of this 
consider adding the
|   paths to debian/not-installed.
| make: *** [debian/rules:489: binary-indep] Error 25
| make: *** Waiting for unfinished jobs
`

The offending two files are created in the install-arch target in
debian/rules, installed in the first two lines of the
lib32ncurses-dev.install file, and since "make" even finished the
binary-arch target I could download the artifacts[2] and convince myself
that they landed in the lib32ncurses-dev package as intended.

I recall that I had seen this error occasionally in my local builds, but
was (and still am) not able to reproduce it :-(.  Maybe there is also an
error in the ncurses package that I do not see.  Any help is appreciated.


1. https://salsa.debian.org/debian/ncurses/-/jobs/4378348
2. https://salsa.debian.org/debian/ncurses/-/jobs/4378348/artifacts/download

Bug#1039876: ITP: golang-maunium-go-mautrix -- Matrix framework in golang

[Nilesh Patra]

On Thu, 29 Jun 2023 12:33:40 +0530 "Nilesh Patra"  wrote:
>   Version : 0.15.3-1

I have uploaded version 0.11.1-1 to new since that is the version
currently needed by gomuks.

Best,
Nilesh


signature.asc
Description: PGP signature

Bug#1039940: flatpak: Audio quality is diminished for flatpak apps

[machine]

Package: flatpak
Version: 1.14.4-1
Severity: important
X-Debbugs-Cc: makdamu...@rediff.com

Dear Maintainer,

* Music apps (amberol, lollypop, sayonara, etc) have diminished audio quality
on their flatpak versions. debs, appimages, official repos do not suffer from
this.

* Steps to reproduce:
1. Install (amberol, sayonara) as flatpak and deb (from apt or software
center).
2. Install EasyEffects from software center.
3. Play any audio and check output quality on Easyefects dashboard:
   An audio clip which is played at 44.1kHz and 2 channels on native app
will be played at 22kHz and 1 channel on flatpak counterparts.
   This quality degradation is easily identifiable through human ears,
earphones preferred, though speakers can do the job as easily.

* This issue is not reproducible on other distro (tried on Fedora 38).


-- Package-specific info:
Permissions of /usr/bin/bwrap:
-rwxr-xr-x 1 root root 72080 Feb 28 15:08 /usr/bin/bwrap
/etc/sysctl.d/*-bubblewrap.conf:
cat: '/etc/sysctl.d/*-bubblewrap.conf': No such file or directory
/usr/lib/sysctl.d/50-bubblewrap.conf:
# Enable unprivileged creation of new user namespaces in older Debian
# kernels.
#
# If this is not desired, copy this file to
# /etc/sysctl.d/50-bubblewrap.conf and change the value of this parameter
# to 0, then use dpkg-statoverride to make /usr/bin/bwrap setuid root.
#
# For more details see https://deb.li/bubblewrap or
# /usr/share/doc/bubblewrap/README.Debian
kernel.unprivileged_userns_clone=1
/proc/sys/kernel/unprivileged_userns_clone:
1
/proc/sys/user/max_cgroup_namespaces:
26696
/proc/sys/user/max_ipc_namespaces:
26696
/proc/sys/user/max_mnt_namespaces:
26696
/proc/sys/user/max_net_namespaces:
26696
/proc/sys/user/max_pid_namespaces:
26696
/proc/sys/user/max_time_namespaces:
26696
/proc/sys/user/max_user_namespaces:
26696
/proc/sys/user/max_uts_namespaces:
26696

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages flatpak depends on:
ii  adduser 3.134
ii  bubblewrap  0.8.0-2
ii  dbus [default-dbus-system-bus]  1.14.6-1
ii  fuse3   3.14.0-4
ii  libappstream4   0.16.1-2
ii  libarchive133.6.2-1
ii  libc6   2.36-9
ii  libcurl3-gnutls 7.88.1-10
ii  libdconf1   0.40.0-4
ii  libfuse3-3  3.14.0-4
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libglib2.0-02.74.6-2
ii  libgpgme11  1.18.0-3+b1
ii  libjson-glib-1.0-0  1.6.6-1
ii  libmalcontent-0-0   0.11.0-4
ii  libostree-1-1   2022.7-2
ii  libpolkit-agent-1-0 122-3
ii  libpolkit-gobject-1-0   122-3
ii  libseccomp2 2.5.4-1+b3
ii  libsystemd0 252.6-1
ii  libxau6 1:1.0.9-1
ii  libxml2 2.9.14+dfsg-1.2
ii  libzstd11.5.4+dfsg2-5
ii  xdg-dbus-proxy  0.1.4-3

Versions of packages flatpak recommends:
ii  ca-certificates20230311
ii  desktop-file-utils 0.26-1
ii  gtk-update-icon-cache  3.24.37-2
ii  hicolor-icon-theme 0.17-2
ii  libpam-systemd 252.6-1
ii  p11-kit0.24.1-2
ii  polkitd122-3
ii  shared-mime-info   2.2-1
ii  xdg-desktop-portal 1.16.0-2
ii  xdg-desktop-portal-gnome [xdg-desktop-portal-backend]  43.1-2
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]1.14.1-1
ii  xdg-user-dirs  0.18-1

Versions of packages flatpak suggests:
ii  avahi-daemon0.8-10
ii  malcontent-gui  0.11.0-4

Versions of packages bubblewrap depends on:
ii  libc62.36-9
ii  libcap2  1:2.66-4
ii  libselinux1  3.4-1+b6

Versions of packages bubblewrap recommends:
ii  procps  2:4.0.2-3

-- no debconf information

Bug#1039939: librust-wyz-dev: impossible to install

[Jonas Smedegaard]

Package: librust-wyz-dev
Version: 0.5.1-1+b1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install due to missing dependencies.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSdyl4ACgkQLHwxRsGg
ASFjrw/9FbzNM6Hw+bYWxv8tn1pJcySdZCNt5L/B9WQB1OnHDKd2xj2OKnIeSuHM
Ubg99PekvUzIVVQ1Ae0iRG/x553fCxp5FloPssJegS7+XBGbmSlVcCfaEbsEzTFq
U9DR3dNS46pbJR0ZBIbUjY9lI7E6AMDRRB+tx6eakHMoIZUIQD3JJ+GqGclzKK3l
sJ0MCRsI/twY6Ye7oCpEIolGAv5zHbI53BIeVf7Ke2YyXRYKc0VopjlYdp8bLTSi
Ju7RDrk9qH4RQmYYng9MGrUGDfPfJnZwCfMLIxWcE+/8iNYEzEKhXZfWDPYUzl0P
RkJA0m1H62+dWmiUh++scTmtZ9XZYHrhPpk7iYmn76X96Fn78MA6rdYbHlOWDoaT
Tym1MV0r5Cs/Fm2hkIUggTiGDW8Q+uJgy9HtjfBRT8EBf2rlywIyTarh6yPIZHo6
c2qqpOEN17/UjQ2AjBeq87t+TReh+amVhexUwlMIJVkzU0N08oZG2LkV6Xks5q+S
a929Oy1aBljX7Nqiqthkkaoic2f6G0iQK6nLigTSAFkXusQURzFYihorzD9XyMPc
RjwdGP1qy7iwVuBr8Sdf/zHKirngf4hfmiuHDG16aOmyUCUu+Pf6P1QadkWWPJvp
vSfroGuBOSUEWqXglEYyPZqYDi+RUZ1cbIIii4m3Q7GctM/GVJI=
=goP6
-END PGP SIGNATURE-

Bug#1039938: librust-aes-dev: impossible to install

[Jonas Smedegaard]

Package: librust-aes-dev
Version: 0.6.0-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package is impossible to install due to missing dependencies.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSdyg4ACgkQLHwxRsGg
ASGVAw/8CPJJ9/qVnPjc+/4jeZWAp696radIMoRpfbrzOImD9LH095qw9njA6SE6
Q1b0i8wDxv6hJQIbqpFGtEuayGdk9+du65u+BiDPvsY4ImvqHIOub1hFlBSNvl0O
IS9MRTawj3nG5e315n3WiwZSr+bEQs0WWJ8Kh/o8yyf3OIJ/guF0HuTcGNpadGg8
B8aWGnZ/iPcrUWN1UvdPnPvMk4AvimX993KPN6NcjE8KMb8xthGjv5RcZLezqQZT
D0BOvyHCtbV4XGy5c4o+IGed2hFRHeBrlVFMfENocizs7f3sJ2uKv0tF5il6d6yd
Juo4n8QUKZ5a9/3qkpOnJkh42eVzRA595mkoCEO4WE6YrXMMEyPbNk9XPZ1auviN
inyAExRJPX9H0r4L54X/9TWiww+ijbuwzVostD2ZJHTI0G+EuQBb+D5UJ7z6Ind3
QCJu1MwGiFMBsNVFfYyg9VIEKfaJB7C1MJLyLDxLHJUNMFJ/CMoI3r9v5VBPe+Q0
apFp3ZsYYrvEiTdREH+FMcsHpratF8bjz580mE/0ZCj6SOUwcS1JB6j1EzqgMSst
QGI/jY5JdmAv9QAcgGFa3SYy1mWIntW6huHLDNufA8MCNYC/UcT2JlgTnd4aupKW
fBCCuzF7NNW534DKvno/zMtwyyO/uLxqLLv+B0xRo9WjjWF+yhI=
=+IqD
-END PGP SIGNATURE-

Bug#1039325: pound: ships sysv-init script without systemd unit

[Luca Boccassi]

On Thu, 29 Jun 2023 at 19:08, Carsten Leonhardt  wrote:
>
> Hi Luca,
>
> bl...@debian.org writes:
>
> > Package: pound
> > Severity: important
> > User: bl...@debian.org
> > Usertags: missing-systemd-service
>
> > [...] by the time Trixie ships [...]
>
> pound is neither in unstable nor in bookworm. I don't see the sense in
> reporting bugs about future developments to a package that has been
> removed?

As mentioned in the bug this was driven by data on lintian.debian.org
which as it turns out it's basically broken and severely outdated,
although there are no indications anywhere that this is the case, so
closing is the right action.

Bug#1039617: liblopsub: reproducible-builds: timestamps in gzip headers for changelog and manpage

[Andre Noll]

On Thu, Jun 29, 08:27, Vagrant Cascadian wrote
> >> Given that this change was accepted in 2019, would you consider
> >> uploading a version with the fixes applied to Debian, either by making a
> >> new upstream version, or applying the patches to an older version?
> >
> > Will do. FWIW: There are also a few unrelated patches pending. My
> > plan is to merge these next weekend and then release v1.0.4.
> >
> > All I have to do to get the new version into Debian is to add a stanza
> > to debian/changelog, and tag the tip commit, correct?
> 
> Be sure to add Closes: #NNN for all the relevent bug numbers to
> debian/changelog.

Will add Closes: #1039617, #1039618

> It also needs someone to upload to Debian. Looks like Adam Borowski
>  has sponsored in the past, but if you need someone
> else to sponsor the upload, I could too.

Yes, Adam uploaded all previous versions so far. But of course it's
also fine if you sponsor the upload this time.

> Possibly also updating debian/copyright.

Will adjust the copyright year. Anything else you had in mind?

> Building the packages and running lintian might also have some suggestions to
> improve the package. The old package has a few issues (though most seem to be
> the gzip timestamp warnings):
> 
>   https://udd.debian.org/lintian/?packages=liblopsub

I might need some help to resolve these. The important one seems to
be shared-library-lacks-stack-section, as that's an error tag while
all other tags are only warnings. It seems to occur only on mips,
and according to lintian-explain-tags(1), "This problem can be fixed
with a rebuild". So how can one avoid this error at the source level?

Then there is hardening-no-relro, which is also ld-related and
which also occurs only on mips. On my x86 system, the RELRO section
is present:

$ readelf -a liblopsub.so.1.0.3 | grep -i relro
  GNU_RELRO  0xcd30 0xdd30 
0xdd30

Do you think it would help to add -z relro to the two recipes of the
Makefile which create the lopsubgen executable and the shared library?

Finally there is the no-debian-changes warning, which I don't
understand at all. How can there be "no changes to the upstream
sources in the Debian-related files"?

Thanks
Andre
-- 
Max Planck Institute for Biology
Tel: (+49) 7071 601 829
Max-Planck-Ring 5, 72076 Tübingen, Germany
http://people.tuebingen.mpg.de/maan/


signature.asc
Description: PGP signature

Bug#1039937: jst-config FTBFS on bytecode architectures

[Adrian Bunk]

Source: jst-config
Version: 0.16.0-1
Severity: important
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=jst-config=0.16.0-1

...
   dh_install -a
dh_install: warning: Cannot find (any matches for) 
"/usr/lib/ocaml/jst-config/*.a" (tried in ., debian/tmp)

dh_install: warning: libjst-config-ocaml-dev missing files: 
/usr/lib/ocaml/jst-config/*.a
dh_install: error: missing files, aborting
make: *** [debian/rules:6: binary-arch] Error 25

Bug#1038888: dpkg-buildpackage(1): mention all supported flags for DEB_BUILD_OPTIONS

[Sebastian Kayser]

Hi Guillem,

even though it's not 100% of what I expected this LGTM. What would you 
think about retaining the link to the Debian Policy?


Kind regards

Sebastian

Bug#1039936: equals rule processing broken

[Marc Haber]

Package: aide
Version: 0.18.3-1
Severity: important
Tags: patch confirmed
Forwarded: https://github.com/aide/aide/issues/154

In aide 0.18, equals rule handling is broken. AIDE totally ignores ny
directories lower than an equals rule directory. Prior to this you could
create secondary rules that allowed tracking of files below an equals
directory.

=/test/dir1 R
=/test/dir1/dir1a R
/test/dir2 R

Suppose I want to track dir1 and specific things under dir1 but not
everything. I create an =dir1 rule to just track the directory, then I
create a =dir1/dir1a to track a sub-directory.

This is upstream issue #154, https://github.com/aide/aide/issues/154,
and the fix is 
https://github.com/aide/aide/commit/cf5026bf0852d350030d6d1a7a0351573c9512e6

upstream plans to do a new upstream point release with the fix which
will go to unstable, and I will then backport the fix to 0.18.3 in
bookworm. bullseye is not affected.

Thankfully, Debian's default configuration does not use equals rules.

Greetings
Marc

Bug#1039935: ITP: python-rlpycairo -- plugin for the ReportLab PDF Toolkit

[Georges Khaznadar]

Package: wnpp
Severity: wishlist
Owner: Georges Khaznadar 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-rlpycairo
  Version : 0.3.0
  Upstream Contact: ReportLab Inc. 
* URL : https://pypi.org/project/rlPyCairo/
* License : BSD
  Programming Lang: Python3
  Description : plugin for the ReportLab PDF Toolkit

   This plugin is intended to replace most of the usage of the
   libart based C extension _renderPM which has been shown to
   have issues when rendering complex documents.

 - without this package, one cannot use package python-biopython
   together with python-reportlab version 4, since
   python-reportlab version 4 provides no longer
   the extension _renderPM cited above.
 - I shall keep maintaining it, shared with python-team/packages in
   https://salsa.debian.org/python-team/packages/python-pycairo

Bug#877512: slapd: enabled systemd integration (untested patch)

[Quanah Gibson-Mount]

--On Thursday, June 29, 2023 12:27 PM +0200 Andreas Henriksson 
 wrote:



Feel free to file a bug upstream if you think the current configure.ac
code needs adjustment.

[...]

It's my impression that configure.ac is missing a call to:

PKG_PROG_PKG_CONFIG(0.29)

Thus the PKG_CONFIG variable will be unset, and thus the PKG_CHECK_*
macros will just skip over and do nothing.


FWIW you do have this:
m4_ifndef([PKG_PREREQ],
[m4_fatal([must install pkg-config 0.29 or later before running
autoconf/autogen])])
... but that only seems to check that pkg.m4 is new enough, not that
the actual pkg-config binary/utility exists.

Adding `PKG_PROG_PKG_CONFIG(0.29)` directly after the m4_ifndef and
rebuilding gave me the expected systemdsystemunitdir=/lib/systemd/system
(as systemd.pc says on debian) rather than the hardcoded fallbacks.


Please file a bug at https://bugs.openldap.org :)

Regards,
Quanah

Bug#1039873: pam-auth-update --disable does not work

[Sam Hartman]

> "Marc" == Marc Dequènes (duck)  writes:

Marc> I don't recall if I tested the feature extensively but I
Marc> updated my Ansible rules and it is ineffective. After
Marc> switching a machine to bookworm I still get the module I want
Marc> disabled around (it is reenabled during upgrade) and that
Marc> breaks authentication.

Hmm.
I just tried:

* pam-auth-update --enable mkhomedir

* confirm pam_mkhomedir is in the config
p
* pam-auth-update --disable mkhomedir

* Confirm that it is not in the config.

--Sam

Bug#1037137: [Pkg-pascal-devel] Bug#1037137: add fp-units-*-win64_*.deb dependency packages required for Windows cross-compilation

[Abou Al Montacir]

On Thu, 2023-06-08 at 21:49 +0200, Abou Al Montacir wrote:
> This may be considered as a separate project that builds on top of FPC in
> order to avoid complicating more the build system of FPC which is already
> quite complex.
> 
I've created https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039930 to
provided required units.
-- 
Cheers,
Abou Al Montacir


signature.asc
Description: This is a digitally signed message part

Bug#1039934: gcc-12: __builtin_cpu_supports does not detect SSE2 on VIA CPU, patch available

[ValdikSS]

Package: gcc-12
Version: 12.2.0-14
Severity: normal
X-Debbugs-Cc: i...@valdikss.org.ru

Dear Maintainer,

GCC function __builtin_cpu_supports, which is used by Debian's isa-support
package to detect various CPU features, such as SSE2 support, in the current
GCC version fails to detect SSE2 support on VIA C7 CPUs, which prevent
installing software which require SSE2 support on such machines.

This has been fixed upstream with the patch to GCC 12:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100758#c25

Kindly asking to apply the patch and rebuild isa-support package.

Bugreport for sse2-support package:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029792

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 6.1.0-9-686-pae (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-12 depends on:
ii  binutils   2.40-2
ii  cpp-12 12.2.0-14
ii  gcc-12-base12.2.0-14
ii  libc6  2.36-9
ii  libcc1-0   12.2.0-14
ii  libgcc-12-dev  12.2.0-14
ii  libgcc-s1  12.2.0-14
ii  libgmp10   2:6.2.1+dfsg1-1.1
ii  libisl23   0.25-1
ii  libmpc31.3.1-1
ii  libmpfr6   4.2.0-1
ii  libstdc++6 12.2.0-14
ii  libzstd1   1.5.4+dfsg2-5
ii  zlib1g 1:1.2.13.dfsg-1

Versions of packages gcc-12 recommends:
ii  libc6-dev  2.36-9

Versions of packages gcc-12 suggests:
pn  gcc-12-doc   
pn  gcc-12-locales   
pn  gcc-12-multilib  

-- no debconf information


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1039933: bookworm-pu: package bepasty/1.0.0-1+deb12u1

[Elena Grandi]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: bepa...@packages.debian.org
Control: affects -1 + src:bepasty

[ Reason ]
The upload is necessary to fix bug #1038452 (
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038452 ) in bepasty,
a pastebin with support for multiple media types: because of an
incompatibility with Pygments-2.12.0 that I didn't spot during the
testing cycle (my fault) bepasty in bookworm is no longer able to
display the rendered version of text uploads.

[ Impact ]
If the update isn't approved the version of bepasty in Debian won't work
for one of the most common use cases (text uploads)

[ Tests ]
Automated tests of the package have been disabled because I wasn't able
to make them work in the package building infrastructure. I plan to work
on this during the trixie cycle.
I'm currently testing this manually by installing locally and trying to
use it.
The package I'm proposing for bookworm-updates has also been installed
on my main instance and being in use for a day (as I write this), and
giving it a bit of heavier than usual use.

[ Risks ]
I believe that the fix is a pretty small change in a part of code with
no special complexities.
However the alternative could be to remove bepasty from stable, and
users could install the updated version that I plan to maintain in
backports.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
The backported upstream patch changes the class CustomHtmlFormatter from
bepasty to work with the changed HtmlFormatter from pygments.
The only other packaging change is to add a versioned dependency to
python3-pygments (>= 2.12.0) (bookworm has 2.14.0+dfsg-1), as that's the
release that introduced the breaking change.

[ Other info ]
The issue is fixed in unstable by uploading the new upstream release
from which this patch comes from.

I will work to improve my testing to avoid something like this from
happening again, sorry.
diff -Nru bepasty-1.0.0/debian/changelog bepasty-1.0.0/debian/changelog
--- bepasty-1.0.0/debian/changelog  2021-12-17 09:35:28.0 +0100
+++ bepasty-1.0.0/debian/changelog  2023-06-28 13:57:40.0 +0200
@@ -1,3 +1,9 @@
+bepasty (1.0.0-1+deb12u1) bookworm; urgency=medium
+
+  * Backport upstream fix for Pygments-2.12.0. (Closes: #1038452)
+
+ -- Elena Grandi   Wed, 28 Jun 2023 13:57:40 +0200
+
 bepasty (1.0.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru bepasty-1.0.0/debian/control bepasty-1.0.0/debian/control
--- bepasty-1.0.0/debian/control2021-12-17 09:35:28.0 +0100
+++ bepasty-1.0.0/debian/control2023-06-28 13:57:40.0 +0200
@@ -9,7 +9,7 @@
  python3-setuptools,
  python3-setuptools-scm,
  python3-flask,
- python3-pygments,
+ python3-pygments (>= 2.12.0),
  python3-pytest,
  python3-selenium,
  python3-sphinx,
@@ -33,7 +33,7 @@
  libjs-jquery-ui,
  libjs-jquery-file-upload,
  python3-flask,
- python3-pygments,
+ python3-pygments (>= 2.12.0),
 Recommends: ${python3:Recommends}
 Suggests: ${python3:Suggests}
 Description: binary pastebin / file upload service
diff -Nru 
bepasty-1.0.0/debian/patches/0004-adapt-to-Pygments-2.12.0-and-also-require-it-fixes-2.patch
 
bepasty-1.0.0/debian/patches/0004-adapt-to-Pygments-2.12.0-and-also-require-it-fixes-2.patch
--- 
bepasty-1.0.0/debian/patches/0004-adapt-to-Pygments-2.12.0-and-also-require-it-fixes-2.patch
1970-01-01 01:00:00.0 +0100
+++ 
bepasty-1.0.0/debian/patches/0004-adapt-to-Pygments-2.12.0-and-also-require-it-fixes-2.patch
2023-06-28 13:57:40.0 +0200
@@ -0,0 +1,67 @@
+From: Thomas Waldmann 
+Date: Sat, 21 Jan 2023 18:48:50 +0100
+Bug: #1038452
+Subject: [PATCH] adapt to Pygments>=2.12.0 (and also require it), fixes #281
+Origin: backport, 
https://github.com/bepasty/bepasty-server/commit/6ab4201e28133476aeac9d80be2e703ca4a4b203
+
+pygments made some incompatible change in 2.12 and bepasty
+was affected by that because we subclassed pygment's
+HtmlFormatter.
+
+i updated our copy of format_unencoded from the HtmlFormatter
+base class and added our customization back to that (calling
+_wrap_lineparagraphs() when needed).
+---
+
+diff --git a/src/bepasty/utils/formatters.py b/src/bepasty/utils/formatters.py
+index d3a8931..6992336 100644
+--- a/src/bepasty/utils/formatters.py
 b/src/bepasty/utils/formatters.py
+@@ -23,26 +23,42 @@ class CustomHtmlFormatter(HtmlFormatter):
+ yield 0, line
+ 
+ def format_unencoded(self, tokensource, outfile):
+-"""Format by wrapping pieces of text according to the user's options
++"""
++The formatting process uses several nested generators; which of
++them are used is determined by the user's options.
++
++Each generator 

Bug#1039521: Summarizing my proposed changes about the Java part of protobuf

[GCS]

Hi Pierre,

On Wed, Jun 28, 2023 at 4:39 PM Pierre Gruet  wrote:
> - removing j2objc from the pom.xml so that rdeps don't look for this
> Debian-unpackaged artifact (touches d/p/no_j2objc.patch);
 Thanks for all of your work on this! I see you added this as a patch,
but not included in the series file. Meaning it will not be applied.
It's just an oversight I guess. Other than that it looks good.
Do you have your proposed package somewhere? I would also like to
check it with the updated protobuf package before uploading.

Thanks,
Laszlo/GCS

Bug#1039932: python-bitstring: please make the build reproducible

[Chris Lamb]

forwarded 1039932 https://github.com/scott-griffiths/bitstring/pull/269
thanks

I've forwarded this upstream here:

  https://github.com/scott-griffiths/bitstring/pull/269


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#1039932: python-bitstring: please make the build reproducible

[Chris Lamb]

Source: python-bitstring
Version: 4.0.2-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed that
python-bitstring could not be built reproducibly.

This was because the documentation used the build year in the
documentation:

│ │ │ ├── ./usr/share/doc/python-bitstring-doc/html/bitarray.html
│ │ │ │ @@ -973,11 +973,11 @@
│ │ │ │   >previous |
│ │ │ │  bitstring 
4.0 documentation 
│ │ │ │Reference 
│ │ │ │  BitArray 
Class 
│ │ │ │
│ │ │ │  
│ │ │ │  
│ │ │ │ - Copyright 2023 - 2023, Scott Griffiths.
│ │ │ │ + Copyright 2023 - 2024, Scott Griffiths.
│ │ │ │  
│ │ │ │
│ │ │ │  

Patch attached that bases this value on SOURCE_DATE_EPOCH if
available.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/0002-reproducible-build.patch  1970-01-01 
01:00:00.0 +0100
--- b/debian/patches/0002-reproducible-build.patch  2023-06-29 
17:25:47.227191969 +0100
@@ -0,0 +1,22 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2023-06-29
+
+--- python-bitstring-4.0.2.orig/doc/conf.py
 python-bitstring-4.0.2/doc/conf.py
+@@ -1,8 +1,14 @@
+ # Configuration file for the Sphinx documentation builder.
+ #
++import os
++import time
+ import datetime
+ 
+-year = datetime.datetime.now().year
++import datetime
++
++year = datetime.datetime.utcfromtimestamp(
++int(os.environ.get('SOURCE_DATE_EPOCH', time.time()))
++).year
+ 
+ project = 'bitstring'
+ copyright = f'2006 - {year}, Scott Griffiths'
--- a/debian/patches/series 2023-06-29 17:24:24.615705188 +0100
--- b/debian/patches/series 2023-06-29 17:25:46.187198262 +0100
@@ -1 +1,2 @@
 0001-delete-mybinder.org-remote-refs-privacy-breach-logo.patch
+0002-reproducible-build.patch

Bug#1029681: nvidia-legacy-340xx-driver: Qt5 apps fail to launch with a segfault

[jim_p]

Package: nvidia-legacy-340xx-driver
Version: 340.108-19
Followup-For: Bug #1029681
X-Debbugs-Cc: pitsior...@outlook.com

Kodi, with today's release of 20.2, fixed the gl library issue with this commit
here
https://github.com/xbmc/xbmc/pull/23226

In other news, a few days ago, qbittorrent became my first qt5 app to migrate
to qt6 and it just worked, without any workarounds or extra -gles packages.
So, can a patch like the one for kodi be applied to qt5? I am mentioning again
that arch does not have a seperate -gles package for qt5, so a single lib that
works everywhere should be possible.


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nvidia-legacy-340xx-driver depends on:
ii  nvidia-installer-cleanup 20220217+3
ii  nvidia-legacy-340xx-alternative  340.108-19
ii  nvidia-legacy-340xx-driver-bin   340.108-19
ii  nvidia-legacy-340xx-driver-libs  340.108-19
ii  nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340  340.108-19
.108]
ii  nvidia-legacy-340xx-vdpau-driver 340.108-19
ii  nvidia-support   20220217+3
ii  xserver-xorg-video-nvidia-legacy-340xx   340.108-19

Versions of packages nvidia-legacy-340xx-driver recommends:
pn  nvidia-persistenced   
ii  nvidia-settings-legacy-340xx  340.108-7

Versions of packages nvidia-legacy-340xx-driver suggests:
ii  nvidia-legacy-340xx-kernel-dkms  340.108-19

Versions of packages nvidia-legacy-340xx-driver-libs:amd64 depends on:
ii  libegl1-nvidia-legacy-340xx 340.108-19
ii  libgl1-nvidia-legacy-340xx-glx  340.108-19

Versions of packages nvidia-legacy-340xx-driver-libs:amd64 recommends:
ii  libgles1-nvidia-legacy-340xx  340.108-19
ii  libgles2-nvidia-legacy-340xx  340.108-19
pn  libnvidia-legacy-340xx-cfg1   
pn  libnvidia-legacy-340xx-encode1
pn  nvidia-legacy-340xx-driver-libs-i386  

Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 depends on:
ii  libc62.36-9
ii  libnvidia-legacy-340xx-glcore340.108-19
ii  libx11-6 2:1.8.6-1
ii  libxext6 2:1.3.4-1+b1
ii  nvidia-installer-cleanup 20220217+3
ii  nvidia-legacy-340xx-alternative  340.108-19
ii  nvidia-support   20220217+3

Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 recommends:
ii  nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340  340.108-19
.108]

Versions of packages libgl1-nvidia-legacy-340xx-glx:amd64 suggests:
ii  nvidia-legacy-340xx-kernel-dkms  340.108-19

Versions of packages xserver-xorg-video-nvidia-legacy-340xx depends on:
ii  libc6  2.36-9
ii  libnvidia-legacy-340xx-glcore  340.108-19
ii  nvidia-installer-cleanup   20220217+3
ii  nvidia-legacy-340xx-alternative340.108-19
ii  nvidia-support 20220217+3
ii  xserver-xorg-core [xorg-video-abi-25]  2:21.1.7-3

Versions of packages xserver-xorg-video-nvidia-legacy-340xx recommends:
ii  nvidia-legacy-340xx-kernel-dkms [nvidia-legacy-340xx-kernel-340  340.108-19
.108]
ii  nvidia-legacy-340xx-vdpau-driver 340.108-19
ii  nvidia-settings-legacy-340xx 340.108-7

Versions of packages xserver-xorg-video-nvidia-legacy-340xx suggests:
ii  nvidia-legacy-340xx-kernel-dkms  340.108-19

Versions of packages nvidia-legacy-340xx-alternative depends on:
ii  dpkg1.21.22
ii  glx-alternative-nvidia  1.2.2

Versions of packages nvidia-legacy-340xx-kernel-dkms depends on:
ii  dkms 3.0.11-3
ii  nvidia-installer-cleanup 20220217+3
ii  nvidia-legacy-340xx-kernel-support [nvidia-legacy-340xx-kernel-  340.108-19
support--v1]

nvidia-legacy-340xx-kernel-dkms recommends no packages.

Versions of packages glx-alternative-nvidia depends on:
ii  dpkg  1.21.22
ii  glx-alternative-mesa  1.2.2
ii  glx-diversions1.2.2
ii  update-glx1.2.2

Versions of packages glx-alternative-nvidia suggests:
ii  nvidia-legacy-340xx-driver [nvidia-driver-any]  340.108-19

Versions of packages nvidia-legacy-340xx-driver is related to:
pn  bumblebee   
pn  bumblebee-nvidia   

Bug#1039931: suricata: Outdated Homepage: filed

[Adrian Bunk]

Source: suricata
Version: 1:6.0.13-1
Severity: minor

debian/control:Homepage: https://www.suricata-ids.org/

This location does no longer exist, the new location is
https://oisf.net/

Bug#1039930: wnnp: ITP: fp-units-win -- FPC cross compilation files for Win32/Win64

[Abou Al Montacir]

Package: wnnp
Severity: wishlist
Owner: Abou Al Montacir 

* Package name: fp-units-win
  Version : 3.2.2
  Upstream Author : Abou Al Montacir 
* URL : https://salsa.debian.org/pascal-team/fp-units-win
* License : LGPL-2.1+ with staticLink exception
  Programming Lang: Pascal
  Description : FPC run time library compiled for Win32/Win64.
These units allow cross compilation of Windows executable programs on Debian
systems.
.
This can be useful for CI/CD tools that run in a Debian container and create
programs to be distributed for Windows users.


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#1039929: RFP: opustags -- Ogg Opus tags editor

[Maximilian Bos]

Package: wnpp
Severity: wishlist

* Package name: opustags
  Version : 1.9.0
  Upstream Contact: Frédéric Mangano 
* URL : https://github.com/fmang/opustags
* License : BSD-3-Clause
  Programming Lang: C++
  Description : Ogg Opus tags editor

View and edit Ogg Opus comments.

opustags supports the following features:
- interactive editing using your preferred text editor,
- batch editing with command-line flags,
- tags exporting and importing through text files.

Bug#803633: britney-tests-live-data/live-2012-05-09 fails randomly

[Paul Gevers]

Hi,

On 26-01-2023 17:45, Paul Gevers wrote:
On Sun, 01 Nov 2015 10:42:49 +0100 Emilio Pozuelo Monfort 
 wrote:

If run in a loop, live-2012-05-09 will eventually fail with:

AssertionError: NUNINST OUT OF SYNC


This issue was fixed in 2016 with this commit: 
https://salsa.debian.org/release-team/britney2/-/commit/2fd6c59460c0e78bb50a34938dbc05637abf27b2



Currently I'm seeing it also/instead being unreproducible.


This remains. I have now 10 different possible end states of britney. 
I'm trying to add sorted() to a bunch of for loops on sets. It seems I'm 
able to make it more deterministic, but I'm not there yet.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1039928: ifupdown2: set-fec encoding auto not supported

[Joe Botha]

Package: ifupdown2
Version: 3.0.0-1.1
Severity: normal
Tags: upstream

Dear Maintainer,

When using the latest ifupdown2 in Debian I get this error on an Nvidia SN2010 
switch:

ifreload -a
error: swp4: cmd '/sbin/ethtool --set-fec swp4 encoding auto' failed: returned 
83 (netlink error: Operation not supported)

It seems this attempts to set Forward Error Correction to Auto.

ifupdown2 version 3.0.0-1.1
ethtool version 6.1 

The Spectrum (mlxsw) driver does not support --set-fec encoding auto

I can make the error go away by commenting this line:

/usr/share/ifupdown2/addons/ethtool.py

if feccmd:
   try:
   feccmd = ('%s --set-fec %s %s' %
  (utils.ethtool_cmd, ifaceobj.name, feccmd))
   #utils.exec_command(feccmd)

I asked the mlxsw developers and they responded with:

"The problem needs to be solved in ifupdown2, which should not assume that 
every net device
implements these optional operations."

-- System Information:
Debian Release: 12.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_ZA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ifupdown2 depends on:
ii  iproute2  6.1.0-3
ii  python3   3.11.2-1+b1

ifupdown2 recommends no packages.

Versions of packages ifupdown2 suggests:
pn  bridge-utils 
ii  ethtool  1:6.1-1
ii  isc-dhcp-client  4.4.3-P1-2
pn  python3-gvgen
pn  python3-mako 

-- no debconf information

Bug#1039927: kazam: Add Japanese Translation

[Green]

Package: kazam
Version: 1.4.5-2.1
Severity: normal

Dear Maintainer,

The upstream of Kazam is no longer active at all. Thus, its translation support 
has been abandoned for a long time.
Evenso, Kazam has adopted into Debian 12 (bookworm) repository.

I am just finished Japanese translation. Please add Japanese support in the 
next update.

I uploaded .po and source file at the website below:

https://ja.osdn.net/projects/linux-desktop-japanese-edition/releases/78929

Best regards,
Green

-- System Information:
Debian Release: 10.13
  APT prefers oldoldstable-updates
  APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-24-amd64 (SMP w/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), 
LANGUAGE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kazam depends on:
ii  gir1.2-gst-plugins-base-1.0  1.14.4-2+deb10u1
ii  gir1.2-gstreamer-1.0 1.14.4-1
ii  gir1.2-keybinder-3.0 0.3.2-1
ii  gir1.2-wnck-3.0  3.30.0-2
ii  gnome-session-canberra   0.30-7
ii  gstreamer1.0-plugins-base1.14.4-2+deb10u1
ii  gstreamer1.0-plugins-good1.14.4-1+deb10u2
ii  gstreamer1.0-plugins-ugly1.14.4-1+deb10u1
ii  gstreamer1.0-pulseaudio  1.14.4-1+deb10u2
ii  python3  3.7.3-1
ii  python3-cairo1.16.2-1+b1
ii  python3-dbus 1.2.8-3
ii  python3-gi   3.30.4-1
ii  python3-gi-cairo 3.30.4-1
ii  python3-xdg  0.25-5

Versions of packages kazam recommends:
ii  gstreamer1.0-libav  1.15.0.1+git20180723+db823502-2+deb10u1

kazam suggests no packages.

-- no debconf information

Bug#1039906: libreoffice: FTBFS on riscv64: uitest throws "index out of range"

[Rene Engelhard]

Hi,

Am 29.06.23 um 17:29 schrieb Rene Engelhard:
Though that does not really matter, see [1]. We are supposed not to use 


Forgot to add that.

https://www.debian.org/doc/debian-policy/ch-source.html#embedded-code-copies

Regards,

Rene

Bug#1039906: libreoffice: FTBFS on riscv64: uitest throws "index out of range"

[Rene Engelhard]

tag 1039906 + moreinfo

found 1039906 4:7.5.4-1

forwarded 1039906 
https://bugs.documentfoundation.org/show_bug.cgi?id=155937


thanks



Almost all the uitest cases throws such exception:

My gut feeling points to python. I mean it's not really test specific 
but on "Almost all the uitest" (which all are python).

ERROR: testThemePage (themepage.Test.testThemePage)
--
Traceback (most recent call last):
  File "/<>/cui/qa/uitest/tabpages/themepage.py", line 
19, in testThemePage
    with self.ui_test.create_doc_in_start_center("impress") as 
component:

  File "/usr/lib/python3.11/contextlib.py", line 144, in __exit__
    next(self.gen)
  File "/<>/uitest/uitest/test.py", line 195, in 
create_doc_in_start_center

    self.close_doc()
  File "/<>/uitest/uitest/test.py", line 221, in close_doc
    frames[0].activate()
    ~~^^^
IndexError: index out of range


I know, that's why I wrote 
https://lists.debian.org/debian-riscv/2023/06/msg0.html in the first 
place
This exception is always throwed when closing the doc window. As I 
described in bugzilla[1], the bug should be located between c++ and 
python environment.

Which is the bridges. Or python itself. I think.


It seems that the exception only throws in current Debian package. If 
I build LibreOffice (both 7.6 and 7.5 version) with external tarballs 
(that means, I pass parameters to autogen.sh as less as possible), 
this bug disappears. Therefore maybe some system-internal component 
are not configured correctly.


For reference: Which exact options?

Though that does not really matter, see [1]. We are supposed not to use 
some  random copies of libraries. Here in this case they also just build 
it using non-default build systems, thus even skipping their testsuite. 
(Which I or Debian or the respective upstream then fixed up)



Anyway, even then it does not make sense at all to ship a obsolete 
(3.8!) python version since then anything using pyUNO then would need to 
build with that python, too. And there's stuff in Debian using pyUNO.




I am building a debug version of LibreOffice with sbuild to debug uitest.


Yes, please.


Or try with a newer python? Unfortunately LibreOffice is not yet ready 
for python 3.12...



Regards,


Rene

Bug#1039617: liblopsub: reproducible-builds: timestamps in gzip headers for changelog and manpage

[Vagrant Cascadian]

On 2023-06-28, Andre Noll wrote:
> On Tue, Jun 27, 14:55, Vagrant Cascadian wrote
>> > This issue was addressed already four years ago when Chris Lamb (CC)
>> > submitted an analogous patch, see below. His patch has been part of the
>> > master branch since then, although no new version has been released.
>> >
>> > I therefore assume that there is nothing to do for me in this
>> > regard. Please let me know if this is not the case.
>> 
>> Given that this change was accepted in 2019, would you consider
>> uploading a version with the fixes applied to Debian, either by making a
>> new upstream version, or applying the patches to an older version?
>
> Will do. FWIW: There are also a few unrelated patches pending. My
> plan is to merge these next weekend and then release v1.0.4.
>
> All I have to do to get the new version into Debian is to add a stanza
> to debian/changelog, and tag the tip commit, correct?

Be sure to add Closes: #NNN for all the relevent bug numbers to
debian/changelog.

It also needs someone to upload to Debian. Looks like Adam Borowski
 has sponsored in the past, but if you need someone
else to sponsor the upload, I could too.

Possibly also updating debian/copyright. Building the packages and
running lintian might also have some suggestions to improve the
package. The old package has a few issues (though most seem to be the
gzip timestamp warnings):

  https://udd.debian.org/lintian/?packages=liblopsub


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1039721: r-base: 4.3 causes many autopkgtests to fail

[Dirk Eddelbuettel]

On 28 June 2023 at 17:39, Jeremy Bícha wrote:
| Control: severity -1 serious
| 
| On Wed, Jun 28, 2023 at 5:29 PM Dirk Eddelbuettel  wrote:
| > Feel free to change the severity back if you truly think it is that serious.
| 
| Done.
| 
| Feel free to close the bug once r-base is ready to migrate to Testing.
| This is mostly just a tracking bug that people may find easier than
| browsing the mailing list.
| 
| > I maintain that r-base is fine.  I have no control over how other people use
| > my package, and if all other maintainers put breaking autopkgtests in well
| > yes then they do hold r-base hostage and it will take "forever" to migrate 
to
| > testing.  We have been there before.
| 
| Some just set this field in debian/control:
| Testsuite: autopkgtest-pkg-r

Of course. That is just the mechanical 'how does one'.

The actual problem is combining this with letting the packages get out of
sync, or in the case of the API change, not yet having rebuilt.

I just filed bug reports against (somewhat popular) packages r-cran-ragg (a
graphics device) and r-cran-svglite (ditto).  Once those are remade this
self-inflicted autopkgtest "issue" will improve.

Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1039925: ragg requires rebuild under R 4.3.*

[Dirk Eddelbuettel]

Package: r-cran-ragg
Version: 1.2.5-1
Severity: normal

R 4.3.0 brought (once again) a new graphics API which requires a rebuild for
functionality that involves creating graphics device.  Once rebuilt the
following will again work:

> getRversion()
[1] ‘4.3.1’
> packageVersion("ragg")
[1] ‘1.2.5’
> library(ragg)
> agg_png(tempfile())
Error in agg_png(tempfile()) : Graphics API version mismatch
> 

R Core decided again not to call this a breaking change, and I concur. We may
want to look into a graphics api tag for the next release. For now, a simple
rebuild should do.

Thanks, Dirk

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1039926: svglite requires rebuild under R 4.3.*

[Dirk Eddelbuettel]

Package: r-cran-svglite
Version: 2.1.1-1
Severity: normal

R 4.3.0 brought (once again) a new graphics API which requires a rebuild for
functionality that involves creating graphics device.  Once rebuilt the
following will again work:

> getRversion()
[1] ‘4.3.1’
> packageVersion("svglite")
[1] ‘2.1.1’
> svglite(tempfile())
Error in svglite_(filename, bg, width, height, pointsize, standalone,  : 
  Graphics API version mismatch
> 

R Core decided again not to call this a breaking change, and I concur. We may
want to look into a graphics api tag for the next release. For now, a simple
rebuild should do.

Thanks, Dirk

--
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#1029792: sse2-support: SSE2 support not detected on VIA Eden Eshter

[ValdikSS]

Still the issue as of Debian 12.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1039710: busybox-udeb: /var/log/syslog is empty

[Roland Clobus]

Control: retitle -1 busybox-udeb: /var/log/syslog is empty

On 28/06/2023 22:54, Cyril Brulebois wrote:

With a local build, confirmed -3 is buggy, and that reverting only
busybox-udeb to -1 is sufficient to restore syslog support in the
installer.


Confirmed and details to reproduce:

* Download the busybox binary file from [1] and extract the file `busybox`
* Run the latest netinst image in Qemu/KVM (sid)
* Select the installer
* Answer all the questions and let it run until an error (to make sure 
that the network is properly configured)

* Select a shell in the installer
* Download the older busybox binary file (you can use my server)
  `cd /`
  `wget http://pioneers.game-host.org/busybox`
  `chmod a+x busybox`
* Kill the running syslogd
  `ps | grep syslogd`
  `kill `
* Restart syslogd from the older busybox
  `/busybox syslogd -m 0 -O /var/log/syslog -S`
* Log something
  `logger -t Test It works now`
* Send Ctrl-Alt-F4, to see the output in the log

With kind regards,
Roland Clobus

[1] 
https://snapshot.debian.org/archive/debian/20230608T144245Z/pool/main/b/busybox/busybox-udeb_1.36.1-1_amd64.udeb


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1029456: RFP: veracrypt -- Cross-platform on-the-fly encryption.

[Blair Noctis]

Control: noowner -1
Control: retitle -1 RFP: veracrypt -- Cross-platform on-the-fly encryption

As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814352, it has
a shady licensing model making it DFSG incompatible. IDK why wnpp-check wouldn't
show that one, so I'll leave this message here.

-- 
Sdrager,
Blair Noctis


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1012232: freespace2: FTBFS with libsdl1.2-compat-dev: 'malloc_usable_size' was not declared in this scope

[Simon McVittie]

Control: severity -1 normal

On Thu, 29 Jun 2023 at 15:47:27 +0100, Simon McVittie wrote:
> sdl12-compat_1.2.64-4 includes workarounds for all these build issues,
> hopefully making this bug non-RC (I'll lower the severity if a test-build
> is successful)

A test-build against 1.2.64-4 was successful. Please use an older version
(the one in bookworm is probably most convenient) to reproduce the build
failure if you want to verify the patches.

smcv

Bug#1039703: With dhcpcd version 9.4.1 interfaces cannot be brought down and up again, please ship at least 9.5.0

[Alain Knaff]

Hi,

On 28/06/2023 14:01, Alain Knaff wrote:
> Package: dhcpcd
> Version: 9.4.1-22
> 
> Hi,
> 
> With the dhcpcd shipped with Debian 12, it is no longer possible to 
> bring an interface down and up again:
> 
> ifdown eth0 ; sleep 1 ; ifup eth0
> 
[...]
> According to https://github.com/NetworkConfiguration/dhcpcd/issues/159, 
> a bug with a similar error message is fixed in dhcpcd-9.5.0
> 

Actually, further test show that dhcpcd-9.5.1, nor dhcpcd-10.0.1 don't 
fix this issue.

What fixes it, is disabling the dhcpcd service in systemd. This works 
even with 9.4.1: interfaces are brought up all right after boot even 
without this service, and can be brought down and up again later!

Regards,

-- 
Alain Knaff
Ingénieur Informaticien

LE GOUVERNEMENT DU GRAND-DUCHÉ DE LUXEMBOURG
Ministère de l'Environnement, du Climat et du Développement durable
Administration de l'environnement

1, avenue du Rock'n'Roll . L-4361 Esch-sur-Alzette
Tél. (+352) 40 56 56-309
E-Mail: alain.kn...@aev.etat.lu
www.emwelt.lu . www.environnement.public.lu . www.luxembourg.lu

Bug#1039924: ITP: baler -- Baler - a machine learning based data compression tool

[Mattias Ellert]

Package: wnpp
Severity: wishlist
Owner: Mattias Ellert 

* Package name: baler
  Version : 1.2.0
* URL : https://github.com/baler-collaboration/baler/
* License : Apache-2.0
  Description : Baler - a machine learning based data compression tool

 Baler is a tool used to test the feasibility of compressing different
 types of scientific data using machine learning-based autoencoders.
 Baler provides you with an easy way to:
 1. Train a machine learning model on your data
 2. Compress your data with that model. This will also save the
compressed file and model
 3. Decompress the file using the model at a later time
 4. Plot the performance of the compression/decompression



signature.asc
Description: This is a digitally signed message part

Bug#1039903: libinsighttoolkit5-dev: Forcing C++14 makes plastimatch FTBFS

[Steven Robbins]

On Thu, 29 Jun 2023 13:40:42 +0300 Adrian Bunk  wrote:

>  1153 | #error\
>   |  ^~
>  1154 | DCMTK was configured to use C++17 features, but your compiler does 
not or was not configured to provide them.
>   | ~
> ...
> 
> 
> 
> This is due to:
> /usr/lib/x86_64-linux-gnu/cmake/ITK-5.3/ITKInitializeCXXStandard.cmake:  
set(CMAKE_CXX_STANDARD 14) # Supported values are 14, 17, 20, and 23.

That is just the default.  Override it for the plastimatch build by adding

set(CMAKE_CXX_STANDARD 17) 

to the plastimatch CMakeLists.txt file.

-Steve


signature.asc
Description: This is a digitally signed message part.