Bug#1053549: Create a Debian theme for documentation based in Sphinx (reStructuredText)

2024-04-12 Thread Holger Wansing
Hi James,

Am 11. April 2024 23:52:52 MESZ schrieb James Addison :
>Hi Holger,
>
>On Sun, 7 Apr 2024 13:00:43 +0200, Holger wrote:
>> The only thing which is not working currently, is the search functionality,
>> but since that's not theme-specific I guess (please correct me, if I'm
>> wrong), I close this bug.
>
>The theme looks great, and I agree with closing this bug.  However, so that
>we don't overlook another potential python3-sphinx bug: could you report the
>problem that you encountered?  (I contribute to upstream and may be able to
>help with investigating that)

It's not a bug in sphinx or something like that.
The issue was in the build process for the website, what lead to some missing 
files in the manuals' tree (javascript script files and the searchindex.js).

Everything fine for now.

I'm currently working on switching the Debian release-notes to the new theme, 
and that might bring some issues, since the release-notes have translations as 
well (this was not the case for the debian-policy).

So maybe I come back to you in such case, if that's ok?


Thanks
Holger


-- 
Sent from /e/ OS on Fairphone3



Bug#1068431: rakarrack dependencies unsatisfiable on 32-bit non-i386 architectures.

2024-04-12 Thread Steve Langasek
Package: rakarrack
Followup-For: Bug #1068431
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru rakarrack-0.6.1/debian/control rakarrack-0.6.1/debian/control
--- rakarrack-0.6.1/debian/control  2024-03-12 00:01:51.0 -0700
+++ rakarrack-0.6.1/debian/control  2024-04-12 22:22:56.0 -0700
@@ -21,9 +21,6 @@
 Architecture: any
 Depends: ${misc:Depends},
  ${shlibs:Depends},
- libfltk1.3,
- libxpm4,
- libasound2,
  jackd
 Description: Simple and easy guitar effects processor for GNU/Linux
  Rakarrack is a guitar effects processor for GNU / Linux simple and easy to use


Bug#1068899: ITP: qtrvsim -- RISC-V CPU simulator for education purposes

2024-04-12 Thread Bo YU
Package: wnpp
Severity: wishlist
Owner: Bo YU 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-ri...@lists.debian.org

* Package name: qtrvsim
  Version : 0.9.7
  Upstream Contact: p...@cmp.felk.cvut.cz
* URL : https://github.com/cvut/qtrvsim
* License : GPL-3.0
  Programming Lang: C++, Python, shell
  Description : RISC-V CPU simulator for education

This is a widely recommended riscv emulator in the riscv community so I
want to bring it to Debian also.

The simulator accepts ELF statically linked executables compiled for
RISC-V target (--march=rv64g). The simulator will automatically select
endianness based on the ELF file header. Simulation will execute as
XLEN=32 or XLEN=32 according to the ELF file header.

64-bit RISC-V ISA RV64IM and 32-bit RV32IM ELF executables are supported.
Compressed instructions are not yet supported.
You can use compile the code for simulation using specialized RISC-V
GCC/Binutils toolchain (riscv32-elf) or using unified Clang/LLVM toolchain
with LLD.

-- 
Regards,
--
  Bo YU



signature.asc
Description: PGP signature


Bug#1068898: Reinstate OpenRD netboot images for bookworm

2024-04-12 Thread Martin Michlmayr
Package: debian-installer
Version: 20230607+deb12u5

I'm sorry to be that guy who shows up every few years to waste
everyone's time... but... I was updating my Kirkwood pages for
bookworm and noticed that the OpenRD images are gone.

Now you may remember that we had the same situation for bullseye
(#934072) and Cyril kindly restored the netboot images:
https://salsa.debian.org/installer-team/debian-installer/-/commit/3ef30be60ab128f53a0cd16e6c1e91a3123988b4

I guess this change never got committed to master/main because
bullseye was going to be the last release for armel.

But armel is still in bookworm and Rick confirmed he's running
bookworm on his OpenRD, so I see no reason why d-i wouldn't work if
we apply the same patch to the bookworm d-i.

Honestly, I'm not sure if it's worth it as Rick is probably the one
Debian on OpenRD left, but since bookworm will probably be the last
release of armel (or not?) it would be nice if the installer was
working on OpenRD.

Cyril or Vagrant, can you easily apply the patch above and generate a
test image for Rick?

Sorry for creating work (again) for such a minor platform...
-- 
Martin Michlmayr
https://www.cyrius.com/



Bug#1068897: litecli: SyntaxWarning: invalid escape sequence

2024-04-12 Thread Paul Wise
Package: litecli
Version: 1.10.1-1
Severity: normal
Usertags: warnings
User: debian-pyt...@lists.debian.org
Usertags: python3.12

A recent upgrade gave me these warnings, likely caused by Python 3.12:

   Preparing to unpack .../litecli_1.10.1-1_all.deb ...
   Unpacking litecli (1.10.1-1) over (1.10.0-1) ...
   Setting up litecli (1.10.1-1) ...
   /usr/lib/python3/dist-packages/litecli/main.py:332: SyntaxWarning: invalid 
escape sequence '\e'
 """Editor command is any query that is prefixed or suffixed by a '\e'.
   /usr/lib/python3/dist-packages/litecli/packages/parseutils.py:15: 
SyntaxWarning: invalid escape sequence '\s'
 "all_punctuations": re.compile("([^\s]+)$"),
   /usr/lib/python3/dist-packages/litecli/packages/parseutils.py:20: 
SyntaxWarning: invalid escape sequence '\d'
 """
   /usr/lib/python3/dist-packages/litecli/packages/special/iocommands.py:124: 
SyntaxWarning: invalid escape sequence '\e'
 pattern = re.compile("(^\\\e|\\\e$)")
   /usr/lib/python3/dist-packages/litecli/packages/special/iocommands.py:248: 
SyntaxWarning: invalid escape sequence '\d'
 match = re.search("\\?|\\$\d+", query)
   /usr/lib/python3/dist-packages/litecli/sqlcompleter.py:260: SyntaxWarning: 
invalid escape sequence '\$'
 self.name_pattern = compile("^[_a-z][_a-z0-9\$]*$")
   
-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental'), 
(500, 'stable-updates'), (500, 'stable-security-debug'), (500, 
'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), 
(500, 'proposed-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages litecli depends on:
ii  python3 3.11.6-1
ii  python3-cli-helpers 2.3.1-1
ii  python3-click   8.1.7-1
ii  python3-configobj   5.0.8-3
ii  python3-prompt-toolkit  3.0.43-1
ii  python3-pygments2.17.2+dfsg-1
ii  python3-sqlparse0.4.4-1

litecli recommends no packages.

litecli suggests no packages.

-- no debconf information

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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


Bug#1065810: tech-ctte: Call for votes on TC membership of Craig Small

2024-04-12 Thread Sean Whitton
Ping again.  Thanks.

On Thu 28 Mar 2024 at 01:33pm +08, Sean Whitton wrote:

> Hello,
>
> On Mon 18 Mar 2024 at 10:43am +08, Sean Whitton wrote:
>
>> The vote has concluded.  The result is that the Technical Committee
>> recommends that Craig Small  be appointed by the Debian Project
>> Leader to the Technical Committee.
>>
>> Jonathan, over to you.
>
> Quick ping about this.  The appointment holds up some administrative
> stuff for us.  Thanks.

-- 
Sean Whitton



Bug#1068896: screenshots

2024-04-12 Thread Russell Coker
settings.png shows the configuration options I'm given.

small.png shows the result of setting small, from the pixel layout you can see 
this isn't very readable text for the battery charge level.  It's possible to 
work it out but not at all clear.

panel-width.png has the full panel width.  It's quite readable but the 
vertical size is significant.  420 pixels out of the 1440 total.  If I made 
the panel slightly wider to make the task manager entries easier to read then 
it would increase the height even more.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/


Bug#1068895:

2024-04-12 Thread Adam Baxter
Confirming the same failure after removing the out-of-tree driver and rebooting

It took running iwlist scanning a few times in quick succession though.

   90.096424] iwlwifi :01:00.0: Scan failed! ret -5
[   95.338259] iwlwifi :01:00.0: Microcode SW error detected. Restarting 
0x0.
[   95.338400] iwlwifi :01:00.0: Start IWL Error Log Dump:
[   95.338410] iwlwifi :01:00.0: Transport status: 0x004B, valid: 6
[   95.338421] iwlwifi :01:00.0: Loaded firmware version: 72.daa05125.0 
ty-a0-gf-a0-72.ucode
[   95.338432] iwlwifi :01:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL
[   95.338443] iwlwifi :01:00.0: 0x02F0 | trm_hw_status0
[   95.338451] iwlwifi :01:00.0: 0x | trm_hw_status1
[   95.338460] iwlwifi :01:00.0: 0x004DB5D2 | branchlink2
[   95.338468] iwlwifi :01:00.0: 0x004D5DC2 | interruptlink1
[   95.338476] iwlwifi :01:00.0: 0x004D5DC2 | interruptlink2
[   95.338483] iwlwifi :01:00.0: 0x00016B0E | data1
[   95.338491] iwlwifi :01:00.0: 0x0010 | data2
[   95.338498] iwlwifi :01:00.0: 0x | data3
[   95.338505] iwlwifi :01:00.0: 0x003D5C19 | beacon time
[   95.338513] iwlwifi :01:00.0: 0x00449605 | tsf low
[   95.338520] iwlwifi :01:00.0: 0x | tsf hi
[   95.338527] iwlwifi :01:00.0: 0x | time gp1
[   95.338534] iwlwifi :01:00.0: 0x0045D256 | time gp2
[   95.338541] iwlwifi :01:00.0: 0x0001 | uCode revision type
[   95.338549] iwlwifi :01:00.0: 0x0048 | uCode version major
[   95.338557] iwlwifi :01:00.0: 0xDAA05125 | uCode version minor
[   95.338565] iwlwifi :01:00.0: 0x0420 | hw version
[   95.338572] iwlwifi :01:00.0: 0x18C89002 | board version
[   95.338580] iwlwifi :01:00.0: 0x80A1FF00 | hcmd
[   95.338587] iwlwifi :01:00.0: 0x0002 | isr0
[   95.338595] iwlwifi :01:00.0: 0x | isr1
[   95.338602] iwlwifi :01:00.0: 0x48F04002 | isr2
[   95.338609] iwlwifi :01:00.0: 0x00C3000C | isr3
[   95.338616] iwlwifi :01:00.0: 0x | isr4
[   95.338623] iwlwifi :01:00.0: 0x001B0103 | last cmd Id
[   95.338630] iwlwifi :01:00.0: 0x00016B0E | wait_event
[   95.338638] iwlwifi :01:00.0: 0x | l2p_control
[   95.338645] iwlwifi :01:00.0: 0x | l2p_duration
[   95.338652] iwlwifi :01:00.0: 0x | l2p_mhvalid
[   95.338660] iwlwifi :01:00.0: 0x | l2p_addr_match
[   95.338667] iwlwifi :01:00.0: 0x0018 | lmpm_pmg_sel
[   95.338675] iwlwifi :01:00.0: 0x | timestamp
[   95.338682] iwlwifi :01:00.0: 0x1844 | flow_handler
[   95.338738] iwlwifi :01:00.0: Start IWL Error Log Dump:
[   95.338745] iwlwifi :01:00.0: Transport status: 0x004B, valid: 7
[   95.338755] iwlwifi :01:00.0: 0x20103609 | ADVANCED_SYSASSERT
[   95.338764] iwlwifi :01:00.0: 0x | umac branchlink1
[   95.338771] iwlwifi :01:00.0: 0x8045F1D0 | umac branchlink2
[   95.338779] iwlwifi :01:00.0: 0x01019BB4 | umac interruptlink1
[   95.338787] iwlwifi :01:00.0: 0x | umac interruptlink2
[   95.338795] iwlwifi :01:00.0: 0x0026 | umac data1
[   95.338802] iwlwifi :01:00.0: 0x0001 | umac data2
[   95.338809] iwlwifi :01:00.0: 0x | umac data3
[   95.338816] iwlwifi :01:00.0: 0x0048 | umac major
[   95.338823] iwlwifi :01:00.0: 0xDAA05125 | umac minor
[   95.338831] iwlwifi :01:00.0: 0x0045D24F | frame pointer
[   95.338838] iwlwifi :01:00.0: 0xC0886C0C | stack pointer
[   95.338845] iwlwifi :01:00.0: 0x0020010D | last host cmd
[   95.338853] iwlwifi :01:00.0: 0x | isr status reg
[   95.338881] iwlwifi :01:00.0: IML/ROM dump:
[   95.33] iwlwifi :01:00.0: 0x0B03 | IML/ROM error/state
[   95.338915] iwlwifi :01:00.0: 0x7FCB | IML/ROM data1
[   95.338942] iwlwifi :01:00.0: 0x0090 | IML/ROM WFPM_AUTH_KEY_0
[   95.338964] iwlwifi :01:00.0: Fseq Registers:
[   95.338981] iwlwifi :01:00.0: 0x6100 | FSEQ_ERROR_CODE
[   95.339000] iwlwifi :01:00.0: 0x00440007 | FSEQ_TOP_INIT_VERSION
[   95.339018] iwlwifi :01:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION
[   95.339037] iwlwifi :01:00.0: 0xA652 | FSEQ_OTP_VERSION
[   95.339056] iwlwifi :01:00.0: 0x0002 | FSEQ_TOP_CONTENT_VERSION
[   95.339074] iwlwifi :01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[   95.339092] iwlwifi :01:00.0: 0x00400410 | FSEQ_CNVI_ID
[   95.339111] iwlwifi :01:00.0: 0x00400410 | FSEQ_CNVR_ID
[   95.339129] iwlwifi :01:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP
[   95.339149] iwlwifi :01:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP
[   95.339169] iwlwifi :01:00.0: 0x9061 | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[   95.339197] iwlwifi :01:00.0: 0x0061 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   95.339390] iwlwifi :01:00.0: WRT: Collecting data: ini trigger 4 fired 
(delay=0ms).
[   95.339403] ieee80211 phy0: Hardware restart was 

Bug#1068896: plasma-workspace: system tray settings has 2 options for icon size that don't duit high DPI displays

2024-04-12 Thread Russell Coker
Package: plasma-workspace
Version: 4:5.27.10-3+b1
Severity: normal

On my laptop with a 13" 1440p screen and vertical panel the two size options
are "Small" (too small to see the power level) and "Scale with panel width"
which uses too much screen space.  I think we need a medium option, maybe
"Scale with half panel width".

I'll attach screen-shots showing the differences after the bug report is
created.

-- System Information:
Debian Release: trixie/sid
Architecture: amd64 (x86_64)

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages plasma-workspace depends on:
ii  dbus-user-session [default-dbus-session-bus] 1.14.10-4+b1
ii  dbus-x11 [dbus-session-bus]  1.14.10-4+b1
ii  drkonqi  5.27.10-1+b1
ii  frameworkintegration 5.107.0-3
ii  gdb-minimal [gdb]13.2-1+b1
ii  init-system-helpers  1.66
ii  iso-codes4.16.0-1
ii  kactivitymanagerd5.27.10-1+b1
ii  kded55.107.0-1+b1
ii  kinit5.107.0-1+b1
ii  kio  5.107.0-1+b2
ii  kpackagetool55.107.0-1+b2
ii  kwin-common  4:5.27.10-1+b1
ii  libappstreamqt5-31.0.2-1+b1
ii  libc62.37-17
ii  libcolorcorrect5 4:5.27.10-3+b1
ii  libcrypt11:4.4.36-4
ii  libfontconfig1   2.15.0-1.1
ii  libfreetype6 2.13.2+dfsg-1+b3
ii  libgcc-s114-20240330-1
ii  libgps30t64  3.25-3+b1
ii  libice6  2:1.0.10-1
ii  libicu72 72.1-4+b1
ii  libkf5activities55.107.0-1+b2
ii  libkf5activitiesstats1   5.107.0-1+b2
ii  libkf5archive5   5.107.0-1+b2
ii  libkf5authcore5  5.107.0-1+b2
ii  libkf5baloo5 5.107.0-1+b1
ii  libkf5bookmarks5 5.107.0-1+b2
ii  libkf5calendarevents55.107.0-1+b2
ii  libkf5completion55.107.0-1+b2
ii  libkf5config-bin 5.107.0-1+b2
ii  libkf5configcore55.107.0-1+b2
ii  libkf5configgui5 5.107.0-1+b2
ii  libkf5configwidgets5 5.107.0-2+b2
ii  libkf5coreaddons55.107.0-1+b2
ii  libkf5crash5 5.107.0-1+b2
ii  libkf5dbusaddons55.107.0-1+b2
ii  libkf5declarative5   5.107.0-1+b2
ii  libkf5globalaccel-bin5.107.0-2+b2
ii  libkf5globalaccel5   5.107.0-2+b2
ii  libkf5guiaddons5 5.107.0-1+b2
ii  libkf5holidays5  1:5.107.0-1+b2
ii  libkf5i18n5  5.107.0-1+b2
ii  libkf5iconthemes55.107.0-1+b2
ii  libkf5idletime5  5.107.0-1+b2
ii  libkf5jobwidgets55.107.0-1+b2
ii  libkf5kcmutils5  5.107.0-2+b2
ii  libkf5kexiv2-15.0.0  23.04.2-2+b1
ii  libkf5kiocore5   5.107.0-1+b2
ii  libkf5kiofilewidgets55.107.0-1+b2
ii  libkf5kiogui55.107.0-1+b2
ii  libkf5kiowidgets55.107.0-1+b2
ii  libkf5networkmanagerqt6  5.107.0-1+b1
ii  libkf5newstuff5  5.107.0-2+b2
ii  libkf5newstuffcore5  5.107.0-2+b2
ii  libkf5newstuffwidgets5   5.107.0-2+b2
ii  libkf5notifications5 5.107.0-1+b2
ii  libkf5notifyconfig5  5.107.0-1+b2
ii  libkf5package5   5.107.0-1+b2
ii  libkf5parts5 5.107.0-1+b2
ii  

Bug#1068895: iwlwifi: Scanning twice on AX210 card causes crash

2024-04-12 Thread Adam Baxter
Package: src:linux
Version: 6.1.76-1
Severity: important
X-Debbugs-Cc: deb...@voltagex.org

Dear Maintainer,


   * What led up to the situation?
Running iwlist scanning twice causes this crash - first invocation works, 
second time I get "wlp1s0Interface doesn't support scanning : Input/output 
error"
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Removing the module and modprobing it again restores the functionality - for 
one scan only.
This machine has Ethernet connected so it's not a huge issue
   * What was the outcome of this action?
Some kind of panic
   * What outcome did you expect instead?
Scanning twice to work fine.


-- Package-specific info:
** Version:
Linux version 6.1.0-18-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.1.0-18-amd64 
root=UUID=5cf14832-bc35-4527-9493-ac0719d68469 ro quiet

** Tainted: WOE (12800)
 * kernel issued warning
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

No idea what I've loaded but it's not related to this card.

** Kernel log:
[4570550.548134] iwlwifi :01:00.0: 0x001F010D | last host cmd
[4570550.548141] iwlwifi :01:00.0: 0x | isr status reg
[4570550.548170] iwlwifi :01:00.0: IML/ROM dump:
[4570550.548177] iwlwifi :01:00.0: 0x0B03 | IML/ROM error/state
[4570550.548205] iwlwifi :01:00.0: 0x7FFC | IML/ROM data1
[4570550.548231] iwlwifi :01:00.0: 0x0090 | IML/ROM WFPM_AUTH_KEY_0
[4570550.548260] iwlwifi :01:00.0: Fseq Registers:
[4570550.548277] iwlwifi :01:00.0: 0x6100 | FSEQ_ERROR_CODE
[4570550.548302] iwlwifi :01:00.0: 0x00440007 | FSEQ_TOP_INIT_VERSION
[4570550.548327] iwlwifi :01:00.0: 0x00080009 | FSEQ_CNVIO_INIT_VERSION
[4570550.548353] iwlwifi :01:00.0: 0xA652 | FSEQ_OTP_VERSION
[4570550.548371] iwlwifi :01:00.0: 0x0002 | FSEQ_TOP_CONTENT_VERSION
[4570550.548396] iwlwifi :01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[4570550.548421] iwlwifi :01:00.0: 0x00400410 | FSEQ_CNVI_ID
[4570550.548439] iwlwifi :01:00.0: 0x00400410 | FSEQ_CNVR_ID
[4570550.548458] iwlwifi :01:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP
[4570550.548478] iwlwifi :01:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP
[4570550.548499] iwlwifi :01:00.0: 0x9061 | 
CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[4570550.548526] iwlwifi :01:00.0: 0x0061 | 
CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[4570550.548717] iwlwifi :01:00.0: WRT: Collecting data: ini trigger 4 
fired (delay=0ms).
[4570550.548731] ieee80211 phy13: Hardware restart was requested
[4570550.548757] iwlwifi :01:00.0: FW error in SYNC CMD SCAN_REQ_UMAC
[4570550.548776] CPU: 2 PID: 3800801 Comm: iwlist Tainted: GW  OE  
6.1.0-18-amd64 #1  Debian 6.1.76-1
[4570550.548787] Hardware name: AZW U59/U59, BIOS JTKT001 05/05/2022
[4570550.548792] Call Trace:
[4570550.548800]  
[4570550.548808]  dump_stack_lvl+0x44/0x5c
[4570550.548830]  iwl_trans_txq_send_hcmd+0x376/0x380 [iwlwifi]
[4570550.548890]  ? cpuusage_read+0x10/0x10
[4570550.548902]  iwl_trans_send_cmd+0x62/0xf0 [iwlwifi]
[4570550.548948]  iwl_mvm_send_cmd+0x12/0x40 [iwlmvm]
[4570550.548990]  iwl_mvm_reg_scan_start+0x398/0x490 [iwlmvm]
[4570550.549047]  iwl_mvm_mac_hw_scan+0x4a/0x70 [iwlmvm]
[4570550.549083]  drv_hw_scan+0x40/0x130 [mac80211]
[4570550.549204]  __ieee80211_start_scan+0x255/0x6f0 [mac80211]
[4570550.549310]  ? cfg80211_wext_siwscan+0xb9/0x3f0 [cfg80211]
[4570550.549435]  ieee80211_request_scan+0x2b/0x50 [mac80211]
[4570550.549542]  rdev_scan+0x25/0xd0 [cfg80211]
[4570550.549656]  cfg80211_wext_siwscan+0x2d6/0x3f0 [cfg80211]
[4570550.549768]  ioctl_standard_iw_point+0x221/0x3b0
[4570550.549781]  ? cfg80211_unlink_bss+0xd0/0xd0 [cfg80211]
[4570550.549892]  ioctl_standard_call+0xa6/0xd0
[4570550.549903]  wext_handle_ioctl+0x156/0x190
[4570550.549914]  sock_ioctl+0x1d2/0x330
[4570550.549926]  __x64_sys_ioctl+0x8d/0xd0
[4570550.549936]  do_syscall_64+0x58/0xc0
[4570550.549945]  ? exit_to_user_mode_prepare+0x40/0x1e0
[4570550.549954]  ? syscall_exit_to_user_mode+0x27/0x40
[4570550.549962]  ? do_syscall_64+0x67/0xc0
[4570550.549968]  ? exit_to_user_mode_prepare+0x40/0x1e0
[4570550.549976]  entry_SYSCALL_64_after_hwframe+0x64/0xce
[4570550.549988] RIP: 0033:0x7f184baf8c5b
[4570550.549997] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 
00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 
00 f0 ff ff 77 1c 48 8b 44 24 18 64 48 2b 04 25 28 00 00
[4570550.550004] RSP: 002b:7ffcb4407b90 EFLAGS: 0246 ORIG_RAX: 
0010
[4570550.550014] RAX: ffda RBX: 55cad3c522a0 RCX: 
7f184baf8c5b
[4570550.550019] RDX: 7ffcb4407c60 RSI: 8b18 RDI: 
0003
[4570550.550023] RBP: 7ffcb4407d00 R08: 0009 R09: 


Bug#1068894: dokuwiki: Get error accessing syntax help page.

2024-04-12 Thread Peter Chubb
Package: dokuwiki
Version: 0.0.20220731.a-2
Severity: normal

Dear Maintainer,

Visiting the 'syntax help' page produces the message,
"TypeError: implode(): Argument #2 ($array) must be of type ?array, 
string given"


This has been reported and fixed upstream at 
https://github.com/dokuwiki/dokuwiki/issues/4087

Packaging the new upstream version would fix this and bug  #1067025



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

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

Versions of packages dokuwiki depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  javascript-common  11+nmu1
ii  libjs-jquery   3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-cookie12-4
ii  libjs-jquery-ui1.13.2+dfsg-1
ii  libphp-simplepie   1.3.1+dfsg-5
ii  perl   5.36.0-7+deb12u1
ii  php2:8.2+93
ii  php-geshi  1.0.9.1-1
ii  php-phpseclib  2.0.42-1+deb12u1
ii  php-random-compat  2.0.21-1
ii  php-xml2:8.2+93
ii  php8.2 [php]   8.2.7-1~deb12u1
ii  php8.2-xml [php-xml]   8.2.7-1~deb12u1
ii  ucf3.0043+nmu1

Versions of packages dokuwiki recommends:
ii  imagemagick  8:6.9.11.60+dfsg-1.6
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.6
ii  php-ldap 2:8.2+93
ii  php8.2-cli [php-cli] 8.2.7-1~deb12u1
ii  php8.2-ldap [php-ldap]   8.2.7-1~deb12u1
ii  wget 1.21.3-1+b2

Versions of packages dokuwiki suggests:
pn  libapache2-mod-xsendfile  

-- Configuration Files:
/etc/dokuwiki/mime.conf changed [not included]
/etc/dokuwiki/plugins.local.php changed [not included]

-- debconf information:
  dokuwiki/wiki/policy: public
  dokuwiki/wiki/failpass:
* dokuwiki/system/restart-webserver: false
  dokuwiki/wiki/email: webmaster@localhost
* dokuwiki/system/documentroot: /
* dokuwiki/system/accessible: global
* dokuwiki/system/writeconf: true
* dokuwiki/wiki/title: TS Wiki
  dokuwiki/wiki/fullname: DokuWiki Administrator
* dokuwiki/system/writeplugins: true
  dokuwiki/wiki/superuser: admin
* dokuwiki/system/purgepages: false
  dokuwiki/system/localnet: 10.0.0.0/24
* dokuwiki/wiki/acl: true
* dokuwiki/wiki/license: cc-by-sa
* dokuwiki/system/configure-webserver: apache2



Bug#1065623: reverse dependencies

2024-04-12 Thread Scott Kitterman
On Mon, 25 Mar 2024 18:48:44 + (UTC) Thorsten Alteholz 
 wrote:
> Control: tags -1 + moreinfo
> 
> Hi,
> 
> there are reverse dependencies that need to be taken care of:
> 
> 
> Checking reverse dependencies...
> # Broken Depends:
> baresip: baresip-x11
> 
> # Broken Build-Depends:
> baresip: libomxil-bellagio-dev
> kodi: libomxil-bellagio-dev
> vlc: libomxil-bellagio-dev
> 
> 
> In case they matter, this needs to be addressed first. Please remove the 
> moreinfo tag once that is done.
> 
>Thorsten

Baresip is not resolved in Unstable.  Please don't remove the moreinfo tag 
again until ALL the rdepends are taken care of.

Scott K

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


Bug#1067639: sasl2-bin: terminates with smashed stack and kills qemu-user?!

2024-04-12 Thread Thorsten Glaser
Bernhard Übelacker dixit:

> On Thu, 4 Apr 2024 21:00:59 + (UTC) Thorsten Glaser  
> wrote:
>> Sometimes, it does not crash with a smashed stack but instead:
>>
>> Setting up sasl2-bin (2.1.28+dfsg1-6+b1) ...
>> BDB0002 __fop_file_setup:  Retry limit (100) exceeded
>> saslpasswd2: generic failure
>
> This looks to be a result of the pre-existing /etc/__db.sasldb2.
> If this file gets removed the stack smashing occurs again.

Right, I got there as well but not any further.

> By some experimenting I could convince gdb to load the debug symbols.

Massive detective work, thanks!

> And the stack seems to point into function __os_unique_id from libdb-5.3.so.
>
> Unfortunately I am not sure where the canary gets overwritten.

I had an immediate hunch as I saw this:

> 38  __os_gettime(env, , 1);

And:

> (gdb) ptype /o v
> type = struct {
> /*  0  |   8 */time_t tv_sec;
> /*  8  |   4 */long tv_nsec;
>
>   /* total size (bytes):   12 */
> }

This is, in the source:

typedef struct {
time_t  tv_sec; /* seconds */
#ifdef HAVE_MIXED_SIZE_ADDRESSING
int32_t tv_nsec;
#else
longtv_nsec;/* nanoseconds */
#endif
} db_timespec;

Compare the newer system header:

struct timespec
{
#ifdef __USE_TIME_BITS64
  __time64_t tv_sec;/* Seconds.  */
#else
  __time_t tv_sec;  /* Seconds.  */
#endif
#if __WORDSIZE == 64 \
  || (defined __SYSCALL_WORDSIZE && __SYSCALL_WORDSIZE == 64) \
  || (__TIMESIZE == 32 && !defined __USE_TIME_BITS64)
  __syscall_slong_t tv_nsec;/* Nanoseconds.  */
#else
# if __BYTE_ORDER == __BIG_ENDIAN
  int: 32;   /* Padding.  */
  long int tv_nsec;  /* Nanoseconds.  */
# else
  long int tv_nsec;  /* Nanoseconds.  */
  int: 32;   /* Padding.  */
# endif
#endif
};

This is actually longer and (IMHO) really stupid. But Linux has:

struct __kernel_timespec {
__kernel_time64_t   tv_sec; /* seconds */
long long   tv_nsec;/* nanoseconds */
};

So this is actually expected. *checks POSIX* which says:

| The  header shall declare the timespec structure, which shall
| include at least the following members:
|
| time_t tv_sec Whole seconds.
| long tv_nsec  Nanoseconds [0, 999 999 999].

So both the kernel definition (tv_nsec must be long, not long long,
which is incompatible on ILP32 big endian platforms) and the one by
db5.3 (struct timespec may include extra members and be in any order)
actually violate POSIX… *sigh*

And yes, it does cast to struct timespec and passes it
to clock_gettime().

But it does give us a possible fix, which I’ll be testing.

bye,
//mirabilos
-- 
22:20⎜ The crazy that persists in his craziness becomes a master
22:21⎜ And the distance between the craziness and geniality is
only measured by the success 18:35⎜ "Psychotics are consistently
inconsistent. The essence of sanity is to be inconsistently inconsistent



Bug#1067623: FTBFS: error: format ‘%ld’ expects argument of type ‘long int’, but argument 2 has type ‘__time64_t’ {aka ‘long long int’}

2024-04-12 Thread Steve Langasek
Package: acm
Followup-For: Bug #1067623
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru acm-6.0+20200416/debian/patches/64-bit-time-t.patch 
acm-6.0+20200416/debian/patches/64-bit-time-t.patch
--- acm-6.0+20200416/debian/patches/64-bit-time-t.patch 1969-12-31 
16:00:00.0 -0800
+++ acm-6.0+20200416/debian/patches/64-bit-time-t.patch 2024-04-12 
17:30:16.0 -0700
@@ -0,0 +1,22 @@
+Description: use 64-bit-safe format string for time_t
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1067623
+Last-Update: 2024-04-12
+Forwarded: no
+
+Index: acm-6.0+20200416/src/dis/test/disscope.c
+===
+--- acm-6.0+20200416.orig/src/dis/test/disscope.c
 acm-6.0+20200416/src/dis/test/disscope.c
+@@ -239,8 +239,9 @@
+   printf ("Family   %d\n", pdu.hdr.protocol_family);
+   printf ("Exercise id  %d\n", pdu.hdr.exercise_id);
+   dis_timestampToTimeval (_stamp, );
+-  printf ("Time stamp   %ld.%ld\n", tm.tv_sec,
+-  tm.tv_usec / 1000);
++  printf ("Time stamp   %lld.%lld\n",
++  (long long int)tm.tv_sec,
++  (long long int)tm.tv_usec / 1000);
+   switch (pdu.hdr.pdu_type) {
+   case PDUTypeEntityState:
+   printf ("Entity (sim.app.eid) : %d/%d/%d\n",
diff -Nru acm-6.0+20200416/debian/patches/series 
acm-6.0+20200416/debian/patches/series
--- acm-6.0+20200416/debian/patches/series  2022-10-17 08:51:57.0 
-0700
+++ acm-6.0+20200416/debian/patches/series  2024-04-12 17:28:43.0 
-0700
@@ -4,3 +4,4 @@
 fix_paths_in_acm_tcl.patch
 hardening1.patch
 fix_buffer_size.patch
+64-bit-time-t.patch


Bug#1067639: sasl2-bin: terminates with smashed stack and kills qemu-user?!

2024-04-12 Thread Bernhard Übelacker

Hello,
I tried to find some more information, with the help of a prebuilt full-system 
VM image.


On Thu, 4 Apr 2024 21:00:59 + (UTC) Thorsten Glaser  wrote:

Sometimes, it does not crash with a smashed stack but instead:

Setting up sasl2-bin (2.1.28+dfsg1-6+b1) ...
BDB0002 __fop_file_setup:  Retry limit (100) exceeded
saslpasswd2: generic failure


This looks to be a result of the pre-existing /etc/__db.sasldb2.
If this file gets removed the stack smashing occurs again.

By some experimenting I could convince gdb to load the debug symbols.
And the stack seems to point into function __os_unique_id from libdb-5.3.so.

Unfortunately I am not sure where the canary gets overwritten.

Kind regards,
Bernhard





https://people.debian.org/~gio/dqib/
https://gitlab.com/giomasce/dqib/-/artifacts
https://gitlab.com/giomasce/dqib/-/jobs/6565595565/artifacts/download?file_type=archive


apt install gdb sasl2-bin sasl2-bin-dbgsym libsasl2-2-dbgsym 
libsasl2-modules-db-dbgsym
apt install libc6-dbg libc6-dbgsym db-util db5.3-util libldap-2.5-0 
libldap-common libsasl2-2 libsasl2-2-dbgsym libsasl2-modules libsasl2-modules-db


export DEBUGINFOD_URLS="https://debuginfod.debian.net;

rm /etc/__db.sasldb2
echo -e "test\ntest" > exclam

gdb -q
file /usr/sbin/saslpasswd2
run -c 'no:such:user' https://debuginfod.debian.net>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading separate debug info for /usr/sbin/saslpasswd2
(No debugging symbols found in /usr/sbin/saslpasswd2)
(gdb) run -c 'no:such:user' , fname=0xc0605cb9 
"/etc/sasldb2", dname=0x0, type=DB_HASH, flags=1, mode=432) at 
../src/db/db_iface.c:1193
#13 0xc0604248 in ?? ()
#14 0xd00087b0 in ?? ()
#15 0x in ?? ()
(gdb) shell objdump --all-headers 
/usr/lib/m68k-linux-gnu/sasl2/libsasldb.so.2.0.25 | grep .text
 11 .text 27f0  138c  138c  138c  2**2
(gdb) print/x 0x138c + 0xc0602000
$4 = 0xc060338c

(gdb) add-symbol-file /usr/lib/m68k-linux-gnu/sasl2/libsasldb.so.2.0.25 
0xc060338c
add symbol table from file "/usr/lib/m68k-linux-gnu/sasl2/libsasldb.so.2.0.25" 
at
.text_addr = 0xc060338c
(y or n) y
Reading symbols from /usr/lib/m68k-linux-gnu/sasl2/libsasldb.so.2.0.25...
Reading symbols from 
/usr/lib/debug/.build-id/29/c8e688eb61b57bcd21794b5403feefe1272dfd.debug...
(gdb) bt
...
#15 0xc0603572 in sasldb_auxprop_store (glob_context=0x0, sparams=0xd00077b8, 
ctx=0xd0007a58, user=0xeed9 "no:such:user", ulen=12) at 
../../plugins/sasldb.c:258
#16 0xc002d26c in ?? ()
#17 0x in ?? ()
(gdb) shell cat /proc/10276/maps | grep -i -E "^c00"
c000-c002 r-xp  08:01 535730 /usr/lib/m68k-linux-gnu/ld.so.1
c002-c0021000 rw-p  00:00 0
c0021000-c0022000 r--p 00021000 08:01 535730 /usr/lib/m68k-linux-gnu/ld.so.1
c0022000-c0024000 rw-p 00022000 08:01 535730 /usr/lib/m68k-linux-gnu/ld.so.1
c0028000-c003c000 r-xp  08:01 539155 
/usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25
c003c000-c003d000 ---p 00014000 08:01 539155 
/usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25
c003d000-c003e000 r--p 00015000 08:01 539155 
/usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25
c003e000-c003f000 rw-p 00016000 08:01 539155 
/usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25
c004-c01b1000 r-xp  08:01 535733 
/usr/lib/m68k-linux-gnu/libc.so.6
(gdb) shell objdump --all-headers /usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25 | 
grep .text
 12 .text e284  3db0  3db0  3db0  2**2
(gdb) print/x 0x3db0 + 0xc0028000
$5 = 0xc002bdb0
(gdb) add-symbol-file /usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25 0xc002bdb0
add symbol table from file "/usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25" at
.text_addr = 0xc002bdb0
(y or n) y
Reading symbols from /usr/lib/m68k-linux-gnu/libsasl2.so.2.0.25...
Reading symbols from 
/usr/lib/debug/.build-id/0f/8954c0644d1a9efec7973fb3198b8fd7649d5f.debug...
(gdb) set width 0
(gdb) set pagination off
(gdb) bt
...
#17 0xc00366dc in sasl_setpass (conn=0xd0006670, user=0xeed9 "no:such:user", 
pass=0xd0006608 "test\ntest", passlen=9, oldpass=0x0, oldpasslen=0, flags=1) at 
../../lib/server.c:186
#18 0xd0001534 in ?? ()
...
(gdb) shell cat /proc/10276/maps | grep -i -E "^d00"
d000-d0002000 r-xp  08:01 539212 /usr/sbin/saslpasswd2
d0003000-d0004000 r--p 3000 08:01 539212 /usr/sbin/saslpasswd2
d0004000-d0005000 rw-p 4000 08:01 539212 /usr/sbin/saslpasswd2
d0005000-d0026000 rwxp  00:00 0  [heap]
(gdb) shell objdump --all-headers /usr/sbin/saslpasswd2 | grep .text
 13 .text 0950  10b8  10b8  10b8  2**2
(gdb) print/x 0x10b8 + 0xd000
$6 = 0xd00010b8

(gdb) add-symbol-file /usr/sbin/saslpasswd2 0xd00010b8
add symbol table from file "/usr/sbin/saslpasswd2" at
.text_addr = 0xd00010b8
(y or n) y
Reading symbols from /usr/sbin/saslpasswd2...
Reading symbols from 

Bug#1068873: openjdk-21: more m68k patches

2024-04-12 Thread Thorsten Glaser
Dixi quod…
>I’ll recompile with re-enabled alignment on the missing base

Seems to be only one.

--- src/hotspot/share/memory/allocation.hpp~2024-04-12 23:52:54.0 
+
+++ src/hotspot/share/memory/allocation.hpp 2024-04-12 23:52:56.0 
+
@@ -276,7 +276,7 @@ class CHeapObj {
   void operator delete [] (void* p) {
 CHeapObjBase::operator delete[](p);
   }
-};
+} __attribute__ ((aligned (4)));
 
 // Base class for objects allocated on the stack only.
 // Calling new or delete will result in fatal error.

>classes like we have in 17. But if someone has ideas ’til then…

gn8,
//mirabilos
-- 
This space for rent.



Bug#1068873: openjdk-21: more m68k patches

2024-04-12 Thread Thorsten Glaser
Dixi quod…

>>(This is what I found trying to build openjdk-20, but it’ll be
>>needed in 21 as well. Even getting to this point took 13½ days
>>already…)
>
>And turns out that this isn’t the cause.
>
>In 17, we’ve got src/hotspot/share/memory/allocation.hpp to
>align all CHeapObj, StackObj, MetaspaceObj, etc. classes; this
>is gone in 21. So this needs to be brought back instead.

Hmmhmm. Since I’m having to build/debug 20 first…

… in 20, StackObj has its alignment bumped manually,
but CHeapObj doesn’t. MetaspaceObj does, ResourceObj
and ArenaObj don’t, AnyObj does.

So I’m guessing we will want to fix up the allocators instead?
(Though raising the alignment for cases where people allocate
them on the stack may still be useful…)

ArenaObj… is not allocated‽

resource_allocate_bytes uses Thread::current()->resource_area()->allocate_bytes
which uses Amalloc which seems to align well.

AllocateHeap uses os::malloc which uses ::malloc (C function?)
in NMT and normal cases. Huh. MallocHeader is 16 bytes, also okay.
The glibc texinfo docs say…
| The address of a block returned by ‘malloc’ or ‘realloc’ in GNU systems
| is always a multiple of eight (or sixteen on 64-bit systems).  If you
… so that should *also* be okay?! Unless that’s not true, anyway…

#define SIZE_SZ (sizeof (INTERNAL_SIZE_T))
#define MALLOC_ALIGNMENT (2 * SIZE_SZ < __alignof__ (long double) \
  ? __alignof__ (long double) : 2 * SIZE_SZ)

… it should.

So where does the unaligned _futex_barrier member in the
class LinuxWaitBarrier : public CHeapObj come from?

AFAICS, the caller is:

WaitBarrier* SafepointSynchronize::_wait_barrier;
  _wait_barrier = new WaitBarrier(vmthread);

With:

typedef LinuxWaitBarrier WaitBarrierDefault;
template 
class WaitBarrierType : public CHeapObj {
  WaitBarrierImpl _impl;
…
}
typedef WaitBarrierType WaitBarrier;

So the “new WaitBarrier” should call CHeapObj::operator new(size_t size)
TTBOMK (IANAC++Programmer) which calls CHeapObjBase::operator new(size, 
mtInternal)
= AllocateHeap(size, mtInternal)…

Hmmm. But, oops, I see something more:

src/hotspot/share/services/mallocTracker.hpp:  static const size_t 
overhead_per_malloc = sizeof(MallocHeader) + sizeof(uint16_t);

That would dealign things… but MallocTracker::record_malloc
only adds sizeof(MallocHeader) and has an assert (unsure if
NDEBUG though) that checks alignment…

I am lost. I can *see* an under-aligned futex barrier in strace.

19270 futex(0xcf80078a, FUTEX_WAKE_PRIVATE, 2147483647) = -1 EINVAL (Invalid 
argument)

I cannot see how, though.

FWIW, /tmp/buildd/openjdk-20-20.0.2+9/build/jdk/bin/java \
-XX:NativeMemoryTracking=summary -version also crashes, same
with an explicit -XX:NativeMemoryTracking=off :/

I’ll recompile with re-enabled alignment on the missing base
classes like we have in 17. But if someone has ideas ’til then…

Mraw,
//mirabilos
-- 
 exceptions: a truly awful implementation of quite a nice idea.
 just about the worst way you could do something like that, afaic.
 it's like anti-design.   that too… may I quote you on that?
 sure, tho i doubt anyone will listen ;)



Bug#1068891: coreutils: is join -t '' just comm -12?

2024-04-12 Thread Pádraig Brady

On 12/04/2024 23:59, наб wrote:

Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: normal

Dear Maintainer,

POSIX.1-202x/D3:
−t char
Use character char as a separator, for both input and 
output. Every appearance of
char in a line shall be significant. When this option 
is specified, the collating
sequence shall be the same as sort without the −b 
option.
so obviously allowing -t '' is an extension.

Manual:
-t CHAR
   use CHAR as input and output field separator

Important: FILE1 and FILE2 must be sorted on the  join  fields.  E.g.,
use  "sort  -k  1b,1"  if 'join' has no options, or use "join -t ''" if
'sort' has no options.  Note, comparisons honor the rules specified by
'LC_COLLATE'.   If  the  input  is  not sorted and some lines cannot be
joined, a warning message will be given.

