Bug#1023640: screen dark, BUG: kernel NULL pointer dereference, address: 0000000000000010, when use radeon.cik_support=0 amdgpu.cik_support=1

[xiao sheng wen]

Package: src:linux
Version: 5.10.149-2
Severity: normal
Tags: upstream
X-Debbugs-Cc: atzli...@sina.com

Hi,

  My PC has [AMD/ATI] Kaveri [Radeon R7 Graphics]  card.

When I add radeon.cik_support=0 amdgpu.cik_support=1 in grub.cfg boot line, 
the PC can't boot, it's screen will dark, the keyboard also can't use.

I find the kernel NULL pointer infos in the kern.log after I power restart
the PC which not use amdgpu.cik_support=1:

The following infos copy from /var/log/kern.log:

Nov  8 15:02:33 atzlinux kernel: [6.776155] Console: switching to colour 
frame buffer device 240x67
Nov  8 15:02:33 atzlinux kernel: [6.776686] BUG: kernel NULL pointer 
dereference, address: 0010
Nov  8 15:02:33 atzlinux kernel: [6.776692] #PF: supervisor read access in 
kernel mode
Nov  8 15:02:33 atzlinux kernel: [6.776694] #PF: error_code(0x) - 
not-present page
Nov  8 15:02:33 atzlinux kernel: [6.776696] PGD 0 P4D 0 
Nov  8 15:02:33 atzlinux kernel: [6.776701] Oops:  [#1] PREEMPT_RT SMP 
NOPTI
Nov  8 15:02:33 atzlinux kernel: [6.776705] CPU: 3 PID: 78 Comm: 
kworker/3:1 Not tainted 5.10.0-19-rt-amd64 #1 Debian 5.10.149-2
Nov  8 15:02:33 atzlinux kernel: [6.776709] Hardware name: Gigabyte 
Technology Co., Ltd. To be filled by O.E.M./F2A88XM-D3H, BIOS F9 12/25/2015
Nov  8 15:02:33 atzlinux kernel: [6.776712] Workqueue: events 
drm_fb_helper_dirty_work [drm_kms_helper]
Nov  8 15:02:33 atzlinux kernel: [6.776751] RIP: 
0010:drm_atomic_helper_dirtyfb+0x151/0x260 [drm_kms_helper]
Nov  8 15:02:33 atzlinux kernel: [6.776776] Code: 48 05 98 04 00 00 4c 8d 
7a f8 48 39 c2 74 4a 4d 8d 67 20 49 8b 75 48 4c 89 e7 e8 0a 82 ea ff 85 c0 75 
3e 49 8b 87 60 02 00 00 <48> 39 68 10 75 c0 4c 89 fe 4c 89 ef e8 be 8a ea ff 48 
3d 00 f0 ff
Nov  8 15:02:33 atzlinux kernel: [6.776779] RSP: 0018:b514c0a17dd0 
EFLAGS: 00010246
Nov  8 15:02:33 atzlinux kernel: [6.776783] RAX:  RBX: 
a03f48af5c80 RCX: 
Nov  8 15:02:33 atzlinux kernel: [6.776785] RDX: b514c0a17df8 RSI: 
b514c0a17df8 RDI: a03f44076c50
Nov  8 15:02:33 atzlinux kernel: [6.776787] RBP: a03f58078988 R08: 
b514c0a17df8 R09: b514c0a17df8
Nov  8 15:02:33 atzlinux kernel: [6.776789] R10: a04173dacb80 R11: 
 R12: a03f44076c20
Nov  8 15:02:33 atzlinux kernel: [6.776791] R13: a03f48af5b00 R14: 
a03f462982b0 R15: a03f44076c00
Nov  8 15:02:33 atzlinux kernel: [6.776793] FS:  () 
GS:a04173d8() knlGS:
Nov  8 15:02:33 atzlinux kernel: [6.776796] CS:  0010 DS:  ES:  
CR0: 80050033
Nov  8 15:02:33 atzlinux kernel: [6.776798] CR2: 0010 CR3: 
000107f08000 CR4: 000506e0
Nov  8 15:02:33 atzlinux kernel: [6.776801] Call Trace:
Nov  8 15:02:33 atzlinux kernel: [6.776809]  
drm_fb_helper_dirty_work+0x188/0x1c0 [drm_kms_helper]
Nov  8 15:02:33 atzlinux kernel: [6.776835]  process_one_work+0x1ad/0x3d0
Nov  8 15:02:33 atzlinux kernel: [6.776845]  ? process_one_work+0x3d0/0x3d0
Nov  8 15:02:33 atzlinux kernel: [6.776850]  worker_thread+0x50/0x3b0
Nov  8 15:02:33 atzlinux kernel: [6.776855]  ? process_one_work+0x3d0/0x3d0
Nov  8 15:02:33 atzlinux kernel: [6.776861]  kthread+0x186/0x1a0
Nov  8 15:02:33 atzlinux kernel: [6.776865]  ? __kthread_parkme+0xa0/0xa0
Nov  8 15:02:33 atzlinux kernel: [6.776869]  ret_from_fork+0x22/0x30
Nov  8 15:02:33 atzlinux kernel: [6.776876] Modules linked in: edac_mce_amd 
kvm_amd ccp rng_core ppdev kvm irqbypass ghash_clmulni_intel 
snd_hda_codec_realtek aesni_intel libaes crypto_simd snd_hda_codec_generic 
cryptd ledtrig_audio glue_helper snd_hda_codec_hdmi pcspkr sp5100_tco k10temp 
fam15h_power watchdog amdgpu(+) snd_hda_intel snd_intel_dspcfg sg 
soundwire_intel soundwire_generic_allocation snd_soc_core snd_compress 
soundwire_cadence parport_pc snd_hda_codec parport snd_hda_core snd_hwdep evdev 
soundwire_bus gpu_sched ttm snd_pcm drm_kms_helper snd_timer cec snd 
i2c_algo_bit soundcore button acpi_cpufreq drm fuse configfs ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_generic usbhid hid sd_mod 
t10_pi crc_t10dif crct10dif_generic ohci_pci r8169 ahci libahci xhci_pci 
ohci_hcd ehci_pci crct10dif_pclmul realtek crct10dif_common ehci_hcd xhci_hcd 
libata mdio_devres crc32_pclmul crc32c_intel libphy usbcore i2c_piix4 scsi_mod 
usb_common video
Nov  8 15:02:33 atzlinux kernel: [6.776966] CR2: 0010
Nov  8 15:02:33 atzlinux kernel: [6.776970] ---[ end trace 0002 
]---
Nov  8 15:02:33 atzlinux kernel: [8.761343] RIP: 
0010:drm_atomic_helper_dirtyfb+0x151/0x260 [drm_kms_helper]
Nov  8 15:02:33 atzlinux kernel: [8.761385] Code: 48 05 98 04 00 00 4c 8d 
7a f8 48 39 c2 74 4a 4d 8d 67 20 49 8b 75 48 4c 89 e7 e8 0a 82 ea ff 85 c0 75 
3e 49 8b 87 60 02 00 00 <48> 39 68 10 75 c0 4c 89 fe 4c 89 ef e8 be 8a ea ff 

Bug#1023639: RM: elpi rdeps on armhf -- RoM

[julien . puydt]

Package: ftp.debian.org
X-Debbugs-CC: Debian OCaml Maintainers



Please remove all binary packages depending on the already-removed
src:elpi package on the armhf architecture:


libcoq-elpi
libcoq-hierarchy-builder
coq-hierarchy-builder
libcoq-mathcomp-algebra-tactics
libcoq-mathcomp-analysis


Sorry for not getting things right directly,

J.Puydt

Bug#494768: ///////'//////////Ugrent

[Vanessa Gomes]

Can i trust you on this transaction?
I have important business to discuss with you as soon as possible.
This proposition will be in the best interest of you and me both.

Bug#1021021: wolfssl: CVE-2022-38152 CVE-2022-38153 CVE-2022-39173

[gs-bugs . debian . org]

> I plan to upload version 5.5.1 in the near future.

Felix, a month has passed and we are still waiting for an upload.

Failure to upload a version with security fixes within the next few days
will result in wolfssl and packages which depend on wolfssl to be
removed from Debian Testing.

Please act accordingly and please look to engage others to help you to
maintain wolfssl in Debian.

Security fixes should not be unduly delayed.

Thank you.  Glenn

Bug#985047: ipxe: New upstream release v1.21.1 available

[Michael Prokop]

* Michael Prokop [Fri Mar 12, 2021 at 09:55:40AM +0100]:
> Package: ipxe
> Version: 1.0.0+git-20190125.36a4c85-5.1
> Severity: wishlist

> according to https://github.com/ipxe/ipxe/releases there's
> v1.21.1 available since 2020-12-31.
> Would be nice to see a new version in Debian as well. :)

Gentle ping, would be nice to have a more recent version in
bookworm.

regards
-mika-


signature.asc
Description: PGP signature

Bug#1023638: memtest86+: README.Debian: wrong file names for EFI images

[Michael Prokop]

Package: memtest86+
Version: 6.00-1
Severity: minor

Quoting from /usr/share/doc/memtest86+/README.Debian:

| Multiple binary images are provided:
| 
|   - A legacy bios 32bit /boot/memtest86+x32.bin that uses Linux zImage
| boot protocol.
| 
|   - A legacy bios 64bit /boot/memtest86+x64.bin that uses Linux zImage
| boot protocol.
| 
|   - A 32bit EFI Image /boot/memtest86+x32.bin
| 
|   - A 64bit EFI Image /boot/memtest86+x64.bin

Those are twice the same file names (e.g. /boot/memtest86+x64.bin),
I suppose the later ones are meant to refer to
/boot/memtest86+x32.efi + /boot/memtest86+x64.efi?

regards
-mika-

Bug#996637: ITP: 86box -- An emulator for classic IBM PC clones

[sun min]

Package: wnpp
Severity: wishlist
Owner: sunmin 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: 86Box
  Version : 3.7.1
  Upstream Author :
* URL : https://86box.net/
* License : GPL-2.0+
  Programming Lang: C/C++
  Description : An emulator for classic IBM PC clones

  86Box is a low level x86 emulator that runs older operating systems and 
software designed for IBM PC systems and compatibles from 1981 through fairly 
recent system designs based on the PCI bus.





Live for truth,goodness and beauty

Bug#1023637: jinja2: new version 3.1.2 is available upstream

[Daniel Kahn Gillmor]

Package: jinja2
Version: 3.0.3-2
Severity: wishlist
Control: affects -1 src:xml2rfc

it looks like jinja2 3.1.2 is available upstream.  it'd be nice to have
that in debian, as it appears that the version of jinja2 might be
related to test failures in xml2rfc:

https://salsa.debian.org/debian/pkg-xml2rfc/-/commit/6ebc826ed2a3e75dd153c78f3907120726b9ed90#note_350498

Thanks for maintaining jinja2 in debian!

   --dkg


signature.asc
Description: PGP signature

Bug#1023279: Segfault on startup; stack overflow involving libwx

[Michael reports bugs]

On Sun, Nov 06, 2022 at 02:25:56PM +0800, Michael's bug reports 
 wrote:
> On Sat, Nov 05, 2022 at 01:47:25PM +0100, Andreas Metzler  
> wrote:
> > It is WX related, problably missing EGL support in glew. 
> > 
> > It worked my in own tests. I realize now that was because I have this
> > setting in ~/.config/hugin.conf:
> > [GLPreviewFrame]
> > [...]
> > isShown=0
> > 
> > (i.e. The OpenGL Preview window does not autoopen). I then need two
> > klicks to actually open it (the first try fails) but apart from that
> > hugin works.
> > 
> > Does this workaround also work at your system?
> 
> Afraid not! It was already set to zero in my ~/.hugin, and changing it to zero
> in ~/.config/hugin.conf had no effect, other than it getting changed back to
> 1 again... o_O

Correction, the workaround worked as described, once I renamed 
~/.config/hugin.conf
out of the way (which seems to have also allowed it to migrate my ~/.hugin to
.config/hugin.conf).

-MD

-- 
-
Michael Deegan   Hugaholic  https://www.deegan.id.au/
  Jung, zr jbeel?  --

Bug#1023636: ITP: ruby-blurhash -- Encode an image as a small string that can saved in the database

[Juri Grabowski]

Package: wnpp
Severity: wishlist
Owner: deb...@jugra.de
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: ruby-blurhash
  Version : 0.1.6
  Upstream Author : Eugen Rochko 
* URL : https://github.com/Gargron/blurhash
* License : Expat
  Programming Lang: Ruby
  Description : Encode an image as a small string that can saved in the 
database
  and used to show a blurred preview before the real image loads

