Bug#1052598: RFA: sisl -- SINTEF Spline Library

[Simon Richter]

Package: wnpp
Severity: normal
X-Debbugs-Cc: s...@packages.debian.org, s...@debian.org
Control: affects -1 + src:sisl

Hi,

I packaged the SINTEF Spline Library a while ago because a prerelease
version of KiCad depended on it. Since none of the release versions did,
this package is probably not used by many people.

That said, it also hasn't had any new upstream releases in ten years, so
both users (popcon count: 2) are probably fine with the situation as it
is.

If there is someone who actively uses this package, and wants to become
maintainer, I'd be happy to hand it over.

The package description is:
 The SINTEF Spline Library is a comprehensive NURBS library for the modeling
 and interrogation of curves and surfaces.
 .
 It is implemented in C and has been under continuous development for over two
 decades.

   Simon

Bug#1052597: RFS: libkysdk-base/2.2.0.1-1 -- common files for kylin sdk base library

[xibowen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libkysdk-base":

 * Package name : libkysdk-base
   Version  : 2.2.0.1-1
   Upstream contact : Zhikai Chen 
 * URL  : https://gitee.com/openkylin/libkysdk-base
 * License  : LGPL-3+
 * Vcs  : https://gitee.com/openkylin/libkysdk-base
   Section  : libs

The source builds the following binary packages:

  libkysdk-base2 - Kylin SDK basic library
  libkysdk-base-dev - development files for libkysdk-base
  libkysdk-base-common - common files for kylin sdk base library

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

  https://mentors.debian.net/package/libkysdk-base/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libk/libkysdk-base/libkysdk-base_2.2.0.1-1.dsc

Changes since the last upload:

 libkysdk-base (2.2.0.1-1) unstable; urgency=medium
 .
   * Update libs soname version.
   * Fix compile error on armhf and ppc64el.
   * d/control:
 - Add libkysdk-base-common.
 - Add Multi-Arch.

Regards,
-- 
  xibowen

Bug#1052596: python3-sympy: sympy.Poly() fails with: GeneratorsNeeded: Cannot initialize from 'dict' without generators

[Kingsley G. Morse Jr.]

Package: python3-sympy
Version: 1.12-6
Severity: normal

Thank you very mcuh for maintaining Debian Linux's
"python3-sympy" package.

It's interesting and sophisticated.

Please allow me to draw your attention a possible
bug.

I can elicit it with just 2 lines of code.

Here is how:

$ ipython3

In [1]: from sympy import Poly

In [2]: Poly('((a - b) - (((a - b)  +  (c - d)  +  (e - f))/3)) + ((c - d) 
- (((a - b)  +  (c - d)  +  (e - f))/3)) + (e - f) - ((a - b)  +  (c - d)  +  
(e - f))/3')

sympy.Poly() complains with

---
GeneratorsNeeded  Traceback (most recent call last)
Cell In [2], line 1
> 1 Poly('((a - b) - (((a - b)  +  (c - d)  +  (e - f))/3)) + ((c - d) 
- (((a - b)  +  (c - d)  +  (e - f))/3)) + (e - f) - ((a - b)  +  (c - d)  +  
(e - f))/3')

File /usr/lib/python3/dist-packages/sympy/polys/polytools.py:182, in 
Poly.__new__(cls, rep, *gens, **args)
180 return cls._from_poly(rep, opt)
181 else:
--> 182 return cls._from_expr(rep, opt)

File /usr/lib/python3/dist-packages/sympy/polys/polytools.py:312, in 
Poly._from_expr(cls, rep, opt)
310 """Construct a polynomial from an expression. """
311 rep, opt = _dict_from_expr(rep, opt)
--> 312 return cls._from_dict(rep, opt)

File /usr/lib/python3/dist-packages/sympy/polys/polytools.py:249, in 
Poly._from_dict(cls, rep, opt)
246 gens = opt.gens
248 if not gens:
--> 249 raise GeneratorsNeeded(
250 "Cannot initialize from 'dict' without generators")
252 level = len(gens) - 1
253 domain = opt.domain

GeneratorsNeeded: Cannot initialize from 'dict' without generators


I expected it to work.

Especially because simply deleting the trailing "/3" from the input does, like 
this...

In [3]: Poly('((a - b) - (((a - b)  +  (c - d)  +  (e - f))/3)) + ((c - d) 
- (((a - b)  +  (c - d)  +  (e - f))/3)) + (e - f) - ((a - b)  +  (c - d)  +  
(e - f))')

Out[3]: Poly(-2/3*a + 2/3*b - 2/3*c + 2/3*d - 2/3*e + 2/3*f, a, b, c, d, e, 
f, domain='QQ')


I suppose an approximate workaround is to replace the trailing

.../3

with a leading

0.333*...

like this...

In [4]: Poly('((a - b) - (((a - b)  +  (c - d)  +  (e - f))/3)) + ((c - d) 
- (((a - b)  +  (c - d)  +  (e - f))/3)) + (e - f) - 0.333*((a - b)  + 
   ...:  (c - d)  +  (e - f))')
Out[4]: Poly(0.000297*a - 0.000297*b + 
0.000297*c - 0.000297*d + 0.000297*e - 
0.000297*f, a, b, c, d, e, f, domain='RR')


I also noticed that replacing the trailing "/3" with division by 1, 2, 4, 5 and 
6 worked.

Thanks again for maintaining Debian's python3-sympy package.

Kind regards,
Kingsley


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
merged-usr: no
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages python3-sympy depends on:
ii  python3 3.11.1-3
ii  python3-mpmath  1.2.1-1

Versions of packages python3-sympy recommends:
ii  isympy-common  1.7.1-2
ii  python3-numpy  1:1.24.2-1
ii  python3-pil9.4.0-1.1+b1

Versions of packages python3-sympy suggests:
pn  dvipng   
pn  python-sympy-doc 
pn  texlive-fonts-extra  

-- no debconf information

Bug#1052595: liburcu: Please add support for loong64

[JiaLing Zhang]

Source: liburcu
Version: 0.14.0-1
Severity: serious
Tags: ftbfs loongarch64

Hello!

the liburcu build failed in buildd , the upstream have support
loongarch. Please update the source.

thanks!
JiaLing

[1]: 
https://github.com/urcu/userspace-rcu/commit/dc46a9c324ae94d89da41ea9a3f97503115df88e

Bug#1052594: RFS: libkysdk-base/2.2.0.1-1 -- common files for kylin sdk base library

[xibowen]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libkysdk-base":

 * Package name   : libkysdk-base
   Version   : 2.2.0.1-1
   Upstream contact   : Zhikai Chen 
 * URL  : https://gitee.com/openkylin/libkysdk-base
 * License  : LGPL-3+
 * Vcs: https://gitee.com/openkylin/libkysdk-base
   Section   : libs

The source builds the following binary packages:

  libkysdk-base2 - Kylin SDK basic library
  libkysdk-base-dev - development files for libkysdk-base
  libkysdk-base-common - common files for kylin sdk base library

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

  https://mentors.debian.net/package/libkysdk-base/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libk/libkysdk-base/libkysdk-base_2.2.0.1-1.dsc

Changes since the last upload:

 libkysdk-base (2.2.0.1-1) unstable; urgency=medium
 .
   * Update libs soname version.
   * Fix compile error on armhf and ppc64el.
   * d/control:
 - Add libkysdk-base-common.
 - Add Multi-Arch.

Regards,
-- 
  xibowen

Bug#1052592: RFS: libkysdk-base/2.2.0.1-1 -- common files for kylin sdk base library

[xibowen]

Package: sponsorship-requests
Severity: normal


Dear mentors,


I am looking for a sponsor for my package "libkysdk-base":


* Package name   : libkysdk-base
 Version : 2.2.0.1-1
 Upstream contact : Zhikai Chen https://gitee.com/openkylin/libkysdk-base
* License : LGPL-3+
* Vcs   : 
https://gitee.com/openkylin/libkysdk-base
 Section : libs


The source builds the following binary packages:


 libkysdk-base2 - Kylin SDK basic library
 libkysdk-base-dev - development files for libkysdk-base
 libkysdk-base-common - common files for kylin sdk base library


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


 https://mentors.debian.net/package/libkysdk-base/


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


 dget -x 
https://mentors.debian.net/debian/pool/main/libk/libkysdk-base/libkysdk-base_2.2.0.1-1.dsc


Changes since the last upload:


libkysdk-base (2.2.0.1-1) unstable; urgency=medium
.
 * Update libs soname version.
 * Fix compile error on armhf and ppc64el.
 * d/control:
  - Add libkysdk-base-common.
  - Add Multi-Arch.


Regards,
--
 xibowen



 

Bug#1052593: RFS: libkysdk-base/2.2.0.1-1 -- common files for kylin sdk base library

[xibowen]

Package: sponsorship-requests
Severity: normal


Dear mentors,


I am looking for a sponsor for my package "libkysdk-base":


* Package name   : libkysdk-base
 Version : 2.2.0.1-1
 Upstream contact : Zhikai Chen https://gitee.com/openkylin/libkysdk-base
* License : LGPL-3+
* Vcs   : 
https://gitee.com/openkylin/libkysdk-base
 Section : libs


The source builds the following binary packages:


 libkysdk-base2 - Kylin SDK basic library
 libkysdk-base-dev - development files for libkysdk-base
 libkysdk-base-common - common files for kylin sdk base library


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


 https://mentors.debian.net/package/libkysdk-base/


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


 dget -x 
https://mentors.debian.net/debian/pool/main/libk/libkysdk-base/libkysdk-base_2.2.0.1-1.dsc


Changes since the last upload:


libkysdk-base (2.2.0.1-1) unstable; urgency=medium
.
 * Update libs soname version.
 * Fix compile error on armhf and ppc64el.
 * d/control:
  - Add libkysdk-base-common.
  - Add Multi-Arch.


Regards,
-- 
 xibowen

Bug#1051910: mirror submission for ossmirror.mycloud.services

[OSSMirror@OnboardCloud]

Hi Adam, We were looking at the mirror listing and our mirror does not seem to have been listed yet. https://www.debian.org/mirror/list-full#SG  May I enquire do you know roughly how long does it take for the mirror to be listed? Best regards, -Original Message-From: OSSMirror@OnboardCloud Date: Sunday, 24 September 2023 at 3:31 AMTo: Adam D. Barratt Cc: 1051...@bugs.debian.org <1051...@bugs.debian.org>Subject: Re: Bug#1051910: mirror submission for ossmirror.mycloud.servicesThanks Adam for the clarification and kind assistance! On 24 Sep 2023, at 2:56 AM, Adam D. Barratt  wrote: On Sun, 2023-09-24 at 01:57 +0800, OSSMirror@OnboardCloud wrote:> Hi Adam,> > Thanks for the reply. Could you elaborate further what do you mean as> the /debian/ works:> > http://ossmirror.mycloud.services/debian/>  Ah, right - I was mislead by the index ofhttp://ossmirror.mycloud.services implying that only /os/ existed, anddidn't check for an alias. Regards, Adam   

Bug#1052591: openscad: Preview renders garbage at difference-planes

[Eric Cooper]

Package: openscad
Version: 2021.01-6
Severity: important

Dear Maintainer,

When I open this SCAD source:

difference() {
cube([10, 10, 10], center = true);
cube([5, 5, 10], center = true);
}

the preview shows garbage in the "openings" created by the difference
operation. The display of the garbage changes as I rotate or zoom the
view.

To get rid of the garbage completely, I have to do a full render. That
is very time-consuming on a larger model, whereas the garbage effect makes
previewing almost useless, so I rated this severity "important".

The bug is independent of the objects being differenced.
It occurs when there is exact co-planarity of
a face of A and a face of B in
difference() { A; B; }

-- Package-specific info:
Output of /usr/share/bug/openscad:
$ glxinfo |grep 'OpenGL .* string:'
OpenGL vendor string: AMD
OpenGL renderer string: AMD Radeon RX 5700 XT (navi10, LLVM 15.0.7, DRM 3.52, 
6.4.0-4-amd64)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 23.1.6-1
OpenGL core profile shading language version string: 4.60
OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.1.6-1
OpenGL shading language version string: 4.60
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 23.1.6-1
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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 openscad depends on:
ii  lib3mf11.8.1+ds-4
ii  libboost-filesystem1.74.0  1.74.0+ds1-22
ii  libboost-program-options1.74.0 1.74.0+ds1-22
ii  libboost-regex1.74.0 [libboost-regex1.74.0-icu72]  1.74.0+ds1-22
ii  libc6  2.37-7
ii  libcairo2  1.17.8-3
ii  libdouble-conversion3  3.3.0-1
ii  libfontconfig1 2.14.2-5
ii  libfreetype6   2.13.2+dfsg-1
ii  libgcc-s1  13.2.0-2
ii  libgl1 1.6.0-1
ii  libglew2.2 2.2.0-4+b1
ii  libglib2.0-0   2.78.0-1
ii  libglu1-mesa [libglu1] 9.0.2-1.1
ii  libgmp10   2:6.3.0+dfsg-2
ii  libharfbuzz0b  8.0.1-1
ii  libmpfr6   4.2.0-1
ii  libopencsg11.5.0-1+b1
ii  libqscintilla2-qt5-15  2.14.1+dfsg-1
ii  libqt5core5a   5.15.10+dfsg-3
ii  libqt5dbus55.15.10+dfsg-3
ii  libqt5gamepad5 5.15.10-2
ii  libqt5gui5 5.15.10+dfsg-3
ii  libqt5multimedia5  5.15.10-2
ii  libqt5network5 5.15.10+dfsg-3
ii  libqt5widgets5 5.15.10+dfsg-3
ii  libspnav0  1.1-1
ii  libstdc++6 13.2.0-2
ii  libx11-6   2:1.8.6-1
ii  libxml22.9.14+dfsg-1.3
ii  libzip41.7.3-1+b1

Versions of packages openscad recommends:
ii  openscad-mcad  2019.05-1

Versions of packages openscad suggests:
pn  geomview  
pn  librecad  
pn  meshlab   
pn  openscad-testing  

-- no debconf information

Bug#1052590: argparse4j: FTBFS with default Java 21

[Vladimir Petko]

Source: argparse4j
Version: 0.4.4-1.1
Severity: normal
Tags: ftbfs
User: debian-j...@lists.debian.org
Usertags: default-java21
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainers,

The package argparse4j ftbfs with default Java 21.
The relevant part of the build log:
---
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.10.1:testCompile 
(default-testCompile) on project argparse4j: Compilation failure: Compilation 
failure: 
[ERROR] 
/<>/src/test/java/net/sourceforge/argparse4j/internal/ArgumentParserImplTest.java:[231,9]
 reference to assertEquals is ambiguous
[ERROR]   both method assertEquals(long,long) in org.junit.Assert and method 
assertEquals(java.lang.Object,java.lang.Object) in org.junit.Assert match
[ERROR] 
/<>/src/test/java/net/sourceforge/argparse4j/internal/ArgumentParserImplTest.java:[321,9]
 reference to assertEquals is ambiguous
[ERROR]   both method assertEquals(long,long) in org.junit.Assert and method 
assertEquals(java.lang.Object,java.lang.Object) in org.junit.Assert match
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: error: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US 
returned exit code 1
---


-- System Information:
Debian Release: bookworm/sid
  APT prefers lunar-updates
  APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), 
(100, 'lunar-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#1052589: apache-directory-server: FTBFS with default Java 21

[Vladimir Petko]

Source: apache-directory-server
Version: 2.0.0~M26-1
Severity: normal
Tags: ftbfs
User: debian-j...@lists.debian.org
Usertags: default-java21
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainers,

The package apache-directory-server ftbfs with default Java 21.
The relevant part of the build log:
---
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.10.1:compile (default-compile) 
on project apacheds-core: Compilation failure: Compilation failure: 
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[96,13]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.CertificateVersion)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[101,13]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.CertificateSerialNumber)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[105,13]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.CertificateAlgorithmId)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[118,13]
 cannot find symbol
