Processed: severity of 1043112 is serious, severity of 1043131 is serious

2023-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 1043112 serious
Bug #1043112 [apfs-dkms] apfs-dkms: module fails to build for Linux 6.5: 
detected write beyond size of object
Severity set to 'serious' from 'important'
> severity 1043131 serious
Bug #1043131 [openafs-modules-dkms] openafs-modules-dkms: module fails to build 
for Linux 6.5: error: static declaration of 'abort' follows non-static 
declaration
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1043112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043112
1043131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043131
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Package is uninstallable, bug unacknowledged, therefore release critical

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 grave
Bug #1051739 [caja-dropbox] 1.26.0-3 uninstallable due to nonexistent package
Severity set to 'grave' from 'normal'

-- 
1051739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1051819: fluidsynth: Consider building with pipewire support

2023-09-16 Thread Gianfranco Costamagna
Hello, i did nmu because... 1) riscv64 porting is finishing and they need to 
build as many packages as possible (this one was blocking a lot of packages) 2) 
im in vac now for more than one week, and i wont have access to laptop or so
Sorry for the rush and indeed feel free to change everything as you prefer :) 
Cheers! 
Gianfranco

Sent from Yahoo Mail on Android 
 
  On Sat, Sep 16, 2023 at 15:27, Johannes Schauer Marin 
Rodrigues wrote:   Hi Nicholas,

Quoting Nicholas D Steeves (2023-09-16 14:06:00)
> Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
> fluidsynth -dev package.  'not sure how that happened, but my mistake!  Isn't
> only waiting 48h a bit rushed for an NMU though?

the number of delayed days are documented here:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#when-and-how-to-do-an-nmu

It seems that indeed a 0-day nmu was a bit too quick here.

> I can of course import your fix and upload in the next 48h, and I'd like to
> improve your changelog entry, because I think you'll agree that the concept
> of "runtime" doesn't make sense for headers ;)

It does make sense as we have two types of dependencies in Debian: build
dependencies and runtime dependencies. A header package is also a binary
package so it has runtime dependencies like all other binary packages do.

But indeed the term "runtime dependency" is not very widely used. I do not
think that Debian policy uses it. I think the term is mostly used by people
like me who work on dependency resolution software.

> If this is truly 0-day urgent, I'm confident a team member (IIRC Josch is a
> multimedia-team member) will upload.

I'm afraid it was already uploaded and is now in unstable. :(

> ('hope this isn't HTML email, since I'm currently AFK on a phone)

It was HTML but it also had a text/plain part. :)

Thanks!

cheers, josch  


Processed: Re: Bug#1052040: mmm-mode: post-install script fails

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 - upstream
Bug #1052040 [mmm-mode] mmm-mode: post-install script fails
Removed tag(s) upstream.

-- 
1052040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1052040: mmm-mode: post-install script fails

2023-09-16 Thread Vincent Lefevre
Control: tags -1 - upstream

The issue actually comes from the 01-xemacs patch.

