Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-13 Thread Thorsten Glaser
On Tue, 13 Jun 2023, Bill Allombert wrote:

>I agree, chroots are important to consider, and the system should not
>make assumptions how and why there are used.

Thanks!

>Conversely, sometimes I need to use chroots to test init scripts.
>start-stop-daemon should not refuse to run in a chroot if policy-rc.d
>allows it.

TTBOMK this works-ish. It certainly starts and stops things, but if
you have the same thing running outside of the chroot, interference
may happen. You’ll probably want a separate pid namespace (I think)
at least, and make sure that, when leaving the chroot, everything
started in it is in fact terminated; sometimes, things like to keep
hanging around. This is easier to manage with VMs or (probably; I
don’t like to use them myself) container-ish thingies.

In my schroot setup I used to start a vncserver in a persistent
chroot back when my main system was x32 and vncserver didn’t like
that nor was coïnstallable (hence the i386 chroot).

My “enter a Debian chroot” script, to use e.g. with a Grml live ISO
to fix the bootloader (or to work under qemu-user with an RPi µSD
image before moving it into the embedded machine), certainly tries
hard to create a policy-rc.d to disable dæmon starting should the
user need to install packages, so it generally will work.
https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=shellsnippets/shellsnippets.git;a=blob;f=posix/sysadmin/debchroot.sh;hb=HEAD
in case someone’s interested, it’s more complete than grml-chroot.

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


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




Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-13 Thread Bill Allombert
On Tue, Jun 13, 2023 at 05:43:17PM +0200, Thorsten Glaser wrote:
> On Mon, 5 Jun 2023, Simon McVittie wrote:
> 
> >No init system at all, (C.), can only happen when starting with a
> >minbase debootstrap or equivalent (because a default debootstrap
> >includes the init metapackage due to its Priority: required). In
> >this scenario it *usually* doesn't really matter whether we
> >install systemd or systemd-tmpfiles-standalone. systemd is somewhat
> 
> This is not quite true; there is one really important use case:
> chroots. I have multiple chroots (sid, stretch, buster) on one
> of my bullseye systems which I use with schroot, but that could
> just as well be any other chroot, to run individual software in
> it. They are, as is proper, configured to not run any services
> (via policy-rc.d).

I agree, chroots are important to consider, and the system should not make
assumptions how and why there are used.

Conversely, sometimes I need to use chroots to test init scripts.
start-stop-daemon should not refuse to run in a chroot if policy-rc.d allows
it.

Cheers,
Bill.



Bug#1028137: [Pkg-electronics-devel] Bug#1028137: nextpnr: Support for more FPGA architectures (esp. ECP5)

2023-06-13 Thread Daniel Gröber
Hi Jonathan,

On Sat, Jan 07, 2023 at 06:01:11PM +0100, Jonathan Neuschäfer wrote:
> to increase the usefulness of nextpnr in Debian, it would be nice to
> package build nextpnr for more FPGA architectures, in addition to iCE40.
> ECP5 comes to mind, because it seems to be fairly usable by now.

I don't have an ECP5 devboard but what I have rediscovered recently is a
Tang Nano 9k (Gowin GW1N) devboard. Hence I've been working on enabling
gowin support. I've got project apicula and nextpnr packaged already but
I'm waiting on a sponsor.

In the meantime I'm having a look at prjtrellis too, but since I don't have
any testing hardware I was wondering if you'd be able to do testing once I
finish packaging?

--Daniel



Bug#1037510: texlive-lang-japanese: dangling symlinks due to missing dependencies

2023-06-13 Thread Vincent Lefevre
Package: texlive-lang-japanese
Version: 2022.20230122-1
Severity: serious

There is a dangling symlink on my machine:
/usr/share/texlive/texmf-dist/fonts/truetype/public/ipaex/ipaexm.ttf -> 
../../../../../../fonts/opentype/ipaexfont-mincho/ipaexm.ttf

This seems to be due to a missing dependency on fonts-ipaexfont-mincho.

Since texlive-lang-japanese provides the following symlinks:

lrwxrwxrwx 1 root root 60 2023-01-24 23:31:57 ipaexg.ttf -> 
../../../../../../fonts/opentype/ipaexfont-gothic/ipaexg.ttf
lrwxrwxrwx 1 root root 60 2023-01-24 23:31:57 ipaexm.ttf -> 
../../../../../../fonts/opentype/ipaexfont-mincho/ipaexm.ttf
lrwxrwxrwx 1 root root 56 2023-01-24 23:31:57 ipag.ttf -> 
../../../../../../fonts/opentype/ipafont-gothic/ipag.ttf
lrwxrwxrwx 1 root root 57 2023-01-24 23:31:57 ipagp.ttf -> 
../../../../../../fonts/opentype/ipafont-gothic/ipagp.ttf
lrwxrwxrwx 1 root root 56 2023-01-24 23:31:57 ipam.ttf -> 
../../../../../../fonts/opentype/ipafont-mincho/ipam.ttf
lrwxrwxrwx 1 root root 57 2023-01-24 23:31:57 ipamp.ttf -> 
../../../../../../fonts/opentype/ipafont-mincho/ipamp.ttf

it should also depend on fonts-ipaexfont-gothic, fonts-ipafont-gothic
and fonts-ipafont-mincho.

-- 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 3539 2023-06-13 11:22:32 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 23:25:33 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2023-04-09 11:54:45 
/usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2023-04-09 11:54:45 /usr/share/texmf/web2c/updmap.cfg 
-> /var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5130 2023-05-22 11:27:35 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2015-09-03 02:24:29 mktex.cnf
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-lang-japanese depends on:
ii  ruby  1:3.1
ii  tex-common6.18
ii  texlive-base  2022.20230122-3
ii  texlive-binaries  2022.20220321.62855-5.1
ii  texlive-lang-cjk  2022.20230122-1

Versions 

Bug#1037509: RFS: cglm/0.9.0-1 -- Optimized OpenGL Mathematics library for C

2023-06-13 Thread Leon Marz

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "cglm":

 * Package name : cglm
   Version  : 0.9.0-1
   Upstream contact : Recep Aslantas 
 * URL  : https://github.com/recp/cglm
 * License  : Expat
 * Vcs  : https://salsa.debian.org/debian/cglm
   Section  : libs

The source builds the following binary packages:

  libcglm-doc - Documentation for the cglm library
  libcglm-dev - Development files for the cglm library
  libcglm0 - Optimized OpenGL Mathematics library for C

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


  https://mentors.debian.net/package/cglm/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/c/cglm/cglm_0.9.0-1.dsc


Changes since the last upload:

 cglm (0.9.0-1) unstable; urgency=medium
 .
   * New upstream release
   * d/copyright: Update copyright year
- Leon


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1037508: texlive-lang-arabic: dangling symlinks amiri/Amiri-BoldSlanted.ttf and amiri/Amiri-Slanted.ttf

2023-06-13 Thread Vincent Lefevre
Package: texlive-lang-arabic
Version: 2022.20230122-1
Severity: normal

There are 2 dangling symlinks:

/usr/share/texlive/texmf-dist/fonts/truetype/public/amiri/Amiri-BoldSlanted.ttf 
-> ../../../../../../fonts/opentype/fonts-hosny-amiri/Amiri-BoldSlanted.ttf
/usr/share/texlive/texmf-dist/fonts/truetype/public/amiri/Amiri-Slanted.ttf -> 
../../../../../../fonts/opentype/fonts-hosny-amiri/Amiri-Slanted.ttf

Moreover, I'm wondering whether Amiri-BoldItalic.ttf and
Amiri-Italic.ttf should be transformed to symlinks to the
files provided by fonts-hosny-amiri.

FYI:

cventin:~> ll /usr/share/fonts/opentype/fonts-hosny-amiri
total 2776
-rw-r--r-- 1 root root 171448 2022-12-03 20:37:44 AmiriQuran.ttf
-rw-r--r-- 1 root root 205080 2022-12-03 20:37:44 AmiriQuranColored.ttf
-rw-r--r-- 1 root root 601600 2022-12-03 20:37:44 Amiri-Bold.ttf
-rw-r--r-- 1 root root 599120 2022-12-03 20:37:44 Amiri-BoldItalic.ttf
-rw-r--r-- 1 root root 625472 2022-12-03 20:37:44 Amiri-Italic.ttf
-rw-r--r-- 1 root root 627240 2022-12-03 20:37:44 Amiri-Regular.ttf

cventin:~> ll /usr/share/texlive/texmf-dist/fonts/truetype/public/amiri
total 888
lrwxrwxrwx 1 root root 65 2023-01-24 23:31:57 Amiri-Bold.ttf -> 
../../../../../../fonts/opentype/fonts-hosny-amiri/Amiri-Bold.ttf
-rw-r--r-- 1 root root 426584 2022-12-04 22:06:57 Amiri-BoldItalic.ttf
lrwxrwxrwx 1 root root 72 2023-01-24 23:31:57 Amiri-BoldSlanted.ttf -> 
../../../../../../fonts/opentype/fonts-hosny-amiri/Amiri-BoldSlanted.ttf
-rw-r--r-- 1 root root 451684 2022-12-04 22:06:57 Amiri-Italic.ttf
lrwxrwxrwx 1 root root 68 2023-01-24 23:31:57 Amiri-Regular.ttf -> 
../../../../../../fonts/opentype/fonts-hosny-amiri/Amiri-Regular.ttf
lrwxrwxrwx 1 root root 68 2023-01-24 23:31:57 Amiri-Slanted.ttf -> 
../../../../../../fonts/opentype/fonts-hosny-amiri/Amiri-Slanted.ttf
lrwxrwxrwx 1 root root 72 2023-01-24 23:31:57 Quran.ttf -> 
../../../../../../fonts/opentype/fonts-hosny-amiri/AmiriQuranColored.ttf
lrwxrwxrwx 1 root root 65 2023-01-24 23:31:57 QuranColored.ttf -> 
../../../../../../fonts/opentype/fonts-hosny-amiri/AmiriQuran.ttf

Note: I do not use these fonts. I just noticed the dangling symlinks.


-- 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 3539 2023-06-13 11:22:32 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 2022-10-12 23:25:33 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 2023-04-09 11:54:45 
/usr/share/texlive/texmf-dist/ls-R -> /var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 2023-04-09 11:54:45 
/usr/share/texmf/web2c/fmtutil.cnf -> /var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 2023-04-09 11:54:45 /usr/share/texmf/web2c/updmap.cfg 
-> /var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 5130 2023-05-22 11:27:35 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 2015-09-03 02:24:29 mktex.cnf
-rw-r--r-- 1 root root 475 2022-10-13 13:39:43 

Bug#922815: insserv: FATAL: service mountkernfs has to be enabled to use service keyboard-setup.sh

2023-06-13 Thread Thorsten Glaser
On Sun, 28 May 2023, Thomas Deutschmann wrote:

> Note: The system was recently upgraded from Debian 8 (without systemd) to
> Debian 9 (where I switched to systemd) to Debian 12.

You did upgrade to Debian 10, then Debian 11, in the middle, right?

Otherwise your system is now completely unsupportable and you will
have to clean up the resulting mess yourself. Skipping releases in
an upgrade was *never* supported, and it’s documented in basically
every place…

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


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




Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-13 Thread Thorsten Glaser
On Mon, 5 Jun 2023, Simon McVittie wrote:

>No init system at all, (C.), can only happen when starting with a
>minbase debootstrap or equivalent (because a default debootstrap
>includes the init metapackage due to its Priority: required). In
>this scenario it *usually* doesn't really matter whether we
>install systemd or systemd-tmpfiles-standalone. systemd is somewhat

This is not quite true; there is one really important use case:
chroots. I have multiple chroots (sid, stretch, buster) on one
of my bullseye systems which I use with schroot, but that could
just as well be any other chroot, to run individual software in
it. They are, as is proper, configured to not run any services
(via policy-rc.d).

>I also think that Policy shouldn't be recommending this interface without

Therefore I belive that Policy ought to *not* recommend any
solution that depends on starting dæmons or init scripts to
create temporary files/directories that are necessary for
programs to work.

>- if we get a useful non-Linux port (admittedly this looks increasingly
>  unlikely) which cannot compile src:systemd, then their reimplementation

hurd-amd64 is just shy of being uploaded; work on Debian GNU/Hurd
is active and things seem to look good on that front. (The pools
for hurd-amd64 have just been created a week or two ago.)

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


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




Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files

2023-06-13 Thread Russ Allbery
Sean Whitton  writes:

> I still find myself feeling queasy about adding this must-with-caveat.
> It feels like with the caveat you're trying to get something between
> "must" and "should", but then rather than build down from "must", why
> not build up from "should"?  I would like to propose:

> Maintainers should strongly prefer using other overriding
> mechanisms, instead of diversions, whenever those other mechanisms
> are sufficient to accomplish the same goal.  In other words,
> diversions in packages should be considered a last resort.

This sounds good to me.  The argument for building up from should instead
of down from must seems compelling.

-- 
Russ Allbery (r...@debian.org)  



Bug#1037507: RM: gnome-games-app -- RoM; unmaintained, renamed to highscore

2023-06-13 Thread Jeremy Bícha
Package: ftp.debian.org
X-Debbugs-Cc: gnome-games-...@packages.debian.org
Affects: src:gnome-games-app

gnome-games-app will no longer be runnable or installable as we
proceed with the grilo part of the ongoing mega libsoup2.4 -> libsoup3
transition. See https://bugs.debian.org/1037433

gnome-games-app was archived upstream and renamed to highscore.
Therefore, once it is ported to libsoup3, it can re-enter Debian with
a new source package name, highscore.

However, the highscore maintainers never did a release after the name
change and the project is currently unmaintained.

Alternatives

Neither gnome-games nor highscore are currently available on Flathub
but gnome-games used to be there and it could return if someone would
step up to maintain it.

There isn't yet a Snap version of the app either.

Both lutris and retroarch are packaged in Debian and are similar apps
to gnome-games-app.

On behalf of the Debian GNOME Team,
Jeremy Bicha



Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files

2023-06-13 Thread Sean Whitton
Hello,

On Tue 06 Jun 2023 at 12:16PM +01, Luca Boccassi wrote:

> My understanding is that "should" is effectively optional, ie: it is
> not enough to make a package rc-buggy, and while they are generally
> followed, there is no actual hard requirement to do so. That is not
> enough for me and for this use case. So again my goal here is to make
> an hypothetical future dpkg-divert or alternative of a unit file
> (wherever it is shipped from) instantly and unambiguously rc-buggy,
> with no leeway (again there are no longer any such cases in the
> archive as of bookworm, so nothing is affected). If you can suggest an
> alternative appropriate wording that can achieve the same effect, that
> would be fine to me - I don't mind how it's written, as long as it
> meets this requirement.

We have more than two bug severities in the BTS and more than two levels
of normative language in Policy.  It's simply untrue that all but one of
each of those is optional.  Debian's normative landscape is more complex
than that.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#1037506: ITP: prjtrellis -- Tools to generate Lattice ECP5 bitstreams

2023-06-13 Thread Daniel Gröber
Package: wnpp
Severity: wishlist
Owner: Daniel Gröber 
X-Debbugs-Cc: debian-de...@lists.debian.org, d...@darkboxed.org

* Package name: prjtrellis
  Version : 1.4
  Upstream Authors: David Shah 
William D. Jones 
Miodrag Milanovi 
myrtle 
* URL : https://github.com/YosysHQ/prjtrellis
* License : ISC/MIT
  Programming Lang: C++/Python
  Description : Tools to generate Lattice ECP5 bitstreams

Project trellis supplies documentation and tools for generating the
bitstream format used by Lattice ECP5 family of FPGAs.

It has been requested[1] that nextpnr enable support for this FPGA
family so we need to package prjtrellis to do this.

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028137

I need a sponsor as always. ~Victims~, eer, volunteers welcome :)

--Daniel


Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files

2023-06-13 Thread Sean Whitton
Hello,

On Tue 06 Jun 2023 at 07:56PM -07, Russ Allbery wrote:

> Sean Whitton  writes:
>
>> I think what's a bit peculiar here is using "must" for a case where
>> there might be package-specific exceptions.  In other cases, Policy uses
>> "should" for these cases.  Typically "must" rules are simple and
>> completely determinate.
>
> I prefer that too, but in this case, it feels like must is appropriate
> for at least systemd configuration files.

I've spent some time thinking about this, and I now agree that we should
add a "must" for systemd unit files, and the other classes of systemd
configuration mentioned in the patch.