[ERROR]   symbol:   method set(java.lang.String,sun.security.x509.X500Name)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[124,13]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.CertificateValidity)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[137,13]
 cannot find symbol
[ERROR]   symbol:   method set(java.lang.String,sun.security.x509.X500Name)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[143,13]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.CertificateX509Key)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[161,19]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.SubjectAlternativeNameExtension)
[ERROR]   location: variable extensions of type 
sun.security.x509.CertificateExtensions
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[165,19]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.BasicConstraintsExtension)
[ERROR]   location: variable extensions of type 
sun.security.x509.CertificateExtensions
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[168,13]
 cannot find symbol
[ERROR]   symbol:   method 
set(java.lang.String,sun.security.x509.CertificateExtensions)
[ERROR]   location: variable info of type sun.security.x509.X509CertInfo
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[197,36]
 no suitable constructor found for X509CertImpl(sun.security.x509.X509CertInfo)
[ERROR] constructor sun.security.x509.X509CertImpl.X509CertImpl(byte[]) is 
not applicable
[ERROR]   (argument mismatch; sun.security.x509.X509CertInfo cannot be 
converted to byte[])
[ERROR] constructor 
sun.security.x509.X509CertImpl.X509CertImpl(sun.security.util.DerValue) is not 
applicable
[ERROR]   (argument mismatch; sun.security.x509.X509CertInfo cannot be 
converted to sun.security.util.DerValue)
[ERROR] constructor 
sun.security.x509.X509CertImpl.X509CertImpl(java.io.InputStream) is not 
applicable
[ERROR]   (argument mismatch; sun.security.x509.X509CertInfo cannot be 
converted to java.io.InputStream)
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[198,20]
 cannot find symbol
[ERROR]   symbol:   method sign(java.security.PrivateKey,java.lang.String)
[ERROR]   location: variable certificate of type sun.security.x509.X509CertImpl
[ERROR] 
/<>/core/src/main/java/org/apache/directory/server/core/security/CertificateUtil.java:[229,36]
 no suitable constructor found for X509CertImpl(sun.security.x509.X509CertInfo)
[ERROR] constructor sun.security.x509.X509CertImpl.X509CertImpl(byte[]) is 
not applicable
[ERROR]   (argument mismatch; sun.security.x509.X509CertInfo cannot be 
converted to byte[])
[ERROR] constructor 
sun.security.x509.X509CertImpl.X509CertImpl(sun.security.util.DerValue) is not 
applicable
[ERROR]   

Bug#1052588: antlr3: FTBFS with default Java 21

[Vladimir Petko]

Source: antlr3
Version: 3.5.3-1
Severity: normal
Tags: ftbfs
User: debian-j...@lists.debian.org
Usertags: default-java21
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainers,

The package antlr3 ftbfs with default Java 21.
The relevant part of the build log:
---
# Build the Ant task
javac -source 7 -target 7 -encoding ISO-8859-1 -g -cp /usr/share/java/ant.jar 
antlr-ant/main/antlr3-task/antlr3-src/org/apache/tools/ant/antlr/ANTLR3.java
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
make: *** [debian/rules:39: common-post-build-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2
---


-- System Information:
Debian Release: bookworm/sid
  APT prefers lunar-updates
  APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), 