On 2023-09-16 17:46:23 +0200, Vincent Lefevre wrote:
> An easy solution would be to avoid the XEmacs form (marked as
> obsolete in GNU Emacs since 23.1 and whose support was removed
> in GNU Emacs 28[*]), i.e. change
> 
> (if (not (string-match "XEmacs" (emacs-version)))
> (define-obsolete-function-alias 'mmm-add-find-file-hooks 
> 'mmm-add-find-file-hook
>   "0.3.8"
>   "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are 
> deprecated.")
>   (define-obsolete-function-alias 'mmm-add-find-file-hooks 
> 'mmm-add-find-file-hook))
> 
> to just
> 
> (define-obsolete-function-alias 'mmm-add-find-file-hooks 
> 'mmm-add-find-file-hook
>   "0.3.8"
>   "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are 
> deprecated.")

Alternatively, update to release 0.5.10, where upstream has just
removed these obsolete functions:

https://github.com/dgutov/mmm-mode/commit/244f8c4794f20a6be5ebe1e405400a9c35ea6d2f

so that mmm-auto.el no longer needs to be patched for xemacs.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1052072: package ontospy contains license CC-BY-1.0

2023-09-16 Thread Thorsten Alteholz

Package: ontospy
Version: 0~20190225~dfsg1-1
Severity: serious
User: alteh...@debian.org
Usertags: license
thanks


Hi Jonas,

unfortunately your package contains a file with license: CC-BY-1.0

   ontospy/gendocs/misc/html-tests/_FOAFspecification.html

This license is not compatible with DFSG[1], so please remove the file or
move the package to non-free.

Thanks!
 Thorsten

[1] https://lists.debian.org/debian-legal/2004/04/msg00031.html



Bug#1052048: marked as done (texlive-bibtex-extra: Can't generate bibliography since last upgrade at trixie)

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 23:59:52 +0200
with message-id <8bf12179-a20f-ff11-544d-2041f2b5c...@web.de>
and subject line Re: Close Bug#1052048:
has caused the Debian Bug report #1052048,
regarding texlive-bibtex-extra: Can't generate bibliography since last upgrade 
at trixie
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-bibtex-extra
Version: 2023.20230613-2
Severity: grave
X-Debbugs-Cc: mechti...@debian.org

After last update at trixie I can't proper build https://salsa.debian.org/ddp-
team/dpb/ locally.

It builds correct on trixie at the Salsa CI at 03.09.2023. The last upload to
trixie was at 05.09.2023.

I lost the bibliography in the pdf of this big document.

That's why I set it to grave.

Kind regards

Mechtilde


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

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

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

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

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

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

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

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

or 

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

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 1956 Sep 10 08:48 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 12  2022 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Aug 27 23:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Aug 27 23:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Oct 18  2022 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Aug 27 23:39 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Aug 27 23:39 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3197 Sep 10 08:47 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep  4  2021 mktex.cnf
-rw-r--r-- 1 root root 475 Oct 18  2022 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-bibtex-extra depends on:
ii  tex-common  6.18
ii  texlive-base2023.20230613-3
ii  texlive-binaries2023.20230311.66589-4
ii  texlive-latex-base  2023.20230613-3

texlive-bibtex-extra recommends no packages.

texlive-bibtex-extra suggests no packages.

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages 

Bug#1051797: marked as done (libtk-img-doc: dpkg extraction error during upgrading)

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 21:45:56 +
with message-id 
and subject line Bug#1051797: fixed in libtk-img 1:1.4.15+dfsg-2
has caused the Debian Bug report #1051797,
regarding libtk-img-doc: dpkg extraction error during upgrading
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1051797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtk-img-doc
Version: 1:1.4.14+dfsg-2
Severity: normal
X-Debbugs-Cc: davide.pr...@null.net

Dear mainteiner,

during the upgrade of the package from version 1:1.4.15+dfsg-1 to
version 1:1.4.14+dfsg-2 I have the following error:

dpkg: errore nell'elaborare l'archivio 
/tmp/user/0/apt-dpkg-install-f3K6IA/18-libtk-img-doc_1%3a1.4.15+dfsg-1_all.deb 
(--unpack):
 tentata sovrascrittura di "/usr/share/doc/libtk-img/README.gz" presente anche 
nel pacchetto libtk-img:amd64 1:1.4.15+dfsg-1

I try to translate:
dpkg: error processing the archive 
/tmp/user/0/apt-dpkg-install-f3K6IA/18-libtk-img-doc_1%3a1.4.15+dfsg-1_all.deb 
(--unpack):
 try to overwrite of "/usr/share/doc/libtk-img/README.gz" present also in the 
package libtk-img:amd64 1:1.4.15+dfsg-1

Ciao
Davide

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

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

libtk-img-doc depends on no packages.

libtk-img-doc recommends no packages.

Versions of packages libtk-img-doc suggests:
ii  libtk-img  1:1.4.15+dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libtk-img
Source-Version: 1:1.4.15+dfsg-2
Done: Sergei Golovan 

We believe that the bug you reported is fixed in the latest version of
libtk-img, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sergei Golovan  (supplier of updated libtk-img package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Sep 2023 23:51:43 +0300
Source: libtk-img
Architecture: source
Version: 1:1.4.15+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Sergei Golovan 
Changed-By: Sergei Golovan 
Closes: 1051797
Changes:
 libtk-img (1:1.4.15+dfsg-2) unstable; urgency=medium
 .
   * Remove duplicate README from libtk-img-doc (closes: #1051797).
Checksums-Sha1:
 0c6f45c2a4d7a6f1a15f08365806d25f06cbf7af 2141 libtk-img_1.4.15+dfsg-2.dsc
 a359fec200b99d41f56ce22c8f2a32d90268fcd6 14032 
libtk-img_1.4.15+dfsg-2.debian.tar.xz
 c10cb910c336805fd5914f94beb17e233376a048 8960 
libtk-img_1.4.15+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 79fd2dfa2a5566c2c85d7eb824c394e8e3c0eede171cd4ddd8e230c6eb3b140e 2141 
libtk-img_1.4.15+dfsg-2.dsc
 f645e4e1abbce9fa9c571b7e27706b7e45313aea638972c62c136e0dc47b731a 14032 
libtk-img_1.4.15+dfsg-2.debian.tar.xz
 8ee28969c23db6826b5fa8d9151c706b748a022f2cefd5e1dfb9dfc9f3cc0acf 8960 
libtk-img_1.4.15+dfsg-2_amd64.buildinfo
Files:
 8b01cf6f495d9440a6ab2d605a6ef804 2141 libs optional libtk-img_1.4.15+dfsg-2.dsc
 07263d39e552b826ab98d034b1205ab1 14032 libs optional 
libtk-img_1.4.15+dfsg-2.debian.tar.xz
 d07db25d20c8f9f96ff6a54573d53585 8960 libs optional 
libtk-img_1.4.15+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/SYPsyDB+ShSnvc4Tyrk60tj54cFAmUGFmEACgkQTyrk60tj
54e0wg//f4vDahOrIwyv3aeZrnFKELme3A4Tgg5nfsEpTgE091EO2Xvav4Ww/ozY
S0BHAIa7pa+TSZ788IggK7cJ3eDN5ECH6QwHp3Rk1xV/I8XDK5Y+tGHMdXXJRmbL
J8ydaETaMk+ZTw0LJ7yXnTJMQOcYYZIay8A8inDA7kHFnmGW6FjpCY6y+yF32v9w
ORPwFtpktyM2U+zq/8PNiqR9kcdasXyEvip/sxrr8yhxNbqxEyIpknsqtkbT7JZL
QkLfuRbOAWa7lx6WSRvpcBnn4sjfySDKKlheupOHvU0Ke4HrWiCnObUSEG6Fkbuo
f91b7qzQt+YsMQcb+g4QhNl7anz+sf1azlhw5F3OXdE5dN2AxZhvLL3EgnlM8kaM
wyDVaKeAyfmckSWlv9soGRNoVZAJ4BCYVAAGCI55lu9zdmiTOk0aGksy95tZTWjx
jWT4Heyao3ZKkUn2IkP4d1cfz592J4FUa37WgAZoMOBC4CAQAW+W9tr6NHVKSfne

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

2023-09-16 Thread Mathias Gibbens
On Sun, 2023-08-06 at 15:20 +0100, Richard Lewis wrote:
> A gentle reminder on the last bit of this - getting it into bookworm
> point release. (i think i read somewhere that 12.2 would be at the
> end of august)

  ACK -- the 12.2 point release has been announced for October 7th,
with a processing freeze the weekend prior. I think we should be able
to get the changes done and proposed to the release team by the end of
next week.

>  -- let me know if there's anything i can do to help with this (i
> couldn't find anything listing what it involves!)

  The process for uploads to (old)stable is described here:
https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable

  I'll contact you directly, off of this bug report so we can
coordinate.

Mathias


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


Bug#1028172: marked as done (libmpich-dev lacks dependencies required by its pkgconfig file)

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 20:50:35 +
with message-id 
and subject line Bug#1028172: fixed in mpich 4.1.2-2
has caused the Debian Bug report #1028172,
regarding libmpich-dev lacks dependencies required by its pkgconfig file
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1028172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiledarray
Version: 1.0.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar

Hi Michael,

tiledarray's build-dependencies are now satisfied in unstable (bug
#1014548), but it fails to build from source :)

[...]
CMake Error at /usr/share/cmake-3.25/Modules/CMakeTestCXXCompiler.cmake:63 
(message):
  The C++ compiler

"/usr/bin/c++"

  is not able to compile a simple test program.

  It fails with the following output:

Change Dir: 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98

Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_d2ec9/fast && 
gmake[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
/usr/bin/gmake  -f CMakeFiles/cmTC_d2ec9.dir/build.make 
CMakeFiles/cmTC_d2ec9.dir/build
gmake[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
Building CXX object CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o
/usr/bin/c++   -I/usr/include/x86_64-linux-gnu/mpich  -o 
CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -c 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98/testCXXCompiler.cxx
Linking CXX executable cmTC_d2ec9
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_d2ec9.dir/link.txt 
--verbose=1
/usr/bin/c++ -I/usr/include/x86_64-linux-gnu/mpich  -lmpich -lpthread 
-lhwloc -lucp -lucs -lrt  CMakeFiles/cmTC_d2ec9.dir/testCXXCompiler.cxx.o -o 
cmTC_d2ec9 
/usr/bin/ld: cannot find -lhwloc: No such file or directory
/usr/bin/ld: cannot find -lucp: No such file or directory
/usr/bin/ld: cannot find -lucs: No such file or directory
collect2: error: ld returned 1 exit status
gmake[3]: *** [CMakeFiles/cmTC_d2ec9.dir/build.make:99: cmTC_d2ec9] Error 1
gmake[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
gmake[2]: *** [Makefile:127: cmTC_d2ec9/fast] Error 2
gmake[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-I8ie98'
[...]

  
(https://buildd.debian.org/status/fetch.php?pkg=tiledarray=amd64=1.0.0-1=1673126398=0)


Possibly an issue in a build-dependency, I see that these library options
come from the output of `pkg-config --libs-only-l mpi` but libmpich-dev
apparently doesn't depend on the packages providing the libs in its output.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mpich
Source-Version: 4.1.2-2
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
mpich, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated mpich package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Sep 2023 21:29:42 +0200
Source: mpich
Architecture: source
Version: 4.1.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Bastian Germann 
Closes: 1028172
Changes:
 mpich (4.1.2-2) unstable; urgency=medium
 .
   * Team upload
   * Drop kfreebsd
   * d/control: Drop unused B-D quilt
   * Add Deps to libmpich-dev needed for pkg-config (Closes: #1028172)
Checksums-Sha1:
 4799fd5004029ab47b06281232d92f979995073f 2558 mpich_4.1.2-2.dsc
 9647facfc7be5cfc93ed21e776520e0fd9a27d67 339120 

Processed: reassign 1051661 to ftp.debian.org

2023-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1051661 ftp.debian.org
Bug #1051661 [dak] /usr/bin/qemu-system-ppc: Package not installable
Warning: Unknown package 'dak'
Bug reassigned from package 'dak' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #1051661 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1051661 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1051577: marked as done (iproute2: obsolete conffiles)

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 19:08:09 +
with message-id 
and subject line Bug#1051577: fixed in iproute2 6.5.0-4
has caused the Debian Bug report #1051577,
regarding iproute2: obsolete conffiles
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1051577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iproute2
Version: 6.5.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

After upgrading to 6.5.0-1 adequate shows:

adequate found packaging bugs
- -

iproute2: obsolete-conffile /etc/iproute2/rt_tables.d/README
iproute2: obsolete-conffile /etc/iproute2/rt_protos.d/README
iproute2: obsolete-conffile /etc/iproute2/rt_protos
iproute2: obsolete-conffile /etc/iproute2/rt_dsfield
iproute2: obsolete-conffile /etc/iproute2/nl_protos
iproute2: obsolete-conffile /etc/iproute2/ematch_map
iproute2: obsolete-conffile /etc/iproute2/bpf_pinning

Cf. dpkg-maintscript-helper(1) and dh_installdeb(1) / package.maintscript
/ rm_conffile.

Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmT898hfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZ76hAAvpluUC3obOOsJfmXhh48GqVoLEt/7wg2B7WR73f21nGSTMUP+nzDSE8W
JwkGRIP8aT6eiHfh8zHj83Ey0r4IZ9g/OlMzyqCq7jDRzPo3fmy6Z3tJePGFO5Qg
nYmZwQA9DA+ANUi0A9BqNvgofguXh9KxIk5k2Gd2M8P5OBPvcXuVBuXtARwPljVw
7wA+niYFUyjkL1rgj1eBdiwzzldyUJiGC4/cve2fkmQyXqtocTqWjQTEXa1zYRGn
zRsCCyRdD0lJl/DqKTHspPyM/BAbWJbVnUPZ0Kn0LJAcvaUuOH+U4UAJTCshzaNM
XzuAHx39Hh90SbRYvikASBPJX3s1jhOBTuJkH6qWjgtgQfSyElvujHqzOwUr73xX
K5Ew9wDBAEbC5JDs4pLZGBQLUWmocQdAKRikPkScSqTpU+s/RIgwzg7uGsVK2tSo
dO7zN6Q08NusJT6T4c7AYgSEHiLsH0rIHA7jY/x9roZ+X57Hg36YRGLdIL5UG74k
1dIgRZh4CpJZdmD28x5lW5Zk2oKE+x3GDhiZKuhoKJBSfH4CbNbHc3n4PkAIlBAD
i2oxEkO20DwuJTiVmsQvDmYRWLOaSvA6Ffi02H78LQ3+QCFjXdKLIsm5Ex3wD7Me
p+tSaEI4OE3VeaFY5xXnr20PIVe/7cf7TUAseyLB59vQk17tSIk=
=dToJ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: iproute2
Source-Version: 6.5.0-4
Done: Luca Boccassi 

We believe that the bug you reported is fixed in the latest version of
iproute2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated iproute2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Sep 2023 18:58:51 +0100
Source: iproute2
Architecture: source
Version: 6.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Luca Boccassi 
Closes: 1051577
Changes:
 iproute2 (6.5.0-4) unstable; urgency=medium
 .
   * postinst: handle legacy config files only when upgrading from previous
 versions that shipped them
   * postinst: ensure that locally modified legacy config files are
 preserved as overrides on upgrade (Closes: #1051577)
   * Note configuration files location changes in NEWS
Checksums-Sha1:
 b9928c7fe0018926dc680275af54c3f1cb6a0c0f 2246 iproute2_6.5.0-4.dsc
 ae34769201655f6e6dc78fd8565cdd726a16ba9d 38208 iproute2_6.5.0-4.debian.tar.xz
 a58fb6d4de5721caa6e32bd09c905d7ccd07e4f7 7528 iproute2_6.5.0-4_source.buildinfo
Checksums-Sha256:
 0e714d3cea2375d80069eeda834988ad1374399a5f88bee6c083ef99a540cb35 2246 
iproute2_6.5.0-4.dsc
 22879801479d99d2b222aaa0f9b0feadba94af45fee1fc3ac53d1c01b5e8a177 38208 
iproute2_6.5.0-4.debian.tar.xz
 a2e63a23f61cab0800124dc0df797177e77ac0f11274abe95cca7b168af93f01 7528 
iproute2_6.5.0-4_source.buildinfo
Files:
 f830f32f646178cf80215b72bb91f843 2246 net optional iproute2_6.5.0-4.dsc
 3ed227ccdc72e03de6b245e14acafbe9 38208 net optional 
iproute2_6.5.0-4.debian.tar.xz
 70f3c326bc99f36cb5538a7090911b6d 7528 net optional 
iproute2_6.5.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmUF950RHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB7o6hAAzYTdzOXgkMIcXdzJ+AM5/TgMvkuDy1uQ
Q1+vYeSeqSKQN6+LfEFGo6erAdh8WN4IQR2Xh5m48kvh2URSFkdHwfESf17rBYLm

Processed: yubioath-desktop: ftbfs with GCC-13

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1037909 [src:yubioath-desktop] yubioath-desktop: ftbfs with GCC-13
Added tag(s) patch.

-- 
1037909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1037909: yubioath-desktop: ftbfs with GCC-13

2023-09-16 Thread Jonathan Bergh
Control: tags -1 + patch

Fixes 1037909 due to upgrade with gcc-13


patch1.debdiff
Description: Binary data


Processed: xrt: ftbfs with GCC-13

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1037903 [src:xrt] xrt: ftbfs with GCC-13
Added tag(s) patch.

-- 
1037903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1037903: xrt: ftbfs with GCC-13

2023-09-16 Thread Jonathan Bergh
Control: tags -1 + patch

Fixes 1037903 due to upgrade to gcc-13


patch1.debdiff
Description: Binary data


Bug#1051592: marked as done (linux: Regression - upgrade to 6.1.52-1 breaks nftables)

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 18:02:59 +
with message-id 
and subject line Bug#1051592: fixed in nftables 1.0.6-2+deb12u2
has caused the Debian Bug report #1051592,
regarding linux: Regression - upgrade to 6.1.52-1 breaks nftables
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1051592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux
Version: 6.1.52-1
Severity: grave

Dear Maintainers,

linux-image-6.1.0-12-amd64 causes a serious regression in nftables. After 
upgrading one of my machines, nftables fails to start - leaving the system 
without an active firewall.

Doing
`nft -cf /etc/nftables.conf'
throws many "Operation not supported" errors on rulesets that have been in 
place for months wihtout issues.

Just to give two simple examples from the log when nftables fails to start:
/etc/nftables.conf:99:4-44: Error: Could not process rule: Operation not 
supported
tcp option maxseg size 1-500 counter drop
^
/etc/nftables.conf:308:4-27: Error: Could not process rule: Operation not 
supported
tcp dport sip-tls accept


Downgrading to linux-image-6.1.0-11-amd64 resolves the issue.

Notes: I'm running a local rebuild of linux-image-amd64 with a few additional 
symbols enabled. But since these symbols are totally unrelated to the netfilter 
subsystem and there are no changes to the source itself, I'm certain, this 
affects the original Debian build as well. Whether it only affects certain 
architectures or rulesets, I can't say, though.

I'm cc'ing debian-secur...@debian.org because the update came via the 
stable-security channel.


Thanks and regards,

Timo
--- End Message ---
--- Begin Message ---
Source: nftables
Source-Version: 1.0.6-2+deb12u2
Done: Salvatore Bonaccorso 

We believe that the bug you reported is fixed in the latest version of
nftables, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1051...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated nftables package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Sep 2023 07:47:15 +0200
Source: nftables
Architecture: source
Version: 1.0.6-2+deb12u2
Distribution: bookworm
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Salvatore Bonaccorso 
Closes: 1051592
Changes:
 nftables (1.0.6-2+deb12u2) bookworm; urgency=medium
 .
   * [136245a] Fix incorrect bytecode generation hit with new kernel check that
 rejects adding rules to bound chains (Closes: #1051592)
 - rule: add helper function to expand chain rules intoi commands
 - rule: expand standalone chain that contains rules
 - src: expand table command before evaluation
Checksums-Sha1: 
 2d4f8f425c28129f4b4c31c3bfeeaa7f0f9636db 2630 nftables_1.0.6-2+deb12u2.dsc
 aaba84a09051e7057bf15418f7cedb936ca63c67 26268 
nftables_1.0.6-2+deb12u2.debian.tar.xz
Checksums-Sha256: 
 413d0a649ec540b6a296673ccc66a45498bcb6e6d7eae7ac5f8e3ceac4107291 2630 
nftables_1.0.6-2+deb12u2.dsc
 529dcfde172cfc9fc33b1efa2a19b35ddf82b13aab8cd5b233d81e4008a95edf 26268 
nftables_1.0.6-2+deb12u2.debian.tar.xz
Files: 
 cc5485484935ac92ae92ebbe984e5097 2630 net important 
nftables_1.0.6-2+deb12u2.dsc
 0cdefcc4793d5134ce8e6b877aca50b4 26268 net important 
nftables_1.0.6-2+deb12u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmUFQfxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EozEP/29wEpNhFeRSLwuAax4FFRrt3Ycz2ew1
FHyQ0atuwhHTMeeoWR5TwiqZpMN+AiBFZ23tzwmDjLsLZn+zmxYsN/95HrKdRsgA
onymtCaX8oita33YFyBFuVEHeeVC3XC1HK8uXZKLi1DOiogEqht7xZXrPc/0yQvx
6V/pqZfannvcNUkvldvwOnulHoLO/mr8QtRtRH0pI8L5eQc0PrlnsZ1hyD8Ui9bQ
bzkncukyC9WQmn97v5ex9d4brP3jNEMSaVpQVn0c9Xdi3B6zcbAeQwssUWmhtK0P
FDz9C1hOlv7lg/KB2py9ckWNY2YKAdwmUszzBDoErg3p2GQD07AbZyEkiZRRJWs+

Bug#1050359: RM: gpr -- RoQA; dead upstream; depends on gtk2

2023-09-16 Thread Till Kamppeter
gpr is not only not upstream-maintained any more and depending oon the 
obsolete GTK2, it is also only used for printing with LPD/gnulpr/LPRng, 
all these being printing systems which are obsolete for near 2 decades 
(replaced by CUPS) and all not maintained upstream any more.


So it does not actually make sense any more to keep gpr in Debian. So I 
am in favor of its removal, too.




Bug#1024722: davs2: do not release with bookworm

2023-09-16 Thread Bastian Germann

Control: retitle -1 davs2: Keep out of testing until it is used

bookworm was released.



Processed: Re: davs2: do not release with bookworm

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 davs2: Keep out of testing until it is used
Bug #1024722 [src:davs2] davs2: do not release with bookworm
Changed Bug title to 'davs2: Keep out of testing until it is used' from 'davs2: 
do not release with bookworm'.

-- 
1024722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: xneur: ftbfs with GCC-13

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1037902 [src:xneur] xneur: ftbfs with GCC-13
Added tag(s) patch.

-- 
1037902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1037902: xneur: ftbfs with GCC-13

2023-09-16 Thread Jonathan Bergh
Control: tags -1 + patch

Fixes 1037902 with change to gcc-13.
I believe this is a documented false positive from gcc.


patch1.debdiff
Description: Binary data


Bug#1000009: opencollada: depends on obsolete pcre3 library

2023-09-16 Thread Bastian Germann

X-Debbugs-Cc: m...@debian.org

This will not be fixed upstream. The blender package has dropped its 
opencollada dependency.
I suggest to remove the package.



Bug#1037799: marked as pending in opencollada

2023-09-16 Thread Bastian Germann
Control: tag -1 pending

Hello,

Bug #1037799 in opencollada reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/opencollada/-/commit/620bdce96176c597093b5600d42c5cbb0b565bfd


Fixes FTBFS due to gcc-13 upgrade (Closes: #1037799)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037799



Processed: Bug#1037799 marked as pending in opencollada

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1037799 [src:opencollada] opencollada: ftbfs with GCC-13
Added tag(s) pending.

-- 
1037799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1052048: Close Bug#1052048:

2023-09-16 Thread Mechtilde Stehmann

Package: texlive-bibtex-extra
Version: 2023.20230613-2

Comment: Sorry for noise



Am 16.09.23 um 17:21 schrieb Debian Bug Tracking System:

Thank you for filing a new Bug report with Debian.

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

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

Your message has been sent to the package maintainer(s):
  Debian TeX Task Force 

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.



--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1052048: Close Bug#1052048:

2023-09-16 Thread Mechtilde Stehmann

Package: texlive-bibtex-extra
Version: 2023.20230613-2

Comment: Sorry for noise



Am 16.09.23 um 17:21 schrieb Debian Bug Tracking System:

Thank you for filing a new Bug report with Debian.

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

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

Your message has been sent to the package maintainer(s):
  Debian TeX Task Force 

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.



--
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F


OpenPGP_signature.asc
Description: OpenPGP digital signature


Processed: opencollada: ftbfs with GCC-13

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1037799 [src:opencollada] opencollada: ftbfs with GCC-13
Added tag(s) patch.

-- 
1037799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1037799: opencollada: ftbfs with GCC-13

2023-09-16 Thread Jonathan Bergh
Control: tags -1 + patch

Fixes 1037799 due to change to gcc-13


patch1.debdiff
Description: Binary data


Bug#1051374: breaks existing setups using /etc/default/mini-httpd

2023-09-16 Thread Johannes Schauer Marin Rodrigues
Hi,

Quoting Alexandru Mihail (2023-09-16 16:40:38)
> > I asked in #debian-systemd and the fix could be as simple as setting the
> > following in the .service file:
> > 
> > EnvironmentFile=-/etc/default/mini-httpd
> > 
> > Can you confirm?
> I will test this and get back to you as soon as I can confirm the fix.
> Documentation on /etc/default/mini-httpd options is rather scarce, do
> you mind posting a minimal /etc/default/mini-httpd file with which I
> could confirm the fix (a path or port setting perhaps)? It would speed
> up my work here as the package does not provide a default one.

here is my /etc/default/mini-httpd:

START=1
DAEMON_OPTS="-h 127.0.0.1 -p 80 -u nobody -dd /mnt/cache -i 
/var/run/mini-httpd.pid -T UTF-8"

I successfully tested the following patch to the .service file:

@@ -5,7 +5,8 @@
 [Service]
 Type=forking
 PIDFile=/run/mini_httpd.pid
-ExecStart=/usr/sbin/mini_httpd -C /etc/mini-httpd.conf
+EnvironmentFile=-/etc/default/mini-httpd
+ExecStart=/usr/sbin/mini_httpd -C /etc/mini-httpd.conf $DAEMON_OPTS -i 
/run/mini_httpd.pid
 
 [Install]
 WantedBy=multi-user.target

The EnvironmentFile uses "=-" to support a non-existant
/etc/default/mini-httpd. The ExecStart line also adds a -i option to make sure
that neither /etc/mini-httpd.conf nor $DAEMON_OPTS can set -i to something that
is different from the path in PIDFile.

What do you think?

Thanks!

cheers, josch

signature.asc
Description: signature


Processed: bug 1051864 is forwarded to https://lore.kernel.org/linux-sparse/e482a4de-55f3-25bd-4938-af05ad553...@kleine-koenig.org

2023-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1051864 
> https://lore.kernel.org/linux-sparse/e482a4de-55f3-25bd-4938-af05ad553...@kleine-koenig.org
Bug #1051864 [src:sparse] sparse: FTBFS with llvm-toolchain-16 as default
Set Bug forwarded-to-address to 
'https://lore.kernel.org/linux-sparse/e482a4de-55f3-25bd-4938-af05ad553...@kleine-koenig.org'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#1052040: mmm-mode: post-install script fails

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> forwarded -1 https://github.com/dgutov/mmm-mode/issues/137
Bug #1052040 [mmm-mode] mmm-mode: post-install script fails
Set Bug forwarded-to-address to 'https://github.com/dgutov/mmm-mode/issues/137'.
> tags -1 upstream
Bug #1052040 [mmm-mode] mmm-mode: post-install script fails
Added tag(s) upstream.

-- 
1052040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1052040: mmm-mode: post-install script fails

2023-09-16 Thread Vincent Lefevre
Control: forwarded -1 https://github.com/dgutov/mmm-mode/issues/137
Control: tags -1 upstream

On 2023-09-16 17:02:54 +0200, Vincent Lefevre wrote:
> This appears to be related to macro expansion, which seems to
> occur even if the code is not executed.

An easy solution would be to avoid the XEmacs form (marked as
obsolete in GNU Emacs since 23.1 and whose support was removed
in GNU Emacs 28[*]), i.e. change

(if (not (string-match "XEmacs" (emacs-version)))
(define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook
  "0.3.8"
  "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are 
deprecated.")
  (define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook))

to just

(define-obsolete-function-alias 'mmm-add-find-file-hooks 'mmm-add-find-file-hook
  "0.3.8"
  "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are deprecated.")

[*] https://github.com/emacs-mirror/emacs/commit/32c6732

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Processed: intel-mediasdk: ftbfs with GCC-13

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1037699 [src:intel-mediasdk] intel-mediasdk: ftbfs with GCC-13
Added tag(s) patch.

-- 
1037699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1037699: intel-mediasdk: ftbfs with GCC-13

2023-09-16 Thread Jonathan Bergh
Control: tags -1 + patch

Fixes FTBFS due to gcc-13 upgrade and closes #1037699


patch1.debdiff
Description: Binary data


Bug#1052048: texlive-bibtex-extra: Can't generate bibliography since last upgrade at trixie

2023-09-16 Thread Preuße

On 16.09.2023 17:16, Mechtilde Stehmann wrote:

Hello Mechtilde,


After last update at trixie I can't proper build https://salsa.debian.org/ddp-
team/dpb/ locally.

It builds correct on trixie at the Salsa CI at 03.09.2023. The last upload to
trixie was at 05.09.2023.

Do you have some kind of log file, showing an error message? Please 
don't send files having a size of > 100KB.



I lost the bibliography in the pdf of this big document.

That's why I set it to grave.


For now I leave it at this severity, although I don't share you opinion.

Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature


Bug#1052048: texlive-bibtex-extra: Can't generate bibliography since last upgrade at trixie

2023-09-16 Thread Mechtilde Stehmann
Package: texlive-bibtex-extra
Version: 2023.20230613-2
Severity: grave
X-Debbugs-Cc: mechti...@debian.org

After last update at trixie I can't proper build https://salsa.debian.org/ddp-
team/dpb/ locally.

It builds correct on trixie at the Salsa CI at 03.09.2023. The last upload to
trixie was at 05.09.2023.

I lost the bibliography in the pdf of this big document.

That's why I set it to grave.

Kind regards

Mechtilde


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

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

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

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

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

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

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

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

or 

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

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 root root 1956 Sep 10 08:48 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 12  2022 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Aug 27 23:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Aug 27 23:39 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Oct 18  2022 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Aug 27 23:39 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Aug 27 23:39 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3197 Sep 10 08:47 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Sep  4  2021 mktex.cnf
-rw-r--r-- 1 root root 475 Oct 18  2022 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-bibtex-extra depends on:
ii  tex-common  6.18
ii  texlive-base2023.20230613-3
ii  texlive-binaries2023.20230311.66589-4
ii  texlive-latex-base  2023.20230613-3

texlive-bibtex-extra recommends no packages.

texlive-bibtex-extra suggests no packages.

Versions of packages tex-common depends on:
ii  ucf  3.0043+nmu1

Versions of packages tex-common suggests:
ii  debhelper  13.11.6

Versions of packages texlive-bibtex-extra is related to:
ii  tex-common6.18
ii  texlive-binaries  2023.20230311.66589-4

-- no debconf information



Bug#1037570: afnix: ftbfs with GCC-13

2023-09-16 Thread Jonathan Bergh
Control: tags -1 + patch

Fixes FTBFS with gcc-13 and closes 1037570


patch1.debdiff
Description: Binary data


Processed: afnix: ftbfs with GCC-13

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 + patch
Bug #1037570 [src:afnix] afnix: ftbfs with GCC-13
Added tag(s) patch.

-- 
1037570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1052040: mmm-mode: post-install script fails

2023-09-16 Thread Vincent Lefevre
On 2023-09-16 16:53:33 +0200, Vincent Lefevre wrote:
> If I understand correctly, the second define-obsolete-function-alias
> (with 2 arguments) is executed instead of the first one (with 4
> arguments). This would mean that
> 
>   (string-match "XEmacs" (emacs-version))
> 
> finds a match. Is there any reason?

Actually, it doesn't.

This appears to be related to macro expansion, which seems to
occur even if the code is not executed.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1052040: mmm-mode: post-install script fails

2023-09-16 Thread Vincent Lefevre
Ditto here.

On 2023-09-16 14:31:11 +0200, mister...@web.de wrote:
> In toplevel form:
> mmm-auto.el:178:4: Error: Wrong number of arguments: (3 . 4), 2

This seems to be due to this change:

-(defalias 'mmm-add-find-file-hooks #'mmm-add-find-file-hook)
+(if (not (string-match "XEmacs" (emacs-version)))
+(define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook
+  "0.3.8"
+  "Both `mmm-add-find-file-hooks' and `mmm-add-find-file-hook' are 
deprecated.")
+  (define-obsolete-function-alias 'mmm-add-find-file-hooks 
'mmm-add-find-file-hook))

If I understand correctly, the second define-obsolete-function-alias
(with 2 arguments) is executed instead of the first one (with 4
arguments). This would mean that

  (string-match "XEmacs" (emacs-version))

finds a match. Is there any reason?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)



Bug#1051374: breaks existing setups using /etc/default/mini-httpd

2023-09-16 Thread Alexandru Mihail
Hello, 
> 
> > > 
> > > If possible it would of course be nice if the systemd service
> > > would not break
> > > user's setups and would continue to consume /etc/default/mini-
> > > httpd.
> > 
> > this issue has now made the mmdebstrap jenkins job fail for 10 days
> > in a row:
> > 
> > https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/
I can confirm the issue and this will be addressed. This is NOT
intentional, thus no NEWS entry will be added.

> 
> > Or will you restore
> > compatibility with existing setups using /etc/default/mini-httpd so
> > that I
> > need to do nothing and just wait for an upload fixing this?
> 
Yes, this is the intended course of action.
> I asked in #debian-systemd and the fix could be as simple as setting
> the
> following in the .service file:
> 
> EnvironmentFile=-/etc/default/mini-httpd
> 
> Can you confirm?
I will test this and get back to you as soon as I can confirm the fix.
Documentation on /etc/default/mini-httpd options is rather scarce, do
you mind posting a minimal /etc/default/mini-httpd file with which I
could confirm the fix (a path or port setting perhaps)? It would speed
up my work here as the package does not provide a default one.
> 
> Thanks!
> 
> cheers, josch
Cheers,
Alexandru Mihail



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


Bug#1037400: spacefm: build-depends on transitional package libgdk-pixbuf2.0-dev

2023-09-16 Thread Bastian Germann

On Mon, 12 Jun 2023 11:55:56 +0100 Simon McVittie wrote:

If this package only requires functionality from gdk-pixbuf-2.0.pc
and , please update the build-dependency to
libgdk-pixbuf-2.0-dev.

If it also requires the Xlib integration gdk-pixbuf-xlib-2.0.pc and
 (unlikely), then you can also build-depend on
libgdk-pixbuf-xlib-2.0-dev until the package can be updated to remove
that requirement.


Only libgdk-pixbuf-2.0-dev is required. Please update the package.



Bug#1051886: marked as pending in qtbase-opensource-src

2023-09-16 Thread Dmitry Shachnev
Control: tag -1 pending

Hello,

Bug #1051886 in qtbase-opensource-src reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/qt-kde-team/qt/qtbase/-/commit/830c9dcdde8b1ed0463bd4368a2ac60610fc34ae


Add a patch from OpenMandriva to work around broken pyside2 build.

Closes: #1051886.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051886



Processed: Bug#1051886 marked as pending in qtbase-opensource-src

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #1051886 [src:pyside2] pyside2: FTBFS with llvm-toolchain-16 as default
Added tag(s) pending.

-- 
1051886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1051819: fluidsynth: Consider building with pipewire support

2023-09-16 Thread Johannes Schauer Marin Rodrigues
Hi Nicholas,

Quoting Nicholas D Steeves (2023-09-16 14:06:00)
> Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
> fluidsynth -dev package.  'not sure how that happened, but my mistake!  Isn't
> only waiting 48h a bit rushed for an NMU though?

the number of delayed days are documented here:

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#when-and-how-to-do-an-nmu

It seems that indeed a 0-day nmu was a bit too quick here.

> I can of course import your fix and upload in the next 48h, and I'd like to
> improve your changelog entry, because I think you'll agree that the concept
> of "runtime" doesn't make sense for headers ;)

It does make sense as we have two types of dependencies in Debian: build
dependencies and runtime dependencies. A header package is also a binary
package so it has runtime dependencies like all other binary packages do.

But indeed the term "runtime dependency" is not very widely used. I do not
think that Debian policy uses it. I think the term is mostly used by people
like me who work on dependency resolution software.

> If this is truly 0-day urgent, I'm confident a team member (IIRC Josch is a
> multimedia-team member) will upload.

I'm afraid it was already uploaded and is now in unstable. :(

> ('hope this isn't HTML email, since I'm currently AFK on a phone)

It was HTML but it also had a text/plain part. :)

Thanks!

cheers, josch

signature.asc
Description: signature


Bug#1042140: marked as done (trophy: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libclanCore.so: undefined reference to `pthread_mutexattr_setkind_np')

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 15:10:45 +0200
with message-id <1bd108cd7e066e15f649f87956c8b3fb8fed2a15.ca...@debian.org>
and subject line Re: trophy: FTBFS:  undefined reference to 
`pthread_mutexattr_setkind_np'
has caused the Debian Bug report #1042140,
regarding trophy: FTBFS: ld: 
/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libclanCore.so: 
undefined reference to `pthread_mutexattr_setkind_np'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1042140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042140
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trophy
Version: 2.0.3-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> g++ -Wall -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security  -Wl,-z,relro -o 
> trophy cagoody.o cainfodialog.o caescapedialog.o canetserver.o 
> casoundeffect.o camenuinput.o capositiontableview.o cagoodytype.o calabel.o 
> capanel.o caconfigurekey.o shopscreen.o cartype.o caimagehueselector.o 
> camenuitem.o camenuselect.o caresources.o calineedit.o player.o track.o 
> guibox.o cacredits.o caimagemanipulation.o camenulabel.o cascreen.o 
> catrophy.o cacarupgrades.o caloadingscreen.o caplayersettingsdialog.o 
> cadialog.o caimageselector.o cachampionshipscreen.o casignupscreen.o 
> cawidget.o trophymath.o caplayerview.o caimageview.o canetclient.o 
> caslotselectiondialog.o camenu.o capositiontable.o humanplayer.o 
> computerplayer.o upgradespanel.o windialog.o -lclanGL -lclanSound 
> -lclanDisplay -lclanCore -lclanSignals -lclanApp  -lclanSignals 
> /usr/bin/ld: 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/libclanCore.so: 
> undefined reference to `pthread_mutexattr_setkind_np'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/trophy_2.0.3-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.0~svn3827-11

Fixed in clanlib 1.0~svn3827-11.


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


Bug#1043124: zfs-dkms: module fails to build for Linux 6.5: None of the expected "bops->release()" interfaces were detected.

2023-09-16 Thread Francesco C
>(Completely unrelated, but browsing the issues it popped up that encryption is
>very broken above 6.3,
>and it has been somewhat broken on older kernels too; not one people lost their
>data due to upgrading
> beyond 6.3, so beware.

"Encryption is very broken" seems too generic : it seems (to me) that
the reported issue affects zfs "native" encryption , not luks with
[(plain) zfs].



Bug#1052038: lxpanel: Segmentation fault in Gnome desktop

2023-09-16 Thread 陳昌倬
control: retitle -1 lxpanel: Segmentation fault in Gnome desktop
control: severity -1 minor


After testing, lxpanel works in sddm + LXDE desktop. It only has
segfault in gdm3 + gnome.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
https://czchen.org/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature


Processed: lxpanel: Segmentation fault in Gnome desktop

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 lxpanel: Segmentation fault in Gnome desktop
Bug #1052038 [lxpanel] lxpanel: Segmentation fault when startup
Changed Bug title to 'lxpanel: Segmentation fault in Gnome desktop' from 
'lxpanel: Segmentation fault when startup'.
> severity -1 minor
Bug #1052038 [lxpanel] lxpanel: Segmentation fault in Gnome desktop
Severity set to 'minor' from 'grave'

-- 
1052038: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1052031: marked as done (python-libcst: FTBFS: error: no matching package named `thiserror` found)

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 12:53:52 +
with message-id 
and subject line Bug#1052031: fixed in python-libcst 1.0.1-2
has caused the Debian Bug report #1052031,
regarding python-libcst: FTBFS: error: no matching package named `thiserror` 
found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-libcst
Version: 1.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=python-libcst=amd64=1.0.1-1%2Bb2=1694694414=0

cargo rustc --lib --message-format=json-render-diagnostics --manifest-path 
native/libcst/Cargo.toml --release -v --features pyo3/extension-module -- 
--crate-type cdylib
error: no matching package named `thiserror` found
location searched: registry `crates-io`
required by package `libcst v0.5.0 (/<>/native/libcst)`
error: `cargo rustc --lib --message-format=json-render-diagnostics 
--manifest-path native/libcst/Cargo.toml --release -v --features 
pyo3/extension-module -- --crate-type cdylib` failed with code 101

ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:395: build: plugin pyproject failed with: exit code=1: 
python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir 
/<>/.pybuild/cpython3_3.11 
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit 
code 13
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 25

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: python-libcst
Source-Version: 1.0.1-2
Done: Jelmer Vernooij 

We believe that the bug you reported is fixed in the latest version of
python-libcst, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated python-libcst package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 16 Sep 2023 12:42:54 +0100
Source: python-libcst
Architecture: source
Version: 1.0.1-2
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Closes: 1052031
Changes:
 python-libcst (1.0.1-2) unstable; urgency=medium
 .
   * Add missing build dependencies on librust-{getopts,thiserror}-dev.
 Closes: #1052031
   * Add patch drop-pyre-tests: Disable tests that require pyre.
Checksums-Sha1:
 a8a04b4311836c0a9e43d9cea4a14b7dc42f8865 1990 python-libcst_1.0.1-2.dsc
 5a2d6648842e2af0c168dd14956c64015a089a8f 5412 
python-libcst_1.0.1-2.debian.tar.xz
 265a9bbc556a7bfd2f4128581fa2aea968bb88ab 23363 
python-libcst_1.0.1-2_source.buildinfo
Checksums-Sha256:
 c740be56c4e03d172e0d2a9d1356fbd4e09aba49f91c29f6d5d4833bbb79d0d1 1990 
python-libcst_1.0.1-2.dsc
 0f6ddfe480f4a2526d488a21b30a021a5e8e5a8c843ae2c869a8fd1c61d1431d 5412 
python-libcst_1.0.1-2.debian.tar.xz
 7490404f1c2f5741e782ae80f4ed7833c171cb3f6c53c796e1c85edb21da0315 23363 
python-libcst_1.0.1-2_source.buildinfo
Files:
 cf94b2bfbcde626596ed1aa8708e77fe 1990 python optional python-libcst_1.0.1-2.dsc
 e99bab2348d0285d5712b9b078dfb1c9 5412 python optional 
python-libcst_1.0.1-2.debian.tar.xz
 05ed60ea62cde0d4cb5c28b27cdee6ab 23363 python optional 
python-libcst_1.0.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmUFlbkACgkQMG8hYYBC
UGamJQf/RdB9eJFaw+v21Ca+YSeugb3UaHgt9+Z1N9ZTN/AEDaVV8n3U6RGbRrnY
bhRa7P0kPEFFBBXz46oml1WjAyBcIzVT3o2Cb9SVzu5v7wTD9kIIlDmKglNMJ+LG
0B490TG5foY3UmxjF+XvFgoNafESThRRTp+gLTAs1b7gJDuFWjG1XLLV+LE78tp+
PwH1lqXioAEaL96uX5HYkEF7+L7AyScGyc14rOxsdu47gpgWXPPLDeXSgSQwfyrM
twjEglZU4tZezpmYNVRquzFdX8i2PBrPoWRDDyfETyd3fScHZyt7tIiC2dnWF1TJ
dh/IWHVxm4XX8ZXBQ3E7J2ZUvv8Knw==
=UuCv
-END PGP SIGNATURE End Message ---


Bug#1050676: enblend-enfuse: FTBFS: dot: maze.c:311: chkSgraph: Assertion `np->cells[0]' failed.

2023-09-16 Thread Andreas Metzler
On 2023-09-15 "László Böszörményi (GCS)"  wrote:
[...]
>  There's still a font issue, you will get something like:
> fontconfig: Didn't find expected font family. Perhaps URW Type 1 fonts
> need installing?

> I don't know why this is happening, as if I check the intermediate dot
> file then only the node font settings cause this error. Other uses of
> the Helvetica font are fine. As per source change, you will need this
> patch for enblend-enfuse.
> Please check if the resulting package works as you expected or not and
> report back your findings.
[...]

except for the expect font difference (Times) this seems to work ok. -
Thanks.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#1052040: mmm-mode: post-install script fails

2023-09-16 Thread mister01x
Package: mmm-mode
Version: 0.5.9-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: mister...@web.de

Dear Maintainer,

installation/upgrading of the package fails with the following output
(please excuse the automatic line wrapping of thunderbirds plain text mode):

# LANG=C apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up mmm-mode (0.5.9-1) ...
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install mmm-mode for emacs
install/mmm-mode: Handling install of emacsen flavor emacs
install/mmm-mode: byte-compiling for emacs

In toplevel form:
mmm-auto.el:178:4: Error: Wrong number of arguments: (3 . 4), 2

In toplevel form:
mmm-class.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-cmds.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-cweb.el:35:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-defaults.el:37:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-erb.el:62:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-mason.el:36:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-mode.el:93:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-myghty.el:41:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-noweb.el:44:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-region.el:42:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-rpm.el:45:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-sample.el:38:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)

In toplevel form:
mmm-univ.el:35:2: Error: Eager macro-expansion failure:
(wrong-number-of-arguments (3 . 4) 2)
ERROR: install script from mmm-mode package failed
dpkg: error processing package mmm-mode (--configure):
 installed mmm-mode package post-installation script subprocess returned
error exit status 1
Errors were encountered while processing:
 mmm-mode
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)



Thanks for maintaining mmm-mode

Marcel

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

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

Versions of packages mmm-mode depends on:
ii  emacs-gtk [emacsen]  1:29.1+1-5
ii  emacsen-common   3.0.5

mmm-mode recommends no packages.

mmm-mode suggests no packages.

-- no debconf information



Bug#1025582: marked as done (lxde-metapackages: recommends transitional policykit-1 package)

2023-09-16 Thread Debian Bug Tracking System
Your message dated Sat, 16 Sep 2023 12:06:55 +
with message-id 
and subject line Bug#1025582: fixed in lxde-metapackages 12
has caused the Debian Bug report #1025582,
regarding lxde-metapackages: recommends transitional policykit-1 package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1025582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lxde-metapackages
Version: 11
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1

This package has a Recommends on the transitional package policykit-1,
which has been separated into polkitd, pkexec and (deprecated)
polkitd-pkla packages.

If the intended functionality for this metapackage is the polkitd D-Bus
service, please represent that as a Depends, Recommends or Suggests on
polkitd.

If the intended functionality is the ability to run /usr/bin/pkexec,
please represent that as a Depends, Recommends or Suggests on pkexec.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: lxde-metapackages
Source-Version: 12
Done: ChangZhuo Chen (陳昌倬) 

We believe that the bug you reported is fixed in the latest version of
lxde-metapackages, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated lxde-metapackages 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 16 Sep 2023 11:34:27 +0800
Source: lxde-metapackages
Architecture: source
Version: 12
Distribution: unstable
Urgency: medium
Maintainer: Debian LXDE Maintainers 
Changed-By: ChangZhuo Chen (陳昌倬) 
Closes: 1025582
Changes:
 lxde-metapackages (12) unstable; urgency=medium
 .
   [ Pino Toscano ]
   * Drop menu-xdg recommend, as it is deprecated, and not needed by LXDE.
 .
   [ ChangZhuo Chen (陳昌倬) ]
   * Bump Standards-Version to 4.6.2.
   * Bump compat to 13.
   * Migrate policykit-1 to polkitd. (Closes: #1025582)
   * Change team email to .
   * Add d/salsa-ci.yml.
   * d/control: Tweak indent.
   * Add ChangZhuo Chen (陳昌倬) as Uploaders.
Checksums-Sha1:
 a28a412f4eba8e5f2c4da4f5e196ce5f9d00035f 1802 lxde-metapackages_12.dsc
 eb1a4a19d9bb8801fe4d93ef148678560e882542 4504 lxde-metapackages_12.tar.xz
 ed701bd6a4c03402dd2cb9ed96540508ccfb7708 6043 
lxde-metapackages_12_source.buildinfo
Checksums-Sha256:
 4bdde6e32ec5cf47a2e4bffa672a293313514e153d540018315aace6932abc66 1802 
lxde-metapackages_12.dsc
 7e74e440a6f5ca6f0d9deb2a51846db7c2af5bad360ff66f63ab9c8942018887 4504 
lxde-metapackages_12.tar.xz
 54ddffe5f8a56ea7a47dea6b9818ec7866ac8dcca7f22872f9b354d8b3cd7451 6043 
lxde-metapackages_12_source.buildinfo
Files:
 9c3e7f0763ae01f1d096cb1f9244e73c 1802 metapackages optional 
lxde-metapackages_12.dsc
 ed4ae4c4ab9a3a5cbb89a76a096eecff 4504 metapackages optional 
lxde-metapackages_12.tar.xz
 64f1496b2f5dccb6a8de44afa582 6043 metapackages optional 
lxde-metapackages_12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE703UlH90QYpfEyJV58vhUqwX+XMFAmUFkWUACgkQ58vhUqwX
+XMgWw//fyTbXSVWBRd9RoKuBCSqbewvI0JMltRnJTJgdNkLsVAhtf7mEnzUF74W
7hQ1TluA06lec+9Ln9z2z26E5A7HC+02/MZR8jRQDg12XxtLsxy+vVPaGOZbhbAZ
mOk1rnwBeWz76qRLMYQK8+4CwNm8xv1APGKK0xY4fcck3DW9nXeusGPWFR0k7aQM
OG4e0D7JMMTWGm2y+yPlhOisRi+HouyaxKIAZiCMlcYNkD0rlzqYuw+OWyXBs2Tb
FuIiyG9KkhrLcQ11DrvyRIbJPyqTYgDxJRjLxCxJOlCBp3MArZS//rSdYhTyf6bq
8DhEm8XoMI8PbKF8jfU4P4ojxzku+X6UHJm4WsJPUjR9vhbdIDU+sAdSFuNKOm/8
xVIUvMUVOz0PnKDTlWqtewu1tv5YuQac32Nm7xQmZZzIE9tqX0wzO01B+U1/TTN+
2jamV0GOJY0D/xHoQZDz3uNW8vcJjlcpHkEqhg+COuky4jp7bKD3JTYvb5iD6ehG
gIvSoMvAS/q3gqv85H+1P2woo/l1nzhv7YYlPlp0hV6iCj/C73/IBpwm6wb6U5QH
bnIFMctoWBb1H2OxDbT64xA4Uuc7ulWhWq2SMY2tpb/C7prVZr19gRem8iR7tnJN
Ik58322cx0v5F+Jl4M8Hqvi9s8HhA13Paw3HqaiO/py7ud5S/qg=
=FhAN
-END PGP SIGNATURE End Message ---


Bug#1051819: fluidsynth: Consider building with pipewire support

2023-09-16 Thread Nicholas D Steeves
Hi Gianfranco,

Oh my, yes, it seems I forgot to add the new pipewire -dev package to the
fluidsynth -dev package.  'not sure how that happened, but my mistake!
Isn't only waiting 48h a bit rushed for an NMU though?  I can of course
import your fix and upload in the next 48h, and I'd like to improve your
changelog entry, because I think you'll agree that the concept of "runtime"
doesn't make sense for headers ;)  If this is truly 0-day urgent, I'm
confident a team member (IIRC Josch is a multimedia-team member) will
upload.

Cheers,
Nicholas

('hope this isn't HTML email, since I'm currently AFK on a phone)


Bug#1052038: lxpanel: Segmentation fault when startup

2023-09-16 Thread 陳昌倬
Package: lxpanel
Version: 0.10.1-4
Severity: grave
Justification: renders package unusable


lxpanel receives signal SIGSEGV, Segmentation fault when startup, and
cause it unusable.


  $ gdb lxpanel
  Reading symbols from lxpanel...
  Reading symbols from 
/usr/lib/debug/.build-id/e2/41004afdf79e3c7d83166b0fec1c7d09733a4b.debug...
  (gdb) r
  Starting program: /usr/bin/lxpanel 
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x757ff6c0 (LWP 315599)]
  [New Thread 0x7fffe6c0 (LWP 315600)]
  [New Thread 0x74ffe6c0 (LWP 315601)]
  [New Thread 0x7fffef7fe6c0 (LWP 315602)]
  [New Thread 0x7fffeeffd6c0 (LWP 315603)]
  
  Thread 1 "lxpanel" received signal SIGSEGV, Segmentation fault.
  0x0003 in ?? ()
  (gdb) bt
  #0  0x0003 in ?? ()
  #1  0x76f1bb6f in XInternAtoms () from 
/lib/x86_64-linux-gnu/libX11.so.6
  #2  0x77fa60ef in resolve_atoms () at ./src/misc.c:380
  #3  0x55563212 in main (argc=, argv=, 
env=0x7fffd208) at ./src/main.c:489




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

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

Versions of packages lxpanel depends on:
ii  libasound2   1.2.10-1
ii  libc62.37-9
ii  libcairo21.17.8-3
ii  libcurl3-gnutls  8.3.0-1
ii  libfm-gtk3-4 1.3.2-4
ii  libfm-modules1.3.2-4
ii  libfm4   1.3.2-4
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.78.0-1
ii  libgtk-3-0   3.24.38-5
ii  libiw30  30~pre9-14
ii  libkeybinder-3.0-0   0.3.2-1.1
ii  libmenu-cache3   1.1.0-1.1
ii  libpango-1.0-0   1.51.0+ds-2
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.6-1
ii  libxml2  2.9.14+dfsg-1.3
ii  lxmenu-data  0.1.5-2.1
ii  lxpanel-data 0.10.1-4

Versions of packages lxpanel recommends:
ii  gnome-shell [notification-daemon] 44.4-1
ii  gnome-terminal [x-terminal-emulator]  3.49.99-1
ii  libnotify-bin 0.8.2-1
ii  lxqt-notificationd [notification-daemon]  1.3.0-1
ii  lxterminal [x-terminal-emulator]  0.4.0-2
ii  notification-daemon   3.20.0-4+b1
ii  pavucontrol   5.0-2
ii  qterminal [x-terminal-emulator]   1.3.0-1
ii  xkb-data  2.38-2
ii  xterm [x-terminal-emulator]   384-1

Versions of packages lxpanel suggests:
ii  firefox-esr [www-browser]   115.2.1esr-1
ii  google-chrome-stable [www-browser]  117.0.5938.88-1
ii  lynx [www-browser]  2.9.0dev.12-1

-- no debconf information

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
https://czchen.org/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature


Bug#1052037: Can't be imported on armel

2023-09-16 Thread Andrey Rakhmatullin
Package: python3-fasttext
Version: 0.9.2+ds-4
Severity: serious

Found in dateparser autopkgtest logs and confirmed on the armel porterbox:

>>> import fasttext_pybind
Traceback (most recent call last):
  File "", line 1, in 
ImportError: /usr/lib/python3/dist-packages/fasttext_pybind.cpython-311-arm-
linux-gnueabi.so: undefined symbol: __atomic_load_8


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

Kernel: Linux 6.4.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU:ru
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-fasttext depends on:
ii  libc6  2.37-8
ii  libgcc-s1  13.2.0-3
ii  libstdc++6 13.2.0-3
ii  python33.11.4-5+b1
ii  python3-numpy  1:1.24.2-1
ii  python3-pkg-resources  68.1.2-1
pn  python3-pybind11   

python3-fasttext recommends no packages.

python3-fasttext suggests no packages.



Processed: tagging 1052035, tagging 1051980, tagging 1051850, tagging 1051819, tagging 1051616, tagging 1051573 ...

2023-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1052035 + sid trixie
Bug #1052035 [src:ulex0.8] ulex0.8: FTBFS: Error: This expression has type char 
Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status but an expression 
was expected of type 'a ref
Added tag(s) sid and trixie.
> tags 1051980 + sid trixie
Bug #1051980 [src:lib2geom] FTBFS on i386: angle-test/bezier-test fail
Added tag(s) trixie and sid.
> tags 1051850 + sid trixie
Bug #1051850 [pastescript] pastescript: FTBFS due to new dh-python clean 
behaviour
Added tag(s) sid and trixie.
> tags 1051819 + sid trixie
Bug #1051819 {Done: Gianfranco Costamagna } 
[fluidsynth] fluidsynth: Consider building with pipewire support
Added tag(s) trixie and sid.
> tags 1051616 + sid trixie
Bug #1051616 {Done: Philip Rinn } [src:rawtherapee] FTBFS: 
error: ‘uint32_t’ does not name a type
Added tag(s) trixie and sid.
> tags 1051573 + sid trixie
Bug #1051573 [src:bambootracker] bambootracker: FTBFS with RtAudio 6
Added tag(s) sid and trixie.
> tags 1051435 + sid trixie
Bug #1051435 [src:python-pytest-asyncio] python-pytest-asyncio: failing 
autopkgtest
Added tag(s) sid and trixie.
> tags 1051400 + sid trixie
Bug #1051400 [tp-smapi-dkms] tp-smapi-dkms: update DEFINE_SEMAPHORE usage for 
linux 6.4+
Added tag(s) sid and trixie.
> tags 1051311 + sid trixie
Bug #1051311 {Done: Jelmer Vernooij } [src:xandikos] 
xandikos: autopkgtests failures against new dulwich
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051311
1051400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051400
1051435: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051435
1051573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051573
1051616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051616
1051819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051819
1051850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051850
1051980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051980
1052035: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052035
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1036076: rust-mysqlclient-sys appears to be unsound when used with mariadb.

2023-09-16 Thread Matthias Geiger

On Mon, 15 May 2023 05:47:10 +0100 Peter Green  wrote:
> Package: rust-mysqlclient-sys
> Severity: serious
>
> I was looking at why rust-diesel was not migrating to testing
> (other than the freeze obviously) and noticed that rust-mysqlclient-sys
> was not built on 32-bit architectures. As with a bunch of other
> packages I correctly suspected this was mostly a case of unportable
> bindgen-generated tests and started preparing fixes for them.
>
> However while doing so, I rapidly came to the conclusion that something
> else was wrong. Specifically I noticed significant discrepancies
> between the "mysql" (actually mariadb) C headers on my system and the
> rust bindings in rust-mysqlclient-sys.
>
> The tests in the crate only test that the size/alignment of the
> structures defined in the crate are consistent with what they were
> when the bindings were generated. They do not check in any way that
> they are consistent with the structures defined by the C headers on
> the user's system. There are no functional tests either.
>
> My conclusion is that attempting to use this crate with mariadb
> is highly unsound, though I don't know enough about how the mysql
> client library is used to determine in what way exactly it will break
> and whether the breakage is likely to be immediately apparent or more
> subtle.
>
>

>

Control: severity -1 important

lowering severity so it and rdeps can migrate. I skipped the failing 
tests for now.


--
Matthias Geiger (werdahias)
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1052035: ulex0.8: FTBFS: Error: This expression has type char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status but an expression was expected of type 'a ref

2023-09-16 Thread Stéphane Glondu

Hi,

Le 16/09/2023 à 12:54, Sebastian Ramacher a écrit :

Source: ulex0.8
Version: 1.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
[...]


See https://bugs.debian.org/1051377


Cheers,

--
Stéphane



Bug#1052035: ulex0.8: FTBFS: Error: This expression has type char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status but an expression was expected of type 'a ref

2023-09-16 Thread Sebastian Ramacher
Source: ulex0.8
Version: 1.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ulex0.8=amd64=1.2-2%2Bb5=1694049779=0

ocamlfind ocamlc -c -package camlp5 -pp 'camlp5o pa_macro.cmo pa_extend.cmo 
q_MLast.cmo' -o pa_ulex.cmo pa_ulex.ml
+ ocamlfind ocamlc -c -package camlp5 -pp 'camlp5o pa_macro.cmo pa_extend.cmo 
q_MLast.cmo' -o pa_ulex.cmo pa_ulex.ml
findlib: [WARNING] Interface topdirs.cmi occurs in several directories: 
/usr/lib/ocaml, /usr/lib/ocaml/compiler-libs
File "pa_ulex.ml", line 267, characters 26-44:
267 |   let old_parse_implem = !Pcaml.parse_implem in
^^
Error: This expression has type
 char Stream.t -> (MLast.str_item * MLast.loc) list * Pcaml.status
   but an expression was expected of type 'a ref
Command exited with code 2.
make[2]: *** [Makefile:5: all] Error 10

Cheers
-- 
Sebastian Ramacher



Bug#1052034: procps: FTBFS on amd64, i386: # of unexpected failures 1

2023-09-16 Thread Sebastian Ramacher
Source: procps
Version: 2:4.0.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=procps=amd64=2%3A4.0.4-1=1694089907=0

WARNING: Couldn't find tool init file
Test run by buildd on Thu Sep  7 12:31:32 2023
Native configuration is x86_64-pc-linux-gnu

=== pmap tests ===

Schedule of variations:
unix

Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for 
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using /<>/testsuite/config/unix.exp as tool-and-target-specific 
interface file.
Running /<>/testsuite/pmap.test/pmap.exp ...
FAIL: pmap XX pid pid has same total

=== pmap Summary ===

# of expected passes13
# of unexpected failures1
/<>/src/pmap version 4.0.4

WARNING: Couldn't find tool init file
Test run by buildd on Thu Sep  7 12:31:32 2023
Native configuration is x86_64-pc-linux-gnu


Cheers
-- 
Sebastian Ramacher



Bug#1052032: msc-generator: FTBFS: [Makefile:793: check-local] Error 1

2023-09-16 Thread Sebastian Ramacher
Source: msc-generator
Version: 8.4.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=msc-generator=amd64=8.4.1-3=1694294426=0

echo doc/ex01.exit doc/ex02.exit doc/ex03.exit doc/ex04.exit doc/ex05.exit 
doc/ex06.exit doc/ex07.exit doc/ex08.exit doc/ex09.exit doc/ex10.exit 
doc/ex11.exit doc/ex12.exit doc/ex13.exit doc/ex14.exit doc/ex15.exit 
doc/ex16.exit doc/ex17.exit doc/ex18.exit doc/ex19.exit doc/ex20.exit 
doc/ex21.exit doc/ex22.exit doc/ex23.exit doc/ex24.exit doc/ex25.exit 
doc/ex26.exit doc/ex27.exit doc/ex29.exit doc/ex30.exit doc/ex31.exit 
doc/ex32.exit doc/ex33.exit doc/ex34.exit doc/ex35.exit doc/ex36.exit 
doc/ex37.exit doc/ex38.exit doc/ex39.exit doc/ex40.exit doc/ex41.exit 
doc/ex42.exit doc/ex43.exit doc/ex44.exit doc/ex45.exit doc/ex46.exit 
doc/ex47.exit doc/ex48.exit doc/ex49.exit doc/ex50.exit doc/ex51.exit 
doc/ex52.exit doc/ex53.exit doc/ex54.exit doc/ex55.exit doc/ex56.exit 
doc/ex57.exit doc/ex58.exit doc/ex59.exit doc/ex60.exit doc/ex61.exit 
doc/ex62.exit doc/ex63.exit doc/ex64.exit doc/ex65.exit doc/ex66.exit 
doc/ex67.exit doc/ex68.exit doc/ex69.exit doc/ex70.exit doc/ex71.exit 
doc/ex72.exit doc/ex73.exit doc/ex74.exit doc/ex75.exit doc/ex76.exit 
doc/ex77.exit doc/ex78.exit doc/ex79.exit doc/ex80.exit doc/ex81.exit 
doc/ex82.exit doc/ex83.exit doc/ex84.exit doc/ex85.exit doc/ex86.exit 
doc/ex87.exit doc/ex88.exit doc/ex89.exit doc/ex90.exit doc/ex91.exit 
doc/ex92.exit doc/ex93.exit doc/ex94.exit doc/ex95.exit doc/ex96.exit 
doc/ex97.exit doc/ex98.exit doc/ex99.exit doc/exA0.exit doc/exA1.exit 
doc/exA2.exit doc/exA3.exit doc/exA4.exit doc/exA5.exit doc/exA6.exit 
doc/exB1.exit doc/exB2.exit doc/exB3.exit doc/exB4.exit doc/exB5.exit 
doc/exB6.exit doc/exB7.exit doc/exB8.exit doc/exB9.exit doc/exBA.exit 
doc/exBD.exit doc/exBE.exit doc/exBF.exit doc/exH0.exit doc/exC0.exit 
doc/exC1.exit doc/exC2.exit doc/exC3.exit doc/exC4.exit doc/exC5.exit 
doc/exC6.exit doc/exC7.exit doc/exC8.exit doc/exC9.exit doc/exD0.exit 
doc/exD1.exit doc/exD2.exit doc/exD3.exit doc/exD4.exit doc/exD5.exit 
doc/exD6.exit doc/exD7.exit doc/exD8.exit doc/exD9.exit doc/exE0.exit 
doc/exE1.exit doc/exE2.exit doc/exE3.exit doc/exE4.exit doc/exE5.exit 
doc/exE6.exit doc/exE7.exit doc/exE8.exit doc/exE9.exit doc/exF0.exit 
doc/exF1.exit doc/exF2.exit doc/exF3.exit doc/exF4.exit doc/exF5.exit 
doc/exF6.exit doc/exF7.exit doc/exF8.exit doc/exF9.exit doc/exG0.exit 
doc/exG1.exit doc/exG2.exit doc/exG3.exit doc/exG4.exit doc/exG5.exit 
doc/exG6.exit doc/exG7.exit doc/exG8.exit doc/exG9.exit doc/exH1.exit 
doc/exH2.exit doc/exH3.exit doc/exH4.exit doc/exH5.exit doc/exH6.exit 
doc/exH7.exit doc/exH8.exit doc/exH9.exit doc/exI0.exit doc/exI1.exit 
doc/exI2.exit doc/exI3.exit doc/exI4.exit doc/exI5.exit doc/exI6.exit 
doc/exI7.exit doc/exI8.exit doc/exI9.exit doc/exJ0.exit doc/exJ1.exit 
doc/exA7.exit doc/exA8.exit doc/exA9.exit doc/exB0.exit doc/exBB.exit 
doc/exBC.exit basic/Block_arrows.exit basic/CDIV_Uncond_online.exit 
basic/Complex.exit basic/Dinand.exit basic/Grouped_entities.exit 
basic/Grouped_entities_2.exit basic/Grouped_entities_3.exit 
basic/International1.exit basic/International1_utf16.exit 
basic/SpecialEndings.exit basic/WidthCalcAlgo.exit basic/actor.exit 
basic/aline.exit basic/arrow_joins.exit basic/arrows.exit basic/boxes.exit 
basic/dini.exit basic/entities.exit basic/ex28_color2.exit basic/g_mini.exit 
basic/gvarrows.exit basic/links.exit basic/looong_note_arrow.exit 
basic/lost_note_arrowhead.exit basic/m2m.exit basic/m_mini.exit 
basic/m_nocomment_small.exit basic/mscgen.exit basic/nested_if.exit 
basic/notes_joins.exit basic/old_test.exit basic/pipes.exit 
basic/self-arrow-join.exit basic/shapes.exit basic/symbols.exit 
basic/test1.exit basic/test_small.exit basic/v5.2features.exit 
basic/variables.exit basic/verticals.exit basic/wonkiness.exit 
basic/wonkiness2.exit basic/wonkiness3.exit basic/wonkiness4.exit 
basic/wonkiness5.exit basic/cshfix.exit basic/variables_block.exit 
basic/escapes.exit basic/record.exit basic/variables_graph.exit 
notes/Block_arrows_note.exit notes/Dinand_note.exit 
notes/Grouped_entities_2_note.exit notes/Grouped_entities_note.exit 
notes/arrows_note.exit notes/boxcollapse_notes.exit notes/boxes_note.exit 
notes/dini_note.exit notes/entities_note.exit notes/ex37_note.exit 
notes/old_test_note.exit notes/pipes_note.exit notes/symbols_note.exit 
notes/test1_note.exit procedures/Block_arrows_proc.exit 
procedures/CDIV_Uncond_online_proc.exit procedures/Complex_proc.exit 
procedures/Dinand_proc.exit procedures/Grouped_entities_2_proc.exit 
procedures/Grouped_entities_3_proc.exit procedures/Grouped_entities_proc.exit 
procedures/International1_proc.exit procedures/International1_utf16_proc.exit 
procedures/SpecialEndings_proc.exit procedures/WidthCalcAlgo_proc.exit 
procedures/actor_proc.exit procedures/aline_proc.exit 

Bug#1052030: delve: FTBFS

2023-09-16 Thread Sebastian Ramacher
Source: delve
Version: 1.21.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=delve=amd64=1.21.0-2%2Bb2=1694856639=0

--- PASS: TestIssue406 (0.40s)
=== RUN   TestEvalExprName
common_test.go:20: failed assertion at integration2_test.go:1651: 
EvalVariable - could not find symbol value for i1
--- FAIL: TestEvalExprName (0.42s)

Cheers
-- 
Sebastian Ramacher



Bug#1052031: python-libcst: FTBFS: error: no matching package named `thiserror` found

2023-09-16 Thread Sebastian Ramacher
Source: python-libcst
Version: 1.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=python-libcst=amd64=1.0.1-1%2Bb2=1694694414=0

cargo rustc --lib --message-format=json-render-diagnostics --manifest-path 
native/libcst/Cargo.toml --release -v --features pyo3/extension-module -- 
--crate-type cdylib
error: no matching package named `thiserror` found
location searched: registry `crates-io`
required by package `libcst v0.5.0 (/<>/native/libcst)`
error: `cargo rustc --lib --message-format=json-render-diagnostics 
--manifest-path native/libcst/Cargo.toml --release -v --features 
pyo3/extension-module -- --crate-type cdylib` failed with code 101

ERROR Backend subprocess exited when trying to invoke build_wheel
E: pybuild pybuild:395: build: plugin pyproject failed with: exit code=1: 
python3.11 -m build --skip-dependency-check --no-isolation --wheel --outdir 
/<>/.pybuild/cpython3_3.11 
dh_auto_build: error: pybuild --build -i python{version} -p 3.11 returned exit 
code 13
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 25

Cheers
-- 
Sebastian Ramacher



Bug#1051563: Backporting mutt patches to Debian Buster

2023-09-16 Thread Utkarsh Gupta
Hi Chris,

On Fri, Sep 15, 2023 at 8:09 PM Chris Frey  wrote:
> Attached is a patch that applies to the unpackaged sources of Debian Buster's
> version of mutt 1.10.
>
> It includes 3 patches:
>
> upstream/Fix-rfc2047-base64-decoding-to-abort-on-illegal-char.patch
> debian-specific/Check-for-NULL-userhdrs.patch
> debian-specific/Fix-write_one_header-illegal-header-check.patch
>
> First one applied from Bullseye.  The other two I modified slightly
> to match the older sources.

Many thanks, as usual. I'll look into it and let you know if we hit a
bump backporting it.


- u



Processed: Re: Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 wishlist
Bug #1051251 [grub-common] /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: 
not found due to wrong shell location
Bug #1051328 [grub-common] grub-common: wrong-path-for-interpreter /usr/bin/sh 
!= /bin/sh [etc/grub.d/25_bli]
Severity set to 'wishlist' from 'critical'
Severity set to 'wishlist' from 'critical'

-- 
1051251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051251
1051328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

2023-09-16 Thread Julian Andres Klode
Control: severity -1 wishlist

On Sat, Sep 16, 2023 at 12:01:36PM +0200, Drew Parsons wrote:
> Control: severity -1 critical
> 
> 
> On 2023-09-16 11:43, Julian Andres Klode wrote:
> > Control: severity -1 wishlist
> > 
> > On Sat, Sep 16, 2023 at 10:36:39AM +0200, Drew Parsons wrote:
> > > Source: grub2
> > > Version: 2.12~rc1-7
> > > Followup-For: Bug #1051251
> > > Control: severity 1051251 critical
> > > 
> > > This is a critical bug.  apt fails on this bug early in its run, and
> > > therefore this one bug is preventing *every* *other* package from
> > > updating.
> > 
> > You have literally hacked around the dependencies of the packages by
> > inserting a fake package to pretend to have merged-usr installed to be
> > able to maintain a file system layout the project has decided is no
> > longer supported.
> 
> I have done literally nothing to change merged-usr status, apart from
> regularly upgrade packages as they come along.

This is not true. init-system-helpers depends on usrmerge | merged-usr, and
merged-usr only installs if your usr is merged, and usrmerge will
convert your system to the supported layout.

And that package is essential.

The only way you end up in that situation is by messing with the
package management system so that you generate a fake package using
equivs or similar that Provides: usrmerge or merged-usr, or using
the buildd workaround. 

Maybe you have followed the warnigns from dpkg that were added by
his hostile maintainer declaring merged-usr to be unsupported and
asking you to run a dangerous dpkg-fsys-usrunmess to mess up your
system.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en



Processed: Re: Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 critical
Bug #1051251 [grub-common] /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: 
not found due to wrong shell location
Bug #1051328 [grub-common] grub-common: wrong-path-for-interpreter /usr/bin/sh 
!= /bin/sh [etc/grub.d/25_bli]
Severity set to 'critical' from 'wishlist'
Severity set to 'critical' from 'wishlist'

-- 
1051251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051251
1051328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: smuxi: useless empty package

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 normal
Bug #1051006 {Done: Bastian Germann } [smuxi] smuxi: useless 
empty package
Severity set to 'normal' from 'grave'

-- 
1051006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1051006: smuxi: useless empty package

2023-09-16 Thread Bastian Germann

Control: severity -1 normal

The package is not migrating even though it is fixed.



Processed: Re: Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 wishlist
Bug #1051251 [grub-common] /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: 
not found due to wrong shell location
Bug #1051328 [grub-common] grub-common: wrong-path-for-interpreter /usr/bin/sh 
!= /bin/sh [etc/grub.d/25_bli]
Severity set to 'wishlist' from 'critical'
Severity set to 'wishlist' from 'critical'

-- 
1051251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051251
1051328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1051251: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

2023-09-16 Thread Julian Andres Klode
Control: severity -1 wishlist

On Sat, Sep 16, 2023 at 10:36:39AM +0200, Drew Parsons wrote:
> Source: grub2
> Version: 2.12~rc1-7
> Followup-For: Bug #1051251
> Control: severity 1051251 critical
> 
> This is a critical bug.  apt fails on this bug early in its run, and
> therefore this one bug is preventing *every* *other* package from updating.

You have literally hacked around the dependencies of the packages by
inserting a fake package to pretend to have merged-usr installed to be
able to maintain a file system layout the project has decided is no
longer supported.

FWIW, if you people keep being annoying I (with my apt head on) am
just going to deliberately make apt error out and refuse any operation
on unmerged systems.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en



Processed: Re: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found due to wrong shell location

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> severity 1051251 critical
Bug #1051251 [grub-common] /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: 
not found due to wrong shell location
Bug #1051328 [grub-common] grub-common: wrong-path-for-interpreter /usr/bin/sh 
!= /bin/sh [etc/grub.d/25_bli]
Severity set to 'critical' from 'wishlist'
Severity set to 'critical' from 'wishlist'

-- 
1051251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051251
1051328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1043124: The related openzfs issue

2023-09-16 Thread grin
6.5 under review:
https://github.com/openzfs/zfs/pull/15268

(Completely unrelated, but browsing the issues it popped up that encryption is 
very broken above 6.3,
and it has been somewhat broken on older kernels too; not one people lost their 
data due to upgrading
beyond 6.3, so beware. 
https://github.com/openzfs/zfs/issues/15275
https://github.com/openzfs/zfs/issues/15140)



Bug#1051374: breaks existing setups using /etc/default/mini-httpd

2023-09-16 Thread Johannes Schauer Marin Rodrigues
Hi,

Quoting Johannes Schauer Marin Rodrigues (2023-09-16 09:23:43)
> On Thu, 07 Sep 2023 00:58:34 +0200 Johannes Schauer Marin Rodrigues
>  wrote:
> > after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems 
> > that
> > this new version changed the init script for a systemd unit where the latter
> > ignores the contents of /etc/default/mini-httpd.
> > 
> > If that is intentional and not an oversight, there should at least be a
> > NEWS entry so that users upgrading to 1.30-4 learn about this breaking
> > change and are also told how to convert their existing configuration to
> > the new style.
> > 
> > If possible it would of course be nice if the systemd service would not 
> > break
> > user's setups and would continue to consume /etc/default/mini-httpd.
> 
> this issue has now made the mmdebstrap jenkins job fail for 10 days in a row:
> 
> https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/
> 
> Even if you do not have time to fix this soon, could you maybe advise on how
> you plan to fix this? Is the behaviour change introduced by the last upload
> supposed to stay and I should adjust my setup accordingly? Or will you restore
> compatibility with existing setups using /etc/default/mini-httpd so that I
> need to do nothing and just wait for an upload fixing this?

I asked in #debian-systemd and the fix could be as simple as setting the
following in the .service file:

EnvironmentFile=-/etc/default/mini-httpd

Can you confirm?

Thanks!

cheers, josch

signature.asc
Description: signature


Bug#1051592: Regression: Commit "netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID" breaks ruleset loading in linux-stable

2023-09-16 Thread Salvatore Bonaccorso
Hi ARturo,

On Sat, Sep 16, 2023 at 09:02:34AM +0200, Arturo Borrero Gonzalez wrote:
> On Sat, Sep 16, 2023, 08:37 Salvatore Bonaccorso  wrote:
> 
> > Hi
> >
> > Dropping some recipients for the Debian specific handling of this
> > issue. So AFAIU upstream will not consider this on src:linux side to
> > be further handled and needs to be addressed in nftables.
> >
> > Arturo: With the patches provided I prepared (as Timo) an update
> > targetting bookworm for the next point release (bug for release.d.o to
> > be submitted soon).
> >
> > Attached is the proposed debdiff, ans as well as MR on salsa.
> >
> >
> > https://salsa.debian.org/pkg-netfilter-team/pkg-nftables/-/merge_requests/11
> > (note not touching thte salsa-ci part was deliberate, but to make the
> > piuparts test one would need adjustment of the target release. But as
> > itwas not done for the +deb12u1 itself, I have not touched this)
> >
> > The same would be needed OTOH for bullseye as well.
> 
> 
> Hi Salvatore,
> 
> thanks for working on this. I just approved the salsa MR
> 
> Please go ahead an upload to the archive via NMU as required ASAP. I won't
> be near the keyboard today.
> 
> really appreciated,

Thank to you! I just filled the request for the release team, and
uploaded the version (following the procedure where one is almost sure
that the upload can be accepted as is).

I have as well pushed a signed tag to my repo in case you want to
fetch that as well.

Next we need to look as well to bullseye, feat that it will be more
complex there.

Regards,
Salvatore



Bug#1051374: breaks existing setups using /etc/default/mini-httpd

2023-09-16 Thread Johannes Schauer Marin Rodrigues
Hi Alexandru & Nicholas,

On Thu, 07 Sep 2023 00:58:34 +0200 Johannes Schauer Marin Rodrigues 
 wrote:
> after an upgrade to mini-httpd 1.30-4 my setup stopped working. It seems that
> this new version changed the init script for a systemd unit where the latter
> ignores the contents of /etc/default/mini-httpd.
> 
> If that is intentional and not an oversight, there should at least be a
> NEWS entry so that users upgrading to 1.30-4 learn about this breaking
> change and are also told how to convert their existing configuration to
> the new style.
> 
> If possible it would of course be nice if the systemd service would not break
> user's setups and would continue to consume /etc/default/mini-httpd.

this issue has now made the mmdebstrap jenkins job fail for 10 days in a row:

https://jenkins.debian.net/job/mmdebstrap-jenkins-worker/

Even if you do not have time to fix this soon, could you maybe advise on how
you plan to fix this? Is the behaviour change introduced by the last upload
supposed to stay and I should adjust my setup accordingly? Or will you restore
compatibility with existing setups using /etc/default/mini-httpd so that I need
to do nothing and just wait for an upload fixing this?

Thanks!

cheers, josch

signature.asc
Description: signature


Processed: bug 1051592 is forwarded to https://lore.kernel.org/stable/20230911213750.5b4b66320...@dd20004.kasserver.com/

2023-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 1051592 
> https://lore.kernel.org/stable/20230911213750.5b4b66320...@dd20004.kasserver.com/
Bug #1051592 {Done: Salvatore Bonaccorso } [src:nftables] 
linux: Regression - upgrade to 6.1.52-1 breaks nftables
Set Bug forwarded-to-address to 
'https://lore.kernel.org/stable/20230911213750.5b4b66320...@dd20004.kasserver.com/'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: Bug#1051980: FTBFS on i386: angle-test/bezier-test fail

2023-09-16 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 + patch
Bug #1051980 [src:lib2geom] FTBFS on i386: angle-test/bezier-test fail
Added tag(s) patch.

-- 
1051980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051980
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#1051980: FTBFS on i386: angle-test/bezier-test fail

2023-09-16 Thread Shengjing Zhu
Control: tag -1 + patch

Hi,

On Fri, Sep 15, 2023 at 4:27 PM Shengjing Zhu  wrote:
> The following tests FAILED:
>   2 - angle-test (Failed)
>   3 - bezier-test (Failed)

They are caused by gcc-13 which defaults to -fexcess-precision=standard for c++.

Please see the attached patch.

-- 
Shengjing Zhu


lib2geom_1.2.2-3.1.debdiff
Description: Binary data


Bug#1051592: Regression: Commit "netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID" breaks ruleset loading in linux-stable

2023-09-16 Thread Arturo Borrero Gonzalez
On Sat, Sep 16, 2023, 08:37 Salvatore Bonaccorso  wrote:

> Hi
>
> Dropping some recipients for the Debian specific handling of this
> issue. So AFAIU upstream will not consider this on src:linux side to
> be further handled and needs to be addressed in nftables.
>
> Arturo: With the patches provided I prepared (as Timo) an update
> targetting bookworm for the next point release (bug for release.d.o to
> be submitted soon).
>
> Attached is the proposed debdiff, ans as well as MR on salsa.
>
>
> https://salsa.debian.org/pkg-netfilter-team/pkg-nftables/-/merge_requests/11
> (note not touching thte salsa-ci part was deliberate, but to make the
> piuparts test one would need adjustment of the target release. But as
> itwas not done for the +deb12u1 itself, I have not touched this)
>
> The same would be needed OTOH for bullseye as well.


Hi Salvatore,

thanks for working on this. I just approved the salsa MR

Please go ahead an upload to the archive via NMU as required ASAP. I won't
be near the keyboard today.

really appreciated,

thanks, regards.


Bug#1051592: Regression: Commit "netfilter: nf_tables: disallow rule addition to bound chain via NFTA_RULE_CHAIN_ID" breaks ruleset loading in linux-stable

2023-09-16 Thread Salvatore Bonaccorso
Hi

Dropping some recipients for the Debian specific handling of this
issue. So AFAIU upstream will not consider this on src:linux side to
be further handled and needs to be addressed in nftables.

Arturo: With the patches provided I prepared (as Timo) an update
targetting bookworm for the next point release (bug for release.d.o to
be submitted soon).

Attached is the proposed debdiff, ans as well as MR on salsa.

https://salsa.debian.org/pkg-netfilter-team/pkg-nftables/-/merge_requests/11
(note not touching thte salsa-ci part was deliberate, but to make the
piuparts test one would need adjustment of the target release. But as
itwas not done for the +deb12u1 itself, I have not touched this)

The same would be needed OTOH for bullseye as well.

Regards,
Salvatore
diff -Nru nftables-1.0.6/debian/changelog nftables-1.0.6/debian/changelog
--- nftables-1.0.6/debian/changelog 2023-06-20 16:55:52.0 +0200
+++ nftables-1.0.6/debian/changelog 2023-09-16 07:47:15.0 +0200
@@ -1,3 +1,13 @@
+nftables (1.0.6-2+deb12u2) bookworm; urgency=medium
+
+  * [136245a] Fix incorrect bytecode generation hit with new kernel check that
+rejects adding rules to bound chains (Closes: #1051592)
+- rule: add helper function to expand chain rules intoi commands
+- rule: expand standalone chain that contains rules
+- src: expand table command before evaluation
+
+ -- Salvatore Bonaccorso   Sat, 16 Sep 2023 07:47:15 +0200
+
 nftables (1.0.6-2+deb12u1) bookworm; urgency=medium
 
   * [7edf72e] d/patches: add 0001-debian-bug-1038724.patch (Closes: #1038724)
diff -Nru 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
--- 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
1970-01-01 01:00:00.0 +0100
+++ 
nftables-1.0.6/debian/patches/rule-add-helper-function-to-expand-chain-rules-into-.patch
2023-09-16 07:47:15.0 +0200
@@ -0,0 +1,82 @@
+From 4e5b0a64227dde250f94bec45b3fb127d78b7fd2 Mon Sep 17 00:00:00 2001
+From: Pablo Neira Ayuso 
+Date: Mon, 6 Feb 2023 15:28:40 +0100
+Subject: [PATCH 1/3,nft] rule: add helper function to expand chain rules intoi
+ commands
+
+[ upstream commit 784597a4ed63b9decb10d74fdb49a1b021e22728 ]
+
+This patch adds a helper function to expand chain rules into commands.
+This comes in preparation for the follow up patch.
+
+Signed-off-by: Pablo Neira Ayuso 
+---
+ src/rule.c | 39 ++-
+ 1 file changed, 22 insertions(+), 17 deletions(-)
+
+diff --git a/src/rule.c b/src/rule.c
+index 1402210acd8d..43c6520517ce 100644
+--- a/src/rule.c
 b/src/rule.c
+@@ -1310,13 +1310,31 @@ void cmd_add_loc(struct cmd *cmd, uint16_t offset, 
const struct location *loc)
+   cmd->num_attrs++;
+ }
+ 
++static void nft_cmd_expand_chain(struct chain *chain, struct list_head 
*new_cmds)
++{
++  struct rule *rule;
++  struct handle h;
++  struct cmd *new;
++
++  list_for_each_entry(rule, >rules, list) {
++  memset(, 0, sizeof(h));
++  handle_merge(, >handle);
++  if (chain->flags & CHAIN_F_BINDING) {
++  rule->handle.chain_id = chain->handle.chain_id;
++  rule->handle.chain.location = chain->location;
++  }
++  new = cmd_alloc(CMD_ADD, CMD_OBJ_RULE, ,
++  >location, rule_get(rule));
++  list_add_tail(>list, new_cmds);
++  }
++}
++
+ void nft_cmd_expand(struct cmd *cmd)
+ {
+   struct list_head new_cmds;
+   struct flowtable *ft;
+   struct table *table;
+   struct chain *chain;
+-  struct rule *rule;
+   struct set *set;
+   struct obj *obj;
+   struct cmd *new;
+@@ -1362,22 +1380,9 @@ void nft_cmd_expand(struct cmd *cmd)
+   >location, flowtable_get(ft));
+   list_add_tail(>list, _cmds);
+   }
+-  list_for_each_entry(chain, >chains, list) {
+-  list_for_each_entry(rule, >rules, list) {
+-  memset(, 0, sizeof(h));
+-  handle_merge(, >handle);
+-  if (chain->flags & CHAIN_F_BINDING) {
+-  rule->handle.chain_id =
+-  chain->handle.chain_id;
+-  rule->handle.chain.location =
+-  chain->location;
+-  }
+-  new = cmd_alloc(CMD_ADD, CMD_OBJ_RULE, ,
+-  >location,
+-  rule_get(rule));
+-  list_add_tail(>list, _cmds);
+-  }
+-  }
++  

Bug#1051592: reassign 1051592 to src:nftables, found 1051592 in 1.0.6-2+deb12u1, found 1051592 in 0.9.8-3.1 ...

2023-09-16 Thread Salvatore Bonaccorso
reassign 1051592 src:nftables 1.0.6-2
found 1051592 1.0.6-2+deb12u1
found 1051592 0.9.8-3.1
found 1051592 0.9.8-3.1+deb11u1
close 1051592 1.0.7-1
affects 1051592 + src:linux
thanks



Processed: reassign 1051592 to src:nftables, found 1051592 in 1.0.6-2+deb12u1, found 1051592 in 0.9.8-3.1 ...

2023-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 1051592 src:nftables 1.0.6-2
Bug #1051592 [linux] linux: Regression - upgrade to 6.1.52-1 breaks nftables
Bug reassigned from package 'linux' to 'src:nftables'.
No longer marked as found in versions 5.10.191-1 and 6.1.52-1.
Ignoring request to alter fixed versions of bug #1051592 to the same values 
previously set
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks 
nftables
Marked as found in versions nftables/1.0.6-2.
> found 1051592 1.0.6-2+deb12u1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks 
nftables
Marked as found in versions nftables/1.0.6-2+deb12u1.
> found 1051592 0.9.8-3.1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks 
nftables
Marked as found in versions nftables/0.9.8-3.1.
> found 1051592 0.9.8-3.1+deb11u1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks 
nftables
Marked as found in versions nftables/0.9.8-3.1+deb11u1.
> close 1051592 1.0.7-1
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks 
nftables
Marked as fixed in versions nftables/1.0.7-1.
Bug #1051592 [src:nftables] linux: Regression - upgrade to 6.1.52-1 breaks 
nftables
Marked Bug as done
> affects 1051592 + src:linux
Bug #1051592 {Done: Salvatore Bonaccorso } [src:nftables] 
linux: Regression - upgrade to 6.1.52-1 breaks nftables
Added indication that 1051592 affects src:linux
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: Re: ldap-account-manager: Multiple embeded and minified javascript library

2023-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 1042528 - ftbfs
Bug #1042528 [src:ldap-account-manager] ldap-account-manager: Multiple embeded 
and minified javascript library
Removed tag(s) ftbfs.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1042528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems