Bug#1052223: marked as done (insighttoolkit5: Use full ::itk namespace in itkMacro.h)

[Debian Bug Tracking System]

Your message dated Mon, 25 Sep 2023 05:51:16 +
with message-id 
and subject line Bug#1052223: fixed in insighttoolkit5 5.3.0-6
has caused the Debian Bug report #1052223,
regarding insighttoolkit5: Use full ::itk namespace in itkMacro.h
to be marked as done.

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

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


-- 
1052223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052223
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sight
Version: 21.1.1-3
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=sight=amd64=21.1.1-3%2Bb2=1687809257=0

[ 66%] Linking CXX shared library 
../../../lib/x86_64-linux-gnu/libsight_module_filter_vision.so
cd /<>/obj-x86_64-linux-gnu/modules/filter/vision && 
/usr/bin/cmake -E cmake_link_script 
CMakeFiles/module_filter_vision.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wl,--as-needed -Wl,--sort-common -Wl,-O2 
-Wl,-z,relro -Wl,-z,now -shared 
-Wl,-soname,libsight_module_filter_vision.so.21.1 -o 
../../../lib/x86_64-linux-gnu/libsight_module_filter_vision.so.21.1.0 
CMakeFiles/module_filter_vision.dir/Plugin.cpp.o 
CMakeFiles/module_filter_vision.dir/SColourImageMasking.cpp.o 
CMakeFiles/module_filter_vision.dir/SDepthImageMasking.cpp.o 
CMakeFiles/module_filter_vision.dir/SOpticalFlow.cpp.o 
CMakeFiles/module_filter_vision.dir/SPointCloudFromDepthMap.cpp.o 
CMakeFiles/module_filter_vision.dir/STransformDepthMap2mm.cpp.o 
CMakeFiles/module_filter_vision.dir/STransformDepthTL2mm.cpp.o 
CMakeFiles/module_filter_vision.dir/SUltrasoundImage.cpp.o 
CMakeFiles/module_filter_vision.dir/registerServices.cpp.o  
-Wl,-rpath,/<>/obj-x86_64-linux-gnu/lib/x86_64-linux-gnu: 
/usr/lib/x86_64-linux-gnu/libopencv_highgui.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_video.so.4.6.0 
../../../lib/x86_64-linux-gnu/libsight_service.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_geometry_data.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_filter_vision.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_io_opencv.so.21.1.0 
/usr/lib/x86_64-linux-gnu/libopencv_videoio.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_imgcodecs.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_dnn.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_features2d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_flann.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.6.0 
../../../lib/x86_64-linux-gnu/libsight_activity.so.21.1.0 
/usr/lib/x86_64-linux-gnu/libopencv_ml.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.6.0 
../../../lib/x86_64-linux-gnu/libsight_data.so.21.1.0 
../../../lib/x86_64-linux-gnu/libsight_core.so.21.1.0 
/usr/lib/x86_64-linux-gnu/libboost_date_time.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_log_setup.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_log.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_chrono.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_regex.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_thread.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_atomic.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.74.0 
/usr/lib/x86_64-linux-gnu/libxml2.so /usr/lib/x86_64-linux-gnu/libcrypto.so 
-ldl /usr/lib/x86_64-linux-gnu/libopencv_calib3d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_features2d.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_flann.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_imgproc.so.4.6.0 
/usr/lib/x86_64-linux-gnu/libopencv_core.so.4.6.0 
In file included from /usr/include/ITK-5.3/itkLightObject.h:21,
 from /usr/include/ITK-5.3/itkObject.h:31,
 from /usr/include/ITK-5.3/itkLightProcessObject.h:21,
 from /usr/include/ITK-5.3/itkImageIOBase.h:24,
 from 
/<>/libs/io/itk/inr2itk/itkInrImageIOFactory.hpp:25,
 from /<>/libs/io/itk/ImageReader.cpp:25:
/<>/libs/io/itk/helper/ProgressItkToFw.hxx:48:5: error: 
‘LightObject’ in namespace ‘sight::io::itk’ does not name a type
   48 | itkNewMacro(Self);
  | ^~~
/<>/libs/io/itk/helper/ProgressItkToFw.hxx: In static member 
function ‘static sight::io::itk::LocalCommand::Pointer 
sight::io::itk::LocalCommand::New()’:

Bug#1052223: marked as pending in insighttoolkit

[Steven Robbins]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/med-team/insighttoolkit/-/commit/d47841b9d2d96c47ab7a98a2476974b45329982d


Use full ::itk namespace in itkMacro.

Applied upstream patch identified by Flavien Bridault.
Closes: #1052223.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1052223

Processed: Bug#1052223 marked as pending in insighttoolkit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1052223 [src:insighttoolkit5] insighttoolkit5: Use full ::itk namespace in 
itkMacro.h
Added tag(s) pending.

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

Processed: tagging 1052572, tagging 1052575

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1052572 + upstream
Bug #1052572 [hoteldruid] hoteldruid: CVE-2023-43371 CVE-2023-43373 
CVE-2023-43374 CVE-2023-43375 CVE-2023-43376 CVE-2023-43377
Added tag(s) upstream.
> tags 1052575 + upstream
Bug #1052575 [jss] jss: CVE-2022-4132
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1052595: liburcu: Please add support for loong64

[JiaLing Zhang]

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

Hello!

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

thanks!
JiaLing

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

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

[Debian Bug Tracking System]

Your message dated Mon, 25 Sep 2023 00:38:10 +
with message-id 
and subject line Bug#1042336: fixed in moment-timezone.js 0.5.40+dfsg-2+2023c
has caused the Debian Bug report #1042336,
regarding moment-timezone.js: FTBFS: cp: cannot stat 
'/usr/share/zoneinfo/posix/*': No such file or directory
to be marked as done.

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

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


-- 
1042336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: moment-timezone.js
Version: 0.5.40+dfsg-1+2023c
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p temp/download/2023c
> ln -s /usr/share/zoneinfo/*.tab temp/download/2023c/
> zcat /usr/share/doc/tzdata/changelog.gz > temp/download/2023c/NEWS
> grunt data-meta:2023c
> >> Local Npm module "grunt-contrib-jshint" not found. Is it installed?
> >> Local Npm module "grunt-contrib-uglify" not found. Is it installed?
> >> Local Npm module "grunt-contrib-clean" not found. Is it installed?
> >> Local Npm module "grunt-exec" not found. Is it installed?
> 
> Running "data-meta:2023c" (data-meta) task
> >> Added metadata for 2023c
> 
> Done.
> mkdir -p temp/zic/2023c temp/zdump/2023c
> cp -RL /usr/share/zoneinfo/posix/* temp/zic/2023c/
> cp: cannot stat '/usr/share/zoneinfo/posix/*': No such file or directory
> make[1]: *** [debian/rules:51: data/unpacked/2023c.json] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/moment-timezone.js_0.5.40+dfsg-1+2023c_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: moment-timezone.js
Source-Version: 0.5.40+dfsg-2+2023c
Done: Martina Ferrari 

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

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

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

Debian distribution maintenance software
pp.
Martina Ferrari  (supplier of updated moment-timezone.js 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Sep 2023 23:49:51 +
Source: moment-timezone.js
Architecture: source
Version: 0.5.40+dfsg-2+2023c
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Martina Ferrari 
Closes: 1042336
Changes:
 moment-timezone.js (0.5.40+dfsg-2+2023c) unstable; urgency=medium
 .
   * Adjust to changes in tzdata package. Closes: #1042336.
 - debian/rules: Use files from /usr/share/zoneinfo instead of
   /usr/share/zoneinfo/posix.
 - debian/control: Depend on tzdata-legacy package, as moment.js expects the
   deprecated names to be present.
   * Fix or override pending lintian tags.
Checksums-Sha1:
 aff49c42ef9b0f65ed76ac418c5ee5bec0139e3c 2356 
moment-timezone.js_0.5.40+dfsg-2+2023c.dsc
 6565c01428bc79dc12d821017ec59d7770b622ad 6812 
moment-timezone.js_0.5.40+dfsg-2+2023c.debian.tar.xz
 38cbd5ccf67c055eec3f8a2d94db70eeed6484d1 20348 
moment-timezone.js_0.5.40+dfsg-2+2023c_amd64.buildinfo
Checksums-Sha256:
 c63342083fe456b19cfdbfe795a8f4fac4e9733790e15f980fc9028a244821c2 2356 
moment-timezone.js_0.5.40+dfsg-2+2023c.dsc
 39ec8c2c583e57e79870779c09142576b4e88d11a401f4479bcd482f06f27c8d 6812 
moment-timezone.js_0.5.40+dfsg-2+2023c.debian.tar.xz
 

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

[Martina Ferrari]

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


I have not just uploaded the fixed package, finally.

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

Hi,

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


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


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

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

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

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


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


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






--
Martina Ferrari (Tina)

Processed: Bug#1042336 marked as pending in moment-timezone.js

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042336 [src:moment-timezone.js] moment-timezone.js: FTBFS: cp: cannot 
stat '/usr/share/zoneinfo/posix/*': No such file or directory
Added tag(s) pending.

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

Bug#1042336: marked as pending in moment-timezone.js

[Martina Ferrari]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/js-team/moment-timezone.js/-/commit/946248d2df6b08213ad2e328503e66de55c73ba6


Adjust to changes in tzdata package. Closes: #1042336.

- debian/rules: Use files from /usr/share/zoneinfo instead of
  /usr/share/zoneinfo/posix.
- debian/control: Depend on tzdata-legacy package, as moment.js expects the
  deprecated names to be present.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042336

Bug#1040901: Upcoming changes to Debian Linux kernel packages

[Bastian Blank]

Hi Ben

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Aka something like that:

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

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

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

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

Package: linux-modules-1.2.3-cloud-arm64

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

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

Bug#1041792: Revision 3.2.1-2

[Arthur Diniz]

Dear Maintainer,

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

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

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

The package now can be cloned and tested.

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

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

---

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

Cheers,
Arthur Diniz

Bug#1050586: marked as done (kmod does not work with XZ in-kernel module decompression)

[Debian Bug Tracking System]

Your message dated Sun, 24 Sep 2023 23:37:56 +0200
with message-id 
and subject line Re: Bug#1050582: kmod update corrupts systemd uefi boot
has caused the Debian Bug report #1050582,
regarding kmod does not work with XZ in-kernel module decompression
to be marked as done.

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

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


-- 
1050582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmod
Version: 30+20230601-1
Severity: grave
Justification: renders system unusable

Dear Maintainer,

I just did a normal apt upgrade and the following packages were upgraded:
kmod 30+20230519-1 to 30-2.230601-1
libkmod2 30+20230519-1 to 30-2.230601-1

The system partially booted but systemd then prevented boot due to missing
modules,
The error message it gave was "decompresson failed with status 6"

I had to boot from a rescue usb stick, set a root password, then I was able to
interact with systemd's idea of a diagnotic console - I'm not systemd's biggest
fan
I used another system to download the older versions of kmod and libkmod2 and
as able to use dpkg to downgrade them.

I installed both on another system and it does the same.
I'm not sure if this effects other system's with sysvinit or non efi.

Regards
Jon Westgate


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

Kernel: Linux 6.4.11 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kmod depends on:
ii  libc6 2.37-7
ii  libkmod2  30+20230601-1
ii  liblzma5  5.4.1-0.2
ii  libssl3   3.0.10-1
ii  libzstd1  1.5.5+dfsg2-1

kmod recommends no packages.

kmod suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sep 15, Martin Nybo Andersen  wrote:

> The problem is, that kmod has switched to using the kernel decompressor when
> available, which is XZ Embedded. This version doesn't handle CRC64 and
> dictionaries larger than 1 MiB.
Thank you a lot for the detailed explanation.
Since this is not a kmod bug and Debian does not ship compressed modules 
I will close the bug.

-- 
ciao,
Marco


signature.asc
Description: PGP signature
--- End Message ---

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

[Markus Koschany]

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

Hi,

The following vulnerabilities were published for hoteldruid.

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


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


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


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


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


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


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.

Regards,

Markus



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

Bug#1050240: marked as done (libqt5location5: Tiles not loading)

[Debian Bug Tracking System]

Your message dated Sun, 24 Sep 2023 19:47:12 +
with message-id 
and subject line Bug#1050240: fixed in qtlocation-opensource-src 
5.15.8+dfsg-3+deb12u1
has caused the Debian Bug report #1050240,
regarding libqt5location5: Tiles not loading
to be marked as done.

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

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


-- 
1050240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5location5
Version: 5.15.8+dfsg-3
Severity: grave
Tags: bookworm
Justification: renders package unusable
X-Debbugs-Cc: raym...@orphiction.nl

Dear Maintainer,

Tiles are not loaded by qtlocation without this change.

The maintainer already showed that is fix is possible using unstable. A similar
fix is created for bookworm and now tiles are loaded as expected.


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

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

Versions of packages libqt5location5 depends on:
ii  libc6  2.36-9+deb12u1
ii  libgcc-s1  12.2.0-14
ii  libqt5core5a [qtbase-abi-5-15-8]   5.15.8+dfsg-11
ii  libqt5gui5 5.15.8+dfsg-11
ii  libqt5positioning5 5.15.8+dfsg-3
ii  libqt5positioningquick55.15.8+dfsg-3
ii  libqt5qml5 [qtdeclarative-abi-5-15-8]  5.15.8+dfsg-3
ii  libqt5qmlmodels5   5.15.8+dfsg-3
ii  libqt5quick5-gles  5.15.8+dfsg-1
ii  libstdc++6 12.2.0-14

libqt5location5 recommends no packages.

libqt5location5 suggests no packages.

-- no debconf information
Index: 
qtlocation-everywhere-src-5.15.8/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
===
--- 
qtlocation-everywhere-src-5.15.8.orig/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
 2022-11-10 21:42:35.0 +0100
+++ 
qtlocation-everywhere-src-5.15.8/src/location/labs/qsg/qgeomapobjectqsgsupport.cpp
  2023-08-22 12:03:25.950516809 +0200
@@ -158,7 +158,7 @@
 if (!root)
 return;
 
-if (m_mapObjectsRootNode && m_mapObjectsRootNode->parent())
+if (m_mapObjectsRootNode && !m_mapObjectsRootNode->parent())
 root->appendChildNode(m_mapObjectsRootNode.get());
 
 if (!m_mapObjectsRootNode) {
--- End Message ---
--- Begin Message ---
Source: qtlocation-opensource-src
Source-Version: 5.15.8+dfsg-3+deb12u1
Done: Dmitry Shachnev 

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

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

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated 
qtlocation-opensource-src package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 23 Sep 2023 22:58:22 +0300
Source: qtlocation-opensource-src
Architecture: source
Version: 5.15.8+dfsg-3+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Dmitry Shachnev 
Closes: 1050240
Changes:
 qtlocation-opensource-src (5.15.8+dfsg-3+deb12u1) bookworm; urgency=medium
 .
   * Backport upstream patch to fix condition for appendChildNode() call
 (closes: #1050240).
Checksums-Sha1:
 411d03a78abc33f1636afe4e63a27ae274908c36 3914 
qtlocation-opensource-src_5.15.8+dfsg-3+deb12u1.dsc
 edbaaebcbcd50dc0c1d07bf50b5f451bab208f1d 4914140 
qtlocation-opensource-src_5.15.8+dfsg.orig.tar.xz
 a20a1b91d5029e61a8d440a288e37413ef246e3f 23896 
qtlocation-opensource-src_5.15.8+dfsg-3+deb12u1.debian.tar.xz
 42a1a662f1b9fbf31835af65cbfd3a8b27d358d0 12857 
qtlocation-opensource-src_5.15.8+dfsg-3+deb12u1_source.buildinfo
Checksums-Sha256:
 95a5fdb5ea234c6c2ccf63dba3e99211a9e604684523212db19229d1c9c3274e 3914 

Bug#1042460: marked as done (openssh-client: ssh-agent CVE-2023-38408)

[Debian Bug Tracking System]

Your message dated Sun, 24 Sep 2023 19:47:34 +
with message-id 
and subject line Bug#1042460: fixed in openssh 1:8.4p1-5+deb11u2
has caused the Debian Bug report #1042460,
regarding openssh-client: ssh-agent CVE-2023-38408
to be marked as done.

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

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


-- 
1042460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-client
Version: 1:8.4p1-5+deb11u1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: mnalis-debian...@voyager.hr, Debian Security Team 



"The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an
insufficiently trustworthy search path, leading to remote code execution if
an agent is forwarded to an attacker-controlled system."

While it does not affect all users of ssh-agent, it does affect many of them
and commonly suggested workaround (using jumphosts instead of agent forwarding)
is not applicable to many use cases (git push over ssh, using
libpam-ssh-agent-auth, etc.)

https://security-tracker.debian.org/tracker/CVE-2023-38408 indicates that
the new fixed version 1:9.3p2-1 has been uploaded in sid and trixie, however
bookworm (stable) and bullseye (oldstable) still have no security fix since 
CVE release on 2023-07-20.

(workaround by pinning fixed version from trixie is not possible, due to
significant libraries clash; and there are no Debian backports either)

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

Kernel: Linux 5.10.0-23-amd64 (SMP w/1 CPU thread)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.20.12
ii  libc6 2.31-13+deb11u6
ii  libedit2  3.1-20210910-1
ii  libfido2-11.6.0-2
ii  libgssapi-krb5-2  1.18.3-6+deb11u3
ii  libselinux1   3.1-3
ii  libssl1.1 1.1.1n-0+deb11u5
ii  passwd1:4.8.1-1
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

Versions of packages openssh-client recommends:
pn  xauth  

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh
pn  monkeysphere  
pn  ssh-askpass   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:8.4p1-5+deb11u2
Done: Colin Watson 

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated openssh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Sep 2023 23:13:51 +0100
Source: openssh
Architecture: source
Version: 1:8.4p1-5+deb11u2
Distribution: bullseye
Urgency: medium
Maintainer: Debian OpenSSH Maintainers 
Changed-By: Colin Watson 
Closes: 1042460
Changes:
 openssh (1:8.4p1-5+deb11u2) bullseye; urgency=medium
 .
   * Cherry-pick from OpenSSH 9.3p2:
 - [CVE-2023-38408] Fix a condition where specific libraries loaded via
   ssh-agent(1)'s PKCS#11 support could be abused to achieve remote code
   execution via a forwarded agent socket (closes: #1042460).
Checksums-Sha1:
 5c8715af36211ea95770b993a652644a70fc0801 3393 openssh_8.4p1-5+deb11u2.dsc
 6ae5d2e17c2036ac074fe7b1041e4417f75c1047 181152 
openssh_8.4p1-5+deb11u2.debian.tar.xz
Checksums-Sha256:
 85766be35d9e1d460e8117164a7a7d5f7347de5130718a7065098c8e6fc4e7bd 3393 
openssh_8.4p1-5+deb11u2.dsc
 72ab9d1e3186a3efbdbb792c9ae08daa4e965a219579482a23d743cfef0180cd 181152 
openssh_8.4p1-5+deb11u2.debian.tar.xz
Files:
 65a6dabac79749aabb9c79450cd1e07e 3393 net standard openssh_8.4p1-5+deb11u2.dsc
 7e2b10adce672e516ecc61f4dfa4ce4f 181152 net standard 
openssh_8.4p1-5+deb11u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmUPYz4ACgkQOTWH2X2G

Bug#1042460: marked as done (openssh-client: ssh-agent CVE-2023-38408)

[Debian Bug Tracking System]

Your message dated Sun, 24 Sep 2023 19:47:11 +
with message-id 
and subject line Bug#1042460: fixed in openssh 1:9.2p1-2+deb12u1
has caused the Debian Bug report #1042460,
regarding openssh-client: ssh-agent CVE-2023-38408
to be marked as done.

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

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


-- 
1042460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openssh-client
Version: 1:8.4p1-5+deb11u1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: mnalis-debian...@voyager.hr, Debian Security Team 



"The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an
insufficiently trustworthy search path, leading to remote code execution if
an agent is forwarded to an attacker-controlled system."

While it does not affect all users of ssh-agent, it does affect many of them
and commonly suggested workaround (using jumphosts instead of agent forwarding)
is not applicable to many use cases (git push over ssh, using
libpam-ssh-agent-auth, etc.)

https://security-tracker.debian.org/tracker/CVE-2023-38408 indicates that
the new fixed version 1:9.3p2-1 has been uploaded in sid and trixie, however
bookworm (stable) and bullseye (oldstable) still have no security fix since 
CVE release on 2023-07-20.

(workaround by pinning fixed version from trixie is not possible, due to
significant libraries clash; and there are no Debian backports either)

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

Kernel: Linux 5.10.0-23-amd64 (SMP w/1 CPU thread)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.20.12
ii  libc6 2.31-13+deb11u6
ii  libedit2  3.1-20210910-1
ii  libfido2-11.6.0-2
ii  libgssapi-krb5-2  1.18.3-6+deb11u3
ii  libselinux1   3.1-3
ii  libssl1.1 1.1.1n-0+deb11u5
ii  passwd1:4.8.1-1
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

Versions of packages openssh-client recommends:
pn  xauth  

Versions of packages openssh-client suggests:
pn  keychain  
pn  libpam-ssh
pn  monkeysphere  
pn  ssh-askpass   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: openssh
Source-Version: 1:9.2p1-2+deb12u1
Done: Colin Watson 

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

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

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated openssh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 23 Sep 2023 23:11:33 +0100
Source: openssh
Architecture: source
Version: 1:9.2p1-2+deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Debian OpenSSH Maintainers 
Changed-By: Colin Watson 
Closes: 1042460
Changes:
 openssh (1:9.2p1-2+deb12u1) bookworm; urgency=medium
 .
   * Cherry-pick from OpenSSH 9.3p2:
 - [CVE-2023-38408] Fix a condition where specific libraries loaded via
   ssh-agent(1)'s PKCS#11 support could be abused to achieve remote code
   execution via a forwarded agent socket (closes: #1042460).
Checksums-Sha1:
 bec06185ba96f1bd9d2196811969c51fc6210516 3352 openssh_9.2p1-2+deb12u1.dsc
 29179a345fc4b31133e212c8dcb9499807957bb4 184920 
openssh_9.2p1-2+deb12u1.debian.tar.xz
Checksums-Sha256:
 908406c2173d3bf99d0283606c841f08f48d9533b27aeab689b9c454b28e535c 3352 
openssh_9.2p1-2+deb12u1.dsc
 416584c486be53038afa618d8bd6605a6d0b54706ea89a911b3d4b8e0abfc3f8 184920 
openssh_9.2p1-2+deb12u1.debian.tar.xz
Files:
 d7947ab3a7f20ca168e65aa93e601ac8 3352 net standard openssh_9.2p1-2+deb12u1.dsc
 a3bc2d1eceb611608505ecea4cb84a0e 184920 net standard 
openssh_9.2p1-2+deb12u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEErApP8SYRtvzPAcEROTWH2X2GUAsFAmUPYsoACgkQOTWH2X2G

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

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.com/skrewball/openweather/-/issues/81
Bug #1052111 [gnome-shell-extension-weather] gnome-shell-extension-weather: 
needs update for GNOME Shell 45
Set Bug forwarded-to-address to 
'https://gitlab.com/skrewball/openweather/-/issues/81'.
> severity -1 serious
Bug #1052111 [gnome-shell-extension-weather] gnome-shell-extension-weather: 
needs update for GNOME Shell 45
Severity set to 'serious' from 'important'

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

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

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1052090 1052104 1052105
Bug #1052556 [bfh-gnome-desktop] bfh-gnome-desktop: Depends on extensions that 
aren't compatible with GNOME Shell 45
1052556 was not blocked by any bugs.
1052556 was not blocking any bugs.
Added blocking bug(s) of 1052556: 1052105, 1052090, and 1052104

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

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

[Manphiz]

Nicholas D Steeves  writes:

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

Great, thanks!

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

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

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

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

> Best,
> Nicholas
>


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


signature.asc
Description: PGP signature

Processed: Re: depends on unmaintained gtkmm2.4, and indirectly on GTK 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #967742 [src:seq24] seq24: depends on deprecated GTK 2
Severity set to 'serious' from 'normal'

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

Processed: Re: depends on unmaintained gtkmm2.4, and indirectly on GTK 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #967245 [src:abgate] abgate: depends on deprecated GTK 2
Severity set to 'serious' from 'normal'

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

Processed: Re: depends on unmaintained gtkmm2.4, and indirectly on GTK 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1041804 [src:showq] showq: depends on unmaintained gtkmm2.4, and 
indirectly on GTK 2
Severity set to 'serious' from 'normal'

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

Processed: Re: depends on unmaintained gtkmm2.4, and indirectly on GTK 2

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1041795 [src:eq10q] eq10q: depends on unmaintained gtkmm2.4, and 
indirectly on GTK 2
Severity set to 'serious' from 'normal'

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

Bug#1040901: Upcoming changes to Debian Linux kernel packages

[Ben Hutchings]

On Sun, 2023-09-24 at 15:01 +0200, Bastian Blank wrote:
[...]
> ## Kernel modules will be signed with an ephemeral key
> 
> The modules will not longer be signed using the Secure Boot CA like the
> EFI kernel image itself.  Instead a key will be created during the build
> and thrown away after.
> 
> Yes, this will make the build unreproducible, but no better solution
> currently exists.  There are some plans, but no-one is working on them.
> If a suitable replacement shows up, we can always switch to that
> solution.

Builds for the architectures involved are already unreproducible due to
inconsistent generation of BTF in both the kernel and modules. 
Additionally, my "plan" would also get rid of signing modules with the
Secure Boot CA, so I'm not going to object to this.


[...]
> ## Image packages contains more version info
> 
> By renaming the kernel packages we try to make several kernels
> installable at the same time.  In contrast to rpm, where you can have
> the same package installed multiple times in different versions, dpkg
> only supports a single one at the same time.  So the co-installable
> versions needs to have different package names.
> 
> The packages will include the full upstream version.  There exists the
> exception of devel builds and uploads to experimental, wich will contain
> even less of the version, to avoid new names in that cases.
> 
> Example: linux-image-6.5.3-cloud-arm64
> 
> There are some drawbacks.
> 
> The same upstream version in testing and backports will have the same
> package name.

This is not OK, because they will be incompatible on architectures
supporting SB (and sometimes incompatible on others due to compiler
differences or required config changes).

If someone upgrades from stable + backports to testing, and has OOT
modules:
- With DKMS, will a rebuild be triggered if the linux-image package
  name doesn't change?
- With module-assistant, the new linux-image package will satisfy
  dependencies of the old modules even though they are incompatible.

> Multiple uploads of the same upstream version will have
> the same package name, but those rarely happens.

Those happen fairly often for urgent security updates.

> Those packages will
> not be compatible and a reboot is necessary to be able to load modules
> again.
> 
> It will not longer be possible to reliably derive the package name from
> kernel release (see above), as both values are not really related
> anymore.

Given all the drawbacks, I don't see the benefit of decoupling package
names from release strings.

In the same way that shared library packages must be renamed for every
backward-incompatible ABI changes, I believe we should keep doing this
for linux-image packages.

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

This is all downside with no justification given.  Please explain what
the benefit is.

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

In the installer, netboot images break every time the kernel ABI is
bumped.  I think there's a specific check and error message for this,
but I'm not exactly sure.  It should be verified that this detection
will work the way you expect, so that the error message doesn't change
and create a support burden for the installer team.

Currently kernel-wedge generates the udeb package names and would need
to add an option to leave out the version part of the names.  I'm happy
to work on that once we have an agreement for what to do.


Ben.

-- 
Ben Hutchings
It is easier to change the specification to fit the program
than vice versa.



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

Bug#1043067: marked as done (FTBFS: This X2Go KDrive version does not support building against X.Org version 21.1.8.)

[Debian Bug Tracking System]

Your message dated Sun, 24 Sep 2023 14:38:34 +
with message-id 
and subject line Bug#1043067: fixed in x2gokdrive 0.0.0.2-1
has caused the Debian Bug report #1043067,
regarding FTBFS: This X2Go KDrive version does not support building against 
X.Org version 21.1.8.
to be marked as done.

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

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


-- 
1043067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: x2gokdrive
Version: 0.0.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

x2gokdrive fails to build from source on amd64 with the following error:


| + sed -r s/^AC_INIT[^,]*, ([^,]+),.*/\1/
| + export XORG_UPSTREAM_VERSION=21.1.8
| + cd /<>/BUILD/xorg-server
| + [ -d ../../patches.xorg/21.1.8 ]
| + set +x
| 
| ##
| ERROR: This X2Go KDrive version does not support
| building against X.Org version 21.1.8.
| ##
| make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:15: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
| 