> And also, just intuitively, I feel like must is correct when people
> are using diversions rather than a native mechanism.  Diversions add
> weird edge cases and we really shouldn't be using them lightly.
>
> The wording I proposed and that Luca has now adopted therefore uses
> must with a caveat.  Does that sound okay to you?

I still find myself feeling queasy about adding this must-with-caveat.
It feels like with the caveat you're trying to get something between
"must" and "should", but then rather than build down from "must", why
not build up from "should"?  I would like to propose:

Maintainers should strongly prefer using other overriding
mechanisms, instead of diversions, whenever those other mechanisms
are sufficient to accomplish the same goal.  In other words,
diversions in packages should be considered a last resort.

I think that this accomplishes everything, in terms of guidance for our
maintainers, that the must-with-caveat wording does.  But it avoids
saying that using diversions over a native mechanism in and of itself
renders a package RC-buggy, which doesn't seem right to me.

My own experience with diversions is limited, and so I accept that I may
well be naively underestimating the badness of the edge cases.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#1037505: RFS: asciidoc/10.2.0-2 -- Highly configurable text format for writing documentation

2023-06-13 Thread Leon Marz

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "asciidoc":

 * Package name : asciidoc
   Version  : 10.2.0-2
   Upstream contact : AsciiDoc Contributors 
https://groups.google.com/group/asciidoc

 * URL  : https://asciidoc.org
 * License  : GPL-2+ and Expat, GFDL-NIV-1.3, GPL-2+
 * Vcs  : https://salsa.debian.org/debian/asciidoc
   Section  : text

The source builds the following binary packages:

  asciidoc - Highly configurable text format for writing documentation
  asciidoc-common - Basic data and configuration files for asciidoc
  asciidoc-base - Minimal version of asciidoc not suitable for pdf
  asciidoc-dblatex - Asciidoc package including dblatex dependencies
  asciidoc-fop - Asciidoc package including fop dependencies
  asciidoc-tests - Test framework for asciidoc

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


  https://mentors.debian.net/package/asciidoc/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/a/asciidoc/asciidoc_10.2.0-2.dsc


