Bug#1052763: libgnuastro18 has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/libgnuastro_make.so

2023-12-04 Thread Andreas Beckmann
On Tue, 26 Sep 2023 20:54:29 +0200 Mohammad Akhlaghi 
 wrote:
Will this problem be fixed if we separate 'libgnuastro_make' as a 
separate package in 'debian/control'?


Given that this library is actually a plugin for GNU make, it would be 
useful to move it to separate package (e.g. libgnuatro-make-plugin, no 
SOVERSION in the name) since you need the unversioned name 
libgnuastro_make.so in the -plugin and not in the -dev package.


You would then need in the new package (assuming you introduce it in 
version 0.20-2):

  Breaks:   libgnuastro17 (<< 0.20), libgnuastro18 (<< 0.20-2~)
  Replaces: libgnuastro17 (<< 0.20), libgnuastro18 (<< 0.20-2~)

Andreas



Bug#1055431: RFS: scala-mode-el/1:1.1.0+git20221025.5d7cf21-1 [RC] [Team] -- Emacs major mode for editing scala source code

2023-12-04 Thread Xiyue Deng
Hi Paul,

Paul Wise  writes:

> On Mon, 2023-12-04 at 02:28 -0800, Xiyue Deng wrote:
>
>> I think dh_auto_clean is the right place, because the build failure is
>> because that the clean target requires the existence of
>> scala-mode-pkg.el, which is generated by Cask.  As we don't have Cask,
>> we need to provide this before dh_auto_clean runs.
>
> I think it is against ftp-master rules to have generated files
> present that can't be built using only tools from Debian main.
>
> So I think you would need to package Cask first?

Cask and similar tools like Eask and Eldev are tools that automatically
install dependencies of an Emacs addon package, which doesn't use and
circumvents the system package management.  I think the Emacsen team
chooses not to package those tools and prefers using dh-elpa for the
job, and may override build target to avoid using those tools.  See also
[1] and [2] for some previous discussions.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837922#15
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875722#16

-- 
Xiyue Deng


signature.asc
Description: PGP signature


Bug#1056998: cdrom: Installation media changes after booting it

2023-12-04 Thread Ram Reddy
Hello,

Thomas Schmitt wrote:FWIW check the BIOS L[123] cache settings and
consider changing them to
> more conservative "slower" values if possible. And you have different RAM

For changing the BIOS L[1/2/3] cache settings, these are laptop BIOSes
which usually have very few features (other than secure boot/tpm
options which are required for laptops with Windows), so there was no
option for that in the BIOSes. However, when I get home I could try
changing the cache settings on the Legion 7i gen 5, as it has a key
combination in the BIOS to enter an "Advanced Mode" with overclocking
settings and more, which likely has cache settings.

> models and configurations, could there be one DIMM in the mix that is >
running overclocked?

None of the memory modules were overclocked, and they were all
operating at stock speeds. The Legion 7i gen 5 got 10 passes in
memtest with 0 errors, and both of the Thinkpad X1 Carbon laptops, and
the Yoga C740, had fully soldered memory. One of the Thinkpad E14 gen
5 laptops also had unchanged memory. The laptops without any changed
memory also showed similar results, so I doubt that it has anything to
do with memory.

Have an exceptionally great day,
Ram


Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak

2023-12-04 Thread Tobias Frost
Am Fri, Dec 01, 2023 at 08:38:55AM +0300 schrieb Igor B. Poretsky:
> Hello Tobias,
> 
> > "Tobias" == Tobias Frost  writes:
> 
> Tobias> You should be able to just re-upload to mentors. If it does
> Tobias> not allow that, remove the package manually from mentors,
> Tobias> then re-upload. In the case a bot auto-close this RFS bug,
> Tobias> just manually re-open it (do not file a new one)
> 
> Indeed, I've done it without a problem. Thus, I've re-uploaded all my
> packages, not only Multispeech. And, since the issues listed are actual
> for other my packages as well, I tried to address them their as well.
> 
> Tobias> On further iterations, you keep at -1 until this is
> Tobias> sponsored.

> But some things should be fixed on the upstream level. Of course, I can
> do it with Debian patches, but is it a point when I am an upstream
> developer myself? How should I act in this situation?

The "-1" is the Debian revision; it is orthogonal to the upstream
version, (except the rules where it resets to usually -1, of course)

If you have fixes that goes into the upstream part, as upsream you can
always cut a new release, that will increase its version; that would
reset the Debian revision generally to -1.
If you for whatever reason don't want to make a new upstream release,
you can as well work with patches, in this case, you would increment the
debian revision *if the previous revision have been uploaded previously.

(Note that the "keep at -1" from my previous mail is meant for this RFS,
it is meant "don't change it until sponsored", in other words, if you
have another upload (after this has been sponsored), lets say "-2", you
would keep "-2" until the RFS is sponsored. Sorry if that caused
confusion.)

BTW, not sure if I pointed you to this document alraeady, but when
you are upstream as well, you should read this:
https://wiki.debian.org/UpstreamGuide

Cheers,
-- 
tobi

 
> Best regards,
> Igor.



Bug#1057443: sqlalchemy ftbfs with Python 3.12

2023-12-04 Thread Matthias Klose

Package: src:sqlalchemy
Version: 1.4.47+ds1-1
Severity: serious
Tags: sid trixie

sqlalchemy ftbfs with Python 3.12:

[...]
test/orm/test_eager_relations.py::InnerJoinSplicingWSecondaryTest_sqlite+pysqlite_3_44_2::test_joined_across 
Fatal Python error: Segmentation fault


Current thread 0x7f74c1526740 (most recent call first):
  File "/<>/lib/sqlalchemy/engine/default.py", line 736 in 
do_execute
  File "/<>/lib/sqlalchemy/engine/base.py", line 1900 in 
_execute_context
  File "/<>/lib/sqlalchemy/engine/base.py", line 1572 in 
_execute_clauseelement
  File "/<>/lib/sqlalchemy/sql/elements.py", line 334 in 
_execute_on_connection
  File "/<>/lib/sqlalchemy/engine/base.py", line 1705 in 
_execute_20
  File "/<>/lib/sqlalchemy/orm/session.py", line 1714 in 
execute

  File "/<>/lib/sqlalchemy/orm/query.py", line 2916 in _iter
  File "/<>/lib/sqlalchemy/orm/query.py", line 2773 in all
  File "/<>/test/orm/test_eager_relations.py", line 3654 in go
  File "/<>/lib/sqlalchemy/testing/assertions.py", line 
871 in assert_sql_execution
  File "/<>/lib/sqlalchemy/testing/assertions.py", line 
890 in assert_sql_count
  File "/<>/test/orm/test_eager_relations.py", line 3656 
in _assert_result
  File "/<>/test/orm/test_eager_relations.py", line 3678 
in test_joined_across
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 194 in 
pytest_pyfunc_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 1792 in 
runtest
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 169 in 
pytest_runtest_call
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 

  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 341 in 
from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 261 in 
call_runtest_hook
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 222 in 
call_and_report
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 133 in 
runtestprotocol
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 114 in 
pytest_runtest_protocol
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 350 in 
pytest_runtestloop
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__

  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 325 in _main
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 271 in 
wrap_session
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 318 in 
pytest_cmdline_main
  File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 77 in 
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 115 in 
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 493 in 
__call__
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", 
line 169 in main
  File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", 
line 192 in console_main
  File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 5 in 


  File "", line 88 in _run_code
  File "", line 198 in _run_module_as_main
Segmentation fault
make[1]: *** [debian/rules:20: override_dh_auto_install] Error 139



Bug#1057442: onboard ftbfs with Python 3.12

2023-12-04 Thread Matthias Klose

Package: src:onboard
Version: 1.4.1-5
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

onboard ftbfs with Python 3.12:

[...]
creating build
creating build/temp.linux-x86_64-cpython-312
creating build/temp.linux-x86_64-cpython-312/Onboard
creating build/temp.linux-x86_64-cpython-312/Onboard/osk
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 
-Wall -g -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -g -fwrapv -O2 -g -O2 
-ffile-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security 
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DMAJOR_VERSION=0 
-DMINOR_VERSION=4 -DMICRO_VERSION=0 -I/usr/include/blkid 
-I/usr/include/cairo -I/usr/include/cloudproviders -I/usr/include/dconf 
-I/usr/include/freetype2 -I/usr/include/fribidi 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/gio-unix-2.0 
-I/usr/include/glib-2.0 -I/usr/include/gtk-3.0 -I/usr/include/harfbuzz 
-I/usr/include/hunspell -I/usr/include/libmount -I/usr/include/libpng16 
-I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/webp 
-I/usr/include/x86_64-linux-gnu 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/python3.12 
-c Onboard/osk/osk_audio.c -o 
build/temp.linux-x86_64-cpython-312/Onboard/osk/osk_audio.o 
-Wsign-compare -Wdeclaration-after-statement 
-Werror=declaration-after-statement

In file included from /usr/include/python3.12/Python.h:44,
 from Onboard/osk/osk_module.h:25,
 from Onboard/osk/osk_audio.c:21:
/usr/include/python3.12/object.h: In function ‘Py_SIZE’:
/usr/include/python3.12/object.h:233:5: error: ISO C90 forbids mixed 
declarations and code [-Werror=declaration-after-statement]

  233 | PyVarObject *var_ob = _PyVarObject_CAST(ob);
  | ^~~
In file included from /usr/include/python3.12/Python.h:53:
/usr/include/python3.12/cpython/longintrepr.h: In function 
‘_PyLong_CompactValue’:
/usr/include/python3.12/cpython/longintrepr.h:121:5: error: ISO C90 
forbids mixed declarations and code [-Werror=declaration-after-statement]
  121 | Py_ssize_t sign = 1 - (op->long_value.lv_tag & 
_PyLong_SIGN_MASK);

  | ^~
Onboard/osk/osk_audio.c: In function ‘osk_audio_init_canberra’:
Onboard/osk/osk_audio.c:70:5: warning: ‘gdk_screen_get_number’ is 
deprecated [-Wdeprecated-declarations]

   70 | nr = gdk_screen_get_number(screen);
  | ^~
In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gdk/gdkx.h:28,
 from Onboard/osk/osk_audio.c:23:
/usr/include/gtk-3.0/gdk/gdkscreen.h:56:14: note: declared here
   56 | gint gdk_screen_get_number(GdkScreen 
*screen);

  |  ^
Onboard/osk/osk_audio.c: In function ‘osk_audio_play’:
Onboard/osk/osk_audio.c:101:5: warning: ‘gdk_screen_get_width’ is 
deprecated [-Wdeprecated-declarations]

  101 | sw = gdk_screen_get_width(screen);
  | ^~
/usr/include/gtk-3.0/gdk/gdkscreen.h:58:14: note: declared here
   58 | gint gdk_screen_get_width (GdkScreen 
*screen);

  |  ^~~~
Onboard/osk/osk_audio.c:102:5: warning: ‘gdk_screen_get_height’ is 
deprecated [-Wdeprecated-declarations]

  102 | sh = gdk_screen_get_height(screen);
  | ^~
/usr/include/gtk-3.0/gdk/gdkscreen.h:60:14: note: declared here
   60 | gint gdk_screen_get_height(GdkScreen 
*screen);

  |  ^
cc1: some warnings being treated as errors
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:395: build: plugin distutils failed with: exit 
code=1: /usr/bin/python3.12 setup.py build

I: pybuild base:310: /usr/bin/python3 setup.py build



Bug#1055431: RFS: scala-mode-el/1:1.1.0+git20221025.5d7cf21-1 [RC] [Team] -- Emacs major mode for editing scala source code

2023-12-04 Thread Paul Wise
On Mon, 2023-12-04 at 02:28 -0800, Xiyue Deng wrote:

> I think dh_auto_clean is the right place, because the build failure is
> because that the clean target requires the existence of
> scala-mode-pkg.el, which is generated by Cask.  As we don't have Cask,
> we need to provide this before dh_auto_clean runs.

I think it is against ftp-master rules to have generated files
present that can't be built using only tools from Debian main.

So I think you would need to package Cask first?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#932617: fixed in fwupd 1.9.10-1

2023-12-04 Thread Paul Wise
On Mon, 2023-12-04 at 15:49 +, Mario Limonciello wrote:

>    * Remove extra conffiles with the 1.9.10~ version instead.
>  (Closes: #932617)

Could you also remove this too?

/etc/fwupd/remotes.d/dell-esrt.conf

https://packages.debian.org/search?suite=bookworm=any=contents=dell-esrt.conf


-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#1057441: linux-image-6.6-amd64: Crypt does not longer work

2023-12-04 Thread Michael Ott
Package: src:linux
Version: 6.6.4-1~exp1
Severity: important

Dear Maintainer,

After updating to the 6.6 kernel the password for my encryption does not longer
work

Please unlock disk nvme0n1p3_crypt: **
device-mapper: table: 253:0: crypt: Error allocation crypto tfm (_ENOENT)
device-mapper: ioctl: error adding target to table
device-mapper: reload ioctl on nvme0n1p3_crypt (253:0) failed: No such file or
directory
cryptsetup: ERROR: nvme0n1p3_crypt: cryptsetup failed, bad password or options?

Everything works with 6.5. I also downgrade systemd and cryptosetup but no
changes



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

** Model information
sys_vendor: LENOVO
product_name: 20KF001GGE
product_version: ThinkPad X280
chassis_vendor: LENOVO
chassis_version: None
bios_vendor: LENOVO
bios_version: N20ET66W (1.51 )
board_vendor: LENOVO
board_name: 20KF001GGE
board_version: Not Defined

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** 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: Lenovo Xeon E3-1200 v6/7th Gen Core Processor Host 
Bridge/DRAM Registers [17aa:2256]
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: Lenovo UHD Graphics 620 [17aa:2256]
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: 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: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem [17aa:2256]
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:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen 
Core Processor Gaussian Mixture Model [17aa:2256]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

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: Lenovo Sunrise Point-LP USB 3.0 xHCI Controller [17aa:2256]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 21)
Subsystem: Lenovo Sunrise Point-LP Thermal subsystem [17aa:2256]
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: intel_pch_thermal
Kernel modules: intel_pch_thermal

00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-LP 
CSME HECI #1 [8086:9d3a] (rev 21)
Subsystem: Lenovo Sunrise Point-LP CSME HECI [17aa:2256]
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: mei_me
Kernel modules: mei_me

00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-LP PCI Express Root 
Port #1 [8086:9d10] (rev f1) (prog-if 00 [Normal decode])
Subsystem: Lenovo Sunrise Point-LP PCI Express Root Port [17aa:2256]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:1c.2 PCI bridge [0604]: Intel 

Bug#1057440: libvcflib: 1

2023-12-04 Thread a
Source: libvcflib
Version: 1.0.9+dsg1
Severity: important
X-Debbugs-Cc: zhangjial...@loongson.cn

Dear Maintainer,

I found the libvcflib loong64 has missed entry, so this build failed.
--- tmp/libvcflib-1.0.9+dfsg1/debian/control2023-12-03 12:29:41.0 
+
+++ debian/control  2023-12-05 05:12:30.851914259 +
@@ -76,7 +76,7 @@
  This package contains the static library and the header files.
 
 Package: libvcflib-tools
-Architecture: any-amd64 arm64 mips64el ppc64el s390x ia64 ppc64 riscv64 
sparc64 alpha
+Architecture: any-amd64 arm64 loong64 mips64el ppc64el s390x ia64 ppc64 
riscv64 sparc64 alpha
 Depends: ${shlibs:Depends},
  ${misc:Depends},
  python3:any,



Bug#1057439: datamash: "antimode" returns lowest, instead of least common, value

2023-12-04 Thread Kingsley G. Morse Jr.
Package: datamash
Version: 1.8-1
Severity: normal

Dear Maintainer,

Thanks for maintaining datamash.

I like that it lets shell scripts calculate
statistics.

The main reason I'm writing is datamash's
"antimode" statistical grouping operation did not
work as I expected.

datamash's man page says its "antimode"
statistical grouping operation is for the "least
common value".

But, my testing suggests datamash's "antimode"
instead returns the lowest value.

My simple test is to 

1.) copy 

echo -e "1\n1\n2" | datamash antimode 1

to the bash command prompt and 

2.) press the  key.


At least on my computer, it returns "1".

But, I expected it to return "2", because "2" is
the least common value.

I suppose maybe either datamash's man page and/or code
could be changed so they're consistent.

Thanks again for datamash!

Kind regards,
Kingsley

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
merged-usr: no
Architecture: i386 (i686)

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

Versions of packages datamash depends on:
ii  libc6  2.37-12

datamash recommends no packages.

datamash suggests no packages.

-- no debconf information

-- 
Time is the fire in which we all burn.



Bug#1057363: RM: twitterwatch -- RoQA; Upstream Dead; Useless with Twitter API Changes

2023-12-04 Thread Boyuan Yang
Hi,

在 2023-12-04星期一的 21:02 +,Miguel Landaeta写道:
> On Mon, Dec 4, 2023 at 12:09 AM Boyuan Yang  wrote:
> > 
> > [...]
> > 
> > Dear Debian FTP Masters,
> > 
> > As discussed in https://bugs.debian.org/1056613 , package twitterwatch 
> > makes use
> > of Twitter API, which is gone since 2023. Its upstream shows no activity 
> > for 7 years,
> > and the Debian package received no maintainer updates since 2016. As a 
> > result, I
> > believe we should have package twitterwatch removed from Debian archive.
> > 
> 
> Hi Boyuan,
> 
> Thanks for submitting this bug.
> 
> Do you have any objection to doing the same for db2twitter and retweet 
> packages?
> 
> I think they are in the same situation.

I am not the package maintainer for db2twitter or retweet, so I am not in the 
position
of saying whether I should object or not.

I see that you are also a Debian Developer; you should have the same permission 
or right
on RM bug submission as I do.

Thanks,
Boyuan Yang


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


Bug#1057382: would it be possible to keep certbot up-to-date?

2023-12-04 Thread Harlan Lieberman-Berg
On Mon, Dec 4, 2023 at 10:15 AM Harald Dunkel  wrote:
> Upstream provides certbot 2.7.4. Would it be possible to keep
> certbot in Sid roughly up-to-date?

Hi Harri,

Right now, I've been hesitant to update certbot because of the lack of
cryptographic signature verification.  I've been working with upstream
to try and close that gap, but we haven't gotten there yet.  Take a
peek at https://github.com/certbot/certbot/issues/9740 for reference.

Even if we don't come up with a solution long-term, I may see if I can
get one of the Let's Encrypt devs to do something as a one-off out of
band, since we are a bit out of date at this point.

It's definitely on my radar!  Hopefully we'll cross this off the list soon.

Sincerely,

-- 
Harlan Lieberman-Berg
~hlieberman



Bug#1057437: pmix: FTBFS: dh_missing: error: missing files, aborting

2023-12-04 Thread Chris Hofstaedtler
Source: pmix
Version: 5.0.1-3
Severity: serious
Tags: ftbfs

Dear Maintainer,

your package FTBFS in unstable, in my own test rebuild as well as on 
reproducible-builds.org.