(100, 'lunar-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#1052587: altos: FTBFS with default Java 21

[Vladimir Petko]

Source: altos
Version: 1.9.15-1
Severity: normal
Tags: ftbfs
User: debian-j...@lists.debian.org
Usertags: default-java21
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainers,

The package altos ftbfs with default Java 21.
The relevant part of the build log:
---
make[3]: Entering directory '/<>/altoslib'
mkdir -p bin; CLASSPATH=bin /usr/lib/jvm/default-java/bin/javac -d bin -target 
1.7 -source 1.7 -encoding UTF-8 -Xlint:deprecation -Xlint:unchecked   
AltosLib.java AltosAccelCal.java AltosAccelCalListener.java AltosAdxl375.java 
AltosCalData.java AltosCompanion.java AltosConfigData.java 
AltosConfigDataException.java AltosConfigValues.java AltosConvert.java 
AltosCRCException.java AltosCSV.java AltosDebug.java AltosEeprom.java 
AltosRecordSet.java AltosEepromRecord.java AltosEepromRecordFull.java 
AltosEepromRecordTiny.java AltosEepromRecordMega.java 
AltosEepromRecordMetrum.java AltosEepromRecordMini.java 
AltosEepromRecordGps.java AltosEepromRecordFireTwo.java 
AltosEepromRecordMicroPeak2.java AltosEepromRecordMotor.java 
AltosEepromRecordSet.java AltosEepromChunk.java AltosEepromDownload.java 
AltosEepromMonitor.java AltosEepromFile.java AltosEepromList.java 
AltosEepromLog.java AltosFile.java AltosFilterListener.java AltosFlash.java 
AltosFlashListener.java AltosDataListener.java AltosDataProvider.java 
AltosFlightSeries.java AltosFlightReader.java AltosFlightStats.java 
AltosForce.java AltosFrequency.java AltosGPS.java AltosGPSTimeValue.java 
AltosGPSSat.java AltosGauss.java AltosGreatCircle.java AltosHexfile.java 
AltosHexsym.java AltosIdle.java AltosIdleFetch.java AltosIdleMonitor.java 
AltosIdleMonitorListener.java AltosIdleReader.java AltosIgnite.java 
AltosIMU.java AltosKML.java AltosLine.java AltosLink.java 
AltosListenerState.java AltosLog.java AltosLogTrace.java AltosMag.java 
AltosMma655x.java AltosMs5607.java AltosNoSymbol.java AltosOrient.java 
AltosParse.java AltosPressure.java AltosPresTemp.java AltosPreferences.java 
AltosPreferencesBackend.java AltosProgrammer.java AltosPyroName.java 
AltosReplayReader.java AltosRomconfig.java AltosSavedState.java 
AltosSelfFlash.java AltosUsbId.java AltosSensorMM.java AltosSensorEMini.java 
AltosSensorEasyTimer1.java AltosSensorTM.java AltosSensorTMini2.java 
AltosSensorTMini3.java AltosSensorMega.java AltosSensorMetrum.java 
AltosSensorTGPS1.java AltosSensorTGPS2.java AltosSensorTGPS3.java 
AltosSensorEasyMotor2.java AltosState.java AltosStateName.java 
AltosStringInputStream.java AltosTelemetry.java 
AltosTelemetryConfiguration.java AltosTelemetryCompanion.java 
AltosTelemetryFile.java AltosTelemetryIterable.java AltosTelemetryLegacy.java 
AltosTelemetryLocation.java AltosTelemetryMap.java 
AltosTelemetryMegaSensor.java AltosTelemetryMegaNorm.java 
AltosTelemetryMegaData.java AltosTelemetryMini2.java AltosTelemetryMini3.java 
AltosTelemetryMetrumSensor.java AltosTelemetryMetrumData.java 
AltosTelemetryReader.java AltosTelemetryRaw.java AltosTelemetrySensor.java 
AltosTelemetrySatellite.java AltosTelemetryStandard.java AltosTime.java 
AltosTimeSeries.java AltosTimeValue.java AltosUnitsListener.java 
AltosUnknownProduct.java AltosUnits.java AltosUnitsRange.java 
AltosDistance.java AltosHeight.java AltosSpeed.java AltosTemperature.java 
AltosAccel.java AltosVoltage.java AltosLocation.java AltosLatitude.java 
AltosLongitude.java AltosRotationRate.java AltosPyro.java AltosWriter.java 
AltosQuaternion.java AltosRotation.java AltosImage.java AltosLatLon.java 
AltosMap.java AltosMapCache.java AltosMapCacheListener.java 
AltosMapInterface.java AltosMapLine.java AltosMapMark.java AltosMapPath.java 
AltosMapPathPoint.java AltosMapRectangle.java AltosMapStore.java 
AltosMapStoreListener.java AltosMapTile.java AltosMapTileListener.java 
AltosMapTransform.java AltosMapZoomListener.java AltosPointDouble.java 
AltosPointInt.java AltosRectangle.java AltosFlightDisplay.java 
AltosFontListener.java AltosLaunchSite.java AltosLaunchSiteListener.java 
AltosLaunchSites.java AltosMapLoaderListener.java AltosMapLoader.java 
AltosMapTypeListener.java AltosJson.java AltosVersion.java AltosUnitInfo.java 
AltosUnitInfoListener.java
warning: [options] bootstrap class path not set in conjunction with -source 7
error: Source option 7 is no longer supported. Use 8 or later.
error: Target option 7 is no longer supported. Use 8 or later.
make[3]: *** [Makefile:523: classaltoslib.stamp] Error 2
make[3]: Leaving directory '/<>/altoslib'
make[2]: *** [Makefile:500: all-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:424: all] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:28: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Build finished at 2023-05-04T13:23:52Z
---


-- System Information:
Debian Release: bookworm/sid
  APT prefers lunar-updates
  APT policy: (500, 

Bug#1052586: aladin: FTBFS with default Java 21

[Vladimir Petko]

Source: aladin
Version: 12.001+dfsg-1
Severity: normal
Tags: ftbfs
Usertags: default-java21
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainers,

The package aladin ftbfs with default Java 21.
The relevant part of the build log:
---
[javac] /<>/cds/allsky/Task.java:96: error: Builder is a 
preview API and is disabled by default.
[javac]  builder = Builder.createBuilder(context,a);
[javac]^
[javac]   (use --enable-preview to enable preview APIs)
[javac] /<>/cds/allsky/Task.java:96: error: cannot find symbol
[javac]  builder = Builder.createBuilder(context,a);
[javac]   ^
[javac]   symbol:   method createBuilder(Context,Action)
[javac]   location: interface Builder
[javac] /<>/cds/allsky/Task.java:97: error: cannot find symbol
[javac]  builder.validateContext();
[javac] ^
[javac]   symbol:   method validateContext()
[javac]   location: variable builder of type Builder
[javac] /<>/cds/allsky/Task.java:98: error: cannot find symbol
[javac]  if( builder.isAlreadyDone() ) {
[javac] ^
[javac]   symbol:   method isAlreadyDone()
[javac]   location: variable builder of type Builder
[javac] /<>/cds/allsky/Task.java:105: error: cannot find symbol
[javac] if( !builder.isFake() ) {
[javac] ^
[javac]   symbol:   method isFake()
[javac]   location: variable builder of type Builder
[javac] /<>/cds/allsky/Task.java:106: error: cannot find symbol
[javac]builder.run();
[javac]   ^
[javac]   symbol:   method run()
[javac]   location: variable builder of type Builder
[javac] /<>/cds/allsky/Task.java:107: error: cannot find symbol
[javac]builder.showStatistics();
[javac]   ^
[javac]   symbol:   method showStatistics()
[javac]   location: variable builder of type Builder
[javac] /<>/cds/allsky/Task.java:148: error: cannot find symbol
[javac]if( now-lastStat>tempo && builder!=null ) { 
builder.showStatistics(); lastStat=now; }
[javac] 
  ^
[javac]   symbol:   method showStatistics()
[javac]   location: variable builder of type Builder
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files additionally use or override a deprecated 
API that is marked for removal.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 9 errors
[javac] 100 warnings
[javac] only showing the first 100 warnings, of 146 total; use -Xmaxwarns 
if you would like to see more

BUILD FAILED
/<>/build.xml:18: Compile failed; see the compiler error output 
for details.
---


-- System Information:
Debian Release: bookworm/sid
  APT prefers lunar-updates
  APT policy: (500, 'lunar-updates'), (500, 'lunar-security'), (500, 'lunar'), 
(100, 'lunar-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Bug#1042336: moment-timezone.js: FTBFS: cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or directory

[Martina Ferrari]

Sorry this took longer than expected. It turns out that the Ubuntu patch 
did not work, and it took me a while to find that many of the zone info 
symlinks had moved to tzdata-legacy.


I have not just uploaded the fixed package, finally.

On 13/09/2023 18:03, Martina Ferrari wrote:

Hi,

Thanks Daniel for spotting this, somehow I had missed all notifications 
and did not even realise Prometheus was about to be removed from testing :(


I have just ported the patch from Benjamin and after I finish building 
the package I will upload it.


On 10/09/2023 06:50, Daniel Swarbrick wrote:
On Wed, 26 Jul 2023 22:08:15 +0200 Lucas Nussbaum  
wrote:

 > Relevant part (hopefully):
 > > mkdir -p temp/zic/2023c temp/zdump/2023c
 > > cp -RL /usr/share/zoneinfo/posix/* temp/zic/2023c/
 > > cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or 
directory

 > > make[1]: *** [debian/rules:51: data/unpacked/2023c.json] Error 1

This appears to have broken due to a change in the tzdata package 
which landed in both Debian and Ubuntu[1].


The Ubuntu moment-timezone.js package was adapted[2] to accommodate 
this change, but the Debian package was not.


[1]: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2008076
[2]: 
https://git.launchpad.net/ubuntu/+source/moment-timezone.js/commit/debian?h=applied/ubuntu/lunar






--
Martina Ferrari (Tina)

Bug#1040901: Upcoming changes to Debian Linux kernel packages

[Bastian Blank]

Hi Ben

On Sun, Sep 24, 2023 at 06:05:09PM +0200, Ben Hutchings wrote:
> On Sun, 2023-09-24 at 15:01 +0200, Bastian Blank wrote:
> > The same upstream version in testing and backports will have the same
> > package name.
> This is not OK, because they will be incompatible on architectures
> supporting SB (and sometimes incompatible on others due to compiler
> differences or required config changes).

I don't know what you are talking about.  Those two packages have
different versions, so won't contain anything compatible.  It is the
same between 1.2.3-1 vs 1.2.3-2 and 1.2.3-1~bpo13+1 vs 1.2.3-1.

> If someone upgrades from stable + backports to testing, and has OOT
> modules:
> - With DKMS, will a rebuild be triggered if the linux-image package
>   name doesn't change?

The same as with a normal package upgrade, it will rebuilt against the
new version.  It just runs into the same version skew as everything
else.

> - With module-assistant, the new linux-image package will satisfy
>   dependencies of the old modules even though they are incompatible.

No, the two linux-image packages have different versions, so won't
satisfy the dependencies.

> > Multiple uploads of the same upstream version will have
> > the same package name, but those rarely happens.
> Those happen fairly often for urgent security updates.   

Right.  Maybe we need a manual or automatic override for this, we can do
a lot of things.

> > It will not longer be possible to reliably derive the package name from
> > kernel release (see above), as both values are not really related
> > anymore.
> Given all the drawbacks, I don't see the benefit of decoupling package
> names from release strings.
> In the same way that shared library packages must be renamed for every
> backward-incompatible ABI changes, I believe we should keep doing this
> for linux-image packages.

Noted, but I don't see a way to do that.  We can't map versions cleanly
into package names.  We have binNMU, which can't change package names,
so will already in violation of that.  And we already don't do that, see
that huge version ignore list.

Also the ABI in shared libraries is to have two independent updateable
identities.  Nothing is true in case of the kernel, it will just break
on every update of either side, which would be the equivalent of a =
dependency.  So no, shared libraries are not a good comparison.

> > ## Header and tool packages will not longer contain version
> > 
> > The headers packages will not longer include the version.  It won't be
> > reliably possible to derive the package name anyway from the running
> > kernel.
> >
> > This means that only headers of one single version can be available on
> > the system at one time.  This might be a bit inconvinient for dkms, as
> > it can't longer build modules for multiple versions.
> >
> > But we too often have the problem that image and headers go out of sync
> > and then you can't find the correct ones anyway.
> > 
> > Example: linux-headers-cloud-arm64
> 
> This is all downside with no justification given.  Please explain what
> the benefit is.

The current way does not work.  See all the bug reports about
uninstallable packages and what not with dkms.

To build modules against version x, you'll need to install version x of
the headers, not x-1 or x+1.  This currently works most of the time, but
is by far stable.  And if you already have to search for the specific
version, it does not matter if you might have the ability to install
multiple at the same time, the archive will in any case only contain one
version at a time.

IMHO the only way around would be to install image and headers always in
one piece for those who want to build own modules against.  But this
will require further restructuring, as the headers for this then need to
be built from linux-signed-* and arch-any to be without skew.  And
use proper dependencies so everything is installed with the same version
always.

Aka something like that:

Package: linux-image-cloud-arm64
Depends:
 linux-image-1.2.3-cloud-arm64 (= 1.2.3-1)

Package: linux-modules-thirdparty-cloud-arm64
Depends:
 linux-image-1.2.3-cloud-arm64 (= 1.2.3-1),
 linux-modules-1.2.3-cloud-arm64 (= 1.2.3-1),
 linux-headers-1.2.3-cloud-arm64 (= 1.2.3-1)

Package: linux-image-1.2.3-cloud-arm64
Depends: linux-modules-1.2.3-cloud-arm64 (= 1.2.3-1)

Package: linux-headers-1.2.3-cloud-arm64
Depends: linux-modules-1.2.3-cloud-arm64 (= 1.2.3-1)

Package: linux-modules-1.2.3-cloud-arm64

However doesn't building modules currently need the vmlinux as well?
Which would not be fullfiled anyway right now.

> > ## Installer packages will not longer contain too much version
> > 
> > The installer can only ever handle one version of kernel.  Also it got
> > an internal mechanism to detect which packages belong together
> > (the Kernel-Version control entry).  So we have no need to rename them
> > and force a matching change in d-i itself just because a new kernel
> > exists.  So it 

Bug#1052585: libc++1: Smooth upgrade with proper breaks version (-11 -> -14)

[Hideki Yamane]

Package: libc++1
Version: 1:14.0-55.7
Severity: normal
X-Debbugs-Cc: henr...@debian.org

Dear Maintainer,

 It seems that libc++ package should change its dependency version for
 smoooth upgrade.


--- control.old 2023-09-13 22:35:38.0 +0900
+++ control 2023-09-25 08:44:39.012538283 +0900
@@ -5,7 +5,7 @@
 Maintainer: LLVM Packaging Team 
 Installed-Size: 14
 Depends: libc++1-16 (>= 16~)
-Breaks: libc++1-11, libc++abi1-11
+Breaks: libc++1-14, libc++abi1-14
 Section: libs
 Priority: optional
 Multi-Arch: same


 With above changes, apt upgrade works smoothly :)


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

Kernel: Linux 6.4.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 libc++1 depends on:
ii  libc++1-14  1:14.0.6-16

libc++1 recommends no packages.

libc++1 suggests no packages.

-- no debconf information
--- control.old 2023-09-13 22:35:38.0 +0900
+++ control 2023-09-25 08:44:39.012538283 +0900
@@ -5,7 +5,7 @@
 Maintainer: LLVM Packaging Team 
 Installed-Size: 14
 Depends: libc++1-16 (>= 16~)
-Breaks: libc++1-11, libc++abi1-11
+Breaks: libc++1-14, libc++abi1-14
 Section: libs
 Priority: optional
 Multi-Arch: same

Bug#1052584: linux-image-6.5.0-1-amd64: NFS4 stopped working in 6.5 with SELinux error

[Michal Kaspar]

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

Dear Maintainer,
After upgrading to kernel version 6.5.0-1-amd64, the NFS4 stopped
working on the station. Whe trying to mount nf4 FS, the mount fails with
error:
mount.nfs: an incorrect mount option was specified for
The kernel log contains error message:
kernel: SELinux: Unable to set superblock options before the security 
server is initialized

This puzzles me a bit as I've got SELinux disabled (don't even have
SELinux userspace installed, /sys/fs/selinux/enforce says 0). Tried
booting with selinux=0 boot parameter but with the same result.
Rebooting wih previou (6.4.0-4-amd64) kernel version fixes the problem
immediately.

-- Package-specific info:
** Version:
Linux version 6.5.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-13 
(Debian 13.2.0-4) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP 
PREEMPT_DYNAMIC Debian 6.5.3-1 (2023-09-13)


** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.5.0-1-amd64 
root=UUID=66909970-fb76-4ca1-ac09-21ce627d56fb ro acpi_osi=Linux 
apparmor=0 quiet resume=UUID=83a4e08d-09cd-40d7-815f-060f24d8ed07


** Not tainted

** Kernel log:
[    4.333757] AVX2 version of gcm_enc/dec engaged.
[    4.333908] AES CTR mode by8 optimization enabled
[    4.335361] snd_hda_intel :34:00.1: enabling device ( -> 0002)
[    4.336166] snd_hda_intel :34:00.1: Handle vga_switcheroo audio 
client
[    4.336173] input: SYNA8018:00 06CB:CE67 Mouse as 
/devices/platform/AMDI0010:01/i2c-1/i2c-SYNA8018:00/0018:06CB:CE67.0001/input/input13
[    4.336314] input: SYNA8018:00 06CB:CE67 Touchpad as 
/devices/platform/AMDI0010:01/i2c-1/i2c-SYNA8018:00/0018:06CB:CE67.0001/input/input14
[    4.336456] hid-multitouch 0018:06CB:CE67.0001: input,hidraw0: I2C 
HID v1.00 Mouse [SYNA8018:00 06CB:CE67] on i2c-SYNA8018:00

[    4.336927] snd_hda_intel :34:00.6: enabling device ( -> 0002)
[    4.339656] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio 
is unblocked

[    4.346487] videodev: Linux video capture interface: v2.00
[    4.349686] thinkpad_acpi: rfkill switch tpacpi_wwan_sw: radio is 
unblocked
[    4.356589] snd_hda_intel :34:00.1: bound :34:00.0 (ops 
amdgpu_dm_audio_component_bind_ops [amdgpu])
[    4.366123] thinkpad_acpi: Standard ACPI backlight interface 
available, not loading native one
[    4.368909] input: HD-Audio Generic HDMI/DP,pcm=3 as 
/devices/pci:00/:00:08.1/:34:00.1/sound/card0/input16
[    4.369050] input: HD-Audio Generic HDMI/DP,pcm=7 as 
/devices/pci:00/:00:08.1/:34:00.1/sound/card0/input17
[    4.369175] input: HD-Audio Generic HDMI/DP,pcm=8 as 
/devices/pci:00/:00:08.1/:34:00.1/sound/card0/input18

[    4.378763] acp_yc_mach acp_yc_mach.0: Enabling ACP DMIC support via DMI
[    4.378827] acp_yc_mach acp_yc_mach.0: Enabling ACP DMIC support via DMI
[    4.414400] thinkpad_acpi: battery 1 registered (start 0, stop 100, 
behaviours: 0x7)

[    4.414423] ACPI: battery: new extension: ThinkPad Battery Extension
[    4.421306] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC257: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[    4.421312] snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[    4.421315] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)

[    4.421318] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
[    4.421320] snd_hda_codec_realtek hdaudioC1D0:    inputs:
[    4.421322] snd_hda_codec_realtek hdaudioC1D0:  Mic=0x19
[    4.421660] usb 5-1: Found UVC 1.10 device Integrated Camera (174f:1812)
[    4.429655] usb 5-1: Found UVC 1.50 device Integrated Camera (174f:1812)
[    4.431756] usbcore: registered new interface driver uvcvideo
[    4.451513] ath11k_pci :01:00.0: BAR 0: assigned [mem 
0x9880-0x989f 64bit]

[    4.451533] ath11k_pci :01:00.0: enabling device ( -> 0002)
[    4.451643] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input12

[    4.452347] ath11k_pci :01:00.0: MSI vectors: 32
[    4.452355] ath11k_pci :01:00.0: wcn6855 hw2.1
[    4.458975] NET: Registered PF_QIPCRTR protocol family
[    4.470682] input: HDA Digital PCBeep as 
/devices/pci:00/:00:08.1/:34:00.6/sound/card1/input19
[    4.470771] input: HD-Audio Generic Mic as 
/devices/pci:00/:00:08.1/:34:00.6/sound/card1/input20
[    4.470850] input: HD-Audio Generic Headphone as 
/devices/pci:00/:00:08.1/:34:00.6/sound/card1/input21

[    4.529613] Bluetooth: Core ver 2.22
[    4.529643] NET: Registered PF_BLUETOOTH protocol family
[    4.529645] Bluetooth: HCI device and connection manager initialized
[    4.529650] Bluetooth: HCI socket layer initialized
[    4.529656] Bluetooth: L2CAP socket layer initialized
[    4.529667] Bluetooth: SCO socket layer initialized
[    4.541302] kvm_amd: TSC scaling supported
[    4.541305] kvm_amd: Nested Virtualization enabled
[    4.541307] kvm_amd: Nested Paging enabled
[    4.541315] 

Bug#1020217: S3-backed snapshot implementation on AWS?

[Noah Meyerhans]

On Fri, Sep 22, 2023 at 05:12:21PM +0200, Bastian Blank wrote:
> > Could we use the Debian AWS account to host that service?
> 
> I would assume that a service like snapshot would be within the scope
> for our AWS usage.  Noah?

It makes sense and I will look into it.  Let's not start anything until
we hear definitive confirmation.  Do we have a sense of how much
outgoing traffic the current snapshot service generates?

> >   It would
> > require one fairly powerful VM, and a large S3 bucket (approximately
> > 150-200 TB).
> 
> 200 TB should be no problem.

Agreed.

> However we need to talk about that "one […] VM", because this sounds
> like you intend to use AWS as VM hosting, which it is not.
> 
> Please think about this in form of services and there should be at least
> two:
> - the injestor, which can only exist once and writes, and
> - the web frontend, which should be able to exist several times and only
>   reads.
> 
> So you want to plan with running the multiple web frontends with load
> balancers and maybe even cloudfront.

I agree that it would be best to design something more cloud-oriented.
However, if there's an existing infrastructure that can be moved as a
"lift & shift" into AWS now, with architectural refactoring happening
later, that's an OK place to start.

noah

Bug#1052420: bullseye-pu: package flameshot/0.9.0+ds1-2+deb11u1

[Boyuan Yang]

在 2023-09-24星期日的 19:09 +0100，Adam D. Barratt写道：
> On Sat, 2023-09-23 at 22:10 +0100, Adam D. Barratt wrote:
> > Control: tags -1 confirmed
> > 
> > On Thu, 2023-09-21 at 13:37 -0400, Boyuan Yang wrote:
> > > As reported in https://bugs.debian.org/1051408 , current flameshot
> > > in Debian 11 (Bullseye) will silently upload the current captured
> > > screenshot to imgur without confirmation whenever the corresponding
> > > hotkey is pressed. This imposes a security risk of leaking
> > > sensitive
> > > information.
> > > 
> > > In order to mitigate this issue, I propose to upload flameshot
> > > 0.9.0+ds1-2+deb11u1, which strips the embedded imgur token
> > > hardcoded
> > > in the source code. Users who wish to utilize the img uploading
> > > feature can fill in their own imgur token in flameshot config
> > > window to re-enable the feature.
> > > 
> > 
> > Please go ahead.
> > 
> 
> I should have spotted this before, but the news file in the source
> package should simply be named "debian/NEWS"; dh_installchangelogs will
> then install it as NEWS.Debian in the binary package.
> 
> It's up to you whether you want to upload a +deb11u2 that simply fixes
> that, or would prefer that we reject the existing upload and you can
> upload a fixed +deb11u1.

Thanks, I just uploaded a +deb11u2 to reflect this change.

Best,
Boyuan Yang


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

Bug#1041792: Revision 3.2.1-2

[Arthur Diniz]

Dear Maintainer,

I've worked on this package doing the following updates:

 * d/control:
  - Bump Standards-Version to 4.6.2.
  - Declare Vcs-* fields under debian salsa group.
  - Declare Rules-Requires-Root to no.
  - Replace debhelper with debhelper-compat.
  - Removed trailing whitespaces.
  * d/copyright:
  - Add Arthur Diniz.
  - Update format URL.
  * d/changelog: Removed trailing whitespaces.
  * d/compat: Removed.
  * d/patches: Patch to disable update checks. (Closes: #1041792)
  * d/upstream/metadata: Created.
  * d/gbp.conf: Created.

A repo has been created in Salsa: https://salsa.debian.org/debian/httpie

The package now can be cloned and tested.

I'm available for any extra fixes and/or updates before uploading.

The changelog is with the label UNRELEASED, if no changes required we can
just change to unstable and do the upload.

---

I'm currently seeking new packages to work and adopt, if you have plans to
orphan httpie I'm available.

Cheers,
Arthur Diniz

Bug#1052583: com-hypirion-io-clojure: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: com-hypirion-io-clojure
Version: 0.3.1-4
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


com-hypirion-io-clojure fails to build with OpenJDK 21 because it invokes javac
with the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  dpkg-buildpackage
  -
  
  Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
  dpkg-buildpackage: info: source package com-hypirion-io-clojure
  dpkg-buildpackage: info: source version 0.3.1-4
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Emmanuel Bourg 
   dpkg-source --before-build .
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with javahelper,jh_maven_repo_helper
 debian/rules override_jh_clean
  make[1]: Entering directory '/<>'
  jh_clean
  rm -f /<>/hypirion-io.jar
  rm -rf /<>/meta
  make[1]: Leaving directory '/<>'
 dh_clean
   debian/rules build
  dh build --with javahelper,jh_maven_repo_helper
 dh_update_autotools_config
 dh_autoreconf
 jh_linkjars
 debian/rules override_jh_build
  make[1]: Entering directory '/<>'
  jh_build --javacopts="-target 7 -source 7 -Xlint:-options" hypirion-io.jar src
  jh_build: warning: Java machine does not support --release 7, using --release 
8
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  jh_build: error: find src -name '*.java' -and -type f -print0 | xargs -s 
512000 -0 /usr/lib/jvm/default-java/bin/javac -g -cp 
:debian/_jh_build.hypirion-io -d debian/_jh_build.hypirion-io -target 7 -source 
7
   -Xlint:-options -encoding ISO8859-1  returned exit code 123
  make[1]: *** [debian/rules:16: override_jh_build] Error 25
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:13: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  

  Build finished at 2023-09-22T20:05:32Z

Bug#1052198: libvte-2.91-0: swallowed characters on libreadline editing

[Christoph Anton Mitterer]

On Thu, 2023-09-21 at 23:31 +0200, Egmont Koblinger wrote:
> VTE's emulation behavior didn't change recently. Bash/Readline could
> have changed, I don't know (might be interesting to check their
> Ubuntu
> packages' changelogs).

What I did notice that libvte and gnome-terminal packages were both
updated recently, and I think I gnome-terminal packages were only
updated a few days after.
But that still doesn't explain, why it suddenly happened with the old
libvte packages.


> Or you're executing somewhat different steps.
> 
> If the printed prompt is exactly the same (including all the bells
> and
> whistles that it prints, like the username, hostname, working
> directory, previous command's exit value, background job stuff), and
> the terminal width is exactly the same (is it?), and you're pressing
> the same keys to invoke the same previous commands or editing the
> current command in the exact same way, then you should see the exact
> same behavior. Any difference in any of these could make the bug
> appear or vanish.

At least I wouldn't be aware of doing anything differently.


> Also make sure that the previous command's output ended with a
> newline, that is, the prompt begins in the first column. Otherwise
> it's common to see misbehavior while editing.

That's clear, and that was definitely not the case.


> By now we are sure that we're talking about two separate issues. The
> line editing misbehavior is surely independent from Samuel's patch.

I guess so, too.



Thanks,
Chris.

Bug#1052582: nescc: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: nescc
Version: 1.3.5-1.1
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


nescc fails to build with OpenJDK 21 because it invokes javac with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  Making all in doc
  make[2]: Entering directory '/<>/doc'
  make[2]: Nothing to be done for 'all'.
  make[2]: Leaving directory '/<>/doc'
  Making all in tools
  make[2]: Entering directory '/<>/tools'
  Making all in java
  make[3]: Entering directory '/<>/tools/java'
  Making all in net
  make[4]: Entering directory '/<>/tools/java/net'
  Making all in tinyos
  make[5]: Entering directory '/<>/tools/java/net/tinyos'
  Making all in nesc
  make[6]: Entering directory '/<>/tools/java/net/tinyos/nesc'
  Making all in wiring
  make[7]: Entering directory 
'/<>/tools/java/net/tinyos/nesc/wiring'
  CLASSPATH=`cygpath -w ../../../.. 2>/dev/null || echo ../../../..` javac 
-source 1.7 -target 1.7 WiringCheck.java
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  make[7]: *** [Makefile:469: WiringCheck.class] Error 2

Bug#1052581: libmatthew-java: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: libmatthew-java
Version: 0.8.1-2
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


libmatthew-java fails to build with OpenJDK 21 because it invokes javac with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  dpkg-buildpackage
  -
  
  Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
  dpkg-buildpackage: info: source package libmatthew-java
  dpkg-buildpackage: info: source version 0.8.1-2
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Thorsten Alteholz 

   dpkg-source --before-build .
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with javahelper
 debian/rules override_dh_auto_clean
  make[1]: Entering directory '/<>'
  dh_auto_clean
  make -j8 clean
  make[2]: Entering directory '/<>'
  rm -rf classes doc
  rm -f .classes .enabledebug .disabledebug *.o *.so *.tar.gz *.jar *.cgi 
Manifest
  rm -rf libmatthew-java-0.8.1
  make[2]: Leaving directory '/<>'
  #rm -f cx/ath/matthew/debug/Debug.java
  make[1]: Leaving directory '/<>'
 jh_clean
 dh_clean
   debian/rules build
  dh build --with javahelper
 dh_update_autotools_config
 dh_autoreconf
 dh_auto_configure
 jh_linkjars
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/<>'
  /usr/bin/make JAVA_HOME=/usr/lib/jvm/default-java \
JAVAC=/usr/lib/jvm/default-java/bin/javac \
JAVAH=/usr/lib/jvm/default-java/bin/javah \
JAVADOC=/usr/lib/jvm/default-java/bin/javadoc \
JAVADOCFLAGS="-quiet -author -link 
/usr/share/doc/default-jdk-doc/api/" \
JVERCFLAGS="-source 1.7" \
JAR=/usr/bin/fastjar \
PREFIX=/usr \
all doc
  make[2]: Entering directory '/<>'
  mkdir -p classes
  /usr/bin/make .disabledebug
  make[3]: Entering directory '/<>'
  mkdir -p classes
  cpp  -C -P -DDEBUGSETTING=false < cx/ath/matthew/debug/Debug.jpp > 
cx/ath/matthew/debug/Debug.java
  /usr/lib/jvm/default-java/bin/javac -source 1.7  -cp classes -d classes 
cx/ath/matthew/debug/Debug.java cx/ath/matthew/utils/Hexdump.java
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  make[3]: *** [Makefile:110: .disabledebug] Error 2
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:54: .classes] Error 2
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:7: override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  

  Build finished at 2023-09-22T18:02:36Z

Bug#1052580: swi-prolog: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: swi-prolog
Version: 9.0.4+dfsg-2
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


swi-prolog fails to build with OpenJDK 21 because it invokes javac with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  [ 65%] Building Java objects for jpl_jar.jar
  cd /<>/packages/jpl/src/main/java && /usr/bin/cmake 
-DCMAKE_JAVA_CLASS_OUTPUT_PATH=/<>/build/packages/jpl/src/main/java/CMakeFiles/jpl_jar.dir
 -DCMAKE_JAR_CLASSES_PREFIX= -P /usr/sh
  are/cmake-3.27/Modules/UseJava/ClearClassFiles.cmake
  cd /<>/packages/jpl/src/main/java && /usr/bin/javac -source 7 
-target 7 -Xlint:-options -classpath 
:/<>/packages/jpl/src/main/java:/<>/build/packages/jpl/src/main/java
 -d /<>/build/packages/jpl/src/main/java/CMakeFiles/jpl_jar.dir 
@/<>/build/packages/jpl/src/main/java/CMakeFiles/jpl_jar.dir/java_sources
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.

Bug#967729: ripperx: depends on deprecated GTK 2

[tony mancill]

On Sun, Sep 24, 2023 at 12:53:01AM +0200, Bastian Germann wrote:
> I suggest removing ripperx in favour of grimripper.

Yes, given the state of ripperx upstream, I agree that this is a good
course of action.  I tested grimripper, and the functionality is nearly
identical.

I went ahead and filed a new wishlist bug against ripperx so we can
discuss the removal there.  Thank you for suggesting this.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052578

Regards,
tony

Bug#1052579: mate-utils: various memleaks resolved upstream

[Mike Gabriel]

Package: src:mate-utils
Severity: important
Version: 1.26.0-1

Various memory leaks have been resolved upstream. The fixes should be  
provided via a new upstream version upload + cherry-pickings to Debian  
bookworm.


See:
https://github.com/mate-desktop/mate-utils/commits/1.26
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpl1PusINiak.pgp
Description: Digitale PGP-Signatur

Bug#1052578: ripperx: proposed-removal in favor of grimripper

[tony mancill]

Source: ripperx
Version: 2.8.0-3
Severity: wishlist

Given the inactivity of the ripperx project upstream and the fact that
grimripper [1] is a suitable, modern replacement, I am filing this
proposed-removal bug for ripperx (as per [2]).  Thank you to Bastian
Germann for suggesting this [3].

If folks have suggestions regarding how we can help ripperx users find
the replacement, please provide feedback here.

In the meantime, I will upload a ripperx package with a NEWS file
suggesting that users install grimripper.  For the trixie release,
perhaps the ripperx package should be empty except for a manpage, the
NEWS file, and a Recommends in debian/control?

Thanks,
tony

[1] https://tracker.debian.org/pkg/grimripper
[2] https://wiki.debian.org/qa.debian.org/removals
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967729#12

Bug#1052577: bookworm-pu: package mate-notification-daemon/1.26.0-1+deb12u1

[Mike Gabriel]

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

This changeset fixes two memories in MATE's notification daemon.

[ Reason ]
Improve robustness of MATE desktop in Debian 12.

[ Impact ]
If not accepted, memory leaks continue to exist in core component of the
MATE desktop.

[ Tests ]
Local smoke tests. No regressions, so far. Patches have been cherry-picked
from upstream.

[ Risks ]
Regression may occur to users of the MATE desktop environment.

[ 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 ]

+  * debian/patches:
++ Add 1001_daemon-fix-memory-leak.patch and 
1002_mnd-daemon-fix-memory-leak.
+  patch. Fix two memory leaks in src/daemon/daemon.c and src/daemon/
+  mnd-daemon.c. (Closes: #1052565).

[ Other info ]
None.
diff -Nru mate-notification-daemon-1.26.0/debian/changelog 
mate-notification-daemon-1.26.0/debian/changelog
--- mate-notification-daemon-1.26.0/debian/changelog2021-12-11 
21:40:50.0 +0100
+++ mate-notification-daemon-1.26.0/debian/changelog2023-09-24 
23:40:09.0 +0200
@@ -1,3 +1,12 @@
+mate-notification-daemon (1.26.0-1+deb12u1) bookworm; urgency=medium
+
+  * debian/patches:
++ Add 1001_daemon-fix-memory-leak.patch and 
1002_mnd-daemon-fix-memory-leak.
+  patch. Fix two memory leaks in src/daemon/daemon.c and src/daemon/
+  mnd-daemon.c. (Closes: #1052565).
+
+ -- Mike Gabriel   Sun, 24 Sep 2023 23:40:09 +0200
+
 mate-notification-daemon (1.26.0-1) unstable; urgency=medium
 
   [ Martin Wimpress ]
diff -Nru 
mate-notification-daemon-1.26.0/debian/patches/1001_daemon-fix-memory-leak.patch
 
mate-notification-daemon-1.26.0/debian/patches/1001_daemon-fix-memory-leak.patch
--- 
mate-notification-daemon-1.26.0/debian/patches/1001_daemon-fix-memory-leak.patch
1970-01-01 01:00:00.0 +0100
+++ 
mate-notification-daemon-1.26.0/debian/patches/1001_daemon-fix-memory-leak.patch
2023-09-24 23:37:04.0 +0200
@@ -0,0 +1,26 @@
+From 954106793cfba1cc5bb3a740dd14373ff30ee14f Mon Sep 17 00:00:00 2001
+From: rbuj 
+Date: Sat, 23 Oct 2021 02:59:59 +0200
+Subject: [PATCH] daemon: fix memory leak
+
+---
+ src/daemon/daemon.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+--- a/src/daemon/daemon.c
 b/src/daemon/daemon.c
+@@ -1685,10 +1685,10 @@
+ {
+   notify_daemon_notifications_complete_get_server_information(object,
+   invocation,
+-  g_strdup("Notification Daemon"),
+-  g_strdup("MATE"),
+-  g_strdup(PACKAGE_VERSION),
+-  g_strdup("1.1"));
++  "Notification Daemon",
++  "MATE",
++  PACKAGE_VERSION,
++  "1.1");
+   return TRUE;
+ }
+ 
diff -Nru 
mate-notification-daemon-1.26.0/debian/patches/1002_mnd-daemon-fix-memory-leak.patch
 
mate-notification-daemon-1.26.0/debian/patches/1002_mnd-daemon-fix-memory-leak.patch
--- 
mate-notification-daemon-1.26.0/debian/patches/1002_mnd-daemon-fix-memory-leak.patch
1970-01-01 01:00:00.0 +0100
+++ 
mate-notification-daemon-1.26.0/debian/patches/1002_mnd-daemon-fix-memory-leak.patch
2023-09-24 23:38:22.0 +0200
@@ -0,0 +1,27 @@
+From 516275e2716ed5cbf8c1c52849fe04d934814791 Mon Sep 17 00:00:00 2001
+From: rbuj 
+Date: Thu, 21 Oct 2021 15:57:00 +0200
+Subject: [PATCH] mnd-daemon: fix memory leak
+
+---
+ src/daemon/mnd-daemon.c | 3 +++
+ 1 file changed, 3 insertions(+)
+
+--- a/src/daemon/mnd-daemon.c
 b/src/daemon/mnd-daemon.c
+@@ -63,12 +63,15 @@
+   error = NULL;
+   if (g_option_context_parse (context, argc, argv, ) == FALSE)
+   {
++  g_option_context_free (context);
+   g_warning ("Failed to parse command line arguments: %s", 
error->message);
+   g_error_free (error);
+ 
+   return FALSE;
+   }
+ 
++  g_option_context_free (context);
++
+   if (debug)
+   g_setenv ("G_MESSAGES_DEBUG", "all", FALSE);
+ 
diff -Nru mate-notification-daemon-1.26.0/debian/patches/series 
mate-notification-daemon-1.26.0/debian/patches/series
--- mate-notification-daemon-1.26.0/debian/patches/series   2021-12-11 
21:39:46.0 +0100
+++ mate-notification-daemon-1.26.0/debian/patches/series   2023-09-24 
23:35:13.0 +0200
@@ -1 +1,3 @@
 1000_add-AssumedAppArmorLabel.patch
+1001_daemon-fix-memory-leak.patch
+1002_mnd-daemon-fix-memory-leak.patch

Bug#1051125: RFS: a2d/2.0.0-1 [ITP] -- APRS to DAPNET portal

[Yogu NY3W]

Hi Boyuan,

Thank you for your valuable feedback on the a2d Debian package. I
appreciate your time and insights into the packaging process. Let me
address the points you've raised:


debian/a2d.init.d: You are absolutely right, I apologize for the oversight.
I've removed /usr/local/ and revised debian/a2d.init.d script.


/etc/nginx/ssl/: This empty directory is intended to be used by a2d to
store user SSL certificates and implement them for nginx. I understand your
concern, but this directory serves a purpose within the functionality of
the program.


/usr/share/scripts/: These scripts are simple helper scripts specific to
a2d. I believe that they should not be available globally like other system
scripts. Placing them in /usr/share/a2d/scripts/ could be better for
managing them.


Lintian Warnings: I have addressed the lintian warnings regarding the
skip-systemd-native-flag-missing-pre-depends in the package. Thank you for
pointing these out.


Thank you once again for your guidance and support. I look forward to your
response and any further suggestions you may have.


Best regards,

Yogeswaran.

Bug#1052576: clj-yaml-clojure: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: clj-yaml-clojure
Version: 0.7.2-1
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


clj-yaml-clojure fails to build with OpenJDK 21 because it invokes javac with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  dpkg-buildpackage
  -
  
  Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
  dpkg-buildpackage: info: source package clj-yaml-clojure
  dpkg-buildpackage: info: source version 0.7.2-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Jérôme Charaoui 
   dpkg-source --before-build .
  dpkg-buildpackage: info: host architecture amd64
   debian/rules clean
  dh clean --with javahelper --with maven_repo_helper
 jh_clean
 debian/rules execute_before_dh_clean
  make[1]: Entering directory '/<>'
  rm -f debian/maven-repo
  rm -f debian/pom.xml
  rm -Rf target
  make[1]: Leaving directory '/<>'
 dh_clean
   debian/rules binary
  dh binary --with javahelper --with maven_repo_helper
 dh_update_autotools_config
 dh_autoreconf
 debian/rules override_dh_auto_configure
  make[1]: Entering directory '/<>'
  cd debian && ln -sf /usr/share/maven-repo .
  make[1]: Leaving directory '/<>'
 jh_linkjars
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/<>'
  lein pom debian/pom.xml
  Wrote /<>/debian/pom.xml
  lein jar
  Compiling 1 source files to /<>/target/classes
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  Compilation of Java sources(lein javac) failed.
  make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:11: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  

  Build finished at 2023-09-22T21:44:04Z

Bug#1052575: jss: CVE-2022-4132

[Markus Koschany]

Package: jss
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for jss.

CVE-2022-4132[0]:
Tomcat: Memory leak in JSS


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-4132
https://www.cve.org/CVERecord?id=CVE-2022-4132

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



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

Bug#1052574: geotranz: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: geotranz
Version: 3.7-3
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


geotranz fails to build with OpenJDK 21 because it invokes javac with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  make makefile-build-indep-target
  make[1]: Entering directory '/<>'
  make -C GEOTRANS3/java_gui all
  make[2]: Entering directory '/<>/GEOTRANS3/java_gui'
  chmod 644 geotrans3/gui/icons/*.gif
  test -f Geotrans_orig.gif || { \
  cp geotrans3/gui/icons/Geotrans.gif Geotrans_orig.gif; \
  giftrans -t '#ced0ce' -o geotrans3/gui/icons/Geotrans.gif 
Geotrans_orig.gif; \
  }
  test -f Icon_orig.gif || { \
  cp geotrans3/gui/icons/Icon.gif Icon_orig.gif; \
  convert -shave 2x2 -scale 16x16 geotrans3/gui/icons/Geotrans.gif 
geotrans3/gui/icons/Icon.gif; \
  }
  test -f NGA_orig.gif || { \
  cp geotrans3/gui/icons/NGA.gif NGA_orig.gif; \
  giftrans -t '#ff' -o geotrans3/gui/icons/NGA.gif NGA_orig.gif; \
  }
  find geotrans3 -type f -name '*.java' > files
  /usr/lib/jvm/default-java/bin/javac -source 1.7 -target 1.7 @files
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  make[2]: *** [Makefile:11: compile] Error 2
  make[2]: Leaving directory '/<>/GEOTRANS3/java_gui'
  make[1]: *** [Makefile:7: makefile-build-indep-target] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:10: build-indep] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Bug#1052573: dicomscope: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: dicomscope
Version: 3.6.0-25
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


dicomscope fails to build with OpenJDK 21 because it invokes javac with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  cd /<>/tkgui && /usr/lib/jvm/default-java/bin/javac -encoding 
Latin1 -d ../DICOMscope -classpath . -source 1.7 -target 1.7 
dicomscope/DICOMscope.java
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  make[3]: *** [tkgui/CMakeFiles/dummy.dir/build.make:303: 
/<>/DICOMscope/DICOMscope.class] Error 2
  make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
  make[2]: *** [CMakeFiles/Makefile2:145: tkgui/CMakeFiles/dummy.dir/all] Error 
2
  make[2]: *** Waiting for unfinished jobs

Bug#1041441: Bug#1018206: luatex loses or changes text when discretionaries with priorities are used

[Preuße]

On 28.08.2023 21:59, Preuße...@buxtehude.debian.org, Hilmar wrote:

On 23.07.2023 23:21, Preuße...@buxtehude.debian.org, Hilmar wrote:


Hi Peter,

I've uploaded the revision -8 to unstable, which is a prereq for 
having a fix in bookworm. I've uploaded packages for bookworm to here 
[1]. Would be nice if you could patch your system and test them. At 
least your example is solved.


Hilmar

[1] https://freeshell.de/~hille42/1041441/



Ping...

I intend to push the fix to next point release, but I need to make sure 
it solves the issue in question.




Ping.

Hilmar



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1052572: hoteldruid: CVE-2023-43371 CVE-2023-43373 CVE-2023-43374 CVE-2023-43375 CVE-2023-43376 CVE-2023-43377

[Markus Koschany]

Package: hoteldruid
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for hoteldruid.

CVE-2023-43371[0]:
| Hoteldruid v3.0.5 was discovered to contain a SQL injection
| vulnerability via the numcaselle parameter at
| /hoteldruid/creaprezzi.php.


CVE-2023-43373[1]:
| Hoteldruid v3.0.5 was discovered to contain a SQL injection
| vulnerability via the n_utente_agg parameter at
| /hoteldruid/interconnessioni.php.


CVE-2023-43374[2]:
| Hoteldruid v3.0.5 was discovered to contain a SQL injection
| vulnerability via the id_utente_log parameter at
| /hoteldruid/personalizza.php.


CVE-2023-43375[3]:
| Hoteldruid v3.0.5 was discovered to contain multiple SQL injection
| vulnerabilities at /hoteldruid/clienti.php via the annonascita,
| annoscaddoc, giornonascita, giornoscaddoc, lingua_cli, mesenascita,
| and mesescaddoc parameters.


CVE-2023-43376[4]:
| A cross-site scripting (XSS) vulnerability in
| /hoteldruid/clienti.php of Hoteldruid v3.0.5 allows attackers to
| execute arbitrary web scripts or HTML via a crafted payload injected
| into the nometipotariffa1 parameter.


CVE-2023-43377[5]:
| A cross-site scripting (XSS) vulnerability in
| /hoteldruid/visualizza_contratto.php of Hoteldruid v3.0.5 allows
| attackers to execute arbitrary web scripts or HTML via a crafted
| payload injected into the destinatario_email1 parameter.


If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-43371
https://www.cve.org/CVERecord?id=CVE-2023-43371
[1] https://security-tracker.debian.org/tracker/CVE-2023-43373
https://www.cve.org/CVERecord?id=CVE-2023-43373
[2] https://security-tracker.debian.org/tracker/CVE-2023-43374
https://www.cve.org/CVERecord?id=CVE-2023-43374
[3] https://security-tracker.debian.org/tracker/CVE-2023-43375
https://www.cve.org/CVERecord?id=CVE-2023-43375
[4] https://security-tracker.debian.org/tracker/CVE-2023-43376
https://www.cve.org/CVERecord?id=CVE-2023-43376
[5] https://security-tracker.debian.org/tracker/CVE-2023-43377
https://www.cve.org/CVERecord?id=CVE-2023-43377

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



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

Bug#1052571: junit: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Package: junit
Version: 3.8.2-9
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


junit fails to build with OpenJDK 21 because it invokes javac with the 
source/target
options set to 7. Since OpenJDK 20 the minimum version supported is 8.


  make[1]: Leaving directory '/<>'
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/<>'
  mkdir -p classes
  (cd src;/usr/lib/jvm/default-java/bin/javac -source 1.7 -target 1.7 
-classpath . -d ../classes junit/*/*.java)
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  make[1]: *** [debian/rules:22: override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:15: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Bug#1052570: jlapack: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Source: jlapack
Version: 0.8~dfsg-5
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


jlapack fails to build with OpenJDK 21 because it invokes javac with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.


  mkdir -p simple/org/netlib/blas
  cp `find obj/org/netlib/blas -name "[A-Z][A-Z]*.java"` simple/org/netlib/blas
  javac -source 1.7 -target 1.7 -classpath 
.:blas.jar:simple:../../src/util/f2jutil.jar:../../src/error_reporting/xerbla.jar
 simple/org/netlib/blas/*.java
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  make[4]: [Makefile:13: blas.jar] Error 2 (ignored)
  cd simple; jar cvf ../blas_simple.jar `find . -name "*.class"`
  'c' flag requires manifest or input files to be specified!
  Try `jar --help' for more information.

Bug#1052569: apt-listchanges: --filter option can't possibly work

[Jonathan Kamens]

Package: apt-listchanges
Version: 3.27
Severity: normal

The --filter option to apt-listchanges (and the corresponding
configuration file system), which is intended to be used with the log
frontend, can't possibly work. It causes a crash with a traceback when
it is used because the code to implement uses methods that aren't
available on the class. I already know the fix -- adding a missing
mixin to the class definition -- and will be committing it when I have
salsa access, but I am filing this bug for the record so that others
can find it if necessary.

-- Package-specific info:
==> /etc/apt/listchanges.conf <==
[apt]
frontend=pager
which=news
email_address=root
email_format=text
confirm=false
headers=false
reverse=false
save_seen=/var/lib/apt/listchanges.db

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

Kernel: Linux 6.4.0-4-amd64 (SMP w/8 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 apt-listchanges depends on:
ii  apt2.7.3
ii  debconf [debconf-2.0]  1.5.82
ii  python33.11.4-5+b1
ii  python3-apt2.6.0
ii  python3-debconf1.5.82
ii  sensible-utils 0.0.20
ii  ucf3.0043+nmu1

apt-listchanges recommends no packages.

Versions of packages apt-listchanges suggests:
ii  chromium [www-browser]116.0.5845.140-1
ii  firefox-mozilla-build [www-browser]   117.0.1-0ubuntu1
ii  gnome-terminal [x-terminal-emulator]  3.49.99-1
ii  google-chrome-stable [www-browser]117.0.5938.92-1
ii  links [www-browser]   2.29-1
ii  lynx [www-browser]2.9.0dev.12-1
ii  postfix [mail-transport-agent]3.8.2-1
ii  python3-gi3.46.0-1
ii  w3m [www-browser] 0.5.3+git20230121-2

-- debconf information excluded

Bug#1052568: saaj: FTBFS with OpenJDK 21 due to security manager removal

[Emmanuel Bourg]

Source: saaj
Version: 1.4.0-3
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


saaj fails to build with OpenJDK 21 because the tests used the now deprecated 
security manager:


  [ERROR] Tests run: 30, Failures: 0, Errors: 15, Skipped: 0, Time elapsed: 
0.199 s <<< FAILURE! - in javax.xml.soap.test.SAAJFactoryTest
  [ERROR] testFactoryDiscoverySM[0](javax.xml.soap.test.SAAJFactoryTest)  Time 
elapsed: 0.024 s  <<< ERROR!
  java.lang.UnsupportedOperationException: The Security Manager is deprecated 
and will be removed in a future release
  at 
javax.xml.soap.test.SAAJFactoryTest.enableSM(SAAJFactoryTest.java:200)
  at 
javax.xml.soap.test.SAAJFactoryTest.testFactoryDiscoverySM(SAAJFactoryTest.java:193)

  [ERROR] testFactoryDiscoverySM[1](javax.xml.soap.test.SAAJFactoryTest)  Time 
elapsed: 0.002 s  <<< ERROR!
  java.lang.UnsupportedOperationException: The Security Manager is deprecated 
and will be removed in a future release
  at 
javax.xml.soap.test.SAAJFactoryTest.enableSM(SAAJFactoryTest.java:200)
  at 
javax.xml.soap.test.SAAJFactoryTest.testFactoryDiscoverySM(SAAJFactoryTest.java:193)

  [ERROR] testFactoryDiscoverySM[2](javax.xml.soap.test.SAAJFactoryTest)  Time 
elapsed: 0.001 s  <<< ERROR!
  java.lang.UnsupportedOperationException: The Security Manager is deprecated 
and will be removed in a future release
  at 
javax.xml.soap.test.SAAJFactoryTest.enableSM(SAAJFactoryTest.java:200)
  at 
javax.xml.soap.test.SAAJFactoryTest.testFactoryDiscoverySM(SAAJFactoryTest.java:193)

  [ERROR] testFactoryDiscoverySM[3](javax.xml.soap.test.SAAJFactoryTest)  Time 
elapsed: 0.002 s  <<< ERROR!
  java.lang.UnsupportedOperationException: The Security Manager is deprecated 
and will be removed in a future release
  at 
javax.xml.soap.test.SAAJFactoryTest.enableSM(SAAJFactoryTest.java:200)
  at 
javax.xml.soap.test.SAAJFactoryTest.testFactoryDiscoverySM(SAAJFactoryTest.java:193)

  [ERROR] testFactoryDiscoverySM[4](javax.xml.soap.test.SAAJFactoryTest)  Time 
elapsed: 0.002 s  <<< ERROR!
  java.lang.UnsupportedOperationException: The Security Manager is deprecated 
and will be removed in a future release
  at 
javax.xml.soap.test.SAAJFactoryTest.enableSM(SAAJFactoryTest.java:200)
  at 
javax.xml.soap.test.SAAJFactoryTest.testFactoryDiscoverySM(SAAJFactoryTest.java:193)

  [ERROR] testFactoryDiscoverySM[5](javax.xml.soap.test.SAAJFactoryTest)  Time 
elapsed: 0.002 s  <<< ERROR!
  java.lang.UnsupportedOperationException: The Security Manager is deprecated 
and will be removed in a future release
  at 
javax.xml.soap.test.SAAJFactoryTest.enableSM(SAAJFactoryTest.java:200)
  at 
javax.xml.soap.test.SAAJFactoryTest.testFactoryDiscoverySM(SAAJFactoryTest.java:193)

  [ERROR] testFactoryDiscoverySM[6](javax.xml.soap.test.SAAJFactoryTest)  Time 
elapsed: 0.002 s  <<< ERROR!
  java.lang.UnsupportedOperationException: The Security Manager is deprecated 
and will be removed in a future release
  at 
javax.xml.soap.test.SAAJFactoryTest.enableSM(SAAJFactoryTest.java:200)
  at 
javax.xml.soap.test.SAAJFactoryTest.testFactoryDiscoverySM(SAAJFactoryTest.java:193)

Bug#792577: mate-notification-daemon: Keep old notifications in pop-up menu until user deletes these

[Mike Gabriel]

Control: close -1
Control: tags -1 wontfix

Hi,

On  Do 16 Jul 2015 14:18:11 CEST, Marcos Schnalke wrote:


Package: mate-notification-daemon
Version: 1.8.0
Severity: wishlist

Dear Maintainer,

I'd suggest to add a functionality to the notification bar - similar  
to what other DEs such as Xfce and KDE have - so that one can review  
previous notifications until the user deletes those himself.
The reason for this request is simply that I'm using LinConnect to  
mirror my Android's notifications i.E. missed calls and SMS to my  
desktop but whenever I might receive important, it often still gets  
pass me because MATE by default won't save any notifications.


Possibly this behavior can be changed separtely via a settings  
window so users can decide what they want to keep and what not.


This functionality is available via ayatana-indicator-notifications.  
This can be used instead of MATE's notification daemon via the  
mate-indicator-applet.


As I don't see this feature being provided in  
mate-notification-daemon, I'll close this feature request. (Debian is  
not the right spot for feature requests, these need to be directed to  
the upstream developers of software, such as the MATE desktop).


light+love
Mike
--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgphdMMsX1SDD.pgp
Description: Digitale PGP-Signatur

Bug#853231: Please update xsensor to newer fork

[Bastian Germann]

Am 24.09.23 um 22:01 schrieb Ricardo Mones:

Mmm... Does it work? Last time I tried that fork it wasn't working very
well (compared to current version in Debian, that is).


Yes, it works well for me.

Bug#1052567: velocity-tools: FTBFS with OpenJDK 21 due to javadoc errors

[Emmanuel Bourg]

Source: velocity-tools
Version: 2.0-8
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


velocity-tools fails to build with OpenJDK 21 due to javadoc errors:


  [javadoc] Building index for all the packages and classes...
  [javadoc] Standard Doclet version 21+35-Debian-1
  [javadoc] Building tree for all the packages and classes...
  [javadoc] error: An internal exception has occurred.
  [javadoc] (java.lang.ClassCastException: class 
com.sun.tools.javac.code.Symtab$6 cannot be cast to class 
com.sun.tools.javac.code.Symbol$ClassSymbol (com.sun.tools.javac.code.Symtab$6 
and com.sun.tools
.javac.code.Symbol$ClassSymbol are in module jdk.compiler of loader 'app'))
  [javadoc] Please file a bug against the javadoc tool via the Java bug 
reporting page
  [javadoc] (https://bugreport.java.com) after checking the Bug Database 
(https://bugs.java.com)
  [javadoc] for duplicates. Include error messages and the following diagnostic 
in your report. Thank you.
  [javadoc] java.lang.ClassCastException: class 
com.sun.tools.javac.code.Symtab$6 cannot be cast to class 
com.sun.tools.javac.code.Symbol$ClassSymbol (com.sun.tools.javac.code.Symtab$6 
and com.sun.tools.java
c.code.Symbol$ClassSymbol are in module jdk.compiler of loader 'app')
  [javadoc] at 
jdk.compiler/com.sun.tools.javac.code.Symbol.outermostClass(Symbol.java:530)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.ToolEnvironment.getFileKind(ToolEnvironment.java:188)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable.isTypeElementSelected(ElementsTable.java:975)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable$IncludedVisitor.visitType(ElementsTable.java:1052)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable$IncludedVisitor.visitType(ElementsTable.java:1028)
  [javadoc] at 
jdk.compiler/com.sun.tools.javac.code.Symbol$ClassSymbol.accept(Symbol.java:1581)
  [javadoc] at 
java.compiler@21/javax.lang.model.util.AbstractElementVisitor6.visit(AbstractElementVisitor6.java:106)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.ElementsTable.isIncluded(ElementsTable.java:330)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.DocEnvImpl.isIncluded(DocEnvImpl.java:76)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.isIncluded(Utils.java:2015)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.hasHiddenTag(Utils.java:1272)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.getFirstVisibleSuperClass(Utils.java:1041)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.getFirstVisibleSuperClass(Utils.java:1055)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.Utils.getFirstVisibleSuperClassAsTypeElement(Utils.java:1017)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.ClassTree.processType(ClassTree.java:264)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.ClassTree.buildTree(ClassTree.java:245)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.util.ClassTree.(ClassTree.java:196)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:205)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.doclets.toolkit.AbstractDoclet.run(AbstractDoclet.java:110)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.doclet.StandardDoclet.run(StandardDoclet.java:104)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.Start.parseAndExecute(Start.java:575)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:398)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.Start.begin(Start.java:347)
  [javadoc] at 
jdk.javadoc/jdk.javadoc.internal.tool.Main.execute(Main.java:57)
  [javadoc] at jdk.javadoc/jdk.javadoc.internal.tool.Main.main(Main.java:46)
  [javadoc] 1 error
  [javadoc] 100 warnings

Bug#1043419: runit: ineffective trigger interest due to /usr-merge

[Helmut Grohne]

Hi Lorenzo,

On Sun, Sep 24, 2023 at 07:59:52PM +0200, Lorenzo wrote:
> I'm resending this to the bug as requested to have a public record; also
> I'm Cc Ian Jackson as he might already be working on this.

Thank you. Giving a more detailed reply now.

> Well yes, my problem is that I know for sure that there are runit-init
> users (especially downstream) that are hostile to usrmerge and are still
> running on unmerged systems on a "wait and see" basis.
> And if I understand correctly your usrmerge plan, there will be a
> *mandatory* file move so that everything will shipped under /usr and
> what they will "see" is that their system will fail to boot the hard
> way after /[s]bin is empty.

I think this is fairly accurate. I caution though that even what Ian
recently proposed to the CTTE entails moving all the files to /usr and
populating the currently aliased locations with symlinks.

> This makes me unhappy, and I'm trying to understand if and how it's
> possible for runit-init to still manage to reach at least an
> emergency shell[1] when boot is performed on an unmerged system.

I think I understand your point of view, but there is little I can and
want to do to support your cause here.

> I think I need to farm symlinks for selected binaries under /sbin and
> /bin; can runit-init package detect if a system is still unmerged and
> do some limited farming without becoming RC buggy?

What you want to do here very much seems like it does not belong into
any init system. In my view, runit-init should very much assume that
systems are merged. Imposing such triggers on every runit user seems
unreasonable to me. Having that functionality in an extra package (as
you explain later) is more debatable in my view.

If your triggers are only relevant for unmerged systems, then I suggest
that you simply close this bug, because you do not want to trigger on
/bin or /sbin. I'll have to add a note to dumat to stop reporting the
issue for runit-init.

> I think I need at least /sbin/init, /bin/sh and stuff inside /lib/init,
> /lib/lsb/; also, I'm not sure if runit C code will run without
> additional symlinks, I need to do some tests.

Very definitely, you also need /lib64/ld-linux-x86-64.so.2 on amd64.

> I still have to check if usrmerge will be broken by symlinks
> inside /[s]bin directories, and who knows how many other things..

As far as I understand it, we require that such compatibility symlinks
do not reside in a data.tar (policy requirement). Packages needing such
symlinks should add them via maintainer scripts. usrmerge has code to
explicitly handle such compatibility links, see
https://sources.debian.org/src/usrmerge/37/convert-usrmerge/#L173 where
it ignores them. So this aspect should be a non-problem.

Helmut

Bug#1043419: runit: ineffective trigger interest due to /usr-merge

[Helmut Grohne]

Hi Lorenzo,

On Sun, Sep 24, 2023 at 08:14:46PM +0200, Lorenzo wrote:
> > If doing this, your base-files-unmerged would have to declare
> > Replaces, Conflicts and Provides with base-files and fully replace its
> > functionality. Otherwise, it would cause a file conflict on /bin,
> > which will become a symbolic link in base-files. Alternatively, it
> > could install diversions for these locations to avoid that file
> > conflict scenario, but installing diversions for directories is not
> > supported by dpkg, so you have to go through some hoops to make it
> > work.
> 
> I assume you're saying such package, if properly done, will be allowed
> to exist in experimental/unstable.

I am not a gatekeeper of those suites and cannot make such a statement.
Declaring a conflict with an essential package definitely raises
eyebrows though and making apt install this is a non-trivial affair.
That said, the usrmerge package still violates assumptions of dpkg and
was/is allowed.

> > Furthermore, it should declare Breaks with systemd to avoid
> > being pulled into usual installations accidentally.
> 
> Isn't a Breaks with systemd-sysv enough? Is there a problem with
> debootstrap or similar tools?
> Declaring a Breaks with systemd will make it very hard to have an
> autopkgtest that runs automatically on salsa for this package..

The answer to this question is not obvious to me. Your reasoning makes
sense to me. On the flip side, systemd upstream will soon drop support
for split-/usr. If you were not declaring such Breaks, I'd assume that
systemd maintainers would want to declare the reverse Breaks having the
same effect.

The implications of continuing to maintain a split-/usr variant of
Debian are very unclear to me. I have not spent much thought on this and
my interest in doing so is fairly limited. That said, if you request
changes to DEP17 to make split-/usr easier, I'll be looking into their
feasibility.

Helmut

Bug#1052566: libnative-platform-java: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7

[Emmanuel Bourg]

Package: libnative-platform-java
Version: 0.14-5
Severity: important
Tags: ftbfs sid trixie
User: debian-j...@lists.debian.org
Usertags: default-java21


libnative-platform-java fails to build with OpenJDK 21 because it invokes javac 
with
the source/target options set to 7. Since OpenJDK 20 the minimum version
supported is 8.

Replacing the makefile with an Ant script would avoid this issue on future JDK 
upgrades.


  dpkg-buildpackage
  -
  
  Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
  dpkg-buildpackage: info: source package libnative-platform-java
  dpkg-buildpackage: info: source version 0.14-5
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Emmanuel Bourg 
   dpkg-source --before-build .
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with maven-repo-helper,javahelper
 debian/rules override_dh_auto_clean
  make[1]: Entering directory '/<>'
  dh_auto_clean
  rm -f -r debian/out
  make[1]: Leaving directory '/<>'
 jh_clean
 dh_clean
   debian/rules build
  dh build --with maven-repo-helper,javahelper
 dh_update_autotools_config
 dh_autoreconf
 jh_linkjars
 debian/rules override_dh_auto_build
  make[1]: Entering directory '/<>'
  mkdir --parents debian/tmp
  make -f debian/Makefile build
  make[2]: Entering directory '/<>'
  mkdir --parents debian/out/classes
  javac -source 1.7 -target 1.7 -encoding UTF-8 -d debian/out/classes -h 
debian/out src/main/java/net/rubygrapefruit/platform/Terminal.java ...
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  make[2]: *** [debian/Makefile:44: debian/out/classes/%.class] Error 2
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:8: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  

  Build finished at 2023-09-22T21:19:47Z

Bug#1050868: bookworm-pu: package debootstrap/1.0.128+nmu2+deb12u1

[Philip Hands]

Luca Boccassi  writes:

> On Sat, 23 Sept 2023 at 14:29, Simon McVittie  wrote:
>>
>> On Wed, 30 Aug 2023 at 16:27:12 +0100, Simon McVittie wrote:
>> > [ Reason ]
>> > Part of the transition to merged-/usr, and more specifically, allowing
>> > us to stop shipping files in trixie whose physical path on disk does
>> > not match their path in the dpkg database due to directory aliasing.
>> >
>> > This change needs to be in bookworm (and bullseye, and maybe buster)
>> > before that process can continue, because official buildds run debootstrap
>> > from stable (or older).
>> >
>> > I also took the opportunity to backport changes that make the autopkgtests
>> > pass.
>> >
>> > [ Impact ]
>> > If not accepted, trixie will continue to be stuck in a
>> > mostly-but-not-entirely merged-/usr limbo, with the moratorium from 
>> > #1035831
>> > remaining in place.
>>
>> I'm aware that we're getting close to the deadline for 12.2 and 11.8,
>> so I've uploaded the proposed version to bookworm-proposed-updates for
>> easier testing and review. Luca: the proposed version and a signed tag
>> are available from my fork on salsa (I am not able to push to the d-i
>> repository for debootstrap). I uploaded with dgit, so the git tree and
>> the .dsc have been verified to be identical.
>>
>> If this version is not accepted for whatever reason, then I think we
>> should treat version 1.0.128+nmu2+deb12u1 as having been used, and skip
>> ahead to 1.0.128+nmu2+deb12u2 for any subsequent bookworm update.
>> (And if there is a problem with having this version in bookworm-pu for
>> whatever reason, I'm happy to upload a +deb12u2 that is identical to
>> 1.0.128+nmu2 except for the changelog.)
>
> Thank you, pushed both branches.
>
> Release Team, we are aware that you requested an explicit review from
> D-I for this and #1025708, however there are no available reviewers,
> so it appears we are deadlocked. Would you please consider waiving
> this requirement to break the deadlock?
> Philip Hands has confirmed on Salsa that the change has been tested
> with OpenQA and everything still works:
> https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/105#note_429838

Just thought I'd mention that those tests were for current unstable.

As mentioned in:
  
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/105#note_430223
my attempts to test the same change in bullseye have not yet worked out,
because bullseye's D-I is missing the features that were recently added
to D-I in order to allow one to add a test repo from which D-I can
obtain modified udebs (such as debootstrap).

I'll ought to be able to sort out tweaked versions of net-retriever &
anne for bullseye, in which case a test should be possible.

I'm somewhat dubious that such a test is going to tell us anything
interesting though.

Cheers, Phil.
-- 
Philip Hands -- https://hands.com/~phil


signature.asc
Description: PGP signature

Bug#1052565: mate-notification-daemon: memory leaks in daemons

[Mike Gabriel]

Package: src:mate-notification-daemon
Severity: important
Version: 1.26.0-1
Forwarded: https://github.com/mate-desktop/mate-notification-daemon/pull/202
Forwarded: https://github.com/mate-desktop/mate-notification-daemon/pull/203

Two memory leaks have been resolved since mate-notification-daemon  
1.26.1. These patches should be cherry-picked to the bookworm version  
of mate-notification-daemon.



--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpghzysJt_Mn.pgp
Description: Digitale PGP-Signatur

Bug#1052564: bookworm-pu: package libmatemixer/1.26.0-2+deb12u1

[Mike Gabriel]

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

It has been reported that audio components using libmatemixer crash when
removable audio devices (such as USB audio devices) get removed from the
system.

[ Reason ]
Stabilize MATE's audio components, such as the volume applet.

[ Impact ]
If this will not be accepted, removal audio devices will cause MATE to
crash in its audio components when these devices get removed.

[ Tests ]
Manual tests. Patch has been cherry-picked from upstream.

[ Risks ]
MATE users will be affected, if the patch introduces regressions.

[ 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 ]

+  * debian/patches:
++ Add 0001_remove-weak-pointers-on-dispose.patch. Remove weak pointers on
+  dispose.
+  A weak pointer has a callback that will happily overwrite freed object
+  memory if the weakly referenced object outlives the object storing the
+  reference. Remove those callbacks when they are no longer needed.
+  This resolves heap corruptions / application crashes when removing audio
+  devices, such as USB audio devices. (Closes: #1052555).

[ Other info ]
None.
diff -Nru libmatemixer-1.26.0/debian/changelog 
libmatemixer-1.26.0/debian/changelog
--- libmatemixer-1.26.0/debian/changelog2021-12-13 17:25:45.0 
+0100
+++ libmatemixer-1.26.0/debian/changelog2023-09-24 22:10:12.0 
+0200
@@ -1,3 +1,16 @@
+libmatemixer (1.26.0-2+deb12u1) bookworm; urgency=medium
+
+  * debian/patches:
++ Add 0001_remove-weak-pointers-on-dispose.patch. Remove weak pointers on
+  dispose.
+  A weak pointer has a callback that will happily overwrite freed object
+  memory if the weakly referenced object outlives the object storing the
+  reference. Remove those callbacks when they are no longer needed.
+  This resolves heap corruptions / application crashes when removing audio
+  devices, such as USB audio devices. (Closes: #1052555).
+
+ -- Mike Gabriel   Sun, 24 Sep 2023 22:10:12 +0200
+
 libmatemixer (1.26.0-2) unstable; urgency=medium
 
   * debian/rules:
diff -Nru 
libmatemixer-1.26.0/debian/patches/0001_remove-weak-pointers-on-dispose.patch 
libmatemixer-1.26.0/debian/patches/0001_remove-weak-pointers-on-dispose.patch
--- 
libmatemixer-1.26.0/debian/patches/0001_remove-weak-pointers-on-dispose.patch   
1970-01-01 01:00:00.0 +0100
+++ 
libmatemixer-1.26.0/debian/patches/0001_remove-weak-pointers-on-dispose.patch   
2023-09-24 22:07:14.0 +0200
@@ -0,0 +1,152 @@
+From d0c6df12a42e2339d323048ff51ae25eea1a3c07 Mon Sep 17 00:00:00 2001
+From: Adric Blake 
+Date: Fri, 1 Sep 2023 21:30:19 -0400
+Subject: [PATCH] Remove weak pointers on dispose
+
+A weak pointer has a callback that will happily overwrite freed object memory 
if the weakly referenced object outlives the object storing the reference. 
Remove those callbacks when they are no longer needed.
+---
+ libmatemixer/matemixer-device-switch.c  | 17 +
+ libmatemixer/matemixer-stream-control.c | 15 +++
+ libmatemixer/matemixer-stream-switch.c  | 17 +
+ libmatemixer/matemixer-stream.c |  4 
+ 4 files changed, 53 insertions(+)
+
+diff --git a/libmatemixer/matemixer-device-switch.c 
b/libmatemixer/matemixer-device-switch.c
+index 51e946e..a8fa18c 100644
+--- a/libmatemixer/matemixer-device-switch.c
 b/libmatemixer/matemixer-device-switch.c
+@@ -53,6 +53,8 @@ static void mate_mixer_device_switch_set_property (GObject   
 *o
+const GValue   
*value,
+GParamSpec 
*pspec);
+ 
++static void mate_mixer_device_switch_dispose  (GObject
*object);
++
+ G_DEFINE_ABSTRACT_TYPE_WITH_PRIVATE (MateMixerDeviceSwitch, 
mate_mixer_device_switch, MATE_MIXER_TYPE_SWITCH)
+ 
+ static void
+@@ -61,6 +63,7 @@ mate_mixer_device_switch_class_init 
(MateMixerDeviceSwitchClass *klass)
+ GObjectClass *object_class;
+ 
+ object_class = G_OBJECT_CLASS (klass);
++object_class->dispose  = mate_mixer_device_switch_dispose;
+ object_class->get_property = mate_mixer_device_switch_get_property;
+ object_class->set_property = mate_mixer_device_switch_set_property;
+ 
+@@ -143,6 +146,20 @@ mate_mixer_device_switch_init (MateMixerDeviceSwitch 
*swtch)
+ swtch->priv = mate_mixer_device_switch_get_instance_private (swtch);
+ }
+ 
++static void
++mate_mixer_device_switch_dispose (GObject *object)
++{
++MateMixerDeviceSwitch *swtch;
++
++swtch = MATE_MIXER_DEVICE_SWITCH (object);
++
++if 

Bug#1052563: RFS: streamlink/6.2.0-1~bpo12+1 -- CLI for extracting video streams from various websites to a video player

[Alexis Murzeau]

Package: sponsorship-requests
Severity: wishlist
X-Debbugs-CC: debian-backpo...@lists.debian.org

Dear mentors,

I am looking for a sponsor for my package "streamlink" into Debian
bookworm-backports repository.

* Package name: streamlink
  Version : 6.2.0-1~bpo12+1
  Upstream Author : Streamlink Team
* URL : https://streamlink.github.io/
* License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
  Section : python

It builds those binary packages:

 python3-streamlink - Python module for extracting video streams from 
various websites
 streamlink - CLI for extracting video streams from various websites to a 
video player

To access further information about this package, please visit the
following URL:
 https://mentors.debian.net/package/streamlink


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

 dget -x 
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_6.2.0-1~bpo12+1.dsc



Differences from testing package (6.2.0-1):
  * d/control,rules: remove doc package because of missing dependencies
on bookworm.
  * d/patches: remove webbrowser tests which require pytest-trio which
is not available on bookworm.



Changes since the stable version in bookworm (5.2.1-1) (streamlink not
yet backported):

streamlink (6.2.0-1~bpo12+1) bookworm-backports; urgency=medium

  * Rebuild for bookworm-backports.
  * d/control,rules: remove doc package because of missing dependencies
on bookworm.
  * d/patches: remove webbrowser tests which require pytest-trio which
is not available on bookworm.

 -- Alexis Murzeau   Fri, 22 Sep 2023 00:02:09 +0200

streamlink (6.2.0-1) unstable; urgency=medium

  * New upstream version 6.2.0
  * d/patches: update patches

 -- Alexis Murzeau   Thu, 21 Sep 2023 19:54:32 +0200

streamlink (6.1.0-1) unstable; urgency=medium

  * d/clean: remove docs/_build directory (Closes: 1045365)
  * d/source/options: add extend-diff-ignore to fix dpkg-source failure
due to local changes (python package metadata regeneration)
  * New upstream version 6.1.0
  * d/patches: fix screenshot link for Streamlink Twitch GUI

 -- Alexis Murzeau   Sun, 20 Aug 2023 12:12:58 +0200

streamlink (6.0.1-1) unstable; urgency=medium

  * New upstream version 6.0.1
  * d/upstream/signing-key.asc: update upstream key
  * d/patches: update patches
  * d/control: add new dependency python3-pytest-trio
  * d/rules: streamlink manpage: use CW font instead of C
  * d/rules: remove unused inclusion of pkg-info.mk
  * d/rules: fix duplicate doc assets
  * d/control: remove depends on rtmpdump and add trio and typing-extensions
  * d/copyright: add src/streamlink/webbrowser/cdp/connection.py
  * Upload to unstable

 -- Alexis Murzeau   Wed, 09 Aug 2023 20:07:05 +0200

streamlink (5.5.1-1~exp1) experimental; urgency=medium

  * New upstream version 5.5.1
  * d/patches: update patches
  * d/patches,control: use furo theme instead of sphinx-rtd-theme
  * d/patches,control: use fork-awesome as a replacement for font-awesome
  * d/s/lintian-overrides: remove obsolete override about a test file

 -- Alexis Murzeau   Sat, 20 May 2023 19:52:43 +0200

Regards,
--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F|

Bug#967455: granule: depends on deprecated GTK 2

[Barak A. Pearlmutter]

Yeah, I'll do that: flush the package, with a parting recommendation
on mnemosyne.

Bug#853231: Please update xsensor to newer fork

[Ricardo Mones]

Hi Bastian,

Wasn't aware you were interested in xsensors, glad to know!

On Sat, 23 Sep 2023 15:49:56 +0200
Bastian Germann  wrote:

> I am uploading a LowNMU to DELAYED/10 to fix this.
> The GitHub generated tarball is used because autoreconf is run anyway.
> The debdiff is attached.

Mmm... Does it work? Last time I tried that fork it wasn't working very
well (compared to current version in Debian, that is).

regards,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «You teach best what you most need to learn.»

Bug#1049974: Bug#1052543: plasma-workspace 5.27.5-2+deb12u1 flagged for acceptance

[Adam D. Barratt]

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

Re-sending to the right bug...

On Sun, 2023-09-24 at 19:38 +, Adam D Barratt wrote:
> package release.debian.org
> tags 1052543 = bookworm pending
> thanks
> 
> Hi,
> 
> The upload referenced by this bug report has been flagged for
> acceptance into the proposed-updates queue for Debian bookworm.
> 
> Thanks for your contribution!
> 
> Upload details
> ==
> 
> Package: plasma-workspace
> Version: 5.27.5-2+deb12u1
> 
> Explanation: fix crash in krunner
> 
> 

Bug#1052562: ITP: eza -- Modern replacement for ls

[Sylvestre Ledru]

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

* Package name: eza
* URL : https://github.com/eza-community/eza
* License : MIT

it is a replacement of exa (dead upstream).
it will break/replace it.

 exa is an improved file lister with more features and better defaults.
 It uses colours to distinguish file types and metadata. It knows about
 symlinks, extended attributes, and Git. And it’s small, fast, and just
 one single binary.

Bug#1052552: libapache-mod-jk 1.2.48-1+deb11u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: libapache-mod-jk
Version: 1.2.48-1+deb11u1

Explanation: remove implicit mapping functionality, which could lead to 
unintended exposure of the status worker and/or bypass of security constraints 
[CVE-2023-41081]

Bug#1052150: openssh 8.4p1-5+deb11u2 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: openssh
Version: 8.4p1-5+deb11u2

Explanation: fix remote code execution issue via a forwarded agent socket 
[CVE-2023-38408]

Bug#1050332: inetutils 2.0-1+deb11u2 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: inetutils
Version: 2.0-1+deb11u2

Explanation: check return values for set*id() functions, avoiding potential 
security issues [CVE-2023-40303]

Bug#1042057: pandoc 2.9.2.1-1+deb11u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: pandoc
Version: 2.9.2.1-1+deb11u1

Explanation: fix arbitrary file write issues [CVE-2023-35936 CVE-2023-38745]

Bug#1052543: plasma-workspace 5.27.5-2+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: plasma-workspace
Version: 5.27.5-2+deb12u1

Explanation: fix crash in krunner

Bug#1052543: plasma-framework 5.103.0-1+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: plasma-framework
Version: 5.103.0-1+deb12u1

Explanation: fix plasmashell crashes

Bug#1052149: openssh 9.2p1-2+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: openssh
Version: 9.2p1-2+deb12u1

Explanation: fix remote code execution issue via a forwarded agent socket 
[CVE-2023-38408]

Bug#1051594: samba 4.17.11+dfsg-0+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: samba
Version: 4.17.11+dfsg-0+deb12u1

Explanation: new upstream stable release

Bug#1051171: qtlocation-opensource-src 5.15.8+dfsg-3+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: qtlocation-opensource-src
Version: 5.15.8+dfsg-3+deb12u1

Explanation: fix freeze when loading map tiles

Bug#1052479: lxc 5.0.2-1+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: lxc
Version: 5.0.2-1+deb12u1

Explanation: fix nftables syntax for IPv6 NAT

Bug#1052070: mutt 2.2.12-0.1~deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: mutt
Version: 2.2.12-0.1~deb12u1

Explanation: new upstream stable release

Bug#1052553: libapache-mod-jk 1.2.48-2+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: libapache-mod-jk
Version: 1.2.48-2+deb12u1

Explanation: remove implicit mapping functionality, which could lead to 
unintended exposure of the status worker and/or bypass of security constraints 
[CVE-2023-41081]

Bug#1052007: lxcfs 5.0.3-1+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: lxcfs
Version: 5.0.3-1+deb12u1

Explanation: fix CPU reporting within an arm32 container with large numbers of 
CPUs

Bug#1051302: jekyll 4.3.1+dfsg-3+deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: jekyll
Version: 4.3.1+dfsg-3+deb12u1

Explanation: support YAML aliases

Bug#1050997: lemonldap-ng 2.16.1+ds-deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: lemonldap-ng
Version: 2.16.1+ds-deb12u1

Explanation: 

Bug#1042903: firewalld 1.3.3-1~deb12u1 flagged for acceptance

[Adam D Barratt]

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

Hi,

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

Thanks for your contribution!

Upload details
==

Package: firewalld
Version: 1.3.3-1~deb12u1

Explanation: don't mix IPv4 and IPv6 addresses in a single nftables rule

Bug#1052561: bookworm-pu: package nfdump/1.7.3-1 (pre-discussion)

[Bernhard Schmidt]

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

[ Reason ]
I am proposing updating updating the nfdump package to a new _upstream_ release
in bookworm.

I made the judgement to switch to the new nfdump 1.7 series in the bookworm
release cycle. This has turned out to be premature. The 1.7.1 release we
shipped in bookworm was under rapid development.

One of the most popular applications for nfdump is to run it together with
nfsen, a PHP based webfrontend to collect and analyze netflows. This one also
has been under rapid development during the bookworm freeze.

It turns out that at least in some cases nfdump does not work well with recent
nfsen versions, see Bug#1042535. The likely commit has been identified, but it
was impossible to backport it due to the major source restructuring nfdump
1.7.x went through. Between 1.7.1 and 1.7.3 there were 169 commits, with bugfix
commits touching core parts of the code.

Things however appear to have stabilized now. The 1.7.3 release is a couple of
weeks old, with no bad bug reports appearing. It has been tested both by the
reporter of Bug#1042535 and by me, and it fixes all known errors with nfdump
1.7.x.

Therefor I'd like to update nfdump in bookworm from 1.7.1 to 1.7.3, same as in
testing.

The alternative would be to use backports to provide a better nfdump version
for bookworm users, but in this case I'm sure that 1.7.3 would be the better
fit for all users. If you reject updating to 1.7.3 I will do this instead.

I'm open to uploading that into -proposed early after the next point release to
give it the maximum possible coverage.

[ Impact ]
Users using nfsen (a popular framework for nfsen) will not get usable profiles.

[ Tests ]
There is an upstream testsuite ran during build, but this did not detect the
nfprofile issue earlier.

[ Risks ]
New upstream version always carries some risk, but the package is low popcon
and most of the times used with nfsen. Which is from the same author who
heartily recommends the latest 1.7.3

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

[ Changes ]
169 upstream commits.

[ Other info ]
I did not attach the debdiff because it would be too large and only consist
of upstream changes. No changes to debian/ (except dropping a backported fix
already in 12.1) are necessary.

Bug#1052560: ITP: zsh-antidote -- ZSH plugin manager

[Michael Fladischer]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: zsh-antidote
  Version : 1.9.2
  Upstream Contact: Matt McElheny
* URL : https://github.com/mattmc3/antidote
* License : Expat
  Programming Lang: Shell
  Description : ZSH plugin manager

 Antidote is a feature-complete Zsh implementation of the legacy Antibody plugin
 manager, which in turn was derived from Antigen. Antidote not only aims to
 provide continuity for those legacy plugin managers, but also to delight new
 users with high-performance, easy-to-use Zsh plugin management.

-BEGIN PGP SIGNATURE-

iQFPBAEBCgA5FiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmUQhvUbHGZsYWRpc2No
ZXJtaWNoYWVsQGZsYWRpLmF0AAoJEP/TyIuZfdFqMjAH+wZrZwc18FWvmN4LTrgH
f81xMrc8IgxkxHq8V6QV+s/eXWkEx/PKqZ7bTTa4+Nl6cCDF4rdJ7LUH1tpw8biE
znLKt3PJyU3lOelqMib3dL/G46Rcn2Lc3jpw3jZ3VkD5b4AX7Ia4OplpwRuNJw6x
ovBmIti9/nY9mPJYNHRbhLsYRnGbX/8Q3yNiRgNS5iAXzurJwbyC0eqS0A1EP3Xf
zRJfYBZyBkrcsfByiBx4KhTpAZ26FHAQKqRkxHsxLz5w07srJyRAEYC6X6rGdmG+
BSKpBZulvcBRmBYuRNBBoSt73yYkTuK/OTKGnZihmxBlXQ0nJGVYyR4ZsuvHzCRs
ycw=
=hJ3L
-END PGP SIGNATURE-

Bug#1052559: No uploader

[Bastian Germann]

Am 24.09.23 um 21:15 schrieb Ben Tris:

Is it possible that I close the bug by just sending an empty message to 
1052559-d...@bugs.debian.org


Yes.

Bug#1052559: No uploader

[Ben Tris]

Bastian Germann schreef op zo 24-09-2023 om 20:45 [+0200]:
> Am 24.09.23 um 20:39 schrieb Ben Tris:
> > I think this counts also in this case?
> > 
> > There is no uploader at this moment, it is required in this case I
> > think.
> > 
> > Debian Policy Manual, Release 4.6.2.0
> > 3.3 The maintainer of a package
> > 
> > If the maintainer of the package is a team of people with a shared
> > email
> > address, the Uploaders control field must be
> > present and must contain at least one human with their personal
> > email address.
> 
> There was no upload that removed me from Uploaders.
> The next upload should be a QA upload that also sets the Maintainer
> field to the usual QA value.

OK, so I guess I did better not make this bugreport. Then I guess this
bug report can be closed? Is it possible that I close the bug by just
sending an empty message to 1052559-d...@bugs.debian.org

Bug#1052107: gnome-shell-extension-shortcuts: needs update for GNOME Shell 45

[Jeremy Bícha]

Control: tags -1 fixed-upstream

This issue has been fixed in the new upstream version 1.4.1

Thank you,
Jeremy Bícha

Bug#1049955: bookworm-pu: package qemu/1:7.2+dfsg-7+deb12u2

[Михаил Токарев]

24.09.2023 19:43, Adam D. Barratt:

On Sun, 2023-09-24 at 06:52 +0300, Michael Tokarev wrote:

..

Will it be easier to upload the reviewed 7.2+dfsg-7+deb12u2 (based on
7.2.5) and close this bug#, and later make 7.2+dfsg-7+deb12u3 (based
on 7.2.6), or update current bug# with new release?

I guess it's better to do it step by step, closing this bug# and
filing a new one.


That might depend when you expect to be ready with the newer update.

The window for 12.2 closes next weekend, so if you'd rather have more
time to test and work on the 7.2.6 update, it would make sense to
upload the 7.2.5-based update for 12.2, and then the newer update for
12.3.


Well, the packages are ready now, and sure thing I know about the
timeline for 12.2.  But the thing is that besides the security fix
(for a class of issues), there's nothing really urgent there.
Instead, I'll propose qemu version 7.2.1234 for debian 12.3 :)

Thank you,

/mjt

Bug#1052111: gnome-shell-extension-weather: needs update for GNOME Shell 45

[Jeremy Bícha]

Control: forwarded -1 https://gitlab.com/skrewball/openweather/-/issues/81
Control: severity -1 serious

Our current upstream archived this project after it was requested to
port the extension to GNOME Shell 45

Thank you,
Jeremy Bícha

Bug#1052096: gnome-shell-extension-flypie: needs update for GNOME Shell 45

[Jeremy Bícha]

Control: tags -1 fixed-upstream

This is fixed in the upstream version v24

Thank you,
Jeremy Bícha

Bug#1052091: gnome-shell-extension-caffeine: needs update for GNOME Shell 45

[Jeremy Bícha]

I noticed that upstream released v49 as a final GNOME Shell 44 version
(at least I expect that it will be for Debian). It changed the build
system to use /usr/bin/gnome-extensions so I'll let you handle that
update.

There is also a new v50 for GNOME Shell 45

Thank you,
Jeremy Bícha

Bug#962968:

[Erik Huelsmann]

> So, ldapsearch and the python script appear to connect with "sasl_ssf=256
ssf=256" but the Perl script connects with "sasl_ssf=1 ssf=256". Why?

The cause lies in this section of the code base:
https://metacpan.org/release/EHUELS/Authen-SASL-2.1700/source/lib/Authen/SASL/Perl/GSSAPI.pm#L140-146
which says:

# set SSF property; if we have just integrity protection SSF is set
# to 1. If we have confidentiality, SSF would be an estimate of the
# strength of the actual encryption ciphers in use which is not
# available through the GSSAPI interface; for now just set it to
# the lowest value that signifies confidentiality.
$self->property(ssf => (($choice & 4) ? 2 : 1));

It would be absolutely perfect to get a patch to address this issue. I'd be
happy to include. Please forward the bug upstream (
https://github.com/gbarr/perl-authen-sasl) so others can learn about this
problem and/or contribute to the solution.

Thanks for reporting!


Regards,
-- 
Bye,

Erik.

http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.

Bug#1052559: No uploader

[Bastian Germann]

Am 24.09.23 um 20:39 schrieb Ben Tris:

I think this counts also in this case?

There is no uploader at this moment, it is required in this case I think.

Debian Policy Manual, Release 4.6.2.0
3.3 The maintainer of a package

If the maintainer of the package is a team of people with a shared email
address, the Uploaders control field must be
present and must contain at least one human with their personal email address.


There was no upload that removed me from Uploaders.
The next upload should be a QA upload that also sets the Maintainer field to 
the usual QA value.

Bug#1051902: bullseye-pu: package dpkg/1.20.13

[Adam D. Barratt]

Control: tags -1 confirmed

On Thu, 2023-09-14 at 00:28 +0200, Guillem Jover wrote:
> This update backports the loong64 arch support as requested in
> #1051763 because some of the Debian infra is still using bullseye.
> There's also a fix for a segfault on virtual field formatting which
> is rather easy to trigger for packages that are known to dpkg, but
> are not installed, such as virtual packages or references from
> Recommends or Suggests, which was also included in the 1.21.22 pre-
> approval request included in bookworm. And finally a fix for a memory
> leak, included in 1.22.0 in unstable.
> 

Please go ahead, bearing in mind that the window for 11.8 closes over
the coming weekend.

Regards,

Adam

Bug#1052559: No uploader

[Ben Tris]

Source: zlmdb
Version: 22.6.1-3
Severity: important
X-Debbugs-Cc: benatt...@gezapig.nl

Dear Maintainer,

I think this counts also in this case?

There is no uploader at this moment, it is required in this case I think.

Debian Policy Manual, Release 4.6.2.0
3.3 The maintainer of a package

If the maintainer of the package is a team of people with a shared email
address, the Uploaders control field must be
present and must contain at least one human with their personal email address.


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

Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.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#1052543: bookworm-pu: package plasma-framework/5.103.0-1+deb12u1

[Patrick Franz]

Hi Adam,

On Sun, 24 Sep 2023 17:37:58 +0100 "Adam D. Barratt"  wrote:
[...]
> Please go ahead.

Package has been uploaded.


-- 
Med vänliga hälsningar

Patrick Franz

Bug#1042058: bookworm-pu: package pandoc/2.17.1.1-2~deb12u1

[Adam D. Barratt]

Control: tags -1 confirmed

On Tue, 2023-07-25 at 23:40 +0200, Guilhem Moulin wrote:
> pandoc 2.17.1.1-1.1 is vulnerable to CVE-2023-35936: Arbitrary file
> write vulnerability via specially crafted image element in the input
> when generating files using the `--extract-media` option or
> outputting to PDF format.
> 

Please go ahead; sorry for the delay.

Regards,

Adam

Bug#1052420: bullseye-pu: package flameshot/0.9.0+ds1-2+deb11u1

[Adam D. Barratt]

On Sat, 2023-09-23 at 22:10 +0100, Adam D. Barratt wrote:
> Control: tags -1 confirmed
> 
> On Thu, 2023-09-21 at 13:37 -0400, Boyuan Yang wrote:
> > As reported in https://bugs.debian.org/1051408 , current flameshot
> > in Debian 11 (Bullseye) will silently upload the current captured
> > screenshot to imgur without confirmation whenever the corresponding
> > hotkey is pressed. This imposes a security risk of leaking
> > sensitive
> > information.
> > 
> > In order to mitigate this issue, I propose to upload flameshot
> > 0.9.0+ds1-2+deb11u1, which strips the embedded imgur token
> > hardcoded
> > in the source code. Users who wish to utilize the img uploading
> > feature can fill in their own imgur token in flameshot config
> > window to re-enable the feature.
> > 
> 
> Please go ahead.
> 

I should have spotted this before, but the news file in the source
package should simply be named "debian/NEWS"; dh_installchangelogs will
then install it as NEWS.Debian in the binary package.

It's up to you whether you want to upload a +deb11u2 that simply fixes
that, or would prefer that we reject the existing upload and you can
upload a fixed +deb11u1.

Regards,

Adam

Bug#1051125: RFS: a2d/2.0.0-1 [ITP] -- APRS to DAPNET portal

[Boyuan Yang]

Hi,

在 2023-09-24星期日的 02:38 -0400，Yogu NY3W写道：
> Hi Boyuan,
> I want to express my appreciation for your valuable feedback. Your insights 
> have been immensely helpful in improving the package, and I've made several 
> important changes.
> 
> 1. I have removed empty conffiles.
> 
> 2. Implemented dh_installcron to manage the crontab within /etc/cron.d/ for a 
> safe and reliable approach.
> 
> 3. Removed the "Name" field in the upstream/metadata to adhere with the 
> current guidelines.
> 
> 4. Invasive manipulation of system files has been avoided, using 
> dh_installsystemd, and others to manage these files appropriately.
> 
> 5. Eliminated wrapper, preinst and postinst scripts. Eliminated the need for 
> mkdir -p and adopted dh_installdirs and dh_installdocs. Significantly 
> minimized the use of
> postinst and postrm scripts to adhere to best practices.
> 
> 6. Revised Nginx configuration handling. I've carefully redesigned the 
> handling of Nginx configurations to ensure that default Nginx settings are 
> not overwritten, thus
> safeguarding any user-modified configurations.
> 
> Throughout this process, I've looked into other debian system packages to 
> ensure that this package aligns with Debian standards. I would greatly 
> appreciate your review of
> these changes and any further guidance. I look forward to your continued 
> support.

I belive the following issues still need to be fixed:

* debian/a2d.init.d still refers to files under /usr/local/, which I believe 
does not exist.

* Why are you installing /etc/nginx/ssl/ as an empty directory? Is this 
directory used
by your program anywhere? If not, please do not have it installed.

The following issues are not required to fix:

* I am curious on your thought of installing files under /usr/share/scripts/. 
This kind of
practice never appeared in Debian's past packages, and I never saw it in other 
software.
Would using /usr/share/a2d/scripts/ be a better choice?

* Please consider fixing the following lintian warnings:

W: a2d: skip-systemd-native-flag-missing-pre-depends (does not satisfy 
init-system-helpers:any) [postinst:24]
W: a2d: skip-systemd-native-flag-missing-pre-depends (does not satisfy 
init-system-helpers:any) [prerm:10]

You may google the warning messages for more information.


Thanks,
Boyuan Yang


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

Bug#1024305: fail2ban: 'allowipv6' not defined in 'Definition'

[Stefan Weil]

I suggest to update /etc/fail2ban/jail.d/defaults-debian.conf to fix 
this bug:



--


# cat /etc/fail2ban/jail.d/defaults-debian.conf
[DEFAULT]
allowipv6 = auto

[sshd]
enabled = true

--


Stefan

Bug#770171: sshd jail fails when system solely relies on systemd journal for logging

[Stefan Weil]

This bug report from 2014 is meanwhile more important than ever.

With the latest stable release Debian marked rsyslog as deprecated (see 
https://wiki.debian.org/Rsyslog).


If a user removes the rsyslog package without removing the related 
logfiles in /var/log, fail2ban silently stops doing its job, because

it looks for failed ssh logins in /var/log/auth which no longer gets
updates. The same applies to other jails which were activated by local 
settings.


If the user not only removes rsyslog but also removes all old files in
/var/log/, fail2ban no longer runs at all but silently fails.

If fail2ban is not working as expected or not running at all, that can 
effect the security of a Debian system. Therefore I suggest to increase 
the priority of this bug report.


My fix for this issue (and also for issue 1024305) is a small 
modification of jail.d/defaults-debian.conf:


--

# cat /etc/fail2ban/jail.d/defaults-debian.conf
[DEFAULT]
allowipv6 = auto
dovecot_backend = systemd
postfix_backend = systemd
sshd_backend = systemd
# ... add more affected backends here

[sshd]
enabled = true

--

I only added the backends which where required for my Debian system. 
Maybe some other jails also must use the systemd backend.


I suggest to update jail.d/defaults-debian.conf and distribute that as a 
security fix.


In addition, rsyslog could be removed from the list of suggested 
packages in future Debian releases.


Stefan

Bug#1052557: fpc: Compiler bootstrap for more release architectures

[Paul Gevers]

Hi,

On 24-09-2023 19:38, Bastian Germann wrote:

How is the bootstrap done and is it planned?


I recall that bug 551400 and/or 784569 give quite some insight in what 
needs to be done.


I don't have any plans of bootstrapping fpc ever again. If anything, I'd 
like to see the glibc 'arch' of fpc actually working, then we could 
support all Debian architectures *and* cross building would probably be 
easier. But it all has been a while.


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1050803: mate-session-manager: please provide a mate-portals.conf for xdg-desktop-portal

[Simon McVittie]

Control: reassign -1 mate-desktop 1.26.1-1
Control: affects -1 mate-session-manager
Control: tags -1 + fixed-upstream pending

On Sun, 24 Sep 2023 at 15:50:37 +, Mike Gabriel wrote:
> On  Di 29 Aug 2023 12:52:06 CEST, Simon McVittie wrote:
> > Please
> > add an mate-portals.conf to tell x-d-p more explicitly what backends
> > MATE is meant to be using by default.
> 
> The mate-portals.conf will be shipped in mate-desktop (providing the
> libmate-desktop-* base library) starting with mate-desktop 1.26.2.
> (Uploading in some minutes).
> 
> The mate-session-manager bit, I need to check deeper.

For the purposes of this bug, it doesn't matter whether mate-portals.conf
is in mate-session-manager or in one of its dependencies, as long as
installing a somewhat minimal MATE desktop will pull it in.

mate-session-manager is the package that owns
/usr/share/xsessions/mate.desktop, so ideally installing
mate-session-manager ought to provide mate-portals.conf either
directly or indirectly. m-s-m depends on mate-desktop-common, and it seems
that you added mate-portals.conf to m-d-c, so I think this bug is now
solved: reassigning to mate-desktop-common so that it can be closed as
fixed in 1.26.2-1.

Thanks,
smcv

Bug#1052558: wxutils: No uploader

[Ben Tris]

Source: wxutils
Version: 0.2.7-1
Severity: important
X-Debbugs-Cc: benatt...@gezapig.nl

Dear Maintainer,

There is no uploader at this moment, it is required in this case I think.

Debian Policy Manual, Release 4.6.2.0
3.3 The maintainer of a package

If the maintainer of the package is a team of people with a shared email
address, the Uploaders control field must be
present and must contain at least one human with their personal email address.


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

Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.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#1052557: fpc: Compiler bootstrap for more release architectures

[Bastian Germann]

Source: fpc
Version: 3.2.2+dfsg-22
Severity: wishlist

According to the upstream platform documentation, fpc should be able to run on 
mips64el and riscv64.
I see that the buildd network does not build them because the package build 
depends on one of its own binary packages.
How is the bootstrap done and is it planned?

Bug#885777: xournal: depends on deprecated libraries

[Bastian Germann]

Would the fork at https://github.com/dmgerman/xournal/tree/gtk3 be an option? 
It is ported to GTK3 and goocanvas.

Bug#1052556: bfh-gnome-desktop: Depends on extensions that aren't compatible with GNOME Shell 45

[Jeremy Bícha]

Package: bfh-gnome-desktop
Version: 20211009-20
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-45
Control: block -1 by 1052090 1052104 1052105

bfh-gnome depends on 3 extensions that need to be ported to support
GNOME Shell 45 or the extensions will be removed from Debian Testing
once GNOME Shell 45 is uploaded to Debian Unstable and is ready for
migration to Testing.

This issue can be fixed by updating all the extensions to support
GNOME Shell 45 or by dropping the dependency on extensions which
haven't been updated.

Unfortunately, it is not possible for extensions to support both GNOME
Shell 45 and earlier versions simultaneously so extension updates need
to go to Experimental until GNOME Shell 45 is uploaded to Unstable.

Thank you,
Jeremy Bícha

Bug#1052555: libmatemixer: heap corruption/crash when pulseaudio audio device is removed

[Mike Gabriel]

Package: src:libmatemixer
Severity: important
Version: 1.26.0-2
Forwarded: https://github.com/mate-desktop/libmatemixer/issues/39

Forwarding bug report from upstream:

If the audio device vanishes, applications which integrate  
libmatemixer will error or crash. In mate-settings-daemon, the  
corruption is detected by malloc:


free(): corrupted unsorted chunks
corrupted double-linked list
malloc_consolidate(): unaligned fastbin chunk detected

In mate-volume-control-status-icon, it presents as so:

malloc(): unaligned tcache chunk detected
../glib/glib/gmem.c:207: failed to allocate 103079215112 bytes

Using a USB audio device, if the audio device disconnects, MATE  
software should handle the device removal gracefully.



--

mike gabriel aka sunweaver (Debian Developer)
mobile: +49 (1520) 1976 148
landline: +49 (4351) 486 14 27

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunwea...@debian.org, http://sunweavers.net



pgpC72Hep6jlY.pgp
Description: Digitale PGP-Signatur

Bug#1052554: Acknowledgement (linux-image-6.5.0-1-amd64: amdgpu crashes)

[Florian Reichl]

I don't have this bug when booting kernel 6.4.13-1 (2023-08-31).

It looks like I have a problem as described here:
https://unix.stackexchange.com/questions/756281/kernel-6-5-2-seems-to-have-amdgpu-crash-on-no-retry-page-fault

Thank you!

Debian Bug Tracking System  schrieb am So., 24.
Sept. 2023, 18:33:

> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1052554:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052554.
>
> 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
>   flor...@reichl.net
> (after having been given a Bug report number, if it did not have one).
>
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team 
>
> If you wish to submit further information on this problem, please
> send it to 1052...@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.
>
> --
> 1052554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052554
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>

Bug#999962: RFS to solve bug#999962 (silversearcher-ag: depends on obsolete pcre3 library)

[Manphiz]

Nicholas D Steeves  writes:

> Manphiz  writes:
>
>> Nicholas D Steeves  writes:
>>> Manphiz  writes:
 Manphiz  writes:
> [snip]
>>> Then finalise the changelog and build the package.
>>>
>>
>> Done as well.
>
> Thanks!
>
>>> Finally, learn about what an "nmudiff" is, and file one at the relevant
>>> bug.
>>>
>>
>> To be careful I'd like to have you take another look before doing so[1]
>> :)
>
> I pulled from your remote and noted the requested updates.  It looks
> good to me :)
>

Great, thanks!

>> BTW, I'm not a DD or DMD yet so I'm probably not able to submit to
>> delayed queue yet, right?
>
> Right, the upload to the delayed queue using dput is something else, and
> any uploads you make to ftp-master will not succeed.  I'm not sure if
> mentors.debian.net has a delayed queue, and I can't see how that would
> be useful--other than for practise.  Did you find the relevant section
> in the Developer's Reference?
>

Uploaded to mentors[1].  Tried to search for NMU and mentors related
contents in the Developer's Reference but didn't find much.  I guess
mentors should be safer than the delayed queue.

> Before we get to the upload you need to submit an nmudiff of the source
> package.  On a related note, if you don't know about these yet,
> "msmtp-mta" and "apt-file" are really useful.  Msmtp-mta is an
> alternative to other MTAs (useful for laptops, and Spwhitton told me
> about apt-file :)  It's technically possible to use debdiff, but
> "nmudiff" is a tool like "reportbug", but I'm not sure if nmudiff will
> function without an mta, unlike reportbug.
>

Also sent the nmudiff to this bug.  Good thing that my postfix still
works :)

> Best,
> Nicholas
>


[1] https://mentors.debian.net/package/silversearcher-ag/
-- 
Manphiz


signature.asc
Description: PGP signature

Bug#1049955: bookworm-pu: package qemu/1:7.2+dfsg-7+deb12u2

[Adam D. Barratt]

On Sun, 2023-09-24 at 06:52 +0300, Michael Tokarev wrote:
> 23.09.2023 23:45, Adam D. Barratt wrote:
> > Control: tags -1 confirmed
> > 
> > On Thu, 2023-08-17 at 12:54 +0300, Michael Tokarev wrote:
> > > There's a next upstream qemu stable/bugfix release, fixing a
> > > big number of various issues, including 3 (minor) security
> > > issues too.  The full list is in the changelog below and
> > > in the upstream git (mirrored in salsa too).
> ...
> 
> > Please go ahead.
> 
> It is a "good" timing, Adam.  Just 2 days ago I sent announcement
> for a new qemu stable-7.2.6 release fixing a bunch of more bugs,
> and fixing an important class of security issues too.
> 
> https://lore.kernel.org/qemu-devel/bf422038-5f0a-e9ca-1eb3-ed25442c7...@tls.msk.ru/
> 
> "Good" because I forgot to send a note to this bug report about the
> upcoming release (it was planned) and as a result we clashed.
> 
> I prepared debian package (based on this new 7.2.6), it is in testing
> now on my local machine.
> 
> Will it be easier to upload the reviewed 7.2+dfsg-7+deb12u2 (based on
> 7.2.5) and close this bug#, and later make 7.2+dfsg-7+deb12u3 (based
> on 7.2.6), or update current bug# with new release?
> 
> I guess it's better to do it step by step, closing this bug# and
> filing a new one.
> 

That might depend when you expect to be ready with the newer update. 

The window for 12.2 closes next weekend, so if you'd rather have more
time to test and work on the 7.2.6 update, it would make sense to
upload the 7.2.5-based update for 12.2, and then the newer update for
12.3.

Regards,

Adam