Changes since the last upload:

 asciidoc (10.2.0-2) unstable; urgency=medium
 .
   [Janitor]
   * Remove maintscript files
   * Update d/upstream/metadata
   * Remove version constraints
 .
   [Leon Marz]
   * d/patches: set iconsdir in recognize-etc-asciidoc.patch (Closes: 
#1036030)

   * d/source/lintian-overrides: Add overrides for some test files
   * d/control: Bump Standards-Version to 4.6.2
   * d/watch: Use the example from uscan(1)
   * d/copyright: Update copyright year

- Leon


OpenPGP_signature
Description: OpenPGP digital signature


Bug#992258: packages.debian.org still not showing bullseye-security packages

2023-06-13 Thread Cyril Brulebois
(Adding back submitter, and everyone who mailed that bug report.)

Hi,

Colomban Wendling  (2022-10-25):
> I have unfortunately no insight on how this could be fixed, but it's
> rather inconvenient as packages.debian.org is thus effectively not a
> trustable source for Bullseye.

Let's see if those help:
  
https://salsa.debian.org/webmaster-team/packages/-/compare/f673a47d01...4111b73ede

As usual, I'm not forcing a refresh right away, and I'll let the next
mirror pulse trigger reindexing. We should have a better idea in 6-12
hours.


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


signature.asc
Description: PGP signature


Bug#1037504: ITP: golang-sourcehut-sircmpwn-go-bare -- Implementation of BARE message encoding for Go

2023-06-13 Thread Taavi Väänänen

X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Taavi Väänänen 

* Package name: golang-sourcehut-sircmpwn-go-bare
  Version : 0.0~git20210406.ab86bc2-1
  Upstream Author : Drew DeVault 
* URL : https://sr.ht/~sircmpwn/go-bare
* License : Apache-2.0
  Programming Lang: Go
  Description : Implementation of BARE message encoding for Go

go-bare provides an implementation of the BARE message format for Go.

This is a dependency of the soju IRC bouncer that I'm packaging.


OpenPGP_0xEF242F709F912FBE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1037503: ITP: golang-gopkg-irc.v4 -- Simple Go IRC library

2023-06-13 Thread Taavi Väänänen

X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Taavi Väänänen 

* Package name: golang-gopkg-irc.v4
  Version : 4.0.0-1
  Upstream Author : Kaleb Elwert
* URL : https://github.com/go-irc/irc
* License : Expat
  Programming Lang: Go
  Description : Simple Go IRC library

go-irc is a simple GO IRC library meant to be a building block for other 
projects.


This is a dependency of the soju IRC bouncer that I'm packaging.


OpenPGP_0xEF242F709F912FBE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1037502: missing ipv4/ipv6 commands

2023-06-13 Thread Daniel Baumann
Package: force-ip-protocol
Version: 0.2.0-2
Severity: wishlist

Hi Thorsten,

thank you very much for force-ip-protocol, it's very handy.

Unfortunately the debian package does not install /usr/bin/ipv4 or
/usr/bin/ipv6. Assuming you did that deliberately (because they would be
quite generic; I woudn't mind though :), maybe naming them
force-ipv4/force-ipv6 would be less generic?

Anyhow - having the helpers in the path and in the binary package would
be super useful.

Regards,
Daniel



Bug#1035733: debian -policy: packages must not use dpkg-divert to override default systemd configuraton files

2023-06-13 Thread Sean Whitton
Hello,

> diff --git a/policy/ch-binary.rst b/policy/ch-binary.rst
> index e517f26..4ceec3f 100644
> --- a/policy/ch-binary.rst
> +++ b/policy/ch-binary.rst
> +
> +Alternatives must never be used for ``systemd`` configuration files.

"Must not" rather than "must never" is our standard phrasing,
and "must not" is not any normatively weaker than "must never".

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#1037498: ITP: weakforced -- Daemon for detecting brute force attacks

2023-06-13 Thread Pierre-Elliott Bécue


De : Jonas Smedegaard 
À : 1037...@bugs.debian.org
Date : 13 juin 2023 16:33:15
Objet : Bug#1037498: ITP: weakforced -- Daemon for detecting brute force attacks

> Quoting Pierre-Elliott Bécue (2023-06-13 15:14:15)
>> The goal of 'wforce' is to detect brute forcing of passwords across many
>> servers, services and instances. In order to support the real world, brute
>> force detection policy can be tailored to deal with "bulk, but legitimate"
>> users of your service, as well as botnet-wide slowscans of passwords.
>> The aim is to support the largest of installations, providing services to
>> hundreds of millions of users.
>> 
>> weakforced doesn't have any real alternative for now in Debian as far as I 
>> can
>> see.
> 
> A somewhat related tool already in Debian seems to be crowdsec.
> 
> Just mentioning in case you or others following along might find it
> helpful - sounds like weakforced would be useful in Debian regardless.
> 
> 
> - Jonas
> 
> -- 
> * Jonas Smedegaard - idealist & Internet-arkitekt
> * Tlf.: +45 40843136  Website: http://dr.jones.dk/
> * Sponsorship: https://ko-fi.com/drjones
> 
> [x] quote me freely  [ ] ask before reusing  [ ] keep private
Thanks for the pointer ! I clearly missed it !

Cheers,

-- 
Pierre-Elliott Bécue



Bug#1037501: surfraw: broken example (/usr/lib/surfraw/rhyme)

2023-06-13 Thread Jakub Wilk

Package: surfraw
Version: 2.3.0-2
Severity: minor

The surfraw(1) manual page contains the following example:

$ /usr/lib/surfraw/rhyme -method=perfect Julian

But /usr/lib/surfraw/rhyme does not exist.

--
Jakub Wilk



Bug#918075: Some patches for dar

2023-06-13 Thread John Goerzen
Hi Laszlo,

I have uploaded dar 2.7.9 with the change to Maintainer.  libthreadar is
also in NEW, and once it is accepted, I will be able to enable curl to
provide FTP/SFTP support and close the bug entirely.

Thank you for your work maintaining dar all this time!

- John

On Mon, Jun 05 2023, László Böszörményi (GCS) wrote:

> Hi John,
>
> On Mon, Jun 5, 2023 at 10:12 PM John Goerzen  wrote:
>> If you are open to me taking over dar at this time, I would go ahead and
>> upload 2.7.9 (with my updates above) with the maintainer changed to me.
>  I just ask for one thing. Please wait until Bookworm is released -
> probably this or next week. Then go ahead and take over dar.
>
> Regards,
> Laszlo/GCS



Bug#1037498: ITP: weakforced -- Daemon for detecting brute force attacks

2023-06-13 Thread Jonas Smedegaard
Quoting Pierre-Elliott Bécue (2023-06-13 15:14:15)
> The goal of 'wforce' is to detect brute forcing of passwords across many
> servers, services and instances. In order to support the real world, brute
> force detection policy can be tailored to deal with "bulk, but legitimate"
> users of your service, as well as botnet-wide slowscans of passwords.
> The aim is to support the largest of installations, providing services to
> hundreds of millions of users.
> 
> weakforced doesn't have any real alternative for now in Debian as far as I can
> see.

A somewhat related tool already in Debian seems to be crowdsec.

Just mentioning in case you or others following along might find it
helpful - sounds like weakforced would be useful in Debian regardless.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature


Bug#1037264: cksum crashes intermittently with "Illegal instruction" on some Xen DomU

2023-06-13 Thread Axel Beckert
Hi,

Pádraig Brady wrote:
> At this stage it would be good to get the output from `cpuid -1`

Ok, I've attached the output of "cpuid -1" from both affected DomUs
(the outputs slightly differ) as well as of the unaffected hosting
server (same CPU) for comparison.

cpuid-domu1.txt and cpuid-domu2.txt is the output on the two affected
DomUs (VMs) and cpuid-dom0.txt is the output on the (Debian 11) Xen
hosting server.

One more note: The Xen version running on the hosting server is
4.14.5+94-ge49571868d-1 (the one from Debian 11), in case that's of
interest.

HTH!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


cpuid-domu1.txt.gz
Description: application/gzip


cpuid-domu2.txt.gz
Description: application/gzip


cpuid-dom0.txt.gz
Description: application/gzip


signature.asc
Description: PGP signature


Bug#1037500: ITP: golang-github-sherclockholmes-webpush-go -- Web Push API library with encryption and VAPID support

2023-06-13 Thread Taavi Väänänen

X-Debbugs-CC: debian-de...@lists.debian.org, debian...@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Taavi Väänänen 

* Package name: golang-github-sherclockholmes-webpush-go
  Version : 1.2.0-1
  Upstream Author : Ethan Holmes
* URL : https://github.com/SherClockHolmes/webpush-go
* License : Expat
  Programming Lang: Go
  Description : Web Push API library with encryption and VAPID support

webpush-go provides a Web Push API library with support for encryption 
and VAPID.


This is a dependency of the soju IRC bouncer that I'm packaging.


OpenPGP_0xEF242F709F912FBE.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1037499: RM: django-testproject -- ROM; obsolete, unmaintained

2023-06-13 Thread Antonio Terceiro
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: django-testproj...@packages.debian.org
Control: affects -1 + src:django-testproject

Please remove src:django-testproject. Is not maintained anymore, and
is not used by anything in the archive.


signature.asc
Description: PGP signature


Bug#1036061: frr: CVE-2023-31489

2023-06-13 Thread David Lamparter
Fixed upstream in 9f1ba873637fd6ce4a2d366eafcf41402775852b for 8.4,
pending pick-up together with fix for #1036062 / CVE-2023-31490.

(Would bump to upstream 8.4.4 if that's acceptable?)


-equi



Bug#1029210: smartmontools.service fails since bookworm

2023-06-13 Thread Christian Franke

Fixed upstream: https://www.smartmontools.org/changeset/5475



Bug#1037496: mdadm: Please restore support for use without systemd as PID 1

2023-06-13 Thread Daniel Baumann
retitle 1037496 show note about missing boot integration for non-systemd
thanks

Hi Mark,

On 6/13/23 14:28, Mark Hindley wrote:
> It would be a great help to users of non-systemd inits if you could restore 
> them.

thanks you for your report.

Personally I'm using systemd, but in general I fully agree that as long
as it's no "burden" to keep the sysvinit scripts around, I'd keep them.

For mdadm specifically, using sysvinit scripts has been the source of a
bunch of bugs as some things are not properly supportable when it comes
to events/race-condition handling when detecting raid devices in early boot.

Most other distributions as well as upstream don't support sysvinit
anymore in mdadm. I can see at least three disadvantages for keeping
sysvinit scripts in mdadm around:

  * I would need to support them in Debian for a type of system I
don't use anywhere anymore since several Debian releases.
Personally, I'd rather spend time on, to me, more appealing things.

  * Keeping sysvinit support for mdadm in Debian de-facto makes me
upstream for these scripts, which doesn't seem right given that
I don't use it myself.

  * Keeping sysvinit support would "falsly advertise" that it's actually
maintained and cared for, which isn't the case and I'd expect that
a lot of bugs don't get spottet in time for a next Debian release.

As of policy 4.5.0, including sysvinit scripts in a package if systemd
units are present, is not longer recommended but optional, so that (at
least after the bookworm release last weekend) I'd expect that a lot of
other packages are going to drop the sysvinit scripts too.

A solution could be for those that like to keep using sysvinit, to
submit the scripts for inclusion in the orphan-sysvinit-scripts package
and maintain it there.

> Installing recent mdadm on a non-systemd system can render the system
> unbootable.

Good point, I'll think about emitting an appropriate message so that
it's not easily overseen in such situtations.

Regards,
Daniel



Bug#1032712: MR on Salsa which fixes these bugs

2023-06-13 Thread Diederik de Haas
Control: tag -1 patch

I've created a MR which fixes these bugs here:
https://salsa.debian.org/xorg-team/lib/mesa/-/merge_requests/27

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


Bug#519558: Please retry with a newer dar

2023-06-13 Thread John Goerzen
tags 519558 moreinfo
thanks

Hello,

This bug is more than 10 years old.  Please retry with a newer Dar;
ideally 2.7.9 in sid.  Failing that, at least the version in bookworm.
It would be very helpful to have a reproducible test case if indeed the
problem can be reproduced.

Thanks,

John



Bug#1036062: frr: CVE-2023-31490

2023-06-13 Thread David Lamparter
Argh, wrong bug, previous mail was for 1036061.

On Tue, Jun 13, 2023 at 03:17:52PM +0200, David Lamparter wrote:
> Fixed upstream in 9f1ba873637fd6ce4a2d366eafcf41402775852b on stable/8.4
> branch.

CVE-2023-31489 / 1036062 was fixed upstream on master but not backported
to 8.4 yet; now pending upstream CI & review in
https://github.com/FRRouting/frr/pull/13782

8.4.4 release is expected upstream shortly, including fixes for both
this and CVE-2023-31490.

-equi



Bug#1036062: frr: CVE-2023-31490

2023-06-13 Thread David Lamparter
Fixed upstream in 9f1ba873637fd6ce4a2d366eafcf41402775852b on stable/8.4
branch.

Debian fix incoming with bump to 8.4.4 if that's OK?  That wouldn't be a
targeted security fix, but FRR minor versions are bugfix-only.


-equi



Bug#1037498: ITP: weakforced -- Daemon for detecting brute force attacks

2023-06-13 Thread Pierre-Elliott Bécue
Package: wnpp
Severity: wishlist
Owner: Pierre-Elliott Bécue 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: weakforced
  Version : 2.8.0
  Upstream Author : Neil Cook 
* URL : https://github.com/PowerDNS/weakforced
* License : GPL-3
  Programming Lang: C++, Python
  Description : Daemon for detecting brute force attacks

The goal of 'wforce' is to detect brute forcing of passwords across many
servers, services and instances. In order to support the real world, brute
force detection policy can be tailored to deal with "bulk, but legitimate"
users of your service, as well as botnet-wide slowscans of passwords.
The aim is to support the largest of installations, providing services to
hundreds of millions of users.

weakforced doesn't have any real alternative for now in Debian as far as I can
see.

For now these packages will be in collab-maint, but I'll see if they
could go somewhere. I'm maintaining them as part of my work at
Gandi.net. This is therefore a Gandi.net contribution to the Debian
Project.


Bug#1035829: frr: CVE-2022-43681 CVE-2022-40318 CVE-2022-40302

2023-06-13 Thread David Lamparter
notfound 1035829 frr/8.4.2-1
stop

On Tue, May 09, 2023 at 09:19:30PM +0200, Moritz Mühlenhoff wrote:
> CVE-2022-43681[0]:
> CVE-2022-40318[1]:
> CVE-2022-40302[2]:

All 3 issues are fixed/not present in 8.4 and thus also 8.4.2-1:

- CVE-2022-43681 - 6c4ca9812976596bf8b5226600269fc4031f1422
- CVE-2022-40318 - 1117baca3c592877a4d8a13ed6a1d9bd83977487
- CVE-2022-40302 - 3e46b43e3788f0f87bae56a86b54d412b4710286

Communication on this was indeed rather poor :( ... working with FRR
community to improve this.


-equi



Bug#1037497: plasma-discover: Unable To List packages

2023-06-13 Thread Bob Wong
Package: plasma-discover
Version: 5.27.5-2
Severity: important
X-Debbugs-Cc: ybx...@gmail.com

Dear Maintainer,

* What led up to the situation?
Change the source file from Debian 12 to Debian 13. And upgrade the system.

* What was the outcome of this action?
fetch ratings! false
adding empty sources model QStandardItemModel(0x56440b7b4340)
no component found for "org.debian.debian"
kf.newstuff.core: Could not find category "Calligra Flow Stencil"
KNS error in "Calligra_stencils" : KNSCore::ConfigFileError "All categories are
missing" QVariant(Invalid)
invalid kns backend! "/etc/xdg/calligra_stencils.knsrc" because: "Invalid
Calligra_stencils backend, contact your distributor."
org.kde.plasma.libdiscover: Discarding invalid backend
"calligra_stencils.knsrc"
kns error "/etc/xdg/calligra_stencils.knsrc" "Invalid Calligra_stencils
backend, contact your distributor."

* What outcome did you expect instead?
Load the packages normally.


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

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

Versions of packages plasma-discover depends on:
ii  appstream0.16.1-2
ii  apt-config-icons 0.16.1-2
ii  kio  5.103.0-1
ii  libappstreamqt2  0.16.1-2
ii  libc62.36-9
ii  libkf5attica55.103.0-1
ii  libkf5configcore55.103.0-2
ii  libkf5configgui5 5.103.0-2
ii  libkf5coreaddons55.103.0-1
ii  libkf5crash5 5.103.0-1
ii  libkf5dbusaddons55.103.0-1
ii  libkf5i18n5  5.103.0-1
ii  libkf5idletime5  5.103.0-2
ii  libkf5jobwidgets55.103.0-1
ii  libkf5kiocore5   5.103.0-1
ii  libkf5kiogui55.103.0-1
ii  libkf5newstuffcore5  5.103.0-1
ii  libkf5notifications5 5.103.0-1
ii  libkf5service-bin5.103.0-1
ii  libkf5service5   5.103.0-1
ii  libkf5widgetsaddons5 5.103.0-1
ii  libkf5windowsystem5  5.103.0-1
ii  libmarkdown2 2.2.7-2
ii  libpackagekitqt5-1   1.1.1-1
ii  libqt5core5a 5.15.8+dfsg-12
ii  libqt5dbus5  5.15.8+dfsg-12
ii  libqt5gui5   5.15.8+dfsg-12
ii  libqt5network5   5.15.8+dfsg-12
ii  libqt5qml5   5.15.8+dfsg-3
ii  libqt5quick5 5.15.8+dfsg-3
ii  libqt5webview5   5.15.8-2+b1
ii  libqt5widgets5   5.15.8+dfsg-12
ii  libstdc++6   12.2.0-14
ii  packagekit   1.2.6-5
ii  plasma-discover-common   5.27.5-2
ii  qml-module-org-kde-kcoreaddons   5.103.0-1
ii  qml-module-org-kde-kirigami2 5.103.0-1
ii  qml-module-org-kde-kquickcontrols5.103.0-1
ii  qml-module-org-kde-kquickcontrolsaddons  5.103.0-1
ii  qml-module-org-kde-qqc2desktopstyle  5.103.0-1
ii  qml-module-qtquick-dialogs   5.15.8-2

Versions of packages plasma-discover recommends:
ii  apt-config-icons-hidpi 0.16.1-2
ii  apt-config-icons-large 0.16.1-2
ii  apt-config-icons-large-hidpi   0.16.1-2
ii  kde-config-updates 5.27.5-2
ii  plasma-discover-backend-fwupd  5.27.5-2
ii  software-properties-qt 0.99.30-4

Versions of packages plasma-discover suggests:
pn  plasma-discover-backend-flatpak  

-- no debconf information



Bug#945269: debian-policy: packages should use tmpfiles.d(5) to create directories below /var

2023-06-13 Thread Mark Hindley
Simon,

Thanks for your care and insight with this and apologies for the delay in
replying (mails to elog...@packages.debian.org have been held up on a
mailserver).

On Tue, Jun 06, 2023 at 11:58:07AM +0100, Simon McVittie wrote:
> Exactly. My hope is that if we had:
> 
> Package: systemd
> Architecture: linux-any
> Provides: default-systemd-tmpfiles, systemd-tmpfiles
> Conflicts: systemd-tmpfiles
> Replaces: systemd-tmpfiles
> 
> Package: systemd-standalone-tmpfiles
> Architecture: linux-any
> Provides: systemd-tmpfiles
> Conflicts: systemd-tmpfiles
> Replaces: systemd-tmpfiles
> 
> Package: elogind
> Depends: systemd-standalone-tmpfiles# or Recommends?

In principle and just looking at the dependencies this seems a viable solution.
It is very similar to the way we handle the logind and default-logind virtual
packages.

Mark



Bug#1037496: mdadm: Please restore support for use without systemd as PID 1

2023-06-13 Thread Mark Hindley
Source: mdadm
Version: 4.2+20230227-1
Severity: normal

Dear Daniel,

SysV initscripts and cron jobs have recently been removed from mdadm.  It would
be a great help to users of non-systemd inits if you could restore them. Service
files and initscripts can happily coexist and systemd will use the available
service files in preference.

Installing recent mdadm on a non-systemd system can render the system
unbootable.

Thanks for you consideration.

Mark


-- System Information:
Debian Release: 12.0
merged-usr: no
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)



Bug#1037495: ITP: drogon -- Daemon for detecting brute force attacks

2023-06-13 Thread Pierre-Elliott Bécue
Package: wnpp
Severity: wishlist
Owner: Pierre-Elliott Bécue 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: drogon
  Version : 1.8.4
  Upstream Author : An Tao 
* URL : https://github.com/drogonframework/drogon
* License : MIT
  Programming Lang: C++
  Description : C++14/17-based HTTP application framework

Drogon can be used to easily build various types of web application server
programs using C++. Drogon is the name of a dragon in the American TV series
"Game of Thrones" that I really like.

Drogon is a cross-platform framework, It supports Linux, macOS, FreeBSD,
OpenBSD, HaikuOS, and Windows. Its main features are as follows:

  * Use a non-blocking I/O network lib based on epoll (kqueue under
macOS/FreeBSD) to provide high-concurrency, high-performance network
IO, please visit the TFB Tests Results for more details;
  * Provide a completely asynchronous programming mode;
  * Support Http1.0/1.1 (server side and client side);
  * Based on template, a simple reflection mechanism is implemented to
completely decouple the main program framework, controllers and
views.
  * Support cookies and built-in sessions;
  * Support back-end rendering, the controller generates the data to the view
to generate the Html page. Views are described by CSP template files, C++ 
codes
are embedded into Html pages through CSP tags. And the drogon command-line 
tool
automatically generates the C++ code files for compilation;
  * Support view page dynamic loading (dynamic compilation and loading at 
runtime);
  * Provide a convenient and flexible routing solution from the path to the
controller handler;
  * Support filter chains to facilitate the execution of unified logic (such as
login verification, Http Method constraint verification, etc.) before 
handling
HTTP requests;
  * Support https (based on OpenSSL);
  * Support WebSocket (server side and client side);
  * Support JSON format request and response, very friendly to the Restful API
application development;
  * Support file download and upload;
  * Support gzip, brotli compression transmission;
  * Support pipelining;
  * Provide a lightweight command line tool, drogon_ctl, to simplify the
creation of various classes in Drogon and the generation of view code;
  * Support non-blocking I/O based asynchronously reading and writing database
PostgreSQL and MySQL(MariaDB) database);
  * Support asynchronously reading and writing sqlite3 database based on thread
pool;
  * Support Redis with asynchronous reading and writing;
  * Support ARM Architecture;
  * Provide a convenient lightweight ORM implementation that supports for
regular object-to-database bidirectional mapping;
  * Support plugins which can be installed by the configuration file at load
time;
  * Support AOP with build-in joinpoints.
  * Support C++ coroutines

This package is needed by weakforced, which I also intend to package.

For now these packages will be in collab-maint, but I'll see if they
could go somewhere. I'm maintaining them as part of my work at
Gandi.net. This is therefore a Gandi.net contribution to the Debian
Project.


Bug#1037488: www.debian.org: drop static/packages-site.css entirely?

2023-06-13 Thread Thomas Lange
> On Tue, 13 Jun 2023 14:27:34 +0200, Cyril Brulebois  
> said:

> Probably best to finally drop it, to avoid wasting more brain time on
> suite updates (for that particular file)?
Yes, please drop it.

-- 
viele Grüße Thomas



Bug#1037493: lxqt: Debian 12 : startlxqt ERROR : "qt.qpa.xcb: cuold not connect to display" | lxdm work normally.

2023-06-13 Thread kachatelq
Package: lxqt
Version: 31
Severity: important
X-Debbugs-Cc: kachat...@hotmail.com

* I like multi-user.target and I like LXQt.
In Debian 11 startx call LXQt, there is no problem.
In Debian 12 startx call MATE,
startxlxqt NOT work: "qt.qpa.xcb could not connect to display"

* lxdm in Debian 12 work normally, LXQt work normally EXCEPT sound :
LXQt can NOT "establish connection to PulseAudio".
In MATE there is sound, no problems whith PulseAudio.


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

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

Versions of packages lxqt depends on:
ii  ark4:22.12.3-1
ii  cinnamon [x-window-manager]5.6.8-1
ii  engrampa   1.26.0-1
ii  featherpad 1.3.5-1
ii  gdm3 [x-display-manager]   43.0-3
ii  kwin-x11 [x-window-manager]4:5.27.5-3
ii  lightdm [x-display-manager]1.26.0-8
ii  lxdm [x-display-manager]   0.5.3-4
ii  lximage-qt 1.2.0-2
ii  lxqt-about 1.2.0-1
ii  lxqt-admin 1.2.0-1
ii  lxqt-branding-debian [lxqt-branding]   0.14.0.3
ii  lxqt-core  31
ii  lxqt-openssh-askpass   1.2.0-1
ii  lxqt-powermanagement   1.2.0-1
ii  lxqt-sudo  1.2.0-1
ii  marco [x-window-manager]   1.26.1-3
ii  metacity [x-window-manager]1:3.46.1-1
ii  muffin [x-window-manager]  5.6.4-1
ii  openbox [x-window-manager] 3.6.1-10
ii  pavucontrol5.0-2
ii  qlipper1:5.1.2-1+b1
ii  qps2.6.0-1
ii  qterminal  1.2.0-2
ii  qttranslations5-l10n   5.15.8-2
ii  sddm [x-display-manager]   0.19.0-5
ii  sddm-theme-breeze [sddm-theme] 4:5.27.5-2
ii  sddm-theme-debian-breeze [sddm-theme]  4:5.27.5-2
ii  slim [x-display-manager]   1.3.6-5.3
ii  xarchiver  1:0.5.4.20-2
ii  xdm [x-display-manager]1:1.1.11-3+b2
ii  xfce4-clipman  2:1.6.2-1
ii  xfwm4 [x-window-manager]   4.18.0-1

Versions of packages lxqt recommends:
ii  audacious  4.2-1
ii  chromium [www-browser] 114.0.5735.106-1~deb12u1
ii  evolution [mail-reader]3.46.4-2
ii  feathernotes   1.1.0-1
ii  firefox-esr [www-browser]  102.12.0esr-1~deb12u1
ii  gucharmap  1:15.0.2-1
ii  hexchat2.16.1-1+b3
ii  kmail [mail-reader]4:22.12.3-1
ii  konqueror [www-browser]4:22.12.3-1
ii  lynx [www-browser] 2.9.0dev.12-1
ii  meteo-qt   3.3-1
ii  network-manager-gnome  1.30.0-2
ii  plasma-nm  4:5.27.5-2
ii  preload0.6.4-5+b1
ii  qpdfview   0.5.0+ds-2
ii  quassel1:0.14.0-1+b2
ii  screengrab 2.5.0-1
ii  smplayer   22.7.0~ds0-1
ii  smtube 21.7.0-1+b1

Versions of packages lxqt suggests:
pn  calibre
pn  compton-conf   
pn  juffed 
pn  nomacs 
pn  obconf-qt  
pn  qt5-style-kvantum  
pn  qtpass 
pn  shutter
pn  vokoscreen 

-- no debconf information



Bug#1037492: ITP: qt6-base-private-gles-dev -- This package contains the private header development files for building some Qt 6 applications like the Qt Creator QML Designer plugin.

2023-06-13 Thread Leonardo Held

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

* Package name : qt6-base-private-gles-dev
Version : 6.4.2
Upstream Author : The Qt Company
* URL : https://www.qt.io/developers/
* License : LGPL-3, GPL-2, GFDL-NIV-1.3, GPL-3 with Qt-1.0 exception,
BSD-3-clause, GFDL-NIV-1.3, Apache-2.0, CC0-1.0, FTL, Hybrid-BSD,
Boost-1.0, W3C, Unicode, libpng, brg-endian, ICC
Programming Lang:  C, C++
Description : This package contains the private header development files
for building some Qt 6 applications like the Qt Creator QML Designer plugin.


qt6-base-private-gles-dev is intend for embedded devices that support
the OpenGL ES rendering API.

This package is useful for using Debian with Qt in devices that are not
contemplated by the already packaged qt6-base-private-dev, which only
works with OpenGL implementations.
This is actively used by anyone who is building Qt applications for
embedded and the scope of this was discussed in bug #1035985, hence the
ITP.
This package will be maintained under the Qt/KDE team.


[Toradex Logo]    Embedded Computing
Made Easy
Choose Us | 
Products | Developer Center | 
Community | Careers
Join our webinar:
- Simplify the development of critical medical and industrial applications with QNX 
and NXP i.MX 8 | June 23, 2023: 
Register

Meet our engineers at:
- Sensors Converge | California, USA | June 20-22, 2023
- Embedded Open Source Summit (EOSS) | June 26-30, 2023 | Czech Republic



Bug#1037491: ITP: qt6-base-gles-dev -- This package contains the header development files used for building Qt 6 applications.

2023-06-13 Thread Leonardo Held

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

* Package name : qt6-base-gles-dev
Version : 6.4.2
Upstream Author : The Qt Company
* URL : https://www.qt.io/developers/
* License : LGPL-3, GPL-2, GFDL-NIV-1.3, GPL-3 with Qt-1.0 exception,
BSD-3-clause, GFDL-NIV-1.3, Apache-2.0, CC0-1.0, FTL, Hybrid-BSD,
Boost-1.0, W3C, Unicode, libpng, brg-endian, ICC
Programming Lang:  C, C++
Description : This package contains the header development files used
for building Qt 6 applications.


qt6-base-gles-dev is intend for embedded devices that support the OpenGL
ES rendering API.

This package is useful for using Debian with Qt in devices that are not
contemplated by the already packaged qt6-base-dev, which only works with
OpenGL implementations.
This is actively used by anyone who is building Qt applications for
embedded and the scope of this was discussed in bug #1035985, hence the
ITP.
This package will be maintained under the Qt/KDE team.

[Toradex Logo]    Embedded Computing
Made Easy
Choose Us | 
Products | Developer Center | 
Community | Careers
Join our webinar:
- Simplify the development of critical medical and industrial applications with QNX 
and NXP i.MX 8 | June 23, 2023: 
Register

Meet our engineers at:
- Sensors Converge | California, USA | June 20-22, 2023
- Embedded Open Source Summit (EOSS) | June 26-30, 2023 | Czech Republic



Bug#1037490: www.debian.org: clean up old files

2023-06-13 Thread Cyril Brulebois
Package: www.debian.org
Severity: normal
User: www.debian@packages.debian.org

Hi,

Spotted while working on #1037479: we have a bunch of files around that
are no longer useful, because relevant suites are EOL and archived, and
have been dropped from the relevant config files, templates, etc.

They could probably be cleaned up, but I don't want to rush this kind of
things, hence this bug report.

Trivial candidates:

kibi@picconi:/srv/packages.debian.org$ du -sch 
www/{,source/}{jessie,stretch}*
681Mwww/jessie
91M www/jessie-backports
11M www/jessie-backports-sloppy
15M www/jessie-updates
594Mwww/stretch
73M www/stretch-backports
9.9Mwww/stretch-backports-sloppy
7.3Mwww/stretch-updates
97M www/source/jessie
22M www/source/jessie-backports
8.5Mwww/source/jessie-backports-sloppy
5.7Mwww/source/jessie-updates
95M www/source/stretch
21M www/source/stretch-backports
8.3Mwww/source/stretch-backports-sloppy
5.5Mwww/source/stretch-updates
1.7Gtotal


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



Bug#1037489: ITP: libqt6gui6-gles -- The QtGui module extends QtCore with GUI functionality for GLES platforms.

2023-06-13 Thread Leonardo Held

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

* Package name : libqt6gui6-gles
Version : 6.4.2
Upstream Author : The Qt Company
* URL : https://www.qt.io/developers/
* License : LGPL-3, GPL-2, GFDL-NIV-1.3, GPL-3 with Qt-1.0 exception,
BSD-3-clause, GFDL-NIV-1.3, Apache-2.0, CC0-1.0, FTL, Hybrid-BSD,
Boost-1.0, W3C, Unicode, libpng, brg-endian, ICC
Programming Lang:  C, C++
Description : The QtGui module extends QtCore with GUI functionality for
GLES platforms.

libqt6gui6-gles is intend for embedded devices that support the OpenGL
ES rendering API.

This package is useful for using Debian with Qt in devices that are not
contemplated by the already packaged libqt6gui6, which only works with
OpenGL implementations.
This is actively used by anyone who is building Qt applications for
embedded and the scope of this was discussed in bug #1035985, hence the ITP.
This package will be maintained under the Qt/KDE team.


[Toradex Logo]    Embedded Computing
Made Easy
Choose Us | 
Products | Developer Center | 
Community | Careers
Join our webinar:
- Simplify the development of critical medical and industrial applications with QNX 
and NXP i.MX 8 | June 23, 2023: 
Register

Meet our engineers at:
- Sensors Converge | California, USA | June 20-22, 2023
- Embedded Open Source Summit (EOSS) | June 26-30, 2023 | Czech Republic



Bug#1037488: www.debian.org: drop static/packages-site.css entirely?

2023-06-13 Thread Cyril Brulebois
Package: www.debian.org
Severity: normal
User: www.debian@packages.debian.org

Hi,

Spotted while working on #1037479, static/packages-site.css hardcodes
suite names. But digging a little deeper, it doesn't seem to be imported
anymore, after the huge redesign:

commit 74376d3a2530091edba43c51241022ca26977b7b
Date:   Thu Oct 28 16:26:15 2010 +0200

Probably best to finally drop it, to avoid wasting more brain time on
suite updates (for that particular file)?


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



Bug#1001786: jpeg-xl: Please build plugins

2023-06-13 Thread Mathieu Malaterre
Control: tags -1 - wontfix

On Fri, Jun 9, 2023 at 1:39 PM Julian Wollrath  wrote:
>
> Hi,
>
> > it seems, like upstream is moving the plugin to use lcms2 [1] which is
> > available in debian.
>
> I tried building a package with a new snapshot and enabled the building
> of the gdk-pixbuf plugin and ended up with the attached changes to the
> packaging. I hope that might be of use.

Very neat ! Thanks.

Uploaded to exp a minute ago.

-M



Bug#1037487: ITP: trantor -- Non-blocking I/O cross-platform TCP network library

2023-06-13 Thread Pierre-Elliott Bécue
Package: wnpp
Severity: wishlist
Owner: Pierre-Elliott Bécue 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: trantor
  Version : 1.5.11
  Upstream Author : An Tao 
* URL : https://github.com/an-tao/trantor
* License : BSD
  Programming Lang: C++
  Description : Non-blocking I/O cross-platform TCP network library

Trantor is a non-blocking I/O cross-platform TCP network library, using
C++14. Drawing on the design of Muduo Library

This package is needed by weakforced as a transitive dependency of
drogon, which I also intend to package.

For now these packages will be in collab-maint, but I'll see if they
could go somewhere. I'm maintaining them as part of my work at
Gandi.net. This is therefore a Gandi.net contribution to the Debian
Project.


Bug#1037113: Should not be in /usr/games

2023-06-13 Thread Dirk Eddelbuettel


On 13 June 2023 at 00:46, Josh Triplett wrote:
| On Mon, Jun 12, 2023 at 05:03:01PM -0500, Dirk Eddelbuettel wrote:
| > 
| > reassign 1037113 screen-message
| > thanks
| > 
| > Binary package 'sm' is from source package 'screen-message'
| > 
| > Binary package 'r-cran-sm' is from source package 'sm', which I maintain, 
and
| > something totally different :-)   Not the first crossed bug report so no
| > worries, the reassign should work.
| 
| Sorry about that, and thank you.

Not to worry: I had a bad 'anti-pattern' of naming packages made from CRAN
for R after just their CRAN name. 'sm' is one, another bad one is 'boot' (for
the statistical method the bootstrap).  These days we stick to r-cran-$NAME.

Best,  Dirk

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



Bug#1037486: new upstream (3.5)

2023-06-13 Thread Daniel Baumann
Package: rspamd
Severity: wishlist

Hi,

thank you so much for maintaining rspamd in debian.

Some time ago, there was a new upstream release with some nice new
features. It would be nice if you could update the package to the
current version (3.5).

Regards,
Daniel



Bug#1037346: Lost all emails during update

2023-06-13 Thread Michael Stockenhuber
Dear Kai,
Thank you very much for this report and a possible solution. Exactly the
same happened to me on upgrade to bookworm. Can you please elaborate how
you did this in detail? I really would be in trouble if I lose the emails.
I know this is a big ask but I would really appreciate your help.
Best regards
Michael

PS. I may have a delay answering, I am down under.


Bug#1037485: Adsense of ovt in Debian 12 iso image

2023-06-13 Thread Winnie Yue
Package: open-vm-tools
Version: 11.2.5 or higher versions
Severity: Serious

We noticed that there is no open-vm-tools in Debian 12.0 iso image. We’d like 
to learn more about this change, is that by designed? If so, could you please 
tell us more about the reason? Thanks a lot.


Best regards
Winnie Yue


Bug#1037479: 500 Internal Server Error accessing https://packages.debian.org/testing/name_of_package

2023-06-13 Thread Cyril Brulebois
Control: tag -1 patch pending

Hi,

And yes, thanks for reporting!

Laura Arjona Reina  (2023-06-13):
> Thanks for the report. It seems that our website packages.debian.org
> still doesn't recognize trixie being testing.

It's worse than that: it doesn't know about trixie at all yet. There are
many places were suites are hardcoded, and I missed adding trixie to one
of the central place (config.sh.sed.in). That's fixed now, and it should
be better after the next mirror push (which triggers indexing). Note the
previous push/indexing is still running, and I really don't want to try
and add a manual run in there, so waiting something like 6 to 12 hours
should be our safest bet.

https://salsa.debian.org/webmaster-team/packages/-/commit/bde18c345814d497ddd0537471759a2d9aad2fcd

Tagging accordingly, the first person to spot the right files popping up
in the right places can close this bug report.


While looking around I spotted the CSS also hardcode suite names. I'll
look into that next. Also spotted leftover files from old suites
(jessie, stretch), will file a different ticket for those.


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


signature.asc
Description: PGP signature


Bug#998705: Many 502 errors, when using apt-cacher-ng for Debian installation

2023-06-13 Thread Mirco Schmidt
On Wed, 16 Feb 2022 09:28:13 -0300 Eriberto Mota  wrote:
> Hi guys,
> 
> I am running Debian Stable (Bullseye) in my desktop and in my local server.
> 
> Yesterday I made a backport version of the apt-cacher-ng for me and I put it
> in the server. The problem seems is solved.
> 
> Regards,
> 
> Eriberto
> 
> 


Same here, while upgrading a machine to bookworm I experienced the issue. Went 
ahead and upgraded the Machine hosting ACNG first and the problem is fixed ;-)

