Bug#1028489: boost1.83 as default

[Anton Gladky]

retitle 1028489 transition: boost1.83
thanks

Dear release team, please consider an updated ben-file. Thanks!

Ben file:

title = "boost1.83";
is_affected = .depends ~ /libboost[a-z-.]*1\.[74]/
is_good = .depends ~ /libboost[a-z-.]*1\.83/
is_bad = .depends ~ /libboost[a-z-.]*1\.74/

Bug#895517: mialmpick is marked for autoremoval from testing

[Andreas Tille]

Hi Gert,

Am Mon, Oct 23, 2023 at 04:39:05AM + schrieb Debian testing autoremoval 
watch:
> mialmpick 0.2.15-2 is marked for autoremoval from testing on 2023-11-20
> 
> It (build-)depends on packages with these RC bugs:
> 895517: libglade2-0: deprecated and unmaintained upstream
>  https://bugs.debian.org/895517

you are upstream and Debian maintainer for this package.  Could you give
some update please, whether you see some chance to solve this issue?  If
not we might consider removing this package.

Kind regards
 Andreas.

-- 
http://fam-tille.de

Bug#1054384: ITP: art/6.1-1 --ASCII art

[Carsten Schoenert]

Hello Yogeswaran,

Am 23.10.23 um 02:33 schrieb Yogeswaran Umasankar:

* Package name     : art
     Version          : 6.1-1
     Upstream contact : Sepand Haghighi 
   * URL              : https://github.com/sepandhaghighi/art
   * License          : MIT
   * Vcs              : https://salsa.debian.org/NGC2023/art
     Section          : python
     Description: ASCII art


the name 'art' is a very generic name, I suggest to use python-art 
according the source is a python library and a similar functionality 
could be also be provided by other programming languages.


The same is true for the binary package name, usually and mostly the 
package name is prefixed by 'python3-'.


PS: Please use reportbug to write your ITPs! It is setting all headers 
correctly.

https://wiki.debian.org/reportbug

--
Regards
Carsten Schönert

Bug#900928: Dependency update

[Jonas Smedegaard]

Quoting Matthias Geiger (2023-10-22 23:55:18)
> While the ruma-stack is still a lot of crates to go through NEW, all are 
> prepared. Meanwhile I uploaded rust-libshumate and rust-libadwaita to 
> unstable.

Yes, I noticed. Thanks!

> I will upload the rest of the ruma crates once the one in NEW has been 
> accepted.

Great!  Thanks for all your work in this,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1054387: vagrant: pkeys are immutable on OpenSSL 3.0

[Phil Dibowitz]

Package: vagrant
Version: 2.3.4+dfsg-1
Severity: important

Dear Maintainer,

I can no longer bring up VMs, they fail with `pkeys are immutable on
OpenSSL 3.0`.

This appears to be because a newer build is required with new net-ssh
dependencies: https://github.com/hashicorp/vagrant/issues/12985

Can you please update? Thanks!

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

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

Versions of packages vagrant depends on:
ii  curl 8.4.0-2
ii  libarchive-tools 3.7.2-1
ii  libruby2.7 [ruby-rexml]  2.7.5-1
ii  libruby3.0 [ruby-rexml]  3.0.4-8
ii  libruby3.1 [ruby-rexml]  3.1.2-7
ii  openssh-client   1:9.4p1-1
ii  rsync3.2.7-1
ii  ruby 1:3.1
ii  ruby-bcrypt-pbkdf1.1.0-2+b3
ii  ruby-childprocess4.1.0-2
ii  ruby-ed25519 1.3.0+ds-1+b4
ii  ruby-erubi   1.12.0-1
ii  ruby-googleapis-common-protos-types  1.4.0-1
ii  ruby-grpc1.51.1-3+b2
ii  ruby-i18n1.14.1-1
pn  ruby-ipaddr  
ii  ruby-listen  3.8.0-1
ii  ruby-log4r   1.1.10-4.1
ii  ruby-mime-types  3.5.1-1
ii  ruby-net-scp 4.0.0-1
ii  ruby-net-sftp1:4.0.0-1
ii  ruby-net-ssh 1:7.2.0-1
ii  ruby-vagrant-cloud   3.0.5-1
ii  ruby-zip 2.3.2-1

Versions of packages vagrant recommends:
ii  vagrant-libvirt  0.11.2-1

Versions of packages vagrant suggests:
ii  virtualbox  7.0.12-dfsg-1

-- no debconf information

Bug#1054386: bookworm-pu: package fssync/1.6-1.1+deb12u1

[Julien Muchembled]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: fss...@packages.debian.org, j...@jmuchemb.eu, sanv...@debian.org
Control: affects -1 + src:fssync

[ Reason ]
This release fixes Bug #858253: FTBFS randomly (AssertionError: Lists differ: 
[b'a', b'a/c'] != [b'a/c'])

[ Impact ]
If the update is not approved, anybody building the package from source will
experience that the package will FTBFS randomly (with high probability) for
no good reason.

[ Tests ]
I can reproduce the random FTBFS failures. The test suite is definitely not 
appropriate
for the current code. As there is a new upstream release in unstable and the 
version in
stable will not change, there is no point in keeping the flaky test suite in 
stable.

[ Risks ]
The program remains the same. Only the test suite is disabled.

[ 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 ]
The test suite is disabled, as it's extremely flaky.
diff -Nru fssync-1.6/debian/changelog fssync-1.6/debian/changelog
--- fssync-1.6/debian/changelog 2021-01-05 18:30:07.0 +0100
+++ fssync-1.6/debian/changelog 2023-10-22 12:25:00.0 +0200
@@ -1,3 +1,10 @@
+fssync (1.6-1.1+deb12u1) bookworm; urgency=medium
+
+  * Disable extremely flaky test suite, as it has been failing randomly
+for several years. Closes: #858253.
+
+ -- Julien Muchembled   Sun, 22 Oct 2023 12:25:00 +0200
+
 fssync (1.6-1.1) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru fssync-1.6/debian/rules fssync-1.6/debian/rules
--- fssync-1.6/debian/rules 2017-01-21 20:53:22.0 +0100
+++ fssync-1.6/debian/rules 2023-10-22 12:25:00.0 +0200
@@ -18,3 +18,5 @@
 
 override_dh_auto_install:
dh_auto_install -- PREFIX=/usr
+
+override_dh_auto_test:


OpenPGP_signature
Description: OpenPGP digital signature

Bug#995414: Acknowledgement (neomutt: pager sometimes displays the wrong mail content)

[Carlos Henrique Lima Melara]

Hey, Jonathan.

I'm going through the list of open bugs in neomutt to triage things,
close some solved bugs and find out what still affects neomutt.

On Fri, 1 Oct 2021 21:26:21 +0100 Jonathan Dowland  wrote:
> Oh of course this is because my header cache got corrupted.

Can I close this bug then? Or do you think neomutt messed your header
cache?

Cheers,
Charles


signature.asc
Description: PGP signature

Bug#1054385: RFS: art/6.1-1 [ITP] -- ASCII art

[Yogeswaran Umasankar]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

 * Package name : art
   Version  : 6.1-1
   Upstream contact : Sepand Haghighi 
 * URL  : https://github.com/sepandhaghighi/art
 * License  : MIT
 * Vcs  : https://salsa.debian.org/NGC2023/art
   Section  : python

The source builds the following binary packages:

  art - ASCII art

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


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

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

  dget -x https://mentors.debian.net/debian/pool/main/a/art/art_6.1-1.dsc

Changes for the initial release:

 art (6.1-1) unstable; urgency=medium
 .
   * Initial release. Closes: #1054384

Regards,
--
  Yogeswaran Umasankar

Bug#1054384: ITP: art/6.1-1 --ASCII art

[Yogeswaran Umasankar]

Package: wnpp
Owner: Yogeswaran Umasankar 
Severity: wishlist

* Package name     : art
   Version          : 6.1-1
   Upstream contact : Sepand Haghighi 
 * URL              : https://github.com/sepandhaghighi/art
 * License          : MIT
 * Vcs              : https://salsa.debian.org/NGC2023/art
   Section          : python
   Description: ASCII art

ASCII art is also known as "computer text art". It involves the
 smart placement of typed special characters or letters to make a
 visual shape that is spread over multiple lines of text.

To access further information about this package, please visit:

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

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

  dget -x https://mentors.debian.net/debian/pool/main/a/art/art_6.1-1.dsc

Changes for the initial release:

  art (6.1-1) unstable; urgency=medium
 .
   * Initial release.

Regards,
--
  Yogeswaran Umasankar

Bug#1054150: surf: no longer display web pages after webkitgtk upgrades

[Dominique Martinet]

Alberto Garcia wrote on Fri, Oct 20, 2023 at 04:19:55PM +0200:
> On Wed, Oct 18, 2023 at 05:06:16PM +0900, Dominique Martinet wrote:
> > After upgrading my system to the latest security updates surf no
> > longer displays anything.
> 
> I had a look at this, the problem is caused by Surf's AppArmor
> configuration.

d'oh ! I need to remember debian now ships this on by default...

