Bug#1040158: texlive-latex-extra: tex4ebook with mathml prints \lim, limsup etc. in italics

[Preuße]

On 02.07.2023 17:53, Karl Grill wrote:

Hi Karl,


*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
  Trying to convert Latex source to Epub 3 with MathML
* What exactly did you do (or not do) that was effective (or
  ineffective)?
  Run "tex4ebook -f epub3 test.tex mathml"
   
I've tested with the upcoming TL 2023 and can confirm that the issue is 
still present. The pdf and the dvi file however still look OK.


H.
--
sigfault



OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037258: curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance

[Bagas Sanjaya]

On Sun, Jun 11, 2023 at 01:56:21AM -0400, Sergio Durigan Junior wrote:
> On Saturday, June 10 2023, Samuel Henrique wrote:
> 
> > Hello,
> >
> > I'm not able to reproduce the issue on Bookworm with a HTTP2 localhost
> > apache server.
> [...]
> 
> Hey,
> 
> I was able to find another URL that triggers the same issue.  This one:
> 
>   
> https://chinarising.puntopress.com/wp-content/uploads/2023/04/Press-TV-KSA-Iran.mp3

OK so I tried reproducing it by installing WP on localhost (actually
behind LXD container). The container is Debian bookworm (with
deb.sury.org repo added).

apache2 site configuration (`/etc/apache2/sites-enabled/test.conf`) is:

```

ServerName  test.test
ServerAdmin webmas...@test.test
DocumentRoot/srv/www/test.test

Redirect301 /   https://wp.bagas.me




ServerName  test.test
ServerAdmin webmas...@test.test
DocumentRoot/srv/www/test.test
DirectoryIndex  index.php index.html

Protocols   h2 http/1.1

...

...


AllowOverride   all
Require all granted

SetHandler 
"proxy:unix:/run/php/php8.2-fpm.sock|fcgi://localhost"




```

(requires mod_proxy and mod_proxy_fcgi for apache2 and php8.2-fpm package).

WP configuration is pretty standard and it's rather fresh install
(see the web for WP installation procedures).

Log in to WP dashboard and upload random .mp3 files. Once uploaded, click
`Copy URL to clipboard` besides the uploaded file and feed it to curl.

In summary, I can't reproduce this bug either with above setup.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara


signature.asc
Description: PGP signature

Bug#1040178: Kernel modules will not build, missing asm/orc_header.h

[Richard A Burton]

Fully updated sid, on amd64.

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
+++----===
ii  linux-kbuild-6.3 6.3.11-1 amd64Kbuild infrastructure for
Linux 6.3

Bug#1040191: libnest2d-dev: Binary-all package that is now bitsize-specific

[Adrian Bunk]

Package: libnest2d-dev
Version: 5.0.0-1
Severity: serious
Tags: ftbfs
Control: affects -1 src:pynest2d

https://buildd.debian.org/status/fetch.php?pkg=pynest2d&arch=i386&ver=5.0.0-2&stamp=1688331535&raw=0

...
CMake Error at CMakeLists.txt:33 (find_package):
  Could not find a configuration file for package "Libnest2D" that is
  compatible with requested version "".

  The following configuration files were considered but not accepted:

/usr/lib/cmake/Libnest2D/Libnest2DConfig.cmake, version: 1.0 (64bit)



-- Configuring incomplete, errors occurred!

Bug#1040190: git: Please package new version 2.41.0

[Bagas Sanjaya]

Package: git
Version: 1:2.40.1-1
Severity: normal
Tags: sid trixie

Dear Jonathan,

There is a latest Git release (v2.41.0), which is available at [1]. The
release was already a month ago, and AFAIK the upstream is about to release
new point release soon (which will be v2.41.1). Please consider packaging it,
thanks!

[1] https://mirrors.edge.kernel.org/pub/software/scm/git/git-2.41.0.tar.gz

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

Kernel: Linux 6.4.0-local (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

Versions of packages git depends on:
ii  git-man  1:2.40.1-1
ii  libc62.36-9
ii  libcurl3-gnutls  7.88.1-10
ii  liberror-perl0.17029-2
ii  libexpat12.5.0-2
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.3p1-1
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   
ii  git-email 1:2.40.1-1
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information

Bug#1039742: [DAViCal-devel] Bug#1039742: Add support for phpunit 10

[Andrew Ruthven]

Hi Athos,

Thank you! As upstream, I've merged the MR

-- 
Andrew Ruthven, Wellington, New Zealand
and...@etc.gen.nz |
Catalyst Cloud:   | This space intentionally left blank
 https://catalystcloud.nz |

Bug#973471: [PATCH] The obvious patch fixes the problem -- but subject to locale

[Peter Moulder]

I'm just writing to confirm that after applying the attached patch (adding -f
to the sole occurrence of `sort' in debian/rules) to scowl-2020.12.07-2, the
test I gave before:

  while read -r i; do
look "$i" | fgrep -q -w "$i" || echo " $i";
  done < /usr/share/dict/words

no longer identifies any words that look doesn't find (when 
/usr/share/dict/words
points via /etc/dictionaries-common/words to /usr/share/dict/american-english,
and look is provided by bsdextrautils 2.36.1-8+deb11u1, whose source package is
util-linux).

I do wonder whether there are any locales with interesting LC_COLLATE (or
LC_CTYPE) behaviour that could cause the above test to fail for some word
lists; though I'd think that that would be a bug to be fixed in util-linux, not
in scowl.  scowl's sort command in question already explicitly sets LC_ALL to C,
which seems like the right behaviour for scowl to me: I don't think one could
really do better even if the sort were delayed until installation time.

util-linux misc-utils/look.c calls setlocale(LC_ALL, "") at startup (i.e.
setting all locale categories from the environment), with no other occurrence
of setlocale in the source file; and its compare() function uses isalnum and
isblank (which are documented to use current locale), and strncasecmp (whose
behaviour is explicitly unspecified in its documentation, outside of POSIX
locale).  So it does seem like one could at least construct locales for which
this implementation of look would fail.  However, I have not tested this
conclusion (which is formed from a cursory look at the source by someone not
an expert in locales).

pjrm.
diff -dur scowl-2020.12.07/debian/rules scowl-2020.12.07-f/debian/rules
--- scowl-2020.12.07/debian/rules	2022-01-20 16:14:35.0 +1100
+++ scowl-2020.12.07-f/debian/rules	2023-07-03 11:14:50.909568820 +1000
@@ -55,7 +55,7 @@
 echo "  $${word_list}" >> w$$SPELLING$$SIZE.scowl-word-lists-used;\
 			fi;\
 		done; \
-	  cat $$SPELLING-english$$SIZE.unsorted | LC_ALL=C sort -d | uniq | iconv -f 'iso8859-1' -t 'utf-8' > $$SPELLING-english$$SIZE; rm $$SPELLING-english$$SIZE.unsorted;\
+	  cat $$SPELLING-english$$SIZE.unsorted | LC_ALL=C sort -d -f | uniq | iconv -f 'iso8859-1' -t 'utf-8' > $$SPELLING-english$$SIZE; rm $$SPELLING-english$$SIZE.unsorted;\
 	  done;\
 	done
 	cd speller && $(MAKE) hunspell

Bug#1040189: miscomputes SHA1 sums on IMX53 (armhf)

[Dmitry Baryshkov]

Package: game-data-packager
Version: 73
Severity: normal

I tried building the quake shareware packages on my fresh iMX53 install
(Debian bookworm, armhf port). However I faced an issue with
game-data-packager being unable to identify any source file, because it
miscomputes sha1 sums. As you can see in the following fragment, md5 and
sha256 sums match, but sha1 doesn't:

$ game-data-packager quake
INFO:game_data_packager.download:downloading 
ftp://ftp.fu-berlin.de/pc/msdos/games/idgames/idstuff/quake/quake106.zip
WARNING:game_data_packager.build:found quake106.zip but it is not one of the 
expected versions:
file:   /tmp/gdptmp.0aow0955/quake106.zip
size:   9094045 bytes
md5:8cee4d03ee092909fdb6a4f84f0c1357
sha1:   e24e7b1c5030bf38d6caaa71dcd54469087aef0f
sha256: ec6c9d34b1ae0252ac0066045b6611a7919c2a0d78a3a66d9387a8f597553239
expected:
  quake106.zip:
size:   9094045 bytes
md5:8cee4d03ee092909fdb6a4f84f0c1357
sha1:   f8a1a509b094ccdbed3c54b96f7d9b351c0898f5
sha256: ec6c9d34b1ae0252ac0066045b6611a7919c2a0d78a3a66d9387a8f597553239


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

Kernel: Linux 6.4.0-next-20230630-12836-gb4a056856b00-dirty (UP)
Kernel taint flags: TAINT_WARN
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)

Versions of packages game-data-packager depends on:
ii  python3 3.11.2-1+b1
ii  python3-debian  0.1.49
ii  python3-yaml6.0-3+b2

Versions of packages game-data-packager recommends:
ii  game-data-packager-runtime  73

Versions of packages game-data-packager suggests:
pn  arj   
ii  binutils  2.40-2
pn  cabextract
pn  cdparanoia
pn  dynamite  
ii  gcc   4:12.2.0-3
pn  gdebi | gdebi-kde 
ii  gir1.2-gdkpixbuf-2.0  2.42.10+dfsg-1+b1
ii  innoextract   1.9-0.1
pn  lgc-pg
pn  lgogdownloader
ii  lhasa [lzh-archiver]  0.3.1-4+b1
ii  make  4.3-4.1
pn  p7zip-full
pn  pkexec
ii  python3-gi3.42.2-3+b1
pn  python3-omg   
pn  python3-pil   
pn  steam 
pn  steamcmd  
pn  unace-nonfree 
pn  unar  
pn  unrar 
pn  unshield  
ii  unzip 6.0-28
pn  vorbis-tools  
pn  xdelta
pn  xdelta3   
pn  xorriso   

-- no debconf information

Bug#1040036: yajl: CVE-2017-16516 CVE-2022-24795

[John Stamp]

On 07/01/23 04:03 AM, Tobias Frost wrote:
> Source: yajl
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: Debian Security Team 
> 
> After preparing the LTS upload of yajl I've seen the following issues in
> the upstream github issue tracker:
> 
> CVE-2017-16516 [1] portential buffer overread: A JSON file can cause denial of
>  service.
> 
> CVE-2022-24795 [2] potential integer overflow which can lead to subsequent 
> heap
>   memory corruption when dealing with large (~2GB) input
> 
> The upstream issue tracker also indicates that there might be other 
> vulnerabilies
> (without CVEs or unknown CVEs), but I did not investiage further:
> https://github.com/lloyd/yajl/issues/206 (double free)
> https://github.com/lloyd/yajl/issues/204 (Uninitialized memory reads and 
> out-of-bound)
> 
> It seems that the code is unmaintained upstream. It might be a good idea to 
> evaluate
> if any of the forks are more active and whether Debian should move there.
> 
> Cheers,
> -- 
> tobi
> 
> [1] https://github.com/lloyd/yajl/issues/248
> Potential fix: 
> https://github.com/brianmario/yajl-ruby/commit/a8ca8f476655adaa187eedc60bdc770fff3c51ce
> 
> [2] https://github.com/lloyd/yajl/issues/239
> Potential fix (howver the use of abort() can cause issues.)
> https://github.com/lloyd/yajl/pull/240


Hello,

I've something nearly ready for upload, but it would be good to get a
second pair of eyes on it:

  https://github.com/jstamp/yajl/commits/master


CVE-2017-16516 looks fixed with the patch that you linked to.


CVE-2022-24795 looks fixed with https://github.com/lloyd/yajl/pull/240

As you said, pull 240's use of abort() can cause problems of its own, but
if I understand the discussion right, there aren't other options without
a significant rewrite to yajl.  The other two potential fixes also use
abort() or assert():

  
https://github.com/robohack/yajl/commit/7d8adb408842a2d19e6a48fccf2725feb333937a
  
https://github.com/robohack/yajl/commit/166b384aec1cf304859d69f03e42c3ab85c34858

  
https://github.com/lloyd/yajl/pull/242/commits/d3a528c788ba9e531fab91db41d3a833c54da325



You also mentioned the following issues:

  https://github.com/lloyd/yajl/issues/204
  https://github.com/lloyd/yajl/issues/206

I can reproduce the reporter's errors in valgrind using yajl's
json_reformat in version 1.0.12, but all appeared well when I tested with
version 2.1.0.  Those issues only seem to affect 1.x  The same applied
to issue 205:

  https://github.com/lloyd/yajl/issues/205


If all this looks sensible to you, I'll head over to mentors for a sponsor.

John

Bug#1038684: firmware-ath9k-htc: TP-Link TL-WN722N is not reported by "iw dev".

[Oleksij Rempel]

Am 03.07.23 um 02:21 schrieb pe...@easthope.ca:

[43926.807143] usb 1-2: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw 
requested


This is the firmware name provided by firmware-ath9k-htc package.


[43927.619075] ath9k_htc 1-2:1.0 wlxe894f6248352: renamed from wlan0


This line shows that devices was successfully registered and renamed to 
wlxe894f6248352 by udev.

Is it the kernel log of good/working case?
--
Regards,
Oleksij

Bug#1039742: Add support for phpunit 10

[Athos Ribeiro]

Since this package is maintained in the upstream package, I filed
https://gitlab.com/davical-project/awl/-/merge_requests/31 to address
this one.


--
Athos Ribeiro

Bug#1040188: gnome-shell: bluetooth's menu search arrow not displayed when activated

[zezamoral]

Package: gnome-shell
Version: 43.4-1
Severity: normal
X-Debbugs-Cc: sazamor...@gmail.com

Dear Maintainer,


   * What led up to the situation?

Activating the gnome-shell bluetooth buton.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Arrow that showed available devices not displayed. Going to the gnome
control center was the only way to display and connect to device.

   * What was the outcome of this action?

Only activating bluetooth adapter works. Before I was able to go from
the same button to the available devices list.

   * What outcome did you expect instead?

Previous behaviour: Activating bluetooth and get arrow to see available
devices.


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

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

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-accountsservice-1.0   22.08.8-6
ii  gir1.2-adw-1 1.2.2-1
ii  gir1.2-atk-1.0   2.46.0-5
ii  gir1.2-atspi-2.0 2.46.0-5
ii  gir1.2-freedesktop   1.74.0-3
ii  gir1.2-gcr-3 3.41.1-1+b1
ii  gir1.2-gdesktopenums-3.0 43.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii  gir1.2-gdm-1.0   43.0-3
ii  gir1.2-geoclue-2.0   2.6.0-2
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gnomebluetooth-3.042.5-3
ii  gir1.2-gnomedesktop-3.0  43.2-2
ii  gir1.2-graphene-1.0  1.10.8-1
ii  gir1.2-gstreamer-1.0 1.22.0-2
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-gtk-4.0   4.8.3+ds-2
ii  gir1.2-gweather-4.0  4.2.0-2
ii  gir1.2-ibus-1.0  1.5.27-5
ii  gir1.2-mutter-11 43.4-2
ii  gir1.2-nm-1.01.42.4-1
ii  gir1.2-nma-1.0   1.10.6-1
ii  gir1.2-pango-1.0 1.50.12+ds-1
ii  gir1.2-polkit-1.0122-3
ii  gir1.2-rsvg-2.0  2.54.5+dfsg-1
ii  gir1.2-soup-3.0  3.2.2-2
ii  gir1.2-upowerglib-1.00.99.20-2
ii  gir1.2-webkit2-4.1   2.40.2-1~deb12u1
ii  gnome-backgrounds43.1-1
ii  gnome-settings-daemon43.0-4
ii  gnome-shell-common   43.4-1
ii  gsettings-desktop-schemas43.0-1
ii  gstreamer1.0-pipewire0.3.65-3
ii  libatk-bridge2.0-0   2.46.0-5
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9
ii  libcairo21.16.0-7
ii  libecal-2.0-23.46.4-2
ii  libedataserver-1.2-273.46.4-2
ii  libgcr-base-3-1  3.41.1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgirepository-1.0-11.74.0-3
ii  libgjs0g 1.74.2-1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.74.6-2
ii  libglib2.0-bin   2.74.6-2
ii  libgnome-autoar-0-0  0.4.3-1
ii  libgnome-desktop-3-2043.2-2
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-3-0   3.24.37-2
ii  libgtk-4-1   4.8.3+ds-2
ii  libical3 3.0.16-1+b1
ii  libjson-glib-1.0-0   1.6.6-1
ii  libmutter-11-0   43.4-2
ii  libnm0   1.42.4-1
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libpolkit-agent-1-0  122-3
ii  libpolkit-gobject-1-0122-3
ii  libpulse-mainloop-glib0  16.1+dfsg1-2+b1
ii  libpulse016.1+dfsg1-2+b1
ii  libsecret-1-00.20.5-3
ii  libsystemd0 

Bug#1039089: [PATCH 1/1] correct_posix1e_v1_delimiters: provide path for error messages

[Aaron M. Ucko]

Rob Browning  writes:

> Thanks to Phil Sutter and Johannes Berg (at least) for reporting the
> problem.

FWIW, I ran into it too, but reported it downstream, as
https://bugs.debian.org/1039089; the patch LGTM offhand, though I
haven't tested it and presumably no longer have an "organic" test case.

Thanks for the fix!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#1040174: nvidia-driver: Can't upgrade to nvidia-driver-525.116.04-1 on debian unstable: build fails

[Andreas Beckmann]

which version of linux-kbuild-6.3 do you have installed?
(dpkg -l linux-kbuild-6.3)

Andreas

Bug#1040178: Kernel modules will not build, missing asm/orc_header.h

[Andreas Beckmann]

which version of linux-kbuild-6.3 do you have installed?
(dpkg -l linux-kbuild-6.3)


Andreas

Bug#982972: dose-extra: option to exclude Extra-Source-Only packages for dose-ceve

[James McCoy]

On Wed, Feb 17, 2021 at 11:41:02PM +0800, Shengjing Zhu wrote:
> Could you add an option for dose-ceve to ignore the Extra-Source-Only
> packages.
> 
> dose-ceve is used in ratt to find out the reverse build depends, however
> sometimes it will pick up packages which are Extra-Source-Only.

Would using "--latest 1" achieve the same result?

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#1040187: ratt: Add a -shallow option to only build immediate reverse deps

[James McCoy]

Package: ratt
Version: 0.0~git20190123.9e77a6d-1+b6
Severity: wishlist

The current use of dose-ceve to determine the reverse deps finds all
transitive reverse deps, too.  For many packages, only the immediate
reverse deps would actually be affected, so rebuilding all reverse deps
is a waste of time.

Experimentally, it seems dose-ceve's "--depth 2" would achieve this, but
it might be good to confirm with someone that understands dose better
than I.

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ratt depends on:
ii  libc6   2.37-3
ii  sbuild  0.85.2

Versions of packages ratt recommends:
ii  dose-extra  7.0.0-1+b2

ratt suggests no packages.

-- no debconf information

Bug#1040186: ipmitool: IANA PEN registry open failed: No such file or directory

[Marc Lehmann]

Package: ipmitool
Version: 1.8.19-4
Severity: normal

Dear Maintainer,

after upgrade to bookworm, ipmitool outputs this on every invocation:

IANA PEN registry open failed: No such file or directory

   * What led up to the situation?

upgrading to bookworm, before it was fine.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

using ipmitool

   * What was the outcome of this action?

the message:

IANA PEN registry open failed: No such file or directory

   * What outcome did you expect instead?

no such message.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'oldstable-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, x32

Kernel: Linux 6.1.35-schmorp (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_USER, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ipmitool depends on:
ii  init-system-helpers1.65.2
ii  libc6  2.36-9
ii  libfreeipmi17  1.6.10-1+b1
ii  libreadline8   8.2-1.3
ii  libssl33.0.9-1
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages ipmitool recommends:
ii  openipmi  2.0.33-1+b1

ipmitool suggests no packages.

-- no debconf information

Bug#1038684: firmware-ath9k-htc: TP-Link TL-WN722N is not reported by "iw dev".

[peter]

From:   Bastian Germann 
Date:   Sat, 1 Jul 2023 16:03:11 +0200
> As you are the only one who complained up to now ...

I received an email from another user who observed the failure. Some 
users observe a failure of a peripheral and resort to another device 
rather than report.

> I am downgrading the severity for this.

OK.

> Can you please post the dmesg output (or just the lines that relate 
> to this driver)?

$ # Plug the TP-Link TL-WN722N after starting dmesg.
$ dmesg -W
[43926.641324] usb 1-2: new high-speed USB device number 9 using xhci_hcd
[43926.806006] usb 1-2: New USB device found, idVendor=0cf3, idProduct=9271, 
bcdDevice= 1.08
[43926.806011] usb 1-2: New USB device strings: Mfr=16, Product=32, 
SerialNumber=48
[43926.806013] usb 1-2: Product: USB2.0 WLAN
[43926.806015] usb 1-2: Manufacturer: ATHEROS
[43926.806017] usb 1-2: SerialNumber: 12345
[43926.807143] usb 1-2: ath9k_htc: Firmware ath9k_htc/htc_9271-1.dev.0.fw 
requested
[43926.807438] usb 1-2: firmware: direct-loading firmware 
ath9k_htc/htc_9271-1.dev.0.fw
[43927.090944] usb 1-2: ath9k_htc: Transferred FW: 
ath9k_htc/htc_9271-1.dev.0.fw, size: 51008
[43927.339373] ath9k_htc 1-2:1.0: ath9k_htc: HTC initialized with 33 credits
[43927.609120] ath9k_htc 1-2:1.0: ath9k_htc: FW Version: 1.4
[43927.609123] ath9k_htc 1-2:1.0: FW RMW support: On
[43927.609126] ath: EEPROM regdomain: 0x809c
[43927.609127] ath: EEPROM indicates we should expect a country code
[43927.609128] ath: doing EEPROM country->regdmn map search
[43927.609129] ath: country maps to regdmn code: 0x52
[43927.609130] ath: Country alpha2 being used: CN
[43927.609131] ath: Regpair used: 0x52
[43927.619075] ath9k_htc 1-2:1.0 wlxe894f6248352: renamed from wlan0
[43927.620602] ieee80211 phy1: Atheros AR9271 Rev:1

- 
mobile: +1 778 951 5147
VoIP:   +1 604 670 0140

Bug#852964: golang-github-hashicorp-yamux: FTBFS randomly (failing tests)

[Cyril Brulebois]

Hi,

Paul Gevers  (2023-06-22):
> I'm seeing flaky tests on ci.debian.net too [1]. Because the
> unstable-to-testing migration software now blocks on regressions in testing,
> flaky tests, i.e. tests that flip between passing and failing without
> changes to the list of installed packages, are causing people unrelated to
> your package to spend time on these tests. Therefor the Release Team
> considers the issue of serious severity.
> 
> Paul
> 
> [1] https://ci.debian.net/packages/g/golang-github-hashicorp-yamux/

I've encountered this a few times already but got told on #debci that
there were no problems at all…

Right now, that page only lists 0.0+git20190923.df201c7-1 for release
architectures in unstable (0.0+git20210316.a95892c-2 for riscv64 only)
while that upload happened 20+ days ago.

Clicking a random arch (amd64) gives me a huge list of tests for that
version, the last one having run on 2023-06-05. This makes no sense to
me.

This also means that the two archs where the failures seem to happen
(armel and armhf) have logs for failed tests with an obsolete version.
That doesn't quite help.

Migration to testing happened 2023-06-17, and yet the testing column has
a mix of both versions. This makes no sense to me either. At least,
there, we have logs for failed tests for the most recent version…


At the moment, I have only been able to produce a single occurrence of a
different problem:

=== RUN   TestGoAway
session_test.go:536: err: 
2023/07/03 02:33:15 [WARN] yamux: frame for missing stream: Vsn:0 Type:1 
Flags:1 StreamID:1 Length:0
2023/07/03 02:33:15 [ERR] yamux: Failed to write header: io: read/write on 
closed pipe
--- FAIL: TestGoAway (0.00s)


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

Bug#1036461: Please update to at least v7.0.1

[Boyuan Yang]

Hi,

在 2023-06-26星期一的 20:18 -0400，Nicholas D Steeves写道：
> Hello,
> 
> Boyuan Yang  writes:
> 
> > 在 2023-05-22星期一的 20:55 -0400，Nicholas D Steeves写道：
> > > Roman Lebedev  writes:
> > > 
> > We could do bookworm-backport for easyeffects after Debian 12 release, no
> > problem. The package belongs to Multimedia Team from the very beginning; its
> > packaging repo can be moved to salsa multimedia-team at anytime.
> 
> Would you please move that repo?  I requested this from the salsa admins
> on IRC, but didn't receive a reply.  I'll CC them now.
> 
> Other than that, easyeffects 7.0.1-1 is now in testing and can be
> backported.  I've been testing in on bookworm since I made the upload to
> experimental, and it works well.

Looks like Non-Salsa-admins cannot move repo out of Debian group through
https://salsa.debian.org/debian/easyeffects/edit . Non-Salsa-admins cannot
delete repos under Debian group either.

On the other hand, bookworm-backports is not open yet according to
https://lists.debian.org/debian-backports/2023/06/msg00016.html .

Thanks,
Boyuan Yang


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

Bug#1039498: gir1.2-harfbuzz-0.0: missing dependency on libharfbuzz0b

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

block 1039498 by 1039714
quit

Well, I tried fixing with the attached patch (fix-gir.patch), using the 
patched dh_girepository. The resulting gir file (also attached) seems to 
reference libharfbuzz.so:

  
  
  
  

is that correct ? Yet the resulting gir1.2-harfbuzz-0.0 package only depends 
on libharfbuzz0b package !

-- 
‎أحمد المحمودي (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#1040185: firmware-amd-graphics: Older DMCUB firmware for AMDPU causes some panels to hang irrecoverably when PSR is enabled

[Gabriel Wayne]

Package: firmware-amd-graphics
Version: 20230210-5
Severity: important
Tags: patch upstream
X-Debbugs-Cc: linux.footwork...@simplelogin.com

Dear Maintainer,

Rembrandt GPUs in combination with certain Parade TCONs are suffering from
irrecoverable system hangs when PSR is enabled (as it is by default). There is
a Gitlab ticket for this issue here:
https://gitlab.freedesktop.org/drm/amd/-/issues/2443#note_1966723

An upstream firmware patch has landed which mitigates the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/amdgpu/yellow_carp_dmcub.bin?id=9dbd8ec28fd810e5f4f9da41452aba74896a5564

Please consider backporting this patch to Bookworm. Thank you very much.


-- 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/16 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

firmware-amd-graphics depends on no packages.

firmware-amd-graphics recommends no packages.

Versions of packages firmware-amd-graphics suggests:
ii  initramfs-tools  0.142

-- no debconf information

Bug#849400: debian-installer: LUKS on rootfs and boot

[Cyril Brulebois]

Hi,

Jinesh Choksi  (2023-07-02):
> The issue is this block of code:
> https://salsa.debian.org/installer-team/partman-crypto/-/blob/master/check.d/crypto_check_mountpoints#L94-102
> 
> This 17 year old "Check - Is there a /boot partition for encrypted
> root?" is no longer valid.

It is.

> Grub2 added support for accessing LUKS1 partitions in 2011 -
> https://git.savannah.gnu.org/cgit/grub.git/commit/?id=a251b71915e40194d12995dbac9efd787687f988

Sure, that's known, and there were two talks during Mini-DebConfs in
2019 about this and LUKS2 (Marseille, Hamburg).

> Grub2 support for LUK2 is also present but only for PBKDF2 keys -
> https://git.savannah.gnu.org/cgit/grub.git/commit/?id=365e0cc3e7e44151c14dd29514c2f870b49f9755

And since default LUKS2 settings are argon2id (argon2i previously), that
means that cannot work.

> For people who use LUKS1 to do full disk encryption, this "Check - Is
> there a /boot partition for encrypted root?" is a blocker in the
> Debian installer.

People finding their way to use LUKS1 instead of the default LUKS2 can
remove this check on their own.

> Dear maintainer(s), please review this bug report and remove this
> check.

Not until GRUB gets support for argon2i{d,}. And that's where my focus
is right now when it comes to d-i vs. LUKS.

PoC at https://salsa.debian.org/kibi/grub/-/commits/luks2-argon2-v0
but I have better plans to investigate.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#1040184: xserver-xorg-video-amdgpu: amdgpu causes unrecoverable system hangs on Rembrandt systems with certain laptop panels

[Gabriel Wayne]

Package: xserver-xorg-video-amdgpu
Version: 23.0.0-1
Severity: important
Tags: patch upstream
X-Debbugs-Cc: linux.footwork...@simplelogin.com

Dear Maintainer,

Laptops with Rembrandt GPUs and certain panels are experiencing total and
unrecoverable system hangs with the following error:

amdgpu :04:00.0: [drm] *ERROR* [CRTC:67:crtc-0] flip_done timed out

After this error occurs the panel is completely frozen and a hard reboot is
required in order to recover.

This has been diagnosed as a problem with PRS-SU on some Parade TCONs running
on older firmware. There is a gitlab ticket which references patches confirmed
to fix the problem: https://gitlab.freedesktop.org/drm/amd/-/issues/2443

Please incorporate these patches into the next Debian stable release if
possible. Thank you.


-- Package-specific info:
/etc/X11/X does not exist.
/etc/X11/X is not a symlink.
/etc/X11/X is not executable.

VGA-compatible devices on PCI bus:
--
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. 
[AMD/ATI] Rembrandt [Radeon 680M] [1002:1681] (rev d1)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 0

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08)

No Xorg X server log files found.

udev information:
-
P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
M: input5
R: 5
U: input
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
E: SUBSYSTEM=input
E: PRODUCT=19/0/1/0
E: NAME="Power Button"
E: PHYS="LNXPWRBN/button/input0"
E: PROP=0
E: EV=3
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: USEC_INITIALIZED=1045297
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: ID_FOR_SEAT=input-acpi-LNXPWRBN_00
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

P: /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4
M: event4
R: 4
U: input
D: c 13:68
N: input/event4
L: 0
E: DEVPATH=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input5/event4
E: SUBSYSTEM=input
E: DEVNAME=/dev/input/event4
E: MAJOR=13
E: MINOR=68
E: USEC_INITIALIZED=15239001
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXPWRBN:00
E: ID_PATH_TAG=acpi-LNXPWRBN_00
E: XKBMODEL=pc105
E: XKBLAYOUT=us
E: BACKSPACE=guess
E: LIBINPUT_DEVICE_GROUP=19/0/1:LNXPWRBN/button
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:

P: 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/LNXVIDEO:00/input/input7
M: input7
R: 7
U: input
E: 
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/LNXVIDEO:00/input/input7
E: SUBSYSTEM=input
E: PRODUCT=19/0/6/0
E: NAME="Video Bus"
E: PHYS="LNXVIDEO/video/input0"
E: PROP=0
E: EV=3
E: KEY=3e000b 0 0 0
E: MODALIAS=input:b0019vp0006e-e0,1,kE0,E1,E3,F1,F2,F3,F4,F5,ramlsfw
E: USEC_INITIALIZED=1071547
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXVIDEO:00
E: ID_PATH_TAG=acpi-LNXVIDEO_00
E: ID_FOR_SEAT=input-acpi-LNXVIDEO_00
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

P: 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/LNXVIDEO:00/input/input7/event5
M: event5
R: 5
U: input
D: c 13:69
N: input/event5
L: 0
E: 
DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/LNXVIDEO:00/input/input7/event5
E: SUBSYSTEM=input
E: DEVNAME=/dev/input/event5
E: MAJOR=13
E: MINOR=69
E: USEC_INITIALIZED=15270866
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-LNXVIDEO:00
E: ID_PATH_TAG=acpi-LNXVIDEO_00
E: XKBMODEL=pc105
E: XKBLAYOUT=us
E: BACKSPACE=guess
E: LIBINPUT_DEVICE_GROUP=19/0/6:LNXVIDEO/video
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
M: input2
R: 2
U: input
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
E: SUBSYSTEM=input
E: PRODUCT=19/0/1/0
E: NAME="Power Button"
E: PHYS="PNP0C0C/button/input0"
E: PROP=0
E: EV=3
E: KEY=10 0
E: MODALIAS=input:b0019vp0001e-e0,1,k74,ramlsfw
E: USEC_INITIALIZED=1045242
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-PNP0C0C:00
E: ID_PATH_TAG=acpi-PNP0C0C_00
E: ID_FOR_SEAT=input-acpi-PNP0C0C_00
E: TAGS=:seat:
E: CURRENT_TAGS=:seat:

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event1
M: event1
R: 1
U: input
D: c 13:65
N: input/event1
L: 0
E: DEVPATH=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event1
E: SUBSYSTEM=input
E: DEVNAME=/dev/input/event1
E: MAJOR=13
E: MINOR=65
E: USEC_INITIALIZED=15231950
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_PATH=acpi-PNP0C0C:00
E: ID_PATH_TAG=acpi-PNP0C0C_00
E: XKBMODEL=pc105
E: XKBLAYOUT=us
E: BACKSPACE=guess
E: LIBINPUT_DEVICE_GROUP=19/0/1:PNP0C0C/button
E: TAGS=:power-switch:
E: CURRENT_TAGS=:power-switch:

P: /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
M: input3
R: 

Bug#1040141: FTBFS: FAIL: TestCheckoutGit

[Adrian Bunk]

On Sun, Jul 02, 2023 at 01:59:01PM +, Bastien Roucariès wrote:
> Source: docker.io
> Version: 18.09.1+dfsg1-7.1+deb10u3
> Severity: serious
> Justification: FTBFS
> X-Debbugs-Cc: debian-...@lists.debian.org
> 
> Dear Maintainer,
> 
> The current security version FTBFS for me with

As a general note, maintainers are no longer responsible for the version 
in LTS.


> -- FAIL: TestCheckoutGit (0.52s)
> gitutils_test.go:188: assertion failed: error is not nil: exit status 128
> 
> 
> I am currently debugging this regression.

Trying in reproducible builds, buster built but bullseye failed:
https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/docker.io.html

The error message looks like #1024506.


> Bastien

cu
Adrian

Bug#1040183: Acknowledgement (zfs-initramfs: snapshots for rootfs mounted in /root/.zfs/snapshot)

[Richard van den Berg]

Upstream issue report: https://github.com/openzfs/zfs/issues/14383

Bug#208659: Introduction – Inna Zaimenko & Deepli

[inna]

Dear Sir or Madam,

I would like to use the opportunity to introduce myself – my name is Inna 
Zaimenko, I am an accomplished biologist and a business lady. I have a company 
Deepli GmbH (https://deepli.net) in Germany and am currently located in UAE on 
a business license.

I live in Germany since 10 years, did a PhD in Integrative Oncology at Charite 
and Master's in Cancer Biology at Heidelberg University. I have Deepli since 
2018, we are an IT company, but because of my background we also do a lot of 
business strategy consulting projects, market research, establish business 
partnerships, and help in general with what we can to those companies 
interested.

We have several software solutions for data mining of scientific literature, 
but we also do custom data science and web development projects. We have access 
to 1.6 millions scientists and 10 millions+ companies.

Among our non-IT projects were market research for medical device manufacturer, 
business strategy for growth for plant engineering company, finding suppliers 
or distributors for medical implant companies, finding a GMP manufacturer for a 
clinical trial, finding journals that are interested in a manuscript, and even 
establishment of two companies in UAE for a project management company from 
Germany.

We can offer:
– data science and web development
– business strategy for growth 
– email marketing at scale from own mail server
– company setup in UAE
– search for information of interest incl. research, supplier, etc.

Is there anything we can do for you at the moment?

I hope this email does not bother you, if yes, I will not contact you again, 
apologies for inconvenience. 

Have a great day!

Kind regards,
Inna Zaimenko


CEO at Deepli GmbH
https://deepli.net
c/o HQ Feringastr. 6, 85774 Unterföhring, Germany
DIC Building 16 Ground Floor, Dubai, UAE

Bug#1040183: zfs-initramfs: snapshots for rootfs mounted in /root/.zfs/snapshot

[Richard van den Berg]

Package: zfs-initramfs
Version: 2.1.11-1
Severity: normal

I have ZFS setup with rootfs which is mounted at boot in /root by initramfs.
This causes the ZFS snapshots to be mounted in /root/.zfs/snapshot instead
of /.zfs/snapshot

Accessing any snapshot in /.zfs/snapshot gives this error:

Too many levels of symbolic links

The root cause is explained at 
https://github.com/openzfs/zfs/issues/9461#issuecomment-1376162949

-- 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_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
C.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zfs-initramfs depends on:
ii  busybox 1:1.35.0-4+b3
ii  initramfs-tools 0.142
ii  zfs-dkms [zfs-modules]  2.1.11-1
ii  zfsutils-linux  2.1.11-1

zfs-initramfs recommends no packages.

zfs-initramfs suggests no packages.

-- no debconf information

Bug#1040182: /usr/share/doc/raspi-firmware/changelog.Debian.gz: Adding more support for 'v3d' on rpi4!

[Sally A.haj]

Package: raspi-firmware
Version: 1.20220830+ds-1
Severity: important
File: /usr/share/doc/raspi-firmware/changelog.Debian.gz
X-Debbugs-Cc: sallya...@yahoo.com

Dear Maintainer,

Hello there,

Debian on rpi4 with GUI, I have tried Gnome/Xfce/Sway, all for me have
the same issues: (I am using rpi4 with 8GB RAM, as a daily desktop
machine, so I use it heavily, 24/7 it's running) 

Maine Issues:
* Some Application, I can't maximize and restore them (firefox-esr,
chromium) unless I enforce them to use wayland.
* Some application, I can't use them at all, can't open/can't run
properly (gimp), but when using the beta release, it works, as it uses
wayland by default.
* Freezing/locks up frequently, which is very annoying.

I am actually a Fedora user, but after recently bad news from Redhat
regarding the binary source of RHEL, I decided to move on.
Fedora 37/38 works just fine and smoothly on rpi4, specifically after
the hardware GPU acceleration driver supports has reached
mainline/upstream kernel "v3d", so I thought that means, debian should
do the same.
I noticed in Fedora, they have 'firmware' updated and has 'overlays',
and in their config.txt "dtoverlay=vc4-kms-v3d-pi4", so I have decided
to give that a try on debian after I talk to "gwolf".

All the above issues have solved by the following:

* I downloaded the latest (firmware-1.20230405) , unzipped it.
* Copied "firmware-1.20230405/boot/overlays" folder to /boot/firmware/
* Added these lines to /etc/default/raspi-firmware-custom
```
# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d-pi4
dtoverlay=cma,cma-256
max_framebuffers=2

# Disable compensation for displays with overscan
disable_overscan=1
```
* Reload raspi-firmware package:
dpkg-reconfigure raspi-firmware

* Then reboot the system.

Thank you so much all.

Sally.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 6.3.0-1-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
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)
LSM: AppArmor: enabled

Versions of packages raspi-firmware depends on:
ii  dosfstools  4.2-1
ii  dpkg1.21.22

raspi-firmware recommends no packages.

Versions of packages raspi-firmware suggests:
ii  bluez-firmware 1.2-9
ii  firmware-brcm80211 20230515-2
pn  firmware-misc-nonfree  

-- Configuration Files:
/etc/default/raspi-firmware changed [not included]

-- no debconf information

Bug#1039986: xterm unicode rendering issue

[Thomas Dickey]

On Fri, Jun 30, 2023 at 06:54:00PM +0200, 10dmar10 wrote:
> Package: xterm
> Version: 382-2
> Severity: minor
> 
> Hi,
> 
> I noticed a unicode character rendering issue in xterm since
> the latest update in debian testing.
> 
> The problem seems to be limited to double width japanese/chinese characters 
> and
> only when using the default bitmap x11 font.

thanks - I had thought the boxes problem was fixed in #381, but
someone reported a related problem on Wednesday, and followed up
with some debugging details (will be working on that soon - after
a more urgent bug-fix).

-- 
Thomas E. Dickey 
https://invisible-island.net


signature.asc
Description: PGP signature

Bug#1040181: openjdk-8: Please disable tests on zero architectures

[Adrian Bunk]

Source: openjdk-8
Version: 8u382~b04-1
Severity: important
Tags: patch
X-Debbugs-Cc: Thorsten Glaser 

Zero is slow, OpenJDK has many tests, and on slower ports
architectures the build can literally take a month:
https://buildd.debian.org/status/logs.php?pkg=openjdk-8&arch=alpha

Please fix this with something like:

--- debian/rules.old2023-07-02 21:46:21.815210161 +
+++ debian/rules2023-07-02 21:48:21.783102835 +
@@ -137,7 +137,7 @@
 endif
 
 with_check = $(if $(findstring nocheck, $(DEB_BUILD_OPTIONS)),,yes)
-ifneq (,$(filter $(DEB_HOST_ARCH), armel))
+ifeq (,$(filter $(DEB_HOST_ARCH), $(hotspot_archs)))
   with_check = disabled running check on $(DEB_HOST_ARCH)
 endif
 ifneq (,$(filter $(distrel),precise))

Bug#1040158: texlive-latex-extra: tex4ebook with mathml prints \lim, limsup etc. in italics

[Preuße]

On 02.07.2023 17:53, Karl Grill wrote:

Hi Karl,


*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
  Trying to convert Latex source to Epub 3 with MathML
* What exactly did you do (or not do) that was effective (or
  ineffective)?
  Run "tex4ebook -f epub3 test.tex mathml"
   
* What was the outcome of this action?

  The resulting test.epub gives a "Math Input Error" when viewed in Calibre,
  test.xhtml renders in firefox, but the "lim sup" is rendered in italics 
instead of normal print.

Please be so kind to track down the issue yourself and (eventually) 
escalate it to the correct party. I won't find the time to do it myself. 
Sorry!


Hilmar

--
sigfault



OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1039976: detex.1: some remarks and editorial fixes in a patch for the manual

[Preuße]

On 30.06.2023 22:48, Preuße...@buxtehude.debian.org, Hilmar wrote:

Hi,

It would be nice if you could provide your content as attachment, this 
would help me to extract the content, even if it is just text.
Further consider to submit your suggestions directly to the upstream 
maintainer of the software, if possible.


For that one I've created an PR: 
https://github.com/pkubowicz/opendetex/pull/83


H.


OpenPGP_0x0C871C4C653C1F59.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1040180: bookworm-pu: package kf5-messagelib/22.12.3-2~deb12u1

[Hefee]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: kf5-message...@packages.debian.org, he...@debian.org
Control: affects -1 + src:kf5-messagelib

[ Reason ]
KMail does can't verify signatures if they are signed with subkeys.

[ Impact ]
Users will see an invalid signature instead of a valid one.

[ Tests ]
Same package is on unstable for some days without any issue.
I also run KMail on a daily basis.

[ Risks ]
The patch is quite small and is a direct patch from upstream. It is very
unlikly that this has side effects.

[ Checklist ]
  [*] *all* changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in bookworm
  [*] the issue is verified as fixed in unstable
diff -Nru kf5-messagelib-22.12.3/debian/changelog 
kf5-messagelib-22.12.3/debian/changelog
--- kf5-messagelib-22.12.3/debian/changelog 2023-03-01 21:33:30.0 
+0100
+++ kf5-messagelib-22.12.3/debian/changelog 2023-07-02 23:21:13.0 
+0200
@@ -1,3 +1,15 @@
+kf5-messagelib (4:22.12.3-2~deb12u1) bookworm; urgency=medium
+
+  * Rebuilt for bookworm.
+
+ -- Sandro Knauß   Sun, 02 Jul 2023 23:21:13 +0200
+
+kf5-messagelib (4:22.12.3-2) unstable; urgency=medium
+
+  * Add upstream patch to search also for subkeys (Closes: #1037363).
+
+ -- Sandro Knauß   Tue, 27 Jun 2023 14:09:30 +0200
+
 kf5-messagelib (4:22.12.3-1) unstable; urgency=medium
 
   [ Patrick Franz ]
diff -Nru kf5-messagelib-22.12.3/debian/patches/series 
kf5-messagelib-22.12.3/debian/patches/series
--- kf5-messagelib-22.12.3/debian/patches/series2022-12-20 
01:37:29.0 +0100
+++ kf5-messagelib-22.12.3/debian/patches/series2023-06-27 
13:33:50.0 +0200
@@ -1 +1,2 @@
 enable_debianabimanager.diff
+upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
diff -Nru 
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
 
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
--- 
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
   1970-01-01 01:00:00.0 +0100
+++ 
kf5-messagelib-22.12.3/debian/patches/upstream-Look-for-matching-subkey-if-no-key-was-found-for-fin.patch
   2023-06-27 13:34:36.0 +0200
@@ -0,0 +1,44 @@
+From 70f39256784280d2034aa7bf1c4765f606c22d56 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Ingo=20Kl=C3=B6cker?= 
+Date: Wed, 3 May 2023 14:51:18 +0200
+Subject: Look for matching subkey if no key was found for fingerprint
+
+If the message was signed with a signing subkey instead of with the
+primary key of an OpenPGP certificate, then we won't find a key with
+findByFingerprint(). To look for a matching subkey we need to use
+findSubkeysByKeyID().
+
+FIXED-IN: 5.23.1
+BUG: 469304
+(cherry picked from commit 606ea1478d2d5b5aacdc6ef3f050655fe0352d87)
+---
+ mimetreeparser/src/messagepart.cpp | 12 +++-
+ 1 file changed, 11 insertions(+), 1 deletion(-)
+
+diff --git a/mimetreeparser/src/messagepart.cpp 
b/mimetreeparser/src/messagepart.cpp
+index f1489d5e0..3e99e71c8 100644
+--- a/mimetreeparser/src/messagepart.cpp
 b/mimetreeparser/src/messagepart.cpp
+@@ -848,8 +848,18 @@ void SignedMessagePart::sigStatusToMetaData()
+ // Search for the key by its fingerprint so that we can check for
+ // trust etc.
+ key = 
Kleo::KeyCache::instance()->findByFingerprint(signature.fingerprint());
++if (key.isNull() && signature.fingerprint()) {
++// try to find a subkey that was used for signing;
++// assumes that the key ID is the last 16 characters of the 
fingerprint
++const auto fpr = std::string_view{signature.fingerprint()};
++const auto keyID = std::string{fpr, fpr.size() - 16, 16};
++const auto subkeys = 
Kleo::KeyCache::instance()->findSubkeysByKeyID({keyID});
++if (subkeys.size() > 0) {
++key = subkeys[0].parent();
++}
++}
+ if (key.isNull()) {
+-qCDebug(MIMETREEPARSER_LOG) << "Found no Key for Fingerprint" 
<< signature.fingerprint();
++qCDebug(MIMETREEPARSER_LOG) << "Found no key or subkey for 
fingerprint" << signature.fingerprint();
+ }
+ }
+ 
+-- 
+2.40.1
+

Bug#1040167: [aure...@debian.org: Re: Fwd: (buildd chroot bug) Re: Bug#1040167: openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian]

[Aurelien Jarno]

I realized that message has been forwarded to *all* buildd maintainers,
and I answered there. So let me forward the answer to the bug report.

- Message transféré de Aurelien Jarno  -

From: Aurelien Jarno 
To: Thorsten Glaser 
Cc: buildd-maintain...@buildd.debian.org
User-Agent: Mutt/2.2.9 (2022-11-12)
Date: Sun, 2 Jul 2023 23:02:38 +0200
Subject: Re: Fwd: (buildd chroot bug) Re: Bug#1040167: openjdk-8-jre-headless: 
version 8u382~b04-1 depends on libjpeg8 which is not in Debian
Message-ID: 

[ tl;dr for buildd-maintainers: nothing to do. ]


Hi,

On 2023-07-02 21:44, Thorsten Glaser wrote:
> Hi,
> 
> please check the footnote below. Thanks!
> 
> -- Forwarded message --
> Message-ID: <2d85d8b1-45e2-d6a8-5088-7fd838b7...@tarent.de>
> Date: Sun, 2 Jul 2023 20:20:16 +0200 (CEST)
> 
> Dixi quod…
> 
> >Indeed. Weird.
> >
> >Thanks for reporting, I’ll have two or three looks at it… fixing that
> >is going to be… fun. Not.
> 
> OK so first analysis is showing the cause of the problem:
> 
> • the buildd chroots for sid/unstable do not identify themselves as
>   sid/unstable but instead as trixie/testing, which is a bug onto
>   itself¹

No the chroots do not identify themselves. I guess you check the output
of "lsb_release -a". If you believe the output is not correct, please
report the bug to the lsb-release package.

> however if the buildd chroot bug could be fixed, I’d be glad.

There is nothing to fix on the buildd chroot side, please fix your
debian/rules script instead.

> ① sid buildd chroots should save the following content…
>   PRETTY_NAME="Debian GNU/Linux sid"
>   NAME="Debian GNU/Linux"
>   ID=debian
>   HOME_URL="https://www.debian.org/";
>   SUPPORT_URL="https://www.debian.org/support";
>   BUG_REPORT_URL="https://bugs.debian.org/";
>   VERSION_ID=unstable
>   VERSION_CODENAME=sid
>   … as /usr/lib/os-release.sid (in the chroot) and run…
>   # dpkg-divert --rename --divert /usr/lib/os-release.dpkg-dist \
> --add /usr/lib/os-release
>   # ln -sfT os-release.sid /usr/lib/os-release
>   … in the chroot, so the reported lsb_release is correct. They used
>   to have this in /etc/lsb-release, but the lsb-release program no
>   longer uses that.

That's plainly wrong, that's not the job of a buildd to configure that.

The chroots are just created using debootstrap --variant=buildd, which
is basically a minimal chroot with build-essential. There shouldn't be
any further visible configuration to the chroot, as your package is
supposed to build the same way on a normal installation outside of a
chroot. The functionality you describe should just come by installing
additional packages.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net


- Fin du message transféré -

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1039883: The issue impacts SSD disks as well

[Hervé Werner]

I've just faced this issue on the SSD disk as well, so it seems that the 
probability is just lower on a speedier disk.

Bug#1040144: same issue with latest kernel from experimental

[Jérôme]

Same issue with latest kernel from experimental.

6.4.0-0-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.4.1-1~exp1 (2023-07-01)
x86_64 GNU/Linux

-- 
Jérôme

Bug#1040179: spyder: Spyder reports missing dependency: pylsp_black >=1.2.0 : None (NOK), but python3-pylsp-black 1.2.1-2 is installed

[Mike Haag]

Package: spyder
Version: 5.4.2+ds-5
Severity: normal
X-Debbugs-Cc: mhaag85...@gmail.com

Dear Maintainer,

Ran $spyder --reset but, still get the missing dependency message.


-- 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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages spyder depends on:
ii  python3 3.11.2-1+b1
ii  python3-spyder  5.4.2+ds-5

spyder recommends no packages.

Versions of packages spyder suggests:
pn  python3-spyder-unittest  

Versions of packages python3-spyder depends on:
ii  ipython3   8.5.0-4
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-mathjax  2.7.9+dfsg-1
ii  pyflakes3  2.5.0-1
ii  pylint 2.16.2-2
ii  python33.11.2-1+b1
ii  python3-atomicwrites   1.4.1-1
ii  python3-autopep8   2.0.1-1
ii  python3-chardet5.1.0+dfsg-2
ii  python3-cloudpickle2.2.0-1
ii  python3-cookiecutter   1.7.3-3
ii  python3-diff-match-patch   20200713-2
ii  python3-docutils   0.19+dfsg-6
ii  python3-flake8 5.0.4-4
ii  python3-intervaltree   3.0.2-1.1
ii  python3-ipython8.5.0-4
ii  python3-jedi   0.18.2-1
ii  python3-jellyfish  0.8.9-1+b4
ii  python3-jsonschema 4.10.3-1
ii  python3-keyring23.9.3-2
ii  python3-mccabe 0.7.0-1
ii  python3-nbconvert  6.5.3-3
ii  python3-numpydoc   1.5.0-1
ii  python3-parso  0.8.3-1
ii  python3-pexpect4.8.0-4
ii  python3-pickleshare0.7.5-5
ii  python3-pkg-resources  66.1.1-1
ii  python3-psutil 5.9.4-1+b1
ii  python3-pycodestyle2.10.0-1
ii  python3-pydocstyle 6.2.3-3
ii  python3-pygments   2.14.0+dfsg-1
ii  python3-pylint-venv2.3.0-2
ii  python3-pyls-spyder0.4.0-2
ii  python3-pylsp  1.7.1-1
ii  python3-pylsp-black1.2.1-2
ii  python3-pyqt5  5.15.9+dfsg-1
ii  python3-pyqt5.qtwebengine  5.15.6-1
ii  python3-qdarkstyle 3.1+ds1-1
ii  python3-qstylizer  0.2.2-1
ii  python3-qtawesome  1.2.2+dfsg-1
ii  python3-qtconsole  5.4.0-1
ii  python3-qtpy   2.3.0-1
ii  python3-rope   1.7.0-1
ii  python3-rtree  1.0.1-1
ii  python3-setuptools 66.1.1-1
ii  python3-sphinx 5.3.0-4
ii  python3-spyder-kernels 2.4.2-1
ii  python3-textdistance   4.5.0-1
ii  python3-three-merge0.1.1-4
ii  python3-watchdog   2.2.1-1
ii  python3-xdg0.28-2
ii  python3-zmq24.0.1-4+b1
ii  spyder-common  5.4.2+ds-5
ii  yapf3  0.32.0-1

python3-spyder recommends no packages.

Versions of packages python3-spyder suggests:
pn  cython3 
ii  python3-matplotlib  3.6.3-1+b1
ii  python3-numpy   1:1.24.2-1
ii  python3-pandas  1.5.3+dfsg-2
ii  python3-pil 9.4.0-1.1+b1
ii  python3-scipy   1.10.1-2
ii  python3-sympy   1.11.1-1

Versions of packages python3-pyqt5 depends on:
ii  libc6 2.36-9
ii  libgcc-s1 12.2.0-14
ii  libpython3.11 3.11.2-6
ii  libqt5core5a [qtbase-abi-5-15-8]  5.15.8+dfsg-11
ii  libqt5dbus5   5.15.8+dfsg-11
ii  libqt5designer5   5.15.8-2
ii  libqt5gui55.15.8+dfsg-11
ii  libqt5help5   5.15.8-2
ii  libqt5network55.15.8+dfsg-11
ii  libqt5printsupport5   5.15.8+dfsg-11
ii  libqt5test5   5.15.8+dfsg-11
ii  libqt5widgets55.15.8+dfsg-11
ii  libqt5xml55.15.8+dfsg-11
ii  libstdc++612.2.0-14
ii  python3   3.11.2-1+b1
ii  python3-pyqt5.sip 12.11.1-1

-- no debconf information

Bug#1040065: [Pkg-netatalk-devel] Bug#1040065: afpd: systemd-logind ReleaseSession rejected by dbus-daemon

[Richard van den Berg]

Hi Daniel,


Thanks for reporting and tracking down the fix.
Do I understand correctly that the fix is confirmed to resolve the
issue for you?


Yes, it fixes the issue for me. No more dbus erorrs since I changed the 
file.



Now, /etc/pam.d/netatalk is obviously a generated file, so for a
persistent fix the file that needs to change is macros/pam-check.m4
I think this should ideally be fixed upstream, so if you have a moment
to spare it'd be helpful if you filed an issue ticket at
https://github.com/Netatalk/netatalk/issues


I have created an issue and pull-request there:

https://github.com/Netatalk/netatalk/issues/361
https://github.com/Netatalk/netatalk/pull/362

Kind regards,

Richard

Bug#1040165: pacemaker: Migration regression after upgrading bullseye to bookworm

[Ferenc Wágner]

Hi,

I've pushed the proposed backported fix to
https://salsa.debian.org/ha-team/pacemaker/-/commits/wferi/debian/bookworm/,
it would be great if you could test it.  You can download the build
artifacts from https://salsa.debian.org/ha-team/pacemaker/-/pipelines/547159
if you don't want to build the packages yourselves.  If they don't
exhibit the bug, I'll ask for a stable update.
-- 
Regards,
Feri.

Bug#1040178: Kernel modules will not build, missing asm/orc_header.h

[Richard A Burton]

Package: nvidia-kernel-dkms

Version: 525.116.04-1


Setting up nvidia-kernel-dkms (525.116.04-1) ...
Removing old nvidia-current-525.116.04 DKMS files...
Deleting module nvidia-current-525.116.04 completely from the DKMS tree.
Loading new nvidia-current-525.116.04 DKMS files...
Building for 6.3.0-1-amd64
Building initial module for 6.3.0-1-amd64
Error! Bad return status for module build on kernel: 6.3.0-1-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-current/525.116.04/build/make.log for
more information.
dpkg: error processing package nvidia-kernel-dkms (--configure):
 installed nvidia-kernel-dkms package post-installation script
subprocess returned error exit status 10
dpkg: dependency problems prevent configuration of nvidia-driver:
 nvidia-driver depends on nvidia-kernel-dkms (= 525.116.04-1) |
nvidia-kernel-525.116.04 | nvidia-open-kernel-525.116.04 |
nvidia-open-kernel-525.116.04; however:
  Package nvidia-kernel-dkms is not configured yet.
  Package nvidia-kernel-525.116.04 is not installed.
  Package nvidia-kernel-dkms which provides nvidia-kernel-525.116.04
is not configured yet.
  Package nvidia-open-kernel-525.116.04 is not installed.
  Package nvidia-open-kernel-525.116.04 is not installed.

dpkg: error processing package nvidia-driver (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.37-3) ...
Errors were encountered while processing:
 nvidia-kernel-dkms
 nvidia-driver
E: Sub-process /usr/bin/dpkg returned an error code (1)



Build log ends with errors such as:
/var/lib/dkms/nvidia-current/525.116.04/build/nvidia-drm.mod.c:10:10:
fatal error: asm/orc_header.h: No such file or directory
   10 | #include 
  |  ^~
compilation terminated.

Bug#1040177: apcupsd: No data from SmartUPS v/s 650 and broken code in ApcSmartUpsDriver::get_capabilities

[Ondrej Zary]

Package: apcupsd
Version: 3.14.14-3.1+b1
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: li...@rainbow-software.org

Dear Maintainer,
there are old bugs in apcupsd preventing it from getting almost any data from 
SmartUPS v/s 650:
# apcaccess
APC  : 001,018,0451
DATE : 2023-07-02 19:43:10 +0200
HOSTNAME : router
VERSION  : 3.14.14 (31 May 2016) debian
UPSNAME  : router
CABLE: Custom Cable Smart
DRIVER   : APC Smart UPS (any)
UPSMODE  : Stand Alone
STARTTIME: 2023-07-02 19:35:08 +0200
STATUS   : ONLINE
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
STATFLAG : 0x0508
END APC  : 2023-07-02 19:43:41 +0200

It used to work long ago. I already posted patches here but upstream does not 
care:
https://sourceforge.net/p/apcupsd/mailman/apcupsd-users/thread/202007312117.55508.li...@zary.sk/#msg37074883

Can they be applied to the Debian package?

After patches applied:
# apcaccess
APC  : 001,025,0603
DATE : 2023-07-02 21:50:53 +0200
HOSTNAME : router
VERSION  : 3.14.14 (31 May 2016) debian
UPSNAME  : router
CABLE: Custom Cable Smart
DRIVER   : APC Smart UPS (any)
UPSMODE  : Stand Alone
STARTTIME: 2023-07-02 21:50:47 +0200
MODEL: Smart-UPS v/s 650
STATUS   : ONLINE
MBATTCHG : 5 Percent
MINTIMEL : 3 Minutes
MAXTIME  : 0 Seconds
LASTXFER : Automatic or explicit self test
NUMXFERS : 0
TONBATT  : 0 Seconds
CUMONBATT: 0 Seconds
XOFFBATT : N/A
SELFTEST : NO
STATFLAG : 0x0508
REG1 : 0x00
REG2 : 0x00
REG3 : 0x00
FIRMWARE : 62.J.I
END APC  : 2023-07-02 21:51:21 +0200

-- 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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages apcupsd depends on:
ii  libc6  2.36-9
ii  libgcc-s1  12.2.0-14
ii  libusb-0.1-4   2:0.1.12-32
ii  libwrap0   7.6.q-32
ii  lsb-base   11.6
ii  sysvinit-utils [lsb-base]  3.06-4

Versions of packages apcupsd recommends:
pn  apcupsd-doc 
pn  s-nail | mailx  

Versions of packages apcupsd suggests:
pn  apcupsd-cgi  
ii  udev 252.6-1

-- debconf-show failed
Description: fix get_capabilities and getline
fixes SmartUPS v/s support

---
The information above should follow the Patch Tagging Guidelines, please
checkout https://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: (upstream|backport|vendor|other), (|commit:)
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: (no|not-needed|)
Applied-Upstream: , (|commit:)
Reviewed-By: 
Last-Update: 2023-07-02

--- apcupsd-3.14.14.orig/src/drivers/apcsmart/apcsmart.h
+++ apcupsd-3.14.14/src/drivers/apcsmart/apcsmart.h
@@ -46,7 +46,7 @@ public:
 
// Public for apctest
char *smart_poll(char cmd);
-   int getline(char *s, int len);
+   int getline(char *s, int len, bool no_action = false);
void writechar(char a);
 
 private:
--- apcupsd-3.14.14.orig/src/drivers/apcsmart/smart.c
+++ apcupsd-3.14.14/src/drivers/apcsmart/smart.c
@@ -150,7 +150,7 @@ char *ApcSmartUpsDriver::smart_poll(char
 
do {
   write(_ups->fd, &cmd, 1);
-  stat = getline(answer, sizeof answer);
+  stat = getline(answer, sizeof answer, cmd == APC_CMD_UPS_CAPS);
 
   /* If nothing returned, the link is probably down */
   if (*answer == 0 && stat == FAILURE) {
@@ -168,7 +168,7 @@ char *ApcSmartUpsDriver::smart_poll(char
  *
  * If s == NULL there is a much more fine-grained locking.
  */
-int ApcSmartUpsDriver::getline(char *s, int len)
+int ApcSmartUpsDriver::getline(char *s, int len, bool no_action)
 {
int i = 0;
int ending = 0;
@@ -231,7 +231,7 @@ int ApcSmartUpsDriver::getline(char *s,
  return FAILURE;
   }
 
-  switch (c) {
+  switch (no_action ? 0 : c) {
  /*
   * Here we can be called in two ways:
   * 
--- apcupsd-3.14.14.orig/src/drivers/apcsmart/smartsetup2.c
+++ apcupsd-3.14.14/src/drivers/apcsmart/smartsetup2.c
@@ -91,7 +91,7 @@ const char *ApcSmartUpsDriver::get_model
 bool ApcSmartUpsDriver::get_capabilities()
 {
char answer[1000];  /* keep this big to handle big string */
-   char caps[1000], *cmds, *p;
+   char caps[1000], *cmds;
int i;
 
write_lock(_ups);
@@ -102,15 +102,15 @@ bool ApcSmartUpsDriver::get_capabilities
   _ups->UPS_Cap[CI_UPS_CAPS] = TRUE;
 
   /* skip version */
-  for (p = caps; *p && *p != '.'; p++)
- ;
-
-  /* skip alert characters */
-  for (; *p && *p != '.'; p++)
- ;
-
-  cmds = p;/* point to commands */
-  if (

Bug#1040001: transition: r-base

[Andreas Tille]

Hi Paul,

Am Sat, Jul 01, 2023 at 05:21:16PM +0200 schrieb Paul Gevers:
> > So per upstream ("R Core" for short), this is clearly on the package
> > side. There is no ABI/API incompatibility: R offers graphics functions new
> > functionality, to use it one needs a rebuild _if a package decides to stop
> > and die on mismatch_.

I'd like to point out that "one needs a rebuild" is something else if
one installs a CRAN package manually or if we upload a Debian package.
A Debian package has to "survive" a set of tests (and here we
continuously disagree but right now in this actual case it has proven to
be necessary) and pass a migration procedure in a dependency tree of
packages which is just more complex than "just rebuild".

> > I so filed three bug reports last weekend against three such packages

... and I told you that this list of three packages was incomplete.  By
chance I had rebuild two other packages that needed the rebuild and some
autopkgtest I was running uncovered that vdiffr simply slipped through
your attention.  That's perfectly human - and since its human I'm in
favour of a technical solution which avoids such manual digging inside
the package pool.

Besides this such technical things to my experience these issues always
go with some well known pattern of "social friction" which is
demotivating for all sides.  I'd like to reduce these friction points
to a minimum if there is some technical solution.

> > requesting a simple rebuild as that is in fact all it takes. (And
> > missed one that was added.)  These were quickly rebuilt.
> 
> While this may be true, in Debian we require that such packages express this
> relation. I understand that that's what we achieve with the proposal of
> Andreas. "Just rebuilding" is often the wrong solution (in Debian) if it
> doesn't express the relation properly.

Fully ACK.
 
> > So let me know what you think.  If the release team thinks we must rebuild
> > across 1100 r-* packages (of which likely 400-500 are Architecture: any)
> > then I will of course work with you.
> 
> I recognize that at this moment we might not need it to straighten things
> out, because of all the new version uploads, but I believe it's the right
> solution for the future, as this seems to be a recurring topic.

IMHO its not a solved case.  The R pkg team is creating a list of packages
that are not up to date and a list of bugs which you can see in the second
table of [1].  This page lists

$ grep serious outdated_r-packages.txt | grep -c 4.3.1 
45

serious bugs that are all caused by the non-transition while we should
have done one.  That's pretty annoying for the people who need to do the
work (in this case basically me).

I would really welcome if we do it the right way even now, specifically
since there is a patch for bug #1040038 that implements a solution that
should help for now and in future.

Kind regards
 Andreas.

[1] 
https://salsa.debian.org/r-pkg-team/maintenance-utilities/-/blob/master/outdated_r-packages.txt

-- 
http://fam-tille.de

Bug#1040176: ITP: cppdap -- C++11 implementation of the Debug Adapter Protocol

[Timo Röhling]

Package: wnpp
Severity: wishlist
Owner: Timo Röhling 
X-Debbugs-Cc: debian-de...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: cppdap
  Version : 1.58.0a
  Upstream Author : Google LLC
* URL : https://github.com/google/cppdap
* License : Apache-2.0
  Programming Lang: C++
  Description : C++11 implementation of the Debug Adapter Protocol

cppdap is a C++11 library to implement a Debug Adapter Protocol (DAP) client
or server. It provides C++ type-safe structures for the full DAP
specification, and provides a simple way to add custom protocol messages.

cppdap is a new dependency of CMake 3.27+

The package will be maintained by Timo Röhling 
at https://salsa.debian.org/debian/cppdap


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmSh1o8ACgkQ+C8H+466
LVnkyAv+Pll6YrJ7fHA25vJfWdXPY4DmjX8G2EXxoi2o+ZYlDJbEVwG+ShL8+d7u
2r7r6aC13UmiSVxpTTFVdW4BCKX0ZTib4VtlNB02DJF1J1pBaS5iDBjtZv7YKRsB
65sZhCbl4FxR0F3+7AqcEgYlRAQnCAfKqcVilBOKgpI6ABfab46VHn3djOkvES2w
qJDqk/awqGc1ziYZfMmXTwrpry+ZekXVps+19O8LNMbdirkdWpTKs81JVMlq5ak+
k6jDrQEBJ6GyZ672biM9ejFVIdH6fv/5WpElKDqbv52xTDxgV7LjeAK7KTE4Ra3u
wJOrZrgYVfkq3dRc/CisGSmcA6Xotuy0NG8FyFsXInfm217tdj1xIBzsmzjlrNNT
hx00YqFxINiSE3Mo3bgg3jqCDsBkJhx4L3qKL5TkPk8QwA6ayyXNCjpBdPYFyy5f
AcSVpsm0peN7znMFsE0ADdjfV/lQ8VvdJ1Ko33m62/kNi/eyfag6MLPl9OjMl7F+
EbLLc+Os
=BlS+
-END PGP SIGNATURE-

Bug#1040174: nvidia-driver: Can't upgrade to nvidia-driver-525.116.04-1 on debian unstable: build fails

[Andrew]

Package: nvidia-driver
Version: 525.116.04-1
Severity: important
X-Debbugs-Cc: andrewgop...@tutanota.com

Dear Maintainer,

Today, after a long time of not checking for upgrades, I finally
upgraded all of my packages. ALl of the other packages upgraded just
fine, but my nvidia driver faild to build. I was pointed to a make.log
file, which showed an error at the end saying that "asm/orc_header.h" was not
found. I've already tried rebooting and purging all nvidia packages then
reinstalling. I also tried to find the orc_header.h, but both
/usr/include/asm-generic and /usr/include/x86_64-linux-gnu/asm do not
contain the file. 


-- Package-specific info:
uname -a:
Linux gopherbox 6.3.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.7-1 
(2023-06-12) x86_64 GNU/Linux

/proc/version:
Linux version 6.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12)

lspci 'display controller [030?]':
27:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP107 [GeForce GTX 
1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050 Ti] [3842:6251]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: nvidia

dmesg:

Device node permissions:
video:x:44:andrewgopher

Alternative 'nvidia':
nvidia - auto mode
  link best version is /usr/lib/nvidia/current
  link currently points to /usr/lib/nvidia/current
  link nvidia is /usr/lib/nvidia/nvidia
  slave nvidia--libEGL_nvidia.so.0-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libEGL_nvidia.so.0
  slave nvidia--libEGL_nvidia.so.0-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libEGL_nvidia.so.0
  slave nvidia--libGLESv1_CM_nvidia.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libGLESv1_CM_nvidia.so.1
  slave nvidia--libGLESv1_CM_nvidia.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libGLESv1_CM_nvidia.so.1
  slave nvidia--libGLESv2_nvidia.so.2-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libGLESv2_nvidia.so.2
  slave nvidia--libGLESv2_nvidia.so.2-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libGLESv2_nvidia.so.2
  slave nvidia--libGLX_nvidia.so.0-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libGLX_nvidia.so.0
  slave nvidia--libGLX_nvidia.so.0-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libGLX_nvidia.so.0
  slave nvidia--libcuda.so-i386-linux-gnu is /usr/lib/i386-linux-gnu/libcuda.so
  slave nvidia--libcuda.so-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libcuda.so
  slave nvidia--libcuda.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libcuda.so.1
  slave nvidia--libcuda.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libcuda.so.1
  slave nvidia--libglxserver_nvidia.so is /usr/lib/nvidia/libglxserver_nvidia.so
  slave nvidia--libnvcuvid.so-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libnvcuvid.so
  slave nvidia--libnvcuvid.so-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libnvcuvid.so
  slave nvidia--libnvcuvid.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libnvcuvid.so.1
  slave nvidia--libnvcuvid.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libnvcuvid.so.1
  slave nvidia--libnvidia-allocator.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libnvidia-allocator.so.1
  slave nvidia--libnvidia-allocator.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libnvidia-allocator.so.1
  slave nvidia--libnvidia-cfg.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/nvidia/libnvidia-cfg.so.1
  slave nvidia--libnvidia-encode.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libnvidia-encode.so.1
  slave nvidia--libnvidia-encode.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libnvidia-encode.so.1
  slave nvidia--libnvidia-ml.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1
  slave nvidia--libnvidia-ptxjitcompiler.so.1-i386-linux-gnu is 
/usr/lib/i386-linux-gnu/libnvidia-ptxjitcompiler.so.1
  slave nvidia--libnvidia-ptxjitcompiler.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.1
  slave nvidia--libvdpau_nvidia.so.1-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.1
  slave nvidia--nv-control-dpy is /usr/bin/nv-control-dpy
  slave nvidia--nvidia-application-profiles-key-documentation is 
/usr/share/nvidia/nvidia-application-profiles-key-documentation
  slave nvidia--nvidia-blacklists-nouveau.conf is 
/etc/nvidia/nvidia-blacklists-nouveau.conf
  slave nvidia--nvidia-bug-report.sh is /usr/lib/nvidia/nvidia-bug-report.sh
  slave nvidia--nvidia-debugdump is /usr/bin/nvidia-debugdump
  slave nvidia--nvidia-drm-outputclass.conf is 
/etc/nvidia/nvidia-drm-outputclass.conf
  slave nvidia--nvidia-drm_gbm.so-x86_64-linux-gnu is 
/usr/lib/x86_64-linux-gnu/gbm/nvidia-drm_gbm.so
  slave nvidia--nvidia-load.conf is /etc/nvidia/nvidia-load.conf
  slave nvidia--nvidia-modprobe.conf

Bug#1040173: RM: yowsup -- ROM; RC-buggy; abandoned upstream

[Josue Ortega]

Package: ftp.debian.org
Control: affects -1 + src:yowsup
User: ftp.debian@packages.debian.org
Usertags: remove

This package has been abandoned by upstream and will not longer work with
Python >= 3.12 [0]. In order to work yowsup must consume the Whatsapp Web API
that is constantly changing making yowsup hard to be maintained [1][2].
This package wasn´t included in the Bookworm release.


[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040077
[1]: https://github.com/tgalal/yowsup/issues/3182
[2]: https://github.com/tgalal/yowsup/issues/3172


---
Josue Ortega
«Happy Hacking»
http://josueortega.org

signature.asc
Description: PGP signature

Bug#1039578: libnfs: Please update to version 5.0.2

[Thomas Uhle]

On Sun, 2 Jul 2023, Bálint Réczey wrote:


Hi,

[...]

I handed over the package maintenance ~1 year ago [1], but there has
been no upload since then. To make it official I've uploaded 5.0.2 to
experimental.

Cheers,
Balint

[1]  https://salsa.debian.org/debian/libnfs/-/merge_requests/1




Hello Balint,

thank you for your effort!

Cheers,

Thomas

Bug#1039983: cups: CMYK capable printer does not print in colour

[Kerstin Hoef-Emden]

Hi Brian,

the lpadmin command did work.

Regards,

Kerstin

Am 02.07.23 um 13:06 schrieb Brian Potkin:

tags 1039983 upstream
retitle 1039983 CMYK capable printer does not print in colour
thanks



On Fri 30 Jun 2023 at 17:56:08 +0200, Kerstin Hoef-Emden wrote:


Package: cups
Version: 2.4.2-3
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
Upgrade from bullseye to bookworm

* What exactly did you do (or not do) that was effective (or
  ineffective)?
First of all, the printer drivers for my printer (Kyocera FS-C5250dn) were not
anymore available in the printers list. The original Kyocera PPD files were
still present in the file system. I chose them by browsing the file system.
Although the printer was now identified as capable of doing CMYK and it was set
to color in the cups browser interface. I also tried to change the setting in
printer.conf a) by hand to printer-color-mode CMYK and I tried the command
lpoptions -p Kyocera -o printer-colormode=CMYK.

* What was the outcome of this action?
It did not work, the printer still prints only Black & White and I am not able
to change the setting in printer.conf.

* What outcome did you expect instead?

For sure I want my color printer to print color again.


THank you for your report,  Kerstin. Your issue sounds like the on at

   https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1971242

Does the lpadmin workaround do anything for you?

Regards,

Brian.

Bug#1040172: mailman3: manage.py migrate not run on upgrade

[Wesley Hertlein]

Package: mailman3
Version: 3.3.8-1
Severity: normal

Dear Maintainer,

I ran into a problem on upgrading an installation of mailman3 during
a Debian system update from bullseye to bookworm.

After the upgrade, the default/installed cron jobs at the hour level
started throwing errors:

[ -f /usr/bin/django-admin ] && flock -n /var/run/mailman3-web/cron.hourly 
/usr/share/mailman3-web/manage.py runjobs hourly

[ERROR/MainProcess] Failed indexing 1 - 1 (retry 5/5): (1054, "Unknown column 
'hyperkitty_mailinglist.archive_rendering_mode' in 'field list'") (pid 2307): 
(1054, "Unknown column 'hyperkitty_mailinglist.archive_rendering_mode' in 
'field list'")
Traceback (most recent call last):
  File 
"/usr/lib/python3/dist-packages/django/db/models/fields/related_descriptors.py",
 line 173, in __get__
rel_obj = self.field.get_cached_value(instance)
  ^
  File "/usr/lib/python3/dist-packages/django/db/models/fields/mixins.py", line 
15, in get_cached_value
return instance._state.fields_cache[cache_name]
   
KeyError: 'mailinglist'

I got a similar error in the logs when I tried to use the web UI to
poke around the hyperkitty settings.  After some random websearches I
took a guess and ran:

# cd /usr/share/mailman3-web
# python3 manage.py migrate
Operations to perform:
  Apply all migrations: account, admin, auth, contenttypes, django_mailman3, 
django_q, hyperkitty, postorius, sessions, sites, socialaccount
Running migrations:
  Applying auth.0012_alter_user_first_name_max_length... OK
  Applying django_q.0010_auto_20200610_0856... OK
  Applying django_q.0011_auto_20200628_1055... OK
  Applying django_q.0012_auto_20200702_1608... OK
  Applying django_q.0013_task_attempt_count... OK
  Applying django_q.0014_schedule_cluster... OK
  Applying hyperkitty.0022_mailinglist_archive_rendering_mode... OK
  Applying hyperkitty.0023_alter_mailinglist_name... OK

Running this resolved the errors.  It's possible the problem here was on
my end (as noted by `mailman3/dbconfig-install: false` in this report) -
the dpkg configuration question sounded like I should choose 'no' if I
had previously set up a database, which of course coming from a working
bullseye installation I had.

Ideally this would have run as part of the package upgrade.

I also got a number of warnings that I was able to clean up easily
enough, this was the only hard error that appeared to break
functionality.  Let me know if there is interest and I can file bugs for
those.  It's possible/probable that they've been dealt with upstream -
this felt like the only Debian specific issue.


-- 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)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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)
LSM: AppArmor: enabled

Versions of packages mailman3 depends on:
ii  cron 3.0pl1-162
ii  dbconfig-mysql   2.0.24
ii  debconf [debconf-2.0]1.5.82
ii  init-system-helpers  1.65.2
ii  logrotate3.21.0-1
ii  python3  3.11.2-1+b1
ii  python3-aiosmtpd 1.4.3-1.1
ii  python3-alembic  1.8.1-2
ii  python3-authheaders  0.15.2-1
ii  python3-authres  1.2.0-3
ii  python3-click8.1.3-2
ii  python3-dateutil 2.8.2-2
ii  python3-dnspython2.3.0-1
ii  python3-falcon   3.1.1-1+b1
ii  python3-flufl.bounce 4.0-3
ii  python3-flufl.i18n   3.0.1-3
ii  python3-flufl.lock   5.0.1-4
ii  python3-gunicorn 20.1.0-6
ii  python3-importlib-resources  5.1.2-2
ii  python3-lazr.config  2.2.3-3
ii  python3-passlib  1.7.4-3
ii  python3-psycopg2 2.9.5-1+b1
ii  python3-public   2.3-4
ii  python3-pymysql  1.0.2-2
ii  python3-requests 2.28.1+dfsg-1
ii  python3-sqlalchemy   1.4.46+ds1-1
ii  python3-zope.component   5.1.0-1
ii  python3-zope.configuration   4.4.1-1
ii  python3-zope.event   4.4-3
ii  python3-zope.interface   5.5.2-1+b1
ii  ucf  3.0043+nmu1

Versions of packages mailman3 recommends:
ii  postfix [mail-transport-agent]  3.7.5-2

Versions of packages mailman3 suggests:
pn  anacron
ii  default-mysql-server   1.1.0
ii  lynx [www-browser] 2.9.0dev.12-1
ii  mailman3-doc   3.3.8-1
ii  mariadb-server [virtual-mysql-server]  1:10.11.3-1

-- debconf information:
  mailman3/database-type: mysql
  mailman3/upgrade-error: abort
  mailman3/mysql/authplugin: default
  mailman3/mysql/met

Bug#1039889: recommends old ffmpeg libs

[Phillip Berndt]

Ok. Made that change, and confirmed that the package still builds and
lintian is happy. We're good to go.

I noticed there's some build warnings emitted by the dependencies by
now. They don't block the build yet, so I'll fix those upstream
separately.

Bug#1040171: noweb: Help to update to version 2.13

[Mechtilde Stehmann]

Package: noweb
Version: 2.12-4
Severity: wishlist
X-Debbugs-Cc: mechti...@debian.org

Hello Hubert,

I try to build version 2.13rc3 of noweb to test it in my environment and then
want to update to version 2.13.

I need help to apply the patches to the new version.

@Hubert can you help me to apply them?

Regards

Mechtilde


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (400, 'testing'), (300, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages noweb depends on:
ii  gawk1:5.2.1-2
ii  iconx   9.4.3-7
ii  libc6   2.36-9
ii  tex-common  6.18

Versions of packages noweb recommends:
ii  texlive  2022.20230122-3

noweb suggests no packages.

-- no debconf information

Bug#1040167: (buildd chroot bug) Re: Bug#1040167: openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian

[Thorsten Glaser]

Dixi quod…

>Indeed. Weird.
>
>Thanks for reporting, I’ll have two or three looks at it… fixing that
>is going to be… fun. Not.

OK so first analysis is showing the cause of the problem:

• the buildd chroots for sid/unstable do not identify themselves as
  sid/unstable but instead as trixie/testing, which is a bug onto
  itself¹

• the source package checks the buildd release codename and does
  things based on that; normally, the tests are written in a manner
  that they fall through to the latest (i.e. they test for known
  names of older releases for the old behaviour, and use the new
  behaviour if none of the old release names is used); the code to
  handle the long ago libjpeg62→libjpeg8→libjpeg62-turbo transition
  however was written the other way round, which causes trouble if
  the new release is unknown

I’ll fix that in the source, but first I need to get the situation
fixed as openjdk-8 build-depends on itself, which will be bad if
it’s not installable.

I’m going to change all uses of the distro codename to fall safely,
however if the buildd chroot bug could be fixed, I’d be glad.

bye,
//mirabilos

① sid buildd chroots should save the following content…
PRETTY_NAME="Debian GNU/Linux sid"
NAME="Debian GNU/Linux"
ID=debian
HOME_URL="https://www.debian.org/";
SUPPORT_URL="https://www.debian.org/support";
BUG_REPORT_URL="https://bugs.debian.org/";
VERSION_ID=unstable
VERSION_CODENAME=sid
  … as /usr/lib/os-release.sid (in the chroot) and run…
# dpkg-divert --rename --divert /usr/lib/os-release.dpkg-dist \
  --add /usr/lib/os-release
# ln -sfT os-release.sid /usr/lib/os-release
  … in the chroot, so the reported lsb_release is correct. They used
  to have this in /etc/lsb-release, but the lsb-release program no
  longer uses that.
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg


/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against  Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!

Bug#1040167: openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian

[Thorsten Glaser]

On Sun, 2 Jul 2023, Fab Stz wrote:

>Updating from 8u372-ga-1 which was the previous version in unstable is not
>possible because openjdk-8-jre-headless_8e382~b04-1 depends on libjpeg8

WTF‽

*checks*

Indeed. Weird.

Thanks for reporting, I’ll have two or three looks at it… fixing that
is going to be… fun. Not.

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg


/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against  Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!

Bug#1040169: smplayer: Smplayer hangs when starting video

[Edward C. Jones]

Package: smplayer
Version: 22.7.0~ds0-1
Severity: important
X-Debbugs-Cc: edcjo...@edcjones.abcd.net

Dear Maintainer,

Smplayer hangs whenever I try to start a video.  When I close the window
smplayer is in, I sometimes get an error message and a log.  Here is a log:

=
/usr/bin/mpv --no-quiet --terminal --no-msg-color
/ --input-ipc-server=/tmp/smplayer-mpv-1ff50
/ --msg-level=ffmpeg/demuxer=error --video-rotate=no --no-config --no-fs
/ --hwdec=no --sub-auto=fuzzy --vo=x11, --no-input-default-bindings
/ --input-vo-keyboard=no --no-input-cursor --cursor-autohide=no
/ --no-keepaspect --wid=8 --monitorpixelaspect=1 --osd-level=1 --osd-scale=1
/ --osd-bar-align-y=0.6 --sub-ass --embeddedfonts --sub-ass-line-spacing=0
/ --sub-scale=1 --sub-font=Arial --sub-color=#
/ --sub-shadow-color=#ff00 --sub-border-

color=#ff00 --sub-border-size=0.75 --sub-shadow-offset=2.5
--sub-font-size=50 --sub-bold=no --sub-italic=no --sub-margin-y=8
--sub-margin-x=20 --sub-codepage=ISO-8859-1 --vid=1 --sub-pos=100
--volume=55 --cache=auto --screenshot-template=cap_%F_%p_%02n
--screenshot-format=jpg
--screenshot-directory=/home/edcjones/Pictures/smplayer_screenshots
--audio-pitch-correction=yes --volume-max=110
--term-playing-msg=MPV_VERSION=${=mpv-version:}

INFO_VIDEO_WIDTH=${=width}
INFO_VIDEO_HEIGHT=${=height}
INFO_VIDEO_ASPECT=${=video-params/aspect}
INFO_VIDEO_FPS=${=container-fps:${=fps}}
INFO_VIDEO_FORMAT=${=video-format}
INFO_VIDEO_CODEC=${=video-codec}
INFO_DEMUX_ROTATION=${=track-list/0/demux-rotation}
INFO_AUDIO_FORMAT=${=audio-codec-name}
INFO_AUDIO_CODEC=${=audio-codec}
INFO_AUDIO_RATE=${=audio-params/samplerate}
INFO_AUDIO_NCH=${=audio-params/channel-count}
INFO_LENGTH=${=duration:${=length}}
INFO_DEMUXER=${=current-demuxer:${=demuxer}}
INFO_SEEKABLE=${=seekable}
INFO_TITLES=${=disc-titles}
INFO_CHAPTERS=${=chapters}
INFO_TRACKS_COUNT=${=track-list/count}
METADATA_TITLE=${metadata/by-key/title:}
METADATA_ARTIST=${metadata/by-key/artist:}
METADATA_ALBUM=${metadata/by-key/album:}
METADATA_GENRE=${metadata/by-key/genre:}
METADATA_DATE=${metadata/by-key/date:}
METADATA_TRACK=${metadata/by-key/track:}
METADATA_COPYRIGHT=${metadata/by-key/copyright:}
INFO_MEDIA_TITLE=${=media-title:}
INFO_STREAM_PATH=${stream-path}
 --audio-client-name=SMPlayer --term-status-msg=STATUS: ${=time-pos} /
 ${=duration:${=length:0}} P: ${=pause} B: ${=paused-for-cache} I:
 ${=core-idle} VB: ${=video-bitrate:0} AB: ${=audio-bitrate:0}
 /data/pics/videos/trever/chris vs mikey.flv

(+) Video --vid=1 (h264 854x480 29.955fps)
 (+) Audio --aid=1 (aac 2ch 44100Hz)
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 12
[vo/x11/x11] Error code: 9, request code: e, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 13
[vo/x11/x11] Error code: 3, request code: 28, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 16
[vo/x11/x11] Error code: 3, request code: 2, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 8, serial: 18
[vo/x11/x11] Error code: 3, request code: 1, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 1b
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 1e
[vo/x11/x11] Error code: 3, request code: 91, minor code: 3
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 20
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 21
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11] Warning: this legacy VO has bad performance. Consider fixing your
 graphics drivers, or not forcing the x11 VO.
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 23
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadWindow (invalid Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 24
[vo/x11/x11] Error code: 3, request code: 12, minor code: 0
[vo/x11/x11] X11 error: BadDrawable (invalid Pixmap or Window parameter)
[vo/x11/x11] Type: 0, display: 0x7f7bd80456b0, resourceid: 1a2, serial: 25
[vo/x11/x11] Error code: 9, request code: 37, minor code: 0
[W][14041.464775] pw.conf  | [  conf.c:  939 try_load_conf()]
   can'

Bug#1038445: When in full-screen mode mpv gets minimized after switching Xfce workspaces

[splashed_overbuilt840]

Today I've discovered that potentially this behavior could be mitigated or even 
fixed by enabling the "Activate focus stealing prevention" option in the Focus 
tab of the Xfce "Window Manager Tweaks" settings section.

I'll test this option for several days to see whether the issue is still 
reproducible. If not, the bug could be closed.

Regards,
Yura

Bug#1039050: same bug here

[Joey Hess]

(com.github.johnfactotum.Foliate:203690): Gjs-WARNING **: 13:14:57.747: 
Unhandled promise rejection. To suppress this warning, add an error handler to 
your promise chain with .catch() or a try-catch block around your await 
expression. Stack trace of the failed promise:
  main@resource:///com/github/johnfactotum/Foliate/js/main.js:478:24
  run@resource:///org/gnome/gjs/modules/script/package.js:206:19
  @/usr/bin/foliate:9:17

Segmentation fault

Foliate had been stable up until recently. I'm tracking unstable so perhaps
something changed that broke it.

Note that the upstream's .deb of foliate is also crashing in the same way.

-- 
see shy jo


signature.asc
Description: PGP signature

Bug#1039907: apt-cacher-cleanup.pl clears/removes all cached packages on trixie

[Niko Tyni]

On Sun, Jul 02, 2023 at 03:40:45PM +0100, Mark Hindley wrote:

> Installing libio-compress-lzma-perl pulls in libio-compress-perl and normal
> apt-cacher decompression is restored.
> 
> I suppose the apt-cacher Recommends will need to become a Depends.

Hi, glad you found a working solution. Thanks to Gregor for investigating.

Like Gregor I'm not aware of recent changes around these things. Please
provide more information if you still think it's a regression on the
perl side.
-- 
Niko Tyni   nt...@debian.org

Bug#1039050: Seeing the same bug

[Fiona Klute]

I'm seeing the same behavior from Foliate, though the exact message from
the crash varies. *In addition to* the one quoted above I've also seen:


**
Gjs:ERROR:../gi/function.cpp:1035:bool Gjs::Function::invoke(JSContext*, const 
JS::CallArgs&, JS::HandleObject, GIArgument*): assertion failed (ffi_arg_pos == 
ffi_argc): (2 == 21960)
Bail out! Gjs:ERROR:../gi/function.cpp:1035:bool Gjs::Function::invoke(JSContext*, 
const JS::CallArgs&, JS::HandleObject, GIArgument*): assertion failed 
(ffi_arg_pos == ffi_argc): (2 == 21960)
Abgebrochen


(Abgebrochen -> Aborted)

And a simple


Speicherzugriffsfehler


(Segmentation fault)


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE
not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages foliate depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-webkit2-4.0   2.40.3-2
ii  gjs  1.74.3-1
ii  python3  3.11.4-1

Versions of packages foliate recommends:
ii  gnome-epub-thumbnailer  1.7-3

foliate suggests no packages.

-- no debconf information

Bug#1040167: openjdk-8-jre-headless: version 8u382~b04-1 depends on libjpeg8 which is not in Debian

[Fab Stz]

Package: openjdk-8-jre-headless
Version: 8u382~b04-1
Severity: important

Dear Maintainer,

Updating from 8u372-ga-1 which was the previous version in unstable is not
possible because openjdk-8-jre-headless_8e382~b04-1 depends on libjpeg8

However libjpeg8 is not to be found in Debian

Expected behaviour: correct dependencies or adding the missing libjpeg8 to
Debian?



-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (991, 'stable-security'), (991, 'stable'), (990, 'proposed-
updates'), (390, 'oldstable-security'), (390, 'oldstable'), (389, 'oldstable-
updates'), (380, 'oldoldstable'), (379, 'oldoldstable-updates'), (370, 
'oldoldstable'), (95, 'testing'), (94, 'unstable'), (93, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages openjdk-8-jre-headless depends on:
ii  ca-certificates-java  20230103
ii  java-common   0.74
ii  libc6 2.36-9
ii  libcups2  2.4.2-3
ii  libfontconfig12.14.1-4
ii  libfreetype6  2.12.1+dfsg-5
ii  libgcc-s1 12.2.0-14
ii  libjpeg62-turbo   1:2.1.5-2
ii  liblcms2-22.14-2
ii  libnss3   2:3.87.1-1
ii  libpcsclite1  1.9.9-2
ii  libstdc++612.2.0-14
ii  libx11-6  2:1.8.4-2+deb12u1
ii  libxext6  2:1.3.4-1+b1
ii  libxi62:1.8-1+b1
ii  libxrender1   1:0.9.10-1.1
ii  libxtst6  2:1.2.3-1.1
ii  util-linux2.38.1-5+b1
ii  zlib1g1:1.2.13.dfsg-1

openjdk-8-jre-headless recommends no packages.

Versions of packages openjdk-8-jre-headless suggests:
ii  fonts-dejavu-extra2.37-6
pn  fonts-indic   
pn  fonts-ipafont-gothic  
pn  fonts-ipafont-mincho  
pn  fonts-wqy-microhei
pn  fonts-wqy-zenhei  
ii  libnss-mdns   0.15.1-3

-- no debconf information

Bug#1040166: mirror submission for packages.debian.rooty.fr

[Tristan Champomier]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: packages.debian.rooty.fr
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 
kfreebsd-amd64 kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Maintainer: Tristan Champomier 
Country: FR France




Trace Url: http://packages.debian.rooty.fr/debian/project/trace/
Trace Url: 
http://packages.debian.rooty.fr/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://packages.debian.rooty.fr/debian/project/trace/packages.debian.rooty.fr

Bug#1040165: pacemaker: Migration regression after upgrading bullseye to bookworm

[Ferenc Wágner]

Package: pacemaker
Version: 2.1.5-1
Severity: important
Tags: patch

As reported on the mailing list by Florent Carli 
https://alioth-lists.debian.net/pipermail/debian-ha-maintainers/2023-June/008761.html:

I encountered a regression with pacemaker when upgrading from debian
bullseye to bookworm. First I contacted pacemaker maintainers and I
explained the problematic behavior:
https://bugs.clusterlabs.org/show_bug.cgi?id=5521

But then I tried with pacemaker 2.1.6 (compiled from source) and I could
not reproduce.

Pacemaker maintainers confirmed that: "We did a bunch of other
refactoring related to migrations (including partial migrations) in
preparation for that fix:
https://github.com/ClusterLabs/pacemaker/commits/main?after=44647f62c012f4305bf5d2e03cfde89356d831bd+34&branch=main&path%5B%5D=lib&path%5B%5D=pengine&path%5B%5D=unpack.c&qualified_name=refs%2Fheads%2Fmain";

So I'm now turning to you, hoping you will consider upgrading pacemaker
package in debian stable to 2.1.6.

As added later by Yoann CONGAL :

>From one of the pacemaker authors the precise fix seems to be
https://github.com/ClusterLabs/pacemaker/commit/ad9fd9548f02a38885fa36765af9742a5a88576e
But this is based on a bunch of refactoring so this patch does not
apply on the 2.1.5 debian branch :(

Reproducing this bug should be simple :
* 3 node cluster (node1, node2, node3)
* a VirtualDomain resource (debian1)
* debian1 has a location constraint on node2
* Gracefully shutdown pacemaker service on node2 (debian1 moves away
e.g. to node1)
* Restart pacemaker service on node2

Here, debian1 should cleanly migrate back to node2 but this migration fails :
* There is no migrate_to task generated in node1
* migrate_from task on node2 timeouts
* debian1 get restarted by a "forced recovery"

Bug#1040163: xqilla: embeds yajl library

[Tobias Frost]

Source: xqilla
Severity: important

Dear Maintainer,

Your package embed a copy of yajl.


Please you:
- compile against the packaged yajl package
- remove by repacking or d/clean the embded code copy in order to avoid 
accidental
  compilation of the embed code copy

Thanks
--
tobi

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'oldstable-security'), (500, 
'oldoldstable'), (500, 'unstable'), (500, 'testing'), (500, 'oldstable'), (100, 
'bullseye-fasttrack'), (100, 'bullseye-backports-staging'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#1002996: [Bug #1002996] ITP: python-orjson -- fast, correct JSON library for Python

[Antonio Valentino]

Dear Agathe,
I'm very interested in this python-orjson it is a dependency of some new 
python packages that I would like to include in debian-gis.


Could I kindly ask what is the status of the packaging and if you have 
an idea about when this package could go in the new queue?


Please let me know if there is anything that I can do to support you.
Is there a public repository for the debian package?


kind regards
--
Antonio Valentino

Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)

[Antonio]

What you read is the kernel liquorix version of the default (first try).

I also installed the Debian kernel and booted with that version as request
and retest (second try): same problem occurs.




Il dom 2 lug 2023, 18:40 Bastian Blank  ha scritto:

> Hi
>
> On Sun, Jul 02, 2023 at 03:12:21PM +0200, antonio wrote:
> > Kernel: Linux 6.3.11-2-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
>
> This is no Debian.  You have to verify that on Debian.
>
> Bastian
>
> --
> Yes, it is written.  Good shall always destroy evil.
> -- Sirah the Yang, "The Omega Glory", stardate unknown
>

Bug#1040162: RM: python-sabyenc -- ROM; superseeded by sabctools; unused

[Jeroen Ploemen]

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

Superseeded by sabctools from the same upstream. The upload of
sabnzbdplus/4.0.2-1 removed the sole reverse dependency.

Thanks


pgp3O94tsKzuY.pgp
Description: OpenPGP digital signature

Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)

[Bastian Blank]

Hi

On Sun, Jul 02, 2023 at 03:12:21PM +0200, antonio wrote:
> Kernel: Linux 6.3.11-2-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)

This is no Debian.  You have to verify that on Debian.

Bastian

-- 
Yes, it is written.  Good shall always destroy evil.
-- Sirah the Yang, "The Omega Glory", stardate unknown

Bug#1040051: prompt-toolkit breaks pymodbus autopkgtest: output on stderr: Task was destroyed but it is pending!

[Daniel Baumann]

notfound 1040051 prompt-toolkit/3.0.38-2
retitle 1040051 autopkgtest err "Task was destroyed but it is pending!"
thanks

Hi,

thanks for reporting this. however, I can't reproduce it - I don't think
the bug is caused by prompt-toolkit but by anthing other that is
different between testing and unstable. Also the error message doesn't
sound like prompt-toolkit is involved here at all.

Regards,
Daniel

Bug#1040157: ITP: golang-github-azuread-microsoft-authentication-library-for-go -- Microsoft Authentication Library (MSAL) for Go

[Shengjing Zhu]

Control: merge -1 1039471

On Sun, Jul 2, 2023 at 11:57 PM Félix Sipma  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Félix Sipma 
>
> * Package name: 
> golang-github-azuread-microsoft-authentication-library-for-go
>   Version : 0.6.0-1
>   Upstream Author : Microsoft
> * URL : 
> https://github.com/AzureAD/microsoft-authentication-library-for-go
> * License : Expat
>   Programming Lang: Go
>   Description : Microsoft Authentication Library (MSAL) library for Go

This has already been packaged, and it's waiting in NEW.
https://ftp-master.debian.org/new/golang-github-azuread-microsoft-authentication-library-for-go_1.0.0-1.html

-- 
Shengjing Zhu

Bug#1040157: Acknowledgement (ITP: golang-github-azuread-microsoft-authentication-library-for-go -- Microsoft Authentication Library (MSAL) for Go)

[Félix Sipma]

Woops, I just realized this is already in the new queue. (ITP - 
#1039471) Sorry for the noise.


On 2023-07-02 15:57+, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

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

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
debian-de...@lists.debian.org, debian...@lists.debian.org
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
w...@debian.org

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

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


--
Félix


signature.asc
Description: PGP signature

Bug#1040158: texlive-latex-extra: tex4ebook with mathml prints \lim, limsup etc. in italics

[Karl Grill]

Package: texlive-latex-extra
Version: 2022.20230122-4
Severity: important
X-Debbugs-Cc: kgr...@chello.at

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
 Trying to convert Latex source to Epub 3 with MathML
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Run "tex4ebook -f epub3 test.tex mathml"
  
   * What was the outcome of this action?
 The resulting test.epub gives a "Math Input Error" when viewed in Calibre,
 test.xhtml renders in firefox, but the "lim sup" is rendered in italics 
instead of normal print.

 Doing the same on a machine running oldstable seems to work correctly.
   * What outcome did you expect instead?
 A line of math that renders correctly in both Calibre and firefox



-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file

\documentclass{report}
\begin{document}
\[ \mu(\limsup_{n} A_{n})\le \limsup_{n} \mu(A_{n})\]
\end{document}


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 3370 Jun 11 17:24 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 12  2022 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Apr  9 11:54 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Apr  9 11:54 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Oct 30  2022 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Apr  9 11:54 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Apr  9 11:54 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5130 Jun 11 17:23 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep  4  2021 mktex.cnf
-rw-r--r-- 1 root root 475 Oct 30  2022 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 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

Versions of packages texlive-latex-extra depends on:
ii  libcommons-logging-java1.2-3
ii  libpdfbox-java 1:1.8.16-2
ii  preview-latex-style12.2-1
ii  python33.11.2-1+b1
ii  tex-common 6.18
ii  texlive-base   2022.20230122-3
ii  texlive-binaries   2022.20220321.62855-5.1
ii  texlive-latex-recommended  2022.20230122-3
ii  texlive-pictures   2022.20230122-3

Versions of packages texlive-latex-extra recommends:
ii  default-jre 2:1.17-74
ii  libspreadsheet-parseexcel-perl  0.6500-3
ii  texlive-fonts-recommended   2022.20230122-3
ii  texlive-plain-generic   2022.20230122-4

Versions of packages texlive-latex-extra suggests:
ii  icc-

Bug#1040157: ITP: golang-github-azuread-microsoft-authentication-library-for-go -- Microsoft Authentication Library (MSAL) for Go

[Félix Sipma]

Package: wnpp
Severity: wishlist
Owner: Félix Sipma 

* Package name: 
golang-github-azuread-microsoft-authentication-library-for-go
  Version : 0.6.0-1
  Upstream Author : Microsoft
* URL : 
https://github.com/AzureAD/microsoft-authentication-library-for-go
* License : Expat
  Programming Lang: Go
  Description : Microsoft Authentication Library (MSAL) library for Go
 The Microsoft Authentication Library (MSAL) for Go is part of the
 Microsoft identity platform for developers (https://aka.ms/aaddevv2)
 (formerly named Azure AD) v2.0. It allows you to sign in users or apps
 with Microsoft identities (Azure AD
 (https://azure.microsoft.com/services/active-directory/) and Microsoft
 Accounts (https://account.microsoft.com)) and obtain tokens to call
 Microsoft APIs such as Microsoft Graph (https://graph.microsoft.io/) or
 your own APIs registered with the Microsoft identity platform. It is
 built using industry standard OAuth2 and OpenID Connect protocols.

Newer restic depends on a newer golang-github-azure-azure-sdk-for-go, 
which depends on this package.

-- 
Félix


signature.asc
Description: PGP signature

Bug#1040156: ITP: golang-github-microsoft-applicationinsights-go -- Microsoft Application Insights SDK for Go

[Félix Sipma]

Package: wnpp
Severity: wishlist
Owner: Félix Sipma 

* Package name: golang-github-microsoft-applicationinsights-go
  Version : 0.4.4-1
  Upstream Author : Microsoft
* URL : https://github.com/microsoft/ApplicationInsights-Go
* License : Expat
  Programming Lang: Go
  Description : Microsoft Application Insights SDK for Go

 This project provides a Go SDK for Application Insights. Application
 Insights (http://azure.microsoft.com/en-us/services/application-insights/)
 is a service that allows developers to keep their applications
 available, performant, and successful.  This go package will allow you
 to send telemetry of various kinds (event, metric, trace) to the
 Application Insights service where they can be visualized in the Azure
 Portal.

Newer restic depends on a newer golang-github-azure-azure-sdk-for-go, 
which depends on this package.

-- 
Félix


signature.asc
Description: PGP signature

Bug#1040155: flowblade: Indirectly depends on SDL 1.2

[Simon McVittie]

Source: flowblade
Tags: trixie sid
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: libsdl1.2
Control: block 1038506 by -1

This package depends on the SDL 1.2 plugin for libmlt7. SDL 1.2 has
been superseded by SDL 2 and is unmaintained upstream.

If possible, please port this package to SDL 2. There is already a SDL 1.2
plugin in libmlt7.

If it is not possible to port to SDL 2, please test the package with
libsdl1.2-compat-shim (preferably version 1.2.64 or later), and leave
this bug open to track the package as still using SDL 1.2 APIs.

libsdl1.2-compat-shim is a compatibility layer that provides the SDL 1.2
API/ABI by using SDL 2: it has already replaced the "classic" SDL 1.2
library in some other distributions like Fedora and Arch, and my intention
is to do the same in Debian during the trixie release cycle.

The interesting scenarios to test with libsdl1.2-compat-shim are:

1. Install libsdl1.2-compat-shim and run the program in an X11 environment,
   such as "GNOME on Xorg" or XFCE.
   ($XDG_RUNTIME_DIR/wayland-* should not exist)
2. Install libsdl1.2-compat-shim and run the program in a Wayland
   environment such as GNOME's default mode, using Xwayland.
   ($XDG_RUNTIME_DIR/wayland-* should exist)
3. Install libsdl1.2-compat-shim and run the program in a Wayland
   environment, but this time with environment variable
   SDL_VIDEODRIVER=wayland so that it uses the native Wayland interface
   (this is not currently the default for SDL 2).
4. Install libsdl1.2-compat-dev and recompile the package.

If any of those fail, please report it as a bug in the
libsdl1.2-compat-shim or libsdl1.2-compat-dev package as appropriate,
with "affects" pointing to the program that is affected.

Thanks,
smcv

-- 
This bug report is part of a mass-bug-filing:

Bug#1040152: ITP: golang-cloudfoundry-clock -- time provider & rich fake for Go

[Félix Sipma]

Package: wnpp
Severity: wishlist
Owner: Félix Sipma 

* Package name: golang-cloudfoundry-clock
  Version : 1.1.0-1
  Upstream Author : Cloud Foundry
* URL : https://github.com/cloudfoundry/clock
* License : Apache-2.0
  Programming Lang: Go
  Description : time provider & rich fake for Go
 Provides a Clock interface, useful for injecting time dependencies in
 tests.

Newer restic depends on a newer golang-github-azure-azure-sdk-for-go, 
which depends on this package.

-- 
Félix


signature.asc
Description: PGP signature

Bug#1028137: nextpnr: Support for more FPGA architectures (esp. ECP5)

[Jonathan Neuschäfer]

On Sat, Jun 24, 2023 at 10:28:07PM +0200, Daniel Gröber wrote:
> Hi Jonathan,

Hi Daniel.

> Thanks for the detailed review and testing!
>
> On Sat, Jun 24, 2023 at 12:35:12PM +0200, Jonathan Neuschäfer wrote:
> > [ Dropping the Debian mailing lists / bugtracker for now ]
>
> No need, I belive reviews should be public :) I've bounced your mail back
> to BTS/pkg-electronics.
>
> > Some notes:
> >
> > prjtrellis:
> >
> > - I tried to build it from source (using the tarballs, with 
> > dpkg-buildpackage),
> >   but it failed because it can't find version.cpp. After a dirty hack to 
> > ensure
> >   that version.cpp is present and usable, and unpacking the orig-database
> >   tarball to the right location, the package builds for me.
>
> Did you build with git/gbp or using the dsc? I see that the build system
> tries to extract the version using git commands. However I always test with
> sbuild so my build environment should also have been a plain unpacked dsc
> and not a git repo. Strange.

I didn't use Git (except separately, as a reference for comparison). I
extracted the orig and debian tarballs manually and then used
dpkg-buildpackage. Perhaps not the recommended method :)

> AFAICT I can define CURRENT_GIT_VERSION from d/rules and that should take
> care of it.

Sounds good.

>
> > apycula:
> >
> > - I think the source package name should rather be apicula (with 'i',
> >   not 'y'), which matches the upstream repo and readme.md. Apycula is
> >   the python binding, AFAIUI.
>
> NACK, what I'm packaging here is the a-py-cula pipy.org package which is
> the main output of project a-pi-cula.

Ah ok, that probably also explains the provenance of the pickle files.

> > - The debian orig tarball contains a few GW1N*.pickle files (in the
> >   apycula subdirectory), that don't appear in the upstream git repo.
> >   They seem to be generated, and are later used in the nextpnr build, but
> >   it's unclear to me where they come from, where the source is.
>
> Indeed I agree it's a bit dodgy and probably warrants an explaination in
> d/README.source. So what project apicula did is write fuzzers to
> map/document what bits in the FPGA bitstream perform what function.
>
> They do this by running the proprietary FPGA-vendor toolchain using their
> automated fuzzing tools. The pickle files encompass the output of these
> tools and essentially provide a map of what logical function is where in
> the hardware.

Right, indeed.

Other toolchains have the same problem, but solve it differently in
Debian, for example with the prjtrellis_1.4.orig-database.tar.gz source
tarball.

I would expect that the apycula database is also maintained in an
upstream git repo, akin to prjtrellis-db, but I haven't found one.

> The a-pi-cula source repo contains these fuzzin tools and produces as
> output the a-py-cula pipy package which is uploaded by the maintainer.
>
> I haven't consulted the sacred scriptures on the finer points yet but IMO
> the pickle files contain facts about the physical world, not computer
> code. My understanding is facts are not copyrightable in the first place so
> the usual derrivative work considerations don't apply.
>
> You can imagine I'm looking forward to ftp-master review ;)

In any case, apycula isn't the first to ship such data, as far as I
understand it.

> > nextpnr:
> >
> > - debian/upstream/metadata: Some of the authors have updated names that
> >   should be used instead of the old names. As far as I can gather:
> >- Myrtle Shah[1] (a.k.a. gatecat)
> >- Claire Xenia Wolf[2] (a.k.a. Claire Xen)
>
> This one is tricky. The license asks that the notices in the source be
> preserved, so it's not clear to me we can honor such name changes without
> explicit permission from the respective copyright holder.

Ah well, ok, that's beyond my legal expertise and I can't speak for the authors.

> > - Because I removed the GWIN*.pickle files of unknown origin, I skipped the
> >   gowin targets.
>
> Do note prjtrellis has the same layout information in the -database
> component just in a more human readable format (json). Have a look at that
> and you'll get an idea of what sort of data we're talking about here.

Yep. It's just that I didn't find the files in the upsteam Git repo that
I checked (and I didn't think to check the pypi package).

>
> > - Building multiple times in the same source directory fails, 
> > override_dh_auto_clean needs a
> >   "rm -rf debian/nextpnr-*-qt-chipdb/usr/share/nextpnr/chipdb-*.bin" or 
> > similar.
> >   Or maybe upstream "make clean" needs to be fixed.
> > - Somehow the chipdb files are installed to /usr/share/nextpnr/chipdb-*.bin
> >   directly, while nextpnr expects them in per-arch subdirectories. As a 
> > quick
> >   work-around I'm symlinked the expected subdirectories to .
> >
> >
> > After all this, I've built a simple test design for ECP5 (OrangeCrab),
> > and it worked!
>
> Excellent news!
>
> > Thanks for your work! I hope my comments help to improve it further 

Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)

[Antonio]

Debian/Sid

Operating System: Debian GNU/Linux
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.8
Kernel Version: 6.3.0-1-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 24 × 12th Gen Intel® Core™ i9-12900T
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 770 (integrated)
Manufacturer: ASUS ROG STRIX B660-I GAMING WIFI


dmesg:
[dom lug  2 17:28:34 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, 
not enough memory for the allocation
[dom lug  2 17:28:34 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, 
not enough memory for the allocation
[dom lug  2 17:28:35 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, 
not enough memory for the allocation
[dom lug  2 17:28:36 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, 
not enough memory for the allocation
[dom lug  2 17:28:37 2023] __vm_enough_memory: pid: 4398, comm: plasmashell, 
not enough memory for the allocation

kernel debian sid:
- linux-image-amd64

Linux SAT 6.3.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12) 
x86_64 GNU/Linux

Same problems



Il 02/07/23 17:16, Aurelien Jarno ha scritto:

control: notfound -1 2.36-9
control: found -1 2.37-3

Hi,

On 2023-07-02 15:12, antonio wrote:

Package: libc6
Version: 2.36-9
Severity: important
X-Debbugs-Cc: antde...@gmail.com

Dear Maintainer,
after upgrade libc6 packages:
--
libc-bin libc-dev-bin libc-devtools libc-l10n libc6 libc6:i386 libc6-dbg
libc6-dev libc6-dev-i386 libc6-dev-x32 libc6-i386 libc6-x32
--
to new version 2.37.3, I can't launch the desktop plasma applications.

With Plasma/X11:
- after clicking on the icon to start any application, the following error
appears (intercepted by journal):

kernel: __vm_enough_memory: pid: 7772, comm: plasmashell, not enough memory for
the allocation

With Plasma/Wayland:
- A msgbox returns with the word "resource error) (fork not succeeded),
impossible to allocate memory

Only Krunner works well and can launch the applications manually

Returning to the previous version 2.36-9 everything works well.

Thanks for your bug report. Unfortunately I am unable to reproduce the
issue locally. Can you please give me a few details that might help to
understand the problem:

- Which version of plasma do you use?
- Do you have any other information in dmesg when the problem happens?
- Can you please try to reproduce the issue using a debian kernel?
- As it seems to be related to display, can you please tell me which GPU
   is your computer using and which driver do you use?

Regards
Aurelien

Bug#1040149: systemd: services considered running after mainpid has exited

[Tomas Janousek]

Package: systemd
Version: 253.5-1
Severity: important
Tags: upstream
X-Debbugs-Cc: t...@nomi.cz

Since 
https://github.com/systemd/systemd-stable/commit/ae83e97a51519ca33e70d7ba142cb3ed24212825,
 
services with ExitType=main (the default) and KillMode=process (not the 
default, but used in e.g. libvirtd.service) are considered active even 
after the main process has exited.

This is clearly a bug, reported multiple times to systemd: [1], [2] that 
has since been fixed upstream [3] and many distros (Fedora, Arch, 
openSUSE, NixOS) are carrying the patch even before a systemd-stable 
release [4] because it's quite a serious bug that breaks libvirtd socket 
activation among other things.

[1]: https://github.com/systemd/systemd/issues/28030
[2]: https://github.com/systemd/systemd/issues/27953
[3]: https://github.com/systemd/systemd/pull/28000
[4]: https://github.com/systemd/systemd-stable/issues/302

Minimal reproducer:

systemd-run --quiet --collect --wait --property=KillMode=process -- sh -c 
'sleep 20 &'

This should not return immediately, but instead blocks for 30 seconds in 
the affected versions of systemd.

Less minimal reproducer:

1. install libvirt-daemon, libvirt-clients
2. make sure the default network is up (which it wouldn't be if you're 
   trying to do this inside another libvirt VM due to IP range conflict)
3. wait until the `/usr/sbin/libvirtd --timeout 120` process terminates
4. `systemctl status libvirtd.service` still says "active (running)"
5. `virsh connect` hangs indefinitely

Can we please get the fix [3] added to Debian as well?

(Also, I believe Luca is a maintainer of v252-stable, where the fix also 
needs to be backported. v252.11 currently in Debian testing and 
stable-proposed-updates is affected as well. I tried to highlight this 
issue a week ago [5] but I understand GitHub notifications are easy to 
miss.)

[5]: https://github.com/systemd/systemd/pull/28000#issuecomment-1608296400


-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  libacl12.3.1-3
ii  libaudit1  1:3.0.9-1
ii  libblkid1  2.38.1-5+b1
ii  libc6  2.37-3
ii  libcap21:2.66-4
ii  libcryptsetup122:2.6.1-4
ii  libfdisk1  2.38.1-5+b1
ii  libgcrypt201.10.2-2
ii  libkmod2   30+20230519-1
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.1-0.2
ii  libmount1  2.38.1-5+b1
ii  libp11-kit00.24.1-2
ii  libseccomp22.5.4-1+b3
ii  libselinux13.4-1+b6
ii  libssl33.0.9-1
ii  libsystemd-shared  253.5-1
ii  libsystemd0253.5-1
ii  libzstd1   1.5.5+dfsg2-1
ii  mount  2.38.1-5+b1
ii  systemd-dev253.5-1

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.14.8-1
ii  systemd-timesyncd [time-daemon]  253.5-1

Versions of packages systemd suggests:
ii  libfido2-11.13.0-1
pn  libqrencode4  
pn  libtss2-esys-3.0.2-0  
pn  libtss2-mu0   
pn  libtss2-rc0   
ii  polkitd   122-4
pn  systemd-boot  
pn  systemd-container 
pn  systemd-homed 
ii  systemd-resolved  253.5-1
pn  systemd-userdbd   

Versions of packages systemd is related to:
pn  dbus-user-session  
pn  dracut 
ii  initramfs-tools0.142
pn  libnss-systemd 
ii  libpam-systemd 253.5-1
ii  udev   253.5-1

-- no debconf information

-- 
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/

Bug#1040148: RFS: fonts-sahel/3.4.0-1 [ITP] -- Sahel font family

[Danial Behzadi دانیال بهزادی]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "fonts-sahel":

 * Package name : fonts-sahel
   Version  : 3.4.0-1
   Upstream contact : Saber Rastikerdar
 * URL  : https://rastikerdar.github.io/sahel-font/
 * License  : OFL1.1
 * Vcs  : https://salsa.debian.org/fonts-team/fonts-sahel
   Section  : fonts

The source builds the following binary packages:

  fonts-sahel - Sahel font family
  fonts-sahel-variable - Sahel font family (VF)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/fonts-sahel/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/f/fonts-sahel/fonts-sahel_3.4.0-1.dsc

Changes for the initial release:

 fonts-sahel (3.4.0-1) unstable; urgency=medium
 .
   * Initial release. (Closes: #1040143)

Regards,

Bug#1039907: apt-cacher-cleanup.pl clears/removes all cached packages on trixie

[gregor herrmann]

On Sun, 02 Jul 2023 15:40:45 +0100, Mark Hindley wrote:

> On Sun, Jul 02, 2023 at 03:37:29PM +0200, gregor herrmann wrote:
> > Random notes:
> > - IO::Uncompress::AnyUncompress is in both perl-modules-5.36 and
> >   libio-compress-perl.
> The system I reproduced on only has perl-modules-5.36 installed.

Ok.
 
> > - From a quick look at libio-compress-perl I don't see any recent
> >   relevant changes.
> > - I note that for de/compressing xz files libio-compress-lzma-perl is
> >   needed,
> Can you point me to the documentation for that, please? I have looked again 
> and
> still can't find it!

TBH, I was grepping through the code and found various occasions
where IO::Compress::Adapter::Xz or IO::Uncompress::Adapter::UnXz and
IO::Compress::Xz or IO::Uncompress::UnXz are mentioned :)

lib/IO/Uncompress/AnyUncompress.pm (from libio-compress-perl in git,
2.204-1) has

41 eval ' use IO::Uncompress::Adapter::UnXz 2.204 ;';

53 eval ' use IO::Uncompress::UnXz 2.204 ;';

   140   if (defined $IO::Uncompress::UnXz::VERSION and

   145  my ($obj, $errstr, $errno) =
   146  IO::Uncompress::Adapter::UnXz::mkUncompObject();

The only thing which comes close to some documentation is

  1060  =head1 SEE ALSO
  1061  
  1062  L, L, L, 
L, L, 
L, L, 
L, L, L, 
L, L, L, 
L, L, L, 
L, L, L, 
L, L, L


Some other grep results:

lib/IO/Compress/Zip.pm:To write Xz content, the module C 
must

lib/IO/Uncompress/Unzip.pm:eval{ require IO::Uncompress::Adapter::UnXz ;
lib/IO/Uncompress/Unzip.pm:  IO::Uncompress::Adapter::UnXz->import() } ;
lib/IO/Uncompress/Unzip.pm:if ! defined 
$IO::Uncompress::Adapter::UnXz::VERSION ;
lib/IO/Uncompress/Unzip.pm:my $obj = 
IO::Uncompress::Adapter::UnXz::mkUncompObject();
lib/IO/Uncompress/Unzip.pm:To read Xz content, the module 
C must

So lib/IO/Compress/Zip.pm and lib/IO/Uncompress/Unzip.pm mention that 
IO::Uncompress::UnXz
is required (and the former should probably mention IO::Compress::Xz)
 
> >   which is only Suggested by libio-compress-perl (and
> >   Recommended by apt-cacher)
> Installing libio-compress-lzma-perl pulls in libio-compress-perl and normal
> apt-cacher decompression is restored.

Yay \o/
 
> I suppose the apt-cacher Recommends will need to become a Depends.

*nod*
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1039779: Support phpunit 10

[Athos Ribeiro]

A fix proposal was submitted through salsa in
https://salsa.debian.org/php-team/pear/php-gettext/-/merge_requests/3


--
Athos Ribeiro

Bug#1033899: pipewire: Pipewire fails to sart, "Main process exited, code=killed, satus=31/SYS".

[Itai]

Thank you for the reply, attached is the output (log file).


On Sat, Jul 1, 2023 at 11:17 PM Dylan Aïssi  wrote:

> Le lun. 3 avr. 2023 à 18:54, Itai Shaked  a écrit :
> >
> > I am at a loss since there seems to be zero usable information in the
> logs,
> > just that the service is killed for some (unspecified?) reason.
> >
>
> Can you manually start pipewire with an increased verbose level?
> The following command should give us more details [1]:
>
> PIPEWIRE_LOG_SYSTEMD=false PIPEWIRE_DEBUG=5 pipewire 2>log
>
>
> Dylan
>
> [1]
> https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Troubleshooting#pipewire-debugging-options
>


log
Description: Binary data

Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)

[Aurelien Jarno]

control: notfound -1 2.36-9
control: found -1 2.37-3

Hi,

On 2023-07-02 15:12, antonio wrote:
> Package: libc6
> Version: 2.36-9
> Severity: important
> X-Debbugs-Cc: antde...@gmail.com
> 
> Dear Maintainer,
> after upgrade libc6 packages:
> --
> libc-bin libc-dev-bin libc-devtools libc-l10n libc6 libc6:i386 libc6-dbg
> libc6-dev libc6-dev-i386 libc6-dev-x32 libc6-i386 libc6-x32
> --
> to new version 2.37.3, I can't launch the desktop plasma applications.
> 
> With Plasma/X11:
> - after clicking on the icon to start any application, the following error
> appears (intercepted by journal):
> 
> kernel: __vm_enough_memory: pid: 7772, comm: plasmashell, not enough memory 
> for
> the allocation
> 
> With Plasma/Wayland:
> - A msgbox returns with the word "resource error) (fork not succeeded),
> impossible to allocate memory
> 
> Only Krunner works well and can launch the applications manually
> 
> Returning to the previous version 2.36-9 everything works well.

Thanks for your bug report. Unfortunately I am unable to reproduce the
issue locally. Can you please give me a few details that might help to
understand the problem:

- Which version of plasma do you use?
- Do you have any other information in dmesg when the problem happens?
- Can you please try to reproduce the issue using a debian kernel?
- As it seems to be related to display, can you please tell me which GPU
  is your computer using and which driver do you use?

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1040145: RM: ptable -- ROM; Unmaintained fork of prettytable - not used in Debian

[Scott Kitterman]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: team+pyt...@tracker.debian.org

This is no longer needed and is unmaintained.  Prettytable is in Debian
and is API compatible.

Scott K

Bug#1013212: I intend to adopt the vim-julia

[Thiago Marques]

retitle 1013212 ITA: vim-julia -- Vim support for Julia language


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

Bug#1040144: linux-image-6.3.0-1-amd64: radeon driver fails to load: modprobe: ERROR: could not insert 'radeon': No such device

[Jérôme Lafréchoux]

Package: src:linux
Version: 6.3.7-1
Severity: normal

Dear Maintainer,

Since I upgraded to Debian Bookworm (Linux 6), radeon drivers won't
load.

I tried both Bookworm and Sid kernels. Reporting against Sid.



Graphic card


VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Oland 
PRO [Radeon R7 240/340 / Radeon 520] [1002:6613]

Graphics:
  Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] driver: N/A
  Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: vesa
unloaded: fbdev,modesetting,radeon dri: swrast gpu: N/A
resolution: 1920x1080
  API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 128 bits)



Symptoms


modprobe: ERROR: could not insert 'radeon': No such device

Xorg log

[32.663] (EE) open /dev/dri/card0: No such file or directory
[32.663] (WW) Falling back to old probe method for modesetting
[32.663] (EE) open /dev/dri/card0: No such file or directory
[32.663] (II) Loading sub module "fbdevhw"
[32.663] (II) LoadModule: "fbdevhw"
[32.663] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[32.691] (II) Module fbdevhw: vendor="X.Org Foundation"
[32.691]compiled for 1.21.1.7, module version = 0.0.2
[32.691]ABI class: X.Org Video Driver, version 25.2
[32.691] (EE) Unable to find a valid framebuffer device
[32.691] (WW) Falling back to old probe method for fbdev
[32.691] (II) Loading sub module "fbdevhw"
[32.691] (II) LoadModule: "fbdevhw"
[32.691] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[32.691] (II) Module fbdevhw: vendor="X.Org Foundation"
[32.691]compiled for 1.21.1.7, module version = 0.0.2
[32.691]ABI class: X.Org Video Driver, version 25.2
[32.691] (EE) open /dev/fb0: No such file or directory
[32.691] (EE) Screen 0 deleted because of no matching config section.
[32.691] (II) UnloadModule: "radeon"
[32.691] (EE) Screen 0 deleted because of no matching config section.
[32.691] (II) UnloadModule: "modesetting"
[32.691] (EE) Screen 0 deleted because of no matching config section.
[32.691] (II) UnloadModule: "fbdev"
[32.691] (II) UnloadSubModule: "fbdevhw"
[32.691] (II) Loading sub module "vbe"
[32.691] (II) LoadModule: "vbe"
[32.691] (II) Loading /usr/lib/xorg/modules/libint10.so
[32.887] (II) Module int10: vendor="X.Org Foundation"
[32.887]compiled for 1.21.1.7, module version = 1.0.0
[32.887]ABI class: X.Org Video Driver, version 25.2
[32.887] (II) Loading sub module "int10"
[32.887] (II) LoadModule: "int10"
[32.887] (II) Loading /usr/lib/xorg/modules/libint10.so
[32.887] (II) Module int10: vendor="X.Org Foundation"
[32.887]compiled for 1.21.1.7, module version = 1.0.0
[32.887]ABI class: X.Org Video Driver, version 25.2
[32.887] (II) VESA(0): initializing int10
[32.891] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[32.891] (II) VESA(0): VESA BIOS detected
[32.891] (II) VESA(0): VESA VBE Version 3.0




-- Package-specific info:
** Version:
Linux version 6.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.3.0-1-amd64 
root=UUID=d719f337-d835-4688-baf2-3e29f147fe04 ro

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Dell Inc
product_name: XPS 630i
product_version: Unknow
chassis_vendor: Dell Inc
chassis_version: Unknow
bios_vendor: Dell Inc.
bios_version: 1.0.12
board_vendor: Dell Inc
board_name: 0C113J
board_version: A00

** Loaded modules:
rfcomm
snd_seq_dummy
snd_hrtimer
snd_seq_midi
snd_seq_midi_event
snd_seq
qrtr
cmac
algif_hash
ecb
algif_skcipher
af_alg
bnep
cpufreq_powersave
cpufreq_userspace
cpufreq_conservative
cpufreq_ondemand
sunrpc
binfmt_misc
snd_usb_audio
btusb
snd_hda_codec_realtek
btrtl
btbcm
btintel
snd_hda_codec_generic
btmtk
ledtrig_audio
bluetooth
snd_usbmidi_lib
snd_hda_codec_hdmi
snd_hda_intel
snd_intel_dspcfg
snd_rawmidi
jitterentropy_rng
snd_intel_sdw_acpi
snd_seq_device
ctr
snd_hda_codec
drbg
mc
snd_hda_core
ansi_cprng
joydev
snd_hwdep
ecdh_generic
snd_pcm_oss
rfkill
snd_mixer_oss
ecc
snd_pcm
coretemp
snd_timer
snd
sha512_ssse3
dcdbas
soundcore
evdev
serio_raw
sha512_generic
pcspkr
sg
nv_tco
drivetemp
parport_pc
ppdev
lp
parport
dm_mod
fuse
loop
efi_pstore
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
uas
usb_storage
efivarfs
raid10
raid456
async_raid6_recov
async_memcpy
async_pq
async_xor
async_tx
xor
raid6_pq
libcrc32c
crc32c_generic
raid0
multipath
linear
hid_generic
usbhid
hid
raid1
md_mod
i2c_algo_bit
sd_mod
drm_display_helper

Bug#1039907: apt-cacher-cleanup.pl clears/removes all cached packages on trixie

[Mark Hindley]

Gregor,

Thanks for your quick reply.

On Sun, Jul 02, 2023 at 03:37:29PM +0200, gregor herrmann wrote:
> Random notes:
> - IO::Uncompress::AnyUncompress is in both perl-modules-5.36 and
>   libio-compress-perl.

The system I reproduced on only has perl-modules-5.36 installed.

> - From a quick look at libio-compress-perl I don't see any recent
>   relevant changes.
> - I note that for de/compressing xz files libio-compress-lzma-perl is
>   needed,

Can you point me to the documentation for that, please? I have looked again and
still can't find it!

>   which is only Suggested by libio-compress-perl (and
>   Recommended by apt-cacher)

Installing libio-compress-lzma-perl pulls in libio-compress-perl and normal
apt-cacher decompression is restored.

I suppose the apt-cacher Recommends will need to become a Depends.

Chris, there maybe another issue with underscore encoding in filenames which I
am looking at.

Mark

Bug#1038506: libmlt7: Contains a plugin for an obsolete version of SDL

[Patrick Matthäi]

Hey

Am 18.06.2023 um 18:42 schrieb Simon McVittie:

Package: libmlt7
Version: 7.14.0-1
Tags: trixie sid
User: pkg-sdl-maintain...@lists.alioth.debian.org
Usertags: libsdl1.2

libmlt7 appears to contain plugins for both SDL 1.2 and SDL 2, and as a
result, it depends on both libsdl1.2debian and libsdl2-2.0-0.
SDL 1.2 is unmaintained upstream and we should be trying to move away
from it.

Various Debian packages depend on mlt:

- flowblade

Flowblade itself still uses SDL 1.2:
https://sourceforge.net/p/mlt/mailman/message/37862164/

- kdenlive
- shotcut
- synfig
- synfigstudio

but as far as I can see, none of them need SDL 1.2 specifically. Would
it be possible to disable/remove the SDL 1.2 plugin in mlt?

Thanks,
 smcv



--
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: https://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#1040143: ITP: fonts-sahel -- Sahel Persian/Arabic truetype font family

[Danial Behzadi]

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

* Package name: fonts-sahel
  Version : 4.3.0
  Upstream Contact: Saber Rastikerdar
* URL : https://rastikerdar.github.io/sahel-font/
* License : OFL-1.1
  Programming Lang: 
  Description : Sahel Persian/Arabic truetype font family

 Sahel is a free and open source font, designed by Saber Rastikerdar
 and many other people for persian and arabic language.

Bug#1040142: bookworm-pu: package aide/0.18.3-1+deb12u2

[Marc Haber]

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

Dear stable release team,

this pre-upload request for the aide package is filed to ask for
guidance whether this package is suitable for bookworm-proposed-updates

[ Reason ]
This update augments 0.18.3-1+deb12u1 which has already been accepted
for bookworm-pu last week. It fixes #1039936, an important bug that is a
regression from bullseye and affects directory processing when using
equals rules.

[ Impact ]
Without this bug fixes, equals rules concerning directories are
incorrectly processed, which differs from the way that bullseye's aide
handled this case and also differs from the way operation is documented.
Debian's default configuration doesn't use equals rules and is therefore
not affected, but local configurations might be.

[ Tests ]
Sadly, none.

[ Risks ]
The fix is reasonably simple, and we have done manual tests.

[ 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 ]
In aide-0.18.3/debian/aide-common.postinst a typo in a version number in
a comment is fixed, which reduces ambiguity and will reduce the size of
future diffs.
aide-0.18.3/debian/patches/debian-bug-1039936 adds the actual patch. It
has been cherry-picked from upstream's 0.18.5 release.

[ Other info ]
The attached debdiff is the debdiff between 0.18.3-1+deb12u1, which is
already in bookworm-proposed-updates and the newly suggested
0.18.3-1+deb12u2 which we are discussing right now. I hope this is the
right thing to do to save you from reviewing the 0.18.3-1+deb12u1
changes a second time.

Should you agree and tell me to go ahead with this upload, I'm planning
to do the upload after 0.18.5-1 has migrated to testing to make sure
that the version in testing and bookworm-pu have the issue both fixed.

Greetings
Marc
diff -Nru aide-0.18.3/debian/aide-common.postinst 
aide-0.18.3/debian/aide-common.postinst
--- aide-0.18.3/debian/aide-common.postinst 2023-06-14 17:04:20.0 
+0200
+++ aide-0.18.3/debian/aide-common.postinst 2023-07-01 14:37:51.0 
+0200
@@ -94,7 +94,7 @@
 chown --quiet _aide:root /var/lib/aide/aide.db /var/lib/aide/aide.db.new 
|| true
 fi
 if dpkg --compare-versions "$2" le 0.18.3-1; then
-# we're updating from 0.18-3 or earlier, chown aideinit logs
+# we're updating from 0.18.3-1 or earlier, chown aideinit logs
 chown --quiet _aide:adm /var/log/aide/aideinit.log 
/var/log/aide/aideinit.errors|| true
 fi
 
diff -Nru aide-0.18.3/debian/changelog aide-0.18.3/debian/changelog
--- aide-0.18.3/debian/changelog2023-06-14 17:04:20.0 +0200
+++ aide-0.18.3/debian/changelog2023-07-01 14:37:51.0 +0200
@@ -1,3 +1,10 @@
+aide (0.18.3-1+deb12u2) bookworm; urgency=medium
+
+  * Upstream patch to fix child directory processing on equal match
+(Closes: #1039936)
+
+ -- Marc Haber   Sat, 01 Jul 2023 14:37:51 
+0200
+
 aide (0.18.3-1+deb12u1) bookworm; urgency=medium
 
   * call dh_installsysusers manually in debian/rules
diff -Nru aide-0.18.3/debian/patches/debian-bug-1039936 
aide-0.18.3/debian/patches/debian-bug-1039936
--- aide-0.18.3/debian/patches/debian-bug-1039936   1970-01-01 
01:00:00.0 +0100
+++ aide-0.18.3/debian/patches/debian-bug-1039936   2023-07-01 
14:37:51.0 +0200
@@ -0,0 +1,21 @@
+Subject: Fix child directory proccessing on equal match
+Forwarded: not-needed
+Source: 
https://github.com/aide/aide/commit/cf5026bf0852d350030d6d1a7a0351573c9512e6
+--- a/src/db_disk.c
 b/src/db_disk.c
+@@ -171,13 +171,12 @@ void scan_dir(char *root_path, bool dry_
+ #endif
+ switch (match) {
+ case RESULT_SELECTIVE_MATCH:
++case RESULT_EQUAL_MATCH:
+ if (S_ISDIR(fs.st_mode)) {
+-log_msg(log_level, "scan_dir: add child 
directory '%s' to scan stack (reason: selective match)", 
&entry_full_path[conf->root_prefix_length]);
++log_msg(log_level, "scan_dir: add child 
directory '%s' to scan stack (reason: selective/equal match)", 
&entry_full_path[conf->root_prefix_length]);
+ queue_enqueue(stack, entry_full_path);
+ free_entry_full_path = false;
+ }
+-// fall through
+-case RESULT_EQUAL_MATCH:
+ if (!dry_run) {
+ handle_matched_file(entry_full_path, 
rule->attr, fs);
+ }
diff -Nru aide-0.18.3/debian/patches/series aide-0.18.3/debian/patches/series

Bug#958487: cairo: Please update to the new upstream version 1.17

[Jeremy Bícha]

Simon,

I plan to upload cairo 1.17 to Unstable soon after Debian 12.1 is
released. cairo has a goal of releasing 1.18 in August:
https://gitlab.freedesktop.org/cairo/cairo/-/milestones/5

Thank you,
Jeremy Bícha

Bug#1040141: FTBFS: FAIL: TestCheckoutGit

[Bastien Roucariès]

Source: docker.io
Version: 18.09.1+dfsg1-7.1+deb10u3
Severity: serious
Justification: FTBFS
X-Debbugs-Cc: debian-...@lists.debian.org

Dear Maintainer,

The current security version FTBFS for me with
-- FAIL: TestCheckoutGit (0.52s)
gitutils_test.go:188: assertion failed: error is not nil: exit status 128


I am currently debugging this regression.

Bastien



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

Bug#1039489: domains in i field and d field are compared as case sensitive

[gregor herrmann]

On Mon, 26 Jun 2023 17:05:19 +0200, Sven Bartscher wrote:

> I would like to fix this issue in an LTS update to Buster. Is it alright for
> you, the package maintainer, if I go ahead and prepare an LTS for Buster?
> Are there any other considerations you would like me to take into account?

I don't think anyone in the Debian Perl Group will have objections to
fixes in LTS, so please go ahead, and feel free to use our packaging
repo at https://salsa.debian.org/perl-team/modules/packages/libmail-dkim-perl
if you like.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1039907: apt-cacher-cleanup.pl clears/removes all cached packages on trixie

[gregor herrmann]

On Sun, 02 Jul 2023 12:32:23 +0100, Mark Hindley wrote:

> It appears to be a regression in the IO::Uncompress::AnyUncompress module 
> which
> doesn't seem to handle xz any more. At the moment I am unsure why. My minimal
> script to reproduce is attached. My testing shows that text and gzipped files
> work as expected, but not xz.

Random notes:
- IO::Uncompress::AnyUncompress is in both perl-modules-5.36 and
  libio-compress-perl.
- From a quick look at libio-compress-perl I don't see any recent
  relevant changes.
- I note that for de/compressing xz files libio-compress-lzma-perl is
  needed, which is only Suggested by libio-compress-perl (and
  Recommended by apt-cacher)
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#929738: gnumail.app: gnumail freezes when i click 'info > preferences'

[Yavor Doganov]

Hi Svetlana,

On Thu, May 30, 2019 at 07:36:41AM +1000, Svetlana Tkachenko wrote:
> Package: gnumail.app
> Version: 1.3.0-1+b1
> Severity: normal
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> click info>preferences
>* What was the outcome of this action?
> it stays highlighted this menu item and does not open preferences

If you have the chance, could you please try gnumail.app/1.4.0-1
available in unstable (a.k.a. sid) and testing (a.k.a. trixie) and see
if this bug, as well as #929737, are fixed?

I could not reproduce either of them but this new version fixes a lot
of problems (albeit some still remain).

Thanks in advance.

Bug#1025552: Bug#1037295: live-config: starting Calamares installer requires a password (which is 'live')

[Simon McVittie]

On Sat, 01 Jul 2023 at 22:07:41 +0200, Roland Clobus wrote:
> policykit-1 is a transitional packages for Bookworm, so I guess it will be
> removed in Trixie.

Yes. I already did a mass bug filing back in 2022, before bookworm:
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-utopia-maintainers%40lists.alioth.debian.org&tag=policykit-1

> Also the script '1080-policykit' in 'live-config' generates a folder
> '/etc/PolicyKit', which is old-style.

Yes, I already mentioned this in
.

> * The script '1080-policykit' in 'live-config' needs to be updated and
> live-config be re-released -> MR at [1]
> [1] https://salsa.debian.org/live-team/live-config/-/merge_requests/13

That looks appropriate to me, thanks for providing it!

smcv

Bug#1040140: libc6: upgrade libc6 to version 2.37-3 break plasma desktop (X11/Wayland)

[antonio]

Package: libc6
Version: 2.36-9
Severity: important
X-Debbugs-Cc: antde...@gmail.com

Dear Maintainer,
after upgrade libc6 packages:
--
libc-bin libc-dev-bin libc-devtools libc-l10n libc6 libc6:i386 libc6-dbg
libc6-dev libc6-dev-i386 libc6-dev-x32 libc6-i386 libc6-x32
--
to new version 2.37.3, I can't launch the desktop plasma applications.

With Plasma/X11:
- after clicking on the icon to start any application, the following error
appears (intercepted by journal):

kernel: __vm_enough_memory: pid: 7772, comm: plasmashell, not enough memory for
the allocation

With Plasma/Wayland:
- A msgbox returns with the word "resource error) (fork not succeeded),
impossible to allocate memory

Only Krunner works well and can launch the applications manually

Returning to the previous version 2.36-9 everything works well.

Thanks,
Antonio



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

Kernel: Linux 6.3.11-2-liquorix-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libc6 depends on:
ii  libgcc-s1  13.1.0-7

Versions of packages libc6 recommends:
ii  libidn2-0  2.3.3-1+b1

Versions of packages libc6 suggests:
ii  debconf [debconf-2.0]  1.5.82
pn  glibc-doc  
ii  libc-l10n  2.36-9
ii  libnss-nis 3.1-4
ii  libnss-nisplus 1.3-4
ii  locales2.36-9

-- debconf information excluded

Bug#1040139: bookworm-pu: package exim4/4.96-15

[Andreas Metzler]

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

Hello,

I would like to get most of the changes from 4.96-16 (unstable/testing)
into bookworm:
   * 75_42-Fix-run-arg-parsing.patch (From upstream GIT master, backported by
 Bryce Harrington for Ubuntu):  Fix argument parsing for ${run } expansion.
 Previously, when an argument included a close-brace character (eg. it
 itself used an expansion) an error occurred. Closes: #1025420
   * 75_68-Fix-srs_encode-.-for-mod-1024-day-zero.patch from upstream GIT
 master:  Fix ${srs_encode ..}. Previously it would give a bad result for
 one day every 1024 days.

The former is something has already popped up a couple of times on the
upstream user support mailing list.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff --git a/debian/changelog b/debian/changelog
index fbbb8c20..0231dc69 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+exim4 (4.96-15+deb12u1) bookworm; urgency=medium
+
+  * 75_42-Fix-run-arg-parsing.patch (From upstream GIT master, backported by
+Bryce Harrington for Ubuntu):  Fix argument parsing for ${run } expansion.
+Previously, when an argument included a close-brace character (eg. it
+itself used an expansion) an error occurred. Closes: #1025420
+  * 75_68-Fix-srs_encode-.-for-mod-1024-day-zero.patch from upstream GIT
+master:  Fix ${srs_encode ..}. Previously it would give a bad result for
+one day every 1024 days.
+
+ -- Andreas Metzler   Sun, 02 Jul 2023 14:56:17 +0200
+
 exim4 (4.96-15) unstable; urgency=medium
 
   * Pull from upstream GIT master:
diff --git a/debian/patches/75_42-Fix-run-arg-parsing.patch b/debian/patches/75_42-Fix-run-arg-parsing.patch
new file mode 100644
index ..79e55d61
--- /dev/null
+++ b/debian/patches/75_42-Fix-run-arg-parsing.patch
@@ -0,0 +1,100 @@
+From 44b6e099b76f403a55e77650821f8a69e9d2682e Mon Sep 17 00:00:00 2001
+From: Jeremy Harris 
+Date: Sat, 3 Dec 2022 23:13:53 +
+Subject: [PATCH] Fix ${run } arg parsing
+ .
+  Backported by Bryce Harrington for Ubuntu
+
+Broken-by: cfe6acff2ddc
+---
+ doc/ChangeLog|  4 
+ src/expand.c | 13 ++---
+ src/transport.c  |  4 +++-
+ test/scripts/-Basic/0002 |  2 ++
+ test/stdout/0002 |  2 ++
+ 5 files changed, 21 insertions(+), 4 deletions(-)
+
+--- a/doc/ChangeLog
 b/doc/ChangeLog
+@@ -28,10 +28,14 @@ JH/13 Bug 2929: Fix using $recipients af
+ JH/14 Bug 2933: Fix regex substring match variables for null matches. Since 4.96
+   a capture group which obtained no text (eg. "(abc)*" matching zero
+   occurrences) could cause a segfault if the corresponding $ was
+   expanded.
+ 
++JH/15 Fix argument parsing for ${run } expansion. Previously, when an argument
++  included a close-brace character (eg. it itself used an expansion) an
++  error occurred.
++
+ 
+ 
+ Exim version 4.96
+ -
+ 
+--- a/src/expand.c
 b/src/expand.c
+@@ -5529,11 +5529,11 @@ while (*s)
+   {
+   FILE * f;
+   const uschar * arg, ** argv;
+   BOOL late_expand = TRUE;
+ 
+-  if ((expand_forbid & RDO_RUN) != 0)
++  if (expand_forbid & RDO_RUN)
+ {
+ expand_string_message = US"running a command is not permitted";
+ goto EXPAND_FAILED;
+ }
+ 
+@@ -5561,16 +5561,22 @@ while (*s)
+ 	}
+   s++;
+ 
+   if (late_expand)		/* this is the default case */
+ 	{
+-	int n = Ustrcspn(s, "}");
++	int n;
++	const uschar * t;
++	/* Locate the end of the args */
++	(void) expand_string_internal(s, TRUE, &t, TRUE, TRUE, NULL);
++	n = t - s;
+ 	arg = skipping ? NULL : string_copyn(s, n);
+ 	s += n;
+ 	}
+   else
+ 	{
++	DEBUG(D_expand)
++	  debug_printf_indent("args string for ${run} expand before split\n");
+ 	if (!(arg = expand_string_internal(s, TRUE, &s, skipping, TRUE, &resetok)))
+ 	  goto EXPAND_FAILED;
+ 	Uskip_whitespace(&s);
+ 	}
+ 			/*{*/
+--- a/src/transport.c
 b/src/transport.c
+@@ -2187,10 +2187,12 @@ if (expand_arguments)
+   BOOL allow_dollar_recipients = addr && addr->parent
+ && Ustrcmp(addr->parent->address, "system-filter") == 0;
+ 
+   for (int i = 0; argv[i]; i++)
+ {
++DEBUG(D_expand) debug_printf_indent("arg %d\n", i);
++
+ /* Handle special fudge for passing an address list */
+ 
+ if (addr &&
+ (Ustrcmp(argv[i], "$pipe_addresses") == 0 ||
+  Ustrcmp(argv[i], "${pipe_addresses}") == 0))
+@@ -2361,11 +2363,11 @@ if (expand_arguments)
+   }
+ else *errptr = msg;
+ return FALSE;
+ }
+ 
+-  if ( f.running_in_test_harness && is_tainted(expanded_arg)
++  if (  f.running_in_test_harness && is_tainted(expanded_arg)
+ 	 && Ustrcmp(etext, "queryprogram rou

Bug#1038343: fim: Depends on SDL 1.2

[Michele Martone]

On 20230622@08:08, Rafael Laboissière wrote:
> * Michele Martone  [2023-06-21 23:43]:
> 
> > On 20230618@22:27, Rafael Laboissière wrote:
> > > * Simon McVittie  [2023-06-18 17:10]:
> > > 
> > > > On Sat, 17 Jun 2023 at 21:11:25 +0200, Rafael Laboissière wrote:
> > > > > Thanks for this bug report. I forwarded it upstream and I am also 
> > > > > sending
> > > > > this message with Cc to the upstream author.
> > > > 
> > > > Thanks. In the meantime, please could you check whether fim
> > > > works as intended with libsdl1.2-compat-shim, which is meant to
> > > > be a drop-in replacement? I'm trying to track whether there are
> > > > any blockers to replacing "classic" SDL 1.2.
> > > 
> > > The package builds fine against libsdl1.2-compat-dev on my sid amd64
> > > system. All tests also passed, but I am not sure this would be
> > > enough. I would rather let the upstream author have the final word,
> > > but if you think I should upload a new version of the package with
> > > that build-dependency, please tell me.
> > 
> > Dear Rafael, dear Simon,
> > 
> > If using the compatibility layer and:
> > 
> > * `make tests` passes
> 
> It is not straightforward for me to do this test, because I build the
> package on a remote system, and SDL does not play well with xvfb-run.
> 
> On the other hand the unit tests that are exercised in file
> debian/test/run-tests succeeded. Essentially, this corresponds to:
> 
> make -C src/testdir
> 
> > * you can start `fim -o sdl $FILE` and move around by pressing   n, p,
> > then enlarging/shrinking with + and -, using the arrows   to scroll, and
> > : to start the console, and after : typing   'quit' and it quits, plus
> > the window is resizable
> 
> The window starts with the image flushed to the bottom right, and not
> centered as with the previous version.
> 
> Keys n, p, + and - work correctly. The arrow keys work also, but there is
> some flickering that I did not observe previously.
> 
> Typing ":quit" works, but there is no echo of the console at the bottom of
> the window.
> 
> So, it mainly works but the behavior with the compatibility version of the
> SDL library is not exactly the same as with the old version of SDL.
> 
> Best,
> 
> Rafael

Dear Rafael,

Thank you for testing out this combination.

As you describe it, it seems perfectly acceptable to me.

If I understand correctly, you're using here a version of FIM
from one year ago or more.
After that, I introduced centering by inserting line
 setenv("SDL_VIDEO_CENTERED","1",0);
in SDLDevice::initialize(), on the line just before calling
SDL_Init().
If that can make sense to you, you can introduce that line as 
a patch. I'll need some calm time in order to port to SDL2 --
but I understand it's something I shall do soon.

ciao,
Michele


signature.asc
Description: PGP signature

Bug#1040138: changelog-file-missing-explicit-entry needs exception for bookworm

[Marc Haber]

Package: lintian
Version: 2.116.3
Severity: important

Hi,

this is the bookworm edition of #1001651 which got fixed by adding an
exception, judging from the changelog entry of lintian 2.115.0.

This issue happens again when preparing a successive upload to bookworm.
I have aide 0.18.3-1, 0.18.3-1+deb12u1 and 0.18.3-1+deb12u2, the deb12u2
gets this lintian tag.

See https://salsa.debian.org/debian/aide/-/blob/bookworm/debian/changelog

Greetings
Marc


-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-zgsrv20080 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lintian depends on:
ii  binutils2.40.50.20230625-1
ii  bzip2   1.0.8-5+b1
ii  diffstat1.65-1
ii  dpkg1.21.22
ii  dpkg-dev1.21.22
ii  file1:5.44-3
ii  gettext 0.21-12
ii  gpg 2.2.40-1.1
ii  intltool-debian 0.35.0+20060710.6
ii  iso-codes   4.15.0-1
ii  libapt-pkg-perl 0.1.40+b2
ii  libarchive-zip-perl 1.68-1
ii  libberkeleydb-perl  0.64-2+b1
ii  libcapture-tiny-perl0.48-2
ii  libclass-xsaccessor-perl1.19-4+b1
ii  libclone-perl   0.46-1
ii  libconfig-tiny-perl 2.29-1
ii  libconst-fast-perl  0.014-2
ii  libcpanel-json-xs-perl  4.36-1
ii  libdata-dpath-perl  0.58-2
ii  libdata-validate-domain-perl0.10-1.1
ii  libdata-validate-uri-perl   0.07-2
ii  libdevel-size-perl  0.83-2+b1
pn  libdigest-sha-perl  
ii  libdpkg-perl1.21.22
ii  libemail-address-xs-perl1.05-1+b1
ii  libfile-basedir-perl0.09-2
ii  libfile-find-rule-perl  0.34-3
ii  libfont-ttf-perl1.06-2
ii  libhtml-html5-entities-perl 0.004-3
ii  libhtml-tokeparser-simple-perl  3.16-4
ii  libio-interactive-perl  1.023-2
ii  libipc-run3-perl0.048-3
ii  libjson-maybexs-perl1.004005-1
ii  liblist-compare-perl0.55-2
ii  liblist-someutils-perl  0.59-1
ii  liblist-utilsby-perl0.12-2
ii  libmldbm-perl   2.05-4
ii  libmoo-perl 2.005005-1
ii  libmoox-aliases-perl0.001006-2
ii  libnamespace-clean-perl 0.27-2
ii  libpath-tiny-perl   0.144-1
ii  libperlio-gzip-perl 0.20-1+b1
ii  libperlio-utf8-strict-perl  0.010-1
ii  libproc-processtable-perl   0.636-1
ii  libregexp-wildcards-perl1.05-3
ii  libsereal-decoder-perl  5.004+ds-1
ii  libsereal-encoder-perl  5.004+ds-1
ii  libsort-versions-perl   1.62-3
ii  libsyntax-keyword-try-perl  0.28-1
ii  libterm-readkey-perl2.38-2+b1
ii  libtext-levenshteinxs-perl  0.03-5+b1
ii  libtext-markdown-discount-perl  0.16-1
ii  libtext-xslate-perl 3.5.9-1+b2
ii  libtime-duration-perl   1.21-2
ii  libtime-moment-perl 0.44-2+b1
ii  libtimedate-perl2.3300-2
ii  libunicode-utf8-perl0.62-2
ii  liburi-perl 5.19-2
ii  libwww-mechanize-perl   2.17-1
ii  libwww-perl 6.71-1
ii  libxml-libxml-perl  2.0207+dfsg+really+2.0134-1+b1
ii  libyaml-libyaml-perl0.86+ds-1
ii  lzip [lzip-decompressor]1.23-6
ii  lzop1.04-2
ii  man-db  2.11.2-2
ii  patchutils  0.4.2-1
ii  perl [libencode-perl]   5.36.0-7
ii  t1utils 1.41-4
ii  unzip   6.0-28
ii  xz-utils5.4.1-0.2

lintian recommends no packages.

Versions of packages lintian suggests:
pn  binutils-multiarch 
pn  libtext-template-perl  

-- no debconf information