Greetz
Mircsicz



Bug#1037364: nextcloud-desktop: TLS initilization failed

2023-06-13 Thread Hefee
Control: tags -1 moreinfo
Control: serverity -1 important

Hey,

I never had issues with using Nextcloud desktop to connect to my server, 
that's why I downgrade the serverity, as it has something to do with your 
specific setup.
I expect that the issue is that your server only accepts TLS < 1.3. The last 
years a lot of ciphers are not trusted anymore by default. You can check your 
servers certificate with online tools e.g. https://www.ssllabs.com/ssltest/.

regards,

hefee

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


Bug#1037482: Bug on Debian 12 Bookworm - add-apt-repository not work

2023-06-13 Thread Salvatore Bonaccorso
Control: reassign -1 software-properties-common
Control: forcemerge 1029766 -1

Hi Philippe,

On Tue, Jun 13, 2023 at 12:41:30PM +0200, pham...@bluewin.ch wrote:
> Package:  add-apt-repository
> Version: ?
> Severity: high
> 
> Bug Description:
> 
> This command, which no longer allows you to add external repositories, worked 
> perfectly under Debian 10 & 11, but it no longer works under Debian 12.
> Command to add Mozilla Firefox official ppa :
> add-apt-repository "deb http://ppa.launchpad.net/mozillateam/ppa/ubuntu focal 
> main"
> apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
> 0AB215679C571D1C8325275B9BDB3D89CE49EC21
> Now it generates errors :
> root@station:~# add-apt-repository "deb 
> http://ppa.launchpad.net/mozillateam/ppa/ubuntu lunar main"
> Traceback (most recent call last):
>   File "/usr/bin/add-apt-repository", line 362, in 
> sys.exit(0 if addaptrepo.main() else 1)
>   ^
>   File "/usr/bin/add-apt-repository", line 345, in main
> shortcut = handler(source, **shortcut_params)
>^^
>   File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
> 40, in shortcut_handler
> return handler(shortcut, **kwargs)
>^^^
>   File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 78, 
> in __init__
> self.lpppa
>   File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 126, 
> in lpppa
> self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
>   ^^^
>   File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 113, 
> in lpteam
> self._lpteam = self.lp.people(self.teamname)
>^^
> AttributeError: 'NoneType' object has no attribute 'people'
> Thank you to correct this as soon as possible.
> Best regards.

Please see #1029766. Installing  python3-launchpadlib should resolve
your issue.

Will merge the two.

Regards,
Salvatore



Bug#1037483: O: python-reportlab - library to create PDF documents using Python3

2023-06-13 Thread Matthias Klose

Package: wnpp

Orphaning python-reportlab.

There is now a 4.0.x release, which splits out the accelerators into a separate 
source package. See


  https://hg.reportlab.com/hg-public/reportlab/
  https://hg.reportlab.com/hg-public/rl-accel/

Requires some re-packaging.



Bug#994682: Debian 12 Bookworm

2023-06-13 Thread Roland Tapken
I have modified the patches to work with Debian 12 Bookworm.

Most noticeable, the "poweroff" command must now be called with the parameter 
"-f" to switch off the system while waiting for an input.--- orig/functions	2023-06-12 19:44:03.169739289 +0200
+++ /usr/lib/cryptsetup/functions	2023-06-12 19:45:25.780386107 +0200
@@ -83,6 +83,7 @@
  CRYPTTAB_OPTION_keyslot \
  CRYPTTAB_OPTION_header \
  CRYPTTAB_OPTION_tcrypthidden \
+ CRYPTTAB_OPTION_timeout \
  CRYPTTAB_OPTION_same_cpu_crypt \
  CRYPTTAB_OPTION_submit_from_crypt_cpus \
  CRYPTTAB_OPTION_no_read_workqueue \
@@ -186,7 +187,7 @@
 fi
 ;;
 # numeric options >=0
-offset|skip|tries|keyslot|keyfile-offset)
+offset|skip|tries|keyslot|keyfile-offset|timeout)
 if ! printf '%s' "${VALUE-}" | grep -Exq "[0-9]+"; then
 return 1
 fi
--- /usr/share/initramfs-tools/scripts/local-top/cryptroot.orig	2023-04-21 00:54:29.0 +0200
+++ /usr/share/initramfs-tools/scripts/local-top/cryptroot	2023-06-12 19:38:06.706673696 +0200
@@ -148,8 +148,16 @@
 fi
 fi
 
-local count=0 maxtries="${CRYPTTAB_OPTION_tries:-3}" fstype vg rv
+local count=0 maxtries="${CRYPTTAB_OPTION_tries:-3}" poweroffpid=0 fstype vg rv
 while [ $maxtries -le 0 ] || [ $count -lt $maxtries ]; do
+if [ "${CRYPTTAB_OPTION_timeout:-0}" -gt 15 ]; then
+# Power down if not key has been entered within $timeout seconds.
+# Ignore values below 15 seconds to give the user a chance
+# to enter his passphrase in case of a typo in /etc/crypttab.
+cryptsetup_message "Timeout in $CRYPTTAB_OPTION_timeout seconds"
+	(sleep "$CRYPTTAB_OPTION_timeout" && cryptsetup_message "poweroff" && /usr/sbin/poweroff -f) &
+poweroffpid=$!
+fi
 if [ -z "${CRYPTTAB_OPTION_keyscript+x}" ] && [ "$CRYPTTAB_KEY" != "none" ]; then
 # unlock via keyfile
 unlock_mapping "$CRYPTTAB_KEY"
@@ -159,6 +167,9 @@
 fi
 rv=$?
 count=$(( $count + 1 ))
+if [ "$poweroffpid" -gt 0 ]; then
+kill "$poweroffpid"
+fi
 
 if [ $rv -ne 0 ]; then
 cryptsetup_message "ERROR: $CRYPTTAB_NAME: cryptsetup failed, bad password or options?"


Bug#1037336: fixed in devscripts 2.23.5

2023-06-13 Thread Sebastiaan Couwenberg

