Bug#990508: RFS: apt-listchanges/3.24.1 [ITA] -- Show new changelog entries from Debian package archives

[Brian Thompson]

On Sat, Jul 03, 2021 at 12:50:17PM +0200, David Kalnischkies wrote:
>Hi,
>
>On Wed, Jun 30, 2021 at 06:13:14PM -0500, Brian Thompson wrote:
>>   * Fix error message being thrown when choosing not to proceed on
>> confirmation (closes: #989496).
>
>If I understand your fix correctly, you have broken the "no"
>functionality as the Pre-Install-Pkgs hook has to fail for apt to
>actually stop… if they are successful apt will continue with what it was
>initially told to do, which seems not inline with what "no" was supposed
>to accomplish… could you clarify?

I didn't realize that the error message I essentially got rid of was
intended functionality.  I did some rudimentary testing of the change,
and if "no" was selected then any packages with a changelog entry aren't
updated, but everything else is.  Still, in hindsight, that could break
the existing package if dependencies are updated and the source package
is held back (that's definitely not what I intended).  I should have
tested more thoroughly, but I can revert the change.

I think the bug that was referenced by that fix shows that [at least]
some users were confused by the error message, and didn't realize it was
intended functionality.  Perhaps cleaning up the error message a bit so
users aren't confused by it (which may lead to erroneous bug reports) is
a good idea.

>(I don't know apt-listchanges code nor do I use the confirmation
> functionality of it, so I could easily be entirely wrong)

I'm pretty new to it as well.  I've only read through the code one time.

>(That seems more like we should have a way for the hooks to tell apt to
> gracefully wind down, but that doesn't exist so far)

That would be ideal.

>Could I interest you in joining the apt-team and maintain listchanges as
>part of it? I am personally not much help than it comes to python, but
>Julian might. Mailing list is de...@lists.debian.org and/or you can join
>our IRC channel #debian-apt.

I would be interested in joining the apt-team, and I think that makes
more sense than making "rogue" contributions outside of the team's view.

>I also note that your changelog targets unstable, which might be fine if
>you want to fix the mentioned bug and consider it RC (I am not so sure),
>but the churn in the package (= reflow of the pt.po and pot file) will
>make the release team unhappy.

That's good to know.  Thanks for pointing that out.  This is my first
contribution.

>Looking at your git history, all this should not be in one single commit
>either – individual commits with proper titles and metadata will help
>you even: You wrote the changelog by hand, git-buildpackage can do this
>for you...
>
>As a bonus, a week later looking at the history you will still know at
>a glance what happened without remembering (or looking up) cryptic
>bugreport numbers first – not to mention others. With the data in place
>you could then also add a hook to salsa which automatically sets
>bugreports to pending after a push of the related commit and many more
>fun stuff.
>
>(It is of course not required, even many upstream projects use "fix #42"
> as commit message and are happy and successful. So if that works for
> you fine, I am just trying to nudge you to try an alternative which
> works better for me, many others and perhaps also you)

Also good stuff to know.  I will take your advice and follow in others'
footsteps.

+++
In the meantime, I will take a closer look at the bug reports to see if
there are any quick wins there.  That way I can proceed with the
adoption of the package.

Lastly, I'll join the IRC channel and look to join the apt-team, as you
suggested.

Thanks, David!

-- 
Best regards,

Brian T


signature.asc
Description: PGP signature

Bug#941951: ITA: tpm2-pk11

[Seunghun Han]

Hello Sean,

On Sun, Jul 4, 2021 at 4:16 AM Sean Whitton  wrote:

> Do you still intend to adopt?  At the very least seems we should
> probably remove this from the RM queue?

Thank you for the notification. I heard that this project was
deprecated [1] and moved to tpm2-pkcs11 project. So, I would like to
cancel it.

Best regards,

Seunghun


[1]: https://github.com/irtimmer/tpm2-pk11

Bug#867548: New HDMI audio video IOMMU issues in Bullseye upgrade on Haswell are old

[Bryan Cebuliak]

Ubuntu 20.04:
dmesg | grep -e DMAR -e IOMMU
[0.007620] ACPI: DMAR 0xD8FFEAE8 B8 (v01 INTEL  HSW
 0001 INTL 0001)
[0.007633] ACPI: Reserving DMAR table memory at [mem
0xd8ffeae8-0xd8ffeb9f]
[0.097851] DMAR: Host address width 39
[0.097852] DMAR: DRHD base: 0x00fed9 flags: 0x0
[0.097855] DMAR: dmar0: reg_base_addr fed9 ver 1:0 cap
c020660462 ecap f0101a
[0.097856] DMAR: DRHD base: 0x00fed91000 flags: 0x1
[0.097858] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[0.097858] DMAR: RMRR base: 0x00dbcf6000 end: 0x00dbd03fff
[0.097859] DMAR: RMRR base: 0x00dd00 end: 0x00df1f
[0.097861] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[0.097861] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[0.097862] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[0.098256] DMAR-IR: Enabled IRQ remapping in x2apic mode

On Sat, 3 Jul 2021 at 17:28, Bryan Cebuliak 
wrote:

> bullseye with intel_iommu=on,igfx_off:
> sudo dmesg | grep -e DMAR -e IOMMU
> [0.007516] ACPI: DMAR 0xD8FFEAE8 B8 (v01 INTEL  HSW
>  0001 INTL 0001)
> [0.007531] ACPI: Reserving DMAR table memory at [mem
> 0xd8ffeae8-0xd8ffeb9f]
> [0.019109] DMAR: Disable GFX device mapping
> [0.047926] DMAR: Host address width 39
> [0.047926] DMAR: DRHD base: 0x00fed9 flags: 0x0
> [0.047930] DMAR: dmar0: reg_base_addr fed9 ver 1:0 cap
> c020660462 ecap f0101a
> [0.047930] DMAR: DRHD base: 0x00fed91000 flags: 0x1
> [0.047932] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
> d2008020660462 ecap f010da
> [0.047933] DMAR: RMRR base: 0x00dbcf6000 end: 0x00dbd03fff
> [0.047934] DMAR: RMRR base: 0x00dd00 end: 0x00df1f
> [0.047936] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
> [0.047937] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
> [0.047937] DMAR-IR: Queued invalidation will be enabled to support
> x2apic and Intr-remapping.
> [0.048327] DMAR-IR: Enabled IRQ remapping in x2apic mode
> [0.793666] DMAR: No ATSR found
> [0.793696] DMAR: dmar1: Using Queued invalidation
> [0.795240] DMAR: Intel(R) Virtualization Technology for Directed I/O
> [0.799207] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel  >
> [0.799207] AMD-Vi: AMD IOMMUv2 functionality not available on this
> system
>
>
> bullseye with no intel_iommu command line setting:
> dmesg | grep -e DMAR -e IOMMU
> [0.007532] ACPI: DMAR 0xD8FFEAE8 B8 (v01 INTEL  HSW
>  0001 INTL 0001)
> [0.007546] ACPI: Reserving DMAR table memory at [mem
> 0xd8ffeae8-0xd8ffeb9f]
> [0.048030] DMAR: Host address width 39
> [0.048031] DMAR: DRHD base: 0x00fed9 flags: 0x0
> [0.048034] DMAR: dmar0: reg_base_addr fed9 ver 1:0 cap
> c020660462 ecap f0101a
> [0.048035] DMAR: DRHD base: 0x00fed91000 flags: 0x1
> [0.048037] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
> d2008020660462 ecap f010da
> [0.048037] DMAR: RMRR base: 0x00dbcf6000 end: 0x00dbd03fff
> [0.048038] DMAR: RMRR base: 0x00dd00 end: 0x00df1f
> [0.048040] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
> [0.048040] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
> [0.048041] DMAR-IR: Queued invalidation will be enabled to support
> x2apic and Intr-remapping.
> [0.048426] DMAR-IR: Enabled IRQ remapping in x2apic mode
> [0.794120] DMAR: No ATSR found
> [0.794149] DMAR: dmar0: Using Queued invalidation
> [0.794154] DMAR: dmar1: Using Queued invalidation
> [0.863652] DMAR: Intel(R) Virtualization Technology for Directed I/O
> [0.867732] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel 
>
> [0.867733] AMD-Vi: AMD IOMMUv2 functionality not available on this
> system
> [1.250394] i915 :00:02.0: [drm] DMAR active, disabling use of
> stolen memory
>
> buster no intel_iommu setting:
> dmesg | grep -e DMAR -e IOMMU
> [0.009193] ACPI: DMAR 0xD8FFEAE8 B8 (v01 INTEL  HSW
>  0001 INTL 0001)
> [0.192242] DMAR: Host address width 39
> [0.192243] DMAR: DRHD base: 0x00fed9 flags: 0x0
> [0.192246] DMAR: dmar0: reg_base_addr fed9 ver 1:0 cap
> c020660462 ecap f0101a
> [0.192246] DMAR: DRHD base: 0x00fed91000 flags: 0x1
> [0.192248] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
> d2008020660462 ecap f010da
> [0.192249] DMAR: RMRR base: 0x00dbcf6000 end: 0x00dbd03fff
> [0.192249] DMAR: RMRR base: 0x00dd00 end: 0x00df1f
> [0.192251] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
> [0.192251] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
> [0.192252] DMAR-IR: Queued invalidation will be enabled to support
> x2apic and Intr-remapping.
> [0.192637] DMAR-IR: Enabled IRQ remapping in x2apic mode
> [0.846867] AMD 

Bug#990660: open-vm-tools: possible leftover /etc/vmware-tools/tools.conf.old on purge

[Christoph Anton Mitterer]

Package: open-vm-tools
Version: 2:11.2.5-2
Severity: normal


Hey.

I've noted that on all my systms I have a file:
/etc/vmware-tools/tools.conf.old

which is left over on purging the package:
Purging configuration files for open-vm-tools (2:11.2.5-2) ...
dpkg: warning: while removing open-vm-tools, directory '/etc/vmware-tools' not 
empty so not removed


The file is pretty old (2011) but I don't think I've ever
created this mysel.
OTOH, I couldn't find (okay I did just some quick greps) any
references to it in the current source package.


So maybe this is a non-issue (then simply close it)... but
if you know any way how this file would still get created
by the current package (maybe some of the CLI tools?) than
it would be nice if it could get cleaned up on purge.


Thanks,
Chris.

Bug#990650: nxagent in shadow mode causes a segfault (since 3.5.99.26-1)

[Mike Gabriel]

Package: nxagent
Version: 3.5.99.26-1
Severity: important
Tags: patch
Fixed: 3.5.99.25-1

For some unknown reason, upstream discovered a regression in nxagent  
(aka x2goagent with X2Go). When connecting to an existing X11 session  
("connect to local desktop"), one gets an nxagent/x2goagent crash:

```
Stack trace of thread 663053:
#0  0x5f237a3f4f0b RREditConnectionInfo (nxagent  
+ 0x32ff0b)
#1  0x5f237a17f840 nxagentChangeScreenConfig  
(nxagent + 0xba840)
#2  0x5f237a16d2e9 nxagentDispatchEvents (nxagent  
+ 0xa82e9)
#3  0x5f237a167e2d nxagentDisplayWriteHandler  
(nxagent + 0xa2e2d)
#4  0x79af2a8bf6f1 _XSendClientPrefix  
(libX11.so.6 + 0x266f1)

#5  0x79af2a8d2cd4 XOpenDisplay (libX11.so.6 + 0x39cd4)
#6  0x79af2a74a9a4 _ZN6Poller4initEv  
(libXcompshad.so.3 + 0x99a4)
#7  0x79af2a74806c NXShadowCreate  
(libXcompshad.so.3 + 0x706c)

#8  0x5f237a17f92a nxagentShadowInit (nxagent + 0xba92a)
#9  0x5f237a1172fb DefineInitialRootWindow  
(nxagent + 0x522fb)

#10 0x5f237a1079f0 main (nxagent + 0x429f0)
#11 0x79af2a0ab082 __libc_start_main (libc.so.6 + 0x27082)
#12 0x5f237a107d7e _start (nxagent + 0x42d7e)
```

It is 100% reproducible, 3.5.99.25 worked fine.

The upstream issue is at https://github.com/ArcticaProject/nx-libs/issues/1009

Patch for this (a commit backported from X.Org) is attached.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

>From a14e1a59a4025cbb464b5deeed0f50d5a2898b0c Mon Sep 17 00:00:00 2001
From: Ulrich Sibiller 
Date: Wed, 17 Mar 2021 21:16:26 +0100
Subject: [PATCH] randr: Do not update ConnectionInfo if NULL

Backport of this xorg-xserver commit:

  commit 941aeb3b92e644923bd112eef8023f033a140ee6
  Author: Olivier Fourdan 
  Date:   Fri May 13 08:58:58 2016 +0200

randr: Do not update ConnectionInfo if NULL

RRScreenSizeNotify() will update the connection information block, but
if this occurs during initialization before ConnectionInfo is even
initialized, this will lead to a crash.

Simply check for ConnectionInfo prior to update it to avoid the crash.

Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=95337
Reviewed-by: Adam Jackson 
Signed-off-by: Olivier Fourdan 

Fixes ArcticaProject/nx-libs#1009

Signed-off-by: Mike Gabriel 
---
 nx-X11/programs/Xserver/randr/rrscreen.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/nx-X11/programs/Xserver/randr/rrscreen.c 
b/nx-X11/programs/Xserver/randr/rrscreen.c
index 4f59e9aea..90371704a 100644
--- a/nx-X11/programs/Xserver/randr/rrscreen.c
+++ b/nx-X11/programs/Xserver/randr/rrscreen.c
@@ -66,6 +66,9 @@ RREditConnectionInfo(ScreenPtr pScreen)
 int screen = 0;
 int d;
 
+if (ConnectionInfo == NULL)
+return;
+
 connSetup = (xConnSetup *) ConnectionInfo;
 vendor = (char *) connSetup + sizeof(xConnSetup);
 formats = (xPixmapFormat *) ((char *) vendor +
-- 
2.30.2



pgpCmfF0pKVw3.pgp
Description: Digitale PGP-Signatur

Bug#990649: nxagent: Tricky minimize/maximize/restore issue in rootless mode

[Mike Gabriel]

Package: nxagent
Version: 3.5.99.26-1
Serverity: important
Tags: patch

When running nxagent in rootless mode (e.g. for published server-side  
applications), X clients that don't use a window manager but prefer  
client side rendered window management controls in some case can't be  
closed, maximized, restored, etc.


The reason for this is a wrong translation of XIDs in nxagent for  
rootless session windows.


The full story is here:
https://github.com/ArcticaProject/nx-libs/issues/1015

Patch to fix this is attached.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

>From 36f804e549121fb56aa71979b7da5d75f2cc7cbe Mon Sep 17 00:00:00 2001
From: Ulrich Sibiller 
Date: Sun, 2 May 2021 18:42:44 +0200
Subject: [PATCH] Forward ClientMessages to nxproxy side

This should help with clients requesting window manager actions like
maximizing or minimizing. This is a first version as it only handles
messages of type WM_STATE_CHANGE and _NET_WM_STATE. But ICCCM and EWMH
know some more.

The other direction, setting of properties by the WM, is already
implemented in Rootless.c.

Fixes ArcticaProject/nx-libs#1015

Signed-off-by: Mike Gabriel 
---
 nx-X11/programs/Xserver/hw/nxagent/Events.c   | 64 +++
 nx-X11/programs/Xserver/hw/nxagent/Events.h   |  2 +
 nx-X11/programs/Xserver/hw/nxagent/NXevents.c |  6 ++
 3 files changed, 72 insertions(+)

diff --git a/nx-X11/programs/Xserver/hw/nxagent/Events.c 
b/nx-X11/programs/Xserver/hw/nxagent/Events.c
index a342cdee1..2a3654731 100644
--- a/nx-X11/programs/Xserver/hw/nxagent/Events.c
+++ b/nx-X11/programs/Xserver/hw/nxagent/Events.c
@@ -4505,6 +4505,70 @@ int nxagentWaitEvents(Display *dpy, useconds_t msec)
   return 1;
 }
 
+void ForwardClientMessage(ClientPtr client, xSendEventReq *stuff)
+{
+Atom netwmstate = MakeAtom("_NET_WM_STATE", strlen("_NET_WM_STATE"), 
False);
+Atom wmchangestate = MakeAtom("WM_CHANGE_STATE", 
strlen("WM_CHANGE_STATE"), False);
+WindowPtr pWin = (WindowPtr)SecurityLookupWindow(stuff->destination, 
client,
+ DixReadAccess);
+
+if (stuff->event.u.clientMessage.u.l.type == netwmstate || 
stuff->event.u.clientMessage.u.l.type == wmchangestate)
+{
+if (pWin->drawable.id == pWin->drawable.pScreen->root->drawable.id)
+{
+#ifdef DEBUG
+fprintf(stderr, "%s: dest [0x%x] window [0x%x] clmsg.type 
[%d]->[%d]\n", __func__, stuff->destination, 
stuff->event.u.clientMessage.window, stuff->event.u.clientMessage.u.l.type, 
nxagentLocalToRemoteAtom(stuff->event.u.clientMessage.u.l.type));
+#endif
+
+XEvent X = {0};
+X.xany.type = ClientMessage;
+
+WindowPtr pWin2 = 
(WindowPtr)SecurityLookupWindow(stuff->event.u.clientMessage.window, client,
+  DixReadAccess);
+X.xclient.window = nxagentWindowPriv(pWin2)->window;
+X.xclient.format = stuff->event.u.u.detail;
+X.xclient.send_event = True;
+X.xclient.serial = 0;
+
+if (X.xclient.format == 32)
+{
+X.xclient.message_type = 
nxagentLocalToRemoteAtom(stuff->event.u.clientMessage.u.l.type);
+X.xclient.data.l[0] = stuff->event.u.clientMessage.u.l.longs0;
+X.xclient.data.l[1] = 
nxagentLocalToRemoteAtom(stuff->event.u.clientMessage.u.l.longs1);
+X.xclient.data.l[2] = 
nxagentLocalToRemoteAtom(stuff->event.u.clientMessage.u.l.longs2);
+X.xclient.data.l[3] = 
nxagentLocalToRemoteAtom(stuff->event.u.clientMessage.u.l.longs3);
+X.xclient.data.l[4] = 
nxagentLocalToRemoteAtom(stuff->event.u.clientMessage.u.l.longs4);
+//X.xclient.data.l[3] = 
stuff->event.u.clientMessage.u.l.longs3;
+//X.xclient.data.l[4] = 
stuff->event.u.clientMessage.u.l.longs4;
+#ifdef DEBUG
+for (int i = 0; i < 5; i++)
+{
+fprintf(stderr, "%s: data[%d] [%ld]\n", __func__, i, 
X.xclient.data.l[i]);
+}
+#endif
+}
+else
+return; // ERROR!
+
+#ifdef DEBUG
+fprintf(stderr, "%s: window [0x%lx]\n", __func__, 
X.xclient.window);
+fprintf(stderr, "%s: message_type [%ld]\n", __func__, 
X.xclient.message_type);
+fprintf(stderr, "%s: format [%d]\n", __func__, X.xclient.format);
+#endif
+
+XlibWindow dest;
+dest = DefaultRootWindow(nxagentDisplay);
+
+Status stat = XSendEvent(nxagentDisplay, dest, stuff->propagate, 
stuff->eventMask, );
+   

Bug#990659: qemu-system-misc: qemu-riscv64-static sometimes crashes while running gcc in chroot

[Rich Ercolani]

Package: qemu-system-misc
Version: 1:5.2+dfsg-9~bpo10+1
Severity: normal

I was assembling a Debian riscv64 (and therefore, currently, sid) root FS to 
test something, ultimately in a VM, and building OpenZFS git master chrooted 
into that root to that end.

I did the ./autogen.sh && ./configure --with-linux=.../source 
--with-linux-obj=.../build && make dance, left it alone for a bit, and came to 
curiously
find it errored out with no error output printed that I saw.

Ran make again, it did not immediately error.

I then noticed in dmesg:

[1726926.715475] cc1[66416]: segfault at 2ad48a0 ip 004857e0 sp 
7ffc9ef97948 error 4 in qemu-riscv64-static[401000+2cc000]
[1726926.715488] Code: 00 e9 24 fc 18 00 0f 1f 40 00 64 83 2c 25 60 ff ff ff 01 
74 05 c3 0f 1f 40 00 48 8d 3d c9 6f 77 00 e9 74 0a 19 00 0f 1f 40 00 <64> 8b 04 
25 60 ff ff ff 85 c0 0f 9f c0 c3 66 90 48 83 ec 08 64 8b
[1726967.092517] cc1[71234]: segfault at 2ad58a0 ip 004857e0 sp 
7ffc23573a18 error 4 in qemu-riscv64-static[401000+2cc000]
[1726967.092530] Code: 00 e9 24 fc 18 00 0f 1f 40 00 64 83 2c 25 60 ff ff ff 01 
74 05 c3 0f 1f 40 00 48 8d 3d c9 6f 77 00 e9 74 0a 19 00 0f 1f 40 00 <64> 8b 04 
25 60 ff ff ff 85 c0 0f 9f c0 c3 66 90 48 83 ec 08 64 8b

(There's a couple more.)

(Much later on, gcc ICEd, on something it hadn't tried building before, but 
that didn't reproduce on running it again...)

I have a core, from doing this dance a second time, from yet another source 
file that built fine on successive runs, but I'm not sure how readily useful it 
is. I'll upload it if it would be helpful.

- Rich

-- System Information:
Debian Release: 10.10
  APT prefers stable-updates
  APT policy: (1000, 'stable-updates'), (1000, 'stable'), (900, 
'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), 
(500, 'stable-debug'), (500, 'proposed-updates-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages qemu-system-misc depends on:
ii  libaio1  0.3.112-3
ii  libasound2   1.1.8-1
ii  libbrlapi0.6 5.6-10+deb10u1
ii  libc62.28-10
ii  libcacard0   1:2.6.1-1
ii  libcapstone4 4.0.2-3
ii  libepoxy01.5.3-0.1
ii  libfdt1  1.6.0-1~bpo10+1
ii  libgbm1  18.3.6-2+deb10u1
ii  libgcc-s1 [libgcc1]  10.2.1-6
ii  libgcc1  1:8.3.0-6
ii  libglib2.0-0 2.58.3-2+deb10u3
ii  libgnutls30  3.6.7-4+deb10u7
ii  libibverbs1  22.1-1
ii  libjpeg62-turbo  1:1.5.2-2+deb10u1
ii  libncursesw6 6.1+20181013-2+deb10u2
ii  libnettle6   3.4.1-1+deb10u1
ii  libnuma1 2.0.12-1
ii  libpixman-1-00.36.0-1
ii  libpmem1 1.5.1-1
ii  libpng16-16  1.6.36-6
ii  librdmacm1   22.1-1
ii  libsasl2-2   2.1.27+dfsg-1+deb10u1
ii  libseccomp2  2.3.3-4
ii  libslirp04.4.0-1
ii  libspice-server1 0.14.0-1.3+deb10u1
ii  libtinfo66.1+20181013-2+deb10u2
ii  libudev1 241-7~deb10u7
ii  liburing10.7-3
ii  libusb-1.0-0 2:1.0.22-2
ii  libusbredirparser1   0.8.0-1
ii  libvdeplug2  2.3.2+r586-2.2
ii  libvirglrenderer00.7.0-2
ii  qemu-system-common   1:5.2+dfsg-9~bpo10+1
ii  qemu-system-data 1:5.2+dfsg-9~bpo10+1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages qemu-system-misc recommends:
ii  ipxe-qemu1.0.0+git-20190125.36a4c85-1
ii  qemu-system-gui  1:5.2+dfsg-9~bpo10+1
ii  qemu-utils   1:5.2+dfsg-9~bpo10+1
ii  seabios  1.12.0-1

Versions of packages qemu-system-misc suggests:
pn  qemu-block-extra  
ii  samba 2:4.9.5+dfsg-5+deb10u1
ii  vde2  2.3.2+r586-2.2

-- no debconf information

Bug#990658: apache2-doc: legacy conffiles leftover

[Christoph Anton Mitterer]

Package: apache2-doc
Version: 2.4.46-2
Severity: normal


Hi.

Apparently the package used to contain the conffiles:
/etc/apache2/conf.d/apache2-doc
but no longer does so.

Please properly clean them up using dpkg-maintscript-helper(1).
(AFAIU, the version that needs to be specified for that is NOT
the version where the conffile was dropped, but rather "the
latest version of the package whose upgrade should trigger
the operation"

Quoting the manpage:
   For example, for a conffile removed in version 2.0-1 of a package,
   prior-version should be set to 2.0-1~. This will cause the conffile
   to be removed even if the user rebuilt the previous version 1.0-1
   as 1.0-1local1. Or a package switching a path from a symlink
   (shipped in version 1.0-1) to a directory (shipped in version
   2.0-1), but only performing the actual switch in the maintainer
   scripts in version 3.0-1, should set prior-version to 3.0-1~.



Also, it hadn't "registered" /etc/reader.conf.d/ so that will probably be left
over, too, unless some other package that contains it is installed (like 
libccid).


Cheers,
Chris.

Bug#990069: openssh-server: Not accepting new connections during Debian 10 -> 11 upgrade

[Colin Watson]

Control: reassign -1 libc6 2.31-12
Control: affects -1 openssh-server

On Sat, Jul 03, 2021 at 11:36:49AM +0200, Olaf van der Spek wrote:
> Op zo 20 jun. 2021 om 10:38 schreef Olaf van der Spek :
> > So I think it's not accepting new connections from the start of the
> > upgrade run until the end:
> > Setting up openssh-sftp-server (1:8.4p1-5) ...
> > Setting up console-setup (1.203) ...
> > Setting up mime-support (3.66) ...
> > Setting up openssh-server (1:8.4p1-5) ...
> > Installing new version of config file /etc/init.d/ssh ...
> > Installing new version of config file /etc/ssh/moduli ...
> > Replacing config file /etc/ssh/sshd_config with new version
> > rescue-ssh.target is a disabled or a static unit, not starting it.
> 
> Hi Colin,
> 
> Any thoughts on this?

Sorry for my delay - it took me a while to spot the problem.  libc6's
postinst does arrange to restart services where needed, but in this case
it doesn't realize that you have the ssh service installed because you
only have the openssh-server package installed, not the ssh metapackage
(i.e. the package with the same name as the service).

I've proposed
https://salsa.debian.org/glibc-team/glibc/-/merge_requests/3 to fix
this.  glibc maintainers, if there's any way to get this into bullseye,
I'm sure it would help avoid some people upgrading remote systems ending
up being unable to fix them if something goes wrong between configuring
libc6 and configuring openssh-server.  Also CCing debian-release for
their information, as I know it's pretty late for glibc changes.

-- 
Colin Watson (he/him)  [cjwat...@debian.org]

Bug#989045: gnome-control-center: Region+Language panel segfault after trying to add new input source

[Gunnar Hjalmarsson]

Hi Will,

I suspect this is same as .

Can you please run this terminal command:

gsettings get org.gnome.desktop.input-sources show-all-sources

and let us know what it outputs. If the value is "true", can you change 
it to "false" via this command:


gsettings reset org.gnome.desktop.input-sources show-all-sources

and let us know if the crash still happens.

--
Rgds,
Gunnar Hjalmarsson

Bug#990647: nxagent: in Compext.c: fix comparisons of 16bit sequence numbers

[Mike Gabriel]

Package: nxagent
Severity: important
Version: 3.5.99.26-1
Tags: patch

In Compext.c a flawed comparison has been discovered lately by Ulrich  
Sibiller and Norm Green.


From the commit message:

```
rep->generic.sequenceNumber is of type CARD16
state->sequence is of type unsigned long

Converting state->sequence to an int as it has been done since the
first version of nxcomp I know of (1.3.0-18 from 2003) is wrong here
because for numbers > INT_MAX this will result in a negative number,
which, after applying the 16bit modulo, will not match
rep->generic.sequenceNumber.

Example with numbers:

CARD16 c = 24565
unsigned long u = 3179110389

c % 65536 = 24565
u % 65536 = 24565

(int)(u) = -1115856907
(int)(u) % 65536 = -40971

-40971 will not match 24565

To fix this we need to ensure the number stays positive. We use CARD16
for this to match the type in the request which is a 16bit number. On
my system CARD16 is unsigned short which is guaranteed to contain _at
least_ the 0-65,535 range. As there is no upper limit of the range we
cannot drop the modulo because we need this value to be 16bit and not
more.

Thanks to Norm Green for providing log after log until we could
finally identify the reason for him seeing "Xlib: unexpected async
reply (sequence 0x94b01439)!" when pasting stopped working.
```

Patch for this has been attached.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

>From 1b4ebce2ce8ef29c01bd124ed56c9d6a14c9a82d Mon Sep 17 00:00:00 2001
From: Ulrich Sibiller 
Date: Wed, 17 Mar 2021 22:17:55 +0100
Subject: [PATCH] Compext.c: fix comparisons of 16bit sequence numbers

rep->generic.sequenceNumber is of type CARD16
state->sequence is of type unsigned long

Converting state->sequence to an int as it has been done since the
first version of nxcomp I know of (1.3.0-18 from 2003) is wrong here
because for numbers > INT_MAX this will result in a negative number,
which, after applying the 16bit modulo, will not match
rep->generic.sequenceNumber.

Example with numbers:

CARD16 c = 24565
unsigned long u = 3179110389

c % 65536 = 24565
u % 65536 = 24565

(int)(u) = -1115856907
(int)(u) % 65536 = -40971

-40971 will not match 24565

To fix this we need to ensure the number stays positive. We use CARD16
for this to match the type in the request which is a 16bit number. On
my system CARD16 is unsigned short which is guaranteed to contain _at
least_ the 0-65,535 range. As there is no upper limit of the range we
cannot drop the modulo because we need this value to be 16bit and not
more.

Thanks to Norm Green for providing log after log until we could
finally identify the reason for him seeing "Xlib: unexpected async
reply (sequence 0x94b01439)!" when pasting stopped working.

Signed-off-by: Mike Gabriel 
---
 nx-X11/programs/Xserver/hw/nxagent/compext/Compext.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/nx-X11/programs/Xserver/hw/nxagent/compext/Compext.c 
b/nx-X11/programs/Xserver/hw/nxagent/compext/Compext.c
index 4a8dacaf4..7a6cb9e30 100644
--- a/nx-X11/programs/Xserver/hw/nxagent/compext/Compext.c
+++ b/nx-X11/programs/Xserver/hw/nxagent/compext/Compext.c
@@ -3435,7 +3435,7 @@ static Bool _NXCollectImageHandler(Display *dpy, xReply 
*rep, char *buf,
   state = (_NXCollectImageState *) data;
 
   if ((rep -> generic.sequenceNumber % 65536) !=
-  ((int)(state -> sequence) % 65536))
+  ((CARD16)(state -> sequence) % 65536))
   {
 #ifdef TEST
 fprintf(stderr, "**_NXCollectImageHandler: Unmatched sequence [%d] for 
opcode [%d] "
@@ -3819,7 +3819,7 @@ static Bool _NXCollectPropertyHandler(Display *dpy, 
xReply *rep, char *buf,
   state = (_NXCollectPropertyState *) data;
 
   if ((rep -> generic.sequenceNumber % 65536) !=
-  ((int)(state -> sequence) % 65536))
+  ((CARD16)(state -> sequence) % 65536))
   {
 #ifdef TEST
 fprintf(stderr, "**_NXCollectPropertyHandler: Unmatched sequence [%d] 
for opcode [%d] "
@@ -4173,7 +4173,7 @@ static Bool _NXCollectGrabPointerHandler(Display *dpy, 
xReply *rep, char *buf,
   state = (_NXCollectGrabPointerState *) data;
 
   if ((rep -> generic.sequenceNumber % 65536) !=
-  ((int)(state -> sequence) % 65536))
+  ((CARD16)(state -> sequence) % 65536))
   {
 #ifdef TEST
 fprintf(stderr, "**_NXCollectGrabPointerHandler: Unmatched sequence 
[%d] for opcode [%d] "
@@ -4447,7 +4447,7 @@ static Bool _NXCollectInputFocusHandler(Display *dpy, 
xReply *rep, char *buf,
   state = (_NXCollectInputFocusState *) data;
 
   if ((rep -> generic.sequenceNumber % 65536) !=
-  ((int)(state -> sequence) % 65536))
+  ((CARD16)(state -> sequence) % 65536))
   {
 #ifdef TEST
 fprintf(stderr, 

Bug#990636: qgis not listed as file browser alternative for opening kml files

[Petter Reinholdtsen]

[Sebastiaan Couwenberg]
> Are you sure qgis supports opening KML?

Yes.

> When I open one of the example KML files from libkml-dev with qgis it
> shows an Invalid Data Source error.

Right.  The KML file I work on was detected as such, and qgis showed the
point placemarks (but not the MultiGeometry/Polygon placemarks :).
This make me believe qgis understand KML at a useful level.

Looked for official documentation on qgis and kml, but failed.
http://maps.cga.harvard.edu/qgis/import/kml/ > provide some
insights, though.

-- 
Happy hacking
Petter Reinholdtsen

Bug#990296: linux-image-5.10.0-7-amd64: Bluetooth device not detected by kernel.

[Salvatore Bonaccorso]

Control: forcemerge 977299 -1

On Tue, Jun 29, 2021 at 03:45:49PM +0200, N. wrote:
> Hi Salvatore,
> the bug is the same as mentioned at this link on last lines of the article
> post -> https://github.com/spxak1/weywot/blob/main/ax210.md
> 
> The Intel AX210 Wifi/Bluetooth chipset provided on Asus Rog Maximus
> XIII mother board seems to be not fully supported on kernel linux 5.10.0-7.
> Wifi was not working after installing Debian 11 Testing, but after renaming
> /lib/firmware/iwlwifi-ty-a0-gf-a0.pnvm (so this file was not loaded on
> boot) wifi works ! But bluetooth still have issue because kernel does not
> detect firmware file (seems that kernel does not recognize firmware version
> because it not support  *Intel Typhoon Peak Bluetooth, USB ID 8087:0032*
> properly).
> Googling the issue seems that kernel 5.11 will be fully supported Intel
> AX210 chipset. Am I wrong ?
> 
> On mail attachment some bluetooth log.
> Sry for mine duplicate  email to your debian dev address.

No worries.

Thanks for your followup to the report. So I'm merging for now both
your's and #977299 report.

For a quick look: First part of it was fixed in 5.10-rc7 including
some missing entries for AX210. firmware-nonfree since 20210315-1~exp1
has "linux-firmware: Update firmware file for Intel Bluetooth AX210".
The "Typhoon Peak Bluetooth" support is only added in 5.11.

Regards,
Salvatore

Bug#990657: python3-dnf-doc: broken symlinks: /usr/share/doc/python3-dnf-doc/html/_static/{jquery,underscore}.js

[Andreas Beckmann]

Package: python3-dnf-doc
Version: 4.5.2-6
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m12.8s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python3-dnf-doc/html/_static/jquery.js -> 
../../../../javascript/jquery/jquery.js (python3-dnf-doc)
  /usr/share/doc/python3-dnf-doc/html/_static/underscore.js -> 
../../../../javascript/underscore/underscore.js (python3-dnf-doc)

The package already uses ${sphinxdoc:Depends}, but that does not seem
to get populated.


cheers,

Andreas


python3-dnf-doc_4.5.2-6.log.gz
Description: application/gzip

Bug#990656: python-rlp-doc: broken symlinks: /usr/share/doc/python-rlp-doc/html/_static/*.js -> ../../../../javascript/sphinxdoc/1.0/*.js

[Andreas Beckmann]

Package: python-rlp-doc
Version: 0.5.1-1.2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m12.5s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python-rlp-doc/html/_static/doctools.js -> 
../../../../javascript/sphinxdoc/1.0/doctools.js (python-rlp-doc)
  /usr/share/doc/python-rlp-doc/html/_static/jquery.js -> 
../../../../javascript/sphinxdoc/1.0/jquery.js (python-rlp-doc)
  /usr/share/doc/python-rlp-doc/html/_static/searchtools.js -> 
../../../../javascript/sphinxdoc/1.0/searchtools.js (python-rlp-doc)
  /usr/share/doc/python-rlp-doc/html/_static/sidebar.js -> 
../../../../javascript/sphinxdoc/1.0/sidebar.js (python-rlp-doc)
  /usr/share/doc/python-rlp-doc/html/_static/underscore.js -> 
../../../../javascript/sphinxdoc/1.0/underscore.js (python-rlp-doc)

You could use the substvars provided by sphinxdoc to get the missing 
dependencies:

dpkg-gencontrol: warning: package python-rlp-doc: substitution variable 
${sphinxdoc:Built-Using} unused, but is defined
dpkg-gencontrol: warning: package python-rlp-doc: substitution variable 
${sphinxdoc:Depends} unused, but is defined


cheers,

Andreas


python-rlp-doc_0.5.1-1.2.log.gz
Description: application/gzip

Bug#990655: python-qpid-proton-doc: roken symlinks: /usr/share/doc/python-qpid-proton-doc/html/_static/*.js -> ../../../../javascript/sphinxdoc/1.0/*.js

[Andreas Beckmann]

Package: python-qpid-proton-doc
Version: 0.22.0-5.1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m10.8s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python-qpid-proton-doc/html/_static/doctools.js -> 
../../../../javascript/sphinxdoc/1.0/doctools.js (python-qpid-proton-doc)
  /usr/share/doc/python-qpid-proton-doc/html/_static/jquery.js -> 
../../../../javascript/sphinxdoc/1.0/jquery.js (python-qpid-proton-doc)
  /usr/share/doc/python-qpid-proton-doc/html/_static/language_data.js -> 
../../../../javascript/sphinxdoc/1.0/language_data.js (python-qpid-proton-doc)
  /usr/share/doc/python-qpid-proton-doc/html/_static/searchtools.js -> 
../../../../javascript/sphinxdoc/1.0/searchtools.js (python-qpid-proton-doc)
  /usr/share/doc/python-qpid-proton-doc/html/_static/underscore.js -> 
../../../../javascript/sphinxdoc/1.0/underscore.js (python-qpid-proton-doc)

You could use the substvars provided by sphinxdoc to get the missing 
dependencies:

dpkg-gencontrol: warning: package python-qpid-proton-doc: substitution variable 
${sphinxdoc:Built-Using} unused, but is defined
dpkg-gencontrol: warning: package python-qpid-proton-doc: substitution variable 
${sphinxdoc:Depends} unused, but is defined


cheers,

Andreas


python-qpid-proton-doc_0.22.0-5.1.log.gz
Description: application/gzip

Bug#990654: python-automaton-doc: broken symlinks: /usr/share/doc/python-automaton-doc/html/_static/*.js -> ../../../../javascript/sphinxdoc/1.0/*.js

[Andreas Beckmann]

Package: python-automaton-doc
Version: 2.2.0-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m11.2s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python-automaton-doc/html/_static/doctools.js -> 
../../../../javascript/sphinxdoc/1.0/doctools.js (python-automaton-doc)
  /usr/share/doc/python-automaton-doc/html/_static/jquery.js -> 
../../../../javascript/sphinxdoc/1.0/jquery.js (python-automaton-doc)
  /usr/share/doc/python-automaton-doc/html/_static/language_data.js -> 
../../../../javascript/sphinxdoc/1.0/language_data.js (python-automaton-doc)
  /usr/share/doc/python-automaton-doc/html/_static/searchtools.js -> 
../../../../javascript/sphinxdoc/1.0/searchtools.js (python-automaton-doc)
  /usr/share/doc/python-automaton-doc/html/_static/underscore.js -> 
../../../../javascript/sphinxdoc/1.0/underscore.js (python-automaton-doc)

You could use the substvars provided by sphinxdoc to get the missing 
dependencies:

dpkg-gencontrol: warning: package python-automaton-doc: substitution variable 
${sphinxdoc:Built-Using} unused, but is defined
dpkg-gencontrol: warning: package python-automaton-doc: substitution variable 
${sphinxdoc:Depends} unused, but is defined


cheers,

Andreas


python-automaton-doc_2.2.0-2.log.gz
Description: application/gzip

Bug#990653: rdkit-doc: broken symlinks: /usr/share/doc/rdkit/html/_static/{jquery,underscore}.js

[Andreas Beckmann]

Package: rdkit-doc
Version: 202009.4-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m12.6s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/rdkit/html/_static/jquery.js -> 
../../../../javascript/jquery/jquery.js (rdkit-doc)
  /usr/share/doc/rdkit/html/_static/underscore.js -> 
../../../../javascript/underscore/underscore.js (rdkit-doc)
  /usr/share/doc/rdkit/html/cppapi/jquery.js -> 
../../../../javascript/jquery/jquery.js (rdkit-doc)

Is rdkit-doc missing dependencies on libjs-jquery, libjs-underscore ?


cheers,

Andreas


rdkit-doc_202009.4-1.log.gz
Description: application/gzip

Bug#990652: python-aiohttp-doc: broken symlinks: /usr/share/doc/python-aiohttp-doc/html/_static/*.js -> ../../../../javascript/sphinxdoc/1.0/*.js

[Andreas Beckmann]

Package: python-aiohttp-doc
Version: 3.7.4-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

>From the attached log (scroll to the bottom...):

0m10.4s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/python-aiohttp-doc/html/_static/doctools.js -> 
../../../../javascript/sphinxdoc/1.0/doctools.js (python-aiohttp-doc)
  /usr/share/doc/python-aiohttp-doc/html/_static/jquery.js -> 
../../../../javascript/sphinxdoc/1.0/jquery.js (python-aiohttp-doc)
  /usr/share/doc/python-aiohttp-doc/html/_static/language_data.js -> 
../../../../javascript/sphinxdoc/1.0/language_data.js (python-aiohttp-doc)
  /usr/share/doc/python-aiohttp-doc/html/_static/searchtools.js -> 
../../../../javascript/sphinxdoc/1.0/searchtools.js (python-aiohttp-doc)
  /usr/share/doc/python-aiohttp-doc/html/_static/underscore.js -> 
../../../../javascript/sphinxdoc/1.0/underscore.js (python-aiohttp-doc)

You could use the substvars provided by sphinxdoc to get the missing 
dependencies:

dpkg-gencontrol: warning: package python-aiohttp-doc: substitution variable 
${sphinxdoc:Built-Using} unused, but is defined
dpkg-gencontrol: warning: package python-aiohttp-doc: substitution variable 
${sphinxdoc:Depends} unused, but is defined


cheers,

Andreas


python-aiohttp-doc_3.7.4-1.log.gz
Description: application/gzip

Bug#977832: fix

[Thomas Lange]

This is the fix for this bug.

https://github.com/faiproject/fai/commit/3ec672e709283fa7ebc668b1a8b7328b60858e08
-- 
viele Grüße Thomas

Bug#990630: unblock: fuse3/3.10.3-2

[Paul Gevers]

Control: tags -1 d-i

Hi

On 03-07-2021 07:17, László Böszörményi (GCS) wrote:
> [ Other info ]
> Builds an udeb and needs a d-i hint as well.

So, let's make kibi aware of this too (via boot).

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#990651: unblock: nx-libs/2:3.5.99.26-2

[Mike Gabriel]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package nx-libs

[ Reason ]
Several important upstream issues have recently been resolved in nx-libs.
The fixes for those issues have been cherry-picked into this version of
Debian's nx-libs package.

+  * debian/patches:
++ Add 0001_Compext.c-fix-comparisons-of-16bit-sequence-numbers.patch.
+  Compext.c: fix comparisons of 16bit sequence numbers. (Closes:
+  #990647).

-> Fixes flawed 16 bit comparison. This resolves an "Xlib: unexpected async
reply (sequence 0x94b01439)!" and clipboard pasting being broken afterwards.

++ Add 0002_Forward-ClientMessages-to-nxproxy-side.patch.
+  Forward ClientMessages to nxproxy side. (Closes: #990649).

-> Resolve window control problems with client side decorated windows if
nxagent is used in rootless/seamless session mode.

++ Add 0003_randr-Do-not-update-ConnectionInfo-if-NULL.patch.
+  randr: Do not update ConnectionInfo if NULL (and avoid the nxagent
+  Xserver from crashing). (Closes: #990650).

-> Regression fix of unknown origin. Could be resolved by cherry-picking
a commit original from X.Org upstream. 

++ Add 0004_document-additional-options-only-nxagent-knows-about.patch.
+  Update man page and --help documentation of nxproxy/nxagent.

-> Recently, upstream added a documentation improvement that now
documents various session options that were undocumented before.

++ Adjust 0004_document-additional-options-only-nxagent-knows-about.patch.
+  Version 3.5.99.26 does not yet have the textclipboard= session
+  parameter.

-> The above patch added one option that is not yet available in 3.5.99.26,
So we removed this bit of documenation for nx-libs in Debian (bullseye).


[ Impact ]
The "connect to local X11 desktop" (shadow session support) would be broken, 

The clipboard between nxagent and the local Xserver might break in some 
situations.

There would be problems with client side decorated windows.

There would be undocumented options.

[ Tests ]
Manual tests.

[ Risks ]
X2Go sessions being busted if some of the above commits is flawed.

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

[ Other info ]
None.

unblock nx-libs/2:3.5.99.26-2

Bug#986109: RM: libgtk2-perl -- ROM; Deprecated upstream + GNOME team's goal of reducing gtk2 use in Debian

[Sean Whitton]

control: tag -1 + moreinfo

Hello intrigeri,

On Mon 29 Mar 2021 at 07:10PM +02, intrigeri wrote:

> I'm hereby requesting removal of libgtk2-perl, as one of its maintainers,
> and of its remaining 4 reverse-dependencies, as the last step of a plan
> that was communicated to the relevant maintainers years ago.

Could we have separate blocking bugs for these, please?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#986107: RM: libparse-keyword-perl -- ROM; Upstream says "DO NOT USE!", no significant usage in Debian

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Mon 29 Mar 2021 at 06:32PM +02, intrigeri wrote:

> Please let me know if you'd like me to file removal requests for these
> 4 packages as well.

Yes please, and kindly remove the moreinfo tag from this bug when done.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#990648: uclibc-source: CVE-2016-2224, CVE-2016-2225, CVE-2016-6264

[Andreas Beckmann]

Package: uclibc-source
Version: 0.9.32-1
Severity: normal
Tags: security
User: debian...@lists.debian.org
Usertags: piuparts
Control: fixed -1 0.9.32-1+deb7u1
Control: close -1 1.0.20-1

   * CVE-2016-2224:
 Fix possible denial of service via a specially crafted DNS reply that could
 cause an infinite loop.
   * CVE-2016-2225:
 Fix possible denial of service via specially crafted packet that will make
 the parser terminate early.
   * CVE-2016-6264:
 It was found that 'BLT' instruction in libc/string/arm/memset.S checks for
 signed values. If parameter of memset is negative, then value added to the
 PC will be large. Attacker that controls the length parameter of memset can
 also control the value of PC register.

This was fixed in wheezy-lts, but not in jessie-security or jessie-lts,
causing version skew:

 uclibc | 0.9.30.2-1  | squeeze | source
 uclibc | 0.9.32-1| wheezy  | source
 uclibc | 0.9.32-1| jessie  | source
 uclibc | 0.9.32-1+deb7u1 | wheezy-security | source
 uclibc | 1.0.20-2| stretch | source
 uclibc | 1.0.31-1| buster  | source
 uclibc | 1.0.35-1| bullseye| source
 uclibc | 1.0.35-1| sid | source


Andreas

Bug#983718: RM: yash [mips64el mipsel] -- RoQA; no longer builds on mips*

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Sun 28 Feb 2021 at 09:58PM +02, Adrian Bunk wrote:

> Package: ftp.debian.org
> Severity: normal
>
> See #982817 for background

So it's expected that it won't be possible to resolve the build issue on
those archs any time soon?  Have you any analysis of the failures?

Thanks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#941951: ITA: tpm2-pk11

[Sean Whitton]

Hello Seunghun,

On Wed 08 Apr 2020 at 01:20PM +09, Seunghun Han wrote:

> I would like to adopt this package.

Do you still intend to adopt?  At the very least seems we should
probably remove this from the RM queue?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

[Hideki Yamane]

On Sat, 3 Jul 2021 21:36:53 +0900
Hideki Yamane  wrote:
>  Mostly done, still have an error with autopkgtest for python3-openscap

 Updated. Passed all salsa-ci test as below, and eliminate most of
 lintian warning/info.
 https://salsa.debian.org/henrich/openscap/-/pipelines/265972


diff -Nru openscap-1.3.4/debian/changelog openscap-1.3.4/debian/changelog
--- openscap-1.3.4/debian/changelog 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/changelog 2021-06-30 16:33:53.0 +0900
@@ -1,3 +1,37 @@
+openscap (1.3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+
+  * Package structure changes
+- Apply soname change (libopenscap8 -> 25)
+- Split libopenscap25 to openscap-scanner, openscap-utils and
+  openscap-common
+- Drop -dbg package and unnecessary lintian-overrides
+  * debian/control
+- Specify https for upstream URL
+- Use debhelper-compat (= 13) to not forget to install necessary files
+  with dh_missing
+- Add missing dependencies: libacl1-dev, libblkid-dev, libglib2.0-dev,
+  libyaml-dev, librpm-dev, libpopt-dev, libprocps-dev, libopendbx1-dev,
+  libxmlsec1-dev, doxygen, graphviz, asciidoc,
+  * Drop unnecessary debian/compat
+  * debian/rules
+- Enable documentation build
+- Enable hardening
+  * Add openscap-common.docs to install HTML docs
+  * debian/openscap-scanner.install
+- Install bash-completion
+  * openscap-utils.install
+- Install autotailor and scap-as-rpm
+  * Add debian/openscap-{scanner,utils}.manpages
+
+  * Trim trailing whitespace.
+  * Update watch file format version to 4.
+  * Set upstream metadata fields: Bug-Database, Bug-Submit.
+  * Drop unnecessary dependency on dh-autoreconf.
+
+ -- Hideki Yamane   Wed, 30 Jun 2021 16:33:53 +0900
+
 openscap (1.3.4-1) unstable; urgency=medium
 
   * New upstream version 1.3.4
diff -Nru openscap-1.3.4/debian/compat openscap-1.3.4/debian/compat
--- openscap-1.3.4/debian/compat2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/compat1970-01-01 09:00:00.0 +0900
@@ -1 +0,0 @@
-11
diff -Nru openscap-1.3.4/debian/control openscap-1.3.4/debian/control
--- openscap-1.3.4/debian/control   2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/control   2021-06-30 16:33:53.0 +0900
@@ -2,7 +2,7 @@
 Priority: optional
 Maintainer: Pierre Chifflier 
 Uploaders: Philippe Thierry 
-Build-Depends: debhelper (>= 13),
+Build-Depends: debhelper-compat (= 13),
 cmake,
 libpcre3-dev,
 libxml2-dev,
@@ -18,19 +18,30 @@
 libattr1-dev,
 libldap2-dev,
 libbz2-dev,
+libacl1-dev,
+libblkid-dev,
+libglib2.0-dev,
+libyaml-dev,
+librpm-dev,
+libpopt-dev,
+libprocps-dev,
+libopendbx1-dev,
+libxmlsec1-dev,
+doxygen, graphviz,
+asciidoc,
 pkg-config,
 dh-python,
 chrpath,
 libdbus-1-dev
+Section: admin
 X-Python3-Version: >= 3.9
 Standards-Version: 4.5.1
-Section: libs
-Homepage: http://www.open-scap.org/
+Homepage: https://www.open-scap.org/
 
 Package: libopenscap-dev
 Section: libdevel
 Architecture: linux-any
-Depends: libopenscap8 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
+Depends: libopenscap25 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -48,13 +59,13 @@
  .
  This package contains the development files for OpenSCAP.
 
-Package: libopenscap8
+Package: libopenscap25
 Section: libs
 Architecture: linux-any
-Conflicts: libopenscap0, libopenscap1, libopenscap3
-Replaces: libopenscap0, libopenscap1, libopenscap3
+Conflicts: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
+Replaces: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends},
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -69,11 +80,13 @@
   * Common Vulnerability Scoring System (CVSS)
   * Extensible Configuration Checklist Description Format (XCCDF)
   * Open Vulnerability and Assessment Language (OVAL)
+ .
+ This package contains libraries for OpenSCAP.
 
 Package: python3-openscap
 Section: python
 Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap8 
(= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap25 
(= ${binary:Version})
 X-Python3-Version: ${python3:Versions}
 Provides: ${python3:Provides}
 Description: Set of libraries enabling integration of the SCAP line of 

Bug#990646: unblock: nodejs/12.21.0~dfsg-5

[Jérémy Lal]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package nodejs

[ Reason ]
nodejs have been using its own copy of libuv for a while,
without me noticing.

[ Impact ]
nodejs using own copy of libuv, bad for security fixes.

[ Tests ]
nodejs own test suite is thorough.

[ Risks ]
None. But I might have overlooked a risk. Please tell me.

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

[ Other info ]
The problem should have been discovered one year ago. Sorry for this.

unblock nodejs/12.21.0~dfsg-5
diff -Nru nodejs-12.21.0~dfsg/debian/changelog 
nodejs-12.21.0~dfsg/debian/changelog
--- nodejs-12.21.0~dfsg/debian/changelog2021-04-21 12:42:46.0 
+0200
+++ nodejs-12.21.0~dfsg/debian/changelog2021-07-03 20:50:29.0 
+0200
@@ -1,3 +1,9 @@
+nodejs (12.21.0~dfsg-5) unstable; urgency=medium
+
+  * Patch uvwasi.gyp to honour --shared-libuv. Closes: #990569.
+
+ -- Jérémy Lal   Sat, 03 Jul 2021 20:50:29 +0200
+
 nodejs (12.21.0~dfsg-4) unstable; urgency=medium
 
   [ Andreas Beckmann ]
diff -Nru nodejs-12.21.0~dfsg/debian/patches/series 
nodejs-12.21.0~dfsg/debian/patches/series
--- nodejs-12.21.0~dfsg/debian/patches/series   2021-03-19 18:28:07.0 
+0100
+++ nodejs-12.21.0~dfsg/debian/patches/series   2021-07-03 16:18:02.0 
+0200
@@ -1,3 +1,4 @@
+shared_uv_from_uvwasi.patch
 large_pages_assembly_gnu_stack.patch
 dfhs_module_path_arch_triplet.patch
 # 2012_kfreebsd.patch
diff -Nru nodejs-12.21.0~dfsg/debian/patches/shared_uv_from_uvwasi.patch 
nodejs-12.21.0~dfsg/debian/patches/shared_uv_from_uvwasi.patch
--- nodejs-12.21.0~dfsg/debian/patches/shared_uv_from_uvwasi.patch  
1970-01-01 01:00:00.0 +0100
+++ nodejs-12.21.0~dfsg/debian/patches/shared_uv_from_uvwasi.patch  
2021-07-03 17:43:00.0 +0200
@@ -0,0 +1,26 @@
+Description: uvwasi depends on uv.gyp and ignores shared_libuv
+Author: Jérémy Lal 
+Last-Update: 2021-07-03
+Forwarded: https://github.com/nodejs/node/issues/39248
+--- a/deps/uvwasi/uvwasi.gyp
 b/deps/uvwasi/uvwasi.gyp
+@@ -18,9 +18,6 @@
+ 'src/wasi_rights.c',
+ 'src/wasi_serdes.c',
+   ],
+-  'dependencies': [
+-'../uv/uv.gyp:libuv',
+-  ],
+   'direct_dependent_settings': {
+ 'include_dirs': ['include']
+   },
+@@ -31,6 +28,9 @@
+ '_POSIX_C_SOURCE=200112',
+   ],
+ }],
++[ 'node_shared_libuv=="false"', {
++  'dependencies': [ '../uv/uv.gyp:libuv' ],
++}],
+   ],
+ }
+   ]
diff -Nru nodejs-12.21.0~dfsg/debian/rules nodejs-12.21.0~dfsg/debian/rules
--- nodejs-12.21.0~dfsg/debian/rules2021-02-23 19:22:31.0 +0100
+++ nodejs-12.21.0~dfsg/debian/rules2021-07-03 15:48:04.0 +0200
@@ -16,19 +16,20 @@
 export LANG
 DEB_CONFIGURE_NORMAL_ARGS =
 DEB_CONFIGURE_EXTRA_FLAGS = \
+--verbose \
 --without-npm \
 --shared \
 --shared-zlib \
 --shared-cares \
---shared-nghttp2 \
 --shared-brotli \
 --with-intl=system-icu \
 --prefix=/usr \
 --openssl-use-def-ca-store \
 --arch-triplet=$(DEB_HOST_MULTIARCH) \
---node-relative-path="lib/$(DEB_HOST_MULTIARCH)/nodejs:share/nodejs:lib/nodejs"
 \
---shared-libuv
+--node-relative-path="lib/$(DEB_HOST_MULTIARCH)/nodejs:share/nodejs:lib/nodejs"
 
+DEB_CONFIGURE_EXTRA_FLAGS += --shared-nghttp2
+DEB_CONFIGURE_EXTRA_FLAGS += --shared-libuv
 DEB_CONFIGURE_EXTRA_FLAGS += --shared-openssl
 
 # map HOST ARCH AND OS, and if unknown let upstream guess

Bug#990641: gpsprune: Cannot load gpx file from OSm route manager (due to blank lines)

[Sebastiaan Couwenberg]

On 7/3/21 5:23 PM, Wookey wrote:
> I had a look at the gpx spec, and the schema is here:
> https://www.topografix.com/GPX/1/1/gpx.xsd but I guess that whether
> the xml line must be on the very first line is actually part of the
> XML spec. I failed to find a simple validator I could run to check whether 

FWIW:

$ wget https://www.topografix.com/GPX/1/1/gpx.xsd -P /tmp

$ xmllint --noout --schema /tmp/gpx.xsd /tmp/Ceredigion+Coast+Path.gpx
/tmp/Ceredigion+Coast+Path.gpx:13: parser error : XML declaration
allowed only at the start of the document

 ^

$ cat /tmp/Ceredigion+Coast+Path.gpx | tidy -xml -i -w -q >
/tmp/Ceredigion+Coast+Path_tidy.gpx

$ xmllint --noout --schema /tmp/gpx.xsd /tmp/Ceredigion+Coast+Path_tidy.gpx
/tmp/Ceredigion+Coast+Path_tidy.gpx validates


libgeo-gpx-perl cannot parse the GPX either:

$ perl -e 'use File::Slurp; use Geo::Gpx; my $xml =
read_file("/tmp/Ceredigion+Coast+Path.gpx"); my $gpx = Geo::Gpx->new(xml
=> $xml); print $gpx->version()."\n";'

XML or text declaration not at start of entity at line 13, column 0,
byte 12 at /usr/share/perl5/XML/TokeParser.pm line 353.

$ perl -e 'use File::Slurp; use Geo::Gpx; my $xml =
read_file("/tmp/Ceredigion+Coast+Path_tidy.gpx"); my $gpx =
Geo::Gpx->new(xml => $xml); print $gpx->version()."\n";'
1.1


Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#990645: Debian's installer's GRUB installer detects Vista instead of my 64-bit W7 installation.

[Ant]

Package: debian-installer
Version: ?

I downloaded, mounted, and booted Debian's net installer ISO (e.g., 
https://gemmei.ftp.acc.umu.se/debian-cd/current/amd64/iso-cd/debian-10.10.0-amd64-netinst.iso
 and 
https://gemmei.ftp.acc.umu.se/cdimage/unofficial/non-free/cd-including-firmware/bullseye_di_rc2+nonfree/amd64/iso-cd/firmware-bullseye-DI-rc2-amd64-netinst.iso)
 
in an old 64-bit W7 HPE SP1 VirtualBox v6.1 VM with a brand new virtual SSD (2 
virtual drives = 1 old W7 HDD + 1 new blank SSD). I'm trying it before 
doing it virtually instead of my real physical PC to learn and practice (don't 
want to hose my 12 yrs. old real hardware production PC!). I picked 
most of Debian's defaults (no GUI packages to install for now). I'm currently 
having problems with its GRUB bootloader part. It detected Vista, but I 
don't have Vista as shown in my https://i.ibb.co/ctfV40c/Grub-Vista.gif screen 
shot/capture. I have W7!

Thank you for reading and hopefully fixing it soon. :)

Bug#990550: [Pre-Approval] unblock: node-babel-plugin-add-module-exports/1.0.4+dfsg1~cs5.8.0-2

[Pirate Praveen]

Control: retitle -1 unblock autosize.js/4.0.2~dfsg1-7

On Sat, 03 Jul 2021 17:47:29 +0530 Pirate Praveen 
 wrote:

> On Thu, 01 Jul 2021 23:28:12 +0530 Pirate Praveen
>  wrote:
>  > I'd like to check if we can unblock package
>  > node-babel-plugin-add-module-exports (currently in experimental) 
with

>  > its reverse build dependencies.
>
> Looks like this update does not actually fix the issue with
> libjs-autosize build. So I will keep this bug open for a few days as 
I

> test other options, but we don't need to unblock this for now.

Fixed libjs-autosize by switching to rollup and removing 
node-babel-plugin-add-module-exports build dependency.


So I'd like to change this to an unblock request for autosize.js

Bug#990393: Debian Bug report logs - #990393 gparted: Invalid option provided to mkfs.exfat when formatting to exfat in gparted on bullseye

[Curtis Gedak]

This bug is a duplicate of Debian Bug report logs - #984714
gparted: unable to create exFAT file systems

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

Regards,
Curtis

Bug#990240: soapyosmo: does not link with boost chrono

[tony mancill]

On Wed, Jun 23, 2021 at 08:50:13PM +0200, Sebastian Ramacher wrote:
> Indeed, soapyosmo does not link with boost chrono. Reassigning
> accordingly.

The attached patch updates the build to link against boost chrono.

However, the patched build alone does not resolve the crash of
sdrangelove on my system until I also install the updated hamlib4 from
experimental.  That is, sdrangelove appears to be affected by 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980472.

I'm not sure what the plans are for the hamlib4 with respect to
Bullseye.  Any concerns with an upload of soapyosmo to get us one step
closer?  

The patch/debdiff is attached.

Thanks,
tony
diff -Nru soapyosmo-0.2.5/debian/changelog soapyosmo-0.2.5/debian/changelog
--- soapyosmo-0.2.5/debian/changelog	2019-10-20 08:31:08.0 -0700
+++ soapyosmo-0.2.5/debian/changelog	2021-07-03 09:31:09.0 -0700
@@ -1,3 +1,10 @@
+soapyosmo (0.2.5-4) UNRELEASED; urgency=medium
+
+  * Team upload.
+  * Add boost::chrono to build (Closes: #990240)
+
+ -- tony mancill   Sat, 03 Jul 2021 09:31:09 -0700
+
 soapyosmo (0.2.5-3) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru soapyosmo-0.2.5/debian/control soapyosmo-0.2.5/debian/control
--- soapyosmo-0.2.5/debian/control	2019-10-20 08:29:52.0 -0700
+++ soapyosmo-0.2.5/debian/control	2021-07-03 09:31:09.0 -0700
@@ -7,6 +7,7 @@
 debhelper (>= 12),
 cmake,
 libboost-dev,
+libboost-chrono-dev,
 libboost-system-dev,
 libboost-thread-dev,
 libosmosdr-dev,
diff -Nru soapyosmo-0.2.5/debian/patches/boost_chrono.patch soapyosmo-0.2.5/debian/patches/boost_chrono.patch
--- soapyosmo-0.2.5/debian/patches/boost_chrono.patch	1969-12-31 16:00:00.0 -0800
+++ soapyosmo-0.2.5/debian/patches/boost_chrono.patch	2021-07-03 09:31:09.0 -0700
@@ -0,0 +1,10 @@
+--- a/CMakeLists.txt
 b/CMakeLists.txt
+@@ -102,6 +102,7 @@
+ SET(BOOST_REQUIRED_COMPONENTS
+ thread
+ system
++chrono
+ )
+ 
+ if(UNIX AND NOT BOOST_ROOT AND EXISTS "/usr/lib64")
diff -Nru soapyosmo-0.2.5/debian/patches/series soapyosmo-0.2.5/debian/patches/series
--- soapyosmo-0.2.5/debian/patches/series	2019-09-22 18:12:05.0 -0700
+++ soapyosmo-0.2.5/debian/patches/series	2021-07-03 09:31:09.0 -0700
@@ -1 +1,2 @@
 internal-common-library
+boost_chrono.patch


signature.asc
Description: PGP signature

Bug#990639: Typo "behavour" on acng-report.html webpage

[Andreas Dolp]

Package: apt-cacher-ng
Version: 3.2.1-1
Severity: minor
Tags: upstream

There is a typo in the word "behavour" on the webpage acng-report.html.
It is in the section "Shared processing options" in the first sentence: 
"Temporary options for the general behavour and index update configuration can 
set in this user interface."

Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied

[xiscu]

Package: kakoune
Version: 2020.01.16-2
Followup-For: Bug #990635

Dear Maintainer,
thanks for the fast response. Here the tests (on fish):

1. ACK :
ls -ld /run/user/1000/kakoune/
drwx--x--x 2 root root 40 Jun 21 18:11 /run/user/1000/kakoune//

2. Changed to user and group and now kakoune (kak cmd) works
for me (that only user in the system, personal machine).

Thanks for mantaining kakoune for debian (I would love to see
kakoune, or at least the ideas, working and its concepts also
intregated on other IDEs!)

xiscu



-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
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 kakoune depends on:
ii  libc6 2.31-12
ii  libgcc-s1 10.2.1-6
ii  libncursesw6  6.2+20201114-2
ii  libstdc++610.2.1-6
ii  libtinfo6 6.2+20201114-2

kakoune recommends no packages.

kakoune suggests no packages.

-- no debconf information

Bug#989958: libopencv-*-dev: Missing pkg-config file (.pc)

[Alejandro Colomar (man-pages)]

Hi Jochen,

On 6/21/21 8:43 PM, Jochen Sprickerhof wrote:
> * Alejandro Colomar (man-pages)  [2021-06-21
> 17:35]:
>> Maybe Debian could write separate pkg-config files, and maybe offer
>> them to upstream OpenCV (I offer myself to help write them if you
>> decide it's a good idea).
> 
> It's easier if you talk to upstream about this directly. Adding them to
> Debian only would be incompatible with other distros and be of limited use.

It seems that they decided long ago to drop support for pkg-config
files.  See
 and


Their only response is "consider using cmake's `find_package()`", which
is not an option for me, and BTW not an option also in many other
important projects.

What should we do about it?  Maintain our pkg-config files in Debian?

> 
>> Yes, for linking against the shared libraries, that's all you need:
>> link against the module you want.  BUT, if you want to try to link
>> against the static library (and now I'm talking from memory (it's been
>> a year since I tried to do that, and I don't remember the result, I
>> only remember a bunch of errors)), you'll need to know which libraries
>> you need, which is the magic of pkg-config.
> 
> Static linking should work fine without pkg-config as well, except that
> you would have to list all dependencies, but looking at the opencv4.pc I
> guess they are incomplete anyhow ;).

Yep, I meant that it's insane adding all of the -l... manually.  That's
the "magic" of pkg-config :).

> 
> Cheers Jochen

Cheers,

Alex

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

Bug#990644: libstorj-dev does not include headers

[Adrian Bunk]

Package: libstorj-dev
Version: 1.0.3-1.1
Severity: serious

$ dpkg -L libstorj-dev | sort
/.
/usr
/usr/lib
/usr/lib/libstorj.a
/usr/lib/libstorj.la
/usr/lib/libstorj.so
/usr/share
/usr/share/doc
/usr/share/doc/libstorj-dev
/usr/share/doc/libstorj-dev/changelog.Debian.gz
/usr/share/doc/libstorj-dev/copyright
$

Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2

[jim_p]

Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com

First things first, I missed message #20. It seems that the errors on the
terminal are identical for ff 89 and tb 90b2 and, imho, irrelevant to the
preferences tab issue.
I do think nvidia is the culprit too and I will try to troubleshoot it on my
own.
So far I have enabled/disabled hardware acceleration and webgl with no luck. I
will keep looking. I am sure it has to do with the proton redesign.

I tried the binary that mozilla provides and the preferences tab opens there
with no issues at all (fresh profile etc). The output in the terminal is the
same though.
My friend (arch user) also has tried both the binary and compiling it from
source. And he mentions the same: the preferences tab opens at the binary but
not at the compiled one.
In both systems, the error console (ctrl+shift+j) reports this error

Uncaught ReferenceError: XPCOMUtils is not defined
 chrome://messenger/content/preferences/preferences.js:37

and a link below that that leads here, which is too complicated for us to
understand. I hope the above error helps though.
https://developer.mozilla.org/en-
US/docs/Web/JavaScript/Reference/Errors/Not_defined

Last but not least, I also use the esr versions of tb (but not of ff), but once
a year, when the new tb version is nearing its release, I switch to the beta
one to see what is new.
And to find issues like this one too, so as to report them early.
To be honest, last time I used the preferences dialog was a couple of years ago
that I wanted to make the font for my (incoming and outgoing) emails bigger and
prettier. The default one was some tiny monospace one that looked bad. And I
have not opened the preferences tab since then.

Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709

[Sebastian Piecha]

Without bonding 2 interfaces there is no kernel panic so far.

spi

Bug#990643: ITP: puremagic -- pure python module to identify files

[Jeroen Ploemen]

Package: wnpp
Severity: wishlist

https://github.com/cdgriffith/puremagic
Needed for future versions of sabnzbdplus


pgpMU_iEkGWHb.pgp
Description: OpenPGP digital signature

Bug#990162: power consumption regression

[John]

The power consumption measurement in my previous message using RC2 was executed 
wrong. A USB key added to the power consumption.

The conclusions based on that are wrong.

New test result after reboot: +6% compared to Debian 10. The same power 
consumption level as in 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990162#31 .

Bug#990641: gpsprune: Cannot load gpx file from OSm route manager (due to blank lines)

[Sebastiaan Couwenberg]

forwarded 990641 https://github.com/activityworkshop/GpsPrune/issues/38
thanks

On 7/3/21 5:23 PM, Wookey wrote:
> If I generate a gpx file with 'OSM Route manager', specifically the 
> Ceredigion Coast path
> https://osmrm.openstreetmap.de/relation.jsp?id=1806040
> 
> when I try to load it with GPSprune it says:
> "Error reading file: The processing instruction target matching 
> '[xX][mM][lL]' is not allowed." 
> 
> This is quite a cryptic error.
> 
> If try 'Import file with GPSbabel' instead I get the somewhat more helpful
> "GPX Read error: 'XML declaration not at start of document.
> "File: /tmp/Ceredigion+Coast+Path.gpx" Line: 13 column: 55'
> 
> Looking at the file (attached) it has 12 leading blank lines. (0x0A
> unix linefeeds). Looks like GPSprune is expecting the xml header to be
> on the first line.
> 
> If you remove those 12 lines then the file loads as expected.
> 
> Now I presume that GPSprune is following the gpx spec, but perhaps it
> could be forgiving of leading whitespace? Certainly it could give a more
> useful error message of the form 'Could not load file : invalid
> GPX file'.
> 
> I had a look at the gpx spec, and the schema is here:
> https://www.topografix.com/GPX/1/1/gpx.xsd but I guess that whether
> the xml line must be on the very first line is actually part of the
> XML spec. I failed to find a simple validator I could run to check whether 
> 
> The codebase for OSMRM is here:
> https://github.com/osmrmhv/osmrmhv/issues so it you are happy that
> GPSprune is correct to reject this file then I guess I should file an
> issue there instead.

gpsprune could be more liberal in what it accepts, but rejecting bad
data is fine IMHO too.

This is not something that will be addressed by the package maintainer,
hence the issue has been forwarded upstream.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#990642: linux-image-4.19.0-17-amd64: kernel panic on xen dom0 with Broadcom Limited NetXtreme II BCM5709

[spi]

Package: src:linux
Version: 4.19.194-1
Severity: important



-- Package-specific info:
** Version:
Linux version 4.19.0-17-amd64 (debian-ker...@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-1 (2021-06-10)

** Command line:
placeholder root=/dev/mapper/srvxen04-root ro console=ttyS0,115200n8
console=tty0 intel_iommu=on nomodeset net.ifnames=1 biosdevname=0

** Not tainted

** Kernel log:
[   39.592859] vif vif-1-0 vif-fw2-OAM: renamed from vif1.0
[   39.620827] vif vif-1-3 vif-fw2-FE: renamed from vif1.3
[   39.648849] vif vif-1-2 vif-fw2-DMZ0: renamed from vif1.2
[   39.676964] vif vif-1-6 vif-fw2-TEST: renamed from vif1.6
[   39.712828] vif vif-1-8 vif-fw2-HOME: renamed from vif1.8
[   39.796755] brLAN: port 2(vif-fw2-LAN) entered blocking state
[   39.802908] brLAN: port 2(vif-fw2-LAN) entered disabled state
[   39.809479] device vif-fw2-LAN entered promiscuous mode
[   39.815267] brOAM: port 2(vif-fw2-OAM) entered blocking state
[   39.821493] brOAM: port 2(vif-fw2-OAM) entered disabled state
[   39.827692] device vif-fw2-OAM entered promiscuous mode
[   39.833365] brWLAN: port 2(vif-fw2-WLAN) entered blocking state
[   39.839769] brWLAN: port 2(vif-fw2-WLAN) entered disabled state
[   39.846161] device vif-fw2-WLAN entered promiscuous mode
[   39.851967] brDMZ0: port 2(vif-fw2-DMZ0) entered blocking state
[   39.858295] brDMZ0: port 2(vif-fw2-DMZ0) entered disabled state
[   39.864659] device vif-fw2-DMZ0 entered promiscuous mode
[   39.874675] brFE: port 2(vif-fw2-FE) entered blocking state
[   39.880621] brFE: port 2(vif-fw2-FE) entered disabled state
[   39.886968] device vif-fw2-FE entered promiscuous mode
[   39.893906] brRLAN: port 2(vif-fw2-RLAN) entered blocking state
[   39.900254] brRLAN: port 2(vif-fw2-RLAN) entered disabled state
[   39.907304] device vif-fw2-RLAN entered promiscuous mode
[   39.915348] brTEST: port 2(vif-fw2-TEST) entered blocking state
[   39.921718] brTEST: port 2(vif-fw2-TEST) entered disabled state
[   39.928290] device vif-fw2-TEST entered promiscuous mode
[   39.934666] brBE: port 2(vif-fw2-BE) entered blocking state
[   39.940616] brBE: port 2(vif-fw2-BE) entered disabled state
[   39.946814] device vif-fw2-BE entered promiscuous mode
[   39.953792] brHOME: port 2(vif-fw2-HOME) entered blocking state
[   39.960107] brHOME: port 2(vif-fw2-HOME) entered disabled state
[   39.966581] device vif-fw2-HOME entered promiscuous mode
[   42.160336] xen-blkback: backend/vbd/1/51712: using 1 queues,
protocol 1 (x86_64-abi)
[   42.353338] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
[   42.358612] brOAM: port 2(vif-fw2-OAM) entered blocking state
[   42.364733] brOAM: port 2(vif-fw2-OAM) entered forwarding state
[   42.378050] vif vif-1-1 vif-fw2-LAN: Guest Rx ready
[   42.383309] brLAN: port 2(vif-fw2-LAN) entered blocking state
[   42.389427] brLAN: port 2(vif-fw2-LAN) entered forwarding state
[   42.428330] vif vif-1-2 vif-fw2-DMZ0: Guest Rx ready
[   42.433682] brDMZ0: port 2(vif-fw2-DMZ0) entered blocking state
[   42.440053] brDMZ0: port 2(vif-fw2-DMZ0) entered forwarding state
[   42.448264] vif vif-1-3 vif-fw2-FE: Guest Rx ready
[   42.453429] brFE: port 2(vif-fw2-FE) entered blocking state
[   42.459409] brFE: port 2(vif-fw2-FE) entered forwarding state
[   42.467498] vif vif-1-4 vif-fw2-BE: Guest Rx ready
[   42.472669] brBE: port 2(vif-fw2-BE) entered blocking state
[   42.478647] brBE: port 2(vif-fw2-BE) entered forwarding state
[   42.486688] vif vif-1-5 vif-fw2-WLAN: Guest Rx ready
[   42.492049] brWLAN: port 2(vif-fw2-WLAN) entered blocking state
[   42.498370] brWLAN: port 2(vif-fw2-WLAN) entered forwarding state
[   42.506575] vif vif-1-6 vif-fw2-TEST: Guest Rx ready
[   42.511964] brTEST: port 2(vif-fw2-TEST) entered blocking state
[   42.518364] brTEST: port 2(vif-fw2-TEST) entered forwarding state
[   42.526458] vif vif-1-7 vif-fw2-RLAN: Guest Rx ready
[   42.531790] brRLAN: port 2(vif-fw2-RLAN) entered blocking state
[   42.538105] brRLAN: port 2(vif-fw2-RLAN) entered forwarding state
[   42.546365] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
[   42.551699] brHOME: port 2(vif-fw2-HOME) entered blocking state
[   42.557990] brHOME: port 2(vif-fw2-HOME) entered forwarding state
[   52.749924] brBE: port 2(vif-fw2-BE) entered disabled state
[   52.857180] vif vif-1-4 vif-fw2-BE: Guest Rx ready
[   52.862389] brBE: port 2(vif-fw2-BE) entered blocking state
[   52.868356] brBE: port 2(vif-fw2-BE) entered forwarding state
[   53.011574] vif vif-1-4 vif-fw2-BE: Guest Rx ready
[   53.011597] NOHZ: local_softirq_pending 08
[   53.145228] vif vif-1-3 vif-fw2-FE: Guest Rx ready
[   53.253183] vif vif-1-3 vif-fw2-FE: Guest Rx ready
[   53.253214] NOHZ: local_softirq_pending 08
[   53.377074] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
[   53.493773] vif vif-1-8 vif-fw2-HOME: Guest Rx ready
[   53.493792] NOHZ: local_softirq_pending 08
[   53.648414] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
[   53.761142] vif vif-1-0 vif-fw2-OAM: Guest Rx ready
[  

Bug#990641: gpsprune: Cannot load gpx file from OSm route manager (due to blank lines)

[Wookey]

Package: gpsprune
Version: 20.2-1
Severity: normal
Tags: upstream

If I generate a gpx file with 'OSM Route manager', specifically the Ceredigion 
Coast path
https://osmrm.openstreetmap.de/relation.jsp?id=1806040

when I try to load it with GPSprune it says:
"Error reading file: The processing instruction target matching '[xX][mM][lL]' 
is not allowed." 

This is quite a cryptic error.

If try 'Import file with GPSbabel' instead I get the somewhat more helpful
"GPX Read error: 'XML declaration not at start of document.
"File: /tmp/Ceredigion+Coast+Path.gpx" Line: 13 column: 55'

Looking at the file (attached) it has 12 leading blank lines. (0x0A
unix linefeeds). Looks like GPSprune is expecting the xml header to be
on the first line.

If you remove those 12 lines then the file loads as expected.

Now I presume that GPSprune is following the gpx spec, but perhaps it
could be forgiving of leading whitespace? Certainly it could give a more
useful error message of the form 'Could not load file : invalid
GPX file'.

I had a look at the gpx spec, and the schema is here:
https://www.topografix.com/GPX/1/1/gpx.xsd but I guess that whether
the xml line must be on the very first line is actually part of the
XML spec. I failed to find a simple validator I could run to check whether 

The codebase for OSMRM is here:
https://github.com/osmrmhv/osmrmhv/issues so it you are happy that
GPSprune is correct to reject this file then I guess I should file an
issue there instead.

--
Wookey

Bug#990636: qgis not listed as file browser alternative for opening kml files

[Jürgen E . Fischer]

Hi Bas,

On Sat, 03. Jul 2021 at 14:16:26 +0200, Sebastiaan Couwenberg wrote:
> Are you sure qgis supports opening KML?

If it's a KML that GDAL recognizes, QGIS will load it.  E.g.

/usr/share/doc/libkml-dev/examples/kml/sky.kml

or

/usr/share/doc/libkml-dev/examples/kml/snippets.kml


Jürgen

-- 
Jürgen E. Fischer   norBIT GmbH Tel. +49-4931-918175-31
Dipl.-Inf. (FH) Rheinstraße 13  Fax. +49-4931-918175-50
Software Engineer   D-26506 Nordenhttps://www.norbit.de
QGIS release manager (PSC)  Germany IRC: jef on Libera|OFTC


signature.asc
Description: PGP signature
norBIT Gesellschaft fuer Unternehmensberatung und Informationssysteme mbH
Rheinstrasse 13, 26506 Norden
GF: Juergen Fischer, Nils Kutscher HR: Amtsgericht Aurich HRB 100827
Datenschutzerklaerung: https://www.norbit.de/83/

Bug#990365: unblock: nemo/4.8.6-2

[Fabio Fantoni]

Il 29/06/2021 22:52, Sebastian Ramacher ha scritto:

The diff: 
https://salsa.debian.org/cinnamon-team/nemo/-/compare/debian%2F4.8.6-1...debian%2F4.8.6-2

Please attach a debdiff of the source packages in testing and unstable to the 
bug.

Cheers


Thanks for reply, the link to salsa with diff from 4.8.6-1 to 4.8.6-2 
was correct and working, however now I attached the diff generates from 
debdiff dsc of testing and unstable as requested.


diff -Nru nemo-4.8.6/debian/changelog nemo-4.8.6/debian/changelog
--- nemo-4.8.6/debian/changelog 2021-03-12 23:47:45.0 +0100
+++ nemo-4.8.6/debian/changelog 2021-06-20 15:51:07.0 +0200
@@ -1,3 +1,10 @@
+nemo (4.8.6-2) unstable; urgency=medium
+
+  * d/patches: nemo-tree-sidebar.c: Fix states for pin/unpin and
+create-folder menu items (Closes: #988924)
+
+ -- Fabio Fantoni   Sun, 20 Jun 2021 15:51:07 +0200
+
 nemo (4.8.6-1) unstable; urgency=medium
 
   * New upstream version 4.8.6
diff -Nru nemo-4.8.6/debian/patches/fix-states-pin-create-folder-menu.patch 
nemo-4.8.6/debian/patches/fix-states-pin-create-folder-menu.patch
--- nemo-4.8.6/debian/patches/fix-states-pin-create-folder-menu.patch   
1970-01-01 01:00:00.0 +0100
+++ nemo-4.8.6/debian/patches/fix-states-pin-create-folder-menu.patch   
2021-06-20 15:51:07.0 +0200
@@ -0,0 +1,134 @@
+Author: Michael Webster 
+Description: nemo-tree-sidebar.c: Fix states for pin/unpin and
+ create-folder menu items.
+
+- Don't allow pinning of items in the root tree level.
+- Correctly set visiblity/sensitivity of the create-folder menu item -
+  disallow in non-writeable locations and in favorites (this is
+  already forbidden elsewhere).
+- Fix incorrect jump when right-clicking a non-selected tree entry.
+
+Fixes #2759
+Origin: 
https://github.com/linuxmint/nemo/commit/d1807d43898861cf159d4bdf8be2f912b396ff05
+---
+ src/nemo-tree-sidebar.c | 44 +
+ 1 file changed, 31 insertions(+), 13 deletions(-)
+
+--- a/src/nemo-tree-sidebar.c
 b/src/nemo-tree-sidebar.c
+@@ -93,11 +93,13 @@
+   GtkWidget *popup_open_in_new_window;
+   GtkWidget *popup_open_in_new_tab;
+   GtkWidget *popup_create_folder;
++GtkWidget *popup_post_create_folder_separator;
+   GtkWidget *popup_cut;
+   GtkWidget *popup_copy;
+   GtkWidget *popup_paste;
+   GtkWidget *popup_rename;
+ GtkWidget *popup_pin;
++GtkWidget *popup_post_pin_separator;
+ GtkWidget *popup_unpin;
+   GtkWidget *popup_trash;
+   GtkWidget *popup_delete;
+@@ -689,13 +691,14 @@
+ button_pressed_callback (GtkTreeView *treeview, GdkEventButton *event,
+FMTreeView *view)
+ {
+-  GtkTreePath *path, *cursor_path;
++  GtkTreePath *path;
+   gboolean parent_file_is_writable;
+   gboolean file_is_home_or_desktop;
+   gboolean file_is_special_link;
+   gboolean can_move_file_to_trash;
+   gboolean can_delete_file;
+   gboolean using_browser;
++gint is_toplevel;
+ 
+   using_browser = g_settings_get_boolean (nemo_preferences,
+   
NEMO_PREFERENCES_ALWAYS_USE_BROWSER);
+@@ -719,12 +722,11 @@
+   gtk_tree_path_free (path);
+   return FALSE;
+   }
+-  gtk_tree_view_get_cursor (view->details->tree_widget, 
_path, NULL);
+-
+-  gtk_tree_path_free (path);
+ 
+   create_popup_menu (view);
+ 
++is_toplevel = gtk_tree_path_get_depth (path) == 1;
++
+   if (using_browser) {
+   gtk_widget_set_sensitive 
(view->details->popup_open_in_new_window,
+ nemo_file_is_directory 
(view->details->popup_file));
+@@ -735,6 +737,15 @@
+   gtk_widget_set_sensitive (view->details->popup_create_folder,
+   nemo_file_is_directory (view->details->popup_file) &&
+   nemo_file_can_write (view->details->popup_file));
++
++if (nemo_file_is_in_favorites (view->details->popup_file)) {
++gtk_widget_hide (view->details->popup_create_folder);
++gtk_widget_hide 
(view->details->popup_post_create_folder_separator);
++} else {
++gtk_widget_show (view->details->popup_create_folder);
++gtk_widget_show 
(view->details->popup_post_create_folder_separator);
++}
++
+   gtk_widget_set_sensitive (view->details->popup_paste, FALSE);
+   if (nemo_file_is_directory (view->details->popup_file) &&
+   nemo_file_can_write (view->details->popup_file)) {
+@@ -785,12 +796,20 @@
+   gtk_widget_hide 
(view->details->popup_unmount_separator);
+   }
+ 
+-if (nemo_file_get_pinning (view->details->popup_file)) {
+-gtk_widget_hide (view->details->popup_pin);
+-gtk_widget_show (view->details->popup_unpin);
++if (!is_toplevel 

Bug#990640: e-antic: new major uptream version 1.0.x

[Jerome Benoit]

Package: e-antic
Severity: normal

Hello,

it appears tha the new upstream version of e-antic depends on
the C library ANTIC. ANTIC is currently not supported in Debian.
I have just submitted an ITP (#990638).

Cheers,
Jerome

Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

On Sat, 03 Jul 2021 18:11:20 +0530 Pirate Praveen 
 wrote:
> But this is babel 6 to babel 7 migration. The code transpiled by 
babel

> 6 works fine, but moving to babel 7 broke it.

One possibility is that the add-module-exports plugin is not compatible 
with babel 7's umd plugin (@babel/plugin-transform-modules-umd).

Bug#990255: keyringer incorrectly tries to use vim settings from '/usr/bin/../share/keyringer/editors/vim'

[rhatto]

Em Wed, Jun 23, 2021 at 06:16:22PM -0700, Cody Brownstein escreveu:
> Package: keyringer
> Version: 0.5.5-1
> Severity: normal
> 
> Dear Maintainer,
> 
> keyringer tries to use vim settings from
> '/usr/bin/../share/keyringer/editors/vim'. However, the file is actually
> located at '/usr/lib/keyringer/editors/vim'. This results in vim
> producing the following error message:
> 
> Error detected while processing command line:
> E484: Can't open file /usr/bin/../share/keyringer/editors/vim

Thanks for reporting :)

Just released keyringer 0.5.6 which I believe fix this issue by moving
the file into /usr/share/keyringer/editos/vim.

-- 
https://fluxo.info


signature.asc
Description: PGP signature

Bug#990625: piper: Svg images of mouse models are not packaged.

[Stephan Lachnit]

On Fri, 02 Jul 2021 19:10:49 -0300 =?utf-8?q?Sebasti=C3=A1n_Lacuesta?= 
 wrote:

> * What led up to the situation?: Mouse images do not show
> * What exactly did you do (or not do) that was effective (or
> ineffective)?: Check for package contents.
> * What was the outcome of this action?: Mouse svg files are not packaged.
> * What outcome did you expect instead?: I expect that piper show the 
image

> of the mouse.


Hi Sebastián,


First of all I want to regard the title of the bugreport: the svgs are 
inside /usr/share/piper/piper.gresource, which is build from the 
upstream svgs at build time.



Now, let's try to figure out why you don't see an image of your mouse. 
Not all mice supported by libratbag have images available, so it would 
be important to know which device you have. Please provide me with the 
output of `lsusb` and `ratbagctl list` with the mouse conntected. Then I 
can see if this is an actual bug or if there is just no image for your 
mouse.



Regards,

Stephan

Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied

[Peter Pentchev]

On Sat, Jul 03, 2021 at 04:03:07PM +0300, Peter Pentchev wrote:
> Control: tag -1 confirmed upstream patch pending
> 
> On Sat, Jul 03, 2021 at 01:39:49PM +0200, xiscu wrote:
> > Package: kakoune
> > Version: 2020.01.16-2
> > Severity: grave
> > Justification: renders package unusable
> > 
> > Dear Maintainer,
> > i'm currently unable to use kakoune as it gives a Permission denied error 
> > on start
> > (reinstalling the package hasn't solved the problem). The programm worked 
> > for me,
> > but currently i get:
> > 
> > Fatal error: unable to bind listen socket '/run/user/1000/kakoune/3781950': 
> > Permission denied
> 
> Hi,
> 
> Yes, you did stumble into an upstream kakoune bug that is fixed in
> a later upstream release that is not in Debian yet. The problem is that
> Kakoune determines the name of a "user-specific directory to put some
> stuff in" using your desktop environment's idea of a "user-specific
> directory to put some stuff in", i.e. the XDG_RUNTIME_DIR environment
> variable that is set upon the start of your GUI session. However, if you
> *first* run `sudo kak something` (and you have told sudo to preserve
> the environment variables!) or `su kak something` (and su, by default,
> does preserve the environment variables), as the first thing you do
> after restarting your computer, before running Kakoune as yourself,
> then Kakoune will create its own directory while running as root, and
> the directory will not be writable by your actual user account.
> So if later you run it from your user account, it will not be able to
> put stuff into that directory. This has happened with other tools, too,
> and this is actually part of the reason why sudo does NOT preserve all
> the environment variables by default. (Note: I'm not saying "don't use
> su, use sudo!"; I'm just saying "su does some weird things by default,
> sudo tries to prevent some problems by doing *other* weird things by
> default, and it is not always the better choice, but it does help
> prevent *some* problems")
> 
> I will test and adapt the patches for this problem...

FTR, just to have it out there before I upload the bugfix version,
the patches in question are:

  
https://github.com/mawww/kakoune/commit/7751c7e188bfc7b2f7e4a70e33032677d84597e5
  
https://github.com/mawww/kakoune/commit/db9ef82398a08bdf985ff26bfb230fb0cd1221a5

> ...but in the meantime,
> a short-term solution for your current situation is:
> 
> 1. Make sure the problem is what I think it is:
> 
>ls -ld /run/user/1000/kakoune
> 
>...and check that it is owned by "root", not by your user account
> 
> 2. Change its owner to your user account:
> 
>sudo chown "$(id -un):$(id -gn)" /run/user/1000/kakoune
> 
>or, if using su:
> 
>su -c "chown '$(id -un)' /run/user/1000/kakoune"

...arrgh, *of course* this should have been:

su -c "chown '$(id -un):$(id -gn)' /run/user/1000/kakoune"

Sorry about that! Although it would work with just the username, too,
since Kakoune would still be able to write into an owner-writable
directory.

>...of course, you can put your account's username and groupname
>directly instead of the "$(id -un):$(id -gn)" construct :)

G'luck,
Peter

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


signature.asc
Description: PGP signature

Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied

[Peter Pentchev]

Control: tag -1 confirmed upstream patch pending

On Sat, Jul 03, 2021 at 01:39:49PM +0200, xiscu wrote:
> Package: kakoune
> Version: 2020.01.16-2
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> i'm currently unable to use kakoune as it gives a Permission denied error on 
> start
> (reinstalling the package hasn't solved the problem). The programm worked for 
> me,
> but currently i get:
> 
> Fatal error: unable to bind listen socket '/run/user/1000/kakoune/3781950': 
> Permission denied

Hi,

Yes, you did stumble into an upstream kakoune bug that is fixed in
a later upstream release that is not in Debian yet. The problem is that
Kakoune determines the name of a "user-specific directory to put some
stuff in" using your desktop environment's idea of a "user-specific
directory to put some stuff in", i.e. the XDG_RUNTIME_DIR environment
variable that is set upon the start of your GUI session. However, if you
*first* run `sudo kak something` (and you have told sudo to preserve
the environment variables!) or `su kak something` (and su, by default,
does preserve the environment variables), as the first thing you do
after restarting your computer, before running Kakoune as yourself,
then Kakoune will create its own directory while running as root, and
the directory will not be writable by your actual user account.
So if later you run it from your user account, it will not be able to
put stuff into that directory. This has happened with other tools, too,
and this is actually part of the reason why sudo does NOT preserve all
the environment variables by default. (Note: I'm not saying "don't use
su, use sudo!"; I'm just saying "su does some weird things by default,
sudo tries to prevent some problems by doing *other* weird things by
default, and it is not always the better choice, but it does help
prevent *some* problems")

I will test and adapt the patches for this problem, but in the meantime,
a short-term solution for your current situation is:

1. Make sure the problem is what I think it is:

   ls -ld /run/user/1000/kakoune

   ...and check that it is owned by "root", not by your user account

2. Change its owner to your user account:

   sudo chown "$(id -un):$(id -gn)" /run/user/1000/kakoune

   or, if using su:

   su -c "chown '$(id -un)' /run/user/1000/kakoune"

   ...of course, you can put your account's username and groupname
   directly instead of the "$(id -un):$(id -gn)" construct :)

That should fix it until the next time you restart your computer, since
Kakoune will see that the directory already exists and will not attempt
to recreate it. Even after you restart your computer, the problem will
only show up if you run Kakoune through su *before* running it from your
own user account.

...and I will indeed upload a bugfix version in the next couple of days.

Thanks for using Kakoune, and thanks for making its Debian package
better by reporting this problem!

G'luck,
Peter

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


signature.asc
Description: PGP signature

Bug#990638: ITP: antic -- Algebraic Number Theory In C

[Jerome Benoit]

Package: wnpp
Severity: wishlist
Owner: Jerome Benoit 

* Package name: antic
  Version : 0.2.4
  Upstream Author : William Hart
* URL : https://github.com/wbhart/antic
* License : GPL
  Programming Lang: C
  Description : Algebraic Number Theory In C

ANTIC is an algebraic number theory library.

The e-antic library (e-antic package) depends now on the
antic library.

I am planning to maintain ANTIC in behalf of the Debian
Science Maintainers team.

Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

On Sat, Jul 3, 2021 at 12:29 pm, Akshay S Dinesh  
wrote:

https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default

But most importantly 
https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution


But this is babel 6 to babel 7 migration. The code transpiled by babel 
6 works fine, but moving to babel 7 broke it.


and looks like autosize upstream moved their build system to 
microbundle (an absctraction of rollup and babel with a set of plugins) 
which is not packaged yet.

Bug#990183: libopenscap8: libopenscap.so.8 is missing from libopenscap8 and is expected by scap-workbench

[Hideki Yamane]

On Fri, 2 Jul 2021 00:43:02 +0200
Sebastian Ramacher  wrote:
> Yes, but note that this needs to happen soon as it has to pass NEW.

 Mostly done, still have an error with autopkgtest for python3-openscap
 https://salsa.debian.org/henrich/openscap/-/pipelines/265919
 (It doesn't have git repo, so I pushed it under my user at salsa).

 It includes fixes a *lot* (sorry at this freeze time, but...), if it should
 be shrunk, we can rebase it.

diff -Nru openscap-1.3.4/debian/changelog openscap-1.3.4/debian/changelog
--- openscap-1.3.4/debian/changelog 2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/changelog 2021-06-30 16:33:53.0 +0900
@@ -1,3 +1,37 @@
+openscap (1.3.4-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+
+  * Package structure changes
+- Apply soname change (libopenscap8 -> 25)
+- Split libopenscap25 to openscap-scanner, openscap-utils and
+  openscap-common
+- Drop -dbg package and unnecessary lintian-overrides
+  * debian/control
+- Specify https for upstream URL
+- Use debhelper-compat (= 13) to not forget to install necessary files
+  with dh_missing
+- Add missing dependencies: libacl1-dev, libblkid-dev, libglib2.0-dev,
+  libyaml-dev, librpm-dev, libpopt-dev, libprocps-dev, libopendbx1-dev,
+  libxmlsec1-dev, doxygen, graphviz, asciidoc,
+  * Drop unnecessary debian/compat
+  * debian/rules
+- Enable documantation build
+- Enable hardening
+  * Add openscap-common.docs to install HTML docs
+  * debian/openscap-scanner.install
+- Install bash-completion
+  * openscap-utils.install
+- Install autotailor and scap-as-rpm
+  * Add debian/openscap-{scanner,utils}.manpages
+
+  * Trim trailing whitespace.
+  * Update watch file format version to 4.
+  * Set upstream metadata fields: Bug-Database, Bug-Submit.
+  * Drop unnecessary dependency on dh-autoreconf.
+
+ -- Hideki Yamane   Wed, 30 Jun 2021 16:33:53 +0900
+
 openscap (1.3.4-1) unstable; urgency=medium
 
   * New upstream version 1.3.4
diff -Nru openscap-1.3.4/debian/compat openscap-1.3.4/debian/compat
--- openscap-1.3.4/debian/compat2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/compat1970-01-01 09:00:00.0 +0900
@@ -1 +0,0 @@
-11
diff -Nru openscap-1.3.4/debian/control openscap-1.3.4/debian/control
--- openscap-1.3.4/debian/control   2021-02-02 00:22:30.0 +0900
+++ openscap-1.3.4/debian/control   2021-06-30 16:33:53.0 +0900
@@ -2,7 +2,7 @@
 Priority: optional
 Maintainer: Pierre Chifflier 
 Uploaders: Philippe Thierry 
-Build-Depends: debhelper (>= 13),
+Build-Depends: debhelper-compat (= 13),
 cmake,
 libpcre3-dev,
 libxml2-dev,
@@ -18,19 +18,30 @@
 libattr1-dev,
 libldap2-dev,
 libbz2-dev,
+libacl1-dev,
+libblkid-dev,
+libglib2.0-dev,
+libyaml-dev,
+librpm-dev,
+libpopt-dev,
+libprocps-dev,
+libopendbx1-dev,
+libxmlsec1-dev,
+doxygen, graphviz,
+asciidoc,
 pkg-config,
 dh-python,
 chrpath,
 libdbus-1-dev
+Section: admin
 X-Python3-Version: >= 3.9
 Standards-Version: 4.5.1
-Section: libs
-Homepage: http://www.open-scap.org/
+Homepage: https://www.open-scap.org/
 
 Package: libopenscap-dev
 Section: libdevel
 Architecture: linux-any
-Depends: libopenscap8 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
+Depends: libopenscap25 (= ${binary:Version}), ${misc:Depends}, 
${python3:Depends}, libjs-jquery
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -48,13 +59,13 @@
  .
  This package contains the development files for OpenSCAP.
 
-Package: libopenscap8
+Package: libopenscap25
 Section: libs
 Architecture: linux-any
-Conflicts: libopenscap0, libopenscap1, libopenscap3
-Replaces: libopenscap0, libopenscap1, libopenscap3
+Conflicts: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
+Replaces: libopenscap0, libopenscap1, libopenscap3, libopenscap8,
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
+Depends: ${shlibs:Depends}, ${misc:Depends},
 Description: Set of libraries enabling integration of the SCAP line of 
standards
  OpenSCAP is a set of open source libraries providing an easier path
  for integration of the SCAP line of standards. SCAP is a line of
@@ -69,11 +80,13 @@
   * Common Vulnerability Scoring System (CVSS)
   * Extensible Configuration Checklist Description Format (XCCDF)
   * Open Vulnerability and Assessment Language (OVAL)
+ .
+ This package contains libraries for OpenSCAP.
 
 Package: python3-openscap
 Section: python
 Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap8 
(= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, libopenscap25 
(= 

Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Akshay S Dinesh]

https://stackoverflow.com/questions/33505992/babel-6-changes-how-it-exports-default

But most importantly 
https://kentcdodds.com/blog/misunderstanding-es6-modules-upgrading-babel-tears-and-a-solution


03-Jul-2021 16:56:56 Pirate Praveen :

> Control: reopen -1
> 
> On Wed, 30 Jun 2021 22:40:13 +0530 Pirate Praveen  
> wrote:
>> and this is working with diaspora. Thanks again for tracking down the
>> issue.
> 
> Looks like I was wrong here and it is still failing with libjs-autosize built 
> with latest node-babel-plugin-add-module-exports.
> 
> You can see this on browser console of 
> https://diaspora.publicvm.com/statistics (setup by Rojin for testing).

Bug#990636: qgis not listed as file browser alternative for opening kml files

[Sebastiaan Couwenberg]

Control: tags -1 moreinfo

On 7/3/21 1:50 PM, Petter Reinholdtsen wrote:
> While working on KML files, I discovered that qgis did not show up in
> KDE Dolphin as an alternative to open the KML files I created.  Only
> Marble showed up there, despite the fact that I have both installed.
> 
> I believe the reason is that the MIME type
> application/vnd.google-earth.kml+xml is not listed in the qgis .desktop
> file as a supported file format.  Perhaps it should be added?  Note, 
> 
> https://wiki.debian.org/MimeTypesSupport/PackageList > and
> https://wiki.debian.org/MimeTypesSupport > have more information
> on MIME types and packages in Debian.

Are you sure qgis supports opening KML?

When I open one of the example KML files from libkml-dev with qgis it
shows an Invalid Data Source error.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#969329: systemd-cron: Special user nobody configured, this is not safe!

[Pontus Stenetorp]

This should be the commit that introduced the warning:


https://github.com/systemd/systemd/commit/bed0b7dfc0070e920d00c89d9a4fd4db8d974cf0

Based on reading it, setting `DynamicUser=yes` seems to be what systemd wants 
you to do.

Official documentation for `DynamicUser`:


https://www.freedesktop.org/software/systemd/man/systemd.exec.html#DynamicUser=

Bug#990550: [Pre-Approval] unblock: node-babel-plugin-add-module-exports/1.0.4+dfsg1~cs5.8.0-2

[Pirate Praveen]

On Thu, 01 Jul 2021 23:28:12 +0530 Pirate Praveen 
 wrote:

> I'd like to check if we can unblock package
> node-babel-plugin-add-module-exports (currently in experimental) with
> its reverse build dependencies.

Looks like this update does not actually fix the issue with 
libjs-autosize build. So I will keep this bug open for a few days as I 
test other options, but we don't need to unblock this for now.

Bug#901636: mandoc: "mandoc -mdoc -T man" causes memory dump

[наб]

Hi, sorry, me again, this also affects .TS requests in mdoc mode,
and minimises to:
-- >8 --
.TS
l .
a
.TE
-- >8 --
which dies as such:
-- >8 --
$ { echo '.TS'; echo 'l .'; echo 'a'; echo '.TE'; } | mandoc -Tman -mdoc
.\" Automatically generated from an mdoc input file.  Do not edit.
.TH "UNTITLED" "" "July 3, 2021" "" "LOCAL"
.nh
mandoc: mdoc_man.c:300: mdoc_man_act: Assertion `tok >= MDOC_Dd && tok <= 
MDOC_MAX' failed.
Aborted
-- >8 --
(original and minimal pages attached)

Attaching GDB yields, rather similarly,
  tok = TOKEN_NONE, type = ROFFT_TBL,

Would it make sense to pass tbl(7) and eqn(7) through,
like it's done in man input mode?

Best,
наб
.TS
l .
a
.TE
.\" SPDX-License-Identifier: 0BSD
.\"
.Dd
.Dt SHA1SUM 1
.Os
.
.Sh NAME
.Nm sha*sum , b2sum , md5sum
.Nd generate or verify cryptographic hashes
.Sh SYNOPSIS
.Nm sha1sum
.Op Fl ztb
.Op Fl -tag
.Oo Ar file Oc Ns …
.Nm sha224sum
.Op Fl ztb
.Op Fl -tag
.Oo Ar file Oc Ns …
.Nm sha256sum
.Op Fl ztb
.Op Fl -tag
.Oo Ar file Oc Ns …
.Nm sha384sum
.Op Fl ztb
.Op Fl -tag
.Oo Ar file Oc Ns …
.Nm sha512sum
.Op Fl ztb
.Op Fl -tag
.Oo Ar file Oc Ns …
.Nm b2sum
.Op Fl ztb
.Op Fl l Ar BITS
.Op Fl -tag
.Oo Ar file Oc Ns …
.Nm md5sum
.Op Fl ztb
.Op Fl -tag
.Oo Ar file Oc Ns …
.Pp
.Nm sha1sum
.Fl c
.Op Fl w
.Op Fl -strict
.Op Fl -quiet
.Op Fl -status
.Op Fl -ignore-missing
.Oo Ar file Oc Ns …
.Nm sha224sum
.Fl c
.Op Fl w
.Op Fl -strict
.Op Fl -quiet
.Op Fl -status
.Op Fl -ignore-missing
.Oo Ar file Oc Ns …
.Nm sha256sum
.Fl c
.Op Fl w
.Op Fl -strict
.Op Fl -quiet
.Op Fl -status
.Op Fl -ignore-missing
.Oo Ar file Oc Ns …
.Nm sha384sum
.Fl c
.Op Fl w
.Op Fl -strict
.Op Fl -quiet
.Op Fl -status
.Op Fl -ignore-missing
.Oo Ar file Oc Ns …
.Nm sha512sum
.Fl c
.Op Fl w
.Op Fl -strict
.Op Fl -quiet
.Op Fl -status
.Op Fl -ignore-missing
.Oo Ar file Oc Ns …
.Nm b2sum
.Fl c
.Op Fl l Ar BITS
.Op Fl w
.Op Fl -strict
.Op Fl -quiet
.Op Fl -status
.Op Fl -ignore-missing
.Oo Ar file Oc Ns …
.Nm md5sum
.Fl c
.Op Fl w
.Op Fl -strict
.Op Fl -quiet
.Op Fl -status
.Op Fl -ignore-missing
.Oo Ar file Oc Ns …
.
.Sh DESCRIPTION
Without
.Fl c ,
hash
.Ar file Ns s Pq the standard input stream if Qo Sy - Qc , the default ,
writing the hashes to the standard output stream.
With
.Fl c ,
verify a hash set from
.Ar file Ns s Pq likewise ,
against on-disk state.
.Pp
.TS
lb lb lb lb
l l l l l .
Program Digest  StandardLength
_
\fBsha1sum\fP   SHA-1   FIPS PUB 180160 bitsavoid use in security 
applications
\fBsha224sum\fP, \fBsha256sum\fP,
\fBsha384sum\fP, \fBsha512sum\fPSHA-2   FIPS PUB 180-2  respective
\fBb2sum\fP BLAKE2b RFC 76938-512 bits
\fBmd5sum\fPMD5 RFC 1321128 bits\fINOT\fP suitable for 
any application
.TE
.
.Ss Generation
When run without
.Fl c
nor
.Fl -tag ,
a listing is produced in the following form:
.Bd -literal -compact -offset Ds
.Li $ Nm sha1sum Li README.md
.Li 22eb73bd30d47540a4e05781f0f6e07640857cae Sy "\ " Ns Ar LICENCE
.Ed
With
.Fl b ,
an asterisk replaces the second space:
.Bd -literal -compact -offset Ds
.Li $ Nm echo Qo POSIX.2 Qc Sy \&| Nm sha1sum Fl b
.Li 33210013f52127d6ada425601f16bbb62e85f3be Sy "*" Ns Ar -
.Ed
.Pp
With
.Fl -tag ,
the output is in the form
.Bd -literal -compact -offset Ds
.Li $ Nm echo Qo POSIX.2 Qc Sy \&| Nm sha1sum Fl -tag Li LICENCE -
.Sy SHA1 Ns Li \&( Ns Ar LICENCE Ns Li )\& Sy = Li 
bd25664d6e803060dcb31bfdd9642ba9d8a3f1b9
.Sy SHA1 Ns Li \&( Ns Ar - Ns Li )\& Sy = Li 
33210013f52127d6ada425601f16bbb62e85f3be
.Ed
A dash and width in bits is appended for non-default digest lengths:
.Bd -literal -compact -offset Ds
.Li $ Nm echo Qo POSIX.2 Qc Sy \&| Nm b2sum Fl -tag l Ar 96
.Sy BLAKE2b- Ns Ar 96 Ns Li \&( Ns Ar - Ns Li )\& Sy = Li 
386b90bea2a1e566249cdb96
.Ed
.Pp
If the filename contains a backslash or newline characters, they're replaced 
with
.Qq Sy \e\e
and
.Qq Sy \en ,
respectively, and a backslash is prepended to the line:
.Bd -literal -compact -offset Ds
.Li $ Nm echo Li 'trademark of AT' Sy > Li \&"$(printf 'UNIX\enregistered')"
.Li $ Nm sha1sum Li \&"$(printf 'UNIX\enregistered')"
.Sy \e Ns Li 7390a4a0bfb7c6da55d6f5f3db4e42c534271363 Sy "\ " Ns Ar 
UNIX\enregistered
.Li $ Nm sha1sum Fl -tag Li \&"$(printf 'UNIX\enregistered')"
.Sy \eSHA1 Ns Li \&( Ns Ar UNIX\enregistered Ns Li )\& Sy = Li 
7390a4a0bfb7c6da55d6f5f3db4e42c534271363
.Ed
With
.Fl z ,
lines are separated by NUL bytes and escaping does not occur.
.
.Ss Verification
With
.Fl c ,
the
.Ar file Ns s
are instead the output in the default format:
lines consisting of a nonzero, even amount of hexadecimal digits (any case), a 
space, a space or an asterisk and a filename
(if the first character of a line is a backslash, it's skipped and the filename 
is de-escaped).
With
.Fl w ,
an error is written to the standard error stream for each invalid line.
With
.Fl -strict ,
invalid lines yield a non-zero exit code.
Be wary of using
.Qq Sy -
.Ar file Ns s
and
.Qq Sy -
hashed files.
.Pp
For each valid line, the file is hashed, 

Bug#990513: texlive-extra-utils: make4ht unusable because make4ht-logging.lua is missing

[Adrian Bunk]

On Sat, Jul 03, 2021 at 12:41:12PM +0200, Janusz S. Bień wrote:
> On Sat, Jul 03 2021 at 11:51 +03, Adrian Bunk wrote:
> > On Thu, Jul 01, 2021 at 08:55:36AM +0200, Hilmar Preuße wrote:
> 
> [...]
> 
> > This locally installed more recent version of make4ht requires something 
> > that is not required by the version of make4ht in buster.
> 
> What makes you think so?

The commit I linked to added the requirement for make4ht-logging.lua

> Janusz

cu
Adrian

Bug#990637: Why do marble have several .desktop files?

[Petter Reinholdtsen]

Package: marble
Version: 4:17.08.3-3.2

I just noticed the .desktop files in marble confuses the script used to
generate https://wiki.debian.org/MimeTypesSupport/PackageList >
because it contain 9 .desktop files:

% dpkg -L marble|grep desktop
/usr/share/applications/marble_geo.desktop
/usr/share/applications/marble_gpx.desktop
/usr/share/applications/marble_kml.desktop
/usr/share/applications/marble_kmz.desktop
/usr/share/applications/marble_shp.desktop
/usr/share/applications/marble_worldwind.desktop
/usr/share/applications/org.kde.marble.desktop
/usr/share/kservices5/marble_part.desktop
/usr/share/kservices5/marble_thumbnail_kmz.desktop
%

Is there a good reason for all these desktop files.  At elast some of
them seem redundant:

--- /usr/share/applications/marble_gpx.desktop  2017-10-20 05:52:49.0 
+0200
+++ /usr/share/applications/marble_shp.desktop  2017-10-20 05:52:49.0 
+0200
@@ -96,7 +96,7 @@
 GenericName[x-test]=xxVirtual Globexx
 GenericName[zh_CN]=虚拟地球仪
 GenericName[zh_TW]=虛擬地球儀
-MimeType=application/x-gpx+xml;
+MimeType=application/x-esri-shape;
 Icon=marble
 Terminal=false
 Categories=Qt;KDE;Education;Geography;

These two files could be combined into once by using

  MimeType=application/x-gpx+xml;application/x-esri-shape;

Perhaps the number of .desktop files in the package can be reduced?
--
Happy hacking
Petter Reinholdtsen

Bug#990636: qgis not listed as file browser alternative for opening kml files

[Petter Reinholdtsen]

Package: qgis
Version: 2.18.28+dfsg-2

While working on KML files, I discovered that qgis did not show up in
KDE Dolphin as an alternative to open the KML files I created.  Only
Marble showed up there, despite the fact that I have both installed.

I believe the reason is that the MIME type
application/vnd.google-earth.kml+xml is not listed in the qgis .desktop
file as a supported file format.  Perhaps it should be added?  Note, 

https://wiki.debian.org/MimeTypesSupport/PackageList > and
https://wiki.debian.org/MimeTypesSupport > have more information
on MIME types and packages in Debian.

-- 
Happy hacking
Petter Reinholdtsen

Bug#981815: Please explain

[Hilko Bengen]

* Сергей Фёдоров:

> Sorry for the late response - I just went to the mail and did not expect
> a letter from you.
>  
> I wanted to use sudo to delete the list of root owner files whose names
> are placed in the file.

Your main problem, as Dennis has explained, is that the redirection will
be interpreted by the shell. All sudo will get to see (and compare
against any rules) is:

xargs -0t -d '\n' -a 'install_manifest.txt'

My advice is: Put the entire operation into a little shellscript (e.g.
/usr/local/bin/cleanup), properly protect it against modifications, and
add a simple sudo rule that references only this script.

I don't see how this is a bug in sudo or in the Debian packaging and
would like to close the bug.

Cheers,
-Hilko

Bug#990635: kakoune: Fatal error: unable to bind listen socket Permission denied

[xiscu]

Package: kakoune
Version: 2020.01.16-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,
i'm currently unable to use kakoune as it gives a Permission denied error on 
start
(reinstalling the package hasn't solved the problem). The programm worked for 
me,
but currently i get:

Fatal error: unable to bind listen socket '/run/user/1000/kakoune/3781950': 
Permission denied

Thanks in advanve,
xiscu

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (900, 'testing'), (10, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads)
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 kakoune depends on:
ii  libc6 2.31-12
ii  libgcc-s1 10.2.1-6
ii  libncursesw6  6.2+20201114-2
ii  libstdc++610.2.1-6
ii  libtinfo6 6.2+20201114-2

kakoune recommends no packages.

kakoune suggests no packages.

-- no debconf information

Bug#990633: fai-diskimage using LVM partitioning creates unbootable image

[Thomas Lange]

This is the fix
https://github.com/faiproject/fai/commit/21932b35604e1eb1af5114a3176c48bc668c85ae
-- 
viele Grüße Thomas

Bug#990458: libjs-autosize is not fixed by node-babel-plugin-add-module exports update

[Pirate Praveen]

Control: reopen -1

On Wed, 30 Jun 2021 22:40:13 +0530 Pirate Praveen 
 wrote:

> and this is working with diaspora. Thanks again for tracking down the
> issue.

Looks like I was wrong here and it is still failing with libjs-autosize 
built with latest node-babel-plugin-add-module-exports.


You can see this on browser console of 
https://diaspora.publicvm.com/statistics (setup by Rojin for testing).

Bug#969916: Updating metadata

[Diederik de Haas]

Control: found -1 5.10.46
Control: tag -1 upstream patch

commit 44dd5e2106dc2fd01697b539085818d1d1c58df0 from 5.13
commit bbac8bd65f5402281cb7b0452c1c5f367387b459 from linux-next from 20210701

Those 2 patches make USB3 work on the Rock64 :)

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

Bug#969916: Correcting updated metadata

[Diederik de Haas]

Control: found -1 5.10.46-1

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

Bug#990508: RFS: apt-listchanges/3.24.1 [ITA] -- Show new changelog entries from Debian package archives

[David Kalnischkies]

Hi,

On Wed, Jun 30, 2021 at 06:13:14PM -0500, Brian Thompson wrote:
>   * Fix error message being thrown when choosing not to proceed on
> confirmation (closes: #989496).

If I understand your fix correctly, you have broken the "no"
functionality as the Pre-Install-Pkgs hook has to fail for apt to
actually stop… if they are successful apt will continue with what it was
initially told to do, which seems not inline with what "no" was supposed
to accomplish… could you clarify?

(I don't know apt-listchanges code nor do I use the confirmation
 functionality of it, so I could easily be entirely wrong)

(That seems more like we should have a way for the hooks to tell apt to
 gracefully wind down, but that doesn't exist so far)


>   * Update maintainer to myself (closes: #981890).

Could I interest you in joining the apt-team and maintain listchanges as
part of it? I am personally not much help than it comes to python, but
Julian might. Mailing list is de...@lists.debian.org and/or you can join
our IRC channel #debian-apt.


I also note that your changelog targets unstable, which might be fine if
you want to fix the mentioned bug and consider it RC (I am not so sure),
but the churn in the package (= reflow of the pt.po and pot file) will
make the release team unhappy.


Looking at your git history, all this should not be in one single commit
either – individual commits with proper titles and metadata will help
you even: You wrote the changelog by hand, git-buildpackage can do this
for you if you had e.g. a commit ala:
>
Update maintainer to myself

Closes: #981890
<
As a bonus, a week later looking at the history you will still know at
a glance what happened without remembering (or looking up) cryptic
bugreport numbers first – not to mention others. With the data in place
you could then also add a hook to salsa which automatically sets
bugreports to pending after a push of the related commit and many more
fun stuff.

(It is of course not required, even many upstream projects use "fix #42"
 as commit message and are happy and successful. So if that works for
 you fine, I am just trying to nudge you to try an alternative which
 works better for me, many others and perhaps also you)


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#983583: golang-github-sylabs-sif: diff for NMU version 1.0.9-2.1

[Adrian Bunk]

Control: tags 983583 + patch

Dear maintainer,

I've prepared an NMU for golang-github-sylabs-sif (versioned as 
1.0.9-2.1) and uploaded it to DELAYED/2. Please feel free to tell
me if I should cancel it.

cu
Adrian
diff -Nru golang-github-sylabs-sif-1.0.9/debian/changelog golang-github-sylabs-sif-1.0.9/debian/changelog
--- golang-github-sylabs-sif-1.0.9/debian/changelog	2020-02-28 09:16:12.0 +0200
+++ golang-github-sylabs-sif-1.0.9/debian/changelog	2021-07-03 13:32:11.0 +0300
@@ -1,3 +1,11 @@
+golang-github-sylabs-sif (1.0.9-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add fix from YunQiang Su for architecture-dependent behaviour
+in mmap() prot. (Closes: #983583)
+
+ -- Adrian Bunk   Sat, 03 Jul 2021 13:32:11 +0300
+
 golang-github-sylabs-sif (1.0.9-2) unstable; urgency=medium
 
   * Build-Depends correction (Closes: #951538).
diff -Nru golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch
--- golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch	1970-01-01 02:00:00.0 +0200
+++ golang-github-sylabs-sif-1.0.9/debian/patches/load-mmap.patch	2021-07-03 13:32:11.0 +0300
@@ -0,0 +1,16 @@
+Description: Fix architecture-dependent behaviour in mmap() prot
+Author: YunQiang Su 
+Bug-Debian: https://bugs.debian.org/983583
+Forwarded: not-needed (https://github.com/sylabs/sif/commit/5ef4cc53eb9bf04e79fb96428daedd5f576fb71d)
+
+--- golang-github-sylabs-sif-1.0.9.orig/pkg/sif/load.go
 golang-github-sylabs-sif-1.0.9/pkg/sif/load.go
+@@ -92,7 +92,7 @@ func (fimg *FileImage) mapFile(rdonly bo
+ 		flags := syscall.MAP_PRIVATE
+ 
+ 		if !rdonly {
+-			prot = syscall.PROT_WRITE
++			prot = syscall.PROT_WRITE | syscall.PROT_READ
+ 			flags = syscall.MAP_SHARED
+ 		}
+ 
diff -Nru golang-github-sylabs-sif-1.0.9/debian/patches/series golang-github-sylabs-sif-1.0.9/debian/patches/series
--- golang-github-sylabs-sif-1.0.9/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ golang-github-sylabs-sif-1.0.9/debian/patches/series	2021-07-03 13:32:11.0 +0300
@@ -0,0 +1 @@
+load-mmap.patch

Bug#990534: arduino: Arduino-IDE not starting witch Cinnamon Desktop.

[Rock Storm]

Control: tags -1 + moreinfo unreproducible

On Thu, 2021-07-01 at 15:53 +0200, Sven Wagner wrote:
> After starting from icon was not working, i tried starting from Mate-Terminal.
> Result was the following message, before returning to prompt:
>
> Picked up JAVA_TOOL_OPTIONS:
> Set log4j store directory /home/sven/.arduino15
> java.lang.UnsatisfiedLinkError: no splashscreen in java.library.path
>   at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1860)
>   at java.lang.Runtime.loadLibrary0(Runtime.java:870)
>   at java.lang.System.loadLibrary(System.java:1124)
>   at java.awt.SplashScreen$1.run(SplashScreen.java:124)
>   at java.awt.SplashScreen$1.run(SplashScreen.java:122)
>   at java.security.AccessController.doPrivileged(Native Method)
>   at java.awt.SplashScreen.getSplashScreen(SplashScreen.java:121)
>   at processing.app.Base.(Base.java:237)
>   at processing.app.Base.main(Base.java:141)

Hi Sven, thanks for reporting. Sadly, I'm unable to reproduce the
stated behaviour. Wild guess would be that you are missing one of the
Java native libraries somehow. I would suggest:

 1. Reinstall package 'openjdk-11-jre'. The report says you've got it
already installed but people with a similar error were missing that
particular package [1].

 2. Reinstall packages 'arduino' and 'arduino-avr-core'. Maybe a
misconfigured arduino app is looking at the wrong places?

 3. Try installing 'openjdk-11-jdk' if it is not already there. Maybe
the arduino package is missing a dependency?


[1]: https://stackoverflow.com/a/63037561

--
Rock Storm
Open PGP: C304 34B3 632C 464C 2FAF C741 0439 CF52 C968 32FD

Bug#990634: thunar: Crashes displaying thumbnail of SSH remote images

[rpnpif]

Package: thunar
Version: 1.8.4-1
Severity: important

Dear Maintainer,

Opening this URI ssh://me@192.168.1.35/home/photos/2020/05/ crashes Thunar.

Regards.

Logs :
tumblerd[6304]: Failed to get filename from uri for 
'sftp://me@192.168.1.35/home/photos/2020/05/IMG_20200503_150043.jpg', skipping
tumblerd[6304]: Failed to get filename from uri for 
'sftp://me@192.168.1.35/home/photos/2020/05/IMG_20200503_175037.jpg', skipping
tumblerd[6304]: Failed to get filename from uri for 
'sftp://me@192.168.1.35/home/photos/2020/05/IMG_20200503_175039.jpg', skipping
tumblerd[6304]: Failed to get filename from uri for 
'sftp://me@192.168.1.35/home/photos/2020/05/IMG_20200503_175041.jpg', skipping
tumblerd[6304]: Failed to get filename from uri for 
'sftp://me@192.168.1.35/home/photos/2020/05/IMG_20200510_104916.jpg', skipping
tumblerd[6304]: Failed to get filename from uri for 
'sftp://me@192.168.1.35/home/photos/2020/05/IMG_20200510_104930.jpg', skipping
tumblerd[6304]: Failed to get filename from uri for 
'sftp://me@192.168.1.35/home/photos/2020/05/IMG_20200510_104936.jpg', skipping
kernel: [ 3415.170141] Thunar[2208]: segfault at 1 ip 7f49251cd6e0 sp 
7ffcf07d4fb0 error 4 in libgobject-2.0.so.0.5800.3[7f49251a3000+32000]
kernel: [ 3415.170156] Code: 48 39 44 ca 48 0f 94 c0 0f b6 c0 c3 66 66 2e 0f 1f 
84 00 00 00 00 00 0f 1f 00 41 54 55 53 48 89 fb 48 85 ff 0f 84 a4 00 00 00 <48> 
8b 07 48 85 c0 0f 84 a4 00 00 00 48 8b 28 48 89 ea 48 81 fd fc


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

Kernel: Linux 5.10.0-0.bpo.7-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunar depends on:
ii  desktop-file-utils  0.23-4
ii  exo-utils   0.12.4-1
ii  libatk1.0-0 2.36.0-2~bpo10+1
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4+deb10u1
ii  libexo-2-0  0.12.4-1
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u3
ii  libgtk-3-0  3.24.5-1
ii  libgudev-1.0-0  232-2
ii  libice6 2:1.0.9-2
ii  libnotify4  0.7.7-4
ii  libpango-1.0-0  1.42.4-8~deb10u1
ii  libsm6  2:1.2.3-1
ii  libthunarx-3-0  1.8.4-1
ii  libxfce4ui-2-0  4.12.1-3
ii  libxfce4util7   4.12.1-3
ii  libxfconf-0-2   4.12.1-1
ii  shared-mime-info1.10-1
ii  thunar-data 1.8.4-1

Versions of packages thunar recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.20-0+deb10u1
ii  dbus-x11 [dbus-session-bus]   1.12.20-0+deb10u1
ii  gvfs  1.38.1-5
ii  libcairo-gobject2 1.16.0-4+deb10u1
ii  libpangocairo-1.0-0   1.42.4-8~deb10u1
ii  libxfce4panel-2.0-4   4.12.2-1
ii  mate-polkit [polkit-1-auth-agent] 1.20.2-1
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-7
ii  thunar-volman 0.9.1-1
ii  tumbler   0.2.3-1
ii  udisks2   2.8.1-4
ii  xdg-user-dirs 0.17-2

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.4.0-2
ii  thunar-media-tags-plugin  0.3.0-2

-- no debconf information

Bug#824168: apt-listchanges: Should not display news for libraries and other packages that the user does not care about

[Jonas Smedegaard]

A somewhat related issue is that libraries installed by debian-installer 
is marked as manually-installed - see bug#742977

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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

signature.asc
Description: signature

Bug#990633: fai-diskimage using LVM partitioning creates unbootable image

[Thomas Lange]

Package: fai-server
Version: 5.10.3

Creating a disk image with logical volumes and volume groups cause the
disk image to be unbootable, if the root file system in on a volume
group. The initrd will not find the volume group. Also other volume
groups may disapear.

The cause is that in fai-diskimage we do a cleanup of the volume
groups using vgremove.

-- 
regards Thomas

Bug#990554: tcpdump: leftover legacy configuration /etc/apparmor.d/local/usr.sbin.tcpdump

[Romain Francoise]

 user pkg-apparmor-t...@lists.alioth.debian.org
 usertags #990554 + help-needed
 thanks

On Fri, Jul 2, 2021 at 1:57 AM Christoph Anton Mitterer
 wrote:
> So is it tcpdump's responsibility to clean this up (manually) or should 
> debhelper
> do it (somehow ^^) automatically, i.e. also migrate the existing file
> automatically, because people might have had config in
> /etc/apparmor.d/local/usr.sbin.tcpdump which should have gotten moved to
> /etc/apparmor.d/local/usr.bin.tcpdump
>
> So maybe this needs to be reassigned to dh-apparmor.

Thank you for bringing this to my attention, I wasn't aware that the
dh_apparmor script snippets would create this file upon installation.
Technically the file isn't part of the package, so indeed it's not
clear whose responsibility it is to clean it up.

Let's add a usertag to loop in the pkg-apparmor team...

Bug#990069: openssh-server: Not accepting new connections during Debian 10 -> 11 upgrade

[Olaf van der Spek]

Op zo 20 jun. 2021 om 10:38 schreef Olaf van der Spek :
>
> So I think it's not accepting new connections from the start of the
> upgrade run until the end:
> Setting up openssh-sftp-server (1:8.4p1-5) ...
> Setting up console-setup (1.203) ...
> Setting up mime-support (3.66) ...
> Setting up openssh-server (1:8.4p1-5) ...
> Installing new version of config file /etc/init.d/ssh ...
> Installing new version of config file /etc/ssh/moduli ...
> Replacing config file /etc/ssh/sshd_config with new version
> rescue-ssh.target is a disabled or a static unit, not starting it.

Hi Colin,

Any thoughts on this?

-- 
Olaf

Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2

[jim_p]

Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com

So, a friend lended me his vm with debian unstable + gnome. Gnome defaults to
wayland, but it can be configured to run on xorg too. Selecting either session
(gnome or gnome on xorg) makes no difference for thunderbird. The preferences
page remains blank, so the issue applies to tb 90b2 regardless of vga driver or
display server.
On the other hand, there are no messages when it is run from the terminal.

Last but not least, tb on that installation was also on 78.11, but uncofigured,
and upgraded to 90b2 a few minutes ago. It was also tested with a fresh
profile.

Unrelated to the above, but I noticed that firefox 89 also pops the same output
when it is run from the terminal.

Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2

[Carsten Schoenert]

On 03.07.21 09:38, jim_p wrote:

You are right about nvidia, but I do not use wayland... And I probably won't be
using it until it becomes as stable as xorg. Also, my card supports up to
opengl 3.3, if this is the case.


I've no idea if this is relevant. NVIDIA cards are quite often a source 
of fun.
BTW: Wayland is stable and also *only* a protocol, it's up to the 
software on top of that to implement that protocol. NVIDIA hasn't done 
any great job here yet.


I build the TB betas to not get lost in keeping track of the required 
patching we need within the Debian packaging, but I usually don't use 
betas for to long and switch back to the ESR version for daily use.



I found the report in bugzilla after I opened this bug report here and I have
also tried launching it after setting this

export MOZ_X11_EGL=1

but it still has the same issue. Does tb 90b2 show the preferences menu as
usual in your setup?


I don't see the error messages on the CLI or the Error Console 
(Ctrl+Shift+J), but I also have issues too in the preferences tab. 
Haven't looked into this before this report.


But I also don't see some clear problem in the Error Console.

My hardware usually uses the integrated graphic card within the Intel 
based CPU. On the PC I'm sitting it's Mesa Intel(R) UHD Graphics 630 
(CFL GT2).


So still I've no idea how to narrow down the problem. It's needed to get 
reported upstream.


--
Regards
Carsten

Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2

[jim_p]

Package: thunderbird
Version: 1:90.0~b2-1
Followup-For: Bug #990631
X-Debbugs-Cc: pitsior...@gmail.com

You are right about nvidia, but I do not use wayland... And I probably won't be
using it until it becomes as stable as xorg. Also, my card supports up to
opengl 3.3, if this is the case.

I found the report in bugzilla after I opened this bug report here and I have
also tried launching it after setting this

export MOZ_X11_EGL=1

but it still has the same issue. Does tb 90b2 show the preferences menu as
usual in your setup?

Bug#990160: mpd: music players using mpd do not play concatenated mp3 files to the end

[kaliko]

Hi

Le 21/06/2021 à 21:40, js a écrit :

For example: cat mvmt1.mp3 mvmt2.mp3 mvmt3.mp3 > symph1.mp3
will play only mvmt1.mp3 on an mpd-based player when symph1.mp3 is
played.


The report is forwarded upstream (cf. 
https://github.com/MusicPlayerDaemon/MPD/issues/1200 ).

Can you please provide the following to ease debugging:

 * a sample of the combined MP3 file that cannot play past the first file
 * output of "mpd --version"
 * verbose log output

If you can, post these in the bug report on github.

Thanks
k



OpenPGP_signature
Description: OpenPGP digital signature

Bug#867548: New HDMI audio video IOMMU issues in Bullseye upgrade on Haswell are old

[Bryan Cebuliak]

bullseye with intel_iommu=on,igfx_off:
sudo dmesg | grep -e DMAR -e IOMMU
[0.007516] ACPI: DMAR 0xD8FFEAE8 B8 (v01 INTEL  HSW
 0001 INTL 0001)
[0.007531] ACPI: Reserving DMAR table memory at [mem
0xd8ffeae8-0xd8ffeb9f]
[0.019109] DMAR: Disable GFX device mapping
[0.047926] DMAR: Host address width 39
[0.047926] DMAR: DRHD base: 0x00fed9 flags: 0x0
[0.047930] DMAR: dmar0: reg_base_addr fed9 ver 1:0 cap
c020660462 ecap f0101a
[0.047930] DMAR: DRHD base: 0x00fed91000 flags: 0x1
[0.047932] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[0.047933] DMAR: RMRR base: 0x00dbcf6000 end: 0x00dbd03fff
[0.047934] DMAR: RMRR base: 0x00dd00 end: 0x00df1f
[0.047936] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[0.047937] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[0.047937] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[0.048327] DMAR-IR: Enabled IRQ remapping in x2apic mode
[0.793666] DMAR: No ATSR found
[0.793696] DMAR: dmar1: Using Queued invalidation
[0.795240] DMAR: Intel(R) Virtualization Technology for Directed I/O
[0.799207] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel 
[0.799207] AMD-Vi: AMD IOMMUv2 functionality not available on this
system


bullseye with no intel_iommu command line setting:
dmesg | grep -e DMAR -e IOMMU
[0.007532] ACPI: DMAR 0xD8FFEAE8 B8 (v01 INTEL  HSW
 0001 INTL 0001)
[0.007546] ACPI: Reserving DMAR table memory at [mem
0xd8ffeae8-0xd8ffeb9f]
[0.048030] DMAR: Host address width 39
[0.048031] DMAR: DRHD base: 0x00fed9 flags: 0x0
[0.048034] DMAR: dmar0: reg_base_addr fed9 ver 1:0 cap
c020660462 ecap f0101a
[0.048035] DMAR: DRHD base: 0x00fed91000 flags: 0x1
[0.048037] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[0.048037] DMAR: RMRR base: 0x00dbcf6000 end: 0x00dbd03fff
[0.048038] DMAR: RMRR base: 0x00dd00 end: 0x00df1f
[0.048040] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[0.048040] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[0.048041] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[0.048426] DMAR-IR: Enabled IRQ remapping in x2apic mode
[0.794120] DMAR: No ATSR found
[0.794149] DMAR: dmar0: Using Queued invalidation
[0.794154] DMAR: dmar1: Using Queued invalidation
[0.863652] DMAR: Intel(R) Virtualization Technology for Directed I/O
[0.867732] AMD-Vi: AMD IOMMUv2 driver by Joerg Roedel 

[0.867733] AMD-Vi: AMD IOMMUv2 functionality not available on this
system
[1.250394] i915 :00:02.0: [drm] DMAR active, disabling use of
stolen memory

buster no intel_iommu setting:
dmesg | grep -e DMAR -e IOMMU
[0.009193] ACPI: DMAR 0xD8FFEAE8 B8 (v01 INTEL  HSW
 0001 INTL 0001)
[0.192242] DMAR: Host address width 39
[0.192243] DMAR: DRHD base: 0x00fed9 flags: 0x0
[0.192246] DMAR: dmar0: reg_base_addr fed9 ver 1:0 cap
c020660462 ecap f0101a
[0.192246] DMAR: DRHD base: 0x00fed91000 flags: 0x1
[0.192248] DMAR: dmar1: reg_base_addr fed91000 ver 1:0 cap
d2008020660462 ecap f010da
[0.192249] DMAR: RMRR base: 0x00dbcf6000 end: 0x00dbd03fff
[0.192249] DMAR: RMRR base: 0x00dd00 end: 0x00df1f
[0.192251] DMAR-IR: IOAPIC id 8 under DRHD base  0xfed91000 IOMMU 1
[0.192251] DMAR-IR: HPET id 0 under DRHD base 0xfed91000
[0.192252] DMAR-IR: Queued invalidation will be enabled to support
x2apic and Intr-remapping.
[0.192637] DMAR-IR: Enabled IRQ remapping in x2apic mode
[0.846867] AMD IOMMUv2 driver by Joerg Roedel 
[0.846867] AMD IOMMUv2 functionality not available on this system

On Sat, 3 Jul 2021 at 02:22, Bryan Cebuliak 
wrote:

> If  igfx_off is  default, how / why is  it  on?
> from
> https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
> "...
>
> intel_iommu=[DMAR] Intel IOMMU driver (DMAR) option
> on
> Enable intel iommu driver.
> off
> Disable intel iommu driver.
> igfx_off [Default Off]
> By default, gfx is mapped as normal device. If a gfx
> device has a dedicated DMAR unit, the DMAR unit is
> bypassed by not enabling DMAR with this option. In
> this case, gfx device will use physical address for
> DMA.
> ...
>
>
> On Sat, 3 Jul 2021 at 01:25, Bryan Cebuliak 
> wrote:
>
>> more  possibly relevant IOMMU video audio  and  passthrough issue links:
>> Easy ACS kernel patch guide for Ubuntu 20.04
>> https://www.youtube.com/watch?v=JBEzshbGPhQ
>>
>>
>> 

Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2

[Carsten Schoenert]

Hello,

Am 03.07.21 um 08:23 schrieb jim_p:

> I upgraded to 90b2 (from 78.11) a few minutes ago, because I really wanted to
> see if tb has adopted that proton redesign ff 89 introduced. It hasn't (yet).
> And I noticed that every single submenu under edit > preferences is now blank
> (attached image). And the same thing happens with a fresh profile.
> Launching it from the terminal shows these errors, althought I think they are
> irrelevant
> 
> $ thunderbird
> [GFX1-]: glxtest: eglBindAPI returned an error
> [GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName

this looks like you use some NVIDIA graphic card.
So far I remember NVIDIA isn't really supporting the Wayland protocol
but I might be wrong. I haven't used NVIDIA for ages.

Reading

https://bugzilla.mozilla.org/show_bug.cgi?id=1689207

let me assume there is some problem around Wayland, the underlying used
graphic hardware and how FF/TB is getting informed about the environment.
Currently I've no idea what goes possible wrong here.

I'd suggest to report your problem to Bugzilla.

-- 
Regards
Carsten

Bug#990632: unblock: fdroidserver/2.0.3-1

[Jochen Sprickerhof]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package fdroidserver

[ Reason ]
fdroidserver has successful autopkgtests but fails on ppc64el due to
zipalign not being available on that platform (Not a regression). I
believe that is #980087.

For the patch itself, it fixes two warnings in the linting part of
fdroidserver. ruamel deprecated one function and a restriction for the
Version field in the F-Droid metadata was lifted.

Note that I opted for a new upstream version cause adding those two
change would have resulted in basically the same patch plus/minus the
version noise. Hope that is fine.

[ Impact ]
bullseye users would would get a lot of false warnings when linting a
metadata file.

[ Tests ]
I tested the new version manually. Also upstream is using it in
production.

[ Risks ]
The code change for the Version field is only changing a regex so it
seems trivial to me. For ruamel the deprecated function was replaced by
it's content.

[ Checklist ]
  [X] all changes are documented in the d/changelog (through upstream
  changelog)
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

unblock fdroidserver/2.0.3-1
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 99a5f430..945e237c 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,7 +4,21 @@ All notable changes to this project will be documented in this 
file.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 
-## [2.0.1] - 2020-03-09
+## [2.0.3] - 2021-07-01
+
+### Fixed
+
+* Support AutoUpdateMode: Version without pattern
+  [931](https://gitlab.com/fdroid/fdroidserver/-/merge_requests/931)
+
+## [2.0.2] - 2021-06-01
+
+### Fixed
+
+* fix "ruamel round_trip_dump will be removed"
+  [932](https://gitlab.com/fdroid/fdroidserver/-/merge_requests/932)
+
+## [2.0.1] - 2021-03-09
 
 ### Fixed
 
@@ -18,7 +32,7 @@ The format is based on [Keep a 
Changelog](https://keepachangelog.com/en/1.0.0/)
 * checkupdates: set User-Agent to make gitlab.com happy
 * Run push_binary_transparency only once
 
-## [2.0] - 2020-01-31
+## [2.0] - 2021-01-31
 
 For a more complete overview, see the [2.0
 milestone](https://gitlab.com/fdroid/fdroidserver/-/milestones/10)
diff --git a/PKG-INFO b/PKG-INFO
index 1c5616cd..3188aba8 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: fdroidserver
-Version: 2.0.1
+Version: 2.0.3
 Summary: F-Droid Server Tools
 Home-page: https://f-droid.org
 Author: The F-Droid Project
diff --git a/debian/changelog b/debian/changelog
index 59e519f1..d45c4c20 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+fdroidserver (2.0.3-1) unstable; urgency=medium
+
+  * Team upload.
+  * New upstream version 2.0.3
+
+ -- Jochen Sprickerhof   Thu, 01 Jul 2021 14:48:57 +0200
+
 fdroidserver (2.0.1-1) unstable; urgency=medium
 
   * New upstream version 2.0.1
diff --git a/fdroidserver.egg-info/PKG-INFO b/fdroidserver.egg-info/PKG-INFO
index 1c5616cd..3188aba8 100644
--- a/fdroidserver.egg-info/PKG-INFO
+++ b/fdroidserver.egg-info/PKG-INFO
@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: fdroidserver
-Version: 2.0.1
+Version: 2.0.3
 Summary: F-Droid Server Tools
 Home-page: https://f-droid.org
 Author: The F-Droid Project
diff --git a/fdroidserver/checkupdates.py b/fdroidserver/checkupdates.py
index f5d0d450..b9e723df 100644
--- a/fdroidserver/checkupdates.py
+++ b/fdroidserver/checkupdates.py
@@ -492,7 +492,7 @@ def checkupdates_app(app):
 logging.warning("Can't auto-update app with no CurrentVersionCode: 
" + app.id)
 elif mode in ('None', 'Static'):
 pass
-elif mode.startswith('Version '):
+elif mode.startswith('Version'):
 pattern = mode[8:]
 suffix = ''
 if pattern.startswith('+'):
diff --git a/fdroidserver/metadata.py b/fdroidserver/metadata.py
index 6c3c4815..8b27c991 100644
--- a/fdroidserver/metadata.py
+++ b/fdroidserver/metadata.py
@@ -448,7 +448,7 @@ valuetypes = {
["AntiFeatures"]),
 
 FieldValidator("Auto Update Mode",
-   r"^(Version .+|None)$",
+   r"^(Version.*|None)$",
["AutoUpdateMode"]),
 
 FieldValidator("Update Check Mode",
@@ -964,7 +964,9 @@ def write_yaml(mf, app):
 return builds
 
 yaml_app = _app_to_yaml(app)
-ruamel.yaml.round_trip_dump(yaml_app, mf, indent=4, block_seq_indent=2)
+yaml = ruamel.yaml.YAML()
+yaml.indent(mapping=4, sequence=4, offset=2)
+yaml.dump(yaml_app, stream=mf)
 
 
 build_line_sep = re.compile(r'(?

Bug#990631: thunderbird: Preferences tab is completely blank after the upgrade to 90b2

[jim_p]

Package: thunderbird
Version: 1:90.0~b2-1
Severity: important
X-Debbugs-Cc: pitsior...@gmail.com

Dear Maintainer,

I upgraded to 90b2 (from 78.11) a few minutes ago, because I really wanted to
see if tb has adopted that proton redesign ff 89 introduced. It hasn't (yet).
And I noticed that every single submenu under edit > preferences is now blank
(attached image). And the same thing happens with a fresh profile.
Launching it from the terminal shows these errors, althought I think they are
irrelevant

$ thunderbird
[GFX1-]: glxtest: eglBindAPI returned an error
[GFX1-]: glxtest: libEGL missing eglGetDisplayDriverName


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500, 'unstable'),
(1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-6-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages thunderbird depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libbotan-2-172.17.3+dfsg-2
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-12
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-2
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4
ii  libicu67 67.1-6
ii  libjson-c5   0.15-2
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.67-1
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.10.0+really1.8.1-dmo1
ii  libx11-6 2:1.7.1-1
ii  libx11-xcb1  2:1.7.1-1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxext6 2:1.3.3-1.1
ii  libxrender1  1:0.9.10-1
ii  psmisc   23.4-2
ii  x11-utils7.7+5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages thunderbird recommends:
pn  myspell-en-us | hunspell-dictionary | myspell-dictionary  

Versions of packages thunderbird suggests:
pn  apparmor  
pn  fonts-lyx 
ii  libgssapi-krb5-2  1.18.3-5
ii  libgtk2.0-0   2.24.33-2