Bug#941060: chromium: When will the upgrade to v77 reach debian?

[jim_p]

Package: chromium
Version: 76.0.3809.100-1
Followup-For: Bug #941060

It has been a month since the release of chromium 77 and still nothing in the
repos. Why such a big delay?
Plus, on 2 weeks max, chromium 78 will be released from upstream, so don't
bother building it.

I will probably move to chrome when 78 comes out. Thanks for nothing.



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/2 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:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages chromium depends on:
ii  chromium-common  76.0.3809.100-1
ii  libasound2   1.1.8-1
ii  libatk-bridge2.0-0   2.34.0-3
ii  libatk1.0-0  2.34.0-1
ii  libatomic1   9.2.1-8
ii  libatspi2.0-02.34.0-3
ii  libavcodec58 10:4.2.1-dmo3
ii  libavformat5810:4.2.1-dmo3
ii  libavutil56  10:4.2.1-dmo3
ii  libc62.29-2
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcups2 2.3.0-5
ii  libdbus-1-3  1.12.16-2
ii  libdrm2  2.4.99-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.9-1
ii  libflac8 1.3.3-1
ii  libfontconfig1   2.13.1-2+b1
ii  libfreetype6 2.9.1-4
ii  libgcc1  1:9.2.1-8
ii  libgdk-pixbuf2.0-0   2.38.2+dfsg-1
ii  libglib2.0-0 2.62.0-3
ii  libgtk-3-0   3.24.12-1
ii  libharfbuzz0b2.6.2-1
ii  libicu63 63.2-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libjsoncpp1  1.7.4-3+b1
ii  liblcms2-2   2.9-3+b1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.21-2
ii  libnss3  2:3.45-1
ii  libopenjp2-7 2.3.0-3
ii  libopus0 1.3-1+b1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  1.42.4-7
ii  libpci3  1:3.6.2-2
ii  libpng16-16  1.6.37-1
ii  libpulse013.0-2
ii  libre2-5 20190901+dfsg-1
ii  libsnappy1v5 1.1.7-1+b1
ii  libstdc++6   9.2.1-8
ii  libvpx6  1.8.1-dmo1
ii  libwebp6 0.6.1-2+b1
ii  libwebpdemux20.6.1-2+b1
ii  libwebpmux3  0.6.1-2+b1
ii  libx11-6 2:1.6.8-1
ii  libx11-xcb1  2:1.6.8-1
ii  libxcb1  1.13.1-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.2.0-2
ii  libxdamage1  1:1.1.5-1
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.32-2.1
ii  libxss1  1:1.2.3-1
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1+b1

Versions of packages chromium recommends:
ii  chromium-sandbox  76.0.3809.100-1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.3-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox 76.0.3809.100-1
ii  dunst [notification-daemon]  1.4.1-1
ii  fonts-liberation 1:1.07.4-10
ii  libgl1-mesa-dri  19.1.6-1
pn  libu2f-udev  
ii  notification-daemon  3.20.0-4
pn  system-config-printer
pn  upower   

Versions of packages chromium-sandbox depends on:
ii  libatomic1  9.2.1-8
ii  libc6   2.29-2
ii  libgcc1 1:9.2.1-8
ii  libstdc++6  9.2.1-8

-- no debconf information

Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account

[Jean-Marc]

On Wed, 09 Oct 2019 17:40:15 +0200 Jean-Marc  wrote:
> Package: gnome-shell
> Version: 3.34.0-2
> Severity: normal
> 
> Dear Maintainer,

I would like to re-phrase :

> Since the last upgrade from gnome-shell 3.30 to 3.34, the gnome-shell does 
> not take the gsettings org.gnome.desktop.peripherals.keyboard numlock-state 
> into account and always start with org.gnome.desktop.peripherals.keyboard 
> numlock-state set to false.

I should have written :
[...] and always start as if the value org.gnome.desktop.peripherals.keyboard 
numlock-state is set to false.

It means, to be as clear as possible I can start with numlock-state set to true 
but the numpad will not render numbers.

Hitting the numlock key changes the value of this setting and the behavior of 
the shell.

Right now, the numlock-state value is false and the numpad returns numbers.

Regards,

Jean-Marc 
https://6jf.be/keys/ED863AD1.txt


pgphxaKb1AFVn.pgp
Description: PGP signature

Bug#909289: #909289: ITP -> RFP (wontfix)

[Andrius Merkys]

retitle -1 RFP: coot-reference-structures -- high resolution PDB files used as 
reference structures by coot
noowner -1
tags -1 + wontfix
unblock 897673 by -1
thanks

The license of the Protein DataBank entries explicitly forbids redistribution
of modified data using the same file names [1], what may cause problems with
getting coot-reference-structures in main. Nevertheless, coot, which depends on
coot-reference-structures, is usable without the package, thus I disown the bug
report.

Andrius

[1] ftp://ftp.wwpdb.org/pub/pdb/advisory.txt

Bug#942084: gamin FTCBFS: uses AC_RUN_IFELSE

[Helmut Grohne]

Source: gamin
Version: 0.1.10-6
Tags: patch upstream
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

gamin fails to cross build from source, because it uses AC_RUN_IFELSE
without a cross default or a cached variable. In this case, the relevant
check is a sanity check (for working abstract unix sockets when the user
requested use of abstract unix sockets). It is reasonable to skip the
check for cross compilation only. Please consider applying the attached
patch.

Helmut
--- gamin-0.1.10.orig/configure.in
+++ gamin-0.1.10/configure.in
@@ -427,10 +427,10 @@
   else 
 exit (0);
 ]])],
-  [have_abstract_sockets=yes],
-  [have_abstract_sockets=no])
+  [have_abstract_sockets=yes; AC_MSG_RESULT(yes)],
+  [have_abstract_sockets=no; AC_MSG_RESULT(no)],
+	  [have_abstract_sockets=yes; AC_MSG_RESULT(cross compiling... guessing yes)])
 AC_LANG_POP(C)
-AC_MSG_RESULT($have_abstract_sockets)
 
 if test x$enable_abstract_sockets = xyes; then
 if test x$have_abstract_sockets = xno; then

Bug#942079: [Pkg-utopia-maintainers] Bug#942079: network-manager: sometimes forgets my wifi password

[Russell Coker]

KDE. Passwords stored per user. When I resume the desktop is locked but the 
keyring isn't.

I'll look into getting logs.

On 10 October 2019 10:37:15 am AEDT, Michael Biebl  wrote:
>Control: tags -1 + moreinfo
>
>Am 10.10.19 um 01:03 schrieb Russell Coker:
>> Package: network-manager
>> Version: 1.14.6-2
>> Severity: normal
>> 
>> Sometimes when I open the lid on my laptop to unsuspend it after
>logging in I
>> get prompted for my wifi password.  This happens about twice a month.
> One
>> network this happens is on my office network and I can't be certain
>that
>> nothing was changed there (although the IT people assure me they
>didn't change
>> anything).  The other network is my home network where I can be
>certain that
>> nothing changes.
>
>
>Can you provided a verbose debug log from NetworkManager when that
>happens? https://wiki.gnome.org/Projects/NetworkManager/Debugging has
>some debugging hints.
>
>How are the passwords stored? System-wide or in the user
>session/keyring? If the latter, which desktop environment is this?
>When you resume, is your desktop session locked? Is your keyring locked
>as well?

-- 
Sent from my Huawei Mate 9 with K-9 Mail.

Bug#942083: lutok FTCBFS: does not pass --host to ./configure

[Helmut Grohne]

Source: lutok
Version: 0.4+dfsg-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

lutok fails to cross build from source, because it does not pass --host
to ./configure. Usually, the easiest fix is using dh_auto_configure, but
this ./configure fails recognizing --runstatedir, so one has to pass
--host explicitly. Additionally, the parameter passed to --libdir
confuses build and host. Refer to man dpkg-architecture for a definition
of these terms. It also confuses gnu-type and multiarch. Presently this
only makes a difference on i386. Refer to man dpkg-architecture for a
definition of these terms. Please consider applying the attached patch.