On Mon, 12 Jun 2023 17:37:12 + Debian FTP Masters wrote:

   * debchange: Update to current Debian distributions (Add bookworm and trixie
 and drop stretch, jessie, and wheezy) (Closes: #1037336)


This change is also needed in bookworm where `dch --bpo` still uses 
bullseye-backports instead of bookworm-backports.


Will you provide the bookworm-pu?

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#1037482: Bug on Debian 12 Bookworm - add-apt-repository not work

2023-06-13 Thread pham...@bluewin.ch
Package:  add-apt-repository
Version: ?
Severity: high

Bug Description:

This command, which no longer allows you to add external repositories, worked 
perfectly under Debian 10 & 11, but it no longer works under Debian 12.
Command to add Mozilla Firefox official ppa :
add-apt-repository "deb http://ppa.launchpad.net/mozillateam/ppa/ubuntu focal 
main"
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
0AB215679C571D1C8325275B9BDB3D89CE49EC21
Now it generates errors :
root@station:~# add-apt-repository "deb 
http://ppa.launchpad.net/mozillateam/ppa/ubuntu lunar main"
Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 362, in 
sys.exit(0 if addaptrepo.main() else 1)
  ^
  File "/usr/bin/add-apt-repository", line 345, in main
shortcut = handler(source, **shortcut_params)
   ^^
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
40, in shortcut_handler
return handler(shortcut, **kwargs)
   ^^^
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 78, in 
__init__
self.lpppa
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 126, in 
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
  ^^^
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 113, in 
lpteam
self._lpteam = self.lp.people(self.teamname)
   ^^
AttributeError: 'NoneType' object has no attribute 'people'
Thank you to correct this as soon as possible.
Best regards.

Philippe


Bug#1037481: outguess: Stack smashing detected and SIGABRT during finding of best embedding

2023-06-13 Thread Björn Wiberg
Package: outguess
Version: 1:0.4-2
Severity: important

Hello,

When trying to run OutGuess on Debian 12, I get a "stack smashing detected" 
error message and the program is aborted (SIGABRT).
This appears to happen for all JPEG images, i.e. it is not triggered by a 
certain image.

Steps to reproduce:

$ wget -q 
https://upload.wikimedia.org/wikipedia/commons/3/3f/JPEG_example_flower.jpg
$ echo msg1 > msg1.txt
$ echo msg2 > msg2.txt
$ outguess -k "key1" -d msg1.txt -E -K "key2" -D msg2.txt -p 100 
JPEG_example_flower.jpg JPEG_example_flower.steg.jpg
Initialize encoding/decoding tables
Reading JPEG_example_flower.jpg
JPEG compression quality set to 100
Extracting usable bits:   70325 bits
Correctable message size: 17434 bits, 24.79%
Encoded 'msg1.txt': 40 bits, 5 bytes
Finding best embedding...
0:33(45.8%)[82.5%], bias28(0.85), saved:-1, total:  0.05%
1:28(38.9%)[70.0%], bias25(0.89), saved:-1, total:  0.04%
6:30(42.3%)[75.0%], bias19(0.63), saved:-1, total:  0.04%
   11:28(38.9%)[70.0%], bias13(0.46), saved:-1, total:  0.04%
11, 41: Embedding data: 40 in 70325
Bits embedded: 72, changed: 28(38.9%)[70.0%], bias: 13, tot: 68673, skip: 68601
Encoded 'msg2.txt' with ECC: 96 bits, 12 bytes
Finding best embedding...
*** stack smashing detected ***: terminated
Aborted

A GDB session shows the following (nothing new):

$ gdb --args outguess -k "key1" -d msg1.txt -E -K "key2" -D msg2.txt -p 100 
JPEG_example_flower.jpg JPEG_example_flower.steg.jpg
GNU gdb (Debian 13.1-3) 13.1
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from outguess...
(No debugging symbols found in outguess)
(gdb) run
Starting program: /usr/bin/outguess -k key1 -d msg1.txt -E -K key2 -D msg2.txt 
-p 100 JPEG_example_flower.jpg JPEG_example_flower.steg.jpg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Initialize encoding/decoding tables
Reading JPEG_example_flower.jpg
JPEG compression quality set to 100
Extracting usable bits:   70325 bits
Correctable message size: 17434 bits, 24.79%
Encoded 'msg1.txt': 40 bits, 5 bytes
Finding best embedding...
0:33(45.8%)[82.5%], bias28(0.85), saved:-1, total:  0.05%
1:28(38.9%)[70.0%], bias25(0.89), saved:-1, total:  0.04%
6:30(42.3%)[75.0%], bias19(0.63), saved:-1, total:  0.04%
   11:28(38.9%)[70.0%], bias13(0.46), saved:-1, total:  0.04%
11, 41: Embedding data: 40 in 70325
Bits embedded: 72, changed: 28(38.9%)[70.0%], bias: 13, tot: 68673, skip: 68601
Encoded 'msg2.txt' with ECC: 96 bits, 12 bytes
Finding best embedding...
*** stack smashing detected ***: terminated

Program received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=, signo=signo@entry=6, 
no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
(gdb) bt full
#0  __pthread_kill_implementation (threadid=, 
signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
tid = 
ret = 0
pd = 
old_mask = {__val = {0}}
ret = 
#1  0x77d83d2f in __pthread_kill_internal (signo=6, threadid=) at ./nptl/pthread_kill.c:78
No locals.
#2  0x77d34ef2 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
ret = 
#3  0x77d1f472 in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1
act = {__sigaction_handler = {sa_handler = 0x20, sa_sigaction = 0x20}, 
sa_mask = {__val = {140737351587994, 17179869190, 8589934656, 140737488344528, 
8589939592, 6848, 93824992358358, 1431883968, 1, 1706640, 0, 93824992485456, 
93824992754952, 140737488344528, 93824992485384, 93824992485744}}, sa_flags = 
1431738664, sa_restorer = 0x8}
#4  0x77d782d0 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77e92210 "*** %s ***: terminated\n") at 
../sysdeps/posix/libc_fatal.c:155
ap = {{gp_offset = 24, fp_offset = 247, overflow_arg_area = 
0x7fffd050, reg_save_area = 0x7fffcfe0}}
fd = 
list = 
nlist = 
cp = 
#5  0x77e10e82 in __GI___fortify_fail (msg=msg@entry=0x77e921f8 
"stack smashing detected") at ./debug/fortify_fail.c:26
No locals.
#6  0x77e10e60 in 

Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-13 Thread Marco d'Itri
retitle -1 1037362 usrmerge: fails to run ldd

On Jun 13, Lawrence Bayly  wrote:

> Spoke too soon, usrmerge broke my system worse than I could have 
> imagined, /usr/bin/init went to systemd but in the old place 
> /lib/systemd (the lib folder was either empty or not there, likely 
> because of the usrmerge), fixing that didn't really do much as 
> I suspect a whole bunch of other stuff was moved without the system 
> really knowing where it all was. (I could have sat there moving stuff 
> around or symlinking to hopefully solve the problem but in the end it 
> seemed like alot of work)
At this point it is not really clear to me what you have done, but 
please note that since convert-usrmerge failed running ldd it means that 
it did not modify your system in any way.
So this looks like auto-inflicted damage to me.

I will keep this bug around for a while to see if anybody else shows up 
with the same problem and to improve the error message.

-- 
ciao,
Marco


signature.asc
Description: PGP signature


Bug#1037480: autopkgtest fails with golang-1.20

2023-06-13 Thread Shengjing Zhu
Source: ycmd
Version: 0+20230103+gitf53e7ac+ds-1
Severity: serious
X-Debbugs-Cc: z...@debian.org

Control: forworded -1 https://github.com/ycm-core/ycmd/commit/01a1f543

I've updated golang-defaults to 1.20 in unstable, your package's autopkgtest
fails with that.

I've sent the fix to upstream, could you backport the commit or package a new
snapshot.

https://github.com/ycm-core/ycmd/commit/01a1f543

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

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



Bug#973050: needrestart: Use of uninitialized value in hex at /usr/share/perl5/NeedRestart/uCode/AMD.pm line 169

2023-06-13 Thread Renato Gallo
needrestart -vw
[main] eval /etc/needrestart/needrestart.conf
[main] needrestart v3.6
[main] running in root mode
[Core] Using UI 'NeedRestart::UI::stdio'...
[main] systemd detected
[ucode] using NeedRestart::uCode::Intel
[ucode] using NeedRestart::uCode::AMD
[uCode/Intel] #0 current revision: 0xa5c
+ iucode_tool --scan-system
+ grep -oE [^[:space:]]+$
+ sig=processor
+ [ -r /sys/devices/system/cpu/cpu0/microcode/processor_flags ]
+ cat /sys/devices/system/cpu/cpu0/microcode/processor_flags
+ filter=-s processor,0x0
+ test -r /etc/needrestart/iucode.sh
+ . /etc/needrestart/iucode.sh
+ type bsdtar
+ IUCODE_TOOL_EXTRA_OPTIONS=
+ test -r /etc/default/intel-microcode
+ . /etc/default/intel-microcode
+ test  = no
+ [ -r /usr/share/misc/intel-microcode* ]
+ iucode_tool -l -s processor,0x0 --ignore-broken -tb
/lib/firmware/intel-ucode
+ grep processor
Use of uninitialized value $processor in concatenation (.) or string at
/usr/share/perl5/NeedRestart/uCode.pm line 61.
[ucode] # did not get available microcode version
[uCode/AMD] #0 cpuid 0x00a50f00  (/dev/cpu/0/cpuid)
[uCode/AMD] #0 cpuid 0x00a50f00  (/proc/cpuinfo)
[uCode/AMD] #0 running ucode 0x0a5c
[uCode/AMD] cpuid 0x00100f80: found processor id 0x1080
[uCode/AMD] cpuid 0x00100f81: found processor id 0x1081
[uCode/AMD] cpuid 0x00100f62: found processor id 0x1062
[uCode/AMD] cpuid 0x00100f23: found processor id 0x1022
[uCode/AMD] cpuid 0x00100f43: found processor id 0x1043
[uCode/AMD] cpuid 0x00100f91: found processor id 0x1081
[uCode/AMD] cpuid 0x00100f2a: found processor id 0x1020
[uCode/AMD] cpuid 0x00100f63: found processor id 0x1043
[uCode/AMD] cpuid 0x00100f42: found processor id 0x1041
[uCode/AMD] cpuid 0x00300f10: found processor id 0x3010
[uCode/AMD] cpuid 0x00200f31: found processor id 0x2031
[uCode/AMD] cpuid 0x00100f52: found processor id 0x1041
[uCode/AMD] cpuid 0x00100fa0: found processor id 0x10a0
[uCode/AMD] cpuid 0x00100f53: found processor id 0x1043
[uCode/AMD] cpuid 0x00100f22: found processor id 0x1022
[uCode/AMD] cpuid 0x00500f10: found processor id 0x5010
[uCode/AMD] cpuid 0x00500f20: found processor id 0x5020
[uCode/AMD] processor id 0x1022: available ucode 0x0183
[uCode/AMD] processor id 0x1020: available ucode 0x0184
[uCode/AMD] processor id 0x1062: available ucode 0x01c7
[uCode/AMD] processor id 0x1043: available ucode 0x01c8
[uCode/AMD] processor id 0x1081: available ucode 0x01d9
[uCode/AMD] processor id 0x1080: available ucode 0x01da
[uCode/AMD] processor id 0x1041: available ucode 0x01db
[uCode/AMD] processor id 0x10a0: available ucode 0x01dc
[uCode/AMD] processor id 0x2031: available ucode 0x0232
[uCode/AMD] processor id 0x3010: available ucode 0x0327
[uCode/AMD] processor id 0x5010: available ucode 0x0529
[uCode/AMD] processor id 0x5020: available ucode 0x05000119
[uCode/AMD] cpuid 0x00600f20: found processor id 0x6020
[uCode/AMD] cpuid 0x00610f01: found processor id 0x6101
[uCode/AMD] cpuid 0x00600f12: found processor id 0x6012
[uCode/AMD] processor id 0x6012: available ucode 0x0600063e
[uCode/AMD] processor id 0x6020: available ucode 0x06000852
[uCode/AMD] processor id 0x6101: available ucode 0x06001119
[uCode/AMD] cpuid 0x00700f01: found processor id 0x7001
[uCode/AMD] processor id 0x7001: available ucode 0x0700010f
[uCode/AMD] cpuid 0x00800f82: found processor id 0x8082
[uCode/AMD] cpuid 0x00800f12: found processor id 0x8012
[uCode/AMD] cpuid 0x00830f10: found processor id 0x8310
[uCode/AMD] processor id 0x8082: available ucode 0x0800820d
[uCode/AMD] processor id 0x8012: available ucode 0x0800126e
[uCode/AMD] processor id 0x8310: available ucode 0x08301072
[uCode/AMD] cpuid 0x00a00f10: found processor id 0xa010
[uCode/AMD] cpuid 0x00a00f11: found processor id 0xa011
[uCode/AMD] cpuid 0x00a00f12: found processor id 0xa012
[uCode/AMD] processor id 0xa010: available ucode 0x0a001078
[uCode/AMD] processor id 0xa011: available ucode 0x0a0011ce
[uCode/AMD] processor id 0xa012: available ucode 0x0a001231
Use of uninitialized value $processor in concatenation (.) or string at
/usr/share/perl5/NeedRestart/uCode.pm line 61.
[ucode] # did not get available microcode version

Failed to check for processor microcode upgrades.











On Thu, 29 Oct 2020 19:30:16 +0100 Thomas Liske 
wrote:
> Hi,
>
> could you please provide the output of `needrestart -vw`?
>
>
> TIA & Regards,
> Thomas
>
>
> On 27.10.20 10:44, Martin-Éric Racine wrote:
>  > Package: needrestart
>  > Version: 3.5-1
>  > Severity: normal
>  >
> > Scanning processes...
> > Use of uninitialized value in hex at
/usr/share/perl5/NeedRestart/uCode/AMD.pm line 169.
   ]
> > Scanning processor microcode...
> > Scanning linux images...
> > Running 

Bug#1037479: 500 Internal Server Error accessing https://packages.debian.org/testing/name_of_package

2023-06-13 Thread Laura Arjona Reina

Package: www.debian.org
User: www.debian@packages.debian.org
Usertag: packages
Severity: normal
X-Debbugs-CC: kevin.torkel...@gmail.com, webmas...@debian.org

Hi Kevin
Thanks for the report. It seems that our website packages.debian.org still 
doesn't recognize trixie being testing.
Not related to any package in particular, if I go to 
https://packages.debian.org/testing/ I obtain:


couldn't read index file trixie/index.en.html: No such file or directory

I'm creating a bug report about it, if you want
to follow you can subscribe to the bug sending a mail to
-subscr...@bugs.debian.org (being  the bug number).

Kind regards

Laura Arjona Reina
https://wiki.debian.org/LauraArjona


 Mensaje reenviado 
Asunto: 500 Internal Server Error
Fecha:  Tue, 13 Jun 2023 00:48:32 -0500
De: Kevin Torkelson 
Para:   webmas...@debian.org



While attempting to investigate why the KDE/Plasma "Discover" app isn't finding 
sources, just after allowing my "testing" system to update from Codename 
bullseye to trixie I went to visit the web site searching for a package "discover".


https://packages.debian.org/testing/discover 



I received a 500 error with a message to please inform the webmaster, thus I am. 
Additional details:


GET https://packages.debian.org/testing/discover 


[HTTP/2 500 Internal Server Error 583ms]

GET /testing/discover HTTP/1.1
Host: packages.debian.org 
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 
Firefox/102.0
Accept: 
text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8

Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://packages.debian.org/ 
DNT: 1
Connection: keep-alive
Upgrade-Insecure-Requests: 1
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: cross-site

HTTP/2 500 Internal Server Error
date: Tue, 13 Jun 2023 05:38:28 GMT
server: Apache
x-content-type-options: nosniff
x-frame-options: sameorigin
referrer-policy: no-referrer
x-xss-protection: 1
permissions-policy: interest-cohort=()
strict-transport-security: max-age=15552000
content-length: 603
content-type: text/html; charset=iso-8859-1
X-Firefox-Spdy: h2

favicon.ico returned 200:



https://packages.debian.org/favicon.ico 


While attempting to investigate why the KDE/Plasma "Discover" app isn't finding 
sources, just after allowing my "testing" system to update from Codename 
bullseye to trixie I went to visit the web site searching for a package "discover".


https://packages.debian.org/testing/discover 



I received a 500 error with a message to please inform the webmaster, thus I am. 
Additional details:


GET https://packages.debian.org/testing/discover 


[HTTP/2 500 Internal Server Error 583ms]

GET /testing/discover HTTP/1.1
Host: packages.debian.org 
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 
Firefox/102.0
Accept: 
text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8

Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
Referer: https://packages.debian.org/ 
DNT: 1
Connection: keep-alive
Upgrade-Insecure-Requests: 1
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: cross-site

HTTP/2 500 Internal Server Error
date: Tue, 13 Jun 2023 05:38:28 GMT
server: Apache
x-content-type-options: nosniff
x-frame-options: sameorigin
referrer-policy: no-referrer
x-xss-protection: 1
permissions-policy: interest-cohort=()
strict-transport-security: max-age=15552000
content-length: 603
content-type: text/html; charset=iso-8859-1
X-Firefox-Spdy: h2

favicon.ico returned 200.
https://packages.debian.org/favicon.ico 


Please don't hesitate to contact me if I may be of any additional assistance.

Best Regards,
Kevin Torkelson



Bug#973050: needrestart: Use of uninitialized value in hex at /usr/share/perl5/NeedRestart/uCode/AMD.pm line 169

2023-06-13 Thread Renato Gallo
Here it is