I am packaging blurhash as it is a dependency of mastodon. (#859741)

Bug#996637: 86box ready to be packaged

[sun min]

Dear maintainers:

I prepared the latested release of 86Box v3.7.1

https://salsa.debian.org/sunmin/86Box

I wish someone can review and push it to new queue.






Live for truth,goodness and beauty

Bug#1023635: reportbug: Add p11kit support for PIV LUKS encryption

[Stuart McKim]

Package: systemd
Version: 252-3
Severity: wishlist

Dear Maintainer,

I'm trying to use PIV to encrypt a partition using LUKS, which, from my
understanding, depends on p11kit being enabled for systemd. According to
the most recent build logs for sid, p11kit is disabled.

This was previously requested in #1007268, but it appears that only
fido2 and tpm support were added.

Stuart

Bug#1022114: RFH: highlight -- Universal source code to formatted text converter

[Daniel Echeverri]

Hello Again!

El lun, 7 nov 2022 a la(s) 13:57, Daniel Echeverri (epsi...@debian.org)
escribió:

> Hello!
>
> El jue, 20 oct 2022 a la(s) 05:33, David Bremner (brem...@debian.org)
> escribió:
>
>> Package: wnpp
>> Severity: normal
>> X-Debbugs-Cc: debian-de...@lists.debian.org
>> Control: affects -1 src:highlight
>>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> I request assistance with maintaining the highlight package.
>>
>> I have not really been keeping up with new upstream releases and could
>> use a co-maintainer.
>>
>> The package description is:
>>  A utility that converts sourcecode to HTML, XHTML, RTF, LaTeX, TeX,
>>  SVG, XML or terminal escape sequences with syntax highlighting.  It
>>  supports several programming and markup languages.  Language
>>  descriptions are configurable and support regular expressions.  The
>>  utility offers indentation and reformatting capabilities.  It is
>>  easily possible to create new language definitions and colour themes.
>>
>>
>> -BEGIN PGP SIGNATURE-
>>
>> iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmNRIyoACgkQA0U5G1Wq
>> FSGyjQ/8CbUEHtTj0Rad0xZAdVULj9B3EqJN9H35YyUatq85rbdJ69p1cMLgWiu0
>> hQbypoCRyn+swf30+Slc7X8tIlmKoqxkDJOiqGl5uLdgEUmMB5Ael89ZUCQU+yh5
>> m2BPAYWb6AuU0uJPPXBGIfIcw54ZtzzGMarvgd7PTlxEOYBaSZo+mkzO4YB/AoXc
>> xLSSXUp8mW3kqQoQEtyJ5NlwfFVoaERUIJcJXHurtd3wWk8NCbqau+10/m/oyem8
>> AzRHzEzu8FsIadYlK6jyvCtcuHY6WwEVnA++qsWd92CjBza2nmb2bjS8bgRRC/JS
>> K/gcK2bf2zA2J4o6BKJgfSmTO9rzp0hb4CwYv/91ecM/rNB8mBvUIYzZn1caKbGZ
>> N758k9HcyMDywEdZ8Ue2fl0hmYg0/skO7FJEB2TIfnAhqJlQ6n+MexRLIVTAJ8zW
>> 1omcULUhnW3c6IdK8WmM6DuX76iO1QGkrslMU3opsKvy8G4jOyp8l3qh3oqd6uWj
>> hXknT5lPaE936qd6xDn2dy4niB07W0FhSWBpb9jb3nb5G1pkoWbx/iRjmRT+v0KU
>> QB50EoNYZDVWw9AyI0wTkU3NwanWWIggG6lpripCoirxaqlDkkJxe5VH0N9fZncZ
>> irLYONNifkBHonshPaDgIYGTN5U55NlaVPs58p95GGvNw+61dmg=
>> =GkDM
>> -END PGP SIGNATURE-
>>
>>
> My perl skills maybe aren't the highest but my desire to help is yes :) so
>  if you agree I could co-maintain highlight with you,
>
> I am working in a new revision, I will push the changes to Salsa soon.
>
> Regards.
>
>

 Could you give me access to salsa repo? or Do you agree if we move this
repo to Debian Group?

Regards.

-- 
Daniel Echeverri
Debian Developer
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB

Bug#1022248: transition: icu

[Sebastian Ramacher]

Control: tags -1 = confirmed

On 2022-10-30 14:08:55 +0100, László Böszörményi wrote:
> Control: tags -1 -moreinfo
> 
> On Thu, Oct 27, 2022 at 11:39 PM Sebastian Ramacher
>  wrote:
> > On 2022-10-22 19:17:58 +0200, László Böszörményi wrote:
> > > Transition is similar to the previous ones, this time boost1.74 needs
> > > to be binNMUed after level1 before other level2 packages and pyicu
> > > will need a sourceful upload (its Git version seems to be ready, but I
> > > wait for its release).
> >
> > I've set up the tracker. Please remove the moreinfo tag once the test
> > builds are done.
>  I can report the following. Rebuilds are done and pyicu (Python
> wrapper for ICU) supporting 72.1 is released and packaged. Two
> immediate problems were found and fixed by its upstream. It can be
> binNMUed for ICU 72.1 version.
> Package nodejs further updated for Sid, flaky test remained. Wile it
> builds on buildd machines, locally I get:
> not ok 3161 sequential/test-debugger-preserve-breaks # TODO : Fix flaky test
>   duration_ms: 31.372
>   severity: flaky
>   exitcode: 1
> 
> Package 0ad and gnucash fail to build [1][2] with ICU 72.1 and bugs are filed.
> Package supercollider failed to build due to another issue [3]. Its
> packaging Git has a working fix and after applying that it was built
> with ICU 72.1 as well.

Alright, please go ahead.

Cheers

> 
> Cheers,
> Laszlo/GCS
> [1] https://bugs.debian.org/1023121
> [2] https://bugs.debian.org/1023122
> [3] https://bugs.debian.org/1019995
> 

-- 
Sebastian Ramacher

Bug#1023634: RM: objcryst-fox [mips64el] -- ROM; cctbx unavailable on mips64el

[Scott Talbert]

Package: ftp.debian.org
Severity: normal

Bug#1023633: python3-scalene: can't import (or execute) scalene

[David M. Cooke]

Package: python3-scalene
Version: 1.4.1-1
Severity: important
X-Debbugs-Cc: david.m.co...@gmail.com

Dear Maintainer,

Running scalene, either with the CLI command `scalene`, or `python3.10 -m
scalene`, or `python3.9 -m scalene`, causes this (or similiar) import error:

Traceback (most recent call last):
  File "/usr/bin/scalene", line 33, in 
sys.exit(load_entry_point('scalene==1.4.1', 'console_scripts',
'scalene')())
  File "/usr/bin/scalene", line 25, in importlib_load_entry_point
return next(matches).load()
  File "/usr/lib/python3.10/importlib/metadata/__init__.py", line 171, in load
module = import_module(match.group('module'))
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1050, in _gcd_import
  File "", line 1027, in _find_and_load
  File "", line 1006, in _find_and_load_unlocked
  File "", line 688, in _load_unlocked
  File "", line 883, in exec_module
  File "", line 241, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/scalene/__main__.py", line 4, in

from scalene import scalene_profiler
  File "/usr/lib/python3/dist-packages/scalene/scalene_profiler.py", line 46,
in 
from scalene.scalene_mapfile import ScaleneMapFile
  File "/usr/lib/python3/dist-packages/scalene/scalene_mapfile.py", line 6, in

from scalene import get_line_atomic  # type: ignore
ImportError: cannot import name 'get_line_atomic' from 'scalene'
(/usr/lib/python3/dist-packages/scalene/__init__.py)

The problem is easily traced to the included get_line_atomic C extension
being installed to /usr/lib/scalene/lib, which is not on Python's search
path for modules.  Extension modules should be installed alongside their
pure-Python companions, in /usr/lib/python3/dist-packages (see: every other
Python package with a C extension.)

This also explains why the generated manpage is a duplicate of `python3 -h`.


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

Kernel: Linux 6.1.0-0-amd64 (SMP w/8 CPU threads; PREEMPT)
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

Versions of packages python3-scalene depends on:
ii  libc62.36-4
ii  libgcc-s112.2.0-9
ii  libstdc++6   12.2.0-9
ii  python3  3.10.6-1
ii  python3-cloudpickle  2.0.0-1
ii  python3-numpy1:1.21.5-1+b1
ii  python3-rich 12.4.4-1

Versions of packages python3-scalene recommends:
ii  python3-ipython  8.5.0-1
ii  python3-pynvml   11.515.75-1

python3-scalene suggests no packages.

-- no debconf information

Bug#1023619: libx86emu: Add riscv64 support

[Paul Wise]

On Tue, 2022-11-08 at 01:58 +0800, Yifan Xu wrote:

> I tried to build on Hifive Unmatched and qemu, build succeed with only 
> enabling
> the architecture in debian/control, no other changes needed.

I note that the current debian/rules disables running the tests, so
libx86emu may not work on riscv64 even if it builds, so please try to
re-enable the tests in debian/rules by dropping override_dh_auto_test
and then building again so that the tests are run.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#1023469: An update from the upstream - eduActiv8

[Ireneusz Imiolek]

Dear Gerard and Maintainers,

Thank you for reporting the issue and sorry for the late reply, I only just
realized a new bug was reported.

If I am not mistaken I have encountered this issue previously. The problem
is that the latest distros started using Python 3, Pygame 2+ and the latest
SDL 2+ which seems to draw windows differently. I ended up changing the way
the program's window gets resized at startup which I believe solved the
reported problem.

The latest source release (just published with the fix) is available on
GitHub at: https://github.com/imiolek-ireneusz/eduActiv8/releases

The upstream version also solves issues: #721829, #721830, #721899 and
#721852.

A hopefully working, but not the most up-to-date (yet) version is available
at:
https://software.opensuse.org/download.html?project=home%3Aimiolek-i=eduactiv8

FAO: Maintainers - just in case any of the configuration files here are of
any use:
https://build.opensuse.org/package/show/home:imiolek-i/eduActiv8

I would really appreciate if you could confirm the latest source code works
as expected, please.

Thanks,
Ireneusz Imiolek
(eduActiv8 Dev)

Bug#1023596: bookworm: document changes in default rsyslog configuration

[Michael Biebl]

Am 07.11.22 um 23:15 schrieb RL:

Are both rsyslog and systemd's journal still both the default in bookworm?

I see rsyslog is still priority: important - any plans to reduce that in
future releases?


That's actually good point: rsyslog in bookworm has been demoted to prio 
optional [1], so is no longer installed by default.


Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018788







OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023596: bookworm: document changes in default rsyslog configuration

[RL]

The following message is a courtesy copy of an article
that has been posted to gmane.linux.debian.devel.documentation as well.

Michael Biebl  writes:

> The rsyslog configuration changed significantly in bookworm.

Hi, I'd potentially be happy to contribute some text for release-notes
on rsyslog. Some questions based on what i'd want to know as an
interested user:

Are both rsyslog and systemd's journal still both the default in bookworm?

I see rsyslog is still priority: important - any plans to reduce that in
future releases?

(Have reordered the below based on what seems most important to me):

>   * Enable high precision timestamps with timezone information.
> Use the default rsyslog file format, which provides several benefits
> like:
> - sortable
> - time zone information
> - sub-second time resolution
> (Closes: #475303)

(this would seem to break every single logcheck rule too)

>   * Stop splitting up mail.*
> This avoids having mail related messages duplicated in mail.log and
> mail.{info,warn,err}. (Closes: #508376)

I think the impact here depends on the mta:
- debian's default mta is exim4
- postfix is a popular alternative
- /var/log/mail.{info,warn,err}* can be deleted after the upgrade (or is this 
done by the upgade?)

Details:
 For exim4, logging was in /var/log/exim4 (and mail.err was duplicating 
paniclog,
 others not used but are created as empty files)

 For postfix, logging was in /var/log/mail.log and duplicated in all/some
 of /var/log/syslog and mail.{info,warn,err}* (unchecked - based on the
 bug report)

Other mtas are likely to be similar to either exim or postfix - but is
there any mta that only uses mail.*?

(For all these we should be clear that the user dosnt need to delete
anything and should check what is being used)

>   * Stop splitting lpr facility into its own log file.
> The default printing system CUPS is not using this facility so its
> basically unused nowadays.

Am i right that
- cups is installed by the default gnome desktop task: anyone using that is
not affected as the /var/log/lpr.log is not created
- systems without any printing systems are likely not affected
   (lpr.log will not exist)
- people who have installed some alternative printing system (is there any?)
   can now delete /var/log/lpr.log* and find log messages about printing
   in syslog (or do other systems expect lpr.log to exist?)


>   * Drop catch-all log files /var/log/{messages,debug}
>   * Stop splitting daemon facility into its own log file.

Similarly (but nothing to do with mtas) users can delete these logs -
the second being /var/log/daemon.log

>   * Split cron facility into its own log file /var/log/cron.log.
> The cron facility is widely used and limited enough in scope to have it
> split out separately. (Closes: #625483)

This one affects everyone using cron (including anacron).  but isnt
there some lintian warning that anaccron is no longer installed for
desktop users? (which should be in release-notes i assume)

I assume that for bookwork, systemd timers are not yet ready to replace
cron jobs by default

Regards

Bug#1023599: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2

[Kevin J. McCarthy]

On Mon, 7 Nov 2022 13:04:04 +0100 Vincent Lefevre  wrote:

The gpgme-config utility was removed in gpgme1.0 1.18.0-2
(because it needs gpg-error-config, which has been removed).

As a consequence the use of --enable-gpgme to build Mutt yields
an error:


Just as a note, with Vincent's help, I've commited two patches to the 
stable branch, updating to the most recent GPGME autoconf files and 
adjusting AM_PATH_GPG_ERROR before AM_PATH_GPGME:


https://gitlab.com/muttmua/mutt/-/commit/012981e8434903e8b5ae5f099b026b9a64426129.patch
https://gitlab.com/muttmua/mutt/-/commit/527537027b0c9134192663c9d3ec01d6cea6c5c2.patch

I will try to get a Mutt release out later this week with these two 
commits, but if you need the fix sooner, please grab the above patches.


-Kevin


signature.asc
Description: PGP signature

Bug#1023632: Please package latest upstream version 4.0.0

[Michael Biebl]

Source: gcr
Version: 3.41.1-1
Severity: wishlist

libnma-gtk4 can be built with Smart Card support (which could be
interesting for gnome-control-center).

This requires a newer gcr version though, namely gcr >= 3.92.0

The latest upstream version appears to be 4.0.0, so it would be nice to
have this version in unstable / bookworm.


Michael

Bug#1023631: firmware-misc-nonfree: Possibly missing firmware for Creative Labs Sound Blaster Z PCIe sound card

[Julian Groß]

Package: firmware-misc-nonfree
Version: 20221012-1
Severity: normal

Dear Maintainer,

I have been running into weird behaviour on my Creative Labs Sound Blaster Z 
(Serial number either SB1500 or SB1502).
Just now I noticed that a seemingly related firmware file doesn't get loaded.
Here is a section out of dmesg:

[9.591329] snd_hda_intel :02:00.0: firmware: failed to load 
ctefx-desktop.bin (-2)
[9.591355] firmware_class: See https://wiki.debian.org/Firmware for 
information about missing firmware
[9.591387] snd_hda_intel :02:00.0: firmware: failed to load 
ctefx-desktop.bin (-2)
[9.591409] snd_hda_intel :02:00.0: Direct firmware load for 
ctefx-desktop.bin failed with error -2
[9.592599] snd_hda_intel :02:00.0: firmware: direct-loading firmware 
ctefx.bin

ctefx-desktop.bin shows up in the list of firmware that is supposed to be 
included in Debian. https://wiki.debian.org/Firmware/List

While the driver seems to load a different firmware file, and the sound card 
works most of the time, the identification in lspci seems wrong, and there is 
random issues like no audio output until reboot, "electric" audio output until 
reboot, no audio input until reboot, settings needing to be applied multiple 
times, and alsactl store failing.
lspci reports a "Subsystem: Creative Labs SB1570 SB Audigy Fx", while this card 
is from a different series and looks completely different from it.
Not knowing much about this sort of thing, I am assuming the driver is falling 
back to the firmware for a different sound card, which might be causing a bunch 
of my issues.


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

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

firmware-misc-nonfree depends on no packages.

firmware-misc-nonfree recommends no packages.

Versions of packages firmware-misc-nonfree suggests:
ii  initramfs-tools  0.142

-- no debconf information

Bug#1023440: emacs: native-comp-async always runs, but no eln files are generated.

[Sean Whitton]

control: tag -1 + unreproducible

Hello,

On Mon 07 Nov 2022 at 10:35AM +09, Youhei SASAKI wrote:

> repopen 1023440
>
> Hi,
>
> On Sun, 06 Nov 2022 14:53:30 -0700 Sean Whitton  
> wrote:
>> Hello,
>>
>> > Package: emacs
>> > Version: 1:28.2+1-3
>> > Severity: important
>> > X-Debbugs-Cc: none, Youhei SASAKI 
>> >
>> > Dear Maintainer,
>> >
>> > Although native-comp-async is always running in the background and
>> > wasting computing resources every time Emacs is invoked,
>> > no eln files are generated under ~/.emacs.d/eln-cache/.
>>
>> I don't know, there isn't really enough information in this bug report
>> to do anything.  Closing for now, but if please reopen if you have a
>> recipe to reproduce.
>
> Ok.
>
>   mkdir -p /tmp/emacs-test
>   env HOME=/tmp/emacs-test emacs -nw --debug-init
>
> then, always running native-compile-async.
>
> I puts async-native-compile-log.txt.gz

Thank you for the additional information, but since the problem does not
occur here, there still isn't really anything to go on.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1023535: transition: protobuf

[Christoph Berg]

Re: László Böszörményi
> On the other hand I'm done with the rebuilds and patched all issues,
> this transition may start immediately at your decision. The only
> downside is that the Sid version of cura-engine is FTBFS and to fix
> it, the libarcus transition (only affecting this package) will need to
> be done.

I'll take care of cura and deps when the transition starts.
(Unfortunately the newest libarcus package doesn't work with the old
protobuf, so we can't upload that yet.)

Christoph

Bug#1023005: A recent Bookworm upgrade broke video playback in the VLC player

[Alexis Murzeau]

Control: found 1023580 5.15.7+dfsg-1

On 07/11/2022 22:27, local10 wrote:


Tried it again with the playlist window. This is how it works for me:

1. Open VLC > Ctrl+L > My Videos > Don't click on any of the videos > Start 
changing the size of the window > no scaling effect is observed, all border are redrawn 
properly

2. Open VLC > Ctrl+L > My Videos > Start playing one of the videos, then stop it > 
Ctrl+L > Start changing the size of the window > scaling effect is clearly observed, the 
video list right and bottom borders are NOT redrawn properly, the effect is very similar to what 
is shown in the qt_5.15.6+dfsg-2_vlc_glitches.mp4 video. See the enclosed file for details.

Regards,



Ok thanks, so you get it too, I'm not the only one to have this :)
(And if you playback the video again, it will show a black screen (if it wasn't 
the case the first time))


I guess the issue might appear a bit differently from user to user but is 
probably the same cause.
I'm trying to find a way to reproduce it easily and maybe find what goes wrong.
I've tried with the Qt version in experimental (5.15.7), but sadly the behavior 
is the same.


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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023005: A recent Bookworm upgrade broke video playback in the VLC player

[local10]

Nov 7, 2022, 20:00 by amub...@gmail.com:

> Thanks for your feedback.
>
> Did you tried with the vlc playlist open as in the video ?
> It only does that when the playlist is open.
>


Tried it again with the playlist window. This is how it works for me:

1. Open VLC > Ctrl+L > My Videos > Don't click on any of the videos > Start 
changing the size of the window > no scaling effect is observed, all border are 
redrawn properly

2. Open VLC > Ctrl+L > My Videos > Start playing one of the videos, then stop 
it > Ctrl+L > Start changing the size of the window > scaling effect is clearly 
observed, the video list right and bottom borders are NOT redrawn properly, the 
effect is very similar to what is shown in the 
qt_5.15.6+dfsg-2_vlc_glitches.mp4 video. See the enclosed file for details.

Regards,

Bug#1023630: network-manager-gnome: fails to install

[IOhannes m zmoelnig]

Package: network-manager-gnome
Version: 1.30.0-1
Severity: serious
Justification: Policy 7.4

Dear Maintainer,

'network-manager-gnome' fails to install if libnma-common_1.10.2-1 is also
installed, as both provide the same file:

```
dpkg: error processing archive 
/tmp/apt-dpkg-install-u13Ac3/157-network-manager-gnome_1.30.0-1_amd64.deb 
(--unpack):
 trying to overwrite 
'/usr/share/glib-2.0/schemas/org.gnome.nm-applet.gschema.xml', which is also in 
package libnma-common 1.10.2-1
```

'libnma-common' is a dependency on 'libnma0' which is a dependency of
'network-manager-gnome' :-/

if the conflicting file is meant to be moved from one package to the other,
please add the appropriate versioned Breaks/Replaces runes.


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

Kernel: Linux 6.0.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: 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 network-manager-gnome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.4-1
ii  dconf-gsettings-backend [gsettings-backend]   0.40.0-3
ii  libatk1.0-0   2.46.0-3
ii  libayatana-appindicator3-10.5.91-1
ii  libc6 2.36-4
ii  libcairo2 1.16.0-6
ii  libgdk-pixbuf-2.0-0   2.42.9+dfsg-1
ii  libglib2.0-0  2.74.1-1
ii  libgtk-3-03.24.34-3
ii  libjansson4   2.14-2
ii  libmm-glib0   1.20.0-1
ii  libnm01.40.2-1
ii  libnma0   1.10.2-1
ii  libpango-1.0-01.50.10+ds-1
ii  libpangocairo-1.0-0   1.50.10+ds-1
ii  libsecret-1-0 0.20.5-3
ii  libselinux1   3.4-1+b2
ii  network-manager   1.40.2-1
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-7+b1

Versions of packages network-manager-gnome recommends:
ii  gnome-icon-theme 3.12.0-5
ii  gnome-keyring42.1-1+b1
ii  iso-codes4.12.0-1
ii  mobile-broadband-provider-info   20220725-1
ii  notification-daemon  3.20.0-4+b1
ii  xfce4-notifyd [notification-daemon]  0.6.4-1

Versions of packages network-manager-gnome suggests:
pn  network-manager-openconnect-gnome  
pn  network-manager-openvpn-gnome  
pn  network-manager-pptp-gnome 
pn  network-manager-vpnc-gnome 

-- no debconf information

Bug#992582: docker.io: Little problem in the dockerd-rootless-setuptool.sh script prevents successful rootless setup

[Alexis Murzeau]

Hi,

I found that doing this as root is sufficient to make the script work:
ln -s /usr/bin/docker /usr/share/docker.io/contrib/docker


This way, the script won't stop with an error at line 336:
DOCKER_HOST="unix://$XDG_RUNTIME_DIR/docker.sock" $BIN/docker version

Here in the script, $BIN points to /usr/share/docker.io/contrib.

Maybe this symbolic link can be added ?
This should be a light enough modification for no maintenance burden.



Also, is there a specific reason to not put this script in /usr/bin ?
Upstream docker is doing that in their .deb packages, both
dockerd-rootless-setuptool.sh and dockerd-rootless.sh are in /usr/bin,
so I guess these scripts expect this to work as-is.
That's at least also a way to solve this issue too.

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


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023609: smbclient does not work with kerberos ccache of KEYRING: type

[Vincent Danjean]

Le 07/11/2022 à 18:58, Andrew Bartlett a écrit :

On Mon, 2022-11-07 at 16:45 +0100, Vincent Danjean wrote:

- smbclient does not handle ccache using the kernel keyring
   Perhaps this is due to samba using heimdal kerberos implementation?


That is all this is.  An MIT build would work, but that isn't a supported way 
to build the AD DC at this time.


As I'm only using the client part (the AD is managed by Microsoft
products in my case), do you have some advises about how to modify
debian/rules,control to (locally) build the samba package with MIT?

I suppose there will be :
- a few build dependencies to change (quickly looking, I see nothing
  about heimdal?)
- a few configure options to tweek
  I should be able to find the options to add such as
  --with-system-mitkrb5
  (and --with-experimental-mit-ad-dc just to pass the compilation?)
  but what should be disabled?
  Or which binary packages should I disable/remove ?

  I would be very pleased if you can give me a few hints.

  Regards
Vincent


Andrew Bartlett

Bug#1023629: glib2.0: flaky autopkgtest on armhf and armel (on ci.d.n infra): glib/threadtests.test times out after 300 seconds

[Paul Gevers]

Source: glib2.0
Version: 2.74.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails since around March 2022 on armel [1] and the 
first of October 2022 on armhf [2].


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

[1] https://ci.debian.net/packages/g/glib2.0/testing/armel/
[2] https://ci.debian.net/packages/g/glib2.0/testing/armhf/

https://ci.debian.net/data/autopkgtest/testing/armhf/g/glib2.0/26345811/log.gz

# Executing: glib/threadtests.test
# Executing: glib/threadtests.test
# Executing: glib/threadtests.test
not ok - Test timed out after 300 seconds
# FAIL: glib/threadtests.test (Child process killed by signal 9)
not ok - glib/threadtests.test

[...]

# SUMMARY: total=275; passed=272; skipped=2; failed=1; user=1680.6s; 
system=176.1s; maxrss=154072

# FAIL: glib/threadtests.test (Child process killed by signal 9)


https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27696626/log.gz

not ok - Test timed out after 300 seconds
# FAIL: glib/threadtests.test (Child process killed by signal 9)
not ok - glib/threadtests.test
# Running test: glib/gutils-user-database.test
# random seed: R02Sa857e7d4f9a0241ca5d1865ccc7eafc1
1..1
# Start of gutils tests
ok 1 /gutils/get_user_database_entry
# End of gutils tests
ok - glib/gutils-user-database.test
# SUMMARY: total=284; passed=281; skipped=2; failed=1; user=1566.6s; 
system=169.8s; maxrss=153428

# FAIL: glib/threadtests.test (Child process killed by signal 9)


https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27421159/log.gz

# SUMMARY: total=276; passed=273; skipped=2; failed=1; user=1555.8s; 
system=175.9s; maxrss=170864

# FAIL: glib/threadtests.test (Child process killed by signal 9)


https://ci.debian.net/data/autopkgtest/testing/armel/g/glib2.0/27116770/log.gz

# SUMMARY: total=276; passed=273; skipped=2; failed=1; user=1552.2s; 
system=274.3s; maxrss=226436

# FAIL: glib/threadtests.test (Child process killed by signal 9)



OpenPGP_signature
Description: OpenPGP digital signature

Bug#907178: gimp-plugin-registry: resynthesizer not appearing in menu Filters/Enhance

[Ralf Jung]

Hi,

the version packaged in Debian seems to be the same that is offered for download 
on the gimp website.


This seems to be an upstream problem: Gimp 3 will be required for Python 3 
support, and Gimp 3 has been delayed ~forever -- Gimp 3 is the GTK 3 port, which 
is not even done yet and meanwhile Gnome is already being ported to GTK 4!


Kind regards,
Ralf

On 07.11.22 21:27, Ying-Chun Liu (PaulLiu) wrote:

Hi,

Yes, we ported that plugin to Python3.
However, gimp in Debian is too old.
There was a package called gimp-python which is python2 and got removed.
Thus right now in Debian we have to disable all python plugins temporarily.
We will bring those plugins back when gimp-python3 is available.

This is not a bug of this package. This should be a bug of gimp.

Yours,
Paul

Bug#907178: gimp-plugin-registry: resynthesizer not appearing in menu Filters/Enhance

[Ying-Chun Liu (PaulLiu)]

Hi,

Yes, we ported that plugin to Python3.
However, gimp in Debian is too old.
There was a package called gimp-python which is python2 and got removed.
Thus right now in Debian we have to disable all python plugins temporarily.
We will bring those plugins back when gimp-python3 is available.

This is not a bug of this package. This should be a bug of gimp.

Yours,
Paul


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#992675: resynthesizer missing in bullseye

[Ying-Chun Liu (PaulLiu)]

Hi,

Yes, we ported that plugin to Python3.
However, gimp in Debian is too old.
There was a package called gimp-python which is python2 and got removed.
Thus right now in Debian we have to disable all python plugins temporarily.
We will bring those plugins back when gimp-python3 is available.

Yours,
Paul


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014595: linux-image-5.19.0-rc4-amd64: Enable CONFIG_SND_SOC_INTEL_SOF_ES8336_MACH=m

[Salvatore Bonaccorso]

Control: tags -1 + pending

Hi,

On Mon, Nov 07, 2022 at 12:53:40PM -0500, Giovanni Caligaris wrote:
> Hi, can anyone pick this up and push it to the latest kernel versions
> please.

I have created a merge request for this change:
https://salsa.debian.org/kernel-team/linux/-/merge_requests/575
and should land in the next experimental upload based on 6.1-rc4.

Regards,
Salvatore

Bug#1023628: www.debian.org: missing distribution name changes in releases/trixie/index.wml

[Rafa]

Package: www.debian.org
Severity: normal

Dear Maintainers,

It seems to me that in file releases/trixie/index.wml, as of commit
bd44c0367d403f4c6efaa83c6373a24a7991a1bb, there are some distribution
name changes missing.

As a consequence, the currently published HTML page incorrectly states
that:

  'The code name for the next major Debian release after bullseye is "trixie"'

I guess that the attached patch could fix this issue.

Regards,

Rafa.

From 0d7b92834f71838de9c116f16735d93c5ce7f663 Mon Sep 17 00:00:00 2001
From: Rafa 
Date: Mon, 7 Nov 2022 18:38:38 +
Subject: [PATCH] Fix some missing distribution name changes

---
 english/releases/trixie/index.wml | 14 +++---
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/english/releases/trixie/index.wml b/english/releases/trixie/index.wml
index f2422bb20b1..05676c19877 100644
--- a/english/releases/trixie/index.wml
+++ b/english/releases/trixie/index.wml
@@ -64,12 +64,12 @@ release, even though it is declared stable. We've made
 credit for making this release happen.
 
 
-
+
 
 The code name for the next major Debian release after bullseye is trixie.
+href="../bookworm/">bookworm is trixie.
 
-This release started as a copy of bullseye, and is currently in a state
+This release started as a copy of bookworm, and is currently in a state
 called testing.
 This means that things should not break as badly as in unstable or
 experimental distributions, because packages are allowed to enter this
@@ -83,7 +83,7 @@ don't have any release-critical bugs filed against them.
 # https://lists.debian.org/debian-testing-security-announce/2008/12/msg00019.html;>announcement
 # of the Testing Security Team.
 You are encouraged to switch your
-sources.list entries from testing to bullseye for the time being if you
+sources.list entries from testing to bookworm for the time being if you
 need security support. See also the entry in the
 Security Team's FAQ for
 the testing distribution.
@@ -115,11 +115,11 @@ debian-devel-announce mailing list.
 
 
 
-
+
 
 The code name for the next major Debian release after bullseye is trixie. Currently,
-bullseye is not released yet. So trixie is still
+href="../bookworm /">bookworm is trixie. Currently,
+bookworm is not released yet. So trixie is still
 far away.
 
 
-- 
2.30.2



signature.asc
Description: PGP signature

Bug#1023452: gimp-plugin-registry: Separate+ plugin crashes

[Ying-Chun Liu (PaulLiu)]

Hi Andreas,

Thanks for the patch. I can reproduce this bug.

I also write this test to test if separate runs ok.
Will upload it soon.

Yours,
Paul
#/bin/sh

TEMP=${AUTOPKGTEST_TMP:-${TMPDIR:-$(mktemp -d)}}
TDIR=$(mktemp -d $TEMP/test-separate-1-XX)

convert /usr/share/wallpapers/EveningGlow/contents/images/2560x1440.jpg -resize 
'640x480!' "$TDIR"/origin.jpg

sleep 1

echo "Run separate+..."
gimp-console -i -b "(let* ((i1 (car (gimp-file-load 1 \"$TDIR/origin.jpg\" 
\"$TDIR/origin.jpg\"))) (layer1 (car (gimp-image-get-active-layer i1))) 
(cmykimg (car (plug-in-separate-full 1 i1 layer1 
\"/usr/share/color/icc/colord/SMPTE-C-RGB.icc\" FALSE 
\"/usr/share/color/icc/ghostscript/gray_to_k.icc\" 1 FALSE FALSE FALSE 
FALSE (gimp-xcf-save 1 cmykimg (car (gimp-image-get-active-drawable 
cmykimg)) \"$TDIR/output.xcf\" \"$TDIR/output.xcf\") (gimp-quit 1))"

sleep 2

if [ ! -e "$TDIR"/output.xcf ]; then
   echo "No output.xcf"
   exit 404
fi


OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023627: grip: missing CSS

[Jakub Wilk]

Package: grip
Version: 4.2.0-3

After I cleared the cache, the pages grip renders appear completely 
unstyled.



-- System Information:
Architecture: i386

Versions of packages grip depends on:
ii  python3-docopt0.6.2-4
ii  python3-flask 2.0.3-1
ii  python3-markdown  3.4.1-2
ii  python3-path-and-address  2.0.1-3
ii  python3-pygments  2.12.0+dfsg-2
ii  python3-requests  2.27.1+dfsg-1
ii  python3   3.10.6-1

--
Jakub Wilk

Bug#1023005: A recent Bookworm upgrade broke video playback in the VLC player

[Alexis Murzeau]

On 07/11/2022 20:22, local10 wrote:

Tried it and I don't seem to have that scaling effect shown in the 
qt_5.15.6+dfsg-2_vlc_glitches.mp4. Am using the Breeze theme (not Breeze Dark 
or Breeze Twilight, just Breeze).

VLC still shows black screen when playing videos (MP4s) though.



Thanks for your feedback.

Did you tried with the vlc playlist open as in the video ?
It only does that when the playlist is open.

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023626: grip --clear: "No README found at"

[Jakub Wilk]

Package: grip
Version: 4.2.0-3

I wanted to clear the cache, but that failed unexpectedly:

$ grip --clear
Traceback (most recent call last):
  File "/usr/bin/grip", line 9, in 
load_entry_point('grip==4.2.0', 'console_scripts', 'grip')()
  File "/usr/share/grip/grip/command.py", line 94, in main
clear_cache()
  File "/usr/share/grip/grip/api.py", line 69, in clear_cache
grip_class().clear_cache()
  File "/usr/share/grip/grip/app.py", line 48, in __init__
source = DirectoryReader(source)
  File "/usr/share/grip/grip/readers.py", line 90, in __init__
root_filename = os.path.abspath(self._resolve_readme(path, silent))
  File "/usr/share/grip/grip/readers.py", line 132, in _resolve_readme
return self._find_file(path, silent)
  File "/usr/share/grip/grip/readers.py", line 108, in _find_file
raise ReadmeNotFoundError(path)
grip.exceptions.ReadmeNotFoundError: No README found at .

I don't think README should be needed to clear the cache...


-- System Information:
Architecture: i386

Versions of packages grip depends on:
ii  python3-docopt0.6.2-4
ii  python3-flask 2.0.3-1
ii  python3-markdown  3.4.1-2
ii  python3-path-and-address  2.0.1-3
ii  python3-pygments  2.12.0+dfsg-2
ii  python3-requests  2.27.1+dfsg-1
ii  python3   3.10.6-1

--
Jakub Wilk

Bug#1023625: puppet-module-puppetlabs-apt: CVE-2022-3275

[Moritz Mühlenhoff]

Source: puppet-module-puppetlabs-apt
X-Debbugs-CC: t...@security.debian.org
Severity: important
Tags: security

Hi,

The following vulnerability was published for puppet-module-puppetlabs-apt.

CVE-2022-3275[0]:
| Command injection is possible in the puppetlabs-apt module prior to
| version 9.0.0. A malicious actor is able to exploit this vulnerability
| only if they are able to provide unsanitized input to the module. This
| condition is rare in most deployments of Puppet and Puppet Enterprise.

https://puppet.com/security/cve/CVE-2022-3275
https://github.com/puppetlabs/puppetlabs-apt/commit/c26ad2a54f318b4d6fbe55f837b00cd6afd9f1eb

This doesn't warrant a DSA (but could be fixed via spu)

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-3275
https://www.cve.org/CVERecord?id=CVE-2022-3275

Please adjust the affected versions in the BTS as needed.

Bug#1023624: RM: pytoml -- ROM; obsoleted by upstream; alternatives exist

[Bastian Germann]

Source: pytoml

pytoml should be removed in favour of python-toml(i).
sid should now be free of reverse dependencies; I will ping again when bookworm 
is free of them as well.
Please reassign this package to ftp.debian.org if you agree to remove it.

Bug#1023623: dolphin: In file rename dialog: Delete and Backspace act on file, not on text

[Max Görner]

Package: dolphin
Version: 4:22.08.1-1
Severity: important

Dear Maintainer,

I don't use Dolphin often, so I cannot say since when this issue exists. 
However, I only noticed it on 5th of November.

I tried to rename a bunch of files using Dolphin. So I selected one file, 
pressed F2 and entered a new text. Now, if I made a typo, I was unable to 
correct this. If I hit the backspace or delete key, Dolphin interpreted the key 
as command, not as text alteration. Thus, upon backspace the parent folder was 
opened. Upon delete the file was removed. You can imagine that this was very 
annoying.

A workaround was to select some text and enter the correction. That would 
replace the selection.

Best Regards
Max Görner

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

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

Versions of packages dolphin depends on:
ii  baloo-kf5 5.98.0-1+b1
ii  kinit 5.98.0-1
ii  kio   5.98.0-1
ii  libc6 2.35-4
ii  libdolphinvcs54:22.08.1-1
ii  libkf5activities5 5.98.0-1
ii  libkf5baloo5  5.98.0-1+b1
ii  libkf5baloowidgets5   4:22.08.1-1
ii  libkf5bookmarks5  5.98.0-1
ii  libkf5codecs5 5.98.0-1
ii  libkf5completion5 5.98.0-1
ii  libkf5configcore5 5.98.0-2
ii  libkf5configgui5  5.98.0-2
ii  libkf5configwidgets5  5.98.0-1
ii  libkf5coreaddons5 5.98.0-1
ii  libkf5crash5  5.98.0-1
ii  libkf5dbusaddons5 5.98.0-1
ii  libkf5filemetadata3   5.98.0-1
ii  libkf5i18n5   5.98.0-1+b1
ii  libkf5iconthemes5 5.98.0-2+b1
ii  libkf5itemviews5  5.98.0-1
ii  libkf5jobwidgets5 5.98.0-1
ii  libkf5kcmutils5   5.98.0-1
ii  libkf5kiocore55.98.0-1
ii  libkf5kiofilewidgets5 5.98.0-1
ii  libkf5kiogui5 5.98.0-1
ii  libkf5kiowidgets5 5.98.0-1
ii  libkf5newstuff5   5.98.0-1
ii  libkf5newstuffwidgets55.98.0-1
ii  libkf5notifications5  5.98.0-1
ii  libkf5parts5  5.98.0-1
ii  libkf5service-bin 5.98.0-1
ii  libkf5service55.98.0-1
ii  libkf5solid5  5.98.0-1
ii  libkf5textwidgets55.98.0-1
ii  libkf5widgetsaddons5  5.98.0-1
ii  libkf5windowsystem5   5.98.0-1
ii  libkf5xmlgui5 5.98.0-1+b1
ii  libkuserfeedbackcore1 1.2.0-2
ii  libkuserfeedbackwidgets1  1.2.0-2
ii  libpackagekitqt5-11.0.2-1
ii  libphonon4qt5-4   4:4.11.1-4
ii  libqt5core5a  5.15.6+dfsg-2
ii  libqt5dbus5   5.15.6+dfsg-2
ii  libqt5gui55.15.6+dfsg-2
ii  libqt5widgets55.15.6+dfsg-2
ii  libqt5xml55.15.6+dfsg-2
ii  libstdc++612.2.0-3
ii  phonon4qt54:4.11.1-4

Versions of packages dolphin recommends:
ii  ffmpegthumbs  4:22.04.2-1
ii  kdegraphics-thumbnailers  4:21.12.3-1
ii  kimageformat-plugins  5.98.0-1+b1
ii  kio-extras4:22.04.3-1+b1

Versions of packages dolphin suggests:
pn  dolphin-plugins  

-- no debconf information

Bug#1023451: Current Bookworm daily image breaks root file system during resize

[Bastian Blank]

Control: reassign -1 linux/6.0-1~exp1
Control: forcemerge 1023450 -1

On Fri, Nov 04, 2022 at 02:04:05PM +0100, Sven Bartscher wrote:
> [  163.701342] EXT4-fs (sda1): resizing filesystem from 491515 to 4161531
> blocks
> [  163.870631] EXT4-fs (sda1): resized filesystem to 4161531
> [  163.914439] EXT4-fs (sda1): Invalid checksum for backup superblock 32768
> [  163.914439]
> [  163.914892] EXT4-fs error (device sda1) in ext4_update_backup_sb:174:
> Filesystem failed CRC

The ext4 maintainer confirmed this is a kernel bug introduced in 6.0.

Bastian

-- 
Only a fool fights in a burning house.
-- Kank the Klingon, "Day of the Dove", stardate unknown

Bug#460232: Please clarify license

[Steve Langasek]

On Mon, Nov 07, 2022 at 11:33:53AM +0100, Bastian Germann wrote:
> Why did you lower the severity when pam is violating the Policy?

The existing copyright file precisely documents a free software license
under which the contents of the package can be distributed and modified. 
The copyright file should be improved (thank you for the patch).  But
claiming that it is violating policy is nonsense.

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


signature.asc
Description: PGP signature

Bug#460232: Please clarify license

[Steve Langasek]

On Mon, Nov 07, 2022 at 11:15:27AM -0800, Steve Langasek wrote:
> On Mon, Nov 07, 2022 at 11:33:53AM +0100, Bastian Germann wrote:
> > Why did you lower the severity when pam is violating the Policy?

> The existing copyright file precisely documents a free software license
> under which the contents of the package can be distributed and modified. 
> The copyright file should be improved (thank you for the patch).  But
> claiming that it is violating policy is nonsense.

Ok, I've reviewed the text accompanying your patch and realize that it's not
nonsense, sorry.  I was unaware that there were contents within the source
package that were not LGPL-licensed (a consequence of Debian's pathological
approach to copyright file handling).  I think this would have been better
done as a separate bug report, but anyway, feel free to re-raise the
severity and I will prioritize getting this addressed.

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


signature.asc
Description: PGP signature

Bug#1023450: e2fsprogs - Does not agree with kernel on clean state

[Bastian Blank]

Control: reassign -1 linux/6.0-1~exp1

On Mon, Nov 07, 2022 at 01:44:01PM -0500, Theodore Ts'o wrote:
> On Fri, Nov 04, 2022 at 01:17:35PM +0100, Bastian Blank wrote:
> Yes, this is a kernel bug.  It's fixed in upstream commit 9a8c5b0d0615
> ("ext4: update the backup superblock's at the end of the online
> resize"), which landed is in v6.1-rc4 and which is tagged for
> backporting to LTS.

Thanks.  Re-assining to the kernel.

Bastian

-- 
The heart is not a logical organ.
-- Dr. Janet Wallace, "The Deadly Years", stardate 3479.4

Bug#1023005: A recent Bookworm upgrade broke video playback in the VLC player

[local10]

Nov 6, 2022, 23:04 by amub...@gmail.com:

> Are you getting something like in the videos attached in the bug: #1023580 ?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023580
>
> I personally also have vlc graphical issues and black screen when playing a 
> video after Qt update to 5.15.6.
> So maybe what you have is related.
>


Tried it and I don't seem to have that scaling effect shown in the 
qt_5.15.6+dfsg-2_vlc_glitches.mp4. Am using the Breeze theme (not Breeze Dark 
or Breeze Twilight, just Breeze).

VLC still shows black screen when playing videos (MP4s) though.


Regards,

Bug#1022114: RFH: highlight -- Universal source code to formatted text converter

[Daniel Echeverri]

Hello!

El jue, 20 oct 2022 a la(s) 05:33, David Bremner (brem...@debian.org)
escribió:

> Package: wnpp
> Severity: normal
> X-Debbugs-Cc: debian-de...@lists.debian.org
> Control: affects -1 src:highlight
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> I request assistance with maintaining the highlight package.
>
> I have not really been keeping up with new upstream releases and could
> use a co-maintainer.
>
> The package description is:
>  A utility that converts sourcecode to HTML, XHTML, RTF, LaTeX, TeX,
>  SVG, XML or terminal escape sequences with syntax highlighting.  It
>  supports several programming and markup languages.  Language
>  descriptions are configurable and support regular expressions.  The
>  utility offers indentation and reformatting capabilities.  It is
>  easily possible to create new language definitions and colour themes.
>
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmNRIyoACgkQA0U5G1Wq
> FSGyjQ/8CbUEHtTj0Rad0xZAdVULj9B3EqJN9H35YyUatq85rbdJ69p1cMLgWiu0
> hQbypoCRyn+swf30+Slc7X8tIlmKoqxkDJOiqGl5uLdgEUmMB5Ael89ZUCQU+yh5
> m2BPAYWb6AuU0uJPPXBGIfIcw54ZtzzGMarvgd7PTlxEOYBaSZo+mkzO4YB/AoXc
> xLSSXUp8mW3kqQoQEtyJ5NlwfFVoaERUIJcJXHurtd3wWk8NCbqau+10/m/oyem8
> AzRHzEzu8FsIadYlK6jyvCtcuHY6WwEVnA++qsWd92CjBza2nmb2bjS8bgRRC/JS
> K/gcK2bf2zA2J4o6BKJgfSmTO9rzp0hb4CwYv/91ecM/rNB8mBvUIYzZn1caKbGZ
> N758k9HcyMDywEdZ8Ue2fl0hmYg0/skO7FJEB2TIfnAhqJlQ6n+MexRLIVTAJ8zW
> 1omcULUhnW3c6IdK8WmM6DuX76iO1QGkrslMU3opsKvy8G4jOyp8l3qh3oqd6uWj
> hXknT5lPaE936qd6xDn2dy4niB07W0FhSWBpb9jb3nb5G1pkoWbx/iRjmRT+v0KU
> QB50EoNYZDVWw9AyI0wTkU3NwanWWIggG6lpripCoirxaqlDkkJxe5VH0N9fZncZ
> irLYONNifkBHonshPaDgIYGTN5U55NlaVPs58p95GGvNw+61dmg=
> =GkDM
> -END PGP SIGNATURE-
>
>
My perl skills maybe aren't the highest but my desire to help is yes :) so
 if you agree I could co-maintain highlight with you,

I am working in a new revision, I will push the changes to Salsa soon.

Regards.

-- 
Daniel Echeverri
Debian Developer
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB

Bug#1023450: e2fsprogs - Does not agree with kernel on clean state

[Theodore Ts'o]

On Fri, Nov 04, 2022 at 01:17:35PM +0100, Bastian Blank wrote:
> Package: e2fsprogs
> Version: 1.46.6~rc1-1+b1
> Severity: important
> 
> While doing an online resize on lnux 6.0.5, the kernel considers the
> filesystem broken:
> 
> | [   56.958856] EXT4-fs (sda1): resizing filesystem from 491515 to 4161531 
> blocks
> | [   57.290138] EXT4-fs (sda1): resized filesystem to 4161531
> | [   57.332382] EXT4-fs (sda1): Invalid checksum for backup superblock 32768
> ...
> 
> Currently I would assume this is a bug in the kernel, do you know more?

Yes, this is a kernel bug.  It's fixed in upstream commit 9a8c5b0d0615
("ext4: update the backup superblock's at the end of the online
resize"), which landed is in v6.1-rc4 and which is tagged for
backporting to LTS.

Apologies for this not getting noticed in my pre-release testing.  I'm
working to improve the testing so this would have gotten caught
earlier.

- Ted

commit 9a8c5b0d061554fedd7dbe894e63aa34d0bac7c4
Author: Theodore Ts'o 
Date:   Thu Oct 27 16:04:36 2022 -0400

ext4: update the backup superblock's at the end of the online resize

When expanding a file system using online resize, various fields in
the superblock (e.g., s_blocks_count, s_inodes_count, etc.) change.
To update the backup superblocks, the online resize uses the function
update_backups() in fs/ext4/resize.c.  This function was not updating
the checksum field in the backup superblocks.  This wasn't a big deal
previously, because e2fsck didn't care about the checksum field in the
backup superblock.  (And indeed, update_backups() goes all the way
back to the ext3 days, well before we had support for metadata
checksums.)

However, there is an alternate, more general way of updating
superblock fields, ext4_update_primary_sb() in fs/ext4/ioctl.c.  This
function does check the checksum of the backup superblock, and if it
doesn't match will mark the file system as corrupted.  That was
clearly not the intent, so avoid to aborting the resize when a bad
superblock is found.

In addition, teach update_backups() to properly update the checksum in
the backup superblocks.  We will eventually want to unify
updapte_backups() with the infrasture in ext4_update_primary_sb(), but
that's for another day.

Note: The problem has been around for a while; it just didn't really
matter until ext4_update_primary_sb() was added by commit bbc605cdb1e1
("ext4: implement support for get/set fs label").  And it became
trivially easy to reproduce after commit 827891a38acc ("ext4: update
the s_overhead_clusters in the backup sb's when resizing") in v6.0.

Cc: sta...@kernel.org # 5.17+
Fixes: bbc605cdb1e1 ("ext4: implement support for get/set fs label")
Signed-off-by: Theodore Ts'o 

Bug#1023622: glusterfs-server: glusterfs-cli is only Recommends instead of Requires

[Alex Ruddick]

Package: glusterfs-server
Version: 10.1-1
Severity: normal
X-Debbugs-Cc: a.rudd...@numat-tech.com

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991383
In 9.3.2 the 'gluster' binary was moved out to a new 'gluster-cli' package.
Part of the rationale given was to match Fedora.
https://fedora.pkgs.org/37/fedora-updates-testing-aarch64/glusterfs-server-10.3-1.fc37.aarch64.rpm.html
However, the new package is only Recommended in Debian/Ubuntu, but Required in 
Fedora.

This means that the server package is basically broken (in a patch release, no 
less!)
since the 'gluster' binary is critical to actually setting up or running a 
server.
Refer to e.g. the upstream Quick Start Guide which references 'gluster' left 
and right.
https://docs.gluster.org/en/main/Quick-Start-Guide/Quickstart/

Note: I had installed from the 9 PPA 
(https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-9),
which did not modify the package as debian did.  So I didn't notice the 
breakage until 10.x was released,
triggering the upgrade.

-- 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 5.15.0-52-generic (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages glusterfs-server depends on:
ii  glusterfs-client  10.1-1
ii  glusterfs-common  10.1-1
ii  lsb-base  11.1.0ubuntu4

Versions of packages glusterfs-server recommends:
ii  glusterfs-cli  10.1-1
ii  nfs-common 1:2.6.1-1ubuntu1

glusterfs-server suggests no packages.

-- no debconf information

Bug#1023621: azure-cli - incomplete dependences: ModuleNotFoundError

[Bastian Blank]

Package: azure-cli
Version: 2.42.0-1
Severity: serious

Simple VM operations, like start, fail with ModuleNotFoundError.  So some
dependencies are incorrect.

|  %  az vm start -h
| The command failed with an unexpected error. Here is the traceback:
| No module named 'azure.mgmt.compute.v2022_08_01'
| Traceback (most recent call last):
|   File "/usr/lib/python3/dist-packages/knack/cli.py", line 233, in invoke
| cmd_result = self.invocation.execute(args)
|   File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", 
line 561, in execute
| self.commands_loader.load_arguments(command)
|   File "/usr/lib/python3/dist-packages/azure/cli/core/__init__.py", line 507, 
in load_arguments
| self.command_table[command].load_arguments()  # this loads the arguments 
via reflection
|   File "/usr/lib/python3/dist-packages/azure/cli/core/commands/__init__.py", 
line 318, in load_arguments
| super(AzCliCommand, self).load_arguments()
|   File "/usr/lib/python3/dist-packages/knack/commands.py", line 104, in 
load_arguments
| cmd_args = self.arguments_loader()
|   File 
"/usr/lib/python3/dist-packages/azure/cli/core/commands/command_operation.py", 
line 125, in arguments_loader
| op = self.get_op_handler(self.op_path)
|   File 
"/usr/lib/python3/dist-packages/azure/cli/core/commands/command_operation.py", 
line 59, in get_op_handler
| handler = import_module(mod_to_import)
|   File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
| return _bootstrap._gcd_import(name[level:], package, level)
|   File "", line 1050, in _gcd_import
|   File "", line 1027, in _find_and_load
|   File "", line 992, in _find_and_load_unlocked
|   File "", line 241, in _call_with_frames_removed
|   File "", line 1050, in _gcd_import
|   File "", line 1027, in _find_and_load
|   File "", line 1004, in _find_and_load_unlocked
| ModuleNotFoundError: No module named 'azure.mgmt.compute.v2022_08_01'

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (700, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 azure-cli depends on:
ii  python33.10.6-1
ii  python3-azure-cli  2.42.0-1

azure-cli recommends no packages.

azure-cli suggests no packages.

-- no debconf information

Bug#1023606: Bug#1023606: samba: IPv6 only samba-tool gpo listall does not work, can't find DC

[Michael Tokarev]

07.11.2022 21:18, Michael Tokarev wrote:
..

Thank you but definitely not: I've been already blamed by
adding even simplest patches to debian which are not applied
upstream - the ones which does not affect functionality in
any way.


I stand correct here. There were no blames, that was a lie.
But it was undoubtfully unwelcome.

I'm sorry for that.

/mjt

Bug#1023609: smbclient does not work with kerberos ccache of KEYRING: type

[Andrew Bartlett]

On Mon, 2022-11-07 at 16:45 +0100, Vincent Danjean wrote:
> - smbclient does not handle ccache using the kernel keyring
>   Perhaps this is due to samba using heimdal kerberos implementation?

That is all this is.  An MIT build would work, but that isn't a
supported way to build the AD DC at this time.

Andrew Bartlett

-- 
Andrew Bartlett (he/him) https://samba.org/~abartlet/
Samba Team Member (since 2001) https://samba.org
Samba Developer, Catalyst IT https://catalyst.net.nz/services/samba

Bug#1023606: [Pkg-samba-maint] Bug#1023606: samba: IPv6 only samba-tool gpo listall does not work, can't find DC

[Michael Tokarev]

Control: severity -1 normal

07.11.2022 17:30, Matthew Grant wrote:

Package: samba
Version: 4.16.5
Severity: important
Tags: patch upstream ipv6
X-Debbugs-Cc: m...@mattgrant.net.nz

This is reported upstream as Samba bug 
https://bugzilla.samba.org/show_bug.cgi?id=15226

Bug in central Samba DNS resolution code in IPv6 only environment.  This one 
probably also
affects domain sign up and join code, as well as samba-tool gpo
funcionality.

finddcs() does not resolve SRV records when there are only  records in the 
DNS for the AD DC servers.


Thank you for the work.

Lowering severity since this is usually easy to work around by using an ipv4 
network,
at least temporarily in rfc1918 address space.


Patch attached.  Please merge with Debian Samba packages.


Thank you but definitely not: I've been already blamed by
adding even simplest patches to debian which are not applied
upstream - the ones which does not affect functionality in
any way. Your does affect, so per upstream, it must be applied
upstream first.

Thanks,

/mjt

Bug#1023619: libx86emu: Add riscv64 support

[Yifan Xu]

Source: libx86emu
Version: 3.5-1
Severity: wishlist
Tags: ftbfs patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
X-Debbugs-Cc: debian-ri...@lists.debian.org

Dear Maintainer,

Please enable riscv64 architecture, patch file is attached.

I tried to build on Hifive Unmatched and qemu, build succeed with only enabling
the architecture in debian/control, no other changes needed.

Thank you.

Yifan Xu
--- control 2022-11-08 01:05:15.714709311 +0800
+++ libx86emu-3.5/debian/control2022-11-08 01:06:05.547714145 +0800
@@ -11,7 +11,7 @@
 Rules-Requires-Root: no
 
 Package: libx86emu3
-Architecture: any-amd64 any-i386 alpha armel armhf ia64
+Architecture: any-amd64 any-i386 alpha armel armhf ia64 riscv64
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
 Pre-Depends: ${misc:Pre-Depends}
@@ -23,7 +23,7 @@
  This package contains the library.
 
 Package: libx86emu-dev
-Architecture: any-amd64 any-i386 alpha armel armhf ia64
+Architecture: any-amd64 any-i386 alpha armel armhf ia64 riscv64
 Multi-Arch: same
 Section: libdevel
 Depends: libx86emu3 (= ${binary:Version}), ${misc:Depends}

Bug#1023620: new upstream required for pgcli

[Daniel Baumann]

Package: python-pgspecial
Version: 1.11.10+dfsg1-2

Hi,

thank you for maintaining python-pgspecial in Debian. Could you please
update it to the current upstream version (1.13.0) that has been ported
to psycopg3. The current relases of pgcli require this and are
unfortunately broken until python-pgspecial is updated.

As you might know, python-pgspecial is prominently used by pgcli, one of
the "dbcli"/prompt-toolkit programs which I'm maintaining all of them in
Debian. Since I'm uploading all of them "together" in sync, except for
python-pgspecial, it might make sense that I could also upload
python-pgspecial to keep the roundtrips short, what do you think?

Regards,
Daniel

Bug#1014595: linux-image-5.19.0-rc4-amd64: Enable CONFIG_SND_SOC_INTEL_SOF_ES8336_MACH=m

[Giovanni Caligaris]

Hi, can anyone pick this up and push it to the latest kernel versions 
please.


On Fri, Jul 8 2022 at 03:05:40 PM +0100, Giovanni Caligaris 
 wrote:

Package: src:linux
Version: 5.19~rc4-1~exp1
Severity: normal
X-Debbugs-Cc: giovannicaliga...@gmail.com 



Dear Maintainer,

Please enable CONFIG_SND_SOC_INTEL_SOF_ES8336_MACH=m. This will 
enable sound on all Chuwi Hi10 Go N5100 tablets


Thanks,

-- Package-specific info:
** Version:
Linux version 5.19.0-rc4-amd64 (debian-ker...@lists.debian.org 
) (gcc-11 (Debian 11.3.0-4) 
11.3.0, GNU ld (GNU Binutils for Debian) 2.38.50.20220627) #1 SMP 
PREEMPT_DYNAMIC Debian 5.19~rc4-1~exp1 (2022-07-01)


** Command line:
BOOT_IMAGE=/vmlinuz-5.19.0-rc4-amd64 
root=UUID=3f54a2bb-e3c0-451d-8253-770c09e73f18 ro quiet


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

** Kernel log:
[7.696875] EXT4-fs (mmcblk0p2): mounted filesystem with ordered 
data mode. Quota mode: none.

[7.726742] mei_me :00:16.0: enabling device ( -> 0002)
[7.727246] iTCO_vendor_support: vendor-support=0
[7.727417] usb 1-3: Found UVC 1.00 device Back Camera (0bda:5876)
[7.728156] cfg80211: Loading compiled-in X.509 certificates for 
regulatory database
[7.728415] cfg80211: Loaded X.509 cert 'b...@debian.org 
: 577e021cb980e0e820821ba7b54b4961b8b4fadf'
[7.728649] cfg80211: Loaded X.509 cert 'romain.per...@gmail.com 
: 
3abbc6ec146e09d1b6016ab9d6cf71dd233f0328'
[7.728886] cfg80211: Loaded X.509 cert 'sforshee: 
00b28ddf47aef9cea7'
[7.730815] platform regulatory.0: firmware: direct-loading 
firmware regulatory.db
[7.732282] platform regulatory.0: firmware: direct-loading 
firmware regulatory.db.p7s
[7.734833] input: Back Camera: Back Camera as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input10

[7.736385] usb 1-4: Found UVC 1.00 device Front Camera (0bda:5842)
[7.755764] input: Front Camera: Front Camera as 
/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/input/input11

[7.755828] usbcore: registered new interface driver uvcvideo
[7.816113] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device 
(Version=6, TCOBASE=0x0400)
[7.817191] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec 
(nowayout=0)
[7.888235] input: PC Speaker as 
/devices/platform/pcspkr/input/input12

[7.896632] pstore: Using crash dump compression: deflate
[7.896651] pstore: Registered efi as persistent store backend
[7.930254] Intel(R) Wireless WiFi driver for Linux
[7.930727] iwlwifi :01:00.0: enabling device ( -> 0002)
[7.941831] iwlwifi :01:00.0: firmware: direct-loading 
firmware iwlwifi-7265D-29.ucode
[7.941861] iwlwifi :01:00.0: Found debug destination: 
EXTERNAL_DRAM

[7.941864] iwlwifi :01:00.0: Found debug configuration: 0
[7.942454] iwlwifi :01:00.0: loaded firmware version 
29.4063824552.0 7265D-29.ucode op_mode iwlmvm

[7.948245] cryptd: max_cpu_qlen set to 1000
[8.044607] SSE version of gcm_enc/dec engaged.
[8.049731] audit: type=1400 audit(1657288784.499:2): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="nvidia_modprobe" pid=455 comm="apparmor_parser"
[8.049739] audit: type=1400 audit(1657288784.499:3): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="nvidia_modprobe//kmod" pid=455 comm="apparmor_parser"
[8.050854] audit: type=1400 audit(1657288784.503:4): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="lsb_release" pid=454 comm="apparmor_parser"
[8.051618] audit: type=1400 audit(1657288784.503:5): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/usr/bin/man" pid=457 comm="apparmor_parser"
[8.051624] audit: type=1400 audit(1657288784.503:6): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="man_filter" pid=457 comm="apparmor_parser"
[8.051626] audit: type=1400 audit(1657288784.503:7): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="man_groff" pid=457 comm="apparmor_parser"
[8.062205] audit: type=1400 audit(1657288784.511:8): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="ioq3ded" pid=475 comm="apparmor_parser"
[8.064971] audit: type=1400 audit(1657288784.515:9): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=477 comm="apparmor_parser"
[8.064980] audit: type=1400 audit(1657288784.515:10): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" 
pid=477 comm="apparmor_parser"
[8.068895] snd_hda_intel :00:1f.3: DSP detected with PCI 
class/subclass/prog-if info 0x040100
[8.070625] audit: type=1400 audit(1657288784.523:11): 
apparmor="STATUS" operation="profile_load" profile="unconfined" 
name="ioquake3" pid=476 comm="apparmor_parser"

[8.152689] Bluetooth: 

Bug#1023618: djview4: division by 0 in QDjVuPrivate::findPosition()

[Jakub Wilk]

Package: djview4
Version: 4.12-3

If you open the attached file, set zoom to 1:1 (View → Zoom → One to 
one), and the close it, djview4 crashes with SIGFPE.


Backtrace:

#0  0x565874df in QDjVuPrivate::findPosition (this=0x567a1fe0, point=..., 
closestAnchor=true) at qdjvuwidget.cpp:1773
#1  0x56589794 in QDjVuWidget::positionWithClosestAnchor (this=0x567efed0, 
point=...) at qdjvuwidget.cpp:2346
#2  0x566211ce in QDjView::getDecoratedUrl (this=0x56799a10) at qdjview.cpp:3401
#3  0x5661ceda in QDjView::closeDocument (this=0x56799a10) at qdjview.cpp:2629
#4  0x5662447b in QDjView::closeEvent (this=0x56799a10, event=0xc480) at 
qdjview.cpp:3768


-- System Information:
Architecture: i386

Versions of packages djview4 depends on:
ii  libc62.36-4
ii  libdjvulibre21   3.5.28-2
ii  libgcc-s112.2.0-9
ii  libqt5core5a 5.15.6+dfsg-2
ii  libqt5gui5   5.15.6+dfsg-2
ii  libqt5network5   5.15.6+dfsg-2
ii  libqt5opengl55.15.6+dfsg-2
ii  libqt5printsupport5  5.15.6+dfsg-2
ii  libqt5widgets5   5.15.6+dfsg-2
ii  libstdc++6   12.2.0-9
ii  libtiff5 4.4.0-5+b1
ii  sensible-utils   0.0.17

--
Jakub Wilk

Bug#1023617: ldc: Build-depends on packages no in testing (llvm-11-dev)

[Scott Kitterman]

Source: ldc
Version: 1:1.30.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: 1000...@bugs.debian.org

LLVM 11 is not in Testing and will not be shipped with Bookworm:

llvm-11-dev | 1:11.0.1-2 | stable   | amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el, s390x
llvm-11-dev | 1:11.1.0-6+b2  | unstable | amd64, arm64, armel, 
armhf, i386, mips64el, mipsel, ppc64el, s390x

ldc needs to build-depend on a newer LLVM or be removed from Testing.

Scott K

Bug#1023403: systemd: After a stand-by a service with an ended trigger is not executed

[Francois Mescam]

Since I've install systemd 252.2 apt-daily is executed just after a 
sleep even if the timer end during sleep state.


So I think you can close 1023403.

Regards

--
Francois Mescam

Bug#1023616: opensbi: Emulation of fence.tso hangs in endless loop

[Heinrich Schuchardt]

Package: opensbi
Version: 1.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu lunar ubuntu-patch

Dear Maintainer,

  * Fix emulation of fence.tso hanging in endless loop on Allwinner D1
d/p/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
(LP: #1995860)

Thanks for considering the patch.

Best regards

Heinrich

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

Kernel: Linux 5.19.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
--- 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
   1970-01-01 01:00:00.0 +0100
+++ 
opensbi-1.1/debian/patches/lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch
   2022-11-07 14:25:01.0 +0100
@@ -0,0 +1,36 @@
+From 111afc12306e4368fa112f97d31ea802c4561294 Mon Sep 17 00:00:00 2001
+From: Rahul Pathak 
+Date: Fri, 12 Aug 2022 19:24:42 +0530
+Subject: [PATCH] lib: sbi_illegal_insn: Fix FENCE.TSO emulation infinite trap
+ loop
+
+In case of missing "FENCE.TSO" instruction implementation,
+opensbi can emulate the "FENCE.TSO" with "FENCE RW,RW", but
+mepc was not incremented to continue from the next instruction
+causing infinite trap.
+
+Fixes: cb8271c8 ("lib: sbi_illegal_insn: Add emulation for fence.tso")
+Signed-off-by: Rahul Pathak 
+Reviewed-by: Andrew Jones 
+Reviewed-by: Xiang W 
+Reviewed-by: Samuel Holland 
+Origin: 
https://github.com/riscv-software-src/opensbi/commit/111afc12306e4368fa112f97d31ea802c4561294
+---
+ lib/sbi/sbi_illegal_insn.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/lib/sbi/sbi_illegal_insn.c b/lib/sbi/sbi_illegal_insn.c
+index ecd3508..9691bce 100644
+--- a/lib/sbi/sbi_illegal_insn.c
 b/lib/sbi/sbi_illegal_insn.c
+@@ -40,6 +40,7 @@ static int misc_mem_opcode_insn(ulong insn, struct 
sbi_trap_regs *regs)
+   /* Errata workaround: emulate `fence.tso` as `fence rw, rw`. */
+   if ((insn & INSN_MASK_FENCE_TSO) == INSN_MATCH_FENCE_TSO) {
+   smp_mb();
++  regs->mepc += 4;
+   return 0;
+   }
+ 
+-- 
+2.37.2
+
diff -Nru opensbi-1.1/debian/patches/series opensbi-1.1/debian/patches/series
--- opensbi-1.1/debian/patches/series   1970-01-01 01:00:00.0 +0100
+++ opensbi-1.1/debian/patches/series   2022-11-07 13:18:42.0 +0100
@@ -0,0 +1 @@
+lib-sbi_illegal_insn-Fix-FENCE.TSO-emulation-infinit.patch

Bug#1023615: libdvd-pkg: remove build-dir after build

[Christoph Anton Mitterer]

Package: libdvd-pkg
Version: 1.4.3-1-1
Severity: wishlist


Hey.

Just a minor thing, but I think /usr/src/libdvd-pkg/build/ could
always be removed after the script ran.

The /usr/src/libdvd-pkg/libdvdcss* files (especially
libdvdcss_1.4.3.orig.tar.bz2) I would however keep (unless of course the
package is removed or purged).
Especially also with regard to what I've proposed in #1023614.


Cheers,
Chris.

Bug#1023614: libdvd-pkg: split builder from provider package and more

[Christoph Anton Mitterer]

Package: libdvd-pkg
Version: 1.4.3-1-1
Severity: wishlist


Hi.

AFAIU, right now we have libdvd-pkg, which is both:
- the package building the actual packages
- a "provider" package (for libdvdcss2 and libdvdcss-dev)

I think this removes quite some flexibility and it would be nice
to have these split up (or maybe, the provider functionality isn't
needed at all?).



If libdvd-pkg would just build the package, one could do e.g.
the following:

- Have a config file parsed, which allows setting e.g.
  DEB_SIGN_KEYID and then have the generated files signed
  (i.e. no -uc in the dpkg-buildpackage call)
- Have a option, which basically allows setting a hook that's
  called after a successful build.
  Per default this could be the current:
dpkg --install /usr/src/${PKGI}/*_${VERGG}~local_*.deb
  but one could also change it to something like moving
  the built files (incl. .changes/etc.) to e.g. the incoming/
  dir of debarchiver and then have that updated. Or call dput.

  Or do both, upload into some e.g. local debarchiver archive
  AND to the dpkg -i.

The benefit would be, that the packages don't shop up as
obsolete/local anymore.


Cheers,
Chris.

Bug#1023613: linux-image-6.0.0-2-amd64: Please enable Gigabyte WMI module

[Anton Shestakov]

Package: src:linux
Version: 6.0.5-1
Severity: normal
X-Debbugs-Cc: a...@dwimlabs.net

Dear Maintainer,

Please enable Gigabyte WMI module, it allows people to see data from
temperature sensors located on various modern Gigabyte motherboards using
`sensors` command.


-- Package-specific info:
** Version:
Linux version 6.0.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.5-1 (2022-10-28)

Bug#1014387: RFA: db-defaults

[Bastian Germann]

Control: retitle -1 ITA: db-defaults -- Berkeley Database Utilities and 
Libraries
Control: owner -1 b...@debian.org

I am going to have a shot at this package.

Bug#1023612: New poetry 1.2.2 version

[Mathieu Malaterre]

Package: src:poetry
Version: 1.1.14+dfsg-1

It would be super nice to have version 1.2.2 uploaded to Debian archive.

Thanks for packaging poetry !

-M

Bug#1023611: mingw: provide EGL for MinGW

[Rainer Sabelka]

Package: mingw-w64-common
Version: 10.0.0-2
Severity: wishlist
File: mingw

Dear Maintainer,
I tried to cross-compile Qt 5.15.7 with MinGW for 64 bit Windows on a recent
Debian Bookworm system. It failed because EGL could not be found.
It would be nice if the Debian MinGW package could include EGL or an
separate MinGW mesa packacke including EGL would be available.


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

Kernel: Linux 6.0.5-1-default (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

-- no debconf information


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

Bug#1023610: cyrus-common: Switch from db-upgrade-util to db-util

[Bastian Germann]

Package: cyrus-common
Version: 3.6.0~beta3-1

Please replace the db-upgrade-util dependency with db-util so that 
db-upgrade-util can be removed,
which is long overdue. This package is its last reverse dependency.

Bug#1023609: smbclient does not work with kerberos ccache of KEYRING: type

[Vincent Danjean]

Package: smbclient
Version: 2:4.16.6+dfsg-5~bpo11+1
Severity: normal

  Hi,

  I'm trying to use smbclient with kerberos login, for example to
get the list of shares with somthing like:

smbclient -N --use-kerberos=required -gL samba-server.example.org

If using the FILE: ccache, it works.
If using a KEYRING: ccache, it does not work.

And the --use-krb5-ccache option does not seems to be taken into account

$ export KRB5CCNAME=FILE:/tmp/ccache_file
$ rm $KRB5CCNAME 
rm: cannot remove 'FILE:/tmp/ccache_file': No such file or directory
$ kinit
Password for XXX@XXX:
$ smbclient -N --use-kerberos=required --use-krb5-ccache=FILE:/tmp/ccache_file 
-gL samba-server.example.org
[... list of shares ...]
$ smbclient -N --use-kerberos=required -gL samba-server.example.org
[... list of shares ...]
$ smbclient -N --use-kerberos=required --use-krb5-ccache=FILE:/non-existant -gL 
samba-server.example.org
[... list of shares ...] <- probably a fail-back to KRB5CCNAME
$ export KRB5CCNAME=FILE:/non-existant
$ smbclient -N --use-kerberos=required -gL samba-server.example.org
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in 
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER
$ smbclient -N --use-kerberos=required --use-krb5-ccache=FILE:/tmp/ccache_file 
-gL samba-server.example.org
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in 
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER
$ smbclient -N --use-kerberos=required --use-krb5-ccache=/tmp/ccache_file -gL 
samba-server.example.org
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in 
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER
$ export KRB5CCNAME=KEYRING:persistent:`id -u`:krb_ccache
$ kinit
Password for XXX@XXX:
$ smbclient -N --use-kerberos=required -gL samba-server.example.org
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in 
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER
$ smbclient -N --use-kerberos=required --use-krb5-ccache=$KRB5CCNAME -gL 
samba-server.example.org
gensec_spnego_client_negTokenInit_step: Could not find a suitable mechtype in 
NEG_TOKEN_INIT
session setup failed: NT_STATUS_INVALID_PARAMETER


klist and other kerberos-enabled tools (such as ssh) work correctly
when KRB5CCNAME is set to FILE:... but also to KEYRING:...

So, from my experiments, it seems:
- the --use-krb5-ccache is never used (at least when KRB5CCNAME is set)
  [it was not the goal of this bug report, but I see it when trying my commands]
- smbclient does not handle ccache using the kernel keyring
  Perhaps this is due to samba using heimdal kerberos implementation?

  Regards,
Vincent


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

Kernel: Linux 5.15.0-0.bpo.3-amd64 (SMP w/6 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages smbclient depends on:
ii  libarchive13  3.4.3-2+deb11u1
ii  libbsd0   0.11.3-1
ii  libc6 2.31-13+deb11u4
ii  libgnutls30   3.7.1-5+deb11u2
ii  libpopt0  1.18-2
ii  libreadline8  8.1-1
ii  libsmbclient  2:4.16.6+dfsg-5~bpo11+1
ii  libtalloc22.3.3-4~bpo11+1
ii  libtevent00.11.0-1~bpo11+1
ii  samba-common  2:4.16.6+dfsg-5~bpo11+1
ii  samba-libs2:4.16.6+dfsg-5~bpo11+1

smbclient recommends no packages.

Versions of packages smbclient suggests:
ii  cifs-utils   2:7.0-2~bpo11+1
pn  heimdal-clients  

-- no debconf information

Bug#1023523: Fw: RFP: poxy -- Documentation generator for C++ based on Doxygen and mosra/m.css

[Bastian Germann]

Am 07.11.22 um 16:01 schrieb Lance Lin:

I would be happy to work on bringing this to Debian. But with so many 
prerequisite packages,
would it make more sense to join the Python Team and work these dependencies 
(and eventually poxy)
through them?

This would require a lot of sponsorship support and hopefully the Python team 
could be
faster than mentors.


Yes, please join the Python team for this.

Bug#1023608: RFP: pytomlpp

[Bastian Germann]

Package: wnpp
Severity: wishlist
X-Debbugs-Cc: debian-de...@lists.debian.org
Control: block -1 by 1020595
Control: block 1023523 by -1

* Package name: pytomlpp
  Upstream Author : Bob Fang 
* URL : https://github.com/bobfang1992/pytomlpp
* License : Expat
  Programming Lang: Python
  Description : python wrapper for toml++ parser/serializer

This is a python wrapper for toml++. The binding is using pybind11.
Converts toml structure to native python data structures (dict/list etc.).
When parsing, this is in line with what json module does.

Bug#1023607: 50-depmod.install fails if kmod is not installed

[Max Kellermann]

Package: systemd
Version: 252-2

My computer has custom-built kernels without module support, and
therefore I did not install kmod.  When installing a kernel package, I get:

 /usr/lib/kernel/install.d/50-depmod.install: 28: exec: depmod: not found

This script comes with the systemd package, but systemd does not
depend on kmod, and doing so would be the wrong solution; the proper
solution is to check whether "depmod" is installed in the script.

Bug#924685: RFP: cumin -- An automation and orchestration framework

[Antoine Beaupré]

On 2021-09-01 10:37:22, Antoine Beaupré wrote:
> On 2019-03-16 21:17:52, Moritz Muehlenhoff wrote:
>> Antoine Beaupre wrote:
>>> Upstream (in CC) already ships Debian packages on their Github
>>> releases page, but it would be great to see this in Debian.
>>> 
>>> I'd be happy to sponsor this package if upstream is willing to act as
>>> maintainers, otherwise I will look at packaging this myself.
>>
>> Hi Antoine,
>> thanks for your interest in Cumin :-)
>>
>> We're totally planning to maintain Cumin in Debian, but there's a
>> few breaking changes lined up we don't want to impose on Debian
>> users (plus NEW is frozen anyway), so this will probably only
>> happen in a few months at the start of the bullseye development cycle.
>
> Hi!
>
> NEW was thawed, and I just reinstalled cumin in a virtualenv, and
> thought of this bug. :) Need help with the packaging? I'd be happy to
> just throw it in the python packaging team...

Ping! did you receive that message?

-- 
We don't need any more heroes.
We just need someone to take out recycling.
- Banksy

Bug#1023606: samba: IPv6 only samba-tool gpo listall does not work, can't find DC

[Matthew Grant]

Package: samba
Version: 4.16.5
Severity: important
Tags: patch upstream ipv6
X-Debbugs-Cc: m...@mattgrant.net.nz

This is reported upstream as Samba bug 
https://bugzilla.samba.org/show_bug.cgi?id=15226

Bug in central Samba DNS resolution code in IPv6 only environment.  This one 
probably also
affects domain sign up and join code, as well as samba-tool gpo
funcionality.

finddcs() does not resolve SRV records when there are only  records in the 
DNS for the AD DC servers.

Patch attached.  Please merge with Debian Samba packages.




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

Kernel: Linux 5.15.75-amd64-mag-lts (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.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 samba depends on:
ii  adduser  3.118
ii  dpkg 1.20.12
ii  init-system-helpers  1.60
ii  libbsd0  0.11.3-1
ii  libc62.31-13+deb11u5
ii  libcups2 2.3.3op2-3+deb11u2
ii  libgnutls30  3.7.1-5+deb11u2
ii  libldap-2.4-22.4.57+dfsg-3+deb11u1
hi  libldb2  2:2.4.1+mag-1
ii  libpam-modules   1.4.0-9+deb11u1
ii  libpam-runtime   1.4.0-9+deb11u1
ii  libpopt0 1.18-2
pn  libpython3.7 
ii  libpython3.9 3.9.2-1
ii  libtalloc2   2.3.3+mag-1~0mag0
ii  libtasn1-6   4.16.0-2
ii  libtdb1  1.4.6+mag-1
ii  libtevent0   0.11.0+mag-1~0mag0
ii  libwbclient0 2:4.16.5+mag-2
ii  lsb-base 11.1.0
ii  procps   2:3.3.17-5
ii  python3  3.9.2-3
ii  python3-dnspython2.0.0-1
pn  python3-samba
pn  samba-common 
pn  samba-common-bin 
pn  samba-libs   
ii  tdb-tools1.4.6+mag-1

Versions of packages samba recommends:
ii  attr1:2.4.48-6
ii  logrotate   3.18.0-2+deb11u1
ii  python3-markdown3.3.4-1
pn  samba-dsdb-modules  
pn  samba-vfs-modules   

Versions of packages samba suggests:
pn  bind9 
ii  bind9-utils [bind9utils]  1:9.16.33-1~deb11u1
ii  bind9utils1:9.16.33-1~deb11u1
ii  chrony4.0-8+deb11u2
pn  ctdb  
ii  ldb-tools 2:2.5.2+samba4.16.5+mag-2
ii  smbldap-tools 0.9.11-2
pn  ufw   
pn  winbind   
diff --git a/source4/libcli/resolve/dns_ex.c b/source4/libcli/resolve/dns_ex.c
index 0bb3ba02287..0525d0d019a 100644
--- a/source4/libcli/resolve/dns_ex.c
+++ b/source4/libcli/resolve/dns_ex.c
@@ -81,7 +81,7 @@ struct dns_records_container {
uint32_t count;
 };
 
-static int reply_to_addrs(TALLOC_CTX *mem_ctx, uint32_t *a_num,
+static int reply_to_addrs(TALLOC_CTX *mem_ctx, uint32_t *addr_num,
  char ***cur_addrs, uint32_t total,
  struct dns_request *reply, int port)
 {
@@ -151,8 +151,8 @@ static int reply_to_addrs(TALLOC_CTX *mem_ctx, uint32_t 
*a_num,
rr->name->pLabelList->label);
if (addrs[total]) {
total++;
-   if (rr->type == QTYPE_A) {
-   (*a_num)++;
+   if (rr->type == QTYPE_A || rr->type == QTYPE_) {
+   (*addr_num)++;
}
}
}
@@ -211,7 +211,7 @@ static struct dns_records_container 
get_a__records(TALLOC_CTX *mem_ctx,
struct dns_request *reply;
struct dns_records_container ret;
char **addrs = NULL;
-   uint32_t a_num, total;
+   uint32_t addr_num, total;
uint16_t qtype;
TALLOC_CTX *tmp_ctx;
DNS_ERROR err;
@@ -236,12 +236,13 @@ static struct dns_records_container 
get_a__records(TALLOC_CTX *mem_ctx,
}
}
 
-   a_num = total = 0;
-   total = reply_to_addrs(tmp_ctx, _num, , total, reply, port);
+   addr_num = total = 0;
+   total = reply_to_addrs(tmp_ctx, _num, , total, reply, port);
 
-   if (qtype == QTYPE_ && a_num == 0) {
+   if (qtype == QTYPE_ && addr_num == 0) {
/*
-   * DNS server didn't returned A when asked for  records.
+   * DNS server didn't returned A when asked for  records,
+   * and no  record returned either
* Most of the server do it, let's ask for A specificaly.
*/
err = dns_lookup(tmp_ctx, name, QTYPE_A, );
@@ -249,7 +250,7 @@ static struct dns_records_container 
get_a__records(TALLOC_CTX *mem_ctx,
goto done;
}
 
-

Bug#1023605: Intel Unknown processors -- Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz

[xiao sheng wen]

Package: linuxinfo
Version: 4.1.0-1
Severity: wishlist
Tags: upstream
X-Debbugs-Cc: atzli...@sina.com

Hi,

 linuxinfo output the "Unknown" for i3 CPU:
  
Linux atzlinux-33 6.0.0-2-rt-amd64 #1 SMP PREEMPT_RT Debian 6.0.6-2 (2022-11-01)
Four Intel Unknown 905MHz processors, 29533.60 total bogomips, 7875M RAM
System library 2.36.0

I hope add i3 in linuxinfo.

Thanks!

-- Package-specific info:
/proc/cpuinfo:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz
stepping: 3
microcode   : 0x28
cpu MHz : 897.982
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb 
invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm 
arat pln pts md_clear flush_l1d
vmx flags   : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb 
flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
bogomips: 7383.40
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz
stepping: 3
microcode   : 0x28
cpu MHz : 897.998
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 1
cpu cores   : 2
apicid  : 2
initial apicid  : 2
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb 
invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm 
arat pln pts md_clear flush_l1d
vmx flags   : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb 
flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
bogomips: 7383.40
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 2
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : Intel(R) Core(TM) i3-4170 CPU @ 3.70GHz
stepping: 3
microcode   : 0x28
cpu MHz : 864.466
cache size  : 3072 KB
physical id : 0
siblings: 4
core id : 0
cpu cores   : 2
apicid  : 1
initial apicid  : 1
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 
ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb 
invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid 
ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm 
arat pln pts md_clear flush_l1d
vmx flags   : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb 
flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
bogomips: 7383.40
clflush size: 64
cache_alignment : 64
address sizes   : 39 bits physical, 48 bits virtual
power management:

processor   : 3
vendor_id   : GenuineIntel
cpu family  : 6
model   : 60
model name  : 

Bug#1022188: debugpy: FTBFS due to either "Timed out..." or "Address already in use"

[Julian Gilbey]

Hi Sergio,

On Fri, Oct 21, 2022 at 01:43:10PM -0400, Sergio Durigan Junior wrote:
> Source: debugpy
> Version: 1.6.3+ds-1
> Severity: serious
> 
> Hi,
> 
> debugpy is currently FTBFSing:
> [...]
> 
> The long summary is too big to post here, but you can see the full log
> at:
> 
>   
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/debugpy.html
> [...]
> I found a few upstream bugs that contain either the "Timed out waiting
> for debug server to connect" or the "Address already in use" messages,
> but I haven't investigated further TBH.

Sorry for the slow reply.  That's interesting, because it built fine
on the buildd network and using lxc.  If it's "address already in
use", it's probably because there are timing issues: it's running the
tests on multiple CPUs and if it tries to spin up local servers on two
CPUs almost simultaneously, they might end up trying to use the same
port.  I saw this same issue with pydevd, and worked around it by
restricting it to using a single CPU; maybe I should do the same here.
If it's "timed out", I'm not sure what the cause is; might it possibly
be that pbuilder does not allow servers to start on local ports or for
the build to connect to local ports?  I had to work around this in
pydevd's debian/rules, but it didn't seem to be a problem with
debugpy.  Maybe it is.

Ho hum, something to investigate!

Best wishes,

   Julian

Bug#1023604: "License" tab in About window needs nonexistent /usr/share/hugin/xrc/data/COPYING.txt

[Michael Deegan]

Package: hugin
Version: 2021.0.0+dfsg-3
Severity: normal

Upon opening the "About" window, an extra window popping up, complaining:

   21:00:01: can't open file '/usr/share/hugin/xrc/data/COPYING.txt' (error 2: 
No such file or directory)
   21:00:01: File couldn't be loaded.

And sure enough, the License tab in the About window is empty. I assume this
is the result of the Debian build system attempting to avoid the situation
where user systems have a bajillion near-identical COPYING.txt files on them.
But I think we need this one. :)

-- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'oldstable-updates'), (500, 'oldstable-debug'), (500, 
'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (480, 'testing-debug'), 
(480, 'testing'), (470, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages hugin depends on:
ii  enblend 4.2-9
ii  enfuse  4.2-9
ii  hugin-tools 2021.0.0+dfsg-3
ii  libc6   2.35-4
ii  libexiv2-27 0.27.5-4
ii  libfftw3-double33.3.8-2
ii  libgcc-s1   10.2.1-6
ii  libglew2.2  2.2.0-4+b1
ii  libglu1-mesa [libglu1]  9.0.2-1.1
ii  libglx0 1.5.0-1
ii  libgomp110.2.1-6
ii  libimage-exiftool-perl  12.16+dfsg-2
ii  liblcms2-2  2.12~rc1-2
ii  libopengl0  1.5.0-1
ii  libpano13-3 2.9.20~rc3+dfsg-1
ii  libsqlite3-03.34.1-3
ii  libstdc++6  12.2.0-3
ii  libtiff54.2.0-1+deb11u1
ii  libvigraimpex11 1.11.1+dfsg-8
ii  libwxbase3.2-0  3.2.1+dfsg-1
ii  libwxgtk3.2-0   3.2.1+dfsg-1
ii  make4.3-4.1

hugin recommends no packages.

Versions of packages hugin suggests:
ii  darktable4.0.0-1
ii  dcraw9.28-2
ii  rawtherapee  5.8-3

-- debconf-show failed

-MD

-- 
-
Michael Deegan   Hugaholic  https://www.deegan.id.au/
  Jung, zr jbeel?  --

Bug#1008735: base-files: /etc/os-release should contain VERSION variables for testing and unstable

[Santiago Vila]

El 6/11/22 a las 2:01, Witold Baryluk escribió:

I am somehow confused by the current solution in base-files 12.3.


Please note that what I did in 12.3 does not try to solve everything, 
only what it was feasible to do in base-files. I do not claim that the 
situation may not improve, only that such improvement, if any, should 
come from some place other than base-files.



bookworm:
[...]
sid:
[...]



How one can distinguish between testing / bookworm and sid now? Do I need
to parse files in /etc/apt/sources.list.d/ now, maybe using `apt-cache
policy base-files` ?


Yes, looking at your apt sources would be a good idea. Note that the 
unability to determine the distribution just by looking at files 
provided by base-files has been the case for a lot of time, in fact it 
is documented in the base-files FAQ:


/usr/share/doc/base-files/FAQ

However, just because the real distribution may be inferred by looking 
at your apt sources does not necessarily mean that you have to do that 
by hand. In theory, it would be possible to modify lsb_release command 
so that it looks at your apt sources for you.


But that's not something that may be done in base-files anymore.

Thanks.

Bug#1023603: virtualbox-dkms: virtualbox dkms fails to build with vmlinuz-5.19.0-0.deb11.2-amd64

[LeJacq, Jean Pierre]

Package: virtualbox-dkms
Version: 6.1.40-dfsg-1~fto11+1
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

I am trying to build the virtualbox modules for kernel  5.19.0-0.deb11.2-amd64


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

$ sudo dpkg-reconfigure virtualbox-dkms Insert authentication card for user 
`jplejacq'
Trying authentication as user `jplejacq'...

--
Deleting module version: 6.1.40
completely from the DKMS tree.
--
Done.
Loading new virtualbox-6.1.40 DKMS files...
Building for 5.19.0-0.deb11.2-amd64
Module build for kernel 5.19.0-0.deb11.2-amd64 was skipped since the
kernel headers for this kernel does not seem to be installed.
Job for virtualbox.service failed because the control process exited with 
error code.
See "systemctl status virtualbox.service" and "journalctl -xeu 
virtualbox.service" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
× virtualbox.service - LSB: VirtualBox Linux kernel module
 Loaded: loaded (/etc/init.d/virtualbox; generated)
 Active: failed (Result: exit-code) since Mon 2022-11-07 08:16:01 EST; 7ms 
ago
   Docs: man:systemd-sysv-generator(8)
Process: 8607 ExecStart=/etc/init.d/virtualbox start (code=exited, 
status=1/FAILURE)
CPU: 45ms

Nov 07 08:16:01 qipf1y4mle systemd[1]: Starting LSB: VirtualBox Linux kernel 
module...
Nov 07 08:16:01 qipf1y4mle virtualbox[8607]: Loading VirtualBox kernel 
modules...No suitable module for running kernel found ...
Nov 07 08:16:01 qipf1y4mle virtualbox[8616]:  failed!
Nov 07 08:16:01 qipf1y4mle virtualbox[8617]:  failed!
Nov 07 08:16:01 qipf1y4mle systemd[1]: virtualbox.service: Control process 
exited, code=exited, status=1/FAILURE
Nov 07 08:16:01 qipf1y4mle systemd[1]: virtualbox.service: Failed with result 
'exit-code'.
Nov 07 08:16:01 qipf1y4mle systemd[1]: Failed to start LSB: VirtualBox Linux 
kernel module.

   * What was the outcome of this action?

Failed to build due to missing header files. I do have the installed the two 
header packages for this kernle.

$ apt-cache policy linux-headers-5.19.0-0.deb11.2-amd64 linux-
headers-5.19.0-0.deb11.2-common
linux-headers-5.19.0-0.deb11.2-amd64:
  Installed: 5.19.11-1~bpo11+1
  Candidate: 5.19.11-1~bpo11+1
  Version table:
 *** 5.19.11-1~bpo11+1 1100
   1100 https://mirrors.edge.kernel.org/debian bullseye-backports/main 
amd64 Packages
100 /var/lib/dpkg/status
linux-headers-5.19.0-0.deb11.2-common:
  Installed: 5.19.11-1~bpo11+1
  Candidate: 5.19.11-1~bpo11+1
  Version table:
 *** 5.19.11-1~bpo11+1 1100
   1100 https://mirrors.edge.kernel.org/debian bullseye-backports/main 
amd64 Packages
100 /var/lib/dpkg/status

   * What outcome did you expect instead?

Modules built.

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


-- System Information:
Debian Release: 11.4 (Qinux 3.2)
  APT prefers stable-security
  APT policy: (1000, 'stable-security'), (1000, 'stable'), (500, 'stable-
updates'), (100, 'bullseye-fasttrack'), (100, 'bullseye-backports-staging'), 
(100, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.19.0-0.deb11.2-amd64 (SMP w/12 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox-dkms depends on:
ii  dkms  2.8.4-3

Versions of packages virtualbox-dkms recommends:
ii  virtualbox  6.1.40-dfsg-1~fto11+1

virtualbox-dkms suggests no packages.

-- no debconf information

Bug#1023602: bullseye-pu: package xfig/1:3.2.8-3

[Roland Rosenfeld]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu

[ Reason ]
This fixes CVE-2021-40241 (a potential buffer overflow in reading an
environment variable).

[ Tests ]
Salsa-CI Pipleline passed except reprotest (no idea, what goes wrong
there, maybe a bullseye problem with the pipeline):
https://salsa.debian.org/debian/xfig/-/pipelines/451502

[ Risks ]
The fix is very minimal (change sprintf to snprintf).

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

[ Changes ]
- fix for CVE-2021-40241
- Change in debian/salsa-ci.yml to build with bullseye instead of unstable

Greetings
Roland
diff -Nru xfig-3.2.8/debian/changelog xfig-3.2.8/debian/changelog
--- xfig-3.2.8/debian/changelog	2021-05-20 21:14:22.0 +0200
+++ xfig-3.2.8/debian/changelog	2022-11-07 13:10:05.0 +0100
@@ -1,3 +1,10 @@
+xfig (1:3.2.8-3+deb11u1) bullseye; urgency=medium
+
+  * 10_CVE-2021-40241: Avoid buffer overflow in LANG (CVE-2021-40241)
+(Closes: #992395).
+
+ -- Roland Rosenfeld   Mon, 07 Nov 2022 13:10:05 +0100
+
 xfig (1:3.2.8-3) unstable; urgency=medium
 
   * testsuite: depend on libgs-dev, so the test does no longer randomly
diff -Nru xfig-3.2.8/debian/patches/10_CVE-2021-40241.patch xfig-3.2.8/debian/patches/10_CVE-2021-40241.patch
--- xfig-3.2.8/debian/patches/10_CVE-2021-40241.patch	1970-01-01 01:00:00.0 +0100
+++ xfig-3.2.8/debian/patches/10_CVE-2021-40241.patch	2022-11-07 13:10:05.0 +0100
@@ -0,0 +1,19 @@
+From: Roland Rosenfeld 
+Date: Fri, 20 Aug 2021 13:18:20 +0200
+Origin: upstream, https://sourceforge.net/p/mcj/xfig/ci/1c4e131
+Bug-Debian: https://bugs.debian.org/992395
+Bug: https://bugs.debian.org/992395
+Subject: Avoid buffer overflow in LANG.
+ Fixes CVE-2021-40241
+
+--- a/src/w_help.c
 b/src/w_help.c
+@@ -52,7 +52,7 @@ launch_refman(Widget w, XtPointer closur
+ #ifdef I18N
+ 	if (appres.international && getenv("LANG")) {
+ 	  /* check localized file ($XFIGDOCDIR/html/$LANG/index.html) first */
+-	  sprintf(filename, "%s/html/%s/index.html", XFIGDOCDIR, getenv("LANG"));
++	  snprintf(filename, PATH_MAX, "%s/html/%s/index.html", XFIGDOCDIR, getenv("LANG"));
+ 	  if (!check_docfile(filename))
+ 	sprintf(filename, "%s/html/index.html", XFIGDOCDIR);
+ 	}
diff -Nru xfig-3.2.8/debian/patches/series xfig-3.2.8/debian/patches/series
--- xfig-3.2.8/debian/patches/series	2021-05-20 21:14:22.0 +0200
+++ xfig-3.2.8/debian/patches/series	2022-11-07 13:10:05.0 +0100
@@ -4,3 +4,4 @@
 07_missing-config.h.patch
 08_fig-format-doc.patch
 09_repair-table-doc.patch
+10_CVE-2021-40241.patch
diff -Nru xfig-3.2.8/debian/salsa-ci.yml xfig-3.2.8/debian/salsa-ci.yml
--- xfig-3.2.8/debian/salsa-ci.yml	2021-05-20 21:14:22.0 +0200
+++ xfig-3.2.8/debian/salsa-ci.yml	2022-11-07 13:10:05.0 +0100
@@ -3,4 +3,4 @@
   - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
 
 variables:
-  RELEASE: 'unstable'
+  RELEASE: 'bullseye'


signature.asc
Description: PGP signature

Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it

[Vincent Lefevre]

Package: libgpgme-dev
Version: 1.18.0-2
Severity: grave
Justification: renders package unusable

The removal of gpgme-config due to

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348

breaks the build of software relying on it, such as Mutt:

  https://gitlab.com/muttmua/mutt/-/issues/430
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348

It was removed without letting developers adapt their code first.
Actually I'm not even sure that this is the right long-term decision;
upstream code should be fixed instead.

I can see in the changelog:

   * Fix FTBFS after removal of gpg-error-config (Closes: #1022348)
   * gpgme-config not installed anymore

It seems that the removal of gpg-error-config was a Debian decision
not to keep it with its build rules:
https://dev.gnupg.org/T5683 says "Now, we can consider deprecation
of gpg-error-config, to show preference to gpgrt-config. [...]
Distributions still can install it (by their own make rule), because
gpg-error-config will be kept distributed and built well."

So, if I understand correctly, either gpgme-config should be based on
gpgrt-config rather than gpg-error-config (this should be an upstream
change), or gpg-error-config should be re-added as suggested.

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

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

Versions of packages libgpgme-dev depends on:
ii  libassuan-dev 2.5.5-5
ii  libassuan02.5.5-5
ii  libc6 2.35-1
ii  libc6-dev 2.35-1
ii  libgpg-error-dev  1.46-1
ii  libgpg-error0 1.46-1
ii  libgpgme111.18.0-2

libgpgme-dev recommends no packages.

libgpgme-dev suggests no packages.

-- no debconf information

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

Bug#710490: Well, the zombie bug just bit me again

[Michael Tokarev]

Please let the thing die already. It's been several debian releases :)

Yes, automount is easy to use with its auto.net map, but it really is
not a big deal to generate list of systemd automount units for this,
or just a bunch of fstab records (with x-systemd.automount option).

/mjt

Bug#1023600: python3-jwcrypto includes an empty directory /usr/share/doc/jwcrypto

[Steve McIntyre]

Source: python-jwcrypto
Version: 1.1.0-1
Severity: minor

It looks like the cleanup of build artifacts in
override_dh_auto_install leaves this around:

dpkg --contents 
/mirror/debian/pool/main/p/python-jwcrypto/python3-jwcrypto_1.1.0-1_all.deb  | 
grep usr/share/doc
drwxr-xr-x root/root 0 2022-03-29 08:33 ./usr/share/doc/
drwxr-xr-x root/root 0 2022-03-29 08:33 ./usr/share/doc/jwcrypto/
drwxr-xr-x root/root 0 2022-03-29 08:33 
./usr/share/doc/python3-jwcrypto/
-rw-r--r-- root/root   715 2022-03-29 08:33 
./usr/share/doc/python3-jwcrypto/changelog.Debian.gz
-rw-r--r-- root/root  1114 2022-03-29 08:30 
./usr/share/doc/python3-jwcrypto/copyright

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

Kernel: Linux 5.10.0-16-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_WARN, 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

Bug#1023523: RFP: poxy -- Documentation generator for C++ based on Doxygen and mosra/m.css

[Lance Lin]

Hello Bastian,

On Sat, 5 Nov 2022 23:11:42 +0100 Bastian Germann  wrote:
> Package: wnpp
> Severity: wishlist
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 

> * Package name: poxy
>Version : 0.11.1
>Upstream Author : Mark Gillard 
> * URL : https://github.com/marzer/poxy
> * License : Expat
>Programming Lang: Python
>Description : Documentation generator for C++ based on Doxygen and 
> mosra/m.css
> 

> mosra/m.css is a Doxygen-based documentation generator that significantly 
> improves on Doxygen's 

> default output by controlling some of Doxygen's more unruly options, 
> supplying it's own HTML+CSS 

> generation and adding a live search feature. Poxy builds upon both by:
> 

>* Moving the configuration out into a TOML file
>* Preprocessing the Doxygen XML to fix a bunch of Doxygen bugs quirks
>* Postprocessing the generated HTML to improve syntax highlighting
>* Allowing source, image and example directories to be recursive
>* Automatically defining C++ language feature macros based on your 
> project's target C++ version
>* Automatically integrating the cppreference.com doxygen tagfile
>* Providing a number of additional built-in doxygen @alias commands
>* Giving more control over the HTML inline using square-bracket 
> [tags][/tags]
>* Adding a switchable light theme
>* Adding support for C++20 concepts
>* Self-hosting fonts to reduce external HTTP requests
>* Inlining SVGs so they can take advantage of currentColor

I took an initial look and there seems to be several dependencies missing from 
Debian. 

These would be: misk, trieregex and pytomlpp.

I would be happy to work on bringing this to Debian. But with so many 
prerequisite packages, 

would it make more sense to join the Python Team and work these dependencies 
(and eventually poxy) 

through them?

This would require a lot of sponsorship support and hopefully the Python team 
could be
faster than mentors.

Thank you,

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

signature.asc
Description: OpenPGP digital signature

Bug#1023510: [Debian-on-mobile-maintainers] Bug#1023510: Use update-alternatives for /usr/share/applications/sm.puri.OSK0

[Arnaud Ferraris]

Hi,

Le 05/11/2022 à 18:42, Guido Günther a écrit :

Package: squeekboard
Version: 1.20.0
Severity: wishlist

It can be useful to have both squeekboard and phosh-osk-stub
installed on a system and to switch between them as both implement
the required interfaces.

The upstream phosh-osk-stub packages solves that by using a diversion
but that is not ideal as one can't switch easily.

As I'd like to upload phosh-osk-stub to experimental it would be great
to make squeekboard use `update-alternatives` for

/usr/share/applications/sm.puri.OSK0

so both packages get co-installable and the OSK implementation could
be switched easily.


This sounds like a sensible idea, I support that.

Cheers,
Arnaud



Filing this bug to see if there are objections, otherwise I'd send a
patch for squeekboard.

Cheers,
  -- Guido

-- System Information:
Debian Release: bookworm/sid
   APT prefers testing
   APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-updates'), (500, 'stable-debug'), (500, 
'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental-debug'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64

Kernel: Linux 6.0.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 squeekboard depends on:
ii  gnome-themes-extra-data  3.28-2
ii  libc62.35-3
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libfeedback-0.0-00.0.0+git20220520-1
ii  libgcc-s112.2.0-3
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.0-2
pn  libgnome-desktop-3-19
ii  libgnome-desktop-3-2043-2
ii  libgtk-3-0   3.24.34-3
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libwayland-client0   1.21.0-1
ii  libxkbcommon01.4.1-1

squeekboard recommends no packages.

squeekboard suggests no packages.

___
Debian-on-mobile-maintainers mailing list
debian-on-mobile-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-on-mobile-maintainers

Bug#1023599: mutt: FTBFS due to lack of gpgme-config since gpgme1.0 1.18.0-2

[Vincent Lefevre]

Package: mutt
Version: 2.2.7-1
Severity: serious
Tags: ftbfs
Justification: FTBFS
Forwarded: https://gitlab.com/muttmua/mutt/-/issues/430

The gpgme-config utility was removed in gpgme1.0 1.18.0-2
(because it needs gpg-error-config, which has been removed).

As a consequence the use of --enable-gpgme to build Mutt yields
an error:

dh_auto_configure: error: cd debian/build && ../../configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc 
--localstatedir=/var --disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--with-mailpath=/var/mail --enable-compressed --enable-debug --enable-fcntl 
--enable-hcache --enable-gpgme --enable-imap --enable-smtp --enable-pop 
--enable-sidebar --enable-dotlock --disable-fmemopen --with-curses 
--with-gnutls --with-gss --with-idn2 --with-mixmaster --with-gsasl 
--without-gdbm --without-bdb --without-qdbm --with-tokyocabinet returned exit 
code 1
make[1]: *** [debian/rules:11: override_dh_auto_configure] Error 25

with debian/build/config.log containing

configure:7932: checking for gpgme-config
configure:7968: result: no
configure:8001: checking for GPGME - version >= 1.4.0
configure:8082: result: no
configure:8090: error: *** GPGME not found or version is older than 1.4.0 ***

A workaround would be to remove --enable-gpgme, with the consequence
that GPGME would no longer be supported in Mutt. But this may be bad
for the end user. I've reported a bug upstream, hoping a solution
would be found:

  https://gitlab.com/muttmua/mutt/-/issues/430

Alternatively, gpg-error-config and gpgme-config could be re-added
until things are resolved:

https://dev.gnupg.org/T5683 says "Now, we can consider deprecation
of gpg-error-config, to show preference to gpgrt-config. [...]
Distributions still can install it (by their own make rule), because
gpg-error-config will be kept distributed and built well."

-- Package-specific info:
Mutt 2.2.8+45 (c11015d0) vl-149028 (2022-11-06)
Copyright (C) 1996-2022 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 6.0.0-2-amd64 (x86_64)
ncurses: ncurses 6.3.20220423 (compiled with 6.3)
libidn: 1.41 (compiled with 1.41)

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 12.2.0-7' 
--with-bugurl=file:///usr/share/doc/gcc-12/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-12 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-plugin 
--enable-default-pie --with-system-zlib --enable-libphobos-checking=release 
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch 
--disable-werror --enable-cet --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-12-zpDQmA/gcc-12-12.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-12-zpDQmA/gcc-12-12.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 12.2.0 (Debian 12.2.0-7) 

Configure options: --prefix=/home/vinc17 --enable-debug --enable-pop 
--enable-imap --with-ssl --enable-compressed 
--with-exec-shell=/home/vinc17/bin/sh.screen 
--with-system-dotlock=/usr/bin/mutt_dotlock CC=gcc 'CFLAGS=-g -O3 -march=native 
-fsanitize=undefined -fno-sanitize-recover'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O3 -march=native 
-fsanitize=undefined -fno-sanitize-recover

Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  +USE_FCNTL  -USE_FLOCK   
+USE_POP  +USE_IMAP  -USE_SMTP  
+USE_SSL_OPENSSL  -USE_SSL_GNUTLS  -USE_SASL  -USE_GSASL  -USE_GSS  
+HAVE_GETADDRINFO  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  +HAVE_FUTIMENS  
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME  
-EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Sudip Mukherjee]

Hi Pavel,

On Mon, Nov 7, 2022 at 11:53 AM Pavel Odintsov  wrote:
>
> Hello!
>
> Thank you for reaching me.
>
> Sure, I'll be happy to check.
>
> May I kindly ask what exactly changed to trigger these errors? I believe it 
> was successfully built previously.

Its the update of libbpf to v1.0.1 which removed some of the deprecated API.


-- 
Regards
Sudip

Bug#1023555: fastnetmon: FTBFS with libbpf 1.0

[Pavel Odintsov]

Hello!

Thank you for reaching me.

Sure, I'll be happy to check.

May I kindly ask what exactly changed to trigger these errors? I believe it
was successfully built previously.


On Mon, 7 Nov 2022 at 10:55, Patrick Matthäi  wrote:

> Hey,
>
> Am 06.11.2022 um 19:32 schrieb Sudip Mukherjee:
> > On Sun, Nov 6, 2022 at 3:51 PM Sebastian Ramacher 
> wrote:
> >> Source: fastnetmon
> >> Version: 1.2.3-1
> >> Severity: serious
> >> Tags: ftbfs
> >> Justification: fails to build from source (but built successfully in
> the past)
> >> X-Debbugs-Cc: sramac...@debian.org, sudipm.mukher...@gmail.com
> >>
> >>
> https://buildd.debian.org/status/fetch.php?pkg=fastnetmon=amd64=1.2.3-1%2Bb1=1667748889=0
> > oops, sorry I missed it in my list of packages depending on libbpf. It
> > seems "fastnetmon" added the dependency on libbpf with the last upload
> > and I generated my list before that.   :(
> >
> > Please let me know if you want me to help with a patch to port the
> > code to libbpf.
> >
> >
> Yeah it is a new feature and was just added, dont worry :-)
>
> @Pavel: This is for you, if you need help maybe dont hestiate to ask
> Sudip (thanks for your offer!)
>
> --
> /*
> Mit freundlichem Gruß / With kind regards,
>   Patrick Matthäi
>   GNU/Linux Debian Developer
>
>Blog: https://www.linux-dev.org/
> E-Mail: pmatth...@debian.org
>  patr...@linux-dev.org
> */
>
>

-- 
Sincerely yours, Pavel Odintsov

Bug#1023586: texlive-extra-utils: pythontex won't find python (when on python3)

[Olivier Berger]

Hi.

Norbert Preining  writes:

> Hi
>
> something is **rather** strange on your system ...
>

A Debian testing...

>
> On Mon, 07 Nov 2022, Olivier Berger wrote:
>> FileNotFoundError: [Errno 2] No such file or directory: 'cmd /C "@echo off & 
>> call python pythontex-files-amc-compiled/py_default_default.py & if 
>> errorlevel 1 exit 1"'
>
> That is Windows CMD code and nothing even remotely related to Linux.
>

Well, I agree it looks fishy, but that's just the error log I
got... so... maybe it's just a wrong error message of some kind ?

>> This can be addressed by explicitely invoking with: 
>> pythontex --interpreter python:python3
>
> Maybe also installing
>   python-is-python3
> or how the package name was.

That's it.

However, the description states "No packages may declare dependencies on
this package." ... does this include recommends or suggests ?

Thanks for the pointer and feedback anyway.

Best regards,

-- 
Olivier BERGER
https://www-public.imtbs-tsp.eu/~berger_o/ - OpenPGP 2048R/0xF9EAE3A65819D7E8
Ingenieur Recherche - Dept INF
Institut Mines-Telecom, Telecom SudParis, Evry (France)

Bug#1021918: debian-installer: Kernel module blacklisting inconsistent

[Olaf Meeuwissen]

Sorry for the belated follow-up.

Pascal Hambourg  writes:

> On 22/10/2022 at 03:39, Olaf Meeuwissen wrote:
>> Pascal Hambourg  writes:
>>> On 17/10/2022 at 13:13, Olaf Meeuwissen wrote:
 I recently tried this version with hardware that triggers loading of the
 mt7921e kernel module.  Loading the module fails due to a firmware file
 load error but the installer starts okay.  However, the installer later
 crashes when probing for network hardware (when it tries to rmmod the
 kernel module).
>>>
>>> How does the installer crash exactly ? Kernel panic ? Freeze ? Error ?
>> Freeze.  Even after ten minutes the network hardware probe does not
>> complete.  FWIW, I have seen an error log as well but that may have
>> been with Devuan's preview installer for daedalus.
>
> I could not reproduce this after tricking the installer into unloading
> and reloading the mt7921e module. The module unloads and reloads
> cleanly. But I do not have any hardware matching this module.

The freeze probably only occurs when an attempt to loadh the firmware
file is made.  Unlikely that will happen if the hardware is not found.
Anyway, this issue is not with this particular kernel module but with
the installer's inconsistent module blacklisting behaviour.

FWIW, I've since installed firmware-misc-nonfree and removed all the
blacklisting bits for the module.  WiFi works fine.

>> I've attached the installer's syslog.  /dev/sdc is the installer ISO.
>> The other disks, /dev/sda, /dev/sdb and /dev/nmve0n1 are the machine's
>> internal disks.  I just ran the installer after the machine was already
>> installed with the workaround I mentioned in the original bug report.
>> The error starts at
>>Oct 19 23:06:13 check-missing-firmware: removing and loading
>> kernel module mt7921e
>
>> Oct 19 23:06:13 kernel: [   40.024088] BUG: unable to handle page fault for 
>> address: 6500
>> Oct 19 23:06:13 kernel: [   40.024092] #PF: supervisor write access in 
>> kernel mode
>> Oct 19 23:06:13 kernel: [   40.024094] #PF: error_code(0x0002) - not-present 
>> page
> (...)
>> Oct 19 23:06:13 kernel: [   40.024120] Call Trace:
>> Oct 19 23:06:13 kernel: [   40.024121]  
>> Oct 19 23:06:13 kernel: [   40.024124]  __cancel_work_timer+0x3c/0x190
>> Oct 19 23:06:13 kernel: [   40.024128]  ? __kernfs_remove.part.0+0x190/0x2b0
>> Oct 19 23:06:13 kernel: [   40.024131]  mt7921_pci_remove+0x2c/0x110 
>> [mt7921e]
>
> It looks like a kernel bug when unloading this module. Can you trigger
> the bug in an installed system ? If yes it means that it not specific
> to the installer.

Machine's at the office, will see if I can test tomorrow or the day after.

 The first issue I ran into was that the documented[1] way to blacklist
 kernel modules is no longer correct
[1]:
 https://www.debian.org/releases/testing/amd64/ch05s03.en.html#module-blacklist
 Instead of
 mt7921e.blacklist=yes
 I had to use
 modprobe.blacklist=mt7921e
>>>
>>> /lib/debian-installer-startup.d/S02module-params has the following comment:
>>>
>>> # Before udev is started, parse kernel command word for module params of
>>> # the form module.param=value and register them so they will be used when
>>> # modules are loaded. Also check for modules to be blacklisted.
>>>
>>> But udev is actually started earlier, so the first method does not
>>> work with modules included in initrd.gz (e.g. storage drivers).
>> In that case, shouldn't that be mentioned in the installation
>> manual?
>> Actually, a single method that works for *all* modules, whether in the
>> initrd.gz or installed later is much preferred.
>>
>>> However it should work with network driver modules which are installed
>>> much later.
>> You may want to double check how the kernel command parse results
>> are
>> used then.
>
> I did, and .blacklist works as expected with NIC modules
> matching my hardware (iwlwifi and e1000e).

I meant double check by reading the source code, not by trying with some
rather commonly used modules.

>> Or maybe the mt7921e module is in the initrd.gz?
>> Just checked, it is not.
>
> Indeed, it is in the package nic-wireless-modules--di.
>
 However, upon booting I saw a pile of ATA bus and I/O errors that made
 me suspicious.  The disk is brand new and a smartmontools extended test
 reports no errors.
 I found a /etc/modprobe.d/blacklist.local.conf file with
 blacklist modprobe
>>>
>>> This is a minor bug in
>>> /lib/debian-installer-startup.d/S02module-params which can be easily
>>> fixed. However, it should not have any actual impact as "modprobe"
>>> does not match any kernel module name or alias.
>> Strange, because removing it made those ATA bus and I/O errors go
>> away,
>> reproducibly at that.
>
> Yes, really strange. I cannot explain nor reproduce it.
>
 Seeing that the kernel boot argument is added correctly to the GRUB
 configuration, there is no need to create a file in /etc/modprobe.d/.
>
> 

Bug#1023507: systemd: using docker causes systemd to revert to HandleLidSwitch=suspend

[Michael Biebl]

Am 05.11.22 um 17:34 schrieb Steve McIntyre:

Package: systemd
Version: 247.3-7+deb11u1
Severity: important

Hi!

I've deliberately configured systemd on my laptops to *not* suspend on
lid close, multiple years ago. I've noticed a few times over the last
couple of years that it will sometimes revert to suspending and then
stay with that unwanted behaviour. This is very frustrating.

I've never managed to work out what's happening here, but I think I
may have finally found a reliable trigger!

On a newly-booted system, everything works fine and lid-close causes a
lock. After I start a docker container on this machine, behaviour
changes and it switches to suspending instead. I've done this three
times just now and this behaviour is reliable.

I'm happy to help debug this, but I have no idea on where to start...


urgh, docker...

They are notorious for not playing nice when it comes to systemd and 
just doing their own thing.

Just curious, if you use podman, can you reproduce the issue?





OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023598: tzdata: Convert d/copyright to machine-readable format

[Bastian Germann]

Source: tzdata
Version: 2022f-1
Severity: wishlist
Tags: patch

Please consider converting d/copyright to the machine-readable format.
I have enclosed a converted file that you can use as a replacement.Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Comment: This is the Debian prepackaged version of the Time Zone and
 Daylight Saving Time Data. 
Source: https://www.iana.org/time-zones
Upstream-Contact: The Internet Assigned Numbers Authority (IANA)
  Commentary should be addressed to t...@iana.org

Files: *
Copyright: IANA
License: public-domain
 This database is in the public domain.

Bug#1023593: dkms 3.0.6-4 signs modules without secure boot enabled

[Holger Schröder]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019425

Bug#1023597: FTBFS: t/21-submodule.t: fatal: transport 'file' not allowed

[gregor herrmann]

Source: libgit-repository-perl
Version: 1.325-1
Severity: serious
Tags: ftbfs 
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libgit-repository-perl's test suite started to fail recently:

Cloning into '/tmp/M19xNBDPV8/sub'...
fatal: transport 'file' not allowed
fatal: clone of '/tmp/tC7mgf7E52' into submodule path '/tmp/M19xNBDPV8/sub' 
failed at t/21-submodule.t line 46.
# Looks like your test exited with 128 before it could output anything.
t/21-submodule.t ...
1..1
Dubious, test returned 128 (wstat 32768, 0x8000)
Failed 1/1 subtests


Propably caused by changes in git:

git (1:2.38.1-1) unstable; urgency=medium

  * new upstream release (closes: #1022046; see RelNotes/2.38.0.txt,
RelNotes/2.38.1.txt).
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.



Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNo7HVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaWbA//Zodx1kLFKEaU9L8rgk545iISZXU8BBU/vdLp7VROP9CvkA2mqa4m9MtU
VwMZuQ0HMbxocdjXIi6HZnyAGgh7goaolQV8qDPpLAp33WHZsuVLDQWC+NGMi87E
8imtl3TbKAlSMxXUvIj0gEAHQ650dchjtLKYeNvP0xMgpKviG1Rzf+Nl/3mcfIYX
zP7avstGrnfGrLEz6CgCdzAoeOI1Fs0B5uase5kuBNv3irj9V2Rvl1LDOiTB4JFB
eSBADjAe5rtiTdRhE7z4IvfOIjLHSTHf3w8LcIfPdhQtUWQBb2jkos1PpOfdN1W8
XeLl8SARf2vNRsCqv4GQuBPGhc8xTbSyMPWf8gZADoQcV6rMkTy//ejUdESPXfE4
JdCQazfPONbq213SWF46pduk7N/heZjWdYDf4geVe0kq4nOSPlkst2S/nakMXV5e
uB+eTb/IwTZ1uc6m+MLwUB8D0jinzgnL3eRoGYCokSNJ55kid3UWJbW9eKGQ69/J
6WbaRjCKbmJAL23djEw65Sj8SbpE2jJyaGQFPbU5Wxl25ukCN0/yoMGp6QOs9l/r
bP64+2iYXJeqrXE06QhFO7iRtv+sPa9Sh/Etc9txtJbutbhMf6ig/DcjBzWYL0xP
LXRG5aYSE94B6bKXnA0NFdtCGB04SuT6AsFLd5VkSb5oNUXIFxU=
=qypE
-END PGP SIGNATURE-

Bug#1023567: systemd-container: systemd-machined segfault 6 ABRT

[Michael Biebl]

Hi

Am 06.11.22 um 20:09 schrieb udent:

Package: systemd-container
Version: 247.3-7+deb11u1
Severity: normal
Tags: patch
X-Debbugs-Cc: ud...@mailbox.org

Dear Maintainer,

If you backup the systemd-machined default directory ("/var/lib/machines") with 
borgbackup,
  is one way to segfault systemd-machined.
Systemd State is now: degraded.

Backup the folder without crash, of course.

I test this little patch and it no longer crash:
https://github.com/codepeon/systemd/commit/1600b38cd2029533547f8c3d4abfa12911ca0630.patch
It apply to current stable release without Problems.
i test with "dpkg-source --commit" and "debuild -us -uc"



This patch has landed in v250, so I'm marking the issue as closed for 
that version.
I assume by filing this against the bullseye package, you want to see 
this fixed via a stable upload?


I tagged the bug report so it shows up at [1]. Should we make another 
stable upload, we can consider this issue. The fix is small enough after 
all.


Michael


[1] 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintain...@lists.alioth.debian.org;tag=bullseye-backport;dist=stable


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023557: rygel: consider After=network.target in rygel.service for lingering

[Jens Georg]

Hi Barak,

Rygel should be able to cope with this situation. If it does not not,
then this is a bug that needs looking into.

Please provide the output of journalctl -u rygel.service and also feel
free to take this upstream at
https://gitlab.gnome.org/GNOME/rygel/issues

Bug#1003974: similar bugs having to do with icons not appearing

[Tomas Pospisek]

Hi bug reporters and Libre Office maintainers,

there's a number of bugs related to Icon rendering that seem to be simlar 
or identical. Herewith I'm posting to them to crosslink them.


I have however *not* looked at them in depth. Here are the bug reports:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661818
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969977
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003974
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972280

The idea of posting to all of them/crosslinking them is the hope that 
maybe the reporters and or maintainers can verify that they are the same 
and/or find workarounds or root causes/fixes to all of them...


*t

Bug#1023596: bookworm: document changes in default rsyslog configuration

[Michael Biebl]

Package: release-notes
Severity: normal

The rsyslog configuration changed significantly in bookworm.
Copying the relevant parts from the changelog:

rsyslog (8.2210.0-3) unstable; urgency=medium

  * Stop splitting up mail.*
This avoids having mail related messages duplicated in mail.log and
mail.{info,warn,err}. (Closes: #508376)
  * Drop catch-all log files /var/log/{messages,debug}
Avoid unnecessary duplication as those log messages end up in
/var/log/syslog anyway. (Closes: #580552)
  * Stop splitting lpr facility into its own log file.
The default printing system CUPS is not using this facility so its
basically unused nowadays.
  * Stop splitting daemon facility into its own log file.
The daemon facility is too vaguely defined to be really useful and since
those log messages end up in /var/log/syslog anyway, stop duplicating
them.
  * Split cron facility into its own log file /var/log/cron.log.
The cron facility is widely used and limited enough in scope to have it
split out separately. (Closes: #625483)
  * Update comments in rsyslog.conf
  * Enable high precision timestamps with timezone information.
Use the default rsyslog file format, which provides several benefits
like:
- sortable
- time zone information
- sub-second time resolution
(Closes: #475303)

 -- Michael Biebl   Sat, 29 Oct 2022 22:54:41 +0200


Assuming there is no huge backlash regarding those changes and they will
stay as-is, they should probably be documented in the release notes.



Regards,
Michael

Bug#1017977: Fails to load intel/ibt-20-1-3.sfi

[Olaf Meeuwissen]

Hi again,

Olaf Meeuwissen  writes:

>> Package: linux-image-5.18.0-4-amd64
>> Severity: important
>>
>> The intel/ibt-20-1-3.sfi file loads fine on linux-image-5.18.0-3-amd64.
>> Used that to report this bug as the failure to load leaves me without a
>> working keyboard.  It's a bluetooth-only keyboard and it not working at
>> all is why I've marked this important.
>
> I just want to add that this is still an issue with 6.0.0-2.  Exact same
> symptoms.  Keyboard is useless when booting after a poweroff.  Booting
> into 5.18.0-3 restores keyboard usability.  A subsequent *reboot* to the
> latest linux-image version, as opposed to a poweroff+boot, leaves the
> keyboard in a usable state.

Just upgraded 6.0.0-2 from 6.0.3-1 to 6.0.5-1 and firmware-iwlwifi, which
provides the intel/ibt-20-1-3.sfi file, from 20210818-1 to 20221012-1.
Still no working keyboard after booting following a poweroff.

I'm back to booting 5.18.0-3 which loads the file just fine and gives me
back my keyboard.
--
Olaf Meeuwissen