Bug#1050775: libgeotiff: FTBFS with PROJ 9.3.0 (test failures)

[Bas Couwenberg]

Source: libgeotiff
Version: 1.7.1-2
Severity: important
Tags: ftbfs upstream
User: debian-...@lists.debian.org
Usertags: proj-9.3
Control: forwarded -1 https://github.com/OSGeo/libgeotiff/issues/89

Dear Maintainer,

Your package FTBFS with PROJ 9.3.0 from experimental:

 --- testlistgeo_out 2023-08-29 03:55:10.645106504 +
 +++ testlistgeo_out.dist.tmp2023-08-29 03:55:10.641106501 +
 @@ -1822,8 +1822,8 @@
 ProjNatOriginLongGeoKey: 0.00 (  0d 0' 0.00"E)
 ProjFalseEastingGeoKey: 0.00 m
 ProjFalseNorthingGeoKey: 0.00 m
 -GCS: 10346/NSIDC Authalic Sphere
 -Datum: 1360/NSIDC International 1924 Authalic Sphere
 +GCS: 4053/Unspecified datum based upon the International 1924 Authalic Sphere
 +Datum: 6053/Not specified (based on International 1924 Authalic Sphere)
  Ellipsoid: 7057/International 1924 Authalic Sphere (6371228.00,6371228.00)
  Prime Meridian: 8901/Greenwich (0.00/  0d 0' 0.00"E)
  Projection Linear Units: 9001/metre (1.00m)
 
 PROBLEMS HAVE OCCURRED
 test file testlistgeo_out saved

Kind Regards,

Bas

Bug#1050352: backside USB-ports stop working after some time

[Rolf Reintjes]

I am on testing.

I could isolate the problem causing code in the debian patches on file

drivers/iommu/intel/iommu.c

With this change

rolf@i7-5820K-debian-testing:~/kernel/linux-source-6.4/drivers/iommu/intel$ 
diff iommu.c.debian iommu.c

286c286
< int dmar_disabled = IS_ENABLED(CONFIG_INTEL_IOMMU_DEFAULT_OFF);
---
> int dmar_disabled = !IS_ENABLED(CONFIG_INTEL_IOMMU_DEFAULT_ON);

the problem is not there.

Bug#1050773: metview: Drop unused libproj-dev build dependency

[Bas Couwenberg]

Source: metview
Version: 5.19.2-1
Severity: normal
Tags: patch

Dear Maintainer,

Your package build depends on libproj-dev but doesn't link to libproj nor 
include proj.h.

The attached patch drops the unused build dependency.

Kind Regards,

Bas
diff -Nru metview-5.19.2/debian/changelog metview-5.19.2/debian/changelog
--- metview-5.19.2/debian/changelog 2023-07-15 10:28:25.0 +0200
+++ metview-5.19.2/debian/changelog 2023-08-29 07:24:56.0 +0200
@@ -1,3 +1,10 @@
+metview (5.19.2-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused libproj-dev build dependency.
+
+ -- Bas Couwenberg   Tue, 29 Aug 2023 07:24:56 +0200
+
 metview (5.19.2-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru metview-5.19.2/debian/control metview-5.19.2/debian/control
--- metview-5.19.2/debian/control   2023-07-15 10:28:25.0 +0200
+++ metview-5.19.2/debian/control   2023-08-29 07:24:55.0 +0200
@@ -48,7 +48,7 @@
   swig, 
   libexpat1-dev,
   libterralib-dev (>= 4.3.0+dfsg.2-8), 
-  libproj-dev, libqt5svg5-dev,
+  libqt5svg5-dev,
   libgd-dev, 
   imagemagick, 
   libnetcdf-dev, libnetcdf-c++4-dev,

Bug#1050772: mysql-workbench: Drop unused libproj-dev build dependency

[Bas Couwenberg]

Source: mysql-workbench
Version: 8.0.32+dfsg-1
Severity: normal
Tags: patch

Dear Maintainer,

Your package build depends on libproj-dev but doesn't link to libproj nor 
include proj.h.

The attached patch drops the unused build dependency.

Kind Regards,

Bas
diff -Nru mysql-workbench-8.0.32+dfsg/debian/changelog 
mysql-workbench-8.0.32+dfsg/debian/changelog
--- mysql-workbench-8.0.32+dfsg/debian/changelog2023-03-22 
04:10:41.0 +0100
+++ mysql-workbench-8.0.32+dfsg/debian/changelog2023-08-29 
07:29:49.0 +0200
@@ -1,3 +1,10 @@
+mysql-workbench (8.0.32+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused libproj-dev build dependency.
+
+ -- Bas Couwenberg   Tue, 29 Aug 2023 07:29:49 +0200
+
 mysql-workbench (8.0.32+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru mysql-workbench-8.0.32+dfsg/debian/control 
mysql-workbench-8.0.32+dfsg/debian/control
--- mysql-workbench-8.0.32+dfsg/debian/control  2022-11-22 11:47:16.0 
+0100
+++ mysql-workbench-8.0.32+dfsg/debian/control  2023-08-29 07:29:48.0 
+0200
@@ -31,7 +31,6 @@
  ,libpcre3-dev
  ,libpixman-1-dev
  ,libpng-dev
- ,libproj-dev
  ,libsqlite3-dev
  ,libtinyxml-dev (>= 2.6.2)
  ,libvsqlitepp-dev

Bug#1050771: linux-image-6.4.0-3-amd64: Error! Bad return status for module build on kernel: 6.4.0-3-amd64 (x86_64) r8168

[alirezaimi]

Package: src:linux
Version: 6.4.11-1
Severity: important
X-Debbugs-Cc: alireza...@gmail.com

Dear Maintainer,

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

   * What led up to the situation? upgrading, apt update; apt upgrade
   * What exactly did you do (or not do) that was effective (or
 ineffective)? nothing .
   * What was the outcome of this action? nothing .
   * What outcome did you expect instead? updating new linux kernel

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


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: X542URV
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: X542URV.308
board_vendor: ASUSTeK COMPUTER INC.
board_name: X542URV
board_version: 1.0   

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5914] (rev 08)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1043:1b10]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 
[8086:5917] (rev 07) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1b10]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- 
EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
10BitTagReq- OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable+, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 08)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen 
Core Processor Thermal Subsystem [1043:1b10]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP USB 3.0 xHCI 
Controller [1043:201f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 

Bug#1050769: greetd FTBFS with DEB_BUILD_OPTIONS=nocheck: does not perform the build

[Helmut Grohne]

Source: greetd
Version: 0.9.0-4
Severity: serious
Justification: nocheck FTBFS is serious since trixie

greetd fails to build from source, when DEB_BUILD_OPTIONS contains
nocheck. A build ends as follows:

| dh binary --buildsystem=cargo
|dh_update_autotools_config -O--buildsystem=cargo
|dh_autoreconf -O--buildsystem=cargo
|debian/rules execute_before_dh_auto_configure
| make[1]: Entering directory '/<>'
| printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po 
'^\S+') > debian/cargo-checksum.json;
| make[1]: Leaving directory '/<>'
|dh_auto_configure -O--buildsystem=cargo
| debian cargo wrapper: options, profiles, parallel: ['nocheck', 'parallel=8'] 
[] ['-j8']
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
| debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/<>/debian/cargo_registry/
|debian/rules override_dh_auto_build
| make[1]: Entering directory '/<>'
| # actually does the build
| dh_auto_test -- --release
| make -C man all
| make[2]: Entering directory '/<>/man'
| /usr/bin/scdoc < agreety-1.scd > agreety.1
| /usr/bin/scdoc < greetd-1.scd > greetd.1
| /usr/bin/scdoc < greetd-5.scd > greetd.5
| /usr/bin/scdoc < greetd-ipc-7.scd > greetd-ipc.7
| make[2]: Leaving directory '/<>/man'
| make[1]: Leaving directory '/<>'
|create-stamp debian/debhelper-build-stamp
|dh_testroot -O--buildsystem=cargo
|dh_prep -O--buildsystem=cargo
|debian/rules override_dh_auto_install
| make[1]: Entering directory '/<>'
| dh_install target/x86_64-unknown-linux-gnu/release/greetd /usr/sbin/
| dh_install: warning: Cannot find (any matches for) 
"target/x86_64-unknown-linux-gnu/release/greetd" (tried in ., debian/tmp)
| 
| dh_install: warning: greetd missing files: 
target/x86_64-unknown-linux-gnu/release/greetd
| dh_install: error: missing files, aborting
| make[1]: *** [debian/rules:26: override_dh_auto_install] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:8: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Note that nothing is ever built. debian/rules suggests that it attempts
to build using dh_auto_test, but given a high enough compatibility level
dh_auto_test honours DEB_BUILD_OPTIONS=nocheck. You probably need to run
dh_auto_build at some point.

Helmut

Bug#866070: higan FTCBFS: uses the build architecture compiler and pkg-config

[Helmut Grohne]

Source: ares
Version: 132-1
Followup-For: Bug #866070
Control: tags -1 patch

I've updated the patch for ares.

Helmut
diff --minimal -Nru ares-132/debian/changelog ares-132/debian/changelog
--- ares-132/debian/changelog   2023-07-22 17:16:04.0 +0200
+++ ares-132/debian/changelog   2023-08-27 20:04:03.0 +0200
@@ -1,3 +1,13 @@
+ares (132-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass the compiler via the non-standard $(compiler) variable.
++ cross.patch: Honour PKG_CONFIG.
++ cross.patch: Don't relink during install.
+
+ -- Helmut Grohne   Sun, 27 Aug 2023 20:04:03 +0200
+
 ares (132-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff --minimal -Nru ares-132/debian/patches/cross.patch 
ares-132/debian/patches/cross.patch
--- ares-132/debian/patches/cross.patch 1970-01-01 01:00:00.0 +0100
+++ ares-132/debian/patches/cross.patch 2023-08-27 20:04:03.0 +0200
@@ -0,0 +1,127 @@
+--- ares-132.orig/hiro/GNUmakefile
 ares-132/hiro/GNUmakefile
+@@ -1,3 +1,5 @@
++PKG_CONFIG ?= pkg-config
++
+ ifeq ($(platform),windows)
+   ifeq ($(hiro),)
+ hiro := windows
+@@ -9,13 +11,13 @@
+   endif
+ 
+   ifeq ($(hiro),gtk2)
+-hiro.flags   = $(flags.cpp) -DHIRO_GTK=2 $(shell pkg-config --cflags 
gtk+-2.0) -Wno-deprecated-declarations
+-hiro.options = $(shell pkg-config --libs gtk+-2.0)
++hiro.flags   = $(flags.cpp) -DHIRO_GTK=2 $(shell $(PKG_CONFIG) --cflags 
gtk+-2.0) -Wno-deprecated-declarations
++hiro.options = $(shell $(PKG_CONFIG) --libs gtk+-2.0)
+   endif
+ 
+   ifeq ($(hiro),gtk3)
+-hiro.flags   = $(flags.cpp) -DHIRO_GTK=3 $(shell pkg-config --cflags 
gtk+-3.0) -Wno-deprecated-declarations
+-hiro.options = $(shell pkg-config --libs gtk+-3.0)
++hiro.flags   = $(flags.cpp) -DHIRO_GTK=3 $(shell $(PKG_CONFIG) --cflags 
gtk+-3.0) -Wno-deprecated-declarations
++hiro.options = $(shell $(PKG_CONFIG) --libs gtk+-3.0)
+   endif
+ endif
+ 
+@@ -36,37 +38,37 @@
+   endif
+ 
+   ifeq ($(hiro),gtk2)
+-hiro.flags   = $(flags.cpp) -DHIRO_GTK=2 $(shell pkg-config --cflags 
gtk+-2.0) -Wno-deprecated-declarations
+-hiro.options = -L/usr/local/lib -lX11 $(shell pkg-config --libs gtk+-2.0)
++hiro.flags   = $(flags.cpp) -DHIRO_GTK=2 $(shell $(PKG_CONFIG) --cflags 
gtk+-2.0) -Wno-deprecated-declarations
++hiro.options = -L/usr/local/lib -lX11 $(shell $(PKG_CONFIG) --libs 
gtk+-2.0)
+   endif
+ 
+   ifeq ($(hiro),gtk2-se)
+ flags   += -DHiro_SourceEdit
+-hiro.flags   = $(flags.cpp) -DHIRO_GTK=2 $(shell pkg-config --cflags 
gtk+-2.0 gtksourceview-2.0) -Wno-deprecated-declarations
+-hiro.options = -L/usr/local/lib -lX11 $(shell pkg-config --libs gtk+-2.0 
gtksourceview-2.0)
++hiro.flags   = $(flags.cpp) -DHIRO_GTK=2 $(shell $(PKG_CONFIG) --cflags 
gtk+-2.0 gtksourceview-2.0) -Wno-deprecated-declarations
++hiro.options = -L/usr/local/lib -lX11 $(shell $(PKG_CONFIG) --libs 
gtk+-2.0 gtksourceview-2.0)
+   endif
+ 
+   ifeq ($(hiro),gtk3)
+-hiro.flags   = $(flags.cpp) -DHIRO_GTK=3 $(shell pkg-config --cflags 
gtk+-3.0) -Wno-deprecated-declarations
+-hiro.options = -L/usr/local/lib -lX11 $(shell pkg-config --libs gtk+-3.0)
++hiro.flags   = $(flags.cpp) -DHIRO_GTK=3 $(shell $(PKG_CONFIG) --cflags 
gtk+-3.0) -Wno-deprecated-declarations
++hiro.options = -L/usr/local/lib -lX11 $(shell $(PKG_CONFIG) --libs 
gtk+-3.0)
+   endif
+ 
+   ifeq ($(hiro),gtk3-se)
+ flags   += -DHiro_SourceEdit
+-hiro.flags   = $(flags.cpp) -DHIRO_GTK=3 $(shell pkg-config --cflags 
gtk+-3.0 gtksourceview-3.0) -Wno-deprecated-declarations
+-hiro.options = -L/usr/local/lib -lX11 $(shell pkg-config --libs gtk+-3.0 
gtksourceview-3.0)
++hiro.flags   = $(flags.cpp) -DHIRO_GTK=3 $(shell $(PKG_CONFIG) --cflags 
gtk+-3.0 gtksourceview-3.0) -Wno-deprecated-declarations
++hiro.options = -L/usr/local/lib -lX11 $(shell $(PKG_CONFIG) --libs 
gtk+-3.0 gtksourceview-3.0)
+   endif
+ 
+   ifeq ($(hiro),qt4)
+ moc = /usr/local/lib/qt4/bin/moc
+-hiro.flags   = $(flags.cpp) -DHIRO_QT=4 $(shell pkg-config --cflags 
QtCore QtGui)
+-hiro.options = -L/usr/local/lib -lX11 $(shell pkg-config --libs QtCore 
QtGui)
++hiro.flags   = $(flags.cpp) -DHIRO_QT=4 $(shell $(PKG_CONFIG) --cflags 
QtCore QtGui)
++hiro.options = -L/usr/local/lib -lX11 $(shell $(PKG_CONFIG) --libs QtCore 
QtGui)
+   endif
+ 
+   ifeq ($(hiro),qt5)
+-moc = $(shell pkg-config --variable=host_bins Qt5Core)/moc
+-hiro.flags   = $(flags.cpp) -DHIRO_QT=5 -fPIC $(shell pkg-config --cflags 
Qt5Core Qt5Gui Qt5Widgets)
+-hiro.options = -L/usr/local/lib -lX11 $(shell pkg-config --libs Qt5Core 
Qt5Gui Qt5Widgets)
++moc = $(shell $(PKG_CONFIG) --variable=host_bins Qt5Core)/moc
++hiro.flags   = $(flags.cpp) -DHIRO_QT=5 -fPIC $(shell $(PKG_CONFIG) 
--cflags Qt5Core Qt5Gui Qt5Widgets)
++hiro.options = -L/usr/local/lib -lX11 $(shell $(PKG_CONFIG) --libs 
Qt5Core Qt5Gui Qt5Widgets)
+   

Bug#1050770: apr FTCBFS: cannot check for cross-process mutex

[Helmut Grohne]

Source: apr
Version: 1.7.2-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

apr fails to cross build from source for most architectures:

| checking for robust cross-process mutex support... configure: error: in 
`/<>/debian/build':
| configure: error: cannot run test program while cross compiling

Usually, I'd consider this an aspect of the builder, but apr is unique
here in that its debian/rules has its own ideas of what that check
should return even natively. I therefore propose updating debian/rules
to also supply the value for cross builds. Do you agree? I'm attaching a
patch for your convenience.

Helmut
diff --minimal -Nru apr-1.7.2/debian/changelog apr-1.7.2/debian/changelog
--- apr-1.7.2/debian/changelog  2023-02-26 21:51:24.0 +0100
+++ apr-1.7.2/debian/changelog  2023-08-28 13:07:59.0 +0200
@@ -1,3 +1,10 @@
+apr (1.7.2-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Supply result for cross-process mutex. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 28 Aug 2023 13:07:59 +0200
+
 apr (1.7.2-3) unstable; urgency=medium
 
   * Add more fixes for atomics from upstream, in particular for
diff --minimal -Nru apr-1.7.2/debian/rules apr-1.7.2/debian/rules
--- apr-1.7.2/debian/rules  2023-02-02 22:18:42.0 +0100
+++ apr-1.7.2/debian/rules  2023-08-28 13:07:55.0 +0200
@@ -36,14 +36,13 @@
  ac_cv_prog_AWK=mawk
 
 # apr_cv_mutex_robust_shared causes hangs in procmutex test on arm(el|hf) and 
alpha
-ifneq (,$(findstring armel,$(DEB_HOST_ARCH)))
-  CONFFLAGS += apr_cv_mutex_robust_shared=no
-endif
-ifneq (,$(findstring armhf,$(DEB_HOST_ARCH)))
+ifneq (,$(filter $(DEB_HOST_ARCH),alpha armel armhf))
   CONFFLAGS += apr_cv_mutex_robust_shared=no
+else
+# apr_cv_mutex_robust_shared cannot be detected during cross compilation
+ifneq ($(DEB_BUILD_ARCH),$(DEB_HOST_ARCH))
+  CONFFLAGS += apr_cv_mutex_robust_shared=yes
 endif
-ifneq (,$(findstring alpha,$(DEB_HOST_ARCH)))
-  CONFFLAGS += apr_cv_mutex_robust_shared=no
 endif
 
 # SH4 cannot use proc_pthread.

Bug#1050768: xastir: Drop unused libproj-dev build dependency

[Bas Couwenberg]

Source: xastir
Version: 2.2.0-1
Severity: normal
Tags: patch

Dear Maintainer,

Your package build depends on libproj-dev but doesn't link to libproj nor 
include proj.h.

The attached patch drops the unused build dependency.

Kind Regards,

Bas
diff -Nru xastir-2.2.0/debian/changelog xastir-2.2.0/debian/changelog
--- xastir-2.2.0/debian/changelog   2023-08-04 10:24:58.0 +0200
+++ xastir-2.2.0/debian/changelog   2023-08-29 07:20:34.0 +0200
@@ -1,3 +1,10 @@
+xastir (2.2.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused libproj-dev build dependency.
+
+ -- Bas Couwenberg   Tue, 29 Aug 2023 07:20:34 +0200
+
 xastir (2.2.0-1) unstable; urgency=medium
 
   * New upstream version 2.2.0.
diff -Nru xastir-2.2.0/debian/control xastir-2.2.0/debian/control
--- xastir-2.2.0/debian/control 2023-08-04 10:24:46.0 +0200
+++ xastir-2.2.0/debian/control 2023-08-29 07:20:30.0 +0200
@@ -13,7 +13,6 @@
festival-dev,
libgraphicsmagick1-dev | libgraphicsmagick-dev,
libshp-dev,
-   libproj-dev,
libpcre2-dev,
libcurl4-gnutls-dev | libcurl-ssl-dev,
libdb-dev,

Bug#1050767: texedit.app: FTBFS: dh_install: error: missing files, aborting

[Aurelien Jarno]

Package: texedit.app
Version: 5.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

texedit.app fails to build from source. From my build log on amd64:

| make[4]: Nothing to be done for 'internal-app-compile'.
|  Copying resources into the app wrapper...
|  Copying localized resources into the app wrapper...
| Warning: .//English.lproj/InfoPlist.strings not found - ignoring
| Warning: .//English.lproj/LinePanel.strings not found - ignoring
| Warning: .//English.lproj/Localizable.strings not found - ignoring
| Warning: .//English.lproj/PrintPanelAccessory.strings not found - ignoring
| Warning: .//English.lproj/ServicesMenu.strings not found - ignoring
| Warning: .//English.lproj/ZoomValues.strings not found - ignoring
| Making install for app TextEdit...
|  Creating 
/<>/debian/textedit.app//usr/lib/GNUstep/Applications...
|  Installing bundle directory...
|  Creating /<>/debian/textedit.app//usr/bin/
| make[1]: Leaving directory '/<>'
|dh_install
| dh_install: warning: Cannot find (any matches for) "*.png" (tried in ., 
debian/tmp)
| 
| dh_install: warning: textedit.app missing files: *.png
| dh_install: error: missing files, aborting
| make: *** [debian/rules:11: binary] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=textedit.app=riscv64=5.0-2=1693238674=0

Regards
Aurelien

Bug#1050766: classified-ads: FTBFS: /usr/include/natpmp.h:52:10: fatal error: natpmp_declspec.h: No such file or directory

[Aurelien Jarno]

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

Dear maintainer,

classified-ads fails to build from source. From my build log on amd64:

| g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -D_REENTRANT -fPIC -DQT_NO_DEBUG 
-DQT_MULTIMEDIA_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_SQL_LIB -DQT_CORE_LIB -I. -I/usr/include/miniupnpc 
-I/usr/include/tcl8.6 -I/usr/include/tk -I/usr/include/tk8.6 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtMultimedia 
-I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtSql 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o networklistener.o 
net/networklistener.cpp
| In file included from net/networklistener.cpp:50:
| /usr/include/natpmp.h:52:10: fatal error: natpmp_declspec.h: No such file or 
directory
|52 | #include "natpmp_declspec.h"
|   |  ^~~
| compilation terminated.
| make[1]: *** [Makefile:2079: networklistener.o] Error 1
| make[1]: Leaving directory '/<>'
| dh_auto_build: error: make -j1 returned exit code 2
| make: *** [debian/rules:10: binary] Error 25
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

A full build log on riscv64 is also available:
https://buildd.debian.org/status/fetch.php?pkg=classified-ads=riscv64=0.15-1=1693267963=0

Regards
Aurelien

Bug#1050765: gammaray: Drop unused libproj-dev build dependency

[Bas Couwenberg]

Source: gammaray
Version: 2.11.3-4
Severity: normal
Tags: patch

Dear Maintainer,

Your package build depends on libproj-dev but doesn't link to libproj nor 
include proj.h.

The attached patch drops the unused build dependency.

Kind Regards,

Bas
diff -Nru gammaray-2.11.3/debian/changelog gammaray-2.11.3/debian/changelog
--- gammaray-2.11.3/debian/changelog2023-07-16 18:33:07.0 +0200
+++ gammaray-2.11.3/debian/changelog2023-08-29 06:29:12.0 +0200
@@ -1,3 +1,10 @@
+gammaray (2.11.3-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop unused libproj-dev build dependency.
+
+ -- Bas Couwenberg   Tue, 29 Aug 2023 06:29:12 +0200
+
 gammaray (2.11.3-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru gammaray-2.11.3/debian/control gammaray-2.11.3/debian/control
--- gammaray-2.11.3/debian/control  2023-07-16 18:32:45.0 +0200
+++ gammaray-2.11.3/debian/control  2023-08-29 06:29:09.0 +0200
@@ -10,7 +10,6 @@
libgraphviz-dev,
libkf5coreaddons-dev,
libkf5syntaxhighlighting-dev,
-   libproj-dev,
libqt5svg5-dev,
libqt5waylandcompositor5-dev,
libwayland-dev (>= 1.12.0),

Bug#1050764: scm: Please add support for new arch Loongarch

[yalingfang]

Package: scm
Version: 5f3-4
Severity: wishlist
Tags: patch
User:debian-de...@lists.debian.org
Usertags: loongarch64

Dear maintainers,

   When I compiled scm for loongarch architecture, it reported
missing architecture support.

We have added loongarch architecture support for scm, the patch

can be found in the attachment.

If you have any questions, you can contact me at any time.

--- scm-5f3.orig/scmfig.h
+++ scm-5f3/scmfig.h
@@ -284,6 +284,10 @@ rgx.c	init_rgx();	regcomp and regexec. *
 # define SHORT_INT
 # define CDR_DOUBLES
 #endif
+#ifdef __loongarch__
+# define SHORT_INT
+# define CDR_DOUBLES
+#endif
 #ifdef MSDOS			/* Microsoft C 5.10 and 6.00A */
 # ifndef GO32
 #  define SHORT_INT

Bug#1050763: pvm: Please add support for new arch Loongarch

[yalingfang]

Package: pvm
Version: 3.4.6-5
Severity: wishlist
Tags: patch
User:debian-de...@lists.debian.org
Usertags: loongarch64

Dear maintainers,

   When I compiled pvm for loongarch architecture, it reported
missing architecture support.

We have added loongarch architecture support for pvm, the patch and the 
getpvmarch change sample file


can be found in the attachment.
 The sample in getpvmarch is following:
loong64)
echo LINUXLOONGARCH
;;


 If you have any questions, you can contact me at any time.

--- /dev/null
+++ pvm-3.4.6/conf/LINUXLOONGARCH.def
@@ -0,0 +1,10 @@
+ARCHCFLAGS =   -DSYSVSIGNAL -DNOWAIT3 -DRSHCOMMAND=\"/usr/bin/rsh\" \
+   -DNEEDENDIAN -DFDSETNOTSTRUCT -DHASERRORVARS \
+   -DCTIMEISTIMET -DSYSERRISCONST -DHASREADLINE
+ARCHDLIB   =
+ARCHDOBJ   =
+ARCHLIB=   -lreadline
+HASRANLIB  =   t
+AR =   ar
+PVM_ARCH   =   LINUXLOONGARCH
+MAKE   =   make
--- /dev/null
+++ pvm-3.4.6/conf/LINUXLOONGARCH.m4
@@ -0,0 +1,19 @@
+divert(-1)
+undefine(`len')
+#
+# append an underscore to FORTRAN function names
+#
+define(`FUNCTION',`$1_')
+#
+# FORTRAN character strings are passed as follows:
+# a pointer to the base of the string is passed in the normal
+# argument list, and the length is passed by value as an extra
+# argument, after all of the other arguments.
+#
+define(`ARGS',`($1`'undivert(1))')
+define(`SAVE',`divert(1)$1`'divert(0)')
+define(`STRING_ARG',`$1_ptr`'SAVE(`, $1_len')')
+define(`STRING_ARG_DECL',`char * $1_ptr; int $1_len')
+define(`STRING_LEN',`$1_len')
+define(`STRING_PTR',`$1_ptr')
+divert(0)
#! /bin/sh

eval `dpkg-architecture`

case $DEB_HOST_ARCH_CPU in
i[36]86)
echo LINUX
;;
sparc*)
echo LINUXSPARC
;;
alpha)
echo LINUXALPHA
;;
m68k)
echo LINUXATARI
;;
amd64)
echo LINUX64
;;
ia64)
echo LINUX64
;;
ppc64|ppc64el)
echo LINUX64
;;
hppa)
echo LINUXHPPA
;;
mips*)
echo LINUXMIPS
;;
s390)
echo LINUXS390
;;
s390x)
echo LINUXS390
;;
powerpc)
echo LINUXPPC
;;
arm)
echo LINUXARM
;;
arm64)
echo LINUX64
;;
sh4)
echo LINUXSH
;;
riscv64)
echo LINUXRISCV
;;
loong64)
echo LINUXLOONGARCH
;;
*)
echo 'Unknown architecture!' 1>&2
exit 1;
esac

Bug#1040690: emacsen-common analysis for cruft files from elpa-foo packages during apt upgrade

[Rob Browning]

Richard Lewis  writes:

> the latter - new emacsen-common is present but in state 'unpacked' before
> new dh-* is unpackaged

I think I may understand what's going on now, and if so, the issue
rests on a misunderstanding in emacsen-common about how the
maintainerscript states work.

We've been discussing some improvements, some more dramatic than others
on #debian-emacs, and I've been toying with some of the possibilities.

> ( i suspect dpkg triggers should be the answer- should the question be
> understood better --- eg it looks like jed does something similar with .sl
> files, at least i think it does -- i didnt find any documentation on that
> either)

Hah, that's one of the approaches I've been toying with for the past few
days.  If it pans out, I'll likely make a proposal along with changes to
debian-emacs-policy in a while.

I'd considered triggers a few times in the past, but only recently
thought of a way that addresses the issues I'd previously been concerned
about.

If this does work out, we're also likely to add recompilation of
rdepends during add-on package upgrades (i.e. in case "public" macros
have changed in incompatible ways).

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#1050577: emacs: please limit number of native-compilation workers

[Rob Browning]

Sean Whitton  writes:

> I would be in favour of patching in setting it to 1.  It's not a problem
> for people to increase it, after all.

No objection, fwiw.  I could also see adding some
DEBIAN_EMACS_DEFAULT_COMPILE_CONCURRENCY variable, or somehthing, if
that would be helpful.

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#1050652:

[Mister Ilari Jääskeläinen]

The build text output is way too verbose anyway.

Bug#1050711: Acknowledgement (dgit erroneously allowed an upload reusing a version number)

[Ian Jackson]

Control: tags -1 + confirmed

$ dgit push-source --damp-run experimental
canonical suite name for experimental is rc-buggy
dpkg-source: warning: short option not allowed in work/debian/source/options, 
line 1
dpkg-source: warning: no source format specified in debian/source/format, see 
dpkg-source(1)
dpkg-source: warning: --include-removal is not a valid option for 
Dpkg::Source::Package::V1
dpkg-source: warning: --no-preparation is not a valid option for 
Dpkg::Source::Package::V1
dpkg-source: info: using source format '1.0'
dpkg-source: warning: source directory 'work' is not 
- 'dgit-test-dummy-1.37'
dpkg-source: info: building dgit-test-dummy in dgit-test-dummy_1.37.tar.gz
dpkg-source: info: building dgit-test-dummy in dgit-test-dummy_1.37.dsc
changelog will contain changes since 1.37
dpkg-genchanges: warning: 'since' option specifies most recent version '1.37', 
ignoring
dpkg-genchanges: info: including full source code in upload
Not updating refs/tags/archive/debian/1.21 from 
a030b5fc0980550014ea0b70c9b89f5892a145f9 to 
29e6a48f4a4cb9bd150c7992746ee22291ab340d.
Not updating refs/tags/debian/1.21 from 
f4849a972e08dd21d585ba643f407f01fa792529 to 
767c2780988df452820b47d52237f7d2d9176f00.
Not updating refs/tags/debian/1.23 from 
1d0ca2f8bccf54c5a4e7e86e3597d4b793524cf1 to 
35ec850491e5f892bbced8d230b664cae514ddd5.
Not updating refs/tags/debian/1.24 from 
4ad4a4cfe21da30ac6ecd6ea5ddbc5a3c7b990ea to 
ea2c675fe61a6739de8ddfdff02bf102f41f664a.
Not updating refs/tags/debian/1.25 from 
bec2b929d3f07a212412e57493fb73a3100a57bd to 
fc1e169c33fcac379317abd39b3d8ba4be9e361b.
last upload to archive: NO git hash
using existing dgit-test-dummy_1.37.tar.gz
dpkg-source: info: extracting dgit-test-dummy in dgit-test-dummy-1.37
dpkg-source: info: unpacking dgit-test-dummy_1.37.tar.gz
synthesised git commit from .dsc 1.37
checking that dgit-test-dummy_1.37.dsc corresponds to HEAD
dpkg-source: warning: extracting unsigned source package 
(/home/ian/things/Dgit/dgit-test-dummy/../bpd/dgit-test-dummy_1.37.dsc)
dpkg-source: info: extracting dgit-test-dummy in dgit-test-dummy-1.37
dpkg-source: info: unpacking dgit-test-dummy_1.37.tar.gz
../bpd/dgit-test-dummy_1.37_source.changes already has appropriate .orig(s) (if 
any)
# gpg --detach-sign --armor -u 559AE46C2D6B6D3265E7CBA1E3E3392348B50D39 
/home/ian/things/Dgit/dgit-test-dummy/.git/dgit/tag.tmp
# gpg --detach-sign --armor -u 559AE46C2D6B6D3265E7CBA1E3E3392348B50D39 
/home/ian/things/Dgit/dgit-test-dummy/.git/dgit/tag-dgit.tmp
# git verify-tag cbf7afc338be0a0b0b58618492ff09749ddf9b86
# git verify-tag 05f1ef19beb590150ee0f7d87f4c67f70f4f0ab0
# git -c push.followTags=false push 
'git+ssh://d...@push.dgit.debian.org/dgit/debian/repos/dgit-test-dummy.git' 
de18c7def52e4a0fc67c0714b7385291a5728838:refs/dgit/rc-buggy 
refs/tags/archive/debian/1.37 refs/tags/debian/1.37
# git update-ref -m 'dgit push' refs/remotes/dgit/dgit/rc-buggy 
de18c7def52e4a0fc67c0714b7385291a5728838
# debsign -k559AE46C2D6B6D3265E7CBA1E3E3392348B50D39 
../bpd/dgit-test-dummy_1.37_source.changes
# dput ftp-master ../bpd/dgit-test-dummy_1.37_source.changes
would be ok: pushed and uploaded 1.37 (but dry run only)
$

-- 
Ian JacksonThese opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Bug#1050762: feedbackd-device-themes: Users are not informed about existing tools from the feedbackd package

[Boud Roukema]

Package: feedbackd-device-themes
Version: 0.0.r3-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?

I tried following the upstream 'feedbackd' README file and spent a lot
of time making wrong guesses about syntax and about testing the effects
of modifying the theme .json files.


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


I checked for /usr/share/doc/feedbackd-device-themes and I searched
through installed versions of the two packages
(feedbackd-device-themes and feedbackd), their Debian git sources, and
their upstream sources for hints.


   * What was the outcome of this action?

I found that there is no installed documentation:

$ ls -l /usr/share/doc/feedbackd-device-themes/
total 3
-rw-r--r-- 1 root root  682 Feb  2  2023 changelog.Debian.gz
-rw-r--r-- 1 root root 1514 Dec 16  2022 copyright


I discovered from browsing sources and git histories that the debian
'feedbackd' package automatically installs several user-level programs
that the user should be informed about:


$ dpkg -L feedbackd | grep /usr/bin

/usr/bin
/usr/bin/fbcli
/usr/bin/fbd-theme-validate




   * What outcome did you expect instead?

I expected to see a useful README.Debian file that informs the
user about Debian tools that are easily made available by installing
'feedbackd':

/usr/share/doc/feedbackd-device-themes/README.Debian.gz

along with a minimal Debian-appropriate hint on customisation.


PROPOSAL:

I propose adding the following file (under GPL-3 for compatibility with
the other files):

cat > debian/feedback-device-themes.README.Debian << EOF
Tools for checking customised themes