root@ghost:~# needrestart -vw
[main] eval /etc/needrestart/needrestart.conf
[main] needrestart v3.6
[main] running in root mode
[Core] Using UI 'NeedRestart::UI::stdio'...
[main] systemd detected
[ucode] using NeedRestart::uCode::Intel
[ucode] using NeedRestart::uCode::AMD
[uCode/Intel] #0 current revision: 0xa5c
+ iucode_tool --scan-system
+ grep -oE [^[:space:]]+$
+ sig=processor
+ [ -r /sys/devices/system/cpu/cpu0/microcode/processor_flags ]
+ cat /sys/devices/system/cpu/cpu0/microcode/processor_flags
+ filter=-s processor,0x0
+ test -r /etc/needrestart/iucode.sh
+ . /etc/needrestart/iucode.sh
+ type bsdtar
+ IUCODE_TOOL_EXTRA_OPTIONS=
+ test -r /etc/default/intel-microcode
+ . /etc/default/intel-microcode
+ test  = no
+ [ -r /usr/share/misc/intel-microcode* ]
+ iucode_tool -l -s processor,0x0 --ignore-broken -tb
/lib/firmware/intel-ucode
+ grep processor
Use of uninitialized value $processor in concatenation (.) or string at
/usr/share/perl5/NeedRestart/uCode.pm line 61.
[ucode] # did not get available microcode version
[uCode/AMD] #0 cpuid 0x00a50f00  (/dev/cpu/0/cpuid)
[uCode/AMD] #0 cpuid 0x00a50f00  (/proc/cpuinfo)
[uCode/AMD] #0 running ucode 0x0a5c
[uCode/AMD] cpuid 0x00100f80: found processor id 0x1080
[uCode/AMD] cpuid 0x00100f81: found processor id 0x1081
[uCode/AMD] cpuid 0x00100f62: found processor id 0x1062
[uCode/AMD] cpuid 0x00100f23: found processor id 0x1022
[uCode/AMD] cpuid 0x00100f43: found processor id 0x1043
[uCode/AMD] cpuid 0x00100f91: found processor id 0x1081
[uCode/AMD] cpuid 0x00100f2a: found processor id 0x1020
[uCode/AMD] cpuid 0x00100f63: found processor id 0x1043
[uCode/AMD] cpuid 0x00100f42: found processor id 0x1041
[uCode/AMD] cpuid 0x00300f10: found processor id 0x3010
[uCode/AMD] cpuid 0x00200f31: found processor id 0x2031
[uCode/AMD] cpuid 0x00100f52: found processor id 0x1041
[uCode/AMD] cpuid 0x00100fa0: found processor id 0x10a0
[uCode/AMD] cpuid 0x00100f53: found processor id 0x1043
[uCode/AMD] cpuid 0x00100f22: found processor id 0x1022
[uCode/AMD] cpuid 0x00500f10: found processor id 0x5010
[uCode/AMD] cpuid 0x00500f20: found processor id 0x5020
[uCode/AMD] processor id 0x1022: available ucode 0x0183
[uCode/AMD] processor id 0x1020: available ucode 0x0184
[uCode/AMD] processor id 0x1062: available ucode 0x01c7
[uCode/AMD] processor id 0x1043: available ucode 0x01c8
[uCode/AMD] processor id 0x1081: available ucode 0x01d9
[uCode/AMD] processor id 0x1080: available ucode 0x01da
[uCode/AMD] processor id 0x1041: available ucode 0x01db
[uCode/AMD] processor id 0x10a0: available ucode 0x01dc
[uCode/AMD] processor id 0x2031: available ucode 0x0232
[uCode/AMD] processor id 0x3010: available ucode 0x0327
[uCode/AMD] processor id 0x5010: available ucode 0x0529
[uCode/AMD] processor id 0x5020: available ucode 0x05000119
[uCode/AMD] cpuid 0x00600f20: found processor id 0x6020
[uCode/AMD] cpuid 0x00610f01: found processor id 0x6101
[uCode/AMD] cpuid 0x00600f12: found processor id 0x6012
[uCode/AMD] processor id 0x6012: available ucode 0x0600063e
[uCode/AMD] processor id 0x6020: available ucode 0x06000852
[uCode/AMD] processor id 0x6101: available ucode 0x06001119
[uCode/AMD] cpuid 0x00700f01: found processor id 0x7001
[uCode/AMD] processor id 0x7001: available ucode 0x0700010f
[uCode/AMD] cpuid 0x00800f82: found processor id 0x8082
[uCode/AMD] cpuid 0x00800f12: found processor id 0x8012
[uCode/AMD] cpuid 0x00830f10: found processor id 0x8310
[uCode/AMD] processor id 0x8082: available ucode 0x0800820d
[uCode/AMD] processor id 0x8012: available ucode 0x0800126e
[uCode/AMD] processor id 0x8310: available ucode 0x08301072
[uCode/AMD] cpuid 0x00a00f10: found processor id 0xa010
[uCode/AMD] cpuid 0x00a00f11: found processor id 0xa011
[uCode/AMD] cpuid 0x00a00f12: found processor id 0xa012
[uCode/AMD] processor id 0xa010: available ucode 0x0a001078
[uCode/AMD] processor id 0xa011: available ucode 0x0a0011ce
[uCode/AMD] processor id 0xa012: available ucode 0x0a001231
Use of uninitialized value $processor in concatenation (.) or string at
/usr/share/perl5/NeedRestart/uCode.pm line 61.
[ucode] # did not get available microcode version

Failed to check for processor microcode upgrades.



On Thu, 29 Oct 2020 19:30:16 +0100 Thomas Liske 
wrote:
> Hi,
>
> could you please provide the output of `needrestart -vw`?
>
>
> TIA & Regards,
> Thomas
>
>
> On 27.10.20 10:44, Martin-Éric Racine wrote:
>  > Package: needrestart
>  > Version: 3.5-1
>  > Severity: normal
>  >
> > Scanning processes...
> > Use of uninitialized value in hex at
/usr/share/perl5/NeedRestart/uCode/AMD.pm line 169.
   ]
> > Scanning processor microcode...
> > Scanning linux 

Bug#1037478: ca-certificates-java: Loop in the execution of the trigger

2023-06-13 Thread Laurent Bigonville
Package: ca-certificates-java
Version: 20230103
Severity: serious

Hello,

While updating today, I got the following error:

dpkg: boucle détectée durant le traitement des actions différées :
 listes des paquets qui en sont responsables (normalement) :
  ca-certificates-java -> ca-certificates-java
 paquets bloqués par le traitement impossible d'actions différées requises :
  ca-certificates-java: update-ca-certificates-java: /usr/lib/jvm
  libc-bin: ldconfig
  dictionaries-common: aspell-autobuildhash

There seems to be a loop in the trigger execution

Kind regards
Laurent Bigonville


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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages ca-certificates-java depends on:
ii  ca-certificates   20230311
ii  openjdk-11-jre-headless [java8-runtime-headless]  11.0.19+7-1

ca-certificates-java recommends no packages.

ca-certificates-java suggests no packages.

-- Configuration Files:
/etc/default/cacerts [Errno 13] Permission non accordée: '/etc/default/cacerts'

-- no debconf information


Bug#1037477: tracker.debian.org: package version in bookworm is displayed as "oldstable"

2023-06-13 Thread Simon McVittie
Package: tracker.debian.org
Severity: important

To reproduce:

- Choose a package that exists in all suites with various different
  versions (gnome-shell is a good example)
- rmadison gnome-shell
- visit https://tracker.debian.org/pkg/gnome-shell

Expected result:

At the time of writing, here are the gnome-shell versions:

% rmadison gnome-shell
gnome-shell | 3.30.2-11~deb10u2 | oldoldstable   | ...
gnome-shell | 3.30.2-11~deb10u2 | oldoldstable-debug | ...
gnome-shell | 3.38.6-1~deb11u1  | oldstable  | ...
gnome-shell | 3.38.6-1~deb11u1  | oldstable-debug| ...
gnome-shell | 43.4-1| stable | ...
gnome-shell | 43.4-1| testing| ...
gnome-shell | 43.6-1| buildd-unstable| ...
gnome-shell | 43.6-1| unstable   | ...
gnome-shell | 43.6-1| unstable-debug | ...
gnome-shell | 44~rc-1   | experimental   | ...
gnome-shell | 44~rc-1   | experimental-debug | ...
gnome-shell | 44.2-1| experimental   | ...
gnome-shell | 44.2-1| experimental-debug | ...

which should make tracker.d.o display this:

o-o-stable: 3.30.2-11~deb10u2
oldstable: 3.38.6-1~deb11u1 <---
stable: 43.4-1  <---
testing: 43.4-1
unstable: 43.6-1
exp: 44.2-1

Actual result:

o-o-stable: 3.30.2-11~deb10u2
oldstable: 43.4-1   <---
testing: 43.4-1
unstable: 43.6-1
exp: 44.2-1



Bug#1037264: cksum crashes intermittently with "Illegal instruction" on some Xen DomU

2023-06-13 Thread Pádraig Brady

On 13/06/2023 09:38, Axel Beckert wrote:

Hi, especially to Pádraig,




Pádraig Brady wrote:

cksum since v9.0 checks at runtime whether pclmul is supported.
It seems that check is not working appropriately on a Xen DomU.
The routine in question is pclmul_supported() at:
https://github.com/coreutils/coreutils/blob/b841f111/src/cksum.c#L160-L191

That either suggests xen is incorrectly setting PCLMUL and AVX bits,
or perhaps these two bits are not sufficient.
Hmm I wonder do we also need to explicitly check for SSSE3 support?

I.e. I wonder does cksum built with the following help?

[…]

diff --git a/src/cksum.c b/src/cksum.c
index 85afab0ac..98733dadf 100644
--- a/src/cksum.c
+++ b/src/cksum.c
@@ -172,7 +172,7 @@ pclmul_supported (void)
return false;
  }