Build log snippet, hopefully relevant:
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cygdb exists 
in debian/tmp but is not installed to anywhere 
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cython exists 
in debian/tmp but is not installed to anywhere 
   dh_missing: warning: usr/lib/x86_64-linux-gnu/pmix2/local/bin/cythonize 
exists in debian/tmp but is not installed to anywhere 
   dh_missing: error: missing files, aborting
  The following debhelper tools have reported what they installed (with 
files per package)
  * dh_install: libpmix-bin (9), libpmix-dev (4), libpmix2 (35), 
python3-pmix (1)
  * dh_installdocs: libpmix-bin (0), libpmix-dev (3), libpmix2 (0), 
python3-pmix (0)
  * dh_installexamples: libpmix-bin (0), libpmix-dev (27), libpmix2 (0), 
python3-pmix (0)
  * dh_installman: libpmix-bin (0), libpmix-dev (5), libpmix2 (0), 
python3-pmix (0)
  If the missing files are installed by another tool, please file a bug 
against it.
  When filing the report, if the tool is not part of debhelper itself, 
please reference the
  "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for 
debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
  Be sure to test with dpkg-buildpackage -A/-B as the results may vary when 
only a subset is built
  If the omission is intentional or no other helper can take care of this 
consider adding the
  paths to debian/not-installed.

  Remember to be careful with paths containing "x86_64-linux-gnu", where 
you might need to
  use a wildcard or (assuming compat 13+) e.g. ${DEB_HOST_MULTIARCH} in 
debian/not-installed
  to ensure it works on all architectures (see #961104).
   make: *** [debian/rules:36: binary] Error 25
   dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

Full build log attached.
rbo build log here:
   
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/pmix_5.0.1-3.rbuild.log.gz

Best,
Chris



pmix_5.0.1-3.gz
Description: application/gzip


Bug#1057436: ovn: FTBFS: tar (child): /usr/src/openvswitch/openvswitch.tar.gz: Cannot open: No such file or directory

2023-12-04 Thread Chris Hofstaedtler
Source: ovn
Version: 23.09.0-1
Severity: serious
Tags: ftbfs

Dear Maintainer,

your package FTBFS in unstable, in my own test rebuild as well as on 
reproducible-builds.org.

Build log snippet, hopefully relevant:
   cd ovs && tar -xzf /usr/src/openvswitch/openvswitch.tar.gz 
--strip-components=1
   tar (child): /usr/src/openvswitch/openvswitch.tar.gz: Cannot open: No such 
file or directory
   tar (child): Error is not recoverable: exiting now
   tar: Child returned status 2
   tar: Error is not recoverable: exiting now
   make[1]: *** [debian/rules:18: override_dh_auto_configure] Error 2
   make[1]: Leaving directory '/<>'
   make: *** [debian/rules:7: binary] Error 2
   dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

Full build log attached.
rbo build log here:
   
https://tests.reproducible-builds.org/debian/rbuild/unstable/arm64/ovn_23.09.0-1.rbuild.log.gz

Best,
Chris

sbuild (Debian sbuild) 0.85.0 (04 January 2023) on cl.home.zeha.at

+==+
| ovn 23.09.0-1 (amd64)Mon, 04 Dec 2023 02:42:26 + |
+==+

Package: ovn
Version: 23.09.0-1
Source Version: 23.09.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

Unpacking /home/ch/.cache/sbuild/unstable-amd64.tar to 
/srv/scratch/sbuild/tmp.sbuild.u2WtD4AYK6...
I: NOTICE: Log filtering will replace 'sbuild-unshare-dummy-location' with 
'<>'
I: NOTICE: Log filtering will replace 'build/ovn-XaBoeO/resolver-0rgGjP' with 
'<>'

+--+
| Update chroot|
+--+

Get:1 http://172.16.172.24/debian unstable InRelease [198 kB]
Get:2 http://deb.debian.org/debian unstable InRelease [198 kB]
Ign:3 http://172.16.172.24/debian unstable/non-free amd64 Packages
Ign:4 http://172.16.172.24/debian unstable/contrib amd64 Packages
Ign:5 http://172.16.172.24/debian unstable/main amd64 Packages
Ign:6 http://172.16.172.24/debian unstable/non-free-firmware amd64 Packages
Get:3 http://172.16.172.24/debian unstable/non-free amd64 Packages [123 kB]
Get:4 http://172.16.172.24/debian unstable/contrib amd64 Packages [66.0 kB]
Get:5 http://172.16.172.24/debian unstable/main amd64 Packages [9596 kB]
Get:6 http://172.16.172.24/debian unstable/non-free-firmware amd64 Packages 
[6364 B]
Get:7 http://deb.debian.org/debian unstable/contrib Sources [60.8 kB]
Get:8 http://deb.debian.org/debian unstable/non-free-firmware Sources [6548 B]
Get:9 http://deb.debian.org/debian unstable/non-free Sources [85.1 kB]
Get:10 http://deb.debian.org/debian unstable/main Sources [10.3 MB]
Fetched 20.7 MB in 7s (2851 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  binutils binutils-common binutils-x86-64-linux-gnu cpp-13 g++-13 gcc-13
  gcc-13-base libasan8 libatomic1 libbinutils libcc1-0 libctf-nobfd0 libctf0
  libgcc-13-dev libgcc-s1 libgomp1 libgprofng0 libhwasan0 libitm1 liblsan0
  libquadmath0 libsframe1 libstdc++-13-dev libstdc++6 libsystemd0 libtsan2
  libubsan1 libudev1
28 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 61.5 MB of archives.
After this operation, 173 kB of additional disk space will be used.
Get:1 http://172.16.172.24/debian unstable/main amd64 libcc1-0 amd64 13.2.0-8 
[43.0 kB]
Get:2 http://172.16.172.24/debian unstable/main amd64 libgprofng0 amd64 
2.41.50.20231202-1 [769 kB]
Get:3 http://172.16.172.24/debian unstable/main amd64 libctf0 amd64 
2.41.50.20231202-1 [87.1 kB]
Get:4 http://172.16.172.24/debian unstable/main amd64 libctf-nobfd0 amd64 
2.41.50.20231202-1 [151 kB]
Get:5 http://172.16.172.24/debian unstable/main amd64 binutils-x86-64-linux-gnu 
amd64 2.41.50.20231202-1 [2234 kB]
Get:6 http://172.16.172.24/debian unstable/main amd64 libbinutils amd64 
2.41.50.20231202-1 [515 kB]
Get:7 http://172.16.172.24/debian unstable/main amd64 binutils-common amd64 
2.41.50.20231202-1 [2537 kB]
Get:8 http://172.16.172.24/debian unstable/main amd64 binutils amd64 
2.41.50.20231202-1 [80.1 kB]
Get:9 http://172.16.172.24/debian unstable/main amd64 libgomp1 amd64 13.2.0-8 
[131 kB]
Get:10 http://172.16.172.24/debian unstable/main amd64 libitm1 amd64 13.2.0-8 
[26.1 kB]
Get:11 http://172.16.172.24/debian unstable/main amd64 libatomic1 amd64 
13.2.0-8 [9304 B]
Get:12 http://172.16.172.24/debian unstable/main amd64 libasan8 amd64 13.2.0-8 
[2558 kB]
Get:13 http://172.16.172.24/debian unstable/main amd64 liblsan0 amd64 13.2.0-8 
[1102 kB]
Get:14 http://172.16.172.24/debian unstable/main amd64 libtsan2 amd64 13.2.0-8 
[2334 kB]
Get:15 

Bug#1057435: ITP: golang-github-containers-gvisor-tap-vsocks -- golang bindings for gvisor

2023-12-04 Thread Reinhard Tartler
Package: wnpp
Severity: wishlist
Owner: Reinhard Tartler 
X-Debbugs-Cc: debian-de...@lists.debian.org, siret...@tauware.de

* Package name: golang-github-containers-gvisor-tap-vsocks
  Version : 0.7.1
  Upstream Contact: gvisor-tap-vsocks authors
* URL : https://github.com/containers/gvisor-tap-vsoc
* License : Apache-2.03
  Programming Lang: Golang
  Description : golang bindings for gvisor

this is a new dependencies for podman 4.8



Bug#1035358: urlview does not work with URLs containing parentheses

2023-12-04 Thread наб
On Mon, May 01, 2023 at 09:45:46PM +0200, Francesco Ariis wrote:
> A workaround is to `cp /etc/urlview/system.urlview ~/.urlview` and
> then replace REGEXP with
> REGEXP (((http|https|ftp|gopher)|mailto):(//)?[^ 
> <>"\t]*|(www|ftp)[0-9]?\.[-a-z0-9.]+)[^ .,;\t\n\r<">\):]?[^, <>"\t]*[^ 
> .,;\t\n\r<">:]
> (i.e. erasing that last “\)”).
This is quite detrimental to the very common case of a URL that's
entirely parenthesised, or one that ends a parenthetical; compare:
  $ tail -n3 text
  Debian#1035358: https://en.wikipedia.org/wiki/Close_Combat_(series)
  vs (https://en.wikipedia.org/wiki/Debian)
  vs  
https://en.wikipedia.org/wiki/(You_Gotta)_Fight_for_Your_Right_(To_Party!)
  $ grep -Eio '((http|https|ftp|gopher|gemini|mailto):(//)?[^ 
<>"]*|(www|ftp)[0-9]?\.[-a-z0-9.]+)[^ .,;<">\):]?[^, <>"]*[^ .,;<">:\)]' text | 
tail -n3
  https://en.wikipedia.org/wiki/Close_Combat_(series
  https://en.wikipedia.org/wiki/Debian
  https://en.wikipedia.org/wiki/(You_Gotta)_Fight_for_Your_Right_(To_Party!
  $ grep -Eio '((http|https|ftp|gopher|gemini|mailto):(//)?[^ 
<>"]*|(www|ftp)[0-9]?\.[-a-z0-9.]+)[^ .,;<">\):]?[^, <>"]*[^ .,;<">:]' text | 
tail -n3
  https://en.wikipedia.org/wiki/Close_Combat_(series)
  https://en.wikipedia.org/wiki/Debian)
  https://en.wikipedia.org/wiki/(You_Gotta)_Fight_for_Your_Right_(To_Party!)
so this trivial solution fixes an IME rare case of an URL ending with a ')'
by breaking the much more common one.

It is quite likely something /can/ be cooked here,
I haven't managed to in a good few minutes of fiddling.

Attaching my test driver.

Best,
наб
static auto regex =
// R"DUPA(((http|https|ftp|gopher|gemini|mailto):(//)?[^ 
<>"]*|(www|ftp)[0-9]?\.[-a-z0-9.]+)[^ .,;<">\):]?(([^, <>"]*)|(\([^, 
<>"]*\)))*[^ .,;<">:\)])DUPA";
R"DUPA(((http|https|ftp|gopher|gemini|mailto):(//)?[^ 
<>"]*|(www|ftp)[0-9]?\.[-a-z0-9.]+)[^ .,;<">\):]?[^, <>"]*[^ .,;<">:\)])DUPA";

#include 
#include 
#include 
#include 