See the upstream README file for hints on how to customise
your feedbackd themes. Example files that can be copied to,
for example, "~/.config/feedbackd/themes/custom.json"
include "/usr/share/feedbackd/themes/default.json"
from the "feedbackd" package and the theme in
"/usr/share/feedbackd/themes/" that matches your device.
You can remove the "parent-theme" parameter if you find
its role unclear.

Use the commands

  gsettings get org.sigxcpu.feedbackd theme
  gsettings set org.sigxcpu.feedbackd theme custom
  gsettings reset org.sigxcpu.feedbackd theme

to get the current theme, set to your custom theme, or reset to
the default theme.

You can use commands from the "feedbackd" package
to check the syntax of your custom.json file and
to check its effects. To check the syntax,

  fbd-theme-validate custom.json

To see the effects of your custom.json file, you will need to restart
the running "feedbackd" daemon, e.g. "killall feedbackd" and then
close and reopen a gui such as chatty that automatically restarts
"feedbackd". Then (or before you switch) you can check individual
effects:

  fbcli --event message-new-sms --profile full
  fbcli --event message-new-sms --profile quiet
  fbcli --event phone-missed-call --profile full
  fbcli --event phone-incoming-call --profile full
  fbcli --event phone-incoming-call --profile quiet
  fbcli --event phone-incoming-call --profile silent

See the man pages on fbd-theme-validate and fbcli for more
information.

[1] https://source.puri.sm/Librem5/feedbackd/README.md
EOF

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 6.1-sunxi64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

feedbackd-device-themes depends on no packages.

Versions of packages feedbackd-device-themes recommends:
ii  feedbackd  0.2.0-2

feedbackd-device-themes suggests no packages.

-- no debconf information

Bug#1050761: RM: golang-github-siddontang-go-snappy -- RoQA; dead upstream; orphaned; gitea leaf package

[Chris Hofstaedtler]

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

Dear ftpmasters,

please remove golang-github-siddontang-go-snappy. It was introduced for
Gitea, which is long gone again.
This package is a library package, itself dead upstream and orphaned in
Debian.

Note: src:golang-github-lunny-nodb must be removed first.

Thanks,
Chris

Bug#1050760: RM: golang-github-lunny-nodb -- RoQA; dead upstream; orphaned; gitea leaf package

[Chris Hofstaedtler]

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

Dear ftpmasters,

please remove golang-github-lunny-nodb. It was introduced for Gitea,
which is long gone again.
This package is a leaf library package, itself dead upstream and
orphaned in Debian.

Thanks,
Chris

Bug#1050759: RM: golang-github-siddontang-rdb -- RoQA; dead upstream; orphaned; gitea leaf package

[Chris Hofstaedtler]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: golang-github-siddontang-...@packages.debian.org
Control: affects -1 + src:golang-github-siddontang-rdb

Dear ftpmasters,

please remove golang-github-siddontang-rdb. It was introduced for Gitea,
which is long gone again.
This package is a leaf library package, itself dead upstream and
orphaned in Debian.

Thanks,
Chris

Bug#1050758: RM: golang-gopkg-alexcesaro-quotedprintable.v3 -- RoQA; dead upstream; orphaned; gitea leaf package

[Chris Hofstaedtler]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: golang-gopkg-alexcesaro-quotedprintable...@packages.debian.org
Control: affects -1 + src:golang-gopkg-alexcesaro-quotedprintable.v3

Dear ftpmasters,

please remove golang-gopkg-alexcesaro-quotedprintable.v3. It was
introduced for Gitea, which is long gone again.
This package is a leaf library package, itself dead upstream and
orphaned in Debian.

Thanks,
Chris

Bug#1050757: RM: golang-strk.kbt-projects-go-libravatar -- RoQA; dead upstream; orphaned; gitea leaf package

[Chris Hofstaedtler]

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

Dear ftpmasters,

please remove golang-strk.kbt-projects-go-libravatar. It was introduced
for Gitea, which is long gone again. This package is a leaf library
package, itself dead upstream and orphaned in Debian.

Thanks,
Chris

Bug#1050756: RM: golang-github-unknwon-paginater -- RoQA; dead upstream; orphaned; gitea leaf package

[Chris Hofstaedtler]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: golang-github-unknwon-pagina...@packages.debian.org
Control: affects -1 + src:golang-github-unknwon-paginater

Dear ftpmasters,

please remove golang-github-unknwon-paginater. It was introduced for
Gitea, which is gone since a long time. This package is a leaf library
package, itself upstream dead and orphaned in Debian.

Thanks,
Chris

Bug#1050602: feedbackd: package documentation files are not installed into /usr/share/doc/

[Boud Roukema]

On Sat, 26 Aug 2023, Boud Roukema wrote:


I expected to find upstream files such as

README.md  (possibly renamed to README.source)
NEWS.gz
NEWS.Debian.gz

installed in /usr/share/doc/feedbackd/ .


Obviously, NEWS.Debian.gz is not an upstream file. :)

Bug#1050755: usr-is-merged.postinst operates on outer directories with DPKG_ROOT

[Johannes Schauer Marin Rodrigues]

Package: usrmerge
Version: 36
Severity: serious
Tags: patch

Hi,

the recent changes to usr-is-merged.postinst broke DPKG_ROOT support:

Setting up usr-is-merged (36) ...
removed '/lib64'
/tmp/mmdebstrap.P6Rv45i7Hi/var/lib/dpkg/info/usr-is-merged.postinst: 16: rmdir: 
not found
dpkg: error processing package usr-is-merged (--configure):
 installed usr-is-merged package post-installation script subprocess returned 
error exit status 127
Errors were encountered while processing:
 usr-is-merged
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: setup failed: E: command failed: 
/usr/share/mmdebstrap/hooks/merged-usr/essential00.sh
I: main() received signal PIPE: waiting for setup...
I: removing tempdir /tmp/mmdebstrap.P6Rv45i7Hi...
Can't exec "rm": No such file or directory at /usr/bin/mmdebstrap line 6232.
E: rm failed: -1

Since usr-is-merged.postinst fails to respect $DPKG_ROOT it will operate
on the directory hierarchy outside the chroot and remove several rather
important directories.

I'm filing this with severity series because it breaks the mmdebstrap
autopkgtest and should thus be prevented from transitioning to testing until
fixed. The following patch fixes the problem:

diff -Nru usrmerge-36/debian/usr-is-merged.postinst 
usrmerge-36+nmu1/debian/usr-is-merged.postinst
--- usrmerge-36/debian/usr-is-merged.postinst   2023-08-27 13:33:27.0 
+0200
+++ usrmerge-36+nmu1/debian/usr-is-merged.postinst  2023-08-29 
01:14:03.0 +0200
@@ -9,11 +9,11 @@
   # so clean up the unused (and unowned) ones
   local arch_directories="/lib64 /lib32 /libo32 /libx32"
   for dir in $arch_directories; do
-[ -e "$dir" ] || continue
+[ -e "$DPKG_ROOT$dir" ] || continue
 if ! dpkg-query -S $dir >/dev/null 2>&1; then
-  rm -v $dir
-  if [ -e /usr$dir ] && ! dpkg-query -S /usr$dir >/dev/null 2>&1 ; then
-rmdir --ignore-fail-on-non-empty -v /usr$dir
+  rm -v "$DPKG_ROOT$dir"
+  if [ -e "$DPKG_ROOT/usr$dir" ] && ! dpkg-query -S /usr$dir >/dev/null 
2>&1 ; then
+rmdir --ignore-fail-on-non-empty -v "$DPKG_ROOT/usr$dir"
   fi
 fi
   done

Bug#1041508: tex-common: fmutil fails to rebuild formats

[Preuße]

On 20.07.2023 00:06, ಚಿರಾಗ್ ನಟರಾಜ್ wrote:

Hello ಚಿರಾಗ್ ನಟರಾಜ್,


Upgrading tex-common seems to fail when attempting to rebuild formats (log 
attached).

This reminds me to an issue I've seen due to an incomplete upgrade to TL 
2023. The issue should be solved by yesterdays upload of TL 2023 to 
unstable. Could you check?


Hilmar
--
sigfault



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042361: RFS: texlive-bin/2023.20230311.66589-3 -- TeX Live: Package split

[Hilmar Preusse]

Control: retitle -1 RFS: texlive-bin/2023.20230311.66589-4 -- TeX Live: Package 
split
Control: tags -1 - moreinfo

On 27.07.23 Hilmar Preusse (hill...@web.de) wrote:

> Package: sponsorship-requests
> Severity: wishlist
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "texlive-bin":
> 
>  * Package name : texlive-bin
>Version  : 2023.20230311.66589-3
>Upstream contact : k...@freefriends.org
>  * URL  : https://www.tug.org/texlive/
>  * License  : MIT, TeX-Live, GPL-2+
>  * Vcs  : https://github.com/debian-tex/texlive-bin
>Section  : tex
> 

The revison -3 was used to upload TL 2023 to unstable. This is
revision -4: next attempt to split the JIT binaries into a new package.

Hilmar
-- 
sigmentation fault


signature.asc
Description: PGP signature

Bug#1050498: pipewire-pulse systemd service not restarted despite dpkg upgrade of all pipewire packages

[Boud Roukema]

hi Dylan,

On Mon, 28 Aug 2023, Dylan Aïssi wrote:


I think the bug you are describing is a kind of duplicate of #1027136 [1]
filled against xdg-desktop-portal. So, I will quote the smcv's answer here [2]:


I think (the) xdg-desktop-portal user service(s) should be stopped before
removing the package. Is that possible?


Not really: maintainer scripts happen in the context of the overall system
(as root) and there is not really a good way to inject service-management
commands into user sessions. Other per-user services like PulseAudio,
Pipewire, gpg-agent and so on are not stopped when you remove them either.


I see your point: from the system point of view, it's the user's responsibility
to know that if s/he upgrades pipewire, then s/he should either restart *all*
services running pipewire, or *none* of them (or live dangerously with a mix 
:P).

However, in that case, we should inform (at least) the user who knows
enough to look in the obvious place: /usr/share/docs/pipewire-pulse/; this
is currently empty except for 'copyright' and 'changelog.Debian.gz'.
At least one moderately experienced user (me) doesn't know much about
pipewire, and messed up. I assumed (incorrectly) that pipewire-pulse
would be automatically restarted if pipewire were restarted.

Here are two non-exclusive proposals.

PROPOSAL (1):

Should the user be informed when doing the system upgrade? More specifically,
would a one-line warning to the user be considered acceptable, as a post-install
script? E.g. something like:

"Please recommend that users restart all scripts running pipewire (such as pipewire, 
pipewire-pulse)"


PROPOSAL (2):

Add the following file (under the default licence for pipewire - Expat - no
need to complicate the licensing further):

cat > debian/pipewire-pulse.README.Debian << EOF 
Relation to pipewire and upgrades

=

The pipewire-pulse systemd service runs independently of the pipewire
service. Both run as user services and are not restarted when a
system-level upgrade is performed by the root user. If you wish to 
check that you restart pipewire-pulse whenever the pipewire is
upgraded using dpkg or apt, then consider using either 
"checkrestart" in the "debian-goodies" package [1] or "needrestart" [2].

These need to be run as root user, but aim to check for both
system and user services that need restarting.

[1] https://tracker.debian.org/pkg/debian-goodies
[2] https://tracker.debian.org/pkg/needrestart
EOF

My guess is that an extra file debian/pipewire-pulse.docs won't be
needed for this to be automatically installed. I tried both
checkrestart and needrestart, which both gave credible answers
(e.g. 'No user sessions are running outdated binaries.')


It's unclear to me if xdg-desktop-portal or other related programs
also need a similar debian/xdg-desktop-portal.README.Debian file.
After the udpate to pipewire 0.3.78 and restarting pipewire, 'pw-dump'
showed all the following as still being pipewire clients at version
0.3.77-1:

$ cat old-pw-dump | grep -n -B14 0\.3\.77 | sed -e "s/\(machine-id.\).*\'/\1: 
/"