So given
$ cat f1
row1f1  1
urow1   f1  2
$ cat f2
row1f2  1
urow2   f2  2
which are stable against both sort and sort -k 1b,1
$ join f?
row1 f1 1 f2 1
$ join f? -t '  '
row1f1  1   f2  1
is all as expected.

But
$ join f? -t ''
returns empty. What would empty -t mean, anyway?
The empty string can either be found at every position
(clearly not the case here, otherwise this'd be joined on r and u)
or at no positions, so
$ cat g1
row1
urow1
$ cat g2
row1
urow2
$ join g? -t ''
row1
which is, well
$ comm g? -12
row1

Somehow I don't feel like this is a good recommendation?


Well sort with no options operates on the whole line.
So the corresponding join -t '' operates on the whole line.

cheers,
Pádraig



Bug#1066315: kraptor: FTBFS: src/main.c:57:5: error: implicit declaration of function ‘mkdir’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Steve Langasek
Package: kraptor
Followup-For: Bug #1066315
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Please find attached a patch for this issue which has been uploaded to
Ubuntu.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch 
kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch
--- kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch   
1969-12-31 16:00:00.0 -0800
+++ kraptor-0.0.20040403+ds/debian/patches/no-implicit-declarations.patch   
2024-04-12 16:42:20.0 -0700
@@ -0,0 +1,18 @@
+Description: add missing include
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/1066315
+Last-Update: 2024-04-12
+Forwarded: no
+
+Index: kraptor-0.0.20040403+ds/src/main.c
+===
+--- kraptor-0.0.20040403+ds.orig/src/main.c
 kraptor-0.0.20040403+ds/src/main.c
+@@ -19,6 +19,7 @@
+ // 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ #include  /* DUMB: musica MOD, XM, etc */
diff -Nru kraptor-0.0.20040403+ds/debian/patches/series 
kraptor-0.0.20040403+ds/debian/patches/series
--- kraptor-0.0.20040403+ds/debian/patches/series   2024-01-04 
16:48:45.0 -0800
+++ kraptor-0.0.20040403+ds/debian/patches/series   2024-04-12 
16:40:54.0 -0700
@@ -14,3 +14,4 @@
 14_create-hidden-kraptor-directory-in-home.patch
 15_reproducible-build.patch
 fix_building_kraptor_with_fix_functions.patch
+no-implicit-declarations.patch


Bug#1068889: coreutils: join -t refuses single-character delimiters as "multi-character tab"s

2024-04-12 Thread Pádraig Brady

On 12/04/2024 23:42, наб wrote:

Package: coreutils
Version: 9.1-1
Version: 9.4-1
Severity: normal

Dear Maintainer,

Yes good:
$ cat f1
row1f1  1
urow1   f1  2
$ cat f2
row1f2  1
urow2   f2  2
$ join f? -t '  '
row1f1  1   f2  1

Not good:
$ cat f1
row1ąf1ą1
urow1ąf1ą2
$ cat f2
row1ąf2ą1
urow2ąf2ą2
$ join f? -t 'ą'
join: multi-character tab ‘ą’

Compare manual:
-t CHAR use CHAR as input and output field separator

Compare POSIX.1-202x/D3, XCU, join, OPTIONS:
−t char
Use character char as a separator, for both input and 
output. Every appearance of
char in a line shall be significant. When this option 
is specified, the collating
sequence shall be the same as sort without the −b 
option.


Please try coreutils 9.5 which has improved multi-byte char support in join



Bug#1068892: coreutils: join -t accepts \0 to mean NUL; doesn't document it

2024-04-12 Thread Pádraig Brady

On 13/04/2024 00:10, наб wrote:

Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: normal

Dear Maintainer,

When trying to decypher -t behaviour for #1068891,
the second empty-string semantic I tried was **(argv + optind),
but that wasn't it. But what /is/ it is -t '\0'; i.e. given
$ cat f1
row1f1  1
urow1   f1  2
$ cat f2
row1f2  1
urow2   f2  2
$ join <(tr '\t' '\0' < f1) <(tr '\t' '\0' < f2) -t '\0' | cat -A
row1^@f1^@1^@f2^@1$
which is great, but the manual doesn't mention this at all.


This is mentioned in the full documentation referenced from the manual



Bug#1068893: python-elgato-streamdeck: Please build -doc package

2024-04-12 Thread Benjamin Drung
Source: python-elgato-streamdeck
Version: 0.9.1+ds-1
Severity: wishlist
X-Debbugs-Cc: bdr...@debian.org

Dear Maintainer,

please build a -doc package containing the documentation.

-- 
Benjamin Drung
Debian & Ubuntu Developer



Bug#1068892: coreutils: join -t accepts \0 to mean NUL; doesn't document it

2024-04-12 Thread наб
Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: normal

Dear Maintainer,

When trying to decypher -t behaviour for #1068891,
the second empty-string semantic I tried was **(argv + optind),
but that wasn't it. But what /is/ it is -t '\0'; i.e. given
$ cat f1
row1f1  1
urow1   f1  2
$ cat f2
row1f2  1
urow2   f2  2
$ join <(tr '\t' '\0' < f1) <(tr '\t' '\0' < f2) -t '\0' | cat -A
row1^@f1^@1^@f2^@1$
which is great, but the manual doesn't mention this at all.

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9+deb12u4
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b6

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


Bug#1066629: ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Peter Pentchev
On Fri, Apr 12, 2024 at 02:56:02PM -0600, Zixing Liu wrote:
> Package: ucspi-tcp
> Followup-For: Bug #1066629
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu noble ubuntu-patch
> Control: tags -1 patch
> 
> Dear Maintainer,
> 
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * debian/patches/0006-implicit-declarations.patch: Add missing
> includes and prototypes.  Closes LP: #2061188.
>   * debian/ipv6-support.patch: Refresh deferred patch.

OK, this is a little creepy :) I am staring at my work-in-progress update of
the ucspi-tcp package and I see a patch named 0006-implicit-declarations.patch 
and
an update to the ipv6-support one :) But mine was not completely done yet,
while yours seems to be.

(and yes, of course, the patch naming is logical)

> Thanks for considering the patch.

Thanks! I will probably upload a new ucspi-tcp version in a couple of days.

G'luck,
Peter

-- 
Peter Pentchev  r...@ringlet.net r...@debian.org p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature


Bug#1068891: coreutils: is join -t '' just comm -12?

2024-04-12 Thread наб
Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: normal

Dear Maintainer,

POSIX.1-202x/D3:
−t char
Use character char as a separator, for both input and 
output. Every appearance of
char in a line shall be significant. When this option 
is specified, the collating
sequence shall be the same as sort without the −b 
option.
so obviously allowing -t '' is an extension.

Manual:
-t CHAR
   use CHAR as input and output field separator

Important: FILE1 and FILE2 must be sorted on the  join  fields.  E.g.,
use  "sort  -k  1b,1"  if 'join' has no options, or use "join -t ''" if
'sort' has no options.  Note, comparisons honor the rules specified by
'LC_COLLATE'.   If  the  input  is  not sorted and some lines cannot be
joined, a warning message will be given.

So given
$ cat f1
row1f1  1
urow1   f1  2
$ cat f2
row1f2  1
urow2   f2  2
which are stable against both sort and sort -k 1b,1
$ join f?
row1 f1 1 f2 1
$ join f? -t '  '
row1f1  1   f2  1
is all as expected.

But
$ join f? -t ''
returns empty. What would empty -t mean, anyway?
The empty string can either be found at every position
(clearly not the case here, otherwise this'd be joined on r and u)
or at no positions, so
$ cat g1
row1
urow1
$ cat g2
row1
urow2
$ join g? -t ''
row1
which is, well
$ comm g? -12
row1

Somehow I don't feel like this is a good recommendation?

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9+deb12u4
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b6

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


Bug#1068890: diffoscope: --hard-timeout option

2024-04-12 Thread Holger Levsen
Package: diffoscope
Version: 264
Severity: wishlist

Dear Maintainer,

currenlty diffoscope has a --timeout option

   --timeout SECONDS
  Best-effort attempt at a global timeout in seconds. If enabled, 
diffoscope will not recurse into any further sub-archives
  after X seconds of total execution time.  (default: no timeout) 
[experimental]

however this doesnt give any guarantees how long diffoscope will be running, so
so far we haven't used it for the RB CI tests, mostly because I'm not sure
what would be a good inner timeout (=for diffoscope) and what would be a good
good outer timeout (=for killing diffoscope from the outside no matter what).

Currently we use 2h as outer timeout, but have no inner timeout. Maybe we should
use --timeout 1h?

Anyhow, about my --hard-timeout option idea:

my idea of "--hard-timeout $time" is that diffoscope terminates itself after
$time, no matter what *and* then re-starts itself with "--max-container-depth 3"
(or whatever is useful to get a glimpse on what files in a Debian package
are different) (probably also with another hard timeout set...) as to guarantee
to always produce meaningful output (especially html output if specified with 
--html).

What do you think?

Else we could also extend the current code for tests.r-b.o/debian, which 
currently
just kills diffoscope after 2h, to then run diffoscope --max-container-depth 3 
:)

https://tests.reproducible-builds.org/debian/index_breakages.html lists
251 pkg/suite/arch combinations where diffoscope runs into a timeout...


& many thanks for rocking diffoscope airlines..! \o/

-- 
cheers,
Holger

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

Bottled water companies don't produce water, they produce plastic bottles.


signature.asc
Description: PGP signature


Bug#1068873: openjdk-21: more m68k patches

2024-04-12 Thread Thorsten Glaser
Dixi quod…

>(This is what I found trying to build openjdk-20, but it’ll be
>needed in 21 as well. Even getting to this point took 13½ days
>already…)

And turns out that this isn’t the cause.

In 17, we’ve got src/hotspot/share/memory/allocation.hpp to
align all CHeapObj, StackObj, MetaspaceObj, etc. classes; this
is gone in 21. So this needs to be brought back instead.



Bug#1068889: coreutils: join -t refuses single-character delimiters as "multi-character tab"s

2024-04-12 Thread наб
Package: coreutils
Version: 9.1-1
Version: 9.4-1
Severity: normal

Dear Maintainer,

Yes good:
$ cat f1
row1f1  1
urow1   f1  2
$ cat f2
row1f2  1
urow2   f2  2
$ join f? -t '  '
row1f1  1   f2  1

Not good:
$ cat f1
row1ąf1ą1
urow1ąf1ą2
$ cat f2
row1ąf2ą1
urow2ąf2ą2
$ join f? -t 'ą'
join: multi-character tab ‘ą’

Compare manual:
-t CHAR use CHAR as input and output field separator

Compare POSIX.1-202x/D3, XCU, join, OPTIONS:
−t char
Use character char as a separator, for both input and 
output. Every appearance of
char in a line shall be significant. When this option 
is specified, the collating
sequence shall be the same as sort without the −b 
option.

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9+deb12u4
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b6

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


Bug#1066483: scrollz: FTBFS: configure: error: Fatal: You must get working getaddrinfo() function.

2024-04-12 Thread Zixing Liu
Package: scrollz
Followup-For: Bug #1066483
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/gcc13.patch: Fix build with GCC 13 and add missing
includes.  Closes LP: #2061184.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru scrollz-2.2.3/debian/patches/gcc13.patch 
scrollz-2.2.3/debian/patches/gcc13.patch
--- scrollz-2.2.3/debian/patches/gcc13.patch1969-12-31 17:00:00.0 
-0700
+++ scrollz-2.2.3/debian/patches/gcc13.patch2024-04-12 16:18:41.0 
-0600
@@ -0,0 +1,131 @@
+Description: Fix build with GCC 13 and add missing includes
+ Also included missing function prototypes
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066483
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/scrollz/+bug/2061184
+Forwarded: no
+Last-Update: 2024-04-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: scrollz/configure
+===
+--- scrollz.orig/configure
 scrollz/configure
