Bug#1040836: udisks2: new udisks (auto-)mounts/unmounts fs?

[Michael Biebl]

To me this looks like a BTRFS specific issue (and I don't use BTRFS).

I still don't see any mounts in the log, just some probing / scanning of 
the BTRFS devices.
Where exactly is the device mounted to / can you actually write to the 
device? You mentioned it's mounted rw.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1040943: systemd-logind: 'HandlePowerKey=ignore' works in logind.conf, not in logind.conf.d/custom.conf

[Michael Biebl]

Am 17.07.23 um 01:58 schrieb Diederik de Haas:

On Monday, 17 July 2023 01:24:43 CEST Michael Biebl wrote:

The journald output shows long and short key presses (with logind
reacting accordingly)

jul 15 09:17:08 pinetab2 systemd-logind[1742]: Power key pressed short.
jul 15 09:17:08 pinetab2 systemd-logind[1742]: Suspending...

jul 15 09:18:42 pinetab2 systemd-logind[1850]: Power key pressed long.
jul 15 09:18:42 pinetab2 systemd-logind[1850]: Powering off...

That looks all as expected and I don't understand the problem this is
supposed to show.


The problem is that in all cases I pressed the power key equally short.


Ok, so it does not look like a configuration issue i.e.
HandlePowerKeyLongPress=shutdown' is *not* interpreted as short.

It's rather that the detection and distinction of long and short key 
presses doesn't work reliably.


Might be a hardware limitation / hardware related bug.

In any case, since Debian doesn't ship any patches in that regard, 
please file this issue upstream at 
https://github.com/systemd/systemd/issues and report back with the issue 
number.


Thanks




OpenPGP_signature
Description: OpenPGP digital signature

Bug#1040947: perl: readline fails to detect updated file

[Niko Tyni]

On Sun, Jul 16, 2023 at 11:35:49AM +0300, Niko Tyni wrote:
> Control: forwarded -1 https://github.com/Perl/perl5/issues/21240
> 
> On Wed, Jul 12, 2023 at 09:17:54PM +, Eric Wong wrote:
> > Package: perl
> > Version: 5.36.0-7
> > Severity: normal
> > Tags: upstream
> > 
> > Dear Maintainer,
> > 
> > The `readline' op (`') no longer detects updates to file
> > which is being written to in Perl 5.36.0 after updating to bookworm.
> > 
> > The attached script worked fine with Perl 5.32.1 in oldstable,
> > both scripts show the size changing with the `-s FH' op.
> > Same behavior on both amd64 and i386.
> 
> Thanks for the report.
> 
> This changed with
> 
>   
> https://github.com/Perl/perl5/commit/80c1f1e45e8ef8c27d170fae7ade41971fe20218
> 
> which went upstream in 5.37.4. We backported it for 5.36 to fix #1016369 .
> 
> I've forwarded it upstream as https://github.com/Perl/perl5/issues/21240

Upstream says it's a direct consequence of fixing #1016369 so
the earlier behaviour of reading after EOF was a bug.

You need to clear the EOF flag by calling $rd->clearerr() or
seek($rd, 0, SEEK_CUR) to get the appended lines.

-- 
Niko Tyni   nt...@debian.org

Bug#1041300: qt6-base-dev: undeclared file conflict with libqt6opengl6-dev

[Helmut Grohne]

Package: qt6-base-dev
Version: 6.4.2+dfsg-12
Severity: serious

The recent upload makes qt6-base-dev include a fair number of files also
contained in libqt6opengl6-dev. Is this some kind of packaging mistake?

Helmut

Bug#1041299: rawloader: multiple undeclared file conflicts

[Helmut Grohne]

Package: rawloader
Version: 0.37.1-1
Severity: serious

rawloader contains multiple undeclared file conflicts

usr/bin/identify is contained in graphicsmagick-imagemagick-compat.
usr/bin/benchmark is contained in libplucene-perl.

In general, these names are fairly generic. I recommend renaming them
rather than expressing these conflicts. Also adding manual pages would
be good.

Helmut

Bug#1041298: debdelta doesn't work as advertised.

[shirish शिरीष]

Package: debdelta
Version: 0.67
Severity: important

Dear Maintainer,
Sharing a session so the problem will be easy to know -

$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  fonts-liberation fonts-liberation2 libgeos-c1v5
The following packages will be upgraded:
  curl libc-l10n libcjson1 libcurl3-gnutls libcurl3-nss libcurl4
libcurl4-openssl-dev libpcre2-16-0 libpcre2-32-0 libpcre2-8-0
libpcre2-dev
  libpcre2-posix3 libplexus-compiler-java libpython3.10
libpython3.10-dev libpython3.10-minimal libpython3.10-stdlib
libwine-development
  libxnvctrl0 libyajl2 openjdk-17-dbg openjdk-17-demo openjdk-17-doc
openjdk-17-jdk openjdk-17-jdk-headless openjdk-17-jre
  openjdk-17-jre-headless python3-nbformat python3-tifffile
python3-zeroconf python3.10 python3.10-dev python3.10-minimal
33 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 483 MB/497 MB of archives.

$ sudo debdelta-upgrade
Delta is not yet ready in the server:
fonts-liberation_1%3a1.07.4-11_1%3a2.1.5-3_all.debdelta
Delta was not created since new package is too small:
fonts-liberation2_2.1.5-1_1%3a2.1.5-3_all.debdelta
Delta is too big: libgeos-c1v5_3.11.1-1_3.12.0-1_amd64.debdelta
Delta is too big:
libplexus-compiler-java_2.12.1-1_2.12.1-2_all.debdelta
Created,time  0.60sec, speed 89kB/sec,
libpcre2-posix3_10.42-2_amd64.deb
Delta is not yet ready in the server:
libwine-development_8.1~repack-1_8.3~repack-1_amd64.debdelta
Created,time  0.31sec, speed 42kB/sec,
libxnvctrl0_525.85.05-3_amd64.deb
Created,time  0.27sec, speed 82kB/sec, libyajl2_2.1.0-5_amd64.deb
Delta is too big: openjdk-17-dbg_17.0.8~6-3_17.0.8~6-5_amd64.debdelta
Downloaded, time  0.25sec, speed 6527B/sec,
openjdk-17-jre_17.0.8~6-3_17.0.8~6-5_amd64.debdelta
Created,time  0.76sec, speed 230kB/sec,
python3-tifffile_20230710-1_all.deb
Downloaded, time  0.26sec, speed 18kB/sec,
libcjson1_1.7.15-1_1.7.16-1_amd64.debdelta
Downloaded, time  0.27sec, speed 19kB/sec,
python3-nbformat_5.5.0-1_5.9.1-1_all.debdelta
Created,time  0.40sec, speed 175kB/sec,
python3-zeroconf_0.71.0-1_all.deb
Downloaded, time  0.34sec, speed 51kB/sec,
openjdk-17-demo_17.0.8~6-3_17.0.8~6-5_amd64.debdelta
Created,time  0.49sec, speed 366kB/sec,
openjdk-17-jre_17.0.8%7e6-5_amd64.deb
Created,time  0.16sec, speed 136kB/sec,
libcjson1_1.7.16-1_amd64.deb
Downloaded, time  0.39sec, speed 63kB/sec,
libpcre2-32-0_10.42-1_10.42-2_amd64.debdelta
Downloaded, time  0.40sec, speed 75kB/sec,
libpcre2-8-0_10.42-1_10.42-2_amd64.debdelta
Created,time  0.47sec, speed 94kB/sec,
python3-nbformat_5.9.1-1_all.deb
Downloaded, time  0.37sec, speed 83kB/sec,
libpcre2-16-0_10.42-1_10.42-2_amd64.debdelta
Downloaded, time  0.57sec, speed 148kB/sec,
libpcre2-dev_10.42-1_10.42-2_amd64.debdelta
Downloaded, time  0.98sec, speed 672kB/sec,
openjdk-17-jdk_17.0.8~6-3_17.0.8~6-5_amd64.debdelta
Downloaded, time  0.54sec, speed 1761kB/sec,
openjdk-17-doc_17.0.8~6-3_17.0.8~6-5_all.debdelta
Created,time  2.49sec, speed 1614kB/sec,
openjdk-17-demo_17.0.8%7e6-5_amd64.deb
Created,time  0.45sec, speed 501kB/sec,
libpcre2-32-0_10.42-2_amd64.deb
Downloaded, time  0.53sec, speed 3273kB/sec,
openjdk-17-jre-headless_17.0.8~6-3_17.0.8~6-5_amd64.debdelta
Created,time  0.28sec, speed 915kB/sec,
libpcre2-8-0_10.42-2_amd64.deb
Created,time  0.29sec, speed 836kB/sec,
libpcre2-16-0_10.42-2_amd64.deb
Created,time  1.40sec, speed 525kB/sec,
libpcre2-dev_10.42-2_amd64.deb
Downloaded, time  2.42sec, speed 6316kB/sec,
openjdk-17-jdk-headless_17.0.8~6-3_17.0.8~6-5_amd64.debdelta
Downloaded, time  0.38sec, speed 253kB/sec,
libplexus-compiler-java_2.12.1-2_all.deb
Downloaded, time  0.02sec, speed 3923kB/sec,
libgeos-c1v5_3.12.0-1_amd64.deb
Downloaded, time  0.02sec, speed 249kB/sec,
fonts-liberation2_2.1.5-3_all.deb
Downloaded, time  0.15sec, speed  9MB/sec,
fonts-liberation_2.1.5-3_all.deb
Created,time  3.52sec, speed 1195kB/sec,
openjdk-17-jdk_17.0.8%7e6-5_amd64.deb
Created,time 65.79sec, speed 191kB/sec,
openjdk-17-doc_17.0.8%7e6-5_all.deb
Created,time 40.12sec, speed 1065kB/sec,
openjdk-17-jre-headless_17.0.8%7e6-5_amd64.deb
Created,time 19.77sec, speed 3522kB/sec,
openjdk-17-jdk-headless_17.0.8%7e6-5_amd64.deb
Delta-upgrade statistics:
 total resulting debs, size 133MB time 147sec virtual speed 930kB/sec

$ sudo aptitude installibcjson1 libpcre2-16-0 libpcre2-32-0
libpcre2-8-0 libpcre2-dev libpcre2-posix3 libplexus-compiler-java
libwine-development libxnvctrl0 libyajl2 openjdk-17-dbg
openjdk-17-demo openjdk-17-doc openjdk-17-jdk openjdk-17-jdk-headless
openjdk-17-jre openjdk-17-jre-headless python3-nbformat
python3-tifffile python3-zeroconf fonts-liberation fonts-liberation2
libgeos-c1v5 5
The following NEW packages will be installed:
  fonts-liberation-sans-narrow{a} libgeos3.12.0{a}
The following packages will be REMOVED:
  libgeos3.11.1{u}
The 

Bug#870143: Expressing interest in packaging Citra

[Ben Westover]

Hello,

I may be interested in packaging this when they start doing actual 
releases instead of just having nightly builds.

--
Ben Westover


OpenPGP_signature
Description: PGP signature

Bug#1041297: geojson-pydantic: autopkgtest failure with GEOS 3.12

[Bas Couwenberg]

Source: geojson-pydantic
Version: 0.5.0-2
Severity: serious
Tags: upstream
Justification: autopkgtest failure

Dear Maintainer,

The autopkgtest of your package fails with GEOS 3.12:

 33s === FAILURES 
===
 33s ___ test_multi_point_valid_coordinates[coordinates0] 
___
 33s 
 33s coordinates = [(1.0, 2.0)]
 33s 
 33s @pytest.mark.parametrize(
 33s "coordinates",
 33s [
 33s [(1.0, 2.0)],
 33s [(1.0, 2.0), (1.0, 2.0)],
 33s [(1.0, 2.0, 3.0), (1.0, 2.0, 3.0)],
 33s [(1.0, 2.0), (1.0, 2.0)],
 33s ],
 33s )
 33s def test_multi_point_valid_coordinates(coordinates):
 33s """
 33s Two or three number elements as coordinates shold be okay
 33s """
 33s p = MultiPoint(coordinates=coordinates)
 33s assert p.type == "MultiPoint"
 33s assert p.coordinates == coordinates
 33s assert hasattr(p, "__geo_interface__")
 33s >   assert_wkt_equivalence(p)
 33s 
 33s tests/test_geometries.py:68: 
 33s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ 
 33s 
 33s geom = MultiPoint(type='MultiPoint', coordinates=[(1.0, 2.0)])
 33s 
 33s def assert_wkt_equivalence(geom: Union[Geometry, GeometryCollection]):
 33s """Assert WKT equivalence with Shapely."""
 33s # Remove any trailing `.0` to match Shapely format
 33s clean_wkt = re.sub(r"\.0(\D)", r"\1", geom.wkt)
 33s >   assert shape(geom.dict()).wkt == clean_wkt
 33s E   AssertionError: assert 'MULTIPOINT ((1 2))' == 'MULTIPOINT (1 2)'
 33s E - MULTIPOINT (1 2)
 33s E + MULTIPOINT ((1 2))
 33s E ?+ +
 33s 
 33s tests/test_geometries.py:25: AssertionError
 33s === short test summary info 

 33s FAILED 
tests/test_geometries.py::test_multi_point_valid_coordinates[coordinates0]
 33s !! stopping after 1 failures 
!!!
 33s = 1 failed, 21 passed in 0.30s 
=

https://ci.debian.net/data/autopkgtest/testing/amd64/g/geojson-pydantic/35907622/log.gz

Bug#1041296: ffmpeg: Undocumented build dependency on libunwind-dev

[Theodoric Stier]

Source: ffmpeg
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: kerd...@gmail.com

Dear Maintainer,

This source package requires the debian package libunwind-dev as a build 
dependency, but it is not installed by apt-src. This usually means the build 
dependency needs to be added to the BuildDepends field of the package data.

Thanks,
Ted Stier

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_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

-- no debconf information

Bug#1041295: smartd.conf.5: some remarks and editorial fixes for the manual

[Bjarni Ingi Gislason]

Package: smartmontools
Version: 7.3-1+b1
Severity: minor
Tags: patch

Dear Maintainer,

here are some notes and editorial fixes for the man page.

Patch is in the attachment.

-.-.

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"groff -man -Z" instead of "nroff -man"

  Add the option "-t", if the file contains a table.

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual, the following
must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Output from "mandoc -T lint smartd.conf.5":

mandoc: smartd.conf.5:250:2: WARNING: line scope broken: SH breaks TP
mandoc: smartd.conf.5:600:81: STYLE: input text line longer than 80 bytes: It 
may also be used ...
mandoc: smartd.conf.5:1080:84: STYLE: input text line longer than 80 bytes: If 
\*(Aq@ALL\*(Aq is...

-.-.

Change '-' (\-) to '\(en' (en-dash) for a numeric range.
GNU gnulib has recently (2023-06-18) updated its
"build_aux/update-copyright" to recognize "\(en" in man pages.

smartd.conf.5:2:Copyright (C) 2002-10 Bruce Allen
smartd.conf.5:3:Copyright (C) 2004-21 Christian Franke
smartd.conf.5:122:# Start short self\-tests daily between 1\-2, 2\-3, and
smartd.conf.5:123:# 3\-4 am.
smartd.conf.5:142:# Start short self\-tests daily between 1\-2, 2\-3, and
smartd.conf.5:143:# 3\-4 am.
smartd.conf.5:152:# 1 am and 2\-3 am
smartd.conf.5:173:# Start short self\-tests daily between 1\-2, 2\-3, and
smartd.conf.5:174:# 3\-4 am.
smartd.conf.5:192:# between midnight and 1 am and 2\-3 am.
smartd.conf.5:225:# Start short self\-tests daily between 1\-2, 2\-3, and
smartd.conf.5:226:# 3\-4 am.
smartd.conf.5:964:  smartctl \-t select,0\- /dev/sda
smartd.conf.5:969:\fB \-s n/../../[1\-5]/12\fP

-.-.

Wrong distance between sentences.

  Separate the sentences and subordinate clauses; each begins on a new
line.  See man-pages(7) ("Conventions for source file layout") and
"info groff" ("Input Conventions").

  The best procedure is to always start a new sentence on a new line,
at least, if you are typing on a computer.

Remember coding: Only one command ("sentence") on each (logical) line.

E-mail: Easier to quote exactly the relevant lines.

Generally: Easier to edit the sentence.

Patches: Less unaffected text.

Seach for two words are easier, when they belong to the same line, and
the same phrase.

  The amount of space between sentences in the output can then be
controlled with the ".ss" request.

167:# uses the cciss driver. Start long tests on Sunday nights and short
248:then the corresponding block device (/dev/sd?) must be listed,
371:then the corresponding SCSI (/dev/sd?) or character device (/dev/twe?,
372:/dev/twa?, /dev/twl? or /dev/tws?) must be listed, along with the
379:then the corresponding device (SCSI /dev/sg? on Linux or /dev/arcmsr0 on

-.-.

Protect a period (.) or a apostrophe (') with '\&' from becoming a
control character, if it could end up at the start of a line
(by splitting the line into more lines).

115:# flagged with the '\-d sat' option.  This situation
648:\fBsmartd\fP checks it.  This is the default behavior if the '\-n'
786:Appending ',ns' (no standby) to this directive is not implemented \"#
801:Appending ',ns' (no standby) to this directive is not implemented \"#
934:0, ... hours, use:
938:To enable staggered tests with delays 0, 1, 2, ..., 9, 10, 0, ... hours,

-.-.

Split a punctuation from a single argument, if a two-font macro is meant

64:.B /etc/smartd.conf.

-.-.

Use \(en for a dash (en-dash) between space characters and at the
beginning of a line, not a minus (\-) or a hyphen (-), except in the
NAME section.

smartd.conf.5:394:\- attempt to guess the device type from the device name or 
from
[... and more]
smartd.conf.5:1644:\- show the presets that are available for all drives and 
then exit.

-.-.

[ "test-groff" is a developmental version of "groff" ]

Input file is ./smartd.conf.5

Output from "test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z ":

troff: backtrace: file '':33
troff::33: warning: trailing space in the line
troff: backtrace: file '':34
troff::34: warning: trailing space in the line
troff: backtrace: file '':786
troff::786: warning: trailing space in the line
troff: backtrace: file '':787
troff::787: warning: trailing space in the line
troff: backtrace: file '':801
troff::801: warning: trailing space in the line
troff: backtrace: file '':802
troff::802: warning: trailing space in the line

-.-.



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

Kernel: Linux 6.3.7-1 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: 

Bug#1040787: dh-elpa: Lots of missing eln files

[Nicholas D Steeves]

Sean Whitton  writes:

> async 1.9.3 is from buster.  You have
> /usr/share/emacs/site-lisp/elpa-async-1.9.7 on your system, right?
>

That's interesting, because that means that this is an old bug!  See
#1040690, which also appears to be this issue.  So far the trigger
condition appears to be a dist-upgrade (or full-upgrade).  I wonder if
the issue is on the emacs-el or dh-elpa side, or both?

Cheers,
Nicholas

Bug#1040676: elpa-debian-el: Documentation fixes.

[Manphiz]

Nicholas D Steeves  writes:

> manp...@gmail.com writes:
>
>> I have a merge request on salsa[1] for documentation fixes for the
>> package elpa-debian-el.  The first commit has typo fixes only, the
>> second one has some proposed wording fixes.  Please review.  Thanks!
>>
>> [1] https://salsa.debian.org/emacsen-team/debian-el/-/merge_requests/10
>
> Thank you for these fixes!  I've started a review.  If for some reason I
> seem to take too long to notice that you've resolved all issues (when
> you've resolved them), please ping me at this bug.
>
> Cheers,
> Nicholas
>

Hi Nicolas,

Friendly ping for comments :)  If I missed your comments please help
point me to them and I'll address them soon.

-- 
Manphiz

Bug#1040836: udisks2: new udisks (auto-)mounts/unmounts fs?

[Christoph Anton Mitterer]

Hey Michael.

I've looked further into this, and it seems to be even worse than
originally thought.

udisks mounts the fs readable (actually even if it would mount it ro,
it might still cause writes to it)... which may easily cause data
corruption if a user unplugs a removable device... because there is no
reason for him to believe that the fs will be automagically mounted.

I'd even say this is a security issue seem my arguing at
https://github.com/storaged-project/udisks/issues/1145#issuecomment-1637258668
.

Upstream has some commits with respect to that issue... but (purely by
the commit message) it would seem to me that they still do this
unwarranted mounting for XFS/ext*.


Would be great if any fixes, so upstream recognises the issue, could be
pulled into Debian ASAP. :-)



Also, perhaps you know anything about this:

- me, opening LUKS container...

Jul 17 03:22:22 heisenberg kernel: BTRFS: device label data-b-1 devid 1 transid 
7188 /dev/dm-1 scanned by (udev-worker) (1086718)
Jul 17 03:22:22 heisenberg kernel: BTRFS info (device dm-1): using crc32c 
(crc32c-intel) checksum algorithm
Jul 17 03:22:22 heisenberg kernel: BTRFS info (device dm-1): using free space 
tree

- even without any restart, udisks seems to do its foul play and
  already mount any new device, but that's not the point here

Jul 17 03:22:22 heisenberg kernel: BTRFS info: devid 1 device path 
/dev/mapper/data-b-1_unformatted changed to /dev/dm-1 scanned by (udev-worker) 
(1086718)
Jul 17 03:22:22 heisenberg kernel: BTRFS info: devid 1 device path /dev/dm-1 
changed to /dev/mapper/data-b-1 scanned by (udev-worker) (1086718)

=> do you perhaps know anything about that "_unformatted"??

This seems new to me (and wrong, as there is an fs within the
container).
Not sure if it's from the udisks upgrade or perhaps the recent
udev/system upgrade 254~rc2-3?

Looks at least strange.


Previously these messages looked like:
2023-06-21T12:58:53.840720+02:00 heisenberg kernel: [   63.194874] BTRFS info: 
devid 1 device path /dev/mapper/data-b-1 changed to /dev/dm-0 scanned by 
(udev-worker) (2282)
2023-06-21T12:58:53.840720+02:00 heisenberg kernel: [   63.197048] BTRFS info: 
devid 1 device path /dev/dm-0 changed to /dev/mapper/data-b-1 scanned by 
(udev-worker) (2282)
(i.e. some back and forth renaming)


Thanks :-)
Chris.

Bug#1019299: Now fixed upstream

[Peter Chubb]

Upstream commit 7e863bb fixes this issue.

Please may we have a new version?
-- 
Dr Peter Chubbhttps://trustworthy.systems/
Trustworthy Systems GroupCSE, UNSW
Core hours: Mon 8am-3pm; Wed: 8am-5pm; Fri 8am-12pm.

Bug#1041294: xindy mishandles funny filenames

[Zefram]

Package: xindy
Version: 2.5.1.20160104-10
Severity: important

xindy(1) does various funny things if a filename contains characters
that are not usually used in filenames:

$ touch '>t0'
$ ls -l
total 0
-rw-rw-r-- 1 zefram zefram 0 Jul 17 01:21 '>t0'
$ xindy '>t0' 2>/dev/null
$ ls -l
total 0
-rw-rw-r-- 1 zefram zefram 0 Jul 17 01:21 '>t0'
-rw-rw-r-- 1 zefram zefram 0 Jul 17 01:21  t0
$ touch '|echo wibble'
$ xindy '|echo wibble' 2>/dev/null
wibble
$

These arise from its use of the <> Perl operator, which is not suitable
for the implementation of a read-from-list-of-files kind of command.
Because the range of misbehaviour includes writing to arbitrary files
and running arbitrary commands, this is a more severe bug than normal.

-zefram

Bug#1041293: elpa-boxquote: New upstream release 2.3

[Xiyue Deng]

Package: elpa-boxquote
Version: 2.2-1
Severity: wishlist
X-Debbugs-Cc: none, Xiyue Deng 

Dear maintainers,

A new upstream release 2.3 of boxquote is available.  I've prepared a
merge request on salsa[1] and it would be great if someone can review
and comment.  Thanks in advance!

[1] https://salsa.debian.org/emacsen-team/boxquote-el/-/merge_requests/3


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

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

Versions of packages elpa-boxquote depends on:
ii  dh-elpa-helper  2.0.16
ii  emacsen-common  3.0.5

Versions of packages elpa-boxquote recommends:
ii  emacs  1:28.2+1-15
ii  emacs-gtk [emacs]  1:28.2+1-15

elpa-boxquote suggests no packages.

-- no debconf information

Bug#1041292: extractres usage message has bad program name

[Zefram]

Package: psutils
Version: 1.17.dfsg-4
Severity: minor

If the extractres(1) program attempts to display a usage message, it
gets its own name wrong:

$ extractres -q
Usage: 1 [-merge] [file]
$

-zefram

Bug#1041291: ts with extra args behaves badly

[Zefram]

Package: moreutils
Version: 0.65-1
Severity: normal

ts(1) is documented to take a `format' argument on its command line,
and no other non-option arguments.  In fact, if given more arguments then
it won't complain about a usage error, but then won't read its standard
input, and will do more or less bizarre things with the extra arguments.
On the mild end of the spectrum, sometimes it will use an argument as
a filename, and take input from that file (which is pointless for a
regular file):

$ echo a > t0
$ ts %F t0
2023-07-17 a
$

It gets weirder if an argument contains certain characters that are not
usually used in filenames:

$ ls -l
total 4
-rw-rw-r-- 1 zefram zefram 2 Jul 17 00:45  t0
$ ts %F '>t1'
$ ls -l
total 4
-rw-rw-r-- 1 zefram zefram 2 Jul 17 00:45  t0
-rw-rw-r-- 1 zefram zefram 0 Jul 17 00:49  t1
$ echo c > 't2 '
$ ts %F 't2 '
Can't open t2 : No such file or directory at /usr/bin/ts line 113.
$ ts %F '|echo wibble'
wibble
$

The details of this behaviour arise because, after failing to check
for extraneous arguments, the program uses the <> Perl operator,
which magically implements a variety of interpretations of command line
arguments.  The range of behaviour includes writing to arbitrary files
and running arbitrary commands, which are very undesirable behaviours
for ts(1).  However, the seriousness of the problem is limited by the
fact that this behaviour only arises if the program is invoked with
extraneous arguments, contrary to its documentation.

It might be considered desirable for ts(1) to read input from files
named on the command line.  (Though pointless for regular files.)
If that is the case then it would not be wrong for the program to
accept the additional arguments.  But in that case it would still be
wrong for it to use the <> Perl operator, which is not suitable for the
implementation of a read-from-list-of-files kind of command, because
of the variety of behaviour described above.  It would also make this
a more serious bug, because the dangerous behaviour such as writing to
files could be invoked by attempts to read from files.  It would also be
a documentation bug that the possibility of naming files on the command
line was not mentioned in the man page or usage message.

-zefram

Bug#1040943: systemd-logind: 'HandlePowerKey=ignore' works in logind.conf, not in logind.conf.d/custom.conf

[Diederik de Haas]

On Monday, 17 July 2023 01:24:43 CEST Michael Biebl wrote:
> The journald output shows long and short key presses (with logind
> reacting accordingly)
> 
> jul 15 09:17:08 pinetab2 systemd-logind[1742]: Power key pressed short.
> jul 15 09:17:08 pinetab2 systemd-logind[1742]: Suspending...
> 
> jul 15 09:18:42 pinetab2 systemd-logind[1850]: Power key pressed long.
> jul 15 09:18:42 pinetab2 systemd-logind[1850]: Powering off...
> 
> That looks all as expected and I don't understand the problem this is
> supposed to show.

The problem is that in all cases I pressed the power key equally short.

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

Bug#1041290: time.1: some remarks and editorial fixes for the manual

[Bjarni Ingi Gislason]

Package: time
Version: 1.9-0.2
Severity: minor
Tags: patch

Dear Maintainer,

here are some notes and editorial fixes for the man page.

Patch is in the attachment.

-.-.

The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"groff -man -Z" instead of "nroff -man"

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual, the following
must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Input file is time.1

Change (or include a "FIXME" paragraph about) misused SI (metric)
numeric prefixes (or names) to the binary ones, like Ki (kibi), Mi
(mebi), Gi (gibi), or Ti (tebi), if indicated.
If the metric prefixes are correct, add the definitions or an
explanation to avoid misunderstanding.

  If "Kilo" is 1000 (then use "kilo"), if 1024 then use "kibi"

185:Average size of the process's unshared data area, in Kilobytes.
196:Kilobytes.
199:Kilobytes.
220:Average amount of shared text in the process, in Kilobytes.
232:Average unshared stack size of the process, in Kilobytes.
238:Average resident set size of the process, in Kilobytes.

-.-.

Use "\e" to print the escape character instead of "\\" (which gets
interpreted in copy mode).

153:A backslash (`\\') introduces a `backslash escape', which is
154:translated into a single printing character upon output.  `\\t' outputs
155:a tab character, `\\n' outputs a newline, and `' outputs a backslash.

-.-.

Output from "test-nroff -man -b -ww -z -rCHECKSTYLE=3":

[ "test-groff" is a developmental version of "groff" ]

Input file is ./time.1

Output from "test-groff -b -mandoc -dAD=l -rF0 -rHY=0 -t -w w -z 
-rSTYLECHECK=3":
an.tmac::4: style: .TH missing fourth argument; suggest package/project 
name and version (e.g., "groff 1.23.0")
troff: backtrace: '/home/bg/git/groff/build/s-tmac/an.tmac':598: macro 'BI'
troff: backtrace: file '':91
troff::91: warning: trailing space in the line
troff: backtrace: '/home/bg/git/groff/build/s-tmac/an.tmac':598: macro 'BI'
troff: backtrace: file '':103
troff::103: warning: trailing space in the line
an-end-check:: Warning: Different number of .RS and .RE calls, 
an-RS-open=2 at end of file

-.-.

  Line:

 %Uuser %Ssystem %Eelapsed %PCPU (%Xtext+%Ddata %Mmax)k

  The 'k' at the end should remain (or use 'kilo') if "Kilobyte" means
1000 bytes, otherwise it should be "Ki" (or kibi).

-.-.

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

Kernel: Linux 6.3.7-1 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), 
LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages time depends on:
ii  libc6  2.37-5

time recommends no packages.

time suggests no packages.

-- no debconf information
The difference between the formatted outputs can be seen with:

  nroff -man  > 
  nroff -man  > 
  diff -u  

and for groff, using

"groff -man -Z" instead of "nroff -man"

  Read the output of "diff -u" with "less -R" or similar.

-.-.

  If "man" (man-db) is used to check the manual, the following
must be set:

  The option "-warnings=w"

  The environmental variable:

export MAN_KEEP_STDERR=yes (or any non-empty value)

  or

  (produce only warnings):

export MANROFFOPT="-ww -z"

export MAN_KEEP_STDERR=yes (or any non-empty value)

-.-.

Input file is time.1, case 1

Change \' (acute) to \[aq], if used as a quote.
Change \' (acute) to ', if used as an apostrophe.

153:A backslash (`\\') introduces a `backslash escape', which is
155:a tab character, `\\n' outputs a newline, and `' outputs a backslash.

-.-.

Change (or include a "FIXME" paragraph about) misused SI (metric)
numeric prefixes (or names) to the binary ones, like Ki (kibi), Mi
(mebi), Gi (gibi), or Ti (tebi), if indicated.
If the metric prefixes are correct, add the definitions or an
explanation to avoid misunderstanding.

  If "Kilo" is 1000 (then use "kilo"), if 1024 then use "kibi"

185:Average size of the process's unshared data area, in Kilobytes.
196:Kilobytes.
199:Kilobytes.
220:Average amount of shared text in the process, in Kilobytes.
232:Average unshared stack size of the process, in Kilobytes.
238:Average resident set size of the process, in Kilobytes.

-.-.


Use "\e" to print the escape character instead of "\\" (which gets
interpreted in copy mode).

153:A backslash (`\\') introduces a `backslash escape', which is
154:translated into a single printing character upon output.  `\\t' outputs
155:a tab character, `\\n' outputs a newline, and `' outputs a backslash.

Bug#1040580: oz: diff for NMU version 0.17.0-5.2

[Timo Röhling]

Control: tags 1040580 + patch
Control: tags 1040580 + pending

Dear maintainer,

I've prepared an NMU for oz (versioned as 0.17.0-5.2) and
uploaded it directly to unstable.


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯
diff -Nru oz-0.17.0/debian/changelog oz-0.17.0/debian/changelog
--- oz-0.17.0/debian/changelog	2022-05-26 17:24:14.0 +0200
+++ oz-0.17.0/debian/changelog	2023-07-17 01:14:10.0 +0200
@@ -1,3 +1,10 @@
+oz (0.17.0-5.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Depend on python3-py for autopkgtest (Closes: #1040580)
+
+ -- Timo Röhling   Mon, 17 Jul 2023 01:14:10 +0200
+
 oz (0.17.0-5.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru oz-0.17.0/debian/tests/control oz-0.17.0/debian/tests/control
--- oz-0.17.0/debian/tests/control	2022-05-26 17:24:14.0 +0200
+++ oz-0.17.0/debian/tests/control	2023-07-17 01:14:10.0 +0200
@@ -1,3 +1,3 @@
 Tests: oz
 Architecture: amd64
-Depends: libvirt-daemon, oz, python3-pytest
+Depends: libvirt-daemon, oz, python3-pytest, python3-py


signature.asc
Description: PGP signature

Bug#1041289: extractres mishandles funny filenames

[Zefram]

Package: psutils
Version: 1.17.dfsg-4
Severity: important

extractres(1) does various funny things if a filename contains characters
that are not usually used in filenames:

$ touch '>t0.ps'
$ ls -l
total 0
-rw-rw-r-- 1 zefram zefram 0 Jul 17 00:25 '>t0.ps'
$ extractres '>t0.ps'
$ ls -l
total 0
-rw-rw-r-- 1 zefram zefram 0 Jul 17 00:25 '>t0.ps'
-rw-rw-r-- 1 zefram zefram 0 Jul 17 00:25  t0.ps
$ touch ' t1.ps'
$ extractres ' t1.ps'
Can't open  t1.ps: No such file or directory at /usr/bin/extractres line 53.
$

These arise from its use of the <> Perl operator, which is not suitable
for the implementation of a read-from-list-of-files kind of command.
Because the range of misbehaviour includes writing to arbitrary files
and running arbitrary commands, this is a more severe bug than normal.

-zefram

Bug#1040943: systemd-logind: 'HandlePowerKey=ignore' works in logind.conf, not in logind.conf.d/custom.conf

[Michael Biebl]

Am 15.07.23 um 11:55 schrieb Diederik de Haas:

Control: retitle -1 With HandlePowerKeyLongPress=shutdown configured, a short 
press is interpreted as long press

On Thursday, 13 July 2023 20:00:54 CEST Diederik de Haas wrote:

When I created /etc/systemd/logind.conf.d/custom.conf with
HandlePowerKey=ignore


If this is the whole content of /etc/systemd/logind.conf.d/custom.conf,
you are missing a [Login] section at the top of the file


It was the whole contents.
Adding the "[Login]" header (back) made it work \o/

I initially had that header, but in my attempts to get it to work, I removed
it again. I must have done something else wrong in my earlier attempts
which made it not work then, but I won't be able to recall exactly what.


It looks like there actually is a bug and not (just) a PEBKAC issue.
What I (actually) started out with, was the following custom config:
```
[Login]
HandlePowerKey=suspend
HandlePowerKeyLongPress=poweroff
```

And when I then pressed the power key *short*, it powered off the system.
My initial conclusion that logind.conf.d/custom.conf didn't work was incorrect.

If I remove or disable (via prepending it with '#') the LongPress action, then
it sees it as a short key press and does the desired thing: suspend.
If I set the LongPress action to 'ignore', then it also registers a short key
press as a short press and does the desired thing: suspend.
But if I set the LongPress action to 'shutdown', then it registers a short key
press as a *long* press and does the poweroff action.

Attached you'll find the custom config I used (same as quoted above) and
also the output from journalctl where all my physical key presses were short.


The journald output shows long and short key presses (with logind 
reacting accordingly)


jul 15 09:17:08 pinetab2 systemd-logind[1742]: Power key pressed short.
jul 15 09:17:08 pinetab2 systemd-logind[1742]: Suspending...

jul 15 09:18:42 pinetab2 systemd-logind[1850]: Power key pressed long.
jul 15 09:18:42 pinetab2 systemd-logind[1850]: Powering off...

That looks all as expected and I don't understand the problem this is 
supposed to show.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041288: ITP: cocotb -- coroutine based cosimulation library for writing VHDL and Verilog testbenches in Python

[Ahmed El-Mahmoudy]

Package: wnpp
Severity: wishlist
Owner: أحمد المحمودي (Ahmed El-Mahmoudy) 

* Package name: cocotb
  Version : 1.8.0
  Upstream Author : Chris Higgs, Stuart Hodgson 
* URL : https://github.com/cocotb/cocotb
* License : BSD
  Programming Lang: Python
  Description : coroutine based cosimulation library for writing VHDL and 
Verilog testbenches in Python

cocotb encourages the same philosophy of design re-use and randomized 
testing as UVM, however is implemented in Python.

With cocotb, VHDL or SystemVerilog are normally only used for the design 
itself, not the testbench.

cocotb has built-in support for integrating with continuous integration 
systems, such as Jenkins, GitLab, etc. through standardized, 
machine-readable test reporting formats.

cocotb was specifically designed to lower the overhead of creating a 
test.

cocotb automatically discovers tests so that no additional step is 
required to add a test to a regression.

All verification is done using Python

 - Intend to maintain it within Electronics team
 - Need a sponsor

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


signature.asc
Description: PGP signature

Bug#1041287: markdown doesn't accept multiple input files

[Zefram]

Package: markdown
Version: 1.0.1-10.1
Severity: normal

The man page markdown(1) says, in the synopsis, that the command accepts
a list of input filenames on the command line.  In fact if more than one
input file is given then only the first is used, and the rest are silently
ignored.  There isn't even an attempt to open the additional files:

$ echo a >t0
$ echo b >t1
$ markdown t0 t1
a
$ markdown t1 t0
b
$ markdown t2doesnotexist
Can't open t2doesnotexist: No such file or directory at /usr/bin/markdown line 
221.
$ markdown t0 t2doesnotexist
a
$

-zefram

Bug#1041286: markdown mishandles funny filenames

[Zefram]

Package: markdown
Version: 1.0.1-10.1
Severity: important

markdown(1) does various funny things if a filename contains characters
that are not usually used in filenames:

$ echo a > '>t0'
$ ls -l
total 4
-rw-rw-r-- 1 zefram zefram 2 Jul 16 23:20 '>t0'
$ markdown '>t0'
$ ls -l
total 4
-rw-rw-r-- 1 zefram zefram 2 Jul 16 23:20 '>t0'
-rw-rw-r-- 1 zefram zefram 0 Jul 16 23:20  t0
$ echo b > 't1 '
$ markdown 't1 '
Can't open t1 : No such file or directory at /usr/bin/markdown line 221.
$

These arise from its use of the <> Perl operator, which is not suitable
for the implementation of a read-from-list-of-files kind of command.
Because the range of misbehaviour includes writing to arbitrary files
and running arbitrary commands, this is a more severe bug than normal.

-zefram

Bug#1041285: ITP: pyuvm -- python implementation of UVM

[Ahmed El-Mahmoudy]

Package: wnpp
Severity: wishlist
Owner: أحمد المحمودي (Ahmed El-Mahmoudy) 

* Package name: pyuvm
  Version : 2.9.1
  Upstream Author : Ray Salemi 
* URL : https://github.com/pyuvm/pyuvm/
* License : Apache-2.0
  Programming Lang: Python
  Description : python implementation of UVM

pyuvm is the Universal Verification Methodology implemented in Python 
instead of SystemVerilog. pyuvm uses cocotb to interact with the 
simulator and schedule simulation events.

pyuvm implements the most often-used parts of the UVM while taking 
advantage of the fact that Python does not have strict typing and does 
not require parameterized classes. The project refactors pieces of the 
UVM that were either overly complicated due to typing or legacy code.

 - Intend to maintain it Electronics team
 - Need a sponsor

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


signature.asc
Description: PGP signature

Bug#1041284: rust-ureq - please update to support new serde-json

[Peter Green]

Package: rust-ureq
Version: 2.7.0-1
Severity: serious

Hi.

A change to error reporting in serde_json 1.0.94, intended to prevent
duplicate error messages broke an error-handling code-path in ureq.

ureq's initial fix was to impose an upper limit on the version of
serde_json. Later a proper fix was made by adding a new method
to serde_json::error and changing ureq to use it.

I've just updated serde_json, please update ureq to match.

Bug#1041283: pure-ftpd-common: pure-ftpd-wrapper does not support setting TLS certificate/key file

[Anselm Lingnau]

Package: pure-ftpd-common
Version: 1.0.50-2.1
Severity: wishlist
Tags: patch

Hi –

It seems that Pure-Ftpd now has a command line option that lets the admin
configure the location of the TLS certificate/key file(s). This option,
however, is not supported by the pure-ftpd-wrapper script.

I'm enclosing a patch that adds support for the two settings mentioned
in the pure-ftpd.conf file (CertFile and CertFileAndKey). The "CertFile"
configuration file specifies a single file name, referring to a file that
contains the certificate and the corresponding private key, while the
"CertFileAndKey" configuration file specifies two file names on the same
line, separated by ":", ",", a space or a tab, giving the file containing
the certificate and that containing the key separately. (In both cases,
the certificate can actually be a bundle of certificates including any
required intermediate certificates.)

It would be great if this patch (or something else to the same effect)
could be made part of the official distribution.

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 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 pure-ftpd-common depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  libpam-modules 1.5.2-6
ii  perl   5.36.0-7

Versions of packages pure-ftpd-common recommends:
pn  pure-ftpd  

pure-ftpd-common suggests no packages.

--- pure-ftpd-wrapper.orig  2023-07-16 21:28:46.981044290 +
+++ pure-ftpd-wrapper   2023-07-16 21:36:46.454419036 +
@@ -65,6 +65,8 @@
'Bind' => ['-S %s', \_string],
'BrokenClientsCompatibility' => ['-b'],
'CallUploadScript' => ['-o'],
+   'CertFile' => ['-2 %s', \_filename],
+   'CertFileAndKey' => ['-2 %s,%s', \_filename_2],
'ChrootEveryone' => ['-A'],
'CreateHomeDir' => ['-j'],
'CustomerProof' => ['-Z'],
@@ -240,6 +242,25 @@
return 1;
 }
 
+sub parse_filename_2 {
+   my ($buf, $fmt, $val) = @_;
+
+   if ($val =~ /^(.*)[,:\s](.*)$/) {
+   unless (-f $1) {
+   $$buf = qq{"$1": No such file};
+   return;
+   }
+   unless (-f $2) {
+   $$buf = qq{"$2": No such file};
+   return;
+   }
+   $$buf = sprintf $fmt, $1, $2;
+   return 1
+   }
+
+   $$buf = qq{"$val": must be two file names separated by comma, colon, or 
space};
+} 
+
 sub parse_ip {
my ($buf, $fmt, $val) = @_;
 

Bug#1041282: jtreg6: Please add jtreg6 depenedencies to allow openjdk -11, -17 jtreg tests to pass

[Vladimir Petko]

Package: jtreg6
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainer,

This patch updates jtreg6 dependencies to allow jtreg tests to pass for
openjdk-11 and -17:
  * Add asmtools dependency (LP: #2015011).
  * debian/control: Use testng 7 (LP: #2012320).
  * debian/jtreg6.links: Fix hamcrest.jar link (LP: #2015010).

asmtools needs to be in the classpath for the number of tests to work.
testng 7 is required for running the tests, the package builds with 6.9 but
updated the build dependency to avoid any possible future break.
hamcrest.jar is used in `test/jdk/tools/jpackage/junit/junit.java` but the
Debian package uses hamcrest-core.jar in the manifest.
The alternative is to patch the JDK test, but it would be a higher-maintenance
decision.

Thanks for considering the patch.


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

Kernel: Linux 6.2.0-24-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru jtreg6-6.1+2/debian/control jtreg6-6.1+2/debian/control
--- jtreg6-6.1+2/debian/control 2022-07-20 21:34:07.0 +1200
+++ jtreg6-6.1+2/debian/control 2023-03-27 14:59:03.0 +1300
@@ -13,7 +13,9 @@
  libjtharness-java (>= 6.0),
  libxalan2-java,
  libhamcrest-java,
- testng
+ libtestng7-java,
+ libasmtools-java,
+ libjcommander-java
 Standards-Version: 4.6.0
 Vcs-Git: https://salsa.debian.org/java-team/jtreg.git
 Vcs-Browser: https://salsa.debian.org/java-team/jtreg
@@ -28,9 +30,12 @@
  javahelp2,
  libjtharness-java (>= 6.0),
  libhamcrest-java,
- libxalan2-java
-Recommends: testng
-Conflicts: jtreg
+ libxalan2-java,
+ libasmtools-java,
+ libjcommander-java,
+ libslf4j-java
+Recommends: libtestng7-java
+Conflicts: jtreg, jtreg7
 Description: Regression Test Harness for the OpenJDK platform
  jtreg is the test harness used by the OpenJDK test framework.
  This framework is intended primarily for regression tests.
diff -Nru jtreg6-6.1+2/debian/jtreg6.links jtreg6-6.1+2/debian/jtreg6.links
--- jtreg6-6.1+2/debian/jtreg6.links2020-07-15 16:28:47.0 +1200
+++ jtreg6-6.1+2/debian/jtreg6.links2023-03-27 14:59:03.0 +1300
@@ -1,6 +1,7 @@
 usr/share/jtreg/bin/jtreg   /usr/bin/jtreg
 usr/share/jtreg/bin/jtdiff  /usr/bin/jtdiff
 
+usr/share/java/hamcrest.jar /usr/share/jtreg/lib/hamcrest.jar
 usr/share/java/hamcrest-core.jar/usr/share/jtreg/lib/hamcrest-core.jar
 usr/share/java/javatest.jar /usr/share/jtreg/lib/javatest.jar
 usr/share/java/jcommander.jar   /usr/share/jtreg/lib/jcommander.jar
@@ -8,7 +9,9 @@
 usr/share/java/jtreg.jar/usr/share/jtreg/lib/jtreg.jar
 usr/share/java/junit4.jar   /usr/share/jtreg/lib/junit.jar
 usr/share/java/testng.jar   /usr/share/jtreg/lib/testng.jar
+usr/share/java/asmtools.jar /usr/share/jtreg/lib/asmtools.jar
 
+usr/share/java/hamcrest.jar 
/usr/share/jtreg/share/java/hamcrest.jar
 usr/share/java/hamcrest-core.jar
/usr/share/jtreg/share/java/hamcrest-core.jar
 usr/share/java/javatest.jar 
/usr/share/jtreg/share/java/javatest.jar
 usr/share/java/jcommander.jar   
/usr/share/jtreg/share/java/jcommander.jar
@@ -16,3 +19,4 @@
 usr/share/java/jtreg.jar/usr/share/jtreg/share/java/jtreg.jar
 usr/share/java/junit4.jar   /usr/share/jtreg/share/java/junit.jar
 usr/share/java/testng.jar   /usr/share/jtreg/share/java/testng.jar
+usr/share/java/asmtools.jar 
/usr/share/jtreg/share/java/asmtools.jar
diff -Nru jtreg6-6.1+2/debian/patches/add-asmtools-to-classpath.patch 
jtreg6-6.1+2/debian/patches/add-asmtools-to-classpath.patch
--- jtreg6-6.1+2/debian/patches/add-asmtools-to-classpath.patch 1970-01-01 
12:00:00.0 +1200
+++ jtreg6-6.1+2/debian/patches/add-asmtools-to-classpath.patch 2023-03-27 
14:59:03.0 +1300
@@ -0,0 +1,16 @@
+Description: Provide path to asmtools.jar
+ A number of hotspot tests use java asmtools. Provide path to asmtools.jar
+Author: Vladimir Petko 
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/jtreg6/+bug/2015011
+Last-Update: 2023-04-03
+--- a/make/build.xml
 b/make/build.xml
+@@ -144,7 +144,7 @@
+ 
+ 
+ 
+-
++
+ 
+ 
+ 
diff -Nru jtreg6-6.1+2/debian/patches/add-logger-to-classpath.patch 

Bug#1033658: ftp.debian.org: Please add "riscv64" to the archive

[Drew Fustini]

On Wed, Jul 05, 2023 at 11:19:48PM +0200, Manuel A. Fernandez Montecelo wrote:
> Hi,
> 
> On Wed, 29 Mar 2023 at 17:48, Manuel A. Fernandez Montecelo
>  wrote:
> >
> > Package: ftp.debian.org
> > Severity: normal
> > X-Debbugs-Cc: aure...@debian.org, m...@debian.org
> >
> > Hello FTP team,
> >
> > We had conversations requesting different teams (FTP, Release, DSA) their
> > opinion about adding riscv64 [1] as a new architecture in the main
> > infrastructure and all teams gave their provisional approval, so we are
> > submitting this to track progress on this task.
> >
> > Could you please tells us if there's any blocker or something else that we
> > should do?
> >
> >
> > Cheers.
> >
> >
> > [1] https://wiki.debian.org/Ports/riscv64
> 
> Gentle ping?
> 
> We'd like to start with this when possible, the rebuilding of the
> whole archive will take a while and this is a good moment for us.
> 
> If there's any blocker, please let us know.
> 
> 
> Cheers.
> -- 
> Manuel A. Fernandez Montecelo 
> 

Hello FTP team,

Thank you for your efforts. Similar to Manuel, I am also interested to
know if there is progress. Our community of users has been using Debian
on the BeagleBoards and BeagleBones for years with great success. We
recently launched a new 64-bit RISC-V board [1] with more planned in the
future. We are currently using a minimal system built with Yocto but we
are eager to switch our BeagleV boards to Debian.

Thank you,
Drew Fustini
BeagleBoard.org Foundation

[1] https://beagleboard.org/beaglev-ahead

Bug#1041279: adduser: [INTL:nl] Dutch translation for the adduser package

[Frans Spiesschaert]

 
 
Package: adduser 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch po file for the adduser package. 
A draft has been posted to the debian-l10n-dutch mailing list allowing for
review. 
Please add it to your next package revision. 
It should be put as "po/nl.po" in your package build tree. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1041278: tzdata: [INTL:nl] Dutch translation of debconf templates

[Frans Spiesschaert]

 
 
Package: tzdata 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of tzdata debconf
messages. A draft has been posted to the debian-l10n-dutch mailing list
allowing for review. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1041277: icingaweb2-module-graphite: [INTL:nl] Dutch translation of debconf templates

[Frans Spiesschaert]

 
 
Package: icingaweb2-module-graphite 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached a Dutch translation of icingaweb2-module-
graphite debconf messages. A draft has been posted to the debian-l10n-
dutch mailing list allowing for review. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Kind regards,
Frans Spiesschaert



nl.po.gz
Description: application/gzip

Bug#1023491: ovmf-ia32 lacks non-secboot firmware images, but qemu does not (yet) support secboot

[Lionel Debroux]

Hi,

A patch such as the attached (to avoid potential line wrap) one, which 
changes debian/rules to:

* add an entry to OVMF32_IMAGES;
* perform a small copy-paste-modify job in the target which depends on 
OVMF32_BINARIES and OVMF32_IMAGES
seems to be enough to build and package a non-secboot 4M code image into 
ovmf-ia32.


Rinse and repeat similar changes for 2M and 2M secboot images, if you 
want them, though I'd say that there's little point in doing so: typical 
UEFI-capable computers, even 32-bit x86 ones, aren't so RAM-starved that 
they'd be able to boot a small UEFI BIOS but not a larger one.



Regards,
Lionel Debroux.--- a/debian/rules2023-07-14 21:28:17.978872495 +0200
+++ b/debian/rules2023-07-15 21:28:39.848206125 +0200
@@ -76,7 +76,7 @@
 OVMF32_BUILD_DIR = Build/OvmfIa32/$(BUILD_TYPE)_$(EDK2_TOOLCHAIN)
 OVMF32_SHELL = $(OVMF32_BUILD_DIR)/IA32/Shell.efi
 OVMF32_BINARIES = $(OVMF32_SHELL)
-OVMF32_IMAGES  := $(addprefix $(OVMF32_INSTALL_DIR)/,OVMF32_CODE_4M.secboot.fd OVMF32_VARS_4M.fd)
+OVMF32_IMAGES  := $(addprefix $(OVMF32_INSTALL_DIR)/,OVMF32_CODE_4M.secboot.fd OVMF32_CODE_4M.fd OVMF32_VARS_4M.fd)
 
 QEMU_EFI_BUILD_DIR = Build/ArmVirtQemu-$(EDK2_HOST_ARCH)/$(BUILD_TYPE)_$(EDK2_TOOLCHAIN)
 AAVMF_BUILD_DIR = Build/ArmVirtQemu-AARCH64/$(BUILD_TYPE)_$(EDK2_TOOLCHAIN)
@@ -99,11 +99,19 @@
build -a IA32 \
-t $(EDK2_TOOLCHAIN) \
-p OvmfPkg/OvmfPkgIa32.dsc \
-   $(OVMF32_4M_SMM_FLAGS) -b $(BUILD_TYPE)
+   $(OVMF32_4M_FLAGS) -b $(BUILD_TYPE)
cp $(OVMF32_BUILD_DIR)/FV/OVMF_CODE.fd \
-   $(OVMF32_INSTALL_DIR)/OVMF32_CODE_4M.secboot.fd
+   $(OVMF32_INSTALL_DIR)/OVMF32_CODE_4M.fd
cp $(OVMF32_BUILD_DIR)/FV/OVMF_VARS.fd \
$(OVMF32_INSTALL_DIR)/OVMF32_VARS_4M.fd
+   rm -rf Build/OvmfIa32
+   set -e; . ./edksetup.sh; \
+   build -a IA32 \
+   -t $(EDK2_TOOLCHAIN) \
+   -p OvmfPkg/OvmfPkgIa32.dsc \
+   $(OVMF32_4M_SMM_FLAGS) -b $(BUILD_TYPE)
+   cp $(OVMF32_BUILD_DIR)/FV/OVMF_CODE.fd \
+   $(OVMF32_INSTALL_DIR)/OVMF32_CODE_4M.secboot.fd
 
 build-ovmf: $(OVMF_BINARIES) $(OVMF_IMAGES) $(OVMF_PREENROLLED_VARS)
 $(OVMF_BINARIES) $(OVMF_IMAGES): debian/setup-build-stamp

Bug#1041271: maildir-utils: public shared library shipped in maildir-utils binary package

[Jeremy Sowden]

On 2023-07-16, at 20:11:30 +0100, Jeremy Sowden wrote:
> On 2023-07-16, at 13:59:43 -0300, David Bremner wrote:
> > I think that libguile-mu.* need to be either moved to a private
> > directory or to their own packages. I don't know enough about guile to
> > say which is better.
> 
> I think it probably wants to go into Guile's extensions directory:
> /usr/lib/${DEB_HOST_MULTIARCH}/guile-3.0/extensions.
> 
> For 1.8, I believe that will require something along the lines of:
> 
>   diff --git a/configure.ac b/configure.ac
>   index 5e44d5d168f9..f99a5cf5c169 100644
>   --- a/configure.ac
>   +++ b/configure.ac
>   @@ -211,6 +211,7 @@ AS_IF([test "x$enable_guile" != "xno"],[
>  GUILE_PKG([3.0 2.2])
>  GUILE_PROGS
>  GUILE_FLAGS
>   +  GUILE_SITE_DIR
>  AC_DEFINE_UNQUOTED([GUILE_BINARY],"$GUILE",[guile binary])
>  vsnarf=guile-snarf${GUILE_EFFECTIVE_VERSION}
>  AC_CHECK_PROGS(GUILE_SNARF,[${vsnarf} guile-snarf], [no])
>   diff --git a/guile/Makefile.am b/guile/Makefile.am
>   index dd911087ded7..992e929c1fdc 100644
>   --- a/guile/Makefile.am
>   +++ b/guile/Makefile.am
>   @@ -42,7 +42,8 @@ AM_CXXFLAGS=  \
>   -Wno-missing-declarations   \
>   -Wno-suggest-attribute=noreturn
>
>   -lib_LTLIBRARIES=   \
>   +guile_extensionsdir = $(GUILE_EXTENSION)
>   +guile_extensions_LTLIBRARIES = \
>   libguile-mu.la
>
>libguile_mu_la_SOURCES=\
> 
> I'll create another MR once I've tested it.

https://salsa.debian.org/emacsen-team/maildir-utils/-/merge_requests/3

J.


signature.asc
Description: PGP signature

Bug#1040787: dh-elpa: Lots of missing eln files

[David Bremner]

Aymeric Agon-Rambosson  writes:

> I would say that any directory in /usr/share/emacs/site-lisp/elpa 
> that has no namesake in /usr/share/emacs/site-lisp/elpa-src, AND 
> that is not provided itself by a package, should not be 
> there. Sean, does that seem right to you, or is that too violent a 
> predicate ?

Sounds about right. You could look for .elc files alongside broken
symlinks to the corresponding .el file

d

Bug#1040871: reportbug fails to start

[Sebastian Ramacher]

Control: reassign -1 pysimplesoap 1.16.2-4
Control: close -1 1.16.2-5

On 2023-07-11 21:27:34 +0200, Laurent Martelli wrote:
> Package: reportbug
> Version: 12.0.0
> Severity: grave
> 
> Reportbug fails to start. It seems to relate to the removal of a deprecated
> function in python 3.11.
> 
> Traceback (most recent call last):
>   File "/usr/bin/reportbug", line 40, in 
> from reportbug import utils
>   File "/usr/lib/python3/dist-packages/reportbug/utils.py", line 70, in
> 
> from . import debbugs   # noqa: E402
> ^
>   File "/usr/lib/python3/dist-packages/reportbug/debbugs.py", line 33, in
> 
> import debianbts
>   File "/usr/lib/python3/dist-packages/debianbts/__init__.py", line 1, in
> 
> from debianbts.debianbts import *  # noqa
> ^
>   File "/usr/lib/python3/dist-packages/debianbts/debianbts.py", line 22, in
> 
> from pysimplesoap.client import SoapClient
>   File "/usr/lib/python3/dist-packages/pysimplesoap/__init__.py", line 16,
> in 
> from . import client, server, simplexml, transport
>   File "/usr/lib/python3/dist-packages/pysimplesoap/client.py", line 33, in
> 
> from .transport import get_http_wrapper, set_http_wrapper, get_Http
>   File "/usr/lib/python3/dist-packages/pysimplesoap/transport.py", line
> 109, in 
> if 'timeout' in inspect.getargspec(httplib2.Http.__init__)[0]:
> ^^
> AttributeError: module 'inspect' has no attribute 'getargspec'. Did you
> mean: 'getargs'?

That was fixed in pysimplesoap 1.16.2-5 which is included in bookworm.
This looks like you did not fully upgrade your system to bookworm.

Reassinging and closing.

Cheers
-- 
Sebastian Ramacher

Bug#1041276: r-cran-hunspell: please use libhunspell-private-dev instead of copying private headers over

[Rene Engelhard]

Source: -rcran-hunspell
Version: 3.0.2+dfsg-2
Severity: wishlist

libhunspell-private-dev was just accepted (and uploaded to unstable).

Thus r-cran-hunspellshoud stop copying private headers over (which it
never should have done!) and use it.

Diff:

diff -Nru r-cran-hunspell-3.0.2+dfsg/debian/changelog 
r-cran-hunspell-3.0.2+dfsg/debian/changelog
--- r-cran-hunspell-3.0.2+dfsg/debian/changelog 2023-01-10 14:31:02.0 
+0100
+++ r-cran-hunspell-3.0.2+dfsg/debian/changelog 2023-06-18 17:06:24.0 
+0200
@@ -1,3 +1,13 @@
+r-cran-hunspell (3.0.2+dfsg-2.1) UNRELEASED; urgency=medium
+
+  * Shop shipping and using copied hunspell private headers
+- build-depend on libhunspell-private-dev
+- don't copy htypes.hxx and csutis.hxx but ln -sf them
+- use libhunspell-private-devs .shlibs to get a strict dependecy
+  on libhunspell
+
+ -- Andreas Tille   Sun, 18 Jun 2023 15:06:24 +
+
 r-cran-hunspell (3.0.2+dfsg-2) experimental; urgency=medium

   * Enable building twice in a row (thanks for the patch to Rene Engelhard)
diff -Nru r-cran-hunspell-3.0.2+dfsg/debian/control 
r-cran-hunspell-3.0.2+dfsg/debian/control
--- r-cran-hunspell-3.0.2+dfsg/debian/control   2023-01-10 14:31:02.0 
+0100
+++ r-cran-hunspell-3.0.2+dfsg/debian/control   2023-06-18 16:19:03.0 
+0200
@@ -14,7 +14,7 @@
r-base-dev,
r-cran-rcpp,
r-cran-digest,
-   libhunspell-dev (>= 1.7.2+really1.7.2)
+   libhunspell-private-dev
 Testsuite: autopkgtest-pkg-r

 Package: r-cran-hunspell
diff -Nru r-cran-hunspell-3.0.2+dfsg/debian/rules 
r-cran-hunspell-3.0.2+dfsg/debian/rules
--- r-cran-hunspell-3.0.2+dfsg/debian/rules 2023-01-10 14:31:02.0 
+0100
+++ r-cran-hunspell-3.0.2+dfsg/debian/rules 2023-06-18 17:06:24.0 
+0200
@@ -8,12 +8,15 @@
rm -rf src/hunspell

 override_dh_auto_build:
-   # FIXME: For the moment hack missing header files in here
-   # Once we are sure that package build file bug report against
-   # libhunspell-dev to include those missing header files
-   cp -a debian/hunspell src
+   mkdir src/hunspell
+   cd src/hunspell && \
+   ln -sf /usr/include/hunspell/csutil.hxx && \
+   ln -sf /usr/include/hunspell/htypes.hxx
dh_auto_build

 override_dh_fixperms:
dh_fixperms
find debian \( -name "*.dic" -o -name "*.aff" \) -exec chmod -x \{\} \;
+
+override_dh_shlibdeps:
+   dh_shlibdeps -- -L/var/lib/dpkg/info/libhunspell-private-dev.shlibs
diff -Nru r-cran-hunspell-3.0.2+dfsg/debian/shlibs.local 
r-cran-hunspell-3.0.2+dfsg/debian/shlibs.local
--- r-cran-hunspell-3.0.2+dfsg/debian/shlibs.local  2023-01-10 
14:31:02.0 +0100
+++ r-cran-hunspell-3.0.2+dfsg/debian/shlibs.local  1970-01-01 
01:00:00.0 +0100
@@ -1 +0,0 @@
-libhunspell-1.70 libhunspell-1.7-0 (>= 1.7.2+really1.7.2)

Due to the extra .shlibs this now also makes r-cran-hunspell get a 

Depends: r-api-4.0, r-cran-rcpp (>= 0.12.12), r-cran-digest, libc6 (>= 2.14), 
libgcc-s1 (>= 3.0), libhunspell-1.7-0 (>= 1.7.2+really1.7.2), libhunspell-1.7-0 
(<< 1.7.2+really1.7.2.1~), libstdc++6 (>= 13.1), hunspell-en-gb, hunspell-en-us

as of now and future hunspell updates will need a bin-NMU of
r-cran-hunspell so be it..

Regards,

Rene

Bug#1040787: dh-elpa: Lots of missing eln files

[Aymeric Agon-Rambosson]

Le dimanche 16 juillet 2023 à 19:39, "Nikolaus Rath" 
 a écrit :


Afraid not. With the current elpa-async package, the files are 
correctly removed on purge.


That's good.

That leaves me with a different question though - how do I clean 
up my system? It seems I have a lot of directories and files  in 
/usr/share/emacs/site-lisp/elpa that should not be there, and 
dpkg -S can't be used to identify what should and shouldn't be 
there. Is there a way to find out what should not be there?


I would say that any directory in /usr/share/emacs/site-lisp/elpa 
that has no namesake in /usr/share/emacs/site-lisp/elpa-src, AND 
that is not provided itself by a package, should not be 
there. Sean, does that seem right to you, or is that too violent a 
predicate ?


Best,

Aymeric

Bug#1041275: sbuild: Using eatmydata with the unshare backend

[Andrea Pappacoda]

Package: sbuild
Version: 0.85.2
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi, I somewhat recently switched to the unshare backend, using tarballs
generated by mmdebstrap, and it has been great!

One thing that is a bit less nice than schroot, though, is the inability of the
unshare backend to use eatmydata to speed up package builds. Not only speed,
but I also fear that continuous (and unnecessary) disk writes may degrade my
disk's lifespan ever so slightly.

Is there a way possible to use eatmydata with the unshare backend? So far I
tried to start the build with `eatmydata sbuild`, but it doesn't seem to work.
The eatmydata package is installed in the tarball.

Thanks!


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

Kernel: Linux 6.3.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 sbuild depends on:
ii  adduser 3.134
ii  libsbuild-perl  0.85.2
ii  perl5.36.0-7

Versions of packages sbuild recommends:
ii  autopkgtest  5.29
ii  debootstrap  1.0.128+nmu2
ii  schroot  1.6.13-3+b2
ii  uidmap   1:4.13+dfsg1-1+b1

Versions of packages sbuild suggests:
pn  deborphan  
ii  e2fsprogs  1.47.0-2
ii  kmod   30+20230519-1
ii  wget   1.21.3-1+b2

- -- no debconf information

-BEGIN PGP SIGNATURE-

iIoEARYIADIWIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCZLRGkBQcYW5kcmVhQHBh
cHBhY29kYS5pdAAKCRBKkgiiRVB3p3/IAQDy9M1Se2vwiTLyj5ZXtB2D8/SsZbKK
gmPZJhpBBLueXQD/QHitxrjCK+f5Vg3eoZ+f6uz7PJwQHXjLvd+se4Xylwk=
=d+oF
-END PGP SIGNATURE-

Bug#1041271: maildir-utils: public shared library shipped in maildir-utils binary package

[Jeremy Sowden]

On 2023-07-16, at 13:59:43 -0300, David Bremner wrote:
> Package: maildir-utils
> Version: 1.8.14-2
> Severity: serious
> Justification: violates policy 8.1
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> I think that libguile-mu.* need to be either moved to a private
> directory or to their own packages. I don't know enough about guile to
> say which is better.

I think it probably wants to go into Guile's extensions directory:
/usr/lib/${DEB_HOST_MULTIARCH}/guile-3.0/extensions.

For 1.8, I believe that will require something along the lines of:

  diff --git a/configure.ac b/configure.ac
  index 5e44d5d168f9..f99a5cf5c169 100644
  --- a/configure.ac
  +++ b/configure.ac
  @@ -211,6 +211,7 @@ AS_IF([test "x$enable_guile" != "xno"],[
 GUILE_PKG([3.0 2.2])
 GUILE_PROGS
 GUILE_FLAGS
  +  GUILE_SITE_DIR
 AC_DEFINE_UNQUOTED([GUILE_BINARY],"$GUILE",[guile binary])
 vsnarf=guile-snarf${GUILE_EFFECTIVE_VERSION}
 AC_CHECK_PROGS(GUILE_SNARF,[${vsnarf} guile-snarf], [no])
  diff --git a/guile/Makefile.am b/guile/Makefile.am
  index dd911087ded7..992e929c1fdc 100644
  --- a/guile/Makefile.am
  +++ b/guile/Makefile.am
  @@ -42,7 +42,8 @@ AM_CXXFLAGS=  \
  -Wno-missing-declarations   \
  -Wno-suggest-attribute=noreturn
   
  -lib_LTLIBRARIES=   \
  +guile_extensionsdir = $(GUILE_EXTENSION)
  +guile_extensions_LTLIBRARIES = \
  libguile-mu.la
   
   libguile_mu_la_SOURCES=\

I'll create another MR once I've tested it.

J.


signature.asc
Description: PGP signature

Bug#1009232: libxslt: New upstream release (v1.1.35, 2022 Feb 16), not detected by debian/watch

[Florian Ernst]

Control: retitle -1 libxslt: New upstream release (v1.1.38, 2023-May-08)

On Sat, Apr 09, 2022 at 02:41:44PM +0200, Mattia Rizzolo wrote:
> On Sat, Apr 09, 2022 at 01:05:20PM +0200, Florian Ernst wrote:
> > there is a new upstream release available, cf.
> > .
> 
> Thank you, I had indeed missed this release…

Apparently this version was also uploaded soon after, cf.
,
including an updated debian/watch.

However, the latter now indicates the availability of 1.1.38, hence
just updating this bug's title accordingly.

Cheers,
Flo


signature.asc
Description: PGP signature

Bug#1040920: Info received (Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID))

[Nikolaus Rath]

Another finding: starting gnome-session with `--builtin` instead of `--systemd` 
works around the problem.

Bug#1040787: dh-elpa: Lots of missing eln files

[Nikolaus Rath]

On Sun, 16 Jul 2023, at 15:20, Sean Whitton wrote:
> Hello,
>
> On Sun 16 Jul 2023 at 12:06pm +01, Nikolaus Rath wrote:
>
>> Hmm. I think the problem is not that the various elpa packages did not
>> get installed correctly, but that they did not get removed fully. So
>> I'll skip this step for now in an attempt to preserve the current state.
>
> Yes, I think that's right.  The .elc should not have been left behind
> when you removed elpa-async.  There isn't really enough information here
> to try to fix whatever caused that.  Let us know if you are able to
> reproduce.

Afraid not. With the current elpa-async package, the files are correctly 
removed on purge.

That leaves me with a different question though - how do I clean up my system? 
It seems I have a lot of directories and files  in 
/usr/share/emacs/site-lisp/elpa that should not be there, and dpkg -S can't be 
used to identify what should and shouldn't be there. Is there a way to find out 
what should not be there?

Best,
-Nikolaus

Bug#1041274: passwordsafe: Editing entry crashes program

[Bill Wohler]

Package: passwordsafe
Version: 1.16.0+dfsg-4
Severity: important

Creating a new entry or editing an existing entry results in the following 
crash:

[wohler@olgas ~ (olgas:*%)]$ pwsafe 
pwsafe: ./src/core/PWScore.cpp:1890: void 
PWScore::GetAllGroups(std::vector >&, bool) 
const: Assertion `!iter2->empty()' failed.
Aborted

I am happy to report that I was able to install Password Safe 1.17
from trixie and this fixed the problem. Fortunately, I was able to
upgrade without pulling in any other packages.

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

Kernel: Linux 6.1.0-10-amd64 (SMP w/6 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.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 passwordsafe depends on:
ii  libc62.36-9
ii  libgcc-s112.2.0-14
ii  libmagic11:5.44-3
ii  libqrencode4 4.1.1-1
ii  libstdc++6   12.2.0-14
ii  libuuid1 2.38.1-5+b1
ii  libwxbase3.2-1   3.2.2+dfsg-2
ii  libwxgtk3.2-13.2.2+dfsg-2
ii  libx11-6 2:1.8.4-2+deb12u1
ii  libxerces-c3.2   3.2.4+debian-1
ii  libxtst6 2:1.2.3-1.1
ii  libykpers-1-11.20.0-3
ii  passwordsafe-common  1.16.0+dfsg-4

Versions of packages passwordsafe recommends:
ii  xvkbd  4.1-2

passwordsafe suggests no packages.

-- no debconf information

Bug#1040343: linux-image-5.10.0-9-amd64: Kernel silenty de-supported nfsv3 UDP mounts

[Ben Hutchings]

On Wed, 2023-07-05 at 15:18 +0200, Hauke Fath wrote:
> On 7/5/23 10:20, Bastian Blank wrote:
> > On Tue, Jul 04, 2023 at 06:35:44PM +0200, Hauke Fath wrote:
> > > /misc /etc/auto.misc  
> > > -nfsvers=3,proto=udp,resvport,retrans=5,rsize=16384,wsize=16384,rw,hard
> > And if you set it to TCP (the default) or better directly switch to
> > NFSv4?
> 
> nfsv3 over tcp works, but is subobtimal , as described - when the router 
> goes down, the tcp mounts will hang, and the machine will have to be 
> rebooted.
[...]

Does this mean you are using the "soft" mount option?  Without that, I
would expect access to the mount to hang until the network connection
is restored, regardless of whether the TCP or UDP transport is used.

The default retry and timeout behaviour *is* different between
transports, though.  See the "timeo" and "retrans" options in nfs(5). 
You may wish to override the defaults in your environment.

Ben.

-- 
Ben Hutchings
Theory and practice are closer in theory than in practice - John Levine



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

Bug#1036971: pwsafe: empty window after internal timeout or screen blank

[Bill Wohler]

Unfortunately, version 1.17 in trixie does not address this issue for me.

Bill Wohler  wrote:

> Just confirmed that it is version 1.16 that I'm running at work. It was
> built from source on a Red Hat 8 system.
> 
> Bill Wohler  wrote:
> 
> > Hi Bill,
> > 
> > I can confirm this regression as I experienced it when I upgraded from
> > bullseye (perhaps with a more recent version than 1.12 from backports)
> > to bookworm (with PasswordSafe 1.16) yesterday.
> > 
> > Normally, when the database is locked after some time of inactivity, the
> > password dialog appears. This dialog is no longer appearing. That's the
> > bug.
> > 
> > Giuseppe, there is a workaround to get the password dialog that takes
> > four more button presses than we'd like: press the Close button followed
> > by the Open button and double-click on your database file.
> > 
> > Bill, I *think* I have a compiled PasswordSafe 1.16 from upstream at
> > work that works as expected. I'll double-check the version tomorrow and
> > let you know.
> > 
> > I wonder if this is a GNOME 43 incompatibility...
> > 
> > -- 
> > Bill Wohler  aka 
> > http://www.newt.com/wohler/, GnuPG ID:610BD9AD
> 
> -- 
> Bill Wohler  aka 
> http://www.newt.com/wohler/, GnuPG ID:610BD9AD

-- 
Bill Wohler  aka 
http://www.newt.com/wohler/, GnuPG ID:610BD9AD

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Sebastian Ramacher]

Contro: severity -1 important

On 2023-07-16 18:47:44 +0200, Fabian Greffrath wrote:
> Why the severity? The fonts-liberation2 package is now a transitional package 
> which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy 
> gesendet

I missed that. britney was failing to remove src:fonts-liberation2
from testing for some time now but failed due to installability issues.
Lowering the severity.

Cheers
-- 
Sebastian Ramacher

Bug#1041273: ITP: rust-rustls-webpki -- web PKI X.509 certificate verification

[Jonas Smedegaard]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: rust-rustls-webpki
  Version : 0.101.1
  Upstream Contact: https://github.com/rustls/webpki/issues
* URL : https://github.com/rustls/webpki
* License : ISC
  Programming Lang: Rust
  Description : web PKI X.509 certificate verification

 rustls-webpki is a library
 that validates Web PKI (TLS/SSL) certificates.
 It's used by Rustls to handle certificate-related tasks
 required for implementing TLS clients and servers.
 .
 rustls-webpki is written in Rust
 and uses ring for cryptographic operations and low-level parsing.
 .
 This is a fork of the webpki project
 which adds a number of features required by the rustls project.
 .
 Rustls is a modern TLS library written in Rust.
 .
 This package contains the source for the Rust rustls-webpki crate,
 for use with cargo and dh-cargo.

This package is needed for newer releases of package rust-rustls.
It will be maintained in the collaborative debian section of salsa, at
https://salsa.debian.org/debian/rust-rustls-webpki

 - Jonas
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmS0K0YACgkQLHwxRsGg
ASGn3A/7BP9I756uFtYaFBjDncLCceCNvtgO9QY+J62IdWaXeg5hj55pKDLrMlFb
GS192qei2/y+sEdntXpfv4lgelw2rS9K9F4U3mPMWaiPfsYZSmdER4YwLF4Qlo9H
I5igYRC+vF2VvprNGqTfzErm4hC8OfMTrlPiBV9SM1Dpn7zUTx2XkSpbv22shJ70
b7S93XfOwrfxEeZXSlkm1Pft5uX9XiklmPAabptbec1gDI0ZFGtDMsBvoiMnVVe8
hOhj04YD0Oyv6ky97drRlpECbbdgp/OsLkgqgK1GW9ZWQDf0wi5x2taUIKF3y6fs
f51MlKVMNUG8aendet+Y0lHFGVjzDnqFc39nb2SGloIlCHnkWCLvjjWlxNwhyGwN
0by/hh27Acta01nAJAa/5ArN0hjxFTu/AC3oZR1dRsadXxZZnEVRquz/JHTlrQlc
KeWB8PM1GcdqasKFhH2QNp48x/voo7004Oiq5TfjlBuv1gD3CqDeSZr26+RrhPAI
CuJPTtQTUiZzC7xjPb1jQuf5shEyHTt/e96aVK+RNUAHm66NUf2F79mep042wd+P
c/mmikCPt0p14mkNPTagstB+Bjb2sUdY6bzqqViRZEDakMO7/FNOjK6KucpqAH0C
kQx6PRgIA0YrgjdJDGqaXDApKL8i8uOvdBLUlzzNCphmfrbpZnw=
=Bfnz
-END PGP SIGNATURE-

Bug#1041272: bookworm-pu: package transmission/3.00-2.1+deb12u1

[Sebastian Ramacher]

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

[ Reason ]
transmission in bookworm suffers from a memory leak in bookworm (see
#1015003). This issue was fixed in unstable in the new upstream
releaase.

[ Impact ]
A memory issue remains in a long running daemon.

[ Tests ]
The patch was used in gentoo. Build-time tests pass. As I have no
interest in transmission itself and users reported that the new patch is
supposed to work, I didn't perform any other tests.

[ Risks ]
New patch looks sane enough to load the legacy openssl provider. So I
don't expect any major risks.

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

[ Changes ]
The patch from Ubuntu for OpenSSL compatibility is exchanged with the
one from Gentoo.

Cheers
-- 
Sebastian Ramacher
diff -Nru transmission-3.00/debian/changelog transmission-3.00/debian/changelog
--- transmission-3.00/debian/changelog  2022-05-21 09:22:10.0 +0200
+++ transmission-3.00/debian/changelog  2023-07-16 19:09:31.0 +0200
@@ -1,3 +1,10 @@
+transmission (3.00-2.1+deb12u1) bookworm; urgency=medium
+
+  * debian/patches/: Replace openssl3 compat patch to fix memory leak.
+(Closes: #1015003)
+
+ -- Sebastian Ramacher   Sun, 16 Jul 2023 19:09:31 +0200
+
 transmission (3.00-2.1) unstable; urgency=low
 
   [ Steve Langasek ]
diff -Nru transmission-3.00/debian/patches/openssl3-compat.patch 
transmission-3.00/debian/patches/openssl3-compat.patch
--- transmission-3.00/debian/patches/openssl3-compat.patch  2022-05-21 
09:21:15.0 +0200
+++ transmission-3.00/debian/patches/openssl3-compat.patch  2023-07-16 
19:09:29.0 +0200
@@ -1,130 +1,37 @@
-Description: Compatibility with OpenSSL 3
- We rely on RC4 because of the torrent protocol we're implementing, but this
- is no longer available in the default provider.
-Author: Steve Langasek 
-Bug-Ubuntu: https://bugs.launchpad.net/bugs/1946215
-Last-Update: 2021-12-13
-Forwarded: no
+From 6ee128b95bacaff20746538dc97c2b8e2b9fcc29 Mon Sep 17 00:00:00 2001
+From: Mike Gilbert 
+Date: Sun, 15 May 2022 10:54:38 -0400
+Subject: [PATCH] openssl: load "legacy" provider for RC4
 
-Index: transmission-3.00/libtransmission/crypto-utils-openssl.c
-===
 transmission-3.00.orig/libtransmission/crypto-utils-openssl.c
-+++ transmission-3.00/libtransmission/crypto-utils-openssl.c
+---
+ libtransmission/crypto-utils-openssl.c | 7 +++
+ 1 file changed, 7 insertions(+)
+
+diff --git a/libtransmission/crypto-utils-openssl.c 
b/libtransmission/crypto-utils-openssl.c
+index 45fd71913..14d680654 100644
+--- a/libtransmission/crypto-utils-openssl.c
 b/libtransmission/crypto-utils-openssl.c
 @@ -20,6 +20,9 @@
  #include 
  #include 
  #include 
-+#if OPENSSL_VERSION_NUMBER >= 0x3000L
++#if OPENSSL_VERSION_MAJOR >= 3
 +#include 
 +#endif
  
  #include "transmission.h"
  #include "crypto-utils.h"
-@@ -182,46 +185,86 @@
- 
- #endif
+@@ -184,6 +187,10 @@ static void 
openssl_evp_cipher_context_free(EVP_CIPHER_CTX* handle)
  
-+typedef struct tr_rc4_ctx {
-+EVP_CIPHER_CTX *cipher_ctx;
-+#if OPENSSL_VERSION_NUMBER >= 0x3000L
-+OSSL_LIB_CTX *lib_ctx;
-+#endif
-+} tr_rc4_ctx;
-+
  tr_rc4_ctx_t tr_rc4_new(void)
  {
--EVP_CIPHER_CTX* handle = EVP_CIPHER_CTX_new();
-+#if OPENSSL_VERSION_NUMBER >= 0x3000L
-+OSSL_PROVIDER *legacy_provider = NULL;
-+OSSL_PROVIDER *default_provider = NULL;
-+#endif
-+const EVP_CIPHER *cipher;
- 
--if (check_result(EVP_CipherInit_ex(handle, EVP_rc4(), NULL, NULL, NULL, 
-1)))
-+tr_rc4_ctx *handle = malloc(sizeof(tr_rc4_ctx));
-+
-+handle->cipher_ctx = EVP_CIPHER_CTX_new();
-+
-+#if OPENSSL_VERSION_NUMBER >= 0x3000L
-+handle->lib_ctx = OSSL_LIB_CTX_new();
-+TR_ASSERT(handle->lib_ctx);
-+legacy_provider = OSSL_PROVIDER_load(handle->lib_ctx, "legacy");
-+TR_ASSERT(legacy_provider);
-+default_provider = OSSL_PROVIDER_load(handle->lib_ctx, "default");
-+TR_ASSERT(default_provider);
-+
-+cipher = EVP_CIPHER_fetch(handle->lib_ctx, "RC4", NULL);
-+#else
-+cipher = EVP_rc4();
-+#endif
-+
-+if (check_result(EVP_CipherInit_ex(handle->cipher_ctx, cipher, NULL, NULL,
-+   NULL, -1)))
- {
- return handle;
- }
- 
--EVP_CIPHER_CTX_free(handle);
-+EVP_CIPHER_CTX_free(handle->cipher_ctx);
-+#if OPENSSL_VERSION_NUMBER >= 0x3000L
-+OSSL_LIB_CTX_free(handle->lib_ctx);
-+#endif
- return NULL;
- }
- 
--void tr_rc4_free(tr_rc4_ctx_t handle)
-+void tr_rc4_free(tr_rc4_ctx_t h)
- {
--if (handle == NULL)
-+if (h == NULL)
- {
- return;
- }
- 
--

Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Sebastian Ramacher]

On 2023-07-16 18:24:17 +0100, Simon McVittie wrote:
> On Sun, 16 Jul 2023 at 17:46:04 +0200, Sebastian Ramacher wrote:
> > Dependency installability problem for wike on amd64:
> > 
> > wike build-depends on missing:
> > - libadwaita-1-dev:amd64 (>= 1.3)
> 
> This will be fixed when the newer libadwaita-1-dev in experimental gets
> uploaded to unstable, presumably as part of GNOME 44. We've been delaying
> the upload of most of GNOME 44 to unstable until after the 12.1 point
> release, in order to get more testing for GNOME 43 packages' upstream
> bugfix releases as potential Debian 12 stable updates.
> 
> I think the only way to resolve this in unstable sooner would be to revert
> to wike 1.8.x with a +really version, which is probably not worth it when
> GNOME 44 is on the way anyway.

Yes, sure. But all this sounds like nobody actually tested the uploaded
wike version. The uploads should have gone to experimental …

Cheers
-- 
Sebastian Ramacher

Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Simon McVittie]

On Sun, 16 Jul 2023 at 17:46:04 +0200, Sebastian Ramacher wrote:
> Dependency installability problem for wike on amd64:
> 
> wike build-depends on missing:
> - libadwaita-1-dev:amd64 (>= 1.3)

This will be fixed when the newer libadwaita-1-dev in experimental gets
uploaded to unstable, presumably as part of GNOME 44. We've been delaying
the upload of most of GNOME 44 to unstable until after the 12.1 point
release, in order to get more testing for GNOME 43 packages' upstream
bugfix releases as potential Debian 12 stable updates.

I think the only way to resolve this in unstable sooner would be to revert
to wike 1.8.x with a +really version, which is probably not worth it when
GNOME 44 is on the way anyway.

smcv

Bug#1037190: closed by Debian FTP Masters (reply to Martin-Éric Racine ) (Bug#1037190: fixed in dhcpcd 10.0.1-1)

[Jonathan Wiltshire]

On Sun, Jul 16, 2023 at 07:14:59PM +0300, Martin-Éric Racine wrote:
> > https://release.debian.org/proposed-updates/stable.html
> >
> > Indicates concerns about the version number. The answer is clear: In
> > Testing, dhcpcd5 9.4.1 is superced by dhcpcd 10.0.1 (same binary
> > targets, but src:package drops the 5).
> >
> > The other concern is whether all changes are suitable. They are.
> 
> It also seems that the above page somehow missed bug #1040951 for the request.

The information on that page is currently just placeholder while the freeze
and release of 12.1 is in progress. You can expect a fuller response soon.


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

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

Bug#1037809: With relase 2023.04+ds-1 opm-material was merged into opm-common

[Markus Blatt]

Tags: wontfix

Dear all,

With the upstream release 2023.04 that I am currently uploading the code of
opm-material was merged into opm-common. Therefore there will be no fix for
this in opm-material as it should be removed anyway. Hopefully this will be
done by the autoremoval system without removing the rest of OPM.

Please note that in the recently uploaded version 2023.04+ds-1 of opm-common
(containing the failing code) this particular problem is fixed.

Cheers,

Markus Blatt

Bug#1039911: transition: sdl12-compat taking over libsdl1.2-dev

[Simon McVittie]

On Sun, 16 Jul 2023 at 18:55:28 +0200, Sebastian Ramacher wrote:
> The autopkgtests of libsdl-perl regressed on the 32-bit architectures.

Yes, and also intermittently on some 64-bit architectures, and it
will also FTBFS with the same test failure (reliably on 32-bit or
intermittently on 64-bit). Unfortunately it seems to be reliable (for
whatever reason) on amd64, which is where I did my rebuild-tests.

I already opened  and marked it as
blocking this transition-tracker bug.

> Could you check whether that is an issue in sdl12-compat or
> libsdl-perl?

It's on my list. I've never used these Perl bindings or written Perl/XS
bindings for a C library, so it might take some time.

smcv

Bug#1041271: maildir-utils: public shared library shipped in maildir-utils binary package

[David Bremner]

Package: maildir-utils
Version: 1.8.14-2
Severity: serious
Justification: violates policy 8.1

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I think that libguile-mu.* need to be either moved to a private
directory or to their own packages. I don't know enough about guile to
say which is better.

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

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

Versions of packages maildir-utils depends on:
ii  guile-3.0-libs  3.0.8-2
ii  libc6   2.37-3
ii  libgcc-s1   13.1.0-6
ii  libglib2.0-02.74.6-2
ii  libgmime-3.0-0  3.2.13+dfsg-2
ii  libreadline88.2-1.3
ii  libstdc++6  13.1.0-6
ii  libxapian30 1.4.22-1

maildir-utils recommends no packages.

maildir-utils suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmS0If4ACgkQA0U5G1Wq
FSFdlw//drvAFftKxrrn1Hk+A1wYL0ATPOgwI/61u3sC4P/uQRcTbC6zfJcO/uca
GJVFWaUHIFsmPr3lwQf6KkZweBtdnm38MXsXbxw7uBH5abEKoLPZCEr0FzArfZe/
CaPFMHgCl6/k25BNigIXUcx5rgvoLCjRYrh8RVvrIN/NWfEioYDYqYs4+ZEmswP3
fMOdoqfohtXlisfKrrI/ysK00gJpI0vWYJzdEcapirDy7eMtSBXOqjUz2a3kGJ/h
Oxtg1J1GCSp/pAb3lJvAojxITQI69ZAkX2T6xGqXUhGbRCKjVUulovI0iSQGbwM4
mKDMs5oH6kn8gM9z/HTUpoxhLE85KbMQjtsTx6MoXXZKPat02ipzloc3NqWQyBDj
pL8BEpnU6Hc0MtZLI6Q+gUG1akq5BmB24pKxrcEfAVRSdFXbOjfGIHjyH6achfcn
QwOz6R5kNte4VLfCOvWXhnsDvCeiOfePC/gaVqvvzJR5/iWMovDOdBTshK9uXWkl
3hgwYqRIYRtnKobz8QcOnqTbVxFiJv8gyaOm7cbhzKGfWeMFwv38mhmJXaRj7Znv
zb8MqG2eK89v8ZkD7RxsfVVOGOU94102QwlmQ6QOuB4etVyfuUkjjnRsjJgwSRE1
TtlYcHfIj8M2EgMPWEB2mjcFb/TKlx48+Br53YNk3z6mErYJtZk=
=HGuU
-END PGP SIGNATURE-

Bug#1039911: transition: sdl12-compat taking over libsdl1.2-dev

[Sebastian Ramacher]

Hi Simon

On 2023-07-11 21:36:39 +0100, Simon McVittie wrote:
> On Tue, 11 Jul 2023 at 22:08:55 +0200, Sebastian Ramacher wrote:
> > On 2023-06-29 13:26:03 +0100, Simon McVittie wrote:
> > > As previously mentioned on -devel, I would like src:sdl12-compat to
> > > take over the libsdl1.2-dev and libsdl1.2debian binary package names
> > > from src:libsdl1.2 during the trixie cycle. This mirrors a transition
> > > that already took place in several other distributions such as Fedora
> > > and Arch.
> > 
> > Please go ahead and raise the remaining regression bugs to serious.
> 
> Thanks, I'll upload the equivalent of sdl12-compat/experimental to
> unstable soon.
> 
> In the end none of the build regressions needed raising to RC:
> 
> - #1039479, #1039575, #1039581 have been fixed
> - #1012232, #1039439, #1039574 have workarounds in upstream
>   sdl12-compat, which I backported into Debian already
> 
> The two runtime regressions #1038738, #1038741 are currently tracked as
> bugs in both sdl12-compat and the relevant game (it's not clear which
> side a fix should come from), and I don't think they're bad enough to
> qualify as RC (the game can still be played, and in particular using
> native X11 instead of Xwayland is a workaround).

The autopkgtests of libsdl-perl regressed on the 32-bit architectures.
Could you check whether that is an issue in sdl12-compat or
libsdl-perl?

Cheers
-- 
Sebastian Ramacher

Bug#1041227: transition: suitesparse

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-07-15 23:25:28 +0200, Sébastien Villemot wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: suitespa...@packages.debian.org
> Control: affects -1 + src:suitesparse
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-suitesparse.html
> Control: block -1 by 1041059 1037905 1037622 1040694 1041225 1037858
> 
> Dear Release Team,
> 
> Please schedule a transition for suitesparse 7, which currently sits in
> experimental.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Fabian Greffrath]

Why the severity? The fonts-liberation2 package is now a transitional package 
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy 
gesendet

Bug#1037810: opm-upscaling: ftbfs with GCC-13

[Markus Blatt]

Package: src:opm-upscaling
Version: 2022.10+ds-4

It turned out the bug was not in opm-grid but in dune-geometry which caused
the build here to fail (see bug #1037631). With the upload of version 2.9.0-3 
of dune-geometry we believe that the bug you reported is fixed.


Cheers,

Markus Blatt

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Fabian Greffrath]

Why the severity? The fonts-liberation2 package is now a transitional package 
which pulls in the actual fonts-liberation package. Von meinem/meiner Galaxy 
gesendet

Bug#1041270: dynarmic: broke ABI without SONAME bump

[Sebastian Ramacher]

Source: dynarmic
Version: 6.4.8+ds-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/y/yuzu/35884387/log.gz

 60s yuzu-cmd: symbol lookup error: yuzu-cmd: undefined symbol: 
_ZN8Dynarmic3A327Context4RegsEv

Cheers
-- 
Sebastian Ramacher

Bug#1041269: hamster-time-tracker: hamster does not start

[Ulrike Uhlig]

Package: hamster-time-tracker
Version: 3.0.2-4
Severity: important

Dear Maintainer,

I installed hamster-time-tracker on a fresh installation of bookworm.

   * What led up to the situation?

Trying to launch hamster from either command line or Gnome, the program fails
to start.

   * What was the outcome of this action?

See errors related to dbus here: http://paste.debian.net/1286041/

   * What outcome did you expect instead?

I expect hamster to run out of the box or give me an actually readable error
message that doesn't require yakshaving :)


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

Kernel: Linux 6.1.0-10-amd64 (SMP w/4 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 hamster-time-tracker depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-gtk-3.0   3.24.37-2
ii  libjs-jquery 3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-ui  1.13.2+dfsg-1
ii  python3  3.11.2-1+b1
ii  python3-cairo1.20.1-5+b1
ii  python3-dbus 1.3.2-4+b1
ii  python3-distutils3.11.2-3
ii  python3-gi   3.42.2-3+b1
ii  python3-xdg  0.28-2

Versions of packages hamster-time-tracker recommends:
ii  gnome-shell-extension-hamster  0.10.0+git20210628-4
ii  yelp   42.2-1

hamster-time-tracker suggests no packages.

-- no debconf information

Bug#1041268: RM: qtwebengine-opensource-src [mipsel] -- RoQA; FTBFS on mipsel

[Sebastian Ramacher]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: qtwebengine-opensource-...@packages.debian.org
Control: affects -1 + src:qtwebengine-opensource-src
Control: block -1 by 1041266 1041265 1041267

qtwebengine-opensource-src currently FTBFS on mipsel (#1041250). Please
remove it from mipsel so that we can complete the Qt tranistion.

Cheers
-- 
Sebastian Ramacher

Bug#1041267: RM: angelfish [mipsel] -- RoQA; qtwebengine-opensource-src FTBFS on mipsel

[Sebastian Ramacher]

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

qtwebengine-opensource-src currently FTBFS on mipsel and thus angelfish
is BD-Uninstallabe. Please remove it from mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041266: RM: qtwebview-opensource-src [mipsel] -- RoQA; qtwebengine-opensource-src FTBFS on mipsel

[Sebastian Ramacher]

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

qtwebengine-opensource-src currently FTBFS on mipsel and thus
qtwebview-opensource-src is BD-Uninstallabe. Please remove it from
mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041260: wike ftbfs

[Matthias Geiger]

Hi Sebastian,

this happened due to an untimely upload of mine. The required libadwaita 
(1.3) is already in experimental; according to the GNOME team they won't 
upload it until after the bookworm 12.1


update. For now all we can do is wait.

cheers

--
Matthias Geiger (werdahias)


OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#943728: policycoreutils-dev: do not depend on binutils

[Christian Göttsche]

The included python script generate.py calls nm(1) from binutils.

Maybe the file-split into binary packages could be changed, since I am
mainly interested in sepolgen-ifgen and sepolgen-ifgen-attr-helper,
which have no dependency on binutils.

Bug#1037190: closed by Debian FTP Masters (reply to Martin-Éric Racine ) (Bug#1037190: fixed in dhcpcd 10.0.1-1)

[Martin-Éric Racine]

On Sun, Jul 16, 2023 at 7:07 PM Martin-Éric Racine
 wrote:
>
> On Fri, Jul 14, 2023 at 9:59 AM Martin-Éric Racine
>  wrote:
> >
> > On Thu, Jul 13, 2023 at 8:15 AM Martin-Éric Racine
> >  wrote:
> > >
> > > On Thu, Jul 13, 2023 at 8:01 AM Martin-Éric Racine
> > >  wrote:
> > > >
> > > > On Thu, Jul 13, 2023 at 3:21 AM Andreas Beckmann  
> > > > wrote:
> > > > >
> > > > > On 11/07/2023 07.05, Martin-Éric Racine wrote:
> > > > > >> This is what I would push to stable-proposed-updates (see 
> > > > > >> attachment).
> > > > > >> Would this do the trick? If yes, I can upload to Mentors. If not,
> > > > > >> please explain.
> > > > > >
> > > > > > Package waiting on Mentors.
> > > > >
> > > > > Looks good. Minor nitpicks:
> > > > > - in d/changelog: use "bookworm" instead of "stable-proposed-updates"
> > > > > - close the bug #1037190
> > > > >
> > > > > Can you put the commits in a new debian/bookworm branch on salsa,
> > > > > starting from tag debian/9.4.1-24?
> > > > >
> > > > > I'll sponsor that upload for you.
> > > >
> > > > E: dhcpcd5 changes: bad-distribution-in-changes-file bookworm
> > > >
> > > > Re-uploaded to Mentors.
> > >
> > > Scratch that. Mentors doesn'r know about any release newer than
> > > Bullseye and rejected the upload. Debdiff attached.
> > >
> > > Martin-Éric
> > >
> > > PS: I don't know how to fork a branch on Git. My Git skills are minimal.
> >
> > It seems that they finally fixed Mentors. Upload accepted.
> >
> > https://mentors.debian.net/debian/pool/main/d/dhcpcd5/dhcpcd5_9.4.1-24+deb12u1.dsc
>
> https://release.debian.org/proposed-updates/stable.html
>
> Indicates concerns about the version number. The answer is clear: In
> Testing, dhcpcd5 9.4.1 is superced by dhcpcd 10.0.1 (same binary
> targets, but src:package drops the 5).
>
> The other concern is whether all changes are suitable. They are.

It also seems that the above page somehow missed bug #1040951 for the request.

Martin-Éric

Bug#1041265: gammaray: stop depending on qtwebengine5-dev on mipsel

[Sebastian Ramacher]

Source: gammaray
Version: 2.11.3-3
Severity: serious
Tags: sid trixie

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041264: fonts-recommended: depends on removed fonts-liberation2

[Sebastian Ramacher]

Source: fonts-recommended
Version: 1
Severity: serious
Tags: sid trixie

One or more binary packages produced by fonts-recommended depends on
fonts-liberation2. The font is now provided by fonts-liberation. See
#1038940. Please update the dependency.

Cheers
-- 
Sebastian Ramacher

Bug#995619: helvum now waiting in NEW queue

[Jonas Smedegaard]

helvum is now in NEW queue, since June 29th: 
https://ftp-master.debian.org/new/helvum_0.4.0-1.html

 - 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#1037190: closed by Debian FTP Masters (reply to Martin-Éric Racine ) (Bug#1037190: fixed in dhcpcd 10.0.1-1)

[Martin-Éric Racine]

On Fri, Jul 14, 2023 at 9:59 AM Martin-Éric Racine
 wrote:
>
> On Thu, Jul 13, 2023 at 8:15 AM Martin-Éric Racine
>  wrote:
> >
> > On Thu, Jul 13, 2023 at 8:01 AM Martin-Éric Racine
> >  wrote:
> > >
> > > On Thu, Jul 13, 2023 at 3:21 AM Andreas Beckmann  wrote:
> > > >
> > > > On 11/07/2023 07.05, Martin-Éric Racine wrote:
> > > > >> This is what I would push to stable-proposed-updates (see 
> > > > >> attachment).
> > > > >> Would this do the trick? If yes, I can upload to Mentors. If not,
> > > > >> please explain.
> > > > >
> > > > > Package waiting on Mentors.
> > > >
> > > > Looks good. Minor nitpicks:
> > > > - in d/changelog: use "bookworm" instead of "stable-proposed-updates"
> > > > - close the bug #1037190
> > > >
> > > > Can you put the commits in a new debian/bookworm branch on salsa,
> > > > starting from tag debian/9.4.1-24?
> > > >
> > > > I'll sponsor that upload for you.
> > >
> > > E: dhcpcd5 changes: bad-distribution-in-changes-file bookworm
> > >
> > > Re-uploaded to Mentors.
> >
> > Scratch that. Mentors doesn'r know about any release newer than
> > Bullseye and rejected the upload. Debdiff attached.
> >
> > Martin-Éric
> >
> > PS: I don't know how to fork a branch on Git. My Git skills are minimal.
>
> It seems that they finally fixed Mentors. Upload accepted.
>
> https://mentors.debian.net/debian/pool/main/d/dhcpcd5/dhcpcd5_9.4.1-24+deb12u1.dsc

https://release.debian.org/proposed-updates/stable.html

Indicates concerns about the version number. The answer is clear: In
Testing, dhcpcd5 9.4.1 is superced by dhcpcd 10.0.1 (same binary
targets, but src:package drops the 5).

The other concern is whether all changes are suitable. They are.

Martin-Éric

Martin-Éric

Bug#1041263: fontconfig: depends on removed fonts-liberation2

[Sebastian Ramacher]

Source: fontconfig
Version: 2.14.1-4
Severity: serious
Tags: sid trixie

One or more binary packages produced by fontconfig depends on
fonts-liberation2. The font is now provided by fonts-liberation. See
#1038940. Please update the dependency.

Cheers
-- 
Sebastian Ramacher

Bug#1009027: mesa: Please enable these new drivers and features available since mesa 22

[Fabio Pedretti]

> There is also the VULKAN_DRIVERS virtio-experimental , I don't know
> however if it's ready for use (archlinux ships it
> https://bbs.archlinux.org/viewtopic.php?id=265471 ).

Since 23.2 virtio-experimental was renamed upstream to virtio and is
no longer considered experimental:
https://cgit.freedesktop.org/mesa/mesa/commit?id=7d76038712ea099424e906d8a4c19ad5c932f7e3
https://cgit.freedesktop.org/mesa/mesa/commit/?id=bdc82f52d7d16b05a9922534be00fba39e3a1c5b

Bug#1041262: casparcg-server: dependens on removed fonts-liberation2

[Sebastian Ramacher]

Source: casparcg-server
Version: 2.3.3+dfsg-3
Severity: serious
Tags: sid trixie

One or more binary packages produced by casparcg-server depends on
fonts-liberation2. The font is now provided by fonts-liberation. See
#1038940. Please update the dependency.

Cheers
-- 
Sebastian Ramacher

Bug#1041261: live-build does not build debian bookworm images

[Илья Пащук]

Package: live-build

Version: 1:20230502



steps to reproduce:

1) make a clean install of Debian 12

2) install the live-build package from the normal repository

3) run "lb config" to create a build tree

expected behavior: tree for bookworm should be made

actual: tree for bullseye is made by default


stage 2:

remove created files, then run:

lb config -d bookworm

to force generation for an appropriat distro


then run lb build

expected: build should complete successfully.

actual: build fails with the following error message:

E: Package 'firmware-linux' has no installation candidate


as I know, this bug is fixed already in newer versions of live-build, 
but the packaged version is not updated to get this fix, which is 
expected to be done through the updates channel.

Bug#1041260: wike: BD-Uninstallable: libadwaita-1-dev:amd64 (>= 1.3)

[Sebastian Ramacher]

Source: wike
Version: 2.0.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/package.php?p=wike=sid

Dependency installability problem for wike on amd64:

wike build-depends on missing:
- libadwaita-1-dev:amd64 (>= 1.3)


Cheers
-- 
Sebastian Ramacher

Bug#1041259: freedv: FTBFS: lpcnet_freedv.h: No such file or directory

[Sebastian Ramacher]

Source: freedv
Version: 1.8.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=freedv=amd64=1.8.11-1%2Bb2=1689518012=0

[ 95%] Building CXX object src/CMakeFiles/freedv.dir/ongui.cpp.o
cd /<>/Build/src && /usr/bin/c++ -DAUDIO_ENGINE_PULSEAUDIO_ENABLE 
-DGIT_HASH=\"None\" -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-I/<>/src -I/<>/Build/src -I/<>/Build 
-isystem /usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -isystem /usr/include/codec2 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -pthread -O2 -g 
-DNDEBUG -std=c++14 -MD -MT src/CMakeFiles/freedv.dir/ongui.cpp.o -MF 
CMakeFiles/freedv.dir/ongui.cpp.o.d -o CMakeFiles/freedv.dir/ongui.cpp.o -c 
/<>/src/ongui.cpp
/<>/src/ongui.cpp:8:10: fatal error: lpcnet_freedv.h: No such file 
or directory
8 | #include "lpcnet_freedv.h"
  |  ^
compilation terminated.
make[3]: *** [src/CMakeFiles/freedv.dir/build.make:345: 
src/CMakeFiles/freedv.dir/ongui.cpp.o] Error 1
Cheers
-- 
Sebastian Ramacher

Bug#1041258: rust-fs-extra: FTBFS: test failures

[Sebastian Ramacher]

Source: rust-fs-extra
Version: 1.3.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=rust-fs-extra=amd64=1.3.0-1=1688994742=0


failures:
it_copy_progress_work

it_copy_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_copy_with_progress_inside_work_target_dir_not_exist
it_copy_with_progress_work_dif_buf_size
it_get_dir_content
it_get_dir_content_many_levels

it_move_dir_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_move_dir_with_progress_inside_work_target_dir_not_exist
it_move_progress_work
it_move_with_progress_work_dif_buf_size

test result: FAILED. 68 passed; 14 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 0.05s

error: test failed, to rerun pass `--test dir`
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 25


Cheers
-- 
Sebastian Ramacher

Bug#1041257: flatbuffers: FTBFS on amd64: symbol differences

[Sebastian Ramacher]

Source: flatbuffers
Version: 2.0.8+dfsg1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=flatbuffers=amd64=2.0.8%2Bdfsg1-3=1689315457=0

+++ dpkg-gensymbols01uTG6   2023-07-14 06:17:31.308919257 +
@@ -286,6 +286,8 @@
  (optional=templinst)_ZNK11flexbuffers9Reference8AsDoubleEv@Base 
1.12.0~git20200706.969d0f7
  (optional=templinst)_ZNK11flexbuffers9Reference8AsUInt64Ev@Base 
1.12.0~git20200706.969d0f7
  _ZNKSt5ctypeIcE8do_widenEc@Base 1.12.0~git20200706.969d0f7
+ _ZNSt12_Vector_baseIjSaIjEED1Ev@Base 2.0.8+dfsg1-3
+ _ZNSt12_Vector_baseIjSaIjEED2Ev@Base 2.0.8+dfsg1-3
  _ZNSt14_Function_baseD1Ev@Base 2.0.8
  _ZNSt14_Function_baseD2Ev@Base 2.0.8
  
_ZNSt17_Function_handlerIFccEPS0_E10_M_managerERSt9_Any_dataRKS3_St18_Manager_operation@Base
 2.0.8
@@ -293,8 +295,8 @@
  
(optional=templinst)_ZNSt3setISt4pairIN11flatbuffers8BaseTypeEPNS1_9StructDefEESt4lessIS5_ESaIS5_EE6insertEOS5_@Base
 1.12.0~git20200706.969d0f7
  
(optional=templinst)_ZNSt6vectorIN11flexbuffers7Builder5ValueESaIS2_EE17_M_default_appendEm@Base
 1.12.1~git20200711.33e2d80
  (optional=templinst)_ZNSt6vectorIhSaIhEE17_M_default_appendEm@Base 
1.12.1~git20200711.33e2d80
- _ZNSt6vectorIjSaIjEED1Ev@Base 2.0.8
- _ZNSt6vectorIjSaIjEED2Ev@Base 2.0.8
+#MISSING: 2.0.8+dfsg1-3# _ZNSt6vectorIjSaIjEED1Ev@Base 2.0.8
+#MISSING: 2.0.8+dfsg1-3# _ZNSt6vectorIjSaIjEED2Ev@Base 2.0.8
  
_ZNSt8_Rb_treeIN11flatbuffers12IncludedFileES1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE24_M_get_insert_unique_posERKS1_@Base
 2.0.8
  
(optional=templinst)_ZNSt8_Rb_treeIN11flatbuffers6OffsetINS0_6StringEEES3_St9_IdentityIS3_ENS0_17FlatBufferBuilder19StringOffsetCompareESaIS3_EE16_M_insert_uniqueIRKS3_EESt4pairISt17_Rb_tree_iteratorIS3_EbEOT_@Base
 1.12.0~git20200706.969d0f7
  
(optional=templinst)_ZNSt8_Rb_treeISt4pairImmES1_St9_IdentityIS1_EN11flexbuffers7Builder19StringOffsetCompareESaIS1_EE16_M_insert_uniqueIRKS1_EES0_ISt17_Rb_tree_iteratorIS1_EbEOT_@Base
 1.12.1~git20200711.33e2d80
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:11: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

[Ansgar]

On Sun, 2023-07-16 at 12:54 +0100, Simon McVittie wrote:
> On Sun, 16 Jul 2023 at 12:42:11 +0100, Luca Boccassi wrote:
> > In the meanwhile, I'll immediately revert the sabotage.
> 
> Both of you, please don't turn this into an NMU war in the archive:
> that doesn't benefit anyone. I would have preferred it if Adam had not
> immediately uploaded a 0-day revert, but preserving the status quo from
> bookworm is not the worst state to be in while we discuss this.

No, we should just have made a decision a long time ago and not go back
and forth the entire time. That we do not do that shows lack of
leadership in Debian.

(And yes, you can reconsider stuff, but the barrier to stop a process
and reconsider it again should not be zero and probably higher the
later one does block progress.)

> If Adam's concerns about this change are valid, then we should address
> them, either by doing something different in debootstrap or by reporting
> bugs against affected packages.

I guess Adam could go ahead with the GR he wanted to bring up the last
time he did NMUs this way (for reverting enabling usrmerge by default
on upgrades).  I would like to ask Adam to stop interfering with
usrmerge until that long announced GR is there (and note that if we
waited for that GR to happen as Adam demanded then we would still be
waiting).

> If Adam's concerns about this change turn out to be unfounded, then we
> should reinstate my change (as NMU'd by Luca) in a calm and considered
> way, and all we will have lost is a few days of progress and a few bytes
> of changelog.

That is false in so far as that only considers technical changes we
get. However we also lose more and more energy/motivation/* even if we
eventually go ahead as planned, i.e., social costs are not considered,
but should be (IMHO).

Ansgar

Bug#1034348: at: autopkgtest regression on arm64

[Jose M Calhariz]

Hi, I believe my last update fixed the problem can someone double check?

Kind regards
Jose M Calhariz


On July 7, 2023 11:26:22 AM GMT+01:00, Jose M Calhariz  
wrote:
>I too think it's a race condition. I made some changes to the test but the 
>upload to Debian did not went well.
>
>
>On July 6, 2023 2:12:59 PM GMT+01:00, Vincent Lefevre  
>wrote:
>>On 2023-07-05 18:58:13 +0200, Johannes Christ wrote:
>>> Is there another way to reproduce this issue?
>>
>>I'm wondering whether there is a race condition in the test:
>>
>># use at command to schedule a job.
>>echo "echo `date` > ${WORKDIR}/${TMPFILE}" | at now + 1 minute
>>
>>So the file is expected to be created 1 minute later.
>>
>>Then in the script:
>>
>>sleep 2
>>
>>[...]
>>
>>sleep 58
>>
>>if grep -Fq "UTC" $WORKDIR/$TMPFILE
>>
>>[...]
>>
>>So the script waits for 1 minute (and some other fast commands)
>>before checking the existence of the file, which is the wait time
>>given to "at".
>>
>>I can see 2 possible issues:
>>
>>1. The system is a bit slow, and the job execution will take a bit
>>more time.
>>
>>2. Time inaccuracies. What are the guaranties given by the system?
>>
>>-- 
>>Vincent Lefèvre  - Web: 
>>100% accessible validated (X)HTML - Blog: 
>>Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1041254: docker.io: FTBFS: test failures

[Shengjing Zhu]

Control: forwarded -1 https://github.com/moby/moby/pull/45972

On Sun, Jul 16, 2023 at 10:51 PM Sebastian Ramacher
 wrote:
>
> Source: docker.io
> Version: 20.10.24+dfsg1-1
> Severity: serious
> Tags: ftbfs sid trixie
> Justification: fails to build from source (but built successfully in the past)
>
> https://buildd.debian.org/status/fetch.php?pkg=docker.io=amd64=20.10.24%2Bdfsg1-1%2Bb4=1689240350=0
>

FTR, it's caused by golang-1.20 1.20.6-1, a security patch release
which restricts http header.
Should be fixed by https://github.com/moby/moby/pull/45972

-- 
Shengjing Zhu

Bug#1041255: librubberband-dev: missing dependency on libfftw3-dev

[Sebastian Ramacher]

Package: librubberband-dev
Version: 3.2.1+dfsg-5
Severity: serious
Control: affects -1 src:ffmpeg

$ pkgconf --modversion rubberband
Package fftw3 was not found in the pkg-config search path.
Perhaps you should add the directory containing `fftw3.pc'
to the PKG_CONFIG_PATH environment variable
Package 'fftw3', required by 'rubberband', not found

This issue causes ffmpeg to FTBFS. Please add the missing dependency on
libfftw3-dev.

Cheers
-- 
Sebastian Ramacher

Bug#1041254: docker.io: FTBFS: test failures

[Sebastian Ramacher]

Source: docker.io
Version: 20.10.24+dfsg1-1
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=docker.io=amd64=20.10.24%2Bdfsg1-1%2Bb4=1689240350=0

=== Failed
=== FAIL: pkg/authorization TestAuthZRequestPluginError (15.01s)
time="2023-07-13T09:24:27Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:24:28Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 2s"
time="2023-07-13T09:24:30Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 4s"
time="2023-07-13T09:24:34Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz381024824/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 8s"
authz_unix_test.go:51: Failed to authorize request Post 
"http://%2F%2Ftmp%2Fauthz381024824%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq":
 http: invalid Host header

=== FAIL: pkg/authorization TestAuthZRequestPlugin (15.00s)
time="2023-07-13T09:24:42Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:24:43Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 2s"
time="2023-07-13T09:24:45Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 4s"
time="2023-07-13T09:24:49Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3777015250/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 8s"
authz_unix_test.go:83: Failed to authorize request Post 
"http://%2F%2Ftmp%2Fauthz3777015250%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq":
 http: invalid Host header

=== FAIL: pkg/authorization TestAuthZResponsePlugin (15.01s)
time="2023-07-13T09:24:57Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:24:58Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 2s"
time="2023-07-13T09:25:00Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 4s"
time="2023-07-13T09:25:04Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz3358757484/authz-test-plugin.sock/AuthZPlugin.AuthZRes: Post 
\"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes\":
 http: invalid Host header, retrying in 8s"
authz_unix_test.go:113: Failed to authorize request Post 
"http://%2F%2Ftmp%2Fauthz3358757484%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZRes":
 http: invalid Host header

=== FAIL: pkg/authorization TestMiddlewareWrapHandler/Positive_Test_Case_: 
(15.01s)
time="2023-07-13T09:25:27Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz2461853618/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz2461853618%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 1s"
time="2023-07-13T09:25:28Z" level=warning msg="Unable to connect to plugin: 
//tmp/authz2461853618/authz-test-plugin.sock/AuthZPlugin.AuthZReq: Post 
\"http://%2F%2Ftmp%2Fauthz2461853618%2Fauthz-test-plugin.sock/AuthZPlugin.AuthZReq\":
 http: invalid Host header, retrying in 2s"

Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Christoph Anton Mitterer]

On Sun, 2023-07-16 at 16:25 +0200, Fabian Greffrath wrote:
> Do you have the heif-gdk-pixbuf package installed? 

Yes:

On Sun, 2023-07-16 at 14:25 +0200, Christoph Anton Mitterer wrote:
> With libheif1, heif-gdk-pixbuf and heif-thumbnailer installed, I was


Cheers,
Chris.

Bug#1041253: pyside2: stop depending on qtwebengine5-dev on mipsel

[Sebastian Ramacher]

Source: pyside2
Version: 5.15.10-2
Severity: serious

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

[Vagrant Cascadian]

On 2023-07-16, Simon McVittie wrote:
> On Sat, 15 Jul 2023 at 18:27:24 +0200, Adam Borowski wrote:
>> But, what matters here is the CTTE ruling in #1035831 -- for the time being,
>> packages must not move files between locations affected by the aliasing.
>
> If that happens in reality, then yes, that's bad, and reverting the change
> is a mitigation. What packages have this behaviour?
>
> We are going to need to bring back this change relatively early in the
> trixie cycle in any case, for the reasons given in the commit message.
> I have not yet analyzed whether we need this change before we can lift
> the moratorium on file moves, but I suspect we might.
>
>> Packages built in an usrmerged chroot place such files under /usr while
>> built without usrmerge into whatever place they were installed to -- which
>> is a direct breach of the ruling.
>
> Do you have examples of packages that differ in this way when built in
> a merged- or unmerged-/usr environment? I think we should treat this
> as a RC-for-trixie bug in those packages (and in fact I would have been
> tempted to call it RC for bookworm as well, again for the reasons given
> by the TC, even though during the trixie cycle it was mitigated by using
> unmerged-/usr fro buildds).
>
> During most of the bookworm cycle, https://reproducible-builds.org/ has
> been doing "build1" in unmerged-/usr and "build2" in merged-/usr, with
> differences tracked in
> 
> (that list is not necessarily complete, there can also be unidentified
> differences in
> ).

For what it is worth, there were various points during the bookworm
cycle where this was not being tested on reproducible builds
infrastructure, as the mechanisms to disable it changed several
times...

We used to just be able to build a non-usrmerge tarball, and then
install usrmerge in the second build, but I think usr-is-merged or some
similar package is installed out of the box now, and the inverse
operation is non-trivial.

... which lead to some of the identified issues being systematically
removed for packages that were otherwise reproducible (you could still
look through git history to find more, but some many may be actually
fixed).

There are differing opinions on weather reproducible builds test
infrastrure should test usrmerge variations at all, given the direction
of Debian, though any alternate test infrastructure would essentially
have to implement a reproducible builds style test to check for
differences...

After upgrading the infrastructure to bookworm, testing usrmerge
variations broke again, and so is currently disabled... though I have
configured the paths_vary_due_to_usrmerge issue so that old known issues
are not automatically removed anymore.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1041252: libksysguard: stop depending on qtwebengine5-dev on mipsel

[Sebastian Ramacher]

Source: libksysguard
Version: 4:5.27.5-2
Severity: serious

qtwebengine-opensource-src currently FTBFS on mipsel (see #1041250). To
complete the currently ongoing Qt transition, please disable support for
qtwebeninge-opensource-src on mipsel for the time being. This would
allow us to (temporarily) remove qtwebengine-opensource-src from mipsel.

Cheers
-- 
Sebastian Ramacher

Bug#1041251: rust-rustls-pemfile: please update to v1.0.3

[Jonas Smedegaard]

Source: rust-rustls-pemfile
Version: 1.0.2-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to at least v1.0.3, needed by newer releases of
rust-rustls.

 - Jonas
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmSz/t0ACgkQLHwxRsGg
ASEEZRAAnBjK2gkehQ9wT0V6CcYs68w7ZUhaZJWnnrgSRJEmi1IF8b0wWj3sd9rX
j+EMCBIB9HNRYwv/j07JEDEYCHF40h+/4NSqPCzv9klSMPtfeQFS2Iuk5MVoDIZr
qrhGLoetfNW+tHecrbYPfylVObfUZBmg1l0Xf8Z5bs23Y57ET/5Sy+DOyhPyD26b
J18qmlsT612IfxyTOq0xK8meKC5/W6B3EYRKPhdAgq+l3yJKaYU5IulX2ZIQeUxw
WFDt8mt44JfSvJk9P7V9MJrNKen9eY6QnljGUNWdKFpr6z48mS7fmpLj5le7WsoT
+lv9/rcv0o4KpUgA/5V0M6H+NIQ07sSr+dVS9XHJitAYOvn6N2bf6LzseJx+HbB8
Drehm2zsvTU7c065hGzuGcIuSrP3OHavFVeUaE3Ggjiy5jjdU0v4Dcg2P4bQdk2X
HxmwVXeebs5HjvpFOltKkbS/iqFMWAIxw1nl/z6ugPnYEzJdSYILk2XybiLxHYWI
JXinJNFIC0qHUD3fuUGJQRRHFgzJzFRdGtYpgscQ8zr3KhnVEPoBygXvIEymO35+
EG4rHqWlzBiUK+dUv0GiTH8XjtdRDGRm6iXQvVnQjvWOxVoOFco4xhP2m30zKNlN
5Xj2rNIVjutSBGBqlS9haq0EW3fEqYhC8w6YCtAHNUzn6QYstpk=
=auNE
-END PGP SIGNATURE-

Bug#1041010: [Pkg-javascript-devel] Bug#1041010: Bug#1041010: Please include nbconvert-css

[Julian Gilbey]

On Fri, Jul 14, 2023 at 07:19:42AM +0400, Yadd wrote:
> On 7/14/23 01:40, Julian Gilbey wrote:
> > Package: node-jupyterlab
> > Version: 4.0.0~rc1+ds1+~1.0.2-1
> > Severity: wishlist
> > 
> > Hi Yadd!
> > 
> > Thanks for building this package!
> > 
> > [...]
> > 
> > For some reason, nbconvert-css is excluded from the package.  Might it
> > be possible to include it?
> > 
> > Best wishes,
> 
> Hi,
> 
> I put node-jupyterlab into experimental because it's still WIP. For now I'm
> not able to build all @jupyterlab/* components due to missing dependencies.
> I'll continue this during autumn.

Hi Yadd,

Thanks for the info!  I'm taking a further look at this now and will
report back when I have more information (hopefully soon).

I also see that two dependencies of node-jupyterlab are sitting in the
NEW queue.

So spyder will just have to drop out of testing for a while.  C'est la
vie!  (I updated nbclient and the nbconvert tests fail with the newer
nbclient, so I'm trying to update nbconvert, but that's proving to be
a bit of a headache)

Best wishes,

   Julian

Bug#1041242: libheif1: 1.16.2-1+b1 breaks displaying any pictures

[Fabian Greffrath]

Do you have the heif-gdk-pixbuf package installed? Von meinem/meiner Galaxy 
gesendet

Bug#1040842: transition: libfm-qt

[Sebastian Ramacher]

Control: block -1 by 1026933
Contrl: forwarded -1 
https://release.debian.org/transitions/html/auto-libfm-qt.html

On 2023-07-11 20:35:28 +0800, ChangZhuo Chen wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: libfm...@packages.debian.org, team+l...@tracker.debian.org
> Control: affects -1 + src:libfm-qt
> 
> libfm-qt has bumped its soversion from 12 to 13, and so we need a transition

This tranistion needs to wait for currently onoing Qt transition to be
completed first.

Cheers
-- 
Sebastian Ramacher

Bug#1040787: dh-elpa: Lots of missing eln files

[Sean Whitton]

Hello,

On Sun 16 Jul 2023 at 12:06pm +01, Nikolaus Rath wrote:

> Hmm. I think the problem is not that the various elpa packages did not
> get installed correctly, but that they did not get removed fully. So
> I'll skip this step for now in an attempt to preserve the current state.

Yes, I think that's right.  The .elc should not have been left behind
when you removed elpa-async.  There isn't really enough information here
to try to fix whatever caused that.  Let us know if you are able to
reproduce.

-- 
Sean Whitton

Bug#1040787: dh-elpa: Lots of missing eln files

[Sean Whitton]

Hello,

On Sun 16 Jul 2023 at 10:52am +01, Nikolaus Rath wrote:

> No. It seems these files got orphaned during the upgrade:

The .elc files do not ship in the .deb, so it's not a case of orphaning.

-- 
Sean Whitton

Bug#1041250: qtwebengine-opensource-src: FTBFS on mipsel

[Sebastian Ramacher]

Source: qtwebengine-opensource-src
Version: 5.15.14+dfsg-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mipsel=5.15.14%2Bdfsg-3=1687417516=0
https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mipsel=5.15.14%2Bdfsg-4=1688914864=0
https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mipsel=5.15.14%2Bdfsg-5=1688996139=0
https://buildd.debian.org/status/fetch.php?pkg=qtwebengine-opensource-src=mipsel=5.15.14%2Bdfsg-6=1689327354=0

rm -f libQt5WebEngineCore.so.5.15.14 libQt5WebEngineCore.so 
libQt5WebEngineCore.so.5 libQt5WebEngineCore.so.5.15
g++ -Wl,-z,relro -Wl,--no-keep-memory -Wl,-z,now 
@/<>/src/core/release/QtWebEngineCore_o.rsp -Wl,--start-group 
@/<>/src/core/release/QtWebEngineCore_a.rsp -Wl,--end-group 
-Wl,-z,noexecstack -Wl,--fatal-warnings -Wl,--build-id=sha1 -fPIC -Wl,-z,relro 
-Wl,-z,now -Wl,-z,defs -Wl,--hash-style=sysv -mips32 -Wl,-O2 -Wl,--gc-sections 
-rdynamic -Wl,-z,relro -Wl,--no-keep-memory -Wl,-z,now -Wl,-O1 
-Wl,--enable-new-dtags -Wl,-whole-archive -lqtwebenginecoreapi 
-Wl,-no-whole-archive -Wl,--no-undefined 
-Wl,--version-script,QtWebEngineCore.version -Wl,-O1 -fuse-ld=gold 
-Wl,--enable-new-dtags -shared -Wl,-soname,libQt5WebEngineCore.so.5 -o 
libQt5WebEngineCore.so.5.15.14   /usr/lib/mipsel-linux-gnu/libQt5Quick.so 
/usr/lib/mipsel-linux-gnu/libQt5Gui.so 
/usr/lib/mipsel-linux-gnu/libQt5QmlModels.so 
/usr/lib/mipsel-linux-gnu/libQt5WebChannel.so 
/usr/lib/mipsel-linux-gnu/libQt5Qml.so 
/usr/lib/mipsel-linux-gnu/libQt5Network.so 
/usr/lib/mipsel-linux-gnu/libQt5Positioning.so 
/usr/lib/mipsel-linux-gnu/libQt5Core.so -lpthread -latomic -lGL -lpthread 
-latomic -ldl -lrt -licui18n -licuuc -licudata -lnss3 -lnssutil3 -lsmime3 
-lplds4 -lplc4 -lnspr4 -lz -levent -lresolv -ljpeg -lm -lopus -lvpx -lX11 
-lXcomposite -lXdamage -lXext -lXfixes -lXrender -lXrandr -lXtst -lgio-2.0 
-lgobject-2.0 -lglib-2.0 -lpng16 -lwebpmux -lwebpdemux -lwebp -lfreetype 
-lexpat -lfontconfig -lharfbuzz-subset -lharfbuzz -lre2 -lX11-xcb -lxcb 
-lxkbcommon -ldbus-1 -lpci -lasound -lsnappy -lxml2 -lxslt -lminizip -llcms2 
-lopenjp2 -L/<>/src/core/api/release -lGL   
/usr/bin/ld.gold: fatal error: libQt5WebEngineCore.so.5.15.14: mmap: failed to 
allocate 216082048 bytes for output file: Cannot allocate memory
collect2: error: ld returned 1 exit status
make[5]: *** [Makefile.core_module:90: 
../../lib/libQt5WebEngineCore.so.5.15.14] Error 1

Cheers
-- 
Sebastian Ramacher

Bug#870886: 'passward' spelled wrong

[sq9ybv+6t32455pzuxds]

Package: libsecret-tools
Followup-For: Bug #870886

These typos don't exist in the manpage on bookworm. Bug can be closed.

Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure

[Sebastian Ramacher]

Source: cpp-httplib
Version: 0.13.1+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

https://buildd.debian.org/status/fetch.php?pkg=cpp-httplib=s390x=0.13.1%2Bds-1=1689418150=0

[--] 1 test from InvalidScheme
[ RUN  ] InvalidScheme.SimpleInterface
[   OK ] InvalidScheme.SimpleInterface (0 ms)
[--] 1 test from InvalidScheme (0 ms total)

[--] 1 test from NoScheme
[ RUN  ] NoScheme.SimpleInterface
[   OK ] NoScheme.SimpleInterface (0 ms)
[--] 1 test from NoScheme (0 ms total)

[--] 1 test from ClientImplMethods
[ RUN  ] ClientImplMethods.GetSocketTest
[   OK ] ClientImplMethods.GetSocketTest (4 ms)
[--] 1 test from ClientImplMethods (4 ms total)

[--] 1 test from HttpToHttpsRedirectTest
[ RUN  ] HttpToHttpsRedirectTest.CertFile
../test/test.cc:5462: Failure
Value of: res
  Actual: false
Expected: true
==


Summary of Failures:

1/1 main TIMEOUT900.25s   killed by signal 15 SIGTERM


When starting an uncoordinated transition, please at least ensure that
the package at least builds on all suported platforms.

Cheers
-- 
Sebastian Ramacher