659-"type": "PipeWire:Interface:Client",
660-"version": 3,
661-"permissions": [ "r", "w", "x", "m" ],
662-"info": {
663-  "change-mask": [ "props" ],
664-  "props": {
665-"application.language": "C.UTF-8",
666-"application.name": "xdg-desktop-portal",
667-"application.process.binary": "xdg-desktop-portal",
668-"application.process.host": "mobian",
669-"application.process.id": 1685,
670-"application.process.user": "mobian",
671-"clock.power-of-two-quantum": true,
672-"core.name": "pipewire-mobian-1685",
673:"core.version": "0.3.77",
--
709-"info": {
710-  "change-mask": [ "props" ],
711-  "props": {
712-"application.language": "C.UTF-8",
713-"application.name": "gsd-power",
714-"application.process.binary": "gsd-power",
715-"application.process.host": "mobian",
716-"application.process.id": 1171,
717-"application.process.machine-id": 
718-"application.process.user": "mobian",
719-"client.api": "pipewire-pulse",
720-"clock.power-of-two-quantum": true,
721-"config.name": "pipewire-pulse.conf",
722-"core.name": "pipewire-mobian-853",
723:"core.version": "0.3.77",
--
759-"info": {
760-  "change-mask": [ "props" ],
761-  "props": {
762-"application.language": "C",
763-"application.name": "CallAudio",
764-"application.process.binary": "callaudiod",
765-"application.process.host": "mobian",
766-"application.process.id": 1040,
767-"application.process.machine-id": 
768-"application.process.user": "mobian",
769-"client.api": "pipewire-pulse",
770-"clock.power-of-two-quantum": true,
771-"config.name": "pipewire-pulse.conf",
772-

Bug#1050754: tolua: Move to a lua version != 5.2

[Bastian Germann]

Source: tolua
Version: 5.2.4-0.1
Severity: wishlist
Control: block 1050640 by -1

Please build your package with a different lua version so we can drop lua5.2 
from the archive.

Bug#1050753: uwsgi-plugin-lua5.2: Drop this package and lua5.2 Build-Depends

[Bastian Germann]

Package: uwsgi-plugin-lua5.2
Version: 2.0.22-1
Severity: wishlist
Control: block 1050640 by -1

Please drop uwsgi-plugin-lua5.2 and its Build-Depends so we can drop lua5.2 
from the archive.
uwsgi-app-integration-plugins has to drop its dependency on the package as well but as it also 
depends on the -lua5.1 version, no harm should be done.

Bug#1050752: breaks chrootless and mmdebstrap autopkgtest

[Johannes Schauer Marin Rodrigues]

Package: debianutils
Version: 5.9
Severity: serious
Tags: patch

Hi,

this commit broke $DPKG_ROOT support:

https://salsa.debian.org/debian/debianutils/-/commit/89daf5e2

this in turn breaks the mmdebstrap autopkgtest, thus filing this with severity
serious to prevent transition to testing until this problem is fixed.

The following patch fixes the problem:

--- a/debian/postinst
+++ b/debian/postinst
@@ -14,10 +14,10 @@ ua() {
 
 usrmerge(){
for p in run-parts tmpfile; do
-   [ -e /usr/bin/$p ] || ln -s /bin/$p /usr/bin/$p
+   [ -e "$DPKG_ROOT/usr/bin/$p" ] || ln -s /bin/$p 
"$DPKG_ROOT/usr/bin/$p"
done
-   [ -e /usr/sbin/installkernel ] || \
-   ln -s /sbin/installkernel 
/usr/sbin/installkernel
+   [ -e "$DPKG_ROOT/usr/sbin/installkernel" ] || \
+   ln -s /sbin/installkernel 
"$DPKG_ROOT/usr/sbin/installkernel"
 }
 
 if test -z "$2" && test ! -f "$DPKG_ROOT/etc/shells"

Bug#1050751: qosmic: Move to a lua version != 5.2

[Bastian Germann]

Source: qosmic
Version: 1.6.0+git20210807.9f63288-4
Severity: wishlist
Control: block 1050640 by -1

Please build your package with a different lua version so we can drop lua5.2 
from the archive.

Bug#1050750: dnsmasq: Move to a lua version != 5.2

[Bastian Germann]

Source: dnsmasq
Version: 2.89-1
Severity: wishlist
Control: block 1050640 by -1

Please build your package with a different lua version so we can drop lua5.2 
from the archive.

Bug#1050749: kyua: Downgrade to lua5.1

[Bastian Germann]

Source: kyua
Version: 0.13+git20190402+a685f911237e-1
Severity: wishlist
Tags: patch
Control: block 1050640 by -1

Please build your package with lua5.1 so we can drop v5.2 from the archive. The build system 
supports it but you can certainly also try patching to a more up to date lua version.


I have attached a patch to downgrade.From: Bastian Germann 
Date: Mon, 28 Aug 2023 23:58:26 +0200
Subject: Build with lua5.1

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index fae788f..7c7d9b3 100644
--- a/debian/control
+++ b/debian/control
@@ -7,7 +7,7 @@ Build-Depends:
  debhelper-compat (= 12),
  libatf-dev,
  atf-sh,
- liblua5.2-dev,
+ liblua5.1-0-dev,
  liblutok-dev,
  libsqlite3-dev,
  pkgconf | pkg-config

Bug#1050746: RM: gnome-shell-extension-pixelsaver -- ROM; no longer works in gnome, not fixed upstream

[Jonathan Carter]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: gnome-shell-extension-pixelsa...@packages.debian.org
Control: affects -1 + src:gnome-shell-extension-pixelsaver


Dear FTP team

Please remove gnome-shell-extension-pixelsaver

It no longer works in GNOME, at least, with most apps, and upstream
doesn't seem to release any new releases/fixes for it.

thanks,

-Jonathan

Bug#1050747: ITP: ktextaddons -- Various text handling addons

[Patrick Franz]

Package: wnpp
Severity: wishlist
Owner: Patrick Franz 
X-Debbugs-Cc: debian-de...@lists.debian.org, 
delta...@debian.org,debian-qt-...@lists.debian.org

* Package name: ktextaddons
  Version : 1.4.0
* URL : https://invent.kde.org/libraries/ktextaddons
* License : GPL-2, LGPL-2
  Programming Lang: C++
  Description : Various text handling addons

KTextAddons is a collection of text addons libraries developed
by the KDE community.

Package will be maintained within the Debian Qt/KDE team.

Bug#1050592: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl

[Aurelien Jarno]

On 2023-08-28 21:56, Aurelien Jarno wrote:
> Hi Niko,
> 
> On 2023-08-27 14:43, Niko Tyni wrote:
> > (full quote for the benefit of the Aurelien and other glibc maintainers)
> > 
> > On Sat, Aug 26, 2023 at 09:07:38PM +0300, Niko Tyni wrote:
> > > Package: perl
> > > Version: 5.36.0-8
> > > Severity: serious
> > > X-Debbugs-Cc: debian-powe...@lists.debian.org
> > > Control: affects -1 libfile-fcntllock-perl
> > > 
> > > Hi,
> > > 
> > > debugging an unexpected autopkgtest failure of
> > > libfile-fcntllock-perl_0.22-4+b1 with perl_5.36.0-8 on ppc64el [1] I found
> > > it's because the old perl binary (5.36.0-7) was built with the fcntl(2)
> > > constant F_GETLK == 12, but the new one with F_GETLK == 5 [2].
> > > 
> > > There are no source or build system changes in perl that would have caused
> > > this change. The failure is currently blocking perl testing migration,
> > > so filing at 'serious'.
> > > 
> > > Perl is built with -D_FILE_OFFSET_BITS=64, and I see that on bullseye
> > > this causes F_GETLK == F_GETLK64 == 12, but on bookworm and later
> > > F_GETLK == 5 while F_GETLK64 == 12 [3]. I didn't find the exact
> > > change that caused this yet.
> > > 
> > > As can be expected from the above, building libfile-fcntllock-perl on
> > > bookworm against perl_5.36.0-7 makes it fail its test suite in a similar
> > > way. And rebuilding it on sid against perl_5.36.0-8 makes it pass.
> > > 
> > > On amd64 the constants have stayed equal (== 5) from bullseye to sid,
> > > and _FILE_OFFSET_BITS=64 doesn't affect them. What's the deal on ppc64el?
> > > 
> > > Copying the powerpc porters list. Could you please look into this?
> > > 
> > > [1] 
> > > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/libf/libfile-fcntllock-perl/34669085/log.gz
> > > [2] perl -MPOSIX -E 'say F_GETLK'
> > > [3] printf '#include \nF_GETLK\nF_GETLK64\n' | cpp 
> > > -D_FILE_OFFSET_BITS=64 | tail -2
> 
> Thanks for the details and the investigation.
> 
> > I think the relevant change here is this in libc6-dev_2.36-9+deb12u1 for 
> > bookworm:
> > 
> > --- libc6-dev_2.36-9/usr/include/powerpc64le-linux-gnu/bits/fcntl.h 
> > 2023-04-10 09:35:16.0 +0100
> > +++ libc6-dev_2.36-9+deb12u1/usr/include/powerpc64le-linux-gnu/bits/fcntl.h 
> > 2023-07-13 19:07:47.0 +0100
> > @@ -33,6 +33,12 @@
> >  # define __O_LARGEFILE 020
> >  #endif
> >  
> > +#if __WORDSIZE == 64
> > +# define F_GETLK   5
> > +# define F_SETLK   6
> > +# define F_SETLKW  7
> > +#endif
> > +
> 
> Indeed you are correct that the issue has been introduced by this patch.
> It fixes the case *without* -D_FILE_OFFSET_BITS=64, but OTOH breaks the
> case *with* it.
> 
> > and a similar one in 2.37-2 for trixie/sid.
> > 
> > The applicable changelog entry is presumably
> > 
> >[ Aurelien Jarno ]
> >* debian/patches/git-updates.diff: update from upstream stable branch:
> >  [...]
> >  - Not affecting bookworm release architectures:
> >- Fix LFS POSIX lock constants for powerpc64.
> > 
> > Aurelien, it seems that there's an oversight as ppc64el is a release 
> > architecture?
> 
> Yes, sorry about that. When reading the changelog and the diff, I
> thought it was only for powerpc64, as ppc64el has a different ABI, but I
> was wrong.
> 
> > I can see that this changed for the better, but what should I do with the 
> > above
> > breakage? Rebuild perl and libfcntl-fcntllock-perl and declare some Breaks?
> > Do we want to do that for stable too?
> 
> I think it's an ABI breakage that should be fixed, but just reverting
> the patch will break the case without -D_FILE_OFFSET_BITS=64. I'll check
> with upstream and try to get the issue fixed in both testing/sid and
> stable. I'll keep you updated. In the meantime feel free to reassign the
> bug to the glibc.

I have opened a bug upstream:
https://sourceware.org/bugzilla/show_bug.cgi?id=30804

And submitted a possible patch:
https://sourceware.org/pipermail/libc-alpha/2023-August/151199.html

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1050748: lutok: Downgrade to lua5.1

[Bastian Germann]

I am uploading a LowNMU to fix this.
The changes are in the git repo.

Bug#1033274: gnome-session: recommends xdg-desktop-portal-gnome and not depends

[Jeremy Bícha]

On Mon, Mar 20, 2023 at 6:51 PM Pablo Mazzini  wrote:
> gnome-session can work properly without xdg-desktop-portal-gnome.
>
> As per the policy:
> Depends: This declares an absolute dependency.
> Recommends: This declares a strong, but not absolute, dependency.
>
> Please recommend xdg-desktop-portal-gnome.
>
> The gnome-core meta package already provides this dependency and it may
> be appropriate there.

I am not convinced by your justification. Flatpak and Snap packages
are expected to work on Debian and require an xdg-desktop-portal
implementation. It is impossible for Flatpak (or Snap) alone to depend
on the correct portal implementation for each desktop. Therefore, the
desktop session needs to depend on the portal that has the best
integration.

The Debian GNOME team has gotten bugs for years from people who
complain that their system doesn't work after disabling installing
recommended packages. Ironically, the fact that you are asking for
this change proves to me that there are people who intend to remove
recommended packages.

I am really struggling to see how the benefit of having one less
package installed outweighs the harm caused by sandboxed apps being
broken.

Thank you,
Jeremy Bícha

Bug#1050748: lutok: Downgrade to lua5.1

[Bastian Germann]

Source: lutok
Version: 0.4+dfsg-4
Severity: wishlist

Please build your package with lua5.1 so we can drop v5.2 from the archive.
The build system supports it as fallback but you can certainly also try patching to a more up to 
date lua version.

Bug#1050745: ITP: labwc -- wlroots-based window-stacking compositor for wayland, inspired by openbox

[Birger Schacht]

Package: wnpp
Severity: wishlist
Owner: Birger Schacht 
X-Debbugs-Cc: debian-de...@lists.debian.org, bir...@debian.org

* Package name: labwc
  Version : 0.6.4
  Upstream Contact: https://github.com/labwc/labwc
* URL : https://labwc.github.io/
* License : GPL-2
  Programming Lang: C
  Description : wlroots-based window-stacking compositor for wayland, 
inspired by openbox

Labwc is a wlroots-based window-stacking compositor for wayland, inspired by
openbox.
.
It is light-weight and independent with a focus on simply stacking windows
well and rendering some window decorations. It takes a no-bling/frills
approach and says no to features such as icons (except window buttons),
animations, decorative gradients and any other options not required to
reasonably render common themes. It relies on clients for panels, screenshots,
wallpapers and so on to create a full desktop environment.

Bug#1050665: clutter-1.0: FTBFS on riscv64 due to test timeout

[Aurelien Jarno]

Hi Simon,

On 2023-08-28 11:07, Simon McVittie wrote:
> On Sun, 27 Aug 2023 at 21:18:38 +0200, Aurelien Jarno wrote:
> >  test(t, test_bin,
> >suite: suite_name,
> >env: test_env,
> > +  timeout: 100,
> >  )
> 
> It's probably worth mentioning before you file too many bugs similar to
> this one that Meson has a feature that's really useful in this situation:

I do not expect a lot similar bugs, as riscv64 was built before on
debian-ports, it's mostly for the packages which evolved since they got
built on debian-ports. That said, the fact that the development is
reopened after the Bookworm release and the lack of experimental on the
debian archive increase the chances to have such cases.

> if debian/rules passes an argument like `--timeout-multiplier 5` to
> `meson test`, then all test(timeout:) arguments are multiplied by 5.
> 
> Choosing an appropriate --timeout-multiplier is often enough to make
> tests pass on slower buildds without having to patch any upstream source,
> which reduces the time spent on rebasing patches later.

Thanks a lot for the explanation. That's indeed way better. I therefore
came with the following patch instead:

--- clutter-1.0-1.26.4+git2779b932+dfsg/debian/rules
+++ clutter-1.0-1.26.4+git2779b932+dfsg/debian/rules
@@ -56,7 +56,7 @@
 ifneq (,$(filter armel s390x,$(DEB_HOST_ARCH)))
 # Ignore test failures on architectures where they fail
 else ifneq (,$(filter hppa hurd-i386 kfreebsd-i386 kfreebsd-amd64 mips mipsel 
mips64el powerpc ppc64 sparc64,$(DEB_HOST_ARCH)))
-   -dbus-run-session -- xvfb-run -a dh_auto_test
+   -dbus-run-session -- xvfb-run -a dh_auto_test -- --timeout-multiplier 3
 else
-   dbus-run-session -- xvfb-run -a dh_auto_test
+   dbus-run-session -- xvfb-run -a dh_auto_test -- --timeout-multiplier 3
 endif

I didn't try to use a different multiplier depending on the
architecture as it has no impact on working tests anyway.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1050744: RM: fnfx -- RoQA; obsolete, dead upstream

[Moritz Muehlenhoff]

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

Please remove fnfx, this is an addon package for 20 year old laptops,
long dead upstream like the laptops it originally supported.

Cheers,
Moritz

Bug#1050743: RM: elida -- RoQA; obsolete, unused, dead upstream

[Moritz Muehlenhoff]

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

Please remove elida, it's obsolete, unused and without an adopter for years.
Upstream is also gone, the former maintainer was also the author.

Cheers,
Moritz

Bug#1050742: RM: digitools -- RoQA; obsolete, dead upstream, unmaintained

[Moritz Muehlenhoff]

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

Please remove digitools. It's obsolete (it's for a barebone system
released 20 years ago), dead upstream and unmaintained (last upload
in 2008).

Cheers,
Moritz

Bug#1021950: bazel-bootstrap: Please upgrade Bazel to version 5.0.0

[Olek Wojnar]

Control: retitle -1 Please upgrade Bazel to version 5.0.0

Hi Daniel and thank you for your interest in the Debian Bazel package!

On 2/5/23 04:05, Daniel Baumann wrote:

retitle 1021950 update to current LTS version (6.0)
thanks


Sorry for not noticing this sooner but this bug is for tracking our 
progress to the goal of packaging Bazel 5.x.



I'd like to upload a package to debian that requires basel >=6, it would
be nice if you could update the package.


I would love to package 6.x and my goal is to include it (if not 7.x) in 
the trixie release. If you want to get notifications for that goal, 
please open a new wishlist bug against bazel-bootstrap so that you can 
get those notifications.


Furthermore, I encourage you to join our team on Salsa [1] and subscribe 
to our excessively low-volume mailing list [2]. We welcome any help that 
you'd be willing to volunteer towards achieving these goals.


Thanks and looking forward to speaking with you more!

-Olek

[1] https://salsa.debian.org/bazel-team/meta/
[2] https://lists.debian.org/debian-bazel/

Bug#1050741: linux-image-6.4.0-3-amd64: left super key (left windows key) no longer works

[Piotr Engelking]

Package: src:linux
Version: 6.4.11-1
Severity: normal

Pressing the left Super key (also known as left Windows key) no longer
has any effect, including in 'showkey -s' or 'showkey -k'.

The right Super key works normally.


-- Package-specific info:
** Version:
Linux version 6.4.0-3-amd64 (debian-ker...@lists.debian.org) (gcc-13
(Debian 13.2.0-2) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1
SMP PREEMPT_DYNAMIC Debian 6.4.11-1 (2023-08-17)

** Command line:
BOOT_IMAGE=/vmlinuz-6.4.0-3-amd64
root=UUID=f20a3c35-14b7-4b08-96ed-a4e4ded880ab ro quiet

** Not tainted

** Kernel log:
Unable to read kernel log; any relevant messages should be attached


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

Kernel: Linux 6.4.0-3-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, 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 linux-image-6.4.0-3-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.142
ii  kmod30+20230519-1
ii  linux-base  4.9

Versions of packages linux-image-6.4.0-3-amd64 recommends:
ii  apparmor 3.0.12-1
ii  firmware-linux-free  20200122-2

Versions of packages linux-image-6.4.0-3-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.06-13
ii  linux-doc-6.4   6.4.11-1

Versions of packages linux-image-6.4.0-3-amd64 is related to:
ii  firmware-amd-graphics 20230515-3
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
ii  firmware-linux-nonfree20230515-3
ii  firmware-misc-nonfree 20230515-3
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
ii  firmware-realtek  20230515-3
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information

Bug#1050738: plocate: please add "9p" to PRUNEFS= (WSL2 support)

[Alexandre Detiste]

There's no cron/systemd by default in WSL2,
/init is a stub that talks to windows Kernel,
on can define an autoexec in /etc/wsl.conf but it's certainly not a
default setting;
latest releases of WSL2 add support for systemd which deeply intrigues me.

There are a lot of complaints that the 9p bridge is genuinely slow.

I don't have this computer, I'll check again when time permits.

Le lun. 28 août 2023 à 22:13, Steinar H. Gunderson  a écrit :
>
> On Mon, Aug 28, 2023 at 10:10:18PM +0200, Alexandre Detiste wrote:
> > It was like 1h then we cancelled with ^C.
>
> But normally it runs through cron/systemd, and then it should be fast the
> next few times?
>
> /* Steinar */

Bug#1050542: marked as done (bookworm-pu: package openbsd-inetd/0.20221205-2+deb12u1)

[Adam D. Barratt]

Control: reopen -1
Control: tags -1 + pending

On Mon, 2023-08-28 at 19:21 +, Debian Bug Tracking System wrote:
> Your message dated Mon, 28 Aug 2023 19:17:18 +
> with message-id 
> and subject line Bug#1050542: fixed in openbsd-inetd 0.20221205-
> 2~deb12u1
> has caused the Debian Bug report #1050542,
> regarding bookworm-pu: package openbsd-inetd/0.20221205-2+deb12u1
> to be marked as done.

Please don't close release.debian.org p-u bugs in uploads. The bug will
get closed (by us) once the updated package is in stable, i.e. after a
point release.

Regards,

Adam

Bug#1050738: plocate: please add "9p" to PRUNEFS= (WSL2 support)

[Alexandre Detiste]

It was like 1h then we cancelled with ^C.

Without 9p it's instantaneous/usable again.


Le lun. 28 août 2023 à 21:44, Steinar H. Gunderson  a écrit :
>
> On Mon, Aug 28, 2023 at 09:37:01PM +0200, Alexandre Detiste wrote:
> > Microsoft's "Windows Subsystem for Linux 2" emulator
> > is reusing the old/experimental '9p' filesystem
> > to mount the Windows filesystems inside then Debian container.
> >
> > This makes plocate takes forever to index local (/remote ?) files.
>
> Hi,
>
> What is “forever”? One would imagine that if the filesystem is mounted,
> it contains files that would also be useful to index? All the others that are
> ignored are either special filesystems that don't actually contain any
> “files” in the usual sense (e.g. procfs, cgroup2), or things that genuinely
> must be reached over the network (e.g. nfs, lustre, cifs). I don't see that
> the WSL host filesystem falls into any of those categories.

Bug#1050738: plocate: please add "9p" to PRUNEFS= (WSL2 support)

[Steinar H. Gunderson]

On Mon, Aug 28, 2023 at 10:10:18PM +0200, Alexandre Detiste wrote:
> It was like 1h then we cancelled with ^C.

But normally it runs through cron/systemd, and then it should be fast the
next few times?

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#964082: parsinsert fails it's tests when built with -O2 gcc-13

[Étienne Mollier]

Hi Andreas,

Andreas Tille, on 2023-08-28:
> Am Sun, Aug 27, 2023 at 11:26:32PM +0200 schrieb Étienne Mollier:
> > 
> >  -O1  -O2   -O3
> > -fPIE + no hardening  OK   OKOK
> > -fno-PIE + no hardening   OK  FAIL  FAIL
> > -fPIE + hardening OK  FAIL  FAIL
> > -fno-PIE + hardening  OK  FAIL  FAIL
> 
> Thanks a lot for creating this matrix.

The change even fixed LTO builds.  :)
On the other hand, well, the hardening is gone.  :(

The package looks to range on the performance critical side of
the spectrum, so this is probably an acceptable trade-off.  This
is probably symptomatic of a deeper problem in the source code
though, but I don't really expect to pinpoint the exact cause
without help from upstream.

> > I'm considering pushing an upload that goes in the direction of
> > disabling hardening and enforcing PIE in the upcoming week,
> > unless there are reasons to hold on, or someone is faster than
> > me in uploading.
> 
> I will probably be not faster than you.  Please make sure you document
> in d/rules that hardening breaks the tests.  This should avoid that
> someone later might simply switch on hardening since we usually do this.
> (may be same for salsa-ci.yaml when you switch of the CI test there.)

This is documented in d/rules.  I'll also add the necessary
lintian overrides and blhc markers to reduce the noise caused by
the change in automated checks.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/tty1, please excuse my verbosity
   `-on air: Orphaned Land - Fail


signature.asc
Description: PGP signature

Bug#1050738: plocate: please add "9p" to PRUNEFS= (WSL2 support)

[Steinar H. Gunderson]

On Mon, Aug 28, 2023 at 09:37:01PM +0200, Alexandre Detiste wrote:
> Microsoft's "Windows Subsystem for Linux 2" emulator
> is reusing the old/experimental '9p' filesystem
> to mount the Windows filesystems inside then Debian container.
> 
> This makes plocate takes forever to index local (/remote ?) files.

Hi,

What is “forever”? One would imagine that if the filesystem is mounted,
it contains files that would also be useful to index? All the others that are
ignored are either special filesystems that don't actually contain any
“files” in the usual sense (e.g. procfs, cgroup2), or things that genuinely
must be reached over the network (e.g. nfs, lustre, cifs). I don't see that
the WSL host filesystem falls into any of those categories.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#1041441: Bug#1018206: luatex loses or changes text when discretionaries with priorities are used

[Preuße]

On 23.07.2023 23:21, Preuße...@buxtehude.debian.org, Hilmar wrote:

On 19.07.2023 00:19, Preuße...@buxtehude.debian.org, Hilmar wrote:

Control: clone 1018206 -1
Control: reopen -1


Hi Peter,

Oh my gosh.  Losing formatting would indeed be not severe.  
Distorting contents is IS severe, especially if this goes unnoticed.  
Heaven knows how much text has already been and will be silently 
changed in all the years of Debian 12.  Therefore, a kind request: 
please push it into the next update of Debian (12.1) or at least one 
of the next updates.



Clone this bug to create a fix for bookworm.

I've uploaded the revision -8 to unstable, which is a prereq for having 
a fix in bookworm. I've uploaded packages for bookworm to here [1]. 
Would be nice if you could patch your system and test them. At least 
your example is solved.


Hilmar

[1] https://freeshell.de/~hille42/1041441/

>
Ping...

I intend to push the fix to next point release, but I need to make sure 
it solves the issue in question.


Hilmar


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1050592: perl: F_GETLK / F_GETLK64 confusion on ppc64el breaking libfile-fcntllock-perl

[Aurelien Jarno]

Hi Niko,

On 2023-08-27 14:43, Niko Tyni wrote:
> (full quote for the benefit of the Aurelien and other glibc maintainers)
> 
> On Sat, Aug 26, 2023 at 09:07:38PM +0300, Niko Tyni wrote:
> > Package: perl
> > Version: 5.36.0-8
> > Severity: serious
> > X-Debbugs-Cc: debian-powe...@lists.debian.org
> > Control: affects -1 libfile-fcntllock-perl
> > 
> > Hi,
> > 
> > debugging an unexpected autopkgtest failure of
> > libfile-fcntllock-perl_0.22-4+b1 with perl_5.36.0-8 on ppc64el [1] I found
> > it's because the old perl binary (5.36.0-7) was built with the fcntl(2)
> > constant F_GETLK == 12, but the new one with F_GETLK == 5 [2].
> > 
> > There are no source or build system changes in perl that would have caused
> > this change. The failure is currently blocking perl testing migration,
> > so filing at 'serious'.
> > 
> > Perl is built with -D_FILE_OFFSET_BITS=64, and I see that on bullseye
> > this causes F_GETLK == F_GETLK64 == 12, but on bookworm and later
> > F_GETLK == 5 while F_GETLK64 == 12 [3]. I didn't find the exact
> > change that caused this yet.
> > 
> > As can be expected from the above, building libfile-fcntllock-perl on
> > bookworm against perl_5.36.0-7 makes it fail its test suite in a similar
> > way. And rebuilding it on sid against perl_5.36.0-8 makes it pass.
> > 
> > On amd64 the constants have stayed equal (== 5) from bullseye to sid,
> > and _FILE_OFFSET_BITS=64 doesn't affect them. What's the deal on ppc64el?
> > 
> > Copying the powerpc porters list. Could you please look into this?
> > 
> > [1] 
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/libf/libfile-fcntllock-perl/34669085/log.gz
> > [2] perl -MPOSIX -E 'say F_GETLK'
> > [3] printf '#include \nF_GETLK\nF_GETLK64\n' | cpp 
> > -D_FILE_OFFSET_BITS=64 | tail -2

Thanks for the details and the investigation.

> I think the relevant change here is this in libc6-dev_2.36-9+deb12u1 for 
> bookworm:
> 
> --- libc6-dev_2.36-9/usr/include/powerpc64le-linux-gnu/bits/fcntl.h 
> 2023-04-10 09:35:16.0 +0100
> +++ libc6-dev_2.36-9+deb12u1/usr/include/powerpc64le-linux-gnu/bits/fcntl.h   
>   2023-07-13 19:07:47.0 +0100
> @@ -33,6 +33,12 @@
>  # define __O_LARGEFILE 020
>  #endif
>  
> +#if __WORDSIZE == 64
> +# define F_GETLK   5
> +# define F_SETLK   6
> +# define F_SETLKW  7
> +#endif
> +

Indeed you are correct that the issue has been introduced by this patch.
It fixes the case *without* -D_FILE_OFFSET_BITS=64, but OTOH breaks the
case *with* it.

> and a similar one in 2.37-2 for trixie/sid.
> 
> The applicable changelog entry is presumably
> 
>[ Aurelien Jarno ]
>* debian/patches/git-updates.diff: update from upstream stable branch:
>  [...]
>  - Not affecting bookworm release architectures:
>- Fix LFS POSIX lock constants for powerpc64.
> 
> Aurelien, it seems that there's an oversight as ppc64el is a release 
> architecture?

Yes, sorry about that. When reading the changelog and the diff, I
thought it was only for powerpc64, as ppc64el has a different ABI, but I
was wrong.

> I can see that this changed for the better, but what should I do with the 
> above
> breakage? Rebuild perl and libfcntl-fcntllock-perl and declare some Breaks?
> Do we want to do that for stable too?

I think it's an ABI breakage that should be fixed, but just reverting
the patch will break the case without -D_FILE_OFFSET_BITS=64. I'll check
with upstream and try to get the issue fixed in both testing/sid and
stable. I'll keep you updated. In the meantime feel free to reassign the
bug to the glibc.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1050740: python-pyramid: CVE-2023-40587

[Salvatore Bonaccorso]

Source: python-pyramid
Version: 2.0+dfsg-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-pyramid.

CVE-2023-40587[0]:
| Pyramid is an open source Python web framework. A path traversal
| vulnerability in Pyramid versions 2.0.0 and 2.0.1 impacts users of
| Python 3.11 that are using a Pyramid static view with a full
| filesystem path and have a `index.html` file that is located exactly
| one directory above the location of the static view's file system
| path. No further path traversal exists, and the only file that could
| be disclosed accidentally is `index.html`. Pyramid version 2.0.2
| rejects any path that contains a null-byte out of caution. While
| valid in directory/file names, we would strongly consider it a
| mistake to use null-bytes in naming files/directories. Secondly,
| Python 3.11, and 3.12 has fixed the underlying issue in
| `os.path.normpath` to no longer truncate on the first `0x00` found,
| returning the behavior to pre-3.11 Python, un an as of yet
| unreleased version. Fixes will be available in:Python 3.12.0rc2 and
| 3.11.5. Some workarounds are available. Use a version of Python 3
| that is not affected, downgrade to Python 3.10 series temporarily,
| or wait until Python 3.11.5 is released and upgrade to the latest
| version of Python 3.11 series.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-40587
https://www.cve.org/CVERecord?id=CVE-2023-40587
[1] https://github.com/Pylons/pyramid/security/advisories/GHSA-j8g2-6fc7-q8f8
[2] 
https://github.com/Pylons/pyramid/commit/347d7750da6f45c7436dd0c31468885cc9343c85
 

Regards,
Salvatore

Bug#1050739: nodejs: CVE-2023-32002 CVE-2023-32006 CVE-2023-32559

[Salvatore Bonaccorso]

Source: nodejs
Version: 18.13.0+dfsg1-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerabilities were published for nodejs.

CVE-2023-32002[0]:
| The use of `Module._load()` can bypass the policy mechanism and
| require modules outside of the policy.json definition for a given
| module.  This vulnerability affects all users using the experimental
| policy mechanism in all active release lines: 16.x, 18.x and, 20.x.
| Please note that at the time this CVE was issued, the policy is an
| experimental feature of Node.js.


CVE-2023-32006[1]:
| The use of `module.constructor.createRequire()` can bypass the
| policy mechanism and require modules outside of the policy.json
| definition for a given module.  This vulnerability affects all users
| using the experimental policy mechanism in all active release lines:
| 16.x, 18.x, and, 20.x.  Please note that at the time this CVE was
| issued, the policy is an experimental feature of Node.js.


CVE-2023-32559[2]:
| A privilege escalation vulnerability exists in the experimental
| policy mechanism in all active release lines: 16.x, 18.x and, 20.x.
| The use of the deprecated API `process.binding()` can bypass the
| policy mechanism by requiring internal modules and eventually take
| advantage of `process.binding('spawn_sync')` run arbitrary code,
| outside of the limits defined in a `policy.json` file. Please note
| that at the time this CVE was issued, the policy is an experimental
| feature of Node.js.


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-32002
https://www.cve.org/CVERecord?id=CVE-2023-32002
[1] https://security-tracker.debian.org/tracker/CVE-2023-32006
https://www.cve.org/CVERecord?id=CVE-2023-32006
[2] https://security-tracker.debian.org/tracker/CVE-2023-32559
https://www.cve.org/CVERecord?id=CVE-2023-32559

Regards,
Salvatore

Bug#1050738: plocate: please add "9p" to PRUNEFS= (WSL2 support)

[Alexandre Detiste]

Package: plocate
Version: 1.1.19-2
Severity: wishlist

Hi,

Microsoft's "Windows Subsystem for Linux 2" emulator
is reusing the old/experimental '9p' filesystem
to mount the Windows filesystems inside then Debian container.

This makes plocate takes forever to index local (/remote ?) files.

Can you please add '9p' to the exclusion list ?

Greetings,

https://www.reddit.com/media?url=https%3A%2F%2Fi.redd.it%2Fpo98dksksjx21.png

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

Kernel: Linux 6.4.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages plocate depends on:
ii  adduser 3.137
ii  libc6   2.37-7
ii  libgcc-s1   13.2.0-2
ii  libstdc++6  13.2.0-2
ii  liburing2   2.4-1
ii  libzstd11.5.5+dfsg2-1

plocate recommends no packages.

Versions of packages plocate suggests:
ii  powermgmt-base  1.37
ii  systemd-sysv254.1-2

-- no debconf information

Bug#1050672: granite-7: FTBFS: error: Argument 1: Cannot convert from `unowned uint8[]' to `unowned string'

[Boyuan Yang]

Control: reassign -1 vala
Control: found -1 0.56.12-1
Control: affects -1 source:granite-7
Control: retitle -1 vala: Regression: Gtk.CssProvider.load_from_data has 
breaking change of VAPI signature in 0.56.11 / main
Control: forwarded -1 https://gitlab.gnome.org/GNOME/vala/-/issues/1478
Control: tags -1 fixed-upstream patch
X-Debbugs-CC: ric...@ubuntu.com

在 2023-08-27星期日的 22:57 +0200，Aurelien Jarno写道：
> Source: granite-7
> Version: 7.3.0-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> 
> Dear maintainer,
> 
> granite-7 fails to build from source. From my build log on amd64:
> 
> > valac -C --define=LINUX --abi-stability --hide-internal --target-glib=2.50 
> > --pkg posix --pkg gtk4 --pkg gobject-2.0 --target-glib 2.50 --pkg glib-2.0 
> > --pkg gio-unix-2.0 --
> > pkg gio-2.0 --pkg gee-0.8 --color=always --directory 
> > lib/libgranite-7.so.7.3.0.p --basedir ../lib --library granite-7 --header 
> > lib/granite-7.h --vapi ../granite-7.vapi --
> > gir ../Granite-7.0.gir --gresources=../lib/Styles/styles.gresource.xml 
> > ../lib/DateTime.vala ../lib/Constants.vala ../lib/Init.vala 
> > ../lib/Services/Application.vala
> > ../lib/Services/AsyncMutex.vala ../lib/Services/ContractorProxy.vala 
> > ../lib/Services/Portal.vala ../lib/Services/Settings.vala 
> > ../lib/Services/System.vala
> > ../lib/Widgets/AbstractSettingsPage.vala 
> > ../lib/Widgets/AbstractSimpleSettingsPage.vala 
> > ../lib/Widgets/AccelLabel.vala ../lib/Widgets/DatePicker.vala
> > ../lib/Widgets/Dialog.vala ../lib/Widgets/HeaderLabel.vala 
> > ../lib/Widgets/HyperTextView.vala ../lib/Widgets/MessageDialog.vala 
> > ../lib/Widgets/ModeSwitch.vala
> > ../lib/Widgets/OverlayBar.vala ../lib/Widgets/Placeholder.vala 
> > ../lib/Widgets/SettingsSidebarRow.vala ../lib/Widgets/SettingsSidebar.vala 
> > ../lib/Widgets/Settings.vala
> > ../lib/Widgets/SwitchModelButton.vala ../lib/Widgets/TimePicker.vala 
> > ../lib/Widgets/Toast.vala ../lib/Widgets/Utils.vala 
> > ../lib/Widgets/ValidatedEntry.vala lib/Config.vala
> > ../lib/Init.vala:53.9-53.24: warning: `Gtk.StyleContext' has been 
> > deprecated since 4.10
> >    53 | Gtk.StyleContext.add_provider_for_display (display, 
> > base_provider, Gtk.STYLE_PROVIDER_PRIORITY_THEME);
> >   | ^~~~
> >   
> > ../lib/Init.vala:56.13-56.28: warning: `Gtk.StyleContext' has been 
> > deprecated since 4.10
> >    56 | Gtk.StyleContext.add_provider_for_display (display, 
> > app_provider, Gtk.STYLE_PROVIDER_PRIORITY_APPLICATION);
> >   | ^~~~
> >    
> > ../lib/Widgets/AccelLabel.vala:110.43-110.71: warning: 
> > `Gtk.Widget.get_style_context' has been deprecated since 4.10
> >   110 | var accel_label_context = 
> > accel_label.get_style_context ();
> >   |   
> > ^    
> > ../lib/Widgets/AccelLabel.vala:110.21-110.39: warning: `Gtk.StyleContext' 
> > has been deprecated since 4.10
> >   110 | var accel_label_context = 
> > accel_label.get_style_context ();
> >   | ^~~ 
> >    
> > ../lib/Widgets/HyperTextView.vala:252.9-252.20: warning: `Gtk.show_uri' has 
> > been deprecated since 4.10
> >   252 | Gtk.show_uri (null, uri, Gdk.CURRENT_TIME);
> >   | ^~~~   
> > ../lib/Widgets/ModeSwitch.vala:91.9-91.37: warning: 
> > `Gtk.Widget.get_style_context' has been deprecated since 4.10
> >    91 | mode_switch.get_style_context ().add_class 
> > (Granite.STYLE_CLASS_MODE_SWITCH);
> >   | ^   
> >  
> > ../lib/Widgets/SettingsSidebarRow.vala:83.9-83.37: warning: 
> > `Gtk.Widget.get_style_context' has been deprecated since 4.10
> >    83 | title_label.get_style_context ().add_class 
> > (Granite.STYLE_CLASS_H3_LABEL);
> >   | ^   
> >   
> > ../lib/Widgets/SettingsSidebar.vala:95.17-95.39: warning: 
> > `Gtk.Widget.get_style_context' has been deprecated since 4.10
> >    95 | label.get_style_context ().add_class 
> > (Granite.STYLE_CLASS_H4_LABEL);
> >   | ^~~ 
> >     
> > ../lib/Widgets/SwitchModelButton.vala:53.49-53.83: warning: 
> > `Gtk.Widget.get_style_context' has been deprecated since 4.10
> >    53 | unowned var description_style_context = 
> > description_label.get_style_context ();
> >   | 
> > ^~~    
> > 

Bug#1050737: xfce4-panel: Auto hide broken after closing application

[tj68792]

Package: xfce4-panel
Version: 4.18.2-1
Severity: normal

Dear Maintainer,

the auto hide feautre from xfce panel at my debian bookworm installation 
doesn't work anymore after closing an application by middle click on the 
window button plugin. It's reproducable for me this way:


1. Configure a xfce panel using "auto hide always"
2. Add plugin "window buttons" to the panel and enable: a. group windows 
by application and b, close Window as middle click action

3. Open more then one Window of an application (e.g. 3 thunar windows)
4. On the xfce panel close one thunar window from the window group by 
click the middle mouse button
5. Now the auto hide doens't work anymore at my system. The panel always 
stays visible (until e.g. I disable the goruping function and reanable it)


I excepted that closing application by clicking middle mouse button 
wouldn't break the panels auto hide feature.


I hope you'll be able to reproduce this problem because its a bit annoying.

Best regards

Timo


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

Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-11-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE 
not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xfce4-panel depends on:
ii  exo-utils4.18.0-1
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9+deb12u1
ii  libcairo21.16.0-7
ii  libdbusmenu-gtk3-4   18.10.20180917~bzr492+repack1-3
ii  libexo-2-0   4.18.0-1
ii  libgarcon-1-04.18.0-1
ii  libgarcon-gtk3-1-0   4.18.0-1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libglib2.0-0 2.74.6-2
ii  libgtk-3-0   3.24.37-2
ii  libpango-1.0-0   1.50.12+ds-1
ii  libpangocairo-1.0-0  1.50.12+ds-1
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.4-2+deb12u1
ii  libxext6 2:1.3.4-1+b1
ii  libxfce4panel-2.0-4  4.18.2-1
ii  libxfce4ui-2-0   4.18.2-2
ii  libxfce4util74.18.1-2
ii  libxfconf-0-34.18.0-2

xfce4-panel recommends no packages.

xfce4-panel suggests no packages.

-- no debconf information

Bug#1050736: O: zemberek-ooo -- Turkish spell checker extension for LibreOffice

[Bastian Germann]

Package: wnpp

zemberek-ooo is obviously not maintained anymore. I am hereby orphaning it.
Please only consider adopting if you can afford the time and have the
skills to maintain it.

Description: Turkish spell checker extension for LibreOffice
 Zemberek is an open source, platform independent, general purpose Natural
 Language Processing library and toolset designed for Turkic languages,
 especially Turkish.
 This package contains Turkish spell checker extension for LibreOffice.

Bug#1050735: RM: python-defer -- RoQA; unmaintained; RC-buggy

[Bastian Germann]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 + src:python-defer

Please remove python-defer. It is unmaintained both upstream and in Debian.
The package is RC-buggy, which made it miss bookworm.

Bug#1038463: cegui-mk2: Is this library still useful to have in Debian?

[Olek Wojnar]

Update: Upstream has agreed to release a new version which should 
address the issues of the aging codebase. Therefore, my current 
inclination is to continue to provide this package.


I'll keep this bug open for now in case anyone else would like to weigh 
in with opinions.


-Olek

Bug#1050542: openbsd-inetd 0.20221205-2~deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1050542 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: openbsd-inetd
Version: 0.20221205-2~deb12u1

Explanation: fix memory handling issues

Bug#1050334: reprepro 5.3.1-1+deb12u1 flagged for acceptance

[Jonathan Wiltshire]

package release.debian.org
tags 1050334 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: reprepro
Version: 5.3.1-1+deb12u1

Explanation: fix race condition when using external decompressors

Bug#1050733: nautilus: tracker build test failure

[Jeremy Bícha]

Source: nautilus
Version: 45~beta-1
Severity: serious
Tags: ftbfs sid

One of the nautilus build tests is failing. I was unable to reproduce
this issue in my local sbuild or in a porterbox. The test also passes
on Ubuntu. I'm filing this bug because it is difficult for me to
figure out a fix without being able to reproduce the issue.

This is a "displayless" test so it's not using GTK

Build log excerpt
--

test: test-nautilus-search-engine-tracker
start time:   12:30:17
duration: 1.22s
result:   (exit status 134 or signal 6 SIGABRT)
command:  G_TEST_SRCDIR='/<>/test/automated/displayless'
RUNNING_TESTS=TRUE
G_TEST_BUILDDIR='/<>/obj-x86_64-linux-gnu/test/automated/displayless'
GSETTINGS_SCHEMA_DIR='/<>/obj-x86_64-linux-gnu/data'
LD_LIBRARY_PATH='/<>/obj-x86_64-linux-gnu/libnautilus-extension'
MALLOC_PERTURB_=69
/usr/lib/x86_64-linux-gnu/tracker-3.0/trackertestutils/tracker-sandbox
--store-tmpdir --index-recursive-tmpdir
test/automated/displayless/test-nautilus-search-engine-tracker
--- stdout ---

Nautilus search engine tracker finished!
Bail out! 
ERROR:../test/automated/displayless/test-nautilus-search-engine-tracker.c
:185:main: assertion failed (total_hits == 1): (0 == 1)
--- stderr ---
** (process:1614914): Message: 12:30:17.919: Starting
 org.freedesktop.Tracker3.Miner.Files
(tracker-miner-fs-3:1614920): Tracker-WARNING **:
 Locale 'LANG' is not set, defaulting to C locale
(tracker-miner-fs-3:1614920): libupower-glib-WARNING **:
 Couldn't connect to proxy: Could not connect: No such file or directory
(tracker-miner-fs-3:1614920): Tracker-WARNING **: Unable to connect to UPower
**
ERROR:../test/automated/displayless/test-nautilus-search-engine-tracker.c:
185:main: assertion failed (total_hits == 1): (0 == 1)
Aborted
(tracker-extract-3:1614930): Tracker-CRITICAL **:
 Could not connect to filesystem miner endpoint:
Message recipient disconnected from message bus without replying


Thank you,
Jeremy Bícha

Bug#1031989: python-iowait: Bzr repo does not exist anymore

[Bastian Germann]

I am uploading a NMU to fix this.diff -Nru python-iowait-0.1/debian/changelog python-iowait-0.1/debian/changelog
--- python-iowait-0.1/debian/changelog  2019-12-22 21:15:00.0 +0100
+++ python-iowait-0.1/debian/changelog  2023-08-28 20:40:57.0 +0200
@@ -1,3 +1,11 @@
+python-iowait (0.1-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop non-existing Vcs repo; Closes: #1031989
+  * Drop obsolete XB-Python3-Version.
+
+ -- Bastian Germann   Mon, 28 Aug 2023 20:40:57 +0200
+
 python-iowait (0.1-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru python-iowait-0.1/debian/control python-iowait-0.1/debian/control
--- python-iowait-0.1/debian/control2019-12-22 21:15:00.0 +0100
+++ python-iowait-0.1/debian/control2023-08-28 20:40:57.0 +0200
@@ -6,14 +6,11 @@
 Build-Depends-Indep: python3-all (>= 3.1.2-1~)
 Standards-Version: 3.9.1
 Homepage: https://launchpad.net/python-iowait
-Vcs-Bzr: http://bazaar.launchpad.net/+branch/python-iowait/0.1
-Vcs-Browser: http://bazaar.launchpad.net/+branch/python-iowait/0.1/files
 
 Package: python3-iowait
 Architecture: all
 Depends: ${misc:Depends}, ${python3:Depends}
 Breaks: ${python3:Breaks}
-XB-Python3-Version: ${python3:Versions}
 Description: Platform-independent module for I/O completion events
  Different operating systems provide different ways to wait for I/O completion
  events: there's select(), poll(), epoll() and kqueue(). For cross-platform

Bug#1050718: logrotate without copytruncate is nicer to aide

[Holger Levsen]

Hi Marc, 

thanks for your bug report with patch! I just have one question:

On Mon, Aug 28, 2023 at 04:27:36PM +0200, Marc Haber wrote:
> Please consider applying this in Debian's munin-node package. If you
> choose to not do this (which I would fully understand, I know that I am
> asking a lot), [...]

why do you think you are asking *a lot*? Because of the restarting? or?


-- 
cheers,
Holger

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

Some of my friends and I overcommit to things, so we made "Saying No to Things"
punch cards. If you say no to 10 things, your friends have to buy you an ice
cream. In a pilot study, we found participants both said no to more things and
got more free ice cream. (@leah_pierson)


signature.asc
Description: PGP signature

Bug#1050679: golang-github-twstrike-gotk3adapter: Unnecessary build dependency libgio-cil

[Shengjing Zhu]

On Tue, Aug 29, 2023 at 1:12 AM Bastian Germann  wrote:
>
> Am 28.08.23 um 19:09 schrieb Shengjing Zhu:
> > Have you seen that this package is FTBFS
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997717
> >
> > I don't think NMU dropping libgio-cil makes sense at this point...
>
> It does, please see #1049372.

Well, the source package of
golang-github-twstrike-gotk3adapter/0.0~git20170505.0.901a95d+ds-3.1
is still in unstable if -3.2 is not built...
Looks more than a `dak rm` bug if it stops complaining. But ftp-master
can remove packages even if `dak rm` complains.
/shrug

-- 
Shengjing Zhu

Bug#1050709: tar-ignore debian/source/options

[Niels Thykier]

On Mon, 28 Aug 2023 13:53:22 +0100 Ian Jackson 
 wrote:

Package: dgit
Version: 11.3

debhelper (at least in sid) has a debian/source/options with;

  tar-ignore
  tar-ignore=debhelper/.idea

And it has a .gitignore.  This has the following effects:

 1. It defeats dgit's passing of a -I and -i options to dpkg-source,
so the dgit-generated source package does not contain .gitignore

 2. If one were to somehow manage to make a proper source package
that corresponds to the git tree, it wouldn't round trip
through dpkg-source.

So IMO there is no way to make a DFSG-compliant source package of
Debian's current debhelper package.

I was just assisting another DD contributor with this and other
problems; I was going to try to help sort out a mess by doing what
amounted to a sponsored upload.  However, this turned out to be
impossible.

I have done a non-dgit-based non-DFSG-compliant upload instead.

What should we do about this ?  Options (not mutually exclusive) could
include:

 * File a bug or MR against debhelper
 * Somehow ask that dpkg-source do something about this, but what ?
 * Have dgit detect this situation and at least explain it to the user
 * Have dgit generate a non-roundtrippable source package
   (probably very hard and also undesirable)

Ian.

[...]


Hi,

So this is a common pattern in my packages although it sometimes appears 
in d/s/local-options rather than d/s/options.


Basically, the issue is when you have something you want to have 
locally, not in git and also not in the archive.  In one my other 
packages, I have a "local" directory filled with local work items 
(including a full copy of the sudo deb package for testing purposes). 
Here the "local" directory is listed both in .gitignore and in 
"tar-ignore", because I do not want it in git nor in the archive when I 
do an upload.


To solve this, I add `tar-ignore=...` (for native packages) to 
debian/source/(local-)options.  However, if you add that option, you end 
up with the entire *.git* directory in the tarball.  To avoid that, I 
add the `tar-ignore` on its own to get the sane defaults back.


This then breaks dgit leading to this bug, which is kind of a catch-22 
if you want local specific things (IDE files or local prototype stuff) 
that you guarantee is excluded from git and dpkg-source automatically 
and also support dgit at the same time.


Best regards,
Niels

PS: Not sure if this problem is specific to native packages, which I 
happen to maintain a lot of (relative to other maintainers).


PPS: Another example is debputy/experimental. In there I also included 
some python related artefacts because the early drafts do not have a 
proper clean rule for all the "local only" tooling I use, such as python 
coverage.  The official builds do not use these things, so the clean 
rule should work fine, but I do not want a left over ".coverage" 
appearing in the source package as it is just cruft.

Bug#1050679: golang-github-twstrike-gotk3adapter: Unnecessary build dependency libgio-cil

[Bastian Germann]

Am 28.08.23 um 19:09 schrieb Shengjing Zhu:

Have you seen that this package is FTBFS
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997717

I don't think NMU dropping libgio-cil makes sense at this point...


It does, please see #1049372.

Bug#262224: syslog-ng: set PATH in startscript

[Georges Khaznadar]

Hello,

I adopted the cron package a few months ago, and want to fix as many bug
reports as possible. The current bug report is now quite twenty years
old, which means, in terms of computer science, about ten eternities ;)

As no consensus has been achieved for twenty years to decide whether
this a bu or a non-bug, and as sane workarounds do exist (make important
scripts independent of environment variants), I shall close this bug
now: I believe that it cannot be fixed by a single change in cron
package.

Of course, you can reopen it if necessary, but please be kind enough to
propose new arguments (I mean newer than the already discussed stuff)

Best regards,   Georges.

Loïc Minier a écrit :
> Steve Greenland  - Thu, Sep 23, 2004:
> 
> > It was discussed a few years ago, when init (or the kernel) changed
> > behaviour, and at the time, the consensus was that scripts like this are
> > responsible for having their PATH. It's been a while, though, and that
> > might have changed, but you might search the archives (sorry I don't
> > have a reference, it's been a while).
> 
>  Don't waste your time searching for this, you really have a lot of
>  better things to do!  :)
> 
>  I think I've already found the discussions[1].  Because they weren't
>  finished and did not result in inclusion in the Policy, I really ought
>  to move my behind and bring this up again in debian-policy, and this is
>  in preparation.
> 
> > /* ... (save me from /etc/cron.conf!) ... (vix, jan90) */
> 
>  Erf!
> 
> > The problem with making it configurable is that the admin might change
> > it, which means that package scripts can still not rely on it.
> 
>  Good point, but it is still useful when you're running scripts that are
>  making the assumption of a sane environment (as was the case of the
>  OP).  Some examples for such scripts are those written to be launched
>  from within "su" or from "dpkg".
> 
> > >  What would you think of a cron.cf, or something similar, serving as a
> > >  placeholder for configuration of the default PATH and the default PATH
> > >  for root?
> > Ech. If the policy crew decides that crond should set the path
> > differently for root, then the Right Thing To Do is pick it up from
> > login.defs, not create yet another place for things to be inconsistent.
> 
>  Ooch, I misunderstood the meaning of ENV_SUPATH to something related to
>  "su" since I found that in the su(1) manpage.  Of course, the values of
>  login.defs should be used, you're right.
> 
>  Thanks for your time.
> 
> [1] If you meant:
>  
>  which started in dd:
>  
> -- 
> Loïc Minier 
> 

-- 
Georges KHAZNADAR et Jocelyne FOURNIER
22 rue des mouettes, 59240 Dunkerque France.
Téléphone +33 (0)3 28 29 17 70



signature.asc
Description: PGP signature

Bug#1050679: golang-github-twstrike-gotk3adapter: Unnecessary build dependency libgio-cil

[Shengjing Zhu]

On Mon, Aug 28, 2023 at 7:00 AM Bastian Germann  wrote:
>
> Source: golang-github-twstrike-gotk3adapter
> Severity: minor
> Version: 0.0~git20170505.0.901a95d+ds-3.1
>
> libgio-cil is a C# library and not even its development package.
> There is no reason to have this in a go package so please drop it.
>

Have you seen that this package is FTBFS
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997717

I don't think NMU dropping libgio-cil makes sense at this point...

Bug#1050731: libmutter-12-0: gnome-shell libmutter-12 segfault

[gozdek]

Package: libmutter-12-0
Version: 44.3-7
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

Step to reproduce:
Gnome-shell: Alt-F2, type 'r' or open Firefox/Chrome browser and play
any video for example from youtube.

all gnome-shell extensions are disabled

>From kernel log:
200~2023-08-28T17:46:20.921037+02:00 stacjonarka kernel: [ 3498.554467]
gnome-shell[24802]: segfault at 28 ip 7fed6c6f5f14 sp
7ffc869e41a0 error 4 in
libmutter-clutter-12.so.0.0.0[7fed6c689000+8d000] likely on CPU 2 (core
2, socket 0)

I found similar problem:

https://gitlab.gnome.org/GNOME/mutter/-/issues/2977201


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

Kernel: Linux 6.4.0-3-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=pl_PL.utf8, LC_CTYPE=pl_PL.utf8 (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 libmutter-12-0 depends on:
ii  adwaita-icon-theme 43-1
ii  gsettings-desktop-schemas  44.0-2
ii  libatk1.0-02.49.90-5
ii  libc6  2.37-7
ii  libcairo-gobject2  1.16.0-7
ii  libcairo2  1.16.0-7
ii  libcanberra0   0.30-10
ii  libcolord2 1.4.6-2.2
ii  libdrm22.4.115-1
ii  libegl11.6.0-1
ii  libfontconfig1 2.14.2-4
ii  libfribidi01.0.13-3
ii  libgbm123.1.6-1
ii  libgdk-pixbuf-2.0-02.42.10+dfsg-1+b1
ii  libgl1 1.6.0-1
ii  libglib2.0-0   2.77.2-1
ii  libgnome-desktop-4-2   44.0-2
ii  libgraphene-1.0-0  1.10.8-1
ii  libgudev-1.0-0 237-2
ii  libharfbuzz0b  8.0.1-1
ii  libice62:1.0.10-1
ii  libinput10 1.23.0-2
ii  libjson-glib-1.0-0 1.6.6-1
ii  liblcms2-2 2.14-2
ii  libpango-1.0-0 1.51.0+ds-2
ii  libpangocairo-1.0-01.51.0+ds-2
ii  libpangoft2-1.0-0  1.51.0+ds-2
ii  libpipewire-0.3-0  0.3.78-1
ii  libsm6 2:1.2.3-1
ii  libstartup-notification0   0.12-6+b1
ii  libsystemd0254.1-2
ii  libudev1   254.1-2
ii  libwacom9  2.7.0-1
ii  libwayland-server0 1.22.0-2
ii  libx11-6   2:1.8.6-1
ii  libx11-xcb12:1.8.6-1
ii  libxau61:1.0.9-1
ii  libxcb-randr0  1.15-1
ii  libxcb-res01.15-1
ii  libxcb11.15-1
ii  libxcomposite1 1:0.4.5-1
ii  libxcursor11:1.2.1-1
ii  libxdamage11:1.1.6-1
ii  libxext6   2:1.3.4-1+b1
ii  libxfixes3 1:6.0.0-2
ii  libxi6 2:1.8-1+b1
ii  libxinerama1   2:1.1.4-3
ii  libxkbcommon-x11-0 1.5.0-1
ii  libxkbcommon0  1.5.0-1
ii  libxkbfile11:1.1.0-1
ii  libxrandr2 2:1.5.2-2+b1
ii  libxtst6   2:1.2.3-1.1
ii  mutter-common  44.3-7
ii  mutter-common-bin  44.3-7

libmutter-12-0 recommends no packages.

libmutter-12-0 suggests no packages.

Versions of packages libmutter-12-0 is related to:
ii  libegl-mesa0 [libegl-vendor]  23.1.6-1
ii  libgl1-mesa-dri   23.1.6-1
ii  libglx-mesa0 [libglx-vendor]  23.1.6-1

-- no debconf information

Bug#460070: - cron: Using day-of-month and day-of-week together doesn't work as expected

[Georges Khaznadar]

Hello Ángel,
thank you for reviving this old bug report, with new ideas.

I adopted the cron package a few months ago, and I would like to reduce
the number of open bugs, in order to gain visibility for future bug
reports to come.

The bug report about the oddities of "day-of-month and day-of-week
together" has been raised fifteen years ago, and no consensus has been
achieved about it. Christian Kastner, the previous maintainer, tagged
this bug wontfix, with severity wishlist, thirty years ago.

I believe that sysadmins should adopt sane methods, like the method
documented in the manpage crontab.5: using the command `date` which is
rather powerful to tackle such particular expressions combining
day-of-month and day-of-week, even in subtle combinations. 

Here is an excerpt of the manpage which can be considered:

   #Execute early the next morning following the first
   #Thursday of each month
   57 2 * * 5 case $(date +d) in 0[2-8]) echo "After 1st Thursday"; esac

If you do not mind, I shall close this bug report in a few weeks. Please
feel free to repoen it when necessary.

Best regards,   Georges.

Ángel a écrit :
> The above patch by Mr. Feliz changed the semantics of crontab by making
> cron AND the dom and dow fields instead of the default OR-when-not-
> star. This would be more consistent overall, but that ship has sailed
> decades ago.
> 
> Interestingly, the cron on early versions of UNIX [1] doesn't seem to
> have that behavior but the "normal" one (it might have been a bug in
> the scheduling). Although some time later it got clearly spelled on
> SUSv2 [2] (probably on v1 as well), and Vixie even defines it as a
> "bizarre" but "it's the standard".
> 
> With the odd behavior set in stone, using day-of-month and day-of-week
> together (which would be useful, as already shown on this bug) requires
> using a syntax which doesn't conflict with the previous one (that SHALL
> keep working as-is).
> 
> The attached patch allows adding an optional '&&' token (surrounded by
> whitespace) before the day of week field to mark that the day of week
> of this line must match *in addition* to the day of month field. Since
> it's a per-entry marker, lines ANDing the fields and ORing the fields
> can be freely mixed in the same file. As a counterpart to &&, a '||'
> token is also recognised at the same place although it's a no-op merely
> for presentation purposes, since it "selects" the default behavior
> (marking entries with dom and dow can be useful as an explicit reminder
> of the dow gotcha).
> 
> The original crontab would look like this
>   21 11   5-15 * && Thuecho test1
>   21 11   5-15 * && Friecho test2
> 
> which is much nicer than the date tests embedded in the command
> 
> 
> The patch is also available at
> https://salsa.debian.org/Angel-guest/cron/-/tree/bug460070
> 
> Regards
> 
> 
> [1]
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=SysIII/usr/src/cmd/cron.c
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=V6/usr/man/man8/cron.8
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/cmd/cron.c
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/man/man8/cron.8
> https://minnie.tuhs.org/cgi-bin/utree.pl?file=2.9BSD/usr/src/cmd/cron.c
> 
> [2] - https://pubs.opengroup.org/onlinepubs/7908799/xcu/crontab.html

> Description: Allow using day-of-month and day-of-week together
>  by prepending a `&&' token (surrounded by whitespace) to the
>  dow field in order to take into account both dom and dow, from
>  the standardised default of matching either of them.
>  .
>  For symmetry, an `||' is also allowed at the same place, useful
>  mainly to serve as a reminder of this unintuitive behavior.
> Bug-Debian: https://bugs.debian.org/460070
> Last-Update: 2023-01-02
> Index: cron/cron.c
> ===
> --- cron.orig/cron.c
> +++ cron/cron.c
> @@ -336,6 +336,8 @@ find_jobs(vtime, db, doWild, doNonWild)
>* on Sundays;  '* * 1,15 * *' will run *only* the 1st and 15th.  this
>* is why we keep 'e->dow_star' and 'e->dom_star'.  yes, it's bizarre.
>* like many bizarre things, it's the standard.
> +  * We add as an extension the syntax '* * 1,15 * && Sun' to run only
> +  * on the 1st and 15th that are Sundays.
>*/
>   for (u = db->head;  u != NULL;  u = u->next) {
>   for (e = u->crontab;  e != NULL;  e = e->next) {
> @@ -345,7 +347,7 @@ find_jobs(vtime, db, doWild, doNonWild)
>   if (bit_test(e->minute, minute) &&
>   bit_test(e->hour, hour) &&
>   bit_test(e->month, month) &&
> - ( ((e->flags & DOM_STAR) || (e->flags & DOW_STAR))
> + ( ((e->flags & DOM_STAR) || (e->flags & (DOW_STAR | 
> DOW_AND)))
> ? (bit_test(e->dow,dow) && bit_test(e->dom,dom))
> : (bit_test(e->dow,dow) || 
> 

Bug#1040172: mailman3: manage.py migrate not run on upgrade

[Alexander Barton]

Hi Wesley!

I’m hitting this as well, so thanks a lot for your report and solution!

Running …

# cd /usr/share/mailman3-web
# python3 manage.py migrate

… solved this for me as well.

Thanks!
Alex

Bug#1049872: FTBFS on multiple release architectures

[Andrius Merkys]

Hi,

On Wed, 16 Aug 2023 14:29:10 +0200 Emanuele Rocca  wrote:

asmjit does not build correctly on the following architectures:
armel, armhf, mips64el, mipsel, s390x.


Does this constitute an RC bug? If not, severity should be lowered.

Thanks,
Andrius

Bug#1050725: debianutils: installs broken symlinks on non-usrmerged systems

[Sven Joachim]

Control: tags -1 + patch

On 2023-08-28 17:31 +0200, Sven Joachim wrote:

> Package: debianutils
> Version: 5.9
>
> The following snippet from the postinst script cannot possibly be
> right, as it creates two broken symlinks on non-usrmerged systems:
>
> ,
> | usrmerge(){
> | for p in run-parts tmpfile; do
> | [ -e /usr/bin/$p ] || ln -s /bin/which /usr/bin/$p
> | done
> `
>
> Apart from the typo ("tmpfile" should be "tempfile"), the intention
> probably was to symlink /bin/$p to /usr/bin/$p, not the non-existent
> /bin/which.

Attached is a quick & dirty patch which fixes the problem for me, I have
tested the upgrade from 5.9 in an unmerged chroot.

Cheers,
   Sven

From e02afe8a760733f5ae0e9f7d1d851ef19139f97a Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Mon, 28 Aug 2023 18:22:45 +0200
Subject: [PATCH] Create correct symlinks on non-usrmerged systems

Remove the dangling symlinks created by the 5.9 postinst first, as
otherwise "ln -s /bin/runparts /usr/bin/runparts" would fail with
EEXIST.

Closes: #1050725
---
 debian/postinst | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/debian/postinst b/debian/postinst
index 1d9f317..15b227f 100755
--- a/debian/postinst
+++ b/debian/postinst
@@ -14,7 +14,10 @@ ua() {

 usrmerge(){
 	for p in run-parts tmpfile; do
-		[ -e /usr/bin/$p ] || ln -s /bin/which /usr/bin/$p
+		[ -e /usr/bin/$p ] || rm -f /usr/bin/$p
+	done
+	for p in run-parts tempfile; do
+		[ -e /usr/bin/$p ] || ln -s /bin/$p /usr/bin/$p
 	done
 	[ -e /usr/sbin/installkernel ] || \
 ln -s /sbin/installkernel /usr/sbin/installkernel
--
2.40.1

Bug#1050730: bookworm-pu: package cyrus-imapd/3.6.1-4+deb12u1

[Yadd]

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

[ Reason ]
I entered a patch some months ago in Bullseye to permits migration to
Cyrus-Imapd 3.6 (Bookworm): without this patch, mailboxes maybe
corrupted.
I added also a postinst check to refuse upgrades if previous  version
wasn't > 3.2.6-2+deb11u2. However, I did a mistake in this patch and
migrations are not blocked. So user that didn't follow Bullseye upgrades
are loosing their mailboxes during Bopokworm upgrades (see #1037346).

[ Impact ]
Data loose risk for users that didn't migrate from 3.2.6-2+deb11u2.

[ Risks ]
No risk here, it just fixes the major risk on upgrades

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

[ Changes ]
 * fix dpkg --compare-versions use
 * update doc to replace minimal 3.2.10 by 3.2.6-2+deb11u2

Cheers,
Yadd
diff --git a/debian/changelog b/debian/changelog
index a6d3c31a..56cfb114 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+cyrus-imapd (3.6.1-4+deb12u1) UNRELEASED; urgency=medium
+
+  * Doc: add patch to fix minimal version needed before upgrade
+(see #1037346)
+  * Fix postint version check (see #1037346)
+
+ -- Yadd   Sat, 26 Aug 2023 07:06:45 +0400
+
 cyrus-imapd (3.6.1-4) unstable; urgency=medium
 
   * Update copyright
diff --git a/debian/cyrus-common.postinst b/debian/cyrus-common.postinst
index 86eb6f0a..10a36946 100755
--- a/debian/cyrus-common.postinst
+++ b/debian/cyrus-common.postinst
@@ -60,7 +60,7 @@ upgradesieve () {
 case "$1" in
 configure)
# Refuse to update if previous version is lower than 3.2.6-2+deb11u2~
-   if [ -z "$1" ] || $(dpkg --compare-versions $1 lt '3.2.6-2+deb11u2~'); 
then
+   if [ -z "$2" ] || $(dpkg --compare-versions $2 lt '3.2.6-2+deb11u2~'); 
then
echo "You must update cyrus-imapd to at least version 
3.2.6-2+deb11u2~" >&2
echo "before updating it to version 3.6.x and run it, else your 
mailboxes" >&2
echo "may be corrupted" >&2
diff --git a/debian/patches/fix-upgrade-versions.patch 
b/debian/patches/fix-upgrade-versions.patch
new file mode 100644
index ..9d0bb2f9
--- /dev/null
+++ b/debian/patches/fix-upgrade-versions.patch
@@ -0,0 +1,37 @@
+Description: fix the minimal version needed to update
+Author: Yadd 
+Bug-Debian: https://bugs.debian.org/1037346
+Forwarded: not-needed
+Last-Update: 2023-07-19
+
+--- a/doc/html/_sources/imap/download/upgrade.rst.txt
 b/doc/html/_sources/imap/download/upgrade.rst.txt
+@@ -25,10 +25,9 @@
+ Versions to upgrade from
+ 
+ 
+-Before upgrading to 3.6, your deployment should be running either:
++Before upgrading to 3.6, your deployment should be running:
+ 
+-* 3.2.10 (or later), or
+-* 3.4.4 (or later)
++* 3.2.6-2+deb11u2 (or later)
+ 
+ If your existing deployment predates these releases, you should first upgrade
+ to one of these versions, let it run for a while, resolve any issues that
+--- a/doc/text/imap/download/upgrade.txt
 b/doc/text/imap/download/upgrade.txt
+@@ -59,11 +59,9 @@
+ Versions to upgrade from
+ 
+ 
+-Before upgrading to 3.6, your deployment should be running either:
++Before upgrading to 3.6, your deployment should be running:
+ 
+-* 3.2.10 (or later), or
+-
+-* 3.4.4 (or later)
++* 3.2.6-2+deb11u2 (or later)
+ 
+ If your existing deployment predates these releases, you should first
+ upgrade to one of these versions, let it run for a while, resolve any
diff --git a/debian/patches/series b/debian/patches/series
index b33e49ac..353fb72b 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -8,3 +8,4 @@
 0018-increase-test-timeout.patch
 #0019-propagate-XXFLAGS.patch
 0020_fix-cyr_cd-shebang.patch
+fix-upgrade-versions.patch
diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml
index 33c3a640..6a91c217 100644
--- a/debian/salsa-ci.yml
+++ b/debian/salsa-ci.yml
@@ -1,4 +1,7 @@
 ---
+variables:
+  RELEASE: 'bookworm'
+
 include:
   - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
   - 
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml

Bug#1050653: emacs: fix ftbfs(workaround) on riscv64

[Bo YU]

Hi!

On Mon, Aug 28, 2023 at 11:55 PM Sean Whitton  wrote:
>
> Hello,
>
> On Sun 27 Aug 2023 at 11:05pm +08, Bo YU wrote:
>
> > I'd suggest leaving the bug open for now to trace the issue to be fixed
> > from upstream even if you apply this patch.:)
>
> I'm not sure there's evidence of an upstream bug in Emacs.  Isn't the
> problem over in libgccjit?

hmm, sorry, here is the upstream i mean from libgccjit.

Before opening the reportbug, I first ask for help for emacs from
upstream and give
backed for there also.

https://lists.gnu.org/archive/html/emacs-devel/2023-08/msg01190.html

Sorry for the inaccurate expression！

BR,
Bo
>
> --
> Sean Whitton

Bug#1050729: gnome-terminal: shift-click in vim acts like page-down

[Marc Glisse]

Package: gnome-terminal
Version: 3.49.92-2
Severity: normal

Dear Maintainer,

I noticed a strange behavior today, that was not present in July. When I
run vim (gtk3 or basic) in a gnome terminal, if I keep SHIFT pressed and
left-click with the mouse, the behavior I get is the same as pressing
PageDown. I tried it with another account that has no .vimrc and got the
same issue. To compare, I have run vim in xterm and konsole and did not
have this weird behavior: shift+double-click selected a word as
expected.

I may be getting the PageDown behavior *in addition to* the normal
behavior. If I go to the end of the file so PageDown has no effect,
shift+double-click does select a word.

PageDown seems to be the expected behavior when rotating the wheel of
the mouse while pressing SHIFT, in case that matters.

I noticed the issue with the version of gnome-terminal in testing and
only upgraded it to experimental because reportbug asked me to check
that the bug was still present there (it is).

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

Kernel: Linux 6.4.0-3-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
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 gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.8-2
ii  dbus-x11 [dbus-session-bus]   1.14.8-2
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-4
ii  gnome-terminal-data   3.49.92-2
ii  gsettings-desktop-schemas 44.0-2
ii  libatk1.0-0   2.49.90-5
ii  libc6 2.37-7
ii  libgcc-s1 13.2.0-2
ii  libglib2.0-0  2.77.2-1
ii  libgtk-3-03.24.38-4
ii  libhandy-1-0  1.8.2-2
ii  libpango-1.0-01.51.0+ds-2
ii  libstdc++613.2.0-2
ii  libuuid1  2.39.2-1
ii  libvte-2.91-0 0.73.93-1
ii  libx11-6  2:1.8.6-1

Versions of packages gnome-terminal recommends:
ii  gvfs   1.51.90-1
ii  nautilus-extension-gnome-terminal  3.49.92-2
ii  yelp   42.2-1

gnome-terminal suggests no packages.

-- no debconf information

Bug#1050728: RFS: xmake/2.8.2+ds-1 [ITP] -- cross-platform build utility based on Lua

[Lin Qigang]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name : xmake
   Version  : 2.8.2+ds-1
   Upstream contact : ruki 
 * URL  : http://xmake.io
 * License  : GPL-2+, Apache-2, Expat
 * Vcs  : https://salsa.debian.org/xmake-team/xmake
   Section  : devel

The source builds the following binary packages:

  xmake - cross-platform build utility based on Lua
  xmake-data - Data for xmake

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/x/xmake/xmake_2.8.2+ds-1.dsc


Changes since the last upload:

 xmake (2.8.2+ds-1) unstable; urgency=medium
 .
   * Initial release (Closes: #986736).

Lance Lin
GPG Fingerprint: 4A31 DB5A 1EE4 096C 8739 9880 9036 4929 4C33 F9B7


OpenPGP_0x903649294C33F9B7.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1050668: python3: Fails to import/work with SSL module due to ImportError

[Stefano Rivera]

Hi Jonathan (2023.08.27_20:35:12_+)

Install python3.11 from debian unstable. The module was built with
3.11.5 and won't import with 3.11.4.

Dependencies *should* capture that, but I'm guessing we missed listing a
symbol in 3.11.5-1

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

Bug#1050653: emacs: fix ftbfs(workaround) on riscv64

[Sean Whitton]

Hello,

On Sun 27 Aug 2023 at 11:05pm +08, Bo YU wrote:

> I'd suggest leaving the bug open for now to trace the issue to be fixed
> from upstream even if you apply this patch.:)

I'm not sure there's evidence of an upstream bug in Emacs.  Isn't the
problem over in libgccjit?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1050498: pipewire-pulse systemd service not restarted despite dpkg upgrade of all pipewire packages

[Dylan Aïssi]

Hello Boud,

Le ven. 25 août 2023 à 13:09,  a écrit :
>
> * What outcome did you expect instead?
>
> What I expected was that the dpkg/apt system and/or the systemd system
> should have recognised that the old 'pipewire-pulse' process was invalid
> and should have forced it to restart with the 0.3.78-1 version.
>

I think the bug you are describing is a kind of duplicate of #1027136 [1]
filled against xdg-desktop-portal. So, I will quote the smcv's answer here [2]:

>> I think (the) xdg-desktop-portal user service(s) should be stopped before
>> removing the package. Is that possible?
>
> Not really: maintainer scripts happen in the context of the overall system
> (as root) and there is not really a good way to inject service-management
> commands into user sessions. Other per-user services like PulseAudio,
> Pipewire, gpg-agent and so on are not stopped when you remove them either.

Best regards,
Dylan

[1] https://bugs.debian.org/1027136
[2] https://bugs.debian.org/1027136#10

Bug#1050577: emacs: please limit number of native-compilation workers

[Sean Whitton]

Hello,

On Sat 26 Aug 2023 at 11:29am -03, David Bremner wrote:

> native-comp-async-jobs-number is a variable defined in ‘comp.el’.
>
> Its value is 0
>
> Default number of subprocesses used for async native compilation.
> Value of zero means to use half the number of the CPU’s execution units,
> or one if there’s just one execution unit.
>
> I think the upstream default is too aggressive, and we should set it
> to a smaller number to reduce the "fork bomb" like behaviour of
> spawning NUM_PHYSICAL_CORES worker processes for each user created
> emacs process. This particularly manifests itself if the user is
> running more than one emacs process. As an example, prior to patching
> the notmuch test suite, I got 200 native compilation processes on my
> desktop.
>
> Upstream may be correct that "one emacs process per machine" is the
> most common scenario, but the bad outcome of having the limit too
> small seems better than the bad outcome of having it too high.  People
> do use emacs in lots of other scenarios (e.g. servers and automated
> processes), and expecting them all to customize their emacs to avoid a
> performance / UX regression seems unkind.  AFAICT since the native
> compilation is asynchronous, there is no obvious pause by queuing the
> compilation jobs.

I would be in favour of patching in setting it to 1.  It's not a problem
for people to increase it, after all.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1050727: zlib: please make the build reproducible

[Chris Lamb]

Source: zlib
Version: 1:1.2.13.dfsg-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed that
zlib could not be built reproducibly.

This is because it embeds the absolute build path in the minizip and
miniunzip scripts.

A patch attached that uses sed to remove these, (although there might
be a cleaner way to inform autotools/libtool to not do this code
injection).

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2023-08-28 08:32:58.504515505 -0700
--- b/debian/rules  2023-08-28 08:44:42.749725457 -0700
@@ -131,6 +131,7 @@
$(MAKE)
 
$(MAKE) -C contrib/minizip minizip miniunzip
+   sed -i -e 's@LD_LIBRARY_PATH="/.*@@g' contrib/minizip/minizip 
contrib/minizip/miniunzip
 
-$(MAKE) test
 

Bug#1040690: emacsen-common analysis for cruft files from elpa-foo packages during apt upgrade

[Richard Lewis]

On Thu, 17 Aug 2023, 20:57 Nicholas D Steeves,  wrote:

> Richard Lewis wrote:
> > David Bremner wrote:
> > > Richard Lewis writes:
> > > > David Bremner wrote:
>
>

> > What happens in the 'apt upgrade' is:
> >
> > the old emacsen-common prerm is called (' upgrade
> > '):
>

> and at the end it _unlinks_:
> > /var/lib/emacsen-common/state/package/installed/emacsen-common
>
> @1
>
> > Then, apt prepares to unpack elpa-dash:
> >
> > The elpa-dash prerm (from bullseye) is called as:
> > /var/lib/dpkg/info/elpa-dash.prerm upgrade
> > 2.19.1+git20220608.1.0ac1ecf+dfsg-1)
> >
> > but this starts with:
> >
> > if [ -e /var/lib/emacsen-common/state/package/installed/emacsen-common -a
> > -x
> >   /usr/lib/emacsen-common/emacs-package-remove ] ; then
> > /usr/lib/emacsen-common/emacs-package-remove --prerm elpa-dash
> >
> > fi
> >
> > ... and so does nothing,
> > because /var/lib/emacsen-common/state/package/installed/emacsen-common is
> > gone.
>
> Oh!  It's a state-related bug!  I wonder if emacsen-common (old version)
> has been deinstalled at @1 (see above), or if the state is
> emacsen-common (new version) is unpacked, but unconfigured, and thus
> missing /var/lib/emacsen-common/state/package/installed/emacsen-common,
> which is presumably created as a last step during package configuration
> post-unpack?
>

the latter - new emacsen-common is present but in state 'unpacked' before
new dh-* is unpackaged



> In other words, elpa-dash (and other...most?..all? dh-elpa-using
> packages) upgrades depends on having emacsen-common fully installed and
> configured at @1.
>

this is  my understanding yes:  this is a feature/assumption made by the
current design but not enforced through package dependencies or code in apt



> I wonder if this can be solved in emacsen-common, or if it needs to be
> solved in dh-elpa and then all the dh-elpa-using packages rebuilt to
> generate new prerm scripts?  Which do you think would be the better
> approach?
>

I would guess the former is possible. but I think what is missing is clear
documentation of what features all the machinery with emacsen-common and
'flavors' and dh-elpa is trying to provide


( i suspect dpkg triggers should be the answer- should the question be
understood better --- eg it looks like jed does something similar with .sl
files, at least i think it does -- i didnt find any documentation on that
either)

Bug#1029170: ITP: golang-github-sigstore-sigstore -- Common go library shared across sigstore services and clients

[Leo Antunes]

Hi Reinhard,

absolutely no worries at all! Huge thanks on all your work and sorry for not 
being more responsive. I can only manage some "debian time" in between "real 
life" blocks, so a lot falls through the cracks :(

Cheers
Leo

--- Original Message ---
On Wednesday, July 19th, 2023 at 12:35, Reinhard Tartler  
wrote:

> Hi Leo,
>
> I hope you are well. Now that all dependencies to build this package are in 
> place, I've taken the liberty of uploading the package to debian/experimental 
> and pushed my sources to 
> https://salsa.debian.org/go-team/packages/golang-github-sigstore-sigstore
>
> I really don't want this to be seen as an ITP takeover, since we've been 
> talking on this ITP for a while, I hope that's okay. Please take a look at 
> this repo and at 
> https://ftp-master.debian.org/new/golang-github-sigstore-sigstore_1.4.0-1.html
>  and let me know what you think.
>
> Best,
> -rt
> --
>
> regards,
> Reinhard

Bug#1050700: pipewire-media-session: complains about nonexistent device

[Francesco Potortì]

>> Package: pipewire-media-session
>>
>> Two strange things in logs by pipewire-media-session.
>>
>> 1) format of log timestamp is not always the same
>>
>> 2) repeatedly complains about a missing default device
>>
>
>Thanks for your bug report, however pipewire-media-session is dead
>upstream [1] and was removed from debian a week ago [2]. Now, it is
>recommended to use wireplumber instead, which is a more sophisticated
>session manager for pipewire.

Wow.  Thanks for the info.

Should I just install wireplumber and everything should work?

-- 
Francesco Potortì (ricercatore)Mobile: +39.348.8283.107
ISTI - Area della ricerca CNR  Skype:  wnlabisti
via G. Moruzzi 1, I-56124 Pisa Web:http://fly.isti.cnr.it
(gate 20, 1st floor, room C71) ISPIN:  https://ieee-jispin.org/

Bug#1049411: chkrootkit: Possible Adore Worm in ansible

[Richard Lewis]

On Tue, 15 Aug 2023 at 12:51, Santiago Vila  wrote:

> On a Debian system with ansible and chkrootkit installed,
> chkrootkit warns that ansible has possibly the Adore Worm.

> WARNING: Possible Adore Worm installed:
>
/usr/lib/python3/dist-packages/ansible_collections/cyberark/conjur/dev/start.sh

The test from upstream simply flags any file under /usr/lib that is named
start.sh as a possible adore worm. This is a classic example of a false
positive -- ansible  seems to be the only package providing such a file, so
it is best to leave users to filter or change the report to ignore or hide
the message: see /usr/share/doc/chkrootkit/README.FALSE-POSITIVES.gz for
various ways to do this.

-- we can add this as an example to that file
-- one thing we could also do, is to have chkrootkit check if files are
from packages with 'dpkg -S'  which would give the user more information
about where files came from

Bug#1050700: pipewire-media-session: complains about nonexistent device

[Dylan Aïssi]

Le lun. 28 août 2023 à 17:31, Francesco Potortì  a écrit :
>
>
> Wow.  Thanks for the info.
>
> Should I just install wireplumber and everything should work?
>

Yes that should work after a reboot to be sure pipewire-media-session
doesn't run anymore.

For safety, you can install the meta package called "pipewire-audio", it depends
on a recommended set of pipewire packages for a standard audio use.

Dylan

Bug#1050726: pdsh: fix malformed changelog (and make the build reproducible)

[Chris Lamb]

Source: pdsh
Version: 2.34-1
Severity: important
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed that
pdsh could not be built reproducibly.

This is caused by a malformed debian/changelog entry which means that
a value for SOURCE_DATE_EPOCH cannot be extracted.

A patch is attached that sources this data from the upload.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/changelog  2023-08-28 08:26:57.384200795 -0700
--- b/debian/changelog  2023-08-28 08:30:23.124338954 -0700
@@ -1,8 +1,11 @@
 pdsh (2.34-1) unstable; urgency=medium
+
   * Add Portuguese-Brazilian translation thanks to Paulo Henrique de Lima
 Santana (Closes: #1028216)
   * Add Recommends on ssh-askpass (Closes: #788312)
 
+ -- Brian Pellin   Sat, 19 Aug 2023 21:51:47 +
+
 pdsh (2.34-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.

Bug#1050725: debianutils: installs broken symlinks on non-usrmerged systems

[Sven Joachim]

Package: debianutils
Version: 5.9

The following snippet from the postinst script cannot possibly be
right, as it creates two broken symlinks on non-usrmerged systems:

,
| usrmerge(){
|   for p in run-parts tmpfile; do
|   [ -e /usr/bin/$p ] || ln -s /bin/which /usr/bin/$p
|   done
`

Apart from the typo ("tmpfile" should be "tempfile"), the intention
probably was to symlink /bin/$p to /usr/bin/$p, not the non-existent
/bin/which.


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

Bug#1050700: pipewire-media-session: complains about nonexistent device

[Dylan Aïssi]

Hello Francesco,

Le lun. 28 août 2023 à 14:09, Francesco Potortì  a écrit :
>
> Package: pipewire-media-session
>
> Two strange things in logs by pipewire-media-session.
>
> 1) format of log timestamp is not always the same
>
> 2) repeatedly complains about a missing default device
>

Thanks for your bug report, however pipewire-media-session is dead
upstream [1] and was removed from debian a week ago [2]. Now, it is
recommended to use wireplumber instead, which is a more sophisticated
session manager for pipewire.

Best regards,
Dylan

[1] https://bugs.debian.org/1030765
[2] https://bugs.debian.org/1043405

Bug#1037930: sssd-pac.service fails to start after Debian 12 upgrade - upstream response

[Adam Cecile]

Hello,


Upstream provided a fix after contacting them using mailing list:

https://lists.fedorahosted.org/archives/list/sssd-us...@lists.fedorahosted.org/thread/HQKQOX53YJ2DUNPYPQ4LC7R56UXO2R3Z/#27FR2CRABDFJIVXRFZUXF5GHDKF7PGT7


They suggest default Debian configuration is incorrect and sssd section 
should have "implicit_pac_responder = false".



Best regards, Adam.

Bug#1043564: linux-image-6.1.0: Possibly same issue Intel Celeron N4000

[Carlos Christoffersen]

Package: src:linux
Version: 6.1.38-4
Followup-For: Bug #1043564

Dear Maintainer,

I believe this is the same issue reported before. When the display
should wake up, it completely hangs up the system.

The only workaround I know is to disable the screen saver.

The issue appeared after upgrading to bookworm (initially with kernel
6.1.0-9). The system was working OK with bullseye.

Thank you,


-- Package-specific info:
** Version:
Linux version 6.1.0-11-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.38-4 (2023-08-08)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-11-amd64 
root=UUID=6c31901f-ba47-4f46-bb71-53a0a3b21937 ro rootflags=subvol=@rootfs 
psmouse.elantech_smbus=0 zswap.enabled=1 resume=/dev/mapper/mmcblk0p3_crypt 
resume_offset=436772 quiet

** Not tainted

** Kernel log:

2023-08-27T09:16:54.692120-04:00 phobos kernel: [ 1218.355021] [ 
cut here ]
2023-08-27T09:16:54.692147-04:00 phobos kernel: [ 1218.355028] i915 
:00:02.0: Unexpected DBuf power power state (0x, expected 
0x0001)
2023-08-27T09:16:54.692151-04:00 phobos kernel: [ 1218.355116] WARNING: CPU: 1 
PID: 3640 at drivers/gpu/drm/i915/display/intel_display_power_well.c:950 
gen9_disable_dc_states+0x2ae/0x2c0 [i915]
2023-08-27T09:16:54.692153-04:00 phobos kernel: [ 1218.355254] Modules linked 
in: ctr ccm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device cmac qrtr 
algif_hash algif_skcipher af_alg bnep binfmt_misc nls_ascii nls_cp437 vfat fat 
snd_sof_pci_intel_apl snd_sof_intel_hda_common soundwire_intel 
soundwire_generic_allocation soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp snd_sof snd_sof_utils ext4 snd_hda_codec_hdmi soundwire_bus 
snd_soc_skl rtw88_8822be rtw88_8822b snd_soc_hdac_hda snd_ctl_led rtw88_pci 
rtw88_core btusb snd_hda_ext_core x86_pkg_temp_thermal snd_soc_sst_ipc 
intel_powerclamp btrtl btbcm coretemp snd_soc_sst_dsp btintel 
snd_soc_acpi_intel_match btmtk snd_soc_acpi snd_hda_codec_realtek mbcache 
bluetooth jbd2 snd_hda_codec_generic snd_soc_core mac80211 ledtrig_audio 
kvm_intel snd_compress snd_hda_intel libarc4 kvm snd_intel_dspcfg 
snd_intel_sdw_acpi snd_hda_codec jitterentropy_rng mei_hdcp intel_rapl_msr 
uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_hda_core 
irqbypass videobuf2_common videodev
2023-08-27T09:16:54.692159-04:00 phobos kernel: [ 1218.355324]  snd_hwdep rapl 
cfg80211 drbg wdat_wdt ansi_cprng mc snd_pcm intel_cstate mei_me watchdog 
pcspkr snd_timer processor_thermal_device_pci_legacy mei 
processor_thermal_device snd processor_thermal_rfim ecdh_generic wmi_bmof ecc 
processor_thermal_mbox crc16 processor_thermal_rapl rfkill soundcore 
intel_rapl_common intel_soc_dts_iosf int3403_thermal int3400_thermal 
intel_pmc_core acpi_thermal_rel int340x_thermal_zone ac sg evdev joydev 
serio_raw squashfs parport_pc ppdev lp parport loop efi_pstore fuse configfs 
efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq 
zstd_compress libcrc32c crc32c_generic sd_mod t10_pi crc64_rocksoft_generic 
crc64_rocksoft crc_t10dif crct10dif_generic crc64 dm_crypt dm_mod ums_realtek 
uas usb_storage scsi_mod scsi_common mmc_block i915 crct10dif_pclmul 
crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 
sha512_generic drm_buddy i2c_algo_bit drm_display_helper cec rc_core xhci_pci 
ttm xhci_hcd drm_kms_helper
2023-08-27T09:16:54.692161-04:00 phobos kernel: [ 1218.355404]  drm sdhci_pci 
aesni_intel usbcore cqhci sdhci crypto_simd i2c_i801 psmouse video cryptd 
mmc_core usb_common i2c_smbus battery wmi button
2023-08-27T09:16:54.692162-04:00 phobos kernel: [ 1218.355422] CPU: 1 PID: 3640 
Comm: Xorg Not tainted 6.1.0-11-amd64 #1  Debian 6.1.38-4
2023-08-27T09:16:54.692163-04:00 phobos kernel: [ 1218.355426] Hardware name: 
HP HP Stream Laptop 14-cb1XX/84FB, BIOS F.24 11/29/2022
2023-08-27T09:16:54.692163-04:00 phobos kernel: [ 1218.355428] RIP: 
0010:gen9_disable_dc_states+0x2ae/0x2c0 [i915]
2023-08-27T09:16:54.692164-04:00 phobos kernel: [ 1218.355535] Code: b6 e8 4c 
8b 6f 50 4d 85 ed 75 03 4c 8b 2f e8 89 3d e9 cb 45 89 e0 89 e9 4c 89 ea 48 89 
c6 48 c7 c7 f8 39 b4 c0 e8 42 23 85 cb <0f> 0b e9 f7 fd ff ff e8 d6 96 1d cc 66 
0f 1f 44 00 00 0f 1f 44 00
2023-08-27T09:16:54.692165-04:00 phobos kernel: [ 1218.355538] RSP: 
0018:ac3842acf7e0 EFLAGS: 00010282
2023-08-27T09:16:54.692166-04:00 phobos kernel: [ 1218.355541] RAX: 
 RBX: 9a450caa RCX: 
2023-08-27T09:16:54.692166-04:00 phobos kernel: [ 1218.355543] RDX: 
0002 RSI: 8d54191e RDI: 
2023-08-27T09:16:54.692167-04:00 phobos kernel: [ 1218.355544] RBP: 
 R08:  R09: ac3842acf650
2023-08-27T09:16:54.692168-04:00 phobos kernel: [ 1218.355546] R10: 
0003 R11: 8dcd43a8 R12: 0001
2023-08-27T09:16:54.692169-04:00 phobos 

Bug#1050724: ignores fcitx 4

[Toni Mueller]

Package: terminator
Version: 2.1.2-2
Severity: normal
Tags: l10n upstream


Hi,

I have terminator installed, but can't for the life of me get fcitx to
activate. Hence, I am unable to write non-ascii characters in
Terminator.

The problem does seem to be fixed in terminator 2.1.3, where I can
activate fcitx so far. For me, this means that I need to use a "foreign" 
terminator for many things.


Thanks,
Toni


-- System Information:
Debian Release: trixie/sid
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (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 terminator depends on:
ii  gir1.2-glib-2.01.74.0-3
ii  gir1.2-gtk-3.0 3.24.37-2
ii  gir1.2-pango-1.0   1.50.14+ds-1
ii  gir1.2-vte-2.910.70.6-1
ii  gsettings-desktop-schemas  43.0-1
ii  python33.11.2-1+b1
ii  python3-cairo  1.20.1-5+b1
ii  python3-configobj  5.0.8-2
ii  python3-dbus   1.3.2-4+b1
ii  python3-gi 3.42.2-3+b1
ii  python3-gi-cairo   3.42.2-3+b1
ii  python3-psutil 5.9.4-1+b1

Versions of packages terminator recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.8-2~deb12u1
ii  dbus-x11 [dbus-session-bus]   1.14.8-2~deb12u1
ii  gir1.2-keybinder-3.0  0.3.2-1.1
ii  gir1.2-notify-0.7 0.8.2-1
ii  xdg-utils 1.1.3-4.1

terminator suggests no packages.

-- no debconf information