int main() {
regex_t rgx;
if(regcomp(, regex, REG_EXTENDED | REG_ICASE))
abort();

for(auto l : {"Debian#1035358: 
https://en.wikipedia.org/wiki/Close_Combat_(series)",  //
  "vs (https://en.wikipedia.org/wiki/Debian)",  
  //
  "vs  
https://en.wikipedia.org/wiki/(You_Gotta)_Fight_for_Your_Right_(To_Party!)"}) {
regmatch_t matches[20];
if(regexec(, l, 20, matches, 0))
abort();

puts(l);
for(size_t i = 0; i <= rgx.re_nsub; ++i)
std::printf("%zu: \"%.*s\"\n", i, 
(int)(matches[i].rm_eo - matches[i].rm_so), l + matches[i].rm_so);
puts("");
}
}


signature.asc
Description: PGP signature


Bug#1057434: libreoffice-numbertext 1.0.11-3 is broken; 1.0.10-1 works as expected

2023-12-04 Thread Alexandre Bonneau
Package: libreoffice-numbertext
Version: 1.0.11-3
Severity: grave

When trying to use the =NUMBERTEXT(5) formula in Libreoffice Calc, you get an 
'Err: 504' error in those cells.

When reverting back to libreoffice-numbertext 1.0.10-1, all the functions using 
the NUMBERTEXT function are correctly parsed.

The package libreoffice-numbertext 1.0.11-3 is broken, when using Debian Trixie 
and Libreoffice 4:7.5.9~rc1-1.

Regards,
Alexandre Bonneau



Bug#1057433: gcc-13: Enable default pie to loong64.

2023-12-04 Thread Peng Fan
Package: gcc-13
Version: 13.2.0-8
Severity: normal
X-Debbugs-Cc: fanp...@loongson.cn

Dear Maintainer,

When compiling the package 'dpkg' for loong64 in the Debian
Package Auto-Building environment, found not buillt pie. So
add --enable-default-pie for it.

-- System Information:
Debian Release: trixie/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: loong64 (loongarch64)

Kernel: Linux 5.10.0-60.96.0.126.oe2203.loongarch64 (SMP w/32 CPU threads)
Locale: LANG=zh_CN.UTF-8, LC_CTYPE=zh_CN.UTF-8 (charmap=ANSI_X3.4-1968) 
(ignored: LC_ALL set to POSIX), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages gcc-13 depends on:
ii  binutils   2.41-6
ii  cpp-13 13.2.0-8
ii  gcc-13-base13.2.0-8
ii  libc6  2.37-9+loong64
ii  libcc1-0   13.2.0-8
ii  libgcc-13-dev  13.2.0-8
ii  libgcc-s1  13.2.0-8
ii  libgmp10   2:6.3.0+dfsg-2
ii  libisl23   0.26-3
ii  libmpc31.3.1-1+b1
ii  libmpfr6   4.2.1-1
ii  libstdc++6 13.2.0-8
ii  libzstd1   1.5.5+dfsg2-2
ii  zlib1g 1:1.3.dfsg-3

Versions of packages gcc-13 recommends:
ii  libc6-dev  2.37-9+loong64

Versions of packages gcc-13 suggests:
pn  gcc-13-doc  
ii  gcc-13-locales  13.2.0-8

-- no debconf information
diff --git a/debian/rules.defs b/debian/rules.defs
index 54a3b84..ef03d3e 100644
--- a/debian/rules.defs
+++ b/debian/rules.defs
@@ -1474,7 +1474,7 @@ ifeq ($(distribution),Debian)
mips mipsel mips64 mips64el mipsn32 mipsn32el \
mipsr6 mipsr6el mips64r6 mips64r6el mipsn32r6 mipsn32r6el \
ppc64el s390x sparc sparc64 kfreebsd-amd64 kfreebsd-i386 \
-   hurd-amd64 hurd-i386 riscv64
+   hurd-amd64 hurd-i386 riscv64 loong64
   endif
   ifeq (,$(filter $(distrelease), jessie stretch))
 pie_archs += powerpc ppc64


Bug#1049457: fuser(1) not working on libraries, possibly because of disagreement over minor device

2023-12-04 Thread Paul Kimoto
On Mon, Aug 21, 2023 at 10:07:04PM -0400, Paul Kimoto wrote:
> FWIW, fuser from psmisc-23.4 configured with
> "--enable-mountinfo-list" produces the kind of output I expect.
> (Without "--enable-mountinfo-list", it doesn't.)

I wrote the above, but it is just wrong.  Sorry for the misinformation.
-Paul



Bug#1053166: RM: nuget -- RoQA; ancient version; orphaned

2023-12-04 Thread Bastian Germann
Control: tags -1 - moreinfo

Those packages do not matter because they are already removed.



Bug#1053153: RM: gtk-sharp2 -- RoQA; RC-buggy; dead upstream; depends on gtk2

2023-12-04 Thread Bastian Germann
Control: tags -1 - moreinfo

Those packages do not matter because they are already removed.



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Michael Biebl

Am 04.12.23 um 23:09 schrieb Michael Biebl:

The code to exclude lost+found appears to be still there:
https://github.com/systemd/systemd/blob/main/src/tmpfiles/tmpfiles.c#L720

Can you create a lost+found directory and then run
SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --prefix /tmp

?


I haven't really debugged this fully, but from a cursory glance it 
appears that systemd-tmpfiles-setup.service is responsible for nuking 
/tmp/lost+found


systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev
doesn't preserve /tmp/lost+found which looks like a regression.


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1051166: FTBFS with doxygen 1.9.8

2023-12-04 Thread Bastian Germann
Please note that this issue keeps doxygen from migrating to testing, which in 
turn keeps llvm-toolchain-14 in the key packages and from being removed.



Bug#1057251: librocfft0-tests: nondeterministic failures in random_real_3d/random_params.vs_fftw

2023-12-04 Thread Cordell Bloor
The test failures are reproducible on my Radeon VII (gfx906) workstation 
when the failing seed is specified. So, the problem is not specific to 
gfx1032:


$ ROCFFT_LAYER=1 /usr/libexec/rocm/librocfft0-tests/rocfft-test 
--gtest_filter='random_real_3d/random_params.vs_fftw/0:random_real_3d/random_params.vs_fftw/1' 
--seed 190206186

single epsilon: 3.75e-05    double epsilon: 1e-15
Random seed: 190206186
rocfft_setup
rocfft_get_version_string,buf,0x7ffe3b83ebf0,len,256
rocFFT version: 1.0.21.
Note: Google Test filter = 
random_real_3d/random_params.vs_fftw/0:random_real_3d/random_params.vs_fftw/1

[==] Running 2 tests from 1 test suite.
[--] Global test environment set-up.
[--] 2 tests from random_real_3d/random_params
[ RUN  ] random_real_3d/random_params.vs_fftw/0
rocfft_plan_description_create,description,0x55fbee94f950
rocfft_plan_description_set_data_layout,description,0x55fbee94f950,in_array_type,real,out_array_type,hermitian_interleaved,in_offsets,[0],out_offsets,[0],in_strides,[1,34,2142],in_distance,154224,out_strides,[1,18,1134],out_distance,81648
rocfft_plan_create,plan,0x55fbe38234e0,placement,notinplace,transform_type,real_forward,precision,double,dimensions,3,lengths,[34,63,72],number_of_transforms,1,description,0x55fbee94f950
rocfft_execution_info_create,info,0x55fbe297e7a0
rocfft_plan_get_work_buffer_size,plan,0x55fbe38234e0,size_in_bytes 
ptr,0x7ffe3b83d1a8,val,0
rocfft_plan_get_work_buffer_size,plan,0x55fbe38234e0,size_in_bytes 
ptr,0x7ffe3b83d1a8,val,0

rocfft_execute,plan,0x55fbe38234e0,in_buffer,0x55fbdef54720,out_buffer,0x55fbe286e600,info,0x55fbe297e7a0
hipModuleLaunchKernel failure
rocfft_execution_info_destroy,info,0x55fbe297e7a0
rocfft_plan_description_destroy,description,0x55fbee94f950
unknown file: Failure
C++ exception with description "rocFFT plan execution failure" thrown in 
the test body.


[  FAILED  ] random_real_3d/random_params.vs_fftw/0, where GetParam() = 
(0, 3, 1, 1, 2) (582 ms)

[ RUN  ] random_real_3d/random_params.vs_fftw/1
rocfft_plan_description_create,description,0x55fbe3ccf780
rocfft_plan_description_set_data_layout,description,0x55fbe3ccf780,in_array_type,hermitian_interleaved,out_array_type,real,in_offsets,[0],out_offsets,[0],in_strides,[1,18,1134],in_distance,81648,out_strides,[1,34,2142],out_distance,154224
rocfft_plan_create,plan,0x55fbe3ccac60,placement,notinplace,transform_type,real_inverse,precision,double,dimensions,3,lengths,[34,63,72],number_of_transforms,1,description,0x55fbe3ccf780
rocfft_execution_info_create,info,0x55fbdf1a84e0
rocfft_plan_get_work_buffer_size,plan,0x55fbe3ccac60,size_in_bytes 
ptr,0x7ffe3b83d1a8,val,0
rocfft_plan_get_work_buffer_size,plan,0x55fbe3ccac60,size_in_bytes 
ptr,0x7ffe3b83d1a8,val,0

rocfft_execute,plan,0x55fbe3ccac60,in_buffer,0x55fbdeecc7b0,out_buffer,0x55fbedb2e280,info,0x55fbdf1a84e0
hipModuleLaunchKernel failure
rocfft_execution_info_destroy,info,0x55fbdf1a84e0
rocfft_plan_description_destroy,description,0x55fbe3ccf780
unknown file: Failure
C++ exception with description "rocFFT plan execution failure" thrown in 
the test body.


[  FAILED  ] random_real_3d/random_params.vs_fftw/1, where GetParam() = 
(0, 3, 1, 1, 3) (368 ms)

[--] 2 tests from random_real_3d/random_params (951 ms total)

[--] Global test environment tear-down
[==] 2 tests from 1 test suite ran. (955 ms total)
[  PASSED  ] 0 tests.
[  FAILED  ] 2 tests, listed below:
[  FAILED  ] random_real_3d/random_params.vs_fftw/0, where GetParam() = 
(0, 3, 1, 1, 2)
[  FAILED  ] random_real_3d/random_params.vs_fftw/1, where GetParam() = 
(0, 3, 1, 1, 3)


 2 FAILED TESTS
rocfft_cleanup
single precision max l-inf epsilon: 0
single precision max l2 epsilon: 0
double precision max l-inf epsilon: 0
double precision max l2 epsilon: 0



Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak

2023-12-04 Thread Samuel Thibault
Hello,

Tobias Frost, le dim. 26 nov. 2023 15:43:24 +0100, a ecrit:
> Am Sun, Nov 26, 2023 at 03:30:18PM +0300 schrieb Igor B. Poretsky:
> > Tobias> d/libmultispeech.shlibs - Why do you need this file?
> > 
> > For the version restriction in dependencies.
> 
> The Debian build system should be able to calculate dependencies on libraries
> automatically, so obviously I'm missing some detail why this is not working
> here.

I'm also wondering why you'd want this. If it's an internal library and
it has a non-public ABI, you can as well just hardcode the depency in
debian/control:

Depends: libmultispeech5 (= ${binary:Version})

> > Tobias> postinst - speech-dispatcher is using a systemd service
> > Tobias> file, if you really need to reload its configuration, you
> > Tobias> should use service speech-dispatcher reload and not kill it
> > Tobias> via kill. (you might overkill)
> > 
> > Actually, it is not mandatory. Speech Dispatcher can as well be
> > automatically spawned by a client. The kill command in this case just
> > sends the SIGHUP signal, that does not kill or restart Speech
> > Dispatcher, but only notifies it about a configuration change. It is
> > documented behaviour of Speech Dispatcher. And I should notify every
> > running instance regardless of the way it was launched by.
> 
> Additional data point: Looking at speech-dispatcher-espeak-ng, they are not
> sending SIGHUP. So it seems not to be nedded,

Actually it is, and this package makes me think that such
speech-dispatcher-foo package should be sending SIGHUPs, to notify
speech-dispatcher instances that a new voice is now available/removed.

Samuel



Bug#1057428: libseccomp ftbfs on i386

2023-12-04 Thread Felix Geyer

On 04.12.23 22:03, Matthias Klose wrote:

Package: src:libseccomp
Version: 2.5.4-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libseccomp ftbfs on i386. probably not related to Python 3.12, but blocks the 
addition of Python 3.12


Seems like glibc 2.37-13 broke valgrind on i386:
https://ci.debian.net/packages/v/valgrind/testing/i386/40527816/



Bug#1057432: python3-aiostream: Package still contains coverage output

2023-12-04 Thread Stuart Prescott
Package: python3-aiostream
Version: 0.5.2-1
Severity: important
X-Debbugs-Cc: stu...@debian.org

Dear Maintainer,

In version 0.5.2-1, there is an attempt to remove coverage outputs from
the binary package. Unfortunately, this is ineffective when there is
more than one Python interpreter in the archive.

The coverage output is originally in an interpreter-specific directory
debian/*/usr/lib/python3.x/dist-packages, and then dh_python3 moves it
to debian/*/usr/lib/python3/dist-packages/ only if the files are
identical. If the files differ for each interpreter, then dh_python3
complains loudly and leaves them where they are.

execute_after_dh_python3:
# Drop cov-generated files
rm -fv debian/*/usr/lib/python3/dist-packages/.coverage
rm -fvr debian/*/usr/lib/python3/dist-packages/htmlcov

When python3-all started to include python3.12 as a supported
interpreter, these files came back, for example:

2   
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61___init___py.html
3   
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61_advanced_py.html
4   
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61_aggregate_py.html
5   
usr/lib/python3.12/dist-packages/htmlcov/d_880e183adc9afb61_combine_py.html

Widening the removal pattern to be 'python3*' is sufficient. (Perhaps
dh_python3 should add these directories to its list of well-known
directories to not include in the package.)

Thanks to Paul Gevers for noticing this in various tests with britney to
include reproducibility output in migrations.



Bug#840160: RFP: mullvad-client

2023-12-04 Thread zachqpublic
Dear Ben & Debian Devs,

May I be of help revitalising this ITP for the Mullvad VPN client?  They 
provide a DEB and RPM.

Kindly,
Zach Cuipylo


Bug#1057431: fakeupstream.cgi: add support for static.rust-lang.org

2023-12-04 Thread Zixing Liu
Package: qa.debian.org
Severity: wishlist
Tags: patch
X-Debbugs-Cc: zixing@canonical.com

Hi Debian QA Team,

I would like to see a fakeupstream service implemented for 
https://static.rust-lang.org/dist so that the debian/watch file inside the
rustc package could be simplified and actually useful for checking new
releases.

Attached below is a patch that I proposed to add the said functionality.
You can find the same patch at:
 https://salsa.debian.org/qa/qa/-/merge_requests/48
if you prefer using Debian Salsa to merge the patch/merge request.

Thanks,
Zixing
>From 9bbd2ecffe31822cf2a77ed0ce9ed69f78931aee Mon Sep 17 00:00:00 2001
From: liushuyu 
Date: Mon, 23 Oct 2023 22:27:29 -0600
Subject: [PATCH] cgi-bin/fakeupstream.cgi: add support ...

... for monitoring Rust releases
---
 cgi-bin/fakeupstream.cgi | 77 
 1 file changed, 77 insertions(+)

diff --git a/cgi-bin/fakeupstream.cgi b/cgi-bin/fakeupstream.cgi
index c13538e8..718b2540 100755
--- a/cgi-bin/fakeupstream.cgi
+++ b/cgi-bin/fakeupstream.cgi
@@ -26,6 +26,8 @@ use JSON;
 use File::Temp qw/ tempdir /;
 use Date::Format;
 use Date::Parse;
+use Time::Piece;
+use Time::Seconds qw(ONE_DAY);
 use Dpkg::Version;
 use threads;
 use constant MAX_THREADS => 3;
@@ -1110,6 +1112,81 @@ elsif( $upstream_param =~ 
m%^google-fonts/($project_char_re+)/($project_char_re+
exit 0;
 }
 
+elsif( $upstream_param eq 'rustc' )
+{
+   my $ua = LWP::UserAgent->new;
+
+   sub fetch_rust_github_tags($) {
+   my $ua = shift;
+   my @versions;
+   my $page_number = 1;
+   my $per_page = 100;
+   my $url = 
"https://api.github.com/repos/rust-lang/rust/tags?per_page=$per_page;;
+   while (1) {
+   my $response = $ua->get( "$url=$page_number" );
+   return_error( "failed to read $url : 
$response->status_line" ) if( not $response->is_success );
+   my $json = JSON::decode_json( 
$response->decoded_content );
+   foreach my $version (@{$json}) {
+   my $version_name = $version->{"name"};
+   if ( $version_name =~ /^\d+\.\d+\.\d+$/ ) {
+   push @versions, $version_name;
+   }
+   }
+   last if (scalar @versions) < $per_page;
+   }
+   $page_number++;
+   return @versions;
+   }
+
+   sub fetch_rust_last_unstable_date($$) {
+   my $ua = shift;
+   my $channel = shift;
+   my $url = 
"https://static.rust-lang.org/dist/channel-rust-$channel-date.txt;;
+   my $response = $ua->get ( $url );
+   return_error( "failed to read $url : $response->status_line" ) 
unless( $response->is_success );
+   return $response->decoded_content;
+   }
+
+   sub make_header($) {
+   my $channel = shift;
+   my $title = "Rust toolchain version listing ($channel)";
+   print $q->header;
+   print $q->start_html({ -title => $title });
+   print $q->h1($title) . "\n";
+   print $q->start_ul;
+   }
+
+   $type_param = 'stable' unless $type_param;
+   my $channel = $type_param;
+
+   if ($channel eq 'stable') {
+   my @tags = fetch_rust_github_tags( $ua );
+   make_header($channel);
+   foreach my $version (@tags) {
+   print $q->li( $q->a( { -href => 
"https://static.rust-lang.org/dist/rustc-$version-src.tar.xz; }, $version ) );
+   }
+   } else {
+   my $last_date = fetch_rust_last_unstable_date ( $ua, $channel );
+   my $limit = 10;
+   make_header($channel);
+   print $q->p( "For unstable channels, only releases within the 
last $limit days are listed." );
+   while ($limit > 0) {
+   my $response = $ua->get( 
"https://static.rust-lang.org/dist/$last_date/channel-rust-$channel.toml; );
+   if ($response->is_success()) {
+   if ($response->decoded_content =~ 
/(1\.\d+\.\d+-(?:nightly|beta)(?:\.\d+)?\s+\([0-9a-f]{9}\s+\d+-\d+-\d+\))/) {
+   print $q->li( $q->a( { -href => 
"https://static.rust-lang.org/dist/$last_date/rustc-$channel-src.tar.xz; }, $1 
) );
+   }
+   }
+   my $next_last_date = Time::Piece->strptime($last_date, 
"%Y-%m-%d") - ONE_DAY;
+   $last_date = $next_last_date->ymd;
+   $limit--;
+   }
+   }
+
+   print $q->end_ul;
+   print $q->end_html;
+   exit 0;
+}
 
 my %upstream_info_per_package =
 (
-- 
GitLab



Bug#1057385: lighttpd FTCBFS: host CFLAGS leak into build compiler invocation

2023-12-04 Thread Johannes Schauer Marin Rodrigues
Hi,

Quoting Emanuele Rocca (2023-12-04 11:49:30)
> some compiler flags are architecture specific and should not leak when
> cross-building.
> 
> As an example, -fcf-protection is x86-specific, and the following fails:
> 
>  aarch64-linux-gnu-gcc-13 -fcf-protection
> 
> Similarly, -mbranch-protection=standard is aarch64-specific, and the
> following fails:
> 
>  x86_64-linux-gnu-gcc-13 -mbranch-protection=standard
> 
> With the attached patch lighttpd cleanly cross-builds from source.

note, that *_FOR_BUILD variables are new in dpkg 1.22.1.

You can get flags that work even before that by running:

CFLAGS_FOR_BUILD ?= $(shell dpkg-architecture --host-arch $(DEB_BUILD_ARCH) 
--force --command dpkg-buildflags --get CFLAGS)

Thanks!

cheers, josch

signature.asc
Description: signature


Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Michael Biebl

The code to exclude lost+found appears to be still there:
https://github.com/systemd/systemd/blob/main/src/tmpfiles/tmpfiles.c#L720

Can you create a lost+found directory and then run
SYSTEMD_LOG_LEVEL=debug systemd-tmpfiles --prefix /tmp

?


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Michael Biebl
On Mon, 4 Dec 2023 20:39:21 +0100 Axel Scheepers 
 wrote:

On Mon, Dec 4, 2023 at 8:27 PM Luca Boccassi  wrote:
> But the main point is, it's fine if you do a custom local setup with
> the appropriate local configuration, but then you also need to add the
> appropriate config for tmpfiles.d. You can either mask or replace
> tmp.conf, simply add your own file as /etc/tmpfiles.d/tmp.conf and it
> will have priority, and do what you need for your custom local setup.

Oh, ok. I admit I have a traditional unix background where it's common
practice to have these a separate real partitions instead. I'll just keep
the exception I already made then. I have some users on the system
which sometimes store larger things in there.


debian-installer offers a partition setup with separate /home, /var and 
/tmp very prominently (see attached screenshot).


Whether this is still a good idea nowadays is debatable.
As Luca said, if we offer /tmp as a separate partition, it should 
probably be tmpfs now and not an (ext4/xfs/...) partition.


For reference, I also include the legacy cleanup routine for SysV:
https://salsa.debian.org/debian/sysvinit/-/blob/master/debian/src/initscripts/lib/init/bootclean.sh#L119-128

So if there should be an exclusion for lost+found (for ext4), there 
should probably also be exclusion for quota related files.


Whether those exclusions should be shipped directly by systemd or 
created by d-i (as suggested by Luca on IRC), is something I don't have 
a strong opinion about. The downside of letting d-i create such a 
tmpfiles snippet is that we wouldn't cover existing systems.


As for d-i itself, my preferred solution for this would be to change it 
to uses tmpfs for /tmp.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245465
(that's an old bug report)


Michael



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057430: ring: FTBFS: configure: error: sdbus-c++ not found

2023-12-04 Thread Sebastian Ramacher
Source: ring
Version: 20230922.0~ds2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=ring=amd64=20230922.0%7Eds2-1%2Bb1=1701601320=0

checking for zlib... yes
checking for libgit2 >= 1.1.0... yes
checking for libpjproject... yes
checking for yaml-cpp >= 0.5.1... yes
checking for yaml-cpp >= 0.5.1... yes
checking for jsoncpp >= 1.6.5... yes
checking for alsa >= 1.0... yes
checking for libpulse >= 0.9.15... yes
checking for jack... no
checking for sdbus-c++... no
configure: error: sdbus-c++ not found
make[1]: *** [debian/rules:31: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'

Cheers
-- 
Sebastian Ramacher



Bug#1057429: Additional info

2023-12-04 Thread Andreas Girlich
Please note that the cause of this issue was setting mail_plugins = 
sieve in 10-mail.conf


loading `sieve` in 20-lmtp.conf with mail_plugins = $mail_plugins sieve 
fixed this issue and the package is usable.


thanks
agi


OpenPGP_0x2978C23E94E01845.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

2023-12-04 Thread Fabio Fantoni

Il 04/12/2023 22:14, Holger Schröder ha scritto:



The same thing happens when you try to build Cinnamon 6.0.0


https://github.com/linuxmint/cinnamon


/hsp


Is not related to cinnamon itself but to latest gobject-introspection 
changes in sid/testing


I don't know what is the good way to fix it, a possibile workaround I 
suppose is add provide for each gir but it doesn't seem like a good idea 
add 6 provides in a muffin package


I'll try to see if someone recommend something better, otherwise I'll 
try anyway






OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057429: dovecot-sieve: sieve binaries abort with exit code 89 due to missing symbol

2023-12-04 Thread Andreas Girlich
Package: dovecot-sieve
Version: 1:2.3.19.1+dfsg1-2.1
Severity: important
Tags: upstream

Dear Maintainer,

   * What led up to the situation?
   Installed dovecot-sieve and compiling/testing simple sieve script
   with sievec and sieve-test

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

create simple sieve script:
~$ cat sieve
require "fileinto";
if header :contains "X-Spam-Flag" "YES" {
fileinto "Junk";
}

~$ sievec sieve
sievec(agi): Fatal: Couldn't load required plugin 
/usr/lib/dovecot/modules/lib90_sieve_plugin.so: dlopen() failed: 
/usr/lib/dovecot/modules/lib90_sieve_plugin.so: undefined symbol: 
mail_deliver_ctx_get_log_var_expand_table

   * What was the outcome of this action?
   sievec and sieve-test abort operation

   * What outcome did you expect instead?
   compiling simple sieve script


-- Package-specific info:

dovecot configuration
-
# 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.19 (4eae2f79)
# OS: Linux 6.1.0-13-amd64 x86_64 Debian 12.2 ext4
# Hostname: apu.don.error23.de
auth_username_format = %Ln
mail_location = maildir:/media/storage/mail/%u
mail_plugins = sieve
mail_privileged_group = mail
namespace inbox {
  inbox = yes
  location = 
  mailbox Drafts {
special_use = \Drafts
  }
  mailbox Junk {
special_use = \Junk
  }
  mailbox Sent {
special_use = \Sent
  }
  mailbox "Sent Messages" {
special_use = \Sent
  }
  mailbox Trash {
special_use = \Trash
  }
  prefix = 
}
passdb {
  driver = pam
}
plugin {
  sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = " imap lmtp"
service imap-login {
  inet_listener imaps {
port = 993
ssl = yes
  }
}
service lmtp {
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
  }
}
ssl_cert = 
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.3.19.1+dfsg1-2.1
pn  dovecot-ldap   
ii  dovecot-lmtpd  1:2.3.19.1+dfsg1-2.1
pn  dovecot-managesieved   
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
ii  dovecot-sieve  1:2.3.19.1+dfsg1-2.1
pn  dovecot-sqlite 

-- no debconf information



Bug#1057391: cinnamon: FTBFS: dh_girepository: error: Could not find Clutter-0.gir dependency

2023-12-04 Thread Holger Schröder


The same thing happens when you try to build Cinnamon 6.0.0


https://github.com/linuxmint/cinnamon


/hsp



Bug#1057424: libmodule-build-perl: Multi-Arch: foreign makes other packages FTBFS

2023-12-04 Thread gregor herrmann
On Mon, 04 Dec 2023 21:59:12 +0200, Niko Tyni wrote:

> The libnet-cidr-set-perl and libparams-validate-perl packages
> fail to build from source in current unstable.

> This is because libmodule-build-perl was recently marked
> Multi-Arch:foreign, but dpkg-checkbuilddeps does not consider that as
> satisfying :native build dependencies, see #1023438.

Oh dear :/
(I added Multi-Arch:foreign because I wanted to cross-build a
package, and I already had the gut feeling that his might be
dangerous …)
 
> My understanding is that M-A:foreign is probably the right thing
> to do here, but we need to remove the :native build dependency
> in other packages first. Fortunately I see only two in the archive,
> libnet-cidr-set-perl and libparams-validate-perl.
> 
>   grep-dctrl -sPackage,Build-Depends,Build-Depends-Indep 
> -FBuild-Depends,Build-Depends-Indep -r 'libmodule-build-perl[^,]*:native' 
> /var/lib/apt/lists/*_main_source_Sources

Thanks for this research!
 
> Filing against libmodule-build-perl for now to prevent it from entering
> trixie before the other two are changed. Feel free to reassign or clone
> or whatever if you like.

Both fixed (by removing the :native) and uploaded.

I guess we could upload libmodule-build-perl with versioned Breaks on
the 2 packages (and close this bug with the upload) to get the
migration/upgrade order right?
 

Cheers,
gregor

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


signature.asc
Description: Digital Signature


Bug#1057363: RM: twitterwatch -- RoQA; Upstream Dead; Useless with Twitter API Changes

2023-12-04 Thread Miguel Landaeta
On Mon, Dec 4, 2023 at 12:09 AM Boyuan Yang  wrote:
>
> [...]
>
> Dear Debian FTP Masters,
>
> As discussed in https://bugs.debian.org/1056613 , package twitterwatch makes 
> use
> of Twitter API, which is gone since 2023. Its upstream shows no activity for 
> 7 years,
> and the Debian package received no maintainer updates since 2016. As a 
> result, I
> believe we should have package twitterwatch removed from Debian archive.
>

Hi Boyuan,

Thanks for submitting this bug.

Do you have any objection to doing the same for db2twitter and retweet packages?

I think they are in the same situation.

Cheers,
Miguel.


-- 
Miguel Landaeta, miguel at miguel.cc
secure email with PGP 0x6E608B637D8967E9 available at http://keyserver.pgp.com/
"Faith means not wanting to know what is true." -- Nietzsche



Bug#1057428: libseccomp ftbfs on i386

2023-12-04 Thread Matthias Klose

Package: src:libseccomp
Version: 2.5.4-2
Severity: serious
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: python3.12

libseccomp ftbfs on i386. probably not related to Python 3.12, but 
blocks the addition of Python 3.12


[...]
Test 59-basic-empty_binary_tree%%001-00351 result:   SUCCESS
 test mode:  c
 test type:  bpf-valgrind
./regression: line 271: 1444558 Illegal instruction valgrind 
--tool=memcheck --error-exitcode=1 --leak-check=full --read-var-info=yes 
--track-origins=yes --suppressions=./valgrind_test.supp --quiet 
--log-fd=4 -- ./59-basic-empty_binary_tree -b
Test 59-basic-empty_binary_tree%%002-1 result:   FAILURE 
59-basic-empty_binary_tree rc=132

Regression Test Summary
 tests run: 8570
 tests skipped: 78
 tests passed: 8533
 tests failed: 37
 tests errored: 0

FAIL: regression
==
1 of 1 test failed
==
make[3]: *** [Makefile:1424: check-TESTS] Error 1



Bug#1057407: texworks: Intent to drop poppler-qt6 on i386

2023-12-04 Thread Preuße

On 04.12.2023 14:43, Jeremy Bícha wrote:

Hi Jeremy,


texworks is the only package that uses poppler's Qt6 in Debian. Please
let me know if it's ok with you if texworks is no longer built for
i386 in Debian.



I personally stopped using i386 about 9 years ago, so in my personal 
opinion it is OK. According to [1] i386 is still on 2nd rank, still 7 
times higher than the 3rd rank arm64, but only 1/22 of amd64.


Can we switch back to QT5 (on i386) or would this not be helpful? Are 
there popcon statistics per package?


Hilmar

[1] https://popcon.debian.org/
--
sigfault



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1052349: bolt FTBFS when systemdsystemunitdir changes in systemd.pc or udevdir changes in udev.pc

2023-12-04 Thread Chris Hofstaedtler
Control: severity -1 serious

* Helmut Grohne  [231204 20:52]:
> [..] When the relevant .pc files change, bolt will FTBFS. I'm
> attaching a patch to avoid that.

systemd.pc has already changed, and bolt now FTBFS, like this:

...
Installing /<>/obj-x86_64-linux-gnu/bolt.service to 
/<>/debian/tmp/usr/lib/systemd/system
Installing /<>/data/90-bolt.rules to 
/<>/debian/tmp/lib/udev/rules.d
...
   dh_install
dh_install: warning: Cannot find (any matches for) "lib/systemd" (tried in ., 
debian/tmp)

dh_install: warning: bolt missing files: lib/systemd
dh_install: error: missing files, aborting
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


Best,
Chris



Bug#1057427: ansible-core: CVE-2023-5764: internal templating can cause unsafe variables to lose their unsafe designation

2023-12-04 Thread Salvatore Bonaccorso
Source: ansible-core
Version: 2.14.11-2
Severity: important
Tags: security upstream
Forwarded: https://github.com/ansible/ansible/pull/82295 
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for ansible-core.

CVE-2023-5764[0]:
| internal templating can cause unsafe variables to lose their unsafe
| designation


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-5764
https://www.cve.org/CVERecord?id=CVE-2023-5764
[1] https://github.com/ansible/ansible/pull/82295 

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#1057425: RFP: noisetorch -- Real-time microphone noise suppression on Linux.

2023-12-04 Thread Joerg Jaspert
Package: wnpp
Severity: wishlist

* Package name: noisetorch
  Version : 0.12.2
  Upstream Contact: https://github.com/noisetorch
* URL : https://github.com/noisetorch
* License : GPL
  Programming Lang: Go
  Description : Real-time microphone noise suppression on Linux.

NoiseTorch-ng is an easy to use open source application for Linux with
PulseAudio or PipeWire. It creates a virtual microphone that
suppresses noise in any application using RNNoise. Use whichever
conferencing or VOIP application you like and simply select the
filtered Virtual Microphone as input to torch the sound of your
mechanical keyboard, computer fans, trains and the likes.



Bug#1057321: gcolor3: cursor doesn't change to dropper and fails to get info of clicked colour

2023-12-04 Thread Derek Griffin
On Mon, 2023-12-04 at 17:20 +0800, Chow Loong Jin wrote:
> On Sun, Dec 03, 2023 at 12:04:08PM +, Derek Griffin wrote:
> > Package: gcolor3
> > Version: 2.4.0-2
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > I attempted to use gcolor3 as intended but when I clicked the
> > dropper
> > icon. The
> > cursor didn't change to a dropper and when clicking a colour
> > anywhere
> > on screen
> > the program doesn't get any info.
> > 
> > When running the program from a terminal the following error is
> > reported:
> > 
> > Failed to pick color:
> > GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No
> > such interface “org.freedesktop.portal.Screenshot” on object at
> > path
> > /org/freedesktop/portal/desktop
> > 
> >    * What outcome did you expect instead?
> > 
> > The hex values of the selected colour to appear in the gcolor3
> > window.
> > 
> > The colour pickers in GIMP and Geany work as expected.
> > 
> > I use XFCE4. Please ask for more information.
> 
> Please try installing xdg-desktop-portal-xapp, and seeing if that
> helps.
> 
Thanks for the reply.

Sadly xdg-desktop-portal-xapp isn't available in Debian 12.

https://packages.debian.org/search?suite=all=all=any=names=xdg-desktop-portal-xapp

I looked at the package in testing but because the version of xapps-
common in stable is too old it will be uninstallable.

Kind regards,

Derek.

Resubmitting because for some reason this message wasn't sent to the
bugs.debian.org.



Bug#1057416: Acknowledgement (ntpsec: Corrupted filtdelay/filtoffset/filtdisp in peer variables)

2023-12-04 Thread Bill Sommerfeld

It looks like this was fixed upstream earlier this year in this commit:

https://gitlab.com/NTPsec/ntpsec/-/commit/9931ebb3d1418b648f80510a86520a4d11bab3d6

The relevant bit is the change to ctl_putarray() to set buffer[0] = 0;

It does not appear that this fix has appeared in a release yet.

Exposing stack garbage like this runs the hard-to-quantify risk that 
keying material could be exposed over the network.


See also https://gitlab.com/NTPsec/ntpsec/-/issues/806 which is another 
manifestation of this bug (depending on the stack garbage, it can cause 
other ntpq subcommands to fail).




Bug#1056974: php-dompdf: providing .ufm files

2023-12-04 Thread William Desportes

Control: tags -1 - wontfix

Hi,

I was wrong while doing my research about the licensing, sorry about 
that.



I think that solution provided by Robin Gustafsson should fix my issue.


Definitely !
I approved the PR and should proceed into sending it to unstable 
shortly.


Thank you all for participating on this bug

--
William



Bug#1057423: logback: CVE-2023-6378

2023-12-04 Thread Salvatore Bonaccorso
On Mon, Dec 04, 2023 at 08:57:52PM +0100, Salvatore Bonaccorso wrote:
> Source: logback
> Version: 1:1.2.11-4
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 
> Control: found -1 1:1.2.11-3
> 
> Hi,
> 
> The following vulnerability was published for logback.
> 
> CVE-2023-6378[0]:
> | A serialization vulnerability in logback receiver component part of
> | logback version 1.4.11 allows an attacker to mount a Denial-Of-
> | Service  attack by sending poisoned data.
> 
> 
> 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-6378
> https://www.cve.org/CVERecord?id=CVE-2023-6378
> [1] 
> https://github.com/qos-ch/logback/commit/b8eac23a9de9e05fb6d51160b3f46acd91af9731

The fix for the 1.2.x series is
https://github.com/qos-ch/logback/commit/bb095154be011267b64e37a1d401546e7cc2b7c3

Regards,
Salvatore



Bug#1057005: linux-image-6.1.0-13-amd64: Kernel Oops in nfs4_do_reclaim, which exits with irqs disabled

2023-12-04 Thread Salvatore Bonaccorso
Control: tags -1 + moreinfo

Hi James,

On Mon, Nov 27, 2023 at 08:00:52PM +, James Chapman wrote:
> Package: src:linux
> Version: 6.1.55-1
> Severity: important
> X-Debbugs-Cc: jamescope...@gmail.com
> 
> Dear Maintainer,
> 
> Hi, I have experienced an issue where my client lost access to an
> NFS server for a period of around 15 minutes, then immediately
> following server recovery, I experienced a kernel oops on the client
> (details below). What made this more severe was the fact that
> nfs4_do_reclaim exited with irqs disabled, which is possibly what
> resulted in a number of "rcu_preempt self-detected stall on CPU"
> errors and a very unstable system, leaving me no choice but to hit
> the reset button.

Are you able to reproduce the issue? otherwise it is quite hard to
make any assessment for this bug.

Regards,
Salvatore



Bug#1056371: RFS: streamlink/6.4.2-1 -- CLI for extracting video streams from various websites to a video player

2023-12-04 Thread Alexis Murzeau

Control: retitle -1 RFS: streamlink/6.4.2-1 -- CLI for extracting video streams 
from various websites to a video player

Package: sponsorship-requests
Severity: normal


Dear mentors,

I am looking for a sponsor for my package "streamlink" for a new
upstream version 6.4.2.
This replaces the previous RFS for version 6.4.0-1 (#1056371).

  * Package name: streamlink
Version : 6.4.2-1
Upstream Author : Streamlink Team
  * URL : https://streamlink.github.io/
  * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1
  * Vcs : https://salsa.debian.org/amurzeau/streamlink/
Section : python

It builds those binary packages:
  python3-streamlink - Python module for extracting video streams from
various websites
  python3-streamlink-doc - CLI for extracting video streams from
various websites (documentation)
  streamlink - CLI for extracting video streams from various websites
to a video player


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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_6.4.2-1.dsc


Changes since the last upload to unstable:
streamlink (6.4.2-1) unstable; urgency=medium

  * New upstream version 6.4.2
  * d/control: remove obsolete omxplayer from recommends
  * d/rules: remove now useless pybuild flag --install-scripts

 -- Alexis Murzeau   Mon, 04 Dec 2023 20:17:11 +0100

Regards,

--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC  2787 E7BD 1904 F480 937F|


OpenPGP_0xE7BD1904F480937F.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057424: libmodule-build-perl: Multi-Arch: foreign makes other packages FTBFS

2023-12-04 Thread Niko Tyni
Package: libmodule-build-perl
Version: 0.423400-2
Severity: serious
Tags: ftbfs
Control: affects -1 libnet-cidr-set-perl libparams-validate-perl
X-Debbugs-Cc: debian-cr...@lists.debian.org
Control: block 1055955 with -1

The libnet-cidr-set-perl and libparams-validate-perl packages
fail to build from source in current unstable.

>From a full build log at

 
http://perl.debian.net/rebuild-logs/sid/libparams-validate-perl_1.31-1/libparams-validate-perl_1.31-1.buildlog

  Command: dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -Zxz
  dpkg-buildpackage: info: source package libparams-validate-perl
  dpkg-buildpackage: info: source version 1.31-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by gregor herrmann 
   dpkg-source -Zxz --before-build .
  dpkg-buildpackage: info: host architecture amd64
  dpkg-checkbuilddeps: error: Unmet build dependencies: 
libmodule-build-perl:native
  dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
  dpkg-buildpackage: warning: (Use -d flag to override.)
 
This is because libmodule-build-perl was recently marked
Multi-Arch:foreign, but dpkg-checkbuilddeps does not consider that as
satisfying :native build dependencies, see #1023438.

My understanding is that M-A:foreign is probably the right thing
to do here, but we need to remove the :native build dependency
in other packages first. Fortunately I see only two in the archive,
libnet-cidr-set-perl and libparams-validate-perl.

  grep-dctrl -sPackage,Build-Depends,Build-Depends-Indep 
-FBuild-Depends,Build-Depends-Indep -r 'libmodule-build-perl[^,]*:native' 
/var/lib/apt/lists/*_main_source_Sources

Filing against libmodule-build-perl for now to prevent it from entering
trixie before the other two are changed. Feel free to reassign or clone
or whatever if you like.

As libparams-validate-perl is an arch:any XS module, we need to fix it
one way or another before the Perl 5.38 transition. So marking this as
a blocker.

Copying the debian-cross list in case I got something wrong :)
-- 
Niko Tyni   nt...@debian.org



Bug#1057423: logback: CVE-2023-6378

2023-12-04 Thread Salvatore Bonaccorso
Source: logback
Version: 1:1.2.11-4
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 1:1.2.11-3

Hi,

The following vulnerability was published for logback.

CVE-2023-6378[0]:
| A serialization vulnerability in logback receiver component part of
| logback version 1.4.11 allows an attacker to mount a Denial-Of-
| Service  attack by sending poisoned data.


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-6378
https://www.cve.org/CVERecord?id=CVE-2023-6378
[1] 
https://github.com/qos-ch/logback/commit/b8eac23a9de9e05fb6d51160b3f46acd91af9731

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#1057422: gnucash: please update homepage and source URLs to https

2023-12-04 Thread Vincent Lefevre
Package: gnucash
Version: 1:5.4-2
Severity: minor

The homepage URL should be changed from

  http://www.gnucash.org/

to

  https://www.gnucash.org/

Ditto for the source URL in the copyright file:

  http://sourceforge.net/projects/gnucash/files/gnucash%20(stable)/

to

  https://sourceforge.net/projects/gnucash/files/gnucash%20(stable)/

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

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

Versions of packages gnucash depends on:
ii  gnucash-common 1:5.4-2
ii  guile-3.0  3.0.8-2+b1
ii  guile-3.0-libs 3.0.8-2+b1
ii  libaqbanking44 6.5.4-2
ii  libboost-filesystem1.74.0  1.74.0+ds1-23
ii  libboost-locale1.74.0  1.74.0+ds1-23
ii  libboost-program-options1.74.0 1.74.0+ds1-23
ii  libboost-regex1.74.0 [libboost-regex1.74.0-icu72]  1.74.0+ds1-23
ii  libc6  2.37-13
ii  libcairo2  1.18.0-1
ii  libcrypt-ssleay-perl   0.73.06-2+b1
ii  libdate-manip-perl 6.93-1
ii  libdbi10.9.0-6
ii  libfinance-quote-perl  1.58-1
ii  libgcc-s1  13.2.0-8
ii  libgdk-pixbuf-2.0-02.42.10+dfsg-3
ii  libglib2.0-0   2.78.1-4
ii  libgtk-3-0 3.24.38-6
ii  libgwengui-gtk3-79 5.10.2-2
ii  libgwenhywfar795.10.2-2
ii  libhtml-tableextract-perl  2.15-2
ii  libhtml-tree-perl  5.07-3
ii  libicu72   72.1-4
ii  libofx71:0.10.9-1
ii  libpango-1.0-0 1.51.0+ds-3
ii  libpangocairo-1.0-01.51.0+ds-3
ii  libpython3.11  3.11.6-3
ii  libsecret-1-0  0.21.1-1
ii  libstdc++6 13.2.0-8
ii  libwebkit2gtk-4.0-37   2.42.2-1
ii  libwww-perl6.72-1
ii  libxml22.9.14+dfsg-1.3
ii  perl   5.36.0-10
ii  zlib1g 1:1.3.dfsg-3

Versions of packages gnucash recommends:
ii  gnucash-docs 5.4-1
ii  python3-gnucash  1:5.4-2
ii  yelp 42.2-1

Versions of packages gnucash suggests:
pn  libdbd-mysql
pn  libdbd-pgsql
pn  libdbd-sqlite3  

-- no debconf information

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



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Axel Scheepers
On Mon, Dec 4, 2023 at 8:27 PM Luca Boccassi  wrote:
> But the main point is, it's fine if you do a custom local setup with
> the appropriate local configuration, but then you also need to add the
> appropriate config for tmpfiles.d. You can either mask or replace
> tmp.conf, simply add your own file as /etc/tmpfiles.d/tmp.conf and it
> will have priority, and do what you need for your custom local setup.

Oh, ok. I admit I have a traditional unix background where it's common
practice to have these a separate real partitions instead. I'll just keep
the exception I already made then. I have some users on the system
which sometimes store larger things in there.

Thanks,
Kind regards,

Axel



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Luca Boccassi
On Mon, 4 Dec 2023 at 19:15, Axel Scheepers  wrote:
>
> On Mon, Dec 4, 2023 at 6:58 PM Luca Boccassi  wrote:
> > You have a separate, non-tmpfs filesystem on /tmp? How did you end up
> > with such a setup?
>
> Hi Luca,
>
> I always configure separate /var, /tmp and /home filesystems. In this case
> the system is also low on ram so tmpfs is not really an option (I think?).
> Is using tmpfs the preferred way to handle this on debian? Or maybe ext4
> as a filesystem is not preferred in this case?

I think the default is simply a directory in the rootfs in Debian -
the more common setup is to have a tmpfs on it.

But the main point is, it's fine if you do a custom local setup with
the appropriate local configuration, but then you also need to add the
appropriate config for tmpfiles.d. You can either mask or replace
tmp.conf, simply add your own file as /etc/tmpfiles.d/tmp.conf and it
will have priority, and do what you need for your custom local setup.



Bug#1057421: sysstat: FTBFS: dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" (tried in ., debian/tmp)

2023-12-04 Thread Chris Hofstaedtler
Source: sysstat
Version: 12.6.1-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

systemd.pc changed systemd_system_unit_dir to point to /usr. As a
consequence, your package now FTBFS in unstable. Due to a human
mistake this problem was not caught before making the change; we'd
like to apologize.

FTBFS log snippet:
>> if [ -n "/usr/lib/systemd/system" -a -n "/usr/lib/systemd/system-sleep" -a 
>> -d "/<>/debian/tmp/usr/lib/systemd/system-sleep" ]; then \
>>  install -m 755 cron/sysstat.sleep 
>> /<>/debian/tmp/usr/lib/systemd/system-sleep; \
>> fi
>> make[2]: Leaving directory '/<>'
>> mv /<>/debian/tmp/usr/bin/sar 
>> /<>/debian/tmp/usr/bin/sar.sysstat
>> mv /<>/debian/tmp/usr/share/man/man1/sar.1 
>> /<>/debian/tmp/usr/share/man/man1/sar.sysstat.1
>> rm -rf /<>/debian/tmp/usr/doc
>> make[1]: Leaving directory '/<>'
>>dh_install
>> dh_install: warning: Cannot find (any matches for) "debian/tmp/lib/systemd/" 
>> (tried in ., debian/tmp)
>> 
>> dh_install: warning: sysstat missing files: debian/tmp/lib/systemd/
>> dh_install: error: missing files, aborting
>> make: *** [debian/rules:23: binary] Error 25
>> dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
>> status 2


It seems likely you'll need to adapt a debhelper .install file for
the /usr path.

Note: if you intend to backport your package to bookworm or earlier,
please revert any changes for moving to /usr.

Best,
Chris



sysstat_12.6.1-1.gz
Description: application/gzip


Bug#1057420: cfengine3: FTBFS: dh_install: warning: cfengine3 missing files: debian/tmp/lib/systemd

2023-12-04 Thread Chris Hofstaedtler
Source: cfengine3
Version: 3.21.0-3
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

systemd.pc changed systemd_system_unit_dir to point to /usr. As a
consequence, your package now FTBFS in unstable. Due to a human
mistake this problem was not caught before making the change; we'd
like to apologize.

FTBFS log snippet:
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install --exclude=examples --exclude=ChangeLog
dh_install: warning: Cannot find (any matches for)
"debian/tmp/lib/systemd" (tried in ., debian/tmp)

dh_install: warning: cfengine3 missing files: debian/tmp/lib/systemd
dh_install: error: missing files, aborting
make[1]: *** [debian/rules:70: override_dh_install] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:16: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess
returned exit status 2


It seems likely you'll need to adapt a debhelper .install file for
the /usr path.

Note: if you intend to backport your package to bookworm or earlier,
please revert any changes for moving to /usr.

Best,
Chris



cfengine3_3.21.0-3.gz
Description: application/gzip


Bug#1057385: lighttpd FTCBFS: host CFLAGS leak into build compiler invocation

2023-12-04 Thread Helmut Grohne
Hi Glenn,

On Mon, Dec 04, 2023 at 10:11:21AM -0500, gs-bugs.debian@gluelogic.com 
wrote:
> On Mon, Dec 04, 2023 at 11:49:30AM +0100, Emanuele Rocca wrote:
> > With the attached patch lighttpd cleanly cross-builds from source.
> 
> Thanks, Emanuele.
> 
> A slightly different patch:
> 
> https://salsa.debian.org/debian/lighttpd/-/commit/a7d695d59c9a8bffe154aae29e335102beaaf3f2
> 
> was committed a few weeks ago to salsa.debian.org, which I based off
> comments in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021292?
> 
> Is your suggested approach (above) preferred to this patch (below)?
> 
> @@ -50,9 +50,9 @@ override_dh_auto_configure:
>   --with-xxhash \
>   --with-zstd \
>   $(if $(filter 
> pkg.lighttpd.libunwind,$(DEB_BUILD_PROFILES)),--with-libunwind) \
> - CFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CFLAGS)" \
> - LDFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get LDFLAGS)" \
> - CPPFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CPPFLAGS)" \
> + CFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f 
> -c dpkg-buildflags --get CFLAGS)" \
> + LDFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f 
> -c dpkg-buildflags --get LDFLAGS)" \
> + CPPFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f 
> -c dpkg-buildflags --get CPPFLAGS)" \
>  
>  override_dh_install:
>   cp NEWS debian/tmp/changelog
> 

Good question!

CFLAGS_FOR_BUILD is a really recent thing in dpkg available since
1.22.1. For going backwards, I suppose CFLAGS_FOR_BUILD will be unknown
and dpkg-buildflags will fail without outputting something. Then empty
build flags tend to work. For going forward, CFLAGS_FOR_BUILD definitely
is something we want to embrace more.

In any case, thanks for handling the issue on your side already.

Helmut



Bug#1057419: consolekit2 FTCBFS: configures twice - once for the build architecture and fails

2023-12-04 Thread Helmut Grohne
Source: consolekit2
Version: 1.2.6-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

consolekit2 fails to cross build from source, because it configures
twice. The first time is during autogen.sh for the build architecture
and this fails. This run is unnecessary and only happens, because
NOCONFIGURE is mis-spelled in debian/rules. I'm attaching a patch for
your convenience.

Unfortunately, this does not make consolekit2 cross builable as it has a
gobject scanner executable that is run during build. This is not
currently fixable. Please close this bug anyway.

Helmut
diff --minimal -Nru consolekit2-1.2.6/debian/changelog 
consolekit2-1.2.6/debian/changelog
--- consolekit2-1.2.6/debian/changelog  2023-11-16 13:42:48.0 +0100
+++ consolekit2-1.2.6/debian/changelog  2023-12-04 15:23:48.0 +0100
@@ -1,3 +1,10 @@
+consolekit2 (1.2.6-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Improve cross building: Fix spelling of NOCONFIGURE. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 04 Dec 2023 15:23:48 +0100
+
 consolekit2 (1.2.6-3) unstable; urgency=medium
 
   * License appstream metainfo as FSFAP.
diff --minimal -Nru consolekit2-1.2.6/debian/rules 
consolekit2-1.2.6/debian/rules
--- consolekit2-1.2.6/debian/rules  2023-11-16 13:42:48.0 +0100
+++ consolekit2-1.2.6/debian/rules  2023-12-04 15:23:47.0 +0100
@@ -17,7 +17,7 @@
# As XDT macros are present in configure.ac, plain dh_autoreconf runs
# xdt-autogen, see #893746; but that invokes glib-gettextize which 
creates an
# incompatible po/Makefile.in.in.  So ensure ./autogen.sh itself is run.
-   NO_CONFIGURE=1 dh_autoreconf --as-needed ./autogen.sh
+   NOCONFIGURE=1 dh_autoreconf --as-needed ./autogen.sh
 
 override_dh_auto_configure:
dh_auto_configure -- $(CONFFLAGS) \


Bug#1057339: dash FTCBFS: host CFLAGS leak into build compiler invocation

2023-12-04 Thread Helmut Grohne
On Sun, Dec 03, 2023 at 11:10:35AM +0100, Helmut Grohne wrote:
> So here is a patch for dash that adds CFLAGS_FOR_BUILD support and thus
> solves this instance. I think there are many more of this and appreciate
> help with fixing them. Thanks in advance.

IRC user punit made me aware of a typo in the patch.

Helmut
--- dash-0.5.12.orig/configure.ac
+++ dash-0.5.12/configure.ac
@@ -15,11 +15,17 @@
 AC_MSG_CHECKING([for build system compiler])
 if test "$cross_compiling" = yes; then
 	CC_FOR_BUILD=${CC_FOR_BUILD-cc}
+	CFLAGS_FOR_BUILD=${CFLAGS_FOR_BUILD-}
+	CPPFLAGS_FOR_BUILD=${CPPFLAGS_FOR_BUILD-}
 else
 	CC_FOR_BUILD=${CC}
+	CFLAGS_FOR_BUILD=${CFLAGS}
+	CPPFLAGS_FOR_BUILD=${CPPFLAGS}
 fi
 AC_MSG_RESULT(${CC_FOR_BUILD})
 AC_SUBST(CC_FOR_BUILD)
+AC_SUBST(CFLAGS_FOR_BUILD)
+AC_SUBST(CPPFLAGS_FOR_BUILD)
 
 AC_MSG_CHECKING([for __attribute__((__alias__()))])
 dash_cv_have_attribute_alias=no
--- dash-0.5.12.orig/src/Makefile.am
+++ dash-0.5.12/src/Makefile.am
@@ -12,7 +12,7 @@
 COMPILE_FOR_BUILD = \
 	$(CC_FOR_BUILD) $(DEFAULT_INCLUDES) $(AM_CPPFLAGS_FOR_BUILD) \
 	$(CPPFLAGS_FOR_BUILD) \
-	$(CPPFLAGS) $(CFLAGS) $(LDFLAGS) \
+	$(LDFLAGS) \
 	$(AM_CFLAGS_FOR_BUILD) $(CFLAGS_FOR_BUILD) 
 
 bin_PROGRAMS = dash


Bug#1057418: Mark consul as EOLed in Bullseye

2023-12-04 Thread Moritz Muehlenhoff
Source: debian-security-support
Version: 1:13+2023.09.27
Severity: wishlist

Hashicorp changed the license of Consul and MPLed patches are onky
provided until Dec 31. As such, it has been removed from unstable
and needs to be EOLed for bullseye (removal from bullseye isn't
simple, it would require source uploads to packages like Prometheus
currently building with Consul support).



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Axel Scheepers
On Mon, Dec 4, 2023 at 6:58 PM Luca Boccassi  wrote:
> You have a separate, non-tmpfs filesystem on /tmp? How did you end up
> with such a setup?

Hi Luca,

I always configure separate /var, /tmp and /home filesystems. In this case
the system is also low on ram so tmpfs is not really an option (I think?).
Is using tmpfs the preferred way to handle this on debian? Or maybe ext4
as a filesystem is not preferred in this case?

Kind regards,
Axel



Bug#1056998: cdrom: Installation media changes after booting it

2023-12-04 Thread Nicholas Geovanis
On Mon, Dec 4, 2023, 3:30 AM Thomas Schmitt  wrote:

> .
> This seems to indicate that the firmware has a stake in the problem ...
>
> > Both the Thinkpad E14 Gen 5s had the same specifications and type number,
> > differing only in that the one with corruption of the installer has 24GB
> of
> > memory (16GB installed in the slot, 8GB soldered) and the other only has
> 8GB
> > soldered. They both have the same BIOS version, R2AET32W(1.07).
>
> ... but the trigger would have to be very subtle.
>
> > This seems to be really interesting because the corruption only happened
> on
> > certain computers, and it would stay that way on repeated attempts.
>


FWIW check the BIOS L[123] cache settings and consider changing them to
more conservative "slower" values if possible. And you have different RAM
models and configurations, could there be one DIMM in the mix that is
running overclocked?

Have a nice day :)
>
> Thomas
>

Grüß Gott :-)


Bug#1057205: The fedora 39 builds using the works on ppc64le

2023-12-04 Thread William Cohen
Hi,

I have noticed a similar problem on riscv64 openSUSE Tumbleweed 
(gcc13-13.2.1+git7813-6.2.riscv64), but everything builds fine on all the 
fedora 39 and rawhide architectures.  These builds include ppc64le.

fedora 39: https://koji.fedoraproject.org/koji/buildinfo?buildID=2321551
fedora rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=2321548

I don't know what the difference are between the ppc64le Debian and Fedora 
environments, but that would be a starting point to to figure out why systemtap 
isn't compiling on Debian.

-Will Cohen



Bug#1008698: libprelude: nmu ongoing

2023-12-04 Thread Gianfranco Costamagna

control: tags -1 patch pending

Dear maintainer,

I've prepared an NMU for libprelude (versioned as 5.2.0-5.2) and
uploaded it.

diff attached

G.
diff -Nru libprelude-5.2.0/debian/changelog libprelude-5.2.0/debian/changelog
--- libprelude-5.2.0/debian/changelog   2023-12-04 11:34:12.0 +0100
+++ libprelude-5.2.0/debian/changelog   2023-12-04 19:30:14.0 +0100
@@ -1,3 +1,20 @@
+libprelude (5.2.0-5.2) unstable; urgency=medium
+
+  [ Gianfranco Costamagna ]
+  * Non-maintainer upload.
+  * Mark 3 symbols as optional, disappearing with -O3 on ppc64el
+(Closes: #1056401)
+  * Also move from libltdl3-dev to libltdl-dev in libprelude-dev
+package (Closes: #1008698)
+
+  [ Helmut Grohne ]
+  * Fix FTCBFS: (Closes: #1022963)
++ Use declarative ruby addon.
++ export cross variables for perl, python and ruby
++ cross.patch: Fix bare and useless pkg-config invocation.
+
+ -- Gianfranco Costamagna   Mon, 04 Dec 2023 
19:30:14 +0100
+
 libprelude (5.2.0-5.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libprelude-5.2.0/debian/control libprelude-5.2.0/debian/control
--- libprelude-5.2.0/debian/control 2021-08-29 10:39:10.0 +0200
+++ libprelude-5.2.0/debian/control 2023-12-04 19:30:14.0 +0100
@@ -6,8 +6,8 @@
 Rules-Requires-Root: no
 Build-Depends: debhelper-compat (= 13),
 dh-sequence-python3 ,
+dh-sequence-ruby ,
 gawk,
-gem2deb ,
 libgcrypt20-dev,
 libgnutls28-dev,
 libltdl-dev,
@@ -30,7 +30,7 @@
 Architecture: any
 Suggests: libprelude-doc
 Depends: libprelude28 (= ${binary:Version}), libpreludecpp12 (= 
${binary:Version}), libgnutls28-dev,
- libgcrypt20-dev, libltdl3-dev, ${misc:Depends}
+ libgcrypt20-dev, libltdl-dev, ${misc:Depends}
 Description: Security Information and Events Management system [ Development 
files ]
  The Prelude Library is a collection of generic functions providing
  communication between the Prelude SIEM suite components. It provides a
diff -Nru libprelude-5.2.0/debian/libpreludecpp12.symbols 
libprelude-5.2.0/debian/libpreludecpp12.symbols
--- libprelude-5.2.0/debian/libpreludecpp12.symbols 2021-11-03 
19:53:39.0 +0100
+++ libprelude-5.2.0/debian/libpreludecpp12.symbols 2023-12-04 
19:30:12.0 +0100
@@ -366,9 +366,9 @@
  
(optional)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 4.1
  
(optional)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC1IS3_EEPKcRKS3_@Base
 5.2.0
  
(optional)_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2IS3_EEPKcRKS3_@Base
 5.2.0
- _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 5.0.0
- _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 5.0.0
- _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 5.0.0
+ (optional)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 
5.0.0
+ (optional)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 
5.0.0
+ (optional)_ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 
5.0.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOS5_EESJ_IJESt17_Rb_tree_iteratorIS8_ESt23_Rb_tree_const_iteratorIS8_EDpOT_@Base
 5.0.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 5.0.0
  
(optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 5.0.0
diff -Nru libprelude-5.2.0/debian/patches/cross.patch 
libprelude-5.2.0/debian/patches/cross.patch
--- libprelude-5.2.0/debian/patches/cross.patch 1970-01-01 01:00:00.0 
+0100
+++ libprelude-5.2.0/debian/patches/cross.patch 2023-12-04 19:30:14.0 
+0100
@@ -0,0 +1,11 @@
+--- libprelude-5.2.0.orig/m4/am_path_ruby.m4
 libprelude-5.2.0/m4/am_path_ruby.m4
+@@ -100,7 +100,7 @@
+ 
+   dnl if PKG-CONFIG is available, we use it. Else, we try to dectect 
RUBY_INCLUDES manually
+   RUBY_VER=`$RUBY -rrbconfig -e "print RbConfig::CONFIG[['ruby_pc']]" | sed 
's/.pc//g'`
+-  PKG_CHECK_MODULES(RUBY_PKG_CONFIG, $RUBY_VER, [RUBY_INCLUDES=`pkg-config 
$RUBY_VER --cflags`], [RUBY_INCLUDES=`$RUBY -r rbconfig -e '
++  PKG_CHECK_MODULES(RUBY_PKG_CONFIG, $RUBY_VER, 
[RUBY_INCLUDES=$RUBY_PKG_CONFIG_CFLAGS], [RUBY_INCLUDES=`$RUBY -r rbconfig -e '
+if RbConfig::CONFIG[["archdir"]] then print " -I" + 
RbConfig::CONFIG[["archdir"]] end
+if RbConfig::CONFIG[["rubyhdrdir"]] then print " -I" + 
RbConfig::CONFIG[["rubyhdrdir"]] end
+if RbConfig::CONFIG[["rubyhdrdir"]] and 
RbConfig::CONFIG[["sitearch"]] then print " -I" + 
RbConfig::CONFIG[["rubyhdrdir"]] + "/" + 

Bug#1042818: firmware-amd-graphics: GPU freezes, monitors not working with kernel 6.0 and version 20230625-1

2023-12-04 Thread Raphaël Gomès
Package: firmware-amd-graphics
Followup-For: Bug #1042818
X-Debbugs-Cc: alphar...@gmail.com

Dear Maintainer,

I think the most relevant new information is that after installing
20230625-1 from 20230515-3 on kernel version 6.0.0-2, I had the random
freezes mentioned above.

Also, only my DP monitor would output anything, and my wayland compositor
would try to make sense of them in a loop, leading to a very unresponsive
system (freezes, missed keystrokes, repeated keystrokes) and other things
like keyboard settings not being applied because the config reload process
got interrupted.

I tried upgrading to linux 6.5.0-5, which didn't do anything. Still on that
version, I manually installed 20230515-4 (instead of the original -3, but
I don't think this makes a difference) and everything is working fine.

The workaround for drm kernel parameters did not work for me unfortunately.

Thanks,
Raphaël Gomès

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

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

firmware-amd-graphics depends on no packages.

firmware-amd-graphics recommends no packages.

Versions of packages firmware-amd-graphics suggests:
ii  initramfs-tools  0.142

-- debconf-show failed


Bug#1056998: cdrom: Installation media changes after booting it

2023-12-04 Thread Thomas Schmitt
Hi,

Ram Reddy wrote:
> https://drive.google.com/file/d/1Zd6iufVRsfIu-qzC-tJx4FEvCOESOz4_/view?usp=sharing

I downloaded the tarball and compared the original FAT filesystem with the
various modified filesystem images.

--

In Legion7iG5-*_modified.esp the suspect lost its ID card at the crime
scene:
At byte 39072 (0x98a0) the changes go from 0-bytes to the text "LENOVO".
At byte 9711680 (0x943040) i see a change from 0-bytes to "BIOS".

Diffing the result of "find" on the mounted unmodified.esp filesystem and
Legion7iG5-*_modified.esp shows that a new branch of directoriies with a
new file is in each of the modified filesystems:
  > ./efi/Lenovo
  > ./efi/Lenovo/BIOS
  > ./efi/Lenovo/BIOS/SelfHealing.fd
The file is empty.

--

In ThinkpadX1CarbonG5-0_modified.esp there is no company name to see in
the changed bytes. I see UTF-16 strings "mation", "System", and
"Volum\000me". ASCII texts "SYSTEM~1", "WPSETT~1DAT". The latter might
possibly be "WPSettings.dat", which causes questions in the internet.
Most plausible seems an answer in the course of
  
https://answers.microsoft.com/en-us/insider/forum/all/whats-wpsettingsdat-generated-by/e11bca97-8c76-4662-8897-774ea3d5691a
  "The WPSettings.dat file is generated by the Storage Service (StorSvc).
   It seems that WPSettings.dat means the data files of Windows Phone's
   Store Settings saved on the drives, [...]"

Diffing the result of "find" on the mounted unmodified.esp filesystem and
ThinkpadX1CarbonG5-0_modified.esp shows that a new directory with a new
file is in the modified filesystem:
  ./System Volume Information
  ./System Volume Information/WPSettings.dat
The file has 12 bytes of binary salad:
  Hex:   0c  00  00  00  2e  42  6b  82  5d  88  0e  c5
  Char:   .   B   k   ]
  Dec:   12   0   0   0  46  66 107 130  93 136  14 197

--

While it makes some sense to me that Lenovo Legion BIOS adds some Lenovo
stuff to the EFI System Partition, i really wonder why Lenovo Thinkpad
BIOS adds a Microsoft directory and file.

Whatever, i'd say that the software in the ISO and especially Debian
Installer are not suspicious to create directories with such names.


Have a nice day :)

Thomas



Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Luca Boccassi
Control: tags -1 moreinfo

On Mon, 04 Dec 2023 18:47:29 +0100 Axel Scheepers
 wrote:
> Package: systemd
> Version: 252.17-1~deb12u1
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
> (previous bug at #788193).
> 
> Automatic run of e2scrub reported:
> 
> So sorry, the automatic e2scrub of /tmp on
mahogany.vultrusercontent.com failed.
> 
> A log of what happened follows:
> × e2scrub@-tmp.service - Online ext4 Metadata Check for /tmp
>  Loaded: loaded (/lib/systemd/system/e2scrub@.service; static)
>  Active: failed (Result: exit-code) since Sun 2023-12-03 03:11:03
> CET; 137ms ago
>    Docs: man:e2scrub(8)
> Process: 25375 ExecStart=/sbin/e2scrub -t /tmp (code=exited,
> status=1/FAILURE)
>    Main PID: 25375 (code=exited, status=1/FAILURE)
> CPU: 227ms

You have a separate, non-tmpfs filesystem on /tmp? How did you end up
with such a setup?

-- 
Kind regards,
Luca Boccassi


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


Bug#1057417: systemd tmpfiles seems to delete lost+found again

2023-12-04 Thread Axel Scheepers
Package: systemd
Version: 252.17-1~deb12u1
Severity: normal
Tags: patch

Dear Maintainer,

   * What led up to the situation?

(previous bug at #788193).

Automatic run of e2scrub reported:

So sorry, the automatic e2scrub of /tmp on mahogany.vultrusercontent.com failed.

A log of what happened follows:
× e2scrub@-tmp.service - Online ext4 Metadata Check for /tmp
 Loaded: loaded (/lib/systemd/system/e2scrub@.service; static)
 Active: failed (Result: exit-code) since Sun 2023-12-03 03:11:03
CET; 137ms ago
   Docs: man:e2scrub(8)
Process: 25375 ExecStart=/sbin/e2scrub -t /tmp (code=exited,
status=1/FAILURE)
   Main PID: 25375 (code=exited, status=1/FAILURE)
CPU: 227ms

Dec 03 03:11:00 mahogany systemd[1]: Starting e2scrub@-tmp.service -
Online ext4 Metadata Check for /tmp...
Dec 03 03:11:01 mahogany e2scrub@-tmp[25387]:   Logical volume
"tmp.e2scrub" created.
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: e2fsck 1.47.0 (5-Feb-2023)
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 1: Checking inodes,
blocks, and sizes
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 2: Checking
directory structure
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 3: Checking
directory connectivity
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: /lost+found not found.
Create? yes
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 4: Checking reference counts
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: Pass 5: Checking group
summary information
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: /dev/system/tmp.e2scrub:
* FILE SYSTEM WAS MODIFIED *
Dec 03 03:11:01 mahogany e2scrub@-tmp[25415]: /dev/system/tmp.e2scrub:
21/124928 files (0.0% non-contiguous), 17515/499712 blocks
Dec 03 03:11:01 mahogany e2scrub@-tmp[25375]: /tmp: Scrub FAILED due
to corruption!  Unmount and run e2fsck -y.
Dec 03 03:11:01 mahogany e2scrub@-tmp[25420]: tune2fs 1.47.0 (5-Feb-2023)
Dec 03 03:11:01 mahogany e2scrub@-tmp[25420]: Setting filesystem error
flag to force fsck.
Dec 03 03:11:01 mahogany e2scrub@-tmp[25422]:   Logical volume
"tmp.e2scrub" successfully removed.
Dec 03 03:11:03 mahogany systemd[1]: e2scrub@-tmp.service: Main
process exited, code=exited, status=1/FAILURE
Dec 03 03:11:03 mahogany systemd[1]: e2scrub@-tmp.service: Failed with
result 'exit-code'.
Dec 03 03:11:03 mahogany systemd[1]: Failed to start
e2scrub@-tmp.service - Online ext4 Metadata Check for /tmp.
Dec 03 03:11:03 mahogany systemd[1]: e2scrub@-tmp.service: Triggering
OnFailure= dependencies.


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

Ineffective: put /tmp on a separate filesystem, effective; add lost+found
to /usr/lib/tmpfiles.d;

 cat /usr/lib/tmpfiles.d/tmp-lost-and-found.conf 
x   /tmp/lost+found


I can't find an exeption in the source nor in /usr/lib/tmpfiles.d/*
root@mahogany:/tmp/src/systemd-252.17/src/tmpfiles# ed tmpfiles.c 
158825
/.journal
   ".journal",
-3,+3n
764 S_ISREG(sx.stx_mode) &&
765 sx.stx_uid == 0 &&
766 STR_IN_SET(de->d_name,
767".journal",
768"aquota.user",
769"aquota.group")) {
770 log_debug("Skipping \"%s\".", sub_path);

Maybe I'm missing something but if not can it be added to either
/usr/lib/tmpfiles.d or as a patch to tmpfiles.c?
I can confirm adding it to tmpfiles.d solves the problem for me.

Happy holidays, kind regards,

Axel

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  libacl12.3.1-3
ii  libaudit1  1:3.0.9-1
ii  libblkid1  2.38.1-5+b1
ii  libc6  2.36-9+deb12u3
ii  libcap21:2.66-4
ii  libcryptsetup122:2.6.1-4~deb12u1
ii  libfdisk1  2.38.1-5+b1
ii  libgcrypt201.10.1-3
ii  libkmod2   30+20221128-1
ii  liblz4-1   1.9.4-1
ii  liblzma5   5.4.1-0.2
ii  libmount1  2.38.1-5+b1
ii  libp11-kit00.24.1-2
ii  libseccomp22.5.4-1+b3
ii  libselinux13.4-1+b6
ii  libssl33.0.11-1~deb12u2
ii  libsystemd-shared  252.17-1~deb12u1
ii  libsystemd0252.17-1~deb12u1
ii  libzstd1   1.5.4+dfsg2-5
ii  mount  2.38.1-5+b1

Versions of packages systemd recommends:
ii  dbus [default-dbus-system-bus]   1.14.10-1~deb12u1
ii  systemd-timesyncd [time-daemon]  252.17-1~deb12u1

Versions of 

Bug#1057416: ntpsec: Corrupted filtdelay/filtoffset/filtdisp in peer variables

2023-12-04 Thread Bill Sommerfeld

Package: ntpsec
Version: 1.2.2+dfsg1-1+deb12u1
Severity: important

Dear Maintainer,

It appears that ntpsec's ntpd returns corrupted values in the "filtdelay",
"filtoffset" and "filtdisp" peer variables visible via ntpq.

reproducer:

$ ntpq
ntpq> peers
(output elided)
ntpq> rv &1 filtdelay filtoffset filtdisp

Expected output:
three lines of 8 numbers for each variable read, looking something like:

filtdelay=17.10   17.20   12.35   14.43   14.71   13.64   14.70   14.46,
filtoffset=   +3.57   +1.58   +0.39   +0.02   +1.04   +0.59   +0.40   -0.56,
filtdisp=  0.00   15.89   31.37   47.39   63.08   78.60   94.13  109.65

Actual output is prefaced with garbage characters and repeated values from the
other variables:

filtdelay=M- M-W}M-HM-^?^? 0.48 0.48 0.47 0.36 0.48 0.45 0.49 0.37?,
filtoffset=M- M-W}M-HM-^?^? 0.48 0.48 0.47 0.36 0.48 0.45 0.49 0.37 -0.52 0.92 
1.32 0.93 1.03 0.45 1.02 2.04?,
filtdisp=M- M-W}M-HM-^?^? 0.48 0.48 0.47 0.36 0.48 0.45 0.49 0.37 -0.52 0.92 
1.32 0.93 1.03 0.45 1.02 2.04 0.00 15.95 31.31 47.42 63.18 78.90 95.03 110.45?

Why I think the bug is in ntpd and not in ntpq:

I see the expected output for these variables when using ntpsec's ntpq to
query another system, and I also see the erroneous output when using that
other system's ntpq to query the debian ntpsec ntpd.

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

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

Versions of packages ntpsec depends on:
ii  adduser3.134
ii  init-system-helpers1.65.2
ii  libbsd00.11.7-2
ii  libc6  2.36-9+deb12u3
ii  libcap21:2.66-4
ii  libssl33.0.11-1~deb12u2
ii  lsb-base   11.6
ii  netbase6.4
ii  python33.11.2-1+b1
ii  python3-ntp1.2.2+dfsg1-1+deb12u1
ii  sysvinit-utils [lsb-base]  3.06-4
ii  tzdata 2023c-5

Versions of packages ntpsec recommends:
ii  cron [cron-daemon]  3.0pl1-162
ii  systemd 252.17-1~deb12u1

Versions of packages ntpsec suggests:
ii  apparmor   3.0.8-3
pn  certbot
ii  ntpsec-doc 1.2.2+dfsg1-1+deb12u1
pn  ntpsec-ntpviz  

-- Configuration Files:
/etc/ntpsec/ntp.conf changed:
driftfile /var/lib/ntpsec/ntp.drift
statistics loopstats peerstats clockstats
filegen loopstats file loopstats type day enable
filegen peerstats file peerstats type day enable
filegen clockstats file clockstats type day enable
restrict -4 default kod notrap nomodify nopeer noquery limited
restrict -6 default kod notrap nomodify nopeer noquery limited
restrict 127.0.0.1
restrict ::1
restrict source notrap nomodify noquery
restrict 192.168.0.0 mask 255.255.0.0 kod notrap nomodify nopeer limited
server hydra.hamachi.org iburst
server the-governor.hamachi.org iburst
server time.cloudflare.com iburst
server time.apple.com iburst
pool 2.us.pool.ntp.org iburst


-- no debconf information



Bug#1055085: waiting for 3.12.1

2023-12-04 Thread Graham Inggs
Control: tags -1 + confirmed

On Thu, 30 Nov 2023 at 10:03, Matthias Klose  wrote:
>
> wait until 3.12.1 is in the archive. 3.12.0+ isn't well handled as a
> version by some third party libraries.

binNMUs are now in progress with python3.12 3.12.0-7 in unstable.

python3.12 (3.12.0-7) unstable; urgency=medium

  * Update to the 3.12 branch 2023-12-02.
  * Identify as version "3.12.0" instead of "3.12.0+", confusing some
third party packages.
  * Remove references to the avr architecture. Closes: #1056761.
  * Fix more shebangs. Closes: #1057192.

 -- Matthias Klose   Sat, 02 Dec 2023 13:35:02 +0100



Bug#1026953: package updated

2023-12-04 Thread Bobby de Vos

Greetings,

The watch file has been fixed, and the latest version, now 3.000, has
been uploaded.

--
Bobby de Vos
/bobby_de...@sil.org/

Bug#709156: fonts-sil-abyssinica: new release should resolve issues

2023-12-04 Thread Bobby de Vos

Greetings,

I recently uploaded a new version of the Abyssinica font (2.201) and all 
the issues reported should be resolved with this upload (if not before).


Bobby

--
Bobby de Vos
/bobby_de...@sil.org/

Bug#1057381: FTBFS: error: invalid use of incomplete typedef ‘WINDOW’

2023-12-04 Thread Sven Joachim
Control: tags -1 + trixie sid patch

On 2023-12-04 10:38 +0100, Chris Hofstaedtler wrote:

> Source: aalib
> Version: 1.4p5-50
> Severity: serious
> Tags: ftbfs
>
> Rebuilding your package in unstable currently fails:
>
>
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -Wdate-time
> -D_FORTIFY_SOURCE=2 -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong
> -fstack-clash-protection -Wformat -Werror=format-security
> -fcf-protection -I/usr/include -I/usr/include/ncurses -c aacurses.c
> -fPIC -DPIC -o .libs/aacurses.o
> aacurses.c: In function ‘curses_getsize’:
> aacurses.c:80:20: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>80 | *width = stdscr->_maxx + 1;
>   |^~
> aacurses.c:81:21: error: invalid use of incomplete typedef ‘WINDOW’ {aka 
> ‘struct _win_st’}
>81 | *height = stdscr->_maxy + 1;
>   | ^~
> make[4]: *** [Makefile:726: aacurses.lo] Error 1

This has been caused by a recent change in ncurses which makes the
WINDOW structure opaque.  Accessing its members directly is no longer
possible, you need to use library functions to obtain window dimensions
and positions.  In the current case, this would be getmaxyx(), see the
attached patch.

See the ncurses INSTALL file:

,
| --enable-opaque-curses
| --enable-opaque-form
| --enable-opaque-menu
| --enable-opaque-panel
|   Define symbol in curses.h controlling whether some library structures
|   are opaque, meaning that their members are accessible only via the
|   documented API.  The --enable-opaque-curses option may be overridden
|   by the --enable-reentrant option.
| 
|   Enabling opaque-curses enables opaque for the form, menu, and panel
|   libraries.  Use their corresponding options to disable the feature
|   individually.
| 
|   NOTE: beginning with ncurses 6.5 this option is enabled by default;
|   older versions disable it by default.
`

While ncurses 6.5 has not been released yet, the change has already been
made in the patchlevel Debian is shipping.  From the NEWS file:

,
| 20231021
|   + change defaults for configure opaque and widec options (prompted by
| discussion with Branden Robinson).
`

Cheers,
   Sven (ncurses maintainer in Debian)

From 033d7355157688eb3bc224b973b130f42d5664b1 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Mon, 4 Dec 2023 17:45:59 +0100
Subject: [PATCH] Use getmaxyx() to obtain width and height

Ncurses patchlevel 20231021 made the WINDOW scructure opaque, so it is
no longer possible to directly access its members, leading to FTBFS.

Closes: #1057381
---
 src/aacurses.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/aacurses.c b/src/aacurses.c
index dc3b220..ae7e097 100644
--- a/src/aacurses.c
+++ b/src/aacurses.c
@@ -77,8 +77,7 @@ static void curses_getsize(aa_context * c, int *width, int *height)
 {
 if (__resized_curses)
 	curses_uninit(c), curses_init(>params, NULL,>driverparams, NULL), __resized_curses = 0;
-*width = stdscr->_maxx + 1;
-*height = stdscr->_maxy + 1;
+getmaxyx(stdscr, *width, *height);
 #ifdef GPM_MOUSEDRIVER
 gpm_mx = *width;
 gpm_my = *height;
--
2.43.0



Bug#1056998: cdrom: Installation media changes after booting it

2023-12-04 Thread Ram Reddy
Hi,
Thomas Schmitt wrote:
> Maybe we can learn more by comparing the files /boot/grub/efi.img of the
> original ISO and of an altered USB stick.
>  iso=/dev/sdX
> and then
>  dd bs=512 if="$iso" of="$iso".esp skip=4476 count=18976
I tried doing that for the times the drive was modified, and they are here:
https://drive.google.com/file/d/1Zd6iufVRsfIu-qzC-tJx4FEvCOESOz4_/view?usp=sharing
Each modification was unique, so I put them all there. The files are for
the 3 most recent attempts I did. G = gen, and the number after - is the
attempt number. For the ones with no modifications, there's a text file
with unmodified in its name which contains "unmodified" in it.
unmodified.esp is the unmodified ESP in the installer.

However, I found some interesting results. I tried redoing the tests on
each laptop, and found that the modifications occurred somewhat randomly.
Laptop Model | Test 1 | Test 2 | Test 3 | Test 4 | Test 5
Lenovo Legion 7i gen 5   | modded | modded | modded | modded | modded
Thinkpad X1 Carbon gen 2 | modded | modded |unmodded|unmodded|unmodded
Thinkpad X1 Carbon gen 5 | modded | modded | modded |unmodded|unmodded
Thinkpad E14 Gen 5 Intel | modded |unmodded|unmodded|unmodded|unmodded
Thinkpad E14 Gen 5 Intel |unmodded|unmodded|unmodded|unmodded|unmodded
Lenovo Yoga C740 |unmodded|unmodded|unmodded|unmodded|unmodded
modded = modificationed
It did show some patterns, however.

Have an awe-inspiring day,
Ram


Bug#1057415: ITP: golang-github-ghjm-cmdline -- Command line parser with multiple configurations for the Go language

2023-12-04 Thread Jérémy Lal
Package: wnpp
Severity: wishlist
Owner: Jérémy Lal 
X-Debbugs-Cc: debian-de...@lists.debian.org, Debian Go Packaging Team 


* Package name: golang-github-ghjm-cmdline
  Version : 0.1.2
  Upstream Contact: Graham Mainwaring
* URL : https://github.com/ghjm/cmdline
* License : Apache-2.0
  Programming Lang: Golang
  Description : Command line parser with multiple configurations for the Go 
language

 This package provides a parsing and execution framework based on
 the idea that structs define accepted fields, receiver functions,
 and execution phases.
 It is more general than the common Go language command line parser.

This is needed by receptor, a cli needed by awx.
I plan to team-maintain it within pkg-go team.

Jérémy


Bug#1056908: tzdata: Support IANA time zones

2023-12-04 Thread Benjamin Drung
On Mon, 2023-12-04 at 10:31 -0500, John Clark wrote:
> On 12/4/23 10:13 AM, Benjamin Drung wrote:
> > Hi,
> > 
> > On Sun, 2023-11-26 at 09:23 -0500, John Clark wrote:
> > > Package: tzdata
> > > Version: 2023c-8
> > > 
> > > The 12 well-known US time zones have been dropped from Debian tzdata as
> > > of 2023c-8:
> > > https://tracker.debian.org/news/1451157/accepted-tzdata-2023c-8-source-into-unstable
> > > 
> > > These time zones are still officially recognized and fully supported by
> > > IANA.
> > > 
> > > IANA Timezone Database:
> > > https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
> > > 
> > > /usr/share/zoneinfo/US/Alaska
> > > /usr/share/zoneinfo/US/Aleutian
> > > /usr/share/zoneinfo/US/Arizona
> > > /usr/share/zoneinfo/US/Central
> > > /usr/share/zoneinfo/US/East-Indiana
> > > /usr/share/zoneinfo/US/Eastern
> > > /usr/share/zoneinfo/US/Hawaii
> > > /usr/share/zoneinfo/US/Indiana-Starke
> > > /usr/share/zoneinfo/US/Michigan
> > > /usr/share/zoneinfo/US/Mountain
> > > /usr/share/zoneinfo/US/Pacific
> > > /usr/share/zoneinfo/US/Samoa
> > > 
> > > 
> > > Their removal appears to be related to this request:
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040997
> > > 
> > > This request does not provide any support as to why Debian should
> > > deviate from IANA standards.
> > > 
> > > Requesting that Debian again adopt international time zone standards and
> > > support these well known IANA time zones as it does in Bookworm.
> > These timezones are considered legacy by the upstream tz project. These
> > timezones were not removed but moved to tzdata-legacy. So please install
> > tzdata-legacy if you want to use them:
> > 
> > sudo apt install tzdata-legacy
> > 
> I looked for deprecations in the upstream project but did not find any.  
> Can you cite any IANA deprecation references?

All legacy names are mentioned in the backward file [1]. The backward
file has an explanation at the beginning of the file. It is also
mentioned on theory.html[2].

[1] https://github.com/eggert/tz/blob/main/backward
[2] https://data.iana.org/time-zones/theory.html

-- 
Benjamin Drung
Debian & Ubuntu Developer



Bug#1057360: python-pyscss: PCRE support missing due to incomplete migration

2023-12-04 Thread Boyuan Yang
Control: forwarded 1057360 https://github.com/Kronuz/pyScss/issues/429

Hi,

在 2023-12-04星期一的 00:17 +,Stefano Rivera写道:
> Hi Boyuan (2023.12.03_23:15:02_+)
> > The packaged python-pyscss/1.4.0-3 claimed to migrate from PCRE to PCRE2. 
> > However,
> > the project has not supported PCRE2 yet [1]. The current migration [2] 
> > effectively
> > disabled the PCRE support as shown in build logs.
> > 
> > As a result, we should not claim to have migrated from old PCRE to PCRE2, 
> > and we
> > should enable PCRE2 support in the future once upstream has made the switch.
> 
> It's not clear to me what the next steps you're asking for entail.
> 
> Can you provide patches?

I believe it is mostly for documentation purpose so that this TODO is not 
forgotten in
future package updates.

Thanks,
Boyuan Yang


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


Bug#1057414: kicad: Please enable EGL support

2023-12-04 Thread Sebastian Reichel
Package: kicad
Version: 7.0.9+dfsg-1
Severity: normal

Dear Maintainer,

Without EGL, KiCAD experience on Wayland can be quite bad even when
using XWayland. At least on AMD GPU based systems, there are ~10 second
lags when switching between PCB and Schematics windows on two different
Wayland workspaces.

I've seen commit 5a3af461df6fc6e4be868399277ea4134e703773 ("Revert
"d/rules: Turn option KICAD_USE_EGL on" ), but I think it would be
better to enable EGL support in libglew, libwxwidgets and KiCAD
instead of disabling it everywhere.

At the moment GLX is used on XWayland and that is missing some
workarounds for SwapBuffers(). For EGL wxwidgets already has the
necessary code to disable vsync. See also upstream bugs:

https://gitlab.freedesktop.org/mesa/mesa/-/issues/10235
https://github.com/wxWidgets/wxWidgets/issues/23512

I asked for the workaround to also be implemented for the GLX API,
but I believe it's a good idea to enable EGL in Debian even if that
happens.

P.S.: If anyone runs into the lag issue and finds this bug: You can
run KiCAD like this as a workaround: `vblank_mode=0 /usr/bin/kicad`.

Thanks,

-- Sebastian

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

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

Versions of packages kicad depends on:
ii  libc62.37-12
ii  libcairo21.18.0-1
ii  libcurl4 8.4.0-2
ii  libfontconfig1   2.14.2-6
ii  libfreetype6 2.13.2+dfsg-1
ii  libgcc-s113.2.0-7
ii  libgl1   1.7.0-1
ii  libglew2.2   2.2.0-4+b1
ii  libglib2.0-0 2.78.1-4
ii  libglu1-mesa [libglu1]   9.0.2-1.1
ii  libgtk-3-0   3.24.38-6
ii  libharfbuzz0b8.0.1-1
ii  libngspice0  41+ds-1
ii  libocct-data-exchange-7.67.6.3+dfsg1-7
ii  libocct-foundation-7.6   7.6.3+dfsg1-7
ii  libocct-modeling-algorithms-7.6  7.6.3+dfsg1-7
ii  libocct-modeling-data-7.67.6.3+dfsg1-7
ii  libocct-ocaf-7.6 7.6.3+dfsg1-7
ii  libodbc2 2.3.12-1
ii  libpixman-1-00.42.2-1
ii  libpython3.113.11.6-3
ii  libstdc++6   13.2.0-7
ii  libwxbase3.2-1   3.2.4+dfsg-1
ii  libwxgtk-gl3.2-1 3.2.4+dfsg-1
ii  libwxgtk3.2-13.2.4+dfsg-1
ii  python3  3.11.4-5+b1
ii  python3-wxgtk4.0 4.2.1+dfsg-1
ii  zlib1g   1:1.2.13.dfsg-3

Versions of packages kicad recommends:
pn  kicad-demos  
ii  kicad-libraries  7.0.9+dfsg-1
ii  xsltproc 1.1.35-1

Versions of packages kicad suggests:
pn  extra-xdg-menus 
pn  kicad-doc-ca | kicad-doc-de | kicad-doc-en | kicad-doc-es | kicad-  
doc-fr | kicad-doc-id | kicad-doc-it | kicad-doc-ja | kicad-doc-pl
 | kicad-doc-ru | kicad-doc-zh
ii  kicad-packages3d7.0.9-1

-- no debconf information



Bug#1053548: check-patroni: does not work well with current Patroni

2023-12-04 Thread Michael Banck
Hi David,

On Mon, Oct 23, 2023 at 07:17:11PM +0200, David Prévot wrote:
> First of all thanks a lot for your bug report!

Sorry that it took me so long to reply now :-/
 
> Le Fri, Oct 06, 2023 at 09:11:32AM +0200, Michael Banck a écrit :
> > Package: check-patroni
> > Version: 1.0.0-1
> > Severity: normal
> > Tags: patch
> > 
> > Hi,
> > 
> > since version 3.0.4, Patroni displays "streaming" as state if a node is
> > actually replicating from its leader. This is taken into account by
> > check-patroni 1.0.0 (see https://github.com/dalibo/check_patroni/pull/30). 
> […]
> 
> I was hoping to answer to your message sooner, and dig deeper into your
> advises, but couldn’t find the time yet, and I’m afraid I won’t have
> much time until at least a few weeks. So please consider this message as
> an apology and an acknowledgement of the various issues and fixes you
> pointed.
> 
> > Actually, I did not realize you had uploaded check-patroni and
> > independently packaged it for the pkg-postgres team here:
> > https://salsa.debian.org/postgresql/check-patroni
> 
> Ha, I quickly prepared this package during DebConf and didn’t try to
> reach out to the Python or PostgreSQL teams, so thanks for the heads up.
> FWIW, I’d be happy to move the packaging under the PostgreSQL team
> umbrella if it makes sense.

So, what are your plans? I can offer to take over the packaging of
check-patroni as part of the Postgres team; I'd move the git to
salsa.debian.org/postgresql and merge in a few of the things I did
differently.

If you want to go ahead and keep maintaining this, that'd be fine as
well of course.


Cheers,

Michael



Bug#1053509: shasta: autopkgtest regression on arm64: is memory suddenly not enough?

2023-12-04 Thread Étienne Mollier
Alright, I think I managed to get somewhere with the program's
configuration options: using an older reference config from
2019, shasta doesn't look to  reserve itself unnecessary amounts
of memory, and the test should now go through.  If this works,
we can forget about checking available memory on the host, and
the Ubuntu specific change (apparently, Steve Langasek disabled
the first command of the test suite, which explains why there
were no issues on this operating system).

I will push an updated autopkgtest soon to close the issue.

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


signature.asc
Description: PGP signature


Bug#1051392: closed by Debian FTP Masters (reply to Guillem Jover ) (Bug#1051392: fixed in victoriametrics 1.79.14+ds1-1)

2023-12-04 Thread Simon Vetter

Hi Guillem,

thanks for taking care of this.

The old version is still in stable as of today and is IMHO rendering 
victoria-metrics almost unusable (keeps crashing randomly, up to 10-15 
times a day on my systems). Is there anything that could be done to push 
the fixed package to bookworm, at the very least for armhf ?


Thanks again for your time and help,

-Simon

On 09/09/2023 00:24, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the victoria-metrics package:

#1051392: Crash on unaligned reads on 32-bit arm architectures

It has been closed by Debian FTP Masters  (reply to 
Guillem Jover ).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
 (reply to Guillem Jover ) 
by
replying to this email.



--
Simon Vetter



Bug#1056908: tzdata: Support IANA time zones

2023-12-04 Thread John Clark

On 12/4/23 10:13 AM, Benjamin Drung wrote:

Hi,

On Sun, 2023-11-26 at 09:23 -0500, John Clark wrote:

Package: tzdata
Version: 2023c-8

The 12 well-known US time zones have been dropped from Debian tzdata as
of 2023c-8:
https://tracker.debian.org/news/1451157/accepted-tzdata-2023c-8-source-into-unstable

These time zones are still officially recognized and fully supported by
IANA.

IANA Timezone Database:
https://en.wikipedia.org/wiki/List_of_tz_database_time_zones

/usr/share/zoneinfo/US/Alaska
/usr/share/zoneinfo/US/Aleutian
/usr/share/zoneinfo/US/Arizona
/usr/share/zoneinfo/US/Central
/usr/share/zoneinfo/US/East-Indiana
/usr/share/zoneinfo/US/Eastern
/usr/share/zoneinfo/US/Hawaii
/usr/share/zoneinfo/US/Indiana-Starke
/usr/share/zoneinfo/US/Michigan
/usr/share/zoneinfo/US/Mountain
/usr/share/zoneinfo/US/Pacific
/usr/share/zoneinfo/US/Samoa


Their removal appears to be related to this request:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040997

This request does not provide any support as to why Debian should
deviate from IANA standards.

Requesting that Debian again adopt international time zone standards and
support these well known IANA time zones as it does in Bookworm.

These timezones are considered legacy by the upstream tz project. These
timezones were not removed but moved to tzdata-legacy. So please install
tzdata-legacy if you want to use them:

sudo apt install tzdata-legacy

I looked for deprecations in the upstream project but did not find any.  
Can you cite any IANA deprecation references?




Bug#1057411: urlview: bad display

2023-12-04 Thread наб
Control: tags -1 + confirmed upstream fixed-upstream

On Mon, Dec 04, 2023 at 03:19:00PM +0100, Vincent Lefevre wrote:
> Package: urlview
> Version: 1b-1
> 
> With the new urlview version, when I invoke it from Mutt, I get
> something like for the first line:
> 
> 3 URLs   urlview-ng 1bAppuyez sur q ou ^C pour 
> quitter !
> 
> in French, or
> 
> 3 URLs   urlview-ng 1b-1  Press q or ^C to 
> quit!
> 
> in English. This is poorly aligned, specially with the French message,
> which overwrites the version number.
These are aligned to left/right margins and center-of-screen,
which looks fine with my usual size of teletype,
but I agree it do be pretty goofy at 80.

I s'pose they could instead be aligned to left/right margins and
center-of-remaining, which'd fix this:
-- >8 --
17 URLsurlview-ng 1b-1Appuyez sur q ou ^C pour quitter !
->1 http://www.cs.hmc.edu/~me
  2 http://www.cs.hmc.edu
  3 https://www.cs.hmc.edu
-- >8 --
and
-- >8 --
17 URLs  urlview-ng 1b-1  Press q or ^C to quit!
->1 http://www.cs.hmc.edu/~me
  2 http://www.cs.hmc.edu
  3 https://www.cs.hmc.edu
-- >8 --
is much more reasonable.

Having modeled that, it was quite easy to implement,
and the results match the model above, incl.
-- >8 --
17 URLi urlview-ng 1b-1Wyjście: q lub ^C
->1 http://www.cs.hmc.edu/~me
  2 http://www.cs.hmc.edu
  3 https://www.cs.hmc.edu
-- >8 --

This is what
  
https://git.sr.ht/~nabijaczleweli/urlview-ng/commit/af9bf97584c015c9417428aa4eca5c64486ff816
does.

Best,
наб


signature.asc
Description: PGP signature


Bug#1057385: lighttpd FTCBFS: host CFLAGS leak into build compiler invocation

2023-12-04 Thread gs-bugs . debian . org
On Mon, Dec 04, 2023 at 11:49:30AM +0100, Emanuele Rocca wrote:
> With the attached patch lighttpd cleanly cross-builds from source.

Thanks, Emanuele.

A slightly different patch:

https://salsa.debian.org/debian/lighttpd/-/commit/a7d695d59c9a8bffe154aae29e335102beaaf3f2

was committed a few weeks ago to salsa.debian.org, which I based off
comments in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021292?

Is your suggested approach (above) preferred to this patch (below)?

@@ -50,9 +50,9 @@ override_dh_auto_configure:
--with-xxhash \
--with-zstd \
$(if $(filter 
pkg.lighttpd.libunwind,$(DEB_BUILD_PROFILES)),--with-libunwind) \
-   CFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CFLAGS)" \
-   LDFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get LDFLAGS)" \
-   CPPFLAGS_FOR_BUILD="$(shell dpkg-buildflags --get CPPFLAGS)" \
+   CFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f 
-c dpkg-buildflags --get CFLAGS)" \
+   LDFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f 
-c dpkg-buildflags --get LDFLAGS)" \
+   CPPFLAGS_FOR_BUILD="$$(dpkg-architecture -a$(DEB_BUILD_ARCH) -f 
-c dpkg-buildflags --get CPPFLAGS)" \
 
 override_dh_install:
cp NEWS debian/tmp/changelog



Bug#1056908: tzdata: Support IANA time zones

2023-12-04 Thread Benjamin Drung
Hi,

On Sun, 2023-11-26 at 09:23 -0500, John Clark wrote:
> Package: tzdata
> Version: 2023c-8
> 
> The 12 well-known US time zones have been dropped from Debian tzdata as 
> of 2023c-8:
> https://tracker.debian.org/news/1451157/accepted-tzdata-2023c-8-source-into-unstable
> 
> These time zones are still officially recognized and fully supported by 
> IANA.
> 
> IANA Timezone Database:
> https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
> 
> /usr/share/zoneinfo/US/Alaska
> /usr/share/zoneinfo/US/Aleutian
> /usr/share/zoneinfo/US/Arizona
> /usr/share/zoneinfo/US/Central
> /usr/share/zoneinfo/US/East-Indiana
> /usr/share/zoneinfo/US/Eastern
> /usr/share/zoneinfo/US/Hawaii
> /usr/share/zoneinfo/US/Indiana-Starke
> /usr/share/zoneinfo/US/Michigan
> /usr/share/zoneinfo/US/Mountain
> /usr/share/zoneinfo/US/Pacific
> /usr/share/zoneinfo/US/Samoa
> 
> 
> Their removal appears to be related to this request: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040997
> 
> This request does not provide any support as to why Debian should 
> deviate from IANA standards.
> 
> Requesting that Debian again adopt international time zone standards and 
> support these well known IANA time zones as it does in Bookworm.

These timezones are considered legacy by the upstream tz project. These
timezones were not removed but moved to tzdata-legacy. So please install
tzdata-legacy if you want to use them:

sudo apt install tzdata-legacy

-- 
Benjamin Drung
Debian & Ubuntu Developer



Bug#1057413: FTBFS: dh_install: warning: gnustep-make-doc missing files: Documentation/gnustep-make.pdf

2023-12-04 Thread Chris Hofstaedtler
Source: gnustep-make
Version: 2.9.1-2
Severity: serious
Tags: ftbfs

Dear Maintainer,

gnustep-make-doc currently FTBFS in unstable, in both my own test build
and on reproducible-builds. Here is a part of the build log:

Installing GNUstep configuration file in 
/build/reproducible-path/gnustep-make-2.9.1/debian/tmp/etc/GNUstep/GNUstep.conf
Installing gnustep-make support software
Installing makefiles
Installing Test Framework scripts
Installing Test Framework support files
Installing (and compressing) manpages
make[1]: Leaving directory 
'/build/reproducible-path/gnustep-make-2.9.1/build-gnustep-make'
   dh_install -O--builddirectory=build-gnustep-make
dh_install: warning: Cannot find (any matches for) 
"Documentation/gnustep-make.pdf" (tried in ., debian/tmp)

dh_install: warning: gnustep-make-doc missing files: 
Documentation/gnustep-make.pdf
dh_install: error: missing files, aborting
make: *** [debian/rules:24: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Full log from reproducible-builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/gnustep-make_2.9.1-2.rbuild.log.gz

Best,
Chris



Bug#1057308: RFS: sioyek/2.0.0+dfsg-4 [RC] -- PDF viewer with a focus on technical books and research papers

2023-12-04 Thread Victor Westerhuis
Package: sponsorship-requests
Followup-For: Bug #1057308

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Apologies for the improper move of the dependency to Static-Built-Using.
I have uploaded a fixed version to mentors.debian.net.
- --
Groet, Regards,

Victor Westerhuis


-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEE6OxII3T+o0Ujs6ECQz2Rq5dHQPsFAmVt2pYTHHZpY3RvckB3
ZXN0ZXJodS5pcwAKCRBDPZGrl0dA+2CIEACc8+mTKxNTY5jCPjTWh8xS3MTBzt76
fljWfp+01YfzRlYub8cxNfd0YVolOU7BTjk6LwqNeu8H0iQxKkdFqB457oPSEsuL
ouBS9ZmRdrxwvDzV/bWFzNx7VfYACljpLF3GokPY4j1yEXcOUHQmX+T2aAFrs6zq
j1GPEKh0pJXpESwGqpZlxc/mtb8EYCLh/RvYbHXcjtuB1/PQqZ3UETHce7p4tk2g
C3GOzGfEp4czhYm/2xEZPzA7leGINp0TCfrp+40Ri9fyrYyRX3fZGO/os9+Lumez
vKgU1WPgotba+A8jYszjL6tQDZzfODWLJH/n0tAByIBSwvvHGlK+63WwiGYt5DRD
fMrKQXVmL56lx5MyqST33ldcZqkue7e8un+Xt/G8arUBH6LNGRCOTCTx9KUGZa4k
c/P+0tQM6EIMLsRKn4vivjcPRtt/2eFmDOIlZdoBxF0n7ezuenJ2dvhOng3izQD1
W9Kr99qKOOY5l/Q1Mw6iy1/uHJr/YCKe729FrfhVsI+ECNJL3WqluTDaJl35Z3/z
8AywDEgAYJstYR1umoVaaHrhxYXc59k8Y9ld5muN+6/R1N9oaZ8F47/USeRx/vQX
v+y+BTu3bKGlMBgY4znCA8XXVnpWMYx/btBJIqJKsDzeszWVb7Qe1t3dTwUY6WMM
2E/kSLUZTAoO+w==
=MJoF
-END PGP SIGNATURE-



Bug#1056498: python-pynvim's autopkg tests fail with Python 3.12

2023-12-04 Thread James McCoy
On Wed, Nov 22, 2023 at 03:46:46PM +0100, Matthias Klose wrote:
> python-pynvim's autopkg tests fail with Python 3.12:
> 
> [...]
> 400s autopkgtest [18:50:54]: test python3-pynvim: [---
> 401s ImportError while loading conftest
> '/tmp/autopkgtest.jZbwTr/autopkgtest_tmp/test/conftest.py'.
> 401s test/conftest.py:6: in 
> 401s import pynvim
> 401s /usr/lib/python3/dist-packages/pynvim/__init__.py:9: in 
> 401s from pynvim.api import Nvim, NvimError
> 401s /usr/lib/python3/dist-packages/pynvim/api/__init__.py:7: in 
> 401s from pynvim.api.buffer import Buffer
> 401s /usr/lib/python3/dist-packages/pynvim/api/buffer.py:2: in 
> 401s from pynvim.api.common import Remote
> 401s /usr/lib/python3/dist-packages/pynvim/api/common.py:6: in 
> 401s from pynvim.compat import unicode_errors_default
> 401s /usr/lib/python3/dist-packages/pynvim/compat.py:5: in 
> 401s from imp import find_module as original_find_module
> 401s E   ModuleNotFoundError: No module named 'imp'

I can backport some patches to fix that, but then it will be blocked
because python-greenlet doesn't support 3.12 yet (#1055498).

While waiting for greenlet, I'll poke upstream to see if they can get a
new pynvim release out so backports aren't needed.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB



Bug#1057411: urlview: bad display

2023-12-04 Thread Vincent Lefevre
Package: urlview
Version: 1b-1
Severity: normal

With the new urlview version, when I invoke it from Mutt, I get
something like for the first line:

3 URLs   urlview-ng 1bAppuyez sur q ou ^C pour quitter !

in French, or

3 URLs   urlview-ng 1b-1  Press q or ^C to quit!

in English. This is poorly aligned, specially with the French message,
which overwrites the version number.

With urlview 0.9, I got:

UrlView 0.9: (3 matches) Press Q or Ctrl-C to Quit!

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

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

Versions of packages urlview depends on:
ii  libc6   2.37-13
ii  libncursesw66.4+20231121-1
ii  libtinfo6   6.4+20231121-1
ii  sensible-utils  0.0.20
ii  ucf 3.0043+nmu1

Versions of packages urlview recommends:
ii  elinks [www-browser]   0.16.1.1-4.1
ii  firefox [www-browser]  120.0.1-1
hi  firefox-esr [www-browser]  92.0-local
ii  links [www-browser]2.29-1+b1
ii  links2 [www-browser]   2.29-1+b1
ii  lynx [www-browser] 2.9.0dev.12-1
ii  w3m [www-browser]  0.5.3+git20230121-2

Versions of packages urlview suggests:
ii  curl  8.4.0-2
ii  lftp  4.9.2-2+b1
ii  mutt  2.2.12-0.1
ii  wget  1.21.4-1+b1

-- no debconf information

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



Bug#1057412: pynormaliz: FTBFS in testing and unstable

2023-12-04 Thread Graham Inggs
Source: pynormaliz
Version: 2.18+ds-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen in reproducible builds [1], pynormaliz currently FTBFS
in testing and unstable.  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


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


dh execute_after_dh_auto_build --buildsystem=pybuild
make[1]: Leaving directory '/build/reproducible-path/pynormaliz-2.18+ds'
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:310: cd
/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build;
PYTHONPATH=/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build
python3.11 tests/runtests.py
Error: nauty.c version mismatch
E: pybuild pybuild:395: test: plugin distutils failed with: exit
code=1: cd 
/build/reproducible-path/pynormaliz-2.18+ds/.pybuild/cpython3_3.11/build;
PYTHONPATH={build_dir} {interpreter} tests/runtests.py
dh_auto_test: error: pybuild --test -i python{version} -p 3.11
returned exit code 13
make: *** [debian/rules:9: binary] Error 25



Bug#1057282: linux-image-6.5.0-0.deb12.1-arm64: arm64 kernel upgrade makes systems unresponsive

2023-12-04 Thread Ben Hutchings
Control: reassign -1 src:linux 6.5.3-1~bpo12+1
Control: tag -1 moreinfo

On Sat, 2023-12-02 at 18:11 +0100, Paul Gevers wrote:
> Package: linux-image-6.5.0-0.deb12.1-arm64
> Version: 6.5.3-1~bpo12+1
> Severity: serious
> Justification: system stops responding
> 
> Dear kernel maintainers,
> 
> Thursday 30 November I upgraded the ci.debian.net workers. We're running 
> the backports kernel there due to issues we discussed earlier, but after 
> upgrading, we lost access to our arm64 hosts one after the other. We're 
> running the 6.4 kernel again now, and I extracted some of the logs. 
> Please let me know if you need more info.

The first error logged in this file has:

> CPU: 6 PID: 15039 Comm: lxc-start Tainted: G  D WL 
> 6.5.0-0.deb12.1-arm64 #1  Debian 6.5.3-1~bpo12+1

The D and W flags mean there were prior BUG and WARN errors logged. 
Please send those as well.

Ben.

-- 
Ben Hutchings
Power corrupts.  Absolute power is kind of neat. - John Lehman



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


Bug#1057410: pymupdf: FTBFS in testing and unstable

2023-12-04 Thread Graham Inggs
Source: pymupdf
Version: 1.22.5+ds1-1
Severity: serious
Tags: ftbfs

Hi Maintainer

As can be seen in reproducible builds [1], pymupdf currently FTBFS in
testing and unstable.  I've copied what I hope is the relevant part of
the log below.

Regards
Graham


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


I: pybuild base:310: cd
/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build;
python3.11 -m unittest discover -v
fitz (unittest.loader._FailedTest.fitz) ... ERROR

==
ERROR: fitz (unittest.loader._FailedTest.fitz)
--
ImportError: Failed to import test module: fitz
Traceback (most recent call last):
  File "/usr/lib/python3.11/unittest/loader.py", line 452, in _find_test_path
package = self._get_module_from_name(name)
  
  File "/usr/lib/python3.11/unittest/loader.py", line 362, in
_get_module_from_name
__import__(name)
  File 
"/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/__init__.py",
line 10, in 
import fitz.fitz as fitz
  File 
"/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/fitz.py",
line 14, in 
from . import _fitz
ImportError: 
/build/reproducible-path/pymupdf-1.22.5+ds1/.pybuild/cpython3_3.11/build/fitz/_fitz.cpython-311-x86_64-linux-gnu.so:
undefined symbol: pdf_lookup_anchor


--
Ran 1 test in 0.003s

FAILED (errors=1)



Bug#1057260: iwlwifi: `N' invalid for parameter `enable_ini'

2023-12-04 Thread Prabin Dahal
Package: src:linux
Followup-For: Bug #1057260

Dear Maintainer,

I also face the same problem when using 6.1.0-14-amd64 kernel.


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

** Model information
sys_vendor: SLIMBOOK
product_name: EXECUTIVE-14
product_version: Standard
chassis_vendor: SLIMBOOK
chassis_version: Standard
bios_vendor: American Megatrends International, LLC.
bios_version: N.1.09GRU00
board_vendor: SLIMBOOK
board_name: EXECUTIVE-14
board_version: Standard

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host 
Bridge/DRAM Registers [8086:9a14] (rev 01)
DeviceName: Onboard - Other
Subsystem: Tongfang Hongkong Limited 11th Gen Core Processor Host 
Bridge/DRAM Registers [1d05:1105]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: igen6_edac

00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 
[Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
DeviceName: Onboard - Video
Subsystem: Tongfang Hongkong Limited TigerLake-LP GT2 [Iris Xe 
Graphics] [1d05:1105]
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: i915
Kernel modules: i915

00:06.0 PCI bridge [0604]: Intel Corporation 11th Gen Core Processor PCIe 
Controller [8086:9a09] (rev 01) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:07.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI 
Express Root Port #0 [8086:9a23] (rev 01) (prog-if 00 [Normal decode])
Subsystem: Tongfang Hongkong Limited Tiger Lake-LP Thunderbolt 4 PCI 
Express Root Port [1d05:1105]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:08.0 System peripheral [0880]: Intel Corporation GNA Scoring Accelerator 
module [8086:9a11] (rev 01)
DeviceName: Onboard - Other
Subsystem: Tongfang Hongkong Limited GNA Scoring Accelerator module 
[1d05:1105]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 
USB Controller [8086:9a13] (rev 01) (prog-if 30 [XHCI])
DeviceName: Onboard - Other
Subsystem: Tongfang Hongkong Limited Tiger Lake-LP Thunderbolt 4 USB 
Controller [1d05:1105]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:0d.2 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 
NHI #0 [8086:9a1b] (rev 01) (prog-if 40 [USB4 Host Interface])
DeviceName: Onboard - Other
Subsystem: Device [:]
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: thunderbolt
Kernel modules: thunderbolt

00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 
xHCI Host Controller [8086:a0ed] (rev 20) (prog-if 30 [XHCI])
DeviceName: Onboard - Other
Subsystem: Tongfang Hongkong Limited Tiger Lake-LP USB 3.2 Gen 2x1 xHCI 
Host Controller [1d05:1105]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-LP Shared SRAM 
[8086:a0ef] (rev 20)
DeviceName: Onboard - Other
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-

Bug#1057399: firmware-amd-graphics: Unintended consequence of /usr merge - video output ceases

2023-12-04 Thread Luca Boccassi
Control: tags -1 wontfix
Control: close -1

On Mon, 04 Dec 2023 23:34:29 +1030 Arthur Marsh
 wrote:
> Package: firmware-amd-graphics
> Version: 20230625-1
> Severity: normal
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
appropriate ***
> 
>    * What led up to the situation?
> 
> A long time ago on a motherboard far away lived an AMD graphics card 
> code-named Cedar. 
> 
> Cedar was missing its firmware so its owner copied the firmware to 
> /lib/firmware/radeon and all was well.
> 
> The graphics card was later moved to another pc (after Cedar firmware
was
> packaged), replaced by an R7 250 
> graphics card and all was well.
> 
> Later on the motherboard went to the great scrap metal recovery yard,
> replaced by a motherboard with an AMD APU, and its graphics unit was 
> code-named Aruba and all was well.
> 
> Then, an early present arrived in the form of /usr merge for AMD
graphics 
> firmware. 
> A small message said: 
> "unable to remove /lib/firmware/radeon - directory not empty" 
> and all was well until update-initramfs was run and a reboot.

> -- System Information:
> Debian Release: trixie/sid
>   APT prefers experimental
>   APT policy: (1, 'experimental')
> merged-usr: no

Hi,

Unfortunately this system appears to be in an unsupported state. Please
install the usrmerge package to fix it. You can find more information
at:

https://wiki.debian.org/UsrMerge

-- 
Kind regards,
Luca Boccassi


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


Bug#1057409: cctools: b-d on python3-all-dev, but not built for all supported Python3 versions

2023-12-04 Thread Graham Inggs
Source: cctools
Version: 9.9-3
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10 python3-all-dev

Hi Maintainer

This package build-depends on python3-all-dev, but does not build
extensions/libraries for all supported python3 versions.  This is seen
on the transition tracker for adding python3.12 support [1] and
creates false positives.

Please either replace the b-d python3-all-dev with python3-dev, or
build for all supported Python3 versions.  With the former solution
yet get later exposure to a new python3 version, with the latter
solution you get early exposure.

Regards
Graham


[1] https://release.debian.org/transitions/html/python3.12-add.html



Bug#1000044: ccze: depends on obsolete pcre3 library

2023-12-04 Thread Yavor Doganov
Axel Beckert wrote:
> A local test on my /var/log/syslog immediately ran into a segfault,
> though, so I guess, that's one of the plugins you couldn't test.

I tested it but I guess results depend on the contents of the log;
apparently my log didn't trigger this code.

> Culprit is this line, actually the first line in my current
> /var/log/syslog:
> 
>   Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration reload request
>   received, reloading configuration;

Many thanks for the reproducer.  Attached is patch that fixes it for
me.  I suspect there are other issues like these; in fact my pathethic
patch introduces a few memory leaks (I should have told you that in
advance).  The problem is that ccze code manipulates strings obtained
with pcre_get_substring, and assumes it can always use "free" to free
them.  That assumption is fine in the case with the old pcre, because
the definition of pcre_free_substring is just a wrapper around free
(src:pcre3: pcre_get.c:655):

void
pcre_free_substring(const char *pointer)
{
(PUBL(free))((void *)pointer);
}

So ccze code always uses "free".  However, in pcre2, the equivalent
function is different (src:pcre2: src/pcre2_substring.c:240):

void
pcre2_substring_free(PCRE2_UCHAR *string)
{
if (string != NULL)
  {
  pcre2_memctl *memctl = (pcre2_memctl *)((char *)string - 
sizeof(pcre2_memctl));
  memctl->free(memctl, memctl->memory_data);
  }
}

Attempting to use "free" to free a string obtained with
pcre2_subtring_get_by* results in SIGABRT with invalid pointer, while
using pcre2_substring_free on a string obtained with strdup or some
other standard (glibc) string manipulation functions results in
SIGSEGV.  Attached are two equivalent minimalistic programs that
demonstrate this: foo.c uses pcre2 and if you exchange the free
functions at the end for date and dup, you will observe exactly what I
wrote above.  The other program, bar.c, uses the old pcre and it
doesn't make any difference if you swap them or use only "free" as
ccze does.

I guess I need to revisit my patch and find some way to fix this.
It's up to you whether to upload the memleaky patch now or wait for me
to find a solution.  Sorry about this.
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
index 6b60dc8..2723ff8 100644
--- a/debian/patches/pcre2.patch
+++ b/debian/patches/pcre2.patch
@@ -2455,26 +2455,32 @@ Last-Update: 2023-12-03
  }

if (process)
-@@ -87,12 +87,13 @@
+@@ -60,7 +60,7 @@
+ 
+ pid = strndup ([1], (size_t)(t2 - t - 1));
+ tmp = strndup (process, (size_t)(t - process));
+-free (process);
++pcre2_substring_free (process);
+ process = tmp;
+   }
+ }
+@@ -87,11 +87,11 @@
else
  toret = strdup (send);
  
 -  free (date);
 -  free (host);
 -  free (send);
--  free (process);
--  free (msg);
 +  pcre2_substring_free (date);
 +  pcre2_substring_free (host);
 +  pcre2_substring_free (send);
-+  pcre2_substring_free (process);
 +  pcre2_substring_free (msg);
+   free (process);
+-  free (msg);
free (pid);
-+  free (tmp);
  
return toret;
- }
-@@ -100,33 +101,34 @@
+@@ -100,33 +100,34 @@
  static void
  ccze_syslog_setup (void)
  {
#define PCRE2_CODE_UNIT_WIDTH 8
#include 
#include 
#include 

int
main (void)
{
  pcre2_code *pcre;
  pcre2_match_data *md;
  int error;
  size_t errptr, l;
  char *date = NULL, *dup;
  const char *str = "Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration "
"reload request received, reloading configuration;";

  pcre = pcre2_compile ("^(\\S*\\s{1,2}\\d{1,2}\\s\\d\\d:\\d\\d:\\d\\d)"
"\\s(\\S+)\\s+((\\S+:?)\\s(.*))$",
PCRE2_ZERO_TERMINATED, 0, , , NULL);

  md = pcre2_match_data_create (99, NULL);

  pcre2_match (pcre, str, PCRE2_ZERO_TERMINATED, 0, 0, md, NULL);
  pcre2_substring_get_bynumber (md, 1, (unsigned char **), );

  if (date)
{
  printf ("%s\n", date);
  dup = strdup (date);
}

  pcre2_substring_free (date);
  free (dup);

  return 0;
}
#include 
#include 
#include 

int
main (void)
{
  pcre *pcre;
  int md[99];
  const char *error;
  int errptr, match;
  char *date = NULL, *dup;
  const char *str = "Dec  3 06:38:28 c6 syslog-ng[26651]: Configuration "
"reload request received, reloading configuration;";

  pcre = pcre_compile ("^(\\S*\\s{1,2}\\d{1,2}\\s\\d\\d:\\d\\d:\\d\\d)"
   "\\s(\\S+)\\s+((\\S+:?)\\s(.*))$",
   0, , , NULL);

  match = pcre_exec (pcre, NULL, str, strlen (str), 0, 0, md, 99);
  pcre_get_substring (str, md, match, 1, (const char **));

  if (date)
{
  printf ("%s\n", date);
  dup = strdup (date);
}

  pcre_free_substring (date);
  free (dup);

  return 0;
}


Bug#1057408: lynis: got pgrep warning every day from a cron job since upgraded to Debian 12.

2023-12-04 Thread shizuma
Package: lynis
Version: 3.0.9-100
Severity: normal

Dear Maintainer,

Excerpt from my cron.daily email:
/etc/cron.daily/lynis:
/usr/sbin /
pgrep: pattern that searches for process name longer than 15 characters will 
result in zero matches
Try `pgrep -f' option to match against the complete command line.
/
End of excerpt.

I tried to debug with 'set -x' but there was way to much data and it filled my 
buffer so I was unable to trace which line is responsible.
I installed a more recent version of lynis.  Did not help.

Best!

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

Kernel: Linux 5.10.0-26-amd64 (SMP w/6 CPU threads)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.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

lynis depends on no packages.

lynis recommends no packages.

Versions of packages lynis suggests:
ii  bind9-dnsutils [dnsutils]  1:9.18.19-1~deb12u1
ii  dnsutils   1:9.18.19-1~deb12u1

-- no debconf information



Bug#1057407: texworks: Intent to drop poppler-qt6 on i386

2023-12-04 Thread Jeremy Bícha
Source: texworks
Version: 0.6.8-3
Severity: important
X-Debbugs-CC: hill...@web.de

As the maintainer of Debian's poppler source package, I would like to
drop poppler's Qt6 packages on i386. This would allow Debian's and
Ubuntu's poppler packaging to be in sync. Ubuntu has dropped i386
support except for enablement of games and similar legacy apps but
none of those apps need Qt6. Based on debian-devel discussion in June,
I expect Debian to eventually take a similar approach to i386.

texworks is the only package that uses poppler's Qt6 in Debian. Please
let me know if it's ok with you if texworks is no longer built for
i386 in Debian.

Thank you,
Jeremy Bícha



  1   2   >