Bug#1029374: mariadb: FTBFS on ppc64

[Otto Kekäläinen]

For the record: After upload of MariaDB 1:10.11.3-1~exp1 the build
failed 3 times in a row and MTR failed on different tests:

https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64=1%3A10.11.3-1%7Eexp1=1685077417=0
Completed: Failed 9/1059 tests, 99.15% were successful.
Failing test(s): main.xa_prepared_binlog_off
main.statistics_upgrade_not_done main.upgrade-check

https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64=1%3A10.11.3-1%7Eexp1=1684999385=0
Completed: Failed 3/1055 tests, 99.72% were successful.
Failing test(s): main.xa_prepared_binlog_off

https://buildd.debian.org/status/fetch.php?pkg=mariadb=ppc64=1%3A10.11.3-1%7Eexp1=1685067613=0
Completed: Failed 3/1055 tests, 99.72% were successful.
Failing test(s): main.host_cache_size_functionality

Test failures have different reasons but this seems common:

[ERROR] InnoDB: Database page corruption on disk or a failed read
of file './ibdata1' page [page id: space=0, page number=59].

Bug#1036785: netfilter-persistent: upgrade does not remove empty directory /etc/systemd/system/netfilter-persistent.service.d

[Vincent Lefevre]

Package: netfilter-persistent
Version: 1.0.20
Severity: normal

When upgrading netfilter-persistent from 1.0.19 to 1.0.20, I got:

dpkg: warning: unable to delete old directory 
'/etc/systemd/system/netfilter-persistent.service.d': Directory not empty

But due to this upgrade, this directory is now empty:

$ ls -a /etc/systemd/system/netfilter-persistent.service.d
.  ..

-- System Information:
Debian Release: 12.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')
merged-usr: no
Architecture: amd64 (x86_64)

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

Versions of packages netfilter-persistent depends on:
ii  init-system-helpers  1.64

netfilter-persistent recommends no packages.

Versions of packages netfilter-persistent suggests:
ii  iptables-persistent  1.0.20

-- no debconf information

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

Bug#1036784: wmbusmeters: Fail to build on hurd-i386 - undefined reference to `SerialCommunicationManagerImp::listSerialTTYs[abi:cxx11]()'

[Petter Reinholdtsen]

Package: wmbusmeters
Version: 1.13.1-2
Severity: serious

The package fail to build on several architectures.  The build log can be found 
on
https://buildd.debian.org/status/package.php?p=wmbusmeters=experimental >.

The common build error from several logs look like this:

OK: Test using netcat to feed hex stream using tcp.
./tests/test_nc3.sh: line 25: xxd: command not found
ERROR: GOT  but expected 123.529
ERROR: Test using netcat to feed rawtty stream using tcp.
Slower tests...
OK: reading all stdin before closing down
OK: Test config with oneshot
OK: Test config with exitafter
OK: Test config override with oneshot
OK: Test config override with exitafter
RUNNING Test alarms ...
STDERR-
[ALARM DeviceInactivity] 4 seconds of inactivity resetting 
simulations/simulation_alarm.txt simulation (timeout 4s expected mon-sun(00-23) 
now 2023-05-20 08:11)
(wmbus) successfully reset wmbus device
STDOUT-
TMP/OUTPUT-
METER =={"media":"cold 
water","meter":"multical21","name":"Water","id":"76348799","status":"DRY","total_m3":6.408,"target_m3":6.408,"flow_temperature_c":127,"external_temperature_c":19,"current_status":"DRY","time_dry":"22-31
 
days","time_reversed":"","time_leaking":"","time_bursting":"","timestamp":"2023-05-20T08:11:40Z"}==
METER =={"media":"cold 
water","meter":"multical21","name":"Water","id":"76348799","status":"DRY","total_m3":6.408,"target_m3":6.408,"flow_temperature_c":127,"external_temperature_c":19,"current_status":"DRY","time_dry":"22-31
 
days","time_reversed":"","time_leaking":"","time_bursting":"","timestamp":"2023-05-20T08:11:46Z"}==
TMP/ALARM--
ALARM_SHELL DeviceInactivity [ALARM DeviceInactivity] 4 seconds of inactivity 
resetting simulations/simulation_alarm.txt simulation (timeout 4s expected 
mon-sun(00-23) now 2023-05-20 08:11)
---
OK: Test alarms
Some tests failed!
make[1]: *** [Makefile:337: test] Error 1

Look like a missing build dependency.

-- 
Happy hacking
Petter Reinholdtsen

Bug#1036783: wmbusmeters: Fail to build on hurd-i386 - undefined reference to `SerialCommunicationManagerImp::listSerialTTYs[abi:cxx11]()'

[Petter Reinholdtsen]

Package: wmbusmeters
Version: 1.13.1-2
Severity: wishlist

The package fail to build on hurd-i386.  The build log can be found on
https://buildd.debian.org/status/package.php?p=wmbusmeters=experimental >.

The build log
https://buildd.debian.org/status/fetch.php?pkg=wmbusmeters=hurd-i386=1.13.1-2=1684573683=0
 >
report this error:

g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Ibuild src/main.cc -c -E > build/main.o.src
g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Ibuild src/main.cc -MMD -c -o build/main.o
g++ -o build/wmbusmeters.g build/aes.o build/aescmac.o build/bus.o 
build/cmdline.o build/config.o build/dvparser.o build/formula.o 
build/mbus_rawtty.o build/metermanager.o build/meters.o 
build/manufacturer_specificities.o build/printer.o build/rtlsdr.o 
build/serial.o build/shell.o build/sha256.o build/threads.o 
build/translatebits.o build/util.o build/units.o build/wmbus.o 
build/wmbus_amb8465.o build/wmbus_im871a.o build/wmbus_cul.o 
build/wmbus_rtlwmbus.o build/wmbus_rtl433.o build/wmbus_simulator.o 
build/wmbus_rawtty.o build/wmbus_rc1180.o build/wmbus_utils.o 
build/lora_iu880b.o  build/driver_abbb23.o build/driver_aerius.o 
build/driver_amiplus.o build/driver_apator08.o build/driver_apator162.o 
build/driver_apator172.o build/driver_apatoreitn.o build/driver_auto.o 
build/driver_aventieshca.o build/driver_aventieswm.o build/driver_bfw240radio.o 
build/driver_c5isf.o build/driver_cma12w.o build/driver_compact5.o 
build/driver_dme_07.o build/driver_ebzwmbe.o build/driver_ehzp.o 
build/driver_ei6500.o build/driver_elf.o build/driver_em24.o 
build/driver_emerlin868.o build/driver_enercal.o build/driver_engelmann-faw.o 
build/driver_esyswm.o build/driver_eurisii.o build/driver_ev200.o 
build/driver_evo868.o build/driver_fhkvdataiii.o build/driver_fhkvdataiv.o 
build/driver_flowiq2200.o build/driver_gransystems.o build/driver_gwfwater.o 
build/driver_hydrocalm3.o build/driver_hydroclima.o build/driver_hydrodigit.o 
build/driver_hydrus.o build/driver_iperl.o build/driver_itron.o 
build/driver_izar.o build/driver_kamheat.o build/driver_kampress.o 
build/driver_lansendw.o build/driver_lansenpu.o build/driver_lansensm.o 
build/driver_lansenth.o build/driver_lse_07_17.o build/driver_lse_08.o 
build/driver_microclima.o build/driver_minomess.o build/driver_mkradio3.o 
build/driver_mkradio4.o build/driver_mkradio4a.o build/driver_multical21.o 
build/driver_munia.o build/driver_nemo.o build/driver_omnipower.o 
build/driver_piigth.o build/driver_pollucomf.o build/driver_q400.o 
build/driver_qcaloric.o build/driver_qheat.o build/driver_qheat_55_us.o 
build/driver_qsmoke.o build/driver_qualcosonic.o build/driver_qwater.o 
build/driver_rfmamb.o build/driver_rfmtx1.o build/driver_sensostar.o 
build/driver_sharky.o build/driver_sharky774.o build/driver_sontex868.o 
build/driver_supercom587.o build/driver_topaseskr.o build/driver_tsd2.o 
build/driver_ultraheat.o build/driver_ultrimis.o build/driver_unismart.o 
build/driver_unknown.o build/driver_vario411.o build/driver_vario451.o 
build/driver_vario451mid.o build/driver_waterstarm.o build/driver_watertech.o 
build/driver_weh_07.o build/main.o -Wl,-z,relro -Wl,-z,now -Wl,--as-needed 
-lrtlsdr -lusb-1.0 -lpthread
/usr/bin/ld: 
build/serial.o:(.data.rel.ro._ZTV29SerialCommunicationManagerImp[_ZTV29SerialCommunicationManagerImp]+0x40):
 undefined reference to 
`SerialCommunicationManagerImp::listSerialTTYs[abi:cxx11]()'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:273: build/wmbusmeters.g] Error 1

-- 
Happy hacking
Petter Reinholdtsen

Bug#1031850: gcc-13: Change "loongarch64-linux-gnuf64" into "loongarch64-linux-gnu"

[WANG Xuerui]

On Sat, 13 May 2023 09:52:11 +0200 Matthias Klose  wrote:

On 13.05.23 09:41, zhangdandan wrote:
> Control: tags -1 moreinfo
> 
> Hi gcc maintainers,
> 
>      I am particularly sorry for the lack of replies under this bug.
> 
> 在 2023/3/5 下午5:12, Matthias Klose 写道:

>> Control: tags -1 + moreinfo
>>
>> This needs documentation in
>> https://wiki.debian.org/Multiarch/Tuples
> 
> We have added documentation in https://wiki.debian.org/Multiarch/Tuples.

> Please review the added information [1] related to LoongArch64.
> 
> [1]: 
> https://wiki.debian.org/Multiarch/Tuples#fnref-607863550593b35d97abb9ba30075128dc27d0cc
> 
> thanks,

> Dandan Zhang
> 

that link describes four different ABIs. I cannot see which one is the one 
proposed for Debian. Please clarify on the wiki page.


Please also note that these changes cannot be made before this support is 
backported in dpkg for the Debian stable release.


FYI, I've updated the wiki pages (Multiarch/Tuples and Ports/loong64, in 
particular) a few days ago to confirm things: the gist is that the 
loong64 port is only utilizing the LP64D ABI right now (and in the 
foreseeable future).


And, regarding the multiarch tuple: as a matter of fact, the 
"loongarch64-linux-gnu" is effectively already stable. But I agree that 
the dpkg backport is still TODO (I just checked 1.20.12 which apparently 
doesn't contain loong64). Maybe Dandan or someone else should open the 
appropriate bug for that.

Bug#1036603: libinventor1: broken symlinks: /usr/share/inventor/fonts/Century-Schoolbook-* -> /usr/share/fonts/X11/Type1/c0590*l.pfb

[Steven Robbins]

On Tue, 23 May 2023 10:21:29 +0200 Andreas Beckmann  wrote:

> fonts-urw-base35 does not provide the old "numeric" font names
> gsfonts-x11 had.

Thanks for this.  Do you happen to know of a package that does ship those 
fonts, even if a different name?

> (gsfonts-x11 is now an empty transitional package,
> so you could drop that alternative dependency.)
> 
> Feel free to downgrade the severity if the missing fonts are harmless.

I couldn't say "harmless", but "mostly harmless", I'd think.  

-Steve


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

Bug#1036443: ntpsec: leftover files on purge

[Richard Laager]

At first glance, I agree that these should be cleaned up. I just need to 
actually do the work on this, ASAP, of course.


On 2023-05-22 08:40, Christoph Anton Mitterer wrote:

Oh and I've just noticed that I've had accidentally reported the bug
against ntpsec, not ntp.


That is correct, I believe. The ntpsec source package has taken over the 
ntp binary packages.


--
Richard



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1036113: libpurple0: license conflict with libsasl2

[Richard Laager]

First, I've downgraded the severity on this to "important". We are 
currently in a freeze with a release imminent. Removing pidgin from the 
next Debian release is a significant step that we should not undertake 
lightly. The issue at hand has existed for years, possibly a decade or 
even two, without complaints, so I think we can afford some time here.


Second, looking at #996892, Philipp Hahn already made some points about 
what is and isn't an advertising clause. There is no 
"BSD-3-Clause-Attribution" license in the copyright file that I can see. 
Please identify specifically which license(s) you are talking about, 
using names as they appear in the copyright file for the cyrus-sasl2 
package.


Third, if a system-library exemption is reasonable (or even possible), 
then there isn't actually an incompatibility in the first place.


On 2023-05-15 12:32, Bastian Germann wrote:

Package: libpurple0
Version: 2.14.12-1
Severity: serious

Hi,

libirc.so and libjabber.so.0.0.0 depend on libsasl2-2, which is licensed 
under CMU's BSD-3-Clause-Attribution license and covered by the RSA-MD 
license. They have clauses in place, which are known to be incompatible 
with GPL-2+ (as far as I can see the mentioned libraries' license). 
There are several possible solutions to this problem:


1) Build with --disable-cyrus-sasl configuration and get rid of the 
libsasl2 (Build-)Dependencies.


Then users lose SASL support, which is not great.


2) Support my request at #996892.


If we are going to treat OpenSSL as a system library, then I think 
cyrus-sasl is a reasonable contender for the same treatment.


3) Ask upstream to add a license exception for libsasl2-2, similar to 
the one that was required by Debian for OpenSSL for a long time.


3 is not viable due to too many copyright holders.

4) Pidgin could switch SASL implementations. This will be happening for 
Pidgin 3 anyway.



Are the problems just limited to MD5? If so:

5) Replace the MD5 implementation in Cyrus SASL with a different one.

6) Cyrus SASL uses OpenSSL for MD5 instead of its built-in MD5 code.

7) Cyrus SASL just drops MD5. (That might actually be reasonable 
post-bookworm.)


--
Richard

Bug#1036740: [Pkg-netatalk-devel] Bug#1036740: Fix for CVE-2022-23123 causes afpd segfault with valid metadata

[Daniel Markstedt]

On Thu, May 25, 2023 at 3:39 AM Markus Koschany  wrote:
>
> Hello Daniel,
>
> Am Donnerstag, dem 25.05.2023 um 08:02 +0200 schrieb Salvatore Bonaccorso:
> > >
> > > These two commits in upstream addressed this:
> > > https://github.com/Netatalk/netatalk/commit/9d0c21298363e8174cdfca657e66c4d10819507b
> > > https://github.com/Netatalk/netatalk/commit/4140e5495bac42ecb9b11975229c81e84762cc98
>
> Both patches have been backported to Buster. You can find them as CVE-2022-
> 23123_part3.patch and CVE-2022-23123_part4.patch.
>
> Did we miss something else?
>
> Regards,
>
> Markus

Salvatore, Markus,

Thank you very much for taking swift action on this!
Please forgive my ignorance here, but are these patches active already
if I apt install netatalk (3.1.12~ds-3+deb10u1) on Buster?
Or do they have to be picked up by some build process that hasn't run yet?

I'm asking because I ran a few tests now and while EA metadata works,
the appledouble v2 metadata functionality is definitely broken, even
when you create a new shared volume from scratch.

dmark@buster:~$ apt show netatalk
Package: netatalk
Version: 3.1.12~ds-3+deb10u1
...
May 25 18:51:08 buster afpd[7415]: ad->ad_ops->ad_header_read(path,
ad, pst) failed: Input/output error
May 25 18:51:08 buster afpd[7415]: getfilparams(Screenshot 2023-05-23
at 10.36.39 AM.png): bad resource fork
May 25 18:51:08 buster afpd[7415]: parse_entries: bogus eid: 3, off: 182, len: 8
May 25 18:51:08 buster afpd[7415]:
ad_header_read(/home/dmark/afp-data): malformed AppleDouble

So either more patches have to be cherry-picked or I need to be patient. :)

Bug#1036782: mailman3: exim4 configurations not up-to-date

[Thomas Krichel]

Package: mailman3
Version: 3.3.8-1
Severity: normal

Dear Maintainer,

exim4/conf.d/main/25_mm3_macros
exim4/conf.d/transport/55_mm3_transport

  distributed with Mailman3 are not the versions posted at

https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/mta.html#exim4-configuration

  This leads to mailman3 being unusable with exim4. Use
  of the posted configurations in the document above
  will fix this. 

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

Kernel: Linux 6.0.0-5-amd64 (SMP w/12 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 mailman3 depends on:
ii  cron 3.0pl1-162
ii  dbconfig-no-thanks   2.0.24
ii  debconf [debconf-2.0]1.5.82
ii  init-system-helpers  1.65.2
ii  logrotate3.21.0-1
ii  python3  3.11.2-1+b1
ii  python3-aiosmtpd 1.4.3-1
ii  python3-alembic  1.8.1-2
ii  python3-authheaders  0.15.2-1
ii  python3-authres  1.2.0-3
ii  python3-click8.1.3-2
ii  python3-dateutil 2.8.2-2
ii  python3-dnspython2.3.0-1
ii  python3-falcon   3.1.1-1+b1
ii  python3-flufl.bounce 4.0-3
ii  python3-flufl.i18n   3.0.1-3
ii  python3-flufl.lock   5.0.1-4
ii  python3-gunicorn 20.1.0-6
ii  python3-importlib-resources  5.1.2-2
ii  python3-lazr.config  2.2.3-3
ii  python3-passlib  1.7.4-3
ii  python3-psycopg2 2.9.5-1+b1
ii  python3-public   2.3-4
ii  python3-requests 2.28.1+dfsg-1
ii  python3-sqlalchemy   1.4.46+ds1-1
ii  python3-zope.component   5.1.0-1
ii  python3-zope.configuration   4.4.1-1
ii  python3-zope.event   4.4-3
ii  python3-zope.interface   5.5.2-1+b1
ii  ucf  3.0043+nmu1

Versions of packages mailman3 recommends:
ii  exim4-daemon-heavy [mail-transport-agent]  4.96-15

Versions of packages mailman3 suggests:
pn  anacron  
ii  links [www-browser]  2.28-1+b2
ii  lynx [www-browser]   2.9.0dev.12-1
pn  mailman3-doc 
ii  postgresql   15+248
ii  w3m [www-browser]0.5.3+git20230121-2

-- debconf information excluded

Bug#933335: aptitude: Please add support for dpkg frontend lock

[Vincent Lefevre]

Control: found -1 0.8.13-5

Just to say that this still occurs.

The error message is now

[...]
Setting up apt (2.6.1) ...
dpkg: error: dpkg frontend lock was locked by another process with pid 4191235
Note: removing the lock file is always wrong, can damage the locked area
and the entire system. See .
E: Sub-process /usr/bin/dpkg returned an error code (2)
[...]

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

Bug#1026026: /usr/sbin/needrestart: typo prevents vm detection and leads to error in microcode check

[Jérôme Charaoui]

Control: severity -1 important

Hello,

This is crippling the usefulness of needrestart in virtual machines, 
because it is systematically reporting a failure every time it runs, 
with the output including:


 Failed to check for processor microcode upgrades.

Furthermore, it is causing needrestart's "nagios check" mode to report a 
false "UNKNWOWN" status where it should be reporting "OK".


Would it be possible to please backport this trivial patch?

Thank you,

-- Jérôme

Bug#1036530: linux-signed-amd64: Hard lock up of system

[Nick Hastings]

Hi Salvatore,

thanks for your help. However, I'm now not sure if I really have
identified the commit that causes my problems. I fear I may have made
one or more mistakes when setting "git bisect good". I had been under
the impression that the lock up would happen no more than a few tens of
minutes after booting, however it seems that sometimes it can take a few
hours to occur.

So, I'm running the git bisect again and will be more careful before
marking "git bisect good". It could take a few days.

Should this particular bug be closed?

Thanks,

Nick.


* Salvatore Bonaccorso  [230526 00:19]:
> Hi Nick,
> 
> On Thu, May 25, 2023 at 08:23:15AM +0900, Nick Hastings wrote:
> > Hi,
> > 
> > * Salvatore Bonaccorso  [230524 19:26]:
> > >
> > > Given you were able to bisect it so far, can you try to isolate the
> > > commit from the merge commit causing it?
> > 
> > I guess I can try. The commit message states:
> > 
> > Merge: c77f54a9bcec a1cf1fd62ae7 562163595a91 018d6711c26e 6cc401be1648
> > 
> > Is there a way extract out each of those?
> 
> Th way i usuually get all commits from a merge request is
> 
> git log --oneline $mergecommit^$mergecommit^2
> 
> though here we have three merge commits, merged with one merge commit
> on top, so you would go down the merges of the acpi-properties,
> acpi-tables, acpi-x86 and acpi-soc branches. Those are those:
> 
> * acpi-properties:
>   ACPI: property: Silence missing-declarations warning in apple.c
> 
> * acpi-tables:
>   ACPI: HMAT: Drop unused dev_fmt() and redundant 'HMAT' prefix
>   ACPI: tables: FPDT: Don't call acpi_os_map_memory() on invalid phys 
> address
> 
> * acpi-x86:
>   ACPI: x86: Add a quirk for Dell Inspiron 14 2-in-1 for StorageD3Enable
> 
> * acpi-soc:
>   ACPI: LPSS: Deduplicate skipping device in acpi_lpss_create_device()
>   ACPI: LPSS: Replace loop with first entry retrieval
> 
> > > One remotely related might be "ACPI: x86: Add a quirk for Dell
> > > Inspiron 14 2-in-1 for StorageD3Enable".
> > 
> > Manually looking at the diff with
> > git diff e996c7e01892ac18ec0db447294d4f591c325efe~  
> > e996c7e01892ac18ec0db447294d4f591c325efe 
> > I guess that means the following:
> > 
> > --- a/drivers/acpi/x86/utils.c
> > +++ b/drivers/acpi/x86/utils.c
> > @@ -207,9 +207,26 @@ static const struct x86_cpu_id storage_d3_cpu_ids[] = {
> > {}
> >  };
> >  
> > +static const struct dmi_system_id force_storage_d3_dmi[] = {
> > +   {
> > +   /*
> > +* _ADR is ambiguous between GPP1.DEV0 and GPP1.NVME
> > +* but .NVME is needed to get StorageD3Enable node
> > +* https://bugzilla.kernel.org/show_bug.cgi?id=216440
> > +*/
> > +   .matches = {
> > +   DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> > +   DMI_MATCH(DMI_PRODUCT_NAME, "Inspiron 14 7425 
> > 2-in-1"),
> > +   }
> > +   },
> > +   {}
> > +};
> > +
> >  bool force_storage_d3(void)
> >  {
> > -   return x86_match_cpu(storage_d3_cpu_ids);
> > +   const struct dmi_system_id *dmi_id = 
> > dmi_first_match(force_storage_d3_dmi);
> > +
> > +   return dmi_id || x86_match_cpu(storage_d3_cpu_ids);
> >  }
> 
> That probably won't work actually as the code has been refactored
> substantiantly after the commit. 
> 
> In the ideal case we could confirm the quirk change is the responsable
> commit, so we can make upstream aware.
> 
> Regards,
> Salvatore

Bug#1036781: gnome-shell segfaults on boot shortly after realmd starts working

[Al Ma]

Package: gnome-shell
Version: 42.3.1-2
Severity: important
In the journal I've discovered a disturbing segfault:
Mai 25 23:43:55 AnonymizedComputerName dbus-daemon[820]: [system] Successfully 
activated service 'org.freedesktop.realmd'
Mai 25 23:43:55 AnonymizedComputerName systemd[1]: Started Realm and Domain 
Configuration.
Mai 25 23:43:55 AnonymizedComputerName realmd[1322]: claimed name on bus: 
org.freedesktop.realmd
Mai 25 23:43:55 AnonymizedComputerName kernel: show_signal_msg: 14 callbacks 
suppressed
Mai 25 23:43:55 AnonymizedComputerName kernel: gnome-shell[1068]: segfault at 0 
ip  sp 7fffc9a8c8a8 error 14
Mai 25 23:43:55 AnonymizedComputerName kernel: Code: Unable to access opcode 
bytes at RIP 0xffd6.
Unfortunately, dmesg and syslog contain no additional information from the last 
moments before the segfault. In my understanding, this failure leads to the 
inability to start Wayland (and xorg kicks in instead).
Who is the real culprit and what to do? Any remedy or bugfix? Any (as small as 
possible) set of packages to upgrade?
I run Debian stable, kernel 5.10.0-23-amd64, with a few updated packages from 
testing. Probably related packages: linux-image-amd64 5.10.179-1, realmd 
0.16.3-3, systemd 247.3-7+deb11u2, dbus 1.12.24-0+deb11u1.
The severity is raised because the bug is (in my understanding) a major reason 
for why Wayland is unusable on my machine.
Gratefully,
AlMa

Bug#1036773: [EXTERNAL] Bug#1036773: cloud.debian.org: During vagrant up, mounting NFS fails

[Meeuwissen Olaf]

+1

I my case installation of the NFS client fails (I'm behind a proxy) but the 
machine
boots fine.

  $ cat Vagrantfile
  Vagrant.configure("2") do |config|
config.vm.box = "debian/testing64"
  end

Last bit of the output from `vagrant up`

  ==> default: Machine booted and ready!
  ==> default: Installing NFS client...
  The following SSH command responded with a non-zero exit status.
  Vagrant assumes that this means the command failed!

  apt-get -yqq update
  apt-get -yqq install nfs-common portmap
  exit $?


  Stdout from the command:



  Stderr from the command:

  W: Failed to fetch https://deb.debian.org/debian/dists/testing/InRelease  
Cannot initiate the connection to debian.map.fastly.net:443 
(2a04:4e42:48::644). - connect (101: Network is unreachable) Could not connect 
to debian.map.fastly.net:443 (151.101.230.132), connection timed out Cannot 
initiate the connection to deb.debian.org:443 (2a04:4e42:36::644). - connect 
(101: Network is unreachable)
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.
  E: Package 'nfs-common' has no installation candidate
  E: Unable to locate package portmap

Hope this helps,


From: Joshua Kugler 
Sent: 26 May 2023 04:37
To: Debian Bug Tracking System
Subject: [EXTERNAL] Bug#1036773: cloud.debian.org: During vagrant up, mounting 
NFS fails

Package: cloud.debian.org
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
I tried to use the debian/testing64 vagrant box.

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

I ran `vagrant up`. It mostly runs, but hangs on ==> default: Mounting 
NFS shared folders...
After sitting there

   * What was the outcome of this action?

It mostly runs, but hangs on ==> default: Mounting NFS shared folders...
After sitting there for a while, it fails with:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=4 192.168.121.1:/home/jkugler/vmware/vagrant_debian 
/vagrant

Stdout from the command:


Stderr from the command:

mount.nfs: Connection refused


   * What outcome did you expect instead?

I expected the machine to come up without issue.

I noticed in the default Vagrantfile that comes with the box, there is 
an NFS shared folder.
That should probably be removed and allow the user to configure shared 
folders as they see fit.

Bug#1036780: hw-detect: detect and add bochs/cirrus to the initramfs

[Cyril Brulebois]

Package: hw-detect
Severity: important

Hi,

This is another expression of the problem I've started documenting in
#1036019: under UEFI/SB, using the std (bochs) or cirrus graphics
drivers leads to corrupted graphics.

[ I'm even able to get a 800×599 resolution via cirrus! ]


I've implemented a workaround in the installer by shipping the two
relevant DRM modules (bochs.ko, cirrus.ko), which makes the install
process itself run fine.

Unfortunately, upon rebooting, since the initramfs doesn't contain
bochs.ko or cirrus.ko by default, the LUKS passphrase prompt is
corrupted as well (efifb, which is built-in, is likely in charge at this
point). Once LUKS has been unlocked, the console becomes readable, and
one can type login and password normally.

The LUKS prompt is worrying on its own, but I'm also worried one might
be missing critical messages, even on non-LUKS systems, if the boot
sequence breaks early.


Therefore, I'm considering detecting when bochs.ko and/or cirrus.ko are
loaded, adding them to /etc/initramfs-tools/modules, and requesting an
update-initramfs call (see #1036019).

The cost/benefit ratio makes it look like a no-brainer to me, but I'm
happy to hear about other opinions.


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

Bug#1036779: finish-install: factorize update-initramfs calls

[Cyril Brulebois]

Package: finish-install
Severity: important

Hi,

At the moment, and only looking at our packages, there are several
finish-install hooks that might trigger an update-initramfs call:
 - hw-detect might deploy a CPU microcode package;
 - finish-install might detect cryptsetup and console-setup, and “play
   safe” to make sure the selected keymap is available for the LUKS
   prompt at start-up.

I know there's at least open-iscsi-udeb with a similar hook, and we
might have some other packages out there — this is definitely not a
complete survey.

Additionally, due to #1036019, one might get a garbled LUKS prompt, and
I'm considering adding some kind of detection. This would likely be
along the way of “if bochs or cirrus are loaded, add them to i-t's
modules and rebuild the initramfs”, making sure the LUKS prompt would be
readable, and increasing chances of seeing error messages if the boot
breaks early. First instinct was hw-detect's finish-install script, but
thinking a bit more and filing the actual report still remain to be
done.


To avoid update-initramfs calls piling up, I'm tempted to have a
specific file where each package/hook could write a reason for
requesting an update-initramfs call, and finish-install's
10update-initramfs would (1) still perform its own cryptsetup vs.
console-setup detection, queueing a call if needed, (2) look at the
queue, logging reason(s) for the call, and (3) lump all calls together,
only running update-initramfs once.


(Of course, this doesn't change the fact there might be multiple runs
earlier; I'm only looking at the “final” run, within finish-install's
realm.)


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

Bug#1036771: debian-installer: Wrong colors in GRUB submenus for netboot on x86

[Cyril Brulebois]

Same player, shoot again.

Cyril Brulebois  (2023-05-25):
> I'm therefore proposing *not* to force those colors in normal submenus,
> and to only force colors when in the dark menu (and its submenus).

And I'm now proposing to only do that on x86, which can be detected via
a new IS_X86 (similar to IS_PURE_GTK), set from x86.cfg.

Doing so shouldn't change anything to the rest of the analysis for x86
(touching netboot and only netboot).

> See how the only affected build targets are netboot and netboot-gtk,
> leaving the “CD-oriented” ones alone, meaning no impact on debian-cd
> builds. I consider this change to be safe for x86.

That's still the plan.


> Not breaking arm64
> ==

That escalated quickly.

> Seeing debian-cd_info.tar.gz there got me worried, keeping in mind the
> original intent was to fix netboot* on x86!

And worried I should have stayed.

> Here, we see that we have the “usual”/“feedback” colors hardcoded at the
> top, there's no background_image call, and there's no condition at all.
> So dropping the re-hardcoding of the same colors in submenus doesn't
> look like it should break anything (I'm pretty sure I tested that a few
> days ago, with my first local netinst arm64 build; but I'll probably
> giving it another spin after uploading debian-installer with the patch,
> waiting for the various buildd/ftp/release bits to happen).

Combine this…

> Also, for some reason, with or without patching the debian-installer
> build, the color “reset” after entering/exiting the dark menu just works
> on arm64.

… with this, and guess what happens?

I'm not sure why that happens (and why that's different across archs),
and I won't get to the bottom of this before the upcoming release, but
dropping the hardcoded colors in submenus on all archs means breaking
submenus on arm*: only the main menu and the dark menu get specified
colors used, and all other submenus have undefined colors instead.

It seems there's some kind of reset each time on moves from one menu to
another one, which is likely why colors have always been hardcoded,
dating back all the way to 2014 and the introduction of this script for
arm64.

For the record, this breaks both netboot and netinst. 100% success rate.

> In passing, I'm seeing a warning/error message when entering the dark
> menu, but that might just be some limitation of the virtualization
> environment (maybe some unsupported video mode change).

For completeness the screen reads:

error: no video mode activated.

Press any key to continue...


> Conclusion
> ==
> 
> This bug report is more for later reference than anything, to fully
> document the reasons, worries, and reassurances about the change, so
> that we can get back to it if anything breaks, without having to
> rediscover that rabbit hole…

Hindsight!


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


signature.asc
Description: PGP signature

Bug#1034824: tomcat9 should not be released with Bookworm

[Markus Koschany]

First of all trapperkeeper-webserver-jetty9-clojure should add a build-
dependency on logback to detect such regressions in advance.

#1036250 is mainly a logback problem, not a tomcat problem. I still would like
to hear Emmanuel's opinion. We still could revert to libtomcat9-java, if we
don't find a solution though.

The tomcatjss / dogtag-pki situation is simple too. If there is no way to make
the application work with Tomcat 10, then there are three options:

1. Embed Tomcat 9 in your application by creating a standalone jar

2. Continue to use the current Tomcat 9 package as is but make sure that nobody
else than dogtag-pki uses it. (Package descriptions should be adjusted, and the
binary tomcat9 package should be probably removed too) Nobody should think that
we support two major Tomcat versions.

In any case the dogtag-pki maintainers must commit to at least three years of
security support, web application + Tomcat 9. Otherwise this is pointless.

3. Remove dogtag-pki and tomcatjss from testing and prepare backports as soon
as dogtag-pki and Co support Tomcat 10.

Markus


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

Bug#1034824: tomcat9 should not be released with Bookworm

[Jérôme Charaoui]

Le 2023-05-25 à 17 h 41, Martin Hostettler a écrit :


Quoting from J�r�me Charaoui in (#1036250):

I did further tests with puppetserver, which is a downstream dependency
of trapperkeeper-webserver-jetty9-clojure and unfortunately, the web
requests (access) logging remains broken. There are no warnings or error
messages anywhere: as you can imagine, the logging events are simply
lost in the ether.

I'm not sure if the latest patches from 2023-05-22 do fix those, but there
was no follow up on the bug with details.


For the record, these patches only fix the build issue and work around 
the test failures by disabling the affected tests.


The logging problem is still present in puppetserver (and almost 
certainly puppetdb) with the patched 
trapperkeeper-webserver-jetty9-clojure package.


Thanks,

-- Jérôme

Bug#1036249: closure-compiler: #1036249

[Markus Koschany]

Sorry, that should have been #1036249.


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

Bug#1034824: tomcat9 should not be released with Bookworm

[Martin Hostettler]

I was asked to send a update to this bug from my notes/open tabs.

>From what i can see this is still a problem and it is getting very late
to fix all the fallout.

There are still 2 packages that are not fixed for this.

src:trapperkeeper-webserver-jetty9-clojure (#1036250) which is as far as
I understand a dependency of puppet, which is used by a lot of admins
including Debian's own DSA.

Which even after trying to fix the build problem left the package in a
state where it the whole logging is non functional: 

Quoting from J�r�me Charaoui in (#1036250):
> I did further tests with puppetserver, which is a downstream dependency 
> of trapperkeeper-webserver-jetty9-clojure and unfortunately, the web 
> requests (access) logging remains broken. There are no warnings or error 
> messages anywhere: as you can imagine, the logging events are simply 
> lost in the ether.

I'm not sure if the latest patches from 2023-05-22 do fix those, but there
was no follow up on the bug with details.

Then there is src:tomcatjss (1031816) which seems to have zero progress
since the bug was filed.

This is a dependency of at least dogtag-pki, pki-ca, pki-kra, pki-ocsp,
pki-server, pki-tks and pki-tps

I'm not sure what the actual state of src:logback is. It seems the problems
in trapperkeeper-webserver-jetty9-clojure are partially related to the
state of logback.
Do we know that it properly works with the tomcat10 migration patchset?
Logback seems to have quite a few reverse dependencies as well.


Some bugs have according to the bts been fixed and migrated meanwile:

#1035995: bazel-bootstrap
#1011597: tiles
#1033366: resteasy3.0

What is the plan here to get this in shape for in time before last unblock
requests for bookworm on the 28th?

 - Martin

Bug#1036249: closure-compiler: #1036159

[Markus Koschany]

Control: tags -1 patch

Hello,

I have been working on #1036159 and before I go ahead with my solution I would
like to hear your opinion whether this is acceptable.

Apparently closure-compiler embeds rhino classes and thus every time rhino is
updated, closure-compiler must be rebuilt too. I did just that in revision -14
but still half of the reverse-dependencies FTBFS because of a parsing error. I
tried to narrow this issue down and even reverted a commit in rhino which made
closure-compiler FTBFS. We addressed the initial FTBFS in revision -13. Still
that made no difference. Although rhino 1.7.14 and our ten year old closure-
compiler package are seemingly compatible at the source level, there must be
some subtle differences which cause the Javascript parsing errors.

Since I could not find a targeted fix I decided to remove the dependency on
rhino 1.7.14 and embedded rhino 1.7.7.2 instead, the last version that worked
well for closure-compiler. You can find the results here:

https://salsa.debian.org/java-team/closure-compiler/-/tree/bookworm

I have rebuilt all reverse-dependencies and this would resolve the problem.

The only exception is ckbuilder / ckeditor. The solution here is simple though.
ckbuilder must be rebuilt against rhino 1.7.14. This is the original solution
for #1026639 but the rebuilding part was forgotten. I have filed #1036778 as a
reminder.

Regards,

Markus




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

Bug#1036778: ckbuilder: must be rebuilt against rhino 1.7.14

[Markus Koschany]

Source: ckbuilder
Version: 2.4.3+dfsg-1
Severity: serious
X-Debbugs-Cc: a...@debian.org


ckbuilder must be rebuilt against rhino 1.7.14. This is a no-change
rebuild. Otherwise ckeditor will continue to FTBFS. This was already
reported in #1026639. This issue has also been reported upstream as

https://github.com/ckeditor/ckbuilder/issues/34

Back then we decided to upgrade rhino but in fact ckbuilder could have
also added the --add-exports java.desktop/sun.java2d=ALL-UNNAMED flag.

The rebuild should be done after #1036249 in closure-compiler has been
resolved.

Bug#299088: Concurrent sounds on system with Xscavenger

[Stephane Ascoet]

Hi, after more games played, it seems that the behaviour is inconsistent. 
Anyway, I'm stuck at level twelve. I've briefly become addicted to levels 
creation while editing it to make it playable.


--
Sincerely, Stephane Ascoet

Bug#1036776: release-notes: Release notes paragraph from Debian Med team

[Andreas Tille]

Package: release-notes
Severity: normal
X-Debbugs-Cc: debian-...@lists.debian.org

Please add the following patch from the Debian Med team to the release notes:


News from Debian Med Blend


As in every release new packages in the field of life sciences and medicine
were added.  The new package shiny-server might be worth extra mentioning
since it simplifies scientific web applications using R.  We kept on to get
Continuous Integration support for the packages maintained by the Debian Med
team.

The Debian Med team is continuously interested in feedback from users
specifically in the form of requesting the packaging of not yet packaged
free software or backports from new packages or higher versions in unstable.

To install packages maintained by the Debian Med team, install the
metapackages named med-*, which are at version 3.8.x for Debian bookworm.
Feel free to visit the
https://blends.debian.org/med/tasks;>Debian Med tasks 
pages
to see the full range of biological and medical software available in 
Debian.



Kind regards
Andreas.

Bug#1036752: [Pkg-rust-maintainers] Bug#1036752: bat: manpage is missing, README.debian is missing

[peter green]

After the bat binary was renamed from batcat to bat and back to batcat, the man 
page is no longer installed:


This appears to have not been directly related to the renames, instead
it appears that Sylvestre disabled the manpage in version 0.18.3-1,
unfortunately the commit message does not say why.

https://salsa.debian.org/rust-team/debcargo-conf/-/commit/82afeef244ea59a98d9d3209d485e85bcc6bc38f

Bug#1036755: linux: 6.1.26 <= x < 6.1.30 breaks applications using mmap(MAP_32BIT)

[Salvatore Bonaccorso]

Hi Apollon,

On Thu, May 25, 2023 at 10:14:57PM +0300, Apollon Oikonomopoulos wrote:
> Hi Salvatore,
> 
> Thanks for the quick response!
> 
> On 19:12 Thu 25 May , Salvatore Bonaccorso wrote:
> > Control: tags -1 + confirmed pending
> > 
> > I'm not yet certain, that critical severity is right, and making it
> > RC. But will look into the issue today.
> 
> Well, technically it is a regression and it does break userspace, 
> although I admit it probably does so only for a handful of edge-cases.  
> Anyway, critical is probably an overstatement, so feel free to downgrade 
> if you wish.

Thanks. I still cannot overview the exact/major imapct if it so does
only for a handful edge cases (your for ganeti beeing one) but we can
defintively keeping it as RC, thanks to you (and Rudolph Bott) for
reporting the issue.

> > Defitnively the issue will be fixed. Just at this stage for the
> > bookworm release I will pick it for the first upload after the release
> > in a point release update or a security update (whatever will come
> > first likely).
> 
> I understand that it is late in the release cycle and it would be a 
> shame to delay the Bookworm release for this. As far as Ganeti is 
> concerned, we can let people know that they should wait for the first 
> point release before upgrading their clusters.

Ack. I'm trying to check now with release team if we still should
cherry-pick the commit or going to just have to include it in the
first point release. it might be worth mentioning the known issue on
release though in the later case. If you have a good wording for that,
that would be welcome.

> Again, thanks for your work!

You are welcome, and feel sorry that a breakage was introduced that
late in the process for bookworm.

Regards,
Salvatore

Bug#1036775: transmission-gtk: Stuck / segfault on startup

[Witold Baryluk]

Package: transmission-gtk
Version: 3.00-2.1+b1
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com

This can be triggered if very first startup is when using magnet link on
command line.

Any subsequent launches will show this issue.

strace shows (after initialization) a lot of calls to brk, to allocate
memory for something.

Looks like it might be running out of stack due to crazy recursion as
shown below.

It eventually crashes.

Stack trace:

(gdb) r
Starting program: /usr/bin/transmission-gtk 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x74b4f6c0 (LWP 2326834)]
[New Thread 0x7fffe6c0 (LWP 2326835)]
[New Thread 0x7fffef7fe6c0 (LWP 2326836)]
[New Thread 0x7fffeeffd6c0 (LWP 2326837)]
[New Thread 0x7fffee7fc6c0 (LWP 2326882)]
[New Thread 0x7fffedffb6c0 (LWP 2326914)]
[Thread 0x7fffedffb6c0 (LWP 2326914) exited]
[New Thread 0x7fffedffb6c0 (LWP 2326967)]
[Thread 0x7fffedffb6c0 (LWP 2326967) exited]
[New Thread 0x7fffedffb6c0 (LWP 2326972)]
[New Thread 0x7fffd622d6c0 (LWP 2326973)]
[Thread 0x7fffedffb6c0 (LWP 2326972) exited]
[New Thread 0x7fffedffb6c0 (LWP 2326974)]
[New Thread 0x7fffd58dd6c0 (LWP 2326975)]
[Thread 0x7fffedffb6c0 (LWP 2326974) exited]
[Thread 0x7fffd622d6c0 (LWP 2326973) exited]
[Thread 0x7fffd58dd6c0 (LWP 2326975) exited]
[New Thread 0x7fffd58dd6c0 (LWP 2327586)]
[New Thread 0x7fffedffb6c0 (LWP 2327587)]
[Thread 0x7fffd58dd6c0 (LWP 2327586) exited]
[Thread 0x7fffedffb6c0 (LWP 2327587) exited]
[Thread 0x7fffe6c0 (LWP 2326835) exited]

Thread 1 "transmission-gt" received signal SIGSEGV, Segmentation fault.
0x77870702 in gtk_css_node_ensure_style (current_time=2833046890377, 
cssnode=0x55db4090 [GtkCssWidgetNode]) at ../../../gtk/gtkcssnode.c:983
983 ../../../gtk/gtkcssnode.c: No such file or directory.
(gdb) set pagination off
(gdb) bt full
#0  0x77870702 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=0x55db4090 [GtkCssWidgetNode]) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#1  gtk_css_node_ensure_style (cssnode=0x55dc2510 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
#2  0x77870707 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#3  gtk_css_node_ensure_style (cssnode=0x55ddf0c0 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
#4  0x77870707 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#5  gtk_css_node_ensure_style (cssnode=0x55ded510 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
#6  0x77870707 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#7  gtk_css_node_ensure_style (cssnode=0x55e04090 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
#8  0x77870707 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#9  gtk_css_node_ensure_style (cssnode=0x55e14530 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
#10 0x77870707 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#11 gtk_css_node_ensure_style (cssnode=0x55e2a890 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
#12 0x77870707 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#13 gtk_css_node_ensure_style (cssnode=0x55d00500 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
#14 0x77870707 in gtk_css_node_ensure_style 
(current_time=2833046890377, cssnode=) at 
../../../gtk/gtkcssnode.c:983
new_style = 
style_changed = 
#15 gtk_css_node_ensure_style (cssnode=0x55e568b0 [GtkCssWidgetNode], 
current_time=current_time@entry=2833046890377) at ../../../gtk/gtkcssnode.c:1003
new_style = 
style_changed = 
...
...
...
...
...
...
...
...
#7748 0x77870707 in 

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

[Gürkan Myczko]

On 25.05.2023 19:47, Martin Hostettler wrote:

On 19/05/2023 12.48, Martin Hostettler wrote:

It seems what is needed is this:

mv 
debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components 
debian/cadabra2/usr/share/javascript
rmdir 
debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static

rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook

(The wildcards are used to avoid hard coding the current debian 
default

python version)


Any chance to get this changes into an upload? The deadline for last
unblock requests is quickly coming.


I'm sorry, I'm busy with other things, if you feel like it please go 
ahead add yourself to
Uploaders and upload. Or NMU, as you like. I am also fine reviewing 
changes, and uploading

via mentors.d.n.

Regards,
Gurkan


 - Martin

Bug#1036774: vym: A new upstream version is available: 2.9.0. The source code was moved to github.

[Jonatas]

Package: vym
Version: 2.6.11-3+b2
Severity: normal
X-Debbugs-Cc: dkdj3p...@mozmail.com

Dear Maintainer,

A new upstream version is available: 2.9.0. 
The source code was moved to github: https://github.com/insilmaril/vym

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages vym depends on:
ii  libc62.36-9
ii  libgcc-s1 [libgcc1]  12.2.0-14
ii  libqt5core5a 5.15.8+dfsg-10
ii  libqt5dbus5  5.15.8+dfsg-10
ii  libqt5gui5   5.15.8+dfsg-10
ii  libqt5network5   5.15.8+dfsg-10
ii  libqt5printsupport5  5.15.8+dfsg-10
ii  libqt5svg5   5.15.8-3
ii  libqt5widgets5   5.15.8+dfsg-10
ii  libqt5xml5   5.15.8+dfsg-10
ii  libstdc++6   12.2.0-14
ii  unzip6.0-28
ii  xsltproc 1.1.35-1
ii  zip  3.0-13

vym recommends no packages.

Versions of packages vym suggests:
pn  ruby | ruby-interpreter  

-- no debconf information

Bug#1036773: cloud.debian.org: During vagrant up, mounting NFS fails

[Joshua Kugler]

Package: cloud.debian.org
Severity: important

Dear Maintainer,

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

   * What led up to the situation?
I tried to use the debian/testing64 vagrant box.

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

I ran `vagrant up`. It mostly runs, but hangs on ==> default: Mounting 
NFS shared folders...
After sitting there 

   * What was the outcome of this action?

It mostly runs, but hangs on ==> default: Mounting NFS shared folders...
After sitting there for a while, it fails with:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

mount -o vers=4 192.168.121.1:/home/jkugler/vmware/vagrant_debian 
/vagrant

Stdout from the command:


Stderr from the command:

mount.nfs: Connection refused


   * What outcome did you expect instead?

I expected the machine to come up without issue.

I noticed in the default Vagrantfile that comes with the box, there is 
an NFS shared folder.
That should probably be removed and allow the user to configure shared 
folders as they see fit.

Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server

[Nicholas D Steeves]

Control: owner -1 !
Control: tag -1 +moreinfo
Control: block 927950 by -1

Hi Alexandru,

Welcome!  I'd like to sponsor your work, and I hope that attention to
detail doesn't annoy you.  Please take a look at the questions in the
following reply:

Alexandru Mihail  writes:

>  * Package name : mini-httpd
>Version  : 1.30-4
>Upstream contact : Jef Poskanzer j...@mail.acme.com
>  * URL  : https://www.acme.com/software/mini_httpd
>  * License  : BSD-2-clause
>  * Vcs  : https://salsa.debian.org/debian/mini-httpd

Do you intend to continue to maintain mini-httpd at this location (Vcs
location), or do you have a new one in mind?  Do you intend to maintain
the package in git, and if so would you please share the remote of your
fork?  You don't have to if you don't want to, by the way.

>  mini-httpd (1.30-4) unstable; urgency=medium
>  .
>* New maintainer. (Closes: #927950)

Thank you for adopting this package!

>* Added missing newline in the rules file
>* Bumped Standards-Version to 4.5.1

This doesn't make sense, because, in 1.30-3, Håvard F. Aasen updated
Standards-Version to 4.6.1; in other words, this line claims you
regressed the package back to 4.5.1.  Yes, Aasen didn't document this
change in the changelog, and that makes it unclear what happened...maybe
it was a "bump", but maybe Aasen did the work of checking the package
was compliant.  I'd like you to verify compliance with the current
version of Debian Policy (4.6.2), and here is the checklist to help you
along your way.  Please start at 4.4.1.

  https://www.debian.org/doc/debian-policy/upgrading-checklist.html.

and I'd like to see you document your work with:

  * Declare compliance with Standards-Version 4.6.2. (no changes required)

because I believe that you're not a robot ;)  One of the perspectives I
was mentored to uphold is that "bumping" is for robots.  Please note
that your sponsor will need to manually check for compliance with Policy
before uploading.  Yes, this means duplicate work, or even triplicate
work if it was a package that needed ftpmaster review!  The number is
just a number, and what really counts is the work.

On the topic of work, has upstream resolved any of these old bugs:

  https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=mini-httpd

If so, let's talk about closing them!  This is a normal part of adopting
a package (closing fixed bugs, and/or reopening ones that are still
relevant).

Regards,
Nicholas


signature.asc
Description: PGP signature

Bug#1036755: linux: 6.1.26 <= x < 6.1.30 breaks applications using mmap(MAP_32BIT)

[Apollon Oikonomopoulos]

Hi Salvatore,

Thanks for the quick response!

On 19:12 Thu 25 May , Salvatore Bonaccorso wrote:
> Control: tags -1 + confirmed pending
> 
> I'm not yet certain, that critical severity is right, and making it
> RC. But will look into the issue today.

Well, technically it is a regression and it does break userspace, 
although I admit it probably does so only for a handful of edge-cases.  
Anyway, critical is probably an overstatement, so feel free to downgrade 
if you wish.

> Defitnively the issue will be fixed. Just at this stage for the
> bookworm release I will pick it for the first upload after the release
> in a point release update or a security update (whatever will come
> first likely).

I understand that it is late in the release cycle and it would be a 
shame to delay the Bookworm release for this. As far as Ganeti is 
concerned, we can let people know that they should wait for the first 
point release before upgrading their clusters.

Again, thanks for your work!

Cheers,
Apollon

Bug#1036755: linux: 6.1.26 <= x < 6.1.30 breaks applications using mmap(MAP_32BIT)

[Salvatore Bonaccorso]

On Thu, May 25, 2023 at 07:12:47PM +0200, Salvatore Bonaccorso wrote:
> Control: tags -1 + confirmed pending
> 
> Hi Apollon,
> 
> On Thu, May 25, 2023 at 03:26:50PM +0300, Apollon Oikonomopoulos wrote:
> > Source: linux
> > Version: 6.1.27-1
> > Severity: critical
> > Tags: upstream
> > Affects: ganeti
> > Justification: breaks unrelated software
> > 
> > Dear Kernel Maintainers,
> > 
> > A regression was introduced with upstream commit 58c5d0d6d5,  
> > subsequently backported to 6.1 as 7e6631f7 and released with 6.1.26.  
> > These commits break MAP_32BIT and affect applications relying on it. In 
> > particular, we are seeing failures in ganeti's autopkgtests[1], where a 
> > daemon written in Haskell (the GHC linker uses MAP_32BIT) segfaults with 
> > a null pointer dereference. From the build artifacts:
> > 
> >  ganeti-luxid: mmap 4096 bytes at (nil): Cannot allocate memory
> >  ganeti-luxid: Try specifying an address with +RTS -xm -RTS
> > 
> > This has already been discussed on GHC's discourse[2] and has been fixed 
> > upstream, with the fix queued for 6.1.30[3]. Please consider upgrading 
> > to 6.1.30 or cherry-picking the fix for Bookworm.
> 
> I'm not yet certain, that critical severity is right, and making it
> RC. But will look into the issue today.
> 
> Defitnively the issue will be fixed. Just at this stage for the
> bookworm release I will pick it for the first upload after the release
> in a point release update or a security update (whatever will come
> first likely).
> 
> In any case I'm already preparing the 6.1.30 import for bookworm.

For the record,
https://lore.kernel.org/linux-mm/cb8dc31a-fef2-1d09-f133-e9f7b9f9e...@sony.com/
gives a reproducer/verifier for the issue.

Regards,
Salvatore

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Julian Gilbey]

On Thu, May 25, 2023 at 09:25:50AM -0700, Brian Vaughan wrote:
> # Spyder, Help > Dependencies
> [...]
> pylsp >=1.7.1;<1.8.0  :  1.7.1 (OK)
> pylsp_black >=1.2.0   :  None (NOK)

Hi Brian,

Thanks for sending all this through.  This is so weird.

> # Commands in the iPython console
> 

All looks normal here.

I am utterly mystified why spyder is not finding pylsp_black.  I'll
have a think about it and get back to you.

Best wishes,

   Julian

Bug#1036772: unblock: swtpm/0.7.1-1.3

[Bastian Germann]

Package: release.debian.org
Control: affects -1 + src:swtpm
X-Debbugs-Cc: sw...@packages.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package swtpm.

[ Reason ]
Fix for RC bugs #1035460 and #1036101.

[ Impact ]
FTBFS and missing dependency.

[ Tests ]
Added autopkgtest to the package.
The FTBFS was only on mipsel, supposedly because the autobuilder machines are 
not fast enough for upstream's timeout.
They built it successfully after doubling it.

[ Risks ]
None.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock swtpm/0.7.1-1.3diff -Nru swtpm-0.7.1/debian/changelog swtpm-0.7.1/debian/changelog
--- swtpm-0.7.1/debian/changelog2022-02-22 08:50:30.0 +0100
+++ swtpm-0.7.1/debian/changelog2023-05-18 19:52:09.0 +0200
@@ -1,3 +1,26 @@
+swtpm (0.7.1-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Revert "Remove essential Depends: adduser"
+
+ -- Bastian Germann   Thu, 18 May 2023 19:52:09 +0200
+
+swtpm (0.7.1-1.2) unstable; urgency=high
+
+  * Non-maintainer upload
+  * Patch: Increase poll timeout (Closes: #1036101)
+  * Add autopkgtest
+  * Remove essential Depends: adduser
+
+ -- Bastian Germann   Thu, 18 May 2023 19:16:12 +0200
+
+swtpm (0.7.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * swtpm-dev: Add missing Depends: swtpm-libs (#1035460)
+
+ -- Bastian Germann   Fri, 12 May 2023 19:06:09 +0200
+
 swtpm (0.7.1-1) unstable; urgency=medium
 
   * New upstream version 0.7.1
diff -Nru swtpm-0.7.1/debian/control swtpm-0.7.1/debian/control
--- swtpm-0.7.1/debian/control  2022-02-22 08:50:30.0 +0100
+++ swtpm-0.7.1/debian/control  2023-05-18 19:30:13.0 +0200
@@ -39,7 +39,8 @@
 
 Package: swtpm-dev
 Architecture: any
-Depends: ${misc:Depends}
+Depends: swtpm-libs (= ${binary:Version}),
+ ${misc:Depends}
 Description: Include files for the TPM emulator's CUSE interface
  The swtpm-dev package provides include files for developing clients
  controlling the CUSE TPM through ioctls.
diff -Nru swtpm-0.7.1/debian/patches/increase-poll-timeout.patch 
swtpm-0.7.1/debian/patches/increase-poll-timeout.patch
--- swtpm-0.7.1/debian/patches/increase-poll-timeout.patch  1970-01-01 
01:00:00.0 +0100
+++ swtpm-0.7.1/debian/patches/increase-poll-timeout.patch  2023-05-18 
17:57:46.0 +0200
@@ -0,0 +1,22 @@
+From e056a48128fe26af6e45675a13bee32700917c0f Mon Sep 17 00:00:00 2001
+From: Bastian Germann 
+Date: Thu, 18 May 2023 17:57:13 +0200
+Subject: Increase poll timeout
+
+---
+ src/swtpm_ioctl/tpm_ioctl.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/swtpm_ioctl/tpm_ioctl.c b/src/swtpm_ioctl/tpm_ioctl.c
+index 1ac1335..38c05bc 100644
+--- a/src/swtpm_ioctl/tpm_ioctl.c
 b/src/swtpm_ioctl/tpm_ioctl.c
+@@ -93,7 +93,7 @@
+ #endif
+ 
+ /* poll timeout that takes into account a busy swtpm creating a key */
+-#define DEFAULT_POLL_TIMEOUT 1 /* ms */
++#define DEFAULT_POLL_TIMEOUT 2 /* ms */
+ 
+ static unsigned long ioctl_to_cmd(unsigned long ioctlnum)
+ {
diff -Nru swtpm-0.7.1/debian/patches/series swtpm-0.7.1/debian/patches/series
--- swtpm-0.7.1/debian/patches/series   2022-02-22 08:12:41.0 +0100
+++ swtpm-0.7.1/debian/patches/series   2023-05-18 17:58:28.0 +0200
@@ -1,2 +1,3 @@
 fix-typos.patch
+increase-poll-timeout.patch
 move-conf-and-options-files-to-man5.patch
diff -Nru swtpm-0.7.1/debian/tests/commandline 
swtpm-0.7.1/debian/tests/commandline
--- swtpm-0.7.1/debian/tests/commandline1970-01-01 01:00:00.0 
+0100
+++ swtpm-0.7.1/debian/tests/commandline2023-05-18 19:03:02.0 
+0200
@@ -0,0 +1,13 @@
+#!/bin/sh
+set -e
+
+export SWTPM_EXE=swtpm
+export SWTPM_IOCTL=swtpm_ioctl
+export SWTPM_BIOS=swtpm_bios
+export SWTPM_SETUP=swtpm_setup
+export SWTPM_CERT=swtpm_cert
+
+for t in tests/test_commandline
+do
+  $t
+done
diff -Nru swtpm-0.7.1/debian/tests/control swtpm-0.7.1/debian/tests/control
--- swtpm-0.7.1/debian/tests/control1970-01-01 01:00:00.0 +0100
+++ swtpm-0.7.1/debian/tests/control2023-05-18 19:01:58.0 +0200
@@ -0,0 +1,2 @@
+Tests: commandline
+Depends: @

Bug#1036021: cadabra2,python3-notebook: undeclared file conflict on /usr/lib/python3/dist-packages/notebook/static/components/codemirror

[Martin Hostettler]

On 19/05/2023 12.48, Martin Hostettler wrote:
> It seems what is needed is this:
> 
> mv 
> debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static/components 
> debian/cadabra2/usr/share/javascript
> rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook/static
> rmdir debian/cadabra2/usr/lib/python3.*/site-packages/notebook
> 
> (The wildcards are used to avoid hard coding the current debian default
> python version)

Any chance to get this changes into an upload? The deadline for last
unblock requests is quickly coming.

 - Martin

Bug#1035765: python-rlp-doc: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Followup-For: Bug #1035765
Control: tag -1 patch

Hi,

all that is needed is a dir_to_symlink call, please see the attached
patch. I'll prepare a NMU and upload it with 0-day delay tomorrow to
get this fix into bookworm.


Andreas
>From a046121a848d7f91cb0a81b91030ce4fb1119bdd Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Thu, 25 May 2023 19:18:52 +0200
Subject: [PATCH] perform dir to symlink conversion of
 /usr/share/doc/python-rlp-doc

---
 debian/changelog  | 8 
 debian/python-rlp-doc.maintscript | 1 +
 2 files changed, 9 insertions(+)
 create mode 100644 debian/python-rlp-doc.maintscript

diff --git a/debian/changelog b/debian/changelog
index 8d50671..72f6d22 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+pyrlp (0.5.1-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Perform dir to symlink conversion of /usr/share/doc/python-rlp-doc.
+(Closes: #1035765)
+
+ -- Andreas Beckmann   Thu, 25 May 2023 19:17:55 +0200
+
 pyrlp (0.5.1-3) unstable; urgency=medium
 
   * Update UScan configuration for changes in upstream releases page.
diff --git a/debian/python-rlp-doc.maintscript 
b/debian/python-rlp-doc.maintscript
new file mode 100644
index 000..3457c0e
--- /dev/null
+++ b/debian/python-rlp-doc.maintscript
@@ -0,0 +1 @@
+dir_to_symlink /usr/share/doc/python-rlp-doc python3-rlp 0.5.1-3.1~
-- 
2.20.1

Bug#1036755: linux: 6.1.26 <= x < 6.1.30 breaks applications using mmap(MAP_32BIT)

[Salvatore Bonaccorso]

Control: tags -1 + confirmed pending

Hi Apollon,

On Thu, May 25, 2023 at 03:26:50PM +0300, Apollon Oikonomopoulos wrote:
> Source: linux
> Version: 6.1.27-1
> Severity: critical
> Tags: upstream
> Affects: ganeti
> Justification: breaks unrelated software
> 
> Dear Kernel Maintainers,
> 
> A regression was introduced with upstream commit 58c5d0d6d5,  
> subsequently backported to 6.1 as 7e6631f7 and released with 6.1.26.  
> These commits break MAP_32BIT and affect applications relying on it. In 
> particular, we are seeing failures in ganeti's autopkgtests[1], where a 
> daemon written in Haskell (the GHC linker uses MAP_32BIT) segfaults with 
> a null pointer dereference. From the build artifacts:
> 
>  ganeti-luxid: mmap 4096 bytes at (nil): Cannot allocate memory
>  ganeti-luxid: Try specifying an address with +RTS -xm -RTS
> 
> This has already been discussed on GHC's discourse[2] and has been fixed 
> upstream, with the fix queued for 6.1.30[3]. Please consider upgrading 
> to 6.1.30 or cherry-picking the fix for Bookworm.

I'm not yet certain, that critical severity is right, and making it
RC. But will look into the issue today.

Defitnively the issue will be fixed. Just at this stage for the
bookworm release I will pick it for the first upload after the release
in a point release update or a security update (whatever will come
first likely).

In any case I'm already preparing the 6.1.30 import for bookworm.

Regards,
Salvatore

Bug#1036737: libsoapysdr0.8: please add Breaks: libsoapysdr0.7 for smoother upgrades from bullseye

[tony mancill]

On Thu, May 25, 2023 at 03:08:22AM +0200, Andreas Beckmann wrote:
> Package: libsoapysdr0.8
> Version: 0.8.1-2
> Severity: serious
> Tags: patch
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> The soapysdr library stacks from bullseye and bookworm are not
> co-installable, but the transitive conflict behind longer dependency
> chains is not always easy detectable by apt. Therefore several upgrade
> paths result in old libraries being kept installed and some upgradable
> packages being kept at an older version.
> 
> Making the conflict explicit between higher scoring packages helps apt
> finding a better upgrade path.
> 
> Please consider applying the attached patch.
 
Hi Andreas,

Thank you for the patch.  I have prepared a package for upload.  I
didn't see any problems with piuparts with the new package, but in the
interest of full disclosure, I also couldn't reproduce the piuparts
failure with 0.8.1-2.  (Perhaps you could share the invocation you used
to identify the problem?)

In any event, I think the change is good and am planning to upload,
provided there are no concerns from the Debian Hams.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

[Andreas Metzler]

Hello,

if you have not got time for an upload I can look into it.

cu Andreas

Bug#1035766: sse{2,3,4.2}-support: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

Followup-For: Bug #1035766
Control: tag -1 patch

The .maintscript files are generated with an uppercase
/usr/share/doc/NAME-support to be converted, that of course does not
work.

Andreas
>From 14252f3d180c8ddf29449ac87d1db7b2855d0168 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Thu, 25 May 2023 18:38:45 +0200
Subject: [PATCH] fix .maintscript generation

---
 debian/@lcn...@-support.maintscript.in | 2 +-
 debian/changelog   | 7 +++
 refresh-package| 1 +
 3 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/debian/@lcn...@-support.maintscript.in 
b/debian/@lcn...@-support.maintscript.in
index 773d275..40503e9 100644
--- a/debian/@lcn...@-support.maintscript.in
+++ b/debian/@lcn...@-support.maintscript.in
@@ -1 +1 @@
-dir_to_symlink /usr/share/doc/@NAME@-support isa-support 8~
\ No newline at end of file
+dir_to_symlink /usr/share/doc/@LCNAME@-support isa-support 15.1~
diff --git a/debian/changelog b/debian/changelog
index dde362f..ce3c4ac 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+isa-support (15.1) UNRELEASED; urgency=medium
+
+  * Fix .maintscript generation for /usr/share/doc/$PACKAGE -> isa-support
+symlink conversion.  (Closes: #1035766)
+
+ -- Andreas Beckmann   Thu, 25 May 2023 18:35:12 +0200
+
 isa-support (15) unstable; urgency=high
 
   * Bug fix: "version 14 fails to install where version 13 installs fine
diff --git a/refresh-package b/refresh-package
index cec9240..8f6e4a9 100755
--- a/refresh-package
+++ b/refresh-package
@@ -15,6 +15,7 @@ sub file_replace
 close IN;
 
 s/[@]NAME[@]/$name/g;
+s/[@]LCNAME[@]/$lcname/g;
 s/[@]DEB_HOST_MULTIARCH[@]/$DEB_HOST_MULTIARCH/g;
 open OUT, ">debian/$foutname"
or die "Can't write debian/$foutname: $!\n";
-- 
2.20.1

Bug#1036565: debian-installer-12-netboot-amd64: Installers needed b43 ucode16_mimo.fw, had to eth0 net install + manual firmware-b43-installer, MacBookPro5,5

[Fan Naibed]

May 24, 2023 at 9:37 PM, "Cyril Brulebois"  wrote:

> 
> Fan Naibed  (2023-05-24):
> 
> > 
> > May 23, 2023 at 3:17 AM, "Cyril Brulebois"  wrote:
> >  How would this work? firmware-b43-installer is just a downloader,
> >  so for it to do anything, you need to have a working connection in
> >  the first place. It's basically an empty shell, with its postinst
> >  doing the downloading.
> >  
> >  Installing onto slightly older Macbooks, using Wi-Fi, just worked(TM).
> >  So, their WiFi fw was included.
> > 
> 
> Do you know which firmware files/packages were involved on those?

The older macbook has

03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43224 
802.11a/b/g/n [14e4:4353] (rev 01)

and uses firmware-brcm80211.

The macbook pro has

03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4322 
802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)



> 
> > 
> > The b43 installer/downloader would need to be changed to a firmware
> >  file that can be included with the installer. :)
> > 
> 
> Presumably those are working this way because the license doesn't
> allow for redistribution. Feel free to get that part resolved!

Since I don't understand how automating the download and install 
is significantly different than including the firmware in the 
debian installer, from a license/legal standpoint, that is beyond me!

> Also, see https://wiki.debian.org/bcm43xx

Thanks

Bug#865183: libjpeg6b: please build-depend on automake, not obsolete automake1.11

[Bill Allombert]

On Thu, May 25, 2023 at 03:18:58PM +0200, Bastian Germann wrote:
> libjpeg6b is not going anywhere.

What does that even mean ?

> I would like to suggest to remove the package for the purpose of reducing the 
> automake1.11 dependent package.
> libjpeg6b has not been part of a Debian release in years. What is the reason 
> for it staying in unstable?

Historical reason. It is required for compatibility with the LSB.
At least that prevent someone to reuse the name by mistake.

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Brian Vaughan]

# Spyder, Help > Dependencies

# Mandatory:
atomicwrites >=1.2.0  :  1.4.1 (OK)
chardet >=2.0.0   :  5.1.0 (OK)
cloudpickle >=0.5.0   :  2.2.0 (OK)
cookiecutter >=1.6.0  :  1.7.3 (OK)
diff_match_patch >=2018   :  20200713 (OK)
intervaltree >=3.0.2  :  3.0.2 (OK)
IPython >=7.31.1;<9.0.0   :  8.5.0 (OK)
jedi >=0.17.2;<0.19.0 :  0.18.2 (OK)
jellyfish >=0.7   :  0.8.9 (OK)
jsonschema >=3.2.0    :  4.10.3 (OK)
keyring >=17.0.0  :  23.9.3 (OK)
nbconvert >=4.0   :  6.5.3 (OK)
numpydoc >=0.6.0  :  1.5.0 (OK)
parso >=0.7.0;<0.9.0  :  0.8.3 (OK)
pexpect >=4.4.0   :  4.8.0 (OK)
pickleshare >=0.4 :  0.7.5 (OK)
psutil >=5.3  :  5.9.4 (OK)
pygments >=2.0    :  2.15.1 (OK)
pylint >=2.5.0;<3.0   :  2.16.2 (OK)
pylint_venv >=2.1.1   :  2.3.0 (OK)
pyls_spyder >=0.4.0   :  0.4.0 (OK)
pylsp >=1.7.1;<1.8.0  :  1.7.1 (OK)
pylsp_black >=1.2.0   :  None (NOK)
qdarkstyle >=3.0.2;<3.2.0 :  3.1 (OK)
qstylizer >=0.2.2 :  0.2.2 (OK)
qtawesome >=1.2.1 :  1.2.2 (OK)
qtconsole >=5.4.0;<5.5.0  :  5.4.0 (OK)
qtpy >=2.1.0  :  2.3.0 (OK)
rtree >=0.9.7 :  1.0.1 (OK)
setuptools >=49.6.0   :  66.1.1 (OK)
sphinx >=0.6.6    :  5.3.0 (OK)
spyder_kernels >=2.4.2;<2.5.0 :  2.4.2 (OK)
textdistance >=4.2.0  :  4.5.0 (OK)
three_merge >=0.1.1   :  0.1.1 (OK)
watchdog >=0.10.3 :  2.2.1 (OK)
xdg >=0.26    :  0.28 (OK)
zmq >=22.1.0  :  24.0.1 (OK)

# Optional:
cython >=0.21 :  None (NOK)
matplotlib >=3.0.0    :  3.6.3 (OK)
numpy >=1.7   :  1.24.2 (OK)
pandas >=1.1.1    :  None (NOK)
scipy >=0.17.0    :  1.10.1 (OK)
sympy >=0.7.3 :  1.11.1 (OK)


# Spyder, Help > About Spyder

* Spyder version: 5.4.2  (pip)
* Python version: 3.11.2 64-bit
* Qt version: 5.15.8
* PyQt5 version: 5.15.9
* Operating System: Linux 6.1.0-9-amd64


# Commands in the iPython console

Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0]
Type "copyright", "credits" or "license" for more information.

IPython 8.5.0 -- An enhanced Interactive Python.

import sys

sys.executable
Out[2]: '/usr/bin/python3'

sys.path
Out[3]:
['/usr/lib/python311.zip',
 '/usr/lib/python3.11',
 '/usr/lib/python3.11/lib-dynload',
 '',
 '/usr/local/lib/python3.11/dist-packages',
 '/usr/lib/python3/dist-packages',
 '/usr/lib/python3.11/dist-packages']

import pylsp_black

sys.modules["pylsp_black"]
Out[5]: '/usr/lib/python3/dist-packages/pylsp_black/__init__.py'>

Bug#1003862: Some news about a fix ?

[gregor herrmann]

Control: tag -1 + unreproducible

On Fri, 05 May 2023 14:16:53 +, Holger Levsen wrote:

> On Fri, May 05, 2023 at 03:49:44PM +0200, Jérôme Bardot wrote:
> > That bug is currently blocking from using munin on not systemd systems.
> I'm not planning on supporting legacy initscripts myself. And despite tagging
> this bug 'wontfix' for the time being I will accept patches, so IOW I'm just
> tagging this 'wontfix' to set expectations right.

In general I'm happy to help with the sysv initscript; in practice I
can only notice that I'm running munin-node (from testing or
unstable) on several machines with sysvinit, and that I haven't
encountered the issue. I just tried to restart and stop/start
munin-node on 3 machines, and it also just worked.

I guess we need more information from those who hit the issue …


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#1036769: lintian: Check for certificates .pem/.crt/.pkcs12 with expiry set

[Florian Lohoff]

Package: lintian
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,
i am in the middle of a stretch rebuild for mipsel (Upgrade path from
jessie as stretch dropped 75% of supported systems with mips32)

A big issue are certificates, mostly for build tests which have an
expire date set. This causes the package to fail just because we are a
couple years behind schedule.

Flo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdb9o7oebX2papQ/KkN1BIMsJ8i8FAmRvfnIACgkQkN1BIMsJ
8i8zNg/9Hn+BSGD5BFZbp5/afhzgM0MkJ+fdkJixiBMV9ETJ+39yjqQ9TBsDDwIV
P7uN3IeB+ndkXH3iY9XbuoUY0AyND3V5bWXKjj/Zf5iS+XWTcn5oVxRunh07LWd0
2dnIg5kekh5ls4Y0GqO7Zmx9KPUNpNtdwQS/O7/YIusyHOA1ExOCCE87bP8FRQOu
JtW9WeUVX84BhtVp76X47P2tLWmrgDSNFjI1Yb/JVJ3a9eI89n/y47O9GFjOd93r
lPOfFtFxpMTtzWV3k+3ks0miH+hqzYoFjG3fv8sgxE5FBvNAia99nieqIkyhTpx/
u+oLyCO1ZM7vDlIzOULKxHATSE9L2HsttD6ndhEi51VrKFGb4lBReJ5IvrL7ECBW
N//nI0TJ0TobuAjna0oKOAaYQW+h+oyH4nFJTMZu5jb+vf3MI98cxq18bSlk39c5
uX/nC2tRFkTtQvLRlVgozz+7InlsVtw62nhSiOCoTtOjU0tCiJWed4E4DKbzSLuw
j2J3vHg5pmQSN7AgbKUOqMW9QpN1VGvEa9z4xtW9Vjh4KjRcMMfDLvax0uWJ4ZFr
BJxFy3ppZMvmMsYxbuGfdxTQyP/Eo/+aM5aNu7bJZfckygVgt51+8eonyXYwOn5v
w2illtNp9OaJLSTH/bUeEajpHsVUDUFupzFi5YWMmUbEvrkcPyA=
=JBxn
-END PGP SIGNATURE-

Bug#1036768: gxkb: shows question mark instead of flag

[Celejar]

Package: gxkb
Version: 0.9.3-1
Severity: normal

The applet functions correctly, but when I switch from my default
'us,dvorak' layout to my alternate 'il' one, a question mark is
displayed instead of the appropriate flag.

My /etc/defaults/keyboard contains:

XKBMODEL="pc105"
XKBLAYOUT="us,il"
XKBVARIANT="dvorak,"
XKBOPTIONS="terminal:ctrl_alt_bksp,grp:alt_shift_toggle,ctrl:swapcaps"

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

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

Versions of packages gxkb depends on:
ii  libayatana-appindicator3-1  0.5.92-1
ii  libc6   2.36-9
ii  libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1
ii  libglib2.0-02.74.6-2
ii  libgtk-3-0  3.24.37-2
ii  libwnck-3-0 43.0-3
ii  libxklavier16   5.4-4

gxkb recommends no packages.

gxkb suggests no packages.

-- no debconf information

Bug#1036767: ITP: d-spy -- D-Bus explorer and test app for GNOME

[Jeremy Bícha]

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-gtk-gn...@lists.debian.org
Owner: jeremy.bi...@canonical.com

Package Name: d-spy
Version: 1.6.0
Upstream Author: Christian Hergert
License: GPL-3+
Programming Lang: C

Description: D-Bus explorer and test app for GNOME
 D-Spy is a tool to explore and test end-points and interfaces on the
 System or Session D-Bus. You can also connect to D-Bus peers by address.
 .
 D-Spy was originally part of the GNOME Builder app.

Other Info
--
This package will be maintained by the Debian GNOME team. Packaging is at
https://salsa.debian.org/gnome-team/d-spy

D-Spy is a maintained alternative to the D-Feet app. D-Spy uses GTK4
and libadwaita.

D-Spy also provides a library that is used to provide its features
integrated into the GNOME Builder app.

Thanks,
Jeremy Bícha

Bug#1036530: linux-signed-amd64: Hard lock up of system

[Salvatore Bonaccorso]

Hi Nick,

On Thu, May 25, 2023 at 08:23:15AM +0900, Nick Hastings wrote:
> Hi,
> 
> * Salvatore Bonaccorso  [230524 19:26]:
> >
> > Given you were able to bisect it so far, can you try to isolate the
> > commit from the merge commit causing it?
> 
> I guess I can try. The commit message states:
> 
> Merge: c77f54a9bcec a1cf1fd62ae7 562163595a91 018d6711c26e 6cc401be1648
> 
> Is there a way extract out each of those?

Th way i usuually get all commits from a merge request is

git log --oneline $mergecommit^$mergecommit^2

though here we have three merge commits, merged with one merge commit
on top, so you would go down the merges of the acpi-properties,
acpi-tables, acpi-x86 and acpi-soc branches. Those are those:

* acpi-properties:
  ACPI: property: Silence missing-declarations warning in apple.c

* acpi-tables:
  ACPI: HMAT: Drop unused dev_fmt() and redundant 'HMAT' prefix
  ACPI: tables: FPDT: Don't call acpi_os_map_memory() on invalid phys 
address

* acpi-x86:
  ACPI: x86: Add a quirk for Dell Inspiron 14 2-in-1 for StorageD3Enable

* acpi-soc:
  ACPI: LPSS: Deduplicate skipping device in acpi_lpss_create_device()
  ACPI: LPSS: Replace loop with first entry retrieval

> > One remotely related might be "ACPI: x86: Add a quirk for Dell
> > Inspiron 14 2-in-1 for StorageD3Enable".
> 
> Manually looking at the diff with
> git diff e996c7e01892ac18ec0db447294d4f591c325efe~  
> e996c7e01892ac18ec0db447294d4f591c325efe 
> I guess that means the following:
> 
> --- a/drivers/acpi/x86/utils.c
> +++ b/drivers/acpi/x86/utils.c
> @@ -207,9 +207,26 @@ static const struct x86_cpu_id storage_d3_cpu_ids[] = {
> {}
>  };
>  
> +static const struct dmi_system_id force_storage_d3_dmi[] = {
> +   {
> +   /*
> +* _ADR is ambiguous between GPP1.DEV0 and GPP1.NVME
> +* but .NVME is needed to get StorageD3Enable node
> +* https://bugzilla.kernel.org/show_bug.cgi?id=216440
> +*/
> +   .matches = {
> +   DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
> +   DMI_MATCH(DMI_PRODUCT_NAME, "Inspiron 14 7425 
> 2-in-1"),
> +   }
> +   },
> +   {}
> +};
> +
>  bool force_storage_d3(void)
>  {
> -   return x86_match_cpu(storage_d3_cpu_ids);
> +   const struct dmi_system_id *dmi_id = 
> dmi_first_match(force_storage_d3_dmi);
> +
> +   return dmi_id || x86_match_cpu(storage_d3_cpu_ids);
>  }

That probably won't work actually as the code has been refactored
substantiantly after the commit. 

In the ideal case we could confirm the quirk change is the responsable
commit, so we can make upstream aware.

Regards,
Salvatore

Bug#1036766: unblock: libreoffice/4:7.4.5-3

[Rene Engelhard]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: libreoff...@packages.debian.org, t...@security.debian.org
Control: affects -1 + src:libreoffice

Please unblock package libreoffice

[ Reason ]
1. Main reason is CVE-2023-2255 and CVE-2023-0950.

2. I had two changelog commits in my tree.
   One is just documentation () and the other one fixes a simple
   spelling error which lintian loudly complains about.
   (cf. 
https://udd.debian.org/lintian/?email1libreoffice==html_error=on_warning=on_tag=spelling-error-in-changelog#all)
   That should be a no-brainer.

3. My tree also included the commit to make ulimit -c calls not fatal.
   Since the bookworm update on ci this fails in lxc. There was a config
   change (to be) deployed to prevent that but either it didn't happen
   or was reverted. It still fails.
   So we probably should include it, experimental has it for ages
   already.

[ Impact ]
for 1. vulnerable LibreOffice

   While we could do this via bookworm-security probably I think we can avoid 
this since we do have
   enough time..

for 3. autopkgtests still failing on ci.d.n inside lxc

[ Tests ]
Not sure whether the automatic tests cover this part.
It obviously builds ;)

[ Risks ]
The diff is big but the patch is taken verbatim from upstream 7.5
branch with just minor adaptions which are not risky (CVE-2023-2255)
and upstream 7.4.6 (CVE-2023-0950)

The ulimit -c changes are already in experimental.

The changelog fix/the addition do not have any risk at all (and it is
also already in experimental)

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

unblock libreoffice/4:7.4.5-3
age-days 2 libreoffice/4:7.4.5-3

diff -Nru libreoffice-7.4.5/debian/changelog libreoffice-7.4.5/debian/changelog
--- libreoffice-7.4.5/debian/changelog  2023-02-05 18:40:59.0 +0100
+++ libreoffice-7.4.5/debian/changelog  2023-05-22 18:00:45.0 +0200
@@ -1,3 +1,17 @@
+libreoffice (4:7.4.5-3) unstable; urgency=high
+
+  * debian/patches/sc-stack-parameter-count.diff: fix CVE-2023-0950
+("Array Index UnderFlow in Calc Formula Parsing")
+  * debian/rules, debian/tests/*: don't fail if ulimit -c unlimited fails 
+(like in ci.d.n infrastructure after the bookworm upgrade...)
+  * debian/patches/CVE-2023-2255.diff:
+fix CVE-2023-2555 ("Remote documents loaded without prompt via IFrame")
+  * debian/changelog:
+- mention CVE-2022-38745 in 1:7.3.1-1s changelog
+- fix typo in last upload (s/choosen/chosen/), thanks lintian
+
+ -- Rene Engelhard   Mon, 22 May 2023 18:00:45 +0200
+
 libreoffice (4:7.4.5-2) unstable; urgency=medium
 
   * fontconfig-2.14.1-no-RGB-stripes-layout-for-sub-pixel-rendering.diff:
@@ -5,7 +19,7 @@
   * debian/control.in:
 - ... but build-conflict against affected fontconfig-configs (with
   ) instead since it now removes the offending config per default
-  (buildd chroot...) if not choosen otherwise via debconf (see #103)
+  (buildd chroot...) if not chosen otherwise via debconf (see #103)
   * debian/rules:
 - Do not add documentation symlinks when not building documentation,
   thanks Vagrant Cascadian (closes: #1030270)
@@ -502,6 +516,8 @@
 libreoffice (1:7.3.1-1) unstable; urgency=medium
 
   * LibreOffice 7.3.1 final release
+- fixes CVE-2022-38745: "Empty entry in Java class path risks arbitrary
+  code execution"
 
  -- Rene Engelhard   Thu, 03 Mar 2022 17:24:16 +
 
diff -Nru libreoffice-7.4.5/debian/patches/CVE-2023-2255.diff 
libreoffice-7.4.5/debian/patches/CVE-2023-2255.diff
--- libreoffice-7.4.5/debian/patches/CVE-2023-2255.diff 1970-01-01 
01:00:00.0 +0100
+++ libreoffice-7.4.5/debian/patches/CVE-2023-2255.diff 2023-05-20 
12:21:27.0 +0200
@@ -0,0 +1,946 @@
+From 683e4de0de8dde7c5570c67cbd2bae17b6d7f0e0 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Caol=C3=A1n=20McNamara?= 
+Date: Tue, 11 Apr 2023 10:13:37 +0100
+Subject: set Referer on loading IFrames
+
+so tools, options, security, options,
+"block any links from document not..."
+applies to their contents.
+
+Change-Id: I04839aea6b07a4a76ac147a85045939ccd9c3c79
+Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150225
+Tested-by: Jenkins
+Reviewed-by: Stephan Bergmann 
+---
+ sfx2/source/doc/iframe.cxx | 13 ++---
+ 1 file changed, 10 insertions(+), 3 deletions(-)
+
+From 49a554471cddc3e52ae381f864e689fe4a8c6131 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Caol=C3=A1n=20McNamara?= 
+Date: Thu, 13 Apr 2023 11:31:17 +0100
+Subject: put floating frames under managed links control
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+like we do for sections and ole objects that link to their content
+
+individual commits in trunk are:
+
+extract a OCommonEmbeddedObject::SetInplaceActiveState for reuse
+
+no behaviour 

Bug#1036765: ITP: libsyntax-operator-in-perl -- infix element-of-list meta-operator

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libsyntax-operator-in-perl
  Version : 0.04
  Upstream Author : Paul Evans 
* URL : https://metacpan.org/release/Syntax-Operator-In
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : infix element-of-list meta-operator

Syntax::Operator::In provides an infix meta-operator that implements a
element-of-list test on either strings or numbers.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1036764: xemacs21: new upstream version available

[Mark Brown]

On Thu, May 25, 2023 at 04:50:59PM +0200, Étienne Mollier wrote:

> Newer releases look to have moved here[3], and there[4] for the
> 21.5.y series; I reckon the layout is not ideal for watch files.

The 21.5 series are beta releases still, the stable release is still
21.4.


signature.asc
Description: PGP signature

Bug#1036764: xemacs21: new upstream version available

[Étienne Mollier]

Source: xemacs21
Version: 21.4.24-11
Severity: wishlist

Dear Maintainer,

On debian-user-french mailing list[1], Basile noticed the
availability of a new version of xemacs21.  Given that the
tracker page of xemacs21[2] reports uscan is failing to get
newer upstream versions, I thought the update might have gone
under your radar, hence the present bug.

Newer releases look to have moved here[3], and there[4] for the
21.5.y series; I reckon the layout is not ideal for watch files.

[1]: https://lists.debian.org/debian-user-french/2023/05/msg00185.html
[2]: https://tracker.debian.org/pkg/xemacs21
[3]: http://ftp.xemacs.org/pub/xemacs/
[4]: http://ftp.xemacs.org/pub/xemacs/xemacs-21.5/

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#981285: Please move fdk-aac to main

[Dylan Aïssi]

Hello ftpmasters,

First of all, thanks for your hard work!

May I ask about the status of the request to move the fdk-aac package into
main? A new version moving fdk-aac in main was uploaded in the NEW queue on
the 31 Jan 2022, but if I am not wrong, there has been no feedback yet
(at least not in #981285).

I am asking because regularity, pipewire users ask me why AAC support is
disabled in the pipewire package whereas it is enabled in others distributions.

I'm sure the decision is not obvious otherwise it would not be the oldest
package in the NEW queue :-) but it would be nice to have an update of your
point of view on that. A "yes", "no" or "maybe" one of them would be enough :-)

Thank you for your time!

Best regards,
Dylan

Bug#1036763: ITP: libsyntax-operator-equ-perl -- equality operators that distinguish C

[gregor herrmann]

Package: wnpp
Owner: gregor herrmann 
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org

* Package name: libsyntax-operator-equ-perl
  Version : 0.05
  Upstream Author : Paul Evans 
* URL : https://metacpan.org/release/Syntax-Operator-Equ
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : equality operators that distinguish C

Syntax::Operator::Equ provides infix operators that implement equality tests
of strings or numbers similar to perl's eq and == operators, except that they
consider undef to be a distinct value, separate from the empty string or the
number zero.

These operators do not warn when either or both operands are undef. They
yield true if both operands are undef, false if exactly one operand is, or
otherwise behave the same as the regular string or number equality tests if
both operands are defined.

The package will be maintained under the umbrella of the Debian Perl Group.

--
Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.


signature.asc
Description: Digital Signature

Bug#1036762: unblock: apt/2.6.1

[Julian Andres Klode]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: a...@packages.debian.org, juli...@ubuntu.com
Control: affects -1 + src:apt

Please unblock package apt

As requested adding back adduser dep.

+ Changed the .gitlab-ci and debian/gbp.conf to point at
  bookworm and 2.6.y branch for future stable updates.

+ Usual autogenerated version number bumps in files

Full diff attached.

unblock apt/2.6.1

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
diff -Nru apt-2.6.0/CMakeLists.txt apt-2.6.1/CMakeLists.txt
--- apt-2.6.0/CMakeLists.txt2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/CMakeLists.txt2023-05-25 16:11:37.0 +0200
@@ -205,7 +205,7 @@
 # Configure some variables like package, version and architecture.
 set(PACKAGE ${PROJECT_NAME})
 set(PACKAGE_MAIL "APT Development Team ")
-set(PACKAGE_VERSION "2.6.0")
+set(PACKAGE_VERSION "2.6.1")
 string(REGEX MATCH "^[0-9.]+" PROJECT_VERSION ${PACKAGE_VERSION})
 
 if (NOT DEFINED DPKG_DATADIR)
diff -Nru apt-2.6.0/debian/changelog apt-2.6.1/debian/changelog
--- apt-2.6.0/debian/changelog  2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/debian/changelog  2023-05-25 16:11:37.0 +0200
@@ -1,3 +1,14 @@
+apt (2.6.1) unstable; urgency=medium
+
+  * Restore adduser dependency for bookworm.
+This caused some regressions to late in the bookworm cycle. To keep
+upgrade paths (which will have adduser installed) the same, we drop
+the base-password alternative rather than requiring both dependencies,
+as that could change resolving or ordering bugs. (Closes: #1035654)
+  * Point gitlab-ci and gbp to bookworm/2.6.y
+
+ -- Julian Andres Klode   Thu, 25 May 2023 16:11:37 +0200
+
 apt (2.6.0) unstable; urgency=medium
 
   * The "unhappy bookworm" release. Too many changes needed to clarify
diff -Nru apt-2.6.0/debian/control apt-2.6.1/debian/control
--- apt-2.6.0/debian/control2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/debian/control2023-05-25 16:11:37.0 +0200
@@ -37,7 +37,7 @@
 
 Package: apt
 Architecture: any
-Depends: base-passwd (>= 3.6.1) | adduser,
+Depends: adduser,
  gpgv | gpgv2 | gpgv1,
  libapt-pkg6.0 (>= ${binary:Version}),
  ${apt:keyring},
diff -Nru apt-2.6.0/debian/gbp.conf apt-2.6.1/debian/gbp.conf
--- apt-2.6.0/debian/gbp.conf   2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/debian/gbp.conf   2023-05-25 16:11:37.0 +0200
@@ -3,7 +3,7 @@
 ;preexport = ./prepare-release pre-export
 prebuild = ./prepare-release pre-build
 postbuild = ./prepare-release post-build
-debian-branch = main
+debian-branch = 2.6.y
 debian-tag = %(version)s
 export-dir = ../build-area
 sign-tags = True
diff -Nru apt-2.6.0/doc/apt-verbatim.ent apt-2.6.1/doc/apt-verbatim.ent
--- apt-2.6.0/doc/apt-verbatim.ent  2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/doc/apt-verbatim.ent  2023-05-25 16:11:37.0 +0200
@@ -274,7 +274,7 @@
 ">
 
 
-
+
 
 
 
diff -Nru apt-2.6.0/doc/po/apt-doc.pot apt-2.6.1/doc/po/apt-doc.pot
--- apt-2.6.0/doc/po/apt-doc.pot2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/doc/po/apt-doc.pot2023-05-25 16:11:37.0 +0200
@@ -5,9 +5,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: apt-doc 2.6.0\n"
+"Project-Id-Version: apt-doc 2.6.1\n"
 "Report-Msgid-Bugs-To: APT Development Team \n"
-"POT-Creation-Date: 2023-03-06 12:29+\n"
+"POT-Creation-Date: 2023-05-25 14:17+\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME \n"
 "Language-Team: LANGUAGE \n"
diff -Nru apt-2.6.0/.gitlab-ci.yml apt-2.6.1/.gitlab-ci.yml
--- apt-2.6.0/.gitlab-ci.yml2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/.gitlab-ci.yml2023-05-25 16:11:37.0 +0200
@@ -1,4 +1,4 @@
-image: debian:unstable
+image: debian:bookworm
 variables:
   DEBIAN_FRONTEND: noninteractive
   CCACHE_DIR: $CI_PROJECT_DIR/.ccache
@@ -30,7 +30,7 @@
 - unbuffer ./test/integration/run-tests -q -j 4
 
 test as user:
-  image: i386/debian:unstable
+  image: i386/debian:bookworm
   stage: test
   script:
 - apt-get install --no-install-recommends -qq libxml2-utils
diff -Nru apt-2.6.0/po/apt-all.pot apt-2.6.1/po/apt-all.pot
--- apt-2.6.0/po/apt-all.pot2023-03-06 13:26:39.0 +0100
+++ apt-2.6.1/po/apt-all.pot2023-05-25 16:11:37.0 +0200
@@ -5,9 +5,9 @@
 #, fuzzy
 msgid ""
 msgstr ""
-"Project-Id-Version: apt 2.6.0\n"
+"Project-Id-Version: apt 2.6.1\n"
 "Report-Msgid-Bugs-To: APT Development Team \n"
-"POT-Creation-Date: 2023-03-06 12:29+\n"
+"POT-Creation-Date: 2023-05-25 14:17+\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME \n"
 "Language-Team: LANGUAGE \n"

Bug#1021396: ITP: batterylog -- laptop battery logging tool

[Antoine Beaupré]

On 2023-05-25 12:04:24, Andreas Tille wrote:
> Hi,
>
> since I keep on tracking down issues when my battery drains to zero when
> in suspend mode I stumbled upon your discussion on framework
> community[1] and this ITP.  Did you pushed something on salsa regarding
> the packaging I might be able to try?

No. Anything I do I document. :)

-- 
Education is the most powerful weapon which we can use to change the
world.
   - Nelson Mandela

Bug#1035691: python3-aiosmtpd: unhandled symlink to directory conversion: /usr/share/doc/python3-aiosmtpd/html/_sources -> ../rst

[Andreas Beckmann]

Followup-For: Bug #1035691
Control: tag -1 patch pending

I've uploaded a verified fix to DELAYED/1 to reach the bookworm deadline.


Andreas
>From 8d9d96a7dd7875670b96ace93c18de1b056d3111 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Thu, 25 May 2023 16:10:24 +0200
Subject: [PATCH] perform symlink to directory conversion of
 /usr/share/doc/python3-aiosmtpd/html/_sources

---
 debian/changelog| 8 
 debian/python3-aiosmtpd.maintscript | 1 +
 2 files changed, 9 insertions(+)
 create mode 100644 debian/python3-aiosmtpd.maintscript

diff --git a/debian/changelog b/debian/changelog
index 50c5ce5..72e5698 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+python-aiosmtpd (1.4.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Perform symlink to directory conversion of
+/usr/share/doc/python3-aiosmtpd/html/_sources.  (Closes: #1035691)
+
+ -- Andreas Beckmann   Thu, 25 May 2023 16:09:53 +0200
+
 python-aiosmtpd (1.4.3-1) unstable; urgency=medium
 
   * New upstream release 1.4.3 (Closes: #1026471, #1025019)
diff --git a/debian/python3-aiosmtpd.maintscript 
b/debian/python3-aiosmtpd.maintscript
new file mode 100644
index 000..265ff02
--- /dev/null
+++ b/debian/python3-aiosmtpd.maintscript
@@ -0,0 +1 @@
+symlink_to_dir /usr/share/doc/python3-aiosmtpd/html/_sources ../rst 1.4.3-1.1~
-- 
2.20.1

Bug#1036761: unblock: kleborate/2.3.1-2

[Étienne Mollier]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: klebor...@packages.debian.org
Control: affects -1 + src:kleborate

Please unblock package kleborate

[ Reason ]
kleborate is affected by the release critical upgrade bug
#1036743 identified by Andreas Beckmann (Thanks for QA tests!).

[ Impact ]
If the unblock is not granted, the package may have inconsistent
blast databases when ncbi-blast+ is upgraded after kleborate.

[ Tests ]
I ran manually the upgrade paths described in #1036743, comment
#30, to make sure the initial issue was reproducible somehow and
actually fixed by the changes.  For extra safety, I also ran a
few more basic piuparts runs since some prerm modification was
involved.

I would have hoped to point to Salsa CI results, but they have a
long standing issues at their build steps.  Other automated
tests were the build time checks and an autopkgtest manually run
on amd64.

Autobuilders look to have managed to get kleborate to build
anywhere where its build dependencies are already available.
Debci autopkgtests are pending; I don't expect difficulties on
this front as changes would have little risk to break in an
architecture specific way anyway.

[ Risks ]
Little risks are identified: changes involve a change in
maintainer script but they should be covered by the piuparts
tests already done, otherwise this is a leaf package so the area
of effect of any mishap should be limited to the package.

[ Checklist ]
  [*] all changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in testing

[ Other info ]
Thanks for your work on putting together the bookworm release!

unblock kleborate/2.3.1-2

Have a nice day,  :)
Étienne.
diff -Nru kleborate-2.3.1/debian/changelog kleborate-2.3.1/debian/changelog
--- kleborate-2.3.1/debian/changelog2023-02-06 07:37:51.0 +0100
+++ kleborate-2.3.1/debian/changelog2023-05-25 14:48:18.0 +0200
@@ -1,3 +1,18 @@
+kleborate (2.3.1-2) unstable; urgency=medium
+
+  * d/{rules,*.prerm}: cleanup .fasta.{ndb,ntf} files
+kleborate binary package  used to embed autogenerated files depending
+on makeblastdb version at both build time and postinst time.  When
+there is a discrepancy of makeblastdb version between the package
+build and the package installation, for instance during a major
+operating system upgrade, there can be a mismatch of int the
+.fasta.ndb and .fasta.ntf files produced and expected.  This change
+gets rid of the build time artifacts to solely rely on the
+post-installation artifacts, which will be more consistent and won't
+break the package consistency. (Closes: #1036743)
+
+ -- Étienne Mollier   Thu, 25 May 2023 14:48:18 +0200
+
 kleborate (2.3.1-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru kleborate-2.3.1/debian/kleborate.prerm 
kleborate-2.3.1/debian/kleborate.prerm
--- kleborate-2.3.1/debian/kleborate.prerm  2023-02-06 07:37:51.0 
+0100
+++ kleborate-2.3.1/debian/kleborate.prerm  2023-05-25 14:48:18.0 
+0200
@@ -5,6 +5,8 @@
 case "$1" in
 remove|purge|upgrade|deconfigure)
rm -f /usr/lib/python3/dist-packages/kleborate/data/*.fasta.nin
+   rm -f /usr/lib/python3/dist-packages/kleborate/data/*.fasta.ndb
+   rm -f /usr/lib/python3/dist-packages/kleborate/data/*.fasta.ntf
 ;;
 failed-upgrade)
 ;;
diff -Nru kleborate-2.3.1/debian/rules kleborate-2.3.1/debian/rules
--- kleborate-2.3.1/debian/rules2023-02-06 07:37:51.0 +0100
+++ kleborate-2.3.1/debian/rules2023-05-25 14:48:18.0 +0200
@@ -7,8 +7,14 @@
 
 override_dh_install:
dh_install
-   # fasta.nin files will be (re)build at package installation time to not 
contain build path
+   # fasta.nin files will be (re)build at package installation time to not
+   # contain build path.  Other fasta.* are rebuilt by makeblastdb and may
+   # cause inconsistencies in the package itself when makeblastdb is
+   # upgraded and changes format, e.g. during a major operating system
+   # upgrade.  See Bug#1036743.
find debian -name "*.fasta.nin" -delete
+   find debian -name "*.fasta.ndb" -delete
+   find debian -name "*.fasta.ntf" -delete
 
 override_dh_fixperms:
dh_fixperms


signature.asc
Description: PGP signature

Bug#1035418: aiksaurus: no Homepage field

[Jonas Smedegaard]

Quoting Jakub Wilk (2023-05-03 10:10:36)
> Source: aiksaurus
> Version: 1.2.1+dev-0.12-7
> Severity: minor
> 
> Please add
> 
>  Homepage: https://aiksaurus.sourceforge.net/
> 
> to debian/control.

Thanks!

I had already added this in git, shortly after most recent packaging
release, but your suggested URI is better - uses secure protocol - so I
have updated it :-)

Kind regards,

- 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#1036760: debhelper: CMake buildsystem ignores ASFLAGS

[Timo Röhling]

Package: debhelper
Version: 13.11.4
Severity: normal
X-Debbugs-Cc: helm...@debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

the ASFLAGS variable will not propagate to a CMake build because CMake
expects the ASMFLAGS variable instead [1].

Possible solutions include

1. Also set the ASMFLAGS variable
2. Pass -DCMAKE_ASM_FLAGS=$(ASFLAGS) to the CMake call


Cheers
Timo

[1] https://cmake.org/cmake/help/latest/envvar/ASM_DIALECTFLAGS.html


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

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

Versions of packages debhelper depends on:
ii  autotools-dev20220109.1
ii  dh-autoreconf20
ii  dh-strip-nondeterminism  1.13.1-1
ii  dpkg 1.21.22
ii  dpkg-dev 1.21.22
ii  dwz  0.15-1
ii  file 1:5.44-3
ii  libdebhelper-perl13.11.4
ii  libdpkg-perl 1.21.22
ii  man-db   2.11.2-2
ii  perl 5.36.0-7
ii  po-debconf   1.0.21+nmu1

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn  dh-make  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmRvbOAACgkQ+C8H+466
LVmjwAv/XycR9Aw26knPSgSRtAvuhXWrEZUln1CwFJyF88Q38XJGwvXLNbL4IsyP
dBJRMVTNo4LHa0zAuN2qXPTwbzi4WjIDvRum6rqVB9t/CNZx6mh5A4bx+8dxnKQ6
kOg/CW4db76y5O5uVhd79YH+9BIrozpEDPdy7sUfcrf5eyOaJjD7EGnimSQQkTNQ
pJPrFHcoNFr0jY7xDyZXf9TLoR8dlZGz2vi4jRhB9baQIsT7Fp1Db+WbYQ62yFtW
V0j2SjV+5Wvy8nJRgdWjmnpa4uYZLC/Lt6jlhpzFvmt6bx11IzIFmDEhBofWcB9o
TB7U/aKsNfnSOwqunV2kKFaVuuJ07ZPkdJpigsDa7HX11kurmcs/6Ev1IlmBBRWw
nJcDnnTeJsdi0HF7M69dSjerShCbGBbrDXbJfHbQaZIdjbbb7S/RAESpaf4jjr+p
z5IC+asIZBNFyyToCR2paIbSgBZ/y+Qmd0Ml+8//E3bD0ccX17ne8Txg24Zgr5lo
1HGATnhE
=tmva
-END PGP SIGNATURE-

Bug#1036759: unblock: heat-cfntools/1.4.2-3

[Thomas Goirand]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: heat-cfnto...@packages.debian.org
Control: affects -1 + src:heat-cfntools

Please unblock package heat-cfntools

[ Reason ]
The fix packages the missing code of heat-cfntools.

[ Impact ]
Package is otherwise not useable (import fails when
launching the command line).

[ Risks ]
No risk, this just adds the missing files.

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

unblock heat-cfntools/1.4.2-3
diff --git a/debian/changelog b/debian/changelog
index 624b1c9..cb37a99 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+heat-cfntools (1.4.2-3) unstable; urgency=medium
+
+  * Also package heat-cfntools python module (Closes: #1035994).
+
+ -- Thomas Goirand   Mon, 22 May 2023 15:40:56 +0200
+
 heat-cfntools (1.4.2-2.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff --git a/debian/heat-cfntools.install b/debian/heat-cfntools.install
index 75f3882..02bc81e 100644
--- a/debian/heat-cfntools.install
+++ b/debian/heat-cfntools.install
@@ -1 +1,2 @@
 bin/* /usr/bin/
+/usr
diff --git a/debian/rules b/debian/rules
index f5a5585..a90397c 100755
--- a/debian/rules
+++ b/debian/rules
@@ -6,7 +6,7 @@ include /usr/share/openstack-pkg-tools/pkgos.make
dh $@ --with python3
 
 override_dh_auto_install:
-   pkgos-dh_auto_install --no-py2
+   pkgos-dh_auto_install --no-py2 --in-tmp
 
 override_dh_auto_build:
echo "Do nothing..."

Bug#1036758: unblock: cloud-initramfs-tools/0.18.debian13

[Thomas Goirand]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: cloud-initramfs-to...@packages.debian.org
Control: affects -1 + src:cloud-initramfs-tools

Please unblock package cloud-initramfs-tools

[ Reason ]
This fixes the path to udevadm.

[ Impact ]
The package is not useable without this patch.

[ Risks ]
Not much, it's been manually tested.
Thanks to Andreas Beckmann for the patch.

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

unblock cloud-initramfs-tools/0.18.debian13
diff --git a/debian/changelog b/debian/changelog
index c1720fa..95d0090 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+cloud-initramfs-tools (0.18.debian13) unstable; urgency=medium
+
+  [ Andreas Beckmann ]
+  * Fix copy_exec /bin/udevadm /sbin (Closes: #1035920).
+
+ -- Thomas Goirand   Wed, 24 May 2023 13:16:27 +0200
+
 cloud-initramfs-tools (0.18.debian12) unstable; urgency=medium
 
   [ Martin Pitt ]
diff --git a/growroot/hooks/growroot b/growroot/hooks/growroot
index 5d06aa8..a8ee1ab 100644
--- a/growroot/hooks/growroot
+++ b/growroot/hooks/growroot
@@ -11,7 +11,7 @@ esac
 ##
 copy_exec /sbin/sfdisk /sbin
 copy_exec /usr/bin/growpart /sbin
-copy_exec /usr/bin/udevadm /sbin
+copy_exec /bin/udevadm /sbin
 copy_exec /usr/bin/flock /bin
 
 # vi: ts=4 noexpandtab

Bug#1036744: PTP in combination with vclocks partially broken on Debian kernels

[Salvatore Bonaccorso]

Control: tags -1 - moreinfo
Control: tags -1 + confirmed

Hi Ben,

On Thu, May 25, 2023 at 03:07:24PM +0200, Ben Hutchings wrote:
> On Thu, 2023-05-25 at 10:37 +0200, Salvatore Bonaccorso wrote:
> > Hi Florian,
> > 
> > [dropping a typoed mail from my to not cause further bounces]
> > 
> > On Thu, May 25, 2023 at 10:18:46AM +0200, Florian Bezdeka wrote:
> > > On Thu, 2023-05-25 at 10:03 +0200, Salvatore Bonaccorso wrote:
> [...]
> > > 
> > > > Ben, would you agree on make the PTP support.
> > > > 
> > > > > It would be possible that we provide a merge request on
> > > > > salsa.debian.org. Just tell me the correct target branch. We would be
> > > > > very happy to have it in 6.1 (bookworm) and of course in all kernel
> > > > > flavors/feature sets.
> > > > 
> > > > I do not plan do accept any further bookworm targetting updates *right
> > > > now*, mabye later for bookworm point releases as we are now in full
> > > > freeze. There is no further upload planned for the 6.1.y series to
> > > > unstable, following to be migrated in testing before the bookworm
> > > > release. We can first apply to master and experimental upload if
> > > > agreed on the following change above and then consider it later for
> > > > bookworm. 
> > > 
> > > I think a point release would be acceptable for us. Sounds like a plan!
> > > Thanks!
> > 
> > Let's see if there are comments from Ben or Arnd on the proposed
> > change.
> 
> I agree we should make this built-in (except on armel/marvell).

Thanks for confirming, so this change can go into the master branch
first.

Regards,
Salvatore

Bug#1035631: libcurlpp-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Followup-For: Bug #1035631
Control: tag -1 patch pending

I've uploaded a verified fix to DELAYED/1 to reach the bookworm deadline.


Andreas
diff -Nru curlpp-0.8.1/debian/changelog curlpp-0.8.1/debian/changelog
--- curlpp-0.8.1/debian/changelog   2021-09-03 09:36:39.0 +0200
+++ curlpp-0.8.1/debian/changelog   2023-05-25 15:39:56.0 +0200
@@ -1,3 +1,11 @@
+curlpp (0.8.1-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * libcurlpp-dev: Perform symlink to directory conversion of
+/usr/share/doc/libcurlpp-dev.  (Closes: #1035631)
+
+ -- Andreas Beckmann   Thu, 25 May 2023 15:39:56 +0200
+
 curlpp (0.8.1-5) unstable; urgency=medium
 
   * Do not ship symbols at the moment.
diff -Nru curlpp-0.8.1/debian/libcurlpp-dev.maintscript 
curlpp-0.8.1/debian/libcurlpp-dev.maintscript
--- curlpp-0.8.1/debian/libcurlpp-dev.maintscript   1970-01-01 
01:00:00.0 +0100
+++ curlpp-0.8.1/debian/libcurlpp-dev.maintscript   2023-05-25 
15:38:51.0 +0200
@@ -0,0 +1 @@
+symlink_to_dir /usr/share/doc/libcurlpp-dev libcurlpp0 0.8.1-5.1~

Bug#1017587: ITP: fheroes2 -- free remake of Heroes of Might and Magic II game engine

[Alexandre Detiste]

Can you publish you git packaging tree somewhere ?

(Salsa, GitHub ...)

Greetings


pgppXLFIGMhf8.pgp
Description: OpenPGP digital signature

Bug#1036757: unblock: debian-security-support/1:12+2023.05.12

[Holger Levsen]

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

Please unblock package debian-security-support to update the status
of security-support in bookworm. The debdiff is trivial:

$ debdiff debian-security-support_12+2023.05.04.dsc 
debian-security-support_12+2023.05.12.dsc
diff -Nru debian-security-support-12+2023.05.04/debian/changelog 
debian-security-support-12+2023.05.12/debian/changelog
--- debian-security-support-12+2023.05.04/debian/changelog  2023-05-04 
19:09:45.0 +0200
+++ debian-security-support-12+2023.05.12/debian/changelog  2023-05-12 
14:45:22.0 +0200
@@ -1,3 +1,14 @@
+debian-security-support (1:12+2023.05.12) unstable; urgency=medium
+
+  [ Holger Levsen ]
+  * Add wpewebkit to security-support-ended.deb12. Thanks to Alberto Garcia.
+Closes: #1035794.
+
+  [ Markus Koschany ]
+  * Add pluxml to security-support-ended.deb10.
+
+ -- Holger Levsen   Fri, 12 May 2023 14:45:22 +0200
+
 debian-security-support (1:12+2023.05.04) unstable; urgency=medium
 
   [ Holger Levsen ]
diff -Nru debian-security-support-12+2023.05.04/security-support-ended.deb10 
debian-security-support-12+2023.05.12/security-support-ended.deb10
--- debian-security-support-12+2023.05.04/security-support-ended.deb10  
2023-04-14 13:16:33.0 +0200
+++ debian-security-support-12+2023.05.12/security-support-ended.deb10  
2023-05-12 10:25:30.0 +0200
@@ -10,7 +10,6 @@
 # 4. Descriptive text or URL with more details (optional)
 #In the program's output, this is prefixed with "Details:"
 
-# none yet (please remove this line once this is not true anymore)
 libperlspeak-perl2.01-2  2020-04-16  
https://bugs.debian.org/954238 (CVE-2020-10674) and 
https://bugs.debian.org/954297 and 954298
 xen  4.11.4+107-gef32c7afa2-12021-08-28  
https://xenbits.xen.org/docs/4.11-testing/SUPPORT.html#release-support
 chromium 90.0.4430.212-1~deb10u1 2022-01-14  
https://lists.debian.org/debian-security-announce/2022/msg00012.html
@@ -18,3 +17,4 @@
 gpac 0.5.2-426-gc5ad4e4+dfsg5-5  2022-08-03  
https://lists.debian.org/debian-lts/2022/05/msg00043.html
 libspring-java   4.3.5-1+deb9u1  2022-08-09  
https://lists.debian.org/debian-lts/2022/08/msg1.html
 ckeditor33.6.6.1+dfsg-1  2022-08-09  
https://lists.debian.org/debian-lts/2022/08/msg1.html
+pluxml   5.6-1   2023-05-06  Removed from 
Debian. No upstream response to CVE.
diff -Nru debian-security-support-12+2023.05.04/security-support-ended.deb12 
debian-security-support-12+2023.05.12/security-support-ended.deb12
--- debian-security-support-12+2023.05.04/security-support-ended.deb12  
2023-04-14 13:16:33.0 +0200
+++ debian-security-support-12+2023.05.12/security-support-ended.deb12  
2023-05-12 10:25:58.0 +0200
@@ -10,4 +10,4 @@
 # 4. Descriptive text or URL with more details (optional)
 #In the program's output, this is prefixed with "Details:"
 
-# none yet (please remove this line once this is not true anymore)
+wpewebkit  2.38.6-12023-05-09  
https://bugs.debian.org/1035794

unblock debian-security-support/1:12+2023.05.12

Thanks!

-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Covid. Changing hearts and minds since 2019. (@1goodtern)


signature.asc
Description: PGP signature

Bug#1036743: [Debian-med-packaging] Bug#1036743: kleborate: debsums reports modified files after apt-get upgrade && apt-get dist-upgrade

[Andreas Beckmann]

On 25/05/2023 14.42, Andreas Tille wrote:

Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier:


Installation of kleborate from sid and testing shown no issues.
Installation of kleborate from bullseye on bullseye is okay too.


Good.  Maybe we should reflect in BTS that this bug is not relevant for
bookworm?


It is relevant for bookworm, it's just not happening in the upgrade 
tests on piuparts.d.o (because that does no 2-step upgrades)


In the failing test kleborate got upgraded during 'apt-get upgrade' 
while ncbi-blast+ only got upgraded during the subsequent 'apt-get 
dist-upgrade'. So the kleborate.postinst from bookworm was actually 
running makeblastdb from bullseye, creating files in the "older" format.
Are these "old format" files still correctly usable after the 
dist-upgrade has been performed? Or would that need some kind of trigger 
mechanism to regenerate these files with the newer makeblastdb version?



I haven't checked closely yet, but I suspect the .ndb and .ntf
should be removed from the .deb and rely entirely on mkaeblastdb
to produce the files.  Looking that up…


Without checking this seems to be a sensible assumption.


Yes. Either the file is created at build time or at installation time. 
Doing both does not look like a sensible idea to me.
(And it didn't produce identical files, otherwise I wouldn't have 
noticed this bug)


Andreas

Bug#865183: libjpeg6b: please build-depend on automake, not obsolete automake1.11

[Bastian Germann]

libjpeg6b is not going anywhere.
I would like to suggest to remove the package for the purpose of reducing the 
automake1.11 dependent package.
libjpeg6b has not been part of a Debian release in years. What is the reason 
for it staying in unstable?

If nobody answers I am going to file a RM bug in some weeks.

Bug#1036744: PTP in combination with vclocks partially broken on Debian kernels

[Ben Hutchings]

On Thu, 2023-05-25 at 10:37 +0200, Salvatore Bonaccorso wrote:
> Hi Florian,
> 
> [dropping a typoed mail from my to not cause further bounces]
> 
> On Thu, May 25, 2023 at 10:18:46AM +0200, Florian Bezdeka wrote:
> > On Thu, 2023-05-25 at 10:03 +0200, Salvatore Bonaccorso wrote:
[...]
> > 
> > > Ben, would you agree on make the PTP support.
> > > 
> > > > It would be possible that we provide a merge request on
> > > > salsa.debian.org. Just tell me the correct target branch. We would be
> > > > very happy to have it in 6.1 (bookworm) and of course in all kernel
> > > > flavors/feature sets.
> > > 
> > > I do not plan do accept any further bookworm targetting updates *right
> > > now*, mabye later for bookworm point releases as we are now in full
> > > freeze. There is no further upload planned for the 6.1.y series to
> > > unstable, following to be migrated in testing before the bookworm
> > > release. We can first apply to master and experimental upload if
> > > agreed on the following change above and then consider it later for
> > > bookworm. 
> > 
> > I think a point release would be acceptable for us. Sounds like a plan!
> > Thanks!
> 
> Let's see if there are comments from Ben or Arnd on the proposed
> change.

I agree we should make this built-in (except on armel/marvell).

Ben.

-- 
Ben Hutchings - Debian developer, member of kernel, installer and LTS
teams

Bug#1035933: linux-image-6.1.0-8-amd64-unsigned: fails to build (llvm-strip not found, missing dependency?)

[Jochen Sprickerhof]

Thanks for the information. I don't see why it should use llvm, on the 
other hand the kernel Makefile is rather clear when to use it. Can you 
check if you an still reproduce the problem?


* Claude Heiland-Allen  [2023-05-25 11:47]:

Hi Jochen,

I didn't set any non-standard compiler options as far as I recall.
I certainly was not intending to build with LLVM.
Unfortunately I have not kept the log of the failing build,
but I remember seeing that gcc was used for the majority of the 
compilation.


Regards,


Claude

PS: export output as requested:

$ export
declare -x ANDROID_HOME="/home/claude/opt/android"
declare -x ANDROID_NDK_HOME="/home/claude/opt/android/ndk/21.4.7075529"
declare -x CLUTTER_IM_MODULE="ibus"
declare -x COLORTERM="truecolor"
declare -x DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"
declare -x DESKTOP_SESSION="xfce"
declare -x DISPLAY=":0.0"
declare -x GDMSESSION="xfce"
declare -x 
GNOME_TERMINAL_SCREEN="/org/gnome/Terminal/screen/0b1a867e_925f_4768_96f3_643cc3c21d91"
declare -x GNOME_TERMINAL_SERVICE=":1.84"
declare -x GTK_IM_MODULE="ibus"
declare -x GTK_MODULES="gail:atk-bridge"
declare -x HOME="/home/claude"
declare -x LANG="en_GB.UTF-8"
declare -x LANGUAGE="en_GB:en"
declare -x LD_LIBRARY_PATH="/home/claude/opt/lib"
declare -x LOGNAME="claude"
declare -x 
LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35
:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.swp=00;90:*.tmp=00;90:*.dpkg-dist=00;90:*.dpkg-old=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:"
declare -x OLDPWD
declare -x PANEL_GDK_CORE_DEVICE_EVENTS="0"
declare -x 
PATH="/home/claude/opt/vbcc/vbcc/bin:/opt/amiga/bin:/home/claude/opt/android/ndk/21.4.7075529:/home/claude/opt/android/platform-tools:/home/claude/opt/android/tools:/home/claude/opt/bin:/home/claude/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/claude/opt/bin"
declare -x PWD="/home/claude"
declare -x QT_ACCESSIBILITY="1"
declare -x QT_IM_MODULE="ibus"
declare -x QT_QPA_PLATFORMTHEME="gtk2"
declare -x 
SESSION_MANAGER="local/eiskaffee:@/tmp/.ICE-unix/1911,unix/eiskaffee:/tmp/.ICE-unix/1911"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_AGENT_PID="2048"
declare -x SSH_AUTH_SOCK="/tmp/ssh-XXtd5uft/agent.1911"
declare -x TERM="xterm-256color"
declare -x USER="claude"
declare -x VBCC="/opt/amiga/vbcc"
declare -x VTE_VERSION="7003"
declare -x XAUTHORITY="/home/claude/.Xauthority"
declare -x XDG_CONFIG_DIRS="/etc/xdg"
declare -x XDG_CURRENT_DESKTOP="XFCE"
declare -x 
XDG_DATA_DIRS="/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share"
declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm/data/claude"
declare -x XDG_MENU_PREFIX="xfce-"
declare -x XDG_RUNTIME_DIR="/run/user/1000"
declare -x XDG_SEAT="seat0"
declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0"
declare -x XDG_SESSION_CLASS="user"
declare -x XDG_SESSION_DESKTOP="xfce"
declare -x XDG_SESSION_ID="2"
declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0"
declare -x XDG_SESSION_TYPE="x11"
declare -x XDG_VTNR="7"
declare -x XMODIFIERS="@im=ibus"



On 2023-05-25 09:20, Jochen Sprickerhof wrote:

Hi Claude,

the Debian kernel is compiled with GCC:

https://buildd.debian.org/status/fetch.php?pkg=linux=amd64=6.1.27-1=1683630698=0

and compiles just fine.

To compile the kernel with llvm you either need to set CC or LLVM 
variables:


https://www.kernel.org/doc/html/latest/kbuild/llvm.html

Bug#1036743: [Debian-med-packaging] Bug#1036743: kleborate: debsums reports modified files after apt-get upgrade && apt-get dist-upgrade

[Étienne Mollier]

I had difficulties reproducing the issue with piuparts, but I
manage to reproduce the problem as I suspected, with the
following upgrade path, most likely because of the inconsistent
makeblastdb version between the one used for building kleborate
in bookworm and the one "refreshed" during postinst by the one
available in bullseye:

 1.  kleborate from bullseye - ncbi-blast+ from bullseye
 dpkg --verify raises no complaints
 2.  kleborate from bookworm - ncbi-blast+ from bullseye
 dpkg --verify starts complaining here!
 3.  kleborate from bookworm - ncbi-blast+ from bookworm
 dpkg --verify still complains!

Upgrading on top of that with a package that only relies on
postinst script (and prerm to manually cleanup the artifacts):

 4.  kleborate fixed - ncbi-blast+ from bookworm
 dpkg --verify raises no complaints

The prerm change is important to ensure there are no leftovers
during package removal and purge.

The following upgrade path is also fixed:

 2. kleborate fixed - ncbi-blast+ from bullseye
dpkg --verify raises no complaints
 3. kleborate fixed - ncbi-blast+ from bookworm
dpkg --verify still raises no complaints

I just pushed my changes on salsa and will upload shorly if CI
tests do not raise anything else outstanding I would have missed
otherwise.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/3, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#1036743: [Debian-med-packaging] Bug#1036743: kleborate: debsums reports modified files after apt-get upgrade && apt-get dist-upgrade

[Étienne Mollier]

Hi Andreas Tille,

Andreas Tille, on 2023-05-25:
> Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier:
> > 
> > Installation of kleborate from sid and testing shown no issues.
> > Installation of kleborate from bullseye on bullseye is okay too.
> 
> Good.  Maybe we should reflect in BTS that this bug is not relevant for
> bookworm?

The problem is there is a specific upgrade order which causes
this bug to happen with the version provided in bookworm, so it
does affect this one too, but this is fixable.  I had difficulty
to reproduce the issue reliably with piuparts but I have the
manual steps.  Stay tuned, details are in a draft email.

Have a nice day,  :)
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#1036756: RM: accelio -- RoQA; low popcon; RC-buggy; dead upstream

[Bastian Germann]

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

Please remove accelio. The package has no reverse dependencies and a low popcon.
Upstream is dead and the package is RC-buggy since 2017.

Bug#1036743: [Debian-med-packaging] Bug#1036743: kleborate: debsums reports modified files after apt-get upgrade && apt-get dist-upgrade

[Andreas Tille]

Hi Étienne,

Am Thu, May 25, 2023 at 10:34:10AM +0200 schrieb Étienne Mollier:
> 
> Installation of kleborate from sid and testing shown no issues.
> Installation of kleborate from bullseye on bullseye is okay too.

Good.  Maybe we should reflect in BTS that this bug is not relevant for
bookworm?

> I suspect this is related to the following code snippet in
> postinst, where a change in makeblastdb output format from
> bullseye to bookworm could have caused a mismatch:
> 
> for fasta in /usr/lib/python3/dist-packages/kleborate/data/*.fasta ; 
> do
> makeblastdb -dbtype nucl -in "$fasta" > /dev/null
> done
> 
> I haven't checked closely yet, but I suspect the .ndb and .ntf
> should be removed from the .deb and rely entirely on mkaeblastdb
> to produce the files.  Looking that up…

Without checking this seems to be a sensible assumption.

Thanks a lot for picking this up that quickly

Andreas.

-- 
http://fam-tille.de

Bug#1036755: linux: 6.1.26 <= x < 6.1.30 breaks applications using mmap(MAP_32BIT)

[Apollon Oikonomopoulos]

Source: linux
Version: 6.1.27-1
Severity: critical
Tags: upstream
Affects: ganeti
Justification: breaks unrelated software

Dear Kernel Maintainers,

A regression was introduced with upstream commit 58c5d0d6d5,  
subsequently backported to 6.1 as 7e6631f7 and released with 6.1.26.  
These commits break MAP_32BIT and affect applications relying on it. In 
particular, we are seeing failures in ganeti's autopkgtests[1], where a 
daemon written in Haskell (the GHC linker uses MAP_32BIT) segfaults with 
a null pointer dereference. From the build artifacts:

 ganeti-luxid: mmap 4096 bytes at (nil): Cannot allocate memory
 ganeti-luxid: Try specifying an address with +RTS -xm -RTS

This has already been discussed on GHC's discourse[2] and has been fixed 
upstream, with the fix queued for 6.1.30[3]. Please consider upgrading 
to 6.1.30 or cherry-picking the fix for Bookworm.

Thanks,
Apollon

[1] https://ci.debian.net/packages/g/ganeti/testing/amd64/, notably the 
run at 2023-05-14 15:13:51 UTC, the first one running on 6.1.27.
[2] 
https://discourse.haskell.org/t/facing-mmap-4096-bytes-at-nil-cannot-allocate-memory-youre-not-alone/6259/9
[3] 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/diff/releases/6.1.30/maple_tree-make-maple-state-reusable-after-mas_empty_area.patch?id=5e2b871e17ca1d2f1f88c4dc6b6995b72e5fc8f2

Bug#1036754: ITP: spack -- flexible package manager for supercomputer

[Gürkan Myczko]

Package: wnpp
Severity: wishlist
Owner: Gürkan Myczko 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: spack
  Version : 0.20.0
  Upstream Authors: Spack Project Developers
  URL : https://spack.io/
* License : Apache-2.0 or MIT
  Description : flexible package manager for supercomputer
 This is a flexible package manager for supercomputer that supports 
multiple

 versions, configurations, platforms, and compilers.

Bug#1035904: dpkg currently warning about merged-usr systems (revisited)

[Matthew Vernon]

Hi,

This thread has rather veered off the initial bug report.

On 11/05/2023 13:16, Simon Richter wrote:

Hi,

On 5/11/23 10:59, Sean Whitton wrote:


Dear ctte, please consider overruling the dpkg maintainer to include
the patch from #994388[1].



Currently dpkg contains code to emit the merged-/usr warning, that's
dead code on Debian, but which becomes active when packages from the
Debian archive are copied unmodified into derivatives.


The way I see it (but I'm not a dpkg maintainer), the current 
implementation is correct, as dpkg does not support aliased directories, 
but Debian has decided to use it in such an environment nonetheless. The 
tech-ctte decision not to roll back usrmerge accepts responsibility for 
this decision, so silencing the warning on Debian is correct, but no one 
has accepted that responsibility for derived distributions.


Any derived distribution can easily go on record and request inclusion 
in the list of distributions where this warning is suppressed, by typing 
the phrase "Yes, I understand that this is a bad idea." into an email 
client.


I have considerable sympathy for this point of view. Further, given 
ongoing (and quite fruitful) discussion on how to resolve the 
outstanding issues around /usr-merge and dpkg, I don't think the 
question of dpkg's warning (and its unfortunate wording) is one that is 
useful for the technical committee (and the dpkg maintainers) to be 
spending time on right now.


I think I would feel differently if there were derivatives who had asked 
the dpkg maintainers to likewise exclude their distro from the warning 
had been rebuffed (though I suspect such folk will just be patching it 
out in their own builds).


Likewise I would expect that once we have finished sorting out the 
outstanding /usr-merge & dpkg issues that the warning would be removed.


But those scenarios aren't where we're at now, so I think the project 
should continue to focus on moving ourselves to the point where dpkg 
does support /usr-merge as implemented in Debian.


Regards,

Matthew

Bug#1034168: RFS: profile-cleaner/2.44-1 [ITP] -- Reduces browser profile size by cleaning their sqlite databases

[Peter B]

On 24/05/2023 22:04, Tobias Frost wrote:

Package: sponsorship-requests
Followup-For: Bug #1034168
Control: tags -1 moreinfo

Hi Peter,

some review:
- d/postinst is not a place to post messages to users;

What do you suggest then?  I could ditch the postinst and put the text
into the man page, but users are probably less like to see it.
Note, this is upstream's postinst, not something I added myself.



  also is does
not have the #DEBHELPER# token. dh_installdeb(1)
(For that, the lintian override is wrong too)

Oops. Fixed, and removed the override



doc/pc.1 says:
".\" Text automatically generated by txt2man"

It seems that the source is missing (the input file for txt2man)?
It would be nice to have this and create the manpage at build time.
(Can you ask upstream to include the source file of the manpage?)


Raised upstream
https://github.com/graysky2/profile-cleaner/issues/39


Thanks for your review.
Uploaded the latest upstream version 2.45 to Mentors
https://mentors.debian.net/package/profile-cleaner/

Bug#1036753: unblock: debian-science/1.14.5

[Andreas Tille]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-scie...@packages.debian.org, 
debian-scie...@lists.debian.org
Control: affects -1 + src:debian-science

Please unblock package debian-science

[ Reason ]
This is the usual update of the Blends metapackages short before the
release to reflect removals inside the freeze process.  Well, admittedly
its not the "usual" one.  I intended to get version 1.14.4 featuring
lots of changes into testing before the freeze and failed.  Its simply
my fault and I should have done this earlier - I'm very sorry about
this.  The consequence is a diff to the version in testing (1.14.3)
which is *way* larger than usually acceptable and I can perfectly
understand if you might reject this unblock request due to this large
diff which is not readable any more.  The consequence would be some
inconsistencies inside the metapackages which might have a non-optimal
user experience.

[ Impact ]
Some packages recommended inside the metapackages are removed from
bookworm.  Due to my late upload of 1.14.4 which contained a lot of
updates regarding packages created by Debian Science users would
miss quite some packages that are not mentioned in the dependencies
of the metapackages.

[ Tests ]
Unfortunately there are no tests for the metapackages.  However, they
are automatically created and thus checked against the package pool
and thus it is sensible to expect that the packages are fine.

[ Risks ]
There is no real code inside the metapackages so the packages are
extremely trivial and all are leaf packages so no other package is
depending from them and thus they can not break any other package.

[ Checklist ]
  [*] all changes are documented in the d/changelog
  [*] I reviewed all changes and I approve them
  [*] attach debdiff against the package in testing

[ Other info ]
I promise to deliver smaller diffs for the next release cycle.

unblock debian-science/1.14.5


debian-science_1.14.3-1.14.5.debdiff.gz
Description: application/gzip

Bug#1036752: bat: manpage is missing, README.debian is missing

[Kyungjoon Lee]

Package: bat
Version: 0.22.1-2
Severity: normal
X-Debbugs-Cc: kjoon...@gmail.com

Dear Maintainer,

After the bat binary was renamed from batcat to bat and back to batcat, the man 
page is no longer installed:

/usr/share/man/man1/batcat.1.gz

bookworm output:

$ dpkg -L bat
/.
/usr
/usr/bin
/usr/bin/batcat
/usr/share
/usr/share/doc
/usr/share/doc/bat
/usr/share/doc/bat/changelog.Debian.gz
/usr/share/doc/bat/changelog.gz
/usr/share/doc/bat/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/bat

Compare bullseye output:

$ dpkg -L bat
/.
/usr
/usr/bin
/usr/bin/batcat
/usr/share
/usr/share/doc
/usr/share/doc/bat
/usr/share/doc/bat/README.Debian
/usr/share/doc/bat/changelog.Debian.arm64.gz
/usr/share/doc/bat/changelog.Debian.gz
/usr/share/doc/bat/copyright
/usr/share/lintian
/usr/share/lintian/overrides
/usr/share/lintian/overrides/bat
/usr/share/man
/usr/share/man/man1
/usr/share/man/man1/batcat.1.gz

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: arm64 (aarch64)

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

Versions of packages bat depends on:
ii  libc62.36-9
ii  libgcc-s112.2.0-14
ii  libgit2-1.5  1.5.1+ds-1

bat recommends no packages.

bat suggests no packages.

-- no debconf information

Bug#1035877: webkit2gtk-driver: Encryption based porting error to non-sse2 systems fail website processes

[Alberto Garcia]

On Wed, May 10, 2023 at 03:26:40PM +0200, Christian Kiss wrote:

> specific websites do not work around encryption like password
> generation in yahoo or gmx login cookiesettings on.

Sorry, I'm not sure that I understand that sentence... could you try
to rephrase it? Thanks!

In general WebKit dropped support for non-SSE2 CPUs at least 5 years
ago and it does not even build in those CPUs. In Debian we're actually
patching the source to relax those requirements, and while it more or
less works fine for basic browsing we cannot guarantee that for all
features.

Berto

Bug#1035933: linux-image-6.1.0-8-amd64-unsigned: fails to build (llvm-strip not found, missing dependency?)

[Claude Heiland-Allen]

Hi Jochen,

I didn't set any non-standard compiler options as far as I recall.
I certainly was not intending to build with LLVM.
Unfortunately I have not kept the log of the failing build,
but I remember seeing that gcc was used for the majority of the 
compilation.


Regards,


Claude

PS: export output as requested:

$ export
declare -x ANDROID_HOME="/home/claude/opt/android"
declare -x ANDROID_NDK_HOME="/home/claude/opt/android/ndk/21.4.7075529"
declare -x CLUTTER_IM_MODULE="ibus"
declare -x COLORTERM="truecolor"
declare -x DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"
declare -x DESKTOP_SESSION="xfce"
declare -x DISPLAY=":0.0"
declare -x GDMSESSION="xfce"
declare -x 
GNOME_TERMINAL_SCREEN="/org/gnome/Terminal/screen/0b1a867e_925f_4768_96f3_643cc3c21d91"

declare -x GNOME_TERMINAL_SERVICE=":1.84"
declare -x GTK_IM_MODULE="ibus"
declare -x GTK_MODULES="gail:atk-bridge"
declare -x HOME="/home/claude"
declare -x LANG="en_GB.UTF-8"
declare -x LANGUAGE="en_GB:en"
declare -x LD_LIBRARY_PATH="/home/claude/opt/lib"
declare -x LOGNAME="claude"
declare -x 
LS_COLORS="rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35

:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:*~=00;90:*#=00;90:*.bak=00;90:*.old=00;90:*.orig=00;90:*.part=00;90:*.rej=00;90:*.swp=00;90:*.tmp=00;90:*.dpkg-dist=00;90:*.dpkg-old=00;90:*.ucf-dist=00;90:*.ucf-new=00;90:*.ucf-old=00;90:*.rpmnew=00;90:*.rpmorig=00;90:*.rpmsave=00;90:"
declare -x OLDPWD
declare -x PANEL_GDK_CORE_DEVICE_EVENTS="0"
declare -x 
PATH="/home/claude/opt/vbcc/vbcc/bin:/opt/amiga/bin:/home/claude/opt/android/ndk/21.4.7075529:/home/claude/opt/android/platform-tools:/home/claude/opt/android/tools:/home/claude/opt/bin:/home/claude/.local/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/claude/opt/bin"

declare -x PWD="/home/claude"
declare -x QT_ACCESSIBILITY="1"
declare -x QT_IM_MODULE="ibus"
declare -x QT_QPA_PLATFORMTHEME="gtk2"
declare -x 
SESSION_MANAGER="local/eiskaffee:@/tmp/.ICE-unix/1911,unix/eiskaffee:/tmp/.ICE-unix/1911"

declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_AGENT_PID="2048"
declare -x SSH_AUTH_SOCK="/tmp/ssh-XXtd5uft/agent.1911"
declare -x TERM="xterm-256color"
declare -x USER="claude"
declare -x VBCC="/opt/amiga/vbcc"
declare -x VTE_VERSION="7003"
declare -x XAUTHORITY="/home/claude/.Xauthority"
declare -x XDG_CONFIG_DIRS="/etc/xdg"
declare -x XDG_CURRENT_DESKTOP="XFCE"
declare -x 
XDG_DATA_DIRS="/usr/share/xfce4:/usr/local/share/:/usr/share/:/usr/share"

declare -x XDG_GREETER_DATA_DIR="/var/lib/lightdm/data/claude"
declare -x XDG_MENU_PREFIX="xfce-"
declare -x XDG_RUNTIME_DIR="/run/user/1000"
declare -x XDG_SEAT="seat0"
declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0"
declare -x XDG_SESSION_CLASS="user"
declare -x XDG_SESSION_DESKTOP="xfce"
declare -x XDG_SESSION_ID="2"
declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0"
declare -x XDG_SESSION_TYPE="x11"
declare -x XDG_VTNR="7"
declare -x XMODIFIERS="@im=ibus"



On 2023-05-25 09:20, Jochen Sprickerhof wrote:

Hi Claude,

the Debian kernel is compiled with GCC:

https://buildd.debian.org/status/fetch.php?pkg=linux=amd64=6.1.27-1=1683630698=0

and compiles just fine.

To compile the kernel with llvm you either need to set CC or LLVM 
variables:


https://www.kernel.org/doc/html/latest/kbuild/llvm.html

Can you send the output of `export` to check what is set in your 
environment?


Given that you don't use the default compiler and that the default
toolchain is provided by the build-essential package, I don't think
this is a 

Bug#1036740: Fix for CVE-2022-23123 causes afpd segfault with valid metadata

[Markus Koschany]

Hello Daniel,

Am Donnerstag, dem 25.05.2023 um 08:02 +0200 schrieb Salvatore Bonaccorso:
> > 
> > These two commits in upstream addressed this:
> > https://github.com/Netatalk/netatalk/commit/9d0c21298363e8174cdfca657e66c4d10819507b
> > https://github.com/Netatalk/netatalk/commit/4140e5495bac42ecb9b11975229c81e84762cc98

Both patches have been backported to Buster. You can find them as CVE-2022-
23123_part3.patch and CVE-2022-23123_part4.patch.

Did we miss something else?

Regards,

Markus


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

Bug#1036751: RFS: mini-httpd/1.30-4 [ITA] -- Small HTTP server

[Alexandru Mihail]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "mini-httpd":

 * Package name : mini-httpd
   Version  : 1.30-4
   Upstream contact : Jef Poskanzer j...@mail.acme.com
 * URL  : https://www.acme.com/software/mini_httpd
 * License  : BSD-2-clause
 * Vcs  : https://salsa.debian.org/debian/mini-httpd
   Section  : web

The source builds the following binary packages:

  mini-httpd - Small HTTP server

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

  https://mentors.debian.net/package/mini-httpd/

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

  dget -x 
https://mentors.debian.net/debian/pool/main/m/mini-httpd/mini-httpd_1.30-4.dsc

Changes since the last upload:

 mini-httpd (1.30-4) unstable; urgency=medium
 .
   * New maintainer. (Closes: #927950)
   * Added missing newline in the rules file
   * Bumped Standards-Version to 4.5.1

Regards,
-- 
  Alexandru Mihail

Bug#1035975: [pre-approval] unblock: mmdebstrap/1.3.5-X

[Luca Boccassi]

On Thu, 25 May 2023 at 11:04, Johannes Schauer Marin Rodrigues
 wrote:
>
> Hi,
>
> Quoting Luca Boccassi (2023-05-24 10:52:08)
> > Regarding dash, would it be possible for the autopkgtest to support both the
> > versions in unstable and experimental, so that it works and you can get it
> > unblocked?
>
> yes. The current version in unstable does exactly that. But as the dash 
> unblock
> request got denied I guess I should revert that change now and do another
> upload.

I think it makes sense to support both situations, in the very
unlikely but not impossible case that we'll need a later dash p-u
upload for any reason.

Kind regards,
Luca Boccassi

Bug#1036750: linux-image-5.10.0-23-marvell: sensors-detect command from lm-sensors package doesn't detect temperature sensor

[Limak Mi Rose]

Package: src:linux
Version: 5.10.179-1
Severity: normal
Tags: upstream
X-Debbugs-Cc: kamil.mi...@live.com

Dear Maintainer,

   * What led up to the situation?

Simply installing the image from debian sources. I've also opened issue
in lm-sensors repository
(https://github.com/lm-sensors/lm-sensors/issues/445) and I've been suggested 
to file this bug
report.

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

I've installed lm-sensors package, ran sensors-detect command and it
told me no sensors were detected by it but it does show fan speed by default.

limak@syrenka-nas:~$ sensors
g762-i2c-0-3e
Adapter: mv64xxx_i2c adapter
fan1: 548 RPM  (div = 1)

According to the site I've used as
guide in NAS configuration it used to work in 3.11 version of kernel: 
http://www.natisbad.org/NAS/#hw-temperature-sensor

Nevertheless the temperature value is already available in the system by cating 
file
/sys/class/thermal/thermal_zone0/temp:

limak@syrenka-nas:~$ cat /sys/class/thermal/thermal_zone0/temp
41100
limak@syrenka-nas:~$ awk '{printf("Marvell 88F6282 SoC Temperature = %.1f 
°C\n",$1/1e3)}' /sys/class/thermal/thermal_zone0/temp
Marvell 88F6282 SoC Temperature = 44.0 °C

If I understand it correctly all modules required  for this to work are
loaded but they don't work with eachother properly (I'd expect hwmon to
be used also by kirkwood_thermal):

limak@syrenka-nas:~$ lsmod | head -1; lsmod | egrep 
"g762|hwmon|kirkwood_thermal"
Module  Size  Used by
g762   20480  0
hwmon  28672  1 g762
kirkwood_thermal   16384  0

I've attempted to compile the kernely myself but I don't have
comfortable test environment for this and I ran out of Inodes on
the NAS (probably because I've done something wrong).

   * What was the outcome of this action?

No sensors detected and no temperature available by the sensors command.

   * What outcome did you expect instead?

Detection of CPU temp sensor and temperature values in sensors and htop.

-- Package-specific info:
** Version:
Linux version 5.10.0-23-marvell (debian-ker...@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 
Debian 5.10.179-1 (2023-05-12)

** Command line:
console=ttyS0,115200 reason=normal 
mtdparts=nand_mtd:0x18@0(u-boot),0x2@0x18(u-boot-env),0x60@0x20(uImage),0x100@0x80(minirootfs),0x680@0x180(jffs2);

** Tainted: W (512)
 * kernel issued warning

** Kernel log:
[   13.132445] [] (__pci_enable_msix_range) from [] 
(pci_alloc_irq_vectors_affinity+0x70/0x104)
[   13.142767] [] (pci_alloc_irq_vectors_affinity) from [] 
(xhci_run+0x128/0x498 [xhci_hcd])
[   13.152903] [] (xhci_run [xhci_hcd]) from [] 
(usb_add_hcd+0x444/0x618 [usbcore])
[   13.162221] [] (usb_add_hcd [usbcore]) from [] 
(usb_hcd_pci_probe+0x32c/0x39c [usbcore])
[   13.172176] [] (usb_hcd_pci_probe [usbcore]) from [] 
(xhci_pci_probe+0x18/0x100 [xhci_pci])
[   13.182343] [] (xhci_pci_probe [xhci_pci]) from [] 
(pci_device_probe+0x84/0xf4)
[   13.191456] [] (pci_device_probe) from [] 
(really_probe+0x274/0x488)
[   13.199605] [] (really_probe) from [] 
(device_driver_attach+0x4c/0x64)
[   13.207924] [] (device_driver_attach) from [] 
(__driver_attach+0x80/0x130)
[   13.216591] [] (__driver_attach) from [] 
(bus_for_each_dev+0x5c/0x80)
[   13.224821] [] (bus_for_each_dev) from [] 
(bus_add_driver+0xd4/0x1f0)
[   13.233054] [] (bus_add_driver) from [] 
(driver_register+0xb4/0xf8)
[   13.241115] [] (driver_register) from [] 
(do_one_initcall+0x64/0x1b0)
[   13.249355] [] (do_one_initcall) from [] 
(do_init_module+0x44/0x1e0)
[   13.257506] [] (do_init_module) from [] 
(sys_finit_module+0xbc/0xd0)
[   13.265657] [] (sys_finit_module) from [] 
(__sys_trace_return+0x0/0x1c)
[   13.274055] Exception stack(0xc2dbffa8 to 0xc2dbfff0)
[   13.279141] ffa0:   b6f1d13c 0099a510 0012 b6f1bf38 
 b6f1ccb0
[   13.287374] ffc0: b6f1d13c 0099a510 156bc300 017b 00998d18 0056356f 
005635e0 0099a510
[   13.295602] ffe0: be9c46f0 be9c46e0 b6f13c64 b6db7940
[   13.300690] ---[ end trace 2624a5770448d0e8 ]---
[   13.305341] [ cut here ]
[   13.309998] WARNING: CPU: 0 PID: 198 at include/linux/msi.h:225 
free_msi_irqs+0x17c/0x18c
[   13.318219] Modules linked in: xhci_pci(+) xhci_hcd ehci_orion(+) ehci_hcd 
marvell mv643xx_eth sg mvmdio orion_nand(+) usbcore orion_wdt nand marvell_cesa 
libdes nand_ecc usb_common watchdog nls_base libaes bch nandcore g762 
rtc_rs5c372 hwmon mtd rtc_mv(+) kirkwood_thermal gpio_keys leds_gpio fuse 
configfs ip_tables x_tables hmac ipv6 autofs4 ext4 crc16 mbcache jbd2 raid10 
raid456 libcrc32c crc32c_generic async_raid6_recov async_memcpy async_pq 
async_xor xor async_tx raid6_pq raid0 multipath linear raid1 md_mod sd_mod 
t10_pi crc_t10dif crct10dif_generic crct10dif_common sata_mv libata scsi_mod
[   13.371193] CPU: 0 PID: 198 Comm: systemd-udevd Tainted: 

Bug#1035975: [pre-approval] unblock: mmdebstrap/1.3.5-X

[Johannes Schauer Marin Rodrigues]

Hi,

Quoting Luca Boccassi (2023-05-24 10:52:08)
> Regarding dash, would it be possible for the autopkgtest to support both the
> versions in unstable and experimental, so that it works and you can get it
> unblocked?

yes. The current version in unstable does exactly that. But as the dash unblock
request got denied I guess I should revert that change now and do another
upload.

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#1021396: ITP: batterylog -- laptop battery logging tool

[Andreas Tille]

Hi,

since I keep on tracking down issues when my battery drains to zero when
in suspend mode I stumbled upon your discussion on framework
community[1] and this ITP.  Did you pushed something on salsa regarding
the packaging I might be able to try?

Kind regards
 Andreas.

[1] 
https://community.frame.work/t/linux-utility-to-help-track-framework-battery-usage/21729/2

-- 
http://fam-tille.de

Bug#1035522: debian-security-support 11+2023.05.04 flagged for acceptance

[Holger Levsen]

On Wed, May 24, 2023 at 10:05:19PM +0100, Adam D. Barratt wrote:
> Great. That's now 
> https://lists.debian.org/debian-stable-announce/2023/05/msg0.html
 
awesome, thank you!


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

wirklicher reichtum ist nicht privatjet fliegen, sondern sich vor dem schützen
können, was privatjet fliegen auslöst." <3 böhmermann am 3.2.23


signature.asc
Description: PGP signature

Bug#1035677: sane-utils: preinst deletes file owned by libsane-common: /usr/share/man/man5/sane-umax_pp.5.gz

[Andreas Beckmann]

On Tue, 16 May 2023 19:09:26 +0200 
=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?=  wrote:

please can you check the changes from


Sorry, I seem to have missed this mail ...

The changes look good and I can confirm that the upgrade issues are 
resolved with the .prerm removed. I've uploaded that to DELAYED/1.



Andreas

Bug#1036747: unblock: osmo-iuh/1.3.0+dfsg1-5

[Thorsten Alteholz]

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

Please unblock package osmo-iuh

[ Reason ]
The current version has a superficial autopkgtest that failed.
The new version still has a superficial autopkgtest but this
no longer fails.

[ Impact ]
Everywhere a autopkgtest of the package is required, a failure would be 
shown for this package.


[ Tests ]
This is only a change in the autopkgtests.

[ Risks ]
As there is no code change, there should be no risk.

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

unblock osmo-iuh/1.3.0+dfsg1-5
diff -Nru osmo-iuh-1.3.0+dfsg1/debian/changelog 
osmo-iuh-1.3.0+dfsg1/debian/changelog
--- osmo-iuh-1.3.0+dfsg1/debian/changelog   2022-10-13 22:23:21.0 
+0200
+++ osmo-iuh-1.3.0+dfsg1/debian/changelog   2023-05-22 23:23:21.0 
+0200
@@ -1,3 +1,20 @@
+osmo-iuh (1.3.0+dfsg1-5) unstable; urgency=medium
+
+  * really "fix" autopkgtest
+at the moment there is no binary in the binary packages available
+so make the superficial test a bit more superficial
+
+ -- Thorsten Alteholz   Mon, 22 May 2023 23:23:21 +0200
+
+osmo-iuh (1.3.0+dfsg1-4) unstable; urgency=medium
+
+  * "fix" autopkgtest
+at the moment there is no binary in the binary packages available
+so make the superficial test a bit more superficial
+(Closes: #1033823)
+
+ -- Thorsten Alteholz   Thu, 18 May 2023 13:23:21 +0200
+
 osmo-iuh (1.3.0+dfsg1-3) unstable; urgency=medium
 
   * upload to unstable
diff -Nru osmo-iuh-1.3.0+dfsg1/debian/tests/can-show-help 
osmo-iuh-1.3.0+dfsg1/debian/tests/can-show-help
--- osmo-iuh-1.3.0+dfsg1/debian/tests/can-show-help 2022-10-13 
22:23:21.0 +0200
+++ osmo-iuh-1.3.0+dfsg1/debian/tests/can-show-help 2023-05-22 
23:23:21.0 +0200
@@ -2,5 +2,7 @@
 
 set -e
 
-osmo-hnbgw -h
+# at the moment there is no binary in the binary packages available
+# so make the superficial test a bit more superficial
+#osmo-hnbgw -h
 echo "run: OK"
diff -Nru osmo-iuh-1.3.0+dfsg1/debian/tests/control 
osmo-iuh-1.3.0+dfsg1/debian/tests/control
--- osmo-iuh-1.3.0+dfsg1/debian/tests/control   2022-10-13 22:23:21.0 
+0200
+++ osmo-iuh-1.3.0+dfsg1/debian/tests/control   2023-05-22 23:23:21.0 
+0200
@@ -1,4 +1,4 @@
 Tests: can-show-help
-Depends: osmo-hnbgw
+#Depends: osmo-hnbgw
 Restrictions: superficial
 

Bug#1036749: unblock: udm/1.0.0.322-4

[Thorsten Alteholz]

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

Please unblock package udm

[ Reason ]
Due to a recent change in lazarus, the package could no longer be built.

[ Impact ]
The user would not be able to build the package.

[ Tests ]
As there is no code change but only a changed debian/rules file, no new 
tests are added.


[ Risks ]
As there is no code change, the risk should be low for this leaf package.


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

unblock udm/1.0.0.322-4
diff -Nru udm-1.0.0.322/debian/changelog udm-1.0.0.322/debian/changelog
--- udm-1.0.0.322/debian/changelog  2023-02-06 22:43:07.0 +0100
+++ udm-1.0.0.322/debian/changelog  2023-05-23 17:43:07.0 +0200
@@ -1,3 +1,11 @@
+udm (1.0.0.322-4) unstable; urgency=medium
+
+  * fix FTBFS (due to upload of new version of lazarus)
+(the solution leaves room for improvement)
+(Closes: #1036257)
+
+ -- Thorsten Alteholz   Tue, 23 May 2023 17:43:07 +0200
+
 udm (1.0.0.322-3) unstable; urgency=medium
 
   * add patch to use correct path for file installation
diff -Nru udm-1.0.0.322/debian/rules udm-1.0.0.322/debian/rules
--- udm-1.0.0.322/debian/rules  2023-02-06 12:27:35.0 +0100
+++ udm-1.0.0.322/debian/rules  2023-05-23 13:48:12.0 +0200
@@ -15,56 +15,56 @@
mkdir $(HOME)
echo "#INCLUDE /etc/fpc.cfg" > $(HOME)/.fpc.cfg
echo "-dLCLGTK2" >> $(HOME)/.fpc.cfg
-   echo "-Fu/usr/lib/lazarus/2.2.4/components/lazutils/lib/x86_64-linux" 
>> $(HOME)/.fpc.cfg
-   echo "-Fu/usr/lib/lazarus/2.2.4/packager/units/x86_64-linux" >> 
$(HOME)/.fpc.cfg
-   echo "-Fu/usr/lib/lazarus/2.2.4/lcl/units/x86_64-linux" >> 
$(HOME)/.fpc.cfg
-   echo 
"-Fu/usr/lib/lazarus/2.2.4/components/ideintf/units/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
-   echo 
"-Fu/usr/lib/lazarus/2.2.4/components/lazcontrols/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
-   echo 
"-Fu/usr/lib/lazarus/2.2.4/components/synedit/units/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
-   echo 
"-Fu/usr/lib/lazarus/2.2.4/components/tachart/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
-   echo 
"-Fu/usr/lib/lazarus/2.2.4/components/printers/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
-   echo 
"-Fu/usr/lib/lazarus/2.2.4/components/cairocanvas/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
-   echo "-Fu/usr/lib/lazarus/2.2.4/lcl/units/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
+   echo "-Fu/usr/lib/lazarus/2.2.6/components/lazutils/lib/x86_64-linux" 
>> $(HOME)/.fpc.cfg
+   echo "-Fu/usr/lib/lazarus/2.2.6/packager/units/x86_64-linux" >> 
$(HOME)/.fpc.cfg
+   echo "-Fu/usr/lib/lazarus/2.2.6/lcl/units/x86_64-linux" >> 
$(HOME)/.fpc.cfg
+   echo 
"-Fu/usr/lib/lazarus/2.2.6/components/ideintf/units/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
+   echo 
"-Fu/usr/lib/lazarus/2.2.6/components/lazcontrols/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
+   echo 
"-Fu/usr/lib/lazarus/2.2.6/components/synedit/units/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
+   echo 
"-Fu/usr/lib/lazarus/2.2.6/components/tachart/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
+   echo 
"-Fu/usr/lib/lazarus/2.2.6/components/printers/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
+   echo 
"-Fu/usr/lib/lazarus/2.2.6/components/cairocanvas/lib/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg
+   echo "-Fu/usr/lib/lazarus/2.2.6/lcl/units/x86_64-linux/gtk2/" >> 
$(HOME)/.fpc.cfg

-   ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttcalc4.inc
-   ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttconfig.inc
-   ln -s /usr/lib/lazarus/2.2.4/components/freetype/ttraster_sweep.inc
+   ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttcalc4.inc
+   ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttconfig.inc
+   ln -s /usr/lib/lazarus/2.2.6/components/freetype/ttraster_sweep.inc

-   ln -s /usr/lib/lazarus/2.2.4/components/opengl/openglcontext.res
+   ln -s /usr/lib/lazarus/2.2.6/components/opengl/openglcontext.res

-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/ideoptionsintf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/baseideintf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/macrointf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/macrodefintf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/compoptsintf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/projectintf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/newitemintf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/projpackintf.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/buildstrconsts.pas
-   ln -s /usr/lib/lazarus/2.2.4/components/buildintf/ideexterntoolintf.pas
-   ln -s 

Bug#1036748: unblock: libricohcamerasdk/1.1.0-4

[Thorsten Alteholz]

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

Please unblock package libricohcamerasdk

[ Reason ]
Due to some magic in debhelper/ldconfig a link to nowhere remained on the 
computer.

This link will be removed in postinst/postrm now.

[ Impact ]
The user will keep a link to a non existing file on his computer.

[ Tests ]
As there is no code change, no new test was added.

[ Risks ]
There should be no risks for this leaf package in non-free.

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

unblock libricohcamerasdk/1.1.0-4
diff -Nru libricohcamerasdk-1.1.0/debian/changelog 
libricohcamerasdk-1.1.0/debian/changelog
--- libricohcamerasdk-1.1.0/debian/changelog2022-05-18 23:30:36.0 
+0200
+++ libricohcamerasdk-1.1.0/debian/changelog2023-05-18 11:30:36.0 
+0200
@@ -1,3 +1,10 @@
+libricohcamerasdk (1.1.0-4) unstable; urgency=medium
+
+  * add postrm/postinst script to remove bad link
+(Closes: #1035795)
+
+ -- Thorsten Alteholz   Thu, 18 May 2023 11:30:36 +0200
+
 libricohcamerasdk (1.1.0-3) unstable; urgency=medium
 
   * manual build on: amd64 armhf
diff -Nru libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postinst 
libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postinst
--- libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postinst   1970-01-01 
01:00:00.0 +0100
+++ libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postinst   2023-05-18 
11:30:36.0 +0200
@@ -0,0 +1,33 @@
+#!/bin/sh
+
+set +e
+
+linkfile=$(ls -1 /usr/lib/*/libRicohCameraSDKCpp.so 2> /dev/null)
+readlinkfile=""
+if [ ! -z "$linkfile" ]; then
+  readlinkfile=$(readlink $linkfile 2> /dev/null)
+fi
+
+set -e
+
+case "$1" in
+configure)
+   # we shall not have a link from libRicohCameraSDKCpp.so to 
libRicohCameraSDKCpp.so.1.1.0
+   if [ -L "$linkfile" ]; then
+   if [ "$readlinkfile" = "libRicohCameraSDKCpp.so.1.1.0" ]; then
+   echo "D: wrong link detected, remove it again"
+   rm $linkfile
+   fi
+   fi
+   ;;
+abort-upgrade|abort-remove|abort-deconfigure)
+   ;;
+*)
+echo "postinst called with unknown argument \`$1'" >&2
+exit 1
+;;
+esac
+
+#DEBHELPER#
+
+exit 0
diff -Nru libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postrm 
libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postrm
--- libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postrm 1970-01-01 
01:00:00.0 +0100
+++ libricohcamerasdk-1.1.0/debian/libricohcamerasdk.postrm 2023-05-18 
11:30:36.0 +0200
@@ -0,0 +1,34 @@
+#!/bin/sh
+
+set +e
+
+linkfile=$(ls -1 /usr/lib/*/libRicohCameraSDKCpp.so 2> /dev/null)
+readlinkfile="" 
+if [ ! -z "$linkfile" ]; then
+  readlinkfile=$(readlink $linkfile 2> /dev/null)
+fi
+
+set -e
+
+
+case "$1" in
+purge|remove)
+   # we shall not have a link from libRicohCameraSDKCpp.so to 
libRicohCameraSDKCpp.so.1.1.0
+   if [ -L "$linkfile" ]; then
+   if [ "$readlinkfile" = "libRicohCameraSDKCpp.so.1.1.0" ]; then
+   echo "D: wrong link detected, remove it again"
+   rm $linkfile
+   fi
+   fi
+   ;;
+upgrade|failed-upgrade)
+   ;;
+*)
+   echo "postrm called with unknown argument \`$1'" >&2
+exit 1
+   ;;
+esac
+
+#DEBHELPER#
+
+exit 0

Bug#1033894: lintian: bad-distribution-in-changes-file bookworm

[Andreas Beckmann]

Followup-For: Bug #1033894

Shouldn't we release bookworm with a lintian that knows about bookworm?
Time is quickly running out ...

Andreas

Bug#1036746: lintian: package-contains-no-arch-dependent-files does not trigger if there is a header file with non-ascii (UTF-8) characters

[Andreas Beckmann]

Package: lintian
Version: 2.116.3
Severity: normal

I just looked into the spurious (dis-)appearance of

X: libnvidia-ml-dev: package-contains-no-arch-dependent-files

libnvidia-ml-dev is a header-only package:

$ find 1*
11.8.0
11.8.0/usr
11.8.0/usr/include
11.8.0/usr/include/nvml.h
11.8.0/usr/share
11.8.0/usr/share/doc
11.8.0/usr/share/doc/libnvidia-ml-dev
11.8.0/usr/share/doc/libnvidia-ml-dev/changelog.Debian.gz
11.8.0/usr/share/doc/libnvidia-ml-dev/copyright
11.8.0/usr/share/lintian
11.8.0/usr/share/lintian/overrides
11.8.0/usr/share/lintian/overrides/libnvidia-ml-dev
12.0.0
12.0.0/usr
12.0.0/usr/include
12.0.0/usr/include/nvml.h
12.0.0/usr/share
12.0.0/usr/share/doc
12.0.0/usr/share/doc/libnvidia-ml-dev
12.0.0/usr/share/doc/libnvidia-ml-dev/changelog.Debian.gz
12.0.0/usr/share/doc/libnvidia-ml-dev/copyright
12.0.1
12.0.1/usr
12.0.1/usr/include
12.0.1/usr/include/nvml.h
12.0.1/usr/share
12.0.1/usr/share/doc
12.0.1/usr/share/doc/libnvidia-ml-dev
12.0.1/usr/share/doc/libnvidia-ml-dev/changelog.Debian.gz
12.0.1/usr/share/doc/libnvidia-ml-dev/copyright

and the only difference I see is

$ file 1*/usr/include/nvml.h
11.8.0/usr/include/nvml.h: C source, ASCII text
12.0.0/usr/include/nvml.h: C source, UTF-8 Unicode text
12.0.1/usr/include/nvml.h: C source, ASCII text

The 11.8.0 package (in sid) does trigger
package-contains-no-arch-dependent-files (but it is overridden),
the 12.0.0 package (in experimental) does not trigger (therefore
override removed), while 12.0.1 (not yet uploaded) again triggers the
tag.

The only non-ascii char seems to be '’' (e2 80 99) in a comment ...


Andreas

Bug#1036745: unblock: qtbase-opensource-src-gles/5.15.8+dfsg-3

[Dmitry Shachnev]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: qtbase-opensource-src-g...@packages.debian.org
Control: affects -1 + src:qtbase-opensource-src-gles

Please unblock package qtbase-opensource-src-gles.

[ Reason ]
* Fixes for two CVEs (CVE-2023-24607 and CVE-2023-32763).
* Updated image_deletion_order.diff to fix dangling or incorrect
  device pointers during handler destruction.
* Fix for cross-building (#1029082).
* Minor update for debian/libqt5gui5-gles.symbols.

[ Impact ]
Of these fixes, CVE-2023-32763 is the most important. It is possible to
trigger a buffer overflow when rendering SVG files.

[ Tests ]
No automated tests are run for this package. But patches that come from
upstream are covered by upstream tests.

[ Risks ]
I think the risk is low. Most of these fixes are already present in the
non-gles variant of the package in testing (5.15.8+dfsg-10) and have been
tested by many users. Except for the cross-build fix which is specific to
the -gles variant, but that fix is only applied when cross-building and
does not affect regular builds.

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

[ Other info ]
(Anything else the release team should know.)

unblock qtbase-opensource-src-gles/5.15.8+dfsg-3

--
Dmitry Shachnev
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,28 @@
+qtbase-opensource-src-gles (5.15.8+dfsg-3) unstable; urgency=medium
+
+  * Add a patch to fix CVE-2023-32763: buffer overflow in Qt SVG
+(closes: #1036702).
+
+ -- Dmitry Shachnev   Wed, 24 May 2023 20:52:26 +0300
+
+qtbase-opensource-src-gles (5.15.8+dfsg-2) unstable; urgency=medium
+
+  * Merge qtbase-opensource-src 5.15.8+dfsg-3 upload.
+  * Compare only upstream version of qt5-qmake-bin when cross-building
+(closes: #1029082).
+
+ -- Dmitry Shachnev   Sat, 04 Mar 2023 14:39:27 +0300
+
+qtbase-opensource-src (5.15.8+dfsg-3) unstable; urgency=medium
+
+  * Use ${DEB_HOST_GNU_TYPE} substitution in debian/qt5-qmake.install.
+  * Add upstream patch to fix denial-of-service in Qt SQL ODBC plugin
+(CVE-2023-24607, closes: #1031872).
+  * Update debian/libqt5gui5.symbols from s390x build log.
+  * Amend image_deletion_order.diff from one more upstream commit.
+
+ -- Dmitry Shachnev   Mon, 27 Feb 2023 11:28:53 +0300
+
 qtbase-opensource-src-gles (5.15.8+dfsg-1) unstable; urgency=medium
 
   * Merge qtbase-opensource-src 5.15.8+dfsg-2 upload.
--- a/debian/libqt5gui5-gles.symbols
+++ b/debian/libqt5gui5-gles.symbols
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 5.15.4 amd64 hppa powerpc ppc64 s390x sparc64
+# SymbolsHelper-Confirmed: 5.15.8 s390x
 libQt5Gui.so.5 libqt5gui5 #MINVER# | libqt5gui5-gles #MINVER#
 | libqt5gui5 #MINVER# | libqt5gui5-gles #MINVER#, qtbase-abi-5-15-8
 | libqt5gui5 #MINVER#
@@ -1563,7 +1563,7 @@ libQt5Gui.so.5 libqt5gui5 #MINVER# | libqt5gui5-gles #MINVER#
  _ZN16QDoubleValidatorD0Ev@Qt_5 5.0.2
  _ZN16QDoubleValidatorD1Ev@Qt_5 5.0.2
  _ZN16QDoubleValidatorD2Ev@Qt_5 5.0.2
- (optional=inline|arch=!hppa !ia64 !s390x)_ZN16QOpenGLFunctions17glBindFramebufferEjj@Qt_5 5.15.2
+ (optional=inline|arch=!hppa !ia64)_ZN16QOpenGLFunctions17glBindFramebufferEjj@Qt_5 5.15.2
  _ZN16QOpenGLFunctions25initializeOpenGLFunctionsEv@Qt_5 5.0.2
  _ZN16QOpenGLFunctionsC1EP14QOpenGLContext@Qt_5 5.0.2
  _ZN16QOpenGLFunctionsC1Ev@Qt_5 5.0.2
--- /dev/null
+++ b/debian/patches/CVE-2023-24607.diff
@@ -0,0 +1,330 @@
+Description: Fix denial-of-service in Qt SQL ODBC driver plugin
+Origin: upstream, https://download.qt.io/official_releases/qt/5.15/CVE-2023-24607-qtbase-5.15.diff
+Last-Update: 2023-02-26
+
+--- a/src/plugins/sqldrivers/odbc/qsql_odbc.cpp
 b/src/plugins/sqldrivers/odbc/qsql_odbc.cpp
+@@ -92,23 +92,39 @@ inline static QString fromSQLTCHAR(const
+ return result;
+ }
+ 
++template 
++void toSQLTCHARImpl(QVarLengthArray , const QString ); // primary template undefined
++
++template 
++void do_append(QVarLengthArray , const Container )
++{
++result.append(reinterpret_cast(c.data()), c.size());
++}
++
++template <>
++void toSQLTCHARImpl<1>(QVarLengthArray , const QString )
++{
++const auto u8 = input.toUtf8();
++do_append(result, u8);
++}
++
++template <>
++void toSQLTCHARImpl<2>(QVarLengthArray , const QString )
++{
++do_append(result, input);
++}
++
++template <>
++void toSQLTCHARImpl<4>(QVarLengthArray , const QString )
++{
++const auto u32 = input.toUcs4();
++do_append(result, u32);
++}
++
+ inline static QVarLengthArray toSQLTCHAR(const QString )
+ {
+ QVarLengthArray result;
+-result.resize(input.size());
+-switch(sizeof(SQLTCHAR)) {
+-case 1:
+-memcpy(result.data(), input.toUtf8().data(), input.size());
+-break;
+-case 2:
+-memcpy(result.data(), input.unicode(), input.size() * 2);
+-break;
+-case 4:
+- 

Bug#1032995: spyder: Spyder on startup says there is a missing dependency (pylsp_black) but it is correctly installed

[Julian Gilbey]

On Wed, May 24, 2023 at 05:13:29PM -0700, Brian Vaughan wrote:
> I'm seeing the same issue, on two different systems, both running Debian
> Sid.
> 
> On one system, there were some libraries under ~/.local/lib/python3.10; I
> deleted those, deleted the config files for spyder, reinstalled it, and
> rebooted, but still saw the error.

Oh dear, this is weird.  Thanks for letting me know.

Please could you start spyder (acknowledging the missing-dependency
warning) and then do Help > Dependencies.  It will give you a list of
dependencies loaded which you can then copy to the clipboard; please
can you send the results to this bug report?  Please do the same with
Help > About Spyder...  These may give some clues.

The next thing we can try is running the following in the iPython
console within Spyder:

import sys
sys.executable
sys.path
import pylsp_black
sys.modules["pylsp_black"]

Please send the output to this report, as there may be some clues
there.

Best wishes,

   Julian