| Build finished at 2023-08-05T15:10:49Z 


The full build log on riscv64 is also available here:
https://buildd.debian.org/status/fetch.php?pkg=x2gokdrive=riscv64=0.0.0.1-1=1691247408=0

This is very likely due to the upload of xorg-server 2:21.1.8-1 to the
archive.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: x2gokdrive
Source-Version: 0.0.0.2-1
Done: Mike Gabriel 

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

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

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated x2gokdrive package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 24 Sep 2023 16:06:52 +0200
Source: x2gokdrive
Architecture: source
Version: 0.0.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Remote Maintainers 
Changed-By: Mike Gabriel 
Closes: 1043067
Changes:
 x2gokdrive (0.0.0.2-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #1043067).
   * debian/patches:
 + Add README file explaining our patch naming scheme.
 + Drop 1001_typo-fixes.patch. Applied upstream.
   * debian/copyright:
 + Update copyright attributions.
 + Update auto-generated copyright.in file.
Checksums-Sha1:
 3a8e2a4859a0c3e02fd79cace89e52575319ba82 3590 x2gokdrive_0.0.0.2-1.dsc
 ad00123f47944fcd8233800883a06db9be68f103 88370 x2gokdrive_0.0.0.2.orig.tar.gz
 851f7aeb681f69723569ba21b97af58ddcb8f76e 488 x2gokdrive_0.0.0.2.orig.tar.gz.asc
 d5c3d12a6cbf31a11c9c36373dba64c0b02bd62c 16872 
x2gokdrive_0.0.0.2-1.debian.tar.xz
 0f8cddd2ff1669811cf33ea4ecb2c151ff1e5d21 11428 
x2gokdrive_0.0.0.2-1_source.buildinfo
Checksums-Sha256:
 b423ce3fcfda1be26341338e83eefc548bcf9414bd1d982c4ebb7b023f9a 3590 
x2gokdrive_0.0.0.2-1.dsc
 b77dc30621ca6c418d8fd6232d9e71c8a3aacd39108bd496d97a505b768b035b 88370 
x2gokdrive_0.0.0.2.orig.tar.gz
 d55fe9840e02aa9dedc32d95006c24cdeca47f3e58bdc941695eb0c637dfbf4e 488 
x2gokdrive_0.0.0.2.orig.tar.gz.asc
 ef01b54e9299a5f4dcafcd1b00103e2ff29f1c55c6fe9ccfaa9bf7f0a55bf228 16872 
x2gokdrive_0.0.0.2-1.debian.tar.xz
 cf12ae9be78c3eb2b985ea8577f8842f984c17d346b0d1ceeb87fe5a4eb4d6d6 11428 
x2gokdrive_0.0.0.2-1_source.buildinfo
Files:
 ae2b142f8cdfa81c80f4829a57eb4131 3590 x11 optional x2gokdrive_0.0.0.2-1.dsc
 87e0010544229ee8a8ce2a54dd1d3878 88370 x11 optional 
x2gokdrive_0.0.0.2.orig.tar.gz
 9a8443e147e7430d7008f56aac584374 488 x11 optional 
x2gokdrive_0.0.0.2.orig.tar.gz.asc
 8045f171b0bffd44a58a1fc9c851bbe0 16872 x11 optional 
x2gokdrive_0.0.0.2-1.debian.tar.xz
 e669f869d31ea5f7e36876cc7786daf0 11428 x11 optional 
x2gokdrive_0.0.0.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1050329: sexpp FTBFS with nocheck profile

[Mechtilde Stehmann]

Hello Daniel,

when do you plan to fix this little problem?

I'm the maintainer of several packages depending on thunderbird, which 
depends on librnp0, which depends on libsexpp0.


I want to prevent the autoremoval of all those packages.

Kind regards

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


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1051355: Arch armhf does not build

[William Desportes]

Can someone have a look to the armhf build ?

https://buildd.debian.org/status/logs.php?suite=sid=armhf=chromium=117.0.5938.62-1

It does not build, and blocks the package migration: 
https://tracker.debian.org/pkg/chromium

Processed: Re: Bug#1052547: unable to boot, no luks passwort prompt shown

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo unreproducible
Bug #1052547 [cryptsetup-initramfs] unable to boot, no luks passwort prompt 
shown
Added tag(s) unreproducible and moreinfo.

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

Bug#1052547: unable to boot, no luks passwort prompt shown

[Guilhem Moulin]

Control: tag -1 + moreinfo unreproducible

Hi,

On Sun, 24 Sep 2023 at 14:42:27 +0200, Eduard Bloch wrote:
> we have a problem here. After latest upgrades, I am no longer able to
> boot into a system with LUKS-encrypted rootfs. This worked just fine a few
> weeks ago. I jumped in circles in the search for the cause, and only
> after downgrading cryptsetup-initramfs to 2:2.6.1-4 it suddenly started
> working again.

I don't see how downgrading cryptsetup-initramfs from 2:2.6.1-5 to
2:2.6.1-4 could solve this:
https://salsa.debian.org/cryptsetup-team/cryptsetup/-/compare/debian%2F2%252.6.1-4...debian%2F2%252.6.1-5?from_project_id=21364=false

Anyway, this bug is not actionable with so little information.  Please
provide a debug trace per 
https://cryptsetup-team.pages.debian.net/cryptsetup/README.debug.html#debug-cryptroot-initramfs-script

cheers
-- 
Guilhem.


signature.asc
Description: PGP signature

Processed: Re: gnome-shell-mailnag: needs update for GNOME Shell 45

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1052113 serious
Bug #1052113 [gnome-shell-mailnag] gnome-shell-mailnag: needs update for GNOME 
Shell 45
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1040901: Upcoming changes to Debian Linux kernel packages

[Bastian Blank]

Hi folks

Debian currently does Secure Boot signing using a shim chained to the
Microsoft key.  This use requires that we follow certain rules.  And one
of the recent changes to those rules state that our method of signing
kernel modules also with the same key will not be allowed anymore.  Some
information are in #1040901.

We could just do the minimal change, sign the modules a different way
and let users walk into authenticated failures and other scary error
messages.  Or we could change the existing ABI setting on every upload,
creating a new set of binary packages.

But maybe we can enhance the user experience a bit, by reducing the
chance of scarry errors, but with the chance of simple errors like "you
need to reboot".  So let's do some more changes and hopefully don't
break the user experience too much.  The planned changes are discussed
in more detail.

## Kernel modules will be signed with an ephemeral key

The modules will not longer be signed using the Secure Boot CA like the
EFI kernel image itself.  Instead a key will be created during the build
and thrown away after.

Yes, this will make the build unreproducible, but no better solution
currently exists.  There are some plans, but no-one is working on them.
If a suitable replacement shows up, we can always switch to that
solution.

## Kernel release value includes complete Debian version

The kernel release is what "uname -r" shows, and how modules are
organized in /lib/modules.  This value will include the complete version
of the binary package, so even binNMU will somehow work.  This will make
sure the value changes with every upload and modules will not be
compatible already from that check.

Example: 6.5.3-2+b2-cloud-arm64

## Image packages contains more version info

By renaming the kernel packages we try to make several kernels
installable at the same time.  In contrast to rpm, where you can have
the same package installed multiple times in different versions, dpkg
only supports a single one at the same time.  So the co-installable
versions needs to have different package names.

The packages will include the full upstream version.  There exists the
exception of devel builds and uploads to experimental, wich will contain
even less of the version, to avoid new names in that cases.

Example: linux-image-6.5.3-cloud-arm64

There are some drawbacks.

The same upstream version in testing and backports will have the same
package name.  Multiple uploads of the same upstream version will have
the same package name, but those rarely happens.  Those packages will
not be compatible and a reboot is necessary to be able to load modules
again.

It will not longer be possible to reliably derive the package name from
kernel release (see above), as both values are not really related
anymore.

## Header and tool packages will not longer contain version

The headers packages will not longer include the version.  It won't be
reliably possible to derive the package name anyway from the running
kernel.

This means that only headers of one single version can be available on
the system at one time.  This might be a bit inconvinient for dkms, as
it can't longer build modules for multiple versions.

But we too often have the problem that image and headers go out of sync
and then you can't find the correct ones anyway.

Example: linux-headers-cloud-arm64

## Installer packages will not longer contain too much version

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

## Further work

The changes outlined here try to avoid changes to the initramfs
protocol, aka /etc/kernel/.  There are larger change is cooking somehow,
see
https://lists.debian.org/msgid-search/y2gbkyerb10ky...@shell.thinkmo.de

Regards,
Bastian

-- 
You!  What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0

Processed: dipy: Skip little-endian test in big-endian compiler

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.7.0-2
Bug #1052241 [src:dipy] dipy: Skip little-endian test in big-endian compiler
Marked as found in versions dipy/1.7.0-2.
> severity -1 serious
Bug #1052241 [src:dipy] dipy: Skip little-endian test in big-endian compiler
Severity set to 'serious' from 'normal'
> affects -1 + nipype
Bug #1052241 [src:dipy] dipy: Skip little-endian test in big-endian compiler
Added indication that 1052241 affects nipype

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

Bug#1052548: smcroute: 'is-system-running' check in autopkgtest breaks on unrelated system changes

[Luca Boccassi]

Package: smcroute
Version: 2.5.6-1
Severity: serious
Justification: stops other packages from migrating to testing
Tags: patch pending
X-Debbugs-Cc: pkg-systemd-maintain...@lists.alioth.debian.org

Dear Maintainer(s),

The autopkgtest does not actually use the systemd service, it calls the
legacy script by hand. Also checking 'is-system-running' is incorrect,
as that might be influenced by random unrelated fluctuations from other
services, that have nothing to do with smcroute.

The immediate solution is to drop the check from the test.

Given this is blocking systemd from migrating to testing, high severity
is set, and I have already uploaded an NMU to DELAYED/3. I have opened
an MR against Salsa with the changes. Debdiff also attached.

MR: https://salsa.debian.org/debian/smcroute/-/merge_requests/3

Failing log:
https://ci.debian.net/data/autopkgtest/testing/amd64/s/smcroute/38108679/log.gz

If you think there is a better solution please let me know and I'll
cancel the deferred NMU, but we'd appreciate a swift resolution given
it blocks migration.

Thanks!

-- 
Kind regards,
Luca Boccassi
diff -Nru smcroute-2.5.6/debian/changelog smcroute-2.5.6/debian/changelog
--- smcroute-2.5.6/debian/changelog	2023-01-08 13:02:40.0 +
+++ smcroute-2.5.6/debian/changelog	2023-09-24 13:34:21.0 +0100
@@ -1,3 +1,10 @@
+smcroute (2.5.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * autopkgtest: drop is-system-running check (Closes: #)
+
+ -- Luca Boccassi   Sun, 24 Sep 2023 13:34:21 +0100
+
 smcroute (2.5.6-1) unstable; urgency=medium
 
   * New upstream version 2.5.6.
diff -Nru smcroute-2.5.6/debian/tests/daemon-init-scripts smcroute-2.5.6/debian/tests/daemon-init-scripts
--- smcroute-2.5.6/debian/tests/daemon-init-scripts	2021-09-25 13:28:23.0 +0100
+++ smcroute-2.5.6/debian/tests/daemon-init-scripts	2023-09-24 13:34:21.0 +0100
@@ -28,7 +28,7 @@
 return $smcroute_pid;
 }
 
-plan tests => 13;
+plan tests => 11;
 
 # Work around test harness, start smcrouted if not already running
 my $startup = capture EXIT_ANY, INIT_SCRIPT, 'start';
@@ -43,11 +43,6 @@
 is $EXITVAL, 0, "stopping smcroute";
 my $smcroute_pid = get_smcrouted_pid 'stopped';
 is $EXITVAL, 1, "smcroute is really stopped".( $EXITVAL ? '' : " (pid $smcroute_pid)" );
-SKIP: {
-skip "System not managed by systemd", 1 unless -e '/run/systemd/system';
-my $wait_output = capture EXIT_ANY, 'systemctl', 'is-system-running', '--wait'; chomp $wait_output;
-is $wait_output, "running", "Stopping smcroute completed";
-}
 
 my $double_stop_output = capture EXIT_ANY, INIT_SCRIPT, 'stop';
 is $EXITVAL, 0, "stopping smcroute twice in a row";
@@ -57,11 +52,6 @@
 # Try to start the daemon again
 my $start_output = capture EXIT_ANY, INIT_SCRIPT, 'start';
 is $EXITVAL, 0, "starting smcroute";
-SKIP: {
-skip "System not managed by systemd", 1 unless -e '/run/systemd/system';
-my $wait_output = capture EXIT_ANY, 'systemctl', 'is-system-running', '--wait'; chomp $wait_output;
-is $wait_output, "running", "Starting smcroute completed";
-}
 my $new_smcroute_pid = get_smcrouted_pid 'running';
 is $EXITVAL, 0, "smcroute is really running".( $EXITVAL ? '' : " (pid $new_smcroute_pid)" );
 isnt $new_smcroute_pid, $initial_smcroute_pid, "smcroute pid changed ($new_smcroute_pid != $initial_smcroute_pid)";


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

Bug#1052547: unable to boot, no luks passwort prompt shown

[Eduard Bloch]

Package: cryptsetup-initramfs
Version: 2:2.6.1-5
Severity: grave

Hello Maintainer,

we have a problem here. After latest upgrades, I am no longer able to
boot into a system with LUKS-encrypted rootfs. This worked just fine a few
weeks ago. I jumped in circles in the search for the cause, and only
after downgrading cryptsetup-initramfs to 2:2.6.1-4 it suddenly started
working again.

The symptom:

initramfs starts more or less okay, after a second KVM switches the
screen mode. And then I see a blinking cursor. And that's all.

Normally (like before, or after after downgrading the package) I get a
LUKS passwort prompt instead, where I enter the rootfs password.

Best regards,
Eduard.


-- Package-specific info:
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.5.5 root=UUID=6e83a5a5-0c68-41e9-8bcb-ea0b50c06197 ro 
acpi=force

-- /etc/crypttab
# 
#xroot /dev/sdb2 none luks,discard
#xroot UUID=4047a384-74d1-465d-9e1b-536f40ed73d2 none luks,discard
yroot UUID=0a03cfce-d1a8-4a93-a403-d411f8ead12e none luks,discard

-- /etc/fstab
# /etc/fstab: static file system information.
#
#
proc /proc   proc   
   defaults  0  
  0
/dev/mapper/yroot  /   ext4  
defaults,errors=remount-ro,noatime,commit=1200  
  1
UUID="e69c6bbe-f493-4dc5-aed3-419654c4bf41" /boot   ext4
defaults,errors=remount-ro 01
UUID="B63D-00A4" /boot/efi vfat defaults,errors=remount-ro 01
/dev/cdrom   /media/cdrom0   
udf,iso9660   ro,user,noauto0   
 0
UUID="0a03cfce-d1a8-4a93-a403-d411f8ead12e"  /mnt/bigdata   auto noauto,user
UUID="2610550D1054E579"/mnt/d  ntfs-3g  
 utf8,user,auto,umask=000,nofail   0
0
UUID="78496414545E7C56"  /mnt/cfs2   ntfs-3g
   defaults,noauto,nofail   0   
 1
UUID=CE2E78A02E78836F /mnt/c  ntfs-3g   
utf8,user,auto,umask=000,nofail   0 
   0
none /var/cache/pbuilder/bd  tmpfs  
   defaults  0  
  0

-- lsmod
Module  Size  Used by
snd_seq_dummy  12288  0
snd_hrtimer12288  1
snd_seq   110592  7 snd_seq_dummy
cpufreq_userspace  16384  0
cpufreq_conservative16384  0
cpufreq_powersave  16384  0
nvme_fabrics   36864  0
overlay   188416  0
bnep   28672  2
uinput 20480  1
binfmt_misc28672  1
nls_ascii  12288  1
nls_cp437  16384  1
vfat   20480  1
fat94208  1 vfat
pktcdvd53248  0
uvcvideo  143360  0
videobuf2_vmalloc  20480  1 uvcvideo
uvc12288  1 uvcvideo
videobuf2_memops   16384  1 videobuf2_vmalloc
videobuf2_v4l2 36864  1 uvcvideo
snd_usb_audio 401408  1
videodev  356352  2 videobuf2_v4l2,uvcvideo
snd_usbmidi_lib49152  1 snd_usb_audio
snd_rawmidi53248  1 snd_usbmidi_lib
videobuf2_common   77824  4 
videobuf2_vmalloc,videobuf2_v4l2,uvcvideo,videobuf2_memops
joydev 24576  0
snd_seq_device 16384  2 snd_seq,snd_rawmidi
mc 94208  5 
videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
btusb  81920  0
btmtk  12288  1 btusb
btrtl  28672  1 btusb
btbcm  24576  1 btusb
btintel57344  1 btusb
bluetooth1110016  15 btrtl,btmtk,btintel,btbcm,bnep,btusb
intel_rapl_msr 20480  0
intel_rapl_common  36864  1 intel_rapl_msr
kvm_amd   180224  0
sha3_generic   16384  1
jitterentropy_rng  20480  1
drbg   28672  1
snd_hda_codec_realtek   192512  1
ccp   135168  1 kvm_amd
snd_hda_codec_generic   110592  1 snd_hda_codec_realtek
ansi_cprng 12288  0
ledtrig_audio  12288  1 snd_hda_codec_generic
ecdh_generic   16384  1 bluetooth
snd_hda_codec_hdmi 90112  2
rfkill 40960  4 bluetooth
snd_hda_intel  61440  3
ecc45056  1 ecdh_generic
snd_intel_dspcfg   24576  1 snd_hda_intel
kvm  1335296  1 kvm_amd
snd_hda_codec 221184  4 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
irqbypass  12288  1 kvm
snd_hda_core  143360  5 

Processed: Re: FTBFS with libfluidsynth-dev:arm64=2.3.3-2

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 1051904 src:fluidsynth 2.3.3-2
Bug #1051904 [src:gst-plugins-bad1.0] FTBFS with libfluidsynth-dev:arm64=2.3.3-2
Bug reassigned from package 'src:gst-plugins-bad1.0' to 'src:fluidsynth'.
No longer marked as found in versions gst-plugins-bad1.0/1.22.4-1.
Ignoring request to alter fixed versions of bug #1051904 to the same values 
previously set
Bug #1051904 [src:fluidsynth] FTBFS with libfluidsynth-dev:arm64=2.3.3-2
Marked as found in versions fluidsynth/2.3.3-2.
>
End of message, stopping processing here.

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

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

[Salvatore Bonaccorso]

Hi Arturo,

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

The work for bookworm has been done, but for bullseye: would you be
able to help here and prepare the fixes? Unfortunatlly the fixes will
not apply cleanly. If we fear to much breakage, maybe upstream can be
convinced to help?

Regards,
Salvatore

Bug#1052544: xtl 0.7.5 could not find "doctest"

[Drew Parsons]

Source: xtl
Version: 0.7.5-2
Severity: serious
Justification: debci

There's a problem with the xtk 0.7.5 cmake configuration.

It fails debian/tests (debci) since it can't find doctest:

 46s CMake Error at CMakeLists.txt:12 (find_package):
 46s   By not providing "Finddoctest.cmake" in CMAKE_MODULE_PATH this project 
has
 46s   asked CMake to find a package configuration file provided by "doctest", 
but
 46s   CMake did not find one.
 46s 
 46s   Could not find a package configuration file provided by "doctest" with 
any
 46s   of the following names:
 46s 
 46s doctestConfig.cmake
 46s doctest-config.cmake
 46s 
 46s   Add the installation prefix of "doctest" to CMAKE_PREFIX_PATH or set
 46s   "doctest_DIR" to a directory containing one of the above files.  If
 46s   "doctest" provides a separate development package or SDK, be sure it has
 46s   been installed.



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

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

Bug#1052541: Bug #1052541 apfs-dkms: Still not building

[Daniele Ricci]

Hi,
I'm sorry for opening a duplicate of #1043112, I thought the bugreport 
utility could be also used to reply/reopen an existing ticket (I 
probably did something wrong).


Regards
--
Daniele Ricci


OpenPGP_0x99F13342E787A3FE.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#999962: silversearcher-ag: diff for NMU version 2.2.0+git20200805-1.1

[Xiyue Deng]

Control: tags 62 + pending

Dear maintainer,

I've prepared an NMU for silversearcher-ag (versioned as 2.2.0+git20200805-1.1)
and uploaded it to mentors.debian.net. Please feel free to tell me if I should
delay it longer.

Regards.

diff -Nru silversearcher-ag-2.2.0+git20200805/debian/changelog 
silversearcher-ag-2.2.0+git20200805/debian/changelog
--- silversearcher-ag-2.2.0+git20200805/debian/changelog2020-08-04 
18:55:35.0 -0700
+++ silversearcher-ag-2.2.0+git20200805/debian/changelog2023-09-21 
23:41:55.0 -0700
@@ -1,3 +1,14 @@
+silversearcher-ag (2.2.0+git20200805-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Enable pcre2 support to replace deprecated pcre1 (Closes: #62)
+- Add d/p/enable_pcre2_support.patch cherrypicked from upstream pcre2
+  branch
+- Build-Depends on libpcre2-dev instead of libpcre3-dev
+  * Update d/copyright with copyright owners of the pcre2 patch and m4/*
+
+ -- Xiyue Deng   Thu, 21 Sep 2023 23:41:55 -0700
+
 silversearcher-ag (2.2.0+git20200805-1) unstable; urgency=medium
 
   * New upstream snapshot (Closes: #957798)
diff -Nru silversearcher-ag-2.2.0+git20200805/debian/control 
silversearcher-ag-2.2.0+git20200805/debian/control
--- silversearcher-ag-2.2.0+git20200805/debian/control  2020-08-04 
18:55:35.0 -0700
+++ silversearcher-ag-2.2.0+git20200805/debian/control  2023-09-06 
02:57:08.0 -0700
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Hajime Mizuno 
-Build-Depends: debhelper-compat (= 13), pkg-config, libpcre3-dev, zlib1g-dev, 
liblzma-dev
+Build-Depends: debhelper-compat (= 13), pkg-config, libpcre2-dev, zlib1g-dev, 
liblzma-dev
 Standards-Version: 4.5.0
 Homepage: https://github.com/ggreer/the_silver_searcher
 
diff -Nru silversearcher-ag-2.2.0+git20200805/debian/copyright 
silversearcher-ag-2.2.0+git20200805/debian/copyright
--- silversearcher-ag-2.2.0+git20200805/debian/copyright2020-08-04 
18:55:35.0 -0700
+++ silversearcher-ag-2.2.0+git20200805/debian/copyright2023-09-21 
23:39:19.0 -0700
@@ -7,10 +7,21 @@
 Copyright: 2013-2018 Geoff Greer 
 License: Apache-2.0
 
+Files: m4/*
+Copyright:
+ 2008 Steven G. Johnson 
+ 2011 Daniel Richard G. 
+License: GPL-3+
+
 Files: debian/*
 Copyright: 2013-2018 Hajime Mizuno 
 License: Apache-2.0
 
+Files: debian/patches/*
+Copyright: 2016 Allen Wild 
+ 2023 Xiyue Deng 
+License: Apache-2.0
+
 License: Apache-2.0
  Licensed under the Apache License, Version 2.0 (the "License");
  you may not use this file except in compliance with the License.
@@ -26,3 +37,17 @@
  .
  On Debian systems, the complete text of the Apache version 2.0 license
  can be found in "/usr/share/common-licenses/Apache-2.0".
+
+License: GPL-3+
+ This program is free software: you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation, either version 3 of the License, or
+ (at your option) any later version.
+ .
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+ GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License
+ along with this program.  If not, see .
diff -Nru 
silversearcher-ag-2.2.0+git20200805/debian/patches/enable_pcre2_support.patch 
silversearcher-ag-2.2.0+git20200805/debian/patches/enable_pcre2_support.patch
--- 
silversearcher-ag-2.2.0+git20200805/debian/patches/enable_pcre2_support.patch   
2020-08-04 18:55:35.0 -0700
+++ 
silversearcher-ag-2.2.0+git20200805/debian/patches/enable_pcre2_support.patch   
2023-09-06 02:57:08.0 -0700
@@ -1,6 +1,6 @@
 Description: enable pcre2 support
  Cherrypick and adapt patch set that adds pcre2 support.
-Author: Xiyue Deng 
+Author: Xiyue Deng 
 Bug-Debian: https://bugs.debian.org/62
 Forwarded: not-needed
 Applied-Upstream:
@@ -75,12 +75,13 @@
  CFLAGS="$CFLAGS -Wpointer-arith -Wcast-qual -Wmissing-prototypes 
-Wno-missing-braces -std=gnu89 -D_GNU_SOURCE"
  LDFLAGS="$LDFLAGS"
  
-@@ -40,6 +38,25 @@ esac
+@@ -40,6 +38,26 @@ esac
  
  LIBS="$PTHREAD_LIBS $LIBS"
  
 +AC_ARG_WITH([pcre2],
 +[AS_HELP_STRING([--with-pcre2], [Enable experimental support for 
libpcre2])])
++with_pcre2=yes
 +
 +AS_IF([test "x$with_pcre2" = "xyes"], [
 +  PKG_CHECK_MODULES([PCRE2], [libpcre2-8], [

Processed: silversearcher-ag: diff for NMU version 2.2.0+git20200805-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 62 + pending
Bug #62 [src:silversearcher-ag] silversearcher-ag: depends on obsolete 
pcre3 library
Added tag(s) pending.

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

Bug#1052541: apfs-dkms: Still not building

[Daniele Ricci]

Package: apfs-dkms
Version: 0.3.3+git20230810+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

Module still does not build with the current unstable version and kernel 6.5.
Using latest upstream (0.3.4) seems to fix the problem though.


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

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

Versions of packages apfs-dkms depends on:
ii  dkms  3.0.11-3

apfs-dkms recommends no packages.

apfs-dkms suggests no packages.

-- no debconf information

Bug#1042967: (no subject)

[ZenWalker]

Did you report it at upstream?

https://github.com/Nheko-Reborn/nheko/issues

Bug#1052540: setuptools: FTBFS in unstable and trixie

[Graham Inggs]

Source: setuptools
Version: 68.1.2-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As per reproducible builds [1], setuptools started to FTBFS in trixie
and unstable sometime around 2023-08-28.

I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/setuptools.html


Traceback (most recent call last):
  File 
"/build/reproducible-path/setuptools-68.1.2/setuptools/config/setupcfg.py",
line 284, in __setitem__
current_value = getattr(target_obj, option_name)

AttributeError: 'MinimalDistribution' object has no attribute 'entry_points'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/build/reproducible-path/setuptools-68.1.2/setup.py", line 92,
in 
dist = setuptools.setup(**setup_params)
   
  File "/build/reproducible-path/setuptools-68.1.2/setuptools/__init__.py",
line 106, in setup
_install_setup_requires(attrs)
  File "/build/reproducible-path/setuptools-68.1.2/setuptools/__init__.py",
line 77, in _install_setup_requires
dist.parse_config_files(ignore_option_errors=True)
  File "/build/reproducible-path/setuptools-68.1.2/setuptools/dist.py",
line 895, in parse_config_files
setupcfg.parse_configuration(
  File 
"/build/reproducible-path/setuptools-68.1.2/setuptools/config/setupcfg.py",
line 177, in parse_configuration
options.parse()
  File 
"/build/reproducible-path/setuptools-68.1.2/setuptools/config/setupcfg.py",
line 500, in parse
section_parser_method(section_options)
  File 
"/build/reproducible-path/setuptools-68.1.2/setuptools/config/setupcfg.py",
line 727, in parse_section_entry_points
self['entry_points'] = parsed

  File 
"/build/reproducible-path/setuptools-68.1.2/setuptools/config/setupcfg.py",
line 286, in __setitem__
raise KeyError(option_name)
KeyError: 'entry_points'
E: pybuild pybuild:395: clean: plugin distutils failed with: exit
code=1: python3.11 setup.py clean