Helmut
diff --minimal -Nru lutok-0.4+dfsg/debian/changelog 
lutok-0.4+dfsg/debian/changelog
--- lutok-0.4+dfsg/debian/changelog 2019-08-02 00:52:59.0 +0200
+++ lutok-0.4+dfsg/debian/changelog 2019-10-10 06:15:11.0 +0200
@@ -1,3 +1,12 @@
+lutok (0.4+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Pass --host to ./configure.
++ Fix build/host and gnu-type/multiarch confusion.
+
+ -- Helmut Grohne   Thu, 10 Oct 2019 06:15:11 +0200
+
 lutok (0.4+dfsg-1) unstable; urgency=low
 
   * Initial release (Closes: #932350)
diff --minimal -Nru lutok-0.4+dfsg/debian/rules lutok-0.4+dfsg/debian/rules
--- lutok-0.4+dfsg/debian/rules 2019-08-02 00:52:59.0 +0200
+++ lutok-0.4+dfsg/debian/rules 2019-10-10 06:15:11.0 +0200
@@ -15,8 +15,9 @@
 override_dh_auto_configure:
./configure --disable-silent-rules --disable-maintainer-mode  \
--disable-dependency-tracking --build=$(DEB_BUILD_GNU_TYPE) 
\
+   --host=$(DEB_HOST_GNU_TYPE) 
\
--prefix=/usr --includedir=/usr/include 
\
-   --libdir=/usr/lib/$(DEB_BUILD_GNU_TYPE) 
\
+   --libdir=/usr/lib/$(DEB_HOST_MULTIARCH) 
\
--docdir=/usr/share/doc/liblutok3   
\
--htmldir=/usr/share/doc/liblutok-doc/html
 

Bug#804168: #804168 smartmontools: The temperature values in the systemlog not Celcuis but Fahrenheit

[Dmitry Smirnov]

I observe this very behavior on 7.0:

smartd logs:

  Device: /dev/sdc [SAT], SMART Usage Attribute: 194 Temperature_Celsius 
changed from 117 to 116

but according to `smartctl --all /dev/sdc`:


smartctl 7.0 2018-12-30 r4883 [x86_64-linux-4.19.0-5-amd64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD60EFRX-68L0BN1

[...]

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME  FLAG VALUE WORST THRESH TYPE  UPDATED  
WHEN_FAILED RAW_VALUE

194 Temperature_Celsius 0x0022   116   095   000Old_age   Always   
-   36


Package: smartmontools
Version: 7.0-1

--- System information. ---
Architecture: 
Kernel:   Linux 4.19.0-5-amd64

Debian Release: 10.1

--

Best wishes,
 Dmitry Smirnov

---

There is no such thing as public opinion. There is only published opinion.
-- Winston Churchill


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

Bug#941712: Same problem on Debian on VirtualBox

[Graham Coster]

The same problem occurred when I tried re-testing on Debian (rather than 
Raspbian) using VirtualBox 6.0.12 r133076 (Qt5.6.3), hosted on a Mac (macOS 
10.14.6).

Again, HFS partitions were corrupted, but EXT4 partitions were not.


Details of installation;

Package: hfsutils
Version: 3.2.6-14 i386

 Output from uname -a
Linux debian 4.19.0-6-686-pae #1 SMP Debian 4.19.67-2+deb10u1 (2019-09-20) i686 
GNU/Linux

 Output from apt show libc6 2>&1 | grep ^Version
Version: 2.28-10


# kern.log;
Oct 10 14:28:50 debian kernel: [  915.021923] hfsplus: trying to free free 
bnode 0(1)
Oct 10 14:28:50 debian kernel: [  915.021931] hfsplus: trying to free free 
bnode 0(1)
Oct 10 14:28:50 debian kernel: [  915.021937] hfsplus: trying to free free 
bnode 0(1)
Oct 10 14:28:50 debian kernel: [  915.021944] BUG: unable to handle kernel NULL 
pointer dereference at 
Oct 10 14:28:50 debian kernel: [  915.021945] *pdpt = 0a582001 *pde = 

Oct 10 14:28:50 debian kernel: [  915.021947] Oops:  [#1] SMP PTI
Oct 10 14:28:50 debian kernel: [  915.021950] CPU: 0 PID: 1727 Comm: smbd 
Tainted: G   OE 4.19.0-6-686-pae #1 Debian 4.19.67-2+deb10u1
Oct 10 14:28:50 debian kernel: [  915.021951] Hardware name: innotek GmbH 
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Oct 10 14:28:50 debian kernel: [  915.021954] EIP: kmap+0x10/0x50
Oct 10 14:28:50 debian kernel: [  915.021955] Code: 00 00 81 e1 00 00 00 80 89 
e5 e8 bb ee ff ff 5d c3 8d b4 26 00 00 00 00 66 90 3e 8d 74 26 00 55 89 e5 53 
89 c3 e8 10 0d 63 00 <8b> 03 c1 e8 1e 83 f8 02 74 1f 83 f8 03 74 11 89 d8 e8 6a 
fd 16 00
Oct 10 14:28:50 debian kernel: [  915.021956] EAX:  EBX:  ECX: 
0002 EDX: c3cb1d3a
Oct 10 14:28:50 debian kernel: [  915.021957] ESI:  EDI: 1ffc EBP: 
c3cb1d0c ESP: c3cb1d08
Oct 10 14:28:50 debian kernel: [  915.021958] DS: 007b ES: 007b FS: 00d8 GS: 
00e0 SS: 0068 EFLAGS: 00210246
Oct 10 14:28:50 debian kernel: [  915.021959] CR0: 80050033 CR2:  CR3: 
03cf4000 CR4: 000406f0
Oct 10 14:28:50 debian kernel: [  915.021962] DR0:  DR1:  DR2: 
 DR3: 
Oct 10 14:28:50 debian kernel: [  915.021962] DR6: fffe0ff0 DR7: 0400
Oct 10 14:28:50 debian kernel: [  915.021963] Call Trace:
Oct 10 14:28:50 debian kernel: [  915.021968]  hfsplus_bnode_write+0x3d/0x170 
[hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021970]  ? hfsplus_bnode_read+0x5a/0x170 
[hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021972]  
hfsplus_bnode_write_u16+0x2c/0x50 [hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021974]  hfsplus_brec_remove+0x11a/0x180 
[hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021975]  __hfsplus_delete_attr+0x70/0xd0 
[hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021977]  
hfsplus_delete_all_attrs+0x53/0xa0 [hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021979]  hfsplus_delete_cat+0x2ce/0x350 
[hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021981]  ? 0xf7dcc000
Oct 10 14:28:50 debian kernel: [  915.021983]  ? 
hfsplus_hash_dentry+0x158/0x210 [hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021984]  ? 
hfsplus_compare_dentry+0x20e/0x320 [hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021986]  hfsplus_unlink+0x73/0x1c0 
[hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021988]  ? mutex_lock+0x10/0x30
Oct 10 14:28:50 debian kernel: [  915.021990]  ? hfsplus_unlink+0x73/0x1c0 
[hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021991]  ? 
hfsplus_hash_dentry+0x210/0x210 [hfsplus]
Oct 10 14:28:50 debian kernel: [  915.021998]  ? __d_lookup+0x109/0x160
Oct 10 14:28:50 debian kernel: [  915.021999]  ? inode_permission+0x54/0x1b0
Oct 10 14:28:50 debian kernel: [  915.022001]  vfs_unlink+0x107/0x190
Oct 10 14:28:50 debian kernel: [  915.022002]  ? vfs_unlink+0x107/0x190
Oct 10 14:28:50 debian kernel: [  915.022004]  do_unlinkat+0x1dd/0x2a0
Oct 10 14:28:50 debian kernel: [  915.022006]  sys_unlink+0x20/0x30
Oct 10 14:28:50 debian kernel: [  915.022007]  do_fast_syscall_32+0x81/0x1a0
Oct 10 14:28:50 debian kernel: [  915.022009]  entry_SYSENTER_32+0x6b/0xbe
Oct 10 14:28:50 debian kernel: [  915.022010] EIP: 0xb7f5ad61
Oct 10 14:28:50 debian kernel: [  915.022011] Code: f6 ff ff 55 89 e5 8b 55 08 
8b 80 5c cd ff ff 85 d2 74 02 89 02 5d c3 8b 04 24 c3 8b 1c 24 c3 90 90 51 52 
55 89 e5 0f 34 cd 80 <5d> 5a 59 c3 90 90 90 90 8d 76 00 58 b8 77 00 00 00 cd 80 
90 8d 76
Oct 10 14:28:50 debian kernel: [  915.022012] EAX: ffda EBX: 00fcd1d0 ECX: 
00fcd420 EDX: b7e90bd0
Oct 10 14:28:50 debian kernel: [  915.022013] ESI: 00fcd420 EDI: 00faac80 EBP: 
00fe1e50 ESP: bf900f9c
Oct 10 14:28:50 debian kernel: [  915.022013] DS: 007b ES: 007b FS:  GS: 
0033 SS: 007b EFLAGS: 00200296
Oct 10 14:28:50 debian kernel: [  915.022015] Modules linked in: isofs udf 
crc_itu_t fuse nls_utf8 hfsplus joydev hid_generic uas usbhid hid usb_storage 
intel_powerclamp snd_intel8x0 crc32_pclmul snd_ac97_codec ac97_bus 
intel_rapl_perf snd_pcm snd_timer pcspkr serio_raw sg snd soundcore 

Bug#942082: mate-settings-daemon: Repeadly opens and closes alsa mixer in background forever

[Witold Baryluk]

Package: mate-settings-daemon
Version: 1.22.1-1
Severity: normal


user@debian:~$ ps aux | grep 101959
user 101959  0.0  0.0 1238344 41012 ?   Dl   03:45   0:00 
/usr/bin/mate-settings-daemon
user@debian:~$ strace -tt -T -f -p 101959

 
[pid 101959] 03:48:58.298045 <... ioctl resumed> , 0x7ffdf0ab84c0) = -1 
ETIMEDOUT (Connection timed out) <5.116320>
[pid 101959] 03:48:58.298114 ioctl(2, TCGETS, 0x7ffdf0ab9240) = -1 ENOTTY 
(Inappropriate ioctl for device) <0.11>
[pid 101959] 03:48:58.298156 getpid()   = 101959 <0.09>
[pid 101959] 03:48:58.298189 stat("/etc/localtime", {st_mode=S_IFREG|0644, 
st_size=118, ...}) = 0 <0.14>
[pid 101959] 03:48:58.298246 write(2, "\n(mate-settings-daemon:101959): "..., 
137) = 137 <0.22>
[pid 101959] 03:48:58.298294 close(22)  = 0 <0.07>
[pid 101959] 03:48:58.298331 close(21)  = 0 <0.05>
[pid 101959] 03:48:58.298355 openat(AT_FDCWD, "/dev/snd/controlC2", 
O_RDONLY|O_CLOEXEC) = 21 <0.13>
[pid 101959] 03:48:58.298389 fcntl(21, F_SETFD, FD_CLOEXEC) = 0 <0.04>
[pid 101959] 03:48:58.298411 ioctl(21, SNDRV_CTL_IOCTL_CARD_INFO, 
0x7ffdf0ab9570) = 0 <0.05>
[pid 101959] 03:48:58.298433 close(21)  = 0 <0.08>
[pid 101959] 03:48:58.298461 stat("/usr/share/alsa/alsa.conf", 
{st_mode=S_IFREG|0644, st_size=9594, ...}) = 0 <0.09>
[pid 101959] 03:48:58.298516 openat(AT_FDCWD, "/dev/snd/controlC2", 
O_RDONLY|O_CLOEXEC) = 21 <0.07>
[pid 101959] 03:48:58.298542 fcntl(21, F_SETFD, FD_CLOEXEC) = 0 <0.04>
[pid 101959] 03:48:58.298565 ioctl(21, SNDRV_CTL_IOCTL_CARD_INFO, 
0x7ffdf0ab9230) = 0 <0.05>
[pid 101959] 03:48:58.298587 close(21)  = 0 <0.05>
[pid 101959] 03:48:58.298610 openat(AT_FDCWD, "/dev/snd/controlC2", 
O_RDWR|O_CLOEXEC) = 21 <0.07>
[pid 101959] 03:48:58.298636 fcntl(21, F_SETFD, FD_CLOEXEC) = 0 <0.04>
[pid 101959] 03:48:58.298658 ioctl(21, SNDRV_CTL_IOCTL_PVERSION, 
0x7ffdf0ab9584) = 0 <0.04>
[pid 101959] 03:48:58.298680 ioctl(21, SNDRV_CTL_IOCTL_CARD_INFO, 
0x7ffdf0ab95f0) = 0 <0.03>
[pid 101959] 03:48:58.298699 close(21)  = 0 <0.03>
[pid 101959] 03:48:58.298717 openat(AT_FDCWD, "/dev/snd/controlC3", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.06>
[pid 101959] 03:48:58.298742 openat(AT_FDCWD, "/dev/aloadC3", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.05>
[pid 101959] 03:48:58.298766 openat(AT_FDCWD, "/dev/snd/controlC4", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.05>
[pid 101959] 03:48:58.298788 openat(AT_FDCWD, "/dev/aloadC4", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.05>
[pid 101959] 03:48:58.298811 openat(AT_FDCWD, "/dev/snd/controlC5", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.05>
[pid 101959] 03:48:58.298834 openat(AT_FDCWD, "/dev/aloadC5", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.05>
[pid 101959] 03:48:58.298857 openat(AT_FDCWD, "/dev/snd/controlC6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.05>
[pid 101959] 03:48:58.298879 openat(AT_FDCWD, "/dev/aloadC6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.298898 openat(AT_FDCWD, "/dev/snd/controlC7", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.298916 openat(AT_FDCWD, "/dev/aloadC7", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.298935 openat(AT_FDCWD, "/dev/snd/controlC8", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.298954 openat(AT_FDCWD, "/dev/aloadC8", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.298972 openat(AT_FDCWD, "/dev/snd/controlC9", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.298991 openat(AT_FDCWD, "/dev/aloadC9", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299009 openat(AT_FDCWD, "/dev/snd/controlC10", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299028 openat(AT_FDCWD, "/dev/aloadC10", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299046 openat(AT_FDCWD, "/dev/snd/controlC11", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299065 openat(AT_FDCWD, "/dev/aloadC11", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299084 openat(AT_FDCWD, "/dev/snd/controlC12", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299102 openat(AT_FDCWD, "/dev/aloadC12", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299120 openat(AT_FDCWD, "/dev/snd/controlC13", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) <0.04>
[pid 101959] 03:48:58.299139 

Bug#942081: utox: segfault on setting proxy settings

[Jeff Cliff]

Package: utox
Version: 0.17.1-1
Severity: normal

Dear Maintainer,

Attempting to turn on the proxy settings results in a segfault
1) navigate to advanced settings
2) put ip address for localhost into settings field, port in port field
  (can't confirm whether or not proxy is working since...it crashes)
3) click on the enable toggle..
boom segfault

stack:
#0  0x771d6d2f in __GI___poll (fds=0x7fffdef8, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x76bc8cf7 in  () at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x76bca91a in xcb_wait_for_event ()
at /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7781cb88 in _XReadEvents ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#4  0x7780bae8 in XNextEvent ()
at /usr/lib/x86_64-linux-gnu/libX11.so.6
#5  0x55569dfc in main (argc=, argv=)
at ./src/xlib/main.c:849

debian: sid
utox:
  Installed: 0.17.1-1
  Candidate: 0.17.1-1
libxcb1:
  Installed: 1.13.1-2
  Candidate: 1.13.1-2

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages utox depends on:
ii  libc6   2.29-2
ii  libdbus-1-3 1.12.16-2
ii  libfontconfig1  2.13.1-2+b1
ii  libfreetype62.9.1-4
ii  libminini1  1.2.a+ds-4
ii  libopenal1  1:1.19.1-1+b1
ii  libqrcodegen1   1.5.0-2
ii  libsodium23 1.0.18-1
ii  libstb0 0.0~git20190817.1.052dce1-1
ii  libtoxcore2 0.2.10-1+b1
ii  libv4lconvert0  1.18.0-1
ii  libvpx6 1.8.1-2
ii  libx11-62:1.6.8-1
ii  libxext62:1.3.3-1+b2
ii  libxrender1 1:0.9.10-1

utox recommends no packages.

utox suggests no packages.

-- no debconf information

Bug#942080: libmatemixer-alsa: Blocking mixer?

[Witold Baryluk]

Package: libmatemixer0
Version: 1.22.0-1
Severity: normal
File: libmatemixer-alsa

Anytime I start MATE the access to sound devices becomes very slow,
even just doing `aplay -l` takes 4 seconds.

Similarly:

user@debian:~$ mate-volume-control

(mate-volume-control:101829): libmatemixer-alsa-WARNING **: 03:40:51.386: 
Failed to load mixer elements for hw:1: Connection timed out

(mate-volume-control:101829): GLib-GIO-WARNING **: 03:41:11.866: Your 
application did not unregister from D-Bus before destruction. Consider using 
g_application_run().

(mate-volume-control:101829): Gtk-CRITICAL **: 03:41:11.902: gtk_main_quit: 
assertion 'main_loops != NULL' failed

(mate-volume-control:101829): libmatemixer-alsa-WARNING **: 03:41:22.106: 
Failed to load mixer elements for hw:1: Connection timed out

almost forever.


This is with pulseaudio not running.

user@debian:~$ sudo lsof /dev/snd/*
lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
  Output information may be incomplete.
COMMAND  PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
mate-sett 101758 user   17u   CHR  116,6  0t0 127703736 /dev/snd/controlC0
mate-sett 101758 user   18u   CHR 116,14  0t0  72716494 /dev/snd/controlC2
mate-volu 101809 user   11u   CHR  116,6  0t0 127703736 /dev/snd/controlC0
mate-volu 101809 user   12u   CHR 116,14  0t0  72716494 /dev/snd/controlC2
mate-volu 101829 user   11u   CHR  116,6  0t0 127703736 /dev/snd/controlC0
mate-volu 101829 user   12u   CHR 116,14  0t0  72716494 /dev/snd/controlC2
mate-volu 101829 user   13u   CHR  116,3  0t0   6682191 /dev/snd/controlC1
mate-volu 101829 user   14u   CHR  116,3  0t0   6682191 /dev/snd/controlC1
user@debian:~$ 

$ time aplay -l
 List of PLAYBACK Hardware Devices 
card 0: M20 [MIYO USB Audio 2.0], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 8: HDMI 2 [HDMI 2]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 9: HDMI 3 [HDMI 3]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 10: HDMI 4 [HDMI 4]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 2: HDMI [HDA ATI HDMI], device 11: HDMI 5 [HDMI 5]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

real  0m3.961s
user  0m0.004s
sys 0m0.000s
$


Same from root.

If I logout out of MATE and execute `aplay -l` from terminal as normal user or
root, it finishes in 20 miliseconds.

Rest of alsa configuration is standard Debian config.




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

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

Versions of packages libmatemixer0:amd64 depends on:
ii  iso-codes4.4-1
ii  libasound2   1.1.8-1
ii  libc62.29-2
ii  libglib2.0-0 2.62.1-1
ii  libmatemixer-common  1.22.0-1
ii  libpulse-mainloop-glib0  13.0-2
ii  libpulse013.0-2

libmatemixer0:amd64 recommends no packages.

libmatemixer0:amd64 suggests no packages.

-- no debconf information

Bug#941958: hardware issue indeed resolves this issue

[Antonio Russo]

Control: severity -1 wishlist

A firmware upgrade on my X470 Taichi Ultimate to P3.4 (from P3.2)
resolved the UUID collisions (AMD Ryzen 3700X).

As terrifying as this was for me, the solution is to have hardware
that functions properly. I think there is merit in leaving this open
so that other people with buggy firmware know to upgrade their
firmware, but adding a test for a UUID collisions is not a grave
defect.

Bug#930462: ERROR: unable to download video data: HTTP Error 403: Forbidden

[Ryan Tandy]

Package: youtube-dl
Followup-For: Bug #930462

Dear Maintainer,

This bug still affects the version in stable. The patch to fix it is 
tiny; would you consider backporting it?

https://github.com/ytdl-org/youtube-dl/commit/027ffdca0d3174963a4269ce8de8519cfed7a12c

The attached debdiff fixes this bug and one other annoying issue. I 
prepared and tested it on a stable system. I would be happy to handle 
the paperwork for a stable update if you would be willing to sponsor the 
actual upload.
diff -Nru youtube-dl-2019.01.17/debian/changelog 
youtube-dl-2019.01.17/debian/changelog
--- youtube-dl-2019.01.17/debian/changelog  2019-04-27 14:03:56.0 
-0700
+++ youtube-dl-2019.01.17/debian/changelog  2019-10-09 18:38:54.0 
-0700
@@ -1,3 +1,12 @@
+youtube-dl (2019.01.17-1.1+deb10u1) buster; urgency=medium
+
+  * Non-maintainer upload.
+  * Add upstream patch to fix 403 Forbidden errors on some YouTube videos.
+(Closes: #930462)
+  * Add upstream patch to fix YouTube video titles not being extracted.
+
+ -- Ryan Tandy   Thu, 10 Oct 2019 01:38:54 +
+
 youtube-dl (2019.01.17-1.1) unstable; urgency=medium
 
   [ Salvatore Bonaccorso ]
diff -Nru youtube-dl-2019.01.17/debian/patches/series 
youtube-dl-2019.01.17/debian/patches/series
--- youtube-dl-2019.01.17/debian/patches/series 2019-04-27 14:03:56.0 
-0700
+++ youtube-dl-2019.01.17/debian/patches/series 2019-10-09 18:38:54.0 
-0700
@@ -1,3 +1,5 @@
 skip_support_file_installation.patch
 disable-autoupdate-mechanism.patch
 youtube-Fix-extraction.patch
+youtube-Use-sp-field-value-for-signature-field-name.patch
+youtube-improve-title-and-description-extraction.patch
diff -Nru 
youtube-dl-2019.01.17/debian/patches/youtube-improve-title-and-description-extraction.patch
 
youtube-dl-2019.01.17/debian/patches/youtube-improve-title-and-description-extraction.patch
--- 
youtube-dl-2019.01.17/debian/patches/youtube-improve-title-and-description-extraction.patch
 1969-12-31 16:00:00.0 -0800
+++ 
youtube-dl-2019.01.17/debian/patches/youtube-improve-title-and-description-extraction.patch
 2019-10-09 18:38:54.0 -0700
@@ -0,0 +1,49 @@
+From 8dbf751aa241475dd8a7a6d3040713b5874fd057 Mon Sep 17 00:00:00 2001
+From: Remita Amine 
+Date: Tue, 30 Jul 2019 00:13:33 +0100
+Subject: [PATCH] [youtube] improve title and description extraction(closes
+ #21934)
+
+---
+ youtube_dl/extractor/youtube.py | 15 +++
+ 1 file changed, 3 insertions(+), 12 deletions(-)
+
+diff --git a/youtube_dl/extractor/youtube.py b/youtube_dl/extractor/youtube.py
+index b2c714505..9a182fcf6 100644
+--- a/youtube_dl/extractor/youtube.py
 b/youtube_dl/extractor/youtube.py
+@@ -1820,16 +1820,11 @@ class YoutubeIE(YoutubeBaseInfoExtractor):
+ video_details = try_get(
+ player_response, lambda x: x['videoDetails'], dict) or {}
+ 
+-# title
+-if 'title' in video_info:
+-video_title = video_info['title'][0]
+-elif 'title' in player_response:
+-video_title = video_details['title']
+-else:
++video_title = video_info.get('title', [None])[0] or 
video_details.get('title')
++if not video_title:
+ self._downloader.report_warning('Unable to extract video title')
+ video_title = '_'
+ 
+-# description
+ description_original = video_description = 
get_element_by_id("eow-description", video_webpage)
+ if video_description:
+ 
+@@ -1854,11 +1849,7 @@ class YoutubeIE(YoutubeBaseInfoExtractor):
+ ''', replace_url, video_description)
+ video_description = clean_html(video_description)
+ else:
+-fd_mobj = re.search(r'
+Date: Fri, 10 May 2019 08:36:10 +0700
+Subject: [PATCH] [youtube] Use sp field value for signature field name (closes
+ #18841, closes #18927, closes #21028)
+
+---
+ youtube_dl/extractor/youtube.py | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/youtube_dl/extractor/youtube.py b/youtube_dl/extractor/youtube.py
+index da202b9bc..8619f3838 100644
+--- a/youtube_dl/extractor/youtube.py
 b/youtube_dl/extractor/youtube.py
+@@ -1987,7 +1987,8 @@ class YoutubeIE(YoutubeBaseInfoExtractor):
+ 
+ signature = self._decrypt_signature(
+ encrypted_sig, video_id, player_url, age_gate)
+-url += '=' + signature
++sp = try_get(url_data, lambda x: x['sp'][0], compat_str) 
or 'signature'
++url += '&%s=%s' % (sp, signature)
+ if 'ratebypass' not in url:
+ url += '=yes'
+ 
+-- 
+2.20.1
+

Bug#935653: 100% CPU usage for a long time

[Pascal Giard]

Dear maintainer,

Recently unattended-upgrades started to consume a LOT more CPU time than
before.

Similarly to the original report, I looked at what strace gets in terms of
statistics, here it is:
strace: Process 5193 detached
% time seconds  usecs/call callserrors syscall
-- --- --- - - 
100,004,762247   2   2288315   1703451 stat
  0,000,51   0   100   read
  0,000,15   020   openat
  0,000,08   020   close
  0,000,05   020   fstat
  0,000,05   020   fcntl
-- --- --- - - 
100.004,762331   2288495   1703451 total

Looks odd, no?

It is so bothering that for now I've disabled unattended-upgrades on all 3
laptops. Manual update + upgrade requires a fraction of the resources
currently required by unattended-upgrades.

I hope this issue gets sorted out. Please let me know if there's something
else I can do to provide useful information.

Thanks,

-Pascal
--
Homepage (http://pascal.giard.info)
École de technologie supérieure (http://etsmtl.ca)

Bug#935614: libinfinity: FTBFS on all architectures

[Paul Wise]

On Wed, 9 Oct 2019 09:24:58 +0200 Petter Reinholdtsen wrote:

> I had a look, and the build fail here too, the exact same way with a
> session test failing with.

I built the unstable code on buster and the test succeeded, so I think
this issue is caused by one of the dependencies. libxml2 is the exact
same version between unstable and buster so it cannot be that.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#942079: [Pkg-utopia-maintainers] Bug#942079: network-manager: sometimes forgets my wifi password

[Michael Biebl]

Control: tags -1 + moreinfo

Am 10.10.19 um 01:03 schrieb Russell Coker:
> Package: network-manager
> Version: 1.14.6-2
> Severity: normal
> 
> Sometimes when I open the lid on my laptop to unsuspend it after logging in I
> get prompted for my wifi password.  This happens about twice a month.  One
> network this happens is on my office network and I can't be certain that
> nothing was changed there (although the IT people assure me they didn't change
> anything).  The other network is my home network where I can be certain that
> nothing changes.


Can you provided a verbose debug log from NetworkManager when that
happens? https://wiki.gnome.org/Projects/NetworkManager/Debugging has
some debugging hints.

How are the passwords stored? System-wide or in the user
session/keyring? If the latter, which desktop environment is this?
When you resume, is your desktop session locked? Is your keyring locked
as well?

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#941853: crypt(3) should be provided by libxcrypt

[Marco d'Itri]

On Oct 09, Aurelien Jarno  wrote:

> I have implemented the first option in the libxcrypt branch:
> 
> https://salsa.debian.org/glibc-team/glibc/tree/libxcrypt
And here you can see a tentative libxcrypt package: does it look right 
to you?

https://salsa.debian.org/md/libxcrypt/blob/master/debian/control

├── libcrypt1
│   ├── DEBIAN
│   │   ├── control
│   │   ├── md5sums
│   │   ├── shlibs
│   │   ├── symbols
│   │   └── triggers
│   └── usr
│   ├── lib
│   │   └── x86_64-linux-gnu
│   │   ├── libcrypt.so.1 -> libcrypt.so.1.1.0
│   │   └── libcrypt.so.1.1.0
│   └── share
│   └── doc
│   └── libcrypt1
│   ├── changelog.Debian.gz
│   ├── changelog.gz
│   └── copyright

├── libcrypt1-dev
│   ├── DEBIAN
│   │   ├── control
│   │   └── md5sums
│   └── usr
│   ├── include
│   │   └── crypt.h
│   ├── lib
│   │   └── x86_64-linux-gnu
│   │   ├── libcrypt.a
│   │   ├── libcrypt.so -> libcrypt.so.1.1.0
│   │   └── pkgconfig
│   │   ├── libcrypt.pc -> libxcrypt.pc
│   │   └── libxcrypt.pc
│   └── share
│   ├── doc
│   │   ├── libcrypt1
│   │   │   ├── README.md.gz
│   │   │   └── TODO.md.gz
│   │   └── libcrypt1-dev -> libcrypt1
│   └── man
│   ├── man3
│   │   ├── crypt.3.gz
│   │   ├── crypt_checksalt.3.gz
│   │   ├── crypt_gensalt.3.gz
│   │   ├── crypt_gensalt_ra.3.gz -> crypt_gensalt.3.gz
│   │   ├── crypt_gensalt_rn.3.gz -> crypt_gensalt.3.gz
│   │   ├── crypt_preferred_method.3.gz
│   │   ├── crypt_r.3.gz -> crypt.3.gz
│   │   ├── crypt_ra.3.gz -> crypt.3.gz
│   │   └── crypt_rn.3.gz -> crypt.3.gz
│   └── man5
│   └── crypt.5.gz

├── libcrypt1-udeb
│   ├── DEBIAN
│   │   └── control
│   └── usr
│   └── lib
│   ├── libcrypt.so.1 -> libcrypt.so.1.1.0
│   └── libcrypt.so.1.1.0

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#931676: [baloo-kf5] suspend doesn't work

[Nicholas D Steeves]

On Tue, Jul 09, 2019 at 12:05:23PM +0500, Alex Volkov wrote:
> Package: baloo-kf5
> Version: 5.54.0-1
> Severity: normal
> 
> --- Please enter the report below this line. ---
> 
> When trying to suspend indexing process with either 'balooctl suspend' or 
> with 
> the button in KInfocentre, it says "File Indexing suspended", 
> 'baloo_file_extractor' gets killed and the button turns to "Resume", but in a 
> second or so 'baloo_file_extractor' spawns back and the indexing resumes 
> again 
> (the button turns to "Suspend"). However f*cked up its developers are, I 
> doubt 
> this is intended behavior.
> 

I can confirm this.  It's a major battery drainer and needs to be
fixed.  I've been manually using balooctl stop to work around the
issue in the meantime.  Also, due to another bug I sometimes need to
killall baloo_file_extractor, which unfortunately doesn't handle
-SIGTERM properly--so I don't think this can honestly be recommended
as a mitigation.


Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#942079: network-manager: sometimes forgets my wifi password

[Russell Coker]

Package: network-manager
Version: 1.14.6-2
Severity: normal

Sometimes when I open the lid on my laptop to unsuspend it after logging in I
get prompted for my wifi password.  This happens about twice a month.  One
network this happens is on my office network and I can't be certain that
nothing was changed there (although the IT people assure me they didn't change
anything).  The other network is my home network where I can be certain that
nothing changes.

I expect that I should only have to enter a password once for each Wifi
network.

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

Kernel: Linux 5.2.1 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Enforcing - Policy name: default

Versions of packages network-manager depends on:
ii  adduser3.118
ii  dbus   1.12.16-1
ii  init-system-helpers1.56+nmu1
ii  libaudit1  1:2.8.4-3
ii  libbluetooth3  5.50-1
ii  libc6  2.28-10
ii  libcurl3-gnutls7.64.0-4
ii  libglib2.0-0   2.58.3-2+deb10u1
ii  libgnutls303.6.7-4
ii  libjansson42.12-1
ii  libmm-glib01.10.0-1
ii  libndp01.6-1+b1
ii  libnewt0.520.52.20-8
ii  libnm0 1.14.6-2
ii  libpam-systemd 241-7~deb10u1
ii  libpolkit-agent-1-00.105-25
ii  libpolkit-gobject-1-0  0.105-25
ii  libpsl50.20.2-2
ii  libreadline7   7.0-5
ii  libselinux12.8-1+b1
ii  libsystemd0241-7~deb10u1
ii  libteamdctl0   1.28-1
ii  libudev1   241-7~deb10u1
ii  libuuid1   2.33.1-0.1
ii  lsb-base   10.2019051400
ii  policykit-10.105-25
ii  udev   241-7~deb10u1
ii  wpasupplicant  2:2.7+git20190128+0c1e29f-6+deb10u1

Versions of packages network-manager recommends:
ii  crda 3.18-1
ii  dnsmasq-base [dnsmasq-base]  2.80-1
ii  iptables 1.8.2-4
ii  isc-dhcp-client  4.4.1-2
pn  modemmanager 
ii  ppp  2.4.7-2+4.1

Versions of packages network-manager suggests:
pn  libteam-utils  

-- no debconf information

Bug#940138: linux-image-5.2.0-2-amd64: panic in pci_assign_unassigned_root_bus_resources

[Kendy Kutzner]

Are there any news? Is there any more debug info that I could provide?

Kendy

On Fri, Sep 13, 2019 at 8:16 AM Kendy Kutzner  wrote:
>
> Attaching the requested output.
>
> One thing I noted: The crash happens reliably at about 0.6s. The dmesg
> output from a 4.19 start looks like this:
>
> [0.478325] Unpacking initramfs...
> [1.254383] Freeing initrd memory: 53188K
>
> Is there a way to enable more verbosity for those 700 milliseconds?
>
> Kendy

Bug#942073: marisa: perl bindings are broken when linked with gcc-9

[Boyuan Yang]

Control: tags -1 + help

Since I'm not quite familiar with Perl, any help or suggestions would
be highly appreciated.

Thanks,
Boyuan Yang

在 2019-10-09三的 23:45 +0300，Niko Tyni写道：
> Package: libmarisa-perl
> Version: 0.2.5-3
> Severity: grave
> Control: block 935737 with -1
> 
> As noticed by the autopkgtest checks, the marisa Perl bindings are
> totally broken in sid after the recent Perl 5.30 rebuild:
> 
>   $ perl -e 'use marisa'
>   Can't load '/usr/lib/x86_64-linux-
> gnu/perl5/5.30/auto/marisa/marisa.so' for module marisa:
> /usr/lib/x86_64-linux-gnu/perl5/5.30/auto/marisa/marisa.so: undefined
> symbol: _ZTVN10__cxxabiv120__si_class_type_infoE at /usr/lib/x86_64-
> linux-gnu/perl/5.30/DynaLoader.pm line 193.
>at /usr/lib/x86_64-linux-gnu/perl5/5.30/marisa.pm line 11.
>   Compilation failed in require at -e line 1.
>   BEGIN failed--compilation aborted at -e line 1.
>  
> Rebuilding marisa in testing with Perl 5.28 triggers the same
> behaviour,
> so it's not a change in Perl 5.30 that broke it. The previous sid
> build
> in July is not broken.
> 
> It looks like this regressed with the gcc 8 -> 9 move. Linking the
> DSO manually with gcc-8 makes it go away, as seen below.
> 
> I have no idea what goes wrong here, but I noticed that broken
> versions
> of blib/arch/auto/marisa/marisa.so have no NEEDED entry for
> libmarisa.so.0
> (as seen with 'objdump -p').
> 
>  reproduce the error 
> 
>   # apt build-dep libmarisa-perl
>   $ ./debian/rules build
>   $ cd bindings/perl
>   $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I
> blib/lib -e 'use marisa'
>   Can't load 'blib/arch/auto/marisa/marisa.so' for module marisa:
> blib/arch/auto/marisa/marisa.so: undefined symbol:
> _ZTVN10__cxxabiv120__si_class_type_infoE at /usr/lib/x86_64-linux-
> gnu/perl/5.30/DynaLoader.pm line 193.
>at blib/lib/marisa.pm line 11.
>   Compilation failed in require at -e line 1.
>   BEGIN failed--compilation aborted at -e line 1.
> 
>  explicitly link with gcc-8, no error ---
> 
>   # apt install gcc-8
>   $ gcc-8 -shared -L/usr/local/lib -L../../lib/marisa/.libs -lmarisa
> -fstack-protector -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  marisa-
> swig.o marisa-swig_wrap.o  -o blib/arch/auto/marisa/marisa.so
>   $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I
> blib/lib -e 'use marisa'
> 
>  explicitly link with gcc-9, same error again ---
> 
>   $ gcc-9 -shared -L/usr/local/lib -L../../lib/marisa/.libs -lmarisa
> -fstack-protector -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  marisa-
> swig.o marisa-swig_wrap.o  -o blib/arch/auto/marisa/marisa.so
>   $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I
> blib/lib -e 'use marisa'
>   Can't load 'blib/arch/auto/marisa/marisa.so' for module marisa:
> blib/arch/auto/marisa/marisa.so: undefined symbol:
> _ZTVN10__cxxabiv120__si_class_type_infoE at /usr/lib/x86_64-linux-
> gnu/perl/5.30/DynaLoader.pm line 193.
>at blib/lib/marisa.pm line 11.
>   Compilation failed in require at -e line 1.
>   BEGIN failed--compilation aborted at -e line 1.
> 


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

Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f

[Nicholas D Steeves]

Package: baloo-kf5
Version: 5.54.0-1
Severity: serious
Justification: poor experience will cause user to give up on baloo; worse than 
GNOME

Hi,

Recently baloo has been crashing whenever I log in.  Today I decided it
was a persistent and serious enough problem that a serious bug was
warranted.  I've attached the backtrace produced by drkonqi.  Here is
some additional info that I hope will help quickly resolve this bug.

$ balooctl start
QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::applicationDirPath: Please instantiate the QApplication 
object first
This process needs a QCoreApplication instance in order to use KCrash
"/home/sten/jack_capture_90.mp3" id seems to have changed. Perhaps baloo was 
not running, and this file was deleted + re-created
mdb.c:3124: Assertion 'pglast <= env->me_pglast' failed in mdb_freelist_save()
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = baloo_file_extractor path = /usr/bin pid = 15575
KCrash: Arguments: /usr/bin/baloo_file_extractor 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from 
kdeinit
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...

$ balooctl clear /home/sten/jack_capture_90.mp3
Skipping: /home/sten/jack_capture_90.mp3 Reason: Not yet indexed
File(s) cleared

$ balooctl index /home/sten/jack_capture_90.mp3
Indexing /home/sten/jack_capture_90.mp3
mdb.c:3124: Assertion 'pglast <= env->me_pglast' failed in mdb_freelist_save()
Aborted

$ balooctl status
Baloo File Indexer is running
Indexer state: Indexing file content
Indexed 57061 / 57062 files
Current size of index is 703.08 MiB

$ balooctl  indexSize
Actual Size: 703.08 MiB
Expected Size: 456.43 MiB

   PostingDB: 111.95 MiB24.527 %
  PositionDB: 189.31 MiB41.476 %
DocTerms:  58.71 MiB12.862 %
DocFilenameTerms:   6.20 MiB 1.357 %
   DocXattrTerms:0 B 0.000 %
  IdTree: 996.00 KiB 0.213 %
  IdFileName:   4.65 MiB 1.019 %
 DocTime:   2.57 MiB 0.563 %
 DocData:   3.51 MiB 0.769 %
   ContentIndexingDB:   4.00 KiB 0.001 %
 FailedIdsDB:0 B 0.000 %
 MTimeDB:   1.20 MiB 0.263 %

...wait a while, then

$ balooctl stop

...wait a while.  Baloo fails to stop.

$ ps xa | grep /usr/bin/baloo_file
$ gdb -p $THAT_PID
$ kill $THAT_PID

Result: no backtrace

$ gdb /usr/bin/baloo_file

Starting program: /usr/bin/baloo_file 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x72c7e700 (LWP 17185)]
[New Thread 0x7215b700 (LWP 17186)]
[Detaching after fork from child process 17187]
QCoreApplication::arguments: Please instantiate the QApplication object first
QCoreApplication::applicationDirPath: Please instantiate the QApplication 
object first
This process needs a QCoreApplication instance in order to use KCrash
"/home/sten/jack_capture_90.mp3" id seems to have changed. Perhaps baloo was 
not running, and this file was deleted + re-created
mdb.c:3124: Assertion 'pglast <= env->me_pglast' failed in mdb_freelist_save()
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = baloo_file_extractor path = /usr/bin pid = 17187
KCrash: Arguments: /usr/bin/baloo_file_extractor 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from 
kdeinit
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...
QSocketNotifier: Invalid socket 18 and type 'Read', disabling...
QSocketNotifier: Invalid socket 10 and type 'Read', disabling...

Result: CRASH.  Drkonqi provides a bt for baloo_file_extractor.  I've attached 
that one too.


Regards,
Nicholas

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

Kernel: Linux 4.19.72-rt25 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages baloo-kf5 depends on:
ii  kio  5.54.1-1
ii  libc62.28-10
ii  libkf5baloo5 5.54.0-1
ii  libkf5balooengine5   5.54.0-1
ii  libkf5configcore55.54.0-1+deb10u1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5filemetadata3  5.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5idletime5  5.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5solid5 5.54.0-1
ii  libqt5core5a 5.11.3+dfsg1-1
ii  libqt5dbus5  5.11.3+dfsg1-1
ii  libqt5gui5   

Bug#866122: kernel resolution

[Ryan Tandy]

Thank you Barry (and Gustavo) for providing closure on this one. :)

On Thu, Sep 12, 2019 at 04:18:00PM -0500, Barry Arndt wrote:

One of the problems was introduced in 4.12, and the other in 4.15.


For posterity I should note that I first encountered the issue back in 
4.9 and bisected it to dc16b553c949e81f37555777dc7bab66d78285a7. It 
looks like the first commit you mentioned largely undoes that one.


In any case I confirmed that cherry-picking those two patches on to an 
affected kernel does fix the issue for me. Thank you!

Bug#941986: [debian-mysql] Bug#941986: Bug#941986: mariadb-client-10.3: InnoTop crashes during use

[Otto Kekäläinen]

> IMHO, if we ship it at all, innotop should be shipped as a separate
> Debian source package with appropriate declared dependencies and
> autopkgtests. This current breakage might be an opportunity to fix that.

Makes sense.

Any volunteer takers?

Bug#942077: /usr/bin/budgie-desktop: Update to GNOME 3.34 breaks Budgie

[David Mohammed]

many thanks for the suggested changes.

Please can you let me know a bit more about your setup to clarify why
the patch is required.

Have you got both gnome-shell and budgie-desktop as sessions?

Are you using GDM3 for your login manager or lightdm login manager?

thanks

On Wed, 9 Oct 2019 at 23:24, Willem Mulder  wrote:
>
> Package: budgie-core
> Version: 10.5-3
> Severity: grave
> File: /usr/bin/budgie-desktop
> Tags: patch
> Justification: renders package unusable
>
> Dear Maintainer,
>
> After upgrading GNOME to 3.34, starting Budgie invariably ends with
> GNOME's error screen (“Oops, something went wrong”). This seems to be
> due to the fact that gnome-session uses systemd as a session manager
> nowadays, resulting in gnome-shell to be started indiscriminately. This
> can be resolved by using gnome-session's builtin session manager. I've
> attached a patch (originally from Arch Linux) to do just that.
>
> Kind regards,
>
> Willem Mulder
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
> LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages budgie-core depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
> ii  gnome-screensaver3.6.1-10+b1
> ii  gnome-session-bin3.34.0-3
> ii  gnome-session-common 3.34.0-3
> ii  gnome-settings-daemon3.34.0-3
> ii  libasound2   1.1.8-1
> ii  libbudgie-plugin010.5-3
> ii  libbudgie-private0   10.5-3
> ii  libbudgietheme0  10.5-3
> ii  libc62.29-2
> ii  libcairo21.16.0-4
> ii  libgdk-pixbuf2.0-0   2.38.2+dfsg-1
> ii  libgirepository-1.0-11.62.0-2
> ii  libgles2 1.1.0-1+b1
> ii  libglib2.0-0 2.62.0-3
> ii  libgnome-bluetooth13 3.34.0-1
> ii  libgnome-desktop-3-183.34.0-2
> ii  libgnome-menu-3-03.32.0-1
> ii  libgtk-3-0   3.24.12-1
> ii  libibus-1.0-51.5.19-4+b1
> ii  libmutter-5-03.34.0-4
> ii  libnotify4   0.7.8-1
> ii  libpeas-1.0-01.22.0-4
> ii  libpolkit-agent-1-0  0.105-26
> ii  libpolkit-gobject-1-00.105-26
> ii  libpulse-mainloop-glib0  13.0-2
> ii  libpulse013.0-2
> ii  libraven010.5-3
> ii  libupower-glib3  0.99.11-1
> ii  libuuid1 2.34-0.1
> ii  libwnck-3-0  3.32.0-1
> ii  libx11-6 2:1.6.8-1
>
> budgie-core recommends no packages.
>
> budgie-core suggests no packages.
>
> -- no debconf information

Bug#942077: /usr/bin/budgie-desktop: Update to GNOME 3.34 breaks Budgie

[Willem Mulder]

Package: budgie-core
Version: 10.5-3
Severity: grave
File: /usr/bin/budgie-desktop
Tags: patch
Justification: renders package unusable

Dear Maintainer,

After upgrading GNOME to 3.34, starting Budgie invariably ends with
GNOME's error screen (“Oops, something went wrong”). This seems to be
due to the fact that gnome-session uses systemd as a session manager
nowadays, resulting in gnome-shell to be started indiscriminately. This
can be resolved by using gnome-session's builtin session manager. I've
attached a patch (originally from Arch Linux) to do just that.

Kind regards,

Willem Mulder

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages budgie-core depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  gnome-screensaver3.6.1-10+b1
ii  gnome-session-bin3.34.0-3
ii  gnome-session-common 3.34.0-3
ii  gnome-settings-daemon3.34.0-3
ii  libasound2   1.1.8-1
ii  libbudgie-plugin010.5-3
ii  libbudgie-private0   10.5-3
ii  libbudgietheme0  10.5-3
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libgdk-pixbuf2.0-0   2.38.2+dfsg-1
ii  libgirepository-1.0-11.62.0-2
ii  libgles2 1.1.0-1+b1
ii  libglib2.0-0 2.62.0-3
ii  libgnome-bluetooth13 3.34.0-1
ii  libgnome-desktop-3-183.34.0-2
ii  libgnome-menu-3-03.32.0-1
ii  libgtk-3-0   3.24.12-1
ii  libibus-1.0-51.5.19-4+b1
ii  libmutter-5-03.34.0-4
ii  libnotify4   0.7.8-1
ii  libpeas-1.0-01.22.0-4
ii  libpolkit-agent-1-0  0.105-26
ii  libpolkit-gobject-1-00.105-26
ii  libpulse-mainloop-glib0  13.0-2
ii  libpulse013.0-2
ii  libraven010.5-3
ii  libupower-glib3  0.99.11-1
ii  libuuid1 2.34-0.1
ii  libwnck-3-0  3.32.0-1
ii  libx11-6 2:1.6.8-1

budgie-core recommends no packages.

budgie-core suggests no packages.

-- no debconf information
diff -Nru budgie-desktop-10.5/debian/changelog 
budgie-desktop-10.5/debian/changelog
--- budgie-desktop-10.5/debian/changelog2019-09-30 19:59:27.0 
+0200
+++ budgie-desktop-10.5/debian/changelog2019-10-09 23:33:24.0 
+0200
@@ -1,3 +1,10 @@
+budgie-desktop (10.5-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use gnome-session's builtin session manager (Closes: #nn)
+
+ -- Willem Mulder   Wed, 09 Oct 2019 23:33:24 
+0200
+
 budgie-desktop (10.5-3) unstable; urgency=medium
 
   * Upload experimental package to unstable
diff -Nru budgie-desktop-10.5/debian/patches/series 
budgie-desktop-10.5/debian/patches/series
--- budgie-desktop-10.5/debian/patches/series   2019-09-14 20:09:47.0 
+0200
+++ budgie-desktop-10.5/debian/patches/series   2019-10-09 23:26:13.0 
+0200
@@ -15,3 +15,4 @@
 wnck-shutdown.patch
 Use-panel-orientation-for-spacer-sizing.patch
 gsd334.patch
+use-builtin-session-manager.patch
diff -Nru budgie-desktop-10.5/debian/patches/use-builtin-session-manager.patch 
budgie-desktop-10.5/debian/patches/use-builtin-session-manager.patch
--- budgie-desktop-10.5/debian/patches/use-builtin-session-manager.patch
1970-01-01 01:00:00.0 +0100
+++ budgie-desktop-10.5/debian/patches/use-builtin-session-manager.patch
2019-10-09 23:33:24.0 +0200
@@ -0,0 +1,17 @@
+Description: Use gnome-session's builtin session manager
+ As it stands, when using the systemd session manager, gnome-shell will be
+ started indiscriminately. This breaks budgie-wm. This patch makes budgie use
+ gnome-session's builtin session manager.
+Author: Balló György 
+Origin: vendor, 
https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/budgie-desktop
+Bug-Archlinux: https://bugs.archlinux.org/task/63849
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/session/budgie-desktop.in
 

Bug#933163: Pending

[Xavier]

Control: tags -1 + pending

Hi,

I pushed a fix to buster-pu (https://bugs.debian.org/942075)

Cheers,
Xavier

Bug#942076: RM: loggerhead-breezy -- ROM; replaced by loggerhead package

[Jelmer Vernooij]

Package: ftp.debian.org
Severity: normal

Please remove the loggerhead-breezy package. It was never in any Debian 
releases, has a low popcon score - and its main functionality (a version of 
Loggerhead that supports Breezy) is now supported by loggerhead proper.

Bug#932246: Re : Bug#932246: Re : Bug#932246: printer-driver-hpcups: no more printing to a HP LaserJet 1320: stack smashing detected and hpcups crashed on signal 6

[Stefan Monnier]

> That'll be 3.19.8+dfsg0-4, uploaded later tonight. It will also ship 
> autopkgtests, to also test hplip printing on fake printers.

FWIW, I have 3.19.8+dfsg0-7 installed and am still seeing this problem.


Stefan

Bug#823201: snmpd: Configuration errors on a fresh install

[Craig Small]

OK, so I have now looked into this bug and what these messages mean.

TLDR: comment out those lines and that's what the next release of snmpd
will have.

Those tokens are for the DISMAN event handling. In effect, they are like a
macro that turns on a lot of event messages for a system such as low disk
free.

The systemd unit file and the init script exclude both the mteTrigger and
mteTriggerConf modules. These modules (one or other or both) contain the
tokens that you see in the log. Turn off the modules snmpd doesn't know
what those lines mean.

So why not remove the configuration to disable those modules?  The modules
require the DISMAN SNMP MIB.  In effect a file that converts the textual
version of an SNMP variable into a number.  MIBs in the old days have the
same license as the RFC which is non-free[1].

For newer ones, they are licensed under the BSD license but not the old
ones, unfortunately.

The options are:
 1) Comment out those lines in the configuration file; or
 2) Download the DISMAN MIBs, Debian cannot have them in main due to
license problems

 - Craig



1: https://wiki.debian.org/NonFreeIETFDocuments

Bug#942075: buster-pu: package cyrus-imapd/3.0.8-6+deb10u1

[Xavier Guimard]

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

Hi all,

cyrus-imapd ≤ 3.0.8 has a RC bug: it may loss data during upgrade from
stretch to buster. The fix is very simple, then I think it is low risky
to upgrade it in next Buster point release.

Cheers,
Xavier
diff --git a/debian/changelog b/debian/changelog
index 8e0033c..ecc4273 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+cyrus-imapd (3.0.8-6+deb10u1) buster; urgency=medium
+
+  * Fix data loss (Closes: #933163)
+
+ -- Xavier Guimard   Wed, 09 Oct 2019 22:38:07 +0200
+
 cyrus-imapd (3.0.8-6) unstable; urgency=medium
 
   [ Anthony Prades ]
diff --git a/debian/patches/0024-dont-skip-records-with-modseq-0.patch 
b/debian/patches/0024-dont-skip-records-with-modseq-0.patch
new file mode 100644
index 000..d284089
--- /dev/null
+++ b/debian/patches/0024-dont-skip-records-with-modseq-0.patch
@@ -0,0 +1,20 @@
+Description: mailbox: don't skip records with modseq == 0
+Author: Bron Gondwana 
+Origin: upstream, https://github.com/cyrusimap/cyrus-imapd/commit/02840505
+Bug: https://github.com/cyrusimap/cyrus-imapd/issues/2839
+Bug-Debian: https://bugs.debian.org/933163
+Forwarded: not-needed
+Reviewed-By: Xavier Guimard 
+Last-Update: 2019-10-09
+
+--- a/imap/mailbox.c
 b/imap/mailbox.c
+@@ -6513,7 +6513,7 @@
+ const struct index_record *record = msg_record(iter->msg);
+ if (!record->uid) continue; /* can happen on damaged mailboxes */
+ if ((record->system_flags & iter->skipflags)) continue;
+-if (record->modseq <= iter->changedsince) continue;
++if (iter->changedsince && record->modseq <= iter->changedsince) 
continue;
+ return iter->msg;
+ }
+ 
diff --git a/debian/patches/series b/debian/patches/series
index c5d71b5..e9631e4 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -22,3 +22,4 @@
 0022-close-backups-on-failure.patch
 0023-fix-memory-leak-on-ldap-failure.patch
 CVE-2019-11356.patch
+0024-dont-skip-records-with-modseq-0.patch

Bug#942074: pgn2web: Should pgn2web be removed from Debian?

[Olly Betts]

Source: pgn2web
Version: 0.4-2
Severity: normal

I wonder if it's time to remove the pgn2web package:

* most recent commit in upstream's VCS was over 10 years ago
* last package update was 1.5 years ago
* has low popcon - inst:176 vote:8
* has no reverse dependencies (according to dak rm)
* 3 open bugs, none with any maintainer response
* I had to NMU for the last wxWidgets transition 5 years ago, and
  it's now a blocker for the current wxwidgets3.0-gtk3 transition
* RC buggy (due to wxwidgets3.0-gtk3 transition) and due to be AUTORMed
  from testing on 2019-10-19

If there are no objections within two weeks, I'll turn this into an RM
bug.

Cheers,
Olly

Bug#682342: Latest patch successfully tested

[Nishanth Aravamudan]

On 22.08.2019 [21:45:26 +0200], Philipp Kern wrote:
> On 8/16/2019 8:34 PM, Nishanth Aravamudan wrote:
> > On 15.08.2019 [17:08:39 +0200], Cyril Brulebois wrote:
> >> Nishanth Aravamudan  (2019-08-14):
> >>> We are able to reproduce this issue at will in Ubuntu Bionic's
> >>> installer (not identical to Debian's, but code-wise in this path the
> >>> same).  While quite a while after the last update from Philipp, we
> >>> tested the patch (netcfg_dhcp_domain.patch) after updating it to avoid
> >>> a compilation issue, we found it did fix the problem for us.
> >>>
> >>> I am not sure if I can get Debian into our infrastructure to test
> >>> explicitly, but I will work on it; at the same time,  the code change
> >>> seems straightforward.
> >>
> >> Thanks for your feedback. Care to share the fixed version? :)
> > 
> > D'oh! I'm sorry, I thought I did. The patch we tested was:
> > 
> > diff -Naur a/dhcp.c b/dhcp.c
> > --- a/dhcp.c2017-10-10 14:01:42.0 +
> > +++ b/dhcp.c2019-08-14 01:04:58.339325357 +
> > @@ -590,7 +590,7 @@
> >  preseed_hostname_from_fqdn(client, buf);
> >  }
> >  
> > -if (netcfg_get_hostname (client, "netcfg/get_hostname", 
> > hostname, 1)) {
> > +if (netcfg_get_hostname (client, "netcfg/get_hostname", 
> > hostname, !have_domain)) {
> >  /*
> >   * Going back to POLL wouldn't make much sense.
> >   * However, it does make sense to go to the retry
> > diff -Naur a/netcfg-common.c b/netcfg-common.c
> > --- a/netcfg-common.c   2017-10-10 14:04:08.0 +
> > +++ b/netcfg-common.c   2019-08-13 20:01:13.606510273 +
> > @@ -1060,14 +1060,24 @@
> >  continue;
> >  }
> >  
> > -if (accept_domain && (s = strchr(hostname, '.'))) {
> > -di_info("Detected we have an FQDN; splitting and setting 
> > domain");
> > -if (s[1] == '\0') { /* "somehostname." <- . should be ignored 
> > */
> > +if ((s = strchr(hostname, '.'))) {
> > +di_info("Detected an FQDN in hostname");
> > +if (s[1] == '\0') {
> > +/* "somehostname." <- . should be ignored */
> >  *s = '\0';
> > -} else { /* assume we have a valid domain name given */
> > -strncpy(domain, s + 1, MAXHOSTNAMELEN);
> > -debconf_set(client, "netcfg/get_domain", domain);
> > -have_domain = 1;
> > +di_info("Stripped trailing dot from hostname");
> > +} else {
> > +/* assume that the domain is valid and copy it if
> > + * accept_domain is set; just use the hostname if
> > + * it is unset
> > + */
> > +if (accept_domain) {
> > +strncpy(domain, s + 1, MAXHOSTNAMELEN);
> > +   di_info("Setting domain to %s", domain);
> 
> This needs indenting fix-up.

Thank you, fixed below, I believe.

diff -Naur a/dhcp.c b/dhcp.c
--- a/dhcp.c2017-10-10 14:01:42.0 +
+++ b/dhcp.c2019-08-14 01:04:58.339325357 +
@@ -590,7 +590,7 @@
 preseed_hostname_from_fqdn(client, buf);
 }
 
-if (netcfg_get_hostname (client, "netcfg/get_hostname", 
hostname, 1)) {
+if (netcfg_get_hostname (client, "netcfg/get_hostname", 
hostname, !have_domain)) {
 /*
  * Going back to POLL wouldn't make much sense.
  * However, it does make sense to go to the retry
diff -Naur a/netcfg-common.c b/netcfg-common.c
--- a/netcfg-common.c   2017-10-10 14:04:08.0 +
+++ b/netcfg-common.c   2019-08-13 20:01:13.606510273 +
@@ -1060,14 +1060,24 @@
 continue;
 }
 
-if (accept_domain && (s = strchr(hostname, '.'))) {
-di_info("Detected we have an FQDN; splitting and setting domain");
-if (s[1] == '\0') { /* "somehostname." <- . should be ignored */
+if ((s = strchr(hostname, '.'))) {
+di_info("Detected an FQDN in hostname");
+if (s[1] == '\0') {
+/* "somehostname." <- . should be ignored */
 *s = '\0';
-} else { /* assume we have a valid domain name given */
-strncpy(domain, s + 1, MAXHOSTNAMELEN);
-debconf_set(client, "netcfg/get_domain", domain);
-have_domain = 1;
+di_info("Stripped trailing dot from hostname");
+} else {
+/* assume that the domain is valid and copy it if
+ * accept_domain is set; just use the hostname if
+ * it is unset
+ */
+if (accept_domain) {
+strncpy(domain, s + 1, MAXHOSTNAMELEN);
+di_info("Setting 

Bug#934738: gettext 0.20.1 available

[Boyuan Yang]

Control: affect -1 + gnulib
X-Debbugs-CC: sanv...@debian.org

Dear gettext maintainer,

The new snapshot of gnulib (https://tracker.debian.org/pkg/gnulib ) includes
some modules that need gettext 0.20+ to work properly. Please do consider
packaging the new version. It would be very useful even if the new version is
only pushed onto Experimental for now.

Thanks,
Boyuan Yang

On Wed, 14 Aug 2019 09:55:38 +0200 Sebastien Bacher  wrote:
> Package: gettext
> Version: 0.19.8.1-9
> 
> There is a new 0.20 version available, it would be nice to get it
> uploaded to Debian
> https://savannah.gnu.org/forum/forum.php?forum_id=9430
> 
> (in fact a .1 on https://ftp.gnu.org/pub/gnu/gettext/gettext-0.20.1.tar.xz)
> 
> Thanks,


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

Bug#942073: marisa: perl bindings are broken when linked with gcc-9

[Niko Tyni]

Package: libmarisa-perl
Version: 0.2.5-3
Severity: grave
Control: block 935737 with -1

As noticed by the autopkgtest checks, the marisa Perl bindings are
totally broken in sid after the recent Perl 5.30 rebuild:

  $ perl -e 'use marisa'
  Can't load '/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/marisa/marisa.so' for 
module marisa: /usr/lib/x86_64-linux-gnu/perl5/5.30/auto/marisa/marisa.so: 
undefined symbol: _ZTVN10__cxxabiv120__si_class_type_infoE at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193.
   at /usr/lib/x86_64-linux-gnu/perl5/5.30/marisa.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.
 
Rebuilding marisa in testing with Perl 5.28 triggers the same behaviour,
so it's not a change in Perl 5.30 that broke it. The previous sid build
in July is not broken.

It looks like this regressed with the gcc 8 -> 9 move. Linking the
DSO manually with gcc-8 makes it go away, as seen below.

I have no idea what goes wrong here, but I noticed that broken versions
of blib/arch/auto/marisa/marisa.so have no NEEDED entry for libmarisa.so.0
(as seen with 'objdump -p').

 reproduce the error 

  # apt build-dep libmarisa-perl
  $ ./debian/rules build
  $ cd bindings/perl
  $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I blib/lib -e 
'use marisa'
  Can't load 'blib/arch/auto/marisa/marisa.so' for module marisa: 
blib/arch/auto/marisa/marisa.so: undefined symbol: 
_ZTVN10__cxxabiv120__si_class_type_infoE at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193.
   at blib/lib/marisa.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.

 explicitly link with gcc-8, no error ---

  # apt install gcc-8
  $ gcc-8 -shared -L/usr/local/lib -L../../lib/marisa/.libs -lmarisa 
-fstack-protector -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  marisa-swig.o 
marisa-swig_wrap.o  -o blib/arch/auto/marisa/marisa.so
  $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I blib/lib -e 
'use marisa'

 explicitly link with gcc-9, same error again ---

  $ gcc-9 -shared -L/usr/local/lib -L../../lib/marisa/.libs -lmarisa 
-fstack-protector -Wl,-z,relro -Wl,-z,now -Wl,--as-needed  marisa-swig.o 
marisa-swig_wrap.o  -o blib/arch/auto/marisa/marisa.so
  $ LD_LIBRARY_PATH=../../lib/marisa/.libs/ perl -I blib/arch -I blib/lib -e 
'use marisa'
  Can't load 'blib/arch/auto/marisa/marisa.so' for module marisa: 
blib/arch/auto/marisa/marisa.so: undefined symbol: 
_ZTVN10__cxxabiv120__si_class_type_infoE at 
/usr/lib/x86_64-linux-gnu/perl/5.30/DynaLoader.pm line 193.
   at blib/lib/marisa.pm line 11.
  Compilation failed in require at -e line 1.
  BEGIN failed--compilation aborted at -e line 1.

-- 
Niko Tyni   nt...@debian.org

Bug#941107: chipw: Should chipw be removed from Debian?

[Olly Betts]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: chipw -- RoQA; dead upstream; unmaintained; low popcon; 
RC-buggy

On Wed, Sep 25, 2019 at 08:46:24AM +1200, Olly Betts wrote:
> I think it's time to remove the chipw package:
> 
> * chipw been dead upstream for many years (last release 2011)
> * chipw has very low popcon - inst:24 vote:1
> * the tworld package includes an alternative editor for this format
> * chipw has no reverse dependencies (according to dak rm)
> * chipw has only been uploaded once by the maintainer, over 9 years ago
> * I've had to NMU chipw for every wxWidgets transition since, and it's
>   now a blocker for the current wxwidgets3.0-gtk3 transition.  I seem
>   to have become the de-facto maintainer, and if I was the actual
>   maintainer I would be filing an RM bug.

The wxWidgets transition bugs are now RC, so in addition the package is
RC-buggy and marked for AUTORM from testing on 2019-10-19.

> If there are no objections within two weeks, I'll turn this into an RM
> bug.

I've had no response at all so going ahead.

Cheers,
Olly

Bug#942070: gnome-shell-extension-workspaces-to-dock: Must be updated to work with GNOME 3.34

[Raphaël Hertzog]

Package: gnome-shell-extension-workspaces-to-dock
Version: 51-1
Severity: grave
Tags: upstream
Justification: renders package unusable
User: de...@kali.org
Usertags: origin-kali

Please package version 52 that is documented to work with GNOME Shell
3.34.

The current version can be installed and loaded but it entirely breaks the
activities overview.

Thank you.

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

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

Versions of packages gnome-shell-extension-workspaces-to-dock depends on:
ii  gnome-shell  3.34.0-2

gnome-shell-extension-workspaces-to-dock recommends no packages.

gnome-shell-extension-workspaces-to-dock suggests no packages.

Bug#942071: [debian Buster] [armhf & arm64] [xarchiver] Depends: libgtk-3-0 (>= 3.0.0) but it is not going to be installed

[Jean-Marc LACROIX]

Package: xarchiver
Version: 1:0.5.4.14-1
Severity: grave

Dear maintainers,

It seems there is a dependency issue when installing xarchiver as 
indicated in following trace.


My target is either armhf, either arm64 Debian Buster 10.1

My test conditions are ...

ansible@vm-buster-armhf-110:~$ cat /etc/debian_version
10.1

ansible@vm-buster-armhf-110:~$ uname -a
Linux vm-buster-armhf-110 4.14.141-odroidxu4 #12 SMP PREEMPT Wed Oct 2 
00:24:32 CEST 2019 armv7l GNU/Linux


ansible@vm-buster-armhf-110:~$ dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
| 
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend

|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version 
Architecture Description

+++--===--===

ansible@vm-buster-armhf-110:~$ deborphan
ansible@vm-buster-armhf-110:~$

ansible@vm-buster-armhf-110:~$ grep deb /etc/apt/sources.list.d/* |grep 
-v "#"
/etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb 
http://ftp.fr.debian.org/debian buster-backports main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_current.list:deb 
http://ftp.debian.org/debian/ buster main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb 
http://ftp.debian.org/debian/ stretch main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_update_security.list:deb 
http://security.debian.org buster/updates main contrib non-free
/etc/apt/sources.list.d/debian_apt_v_10_buster_updates.list:deb 
http://ftp.fr.debian.org/debian buster-updates main contrib non-free



ansible@vm-buster-armhf-110:~$  cat /etc/apt/preferences.d/preferences_* 
|grep -v "#"  |grep -v "^$"

Package: *
Pin: release o=Debian,l=Debian,n=buster-update
Pin-Priority: 901
Package: *
Pin: release o=Debian,l=Debian,n=buster
Pin-Priority: 900
Package: *
Pin: release o=Debian,l=Debian,n=buster-backports
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=stretch
Pin-Priority: 400
Package: *
Pin: release o=Debian,l=Debian,n=testing
Pin-Priority: -1
Package: *
Pin: release o=Debian,l=Debian,n=unstable
Pin-Priority: -1
Package: udev
Pin: release o=Debian,l=Debian,n=*
Pin-Priority: -1
Package: dhcpcd5
Pin: release *
Pin-Priority: -1
Package: systemd
Pin: release *
Pin-Priority: -1



ansible@vm-buster-armhf-110:~$ sudo apt update && sudo apt upgrade
Hit:1 http://ftp.fr.debian.org/debian buster-backports InRelease
Hit:2 http://ftp.fr.debian.org/debian buster-updates InRelease 

Hit:3 http://security.debian.org buster/updates InRelease 

Hit:4 http://ftp.debian.org/debian buster InRelease 


Ign:5 http://ftp.debian.org/debian stretch InRelease
Hit:6 http://ftp.debian.org/debian stretch Release
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
ansible@vm-buster-armhf-110:~$


ansible@vm-buster-armhf-110:~$ sudo apt install xarchiver
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xarchiver : Depends: libgtk-3-0 (>= 3.0.0) but it is not going to be 
installed

E: Unable to correct problems, you have held broken packages.
ansible@vm-buster-armhf-110:~$

Please note that on target arm64, result is the same 
ansible@vm-buster-arm64-130:~$ sudo apt install xarchiver
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xarchiver : Depends: libgtk-3-0 (>= 3.0.0) but it is not going to be 
installed

E: Unable to correct problems, you have held broken packages.
ansible@vm-buster-arm64-130:~$ uname -a
Linux vm-buster-arm64-130 4.4.182-rockchip64 #1 SMP Fri Jun 28 17:34:00 
CEST 2019 aarch64 GNU/Linux

ansible@vm-buster-arm64-130:~$


Because my package pining is always available with the n-1 release
(stretch), (Thanks to Debian preferences !), the proposed workaround for 
the moment is :


sudo apt -t stretch install xarchiver

Thanks in advance for your help...

Best regards

Bug#942072: recollcmd: possible helpers to suggest/recommend

[-----]

Package: recollcmd
Severity: normal


While skimming the upstream list of helpers [1], these Debian packages
were found, which are not among the package depends/suggests/recommends.
You may want to consider them for inclusion.


- libwpd-tools
- python-icalendar
- djvulibre-bin
- midi: python-six, python{,3}-chardet


[1]: https://www.lesbonscomptes.com/recoll/features.html#doctypes

Bug#942032: openjazz: please provide a launcher for Jazz Jackrabbit Holiday Hare '95

[Ryan Armstrong]

(then G-D-P should provide in /usr/share/games/jazz-jackrabbit-hh95
a symlink to /usr/games/OpenJazz to makes it work ?)


When I did my initial testing, the HH95 path just needs to be provided
as a command-line argument to openjazz. For example:

$ OpenJazz /usr/share/games/jazz-jackrabbit-hh95

Once the game is started, the menu item for 'Episode X' will run the
HH95 levels instead of the HH94 levels included with the full game.

It seems to find the existing game data files in the jazz-jackrabbit folder just
fine, even if the only such file is openjazz.000. If run without the main game 
data
present, the other episodes will just be disabled on the main menu.

Ryan

Bug#941481: kalarm: The Akonadi personal information management service is not running

[Richard Elias]

Control: tags -1 - moreinfo

Infos were provided...

Bug#782636: Your profile has been checked out by

[fubar Alert]

Guess who liked your profile and rated you an 11!

How do you know who's "real" on fubar?
Look for profiles with a Salute: 
https://fubar.com/recallclick.php?email=782...@bugs.debian.org=WMDbIIoMc4SVzI1ppenIJorcJDnuqa40.51

Have questions?
Check out the fubar Bible: 
https://fubar.com/recallclick.php?email=782...@bugs.debian.org=WMDbIIoMc4SVzI1ppenIJorcJDnuqa40.18
Visit the fubar Support Lounge: 
https://fubar.com/recallclick.php?email=782...@bugs.debian.org=WMDbIIoMc4SVzI1ppenIJorcJDnuqa40.21




Available at the App Store: 
https://itunes.apple.com/app/apple-store/id455311703?pt=395928=email

Get it on Google Play: 
https://play.google.com/store/apps/details?id=com.fubar.mobile=utm_source%3Demail%26utm_medium%3Demail%26utm_campaign%3Demail

--

Unsubscribe or change your email settings here: 
https://fubar.com/email_settings.php?s=ZJXys3yhx7rpA58C6hE6t%2F63YL%2F4KCbsGEE8ICpXujo7ryRGo%2B0PYQ%3D%3D
fubar - 50 Woodside Plaza #433 - Redwood City, CA 94061 

Bug#942042: systemd: Enabling systemd-networkd does not disable ifupdown management of /etc/network/interfaces

[Artur Pydo]

Thank you all for the explanations and suggestions.

I undestand your decision to close this report.

The following article in Debian wiki explains how to setup
systemd-networkd and suggests to rename /etc/network/interfaces. It
should be enough.

https://wiki.debian.org/SystemdNetworkd

-- 
Best regards,
Artur

Bug#942069: RFP: python-opentracing -- Python interface to the OpenTracing.io API

[Fabrice BAUZAC]

Package: wnpp
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: python-opentracing
  Version : 2.2.0
  Upstream Author : Carlos Alberto Cortez 
* URL : https://opentracing.io/
* License : Apache 2.0
  Programming Lang: Python
  Description : Python interface to the OpenTracing.io API

OpenTracing is a vendor-neutral API for tracing distributed and
non-distributed systems.

It allows programs in any language to send traces uniformly.  In
particular, sending messages between programs and timing information
are standardized, which allow any OpenTracing-compatible servers to
display graphical profiling information.  One of the best known such
servers is JaegerTracing.

The available languages are currently: Go, Javascript, Java, Python,
Ruby, PHP, Objective-C, C++, C#.

Currently on Debian there are packages for the Ruby and Go interfaces.

The source code for the Python interface is available at
https://github.com/opentracing/opentracing-python.  I have seen that
Carlos Alberto Cortez is the main committer, but I have not contacted
him.

I use the Python interface for my Python2 programs to track
performance issues.  At the moment I rely on the PyPI package and
virtualenvs, but it would be much cleaner to have a proper Debian
package.

I'm not sure what is the best way to proceed.  If it's trivial for the
Python team to add this package and handle it through their automated
scripts, we can go for it.  Otherwise I think I can work on packaging
and maintaining it myself.

Thanks!

Best regards
Fabrice

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEAVrpsl3LBRHSAKdd5WdN6lFMiR0FAl2eOfIRHG5vb25AbXlr
b2xhYi5jb20ACgkQ5WdN6lFMiR3rWQ//SASE3wwMbM0Ntqwo4Nky0pORetWuUIj8
86umdmDJ+Y70hEWG4JB3EVHjwngSf5Nw19fZd+tSIH8dkzotODJXnKwn+6ZhmKAi
UWbGLPwDf8MDd2Nr9PpKHdXfVG8fi0jEMXToAJKYVKmlho3D2F7UbFJ0mAyuOHsw
kBQiN+K+Uel0nmIy2LESlyC3vcvMQ7Q1fNSveNppXiInx0BGETfRRxG/wJMJMoRG
KEVodkQcYroGBNmD8PS1Pwxi2trrPHwdlKd3UP29vLBf/zvqISNTD5aEwodvcWYF
QRRE8Ypz8olcVwrkM2ssLjryfmkTsut9sjH2wkEEeANzZlQPfCCKYdGEA+yMzckk
LAmNPNzmdfH1IBzLSxIQhTG4PqS9If9EknKQ9ttwqEXhafI0lBd/Vux9rLrpc9QU
QWsPma/UsfDSFI/52uzPHofnvomQMs8i0x7wVRu8nwU4jeSCePKkAoynCc5yH9Wy
u23uaZdfaRM61ZfoEbUaQYjEJm/5U2RijFHnJM9FdS8erjoxrB69WPJc+ZMxhmNk
Cq5JGEVnVWuVCKS9MGFKU/lkYFyDDLkLkM91U2GQf2t6oTjeobuplyItTCzrvYcu
04dS0RguYPtkNX+KT1z59Dz//JiVPTp4xRDcuyzR42ke0soUOhDkndSMApaaRNYJ
B1veCjvhsYc=
=iDZn
-END PGP SIGNATURE-

Bug#942066: filezilla: FTBFS with GCC 9: error: #error You need to use a C++17 compiler.

[Sven Joachim]

Control: retitle -1 filezilla: FTBFS with libfilezilla 0.18.2

On 2019-10-09 21:06 +0200, Andreas Beckmann wrote:

> Package: filezilla
> Version: 3.39.0-2
> Severity: serious
> Tags: sid bullseye
> Justification: fails to build from source (but built successfully in the past)
>
> filezilla FTBFS in sid, probably related to the default compiler being
> switched from GCC 8 to GCC 9:

Not really, I think.

> In file included from /usr/include/libfilezilla/libfilezilla.hpp:4,
>  from ../../src/include/libfilezilla_engine.h:12,
>  from ./filezilla.h:1,
>  from backend.cpp:1:
> /usr/include/libfilezilla/private/defs.hpp:10:4: error: #error You need to 
> use a C++17 compiler. Try passing -std=c++17 as compiler flag.
>10 |   #error You need to use a C++17 compiler. Try passing -std=c++17 as 
> compiler flag.
>   |^

That's because libfilezilla is built with -std=c++17.  See #941193.

Cheers,
   Sven

Bug#941267: ukwm can't start, dmesg has segfault error info libukwm-cogl-1.so [b5b4c000+68000]

[Andreas Beckmann]

Control: tag -1 moreinfo unreproducible

On Fri, 27 Sep 2019 19:14:16 +0800 xiao shengwen  wrote:
> Package: ukwm
> Version: 1.1.11-1+b1

Note: This is not the version from stable (which has 1.1.11-1), but from
testing some time ago, now superseded by 1.1.11-1+b2

> [  306.124994] ukwm[1159]: segfault at 38 ip b5b57084 sp bf9b2d0c error 4 in 
> libukwm-cogl-1.so[b5b19000+68000]

> -- System Information:
> Debian Release: 10.1
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
> Architecture: i386 (i686)

You seem to running a mixture of stable and testing, which is not a
supported setup. I tried in a chroot, but could not reproduce any segfaults.

testing and sid now have 1.1.11-1+b2 - does the crash still happen with
these versions that were rebuilt against newer libraries? (Don't forget
to upgrade the libukwm-1-0 package, too.)

Can you reproduce the segfault in a clean stable environment?


Andreas

Bug#941193: filezilla: Crash on startup: undefined symbol: _ZTIN2fz6threadE

[Sven Joachim]

On 2019-09-26 08:16 +0200, Sven Joachim wrote:

> Control: reassign -1 libfilezilla0 0.18.2-1
>
> On 2019-09-26 17:53 +1200, jfp wrote:
>
>> Package: filezilla
>> Version: 3.39.0-2
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>>
>> Crashes on startup with the folloing error:
>>
>> filezilla: symbol lookup error: filezilla: undefined symbol: _ZTIN2fz6threadE
>
> Confirmed here, looks like libfilezilla changed the ABI without bumping
> SONAME.  Downgrading libfilezilla0 to 0.15.1-1 helps.

I am not really a C++ expert, but probably this ABI break has been
caused by libfilezilla being built with "-std=c++17".  If so, the SONAME
should be retained and either

- the packagename changed, or

- a versioned Breaks against filezilla added to debian/control and
  shlibs bumped (e.g. via "dh_makeshlibs -VUpstream-Version" in
  debian/rules).

And of course a new filezilla needs to be uploaded with a bumped
Build-Depends on libfilezilla-dev.

Cheers,
   Sven

Bug#942068: openvpn-systemd-resolved: missing script for update-systemd-resolved

[Johan Smits]

Package: openvpn-systemd-resolved
Version: 1.3.0-3
Severity: normal

Dear Maintainer,

When I check the journal log I see a lot of errors.
It seems like there is a file missing to start the VPN.
But when I start the VPN all works normal (my vpn also uses the same public dns 
services)

okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: 
Service RestartSec=5s expired, scheduling restart.
okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: 
Scheduled restart job, restart counter is at 1207.
okt 09 21:08:37 laptop systemd[1]: Stopped OpenVPN connection to 
update-systemd-resolved.
okt 09 21:08:37 laptop systemd[1]: Starting OpenVPN connection to 
update-systemd-resolved...
okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Options error: --up 
script fails with '/etc/openvpn/scripts/update-systemd-resolved': No such file 
or directory (errno=2)
okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Options error: 
Please correct this error.
okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: 
Main process exited, code=exited, status=1/FAILURE
okt 09 21:08:37 laptop ovpn-update-systemd-resolved[20604]: Use --help for more 
information.
okt 09 21:08:37 laptop systemd[1]: openvpn@update-systemd-resolved.service: 
Failed with result 'exit-code'.
okt 09 21:08:37 laptop systemd[1]: Failed to start OpenVPN connection to 
update-systemd-resolved.

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

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

Versions of packages openvpn-systemd-resolved depends on:
ii  libnss-resolve  242-7
ii  openvpn 2.4.7-1
ii  systemd 242-7

openvpn-systemd-resolved recommends no packages.

openvpn-systemd-resolved suggests no packages.

-- no debconf information

Bug#941853: crypt(3) should be provided by libxcrypt

[Aurelien Jarno]

On 2019-10-07 14:16, Aurelien Jarno wrote:
> On 2019-10-07 00:31, Marco d'Itri wrote:
> > On Oct 07, Aurelien Jarno  wrote:
> > 
> > Dear debian-boot: for the benefit of the ftpmasters, please confirm that 
> > you have no objections to src:libxcrypt generating a libcrypt1-udeb 
> > package (initially in experimental) which will provide crypt(3) 
> > currently in the libc udeb.
> > 
> > > I guess we should keep building libcrypt1 for the bi/tri-arch packages.
> > What do I need to do about this?
> 
> There are two options:
> - We continue to build libcrypt1 from the glibc package for the
>   bi/tri-arch packages.
> - src:libxcrypt starts to build lib32crypt1, lib64-crypt1, libn32crypt1
>   and libx32crypt1, using gcc-multilib.
> 
> Note that the second option can be implemented in a second step.
> 

I have implemented the first option in the libxcrypt branch:

https://salsa.debian.org/glibc-team/glibc/tree/libxcrypt

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#794821: libwxbase3.0-0: segmentation fault (SIGSEGV) with gnuplot5

[Olly Betts]

Sorry, I seem to have failed to respond to this before (or my response
never made it to the BTS).  I certainly did take a look before as I
found your repoducer script on my disk...

On Thu, Aug 06, 2015 at 11:35:44PM +0200, Vincent Lefevre wrote:
> A reproducible crash in /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
> with gnuplot5:
> 
> 
> #!/bin/sh
> 
> set -e
> 
> cat < tmpfile-plot
> 0 0
> 10 10
> EOF
> 
> gnuplot -persist < set term wxt
> plot "tmpfile-plot" using 1:2 t '' with line
> EOF
> 
> rm tmpfile-plot
> echo "Scroll with the mouse wheel -> gnuplot crashes (see 'core' file)."
> 

I can reproduce the crash, but it appears to be connected with the
removal of tmpfile-plot - if I add:

sleep 5

before the "rm" command then I can use the scroll wheel for 5 seconds
but then get the crash after that - presumably changing the viewing
area causes gnuplot to try to reload the plot file or something like
that?

> Core was generated by `/usr/bin/gnuplot -persist'.
> Program terminated with signal SIGSEGV, Segmentation fault.
> #0  0x7f8bd16fc2c7 in ?? ()
>from /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
> 
> The backtrace:
> 
> Thread 1 (Thread 0x7f8bd2dd4a00 (LWP 9205)):
> #0  0x7f8bd16fc2c7 in  () at 
> /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
> #1  0x7f8bd16fc989 in wxThread::Wait(wxThreadWait) () at 
> /usr/lib/x86_64-linux-gnu/libwx_baseu-3.0.so.0
> #2  0x7f8bd2d009ce in  ()
> #3  0x7f8bd2ca5a5a in  ()
> #4  0x7f8bd2c080bd in  ()
> #5  0x7f8bceb1cb45 in __libc_start_main (main=0x7f8bd2c07a70, argc=2, 
> argv=0x7ffe756fde98, init=, fini=, 
> rtld_fini=, stack_end=0x7ffe756fde88) at libc-start.c:287

Hmm, I don't seem to get a core file (and sadly am struggling to work
out how to enable them on current Debian).

But repeating that after installing these packages (assuming unstable)
would be more enlightening:

libwxbase3.0-0v5-dbgsym libwxgtk3.0-gtk3-0v5-dbgsym

Cheers,
Olly

Bug#942067: rsyslog: CVE-2019-17041

[Salvatore Bonaccorso]

Source: rsyslog
Version: 8.1908.0-1
Severity: normal
Tags: security upstream
Forwarded: https://github.com/rsyslog/rsyslog/pull/3884

Hi,

The following vulnerability was published for rsyslog, filling mainly
for tracking, we marked it as no-dsa given the module is not enabled
by default and somehow exotic. But let us know please at team@s.d.o if
you disagree with the assessment and we can revert.

CVE-2019-17041[0]:
| An issue was discovered in Rsyslog v8.1908.0.
| contrib/pmaixforwardedfrom/pmaixforwardedfrom.c has a heap overflow in
| the parser for AIX log messages. The parser tries to locate a log
| message delimiter (in this case, a space or a colon) but fails to
| account for strings that do not satisfy this constraint. If the string
| does not match, then the variable lenMsg will reach the value zero and
| will skip the sanity check that detects invalid log messages. The
| message will then be considered valid, and the parser will eat up the
| nonexistent colon delimiter. In doing so, it will decrement lenMsg, a
| signed integer, whose value was zero and now becomes minus one. The
| following step in the parser is to shift left the contents of the
| message. To do this, it will call memmove with the right pointers to
| the target and destination strings, but the lenMsg will now be
| interpreted as a huge value, causing a heap overflow.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-17041
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17041
[1] https://github.com/rsyslog/rsyslog/pull/3884

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#942065: rsyslog: CVE-2019-17042

[Salvatore Bonaccorso]

Source: rsyslog
Version: 8.1908.0-1
Severity: normal
Tags: security upstream
Forwarded: https://github.com/rsyslog/rsyslog/pull/3883

Hi,

The following vulnerability was published for rsyslog, filling this
for tracking mainly.

CVE-2019-17042[0]:
| An issue was discovered in Rsyslog v8.1908.0.
| contrib/pmcisconames/pmcisconames.c has a heap overflow in the parser
| for Cisco log messages. The parser tries to locate a log message
| delimiter (in this case, a space or a colon), but fails to account for
| strings that do not satisfy this constraint. If the string does not
| match, then the variable lenMsg will reach the value zero and will
| skip the sanity check that detects invalid log messages. The message
| will then be considered valid, and the parser will eat up the
| nonexistent colon delimiter. In doing so, it will decrement lenMsg, a
| signed integer, whose value was zero and now becomes minus one. The
| following step in the parser is to shift left the contents of the
| message. To do this, it will call memmove with the right pointers to
| the target and destination strings, but the lenMsg will now be
| interpreted as a huge value, causing a heap overflow.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-17042
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17042
[1] https://github.com/rsyslog/rsyslog/pull/3883

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#942066: filezilla: FTBFS with GCC 9: error: #error You need to use a C++17 compiler.

[Andreas Beckmann]

Package: filezilla
Version: 3.39.0-2
Severity: serious
Tags: sid bullseye
Justification: fails to build from source (but built successfully in the past)

filezilla FTBFS in sid, probably related to the default compiler being
switched from GCC 8 to GCC 9:

In file included from /usr/include/libfilezilla/libfilezilla.hpp:4,
 from ../../src/include/libfilezilla_engine.h:12,
 from ./filezilla.h:1,
 from backend.cpp:1:
/usr/include/libfilezilla/private/defs.hpp:10:4: error: #error You need to use 
a C++17 compiler. Try passing -std=c++17 as compiler flag.
   10 |   #error You need to use a C++17 compiler. Try passing -std=c++17 as 
compiler flag.
  |^

(filezilla still builds fine in buster)


Andreas


sid.build.gz
Description: application/gzip

Bug#794799: libwxgtk3.0-0: assertion failure with gnuplot5

[Olly Betts]

Control: tag -1 + unreproducible

Tagging based on "This is not reproducible" in the initial report.  If
you've since found a way to reproduce, please remove the tag and provide
details.

On Mon, Aug 17, 2015 at 10:36:20PM +0200, Vincent Lefevre wrote:
> On 2015-08-11 23:30:21 +0200, Vincent Lefevre wrote:
> > On 2015-08-11 18:38:06 +0100, Olly Betts wrote:
> > > On Tue, Aug 11, 2015 at 05:59:59PM +0200, Vincent Lefevre wrote:
> > > > On 2015-08-11 16:22:04 +0100, Olly Betts wrote:
> > > > > On Thu, Aug 06, 2015 at 08:54:19PM +0200, Vincent Lefevre wrote:
> > > > > > gnuplot5 crashed due to an assertion failure in libwxgtk3.0-0.
> > > > > > This is not reproducible.
> > > > > 
> > > > > You don't seem to have included the assertion message which was
> > > > > displayed, which would be the most useful information to have.
> > > > 
> > > > IIRC, there wasn't more information.
> > > 
> > > There wasn't an assertion dialog on screen?
> > 
> > There was a dialog saying that there was an assertion failure in
> > libwxgtk3.0-0, but I don't think there was more information. Or
> > perhaps it disappeared before I could get the information.
> 
> I now remember that I had saved the file:
> 
> ASSERT INFO:
> ../src/gtk/dcclient.cpp(250): assert "Assert failure" failed in 
> wxFreePoolGC(): Wrong GC

This situation seems "impossible".  I suspect (especially given the
unreproducibility) that there's a stray memory write corrupting either
the wxGCPool array, or one of the members (m_penGC, etc) such that when
it comes time to remove the pool entry it isn't found.

It's hard to know if that's a bug in wxWidgets, the application or
another library in use.  We don't have a pile of reports suggesting a
memory corruption bug in wx, but it could be one which requires
particular circumstances to trigger.

Cheers,
Olly

Bug#941912: libsoup2.4: CVE-2019-17266

[Salvatore Bonaccorso]

Hi Claudio,

On Wed, Oct 09, 2019 at 01:10:04PM +0300, Claudio Saavedra wrote:
> On Mon, 07 Oct 2019 16:43:28 +0200 Salvatore Bonaccorso <
> car...@debian.org> wrote:
> 
> > Please adjust the affected versions in the BTS as needed.
> 
> I'm the libsoup maintainer. This bug affects libsoup from 2.65.1 until
> 2.68.1, previous versions are unaffected. I just uploaded upstream new
> packages fixing this vulnerability for the 2.66 and 2.68 series (2.66.4
> and 2.68.2, respectively).

Thanks for this information, so I'm updating the tracker information.
While at it, I'm pretty sure
https://gitlab.gnome.org/GNOME/libsoup/issues/173 was previously
accessible, but now it is not anymore (I was wondering about the
reason).

Regards,
Salvatore

Bug#942064: profphd: autopkgtest failure

[gregor herrmann]

Source: profphd
Version: 1.0.42-3
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

profphd fails its autopkgtests:

autopkgtest [01:06:02]: test installation-test: [---
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/prof.pl line 15.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Assigning non-zero to $[ is no longer possible at 
/usr/share/profphd/prof/prof.pl line 139.
autopkgtest [01:06:03]: test installation-test: ---]


from: 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/profphd/3106658/log.gz


This is with perl 5.30, older tests passed with

autopkgtest [11:24:16]: test profphd-install-test: [---
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/prof.pl line 15.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/embl/phd.pl line 16.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/prof.pl line 15.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/embl/phd.pl line 16.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/prof.pl line 15.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/embl/phd.pl line 16.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/prof.pl line 15.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/embl/phd.pl line 16.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/prof.pl line 15.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/embl/phd.pl line 16.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Can't exec "pp_popcon_cnt": No such file or directory at 
/usr/share/profphd/prof/prof.pl line 15.
The Rost Lab recommends you install the pp-popularity-contest package that 
provides pp_popcon_cnt:

sudo apt-get install pp-popularity-contest
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant argument in printf at /usr/share/perl5/RG/Utils/Copf.pm line 6536.
Redundant 

Bug#942063: libbio-graphics-perl: test failures

[gregor herrmann]

Source: libbio-graphics-perl
Version: 2.40-3
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package fails its testsuite both during build:

   dh_auto_test
perl Build test --verbose 1

#   Failed test 'use Bio::Graphics::FeatureFile;'
#   at t/BioGraphics.t line 26.
# Tried to use 'Bio::Graphics::FeatureFile'.
# Error:  Can't locate Bio/DB/SeqFeature/Store.pm in @INC (you may need to 
install the Bio::DB::SeqFeature::Store module) (@INC contains: . 
/build/libbio-graphics-perl-2.40/t/../lib 
/build/libbio-graphics-perl-2.40/blib/lib 
/build/libbio-graphics-perl-2.40/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
/build/libbio-graphics-perl-2.40/t/../lib/Bio/Graphics/FeatureFile.pm line 259.
# BEGIN failed--compilation aborted at 
/build/libbio-graphics-perl-2.40/t/../lib/Bio/Graphics/FeatureFile.pm line 259.
# Compilation failed in require at t/BioGraphics.t line 26.
# BEGIN failed--compilation aborted at t/BioGraphics.t line 26.
Can't locate object method "new" via package "Bio::Graphics::FeatureFile" at 
t/BioGraphics.t line 49,  line 192.
# Looks like your test exited with 255 just after 3.
t/BioGraphics.t .. 
1..49
ok 1 - use GD::Image;
not ok 2 - use Bio::Graphics::FeatureFile;
ok 3 - use Bio::Graphics::Panel;
Dubious, test returned 255 (wstat 65280, 0xff00)
Failed 47/49 subtests 
Can't locate Bio/DB/SeqFeature/Store.pm in @INC (you may need to install the 
Bio::DB::SeqFeature::Store module) (@INC contains: 
/build/libbio-graphics-perl-2.40/t/../lib 
/build/libbio-graphics-perl-2.40/t/../blib/lib 
/build/libbio-graphics-perl-2.40/t/../blib/arch 
/build/libbio-graphics-perl-2.40/blib/lib 
/build/libbio-graphics-perl-2.40/blib/arch /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.30.0 /usr/local/share/perl/5.30.0 
/usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.30 /usr/share/perl/5.30 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/build/libbio-graphics-perl-2.40/t/../lib/Bio/Graphics/FeatureFile.pm line 259.
BEGIN failed--compilation aborted at 
/build/libbio-graphics-perl-2.40/t/../lib/Bio/Graphics/FeatureFile.pm line 259.
Compilation failed in require at 
/build/libbio-graphics-perl-2.40/t/../lib/Bio/Graphics/Wiggle/Loader.pm line 
118.
BEGIN failed--compilation aborted at 
/build/libbio-graphics-perl-2.40/t/../lib/Bio/Graphics/Wiggle/Loader.pm line 
118.
Compilation failed in require at t/Wiggle.t line 16.
BEGIN failed--compilation aborted at t/Wiggle.t line 16.
# Looks like your test exited with 2 before it could output anything.
t/Wiggle.t ... 
1..11
Dubious, test returned 2 (wstat 512, 0x200)
Failed 11/11 subtests 

Test Summary Report
- ---
t/BioGraphics.t (Wstat: 65280 Tests: 3 Failed: 1)
  Failed test:  2
  Non-zero exit status: 255
  Parse errors: Bad plan.  You planned 49 tests but ran 3.
t/Wiggle.t (Wstat: 512 Tests: 0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: Bad plan.  You planned 11 tests but ran 0.
Files=2, Tests=3,  1 wallclock secs ( 0.02 usr  0.01 sys +  0.38 cusr  0.05 
csys =  0.46 CPU)
Result: FAIL
Failed 2/2 test programs. 1/3 subtests failed.
dh_auto_test: perl Build test --verbose 1 returned exit code 2



and also during autopkgtest, e.g.
https://ci.debian.net/data/autopkgtest/testing/amd64/libb/libbio-graphics-perl/3123490/log.gz


Cheers,
gregor


-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAl2eKItfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbs3hAAwcfxhoP1R0sNNGxOaxFrr1037TniLazB1poWxjDG1e4FEyD95FfmZBms
M6JwTvi66mfDNjONLO93qP064nwU8SKZJfokYjNNGkspQA1ATtpdWXpn+h3ilhtm
C5BKww+O1scwg7JkooTKywrzPCS7duwZ6WprikayZtx8P0/BUh9K99CXhFGHI8Mj
EaJklONDZsQ+/M6Z0mlN5d7WnpghqEmd8WVVZ53ioLs3SkgTzo3MHW0cH2OmKaX5
vo1kopX/Bu/qbAb9KvcTMZjHaKu70WAmYJa47C2kXchj+qhHWI0laxKa0p6jAWdX
zu65QHFj34ZLe8sFsRyxJWMXa9KqsYdYSneBof5KudbHxtH20O+/ILrQR0UzhKMU
NttZUcGEX9cj2tG2r0YPOPDf4F7uF/+vQbgwUfnhY5wyVwHAztSlAdSjK12xGYbj
cBAS8LKhmowbOUQDom9ssLQp7DxmqmPfDrg/tqTnq+TOx4ghAwxxaZOb7ZkXuf0x
IUqoKTKGheV08X4tOdZm69MKDQxrl0RaCMG+rk2V64ONPz+MhmHwXOG9di+RfAnw
Vry0kpfnx1SplZ+b/BtIIGOZpMTPTTEYsMvHU3jvgkxF+UxGgSOBug50BpcIqr9G
m2JWQeEaQ1379IWo+OoOsTFlf1AwZBpsZjf/QIU48YdN2k7OZCo=
=bYbz
-END PGP SIGNATURE-

Bug#939571: Fails to import

[Jameson Graef Rollins]

severity 939571 grave
thanks

Bug#941026: netcfg_gateway_reachable wrongly rejects IPv6 link-local addresses

[Andrew Kanaber]

On Wed, Oct 02, 2019 at 08:27:34AM +0200, Philipp Kern wrote:
> On 2019-09-23 18:00, Andrew Kanaber wrote:
> > When doing static IP configuration, netcfg will reject a gateway address
> > outside the host's network as defined by the netmask.
> So how does it identify the interface to use in this case? Does the kernel
> have special support to pick the correct one if there is only one
> non-loopback interface? Generally link-local addresses do need to be
> qualified with the interface to be used.

The routing table entry contains both the gateway address and the interface to
use. When the kernel decides to use the route it has everything it needs.

Using a link-local gateway is an entirely standard thing to do. It would have
been reasonable for netcfg to reject link-local addresses entered as the actual
host address - but it doesn't check for that, it just does this netmask check
that happens to reject global unicast host address plus link-local gateway.

Thanks,

Andrew

Bug#939571: Fails to import

[Jameson Graef Rollins]

severity 939571 grave

The 0.10.0-4 package in testing and unstable is currently unusable since
it can not be imported because of this ModuleNotFoundError exception.

jamie.

Bug#288822: marked as done (developers-reference: "Bugs" control field not documented)

[Guillem Jover]

On Tue, 2019-10-08 at 10:33:46 +, Holger Levsen wrote:
> On Tue, Oct 08, 2019 at 12:30:50PM +0200, Guillem Jover wrote:
> > > I don't really understand "#288822: developers-reference: "Bugs" control 
> > > field
> > > not documented" and I'm not sure it's really an issue still.
> > This would be the Bugs field documented now in both deb-control(5) and
> > deb-src-control(5), since dpkg 1.14.7 (2007-10-08), ref #173463.
> 
> thanks for that information! do you agree there's nothing to be added to
> dev-ref?

Yeah, looks like it.

Thanks,
Guillem

Bug#940571: dpkg-buildflags should support an optimization area for things like lto and pgo

[Guillem Jover]

Control: tag -1 - patch + moreinfo
Control: retitle -1 dpkg-buildflags: Add support for an optimize area for 
things like LTO

On Tue, 2019-09-17 at 14:36:44 +0200, Matthias Klose wrote:
> Package: src:dpkg
> Version: 1.19.7
> Tags: patch

> Please add an optimization area (opt, optimization) for extra optimizations
> like lto (link time optimization) and pgo (profile guided optimization).

> lto can be directly translated into compiler flags, as seen in the attached
> patch, assuming that no lto across package boundaries is done (ensured by
> the debhelper patch in #939656).  The patch assumes that just nolto can be
> used to disable lto until an area is introduced in dpkg.
> 
> Some upstream packages also provide build support for lto builds, so for
> these an option should be given to disable the addition to the compiler
> flags (like the nolto in the proposed patch).

I take you are requesting both adding this and also enabling LTO by
default?

I'm fine with the former (even implementing that myself), but the latter
would need to go through [Q] first. And I see this can cause breakage [O]
according to the OpenSUSE people.

[Q] 

[O] 


> pgo doesn't directly translate into compiler flags, but almost always
> requires upstream support in the build system.  pgo usually is enabled by
> some configure options which are specific to the upstream build.  pgo
> usually requires running a profiling task, so this optimization probably
> should be disabled for cross builds, otoh, the cross build then is different
> to the native build (although it should create a functional identical
> package).

I don't see how dpkg can support PGO, so I'm excluding that from this
request, as it seems this would be pretty much unactionable.

Regards,
Guillem

Bug#942062: liblept5: Please add Multi-Arch support

[Christian Marillat]

Package: liblept5
Version: 1.78.0-2+b1
Severity: normal

Dear Maintainer,

Both packages liblept5 and libept-dev must have "Multi-Arch: same"

Christian

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

Kernel: Linux 4.19.78 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages liblept5 depends on:
ii  libc62.29-2
ii  libgif7  5.1.4-3
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libopenjp2-7 2.3.1-1
ii  libpng16-16  1.6.37-1
ii  libtiff5 4.0.10+git191003-1
ii  libwebp6 0.6.1-2+b1
ii  zlib1g   1:1.2.11.dfsg-1+b1

liblept5 recommends no packages.

liblept5 suggests no packages.

-- no debconf information

Bug#941898: Acknowledgement (munin-node: all Plugins fail with "Can't drop privileges: at /usr/share/perl5/Munin/Node/Service.pm line 228.")

[devel]

Hello Cord,


On Wed, 9 Oct 2019 09:14:15 +0200 Cord Beermann  wrote:

> The issue disappeared with a new perl package.

thank you for documenting the issue and for updating the bug status!

Cheers,
Lars

Bug#941700: [Pkg-javascript-devel] Bug#941700: Bug#941700: Update babel to version 7

[Evgeny Kapun]

[14:53:55] ReferenceError: [BABEL]
/home/pravi/forge/debian/git/js-team/node-babel/packages/babel-parser/src/x.js:
Unknown option: base.envName. Check out
 for more information about options.


The reason for this error and other errors is that this version uses multiple 
Babel features introduced in Babel 7, such as:
* envName option [1]
* babel.config.js file [2]
* Numeric separator [3]

For these reasons, it doesn't seem possible to build Babel 7.4.5 using Babel 6. 
I see two possible ways to solve this:
1. Bootstrap Babel manually, that is, build it locally using Babel installed 
from NPM and upload the resulting binary packages.
2. First package an older version of Babel, such as 7.0.0, then use it to build 
the current version.

Some other notes:
* The version being packaged is 7.4.5, but the latest stable version is already 
7.6.0.
* During build, it is better to set NODE_ENV=production, because otherwise it 
will build for the current version of Node, so the resulting code may not run 
on older versions. With NODE_ENV=production, it will build for Node 6.9 and 
later (this is specified in babel.config.js).

[1]: https://babeljs.io/docs/en/options#envname
[2]: https://babeljs.io/docs/en/config-files#root-babelconfigjs-files
[3]: https://babeljs.io/docs/en/babel-plugin-proposal-numeric-separator

Bug#942056: [PATCH] debian: Update list of copyright holders.

[Ben Pfaff]

The list of copyright holders was incomplete and out of date.  This
updates it based on a "grep" for copyright notices, which I reviewed by
hand.

CC: 942...@bugs.debian.org
Reported-by: Chris Lamb 
Reported-at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942056
Signed-off-by: Ben Pfaff 
---
 debian/copyright.in | 80 -
 1 file changed, 64 insertions(+), 16 deletions(-)

diff --git a/debian/copyright.in b/debian/copyright.in
index 9ad00340f6bb..3669255c75cd 100644
--- a/debian/copyright.in
+++ b/debian/copyright.in
@@ -8,22 +8,70 @@ Upstream Authors (from AUTHORS):
 
 Upstream Copyright Holders:
 
-Copyright (c) 2007, 2008, 2009, 2010, 2011, 2012, 2013 Nicira, Inc.
-Copyright (c) 2010 Jean Tourrilhes - HP-Labs.
-Copyright (c) 2008,2009,2010 Citrix Systems, Inc.
-and authors listed above.
-Copyright (c) 2011 Gaetano Catalli
-Copyright (C) 2000-2003 Geoffrey Wossum (gwos...@acm.org)
-Copyright (C) 2000 The NetBSD Foundation, Inc.
-Copyright (C) 1995, 1996, 1997, and 1998 WIDE Project.
-Copyright (c) 1982, 1986, 1990, 1993 The Regents of the University of 
California.
-Copyright (c) 2008, 2012 Vincent Bernat 
-Copyright (c) 2014 Michael Chapman
-Copyright (c) 2014 WindRiver, Inc.
-Copyright (c) 2014 Avaya, Inc.
-Copyright (c) 2001 Daniel Hartmeier
-Copyright (c) 2002 - 2008 Henning Brauer
-Copyright (c) 2012 Gleb Smirnoff 
+6WIND S.A.
+Alexandru Copot , with support from IXIA.
+Alexey I. Froloff.
+Amir Vadai 
+Arm Limited
+Avaya, Inc.
+Benjamin Kosnik 
+Cisco Systems, Inc
+Citrix Systems, Inc.
+Cloudbase Solutions Srl
+Cumulus Netowkrs
+Daniel Baluta 
+Daniel Hartmeier
+Dan Nicholson 
+Dustin J. Mitchell 
+Ed Maste
+Eelco Chaudron
+Ericsson AB
+Free Software Foundation, Inc.,
+Gaetano Catalli
+Gary S. Brown.
+Geoffrey Wossum (gwos...@acm.org)
+Gleb Smirnoff 
+Grant Jenks
+Henning Brauer
+Hewlett Packard Enterprise Development LP
+Horms Solutions Ltd.
+IBM
+Ilya Maximets 
+Javier Fernandez-Sanguino 
+Jean Tourrilhes - HP-Labs.
+Jiri Pirko 
+Kmindg 
+Krzesimir Nowak 
+M3S, Srl - Italy
+Mark Pilgrim
+Mellanox Technologies, Ltd.
+Michael Chapman
+Moritz Klammler
+Netronome
+Nicira, Inc.
+Open Networking Foundation
+Paolo Abeni 
+Paul Norman 
+Red Hat, Inc.
+Roy Stogner 
+Samsung Electronics Co.,Ltd.
+Scott James Remnant 
+Scott Pakin 
+Siemens AG
+Sten Spans 
+Stephen Finucane 
+The Board of Trustees of The Leland Stanford Junior University
+The NetBSD Foundation, Inc.
+The Regents of the University of California.
+The University of Waikato
+USAGI/WIDE Project
+Vincent Bernat 
+VMware, Inc.
+WIDE Project.
+WindRiver, Inc.
+YAMAMOTO Takashi
+Zack Weinberg 
+Zmanda Inc. 
 
 License:
 
-- 
2.21.0

Bug#905209: libgraphviz-dev: broken symlinks: /usr/lib/tcl8.6/graphviz/lib*.so -> lib*.so.0.0.0

[GCS]

On Wed, Oct 9, 2019 at 6:12 PM Sven Joachim  wrote:
> In the current libgraphviz-dev version (2.42.2-2) the originally
> reported symlinks are gone, but a new one has popped up:
>
> ,
> | % file /usr/lib/x86_64-linux-gnu/graphviz/libgvplugin_visio.so
> | /usr/lib/x86_64-linux-gnu/graphviz/libgvplugin_visio.so: broken symbolic 
> link to libgvplugin_visio.so.6.0.0
> `
 Fixed these with others. Upload is coming, but please ping back if
you may find other broken symlinks.

Thanks,
Laszlo/GCS

Bug#942022: librsvg: FTBFS on ppc64el: assertion failed: bounds.x1 >= bounds.x0

[Simon McVittie]

On Wed, 09 Oct 2019 at 18:29:23 +0200, Frédéric Bonnard wrote:
> I see 2.44.14 which previously built, does not built in the very same build
> environment where 2.44.15 fails.
> Looking at the differences and trying downgrading some build deps, I
> found that replacing rustc 1.37 with 1.36 makes 2.44.14 and 2.44.15 build
> again in that latest schroot.
> Any idea about changes brought by 1.37 ?

Sorry, I think someone who knows more Rust than me will have to take
over at this point.

smcv

Bug#908111: mutt: No S/MIME support in mutt, fails to locate certificates, no signing/encryption possible.

[Axel Beckert]

Dear Karlheinz,

dk...@darc.de wrote:
> mutt 1.10.1-2 fails to sign, encrypt and verfiy S/MIME E-Mail messages.
> 
> "#840850 mutt: Mutt can't find S/MIME key to sign messages" suggests to
> _unset crypt_use_gpgme_ in muttrc, but this changes nothing.

Really nothing?

For me it definitely changed the error message from IIRC "secret key
`fea09d36.0' not found: End of file?" to something like "Can't open
file /home/abe/.smime/certificates/0x91178E78F3FD43F14391244E67B3FB6257AB0136:
file not found" — at least a clearly a different error message despite
again about a key not being found.

I first solved this by maing a symlink from the file name in the new
error message to the file with the old certificate:

$ cd ~/.smime/certificates/
$ ln -vis fea09d36.0 0x91178E78F3FD43F14391244E67B3FB6257AB0136

This helped to find the certificate, but the verification of the sent
mails now failed because the (in my and most cases necessary)
intermediate certificate was no more included.

So I removed the the symlink again and created a new file named
0x91178E78F3FD43F14391244E67B3FB6257AB0136 containing my certificate
and the intermediate certificate concatenated:

$ cat fea09d36.0 cfb2f36d.0 > 0x91178E78F3FD43F14391244E67B3FB6257AB0136

>From then on, my mutt was able to sent S/MIME signed mails again.
(Haven't tried S/MIME-encryption yet, though.)

The only thing I so far didn't figure out is, what kind of hashes were
and are now used for looking for the certificate files.

> thx fer ani hlp, vy 73 de Karlheinz, DK8KK

HTH. (Sorry, still no AFu speak here. :-)

And JFTR of #840850: The bug has been initially reported by a version
older than in Stretch, but I never had this issue in Stretch, just
after upgrading from Stretch (1.7.2-1+deb9u1) to Buster (1.10.1-2.1 —
mutt, not neomutt).

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#925344: polkit-qt-1: NMU diff for 0.112.0-7.1

[Thorsten Glaser]

Dear maintainer,

please find the NMU debdiff attached. I have uploaded to
the DELAYED/5 queue, in accordance with devref and my
previously stated intent to NMU.

Please do include the diff in the next maintainer upload.

Thanks for your consideration,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**diff -Nru polkit-qt-1-0.112.0/debian/changelog 
polkit-qt-1-0.112.0/debian/changelog
--- polkit-qt-1-0.112.0/debian/changelog2019-08-31 21:24:32.0 
+0200
+++ polkit-qt-1-0.112.0/debian/changelog2019-10-09 19:22:38.0 
+0200
@@ -1,3 +1,11 @@
+polkit-qt-1 (0.112.0-7.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Apply patch from Mark Hindley to Use new logind virtual packages
+instead of libpam-systemd (Closes: #925344)
+
+ -- Thorsten Glaser   Wed, 09 Oct 2019 19:22:38 +0200
+
 polkit-qt-1 (0.112.0-7) unstable; urgency=medium
 
   * Teamp upload.
diff -Nru polkit-qt-1-0.112.0/debian/control polkit-qt-1-0.112.0/debian/control
--- polkit-qt-1-0.112.0/debian/control  2019-08-31 21:22:59.0 +0200
+++ polkit-qt-1-0.112.0/debian/control  2019-10-09 19:22:34.0 +0200
@@ -37,7 +37,8 @@
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
-Depends: libpam-systemd [linux-any], ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends},
+ default-logind [linux-any] | logind [linux-any]
 Description: PolicyKit-qt5-1 library
  PolicyKit is an application-level toolkit for defining and handling the policy
  that allows unprivileged processes to speak to privileged processes.

Bug#435681: Fixed in 3.3.0

[Topi Miettinen]

Using $XDG_DATA_HOME, falling back to $HOME/.local/share/, was 
implemented with 54901bcd1672c9e22db35c66741ec2eda123b491, which was 
released in 3.3.0.


-Topi

Bug#942061: ITP: jax-maven-plugin -- Using the xjc goal with OpenJDK 11+

[Mechtilde Stehmann]

Package: wnpp
Severity: wishlist

* Package name: libjax-maven-pulgin-java
  Version : 0.1.8
  Upstream Author : Dave Moten
* URL : https://github.com/davidmoten/jax-maven-plugin
* License : Apache License 2.0
  Programming Lang: Java
  Description : Using the xjc goal with OpenJDK 11+

Supports the xjc goal and others. We wanted to move to OpenJDK 11+


It is a dependency for Jollyday, which is a dependency of JVerein



It should be maintained by the java-team

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



signature.asc
Description: OpenPGP digital signature

Bug#942060: mirror submission for us.mirror.nsec.pt

[NSEC Mirror Team]

Package: mirrors
Severity: wishlist
User: mirr...@packages.debian.org
Usertags: mirror-submission

Submission-Type: new
Site: us.mirror.nsec.pt
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Maintainer: NSEC Mirror Team 
Country: US United States
Location: Vint Hill, Virgina, United States
Sponsor: NSEC http://www.nsec.pt/
Comment: Hello.
 
 I'd like to add a new mirror to the official Debian mirror list. For now it 
only has public http but we are also thinking about adding ftp. 
 
 The connection is 1gbit, and we have all the archives (/debian, /debian-cd, 
/debian-archive).
 debian is updated 4 times a day, cd and archive are updated daily.
 
 We already prepared the push mirroring and just need to get the ssh public 
keys of the Tier 1 mirrors for it to work.
 
 Thanks.




Trace Url: http://us.mirror.nsec.pt/debian/project/trace/
Trace Url: http://us.mirror.nsec.pt/debian/project/trace/ftp-master.debian.org
Trace Url: http://us.mirror.nsec.pt/debian/project/trace/us.mirror.nsec.pt

Bug#942059: gcc-9-cross: uses “long” as “time_t” leading to failure on most new 32-bit architectures

[Thorsten Glaser]

Source: gcc-9-cross
Version: 12
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)


x86_64-linux-gnux32-g++-9 -fno-PIE -c -g -I-I../../src/gcc/gm2 -Igm2 
-I../../src/gcc/gm2/gm2-gcc -Igm2/gm2-gcc   -g -O2 -DIN_GCC  
-DCROSS_DIRECTORY_STRUCTURE   -fno-exceptions -fno-rtti 
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
-Wcast-qual-DHAVE_CONFIG_H -I. -Igm2 -I../../src/gcc -I../../src/gcc/gm2 
-I../../src/gcc/../include -I../../src/gcc/../libcpp/include  
-I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/bid 
-I../libdecnumber -I../../src/gcc/../libbacktrace   -I. -Igm2 -I../../src/gcc 
-I../../src/gcc/gm2 -I../../src/gcc/../include 
-I../../src/gcc/../libcpp/include  -I../../src/gcc/../libdecnumber 
-I../../src/gcc/../libdecnumber/bid -I../libdecnumber 
-I../../src/gcc/../libbacktrace  ../../src/gcc/gm2/gm2-lang.c -o gm2/gm2-lang.o
../../src/gcc/gm2/m2.flex: In function 'void handleDate()':
../../src/gcc/gm2/m2.flex:354:24: error: cannot convert 'long int*' to 
'time_t*' {aka 'long long int*'}
  354 |   time_t  clock = time((long *)0);
  |^
  ||
  |long int*
In file included from ../../src/gcc/system.h:337,
 from ../../src/gcc/gm2/gm2-gcc/gcc-consolidation.h:23,
 from ../../src/gcc/gm2/m2.flex:22:
/usr/include/time.h:75:29: note:   initializing argument 1 of 'time_t 
time(time_t*)'
   75 | extern time_t time (time_t *__timer) __THROW;
  | ^~~
make[5]: *** [../../src/gcc/gm2/Make-lang.in:1124: 
gm2/gm2-compiler-boot/m2flex.o] Error 1

Bug#942058: puredata-core: floating point exception

[IOhannes m zmoelnig]

Package: puredata-core
Version: 0.50.0-1
Severity: important

Dear Maintainer,

during a workshop one of the participants did a fresh installation of puredata
on their Debian/bullseye laptop, but were unable to run it as the program
terminated immediately with a floating point exception.

This is an amd64 system with (iirc) an i7 processor.
(hopefully i can gather more information in the next days).

Bug#942054: [Pkg-javascript-devel] Bug#942054: node-oauth does not honor "nocheck" build profile

[Xavier]

Le Mercredi, Octobre 09, 2019 18:12 CEST, Sven Mueller 
 a écrit:
> Source: node-oauth
> Version: 0.9.11-1
> Severity: normal
>
> Debian policy defines the "nocheck" build profile to enable skipping any
> tests. I would need to skip tests because the tests access the network (see
> http://bugs.debian.org/830214) and my build machine doesn't allow DNS
> resolution.
>
> The contents of override_dh_auto_test should be wrapped in
> ifeq ($(filter nocheck, $(DEB_BUILD_OPTIONS)),)
>
> endif

TODO: switch test and install to pkg-js-tools to avoid this and other lintian 
warnings

Bug#942022: works with rustc 1.36

[Frédéric Bonnard]

Hi,
I see 2.44.14 which previously built, does not built in the very same build
environment where 2.44.15 fails.
Looking at the differences and trying downgrading some build deps, I
found that replacing rustc 1.37 with 1.36 makes 2.44.14 and 2.44.15 build
again in that latest schroot.
Any idea about changes brought by 1.37 ? maybe bisecting rustc could help point 
out some commit.


F.


pgpfveYXdEmmx.pgp
Description: PGP signature

Bug#942057: claws-mail: shows wrong sha256 certificate fingerprint

[koniu]

Package: claws-mail
Version: 3.17.3-2
Severity: normal

Hi,

Just a headsup- current claws in stable/testing (3.17.3-2) shows wrong sha256
certificate fingerprints.

This was fixed in 3.17.4, in sid since August. Is there a block to
upgrade in  testing/stable?

Upstream bug report:
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4143
The fix:
https://git.claws-mail.org/?p=claws.git;a=commit;h=8b5f46f3d98ec16c2050737659451fef2bff3a2a

Bug#942056: openvswitch: Incomplete debian/copyright?

[Chris Lamb]

Source: openvswitch
Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-1
Severity: serious
Justication: Policy §12.5
X-Debbugs-CC: Thomas Goirand , ftpmas...@debian.org

Hi,

I just ACCEPTed openvswitch from NEW but noticed it was missing 
attribution in debian/copyright for at least Ericsson.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#845162: ntfs-3g: Please include plugin ntfs-3g-system-compression

[Jean-Pierre André]

> Sep  4 22:22:04 basil ntfs-3g[25041]: Hint
> /usr/lib/x86_64-linux-gnu/ntfs-3g/ntfs-plugin-801b.so: cannot open
> shared object file: No such file or directory

The tag 801b is not about system compression, but
for what Microsoft calls IO_REPARSE_TAG_APPEXECLINK.
AFAIK it is a trigger to start (or install) some Windows
application.

It is not clear what should be expected when accessing
such file from Linux, so this is bound to remain unsupported
until someone suggests some useful action.

Bug#942051: debian-policy: [4.9] requirement to write only to /tmp, /var/tmp, ${TMPDIR} is too strict

[Simon McVittie]

On Wed, 09 Oct 2019 at 18:08:09 +0200, Bill Allombert wrote:
> On Wed, Oct 09, 2019 at 05:51:53PM +0200, Ansgar Burchardt wrote:
> > There are
> > other paths that should be fine to be written to during the build
> > process, for example /dev/shm
> 
> Do you have example of packages that does that ?

Anything that uses the POSIX shared memory API (shm_open()), and notably
anything that is built using fakeroot with its default fakeroot-sysv
backend.

smcv

Bug#878091: jq: accepts invalid JSON

[陳昌倬]

Control: forwarded -1 https://github.com/stedolan/jq/issues/1404


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debconf,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#942051: debian-policy: [4.9] requirement to write only to /tmp, /var/tmp, ${TMPDIR} is too strict

[Bill Allombert]

On Wed, Oct 09, 2019 at 05:51:53PM +0200, Ansgar Burchardt wrote:
> Package: debian-policy
> Version: 4.4.1.1
> Severity: minor
> 
> While checking the upgrade checklist I noticed this new requirement:
> 
> +---
> | 4.9
> |Required targets must not write outside of the unpacked source
> |package tree, except for TMPDIR, /tmp and /var/tmp.
> +---
> 
> The wording is a bit too strict and should be relaxed.  There are
> other paths that should be fine to be written to during the build
> process, for example /dev/shm, /run/lock[1], or possibly anything
> below /proc/ for processes spawned by the build process.

Hello Ansgar,

Do you have example of packages that does that ?

(FWIW I do not consider writing to /proc/pid to be writing.
This is the same issue as with using localhost and network access.)

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 

Bug#941937: apt: Unexpected linkage dependency on libsystemd

[Balint Reczey]

Hi David,

On Wed, Oct 9, 2019 at 6:03 PM David Kalnischkies  wrote:
>
> On Wed, Oct 09, 2019 at 12:53:45AM +0200, Adam Borowski wrote:
> > It's not about not being available in normal use, it's because switching the
> > library's implementation is fragile -- especially if systemd's prerm fails
> > which it's notorious to.  This will make apt fail, and apt happens to be the
> > very package supposed to fix such a problem.
>
> I think systemd has to many fingers in too many areas to switch it out at
> runtime. But I also think you and everyone else reading this bugreport
> knows that better than I do. That might be unfortunate, but as a user is
> unlikely to change from and to it a lot it seems like a waste to
> optimize for potential problems in "unrelated" packages (if we called
> every package with a failing maintainer script related to apt because it
> makes apt fail, apt would be related to the entire archive).
>
> APT is also not "the very package supposed to fix such a problem". The
> entire program family is supposed to start from a consistent state and
> end in a consistent state. Some tools like apt might have a --fix-broken
> mode which tries to help if it is really easy, but the only tool which
> can help you for real if you deal with major breakage is dpkg: That not
> only knows what a maintainer script is (apt doesn't) – it is also
> essential, so it [normally] works even in inconsistent states.
>
>
> > > I expect that apt will eventually switch to using libglib's dbus support,
> > > once we implement a daemon, but that's a bit off, and that stuff might 
> > > live
> > > in a separate binary to not pull in libglib on systems that don't need a
> > > daemon.
> >
> > Would you accept a patch to move the inhibit function to a small separate
> > binary?  That'd be a very simple solution.
>
> The Inhibit() is implemented in libapt so that shutdown is inhibited for
> all libapt-based tools from aptitude to unattended-upgrades – and so
> they all gain this linkage via libapt.

For the record unattended-upgrades handles inhibition on its own
(differently) and did so before libapt added inhibition handling.

Cheers,
Balint

-- 
Balint Reczey
Ubuntu & Debian Developer

Bug#942055: cups-filters: Fails to print on Brother HL-2035 (foomatic/kl1250) with ghostscript 9.27~dfsg-2+deb10u2 armel

[Michael Schütz]

Package: cups-filters
Version: 1.21.6-5
Severity: normal

Dear Maintainer,

the problem starts with upgrading from 'stretch' to 'buster'.
Printer doesn't print properly. 

After downgrade ghostscript, libgs9 and libgs9-common to the version from 
oldstable ('stretch'), printer works properly again.


-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (500, 'stable'), (500, 'oldstable')
Architecture: armel (armv5tel)

Kernel: Linux 4.19.0-6-marvell
Kernel taint flags: TAINT_CRAP
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cups-filters depends on:
ii  bc 1.07.1-2+b1
ii  cups-filters-core-drivers  1.21.6-5
ii  ghostscript9.26a~dfsg-0+deb9u5
ii  libc6  2.28-10
ii  libcups2   2.2.10-6+deb10u1
ii  libcupsfilters11.21.6-5
ii  libcupsimage2  2.2.10-6+deb10u1
ii  libfontconfig1 2.13.1-2
ii  libfontembed1  1.21.6-5
ii  libgcc11:8.3.0-6
ii  libqpdf21  8.4.0-2
ii  libstdc++6 8.3.0-6
ii  poppler-utils  0.71.0-5

ii  libgs9:armel   9.26a~dfsg-0+deb9u5 armel
ii  libgs9-common  9.26a~dfsg-0+deb9u5 all


Versions of packages cups-filters recommends:
ii  colord 1.4.3-4
ii  liblouisutdml-bin  2.7.0-5+b1

Versions of packages cups-filters suggests:
ii  antiword   0.37-14
ii  docx2txt   1.4-1
ii  foomatic-db-compressed-ppds [foomatic-db]  20181217-2
ii  imagemagick8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]8:6.9.10.23+dfsg-2.1

-- no debconf information

Bug#942054: node-oauth does not honor "nocheck" build profile

[Sven Mueller]

Source: node-oauth
Version: 0.9.11-1
Severity: normal

Debian policy defines the "nocheck" build profile to enable skipping any
tests. I would need to skip tests because the tests access the network (see
http://bugs.debian.org/830214) and my build machine doesn't allow DNS
resolution.

The contents of override_dh_auto_test should be wrapped in
ifeq ($(filter nocheck, $(DEB_BUILD_OPTIONS)),)
   
endif

Bug#905209: libgraphviz-dev: broken symlinks: /usr/lib/tcl8.6/graphviz/lib*.so -> lib*.so.0.0.0

[Sven Joachim]

On 2018-10-13 14:58 +0200, Andreas Beckmann wrote:

> Followup-For: Bug #905209
> Control: found -1 2.40.1-5
>
> Hi,
>
> I don't see a change w.r.t. these broken symlinks in the last upload.
> Did you want to close #910198 instead?

In the current libgraphviz-dev version (2.42.2-2) the originally
reported symlinks are gone, but a new one has popped up:

,
| % file /usr/lib/x86_64-linux-gnu/graphviz/libgvplugin_visio.so
| /usr/lib/x86_64-linux-gnu/graphviz/libgvplugin_visio.so: broken symbolic link 
to libgvplugin_visio.so.6.0.0
`

According to apt-file there is no libgvplugin_visio.so.6.0.0 anywhere in
the archive.

Cheers,
   Sven

Bug#942053: dh-runit: generates dangling symlinks

[Sven Joachim]

Package: dh-runit
Version: 2.8.14

The fix for bug #934500 has the side effect of introducing broken
symlinks[1] into packages using it, causing complaints by tools that
report such oddities, e.g. adequate(1) or symlinks(1):

,
| $ sudo symlinks -r /etc | grep dangling
| dangling: /etc/sv/ssh/log/supervise -> /run/runit/supervise/ssh.log
| dangling: /etc/sv/ssh/supervise -> /run/runit/supervise/ssh
| $ adequate openssh-server
| openssh-server: broken-symlink /etc/sv/ssh/log/supervise -> 
/run/runit/supervise/ssh.log
| openssh-server: broken-symlink /etc/sv/ssh/supervise -> 
/run/runit/supervise/ssh
`

I find that quite annoying.


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

Kernel: Linux 5.3.5-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


1. For people who actually use runit as init system the symlinks are
   probably not broken, but that is currently a small minority.

Bug#313382:

[Руля Штаф]

On Wed, 9 Oct 2019 08:45:06 -0700 =?UTF-8?B?0KDRg9C70Y8g0KjRgtCw0YQ=?= <
rulast...@gmail.com> wrote:
>

Bug#942052: Libreoffice window doesn't scroll up or down when another window is minimized

[Salvi Loris]

Package: libreoffice
Version: 6.1.5.2

If a Libreoffice window is maximized, it won't scroll up or down with 
the mouse wheel when another window in front of it is minimized. It 
isn't a focus problem, because if i press any keyboard's key or if i 
press CTRL + 'mouse wheel', everything works fine. The bug is just about 
scroll up or down.


I'm using Debian Buster with KDE:

Debian GNU/Linux 10 4.19.0-6-amd64
KDE Plasma: 5.14.5
Qt: 5.11.3

Step to reproduce:

1) Open a libreoffice's window and maximize it
2) Open another window and maximize it (I tried with Thunderbird, 
Firefox, Kwrite, etc.)

2.1) Be sure two windows are in the same desktop
2.2) Be sure libreoffice's window is behind the other window
3) Minimize the second window
4) In the libreoffice window that will show up, try to scroll up or down.

Thank you,
Loris


AVVISO: Questo messaggio e' inviato da Banca Sammarinese di Investimento S.p.A. 
e puo' contenere informazioni di carattere estremamente riservato e 
confidenziale. Qualsivoglia utilizzo non autorizzato del contenuto di questo 
messaggio costituisce violazione dell'obbligo di non prendere cognizione della 
corrispondenza tra altri soggetti, salvo piu' grave illecito ed espone il 
responsabile alle relative conseguenze.
Qualora non foste i destinatari, vogliate immediatamente informarci con lo 
stesso mezzo ed eliminare il messaggio, con gli eventuali allegati, senza 
trattenerne copia. Grazie per la collaborazione.

DISCLAIMER: This e-mail contains confidential information, which is intended 
only for the use of the recipient(s) named above. If you have received this 
communication in error, please notify the sender immediately via e-mail and 
return the entire message. Thank you for your assistance.

Bug#313382:

[Руля Штаф]

Bug#940730: [External] Re: Bug#940730: alsa-utils: Add ucm support for whiskeylake sof-skl_hda_card audio

[Hector Oron]

On Wed, Sep 25, 2019 at 03:07:21PM +, Mark Pearson wrote:
> > 
> > This is not a Debian specific bug. It should be handled by the ALSA project
> > itself to provide it for all linux distributions using ALSA.
> > 
> Hi Elimar,
> 
> The ALSA team have done an initial import of the new alsa-ucm-conf repository 
> (https://github.com/alsa-project/alsa-ucm-conf/tree/import) which has the 
> support for the sof-skl_hda_card which I was looking for with this bug.
> 
> How does it work for this making its way into Debian? I appreciate that it's 
> still all new and an exercise in progress on the ALSA side but was curious as 
> to how the process worked from there with regards to Debian.

I have backported patches from upstream project into current SID
package. Find attached patches that apply on top of alsa-lib in
salsa.debian.org.

@Mark, could you please verify those patches are fine and build
them?

Regards
From 945fa07aa6c078e72402ff8f76f0828220dcb05d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?H=C3=A9ctor=20Or=C3=B3n=20Mart=C3=ADnez?= 
Date: Wed, 9 Oct 2019 17:33:59 +0200
Subject: [PATCH 1/2] conf/ucm: sof-skl_hda_card: backport
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

  Fixes audio on Lenovo X1 Carbon Gen 7 using the whiskeylake processor.
  (Closes: #940730)

Signed-off-by: Héctor Orón Martínez 
---
 .../patches/backport-sof-skl_hda_card.patch   | 681 ++
 debian/patches/series |   1 +
 2 files changed, 682 insertions(+)
 create mode 100644 debian/patches/backport-sof-skl_hda_card.patch

diff --git a/debian/patches/backport-sof-skl_hda_card.patch b/debian/patches/backport-sof-skl_hda_card.patch
new file mode 100644
index ..e172b3b9
--- /dev/null
+++ b/debian/patches/backport-sof-skl_hda_card.patch
@@ -0,0 +1,681 @@
+Description: Add support for sof-skl_hda_card
+Fixes support for Lenovo X1 Carbon Gen 7 using the whiskeylake processor
+.
+Author: Héctor Orón Martínez 
+Bug-Debian: https://bugs.debian.org/940730
+Origin: upstream
+Forwarded: not-needed
+Reviewed-By: Mark Pearson 
+Last-Update: 2019-10-09
+
+--- alsa-lib-1.1.8.orig/src/conf/ucm/Makefile.am
 alsa-lib-1.1.8/src/conf/ucm/Makefile.am
+@@ -44,6 +44,7 @@ PAZ00 \
+ PIPO-W2S-Defaultstring-CherryTrailCR \
+ SDP4430 \
+ skylake-rt286 \
++sof-skl_hda_card \
+ TECLAST-X80Pro-Defaultstring-CherryTrailCR \
+ tegraalc5632 \
+ VEYRON-I2S
+--- /dev/null
 alsa-lib-1.1.8/src/conf/ucm/sof-skl_hda_card/HiFi.conf
+@@ -0,0 +1,166 @@
++# Use case Configuration for skl-hda-card
++
++SectionVerb {
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Master Playback Switch' on"
++		cset "name='Capture Switch' on"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++}
++
++SectionDevice."Headphone" {
++	Comment "Headphone"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Headphone Playback Switch' on"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Headphone Playback Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:sofsklhdacard,0"
++		PlaybackChannels "2"
++		JackName "sof-skl_hda_card Headphone"
++		JackType "gpio"
++		JackSwitch "12"
++		JackControl "Headphone Jack"
++	}
++}
++
++SectionDevice."Speaker" {
++	Comment "Speaker"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Speaker Playback Switch' on"
++	]
++
++	DisableSequence [
++		cset "name='Speaker Playback Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:sofsklhdacard,0"
++		JackHWMute "Headphone"
++		PlaybackChannels "2"
++	}
++}
++
++SectionDevice."Headset" {
++	Comment "Headset Mic"
++
++	ConflictingDevice [
++		"DMIC Stereo"
++	]
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	Value {
++		CapturePCM "hw:0,0"
++		CaptureChannels "2"
++		JackControl "Mic Jack"
++	}
++}
++
++SectionDevice."Dmic" {
++	Comment "DMIC Stereo"
++
++	ConflictingDevice [
++		"Headset Mic"
++	]
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++	]
++
++	Value {
++		CapturePCM "hw:0,6"
++		CaptureChannels "2"
++	}
++}
++
++SectionDevice."HDMI1" {
++	Comment "HDMI1/DP1 Output"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='hif5-0 Jack Switch' on"
++		cset "name='Pin5-Port0 Mux' 1"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Pin5-Port0 Mux' 0"
++		cset "name='hif5-0 Jack Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:0,3"
++		PlaybackChannels "2"
++		JackControl "HDMI/DP, pcm=11 Jack"
++	}
++}
++
++SectionDevice."HDMI2" {
++	Comment "HDMI2/DP2 Output"
++
++	EnableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='hif6-0 Jack Switch' on"
++		cset "name='Pin6-Port0 Mux' 2"
++	]
++
++	DisableSequence [
++		cdev "hw:sofsklhdacard"
++		cset "name='Pin6-Port0 Mux' 0"
++		cset "name='hif6-0 Jack Switch' off"
++	]
++
++	Value {
++		PlaybackPCM "hw:0,4"
++		

Bug#942051: debian-policy: [4.9] requirement to write only to /tmp, /var/tmp, ${TMPDIR} is too strict

[Ansgar Burchardt]

Package: debian-policy
Version: 4.4.1.1
Severity: minor

While checking the upgrade checklist I noticed this new requirement:

+---
| 4.9
|Required targets must not write outside of the unpacked source
|package tree, except for TMPDIR, /tmp and /var/tmp.
+---

The wording is a bit too strict and should be relaxed.  There are
other paths that should be fine to be written to during the build
process, for example /dev/shm, /run/lock[1], or possibly anything
below /proc/ for processes spawned by the build process.

Ansgar

  [1] Which I noticed is world-writable which I'm not sure should be
  as users could then fill /run...  Note that /run/user/ has
  separate filesystems to avoid this problem; but then there are
  many paths below /run writable by service users which can cause
  the same problems.

Bug#313382:

[Руля Штаф]

Bug#941937: apt: Unexpected linkage dependency on libsystemd

[David Kalnischkies]

On Wed, Oct 09, 2019 at 12:53:45AM +0200, Adam Borowski wrote:
> It's not about not being available in normal use, it's because switching the
> library's implementation is fragile -- especially if systemd's prerm fails
> which it's notorious to.  This will make apt fail, and apt happens to be the
> very package supposed to fix such a problem.

I think systemd has to many fingers in too many areas to switch it out at
runtime. But I also think you and everyone else reading this bugreport
knows that better than I do. That might be unfortunate, but as a user is
unlikely to change from and to it a lot it seems like a waste to
optimize for potential problems in "unrelated" packages (if we called
every package with a failing maintainer script related to apt because it
makes apt fail, apt would be related to the entire archive).

APT is also not "the very package supposed to fix such a problem". The
entire program family is supposed to start from a consistent state and
end in a consistent state. Some tools like apt might have a --fix-broken
mode which tries to help if it is really easy, but the only tool which
can help you for real if you deal with major breakage is dpkg: That not
only knows what a maintainer script is (apt doesn't) – it is also
essential, so it [normally] works even in inconsistent states.


> > I expect that apt will eventually switch to using libglib's dbus support,
> > once we implement a daemon, but that's a bit off, and that stuff might live
> > in a separate binary to not pull in libglib on systems that don't need a
> > daemon.
> 
> Would you accept a patch to move the inhibit function to a small separate
> binary?  That'd be a very simple solution.

The Inhibit() is implemented in libapt so that shutdown is inhibited for
all libapt-based tools from aptitude to unattended-upgrades – and so
they all gain this linkage via libapt.

You can disable it at runtime by setting DPkg::Inhibit-Shutdown to false
via config/option. That still requires that the linker can find
something to load, but that is a given in a consistent state and in
a state so broken that the linker can't, no libapt-based tool can be of
much help anyhow.

So, I am not sure what a small separate binary would give us…
As Julian already said, it is "just" used for its dbus communication
implementation. We don't require systemd to be your init or to be even
functional. So I guess proposing an alternative which a) works equally
well and b) doesn't add additional bootstrapping complications has
better chances of acceptance – assuming that exists as the obvious
choice libdbus links against libsystemd as well even before checking a)
and b) …


Best regards

David Kalnischkies


signature.asc
Description: PGP signature

Bug#942050: gnome-shell: gnome shell does not take the org.gnome.desktop.peripherals.keyboard numlock-state into account

[Jean-Marc]

Package: gnome-shell
Version: 3.34.0-2
Severity: normal

Dear Maintainer,


Since the last upgrade from gnome-shell 3.30 to 3.34, the gnome-shell does not 
take the gsettings org.gnome.desktop.peripherals.keyboard numlock-state into 
account and always start with org.gnome.desktop.peripherals.keyboard 
numlock-state set to false.

I set "org.gnome.desktop.peripherals.keyboard remember-numlock-state true" on 
my system. to keep the numlock-state to the same value reboot after reboot, 
session after session.

So, when GDM starts, it remembers the last numlock-state.

With gnome-shell 3.30, it was the same.

Now, with gnome-shell 3.34, it always start with numlock-state set to false 
leading to strange behaviors.

For example, if I leave the session with numlock on, when I re-open a new 
session, gsettings show this:
$ gsettings list-recursively | grep keyboard.*numlock
org.gnome.desktop.peripherals.keyboard remember-numlock-state true
org.gnome.desktop.peripherals.keyboard numlock-state true

and my numlock key on my keyboard is set to on too (with the led swtiched to 
on) but when I type on the numpad, I do not get numbers.

I have to type on numlock key, swithing the led off to get my numpad working as 
it was on.

For example, now, that's my setting:
$ gsettings list-recursively | grep keyboard.*numlock
org.gnome.desktop.peripherals.keyboard remember-numlock-state true
org.gnome.desktop.peripherals.keyboard numlock-state false

and the numpad with the led off gives numbers.


I hope I am clear in my explanations.

Regards,

Jean-Marc



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

Kernel: Linux 5.2.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.34.0-1
ii  evolution-data-server3.34.0-3
ii  gir1.2-accountsservice-1.0   0.6.45-2
ii  gir1.2-atspi-2.0 2.34.0-3
ii  gir1.2-freedesktop   1.62.0-2
ii  gir1.2-gcr-3 3.33.4-2
ii  gir1.2-gdesktopenums-3.0 3.34.0-2
ii  gir1.2-gdm-1.0   3.34.0-2
ii  gir1.2-geoclue-2.0   2.5.5-1
ii  gir1.2-glib-2.0  1.62.0-2
ii  gir1.2-gnomebluetooth-1.03.34.0-1
ii  gir1.2-gnomedesktop-3.0  3.34.0-2
ii  gir1.2-gtk-3.0   3.24.12-1
ii  gir1.2-gweather-3.0  3.28.3-2
ii  gir1.2-ibus-1.0  1.5.19-4+b1
ii  gir1.2-mutter-5  3.34.0-4
ii  gir1.2-nm-1.01.20.2-1
ii  gir1.2-nma-1.0   1.8.22-2
ii  gir1.2-pango-1.0 1.42.4-7
ii  gir1.2-polkit-1.00.105-26
ii  gir1.2-rsvg-2.0  2.44.14-1
ii  gir1.2-soup-2.4  2.68.1-2
ii  gir1.2-upowerglib-1.00.99.11-1
ii  gjs  1.58.0-2
ii  gnome-backgrounds3.34.0-1
ii  gnome-settings-daemon3.34.0-3
ii  gnome-shell-common   3.34.0-2
ii  gsettings-desktop-schemas3.34.0-2
ii  libatk-bridge2.0-0   2.34.0-3
ii  libatk1.0-0  2.34.0-1
ii  libc62.29-2
ii  libcairo21.16.0-4
ii  libcroco30.6.13-1
ii  libecal-2.0-13.34.0-3
ii  libedataserver-1.2-243.34.0-3
ii  libgcr-base-3-1  3.33.4-2
ii  libgdk-pixbuf2.0-0   2.38.2+dfsg-1
ii  libgirepository-1.0-11.62.0-2
ii  libgjs0g 1.58.0-2
ii  libgles2 1.1.0-1+b1
ii  libglib2.0-0 2.62.0-3
ii  libglib2.0-bin   2.62.0-3
ii  libgnome-autoar-0-0  0.2.3-2
ii  libgstreamer1.0-01.16.1-1
ii  libgtk-3-0   3.24.12-1
ii  libical3 3.0.5-2
ii  libjson-glib-1.0-0   1.4.4-2
ii  libmutter-5-03.34.0-4
ii  libnm0   1.20.2-1
ii  libpango-1.0-0   1.42.4-7
ii  libpangocairo-1.0-0  

Bug#941125: xfce4-terminal: Multiple open windows; closing one by button; bash zombie

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, 2019-09-25 at 10:36 +0200, Andries van Bergen wrote:
> Dear Maintainer,
> 
> When more than one window is open, closing one window (by button) makes a 
> zombie process of Bash.
> Closing the last window (by button), or any window by typing 'exit' clears up 
> the zombie processes.

Hi, that looks pretty weird. I don't use bash, but I can't reproduce with zsh.
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl2d/nIACgkQ3rYcyPpX
RFvUqQf+JfCruGGU1EuSCmbIACvo02jS2y4l7/pYsESGEX/aQ7dJPEOyLozyo2wU
6iRu3IXIZOq3Qqv2MnZG2gfdvfw08EZxbQZPTD3cFC3VClAD18/uT35rcG2EOx5T
6RH/6YC7+yGJVBbBx1HBuRdsAA2jp3TmXH4O8wVBoBqNUa1K7RmgavTc7HupyNWJ
UBZCSYLZqJYd24BhQb6ZySIdZtjxxUpkdfbQW/JmhuQQGpPA7N+J+wWzihEhkurM
JmCsM+naQDcobxPdLML7v7k8WGxleHzOsOZ6poRBUuibtauY8I9DvP1ACKO8TFxy
E/EEyaqeR8B9Cr4xS2jtSMyjDx6uOw==
=Of79
-END PGP SIGNATURE-

Bug#885371: Updates to cylc

[Alastair McKinstry]

Hi,

These bugs (dependence on python2, pygtk) are expected to be solved in 
the upcoming cylc-8 releases.


Unfortunately cylc-8 is feature incomplete (current alpha is server-side 
only, the GUI work not released), and will depend on stuff thats not 
packaged yet.


cylc_8.0a1-1 is in Experimental and I'm packaging upcoming expected 
dependencies. cylc-7.8.4 may be backported to buster.


Regards

Alastair

--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered. 

Bug#885813: bumping severity of xfce4-notes-plugin's use of libunique to Serious

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 2019-10-06 at 07:08 -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> 
> The Debian GNOME team would like to remove libunique from Debian.
> Therefore, I'm bumping the severity of this bug to serious.
> 
> Please see the master bug https://bugs.debian.org/895520 for
> documentation on moving away from libunique. It looks like it requires
> finishing the port to gtk3.
> 
> Because xfce4-notes-plugin is a "key package", it won't be
> automatically removed from Testing. But note that this package is one
> of the last 2 or 3 keeping libunique in Debian.
> 
Hi, thanks for the update. It seems that the GTK3 port isn't really complete.
And it seems notes isn't really maintained upstream anymore. I'm adding Mike
to the CC but we might end up completely dropping xfce4-notes-plugin from
Debian in the end.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl2d/fgACgkQ3rYcyPpX
RFs55Qf+JxcS3s1GjkDy4+TzN6+ZuB9RJ4Kx98wXE4fnYYAzDE+sMo+O8RUcbcf9
uEn14PFzQiOXqMcGL6NOXwjE+Hg71MEuwmHbnI2/JWb/QTBv1Bu0yFo3Em6dOFBn
nUtBa3a7UrxBU7fjh2RDyU5/S4EmZaZIRXZs1sPQRN79Fu3h/oM1WRabvAD6Zn2G
A1dR9DaaUpKsaKZpiIUsYQ3m3V2R6sAuT2evuVTbe/RvXFIGC+9CCgeMwkXHDqMn
PlbtOMirYoGd1o90pgSn6WScDNfHNSVUI7E/Q75vSwlqKdARDNT3m523tW9miIAO
598tOZfMnG8MgQUejyikOzoe0gvK+g==
=mAmx
-END PGP SIGNATURE-

Bug#942049: libobjc-9-dev: broken symlink /usr/lib/gcc/*/gnu/9/libobjc_gc.so

[Sven Joachim]

Package: libobjc-9-dev
Version: 9.2.1-8

Your package includes a dangling symlink:

,
| $ file /usr/lib/gcc/x86_64-linux-gnu/9/libobjc_gc.so
| /usr/lib/gcc/x86_64-linux-gnu/9/libobjc_gc.so: broken symbolic link to 
../../../x86_64-linux-gnu/libobjc_gc.so.4
`

According to apt-file there is no libobjc_gc.so.4 anywhere in the
archive.

A similar broken symlink is shipped in libobjc-8-dev and apparently also
in libobjc-7-dev (don't have libobjc-7-dev installed now).


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

Kernel: Linux 5.3.5-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libobjc-9-dev depends on:
ii  gcc-9-base9.2.1-8
ii  libgcc-9-dev  9.2.1-8
ii  libobjc4  9.2.1-8

libobjc-9-dev recommends no packages.

libobjc-9-dev suggests no packages.

-- no debconf information