+@@ -2317,6 +2317,7 @@ else
+ /* System header to define __stub macros and hopefully few prototypes,
+ which can conflict with char snprintf(); below.  */
+ #include 
++#include 
+ /* Override any gcc2 internal prototype to avoid an error.  */
+ /* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply.  */
+@@ -2368,6 +2369,7 @@ else
+ /* System header to define __stub macros and hopefully few prototypes,
+ which can conflict with char vsnprintf(); below.  */
+ #include 
++#include 
+ /* Override any gcc2 internal prototype to avoid an error.  */
+ /* We use char because int might match the return type of a gcc2
+ builtin and then its argument prototype would still apply.  */
+@@ -2536,6 +2538,7 @@ else
+ #line 2537 "configure"
+ #include "confdefs.h"
+ #include 
++#include 
+ #define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
+ #define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
+ #define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
+@@ -5472,6 +5475,7 @@ else
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ main()
+ {
+Index: scrollz/include/edit.h
+===
+--- scrollz.orig/include/edit.h
 scrollz/include/edit.h
+@@ -72,7 +72,7 @@ extern   u_char  *recv_nick;
+   voidcommand_completion _((u_int, char *));
+   voide_quit _((char *, char *, char *));
+   int check_wait_command _((char *));
+-  
++  int  GrabURL _((char *, char *, char *, char *));
+ #define AWAY_ONE 0
+ #define AWAY_ALL 1
+ 
+Index: scrollz/include/trace.h
+===
+--- scrollz.orig/include/trace.h
 scrollz/include/trace.h
+@@ -29,4 +29,6 @@ void TraceChannelInfo _((int indent, Cha
+ void TraceNickListInfo _((int indent, NickList *nicks));
+ void TraceWindowInfo _((int indent, Window *window));
+ 
++void Trace(long area, char *format, ...);
++
+ #endif
+Index: scrollz/source/edit.c
+===
+--- scrollz.orig/source/edit.c
 scrollz/source/edit.c
+@@ -101,6 +101,7 @@ static voidsend_action _((char *, char
+ 
+ TimerList *PendingTimers = (TimerList *) 0;
+ 
++extern void PopLine(void);
+ /* used with input_move_cursor */
+ #define RIGHT 1
+ #define LEFT 0
+Index: scrollz/source/edit2.c
+===
+--- scrollz.orig/source/edit2.c
 scrollz/source/edit2.c
+@@ -195,6 +195,8 @@ static char *celeawaystr=(char *) 0;
+ static time_t CeleAwayTime=0;
+ #endif
+ extern char *CelerityNtfy;
++extern int  DecryptMessage _((char *, char *));
++extern int  EncryptMessage _((char *, char *));
+ 
+ /* Kicks all unopped people from current channel */
+ void LameKick(command,args,subargs)
+Index: scrollz/source/edit3.c
+===
+--- scrollz.orig/source/edit3.c
 scrollz/source/edit3.c
+@@ -96,6 +96,7 @@ extern NickList * find_in_hash _((Channe
+ 
+ extern void dcc_chat _((char *));
+ extern void dcc_close _((char *));
++extern int  DecryptString _((char *, char *, char *, int, int));
+ 
+ extern char 

Bug#1068888: bookworm-pu: package zookeeper/3.8.0-11+deb12u2

2024-04-12 Thread Bastien Roucariès
Package: release.debian.org
Severity: normal
Tags: bookworm
X-Debbugs-Cc: zookee...@packages.debian.org
Control: affects -1 + src:zookeeper
User: release.debian@packages.debian.org
Usertags: pu


[ Reason ]
CVE-2024-23944 (Closes: #1066947):
An information disclosure in persistent watchers handling was found in
Apache ZooKeeper due to missing ACL check.  It allows an attacker to
monitor child znodes by attaching a persistent watcher (addWatch
command) to a parent which the attacker has already access
to. ZooKeeper server doesn't do ACL check when the persistent watcher
is triggered and as a consequence, the full path of znodes that a
watch event gets triggered upon is exposed to the owner of the
watcher. It's important to note that only the path is exposed by this
vulnerability, not the data of znode, but since znode path can contain
sensitive information like user name or login ID, this issue is
potentially critical.

[ Impact ]
CVE-2024-23944 is not fixed

[ Tests ]
Full upstream testsuite run at build time

[ Risks ]
None know

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

[ Changes ]
See debdiff
diff -Nru zookeeper-3.8.0/debian/changelog zookeeper-3.8.0/debian/changelog
--- zookeeper-3.8.0/debian/changelog	2023-10-29 07:57:11.0 +
+++ zookeeper-3.8.0/debian/changelog	2024-03-25 08:30:56.0 +
@@ -1,3 +1,22 @@
+zookeeper (3.8.0-11+deb12u2) bookworm-security; urgency=medium
+
+  * Team upload
+  * Bug fix: CVE-2024-23944 (Closes: #1066947):
+An information disclosure in persistent watchers handling was found in
+Apache ZooKeeper due to missing ACL check.  It allows an attacker to
+monitor child znodes by attaching a persistent watcher (addWatch
+command) to a parent which the attacker has already access
+to. ZooKeeper server doesn't do ACL check when the persistent watcher
+is triggered and as a consequence, the full path of znodes that a
+watch event gets triggered upon is exposed to the owner of the
+watcher. It's important to note that only the path is exposed by this
+vulnerability, not the data of znode, but since znode path can contain
+sensitive information like user name or login ID, this issue is
+potentially critical.
+  * Add salsa CI
+
+ -- Bastien Roucari??s   Mon, 25 Mar 2024 08:30:56 +
+
 zookeeper (3.8.0-11+deb12u1) bookworm-security; urgency=medium
 
   * Team upload:
diff -Nru zookeeper-3.8.0/debian/patches/0027-CVE-2024-23944-ZOOKEEPER-4799-Refactor-ACL-check-in-.patch zookeeper-3.8.0/debian/patches/0027-CVE-2024-23944-ZOOKEEPER-4799-Refactor-ACL-check-in-.patch
--- zookeeper-3.8.0/debian/patches/0027-CVE-2024-23944-ZOOKEEPER-4799-Refactor-ACL-check-in-.patch	1970-01-01 00:00:00.0 +
+++ zookeeper-3.8.0/debian/patches/0027-CVE-2024-23944-ZOOKEEPER-4799-Refactor-ACL-check-in-.patch	2024-03-25 08:30:56.0 +
@@ -0,0 +1,1223 @@
+From: Andor Molnar 
+Date: Tue, 28 Nov 2023 21:25:00 +0100
+Subject: CVE-2024-23944: ZOOKEEPER-4799: Refactor ACL check in 'addWatch'
+ command
+
+As of today, it is impossible to diagnose which watch events are dropped
+because of ACLs.  Let's centralize, systematize, and log the checks at
+the 'process()' site in the Netty and NIO connections.
+
+(These 'process()' methods contain some duplicated code, and should also
+be refactored at some point.  This series does not change them.)
+
+This patch also adds a substantial number of tests in order to avoid
+unexpected regressions.
+
+Co-authored-by: Patrick Hunt 
+Co-authored-by: Damien Diederen 
+
+origin: https://github.com/apache/zookeeper/commit/65b91d2d9a56157285c2a86b106e67c26520b01d
+bug: https://issues.apache.org/jira/browse/ZOOKEEPER-4799
+bug-debian-security: https://security-tracker.debian.org/tracker/CVE-2024-23944
+---
+ .../apache/zookeeper/server/watch/WatchBench.java  |   6 +-
+ .../java/org/apache/zookeeper/server/DataTree.java |  23 +-
+ .../org/apache/zookeeper/server/DumbWatcher.java   |   4 +-
+ .../org/apache/zookeeper/server/NIOServerCnxn.java |  16 +-
+ .../apache/zookeeper/server/NettyServerCnxn.java   |  17 +-
+ .../org/apache/zookeeper/server/ServerCnxn.java|  10 +-
+ .../org/apache/zookeeper/server/ServerWatcher.java |  29 +
+ .../zookeeper/server/watch/IWatchManager.java  |   7 +-
+ .../zookeeper/server/watch/WatchManager.java   |  15 +-
+ .../server/watch/WatchManagerOptimized.java|  15 +-
+ .../apache/zookeeper/server/MockServerCnxn.java|   4 +-
+ .../zookeeper/server/watch/WatchManagerTest.java   |  14 +-
+ .../zookeeper/test/PersistentWatcherACLTest.java   | 629 +
+ .../zookeeper/test/UnsupportedAddWatcherTest.java  |   9 +-
+ 14 files changed, 763 insertions(+), 35 deletions(-)
+ create mode 100644 

Bug#1068864: coreutils: join -a3 errors "invalid field number" even when no field number given

2024-04-12 Thread Pádraig Brady

On 12/04/2024 14:12, наб wrote:

Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: normal

Dear Maintainer,

$ join -a3 /dev/null /dev/null
join: invalid field number: ‘3’

Not sure where field 3 came from here.


Indeed, that looks to be a copy n paste issue in:
https://github.com/coreutils/coreutils/commit/6f63d53e1

I'll s/field/file/ upstream.

thanks,
Pádraig



Bug#1065270: Unable to open VTK file with appended data that were fine with previous versions (invalid token in vtkXMLDataParser)

2024-04-12 Thread Giuseppe Bilotta
Package: paraview
Version: 5.11.2+dfsg-6+b9
Followup-For: Bug #1065270

The issue is still present with the current version of paraview
(5.11.2+dfsg-6+b9) and libexpat (2.6.2-1), except that now downgrading
to the previous version of expat to work around the issue
is not possible anymore.

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

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

Versions of packages paraview depends on:
ii  libadios2-mpi-c++11-2 2.9.2+dfsg1-13+b1
ii  libavcodec60  10:6.1.1-dmo4
ii  libavformat60 10:6.1.1-dmo4
ii  libavutil58   10:6.1.1-dmo4
ii  libc6 2.37-17
ii  libdouble-conversion3 3.3.0-1+b1
ii  libexpat1 2.6.2-1
ii  libfreetype6  2.13.2+dfsg-1+b3
ii  libgcc-s1 14-20240330-1
ii  libgdal34t64  3.8.5+dfsg-1
ii  libgl2ps1.4   1.4.2+dfsg1-2
ii  libglew2.22.2.0-4+b1
ii  libglx0   1.7.0-1
ii  libgmsh4.12t644.12.1+ds1-1.1+b1
ii  libhdf5-openmpi-103-1t64  1.10.10+repack-3.3
ii  libjpeg62-turbo   1:2.1.5-2+b2
ii  liblz4-1  1.9.4-2
ii  liblzma5  5.6.1+really5.4.5-1
ii  libnetcdf19t641:4.9.2-5+b1
ii  libogg0   1.3.5-3
ii  libopengl01.7.0-1
ii  libopenmpi3t644.1.6-9
ii  libpng16-16t641.6.43-5
ii  libpython3.11t64  3.11.9-1
ii  libpython3.12t64  3.12.3-1
ii  libqt5core5t645.15.10+dfsg-7.2+b1
ii  libqt5gui5t64 5.15.10+dfsg-7.2+b1
ii  libqt5help5   5.15.10-6+b2
ii  libqt5network5t64 5.15.10+dfsg-7.2+b1
ii  libqt5opengl5t64  5.15.10+dfsg-7.2+b1
ii  libqt5widgets5t64 5.15.10+dfsg-7.2+b1
ii  libstdc++614-20240330-1
ii  libswscale7   10:6.1.1-dmo4
ii  libtheora01.1.1+dfsg.1-16.1+b2
ii  libtiff6  4.5.1+git230720-4
ii  libx11-6  2:1.8.7-1
ii  libxcursor1   1:1.2.1-1
ii  libxml2   2.9.14+dfsg-1.3+b2
ii  python3-matplotlib3.6.3-1.1
ii  python3-mpi4py3.1.5-5+b1
ii  tcl [tclsh]   8.6.14
ii  zlib1g1:1.3.dfsg-3.1

Versions of packages paraview recommends:
ii  mpi-default-bin   1.15
ii  paraview-doc  5.11.2+dfsg-6
ii  python3-paraview  5.11.2+dfsg-6+b9

Versions of packages paraview suggests:
pn  h5utils 
ii  hdf5-tools  1.10.10+repack-3.3

-- no debconf information



Bug#1064061: CVE-2023-52160

2024-04-12 Thread Bastien Roucariès
control: tags -1 + patch

Hi,

You will find a merge request for fixing CVE-2023-52160

https://salsa.debian.org/debian/wpa/-/merge_requests/15

I can do a NMU if neeeded

Bastien


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


Bug#1066529: samhain: FTBFS: x_sh_prelude.c:840:42: error: implicit declaration of function ‘isblank’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Zixing Liu
Package: samhain
Followup-For: Bug #1066529
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/gcc13.patch: Add missing includes and use va_copy
compiler builtin.  Closes LP: #2061192.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru samhain-4.1.4/debian/patches/gcc13.patch 
samhain-4.1.4/debian/patches/gcc13.patch
--- samhain-4.1.4/debian/patches/gcc13.patch1969-12-31 17:00:00.0 
-0700
+++ samhain-4.1.4/debian/patches/gcc13.patch2024-04-12 15:20:21.0 
-0600
@@ -0,0 +1,33 @@
+Description: Add missing includes and use va_copy compiler builtin
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066529
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/samhain/+bug/2061192
+Forwarded: no
+Last-Update: 2024-04-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: samhain/src/sh_error.c
+===
+--- samhain.orig/src/sh_error.c
 samhain/src/sh_error.c
+@@ -1584,7 +1584,7 @@ int sh_error_ehead (/*@null@*/const char
+ #if defined(__GNUC__) && defined(__PPC__) && (defined(_CALL_SYSV) || 
defined(_WIN32))
+ #define VA_COPY(ap1, ap2) (*(ap1) = *(ap2))
+ #elif defined(VA_COPY_AS_ARRAY)
+-#define VA_COPY(ap1, ap2) memmove ((ap1), (ap2), sizeof (va_list))
++#define VA_COPY(ap1, ap2) va_copy((ap1), (ap2))
+ #else /* va_list is a pointer */
+ #define VA_COPY(ap1, ap2) ((ap1) = (ap2))
+ #endif
+Index: samhain/src/sh_prelude.c
+===
+--- samhain.orig/src/sh_prelude.c
 samhain/src/sh_prelude.c
+@@ -35,6 +35,7 @@
+ 
+ #include "config_xor.h"
+ 
++#include 
+ #include 
+ #include 
+ #include 
diff -Nru samhain-4.1.4/debian/patches/series 
samhain-4.1.4/debian/patches/series
--- samhain-4.1.4/debian/patches/series 2023-08-15 14:46:14.0 -0600
+++ samhain-4.1.4/debian/patches/series 2024-04-12 15:17:16.0 -0600
@@ -1,2 +1,3 @@
 debian.patch
 configure.patch
+gcc13.patch


Bug#1068887: ucommon: FTBFS on i386 after package hijack

2024-04-12 Thread Bastian Germann

Source: ucommon
Version: 7.0.1-0.3
X-Debbugs-Cc: vor...@debian.org
Severity: serious

Hi Steve,

with your last ucommon NMU you have fixed the armel/armhf builds but you have 
introduced a symbol-based FTBFS on i386:
https://buildd.debian.org/status/fetch.php?pkg=ucommon=i386=7.0.1-0.3=1710782303=0

Also, you have hijacked the package, which has also happened on coin3 and libvformat. It is obvious that this was not 
done intentionally. But please make sure that this does not happen so often. Maybe introduce a check on dput that checks 
the Maintainer field and if it is an upload to Debian and has the XSBC-Original-Maintainer field set, prevent the upload.


I have fixed the Maintainer field in git already. It would be nice if you could 
fix the i386 FTBFS.

Cheers,
Bastian



Bug#1038845: reprotest: transition from /etc/timezone to /etc/localtime

2024-04-12 Thread Vagrant Cascadian
Control: block 1038845 by 1001250

On 2023-06-21, bl...@debian.org wrote:
> reprotest is currently referencing /etc/timezone without support for
> /etc/localtime. /etc/timezone is a legacy interface that is Debian
> specific. The cross-distro standard /etc/localtime (as a symlink to
> the appropriate timezone file), so please switch your package to
> /etc/localtime. tzsetup will stop creating /etc/timezone soon. Note
> that the list of affected source packages was compiled with
> codesearch, so false positives are possible. Thank you. 

This is only in the code running in a qemu virtual machine, although
that is currently broken, so needs to be fixed somehow to remove
/etc/timezone.

live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1066629: ucspi-tcp: FTBFS: tcpserver.c:143:29: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration]

2024-04-12 Thread Zixing Liu
Package: ucspi-tcp
Followup-For: Bug #1066629
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu noble ubuntu-patch
Control: tags -1 patch

Dear Maintainer,

In Ubuntu, the attached patch was applied to achieve the following:

  * debian/patches/0006-implicit-declarations.patch: Add missing
includes and prototypes.  Closes LP: #2061188.
  * debian/ipv6-support.patch: Refresh deferred patch.


Thanks for considering the patch.


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

Kernel: Linux 6.5.0-26-generic (SMP w/10 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ucspi-tcp-0.88/debian/ipv6-support.patch 
ucspi-tcp-0.88/debian/ipv6-support.patch
--- ucspi-tcp-0.88/debian/ipv6-support.patch2024-02-27 02:57:42.0 
-0700
+++ ucspi-tcp-0.88/debian/ipv6-support.patch2024-04-12 14:19:46.0 
-0600
@@ -741,7 +741,7 @@
 index 0948b1a..f06c5a8 100644
 --- a/dns.h
 +++ b/dns.h
-@@ -34,51 +34,60 @@ struct dns_transmit {
+@@ -34,51 +34,61 @@ struct dns_transmit {
unsigned int curserver;
struct taia deadline;
unsigned int pos;
@@ -812,6 +812,7 @@
 -extern int dns_mx_packet(stralloc *,char *,unsigned int);
 -extern int dns_mx(stralloc *,stralloc *);
 +extern int dns_name4(stralloc *,const char *);
++extern int dns_name6(stralloc *,char *);
 +extern int dns_txt_packet(stralloc *,const char *,unsigned int);
 +extern int dns_txt(stralloc *,const stralloc *);
 +extern int dns_mx_packet(stralloc *,const char *,unsigned int);
@@ -1330,11 +1331,6 @@
 index b9892b4..2158ed4 100644
 --- a/dns_random.c
 +++ b/dns_random.c
-@@ -1,3 +1,4 @@
-+#include 
- #include "dns.h"
- #include "taia.h"
- #include "uint32.h"
 @@ -29,7 +30,7 @@ static void surf(void)
}
  }
@@ -1433,8 +1429,8 @@
 index 6f215ac..b0c8e6d 100644
 --- a/dns_rcrw.c
 +++ b/dns_rcrw.c
-@@ -1,16 +1,17 @@
-+#include 
+@@ -1,16 +1,16 @@
+ #include 
  #include "taia.h"
 -#include "env.h"
  #include "byte.h"
@@ -1511,17 +1507,7 @@
 index df12826..9511511 100644
 --- a/dns_transmit.c
 +++ b/dns_transmit.c
-@@ -1,12 +1,15 @@
-+#include 
-+#include 
-+#include 
-+#include 
- #include "socket.h"
--#include "alloc.h"
--#include "error.h"
-+#include 
- #include "byte.h"
--#include "readwrite.h"
+@@ -7,7 +7,8 @@
  #include "uint16.h"
  #include "dns.h"
 +#include "ip6.h"
@@ -1985,7 +1971,7 @@
 +#include "byte.h"
 +
 +extern unsigned int scan_ip6(const char *src,char *ip);
-+extern unsigned int fmt_ip6(char *dest,const char *ip);
++extern unsigned int ip6_fmt(char *dest,char *ip);
 +
 +extern unsigned int scan_ip6_flat(const char *src,char *);
 +extern unsigned int fmt_ip6_flat(char *dest,const char *);
@@ -2357,7 +2343,8 @@
 index 000..cf3b7c1
 --- /dev/null
 +++ b/remoteinfo6.c
-@@ -0,0 +1,98 @@
+@@ -0,0 +1,99 @@
++#include 
 +#include "fmt.h"
 +#include "buffer.h"
 +#include "socket.h"
@@ -3065,7 +3052,8 @@
 index 000..74099e2
 --- /dev/null
 +++ b/socket_tcp6.c
-@@ -0,0 +1,44 @@
+@@ -0,0 +1,45 @@
++#include 
 +#include 
 +#include 
 +#include 
diff -Nru ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch 
ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch
--- ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch  
1969-12-31 17:00:00.0 -0700
+++ ucspi-tcp-0.88/debian/patches/0006-implicit-declarations.patch  
2024-04-12 14:33:32.0 -0600
@@ -0,0 +1,356 @@
+Description: Add missing includes and prototypes
+Author: Zixing Liu 
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066629
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ucspi-tcp/+bug/2061188
+Forwarded: no
+Last-Update: 2024-04-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+Index: ucspi-tcp/dns_random.c
+===
+--- ucspi-tcp.orig/dns_random.c
 ucspi-tcp/dns_random.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "dns.h"
+ #include "taia.h"
+ #include "uint32.h"
+Index: ucspi-tcp/dns_rcrw.c
+===
+--- ucspi-tcp.orig/dns_rcrw.c
 ucspi-tcp/dns_rcrw.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "taia.h"
+ #include "env.h"
+ #include "byte.h"
+Index: ucspi-tcp/remoteinfo.c
+===
+--- ucspi-tcp.orig/remoteinfo.c
 ucspi-tcp/remoteinfo.c
+@@ -1,3 +1,4 @@
++#include 
+ #include "fmt.h"
+ #include "buffer.h"
+ #include "socket.h"
+Index: ucspi-tcp/tcpserver.c
+===
+--- ucspi-tcp.orig/tcpserver.c
 

Bug#1068886: RFP: rust-topgrade -- all-in-one upgrade tool which doesn't try reinventing the wheel

2024-04-12 Thread Carl Johnson
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: kni9p...@anonaddy.me, debian-r...@lists.debian.org

* Package name: rust-topgrade
  Version : 14.0.1
  Upstream Contact: r-darwish
* URL : https://github.com/topgrade-rs/topgrade
* License : GPL-3.0 license
  Programming Lang: Rust
  Description : all-in-one upgrade tool which doesn't try reinventing the 
wheel

Keeping your system up to date usually involves invoking multiple package 
managers. This results in big, non-portable shell one-liners saved in your 
shell. To remedy this, Topgrade detects which tools you use and runs the 
appropriate commands to update them.
It can upgrade firmware, native packages, Flatpak, Docker containers, TLDR, vim 
plugins, ... and pull Git repositories on the host machine as well as on remote 
machines via SSH.



Bug#1068885: Upgrading python3-fife to 0.4.2-6+b1 breaks unknown-horizons

2024-04-12 Thread Evgeny Kapun

Package: python3-fife

Version: 0.4.2-6+b1


After upgrading python3-fife to version 0.4.2-6+b1, unknown-horizons 
fails to launch. The following exception is printed:



Traceback (most recent call last):
  File "/usr/games/unknown-horizons", line 381, in 
    main()
  File "/usr/games/unknown-horizons", line 109, in main
    import horizons.main
  File "/usr/lib/python3/dist-packages/horizons/main.py", line 46, in 


    from horizons.gui import Gui
  File "/usr/lib/python3/dist-packages/horizons/gui/__init__.py", line 
22, in 

    from .gui import Gui
  File "/usr/lib/python3/dist-packages/horizons/gui/gui.py", line 30, 
in 
    from horizons.component.ambientsoundcomponent import 
AmbientSoundComponent
  File 
"/usr/lib/python3/dist-packages/horizons/component/ambientsoundcomponent.py", 
line 24, in 

    from fife.fife import AudioSpaceCoordinate
ImportError: cannot import name 'AudioSpaceCoordinate' from 'fife.fife' 
(/usr/lib/python3/dist-packages/fife/fife.py)



It works fine with version 0.4.2-6.



Bug#1055755: transition: libre/rem/baresip

2024-04-12 Thread Bastian Germann

Control: tags -1 - moreinfo

On Fri, 10 Nov 2023 22:34:49 +0100 Sebastian Ramacher  
wrote:

Did you coordinate this plan with the maintainer of libre?


I am now part of the maintaining team and confirm my request.



Bug#1068884: rust-is-macro: please update to v0.3.5

2024-04-12 Thread Jonas Smedegaard
Source: rust-is-macro
Version: 0.3.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to at least v0.3.5.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYZi4kACgkQLHwxRsGg
ASH/vhAArm5vn8fkI4XmTW1/brVm14FCIcPVcTJYsfm8cSwVnLdECjHZ1IpXpCVm
QMFuoBfR/TzI8biQc8Xtd1rlmftgtTxMa1HhteBdtcUpTjUAR2fvWJMouZ4P8qQd
oD+gaA4xybuUG8e6MaliZfxkkLrMYUOdLa1zp35NjUiduC3lW/bP+o6jKYStXnRi
2rI43M5xIN4pV8H7t8NfsdW0MUhQuJjh3WmnQoiJi11GE5vrbNqjIpYBEZJpHry9
VoggYShSV4tpyNirSR/vGhHpUa81L763WYAmhF6yo49d7LIRZ8EERPa1bjMgoRh3
e0+7CcNyJyfrWE/ErBJxcdJbNp6me0Tm7JSs+olVM/pC1fKPKW/ORqwGXi83Eyll
0+Awq9whIWD6owfuWqNyIEy4xFyHKw7U4SRzs7n5pk4AOudJTrGf5iysFEOl2TW3
iXojqRSX8p3LD0Q1WrViExRWXYis1/ottmPfyOY57XSOWBhXALKLh8lEFH31EIED
Bx+0rnbrZQ1l9rC5pO9Vx+/bb1OQCG3mWokT1ZhPTTySdrg3PdDujuhHkzeKY/nF
hlyS+CY56aBJukJFTYQfK+P6WhDPyi/BNlAm9vHT43ISpUuk112Y+4BiQZA3ruAY
g+SXpCNwx2hcLkM9nEtNOmENa9IruJDGUDDFSrHqr9FdTKIdvt4=
=q/+h
-END PGP SIGNATURE-



Bug#1068883: RM: boost1.81/experimental -- RoQA; superseded by boost1.83; accidentally part of time_t transition

2024-04-12 Thread Bastian Germann

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

Please remove the experimental boost1.81 which was NMUed to experimental on the 
day that it got removed from unstable.



Bug#1067046: RM: pyhanko/experimental -- ROM; An ITP was raised for python-pyhanko, and python-pyhanko is in the NEW queue

2024-04-12 Thread Bastian Germann

Control: reopen -1

On Thu, 11 Apr 2024 08:41:44 -0400 Scott Kitterman  wrote:

No longer in experimental, so closing the bug.


It was never in experimental but it is still in NEW.
The python-pyhanko should stay in NEW but the pyhanko package should be removed.



Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Jeremy Sowden
On 2024-04-12, at 10:58:59 -0700, Xiyue Deng wrote:
> Jeremy Sowden  writes:
> > Control: tags -1 confirmed
> >
> > On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote:
> >> Package: mu4e
> >> Version: 1.12.3-2
> >> Severity: grave
> >> Justification: renders package unusable
> >> 
> >> Dear Maintainer,
> >> 
> >> I upgraded my Sid machine with the latest mu4e and maildir-utils
> >> packages : 1.12.3-2. Emacs isn't able to find the mu4e command
> >> anymore. From *Messages*: "Cannot open load file: No such file or
> >> directory, mu4e" when trying to load the mu4e library (using
> >> use-package).
> >> 
> >> It seems that some files are missing (mu4e.el at least).
> >
> > Confirmed.  Will get this fixed ASAP.  Thanks for the report.
>
> I made a MR[1] with a potential fix.  There is an alternative way to
> do this (where I left a comment[2]) so would like to hear your opinion
> before merging.  Thanks!

D'oh!  Somehow I missed the fact that meson was installing the .el
files, which is why I was copying them from the build directory.  Thank
you for your fresh eyes. :)

I pushed a different fix, so I will revert that and merge yours.

J.


signature.asc
Description: PGP signature


Bug#1068882: rust-either: please update to v1.10.0

2024-04-12 Thread Jonas Smedegaard
Source: rust-either
Version: 1.9.0-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to at least v1.10.0.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYZg/YACgkQLHwxRsGg
ASFXsw//WD8bPSKjfwlXB9g8Ss/xSGVPZewpwWD0XAEtvZIvV8ToF25wB9vDfsMp
eR80BoU49do/hOOoG4LzqUxbGYrilJtU1EBr0tWFOazaN8HLaoIP8ZPjm06bACi0
3zPgsE3FqpRqo5XuK4KRGZVW1+yiiYMovCmVZBLeSIipb2aWBFoXrqgdHmhIbi7h
r9x5+wNPjfMjYcyE0WJUtbbXmDXNNY9aWTKAWpo6XDZMFDjrcKeROqtfCJnvX1NN
6DvAf+BTgeFmqjA+tPdkaFoft8PcMW1JcO9Qq4SKI+AWTE6xSiIKwkOQfU61QuVF
c7vUIBXL81KDMmZpEOv3FVScyKRPbZ//3dEK61DZA0hiolB9uzsLC9psG9oCUR6e
c2DNnFqSQ62kBAaniDikXLzzMsVY9gKn70Zz5HuP5WKQd8lwsDiqwFbL7RJ3RBAy
khhiWtDRx22PXTnf1wQaLcdRv7qAfVVbI6Gw/Yix3iFVeqAEvQoXVcuQDqyyHeGl
8n/1tYbB8XWlL9YBHgWULH6Fm2Fz516nBTVLTMIegKgOlSXWLtC0vSTtfG+uwjwU
o72A9ZFomH1mzTLrAFxKsQ98D+71V0xRAl0t8prY7UAPHDedKv8s5ynTe+qQaYot
mP6+G0L3WcDu/6mPitwO218pFetTi2xpWrymXOmQXZxAAEerwe8=
=WXlI
-END PGP SIGNATURE-



Bug#1068881: rust-serde-json: please update to v1.0.115

2024-04-12 Thread Jonas Smedegaard
Source: rust-serde-json
Version: 1.0.111-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to at least v1.0.115.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYZf+4ACgkQLHwxRsGg
ASGgnQ/8CTKUSQ7wIWpHIIc4EkyjSSnEHTENtUOKPHSrZctMC8/qGRCdEPNxCnXQ
DviwNs7a4P5FuS573bsti4pt+FYil9PZC6rdENC2vdqMCbx58iuyFuDRmj9o2KHl
GhYqx9WSmC5DiJltbU8sL3xSYhPo77hxHLt8xa90JhlzAlWUOz1CCYKA8ZnT5s2a
VNdl9AkPhSJhAP79Bx+Eh5PmM63QxW2VeOGZ4m9kApFxSzIDqkviWGxBY8tEgBUy
I0dMP6ropVK+XA8ZFCt1bu8h+8gP5LlMa5HlohyzKpa1n9Lc+77OTTUIm+oGIoy0
AoDkser3+w4kW0YzVRm6oH+oyDdhgUTUt5bgYruvpKr3N/vT6LGKqFqEgrtbryZu
oc34Uo0P1ffz4zj3AbzgW16EVNMR59Pav5DeB8hqsNNdxXuAko2FVia6e0k+VRy3
fzqQN6sd5TQm8sb8SoO7KTJRm5Nu6txojHcaWRQUP8IrFKJRxEDBSXVHMr6o8l8X
iEnsE+x2vWR4XKvHRocGggMJR7oyuXBGhnL5kZXbWQ9E/GjvQmLUfwC3O1LIN+Sf
f8JdykMfh7nvsq9TlztBdg0knCl8pGjN94Rx1P4rhXjKYsEjxsbpJhim6drGXZh2
5NdxQH2me6QiZVSMH7UmhNmdR3Ks/GW7+tBvsR7SLkc57YIso28=
=wXA2
-END PGP SIGNATURE-



Bug#1068853: reprotest: SyntaxWarning: invalid escape sequence '\;'

2024-04-12 Thread Vagrant Cascadian
On 2024-04-12, Fay Stegerman wrote:
> * Vagrant Cascadian  [2024-04-12 19:29]:
>> On 2024-04-12, Holger Levsen wrote:
>> > when installing reprotest 0.7.27:
>> >
>> > SyntaxWarning: invalid escape sequence '\;'
>> > Setting up reprotest (0.7.27) ...
>> > /usr/lib/python3/dist-packages/reprotest/__init__.py:360: SyntaxWarning: 
>> > invalid escape sequence '\;'
>> >   run_or_tee(['sh', '-ec', 'find %s -type f -exec sha256sum "{}" \;' % 
>> > self.artifact_pattern],
> [...]
>> How exactly did you get this error?
>> 
>> I installed locally, but did not encounter any such issues on package
>> installation just now, and also nothing when manually running a simple
>> test:
>> 
>>   reprotest 'date > date' date
>> WARNING:reprotest:The control build runs on 1 CPU by default, give 
>> --min-cpus to increase this.
>> WARNING:reprotest.build:IGNORING user_group variation; supply more 
>> usergroups with --variations=user_group.available+=USER1:GROUP1;USER2:GROUP2 
>> or alternatively, suppress this warning with --variations=-user_group
>> WARNING:reprotest.build:Not using sudo for domain_host; your build may fail. 
>> See man page for other options.
>> WARNING:reprotest.build:Be sure to `echo 1 > 
>> /proc/sys/kernel/unprivileged_userns_clone` if on a Debian system.
>> --- /tmp/tmp4vqq6736/control
>> +++ /tmp/tmp4vqq6736/experiment-1
>> │   --- /tmp/tmp4vqq6736/control/source-root
>> ├── +++ /tmp/tmp4vqq6736/experiment-1/source-root
>> │ │   --- /tmp/tmp4vqq6736/control/source-root/date
>> │ ├── +++ /tmp/tmp4vqq6736/experiment-1/source-root/date
>> │ │ @@ -1 +1 @@
>> │ │ +L 13 apr   2024 07:27:01 GMT
>> │ │ -Fri Apr 12 05:27:01 GMT 2024
>
> That syntax warning is new in Python 3.12.  And it's correct, one should use 
> raw
> strings (r'...') or two backslashes for escape sequences intended for e.g.
> regexes or shell commands like here, not Python itself.

Ok, finally able to reproduce this by installing python3.12 in the
environment, which is not yet the default python or installed by
default, but obviously will be before too long...

That at least gives me enough to poke at this going forward!

Thanks!

live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1068810: [Pkg-electronics-devel] Bug#1068810:

2024-04-12 Thread Bdale Garbee
Gianfranco Costamagna  writes:

> yes, but the library was renamed in librnd4t64, so either you need to
> depend on the new one, or drop it, to let the auto decrufter finish
> the time64_t transition and decruft it.

Ah, thank you, that's a useful observation.  Since the relevant version
hasn't made it into testing with the changed library names yet, the
easiest course of action is indeed to just drop this dependency, as any
version of librnd4t64 that's ever in testing will be "new enough" to
meet the new sch-rnd requirement.

> Depending on NBS packages is RC critical.

FWIW, I had to look up what "NBS" means in this context.  A new acronym
to me despite being part of Debian since 1994...

Bdale


signature.asc
Description: PGP signature


Bug#1068880: fwbuilder FTBFS: error: debhelper compat level specified both in debian/compat and in debian/control

2024-04-12 Thread Adrian Bunk
Source: fwbuilder
Version: 5.3.7-7
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Jeremy Bícha 

https://buildd.debian.org/status/logs.php?pkg=fwbuilder=5.3.7-7

...
 fakeroot debian/rules clean
dh clean
dh: warning: Please specify the debhelper compat level exactly once.
dh: warning:  * debian/compat requests compat 9.
dh: warning:  * debian/control requests compat 12 via "debhelper-compat (= 12)"
dh: warning: 
dh: warning: Hint: If you just added a build-dependency on debhelper-compat, 
then please remember to remove debian/compat
dh: warning: 
dh: error: debhelper compat level specified both in debian/compat and in 
debian/control
make: *** [debian/rules:13: clean] Error 255


Bug#1068879: rust-serde-derive: please update to v1.0.197

2024-04-12 Thread Jonas Smedegaard
Source: rust-serde-derive
Version: 1.0.195-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Pleas update to at least v1.0.197.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYZeJUACgkQLHwxRsGg
ASHhlw//RfxWkcDM3AFIxAaFXrvbWTwpUrq/oIDSl/LW2xG0r0jtqfymYPvxUAck
+PnQzoSgrJolQ4FTvMnUIk4nJdpng8wUnEMMra0/77/gvjVgXVHBTGOjDgCaDUU1
sn3894V0ISHw02+aUGQHWLnSxankBABOzXIXhVw5/FKQwNPL8ak22R0PYFCME3Gi
JvinA9jMJw1GUzqAnvIMfxFWMSP4GZR/it6On8BPHn1HrTu7ay9NxpnzQ1Mt7Ca4
J9Su1YTEkqu8D9CJBqGIHT0HEOs7sLP0omvC/DvMw1afw6mdAr8zKNVsMEHPDksE
jWuVMoEZOpb95X2BJGsK/Z4LMl4xV6hydTV2xQKJ1b6irWsIwaePezeNMOzrIjU+
kT8FgHFT04ck+KxZrqKvdZfELG4IAlWei+6z0qYkbXkgvHCmE0kDCSqFkDk1fA7K
FlVSuTuyUHxknc23D115gBINYjc3SWQY5GluB5AM2DUiDs5Fs0MhbNWZL/842eYT
LrYAik3L4rrHLH+bwnvi3F0CFIv8oO/DHyhzD5q9K9wSCdCNjQjASy/NH/K7qL86
VYMDqlol+gBGeNsop+sTz/UyrtFA/qAcyGC2e5MCLXTs0Yeqqug848nuRKK6E0x6
BxwSDqjmJhVlQ2Lz8HUgqrtFhhh4k3fAIDCPbixJlvwxe2JMLrg=
=nrwQ
-END PGP SIGNATURE-



Bug#1068878: rust-serde: please update to v1.0.197

2024-04-12 Thread Jonas Smedegaard
Source: rust-serde
Version: 1.0.195-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to at least v1.0.197.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYZeHAACgkQLHwxRsGg
ASFKuBAAhHiQmpeYkYEy6fwtqZyBGgwUVMJMDISEM2jbaCOe/KUmQntdCUUBF5PM
Ea9UVaMllTsWAc3iLuy28LDV7/uDGqLnneSqXbXedr/hEZXtz+zpPX+/TT4c/HV/
KageQcVXYCmfXZ4qtE5B7rOlBN+MK3FGcwFs8Xf6Xlyb5mGtnrp1xnmjs5wnDTGW
lMWoftcnHThRItk5C1PmMqN5Hgdz1lcNMXhDnP+9vdLl6ohbMVZQ4WhJdUftH0te
DnjqNKJKaTrxpU27xkIREhDr3xOPpI7b0iVeCNLHtMkWiZQZCI+22mq7oDnxZE0U
hXm7Cxq6WnXTf8RUOUPl9eCdrlegBk6OQqmyq9iG1DUqSzj8NpbbdwNNJ0KZysBR
q+wGH2KWd9EaaTy1yDAP9Qh0wCZkic9UQJScljZJO6dS8ydL+Fu3b+anCuWstH55
DZ4c8Ww/bfSpx47hUczMhzrgbB1gWA/cIimnEI6xezsxtICEK2H8msQLI08e+WZO
AMYstOTIMt6DmycDt5Ipf97mTa4RUGvPd2ty6p9YbmYyB2VX7M4A2zzkjjeVvM98
mOamvHGHzEbTwwMLDhLRDyet53m3Sjdu17PtOPN7tLzdQgrWJNaf888Y1XS3lMio
99hTBUH9vG8VRKOL8S+tabwVv7bS3+Or03lAU5CXAlUFzKD7pDA=
=hWgB
-END PGP SIGNATURE-



Bug#1068877: virt-manager: README.Debian points to a non-existent document

2024-04-12 Thread Ernesto Domato
Package: virt-manager
Version: 1:4.1.0-3
Severity: wishlist
X-Debbugs-Cc: edom...@gmail.com

Hi,

In README.Debian there's a line that says:

See also /usr/share/doc/libvirt-daemon-system/README.Debian.gz.

Which no longer exists in the package, the directory is even a symlink to
libvirt0 package.

I suggest removing the line to avoid confusions, or restore the file if it's
pertinent.

Thanks.
Ernesto


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

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

Versions of packages virt-manager depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4+b2
ii  gir1.2-gtk-3.0   3.24.41-4
ii  gir1.2-gtk-vnc-2.0   1.3.1-1+b2
ii  gir1.2-gtksource-4   4.8.4-5+b2
ii  gir1.2-libosinfo-1.0 1.11.0-2+b1
ii  gir1.2-libvirt-glib-1.0  5.0.0-2+b3
ii  gir1.2-vte-2.91  0.75.92-1
ii  python3  3.11.8-1
ii  python3-gi   3.48.2-1
ii  python3-gi-cairo 3.48.2-1
ii  python3-libvirt  10.2.0-1
ii  virtinst 1:4.1.0-3

Versions of packages virt-manager recommends:
ii  gir1.2-ayatanaappindicator3-0.1  0.5.93-1+b1
ii  gir1.2-spiceclientglib-2.0   0.42-2+b4
ii  gir1.2-spiceclientgtk-3.00.42-2+b4
ii  libvirt-daemon-system10.2.0-1

Versions of packages virt-manager suggests:
ii  gir1.2-secret-1  0.21.4-1+b1
ii  gnome-keyring46.1-2
pn  python3-guestfs  
pn  ssh-askpass  
ii  virt-viewer  11.0-3+b1

Versions of packages virt-manager is related to:
ii  libvirt-clients  10.2.0-1
ii  libvirt-daemon   10.2.0-1
ii  libvirt0 10.2.0-1
ii  osinfo-db0.20231215-1

-- no debconf information



Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Xiyue Deng
Jeremy Sowden  writes:

> Control: tags -1 confirmed
>
> On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote:
>> Package: mu4e
>> Version: 1.12.3-2
>> Severity: grave
>> Justification: renders package unusable
>> 
>> Dear Maintainer,
>> 
>> I upgraded my Sid machine with the latest mu4e and maildir-utils
>> packages : 1.12.3-2. Emacs isn't able to find the mu4e command
>> anymore. From *Messages*: "Cannot open load file: No such file or
>> directory, mu4e" when trying to load the mu4e library (using
>> use-package).
>> 
>> It seems that some files are missing (mu4e.el at least).
>
> Confirmed.  Will get this fixed ASAP.  Thanks for the report.
>
> J.
>

Hi Jeremy,

I made a MR[1] with a potential fix.  There is an alternative way to do
this (where I left a comment[2]) so would like to hear your opinion
before merging.  Thanks!

-- 
Xiyue Deng

[1] https://salsa.debian.org/emacsen-team/maildir-utils/-/merge_requests/6
[2] https://salsa.debian.org/emacsen-team/maildir-utils/-/merge_requests/6/diffs


signature.asc
Description: PGP signature


Bug#1068775: sbuild-qemu: fails to work, if piuparts is requested, but not installed on the host

2024-04-12 Thread Johannes Schauer Marin Rodrigues
Hi Francesco,

Quoting Francesco Poli (wintermute) (2024-04-11 00:13:51)
> I am trying to set up sbuild-qemu to build (and test) Debian packages.
> 
> After creating the virtual machine image:
> 
>   $ mkdir -p ~/.cache/sbuild/build
>   $ cd /dev/shm
>   $ TMPDIR=/dev/shm mmdebstrap-autopkgtest-build-qemu \
> --size=25G --boot=efi sid unstable-autopkgtest-amd64.img
>   $ mv -i unstable-autopkgtest-amd64.img ~/.cache/sbuild/
> 
> I prepared the following configuration file:
> 
>   $ cat ~/.sbuildrc 
>   $source_only_changes = 1;
>   $autopkgtest_require_success = 1;
>   $lintian_require_success = 0;
>   $piuparts_require_success = 1;
>   $run_autopkgtest = 1;
>   $run_lintian = 1;
>   $run_piuparts = 1;
>   $build_dir = "$HOME/.cache/sbuild/build";
>   
>   # don't remove this, Perl needs it:
>   1;
> 
> I can update the virtual machine (if I create a symlink, see bug [#1061816]):
>
>   $ sbuild-qemu-update --boot=efi unstable-autopkgtest-amd64.img
> 
> [#1061816]: 

I think 1061816 was fixed with 0.85.7 and the changelog was just missing the
"closes" entry:

https://tracker.debian.org/news/1518576/accepted-sbuild-0857-source-into-unstable/

> But, when I try to build a package from withing the unpacked source
> tree:
> 
>   $ sbuild-qemu --boot=efi --overlay-dir=/dev/shm
>   sbuild --dist unstable --purge-build=never --purge-deps=never 
> --chroot-mode=autopkgtest --autopkgtest-virt-server=qemu 
> --autopkgtest-virt-server-opt --overlay-dir=/dev/shm 
> --autopkgtest-virt-server-opt --qemu-architecture=x86_64 
> --autopkgtest-virt-server-opt --ram-size=2048 --autopkgtest-virt-server-opt 
> --cpus=2 --autopkgtest-virt-server-opt --boot=efi 
> --autopkgtest-virt-server-opt 
> /home/$USER/.cache/sbuild/unstable-autopkgtest-amd64.img 
> --bd-uninstallable-explainer apt
> Error reading configuration: PIUPARTS binary 'piuparts' does not exist or is 
> not executable at /usr/share/perl5/Sbuild/Conf.pm line 76.
> 
> Now, piuparts is indeed not installed on the host:
> 
>   $ apt policy piuparts
>   piuparts:
> Installed: (none)
> Candidate: 1.4.1
> Version table:
>1.4.1 800
>   800 http://deb.debian.org/debian testing/main amd64 Packages
>   500 http://deb.debian.org/debian unstable/main amd64 Packages
> 
> However, I thought that setting $run_piuparts = 1 in ~/.sbuildrc caused
> piuparts to be run inside the virtual machine guest system, not on the
> host system!

What made you think that? Is the error message above not clear enough? Do you
think it should be improved to make things clearer? Do you have suggestions for
a message that would've better explained that piuparts needs to be installed on
the host system?

> Hence, I thought that piuparts was going to be automatically installed
> and executed on the guest system (actually on the throw-away overlay).
> And I thought that the same was going to happen for $run_autopkgtest = 1
> and for $run_lintian = 1 ...
> 
> Am I completely off-track?
> What did I fail to understand?
> 
> Why does sbuild-qemu insist that piuparts be installed on the *host*
> system?

Because it needs to be installed on the host. In the same way as autopkgtest
needs to be on the host. What can sbuild improve?

Thanks!

cheers, josch

signature.asc
Description: signature


Bug#1068853: reprotest: SyntaxWarning: invalid escape sequence '\;'

2024-04-12 Thread Holger Levsen
On Fri, Apr 12, 2024 at 10:29:07AM -0700, Vagrant Cascadian wrote:
> How exactly did you get this error?

upgrading my sid schroot. just confirmed the bug by removing it there
and installing it again. then I mounted /proc but the bug is still
there. /dev is also populated, though /usr/bin/mount fails with 
"mount: failed to read mtab: No such file or directory".

 
> I installed locally, but did not encounter any such issues on package
> installation just now, and also nothing when manually running a simple
> test:
> 
>   reprotest 'date > date' date

that also fails verbosely here:

$ schroot -- reprotest 'date > date' date
WARNING:reprotest:The control build runs on 1 CPU by default, give --min-cpus 
to increase this.
WARNING:reprotest.build:IGNORING user_group variation; supply more usergroups 
with --variations=user_group.available+=USER1:GROUP1;USER2:GROUP2 or 
alternatively, suppress this warning with --variations=-user_group
WARNING:reprotest.build:Not using sudo for domain_host; your build may fail. 
See man page for other options.
WARNING:reprotest.build:Be sure to `echo 1 > 
/proc/sys/kernel/unprivileged_userns_clone` if on a Debian system.
fusermount: failed to open /etc/mtab: No such file or directory
fusermount: mount failed: Operation not permitted
fusermount: failed to unmount /tmp/reprotest.AQkTKX/build-experiment-1: 
Operation not permitted
cleanup failed with exit code 1
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 862, in run
return 0 if check_func(*check_args) else 1
^^^
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 379, in 
check
local_dists += [proc.send(nv) for nv in zip(bnames[1:], 
build_variations[1:])]
   
^^^
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 379, in 

local_dists += [proc.send(nv) for nv in zip(bnames[1:], 
build_variations[1:])]
^
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 339, in 
corun_builds
bctx.run_build(testbed, build, os.environ, artifact_pattern, 
testbed_build_pre, no_clean_on_error)
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 218, in 
run_build
testbed.check_exec2(build_argv,
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 63, in 
check_exec2
self.bomb('"%s" failed with status %i' % (' '.join(argv), code),
  File "/usr/lib/python3/dist-packages/reprotest/__init__.py", line 70, in bomb
raise _type(m)
reprotest.lib.adtlog.AutopkgtestError: "sh -ec run_build() {
mkdir -p /tmp/reprotest.AQkTKX/build-experiment-1-aux && \
SETARCH_ARCH=$(for a in $(setarch --list); do setarch $a true && echo $a || 
true; done) && \
DROP_ARCH="-v -e ^$(uname -m)\$" && \
WORDSIZE=64 && \
if [ $WORDSIZE -eq 64 ]; then for _ARCH_TO_DROP in armh armv7b armv7l   
  armv8b armv8l arm athlon i386 i486 i586 i686 linux32 mips32 mips 
parisc32 parisc ppc32le ppc32 ppcle ppc s390 sparc32bash 
sparc32 sparc; do DROP_ARCH="$DROP_ARCH -e ^$_ARCH_TO_DROP\$"; 
done; fi && \
SETARCH_ARCH=$(echo "$SETARCH_ARCH" | grep $DROP_ARCH | shuf -n1) && \
KERNEL_VERSION=$(uname -r) && \
if [ ${KERNEL_VERSION#2.6} = $KERNEL_VERSION ]; then 
SETARCH_OPTS=--uname-2.6; fi && \
CPU_MAX=$(nproc) && \
CPU_MIN=$({ echo $CPU_MAX; echo 1; } | sort -n | head -n1) && \
CPU_NUM=$(if [ $CPU_MIN = $CPU_MAX ]; then echo $CPU_MIN; echo 
>&2 "only 1 CPU is available; num_cpus is ineffective"; else shuf 
-i$((CPU_MIN + 1))-$CPU_MAX -n1; fi) && \
export CPU_LIST="$(echo $(shuf -i0-$((CPU_MAX - 1)) -n$CPU_NUM) | tr ' ' 
,)" && \
mv /tmp/reprotest.AQkTKX/build-experiment-1/ 
/tmp/reprotest.AQkTKX/build-experiment-1-before-disorderfs/ && \
mkdir -p /tmp/reprotest.AQkTKX/build-experiment-1/ && \
disorderfs -q --shuffle-dirents=yes 
/tmp/reprotest.AQkTKX/build-experiment-1-before-disorderfs/ 
/tmp/reprotest.AQkTKX/build-experiment-1/ && \
umask 0002 && \
export REPROTEST_BUILD_PATH=/tmp/reprotest.AQkTKX/build-experiment-1/ && \
export REPROTEST_UMASK=$(umask) && \
unshare -r --uts sh -ec '
hostname reprotest-capture-hostname
domainname "reprotest-capture-domainname"
"$@"' - \
faketime +398days+2hours+27minutes \
taskset -a -c $CPU_LIST \
setarch $SETARCH_ARCH $SETARCH_OPTS \
sh -ec 'cd "$REPROTEST_BUILD_PATH"; unset REPROTEST_BUILD_PATH; umask 
"$REPROTEST_UMASK"; unset REPROTEST_UMASK; date > date'
}

cleanup() {
__c=0; \
export PATH="/tmp/reprotest.AQkTKX/bin:$PATH" || __c=$?; \
fusermount -u /tmp/reprotest.AQkTKX/build-experiment-1/ || __c=$?; \
rmdir /tmp/reprotest.AQkTKX/build-experiment-1/ || __c=$?; \
mv /tmp/reprotest.AQkTKX/build-experiment-1-before-disorderfs/ 

Bug#1068853: reprotest: SyntaxWarning: invalid escape sequence '\;'

2024-04-12 Thread Fay Stegerman
* Vagrant Cascadian  [2024-04-12 19:29]:
> On 2024-04-12, Holger Levsen wrote:
> > when installing reprotest 0.7.27:
> >
> > SyntaxWarning: invalid escape sequence '\;'
> > Setting up reprotest (0.7.27) ...
> > /usr/lib/python3/dist-packages/reprotest/__init__.py:360: SyntaxWarning: 
> > invalid escape sequence '\;'
> >   run_or_tee(['sh', '-ec', 'find %s -type f -exec sha256sum "{}" \;' % 
> > self.artifact_pattern],
[...]
> How exactly did you get this error?
> 
> I installed locally, but did not encounter any such issues on package
> installation just now, and also nothing when manually running a simple
> test:
> 
>   reprotest 'date > date' date
> WARNING:reprotest:The control build runs on 1 CPU by default, give --min-cpus 
> to increase this.
> WARNING:reprotest.build:IGNORING user_group variation; supply more usergroups 
> with --variations=user_group.available+=USER1:GROUP1;USER2:GROUP2 or 
> alternatively, suppress this warning with --variations=-user_group
> WARNING:reprotest.build:Not using sudo for domain_host; your build may fail. 
> See man page for other options.
> WARNING:reprotest.build:Be sure to `echo 1 > 
> /proc/sys/kernel/unprivileged_userns_clone` if on a Debian system.
> --- /tmp/tmp4vqq6736/control
> +++ /tmp/tmp4vqq6736/experiment-1
> │   --- /tmp/tmp4vqq6736/control/source-root
> ├── +++ /tmp/tmp4vqq6736/experiment-1/source-root
> │ │   --- /tmp/tmp4vqq6736/control/source-root/date
> │ ├── +++ /tmp/tmp4vqq6736/experiment-1/source-root/date
> │ │ @@ -1 +1 @@
> │ │ +L 13 apr   2024 07:27:01 GMT
> │ │ -Fri Apr 12 05:27:01 GMT 2024

That syntax warning is new in Python 3.12.  And it's correct, one should use raw
strings (r'...') or two backslashes for escape sequences intended for e.g.
regexes or shell commands like here, not Python itself.

- Fay



Bug#1068794: sane-utils: (x)scanimage only works once, a second scan right after the first one fails

2024-04-12 Thread Paul Cobbaut





On 4/12/24 18:55, Jörg Frings-Fürst wrote:


Please contact the developers directly at [2].


Done.
They already had an issue for it.
https://gitlab.com/sane-project/backends/-/issues/742

Paul



Bug#1068408: (No Subject)

2024-04-12 Thread Javier Vilarroig
I'm in the same situation.

Right now I can't use Kicad.

Enviado con el correo electrónico seguro de [Proton Mail](https://proton.me/).

Bug#1068853: reprotest: SyntaxWarning: invalid escape sequence '\;'

2024-04-12 Thread Vagrant Cascadian
On 2024-04-12, Holger Levsen wrote:
> when installing reprotest 0.7.27:
>
> SyntaxWarning: invalid escape sequence '\;'
> Setting up reprotest (0.7.27) ...
> /usr/lib/python3/dist-packages/reprotest/__init__.py:360: SyntaxWarning: 
> invalid escape sequence '\;'
>   run_or_tee(['sh', '-ec', 'find %s -type f -exec sha256sum "{}" \;' % 
> self.artifact_pattern],
> /usr/lib/python3/dist-packages/reprotest/build.py:315: SyntaxWarning: invalid 
> escape sequence '\$'
>   _ = _.append_setup_exec_raw('DROP_ARCH="-v -e ^$(uname -m)\$"')
> /usr/lib/python3/dist-packages/reprotest/build.py:317: SyntaxWarning: invalid 
> escape sequence '\$'
>   _ = _.append_setup_exec_raw('if [ $WORDSIZE -eq 64 ]; then \
> /usr/lib/python3/dist-packages/reprotest/environ.py:10: SyntaxWarning: 
> invalid escape sequence '\w'
>   "path": "(/\w{1,12}){1,4}",
> /usr/lib/python3/dist-packages/reprotest/environ.py:11: SyntaxWarning: 
> invalid escape sequence '\d'
>   "port": "([1-9]\d{0,3}|[1-5]\d{4})",
> /usr/lib/python3/dist-packages/reprotest/environ.py:12: SyntaxWarning: 
> invalid escape sequence '\w'
>   "domain": "\w{1,10}(\.\w{1,10}){0,3}",
> /usr/lib/python3/dist-packages/reprotest/environ.py:13: SyntaxWarning: 
> invalid escape sequence '\w'
>   "password": "\w{1,40}",
> /usr/lib/python3/dist-packages/reprotest/environ.py:14: SyntaxWarning: 
> invalid escape sequence '\w'
>   "username": "\w{2,20}",
> /usr/lib/python3/dist-packages/reprotest/environ.py:113: SyntaxWarning: 
> invalid escape sequence '\w'
>   "REPROTEST_CAPTURE_ENVIRONMENT_UNKNOWN_\w+"]
> /usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py:305: 
> SyntaxWarning: invalid escape sequence '\['
>   script = '''sed -rn 's/^(deb|deb-src) +(\[.*\] *)?([^ 
> ]*(ubuntu.com|debian.org|ftpmaster|file:\/\/\/tmp\/testarchive)[^ ]*) +([^ 
> -]+) +(.*)$/\\1 \\2\\3 \\5-%s \\6/p' /etc/apt/sources.list `ls 
> /etc/apt/sources.list.d/*.list 2>/dev/null|| true` > 
> /etc/apt/sources.list.d/%s.list; for retry in 1 2 3; do apt-get 
> --no-list-cleanup -o Dir::Etc::sourcelist=/etc/apt/sources.list.d/%s.list -o 
> Dir::Etc::sourceparts=/dev/null update 2>&1 && break || sleep 15; done''' % 
> (pocket, pocket, pocket)
> /usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py:320: 
> SyntaxWarning: invalid escape sequence '\/'
>   'for d in %s; do [ ! -d $d ] || touch -r $d %s/${d//\//_}.stamp; done' % (
> /usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py:342: 
> SyntaxWarning: invalid escape sequence '\/'
>   'for d in %s; do s=%s/${d//\//_}.stamp;'
> /usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py:724: 
> SyntaxWarning: invalid escape sequence '\('
>   script = '''d=%(t)s/deps
> /usr/lib/python3/dist-packages/reprotest/lib/adt_testbed.py:1211: 
> SyntaxWarning: invalid escape sequence '\/'
>   script += '''REL=$(sed -rn '/^(deb|deb-src) 
> .*(ubuntu.com|debian.org|ftpmaster|file:\/\/\/tmp\/testarchive)/ { s/^[^ ]+ 
> +(\[.*\] *)?[^ ]* +([^ -]+) +.*$/\\2/p}' $SRCS | head -n1); '''

How exactly did you get this error?

I installed locally, but did not encounter any such issues on package
installation just now, and also nothing when manually running a simple
test:

  reprotest 'date > date' date
WARNING:reprotest:The control build runs on 1 CPU by default, give --min-cpus 
to increase this.
WARNING:reprotest.build:IGNORING user_group variation; supply more usergroups 
with --variations=user_group.available+=USER1:GROUP1;USER2:GROUP2 or 
alternatively, suppress this warning with --variations=-user_group
WARNING:reprotest.build:Not using sudo for domain_host; your build may fail. 
See man page for other options.
WARNING:reprotest.build:Be sure to `echo 1 > 
/proc/sys/kernel/unprivileged_userns_clone` if on a Debian system.
--- /tmp/tmp4vqq6736/control
+++ /tmp/tmp4vqq6736/experiment-1
│   --- /tmp/tmp4vqq6736/control/source-root
├── +++ /tmp/tmp4vqq6736/experiment-1/source-root
│ │   --- /tmp/tmp4vqq6736/control/source-root/date
│ ├── +++ /tmp/tmp4vqq6736/experiment-1/source-root/date
│ │ @@ -1 +1 @@
│ │ +L 13 apr   2024 07:27:01 GMT
│ │ -Fri Apr 12 05:27:01 GMT 2024

live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1068559: [Pkg-zfsonlinux-devel] Bug#1068559: zfs-linux: isolation-machine autopkgtest fails: zfs-test-suite times out (hangs?)

2024-04-12 Thread 陈 晟祺
Hi,

> 2024年4月12日 12:48,Paul Gevers  写道:
> 
> Hi,
> 
> On 12-04-2024 4:42 a.m., 陈 晟祺 wrote:
>> - If I limit the test file size to 1G, quite many tests would fail even with 
>> adequate resources
> 
> Ack. To be fair, I was more thinking to make current test conditional on the 
> available free disk space. But yeah, that might also lead to issues as the 
> test might be randomly skipped.
> 

You got the point. I previously thought that testifies are on disk,
but actually they are in tmpfs and consuming huge memory.
That’s why OOM killer would kick in when writing large files in tests.

> Good, so 2GB memory is not enough for zfs-linux (I assume you ran this test 
> with 2 cores like I did)

Yes, I always use 2 cores. 

> 
> I agree we shouldn't spend too much time on squeezing it into the *current* 
> defaults. I'm still somewhat hoping that we could squeeze out a somewhat 
> smaller memory defaults than 8 GB: does 4 GB work (and if so, how long does 
> it take)?
> 

I am now trying to run tests on 2 core and 4GB memory (and maybe less later).
If the tester itself does not occupy too much RAM, the real requirement for 
resources
is now probably several gigabytes of disk space (currently it’s ~10GB).

I will give more feedback once new results come out.

Thanks,
--
Shengqi Chen



Bug#1061137: Doesn't work on SheevaPlug

2024-04-12 Thread Vagrant Cascadian
On 2024-04-12, Martin Michlmayr wrote:
> * Vagrant Cascadian  [2024-01-18 20:07]:
>> > So we need a stable update with this change.
>> 
>> Thanks everyone!
>> 
>> This is a pretty trivial fix, so including in the next bookworm/stable
>> point release should work!
>
> Is this still planned?

Yes ... I think. :)

Thanks for the reminder!

live well,
  vagrant


signature.asc
Description: PGP signature


Bug#1068564: RFS: emacs-buttercup/1.35-1 -- behaviour-driven testing for Emacs Lisp packages

2024-04-12 Thread Xiyue Deng
Jeremy Sowden  writes:

> On 2024-04-12, at 19:50:58 +0800, Sean Whitton wrote:
>> On Fri 12 Apr 2024 at 12:44pm +01, Jeremy Sowden wrote:
>> > On 2024-04-12, at 17:53:15 +0800, Sean Whitton wrote:
>> > > Do you have your 1.34 upload of buttercup in git, please?
>> >
>> > Yup, it's all on Salsa.
>> 
>> Er.  I got confused, then, didn't I?  Should this RFS be closed?
>
> I uploaded 1.34, and that is what is currently in the emacsen-team repo.
> This bug is for 1.35, which is currently sitting in Xiyue's fork, by the
> looks of it.  I haven't looked at this yet.  I can pick it up over the
> week-end.
>
> J.
>

So I did it again (pushed to my fork but forgot to push to team repo :P)
Just pushed there as well.  Please take another look.  Thanks!

-- 
Xiyue Deng


signature.asc
Description: PGP signature


Bug#1068876: coreutils: join: -a doesn't exclude -v (ought to per POSIX), confusing behaviour when combined

2024-04-12 Thread наб
Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: normal

Dear Maintainer,

Given
$ cat f1
row1f1  1
urow1   f1  2
$ cat f2
row1f2  1
urow2   f2  2
and join(1)
-a FILENUM
   also print unpairable lines from file FILENUM, where FILENUM is 1
   or 2, corresponding to FILE1 or FILE2
-v FILENUM
   like -a FILENUM, but suppress joined output lines
and POSIX.1-202x/D3, XCU, join
100437  SYNOPSIS
100438  join [-a file_number|-v file_number] [-e string] [-o 
list] [-t char]
100439  [-1 field] [-2 field] file1 file2

100460  OPTIONS
100463  −a file_number
100464  Produce a line for each unpairable line in file 
file_number, where file_number is 1 or
100465  2, in addition to the default output. If both −a1 and 
−a2 are specified, all unpairable
100466  lines shall be output.
100482  −v file_number
100483  Instead of the default output, produce a line only for 
each unpairable line in
100484  file_number, where file_number is 1 or 2. If both −v1 
and −v2 are specified, all
100485  unpairable lines shall be output.
we observe:
$ join f?
row1 f1 1 f2 1
$ join -v1 f?
urow1 f1 2
$ join -v1 -a1 f?
urow1 f1 2
$ join -v1 -a2 f?
urow1 f1 2
urow2 f2 2

This does not conform to POSIX (should be refused);
the manual implies some sort of separate accounting for -a and -v
(and the interaxion is not described at all),
but -v 1 appears to just be -v -a1. Why?

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9+deb12u4
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b6

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


Bug#1068629: testng7 backport for bullseye needed for latest Java LTS releases

2024-04-12 Thread Thorsten Glaser
Hi Vladimir,

if you have any suggestions as to what to do best with openjdk-8,
feel free to say.

In Debian, it’s only relevant in unstable, ELTS stretch and jessie,
but for Ubuntu it’s used in more.

bye,
//mirabilos
-- 
15:41⎜ Somebody write a testsuite for helloworld :-)



Bug#1068134: globus-gram-job-manager-scripts: arch:all package depends on pre-t64 library

2024-04-12 Thread Mattias Ellert
Control: found 1068134 7.3-1
Control: notfound 1068134 7.3-2

The bug reported here is already fixed in the version for which the bug
was reported.

This bug was present in the previous version. The current version was
uploaded precisely to fix the problem reported.

Previous version (7.3-1) had

Depends: libglobus-common0 (>= 15)

Current version (7.3-2) has

Depends: libglobus-common0 (>= 15) | libglobus-common0t64 (>= 15)

I.e. it does not depend only on the old package name, but on either the
new or the old. The package is therefore not blocking the t64
transition.

Mattias

sön 2024-03-31 klockan 17:41 +0200 skrev Sebastian Ramacher:
> Source: globus-gram-job-manager-scripts
> Version: 7.3-2
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> 
> globus-gram-job-manager-scripts builds an Architecture: all packages
> depending on a library package involved in the time_t 64 transition.
> This dependency needs to be updated.
> 
> Cheers
> --
> Sebastian Ramacher
> 
> VARNING: Klicka inte på länkar och öppna inte bilagor om du inte
> känner igen avsändaren och vet att innehållet är säkert.
> CAUTION: Do not click on links or open attachments unless you
> recognise the sender and know the content is safe.



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


Bug#1068133: globus-gram-audit: arch:all package depends on pre-t64 library

2024-04-12 Thread Mattias Ellert
Control: found 1068133 5.1-2
Control: notfound 1068133 5.1-3

The bug reported here is already fixed in the version for which the bug
was reported.

This bug was present in the previous version. The current version was
uploaded precisely to fix the problem reported.

Previous version (5.1-2) had

Depends: libglobus-common0 (>= 15)

Current version (5.1-3) has

Depends: libglobus-common0 (>= 15) | libglobus-common0t64 (>= 15)

I.e. it does not depend only on the old package name, but on either the
new or the old. The package is therefore not blocking the t64
transition.

Mattias

sön 2024-03-31 klockan 17:39 +0200 skrev Sebastian Ramacher:
> Source: globus-gram-audit
> Version: 5.1-3
> Severity: serious
> X-Debbugs-Cc: sramac...@debian.org
> 
> globus-gram-audit builds an Architecture: all packages depending on a
> library package involved in the time_t 64 transition. This dependency
> needs to be updated.
> 
> Cheers
> --
> Sebastian Ramacher
> 
> VARNING: Klicka inte på länkar och öppna inte bilagor om du inte
> känner igen avsändaren och vet att innehållet är säkert.
> CAUTION: Do not click on links or open attachments unless you
> recognise the sender and know the content is safe.



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


Bug#1068794: sane-utils: (x)scanimage only works once, a second scan right after the first one fails

2024-04-12 Thread Jörg Frings-Fürst
Hello Paul,

thank you for spending your time helping to make Debian better with this bug
report.
Unfortunately, I do not have a scanner available to investigate the error.

The scanner is not listed in [1]. However, under the only Kyocera scanner listed
there it says "1 pass, ??? dpi, A4", which IMHO points to your error.


Please contact the developers directly at [2].


CU
Jörg


[1] http://sane-project.org/sane-mfgs.html#Z-KYOCERA
[2] https://gitlab.com/sane-project/backends/-/issues


-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB 30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key : 8CA1D25D
CAcert Key S/N : 0E:D4:56


Jörg Frings-Fürst
D-54470 Lieser


git: https://git.jff.email/cgit/

Skype: jff-skype@jff.email
Jami: joergfringsfuerst
Telegram: @joergfringsfuerst
Matrix: @joergff:matrix.snct-gmbh.de

My wish list: 
- Please send me a picture from the nature at your home.






Am Donnerstag, dem 11.04.2024 um 10:42 +0200 schrieb Paul Cobbaut:
> Package: sane-utils
> Version: 1.2.1-2
> Severity: normal
> X-Debbugs-Cc: debianbugreport_20240411+s...@cobbaut.be
> 
> Dear Maintainer,
> 
>    * What led up to the situation?
> 
>A. > Using a Kyocera ECOSYS M5526cdw printer to scan hundreds of pages.
>   Using the
> flatbed, not the document feeder.
> 
> Any scan of a page works fine, but I have to wait about two minutes before
> scanning the next page, otherwise it fails with "device busy".
> 
> 
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> scanimage, with or without the --batch option, only allows for one scan. A
> second scan will fail, providing it is done within about two minutes.
> 
> For example this command will scan perfectly:
> $ scanimage -d 'escl:http://192.168.178.32:9095/eSCL'  --format jpeg --mode
> Gray -o page1.jpg
> 
> This command, executed after flipping the page on the scanner, fails as
> follows:
> $ scanimage -d 'escl:http://192.168.178.32:9095/eSCL'  --format jpeg --mode
> Gray -o page2.jpg
> scanimage: sane_start: Device busy
>  503 Service Unavailable 503 Service Unavailable 503 Service Unavailable 503
> Service Unavailable
> 
> Using the vendor kyocera-sane package makes no difference.
> Using 'escl:http://192.168.178.32:9095' or
> 'escl:http://192.168.178.32:9096' as
> the device name makes no difference.
> The result is identical when using xscanimage in GIMP 2.10 or xsane in GIMP
> 2.8.
> 
> According to one Reddit user on r/Debian it is a known problem.
> 
> 
>    * What outcome did you expect instead?
> 
> I was hoping to use a script to quickly scan hundreds of pages into jpg.
> 
> for i in $(seq -w 12 100)
> do
>  scanimage --format jpeg --mode Gray -o page$i.jpg
>  #sleep 120
> done
> 
> But the script only works when the sleep 120 command is included, which limits
> my scanning ability to 30 pages per hour.
> 
> 
> 
> -- System Information:
> Debian Release: 12.5
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.10.0-28-amd64 (SMP w/24 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
> TAINT_UNSIGNED_MODULE
> Locale: LANG=C.UTF-8, 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 sane-utils depends on:
> ii  adduser    3.134
> ii  debconf [debconf-2.0]  1.5.82
> ii  init-system-helpers    1.65.2
> ii  libavahi-client3   0.8-10
> ii  libavahi-common3   0.8-10
> ii  libc6  2.36-9+deb12u4
> ii  libieee1284-3  0.2.11-14
> ii  libjpeg62-turbo    1:2.1.5-2
> ii  libpng16-16    1.6.39-2
> ii  libsane1   1.2.1-2
> ii  libsystemd0    252.22-1~deb12u1
> ii  libusb-1.0-0   2:1.0.26-1
> ii  libxml2    2.9.14+dfsg-1.3~deb12u1
> ii  update-inetd   4.53
> 
> sane-utils recommends no packages.
> 
> Versions of packages sane-utils suggests:
> ii  avahi-daemon  0.8-10
> ii  unpaper   7.0.0-0.1
> 
> -- Configuration Files:
> /etc/sane.d/saned.conf changed:
> 192.168.178.0/24
> 
> 
> -- debconf information:
>   sane-utils/saned_run: false
>   sane-utils/saned_scanner_group: true



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


Bug#1068875: elpa-magit: Magit hangs when staging chunks over tramp

2024-04-12 Thread Diane Trout
Package: elpa-magit
Version: 3.3.0-3
Severity: normal
X-Debbugs-Cc: none, Diane Trout 

Dear Maintainer,

Hi. I ran into a bug on testing while running emacs 29.2 where staging
chunks in magit sessions over tramp kept hanging. its described in

"Emacs hangs on staging chunks over Tramp"
https://github.com/magit/magit/issues/4720

and was caused by a change in tramp.

"30.0.50; tramp: commit 8c6a463 breaks remotely staging chunks
in magit" https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62093

The tramp part of the fix is in emacs 29.3 but there's a patch needed for
magit as well, and probably a configuration change.
https://github.com/magit/magit/commit/debb9723d9ce8ede802e33c7247ee9fa473907c3


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

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

Versions of packages elpa-magit depends on:
ii  dh-elpa-helper  2.0.17
ii  elpa-dash   2.19.1+git20220608.1.0ac1ecf+dfsg-1
ii  elpa-git-commit 3.3.0-3
ii  elpa-magit-section  3.3.0-3
ii  elpa-with-editor3.3.2-1
ii  emacsen-common  3.0.5
ii  git 1:2.43.0-1

elpa-magit recommends no packages.

elpa-magit suggests no packages.

-- no debconf information



Bug#1068874: rust-anyhow: please update to v1.0.81

2024-04-12 Thread Jonas Smedegaard
Source: rust-anyhow
Version: 1.0.75-1
Severity: normal
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please update to at least v1.0.81.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmYZZOcACgkQLHwxRsGg
ASHOKRAAm0uJK/TsEoRhiubwEMJssn91k6TzKfuqCN+5nqFrdnN5vyf57YdtQwbu
8NmZb2Jkr2o5UnqkaqDeV0ArulsixK81NBTPrTk37Jgfa0NQKEdp9vJilrwKTRSC
T5vLVNIZiot+bna5PNga1v9NM5NxgAP5z6AI6t5cDJsvr7P01OOyNC5TLDdNE4xw
83fz4Za3xQsuRXivVCdz4f8D5r12OnmOobxaX9WZHbLX4VaBcmR0Ebi3H/ebmH8u
E8mrAS2Ft3uRaWmIUt1C3R5BBxODAClHkOfz1qV/cczHUuKiad4iItl7QHEjv9Wy
7yLtUPRF1cxLp1YDunfheOQTO/bw12eeNpCB16DHHecdYt/h7XIpj9+lZ7wSN7zx
JXErTNlhDiXYhpa+AKP4Zjn+x9aAx7IT4wzZrInQRlxZjpKb0stdMMD2et7QMFtS
r1EwUHdwmYT8khyWcIk9BGV2lxNG/0g8oE2lOJ2T1ALimx/sTnoGWc8mBIJ8E+Mg
htcwDKffAehv/mc2oBv8N/kOrDdpOf/zbtyaEdSi+ny7HRCUNH1s153IW9gjotzF
X33mPwR0Pc9rqGjOBWO1gHl2UtqgbxCBImfMF3wvePz8DEzhNA5cNl1aPrprWgM/
M93DP6srAUv35SM+0v7Mo3UKcaQQUybKJFcWGD01vMs73tRz0uY=
=TO2/
-END PGP SIGNATURE-



Bug#1068122: /usr/bin/firefox: clings to USB stick, Debian 12.5 up-to-date, Xfce

2024-04-12 Thread Max Nikulin

On Tue, 9 Apr 2024 14:34:36 +0300 Antti-Pekka Känsälä wrote:

> > I am worried Gmail in a Firefox tab is able to break out of Firefox
> > somehow, gaining unauthorized access to 128 files on a mounted USB
stick.

For my initial bug report, I just quickly did a "wc -l" on a long initial
printout, so I was mistaken to claim those were distinct files, I don't
know if they were.  But now I think it is strange that the same file should
be open so many times, it is wasteful at least and could lead to a cause
for the clinging.


The file is opened once accordingly to the output you posted. It is how 
lsof reports usage in the case of multithread applications. Perhaps 
other ways to deal with files exist, but I am in doubts concerning real 
benefits for multithread applications related to privacy.


As to access to other files, you may try to figure out if Firefox uses 
file picker provided by desktop-portal. Behavior may be different for 
flatpak/snap and deb packages. I am unsure if XFCE uses some 
desktop-portal implementation. This feature is intended to control what 
files an application may access, however in the case of deb package 
there is no barriers.



Maybe it has to do with semi-legitimate virus scanning,


You should know better if you have virus scanning software installed. 
From my point of view, some file indexer should be more probable 
variant (however it should ignore removable devices at least by default).



I continue to worry about my USB stick security.


You may find processes accessing specific files using autitd.

What actions do you expect from Debian maintainers? (I am not a maintainer.)



Bug#1068873: openjdk-21: more m68k patches

2024-04-12 Thread Thorsten Glaser
Source: openjdk-21
X-Debbugs-Cc: t...@mirbsd.de, debian-...@lists.debian.org

Please add the following patch e.g. to debian/patches/m68k-support.diff
for more making implicit alignment assumptions (here by the futex
syscall) explicit:

--- src/hotspot/os/linux/waitBarrier_linux.hpp~ 2024-04-12 18:24:38.584686322 
+0200
+++ src/hotspot/os/linux/waitBarrier_linux.hpp  2024-04-12 18:24:46.768716977 
+0200
@@ -29,7 +29,7 @@
 #include "utilities/globalDefinitions.hpp"
 
 class LinuxWaitBarrier : public CHeapObj {
-  volatile int _futex_barrier;
+  volatile int _futex_barrier __attribute__((__aligned__(4)));
 
   NONCOPYABLE(LinuxWaitBarrier);
 

Thanks!

(This is what I found trying to build openjdk-20, but it’ll be
needed in 21 as well. Even getting to this point took 13½ days
already…)



Bug#1068789: nsis: build fails if version number has buildX or ubuntuX suffix

2024-04-12 Thread Thomas Gaugler
Thanks for making me aware of the issue.

I’d like to fix this issue for other Debian derivatives such as Linux Mint as 
well.

Would the following change work for you?

VER_REVISION=$(shell echo $(firstword $(subst +, ,$(word 
3,$(VERSION_DECOMPOSED | sed 's/[^0-9]//g')

Are there any other suffixes beside build and lowercase $(dpkg-vendor --query 
Vendor) followed by the revision number?




Bug#1064975: RFS: k3conf/0.3-1 [ITP] -- Powerful Diagnostic Tool for Texas Instruments K3 based Processors

2024-04-12 Thread Andrew Davis

On 4/10/24 3:50 PM, Andrey Rakhmatullin wrote:

On Wed, Apr 10, 2024 at 03:05:04PM -0500, Andrew Davis wrote:

is that not right? Maybe my lintian version is old, I'm on v2.114, I'll
see if updating that helps.

2.114 is older than stable, and for packages aimed at unstable you need
to use tools from unstable.



That makes sense, seems my build environment (based on sid) got out of
date and updating man/groff shows the warning now, thanks!

Fixed warnings and pushed new source package.

Thanks,
Andrew



Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Jeremy Sowden
Control: tags -1 confirmed

On 2024-04-12, at 16:56:25 +0200, Clément Calmels wrote:
> Package: mu4e
> Version: 1.12.3-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> I upgraded my Sid machine with the latest mu4e and maildir-utils
> packages : 1.12.3-2. Emacs isn't able to find the mu4e command
> anymore. From *Messages*: "Cannot open load file: No such file or
> directory, mu4e" when trying to load the mu4e library (using
> use-package).
> 
> It seems that some files are missing (mu4e.el at least).

Confirmed.  Will get this fixed ASAP.  Thanks for the report.

J.

> Package version 1.12.3-2:
> $ dpkg -L mu4e
> /.
> /usr
> /usr/lib
> /usr/lib/emacsen-common
> /usr/lib/emacsen-common/packages
> /usr/lib/emacsen-common/packages/compat
> /usr/lib/emacsen-common/packages/compat/mu4e
> /usr/lib/emacsen-common/packages/install
> /usr/lib/emacsen-common/packages/install/mu4e
> /usr/lib/emacsen-common/packages/remove
> /usr/lib/emacsen-common/packages/remove/mu4e
> /usr/share
> /usr/share/doc
> /usr/share/doc/mu4e
> /usr/share/doc/mu4e/NEWS.Debian.gz
> /usr/share/doc/mu4e/changelog.Debian.gz
> /usr/share/doc/mu4e/copyright
> /usr/share/emacs
> /usr/share/emacs/site-lisp
> /usr/share/emacs/site-lisp/elpa-src
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-autoloads.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-config.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-pkg.el
> /usr/share/info
> /usr/share/info/mu4e.info.gz
> /usr/share/doc/mu4e/NEWS.org
> /usr/share/doc/mu4e/README.org.gz
> /usr/share/doc/mu4e/TODO.gz
> /etc/emacs/site-start.d/50mu4e.el
> 
> Package version 1.10.8-2:
> $ dpkg -L mu4e
> /.
> /usr
> /usr/lib
> /usr/lib/emacsen-common
> /usr/lib/emacsen-common/packages
> /usr/lib/emacsen-common/packages/compat
> /usr/lib/emacsen-common/packages/compat/mu4e
> /usr/lib/emacsen-common/packages/install
> /usr/lib/emacsen-common/packages/install/mu4e
> /usr/lib/emacsen-common/packages/remove
> /usr/lib/emacsen-common/packages/remove/mu4e
> /usr/share
> /usr/share/doc
> /usr/share/doc/mu4e
> /usr/share/doc/mu4e/NEWS.Debian.gz
> /usr/share/doc/mu4e/changelog.Debian.gz
> /usr/share/doc/mu4e/changelog.gz
> /usr/share/doc/mu4e/copyright
> /usr/share/emacs
> /usr/share/emacs/site-lisp
> /usr/share/emacs/site-lisp/elpa-src
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-actions.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-autoloads.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-bookmarks.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-compose.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-config.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contacts.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-context.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contrib.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-draft.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-folders.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-headers.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-helpers.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-icalendar.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-lists.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-main.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-mark.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-message.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-modeline.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-notification.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-obsolete.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-org.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-pkg.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-query-items.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-search.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-server.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-speedbar.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-update.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-vars.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-view.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-window.el
> /usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e.el
> /usr/share/info
> /usr/share/info/mu4e.info.gz
> /usr/share/doc/mu4e/NEWS.org
> /usr/share/doc/mu4e/README.org.gz
> /usr/share/doc/mu4e/TODO.gz
> /etc/emacs/site-start.d/50mu4e.el
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.7.9-amd64 (SMP w/24 CPU threads; PREEMPT)
> Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to 

Bug#1068872: libgrokj2k1: upstream repository reset and old releases removed upstream

2024-04-12 Thread Matthias Geerdsen

Package: libgrokj2k1
Severity: normal


Hi,

I noticed that the upstream repository has been cleaned and old commits 
are not available anymore. Also all older releases have been removed 
from GitHub.
An upstream issue has been created about this [1] but has been closed 
without much further information. I just wanted to raise this, as it 
would be good to rule out any security, legal or other concerns which 
might have lead to this decision.


Best
Matthias

[1] https://github.com/GrokImageCompression/grok/issues/358



Bug#1068871: spfquery: Pgm prints dead URL www.openspf.org

2024-04-12 Thread U.Mutlu
Package: spfquery
Version: 1.2.10-7.1~deb11u1
Severity: important
X-Debbugs-Cc: um4...@mutluit.com

Dear Maintainer,

The SPF testing program "spfquery" in its result gives a reference link for 
further info
but which is an old URL ( www.openspf.org ) that's no more active and has been 
replaced
by a new URL ( www.open-spf.org ).
Ie. a user who got this message and is then going to the said old link gets an 
error.
The program should be recompiled after fixing that address in the source code..

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

Kernel: Linux 6.1.0-0.deb11.11-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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 spfquery depends on:
ii  libc6  2.31-13+deb11u6
ii  libspf2-2  1.2.10-7.1~deb11u1

spfquery recommends no packages.

spfquery suggests no packages.

-- no debconf information



Bug#910482: silent failure for 6.9.11.60+dfsg-1.6+deb12u1 when inkscape is not installed

2024-04-12 Thread Boud Roukema

Dear all,

This bug is still present in the current Debian bookworm.

CONTEXT:

Debian/bookworm

$ dpkg -l |grep -E "inkscape|imagemagick"
ii  imagemagick8:6.9.11.60+dfsg-1.6+deb12u1 
  amd64image manipulation programs -- binaries
ii  imagemagick-6-common   8:6.9.11.60+dfsg-1.6+deb12u1 
  all  image manipulation programs -- infrastructure
ii  imagemagick-6.q16  8:6.9.11.60+dfsg-1.6+deb12u1 
  amd64image manipulation programs -- quantum depth Q16

i.e. inkscape is not installed


REPRODUCE:

wget https://upload.wikimedia.org/wikipedia/commons/9/90/World_line2.svg # 
version of 26 June 2008 20:05
wget 
https://upload.wikimedia.org/wikipedia/commons/7/74/Ladder_Paradox_Overview.svg 
# version of 2009-08-24

convert -verbose World_line2.svg -resize 500 W.eps |& tee log.1
convert -verbose Ladder_Paradox_Overview.svg -resize 500 L.eps |& tee log.2

STDOUT+STDERR:

$ cat log.[12]

'inkscape' '/tmp/magick--xCaXnAzMn6TMu2YcffaCk_bNw2IGZBA' 
--export-filename='/tmp/magick-rhLErifp8wZ4D332LJx_ABM0iHpXANep.png' --export-dpi='96' 
--export-background='rgb(100%,100%,100%)' 
--export-background-opacity='0.2212' > 
'/tmp/magick-MWNHBpvNh4Lwt-jVMJZXkgEtANDzORNy' 2>&1
mvg:/tmp/magick-pLnisu3k87MW9GIzRh03yxBbjSvsBZQr=>/tmp/magick-pLnisu3k87MW9GIzRh03yxBbjSvsBZQr
 MVG 675x600 675x600+0+0 16-bit sRGB 58245B 0.200u 0:00.128
World_line2.svg SVG 675x600 675x600+0+0 16-bit sRGB 58245B 0.000u 0:00.000
World_line2.svg=>W.eps SVG 675x600=>500x444 500x444+0+0 16-bit sRGB 1.292MiB 
0.080u 0:00.030
'inkscape' '/tmp/magick-eEqnoa1lh-bR2YQ4wRImT-RpuUqmeu8r' 
--export-filename='/tmp/magick-xVXVTXaZCe4bk3IUC_lD4zzfn5XCIRVB.png' --export-dpi='96' 
--export-background='rgb(100%,100%,100%)' 
--export-background-opacity='0.2212' > 
'/tmp/magick-zvM9MVRkEGWdQArdpXoX7hWFS-3Qn7DO' 2>&1
mvg:/tmp/magick-wUkS3YTrUUaAgYTsUltnJzfghGl8I2Xy=>/tmp/magick-wUkS3YTrUUaAgYTsUltnJzfghGl8I2Xy
 MVG 278x120 278x120+0+0 16-bit sRGB 5200B 0.150u 0:00.148
Ladder_Paradox_Overview.svg SVG 278x120 278x120+0+0 16-bit sRGB 5200B 0.000u 
0:00.000
Ladder_Paradox_Overview.svg=>L.eps SVG 278x120=>500x216 500x216+0+0 16-bit 
Bilevel Gray 33253B 0.040u 0:00.045

Visual checks: 'gv W.eps' looks OK; 'gv L.eps' looks completely blank

I assume that W.eps was created OK without inkscape because the .svg
file has a section with i:pgf ... !CDATA that presumably contains a PGF
image - https://en.wikipedia.org/wiki/Progressive_Graphics_File

WHAT TO DO:

Weak arguments for and against changing from 'Suggests: inkscape' to 
'Recommends: inkscape':

- for - fewer people will have this bug occur and be annoyed at the failure;

- against - inkscape is a medium size package with lots of
dependencies (120 Mb after unpacking for my system, including the
dependencies) and not everyone using imagemagick wants to do svg
conversions.


This does seem like a user feedback problem for upstream. Shouldn't
'convert' be expected to give either a warning or an error to the
user? The fact that it works in one case out of the two in the above
example favours a warning rather than an error.


Cheers
Boud



Bug#1068870: firmware-iwlwifi: No wlan for Wi-Fi 6 AX101, REV=0x351 even with firmware-iwlwifi 20230625-2 or 20230210-5

2024-04-12 Thread alimdi
Package: firmware-iwlwifi
Version: 20230625-2
Severity: important
X-Debbugs-Cc: deb...@moua7.com




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

Kernel: Linux 6.1.0-18-amd64 (SMP w/4 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

firmware-iwlwifi depends on no packages.

firmware-iwlwifi recommends no packages.

Versions of packages firmware-iwlwifi suggests:
ii  initramfs-tools  0.142

-- no debconf information

The wlan interface is not present even if it is detected on startup and 
firmware seems to be loaded.
See dmsg :

[4.069571] iwlwifi :00:14.3: enabling device ( -> 0002)
[4.081750] iwlwifi :00:14.3: firmware: direct-loading firmware 
iwlwifi-QuZ-a0-hr-b0-72.ucode
[4.081771] iwlwifi :00:14.3: api flags index 2 larger than supported by 
driver
[4.081781] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 
89.3.35.37
[4.082502] iwlwifi :00:14.3: loaded firmware version 72.daa05125.0 
QuZ-a0-hr-b0-72.ucode op_mode iwlmvm
[4.206533] iwlwifi :00:14.3: Detected Intel(R) Wi-Fi 6 AX101, REV=0x351
[4.206606] thermal thermal_zone1: failed to read out thermal zone (-61)
[4.383206] iwlwifi :00:14.3: Detected RF HR1 B3, rfid=0x10c000
[5.410407] iwlwifi :00:14.3: Collecting data: trigger 16 fired.
[5.411537] iwlwifi :00:14.3: Start IWL Error Log Dump:
[5.411591] iwlwifi :00:14.3: Transport status: 0x004A, valid: 6
[5.411634] iwlwifi :00:14.3: Loaded firmware version: 72.daa05125.0 
QuZ-a0-hr-b0-72.ucode
[5.411683] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN
[5.411726] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0
[5.411761] iwlwifi :00:14.3: 0x | trm_hw_status1
[5.411796] iwlwifi :00:14.3: 0x004CC13E | branchlink2
[5.411829] iwlwifi :00:14.3: 0x004C25DE | interruptlink1
[5.411864] iwlwifi :00:14.3: 0x004C25DE | interruptlink2
[5.411898] iwlwifi :00:14.3: 0x004CADF8 | data1
[5.411928] iwlwifi :00:14.3: 0x0100 | data2
[5.411959] iwlwifi :00:14.3: 0x | data3
[5.411990] iwlwifi :00:14.3: 0x | beacon time
[5.413065] iwlwifi :00:14.3: 0x0011C5FA | tsf low
[5.414106] iwlwifi :00:14.3: 0x | tsf hi
[5.415136] iwlwifi :00:14.3: 0x | time gp1
[5.416130] iwlwifi :00:14.3: 0x001221B5 | time gp2
[5.417095] iwlwifi :00:14.3: 0x0001 | uCode revision type
[5.418047] iwlwifi :00:14.3: 0x0048 | uCode version major
[5.418988] iwlwifi :00:14.3: 0xDAA05125 | uCode version minor
[5.419897] iwlwifi :00:14.3: 0x0351 | hw version
[5.420781] iwlwifi :00:14.3: 0x18C89001 | board version
[5.421646] iwlwifi :00:14.3: 0x8002FC12 | hcmd
[5.422400] iwlwifi :00:14.3: 0x0002 | isr0
[5.423036] iwlwifi :00:14.3: 0x | isr1
[5.423650] iwlwifi :00:14.3: 0x08F2 | isr2
[5.424245] iwlwifi :00:14.3: 0x00CC | isr3
[5.424821] iwlwifi :00:14.3: 0x | isr4
[5.425308] iwlwifi :00:14.3: 0x | last cmd Id
[5.425738] iwlwifi :00:14.3: 0x004CADF8 | wait_event
[5.426151] iwlwifi :00:14.3: 0x | l2p_control
[5.426558] iwlwifi :00:14.3: 0x | l2p_duration
[5.426949] iwlwifi :00:14.3: 0x | l2p_mhvalid
[5.427327] iwlwifi :00:14.3: 0x | l2p_addr_match
[5.427695] iwlwifi :00:14.3: 0x000B | lmpm_pmg_sel
[5.428060] iwlwifi :00:14.3: 0x | timestamp
[5.428340] iwlwifi :00:14.3: 0x0020 | flow_handler
[5.428656] iwlwifi :00:14.3: Start IWL Error Log Dump:
[5.428930] iwlwifi :00:14.3: Transport status: 0x004A, valid: 7
[5.429204] iwlwifi :00:14.3: 0x2066 | NMI_INTERRUPT_HOST
[5.429473] iwlwifi :00:14.3: 0x | umac branchlink1
[5.429744] iwlwifi :00:14.3: 0x80455E9C | umac branchlink2
[5.430016] iwlwifi :00:14.3: 0x8047257E | umac interruptlink1
[5.430284] iwlwifi :00:14.3: 0xC0081E62 | umac interruptlink2
[5.430557] iwlwifi :00:14.3: 0x0100 | umac data1
[5.430830] iwlwifi :00:14.3: 0xC0081E62 | umac data2
[5.431102] iwlwifi :00:14.3: 0x | umac data3
[5.431374] iwlwifi :00:14.3: 0x0048 | umac major
[5.431646] iwlwifi :00:14.3: 0xDAA05125 | umac minor
[5.431919] iwlwifi :00:14.3: 0x001221B3 | frame pointer
[5.432193] iwlwifi :00:14.3: 0xC0887EFC | stack pointer
[5.432466] iwlwifi :00:14.3: 0x00010C00 | last host cmd
[5.432740] iwlwifi :00:14.3: 0x0004 | isr status reg
[5.433037] iwlwifi 

Bug#1068869: mu4e: Cannot open load file: No such file or directory, mu4e

2024-04-12 Thread Clément Calmels
Package: mu4e
Version: 1.12.3-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I upgraded my Sid machine with the latest mu4e and maildir-utils
packages : 1.12.3-2. Emacs isn't able to find the mu4e command
anymore. From *Messages*: "Cannot open load file: No such file or
directory, mu4e" when trying to load the mu4e library (using
use-package).

It seems that some files are missing (mu4e.el at least).
Package version 1.12.3-2:
$ dpkg -L mu4e
/.
/usr
/usr/lib
/usr/lib/emacsen-common
/usr/lib/emacsen-common/packages
/usr/lib/emacsen-common/packages/compat
/usr/lib/emacsen-common/packages/compat/mu4e
/usr/lib/emacsen-common/packages/install
/usr/lib/emacsen-common/packages/install/mu4e
/usr/lib/emacsen-common/packages/remove
/usr/lib/emacsen-common/packages/remove/mu4e
/usr/share
/usr/share/doc
/usr/share/doc/mu4e
/usr/share/doc/mu4e/NEWS.Debian.gz
/usr/share/doc/mu4e/changelog.Debian.gz
/usr/share/doc/mu4e/copyright
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/elpa-src
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-autoloads.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-config.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.12.3/mu4e-pkg.el
/usr/share/info
/usr/share/info/mu4e.info.gz
/usr/share/doc/mu4e/NEWS.org
/usr/share/doc/mu4e/README.org.gz
/usr/share/doc/mu4e/TODO.gz
/etc/emacs/site-start.d/50mu4e.el

Package version 1.10.8-2:
$ dpkg -L mu4e
/.
/usr
/usr/lib
/usr/lib/emacsen-common
/usr/lib/emacsen-common/packages
/usr/lib/emacsen-common/packages/compat
/usr/lib/emacsen-common/packages/compat/mu4e
/usr/lib/emacsen-common/packages/install
/usr/lib/emacsen-common/packages/install/mu4e
/usr/lib/emacsen-common/packages/remove
/usr/lib/emacsen-common/packages/remove/mu4e
/usr/share
/usr/share/doc
/usr/share/doc/mu4e
/usr/share/doc/mu4e/NEWS.Debian.gz
/usr/share/doc/mu4e/changelog.Debian.gz
/usr/share/doc/mu4e/changelog.gz
/usr/share/doc/mu4e/copyright
/usr/share/emacs
/usr/share/emacs/site-lisp
/usr/share/emacs/site-lisp/elpa-src
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-actions.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-autoloads.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-bookmarks.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-compose.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-config.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contacts.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-context.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-contrib.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-draft.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-folders.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-headers.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-helpers.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-icalendar.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-lists.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-main.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-mark.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-message.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-modeline.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-notification.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-obsolete.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-org.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-pkg.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-query-items.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-search.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-server.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-speedbar.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-update.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-vars.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-view.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e-window.el
/usr/share/emacs/site-lisp/elpa-src/mu4e-1.10.8/mu4e.el
/usr/share/info
/usr/share/info/mu4e.info.gz
/usr/share/doc/mu4e/NEWS.org
/usr/share/doc/mu4e/README.org.gz
/usr/share/doc/mu4e/TODO.gz
/etc/emacs/site-start.d/50mu4e.el


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

Kernel: Linux 6.7.9-amd64 (SMP w/24 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 mu4e depends on:
ii  dh-elpa-helper  2.0.17
ii  emacsen-common  3.0.5
ii  maildir-utils   1.12.3-2

mu4e recommends no packages.

mu4e suggests no packages.

-- no debconf information



Bug#1068868: ITP: python3-pyzmq -- Python bindings for 0MQ

2024-04-12 Thread Luca Boccassi
On Fri, 12 Apr 2024 at 14:39, Cody Scott  wrote:
>
> Package: wnpp
> Severity: wishlist
> Owner: Cody Scott 
> X-Debbugs-Cc: debian-de...@lists.debian.org, cody.sc...@giatec.ca
>
> * Package name: python3-pyzmq
>   Version : 25.1.2
>   Upstream Contact: ZeroMQ 
> * URL : https://pyzmq.readthedocs.io/en/latest/
> * License : BSD
>   Programming Lang: Python
>   Description : Python bindings for 0MQ
>
>
> This will be used by Python applications that use ZeroMQ.
>
> There doesn't appear to be any other Python bindings for ZeroMQ.
>
> I plan to maintain it and I'm looking for a sponsor.

This is already in Debian: https://tracker.debian.org/pkg/pyzmq



Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Guilhem Moulin
On Fri, 12 Apr 2024 at 14:37:16 +0200, Guilhem Moulin wrote:
> What is that “GUI” view?  src:cryptsetup doesn't provide that, I wonder
> if it might be what needs libphtread.

FWIW, I later noticed you used a splash screen (plymouth) and thought it
might be because of that, but I still cannot reproduce the issue in a
bookworm VM upgraded to sid (using d-i's “encrypted LVM” layout + a
splash screen).

>> After a ctrl-alt-del, I got to the console and there it showed an error about
>> libgcc_s.so.1 not available and aborting.

What was that error message exactly?

> If you still have the broken initramfs image, please extract it with
> `unmkinitramfs /path/to/broken.initrd.img /path/to/destdir` and try to
> find which executable / shared library needs libphtread, for instance
> with
>
>cd /path/to/destdir
>for p in $(find -P {usr/,}lib/x86_64-linux-gnu  {usr/,}{,s}bin/ -type f); 
> do objdump -p "$p" 2>/dev/null | grep -q pthread && echo "$p"; done

Erm no, that likely won't work since pthread functions have moved from
libpthread.so.1 to libc.so.6 with glibc 2.34.  Otherwise copy_exec()
would have pulled in libgcc_s.  New attempt:

rm -rf /tmp/initramfs-destdir && \
mkdir -m0700 /tmp/initramfs-destdir && \
unmkinitramfs /path/to/broken.initrd.img /tmp/initramfs-destdir && \
for p in $(find /tmp/initramfs-destdir/main -type f | sort); do \
  objdump -T "$p" 2>&1 | grep pthread_exit && echo "^^ $p"; \
done

-- 
Guilhem.


signature.asc
Description: PGP signature


Bug#1064293: less: CVE-2022-48624

2024-04-12 Thread Christoph Anton Mitterer
Hey.

There seems to be a somewhat similar issue reported by Jakub Wilk on
oss-security:
https://www.openwall.com/lists/oss-security/2024/04/12/5

where quoting causes troubles (though I couldn't replay the demo).

Any chance to get both fixed in Debian unstable?


Cheers,
Chris.



Bug#1068207: Problem appeared in other architecture

2024-04-12 Thread Ervin Hegedüs
The mentioned problem has appeared in other architecture too:

https://buildd.debian.org/status/fetch.php?pkg=libnginx-mod-http-modsecurity=riscv64=1.0.3-1%2Bb1=1712870226=log


a.


Bug#1017361: ITA: postsrsd -- Sender Rewriting Scheme (SRS) lookup table for Postfix

2024-04-12 Thread Abhijith PA
Hello Andreas,

On 12/04/24 03:34 PM, Andreas Metzler wrote:
> On 2023-07-17 Oxan van Leeuwen  wrote:
> > On 16-07-2023 22:35, Timo Röhling wrote:
> > > I think this was not forwarded to Oxan, so I'm resending it to
> 
> > You're right, thanks for the forward.
> 
> > On Sun, 11 Jun 2023 23:09:11 +0530 Abhijith PA  wrote:
> > > I would like to adopt this package. I maintain a mailing list server
> > > where I am already using postsrsd.
> 
> > That's great! The packaging is currently hosted in the Debian group on
> > Salsa, so as a DD you should already have access to it. I'm not aware of
> > anything that needs to be done for the handover, so feel free to take over
> > that repository (or move it elsewhere, if you prefer), and to upload a new
> > version with you listed as Maintainer.
> 
> > If you've any questions about the current packaging, don't hesitate to reach
> > out!
> 
> Hello Abhijith,
> 
> I guess you are not interested anymore?

I am interested. I have pushed latest upstream source to 
salsa.(https://salsa.debian.org/debian/postsrsd). Made an upload for 
Raju (Cc'ed). But I failed to package latest upstream to Debian repo. 
I tried and hit at obstacle and then left at there. 

I am happy to pass it you and Raju. Let me know.

--abhijith



Bug#1017361: ITA: postsrsd -- Sender Rewriting Scheme (SRS) lookup table for Postfix

2024-04-12 Thread Andreas Metzler
On 2023-07-17 Oxan van Leeuwen  wrote:
> On 16-07-2023 22:35, Timo Röhling wrote:
> > I think this was not forwarded to Oxan, so I'm resending it to

> You're right, thanks for the forward.

> On Sun, 11 Jun 2023 23:09:11 +0530 Abhijith PA  wrote:
> > I would like to adopt this package. I maintain a mailing list server
> > where I am already using postsrsd.

> That's great! The packaging is currently hosted in the Debian group on
> Salsa, so as a DD you should already have access to it. I'm not aware of
> anything that needs to be done for the handover, so feel free to take over
> that repository (or move it elsewhere, if you prefer), and to upload a new
> version with you listed as Maintainer.

> If you've any questions about the current packaging, don't hesitate to reach
> out!

Hello Abhijith,

I guess you are not interested anymore?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



Bug#1068868: ITP: python3-pyzmq -- Python bindings for 0MQ

2024-04-12 Thread Cody Scott
Package: wnpp
Severity: wishlist
Owner: Cody Scott 
X-Debbugs-Cc: debian-de...@lists.debian.org, cody.sc...@giatec.ca

* Package name: python3-pyzmq
  Version : 25.1.2
  Upstream Contact: ZeroMQ 
* URL : https://pyzmq.readthedocs.io/en/latest/
* License : BSD
  Programming Lang: Python
  Description : Python bindings for 0MQ


This will be used by Python applications that use ZeroMQ.

There doesn't appear to be any other Python bindings for ZeroMQ.

I plan to maintain it and I'm looking for a sponsor.



Bug#1068867: python3-reno: SyntaxWarning: invalid escape sequence

2024-04-12 Thread Julian Gilbey
Package: python3-reno
Version: 2.11.2-4
Severity: normal

On a testing system, Python 3.12 flags the following warnings when
setting up python3-reno:

Setting up python3-reno (2.11.2-4) ...
/usr/lib/python3/dist-packages/reno/config.py:68: SyntaxWarning: invalid escape 
sequence '\d'
  textwrap.dedent('''\
/usr/lib/python3/dist-packages/reno/config.py:79: SyntaxWarning: invalid escape 
sequence '\.'
  textwrap.dedent('''\
/usr/lib/python3/dist-packages/reno/tests/test_exts.py:102: SyntaxWarning: 
invalid escape sequence '\d'
  textwrap.dedent('''\
/usr/lib/python3/dist-packages/reno/tests/test_exts.py:113: SyntaxWarning: 
invalid escape sequence '\d'
  expected = textwrap.dedent("""\
/usr/lib/python3/dist-packages/reno/tests/test_scanner.py:71: SyntaxWarning: 
invalid escape sequence '\s'
  gnupg_version_re = re.compile('^gpg\s.*\s([\d+])\.([\d+])\.([\d+])')

These can presumably be fixed by making the strings raw or quoting the
backslashes (making the strings raw with the """\ wouldn't work,
though).

Best wishes,

   Julian



Bug#1068866: chordii successor chordpro is now available

2024-04-12 Thread Roland Rosenfeld
Package: chordii
Version: 4.5.3+repack-0.2
Severity: normal

Dear maintainer,

I just wanted to inform you, that I packaged ChordPro for Debian now
(see https://tracker.debian.org/pkg/chordpro).

According to https://johan.vromans.org/projects/Chordii/ Chordii is
discontinued and ChrodPro is its successor, also written by Johan
Vromans, but in Perl instead of C.

The last non-NMU upload of chordii was version 4.3 in 2016, with an
NMU of 4.5.3 in 2017 and an ftbfs fix NMU in 2020, this package seems
to be not being actively maintained.  Also the last upstream update
4.5.3b (released 2020) wasn't imported to Debian.

I'd suggest to remove chordii from Debian in favor of chordpro, which
is actively maintained upstream and in Debian.

Greetings
Roland



Bug#1068865: gosa: Setup failure: "PHP Fatal error: Uncaught TypeError: ldap_get_entries()"

2024-04-12 Thread Lars Kruse
Package: gosa
Version: 2.8~git20230203.10abe45+dfsg-1+deb12u2
Severity: normal

Dear Maintainer,

thank you for maintaining gosa!

I just run the web-based setup procedure of gosa in Debian Bookworm.
Quite early I received the following error:

PHP Fatal error:  Uncaught TypeError: ldap_get_entries(): Argument #2 ($result) 
must be of type LDAP\\Result, bool given in 
/usr/share/gosa/include/class_ldap.inc:1525\nStack trace:\n#0 
/usr/share/gosa/include/class_ldap.inc(1525): ldap_get_entries()\n#1 
/usr/share/gosa/setup/class_setupStep_Ldap.inc(73): 
LDAP::get_naming_contexts()\n#2 /usr/share/gosa/setup/class_setup.inc(79): 
Step_Ldap->execute()\n#3 /usr/share/gosa/setup/main.inc(29): 
setup->execute()\n#4 /usr/share/gosa/html/setup.php(123): 
require_once('...')\n#5 {main}\n  thrown in 
/usr/share/gosa/include/class_ldap.inc on line 1525, referer: 
https://accounts.silicann.systems/setup.php

According to the environment settings visible in the apache2 log, the
culprit seems to be the assumption, that a local LDAP server is
available:

  ldap_connect_to_host: TCP localhost:389

Maybe the setup procedure does not deal with a remote LDAP server gracefully?

My workaround was a temporary `ssh -R ...` port forwarding between the
remote LDAP server and the local host running gosa.
The following setup screen allowed me to configure the real LDAP URI.

Thanks for your time,
Lars



Bug#1068864: coreutils: join -a3 errors "invalid field number" even when no field number given

2024-04-12 Thread наб
Package: coreutils
Version: 9.1-1
Version: 9.4-3
Severity: normal

Dear Maintainer,

$ join -a3 /dev/null /dev/null
join: invalid field number: ‘3’

Not sure where field 3 came from here.

Best,
наб

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

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

Versions of packages coreutils depends on:
ii  libacl1  2.3.1-3
ii  libattr1 1:2.5.1-4
ii  libc62.36-9+deb12u4
ii  libgmp10 2:6.2.1+dfsg1-1.1
ii  libselinux1  3.4-1+b6

coreutils recommends no packages.

coreutils suggests no packages.

-- no debconf information


signature.asc
Description: PGP signature


Bug#1068425: pflogsumm: Postfix logs days in month < 10 with leading zeroes, pflogsumm expects space padding

2024-04-12 Thread Sven Hoexter
On Fri, Apr 05, 2024 at 01:01:52AM +0200, Magnus Stenman wrote:

Hi,
sorry for the delay, I just started to briefly look into the issue.

> Pflogsumm reports zero mails on day 1-9 of every month
> 
> Stock debian postfix version
> 
> Patch:
> --- /usr/sbin/pflogsumm.orig2024-04-05 00:45:38.214914066 +0200
> +++ /usr/sbin/pflogsumm 2024-04-05 00:45:44.710952673 +0200
> @@ -1518,7 +1518,7 @@
>  }
>  my ($t_mday, $t_mon, $t_year) = (localtime($time))[3,4,5];
> 
> -return sprintf("%s %2d", $monthNames[$t_mon], $t_mday), 
> sprintf("%04d-%02d-%02d", $t_year+1900, $t_mon+1, $t_mday);
> +return sprintf("%s %02d", $monthNames[$t_mon], $t_mday), 
> sprintf("%04d-%02d-%02d", $t_year+1900, $t_mon+1, $t_mday);
>  }

It's been a while I looked into pflogsumm and for me it still works,
but I do not rely for a long time on the traditional BSD syslog format.
Also Debian doesn't do that by default for some time, so I'm wondering
what exactly your logs look like. If possible please provide a sample.
Also how did you invoke pflogsumm, any flags in use?

According to RFC3164 section 4.1.2 there isn't zero padding but space
padding in the traditional timestamp. Likely there is a bug
somewhere, maybe even in one of the other patches I carry in the
package, but I believe the format returned here, without zero
padding on the day of the month is correct.

Sven



Bug#1067234: symfit: autopkgtest regression with NumPy 1.26

2024-04-12 Thread Michael R. Crusoe

On Mon, 8 Apr 2024 17:09:33 + Graham Inggs  wrote:
> Control: tags -1 + patch
>
> Hi Maintainer
>
> While asserting that no warnings are raised is a useful test for the
> upstream developers, I don't think it makes sense for downstreams.
>
> I propose to disable the assertion as follows:
>
> --- a/tests/test_minimizers.py
> +++ b/tests/test_minimizers.py
> @@ -117,7 +117,7 @@
> # Should no longer raise warnings, because internally we practice
> # what we preach.
> fit_custom = BFGS(chi_squared, [a, b])
> - assert len(recwarn) == 0
> +# assert len(recwarn) == 0
>
> fit_custom_result = fit_custom.execute()
>
> Please let me know if you are happy with a team upload and I will proceed.
> As a bonus, I attach a patch that fixes several SyntaxWarnings that
> occur with Python 3.12.


Hey Graham,

A team upload is fine, thanks for the fixes; please go ahead and upload them.



OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1068863: ITP: python3-atcom -- A tool which makes AT communication easier.

2024-04-12 Thread Cody Scott
Package: wnpp
Severity: wishlist
Owner: Cody Scott 
X-Debbugs-Cc: debian-de...@lists.debian.org, cody.sc...@giatec.ca

* Package name: python3-atcom
  Version : 0.4.3
  Upstream Contact: Sixfab 
* URL : https://pypi.org/project/atcom/
* License : Apache Version 2.0
  Programming Lang: Python
  Description : A tool which makes AT communication easier.


This is a Python package that provides utilities to use cellular modems.
I am using it in a travelling device.

There appears to be an alternative that I haven't used.
https://pypi.org/project/atcom/

I plan to maintain it.



Bug#1068859: [INTL:sv] Swedish strings for put-dns debconf

2024-04-12 Thread Anders Jonsson

Hi Martin,
this fixes a typo (uppdareras -> uppdateras) and an unmatched "<" in the 
Language-team header.



Regards,
Anders# Translation of put-dns debconf template to Swedish
# Copyright (C) 2024 Martin Bagge 
# This file is distributed under the same license as the put-dns package.
#
# Martin Bagge , 2024
msgid ""
msgstr ""
"Project-Id-Version: put-dns\n"
"Report-Msgid-Bugs-To: put-...@packages.debian.org\n"
"POT-Creation-Date: 2021-02-22 08:32+\n"
"PO-Revision-Date: 2024-04-12 13:20+0200\n"
"Last-Translator: Martin Bagge , 2024\n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Automatically update domain in put-dns.conf?"
msgstr "Uppdatera domän i put-dns.conf automatiskt?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"If enabled put-dns will, on configuration, try to detect a valid external "
"domain name on the current system and update the put-dns.conf configuration "
"file to use it. If disabled then the configuration will not be automatically "
"updated."
msgstr "Aktiveras detta alternativ kommer put-dns försöka hitta en giltig extern domän för systemet vid omkonfiguration och uppdaterar put-dns.conf så att den används. Om det inte aktiveras kommer inställningarna inte att uppdateras automatiskt."


Bug#1068851: Acknowledgement (bash calls sudo when sartting ?)

2024-04-12 Thread Eric Valette
Closing. It is a resolver problem. For some reason, Network-anager does 
not read /etc/hosts and my fiber box, does not honor the host-name send 
in dhcp request. Grrr


-- eric



Bug#1068857: [INTL:sv] Swedish strings for unl0kr debconf

2024-04-12 Thread Anders Jonsson

Hi Martin,
this fixes a typo in the file. (instancer->instanser)

Regards,
Anders# Translation of unl0kr debconf template to Swedish
# Copyright (C) 2024 Martin Bagge 
# This file is distributed under the same license as the unl0kr package.
#
# Martin Bagge , 2024
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: unl...@packages.debian.org\n"
"POT-Creation-Date: 2024-04-01 23:38+\n"
"PO-Revision-Date: 2024-04-12 13:26+0200\n"
"Last-Translator: Martin Bagge \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: boolean
#. Description
#: ../templates:1001
msgid "Automatically clean crypttab?"
msgstr "Ska crypttab städas upp automatiskt?"

#. Type: boolean
#. Description
#: ../templates:1001
msgid ""
"Selecting this will result in instances of 'unl0kr-keyscript'  being removed "
"from /etc/crypttab on package removal."
msgstr "Aktiveras detta alternativ så kommer instanser av unl0kr-keyscript tas bort från /etc/crypttab när paketet tas bort."


Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Guilhem Moulin
Control: tag -1 + unreproducible moreinfo

On Fri, 12 Apr 2024 at 12:45:09 +0200, Milan Broz wrote:
> Just FYI (for upstream code): if cryptsetup/libcryptsetup is linked with 
> OpenSSL >= 3.2,
> it does not need libphtread (as threads are implemented in OpenSSL for Argon2 
> internally).

Thanks for confirming!  We're now linking with OpenSSL 3.2 indeed, and
our CI confirms that unlocking works in that environment.

2:2.7.2-1 builds with OpenSSL 3.2 *and* removes the libgcc_s/libargon2
workaround from the initramfs hook:
https://tracker.debian.org/news/1517996/accepted-cryptsetup-2272-1-source-into-unstable/

>> It would also be nice if the "gui" view could show the error or at
>> least tell the user to pres ctrl-alt-del to get to a more informative
>> view, took me ages to figure out that one :-(

What is that “GUI” view?  src:cryptsetup doesn't provide that, I wonder
if it might be what needs libphtread.

Otherwise, my guess is a race where the the initramfs image was somehow
rebuilt before libcryptsetup12 was upgraded, but AFAICT the dependencies
are properly set to avoid that.  Does the broken initramfs image contain
libargon2.so, if so does its libcryptsetup12 use it?

If you still have the broken initramfs image, please extract it with
`unmkinitramfs /path/to/broken.initrd.img /path/to/destdir` and try to
find which executable / shared library needs libphtread, for instance
with

cd /path/to/destdir
for p in $(find -P {usr/,}lib/x86_64-linux-gnu  {usr/,}{,s}bin/ -type f); 
do objdump -p "$p" 2>/dev/null | grep -q pthread && echo "$p"; done

This will hopefully shed some light on this.

-- 
Guilhem.


signature.asc
Description: PGP signature


Bug#1068862: ITP: node-microsoft-fast -- FAST monorepo, containing web component packages, tools, examples, and documentation

2024-04-12 Thread Yadd
Package: wnpp
Severity: wishlist
Owner: Yadd 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: node-microsoft-fast
  Version : 0~20240320-1
  Upstream Contact: https://github.com/Microsoft/fast/issues
* URL : https://github.com/Microsoft/fast
* License : Expat
  Programming Lang: JavaScript
  Description : FAST monorepo, containing web component packages, tools, 
examples, and documentation

FAST is a collection of technologies built on Web Components and modern Web
Standards, designed to help you efficiently tackle some of the most common
challenges in website and application design and development.

* Create reusable UI components with `@microsoft/fast-element`, all based on
  W3C Web Component standards.
* Use `@microsoft/fast-foundation` library to rapidly build W3C OpenUI-based
  (https://open-ui.org/) design systems without re-implementing component
  logic.
* Leverage modern, W3C standards-based SSR for Web Components by plugging in
  `@microsoft/fast-ssr`.
* Bring all the pieces together to build SPAs and rich experiences with our
  Web Components router by installing `@microsoft/fast-router`.
* React users can drop in `@microsoft/fast-react-wrapper` to turn any Web
  Component into a native React component.
* Integrate FAST Web Components with any library, framework, or build system.

This monorepositopry will provide the following packages:
* node-microsoft-fast-colors
* node-microsoft-fast-element
* node-microsoft-fast-foundation
* node-microsoft-fast-react-wrapper
* node-microsoft-fast-router
* node-microsoft-fast-ssr
* node-microsoft-fast-web-utilities

This is required to update node-jupyterlab.



Bug#1068849: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1

2024-04-12 Thread Jan Katins
On Fri, 12 Apr 2024 at 14:00, Chris Hofstaedtler  wrote:
> Can you tell us which part was wanting libgcc_s.so.1?
> cryptsetup in the initramfs doesn't seem to be the (original)
> problem of that.

How would I find out? (I've never debugged such a problem, and have
basically no clue what is happening behind the scenes during encrypted
hd unlock and how to figure out "what wants it" :-( )

I basically inputted a password (both on the "UI" and the console
after ctrl-alt-del) and on the console it showed me that error after
pressing enter. It then showed the passwort entry box/line again.
Given that it was the password validation, I figured I should file a
bug here.

Jan



Bug#1068564: RFS: emacs-buttercup/1.35-1 -- behaviour-driven testing for Emacs Lisp packages

2024-04-12 Thread Jeremy Sowden
On 2024-04-12, at 19:50:58 +0800, Sean Whitton wrote:
> On Fri 12 Apr 2024 at 12:44pm +01, Jeremy Sowden wrote:
> > On 2024-04-12, at 17:53:15 +0800, Sean Whitton wrote:
> > > Do you have your 1.34 upload of buttercup in git, please?
> >
> > Yup, it's all on Salsa.
> 
> Er.  I got confused, then, didn't I?  Should this RFS be closed?

I uploaded 1.34, and that is what is currently in the emacsen-team repo.
This bug is for 1.35, which is currently sitting in Xiyue's fork, by the
looks of it.  I haven't looked at this yet.  I can pick it up over the
week-end.

J.


signature.asc
Description: PGP signature


  1   2   >