-  if (! (ecx & bit_PCLMUL) || ! (ecx & bit_AVX))
+  if (! (ecx & bit_PCLMUL) || ! (ecx & bit_AVX) || ! (ecx & bit_SSSE3))
  {
if (cksum_debug)
  error (0, 0, "%s", _("pclmul support not detected"));


No, the patch unfortunately didn't help:


It's great you can test changes at least.
Thanks for trying the above.

At this stage it would be good to get the output from `cpuid -1`
so that hopefully we can get something there to key on
that indicates the cpu doesn't support the instructions.

thanks,
Pádraig



Bug#1036042: build-depends on libgmock-dev

2023-06-13 Thread Mathieu Malaterre
Control: tags -1 invalid wontfix

> it succeded once I installed the package libgmock-dev.

My crystal ball tells me the compilation error arises somewhere in the
*.cmake ot GTest package.

Since no debuidd machines are failing, closing as invalid.

Thanks



Bug#996466: python-is-python3: needs to Provide: python

2023-06-13 Thread Matthias Klose

Control: tags -1 + wontfix

No, the package is called python3 now, and won't change. There should be no 
dependencies on python, these should be fixed by the third parties. I'm unaware 
of any 'python' package in the deb packaging ecosystem.




Bug#1029210: smartmontools.service fails since bookworm

2023-06-13 Thread Christian Franke

Alban Browaeys wrote:

Why is smartd of type notify? Does it send notification to systemd via
sd_notify?


Yes, otherwise this would not appear in systemctl status output:

 Status: "No devices to monitor"

See 'man smartd' for details.

Unfortunately it does not properly work in conjunction with '-q nodev0' 
because 'READY=1' is not notified before 'exit(0)' then. Systemd reports 
"failed (Result: protocol)" in this case. This will be fixed in the next 
release of smartmontools.


Regards,
Christian



Bug#1037264: cksum crashes intermittently with "Illegal instruction" on some Xen DomU

2023-06-13 Thread Axel Beckert
Hi, especially to Pádraig,

I wrote:
> Control: affects -1 aptitude-robot

JFYI: The fix for /etc/cron.daily/aptitude-robot, which triggers the
issue in its non-bash compatibility mode, is to change its shebang
line from "#!/bin/sh" to "#!/bin/bash". (dpkg-reconfigure dash or bash
to switch /bin/sh to bash unfortunately no more works since Debian 12.
Cc'ing andrewsh@d.o for that comment.)

Pádraig Brady wrote:
> cksum since v9.0 checks at runtime whether pclmul is supported.
> It seems that check is not working appropriately on a Xen DomU.
> The routine in question is pclmul_supported() at:
> https://github.com/coreutils/coreutils/blob/b841f111/src/cksum.c#L160-L191
> 
> That either suggests xen is incorrectly setting PCLMUL and AVX bits,
> or perhaps these two bits are not sufficient.
> Hmm I wonder do we also need to explicitly check for SSSE3 support?
> 
> I.e. I wonder does cksum built with the following help?
[…]
> diff --git a/src/cksum.c b/src/cksum.c
> index 85afab0ac..98733dadf 100644
> --- a/src/cksum.c
> +++ b/src/cksum.c
> @@ -172,7 +172,7 @@ pclmul_supported (void)
>return false;
>  }
> 
> -  if (! (ecx & bit_PCLMUL) || ! (ecx & bit_AVX))
> +  if (! (ecx & bit_PCLMUL) || ! (ecx & bit_AVX) || ! (ecx & bit_SSSE3))
>  {
>if (cksum_debug)
>  error (0, 0, "%s", _("pclmul support not detected"));

No, the patch unfortunately didn't help:

# dpkg -l coreutils
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   VersionArchitecture Description
+++-==-==--=
ii  coreutils  9.1-1+abetest1 amd64GNU core utilities
# while :; do dd if=/dev/urandom count=1 2> /dev/null | cksum ; done
Illegal instruction
3835785655 512
1264218280 512
1265063674 512
3358845510 512
3390842004 512
658376191 512
3092360732 512
57993113 512
4257983404 512
2816803635 512
4082554882 512
1183251249 512
3097645355 512
3238771197 512
229543 512
3714227940 512
3331192910 512
1805379772 512
2540013463 512
294869588 512
222826476 512
1622837079 512
2515049677 512
3855944559 512
4031692020 512
4041321365 512
1802184575 512
2031964685 512
2781701490 512
460914961 512
Illegal instruction
3835252621 512
412678137 512
200496131 512
194185340 512
3286885624 512
Illegal instruction
2202092457 512
418097046 512
2216824095 512
3861063118 512
4214986749 512
259193791 512
2169514763 512
892443556 512
705097717 512
1758684834 512
2206099568 512
1780257589 512
82224867 512
Illegal instruction
2247709549 512
[…]

Thanks for trying to find a patch anyways.

> # while :; do dd if=/dev/urandom count=1 2> /dev/null | cksum ; done
> 1758277878 512
> 2101634611 512
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> Illegal instruction
> 2704754638 512
> Illegal instruction
> 4028135672 512
> 2625667858 512
> Illegal instruction
> Illegal instruction
> Illegal instruction

One weird thing: The "Illegal instruction" happens much more seldom
today on the second affected DomU with the patched cksum (above) as
well as with the unpatched cksum (below), not sure why. Maybe this
also gives some hint on where to look for the cause of this issue.

1829747093 512
Illegal instruction
198577731 512
428043084 512
3695864207 512
2965121539 512
1048852751 512
3278958013 512
Illegal instruction
1852035202 512
2493300527 512
2163958493 512
1863124891 512
2734183826 512
1004299335 512
3257604044 512
1233477715 512
1720570219 512
3013835401 512
3175649825 512
1828643038 512
3146557230 512
911790943 512
1016865138 512
3033781151 512
Illegal instruction
2243248050 512

The DomU on which I initially discovered the issue still hits it as
hard as before or maybe even harder now:

[…]
Illegal instruction
3963278313 512
Illegal instruction
118145379 512
211261244 512
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
1435849033 512
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction

Bug#1037476: RM: linux-ftpd -- RoQA; orphaned; contains only transitional pkg

2023-06-13 Thread Bastian Germann

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove linux-ftpd. It is orphaned and the only binary package ftpd is 
transitional since the bookworm release.



Bug#1037475: RM: netkit-tftp -- RoQA; orphaned; contains only transitional pkg

2023-06-13 Thread Bastian Germann

Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Severity: normal

Please remove netkit-tftp. It is orphaned and the only binary package tftp is 
transitional since the bookworm release.



Bug#1037185: bpftrace: Fix FTBFS on armhf

2023-06-13 Thread Danilo Egea Gondolfo

On 07/06/2023 22:09, Vincent Bernat wrote:


On 2023-06-07 12:07, Danilo Egea Gondolfo wrote:


* What led up to the situation?

The build is failing on armhf because cmake is not detecting the 
architecture correctly as we cross compile on arm64.


Also, after fixing the cmake part, the build will fail in 
src/triggers.h due to the attribute used when it build on arm 32-bit. 
It might be a bug on gcc but I'm not sure (clang++ doesn't throw the 
same error).


Shouldn't all this be fixed upstream?


Hi,

I've started a discussion here https://github.com/iovisor/bpftrace/pull/2360

It appears to be a bug in GCC. One of the developers replied with a nice 
explanation on why this code is required and suggested that building the 
entire package using the ARM ISA could be a good solution.




Bug#1037474: transition: openmm

2023-06-13 Thread Andrius Merkys

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition

Hello,

I would like to request a transition slot for openmm
(experimental -> unstable) due to soname bump. Current ben tracker [1]
is OK.

Status of reverse dependencies:

- cpptraj: not in sid
- molmodel: FTBFS with gemmi (#1037472)
- openstructure: OK
- python-pdbfixer: OK
- macromoleculebuilder: FTBFS with gemmi (#1037463)

Thanks,
Andrius

[1] https://release.debian.org/transitions/html/auto-openmm.html



Bug#1037473: ocsinventory-reports: No such file or directory in /usr/share/ocsinventory-reports/require/header.php on line 31

2023-06-13 Thread Pedro Magín
Package: ocsinventory-reports
Version: 2.8.1+dfsg1+~2.11.1-1
Severity: important
X-Debbugs-Cc: pfrago...@gmail.com

Dear Maintainer,

   * What led up to the situation?

apt install ocsinventory-server
http://server/ocsreports/ shows nothing

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

vi /etc/php/8.2/apache2/php.ini
display_errors = On
systemctl restart apache2

   * What was the outcome of this action?

http://server/ocsreports/ shows:

Warning: require_once(/usr/share/ocsinventory-reports/vendor/autoload.php): 
Failed to open stream: No such file or directory in 
/usr/share/ocsinventory-reports/require/header.php on line 31

Fatal error: Uncaught Error: Failed opening required 
'/usr/share/ocsinventory-reports/vendor/autoload.php' 
(include_path='.:/usr/share/php') in 
/usr/share/ocsinventory-reports/require/header.php:31 Stack trace: #0 
/usr/share/ocsinventory-reports/index.php(44): require() #1 {main} thrown in 
/usr/share/ocsinventory-reports/require/header.php on line 31

   * What outcome did you expect instead?

Start the application configuration
Files appear to be missing

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.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 ocsinventory-reports depends on:
ii  ieee-data   20220827.1
ii  javascript-common   11+nmu1
ii  libapache2-mod-php  2:8.2+93
ii  libapache2-mod-php8.2 [libapache2-mod-php]  8.2.5-2
ii  libjs-bootstrap 3.4.1+dfsg-3
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-datatables 1.11.5+dfsg-2
ii  libjs-jquery-file-upload10.32.0-1
ii  libjs-jquery-migrate-1  1.4.1-2
ii  libjs-jquery-ui 1.13.2+dfsg-1
ii  libjs-select2.js4.0.13+dfsg1-6
ii  libphp-phpmailer6.6.3-1
ii  mariadb-client [virtual-mysql-client]   1:10.11.3-1
ii  perl5.36.0-7
ii  php 2:8.2+93
ii  php-cas 1.6.0-1
ii  php-cli 2:8.2+93
ii  php-gd  2:8.2+93
ii  php-imap2:8.2+93
ii  php-ldap2:8.2+93
ii  php-mbstring2:8.2+93
ii  php-mysql   2:8.2+93
ii  php-pclzip  2.8.2-5
ii  php-soap2:8.2+93
ii  php-xml 2:8.2+93
ii  php-zip 2:8.2+93
ii  php8.2 [php]8.2.5-2
ii  php8.2-cli [php-cli]8.2.5-2
ii  php8.2-gd [php-gd]  8.2.5-2
ii  php8.2-imap [php-imap]  8.2.5-2
ii  php8.2-ldap [php-ldap]  8.2.5-2
ii  php8.2-mbstring [php-mbstring]  8.2.5-2
ii  php8.2-soap [php-soap]  8.2.5-2
ii  php8.2-xml [php-xml]8.2.5-2
ii  php8.2-zip [php-zip]8.2.5-2
ii  phpqrcode   1.1.4-3.1

Versions of packages ocsinventory-reports recommends:
ii  apache2 [httpd]  2.4.57-2
ii  libdbd-mysql-perl4.050-5+b1
ii  libdbi-perl  1.643-4
ii  libnet-ip-perl   1.26-3
ii  libxml-simple-perl   2.25-2
ii  nmap 7.93+dfsg1-1
ii  ocsinventory-server  2.8.1+dfsg1+~2.11.1-1
ii  samba-common 2:4.17.8+dfsg-2

ocsinventory-reports suggests no packages.

-- no debconf information



Bug#1037362: usrmerge: Can not run due to an open file handle (GLOB) that it seems is not possible to close

2023-06-13 Thread Lawrence Bayly
Spoke too soon, usrmerge broke my system worse than I could have imagined, 
/usr/bin/init went to systemd but in the old place /lib/systemd (the lib folder 
was either empty or not there, likely because of the usrmerge), fixing that 
didn't really do much as I suspect a whole bunch of other stuff was moved 
without the system really knowing where it all was. (I could have sat there 
moving stuff around or symlinking to hopefully solve the problem but in the end 
it seemed like alot of work)

So I figured it was easier to reinstall than try and figure out what went wrong 
at that point.

My suspicion is that trying to resolve that GLOB issue caused me to 
inadvertently get it so usrmerge ran (which honestly was what I wanted so I 
could get apt to work again) when it probably shouldn't have, a whole bunch of 
libraries stopped working because they couldn't be found and then I couldn't 
login to the machine anymore because bash couldn't run.



From: Marco d'Itri
Sent: Monday, June 12, 2023 12:08
To: Lawrence Bayly
Cc: 1037...@bugs.debian.org
Subject: Re: Bug#1037362: usrmerge: Can not run due to an open file handle 
(GLOB) that it seems is not possible to close

On Jun 12, Lawrence Bayly  wrote:

> root@cg-sg:/tmp/coreutils/bin# ldd /bin/cp
> not a dynamic executable
> root@cg-sg:/tmp/coreutils/bin# file /bin/cp
> /bin/cp: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically 
> linked, interpreter /lib64/ld-linux-x86-64.so.2, 
> BuildID[sha1]=e8f03b272b3dbd03cc8748cf2b52744a58d0cf5c, for GNU/Linux 3.2.0, 
> stripped
This is the correct file. Is your ldd weird then?

It should look like this:

-rwxr-xr-x 1 root root 5398 Apr 10 10:35 /usr/bin/ldd

Please also report the output of:
- dpkg -l libc-bin
- which ldd
- ldd --version

--
ciao,
Marco


Bug#1037472: molmodel: FTBFS with gemmi 0.6.2+ds-1

2023-06-13 Thread Andrius Merkys

Source: molmodel
Severity: serious
Version: 3.1.0-2

Hello,

molmodel FTBFS after recent update of gemmi to 0.6.2+ds-1:

/home/merkys/molmodel-3.1.0/src/PDBReader.cpp: In function 
'gemmi::Structure getStructureFromFile(const std::string&)':
/home/merkys/molmodel-3.1.0/src/PDBReader.cpp:98:29: error: 
'make_structure_from_block' is not a member of 'gemmi::impl'; did you 
mean 'gemmi::make_structure_from_block'?
   98 | return gemmi::impl::make_structure_from_block ( 
gemmiDoc.blocks.at(0) );

  | ^
In file included from /usr/include/gemmi/mmread.hpp:13,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/Compound.h:48,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/CompoundSystem.h:6,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/PDBReader.h:36,

 from /home/merkys/molmodel-3.1.0/src/PDBReader.cpp:33:
/usr/include/gemmi/mmcif.hpp:15:21: note: 
'gemmi::make_structure_from_block' declared here
   15 | GEMMI_DLL Structure make_structure_from_block(const cif::Block& 
block);

  | ^
make[3]: *** [CMakeFiles/SimTKmolmodel.dir/build.make:219: 
CMakeFiles/SimTKmolmodel.dir/src/PDBReader.cpp.o] Error 1

make[3]: *** Waiting for unfinished jobs
/home/merkys/molmodel-3.1.0/src/Pdb.cpp: In function 'gemmi::Structure 
gemmiStructFromDoc(const gemmi::cif::Document&)':
/home/merkys/molmodel-3.1.0/src/Pdb.cpp:39:25: error: 
'make_structure_from_block' is not a member of 'gemmi::impl'; did you 
mean 'gemmi::make_structure_from_block'?
   39 | return 
gemmi::impl::make_structure_from_block(doc.blocks.front());

  | ^
In file included from /usr/include/gemmi/mmread.hpp:13,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/Compound.h:48,
 from 
/home/merkys/molmodel-3.1.0/./include/molmodel/internal/Pdb.h:6,

 from /home/merkys/molmodel-3.1.0/src/Pdb.cpp:4:
/usr/include/gemmi/mmcif.hpp:15:21: note: 
'gemmi::make_structure_from_block' declared here
   15 | GEMMI_DLL Structure make_structure_from_block(const cif::Block& 
block);

  | ^

The issue is better fixed upstream, I will forward the report. In the 
meantime it is OK to remove molmodel from testing to not obstruct the 
upcoming openmm transition.


Andrius



Bug#1037471: easy-rsa: Import new upstream version

2023-06-13 Thread Bastian Germann

Source: easy-rsa
Version: 3.1.0-2
Severity: wishlist
X-Debbugs-Cc: lq27...@gmail.com

Please import the latest easy-rsa version, which is 3.1.5 currently.



Bug#1037469: ruby-kramdown-parser-gfm ftbfs with ruby-rouge 4.1 in experimental

2023-06-13 Thread Pirate Praveen

Package: ruby-kramdown-parser-gfm
Version: 1.1.0-2
Severity: important

I'd like to upload ruby-rouge 4.1 to unstable soon.

 1) Failure:
TestFiles#test_gfm_codeblock_fenced_to_html 
[/tmp/autopkgtest-lxc.r0kgad0i/downtmp/build.yfB/src/test/test_files.rb:32]:

--- expected
+++ actual
@@ -16,6 +16,6 @@

indent with 2 spaces

-class=\"highlight\"> class=\"nx\">console.class=\"nx\">log(class=\"dl\">\"helloclass=\"dl\">\");
+class=\"highlight\"> class=\"nx\">console.class=\"nf\">log(class=\"dl\">\"helloclass=\"dl\">\");


"


13 runs, 13 assertions, 1 failures, 0 errors, 0 skips

full log attached

autopkgtest [13:11:22]: starting date and time: 2023-06-13 13:11:22+0530
autopkgtest [13:11:22]: version 5.28
autopkgtest [13:11:22]: host mahishi; command line: /usr/bin/autopkgtest --user debci --apt-upgrade --log-file=/tmp/ruby-rouge_4.1.0-1_amd64.UF50hEJjZw/autopkgtest/ruby-kramdown-parser-gfm.log /home/pravi/forge/ruby-team/build-area/ruby-rouge_4.1.0-1_all.deb ruby-kramdown-parser-gfm -- lxc --sudo autopkgtest-unstable-amd64
autopkgtest [13:11:39]:  test bed setup
Get:1 http://deb.debian.org/debian unstable InRelease [199 kB]
Get:2 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB]
Get:3 http://deb.debian.org/debian unstable/contrib Sources.diff/Index [63.3 kB]
Get:4 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [63.3 kB]
Get:5 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:6 http://deb.debian.org/debian unstable/non-free amd64 Packages.diff/Index [63.3 kB]
Get:7 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index [63.3 kB]
Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:9 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [53.7 kB]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:11 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:10 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:12 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:15 http://deb.debian.org/debian-debug unstable-debug/main Sources.diff/Index [63.6 kB]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:16 http://deb.debian.org/debian-debug unstable-debug/contrib Sources.diff/Index [63.3 kB]
Get:17 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages.diff/Index [63.6 kB]
Get:18 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages.diff/Index [63.3 kB]
Get:19 http://incoming.debian.org/debian-buildd buildd-unstable/non-free Sources [1,228 B]
Get:20 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:21 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:22 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:23 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Get:20 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:21 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:22 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:23 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Get:24 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [6,695 B]
Get:25 http://incoming.debian.org/debian-buildd buildd-unstable/main Sources [277 kB]
Get:26 http://incoming.debian.org/debian-buildd buildd-unstable/contrib Sources [3,100 B]
Get:27 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages [377 kB]
Get:28 http://incoming.debian.org/debian-buildd 

Bug#1037468: nvidia-driver: RmInitAdapter failed! (0x25:0x65:1457)

2023-06-13 Thread Allan Wind
Package: nvidia-driver
Version: 525.105.17-1
Severity: important

Dear Maintainer,

The upgrade to 12 was smooth except the nvidia-driver did not load 
after rebooting on my Lenovo P51 with:

01:00.0 VGA compatible controller: NVIDIA Corporation GM206GLM [Quadro M2200 
Mobile] (rev a1)

I get a few dmesg then a blank screen with a cursor.  Not able
to change to a virtual terminal. I also also tried the version in 
experimental with similar effect:

Version: 525.105.17-1

2023-06-12T06:14:43.764+00:00 vent kernel: NVRM: GPU :01:00.0: 
RmInitAdapter failed! (0x25:0x65:1457)
2023-06-12T06:14:43.764+00:00 vent kernel: NVRM: GPU :01:00.0: 
rm_init_adapter failed, device minor number 0
2023-06-12T06:14:43.764+00:00 vent systemd[1]: lightdm.service: Failed with 
result 'exit-code'.

Version: 530.41.03-1

2023-06-13T02:02:39.056+00:00 vent kernel: NVRM: GPU :01:00.0: 
RmInitAdapter failed! (0x25:0x65:1462)
2023-06-13T02:02:39.056+00:00 vent kernel: NVRM: GPU :01:00.0: 
rm_init_adapter failed, device minor number 0
2023-06-13T02:02:39.056+00:00 vent systemd[1]: lightdm.service: Failed with 
result 'exit-code'.

I do have non-free-firmware enabled and hence the nvidia firmware.  
Upgraded bios to latest version  No difference if I use 
linux-image 6.1.0-9-amd64 or 5.10.0-23-amd64.

The only semi-workaround is to uninstall the nvidia driver and 
rely on nouveau.  Surprisingly to me, nouveau, doesn't seem to 
require the xserver-xorg-video-nouveau package to be installed(?).

Reported upstream as requested:

https://forums.developer.nvidia.com/t/rminitadapter-failed-0x251457/256445

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_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 nvidia-driver depends on:
pn  nvidia-alternative   
pn  nvidia-driver-bin
pn  nvidia-driver-libs   
pn  nvidia-installer-cleanup 
pn  nvidia-kernel-dkms | nvidia-kernel-525.105.17 | nvidia-open-kernel-  
525.105.17 | nvidia-open-kernel-525.105.17
pn  nvidia-legacy-check  
pn  nvidia-support   
pn  nvidia-vdpau-driver  
pn  xserver-xorg-video-nvidia

Versions of packages nvidia-driver recommends:
pn  libnvidia-cfg1   
pn  nvidia-persistenced  
pn  nvidia-settings  

Versions of packages nvidia-driver suggests:
pn  nvidia-kernel-dkms | nvidia-kernel-source | nvidia-open-kernel-sour  
ce | nvidia-open-kernel-source



Bug#1037113: Should not be in /usr/games

2023-06-13 Thread Josh Triplett
On Mon, Jun 12, 2023 at 05:03:01PM -0500, Dirk Eddelbuettel wrote:
> 
> reassign 1037113 screen-message
> thanks
> 
> Binary package 'sm' is from source package 'screen-message'
> 
> Binary package 'r-cran-sm' is from source package 'sm', which I maintain, and
> something totally different :-)   Not the first crossed bug report so no
> worries, the reassign should work.

Sorry about that, and thank you.



Bug#1037343: Acknowledgement (vlc produce error: Codec `h264' (H264 - MPEG-4 AVC (part 10)) is not supported.)

2023-06-13 Thread Александр Коновалов
really, a have cusom  libva in /usr/local installed with make install

after removing and reinstall libva2 vlc  run successful

thank's. it's not a bug

вс, 11 июн. 2023 г. в 22:27, Debian Bug Tracking System <
ow...@bugs.debian.org>:

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


Bug#1037467: ruby-gollum-lib not compatible with ruby-rouge 4.1

2023-06-13 Thread Pirate Praveen

Package: ruby-gollum-lib
Version: 4.2.7.10~gitlab.2+dfsg-1
Severity: important

/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': 
Could not find 'rouge' (~> 3.1) - did find: [rouge-4.1.0]


full log attached. I'd like to reupload ruby-rouge 4.1 to unstable soon.