> I can make it run on my computer with something like this added to
> /etc/apparmor.d/usr.bin.surf, but your mileage may vary:
> 
>   /sys/devices/virtual/dmi/id/chassis_type r,
>   /etc/glvnd/egl_vendor.d/ r,
>   /etc/glvnd/egl_vendor.d/** r,
>   /usr/share/glvnd/egl_vendor.d/ r,
>   /usr/share/glvnd/egl_vendor.d/** r,
>   /usr/share/libdrm/* r,  

Thanks, I can confirm this works for me as well on various systems
(bullseye VM and bookworm with intel GPU)

(I'm especially annoyed because I saw these in strace output, but the
previous version of webkit also used to try to look at chassis_type and
egl_vendor.d directories so I dismissed that too fast... It's possible
previous versions of webkit were also disabling compositing mode due to
the apparmor rules, but the new one fails to disable it properly when it
didn't find what it wanted there? If so I guess one could argue that's a
bug on its own)

> I think that Surf's AppArmor profile is just too restrictive for a
> program that has so many dependencies.

Right, I guess it's a tight line between trying to sandbox a web browser
and allowing all sort of things a web browser might need to do...
I'll leave follow-ups to Reiner (surf's maintainer), and definitely
remember about apparmor next time.

Thank you again for looking Alberto !

-- 
Dominique

Bug#1054382: gst-plugins-bad1.0: Please migrate away from transitional pkg libzxingcore-dev

[Boyuan Yang]

Source: gst-plugins-bad1.0
X-Debbugs-Cc: by...@debian.org jbi...@ubuntu.com
Version:  1.22.4-1
Severity: normal
Tags: patch sid
Usertags: libzxingcore-dev-removal

Dear Maintainer,

Your package gst-plugins-bad1.0 build-depends on package libzxingcore-dev,
which is a transitional package replaced by libzxing-dev. Package
libzxing-dev is present in Debian Bookworm, Debian Sid and Debian
Testing.

Please replace libzxingcore-dev with libzxing-dev in debian/control
file for your next package upload. Thanks!

Best Regards,
Boyuan Yang


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

Bug#1054383: kaidan: Please migrate away from transitional pkg libzxingcore-dev

[Boyuan Yang]

Source: kaidan
X-Debbugs-Cc: by...@debian.org couc...@debian.org
Version:  0.8.0-2
Severity: normal
Tags: patch sid
Usertags: libzxingcore-dev-removal

Dear Maintainer,

Your package kaidan build-depends on package libzxingcore-dev,
which is a transitional package replaced by libzxing-dev. Package
libzxing-dev is present in Debian Bookworm, Debian Sid and Debian
Testing.

Please replace libzxingcore-dev with libzxing-dev in debian/control
file for your next package upload. Thanks!

Best Regards,
Boyuan Yang


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

Bug#1054381: linphone: Please migrate away from transitional pkg libzxingcore-dev

[Boyuan Yang]

Source: linphone
X-Debbugs-Cc: by...@debian.org be...@debian.org d.fil...@web.de
Version: 5.2.0-4
Severity: normal
Tags: patch sid
Usertags: libzxingcore-dev-removal

Dear Maintainer,

Your package linphone build-depends on package libzxingcore-dev,
which is a transitional package replaced by libzxing-dev. Package
libzxing-dev is present in Debian Bookworm, Debian Sid and Debian
Testing.

Please replace libzxingcore-dev with libzxing-dev in debian/control
file for your next package upload. Thanks!

Best Regards,
Boyuan Yang


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

Bug#1054380: mediastreamer2: Please migrate away from transitional pkg libzxingcore-dev

[Boyuan Yang]

Source: mediastreamer2
X-Debbugs-Cc: by...@debian.org be...@debian.org d.fil...@web.de
Version:  1:5.2.0+dfsg-3
Severity: normal
Tags: patch sid
Usertags: libzxingcore-dev-removal

Dear Maintainer,

Your package mediastreamer2 build-depends on package libzxingcore-dev,
which is a transitional package replaced by libzxing-dev. Package
libzxing-dev is present in Debian Bookworm, Debian Sid and Debian
Testing.

Please replace libzxingcore-dev with libzxing-dev in debian/control
file for your next package upload. Thanks!

Best Regards,
Boyuan Yang


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

Bug#1030801: xdaliclock no longer honors -font or -geometry command line switches

[ydld1pw02]

On Tue, 7 Feb 2023 22:43:29 + (UTC) Daniel Ramaley  
wrote:
> JWZ, thank you for the comment!
>
> Your little program has been a constant part of my Linux desktop since around 
> 1998. And i had no idea that 2.46, which looks like a minor update from the 
> version number, was such a major rewrite under the hood. In the past, i 
> configured xdaliclock via a janky combination of window manager hints, 
> Xresources, and command line switches. I just played with the new version 
> though, and see that if i just resize the window that the font adjusts 
> automatically, and if i place the clock where i want it, it will reopen at 
> that spot the next time i run it. Perfect! No more need for the old way of 
> configuring it. You're right, this is indeed better. Thank you for keeping 
> this old program alive!
>
>

I agree this is better (although it would be nice if there was documentation 
somewhere, e.g. the man page, describing how to customize the size and location 
of the window) except that after I change the size and location of the window 
to 58x19 in the bottom-right corner of my display, when I quit and restart 
xdaliclock it retains the size, but not the position.

Bug#1054379: prison-kf5: Please migrate away from transitional pkg libzxingcore-dev

[Boyuan Yang]

Source: prison-kf5
X-Debbugs-Cc: by...@debian.org couc...@debian.org
Version:  5.107.0-1
Severity: normal
Tags: patch sid
Usertags: libzxingcore-dev-removal

Dear Maintainer,

Your package prison-kf5 build-depends on package libzxingcore-dev,
which is a transitional package replaced by libzxing-dev. Package
libzxing-dev is present in Debian Bookworm, Debian Sid and Debian
Testing.

Please replace libzxingcore-dev with libzxing-dev in debian/control
file for your next package upload. Thanks!

Best Regards,
Boyuan Yang


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

Bug#1054378: kitinerary: Please migrate away from transitional pkg libzxingcore-dev

[Boyuan Yang]

Source: kitinerary
X-Debbugs-Cc: by...@debian.org delta...@debian.org
Version: 22.12.3-2
Severity: normal
Tags: patch
Usertags: libzxingcore-dev-removal

Dear Maintainer,

Your package kitinerary build-depends on package libzxingcore-dev,
which is a transitional package replaced by libzxing-dev. Package
libzxing-dev is present in Debian Bookworm, Debian Sid and Debian
Testing.

Please replace libzxingcore-dev with libzxing-dev in debian/control
file for your next package upload. Thanks!

Best Regards,
Boyuan Yang


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

Bug#1054377: Touchscreen doesn't wake up the system

[Ivan Nikishov]

Package: gnome
Version: 1:43+1

I'm running Debian-12 (5.16.0-rc5) on arm64 architecture (Amlogic S905d3).
Interacting with the touchscreen doesn't wake up the system, after it entered 
suspend state.
As this is a tablet-like device, waking up on touch is a desired behavior.

Is this gnome-shell issue or, perhaps, just a matter of configuration?
I would appreciate some directions on solving this. Thanks in advance.

Bug#1054274: Sound changes volume with cracking noise

[david]

After using for two days last pipewire version, sound seems more stable now,
with usual clicks when changing window focus, for example, but without cracking
in youtube videos or mpv films.

I hope it is so :)

-- 
David

Bug#1053825: Screensaver with only blank does not work after suspend

[Klaus Ethgen]

Hi,

Am Do den 19. Okt 2023 um 20:46 schrieb Salvatore Bonaccorso:
> Can you please attach as well the kernel log once you triggered the
> behaviour? Anything suspicious logged? 

Here is the log of one sleep and wakeup where I had the issue:
   [130045.885692] r8169 :01:00.0 eth0: Link is Down
   [130046.577482] PM: suspend entry (s2idle)
   [130046.577610] Filesystems sync: 0.000 seconds
   [130046.577999] (NULL device *): firmware: direct-loading firmware 
ath11k/WCN6855/hw2.1/regdb.bin
   [130046.578143] (NULL device *): firmware: direct-loading firmware 
ath11k/WCN6855/hw2.1/m3.bin
   [130046.578406] (NULL device *): firmware: direct-loading firmware 
regulatory.db
   [130046.578415] (NULL device *): firmware: direct-loading firmware 
regulatory.db.p7s
   [130046.582058] (NULL device *): firmware: direct-loading firmware 
ath11k/WCN6855/hw2.1/amss.bin
   [130046.582223] (NULL device *): firmware: direct-loading firmware 
ath11k/WCN6855/hw2.1/board-2.bin
   [130046.638817] Freezing user space processes
   [130046.640672] Freezing user space processes completed (elapsed 0.001 
seconds)
   [130046.640680] OOM killer disabled.
   [130046.640682] Freezing remaining freezable tasks
   [130046.642003] Freezing remaining freezable tasks completed (elapsed 0.001 
seconds)
   [130046.642010] printk: Suspending console(s) (use no_console_suspend to 
debug)
   [130046.644003] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local 
choice (Reason: 3=DEAUTH_LEAVING)
   [130046.833356] ACPI: EC: interrupt blocked

   [130048.458201] ACPI: EC: interrupt unblocked
   [130048.646436] [drm] PCIE GART of 1024M enabled (table at 
0x00F43FC0).
   [130048.646479] amdgpu :04:00.0: amdgpu: SMU is resuming...
   [130048.650454] amdgpu :04:00.0: amdgpu: SMU is resumed successfully!
   [130048.660496] nvme nvme0: Shutdown timeout set to 10 seconds
   [130048.665582] nvme nvme0: 16/0/0 default/read/poll queues
   [130048.758856] [drm] VCN decode and encode initialized successfully(under 
DPG Mode).
   [130048.758941] [drm] JPEG decode initialized successfully.
   [130048.758949] amdgpu :04:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 
0 on hub 0
   [130048.758954] amdgpu :04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 
1 on hub 0
   [130048.758957] amdgpu :04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 
4 on hub 0
   [130048.758960] amdgpu :04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 
5 on hub 0
   [130048.758962] amdgpu :04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 
6 on hub 0
   [130048.758964] amdgpu :04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 
7 on hub 0
   [130048.758966] amdgpu :04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 
8 on hub 0
   [130048.758969] amdgpu :04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 
9 on hub 0
   [130048.758971] amdgpu :04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 
10 on hub 0
   [130048.758974] amdgpu :04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv 
eng 11 on hub 0
   [130048.758976] amdgpu :04:00.0: amdgpu: ring sdma0 uses VM inv eng 12 
on hub 0
   [130048.758978] amdgpu :04:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 
0 on hub 8
   [130048.758981] amdgpu :04:00.0: amdgpu: ring vcn_enc_0.0 uses VM inv 
eng 1 on hub 8
   [130048.758983] amdgpu :04:00.0: amdgpu: ring vcn_enc_0.1 uses VM inv 
eng 4 on hub 8
   [130048.758985] amdgpu :04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 5 
on hub 8
   [130048.768693] r8169 :01:00.0 eth0: Link is Down
   [130048.778010] OOM killer enabled.
   [130048.778015] Restarting tasks ... done.
   [130048.781711] random: crng reseeded on system resumption
   [130048.797062] PM: suspend exit

Unlike I seen before, fvwm2 is also affected. Also it is not that
relyable to reproduce. Some times it needs extendet sleeping time and in
the other moment it happens directly after going to sleep.

It looks like the display is drawed in the wrong direction, first the
blacking out from the screensaver and afterwards the content of my
desktop gets drawed above it. And when it happens, it is pretty slow
(for that machine). It takes about one or two seconds.

Note also that there is no S3 on that system available. The system only
went to S2.

Regards
   Klaus
-- 
Klaus Ethgen   http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16Klaus Ethgen 
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C


signature.asc
Description: PGP signature

Bug#1007398: vonsh: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAyED/10 in order to fix this.
The debdiff is attached.diff -Nru vonsh-1.0/debian/changelog vonsh-1.0/debian/changelog
--- vonsh-1.0/debian/changelog  2019-08-26 13:29:08.0 +0200
+++ vonsh-1.0/debian/changelog  2023-10-23 00:25:29.0 +0200
@@ -1,3 +1,11 @@
+vonsh (1.0-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop build-essential packages from Build-Depends. (Closes: #949218)
+  * Convert to source format 3.0. (Closes: #1007398)
+
+ -- Bastian Germann   Mon, 23 Oct 2023 00:25:29 +0200
+
 vonsh (1.0) unstable; urgency=medium
 
   * Initial packaging. Closes: #935761
diff -Nru vonsh-1.0/debian/control vonsh-1.0/debian/control
--- vonsh-1.0/debian/control2019-08-26 13:29:08.0 +0200
+++ vonsh-1.0/debian/control2023-10-23 00:25:26.0 +0200
@@ -2,7 +2,7 @@
 Section: games
 Priority: optional
 Maintainer: Andrzej Urbaniak 
-Build-Depends: libc6-dev (>=2.28), gcc (>=4:8.3.0), g++ (>=4:8.3.0), make 
(>=4.2.1), dpkg-dev (>=1.19.7), debhelper (>= 12), libsdl2-dev (>=2.0.9), 
libsdl2-image-dev (>=2.0.4), libsdl2-mixer-dev (>=2.0.4)
+Build-Depends: debhelper (>= 12), libsdl2-dev (>=2.0.9), libsdl2-image-dev 
(>=2.0.4), libsdl2-mixer-dev (>=2.0.4)
 Standards-Version: 4.3.0
 Homepage: https://github.com/aurb/vonsh/
 
diff -Nru vonsh-1.0/debian/source/format vonsh-1.0/debian/source/format
--- vonsh-1.0/debian/source/format  2019-08-23 22:08:14.0 +0200
+++ vonsh-1.0/debian/source/format  2023-10-23 00:25:29.0 +0200
@@ -1 +1 @@
-1.0
+3.0 (quilt)

Bug#1038710: src:procmail: fails to migrate to testing for too long: unresolved RC bug

[Santiago Vila]

Hi.

In addition to your very appropriate ping in github in August, I've just
made another ping today, let's see what comes from all this.

(If nothing happens, I guess reuploading the old version as
3.24.really.3.23 or alike will be a real possibility).

Thanks.

Bug#1043390: yapra: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a DELAYED/10 NMU in order to fix this.
The debdiff is attached.diff -Nru yapra-0.1.2/debian/changelog yapra-0.1.2/debian/changelog
--- yapra-0.1.2/debian/changelog2023-10-23 00:15:35.0 +0200
+++ yapra-0.1.2/debian/changelog2023-10-23 00:04:37.0 +0200
@@ -1,3 +1,13 @@
+yapra (0.1.2-7.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Convert to source format 3.0. (Closes: #1043390)
+  * Set Priority: optional over extra.
+  * Drop outdated README.source.
+  * Drop Vcs fields. (Closes: #1054375)
+
+ -- Bastian Germann   Mon, 23 Oct 2023 00:04:37 +0200
+
 yapra (0.1.2-7.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru yapra-0.1.2/debian/control yapra-0.1.2/debian/control
--- yapra-0.1.2/debian/control  2023-10-23 00:15:35.0 +0200
+++ yapra-0.1.2/debian/control  2023-10-23 00:04:37.0 +0200
@@ -1,12 +1,10 @@
 Source: yapra
 Section: net
-Priority: extra
+Priority: optional
 Maintainer: Taku YASUI 
-Build-Depends: ruby | ruby-interpreter, quilt, debhelper-compat (= 13)
+Build-Depends: ruby | ruby-interpreter, debhelper-compat (= 13)
 Standards-Version: 3.9.3
 Homepage: http://yapra.rubyforge.org/
-Vcs-Svn: svn://svn.debian.org/svn/collab-maint/deb-maint/yapra
-Vcs-Browser: http://anonscm.debian.org/viewvc/collab-maint/deb-maint/yapra
 
 Package: yapra
 Architecture: all
diff -Nru yapra-0.1.2/debian/README.source yapra-0.1.2/debian/README.source
--- yapra-0.1.2/debian/README.source2023-10-23 00:15:35.0 +0200
+++ yapra-0.1.2/debian/README.source1970-01-01 01:00:00.0 +0100
@@ -1,38 +0,0 @@
-This package uses dpatch to manage all modifications to the upstream
-source. Changes are stored in the source package as diffs in
-debian/patches and applied during the build.
-
-To get the fully patched source after unpacking the source package, cd
-to the root level of the source package and run:
-
-debian/rules patch
-
-Removing a patch is as simple as removing its entry from the
-debian/patches/00list file, and please also remove the patch file
-itself.
-
-Creating a new patch is done with "dpatch-edit-patch patch XX_patchname"
-where you should replace XX with a new number and patchname with a
-descriptive shortname of the patch. You can then simply edit all the
-files your patch wants to edit, and then simply "exit 0" from the shell
-to actually create the patch file.
-
-To tweak an already existing patch, call "dpatch-edit-patch XX_patchname"
-and replace XX_patchname with the actual filename from debian/patches
-you want to use.
-
-To clean up afterwards again, "debian/rules unpatch" will do the
-work for you - or you can of course choose to call
-"fakeroot debian/rules clean" all together.
-
-
 
-
-this documentation is part of dpatch package, and may be used by
-packages using dpatch to comply with policy on README.source. This
-documentation is meant to be useful to users who are not proficient in
-dpatch in doing work with dpatch-based packages. Please send any
-improvements to the BTS of dpatch package.
-
-original text by Gerfried Fuchs, edited by Junichi Uekawa 
-10 Aug 2008.
diff -Nru yapra-0.1.2/debian/rules yapra-0.1.2/debian/rules
--- yapra-0.1.2/debian/rules2023-10-23 00:15:35.0 +0200
+++ yapra-0.1.2/debian/rules2023-10-23 00:04:08.0 +0200
@@ -4,7 +4,7 @@
 RUBYLIBDIR = $(shell ruby -rrbconfig -e 'puts RbConfig::CONFIG["vendordir"]')
 
 %:
-   dh $@ --with quilt
+   dh $@
 
 execute_after_dh_install:
install -m 755 bin/yapra $(DEB_DESTDIR)/usr/bin/yapra
diff -Nru yapra-0.1.2/debian/source/format yapra-0.1.2/debian/source/format
--- yapra-0.1.2/debian/source/format1970-01-01 01:00:00.0 +0100
+++ yapra-0.1.2/debian/source/format2023-10-23 00:04:37.0 +0200
@@ -0,0 +1 @@
+3.0 (quilt)

Bug#1054326: [Debian-ha-maintainers] Bug#1054326: Can't start golbal heartbeat when drbd device is on top LVM device

[Daniel Smolik]

May be but this don't work.

I create  LVM volume heartbeat on both nodes. Set ocfs mode to local.

 o2cb add-heartbeat mdtxcluster  /dev/c/heratbeat
On both nodes.

o2cb start-heartbeat mdtxcluster
on both nodes

ocfs2: Mounting device (147,0) on (node 0, slot 0) with ordered data mode.
[ 1290.746345] o2dlm: Leaving domain 3D69F9BD7AF24C59BB600A8D7B1D4770
[ 1290.788991] ocfs2: Unmounting device (147,0) on (node 0)
[ 1828.717874] o2hb: Heartbeat stopped on region 
3D69F9BD7AF24C59BB600A8D7B1D4770 (dm-0)
[ 2202.976390] o2hb: Heartbeat started on region 
FD5342AE132B4A40A3DE39D0406252E5 (dm-1)
[ 2205.008194] o2hb: Region FD5342AE132B4A40A3DE39D0406252E5 (dm-1) is 
now a quorum device

[ 2229.339352] o2dlm: Joining domain 3D69F9BD7AF24C59BB600A8D7B1D4770
[ 2229.339359] (
[ 2229.339362] 0
[ 2229.339364] ) 1 nodes
[ 2229.360976] ocfs2: Mounting device (147,0) on (node 0, slot 1) with 
ordered data mode.
[ 2229.366496] ocfs2: Begin replay journal (node 1, slot 0) on device 
(147,0)

[ 2229.380189] ocfs2: End replay journal (node 1, slot 0) on device (147,0)
[ 2256.920272] o2dlm: Leaving domain 3D69F9BD7AF24C59BB600A8D7B1D4770
[ 2256.960029] ocfs2: Unmounting device (147,0) on (node 0)
[ 2333.541256] o2dlm: Joining domain 3D69F9BD7AF24C59BB600A8D7B1D4770
[ 2333.541263] (
[ 2333.541266] 0
[ 2333.541268] ) 1 nodes
[ 2333.667424] ocfs2: Mounting device (147,0) on (node 0, slot 0) with 
ordered data mode.

root@drbd-server01:/home/marvin#  o2cb start-heartbeat mdtxcluster



o2hb: Heartbeat started on region C402D542D0D648FAA7EA1D8D7B6571B8 (dm-1)
[ 2802.429790] o2hb: Region C402D542D0D648FAA7EA1D8D7B6571B8 (dm-1) is 
now a quorum device

[ 2847.205047] o2dlm: Joining domain 3D69F9BD7AF24C59BB600A8D7B1D4770
[ 2847.205055] (
[ 2847.205058] 1
[ 2847.205061] ) 1 nodes
[ 2847.292767] ocfs2: Mounting device (147,0) on (node 1, slot 0) with 
ordered data mode.

[ 2875.108121] o2dlm: Leaving domain 3D69F9BD7AF24C59BB600A8D7B1D4770
[ 2875.144193] ocfs2: Unmounting device (147,0) on (node 1)
[ 2963.823619] o2dlm: Joining domain 3D69F9BD7AF24C59BB600A8D7B1D4770
[ 2963.823626] (
[ 2963.823629] 1
[ 2963.823631] ) 1 nodes
[ 2963.870726] ocfs2: Mounting device (147,0) on (node 1, slot 1) with 
ordered data mode.
[ 2963.879606] ocfs2: Begin replay journal (node 0, slot 0) on device 
(147,0)

[ 2963.893880] ocfs2: End replay journal (node 0, slot 0) on device (147,0)



You can see that I have two one node clusters. But no shared storage no 
one two node cluster.





o2cb -v -v -v -v  start-heartbeat   mdtxcluster
Using config file '/etc/ocfs2/cluster.conf'
Initializing cluster stack
Checking heartbeat mode
Global heartbeat enabled
Heartbeat region C402D542D0D648FAA7EA1D8D7B6571B8
Scanning devices
Region C402D542D0D648FAA7EA1D8D7B6571B8 matched to device 
/dev/mapper/c-heratbeat

About to start heartbeat
Starting heartbeat on region C402D542D0D648FAA7EA1D8D7B6571B8, device 
/dev/mapper/c-heratbeat

Stop heartbeat on devices removed from config
Checking heartbeat mode
Global heartbeat enabled
Looking up active heartbeat regions
Global heartbeat started

I set mode to local but after start set to global. I don´t know why.


Regards
                Dan




Dne 22. 10. 23 v 23:48 Valentin Vidic napsal(a):

On Sun, Oct 22, 2023 at 11:38:56PM +0200, Daniel Smolik wrote:

But when use local heartbeat mode I  can  mount ocfs but not work in cluster
mode. I mean that without global heartbeat you didn't have shared storage.

If I understand correctly with local heartbeat there is one heartbeat
running per ocfs2 mount and this should still allow cluster storage
to work.

Global heartbeat only optimizes this to run one or more heartbeat
devices for all ocfs2 mounts, so it should not be a strong requirement
for running a shared cluster storage.

Bug#1054376: liborcus: FTBFS on hppa - segmentation fault in orcus-test-xml-mapped

[John David Anglin]

Source: liborcus
Version: 0.17.2-4
Severity: normal
Tags: ftbfs

Dear Maintainer,

The build fails on real hppa hardware (i.e., not qemu):

FAIL orcus-test-xml-mapped (exit status: 139)


Testsuite summary for liborcus 0.17.2

# TOTAL: 10
# PASS:  9
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

Full log is here:
https://buildd.debian.org/status/fetch.php?pkg=liborcus=hppa=0.17.2-4=1697970148=0

Console output:

do_page_fault() command='orcus-test-xml-' type=15 address=0xf5aca03a in 
libc.so.6[f7429000+1bc000]
trap #15: Data TLB miss fault, vm_start = 0xf5ad4000, vm_end = 0xf5ad5000

strace output:

[...]
statx(AT_FDCWD, "../test/xml-mapped/attribute-namespace/input.xml", 
AT_STATX_SYNC_AS_STAT|AT_NO_AUTOMOUNT, STATX_BASIC_STATS, 
{stx_mask=STATX_BASIC_STATS|STATX_MNT_ID, stx_attributes=0, 
stx_mode=S_IFREG|0644, stx_size=410, ...}) = 0
openat(AT_FDCWD, "../test/xml-mapped/attribute-namespace/input.xml", O_RDONLY) 
= 3
mmap2(NULL, 410, PROT_READ, MAP_SHARED, 3, 0) = 0xf7aca000
munmap(0xf56cf000, 345) = 0
close(5)= 0
openat(AT_FDCWD, "out.xml", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 5
write(5, "\n)
at /usr/include/boost/interprocess/mapped_region.hpp:276
#3  0xfa48e5d8 in orcus::file_content::impl::~impl (this=0x1e4398, 
__in_chrg=) at stream.cpp:152
#4  0xfa48e65c in std::default_delete::operator() 
(this=0xf8f02970, __ptr=0x1e4398)
at /usr/include/c++/13/bits/unique_ptr.h:99
#5  0xfa48c814 in std::unique_ptr >::~unique_ptr (
this=0xf8f02970, __in_chrg=) at 
/usr/include/c++/13/bits/unique_ptr.h:404
#6  0xfa484590 in orcus::file_content::~file_content (this=0xf8f02970, 
__in_chrg=) at stream.cpp:186
#7  0x000194d0 in operator() (__closure=0xf8f02564,

dump_content="ns0=\"http://ns-1\"\nns1=\"http://ns-2\"\n/ns0:data\n/ns0:data/ns1:entries\n/ns0:data/ns1:entries/ns1:entry\n/ns0:data/ns1:entries/ns1:entry@ns1:date-processed=\"2011-01-03\"\n/ns0:data/ns1:entries/ns1:entry@ns1:;...,
filepath=0x1e4678 "../test/xml-mapped/attribute-namespace/input.xml", 
cxt=...) at orcus_test_xml_mapped.cpp:77
#8  0x0001a0fc in (anonymous namespace)::test_mapped_xml_import () at 
orcus_test_xml_mapped.cpp:150
#9  0x0001c01c in main () at orcus_test_xml_mapped.cpp:280
(gdb) c
Continuing.

Breakpoint 2, __GI_memcmp (s1=0xf6fb5024, s2=0xf72ca03a, len=1) at memcmp.c:306
306 memcmp.c: No such file or directory.
(gdb) bt
#0  __GI_memcmp (s1=0xf6fb5024, s2=0xf72ca03a, len=1) at memcmp.c:306
#1  0x0001d65c in std::char_traits::compare (
__s1=0xf6fb5024 "a=\"http://ns-1\; xmlns:b=\"http://ns-2\;>\n
, __n=1) 
at /usr/include/c++/13/bits/char_traits.h:399
#2  0x000218d4 in std::basic_string_view 
>::compare (this=0xf8f03258,
__str=) at 
/usr/include/c++/13/string_view:345
#3  0x000206dc in std::operator== > (__x="a", 
__y=)
at /usr/include/c++/13/string_view:610
#4  0xfa666714 in std::equal_to > >::operator() (this=0x65ebc, __x="a",
__y=) at 
/usr/include/c++/13/bits/stl_function.h:378
#5  0xfa4c186c in std::__detail::_Hashtable_base >, std::pair > const, std::vector > >, std::__detail::_Select1st, 
std::equal_to > >, 
std::hash > >, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Hashtable_traits >::_M_key_equals (
this=0x65ebc, __k="a", __n=...) at 
/usr/include/c++/13/bits/hashtable_policy.h:1728
#6  0xfa4beeb8 in std::_Hashtable >, std::pair > const, std::vector > >, std::allocator > const, std::vector > > >, std::__detail::_Select1st, 
std::equal_to > >, 
std::hash > >, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::find (this=0x65ebc, __k="a") at 
/usr/include/c++/13/bits/hashtable.h:1657
#7  0xfa4bc678 in std::unordered_map >, std::vector for more, q to quit, c to continue without paging--
onst*> >, std::hash > >, 
std::equal_to > >, 
std::allocator > 
const, std::vector > > > >::find 
(this=0x65ebc, __x="a") at /usr/include/c++/13/bits/unordered_map.h:876
#8  0xfa4b454c in orcus::xmlns_context::push (this=0xf8f02628, key="a", 
uri="http://ns-1;) at xml_namespace.cpp:238
#9  0xfa697e28 in 
orcus::sax_ns_parser::handler_wrapper::attribute
 (this=0xf8f02a88, attr=...)
at ../../include/orcus/sax_ns_parser.hpp:235
#10 0xfa695fd4 in 
orcus::sax_parser::handler_wrapper,
 orcus::sax_parser_default_config>::attribute (this=0xf8f02b14) at 
../../include/orcus/sax_parser.hpp:570
#11 0xfa69714c in 
orcus::sax_parser::handler_wrapper,
 orcus::sax_parser_default_config>::element_open (this=0xf8f02b14, 
begin_pos=22) at ../../include/orcus/sax_parser.hpp:290
#12 0xfa6948c8 in 
orcus::sax_parser::handler_wrapper,
 orcus::sax_parser_default_config>::element (this=0xf8f02b14) at 
../../include/orcus/sax_parser.hpp:246
#13 0xfa692da8 in 

Bug#1054375: yapra: Drop Vcs

[Bastian Germann]

Source: yapra

The Vcs-* URLs are not available anymore.
Please drop the fields from d/control.

Bug#1007339: yaret: please consider upgrading to 3.0 source format

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru yaret-2.1.0/debian/changelog yaret-2.1.0/debian/changelog
--- yaret-2.1.0/debian/changelog2023-10-22 23:57:50.0 +0200
+++ yaret-2.1.0/debian/changelog2023-10-22 23:51:06.0 +0200
@@ -1,3 +1,12 @@
+yaret (2.1.0-5.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/copyright: Convert to machine-readable format.
+  * Convert to source format 3.0. (Closes: #1007339)
+  * Use Build-Depends instead of Build-Depends-Indep to enable source builds.
+
+ -- Bastian Germann   Sun, 22 Oct 2023 23:51:06 +0200
+
 yaret (2.1.0-5.2) unstable; urgency=medium
 
   * Non maintainer upload by the Reproducible Builds team.
diff -Nru yaret-2.1.0/debian/control yaret-2.1.0/debian/control
--- yaret-2.1.0/debian/control  2023-10-22 23:57:50.0 +0200
+++ yaret-2.1.0/debian/control  2023-10-22 23:51:06.0 +0200
@@ -2,7 +2,7 @@
 Section: sound
 Priority: optional
 Maintainer: Marco Nenciarini 
-Build-Depends-Indep: cdbs, debhelper (>= 10), quilt
+Build-Depends: cdbs, debhelper (>= 10)
 Standards-Version: 3.9.8
 Homepage: http://www.nongnu.org/yaret
 
diff -Nru yaret-2.1.0/debian/copyright yaret-2.1.0/debian/copyright
--- yaret-2.1.0/debian/copyright2023-10-22 23:57:50.0 +0200
+++ yaret-2.1.0/debian/copyright2023-10-22 23:50:02.0 +0200
@@ -1,31 +1,31 @@
-This package was debianized by Marco Nenciarini  on
-Fri, 11 Jun 2004 13:17:53 +0200.
-
-It was downloaded from http://savannah.nongnu.org/download/yaret/
-
-Upstream Authors: Adam Luter ,
-  Marco Nenciarini 
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: YaRET
+Comment:
+ This package was debianized by Marco Nenciarini .
+Source:
+ http://savannah.nongnu.org/download/yaret/
+Upstream-Contact:
+ Adam Luter ,
+ Marco Nenciarini 
 
+Files: *
 Copyright:
-
-YaRET -- Yet another Ripper-Encoder-Tagger
-
 Copyright (c) 2004 by Marco Nenciarini 
and by Adam Luter   
-
+License: GPL-2+
  This program is free software; you can redistribute it and/or modify
  it under the terms of the GNU General Public License as published by
  the Free Software Foundation; either version 2 of the License, or
  (at your option) any later version.
-
+ .
  This program is distributed in the hope that it will be useful,
  but WITHOUT ANY WARRANTY; without even the implied warranty of
  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  GNU General Public License for more details.
-
+ .
  You should have received a copy of the GNU General Public License
  along with this program; if not, write to the Free Software Foundation,
  Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.
-
-On Debian GNU/Linux systems, the complete text of the GNU General
-Public License can be found in /usr/share/common-licenses/GPL'.
+Comment:
+ On Debian GNU/Linux systems, the complete text of the GNU General
+ Public License can be found in /usr/share/common-licenses/GPL'.
diff -Nru yaret-2.1.0/debian/rules yaret-2.1.0/debian/rules
--- yaret-2.1.0/debian/rules2023-10-22 23:57:50.0 +0200
+++ yaret-2.1.0/debian/rules2023-10-22 23:51:06.0 +0200
@@ -1,7 +1,6 @@
 #!/usr/bin/make -f
 
 include /usr/share/cdbs/1/rules/debhelper.mk
-include /usr/share/cdbs/1/rules/patchsys-quilt.mk
 
 install/yaret::
install -m 755 yaret debian/yaret/usr/bin/yaret
diff -Nru yaret-2.1.0/debian/source/format yaret-2.1.0/debian/source/format
--- yaret-2.1.0/debian/source/format1970-01-01 01:00:00.0 +0100
+++ yaret-2.1.0/debian/source/format2023-10-22 23:51:06.0 +0200
@@ -0,0 +1 @@
+3.0 (quilt)

Bug#1053857: cups: CVE-2023-32360 instructions in NEWS have a typo and are unclear

[Brendon Higgins]

On Thu, 12 Oct 2023 14:22:27 -0400 Jonathan Kamens  wrote:
> In addition, after reading the NEWS entry and reviewing the contents
> of my cupsd.conf file, I'm left completely clueless about whether I
> actually need to change anything, or if doing so will break cups.

I'm in exactly the same boat. I've found some useful additional information in 
bug #1052419, and especially Andres Salomon's message gives an actionable 
procedure to try. That bug was closed with an update to that NEWS message, 
although I still find that as written it assumes the user already has a grasp 
of the cupsd.conf file format and content, despite that they may never have 
touched that file and have no idea what they are being asked to do.

Best,
Brendon

Bug#900928: Dependency update

[Matthias Geiger]

While the ruma-stack is still a lot of crates to go through NEW, all are 
prepared. Meanwhile I uploaded rust-libshumate and rust-libadwaita to 
unstable.


I will upload the rest of the ruma crates once the one in NEW has been 
accepted.


--
Matthias Geiger 
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1054326: [Debian-ha-maintainers] Bug#1054326: Can't start golbal heartbeat when drbd device is on top LVM device

[Valentin Vidic]

On Sun, Oct 22, 2023 at 11:38:56PM +0200, Daniel Smolik wrote:
> But when use local heartbeat mode I  can  mount ocfs but not work in cluster
> mode. I mean that without global heartbeat you didn't have shared storage.

If I understand correctly with local heartbeat there is one heartbeat
running per ocfs2 mount and this should still allow cluster storage
to work.

Global heartbeat only optimizes this to run one or more heartbeat
devices for all ocfs2 mounts, so it should not be a strong requirement
for running a shared cluster storage.

-- 
Valentin

Bug#1017991: zmakebas: wrong compilation of BASIC program

[Bastian Germann]

I am uploading a NMU in order to fix this.
The debdiff is attached.diff -Nru zmakebas-1.2/bugs12.bas zmakebas-1.2b/bugs12.bas
--- zmakebas-1.2/bugs12.bas 1970-01-01 01:00:00.0 +0100
+++ zmakebas-1.2b/bugs12.bas2021-12-21 23:16:20.0 +0100
@@ -0,0 +1,24 @@
+# Tests for various version 1.2/1.2a bugs since fixed.
+# Does DEF FN, VAL$, and line-continuation at EOF.
+#
+# (See e.g. https://bugs.launchpad.net/ubuntu/+source/zmakebas/+bug/1908289
+# for more on 1.2's DEF FN bug.)
+#
+# The last line intentionally ends with a backslash, it's one of the
+# bug tests. If that hangs it, remove to check the others. If you do
+# that then try the output from 1.2 (not 1.2a), RUN will give "Q
+# Parameter error", as will GO TO 50 and GO TO 60. GO TO 70 will give
+# "C Nonsense in BASIC".
+#
+# 1.2a will give multiple question marks from line 90's LIST.
+
+10 def fn a(x)=x*x
+20 def fn b(x,y)=x*y
+30 def fn a$(x$)=x$+x$
+40 print fn a(2);" should be 4"
+50 print fn b(2,3);" should be 6"
+60 print fn a$("foo");" should be foofoo"
+70 print val$ """foo""+""bar""";" should be foobar"
+80 print '"Should LIST 100 with no ?:"''
+90 list 100
+100 def fn c()=(0)\
diff -Nru zmakebas-1.2/ChangeLog zmakebas-1.2b/ChangeLog
--- zmakebas-1.2/ChangeLog  2004-07-23 14:13:43.0 +0200
+++ zmakebas-1.2b/ChangeLog 2021-12-21 23:19:15.0 +0100
@@ -1,3 +1,61 @@
+2021-12-21  Russell Marks  
+
+   * Version 1.2b.
+
+   * bugs12.bas: fixed incorrect comment about LIST result, it was
+   only version 1.2a that had the relevant issue.
+
+2021-12-19  Russell Marks  
+
+   * README: slight update for new version.
+
+   * zmakebas.1: version bump.
+
+   * bugs12.bas: updated to add a test of sorts for the latest DEF FN
+   bugfix.
+
+   * zmakebas.c: fix for failing to spot the end of DEF FN
+   parameters. Thanks to Chris Born for reporting this bug.
+
+2021-07-04  Russell Marks  
+
+   * Version 1.2a.
+
+   * zmakebas.c: fixed possible buffer overruns. The remaining uses
+   of strcpy look reasonable. There is one use of sprintf I'd prefer
+   to replace with snprintf, but for some platforms it might be
+   unhelpful to require that. It's only used to get a known-4-digit
+   line number, so realistically it should be fine.
+
+2021-07-03  Russell Marks  
+
+   * README: small tweaks, and noting that other versions are around.
+
+   * Makefile: updated to avoid warnings on more recent gcc, and use
+   a more usual man page location and file permissions.
+
+   * zmakebas.1: minor tweaks to update it, and made option listing
+   more consistent.
+
+   * bugs12.bas: tests for various bugs in 1.2, which are now fixed.
+
+   * Fixed line-continuation bug, it got confused if it hit EOF in
+   certain circumstances and could loop indefinitely.
+
+   * Made input buffer sizes capable of handling Basic lines larger
+   than a 48k Spectrum can load. So if you want to embed substantial
+   binary data like machine code in a REM statement you should now be
+   able to. Thanks to Paul Humphreys for his version that suggested
+   this would be useful, though I went a bit bigger. :-)
+
+   * Included DEF FN fix based on Antonio Villena's version. I
+   altered it slightly to avoid the sequence-point issue.
+
+2021-06-27  Russell Marks  
+
+   * Fixed non-parsing of VAL$. Thanks to Andy J for pointing this
+   out.
+
 2004-07-23  Russell Marks  
 
* Version 1.2.
diff -Nru zmakebas-1.2/debian/changelog zmakebas-1.2b/debian/changelog
--- zmakebas-1.2/debian/changelog   2023-10-22 23:37:41.0 +0200
+++ zmakebas-1.2b/debian/changelog  2023-10-22 23:29:09.0 +0200
@@ -1,3 +1,12 @@
+zmakebas (1.2b-0.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update to new upstream version. (Closes: #1017991)
+  * Convert to source format 3.0. (Closes: #1007306)
+  * Use Priority: optional over extra.
+
+ -- Bastian Germann   Sun, 22 Oct 2023 23:29:09 +0200
+
 zmakebas (1.2-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru zmakebas-1.2/debian/control zmakebas-1.2b/debian/control
--- zmakebas-1.2/debian/control 2023-10-22 23:37:41.0 +0200
+++ zmakebas-1.2b/debian/control2023-10-22 23:29:09.0 +0200
@@ -1,7 +1,7 @@
 Source: zmakebas
 Maintainer: Krystian Wlosek 
 Section: otherosfs
-Priority: extra
+Priority: optional
 Standards-Version: 3.7.2
 Build-Depends: debhelper (>= 8)
 
diff -Nru zmakebas-1.2/debian/copyright zmakebas-1.2b/debian/copyright
--- zmakebas-1.2/debian/copyright   2023-10-22 23:37:41.0 +0200
+++ zmakebas-1.2b/debian/copyright  2023-10-22 23:29:09.0 +0200
@@ -2,7 +2,7 @@
 into ZX Spectrum Basic programs.  It was Debianised by
 Krystian Wlosek , and uploaded by Piotr
 Roszatycki , using files obtained from
-ftp://ftp.ibiblio.org/pub/Linux/system/emulators/zx/zmakebas-1.1.tar.gz>.

Bug#1054326: [Debian-ha-maintainers] Bug#1054326: Can't start golbal heartbeat when drbd device is on top LVM device

[Daniel Smolik]

But when use local heartbeat mode I  can  mount ocfs but not work in 
cluster mode. I mean that without global heartbeat you didn't have 
shared storage.


Regards
                Dan




Dne 22. 10. 23 v 13:37 Valentin Vidic napsal(a):

On Sun, Oct 22, 2023 at 12:11:19PM +0200, Daniel Smolik wrote:

Yes no problem. There it is.

Thanks. My best guess is that the problem happens because the region
UUID is visible on both drbd and the lower device, so the global
heartbeat might work if drbd device is selected first (for example in
the case of md).

Since I don't know if it possible to specify the device directly, your
best bet now is probably to use the local heartbeat mode (that should
work without the regions being specified).

Bug#1041327: RFS: libtypec/0.3-1 [RFP] -- Development files for an interface for USB-C port management

[Bálint Réczey]

Hi Colin,

I've checked the second upload at [1].
As you can see in the Lintian warnings there is a .git directory which
is not ideal for a source package.
I suggest using the most widely used git-buildpackage based workflow
where the gbp command takes care of exporting the source package
without the .git dir from the packaging repository.
I'd be happy to set up a packaging repo for you at
https://salsa.debian.org/debian/libtypec and add you as a maintainer
as described in [2]

Other observations regarding the packaging:

* There is debian/install and also there are binary package specific
*.install files which is slightly confusing.
   I suggest dropping debian/install.
* In the debian/*.install files you need to specify only the target
dir, not the target file.
  In libtypec-dev
/usr/share/pkgconfig/${DEB_HOST_MULTIARCH}/libtypec.pc/libtypec.pc
gets shipped, which is not desired.
* libtypec.h seems to be the same on all architectures. Does it have
to be shipped in a multiarch include location?
* Binary packages in debian/control are not marked as Multi-Arch: same
* Please target experimental. The package needs to pass NEW and to
migrate to testing it will need a new source-only upload anyway.

Cheers,
Balint

[1] https://mentors.debian.net/package/libtypec/
[2] 
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group

On Thu, 3 Aug 2023 17:00:58 +0100 "Colin King (gmail)"
 wrote:
> Hi,
>
> I've uploaded a fixed package that addresses these issues.
>
> Colin
>
> On 18/07/2023 08:50, Adam Borowski wrote:
> > On Mon, Jul 17, 2023 at 03:29:13PM +0100, Colin King (gmail) wrote:
> >>   * Package name : libtypec
> >> Version  : 0.3-1
> >>   * URL  : https://github.com/Rajaram-Regupathy/libtypec
> >
> >>libtypec1 - generic interface for efficient USB-C port management
> >>libtypec-dev - Development files for an interface for USB-C port 
> >> management
> >
> >>   libtypec (0.3-1) unstable; urgency=low
> >>   .
> >> * Initial release (Closes: #1023477)
> >> * Add patch 0001-fix-libtypec-so-version.patch to fix .so name version
> >
> > Hi!
> > Before doing manual review, let's start with lintian:
> >
> > E: libtypec1: pkg-config-multi-arch-wrong-dir full text contains 
> > architecture specific dir x86_64-linux-gnu [usr/share/pkgconfig/libtypec.pc]
> > W: libtypec-dev: empty-binary-package
> > W: libtypec1: lacks-unversioned-link-to-shared-library example: 
> > usr/lib/x86_64-linux-gnu/libtypec.so 
> > [usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0]
> > W: libtypec1: link-to-shared-library-in-wrong-package 
> > usr/lib/x86_64-linux-gnu/libtypec.so.0.3.0 
> > [usr/lib/x86_64-linux-gnu/libtypec.so]
> >
> >
> > Meow!
>
>
>

Bug#967795: view3dscene: depends on deprecated GTK 2

[Bastian Germann]

Meanwhile, you can drop libgtkglext1-dev, which is not used, and unblock 
#967491.

Bug#979833: libtiff4: Document that Debian build is GPL due to dependency on libjbig0 (?)

[Bastian Germann]

We do not need to add additional disclaimers or notes.
However, there might be problematic packages in Debian:
If a reverse dependency has a GPL-2+-incompatible license
it is affected by libtiff linking with libjbig.
In case there is such a package, please list it here.

Bug#1052172: gnome-terminal: crash during scroll-up

[Samuel Thibault]

Hello,

It has been a month now, can we perhaps reconsider adding it (attached)
to debian for wider testing?

Samuel

Patrice Duroux, le sam. 23 sept. 2023 19:44:47 +0200, a ecrit:
> Up to now, it is stable!
> 
> Le sam. 23 sept. 2023 à 17:43, Samuel Thibault  a écrit 
> :
> >
> > Patrice Duroux, le sam. 23 sept. 2023 16:53:36 +0200, a ecrit:
> > > Much more stable and harder to crash but still got one doing in this
> > > case some ample resizes of the terminal window.
> >
> > Ok, good!
> >
> > Could you try version 0.73.99-1+fix3 from
> >
> > https://people.debian.org/~sthibault/tmp/bookworm-tmp/
> >
> > Thanks,
> > Samuel
commit be524d2a35a3bd5a7dfd6094b8cb49834c5702b4
Author: Samuel Thibault 
Date:   Thu Sep 21 02:09:00 2023 +0200

widget: a11y: Add missing text changes on scrolling with modifications

When vte_terminal_accessible_text_scrolled gets called, the terminal
might have not only scrolled, but also changed.  We thus have to check
whether the remaining text really is exactly the same as expected.

We here support simple diff for the common case: an ample head and/or tail
content is the same. This allows to emit only the modification, which is
usually relatively small.

Fixes: https://gitlab.gnome.org/GNOME/vte/issues/88

diff --git a/src/vteaccess.cc b/src/vteaccess.cc
index 00bb1cd3..175c73fc 100644
--- a/src/vteaccess.cc
+++ b/src/vteaccess.cc
@@ -493,6 +493,44 @@ 
_vte_terminal_accessible_text_modified(VteTerminalAccessible* accessible)
 g_array_free(old_characters, TRUE);
 }
 
+/* Compute a simple diff between the `before` string (before_len bytes) and the
+   `after` string (after_len bytes). We here only check for common head and
+   tail.
+
+   If the strings are equal, this returns FALSE.
+
+   If the strings differ, this returns TRUE, and *head_len is set to the number
+   of bytes that are identical at the beginning of `before` and `after`, and
+   *tail_len is set to the number of bytes that are identical at the end of
+   `before` and `after`. */
+static gboolean
+check_diff(const gchar *before, guint before_len,
+  const gchar *after, guint after_len,
+  guint *head_len, guint *tail_len)
+{
+   guint i;
+
+   for (i = 0; i < before_len && i < after_len; i++)
+   if (before[i] != after[i])
+   break;
+
+   if (i == before_len && i == after_len)
+   /* They are identical. */
+   return FALSE;
+
+   /* They started diverging at i. */
+   *head_len = i;
+
+   for (i = 1; i <= before_len - *head_len && i <= after_len - *head_len; 
i++)
+   if (before[before_len - i] != after[after_len - i])
+   break;
+
+   /* They finished diverging here. */
+   *tail_len = i - 1;
+
+   return TRUE;
+}
+
 void
 _vte_terminal_accessible_text_scrolled(VteTerminalAccessible* accessible,
long howmuch)
@@ -500,7 +538,7 @@ 
_vte_terminal_accessible_text_scrolled(VteTerminalAccessible* accessible,
VteTerminalAccessiblePrivate *priv = (VteTerminalAccessiblePrivate 
*)_vte_terminal_accessible_get_instance_private(accessible);
struct _VteCharAttributes attr;
long delta, row_count;
-   guint i, len;
+   guint drop, old_len, new_len, old_common, new_common;
 
 /* TODOegmont: Fix this for smooth scrolling */
 /* g_assert(howmuch != 0); */
@@ -537,6 +575,7 @@ 
_vte_terminal_accessible_text_scrolled(VteTerminalAccessible* accessible,
 
vte_terminal_accessible_maybe_emit_text_caret_moved(accessible);
return;
}
+
/* Find the start point. */
delta = 0;
if (priv->snapshot_attributes != NULL) {
@@ -550,91 +589,196 @@ 
_vte_terminal_accessible_text_scrolled(VteTerminalAccessible* accessible,
/* We scrolled up, so text was added at the top and removed
 * from the bottom. */
if ((howmuch < 0) && (howmuch > -row_count)) {
-   gboolean inserted = FALSE;
howmuch = -howmuch;
if (priv->snapshot_attributes != NULL &&
priv->snapshot_text != NULL) {
+   old_len = priv->snapshot_attributes->len;
+
/* Find the first byte that scrolled off. */
-   for (i = 0; i < priv->snapshot_attributes->len; i++) {
+   for (old_common = 0; old_common < old_len; 
old_common++) {
attr = g_array_index(priv->snapshot_attributes,
struct _VteCharAttributes,
-   i);
+   old_common);
if (attr.row >= delta + row_count - howmuch) {
break;
}
}
-   

Bug#1017466: German translation: “eine Verknüpfung”, “eine Datei”

[Santiago Vila]

El 16/8/22 a las 16:33, Peter Mueller escribió:

Package: diffutils
Version: 1:3.7-5

Reproduce:

$ cd /tmp
$ touch f1
$ ln -s f1 f2
$ diff --no-dereference f1 f2

Datei f1 ist ein normale leere Datei, während Datei f2 ein symbolische 
Verknüpfung ist.


Two “e”s are missing. The correct German phrase would be “Datei f1 ist eine 
normale leere Datei, während Datei f2 eine symbolische Verknüpfung ist.”


Hello. I'm closing this bug because according to the rules of Translation 
Project,
programmers (and I include myself here as a Debian maintainer) should only 
accept
translations from the Translation Project.

There is also a message in diff --help saying how to report translation bugs:

$ diff --help | grep translationproject
Übersetzungsfehler an .


However, I'm including Friedrich Beckmann (leader for the "de" team)
and Mario Blättermann (last translator) in the CC, so that they are aware
of this issue that you reported and it's not lost.


While we are at it, a quick look at the latest "de.po" file says
this is the relevant string that would have to be changed:

#: src/diff.c:1411 src/diff.c:1461
#, c-format
msgid "File %s is a %s while file %s is a %s\n"
msgstr "Datei %s ist ein %s, während Datei %s ein %s ist.\n"


I see a potential problem here, because the %s is
to be replaced by different types of "files".

If all of them have the same gender, then the proposed fix
would make sense.

However, if not all of them have the same gender, then this
would be an internationalization problem, not a localization
problem, and in such case you should probably report it as a
bug to bug-diffut...@gnu.org.

Thanks.

Bug#1054373: Regression in monolithic EFI normal disk boot image with --removable and --bootloader-id

[Pascal Hambourg]

MR: https://salsa.debian.org/grub-team/grub/-/merge_requests/44

Bug#1054297: exabgp can not bind to IP:179

[Lucas da Vila]

Sorry, the lines added in /lib/systemd/system/exabgp.service were

```
CapabilityBoundingSet=CAP_NET_BIND_SERVICE
AmbientCapabilities=CAP_NET_BIND_SERVICE
```

On 21/10/2023 00:07, lucas wrote:

Package: exabgp
Version: 4.2.21-1.1
Severity: normal
X-Debbugs-Cc: ldav...@syt.net

Dear Maintainer,

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

* What led up to the situation?
  I was trying to establish a BGP sessionbetween two exabgp services,
  sniffing the interface I've noticed that exabgp was sending a RST after 
the
  TCP SYN, leading me to run `ss -naltp` and not seeing exabgp listening on
  port 179.  After changing the exabgp.tcp.bind from '' to '0.0.0.0' in
  exabgp.env, exabgp was not able to start informing that can not bind to
  0.0.0.0:179 because it was not running as root.

* What exactly did you do (or not do) that was effective (or
  ineffective)?
  I was able to let exabgp service to bind on port 179 adding the following
  lines to /lib/systemd/system/exabgp.service
  ```
  CapabilityBoundingSet=CAP_NET_BIND_SERVICE
  CapabilityBoundingSet=CAP_NET_BIND_SERVICE
  ```
  
* What was the outcome of this action?

  Exabgp was able to start succesfully binding to 0.0.0.0:179


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

Kernel: Linux 6.1.21-v8+ (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CRAP
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)

Versions of packages exabgp depends on:
ii  adduser3.137
ii  debconf1.5.82
ii  dpkg   1.22.0
ii  init-system-helpers1.65.2
ii  lsb-base   11.6
ii  python3-exabgp 4.2.21-1.1
ii  python3-pkg-resources  68.1.2-2
ii  sysvinit-utils [lsb-base]  3.08-3
ii  ucf3.0043+nmu1

exabgp recommends no packages.

exabgp suggests no packages.

-- no debconf information


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1038224: please drop transitional package bsdmainutils from src:bsdmainutils

[Bastian Germann]

This can be done now because all reverse dependencies have moved away from it
or only have it as an alternative.

Bug#1054374: dispcalgui: Drop transitional package

[Bastian Germann]

Package: dispcalgui

Please drop the transitional package which has been in several releases.

Bug#1006477: Broken firmware

[Chris Bainbridge]

> So, my conclusion is that there is something specific to the debian kernels 
> that is breaking this USB ethernet card.

The IOMMU error is most likely caused by a bug in the VL805 firmware.
It happens with the Debian kernel (and not mainline) as Debian patches
the kernel to enable IOMMU by default. The updated VL805 firmware
apparently fixes the bug, it can be installed using the VIA Windows
tool (this did not work for me), or you can just turn off IOMMU.

Bug#994540: Go ahead with imagemagick/experimental ?

[Bastien Roucariès]

Le dimanche 22 octobre 2023, 15:03:50 UTC Sebastian Ramacher a écrit :
> Control: tags -1 confirmed
> 
> On 2023-10-22 14:51:42 +, Bastien Roucariès wrote:
> > Le dimanche 22 octobre 2023, 14:08:20 UTC Sebastian Ramacher a écrit :
> > > Hi Bastien
> > > 
> > > On 2023-10-21 20:10:47 +, Bastien Roucariès wrote:
> > > > Can I go ahead with imagemagick experimental ?
> > > 
> > > As a year has past since the last mail to the transition bug report: did
> > > any new build failures in reverse dependencies appear? What's the
> > > status?
> > 
> > Reverse build are ok (just tested in pbuilder), so for me it is a green 
> > light
> 
> Please go ahead.
Done
> 
> Cheers
> 



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

Bug#1054373: Regression in monolithic EFI normal disk boot image with --removable and --bootloader-id

[Pascal Hambourg]

Package: src:grub2
Version: 2.06-14

Commit 5171e04d ("Bundle unicode.pf2 in a squashfs memdisk attached to 
the signed EFI binary") removed (memdisk)/grub.cfg from monolithic EFI 
normal disk boot images.


So now the normal disk boot image looks for grub.cfg in /EFI/debian only 
and not in $cmdpath any more. This breaks boot from the removable media 
path when installed with --removable, and normal boot when installed 
with --bootloader-id or $GRUB_DISTRIBUTOR != "debian".


Expected behaviour: GRUB loads $cmdpath/grub.cfg and displays the menu.
Observed behaviour: GRUB does not load $cmdpath/grub.cfg and enters 
command-line mode instead of displaying the menu.


Proposed fix: add a new grub.cfg into normal disk boot images instead of 
re-adding the previously used one which seems to be intended for CD boot 
images.


Option A: the new embedded grub.cfg looks for grub.cfg in $cmdpath first 
then in $prefix as fallback.


Option B: the new embedded grub.cfg looks for grub.cfg in $cmdpath only.
Caveats:
- For boot from the removable media path to keep working when installed 
with --force-extra-removable, this change requires to patch grub-install 
to install grub.cfg into the removable media path too.
- For boot from live and installation ISO-hybrid images to keep working, 
this change requires to patch the image builders to install grub.cfg 
into the removable media path.


Note: option A may also require grub-install --force-extra-removable to 
install grub.cfg in /EFI/Boot in order to boot properly from the 
removable media path when combined with --no-nvram and --bootloader-id 
or $GRUB_DISTRIBUTOR != "debian", which was already broken.

Bug#1054372: (no subject)

[Kacper Misiaszek]

Package: python3-django-macaddress
Version: 1.5.0-3
Severity: grave
X-Debbugs-Cc: kkmisias...@gmail.com

Dear Maintainer,

version of the package is outdated and does not support current
version of python3-django in bookworm. When you try to import from macaddress, 
it
throws and ImportError caused by:
from django.forms.fields import EMPTY_VALUES.

Updating the version of this package should fix this issue.

-- System Information:
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.7-arch1-1 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)

Bug#1054371: RFS: sphinx-wagtail-theme/6.1.1-1 [ITP] -- Sphinx theme for Wagtail

[Danial Behzadi]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "sphinx-wagtail-theme":

* Package name : sphinx-wagtail-theme
  Version  : 6.1.1-1
  Upstream contact : https://github.com/wagtail/sphinx-wagtail-theme
* URL  : https://github.com/wagtail/sphinx-wagtail-theme
* License  : MIT
* Vcs  :
https://salsa.debian.org/python-team/packages/sphinx-wagtail-theme
  Section  : python

The source builds the following binary packages:

 python3-sphinx-wagtail-theme - Sphinx theme for Wagtail (Python 3)
 python3-sphinx-wagtail-theme-doc - Sphinx theme for Wagtail (Document)

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

 https://mentors.debian.net/package/sphinx-wagtail-theme/

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

 dget -x
https://mentors.debian.net/debian/pool/main/s/sphinx-wagtail-theme/sphinx-wagtail-theme_6.1.1-1.dsc

Changes for the initial release:

sphinx-wagtail-theme (6.1.1-1) unstable; urgency=medium
.
  * Initial release. (Closes: #1054350)

Regards,
-- 
  Danial Behzadi

Bug#951166: RE: ITP Shortwave

[Matthias Geiger]

On Sun, 1 Oct 2023 16:52:21 +0200 Matthias Geiger  
wrote:

>
> I updated gtk-rs to the latest version. libadwaita-rs landed in
> unstable; I prepared libshumate for upload. mpris-player was updated
> upstream; so I'll look into packaging it and see if Shortwave builds
>
> against it.
>
libshumate was just accepted into experimental. I'll tackle mpris-server 
next as upstream is considering switching to it.


--
Matthias Geiger 
Debian Maintainer
"Freiheit ist immer Freiheit des anders Denkenden" -- Rosa Luxemburg



OpenPGP_0x18BD106B3B6C5475.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#790955: 790955 - localectl list-keymaps

[Martin Bruset Solberg]

Yes, hello, hello. It is now 2023...

Bug#1054370: RM: haskell-monadcryptorandom -- ROM; obsolete

[Ilias Tsitsimpis]

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

Please remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

-- 
Ilias

Bug#1054334: monero: segfault/illegal operation once mining is enabled

[Jeffrey Cliff]

ok this is odd, apparently i *did* have the dbgsym package installed

root@wicksell:~# apt-cache policy monero-dbgsym
monero-dbgsym:
  Installed: 0.18.3.1+~0+20200826-1
  Candidate: 0.18.3.1+~0+20200826-1
  Version table:
 *** 0.18.3.1+~0+20200826-1 500
500 http://deb.debian.org/debian-debug sid-debug/main amd64 Packages
500 http://deb.debian.org/debian-debug testing-debug/main amd64 Packages
100 /var/lib/dpkg/status
 0.18.0.0+~0+20200826-1+b1 500
500 http://deb.debian.org/debian-debug bookworm-debug/main
amd64 Packages
 0.17.2.0+~0+20200826-1 500
500 http://deb.debian.org/debian-debug bullseye-debug/main
amd64 Packages
root@wicksell:~# apt-cache policy monero
monero:
  Installed: 0.18.3.1+~0+20200826-1
  Candidate: 0.18.3.1+~0+20200826-1
  Version table:
 *** 0.18.3.1+~0+20200826-1 500
500 https://mishka.snork.ca/devuan/merged unstable/main amd64 Packages
500 https://ftp.fau.de/devuan/merged unstable/main amd64 Packages
100 /var/lib/dpkg/status
root@wicksell:~# which monero
root@wicksell:~# which monerod
/usr/bin/monerod
root@wicksell:~# dpkg -S /usr/bin/monerod
monero: /usr/bin/monerod


On Sun, Oct 22, 2023 at 1:51 AM Bastian Germann  wrote:
>
> Am 22.10.23 um 08:32 schrieb Jeffrey Cliff:
> > captured in gdb doesn't have debugging symbols so wasn't super useful:
>
> Have you tried installing monero-dbgsym from the debian-debug repository?



-- 

End the campaign to Cancel Richard Stallman - go to stallmansupport.org !

Bug#1054369: RM: haskell-hashable-time -- ROM; obsolete

[Ilias Tsitsimpis]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: haskell-hashable-t...@packages.debian.org
Control: affects -1 + src:haskell-hashable-time

Please remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It's not part of the latest Stackage LTS
  * Deprecated in favor of haskell-time-compat

-- 
Ilias

Bug#1012016: possible solution for libapache-poi-java needs updates for newer xmlbeans

[debian]

Hi all,

I am a Java developer and I faced the same problem after upgrading 
debian from bullseye to bookworm.


I compared the file /usr/share/java/poi-ooxml-schemas-4.0.1.jar between 
bullseye, bookworm and those from the maven central repo. The version of 
bookworm contains a very reduced amount of files.


So I tested the reproducer problem.java from Erik with the corresponding 
jar from bullseye and the test was OK.


I assume, that there has been a problem in creating the 
poi-ooxml-schemas-4.0.1.jar for bookworm. Could a maintainer please fix 
this file?


Thank you and best regards
Florian Paul

Bug#967569: libcanberra: depends on deprecated GTK 2

[Jeremy Bícha]

On Sun, Oct 22, 2023 at 12:57 PM Bastian Germann  wrote:
> I am uploading a NMU to DELAYED/10 in order to fix this.
> The debdiff is attached.

Feel free to upload now without delay.

Thank you,
Jeremy Bícha

Bug#866075: [dhtnode] ship http_server.py and a systemd associated service

[Amin Bandali]

Control: tags -1 pending
X-Debbugs-CC: Tobias Frost 

Hello,

Apologies this took *a while* to get to, but it's [nearly] here,
at last:

I've added an opendht-tools package as part of the upcoming 3.0.0-4
upload, which among other tools packages python/tools/http_server.py
as /usr/bin/dhtnode-http with a corresponding dhtnode-http.service
and configuration file at /etc/default/dhtnode-http.  Hope this helps.

Tobi, would you please sponsor opendht 3.0.0-4 for me?  Since it has
a new binary package, I believe it will have to pass through NEW.

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

Thanks,
-a

Bug#1054368: debhelper: Does not support double build (possible violation of Policy 4.9)

[Helge Kreutzmann]

Package: debhelper
Version: 13.11.4
Severity: minor
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Some time ago my package linuxinfo aquired a bug (#1047898) whereas
dpkg-buildpackage ; dpkg-buildpackage -S 
does not work. And if fact, it does not.

The reporter informed me that this is a potential violation of Debian
Policy section 4.9 (clean target), but that this was under discussion
at the time of the reporting. 

I first checked (my) upstream build system. Except for one stamp file
(which is *much* less than done by debhelper) the build is idempotent,
i.e.:

./configure && make && make clean

returns the sources into the state as shipped.

In the past I had an explicit debian/rules, but to ensure compliance
with the ever evolving Debian Policy I made it on purpose very simple:

include /usr/share/dpkg/architecture.mk

ifeq ($(DEB_HOST_ARCH),amd64)
confflags += --with-pcre
else ifeq ($(DEB_HOST_ARCH),i386)
confflags += --with-pcre
else ifeq ($(DEB_HOST_ARCH),x32)
confflags += --with-pcre
endif

%:
dh $@

override_dh_auto_configure:
dh_auto_configure -- $(confflags)

As you can see, I only add (architecture dependend) configuration flags 
for linking with pcre.

dh seems to delete quite a few files shipped in the package.

For me, this is a clear bug in dh, as linuxinfo just uses it plain and
there is no "manipulation" of build files happening (on purpose).

I checked dh_clean(1) and dh(1), but could not find any mention of how 
to modify this (which I would not have expected anyhow).

If the severity of 1047898 is changed, then I will change this one (as
it is the root cause). In linuxinfo I probably could work around this,
by backing up all affected files before clean and restoring them after
clean (using an override). But this is a band aid, not a solution.

-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1051803: ITS: freespace2

[Sébastien Noel]

Ping ?


Le mercredi 20 septembre 2023 à 10:04 +0200, Sébastien Noel a écrit :
> Hi Dmitry !
> 
> Le 2023-09-19 05:06, Dmitry Smirnov a écrit :
> > I still have interest for this package but I'm struggling with
> > limited
> > capacity and more pressing priorities. I'd appreciate some help and
> > you
> > are welcome to co-maintain the package.
> > 
> > Thank you for your attention and care.
> 
> Glad to read that you are still interested to maintain freespace2 :-)
> And I'm more than willing to co-maintain the package with you!
> As mentioned in my email, I have pushed changes to salsa [1]
> and have uploaded a "ready to use" package on m.d.n [2] ;
> I would really appreciate if you could find time to review those
> changes
> and get back to me :-)
> 
> I'm going to close this ITS
> 
> Best regards,
> Sébastien
> 
> [1] https://salsa.debian.org/onlyjob/freespace2/-/merge_requests/1
> [2] https://mentors.debian.net/package/freespace2/

Bug#967569: libcanberra: depends on deprecated GTK 2

[Bastian Germann]

I am uploading a NMU to DELAYED/10 in order to fix this.
The debdiff is attached.diff -Nru libcanberra-0.30/debian/changelog libcanberra-0.30/debian/changelog
--- libcanberra-0.30/debian/changelog   2022-04-08 22:10:09.0 +0200
+++ libcanberra-0.30/debian/changelog   2023-10-22 18:49:02.0 +0200
@@ -1,3 +1,10 @@
+libcanberra (0.30-10.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Drop gtk2 support (Closes: #967569)
+
+ -- Bastian Germann   Sun, 22 Oct 2023 18:49:02 +0200
+
 libcanberra (0.30-10) unstable; urgency=medium
 
   * debian/patches/gtk_dont_assume_x11.patch: Avoid more X11-only codepaths
diff -Nru libcanberra-0.30/debian/control libcanberra-0.30/debian/control
--- libcanberra-0.30/debian/control 2022-04-08 22:10:09.0 +0200
+++ libcanberra-0.30/debian/control 2023-10-22 18:49:02.0 +0200
@@ -6,14 +6,13 @@
 Section: libs
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

-Uploaders: Josselin Mouette , Laurent Bigonville 
, Michael Biebl , Sjoerd Simons 

+Uploaders: Josselin Mouette , Laurent Bigonville 
, Marco Trevisan (Treviño) , Michael Biebl 
, Sjoerd Simons 
 Build-Depends: debhelper-compat (= 13),
gnome-pkg-tools,
libltdl-dev | libltdl7-dev (>= 2.2.6),
libasound2-dev [linux-any],
libvorbis-dev,
libgtk-3-dev (>= 3.0.0),
-   libgtk2.0-dev (>= 2.22),
libtdb-dev (>> 1.1) [!hurd-any],
gtk-doc-tools,
libpulse-dev (>= 0.9.11),
@@ -28,7 +27,7 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}, sound-theme-freedesktop
-Suggests: libcanberra-gtk0, libcanberra-pulse
+Suggests: libcanberra-pulse
 Description: simple abstract interface for playing event sounds
  libcanberra defines a simple abstract interface for playing event
  sounds.
@@ -77,19 +76,6 @@
  .
  This package contains the GStreamer backend for libcanberra.
 
-Package: libcanberra-gtk0
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: libcanberra-gtk-module
-Description: GTK+ helper for playing widget event sounds with libcanberra
- libcanberra-gtk provides a few functions that simplify libcanberra
- usage from GTK+.
- .
- Contextual information is needed to play event sound. This library
- can help to compile directly event sounds property lists based on
- active GtkWidget objects or GdkEvent events.
-
 Package: libcanberra-gtk-common-dev
 Section: libdevel
 Architecture: all
@@ -108,35 +94,6 @@
  This package contains common headers for developing
  applications using libcanberra-gtk and libcanberra-gtk3
 
-Package: libcanberra-gtk-dev
-Section: libdevel
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends},
-   ${misc:Depends},
-   libcanberra-gtk0 (= ${binary:Version}),
-   libcanberra-dev (= ${binary:Version}),
-   libgtk2.0-dev (>= 2.20),
-   libcanberra-gtk-common-dev
-Description: simple interface for playing event sounds (GTK+ 2 development 
files)
- libcanberra-gtk provides a few functions that simplify
- libcanberra usage from GTK+.
- .
- Contextual information is needed to play event sound. This library
- can help to compile directly event sounds property lists based on
- active GtkWidget objects or GdkEvent events.
- .
- This package contains headers and libraries for developing
- applications that play event sounds with libcanberra-gtk.
-
-Package: libcanberra-gtk-module
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}, libgtk2.0-0 (>= 2.24.5-4)
-Description: translates GTK+ widgets signals to event sounds
- A GtkModule which will automatically hook into all kinds of events
- inside a GTK+ program and generate sound events from them.
-
 Package: libcanberra-gtk3-0
 Architecture: any
 Multi-Arch: same
diff -Nru libcanberra-0.30/debian/control.in libcanberra-0.30/debian/control.in
--- libcanberra-0.30/debian/control.in  2022-04-08 22:10:09.0 +0200
+++ libcanberra-0.30/debian/control.in  2023-10-22 18:48:50.0 +0200
@@ -9,7 +9,6 @@
libasound2-dev [linux-any],
libvorbis-dev,
libgtk-3-dev (>= 3.0.0),
-   libgtk2.0-dev (>= 2.22),
libtdb-dev (>> 1.1) [!hurd-any],
gtk-doc-tools,
libpulse-dev (>= 0.9.11),
@@ -24,7 +23,7 @@
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}, sound-theme-freedesktop
-Suggests: libcanberra-gtk0, libcanberra-pulse
+Suggests: libcanberra-pulse
 Description: simple abstract interface for playing event sounds
  libcanberra defines a simple abstract interface for playing event
  sounds.
@@ -73,19 +72,6 @@
  .
  This package contains the GStreamer backend for libcanberra.
 
-Package: libcanberra-gtk0
-Architecture: any
-Multi-Arch: same
-Depends: ${shlibs:Depends}, ${misc:Depends}
-Recommends: libcanberra-gtk-module
-Description: GTK+ 

Bug#1054367: cjs: Move to mozjs115

[Bastian Germann]

Source: cjs
Severity: wishlist
Version: 5.8.0-3
Control: forwarded -1 https://github.com/linuxmint/cjs/issues/120

Hi,

Please consider moving to mozjs115, which does not build-depend on the obsolete 
autoconf2.13.
As cjs is mozjs102's only reverse dependency, it is one of the key packages to 
resolve this.
See also the discussion in #977321.

Bug#207095: closed by Thomas Lange (closing)

[Boyuan Yang]

在 2023-10-22星期日的 08:46 -0700，Dan Jacobson写道：
> OK, that's great. But nobody visiting the packages page knows about the 
> tracker page, so there ought to be a hyperlink added to it on the 
> packages page.

There is one, albeit deeply hidden in the sidebar called "Developer 
Information".
It does not mention "Tracker" or "PTS". It is not put together in the main body
like the link to the source package. That is one of the main reasons that I hate
the current layout of packages.debian.org.

Thanks,
Boyuan Yang


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

Bug#1024824: The software outputs: "No access to printer device file"

[Graham Inggs]

Control: severity -1 normal
Control: tags -1 + moreinfo

The severity of this bug keeps mtink out of testing, and needs more information.

Bug#1018196: Bug#1018197: Removal notice: obsolete

[Adrian Bunk]

Control: tags -1 - bookworm
Control: severity -1 serious

On Wed, Nov 23, 2022 at 11:04:09AM +0200, Ilias Tsitsimpis wrote:
> Control: severity -1 important
> 
> Downgrading this, since git-annex depends on it (see #1022681).

#1022681 has now been fixed.

> Ilias

cu
Adrian

Bug#1054366: RM: haskell-cipher-aes128 -- ROM; obsolete

[Ilias Tsitsimpis]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: haskell-cipher-aes...@packages.debian.org
Control: affects -1 + src:haskell-cipher-aes128

Please remove this package:

  * It has no rev dependencies, other than haskell-drbg which I have
requested to be removed
  * The current version FTBFS
  * Seems unmaintained; repo is archived
  * It's not part of the latest Stackage LTS

-- 
Ilias

Bug#1054365: RM: haskell-drbg -- ROM; obsolete

[Ilias Tsitsimpis]

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

Please remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; repo is archived
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

-- 
Ilias

Bug#207095: closed by Thomas Lange (closing)

[Dan Jacobson]

OK, that's great. But nobody visiting the packages page knows about the 
tracker page, so there ought to be a hyperlink added to it on the 
packages page.

Bug#1054364: FTBFS: test failure in t/Software-License.t

[gregor herrmann]

Source: libstring-license-perl
Version: 0.0.9-2
Severity: serious
Tags: ftbfs trixie sid
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As noted by ci.debian.net, libstring-license-perl's test suite
started to fail around a week ago:

https://ci.debian.net/packages/libs/libstring-license-perl/

 41s t/Software-License.t .. 
 41s # Seeded srand with seed '20231020' from local date.
 41s 1..29
 41s ok 1 - matches expected license for SPDX id AGPL-3.0
 41s ok 2 - matches expected license for SPDX id Apache-1.1
 41s ok 3 - matches expected license for SPDX id Apache-2.0
 41s ok 4 - matches expected license for SPDX id Artistic-1.0
 41s ok 5 - matches expected license for SPDX id Artistic-1.0-Perl OR 
GPL-1.0-or-later
 41s ok 6 - matches expected license for SPDX id Artistic-2.0
 41s ok 7 - matches expected license for SPDX id BSD
 41s ok 8 - matches expected license for SPDX id BSD-2-Clause-FreeBSD
 41s ok 9 - matches expected license for SPDX id CC0-1.0
 41s ok 10 - matches expected license for SPDX id EUPL-1.1
 41s ok 11 - matches expected license for SPDX id EUPL-1.2
 41s not ok 12 - matches expected license for SPDX id GFDL-1.2-or-later
 41s 
 41s # Failed test 'matches expected license for SPDX id GFDL-1.2-or-later'
 41s # at t/Software-License.t line 96.
 41s # +---++---+
 41s # | GOT   | OP | CHECK |
 41s # +---++---+
 41s # | GFDL-1.2-or-later | eq | GFDL-1.2-or-later and/or GFDL-1.3 |
 41s # +---++---+

The same failure happens during build, hence this FTBFS bug.


The issue might be related to the upload of libsoftware-license-perl_0.104004-1
on 15 October …


Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmU1Q15fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaZxQ//W2IU7ZT4fKopEH4ECzg2b0/pn5eDU8Ey0JFXH/BGPNxNNvC3tmUXVK2W
lUMqKUkjn0+0G1XpG1A4eB0G3aeZ16MJwUV3OYstZVv4UtmNY6KAyHbhakgFtx8r
UpW0Q0w6XUGegvZUv7q1u+MeEyWUv90Fmvqo4zrt9VwsvEQ9chSn2z28q2kupm0C
PoYjjIuzx+uESgQgytTXcCTY73dcCZmmdSQAZQzwAvXwIC/NKJyueIKZ+Dk8DyeI
9Oc6nnZHmwhkOQrdmbHQy+rRhobz0B10qrropkNkrgu0b0X+jM6aPtitk+ONWXGC
PUVSr+JkDFPCP09b3YAIdWlIdr6r8Rj30F6BY1mQlnjZmCTOKDLEpdYhxrROYEyc
hkDDTmIBItycWnPQ1+jDg11W2I3/wFRx1S6K0a+drN2dKWfyaoSYeHh9XRcM3FVb
nZ9FLUrKQWFBKsM9cyQx5M2EgluLNuJvksxHMPZ+18fCFKwPEYvHZqFOU5Yd0P7t
cRcUL5lOzvPDDAqcywr+mGX8PZTeBdPFEChDuKofvo4nhhwQiCh79E15LU1/RF21
gKzDTkufjnCz8CTxl4j2gt6/2ozaOERDHw/7koujjmVBnLLOM/o/33EB7EAq6u7X
GqoztMBvtSS4z0DbDd6FnYJ4aNh+t/Vlxex+NhE+gQx+79C+T54=
=omfM
-END PGP SIGNATURE-

Bug#1040445: udev creates wrong symlink from rule after upgrade to bookworm

[peter]

In Debian 11.
root@imager:~# cat /etc/deb*ver*
11.8

root@imager:~# head -n 13 /etc/udev/rules.d/10* | tail -n 2
KERNEL=="sd?3", SUBSYSTEM=="block", ATTR{size}=="60028928", \
  SYMLINK+="AY", OWNER="root", GROUP="root", MODE="700"

root@imager:~# ls -ld /dev/A*
lrwxrwxrwx 1 root root 4 Oct 22 07:00 /dev/AY -> sdb3

# That, ^, is the correct result.

In Debian 12.
root@imager:~# cat /etc/deb*ver*
12.2

root@imager:~# head -n 23 /etc/udev/rules.d/10* | tail -n 2
KERNEL=="sd?3", SUBSYSTEM=="block", ATTR{size}=="60028928", \ 
  SYMLINK+="A1", OWNER="root", GROUP="root", MODE="700"

root@imager:~# ls -ld /dev/A*
lrwxrwxrwx 1 root root 4 Oct 22 06:53 /dev/A1 -> sda5

# That, ^, is the wrong result.  /dev/sda has no ATTR{size}=="60028928".

Simple tests similar to these reported by Karl and I are likely to 
produce failures in short order.

Failure of salient features impairs the appeal of Debian.  With 
removable storage routinely depending upon udev, successful operation 
really should be verified before a new Debian is released.

Regards,   ... Peter E.

- 
VoIP:   +1 604 670 0140
work: https://en.wikibooks.org/wiki/User:PeterEasthope

Bug#1054363: bookworm-pu:package dav4tbsync

[Mechtilde Stehmann]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: eas4tbs...@packages.debian.org, mechti...@debian.org
Control: affects -1 + src:eas4tbsync

[ Reason ]

This package is a dependency of the extension tbsync to thunderbird. 
After thunderbird is updated to version 115.* in bookwork it is 
necessary to update this extension too.


[ Impact ]

Otherwise this extension doesn't work anymore

[ Risks ]

Only tbsync, dav4tbsync and eas4tbsync are affected and will be updated too

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

There is a new version of dav4tbsync to work with thunderbird 115.x

[ Other info ]

The output of debdiff (stable vs stable-pu is attached)

Tbsync and dav4tbsync are already updated

Kind regards to the release team

Mechtilde

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

 Makefile  |   25 
 background.js |2 
 content/api/BootstrapLoader/CHANGELOG.md  |   15 
 content/api/BootstrapLoader/implementation.js |  676 --
 content/api/BootstrapLoader/schema.json   |4 
 content/bootstrap.js  |   10 
 content/includes/calendarsync.js  |   13 
 content/includes/network.js   |   25 
 content/includes/tasksync.js  |   32 +
 content/includes/tools.js |   16 
 content/manager/createAccount.xhtml   |2 
 content/provider.js   |   21 
 debian/changelog  |   22 
 debian/control|4 
 debian/gbp.conf   |2 
 manifest.json |6 
 16 files changed, 677 insertions(+), 198 deletions(-)

diff -Nru eas4tbsync-4.1.5/background.js eas4tbsync-4.7/background.js
--- eas4tbsync-4.1.5/background.js	2022-10-13 11:05:56.0 +0200
+++ eas4tbsync-4.7/background.js	2023-08-18 16:51:43.0 +0200
@@ -16,7 +16,7 @@
 let manifest = browser.runtime.getManifest();
 browser.notifications.create({
   type: "basic",
-  iconUrl: browser.runtime.getURL("content/skin/sabredav32.png"),
+  iconUrl: browser.runtime.getURL("content/skin/eas32.png"),
   title: `${manifest.name}`,
   message: "Please update Thunderbird to at least 102.3.3 to be able to use this provider.",
 });
diff -Nru eas4tbsync-4.1.5/content/api/BootstrapLoader/CHANGELOG.md eas4tbsync-4.7/content/api/BootstrapLoader/CHANGELOG.md
--- eas4tbsync-4.1.5/content/api/BootstrapLoader/CHANGELOG.md	2022-10-13 11:05:56.0 +0200
+++ eas4tbsync-4.7/content/api/BootstrapLoader/CHANGELOG.md	2023-08-18 16:51:43.0 +0200
@@ -1,3 +1,18 @@
+Version: 1.21
+-
+- Explicitly set hasAddonManagerEventListeners flag to false on uninstall
+
+Version: 1.20
+-
+- hard fork BootstrapLoader v1.19 implementation and continue to serve it for
+  Thunderbird 111 and older
+- BootstrapLoader v1.20 has removed a lot of unnecessary code used for backward
+  compatibility
+
+Version: 1.19
+-
+- fix race condition which could prevent the AOM tab to be monkey patched correctly
+
 Version: 1.18
 -
 - be precise on which revision the wrench symbol should be displayed, instead of
diff -Nru eas4tbsync-4.1.5/content/api/BootstrapLoader/implementation.js eas4tbsync-4.7/content/api/BootstrapLoader/implementation.js
--- eas4tbsync-4.1.5/content/api/BootstrapLoader/implementation.js	2022-10-13 11:05:56.0 +0200
+++ eas4tbsync-4.7/content/api/BootstrapLoader/implementation.js	2023-08-18 16:51:43.0 +0200
@@ -2,7 +2,7 @@
  * This file is provided by the addon-developer-support repository at
  * https://github.com/thundernest/addon-developer-support
  *
- * Version: 1.18
+ * Version: 1.21
  *
  * Author: John Bieling (j...@thunderbird.net)
  *
@@ -17,70 +17,65 @@
 var { AddonManager } = ChromeUtils.import("resource://gre/modules/AddonManager.jsm");
 var { Services } = ChromeUtils.import("resource://gre/modules/Services.jsm");
 
-var BootstrapLoader = class extends ExtensionCommon.ExtensionAPI {
-  getMessenger(context) {   
-let apis = [
-  "storage",
-  "runtime",
-  "extension",
-  "i18n",
-];
-
-function getStorage() {
-  let localstorage = null;
-  try {
-localstorage = context.apiCan.findAPIPath("storage");
-localstorage.local.get = (...args) =>
-  localstorage.local.callMethodInParentProcess("get", args);
-localstorage.local.set = (...args) =>
-  

Bug#1054362: The PackageKit daemon has crashed

[Pascal Raton]

Subject: packagekit: The PackageKit daemon has crashed
Package: packagekit
Version: 1.2.7-1
Severity: normal

Dear Maintainer,

When I update the system with apper or discover, they stop with message 
"The PackageKit daemon has crashed
I reinstall all the system, same problem occur. Same thing in a VM fresh 
install

Here the log :


22/10/2023 16:40    packagekitd 
PackageKit:ERROR:../src/pk-transaction.c:5528:pk_transaction>
22/10/2023 16:40    packagekitd Bail out! 
PackageKit:ERROR:../src/pk-transaction.c:5528:pk_t>
22/10/2023 16:40    systemd Started 
systemd-coredump@17-462144-0.service - Process Core Dump (PI>
22/10/2023 16:40    systemd Started 
drkonqi-coredump-processor@17-462144-0.service - Pass system>
22/10/2023 16:40    systemd-coredump    Process 461772 
(packagekitd) of user 0 dumped core.


Module libudev.so.1 from deb systemd-254.5-1.amd64
Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2.amd64
Module libsystemd.so.0 from deb systemd-254.5-1.amd64
Stack trace of thread 461772:
#0  0x7f9a10fc n/a (libc.so.6 + 0x8a0fc)
#1  0x7f953472 raise (libc.so.6 + 0x3c472)
#2  0x7f93d4b2 abort (libc.so.6 + 0x264b2)
#3  0x7ffdaf08 n/a (libglib-2.0.so.0 + 0x1ef08)
#4  0x7fddde041e4e g_assertion_message_expr (libglib-2.0.so.0 + 0x85e4e)
#5  0x55bb171fdddc n/a (packagekitd + 0xfddc)
#6  0x7ff769c0 g_object_unref (libgobject-2.0.so.0 + 0x1b9c0)
#7  0x7ff98dc0 g_value_unset (libgobject-2.0.so.0 + 0x3ddc0)
#8  0x7ff85ebd n/a (libgobject-2.0.so.0 + 0x2aebd)
#9  0x7ff8c186 g_signal_emit_valist (libgobject-2.0.so.0 + 0x31186)
#10 0x7ff8c243 g_signal_emit (libgobject-2.0.so.0 + 0x31243)
#11 0x55bb17200992 pk_transaction_set_state (packagekitd + 0x12992)
#12 0x55bb1720728d n/a (packagekitd + 0x1928d)
#13 0x7fe7fc9c n/a (libgio-2.0.so.0 + 0x111c9c)
#14 0x7fddde013099 n/a (libglib-2.0.so.0 + 0x57099)
#15 0x7fddde0162d7 n/a (libglib-2.0.so.0 + 0x5a2d7)
#16 0x7fddde016bdf g_main_loop_run (libglib-2.0.so.0 + 0x5abdf)
#17 0x55bb171fbef1 main (packagekitd + 0xdef1)
#18 0x7f93e6ca n/a (libc.so.6 + 0x276ca)
#19 0x7f93e785 __libc_start_main (libc.so.6 + 0x27785)
#20 0x55bb171fc091 _start (packagekitd + 0xe091)

Stack trace of thread 462141:
#0  0x7fdddad165fd 
_ZN13debListParser12ParseDependsEPKcS1_RN3APT10StringViewES4_RjbbbNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE 
(libapt-pkg.so.6.0 + 0x1165fd)

#1  0x7fdddad17ba4 n/a (libapt-pkg.so.6.0 + 0x117ba4)
#2  0x7fdddad19685 n/a (libapt-pkg.so.6.0 + 0x119685)
#3  0x7fdddad9f0c2 n/a (libapt-pkg.so.6.0 + 0x19f0c2)
#4  0x7fdddada1776 n/a (libapt-pkg.so.6.0 + 0x1a1776)
#5  0x7fdddad7f1d5 
_ZN18pkgDebianIndexFile5MergeER17pkgCacheGeneratorP10OpProgress 
(libapt-pkg.so.6.0 + 0x17f1d5)

#6  0x7fdddad9b091 n/a (libapt-pkg.so.6.0 + 0x19b091)
#7  0x7fdddad9cf87 n/a (libapt-pkg.so.6.0 + 0x19cf87)
#8  0x7fdddada46ba n/a (libapt-pkg.so.6.0 + 0x1a46ba)
#9  0x7fdddacb98f1 _ZN12pkgCacheFile11BuildCachesEP10OpProgressb 
(libapt-pkg.so.6.0 + 0xb98f1)
#10 0x7fdddacb9c48 _ZN12pkgCacheFile4OpenEP10OpProgressb 
(libapt-pkg.so.6.0 + 0xb9c48)
#11 0x7f3399e0 _ZN12AptCacheFile4OpenEb (libpk_backend_apt.so + 
0x219e0)

#12 0x7f33f244 _ZN6AptJob4initEPPc (libpk_backend_apt.so + 0x27244)
#13 0x7f3361e1 n/a (libpk_backend_apt.so + 0x1e1e1)
#14 0x55bb17211e4a n/a (packagekitd + 0x23e4a)
#15 0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1)
#16 0x7f99f3ec n/a (libc.so.6 + 0x883ec)
#17 0x7fa1fa4c n/a (libc.so.6 + 0x108a4c)

Stack trace of thread 461778:
#0  0x7fa12a1f __poll (libc.so.6 + 0xfba1f)
#1  0x7fddde016237 n/a (libglib-2.0.so.0 + 0x5a237)
#2  0x7fddde016bdf g_main_loop_run (libglib-2.0.so.0 + 0x5abdf)
#3  0x7fe90dfa n/a (libgio-2.0.so.0 + 0x122dfa)
#4  0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1)
#5  0x7f99f3ec n/a (libc.so.6 + 0x883ec)
#6  0x7fa1fa4c n/a (libc.so.6 + 0x108a4c)

Stack trace of thread 461779:
#0  0x7fa17ee9 syscall (libc.so.6 + 0x100ee9)
#1  0x7fddde071b70 g_cond_wait_until (libglib-2.0.so.0 + 0xb5b70)
#2  0x7ffe0133 n/a (libglib-2.0.so.0 + 0x24133)
#3  0x7fddde0443ea n/a (libglib-2.0.so.0 + 0x883ea)
#4  0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1)
#5  0x7f99f3ec n/a (libc.so.6 + 0x883ec)
#6  0x7fa1fa4c n/a (libc.so.6 + 0x108a4c)

Stack trace of thread 461777:
#0  0x7fa12a1f __poll (libc.so.6 + 0xfba1f)
#1  0x7fddde016237 n/a (libglib-2.0.so.0 + 0x5a237)
#2  0x7fddde0168f0 g_main_context_iteration (libglib-2.0.so.0 + 0x5a8f0)
#3  0x7fddde016941 n/a (libglib-2.0.so.0 + 0x5a941)
#4  0x7fddde0439e1 n/a (libglib-2.0.so.0 + 0x879e1)
#5  0x7f99f3ec n/a (libc.so.6 + 0x883ec)
#6  0x7fa1fa4c n/a (libc.so.6 + 0x108a4c)

Stack trace of thread 461776:
#0  0x7fa17ee9 syscall (libc.so.6 + 0x100ee9)
#1  

Bug#994540: Go ahead with imagemagick/experimental ?

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-10-22 14:51:42 +, Bastien Roucariès wrote:
> Le dimanche 22 octobre 2023, 14:08:20 UTC Sebastian Ramacher a écrit :
> > Hi Bastien
> > 
> > On 2023-10-21 20:10:47 +, Bastien Roucariès wrote:
> > > Can I go ahead with imagemagick experimental ?
> > 
> > As a year has past since the last mail to the transition bug report: did
> > any new build failures in reverse dependencies appear? What's the
> > status?
> 
> Reverse build are ok (just tested in pbuilder), so for me it is a green light

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#994540: Go ahead with imagemagick/experimental ?

[Bastien Roucariès]

Le dimanche 22 octobre 2023, 14:08:20 UTC Sebastian Ramacher a écrit :
> Hi Bastien
> 
> On 2023-10-21 20:10:47 +, Bastien Roucariès wrote:
> > Can I go ahead with imagemagick experimental ?
> 
> As a year has past since the last mail to the transition bug report: did
> any new build failures in reverse dependencies appear? What's the
> status?

Reverse build are ok (just tested in pbuilder), so for me it is a green light
> 
> Cheers
> 



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

Bug#1054361: ITP: jruby-jzlib

[Jérôme Charaoui]

Package: wnpp
Severity: wishlist
Owner: Jérôme Charaoui 
X-Debbugs-Cc: debian-de...@lists.debian.org

   Package name : jruby-jzlib
   Version  : 1.1.5
   Upstream author  : y...@jcraft.com, JCraft,Inc.
   Upstream contact : Charles Oliver Nutter 
   URL  : https://github.com/jruby/jzlib
   License  : BSD-3-clause
   Programming Lang : Java
   Description  : JRuby's fork of the jzlib pure-Java zlib library

JZlib is a re-implementation of zlib in pure Java. This version is a 
fork of com.jcraft:jzlib with additional improvements for the JRuby 
environment.


This is part of an effort to improve the JRuby build chain in Debian.

Thanks,

-- Jerome

Bug#1054360: ITP: copy-rename-maven-plugin

[Jérôme Charaoui]

Package: wnpp
Severity: wishlist
Owner: Jérôme Charaoui 
X-Debbugs-Cc: debian-de...@lists.debian.org

   Package name : copy-rename-maven-plugin
   Version  : 2.0.0
   Upstream author  : Aneesh Joseph
   URL  : 
https://github.com/kohlschutter/copy-rename-maven-plugin

   License  : Expat
   Programming Lang : Java
   Description  : m2e compatible maven plugin for renaming/copying

This plugin helps in copying files or renaming files or directories 
during the Maven build lifecycle.


This is part of an effort to improve the JRuby build chain in Debian.

Thanks,

-- Jerome

Bug#994540: Go ahead with imagemagick/experimental ?

[Sebastian Ramacher]

Hi Bastien

On 2023-10-21 20:10:47 +, Bastien Roucariès wrote:
> Can I go ahead with imagemagick experimental ?

As a year has past since the last mail to the transition bug report: did
any new build failures in reverse dependencies appear? What's the
status?

Cheers
-- 
Sebastian Ramacher

Bug#1054359: opendht: FTBFS everywhere

[Sebastian Ramacher]

Source: opendht
Version: 3.0.0-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=opendht=amd64=3.0.0-3=1697936725=0

  dh_missing -a
dh_missing: warning: usr/bin/dhtchat exists in debian/tmp but is not installed 
to anywhere 
dh_missing: warning: usr/bin/dhtcluster exists in debian/tmp but is not 
installed to anywhere 
dh_missing: warning: usr/bin/dhtscanner exists in debian/tmp but is not 
installed to anywhere 
dh_missing: error: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: dhtnode (2), libopendht-c-dev (3), libopendht-c3 (2), 
libopendht-dev (7), libopendht3 (2), python3-opendht (2)
 * dh_installdocs: dhtnode (0), libopendht-c-dev (0), libopendht-c3 
(0), libopendht-dev (0), libopendht3 (0), python3-opendht (0)
 * dh_installman: dhtnode (1), libopendht-c-dev (0), libopendht-c3 (0), 
libopendht-dev (0), libopendht3 (0), python3-opendht (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.md.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
make: *** [debian/rules:23: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher

Bug#1054358: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-mbox
Version: 0.3.4-6
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1054357: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-fclabels
Version: 2.0.5.1-1
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1054356: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-data-tree-print
Version: 0.1.0.2-3
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1054355: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-parallel-tree-search
Version: 0.4.2-2
Severity: serious

I intend to remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 3 years ago
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1054353: Removal notice: obsolete

[Ilias Tsitsimpis]

Source: haskell-tree-monad
Version: 0.3.2-1
Severity: serious

I intend to remove this package:

  * The current version FTBFS
  * It's not part of the latest Stackage LTS

If you believe we should keep this package in Debian, please close this
bug report.

-- 
Ilias

Bug#1054354: netdata: Anomaly detection (ML)

[Skibbi]

Package: netdata
Version: 1.43.0-1
Severity: wishlist

Dear Maintainer,

Are there any issues to include ML (machine learning) anomaly detection
in netdata debian build? It would be nice to have this feature enabled for
debian package.

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 netdata depends on:
ii  netdata-core  1.43.0-1
ii  netdata-plugins-bash  1.43.0-1
ii  netdata-web   1.43.0-1

Versions of packages netdata recommends:
ii  netdata-plugins-python  1.43.0-1

netdata suggests no packages.

-- no debconf information

Bug#1054352: RM: haskell-template -- ROM; obsolete

[Ilias Tsitsimpis]

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

Please remove this package:

  * It has no rev dependencies
  * The current version FTBFS
  * Seems unmaintained; Last upload more than 5 years ago
  * It's not part of the latest Stackage LTS

Thanks,

-- 
Ilias

Bug#1032670: Remove fixed-upstream tag

[Andreas Rönnquist]

tags 1032670 - fixed-upstream
thanks

It's not fixed upstream in allegro4 - it is in allegro5, but not in
allegro4.

Bug#1054351: netdata: Missing directory in /etc/netdata

[Skibbi]

Package: netdata
Version: 1.43.0-1
Severity: minor

Dear Maintainer,

When starting netdata following error appears in the logs:
2023-10-22 13:45:16: netdata ERROR : PLUGINSD : cannot open plugins directory 
'/etc/netdata/custom-plugins.d' (errno 2, No such file or directory)

I think this directory should be created automatically when netdata is
installed.

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 netdata depends on:
ii  netdata-core  1.43.0-1
ii  netdata-plugins-bash  1.43.0-1
ii  netdata-web   1.43.0-1

Versions of packages netdata recommends:
ii  netdata-plugins-python  1.43.0-1

netdata suggests no packages.

-- no debconf information

Bug#1054350: ITP: python3-sphinx-wagtail-theme -- Sphinx theme for Wagtail

[Danial Behzadi]

Package: wnpp
Severity: wishlist
Owner: Danial Behzadi 
X-Debbugs-Cc: debian-de...@lists.debian.org, dani.be...@ubuntu.com

* Package name: python3-sphinx-wagtail-theme
  Version : 6.1.1
  Upstream Contact: Wagtail contributors 
https://github.com/wagtail/sphinx-wagtail-theme
* URL : https://github.com/wagtail/sphinx-wagtail-theme
* License : MIT
  Programming Lang: Javascript
  Description : Sphinx theme for Wagtail

Sphinx Wagtail theme contains all files required to build a Sphinx extension
that provides the theme.

Bug#1054326: [Debian-ha-maintainers] Bug#1054326: Can't start golbal heartbeat when drbd device is on top LVM device

[Daniel Smolik]

I completely  agree, but when it is on md device then is UUID visible on 
both nodes too. My guess is  that name  of LVM  device is longer than md 
or drbd device.  And I looked  to source code and start heartbeat failed


here: in op_start.c

 if (!(od->od_flags & O2CB_DEVICE_FOUND)) {
    tcom_err(ret, "%s", od->od_uuid);
    goto bail;
    }

It is only testing device and for final solution isn't  local heartbeat 
possible. In o2cb is not possible specify device where start heartbeat.







Dne 22. 10. 23 v 13:37 Valentin Vidic napsal(a):

On Sun, Oct 22, 2023 at 12:11:19PM +0200, Daniel Smolik wrote:

Yes no problem. There it is.

Thanks. My best guess is that the problem happens because the region
UUID is visible on both drbd and the lower device, so the global
heartbeat might work if drbd device is selected first (for example in
the case of md).

Since I don't know if it possible to specify the device directly, your
best bet now is probably to use the local heartbeat mode (that should
work without the regions being specified).

Bug#1049459: RM: mime-support -- ROM; Transition over

[Charles Plessy]

Le Tue, Oct 10, 2023 at 06:56:43AM +0900, Charles Plessy a écrit :
> 
> python3-pil depends on mime-support | python3-pil.imagetk, and
> python3-pil.imagetk does not depend on mime-support, thus python3-pil is
> installable without mime-support, isn't it?
> 
> Could you please remove mime-support?

Shall I understand your silence as a "no?"

> I would like to finish this
> transition, to not have to think about it anymore, and focus on the
> future.
> 
> If you prefer I NMU pillow instead, please let me know.
> 
> Have a nice day,
> 
> Charles
> 
> -- 
> Charles Plessy Nagahama, Yomitan, Okinawa, Japan
> Tooting from work,   https://fediscience.org/@charles_plessy
> Tooting from home, https://framapiaf.org/@charles_plessy

Bug#1054345: Bug presebt on all recent kernel versions

[ael]

 just tested on kernel versions 6.5.0-1-amd64, 6.4.0-4-amd64, 6.4.0-3-amd64 & 
6.4.0-2-amd64
 and same bug present on all. So it is long standing, and not specific
 to 6.5.0-2.

 ael

Bug#1054298: apt-listchanges: 4.4 still/again showing old changelogs

[Andreas Metzler]

On 2023-10-21 Jonathan Kamens  wrote:
> On 10/21/23 12:24, Andreas Metzler wrote:
> > However I still do not get it.
> > * Is there a useful scenario where someone would set save_seen=none in
> >the apt stanza?
> *shrug* I don't know. That design decision was made long before my time. I
> don't see any good reason to change it given that if anybody /is/ taking
> advantage of it for whatever reason, then doing so would cause them trouble.

Hello, 

I have played around a little bit, upgrading a single package, with and
without save_seen=none:

I could not see a difference in behavior for apt-listchanges 3.x. It
showed new changelog entries compared to the installed version even if
the same upgrade was previously aborted.

With apt-listchanges there is a difference in behavior, with
save_seen=none it showed new changelog entries compared to the installed
version even on abort (like 3.x), with
save_seen=/var/lib/apt/listchanges.db it did not re-show changes if the
previous try was aborted.

I could *not* reproduce this bug, i.e. apt-listchanges showing older
changelog entries than the one installed.

Assuming 3.x behavior is correct (see below) I still have no idea what
user-visible changes save_seen is supposed to trigger. Is this a
performance optimization or an implementation detail? Afaiu
apt-listchanges

> > * Would I be reshown changelog entries when I had already seen them
> >before but aborted the upgrade if save_seen=/var/lib/apt/listchanges
> >was set?

> In version 3.x of apt-listchanges, if you aborted the update and then ran it
> again you would be shown the changes again. In the current 4.x version of
> apt-listchanges, you will /not/ be shown the changes again if you abort and
> rerun an update.

> Your question has prompted me to think further about this and now I'm not
> convinced the change in behavior in 4.x is correct. What do you think? Do
> you think the program should only "commit" the changes to the database and
> not display them again if the user goes through with the update?

Yes I think the old behavior is correct.

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

Bug#1052847: fixed in python-marshmallow 3.20.1-1

[Luca Boccassi]

On Tue, 10 Oct 2023 07:49:21 + Debian FTP Masters
 wrote:
> Source: python-marshmallow
> Source-Version: 3.20.1-1
> Done: Federico Ceratto 
> 
> We believe that the bug you reported is fixed in the latest version
of
> python-marshmallow, which is due to be installed in the Debian FTP
archive.
> 
> A summary of the changes between this version and the previous one is
> attached.
> 
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 1052...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Federico Ceratto  (supplier of updated python-
marshmallow package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Sun, 08 Oct 2023 15:44:04 +0200
> Source: python-marshmallow
> Binary: python3-marshmallow python3-marshmallow-doc
> Architecture: source all
> Version: 3.20.1-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Federico Ceratto 
> Changed-By: Federico Ceratto 
> Description:
>  python3-marshmallow - Lightweight library for converting complex
datatypes
>  python3-marshmallow-doc - Library for converting complex datatypes -
documentation
> Closes: 1052847
> Changes:
>  python-marshmallow (3.20.1-1) unstable; urgency=medium
>  .
>    * New upstream release
>    * Add tzdata-legacy dependency (Closes: #1052847)
> Checksums-Sha1:
>  d071d76b4927a7dd9977a679731177a728ffec17 2231 python-
marshmallow_3.20.1-1.dsc
>  b7c0b0ab3e920d0be51a2781494572be50497256 183404 python-
marshmallow_3.20.1.orig.tar.gz
>  0897439bc42faacd2cc589019b230a2105fb24ca 3416 python-
marshmallow_3.20.1-1.debian.tar.xz
>  52cae8744d027eda054153839f2531640196bbc6 8173 python-
marshmallow_3.20.1-1_amd64.buildinfo
>  de04d18ad70a546ceda5ee7b43133a58c8f1934e 206608 python3-marshmallow-
doc_3.20.1-1_all.deb
>  91df8b952bcc1c2b1cb3147e0fd6374d53f763c4 67344 python3-
marshmallow_3.20.1-1_all.deb
> Checksums-Sha256:
>  e7b4a412db99f1cfe0085d5ca6f7053804a773bc9d6223724b945889ca523dd7
2231 python-marshmallow_3.20.1-1.dsc
>  1f37696dea0b6d4a9de04459ba694106531c42179547b286c81113e02234d1bf
183404 python-marshmallow_3.20.1.orig.tar.gz
>  0cdd5c67f3f622d0bd7fab8cde497a149867cbde65c5440dd66cbb9f57f0d02b
3416 python-marshmallow_3.20.1-1.debian.tar.xz
>  c3966faf26c25ac7696bfec0d96bc76a8a96742a04830f7ec8f0ce8656dc70c9
8173 python-marshmallow_3.20.1-1_amd64.buildinfo
>  02ca24d9e18b15a09b06e1c27df34eff09947bb7ba9270ef8cc705ecb0a5ac12
206608 python3-marshmallow-doc_3.20.1-1_all.deb
>  c03f1923160bbba80b5823dd7310c185cbabef9fe723ba1be1c2f009a8003158
67344 python3-marshmallow_3.20.1-1_all.deb
> Files:

Federico,

This was done as a binary upload, so it cannot migrate to testing. A
bunch of stuff is going to be autoremoved soon because of this. Was
that intentional? Could you please do a source-only upload?

-- 
Kind regards,
Luca Boccassi


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

Bug#1054349: netdata: debugfs plugin requires setuid flag set to work properly

[Skibbi]

Package: netdata
Version: 1.43.0-1
Severity: normal

Dear Maintainer,
I've got some time to check latest netdata package and I found several
issues. One is related to debugfs plugin. Here is the excerpt from logs:

2023-10-22 12:56:07: debugfs.plugin ERROR : debugfs.plugin : debugfs.plugin 
should either run as root (now running with uid 998, euid 998) or have special 
capabilities. Without these, debugfs.plugin cannot access /sys/kernel/debug. To 
enable capabilities run: sudo setcap cap_dac_read_search,cap_sys_ptrace+ep 
/usr/lib/netdata/plugins.d/debugfs.plugin; To enable setuid to root run: sudo 
chown root:netdata /usr/lib/netdata/plugins.d/debugfs.plugin; sudo chmod 4750 
/usr/lib/netdata/plugins.d/debugfs.plugin;  (errno 13, Permission denied)

I followed the suggestion and added setuid flag to the plugin binary.
After restart the issue is gone. So, perhaps setuid should be set as
defaukt for debugfs plugin?

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

Kernel: Linux 6.4.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 netdata depends on:
ii  netdata-core  1.43.0-1
ii  netdata-plugins-bash  1.43.0-1
ii  netdata-web   1.43.0-1

Versions of packages netdata recommends:
ii  netdata-plugins-python  1.43.0-1

netdata suggests no packages.

-- no debconf information

Bug#1054326: [Debian-ha-maintainers] Bug#1054326: Can't start golbal heartbeat when drbd device is on top LVM device

[Valentin Vidic]

On Sun, Oct 22, 2023 at 12:11:19PM +0200, Daniel Smolik wrote:
> Yes no problem. There it is.

Thanks. My best guess is that the problem happens because the region
UUID is visible on both drbd and the lower device, so the global
heartbeat might work if drbd device is selected first (for example in
the case of md).

Since I don't know if it possible to specify the device directly, your
best bet now is probably to use the local heartbeat mode (that should
work without the regions being specified).

-- 
Valentin

Bug#1054348: parcellite: windows fail to appear

[Thorsten Bonow]

Package: parcellite
Version: 1.2.1-7
Severity: grave
X-Debbugs-Cc: none, Thorsten Bonow 



Dear Maintainer,

when starting parcellite with "parcellite" or "parcellite -n" (I'm 
using LarsWM, a window manager without icon support), I can no longer 
access the programm.  The hotkeys (C-M-ö for the clipboard history, 
C-M-ß for the persistent history or C-M-ä for actions) don't open any 
windows.


Downgrading the parcellite package to parcellite_1.2.1-5_amd64.deb 
solves the problem for me!


The new version 1.2.1-7 gives the following output after startup:

Flag 0x0001, status 0, EXIT 1 STAT 0

Flag 0x0001, status 0, EXIT 1 STAT 0

Upon pressing a hotkey, this output is generated:

(parcellite:660159): Gdk-CRITICAL **: 12:45:55.482: 
gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed


Thx for any help.

Toto

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

Kernel: Linux 6.5.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

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

Versions of packages parcellite depends on:
ii  libc6   2.37-12
ii  libglib2.0-02.78.0-2
ii  libgtk-3-0  3.24.38-5
ii  libpango-1.0-0  1.51.0+ds-2
ii  libx11-62:1.8.7-1

parcellite recommends no packages.

parcellite suggests no packages.

-- debconf-show failed

Bug#837060: debootstrap: Do not install packages of Priority:required for buildd variant

[Johannes Schauer Marin Rodrigues]

Hi Luca,

Quoting Luca Boccassi (2023-10-18 19:38:16)
> Thanks - I'll merge and do an upload over the weekend then

thank you for your upload!! :D

I temporarily subscribed to debootstrap via tracker.d.o so that I hopefully
catch any bug report coming in related to this change.

I also re-triggered some autopkgtests that were flaky and where re-running them
now makes all the reverse dependencies work.

Well, not all the reverse dependencies. The autopkgtest of mmdebstrap broke as
expected, which is of course also good because it matches our expectations.

I have the fix for this locally and am currently running the mmdebstrap test
suite with the fix I posted in my last mail. This made me find another change
that was necessary. /usr/share/debootstrap/scripts/debian-common sets up
/etc/localtime if it doesn't exist yet. This code-path was probably not taken
so far because tzdata was always installed? In any case, I think this is
harmless and doesn't require any changes.

Then I worried that we forgot to update the man page after this change.
Luckily, the man page only points out that the buildd profile installs
build-essential and does not talk about priority:required packages, so that
checks out. What could maybe be added is, that the buildd variant installs
build-essential *and* apt which is the remaining exception to the rule.

I will upload mmdebstrap with the required changes after the test suite
finished in about six hours.

Thanks again!

cheers, josch

signature.asc
Description: signature

Bug#208967: [docbook2man] Patch to get correct replacement for dashes/hyphen

[Alejandro Colomar]

Hi!

Here's a ping, reminding that this bug still affects Debian Trixie
(currently unstable).  I have uncommented the workaround in my
/etc/groff/man.local, because as maintainer of the Linux man-pages, I do
want to be able to check if there are problems in my manual pages.  As a
consequence, I can't search (/) for options and things that contain '-'
in manual pages that have this bug.

There's a patch, so what else do we need to fix the bug?  Can the patch
be offered to upstream, please?

Thanks,
Alex

On Sun, 10 Aug 2014 13:17:20 +0200 Joseph Herlant  wrote:
> Control: tags -1 +patch
> 
> Hi,
> 
> Please find attached the debdiff patch that should solve both #208967
> and #628751.
> 
> In short:  Current version of docbook2man's hyphen rendering makes
> lintian complain about "hyphen-used-as-minus-sign". This patch renders
> `-' as `\-' and `\-' as `\\\-', so we should have a correct output and
> lintian not complaining again.
> 
> This should solve a big amount of the current
> "hyphen-used-as-minus-sign" reports.
> 
> I wrote it as an NMU but I'd rather have it uploaded and integrated by
> official maintainers.
> 
> Tested on module-init-tools (the oldstable version which uses sgml)
> and it seems fine to me.
> Also tested on gnome-shell-pomodoro I am currently using sgml man
> pages with and it also works great!
> 
> Best,
> Joseph

-- 



signature.asc
Description: PGP signature

Bug#1054347: gnuradio-doc: wrong filename in package description

[Daniele Forsi]

Package: gnuradio-doc
Version: 3.10.8.0-1
Severity: minor
X-Debbugs-Cc: dfo...@gmail.com

Dear maintainer,

tha package description refers to this file:
file:///usr/share/doc/gnuradio-doc/html/index.htnl

however the extension should be html instead of htnl.

regards,
Daniele

Bug#1037258: curl -I (HEAD request) fails with HTTP/2 against a Debian Apache instance

[Samuel Henrique]

Since 2023-10-02, we have a fixed version of the curl package on
stable-backports, so this can serve as a workaround if you're fine
with the constraints of the backports repository[0].

The current investigation status is that we know which commit caused
the regression and which one fixed it, but we don't know exactly what
change in the fixing commit is required (it's changing a lot of things
at once).

We also don't know exactly what are the conditions that trigger the
issue, but we know it has to do with HTTP2 and there are a couple of
endpoints we can use for debugging.

Regression commit:
https://github.com/curl/curl/commit/8c762f59983a3e9e2b80fdb34aa5e08f1d9a1c7d
(curl-7_88_0)
Fixing commit: 
https://github.com/curl/curl/commit/744dcf22fac6cf12a9112df106b61864982afef9
(curl-8_1_0)

[0]: https://backports.debian.org/

Cheers,

-- 
Samuel Henrique 

Bug#1054345: linux-image-6.5.0-2-amd64: Segfault with USB Mass storage

[ael]

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

Dear Maintainer,

This is just a very preliminary report with little proper information as
yet: perhaps a placeholder which may be useful if other are seein this
problem.

Since installing 6.5.0-2, when hot plugging USB sticks, I see segfault
messages in dmesq such as:

---
[ 2538.645420] usb 2-9: new high-speed USB device number 3 using xhci_hcd
[ 2538.800696] usb 2-9: New USB device found, idVendor=090c, idProduct=1000, 
bcdDevice=20.40
[ 2538.800705] usb 2-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2538.800708] usb 2-9: Product: USB 2.0 Flash Drive
[ 2538.800711] usb 2-9: Manufacturer: Super Talent Flash
[ 2538.800713] usb 2-9: SerialNumber: 13005672
[ 2538.915612] w[15439]: segfault at 4c ip 55bcdea2d09e sp 7ffd80083c00 
error 4 in w[55bcdea2c000+3000] likely on CPU 5 (core 1, socket 0)
[ 2538.915624] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f 
be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 
00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d
[ 2539.107372] usb-storage 2-9:1.0: USB Mass Storage device detected
[ 2539.107500] scsi host6: usb-storage 2-9:1.0
[ 2539.107576] usbcore: registered new interface driver usb-storage
[ 2539.110315] usbcore: registered new interface driver uas
[ 2539.194645] w[16015]: segfault at 4c ip 55595990709e sp 7ffd9dc81ca0 
error 4 in w[555959906000+3000] likely on CPU 2 (core 2, socket 0)
[ 2539.194662] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f 
be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 
00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d
[ 2540.114671] scsi 6:0:0:0: Direct-Access Flash/SM Super Talent 2.0 2040 
PQ: 0 ANSI: 0 CCS
[ 2540.115312] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2540.116750] sd 6:0:0:0: [sdb] 1014784 512-byte logical blocks: (520 MB/496 
MiB)
[ 2540.117302] sd 6:0:0:0: [sdb] Write Protect is off
[ 2540.117308] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 2540.117876] sd 6:0:0:0: [sdb] No Caching mode page found
[ 2540.117883] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 2540.172366]  sdb: sdb1 sdb2
[ 2540.172729] sd 6:0:0:0: [sdb] Attached SCSI removable disk



This has happened with at least two different usb sticks of very
different vintages.

I did run a memtest check on RAM, but this only seem to happen when
hotplugging USB sticks, so I am confident that this is a kernel/module
bug.

When I have more time, I will attempt to turn on debugging options and
symbols and more. But I doubt that I am the only one seeing this, and
maybe the bug is already fixed upstream.



-- Package-specific info:
** Version:
Linux version 6.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 
13.2.0-5) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC 
Debian 6.5.6-1 (2023-10-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.5.0-2-amd64 
root=UUID=5b8060f7-f126-4534-a051-db5d205bd315 ro elevator=deadline

** Not tainted

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

** Model information
sys_vendor: Notebook
product_name: W54_55SU1,SUW
product_version: Not Applicable  
chassis_vendor: Notebook
chassis_version: N/A 
bios_vendor: American Megatrends Inc.
bios_version: 4.6.5
board_vendor: Notebook
board_name: W54_55SU1,SUW
board_version: Not Applicable  

** Loaded modules:
uas
usb_storage
mptcp_diag
xsk_diag
tcp_diag
udp_diag
raw_diag
inet_diag
unix_diag
af_packet_diag
netlink_diag
xt_recent
ipt_REJECT
nf_reject_ipv4
xt_comment
xt_hashlimit
xt_addrtype
xt_mark
xt_NFLOG
nfnetlink_log
xt_LOG
nf_log_syslog
nf_nat_tftp
nf_nat_snmp_basic
nf_conntrack_snmp
nf_nat_sip
nf_nat_pptp
nf_nat_irc
nf_nat_h323
nf_nat_ftp
nf_nat_amanda
ts_kmp
nf_conntrack_amanda
nf_conntrack_sane
nf_conntrack_tftp
nf_conntrack_sip
nf_conntrack_pptp
nf_conntrack_netlink
nf_conntrack_netbios_ns
nf_conntrack_broadcast
nf_conntrack_irc
nf_conntrack_h323
nf_conntrack_ftp
xt_tcpudp
xt_conntrack
nft_compat
nft_chain_nat
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nf_tables
libcrc32c
nfnetlink
qrtr
tun
uinput
binfmt_misc
btusb
btrtl
btbcm
btintel
btmtk
bluetooth
sha3_generic
jitterentropy_rng
drbg
ansi_cprng
ecdh_generic
ecc
pktcdvd
intel_rapl_msr
intel_rapl_common
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
iwlmvm
kvm
cpufreq_ondemand
irqbypass
crc32_pclmul
mac80211
ghash_clmulni_intel
sha512_ssse3
sha512_generic
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
snd_hda_codec_hdmi
libarc4
aesni_intel
snd_hda_intel
snd_intel_dspcfg
crypto_simd
snd_intel_sdw_acpi
cryptd
snd_hda_codec
iwlwifi
iTCO_wdt

Bug#1054346: linux-image-6.5.0-2-amd64: Segfault with USB Mass storage

[ael]

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

Dear Maintainer,

This is just a very preliminary report with little proper information as
yet: perhaps a placeholder which may be useful if other are seein this
problem.

Since installing 6.5.0-2, when hot plugging USB sticks, I see segfault
messages in dmesq such as:

---
[ 2538.645420] usb 2-9: new high-speed USB device number 3 using xhci_hcd
[ 2538.800696] usb 2-9: New USB device found, idVendor=090c, idProduct=1000, 
bcdDevice=20.40
[ 2538.800705] usb 2-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2538.800708] usb 2-9: Product: USB 2.0 Flash Drive
[ 2538.800711] usb 2-9: Manufacturer: Super Talent Flash
[ 2538.800713] usb 2-9: SerialNumber: 13005672
[ 2538.915612] w[15439]: segfault at 4c ip 55bcdea2d09e sp 7ffd80083c00 
error 4 in w[55bcdea2c000+3000] likely on CPU 5 (core 1, socket 0)
[ 2538.915624] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f 
be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 
00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d
[ 2539.107372] usb-storage 2-9:1.0: USB Mass Storage device detected
[ 2539.107500] scsi host6: usb-storage 2-9:1.0
[ 2539.107576] usbcore: registered new interface driver usb-storage
[ 2539.110315] usbcore: registered new interface driver uas
[ 2539.194645] w[16015]: segfault at 4c ip 55595990709e sp 7ffd9dc81ca0 
error 4 in w[555959906000+3000] likely on CPU 2 (core 2, socket 0)
[ 2539.194662] Code: 0f be c3 48 8b 12 f6 44 42 01 40 74 7f 80 fb 20 74 7a 0f 
be fb 48 83 c5 01 e8 6e f1 ff ff 49 39 ee 0f 84 7d 00 00 00 45 89 e7 <0f> b6 5d 
00 84 db 75 ba 45 85 ff 75 65 48 8b 35 76 3f 00 00 bf 2d
[ 2540.114671] scsi 6:0:0:0: Direct-Access Flash/SM Super Talent 2.0 2040 
PQ: 0 ANSI: 0 CCS
[ 2540.115312] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 2540.116750] sd 6:0:0:0: [sdb] 1014784 512-byte logical blocks: (520 MB/496 
MiB)
[ 2540.117302] sd 6:0:0:0: [sdb] Write Protect is off
[ 2540.117308] sd 6:0:0:0: [sdb] Mode Sense: 43 00 00 00
[ 2540.117876] sd 6:0:0:0: [sdb] No Caching mode page found
[ 2540.117883] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[ 2540.172366]  sdb: sdb1 sdb2
[ 2540.172729] sd 6:0:0:0: [sdb] Attached SCSI removable disk



This has happened with at least two different usb sticks of very
different vintages.

I did run a memtest check on RAM, but this only seem to happen when
hotplugging USB sticks, so I am confident that this is a kernel/module
bug.

When I have more time, I will attempt to turn on debugging options and
symbols and more. But I doubt that I am the only one seeing this, and
maybe the bug is already fixed upstream.



-- Package-specific info:
** Version:
Linux version 6.5.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-13 (Debian 
13.2.0-5) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC 
Debian 6.5.6-1 (2023-10-07)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-6.5.0-2-amd64 
root=UUID=5b8060f7-f126-4534-a051-db5d205bd315 ro elevator=deadline

** Not tainted

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

** Model information
sys_vendor: Notebook
product_name: W54_55SU1,SUW
product_version: Not Applicable  
chassis_vendor: Notebook
chassis_version: N/A 
bios_vendor: American Megatrends Inc.
bios_version: 4.6.5
board_vendor: Notebook
board_name: W54_55SU1,SUW
board_version: Not Applicable  

** Loaded modules:
uas
usb_storage
mptcp_diag
xsk_diag
tcp_diag
udp_diag
raw_diag
inet_diag
unix_diag
af_packet_diag
netlink_diag
xt_recent
ipt_REJECT
nf_reject_ipv4
xt_comment
xt_hashlimit
xt_addrtype
xt_mark
xt_NFLOG
nfnetlink_log
xt_LOG
nf_log_syslog
nf_nat_tftp
nf_nat_snmp_basic
nf_conntrack_snmp
nf_nat_sip
nf_nat_pptp
nf_nat_irc
nf_nat_h323
nf_nat_ftp
nf_nat_amanda
ts_kmp
nf_conntrack_amanda
nf_conntrack_sane
nf_conntrack_tftp
nf_conntrack_sip
nf_conntrack_pptp
nf_conntrack_netlink
nf_conntrack_netbios_ns
nf_conntrack_broadcast
nf_conntrack_irc
nf_conntrack_h323
nf_conntrack_ftp
xt_tcpudp
xt_conntrack
nft_compat
nft_chain_nat
nf_nat
nf_conntrack
nf_defrag_ipv6
nf_defrag_ipv4
nf_tables
libcrc32c
nfnetlink
qrtr
tun
uinput
binfmt_misc
btusb
btrtl
btbcm
btintel
btmtk
bluetooth
sha3_generic
jitterentropy_rng
drbg
ansi_cprng
ecdh_generic
ecc
pktcdvd
intel_rapl_msr
intel_rapl_common
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
iwlmvm
kvm
cpufreq_ondemand
irqbypass
crc32_pclmul
mac80211
ghash_clmulni_intel
sha512_ssse3
sha512_generic
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
snd_hda_codec_hdmi
libarc4
aesni_intel
snd_hda_intel
snd_intel_dspcfg
crypto_simd
snd_intel_sdw_acpi
cryptd
snd_hda_codec
iwlwifi
iTCO_wdt

Bug#1054342: Acknowledgement (ITP: g-golf -- Guile Object Library for GNOME)

[Tommi Höynälänmaa]

The upstream author of the package is David Pirotte .


--
Kotisivu / Homepage: http://www.iki.fi/tohoyn/
Sähköposti / E-Mail: tommi.hoynalan...@iki.fi
GPG-sormenjälki / GPG fingerprint:
55F4 2477 7155 3528 5CB2 2B7A BB86 1FDE 4046 0F83
FM, Debian-ylläpitäjä / M.Sc., Debian Maintainer

Bug#1054344: ITP: theme-d-intr -- software library for using G-Golf in Theme-D

[Tommi Höynälänmaa]

Package: wnpp
Severity: wishlist
Owner: Tommi Höynälänmaa 
X-Debbugs-Cc: debian-de...@lists.debian.org, tommi.hoynalan...@iki.fi

* Package name: theme-d-intr
  Upstream Contact: Tommi Höynälänmaa 
* URL : https://www.iki.fi/tohoyn/theme-d-intr/
* License : GPL and LGPL
  Programming Lang: Theme-D and Scheme
  Description : software library for using G-Golf in Theme-D

Theme-D-Intr is a software library that allows using the G-Golf
introspection library in Theme-D. For example, you can use the Gtk
user interface library in Theme-D.