autopkgtest [13:01:15]: starting date and time: 2023-06-13 13:01:15+0530
autopkgtest [13:01:15]: version 5.28
autopkgtest [13:01:15]: host mahishi; command line: /usr/bin/autopkgtest --user debci --apt-upgrade --log-file=/tmp/ruby-rouge_4.1.0-1_amd64.UF50hEJjZw/autopkgtest/ruby-gollum-lib.log /home/pravi/forge/ruby-team/build-area/ruby-rouge_4.1.0-1_all.deb ruby-gollum-lib -- lxc --sudo autopkgtest-unstable-amd64
autopkgtest [13:01:54]:  test bed setup
Get:1 http://deb.debian.org/debian unstable InRelease [199 kB]
Get:2 http://incoming.debian.org/debian-buildd buildd-unstable InRelease [53.7 kB]
Get:3 http://deb.debian.org/debian-debug unstable-debug InRelease [56.7 kB]
Get:4 http://incoming.debian.org/debian-buildd buildd-unstable/contrib Sources [3,100 B]
Get:5 http://incoming.debian.org/debian-buildd buildd-unstable/non-free Sources [1,228 B]
Get:6 http://incoming.debian.org/debian-buildd buildd-unstable/main Sources [277 kB]
Get:7 http://incoming.debian.org/debian-buildd buildd-unstable/non-free amd64 Packages [1,040 B]
Get:8 http://incoming.debian.org/debian-buildd buildd-unstable/contrib amd64 Packages [7,448 B]
Get:9 http://incoming.debian.org/debian-buildd buildd-unstable/main amd64 Packages [377 kB]
Get:10 http://deb.debian.org/debian unstable/non-free Sources.diff/Index [63.3 kB]
Get:11 http://deb.debian.org/debian unstable/contrib Sources.diff/Index [63.3 kB]
Get:12 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:13 http://deb.debian.org/debian unstable/non-free amd64 Packages.diff/Index [63.3 kB]
Get:14 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index [63.3 kB]
Get:15 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB]
Get:16 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:17 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:18 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:19 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:20 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:16 http://deb.debian.org/debian unstable/non-free Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [752 B]
Get:20 http://deb.debian.org/debian unstable/contrib amd64 Packages T-2023-06-12-2020.02-F-2023-06-12-1422.14.pdiff [2,664 B]
Get:19 http://deb.debian.org/debian unstable/non-free amd64 Packages T-2023-06-13-0242.35-F-2023-06-13-0242.35.pdiff [326 B]
Get:18 http://deb.debian.org/debian unstable/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [124 kB]
Get:17 http://deb.debian.org/debian unstable/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [1,388 B]
Get:21 http://deb.debian.org/debian-debug unstable-debug/contrib Sources.diff/Index [63.3 kB]
Get:22 http://deb.debian.org/debian-debug unstable-debug/main Sources.diff/Index [63.6 kB]
Get:23 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages.diff/Index [63.6 kB]
Get:24 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages.diff/Index [63.3 kB]
Get:25 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:26 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:27 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:28 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Get:25 http://deb.debian.org/debian unstable/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [158 kB]
Get:26 http://deb.debian.org/debian-debug unstable-debug/contrib Sources T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [968 B]
Get:27 http://deb.debian.org/debian-debug unstable-debug/main Sources T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [73.0 kB]
Get:29 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [6,695 B]
Get:29 http://deb.debian.org/debian-debug unstable-debug/contrib amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-2020.02.pdiff [6,695 B]
Get:28 http://deb.debian.org/debian-debug unstable-debug/main amd64 Packages T-2023-06-13-0242.35-F-2023-06-12-1422.14.pdiff [80.9 kB]
Fetched 2,059 kB in 21s (98.3 kB/s)
Reading package lists...

Bug#1000072: libapache2-mod-qos: depends on obsolete pcre3 library

2023-06-13 Thread Matthieu Schapranow
Hi all,

Currently, libapache2-mod-qos is still at 11.63 in stable and unstable although 
the latest release version is 11.74 from early May 2023 available at SF.net. I 
hope that our great packet maintainer Sergey finds some time to build an 
updated version, because many users depend on a working version of mod_qos as 
part of bookworm.

Thanks in advance for your efforts!

Matthieu
  

On Tue, 16 May 2023 09:07:51 +0200 Stefan Baier  wrote:
> Package: libapache2-mod-qos
> Version: 11.63-1+b2
> Followup-For: Bug #172
> X-Debbugs-Cc: tech...@planet-ic.de
> 
> Apache mod_qos is in default bookworm sources still not useable 
> out-of-the-box.
> If module is loaded, the daemon is not able to start and throws an error 
> depending
> the mod_qos library:
> "[…] mod_qos.so: undefined symbol: pcre_free […]"
> 
> Purging the old pcre version is not possible, due to the dependency to 
> libapache2-mod-qos.
> 
> 
> -- System Information:
> Debian Release: 12.0
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 6.1.0-7-amd64 (SMP w/2 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 libapache2-mod-qos depends on:
> ii  apache2-bin [apache2-api-20120211]  2.4.57-2
> ii  libapr1 1.7.2-3
> ii  libaprutil1 1.6.3-1
> ii  libc6   2.36-9
> ii  libpcre32:8.39-15
> ii  libpng16-16 1.6.39-2
> ii  libssl3 3.0.8-1
> ii  zlib1g  1:1.2.13.dfsg-1
> 
> libapache2-mod-qos recommends no packages.
> 
> libapache2-mod-qos suggests no packages.
> 
> -- no debconf information


Bug#1037466: nmu: spirv-llvm-translator-16_16.0.0-1

2023-06-13 Thread Andreas Beckmann
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

nmu spirv-llvm-translator-16_16.0.0-1 . ANY . experimental . -m "Rebuild 
against llvm 16.0.5"

the updated llvm-16/gcc-13 combination causes symbol changes that I'd
like to collect before uploading the package to unstable

Andreas



Bug#1036899: logiops: logid does not work for MX Master 3

2023-06-13 Thread Mikołaj Kuranowski

Hello, unfortunately for me both 0.3.1-2 and 0.3.2-1 still don't work.
I'm experiencing the same issue (thumb button remapping not working); 
0.2.4 built from the source works fine.


On Tue, 06 Jun 2023 14:24:30 +0200 Hendrik Tews 
 wrote:

Hi,

On 2023-06-05 10:22:35, Chow Loong Jin  wrote:

> Could you check if 0.3.1-1 (in unstable) or 0.3.2-1 (in experimental) is
> working for you?

thanks for following up. Both 0.3.1-2 from unstable and 0.3.2-1 from
experimental work. (Unexpected to me, because I reproduced the problem
with the newest upstream version.)

Version 0.3.1-1 is the version from testing, this version does not
work.

Hendrik










Bug#1037463: macromoleculebuilder: FTBFS with gemmi 0.6.2+ds-1

2023-06-13 Thread Andrius Merkys

Source: macromoleculebuilder
Severity: serious
Version: 4.0.0+dfsg-2

Hello,

macromoleculebuilder FTBFS after recent update of gemmi to 0.6.2+ds-1:

/home/merkys/macromoleculebuilder-4.0.0+dfsg/src/CifOutput.cpp: In 
function 'void SimTK::CIFOut::reWriteOutCif(const gemmi::Model&, const 
std::string&, const std::string&, ParameterReader&, const 
SimTK::CompoundSystem&, bool)':
/home/merkys/macromoleculebuilder-4.0.0+dfsg/src/CifOutput.cpp:113:81: 
error: cannot bind rvalue reference of type 'gemmi::cif::Document&&' to 
lvalue of type 'gemmi::cif::Document'
  113 | gemmi::Structure myTrajectoryOutputFile   = 
gemmi::make_structure ( doc );
  | 
^~~


The issue is better fixed upstream, I will forward the report. In the 
meantime it is OK to remove macromoleculebuilder from testing to not 
obstruct the upcoming openmm transition.


Andrius



Bug#1037462: perltidy: please package upstream v20230309

2023-06-13 Thread Jonas Smedegaard
Package: perltidy
Version: 20220613-1
Severity: wishlist
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

Please consider packaging upstream release v20230309.

It is recommended for use with new upstream release of perltidier,
which adopts my patches to support Object::Pad - which I am relying on
for my perl hacking, and would love to have in Debian with official
upstream support.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSIFd8ACgkQLHwxRsGg
ASG7Sw/+JqbinbNFjNp4ElXGtzHnwYUvLF6REZ30j1Ugv0LaWZCKwup+jes5uypf
s0s9gp0ur8R0QGoOLlerQl291jSRELv5UuE9RgPXZEfZ23r9CzNYxx40EgRN2TR9
/hkup1tJNdnxoA1U79JMXT22zkn96NOOPqKpxt7RdAgvft+D3rOMNGF9U8uaDTyx
JoIUMhjrBf7WQQeSHRMWw4sOy5ErelDpTLcuGyL+rggnGOZTauOxoeGvs/hqsOmG
m+5rNOpfH5Gkxy20LtGkqGDNEZWDIdv73MdlEtdBQGkSGzzAZii8NrmoDpjKVAcF
H0ckkBgCKGVmAVJimBEgkn/S6wKotzODuIn8N73/IIO0l8cC+6GG3bGNYPMRO0n0
/6xPp4vx6iciFynWx+4eiESw5bvjzDGXSEV+ExN6LN0fYNz8Kq5GOvHeamdv5LQJ
D5ih3Z+z+eW/mzbTMLQej6UOUSe+kN7cdTGjXvOiesf/35rHW/MrQPOllu9M/2gp
mxd05+7pWAjSncBsZhnHOuuVcujhV8a/Rt9O93Lgc8UdhbrM7D0RocRPhQY2PyLx
pxWWj0fFiOkt2o90831dB7KythFJjk50/4W7tuFDmsS8NT7zeUTWCcM7NYViyu1r
DX0IYdtU8aZwonqaMWH4HddGrKqUefa3wys23aQqvZcRAY19xC4=
=OjeK
-END PGP SIGNATURE-



Bug#1037461: bookworm-pu: package ayatana-indicator-datetime/22.9.1-1+deb12u1

2023-06-13 Thread Mike Gabriel
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
In Lomiri's clock app, it is possible to configure alarms with
custom alarm sounds. ayatana-indicator-datetime is responsible
for playing those alarm sounds when the time comes.

However, ayatana-indicator-datetime only plays the system-wide
default alarm sound.

[ Impact ]
Limited to Lomiri users, configuring custom alarm sounds will
work with this changeset.

[ Tests ]
Manually, on a bookworm system running Lomiri.

[ Risks ]
Virtually none.

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

[ Changes ]

+  * debian/patches:
++ Add 0001_engine-eds-fix-retrieving-custom-alarm-sound-path.patch. Fix
+  playing of custom alarm sounds. (Closes: #1037330).

-> a patch from upstream (contributed by Ubuntu Touch developers) will be
cherry-picked into bookworm's version of ayatana-indicator-datetime.

[ Other info ]
None.
diff -Nru ayatana-indicator-datetime-22.9.1/debian/changelog 
ayatana-indicator-datetime-22.9.1/debian/changelog
--- ayatana-indicator-datetime-22.9.1/debian/changelog  2022-11-23 
17:06:05.0 +0100
+++ ayatana-indicator-datetime-22.9.1/debian/changelog  2023-06-11 
17:54:33.0 +0200
@@ -1,3 +1,11 @@
+ayatana-indicator-datetime (22.9.1-1+deb12u1) bookworm; urgency=medium
+
+  * debian/patches:
++ Add 0001_engine-eds-fix-retrieving-custom-alarm-sound-path.patch. Fix
+  playing of custom alarm sounds. (Closes: #1037330).
+
+ -- Mike Gabriel   Sun, 11 Jun 2023 17:54:33 +0200
+
 ayatana-indicator-datetime (22.9.1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru 
ayatana-indicator-datetime-22.9.1/debian/patches/0001_engine-eds-fix-retrieving-custom-alarm-sound-path.patch
 
ayatana-indicator-datetime-22.9.1/debian/patches/0001_engine-eds-fix-retrieving-custom-alarm-sound-path.patch
--- 
ayatana-indicator-datetime-22.9.1/debian/patches/0001_engine-eds-fix-retrieving-custom-alarm-sound-path.patch
   1970-01-01 01:00:00.0 +0100
+++ 
ayatana-indicator-datetime-22.9.1/debian/patches/0001_engine-eds-fix-retrieving-custom-alarm-sound-path.patch
   2023-06-11 17:53:40.0 +0200
@@ -0,0 +1,203 @@
+From e089a84b306ef09667752b910d87538043140042 Mon Sep 17 00:00:00 2001
+From: Ratchanan Srirattanamet 
+Date: Tue, 6 Jun 2023 15:54:11 +0700
+Subject: [PATCH] engine-eds: fix retrieving custom alarm sound path
+
+ECal 2.0 returns the list of attachments as a GSList (a singly linked
+list). I'm not sure why, but the logic for iterating the list is
+completely incorrect. Fixing that fixes custom alarm sound.
+
+A test is added to catch this case.
+
+Bug-UBports: 
https://gitlab.com/ubports/development/apps/lomiri-clock-app/-/issues/183
+Signed-off-by: Mike Gabriel 
+---
+ src/engine-eds.cpp   | 13 ++-
+ tests/CMakeLists.txt |  1 +
+ tests/test-eds-ics-alarm-custom-sound.cpp| 92 
+ tests/test-eds-ics-alarm-custom-sound.ics.in | 32 +++
+ 4 files changed, 131 insertions(+), 7 deletions(-)
+ create mode 100644 tests/test-eds-ics-alarm-custom-sound.cpp
+ create mode 100644 tests/test-eds-ics-alarm-custom-sound.ics.in
+
+diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp
+index b7f4682..2748fc1 100644
+--- a/src/engine-eds.cpp
 b/src/engine-eds.cpp
+@@ -635,19 +635,18 @@ private:
+ auto action = e_cal_component_alarm_get_action(alarm);
+ if (action == E_CAL_COMPONENT_ALARM_AUDIO)
+ {
+-ICalAttach *attach = nullptr;
+ auto attachments = e_cal_component_alarm_get_attachments(alarm);
+ 
+-if (attachments != nullptr && attachments->next != nullptr)
+-attach = I_CAL_ATTACH (attachments->data);
++for (; attachments != nullptr; attachments = attachments->next) {
++ICalAttach *attach = I_CAL_ATTACH (attachments->data);
+ 
+-if (attach != nullptr)
+-{
+-if (i_cal_attach_get_is_url (attach))
++if (attach != nullptr && i_cal_attach_get_is_url (attach))
+ {
+ const char* url = i_cal_attach_get_url(attach);
+-if (url != nullptr)
++if (url != nullptr) {
+ ret = url;
++break;
++}
+ }
+ }
+ if (ret.empty())
+diff --git a/tests/CMakeLists.txt b/tests/CMakeLists.txt
+index 4b9b1d7..81eeb5d 100644
+--- a/tests/CMakeLists.txt
 b/tests/CMakeLists.txt
+@@ -108,6 +108,7 @@ add_eds_ics_test_by_name(test-eds-ics-tzids-2)
+ add_eds_ics_test_by_name(test-eds-ics-tzids-utc)
+ add_eds_ics_test_by_name(test-eds-ics-non-attending-alarms)
+ 

Bug#1036428: libapache2-mod-apreq2: the package is missing from testing release and from i386 architecture

2023-06-13 Thread Sebastiaan Couwenberg

On Sat, 20 May 2023 19:25:41 +0200 Rafal Pietrak wrote:

I've experieced problem after upgrading old (i386) machine to Debian-12
I've upgraded it from Debian-10, through Debian-11 (without testing this

The package got removed from bookworm due to #1027355.

libapreq2 (2.17-3) should migrate to testing in a few days.

Once it's back in testing, it will be rebuilt for bookworm-backports.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1



Bug#1037460: RM: icingaweb2-module-ipl -- RoM; obsoleted by icinga-php-library

2023-06-13 Thread Kunz David


Package: ftp.debian.org
Severity: normal

Icingaweb2-module-ipl is removed from unstable.
This should also be removed from experimental.


Greetings,
David



Bug#1037459: ITP: miopen -- ROCm library for machine learning primitives

2023-06-13 Thread Cordell Bloor
Package: wnpp
Severity: wishlist
Owner: Cordell Bloor 
X-Debbugs-Cc: debian-de...@lists.debian.org, c...@slerp.xyz, 
debian...@lists.debian.org

* Package name: miopen
  Version : 5.5.0
  Upstream Author : Advanced Micro Devices, Inc.
* URL : https://github.com/ROCmSoftwarePlatform/MIOpen
* License : Expat
  Programming Lang: C++, HIP
  Description : ROCm library for machine learning primitives

 MIOpen is a library for machine learning on AMD GPUs. It provides
 high-performance primitives for a number of operations, including
 convolutions, batch normalization, pooling layers, and softmax layers
 for Recurrent Neural Networks. HIP and OpenCL are both supported as
 programming models.

MIOpen is a key library for machine learning on AMD GPU hardware and is
a dependency of both PyTorch and Tensorflow. It is an open-source
alternative to nvidia-cudnn.

This package is part of AMD's ROCm stack and will be maintained under the
Debian AI team umbrella.



<    1   2