Bug#950003: ITP: ppx-fields-conv -- generation of accessor and iteration functions for OCaml records

[Stéphane Glondu]

Package: wnpp
Severity: wishlist
Owner: Stéphane Glondu 

* Package name: ppx-fields-conv
  Version : 0.13.0
  Upstream Author : Jane Street Group, LLC
* URL : https://github.com/janestreet/ppx_fields_conv
* License : MIT
  Programming Lang: OCaml
  Description : generation of accessor and iteration functions for OCaml 
records

 ppx_fields_conv is a ppx rewriter that can be used to define first
 class values representing record fields, and additional routines, to
 get and set record fields, iterate and fold over all fields of a
 record and create new record values.

This package is a new dependency of sexplib310. Il will be maintained
in the OCaml team.

Bug#944282: stretch-pu: monit 1:5.20.0-6+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2019-11-07 08:49, Sergey B Kirpichev wrote:

I would like to make an upload to stable in order to fix bug
#941895 (CSRF check) in the monit package.


Please go ahead; sorry for the delay.

Regards,

Adam

Bug#949909: stretch-pu: package libparse-win32registry-perl/1.0-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 21:40, Adrian Bunk wrote:

  * Add patch to fix Y2K20 problem.
(Closes: #948682)


Please go ahead.

Regards,

ADam

Bug#949907: stretch-pu: package libtimedate-perl/2.3000-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 21:22, Adrian Bunk wrote:

  * Add patch from upstream pull request to fix Y2K20 test failure.
(Closes: #948680)


Please go ahead.

Regards,

Adam

Bug#949905: stretch-pu: package libole-storage-lite-perl/0.19-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 21:09, Adrian Bunk wrote:

  * Backport upstream fix for years >= 2020 being misinterpreted.
(Closes: #948668)


Please go ahead.

Regards,

Adam

Bug#950005: qemu-system-ppc64: Program exception in Open Firmware

[Herwig]

Package: qemu-system-ppc
Version: 1:4.2-1
Severity: important

Dear Maintainer,

It's currently impossible to boot a PPC64 image with QEMU 4.2 in Bullseye as
apparently Open Firmware crashes on launch:

$ qemu-system-ppc64 -serial stdio
qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-
cfpc=workaround
qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-
sbbc=workaround
qemu-system-ppc64: warning: TCG doesn't support requested feature, cap-
ibs=workaround


SLOF **
QEMU Starting
 Build Date = Dec 28 2018 13:55:34
 FW Version = buildd@ release 20180702
 Press "s" to enter Open Firmware.

Populating /vdevice methods
Populating /vdevice/vty@7100
Populating /vdevice/nvram@7101
Populating /vdevice/l-lan@7102
Populating /vdevice/v-scsi@7103


( 700 ) Program Exception [ 0 ]


R0 .. R7   R8 .. R15 R16 .. R23 R24 .. R31
1dbf0b34   1dc64028      0006
1e67ffe0   1e47c010   1e759592   1e680050
1dc26700   1dc64020   1dc64038   1dc1c500
1e758e20   1fbc0df0   1dbf4770   1dc20f58
      1dc21398   0003
      1dc21128   f001
      8000   1e680060
1dc64030   1e743623   f003   

CR / XER   LR / CTR  SRR0 / SRR1DAR / DSISR
8402   1dbf0b34      
2004      8008   


5 >

This also happens with qemu-system-ppc64le. The warnings can be avoided by
using "-M pseries-3.1" but this has no effect on the crash.

Best regards
Björn Herwig



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

Kernel: Linux 5.4.0-3-amd64 (SMP w/48 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)
LSM: AppArmor: enabled

Versions of packages qemu-system-ppc depends on:
ii  libaio1 0.3.112-5
ii  libasound2  1.2.1.2-2
ii  libbluetooth3   5.50-1+b1
ii  libbrlapi0.76.0+dfsg-4+b1
ii  libc6   2.29-9
ii  libcacard0  1:2.6.1-1
ii  libcapstone34.0.1+really+3.0.5-1+b1
ii  libepoxy0   1.5.4-1
ii  libfdt1 1.5.1-1
ii  libgbm1 19.3.2-1
ii  libgcc1 1:9.2.1-22
ii  libglib2.0-02.62.4-1
ii  libgnutls30 3.6.11.1-2
ii  libibverbs1 27.0-2
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  libncursesw66.1+20191019-1
ii  libnettle7  3.5.1+really3.5.1-2
ii  libnuma12.0.12-1+b1
ii  libpixman-1-0   0.36.0-1
ii  libpng16-16 1.6.37-1
ii  librdmacm1  27.0-2
ii  libsasl2-2  2.1.27+dfsg-2
ii  libseccomp2 2.4.2-2
ii  libslirp0   4.1.0-2
ii  libspice-server10.14.2-4
ii  libtinfo6   6.1+20191019-1
ii  libusb-1.0-02:1.0.23-2
ii  libusbredirparser1  0.8.0-1+b1
ii  libvdeplug2 2.3.2+r586-2.2+b1
ii  libvirglrenderer1   0.8.1-6
ii  openbios-ppc1.1.git20181001-1
ii  openhackware0.4.1+git-20140423.c559da7c-4.1
ii  qemu-slof   20180702+dfsg-1
ii  qemu-system-common  1:4.2-1
ii  qemu-system-data1:4.2-1
ii  zlib1g  1:1.2.11.dfsg-1+b1

Versions of packages qemu-system-ppc recommends:
ii  ipxe-qemu1.0.0+git-20190125.36a4c85-4
ii  qemu-system-gui  1:4.2-1
ii  qemu-utils   1:4.2-1
ii  seabios  1.13.0-1

Versions of packages qemu-system-ppc suggests:
pn  qemu-block-extra  
pn  samba 
pn  vde2  

-- no debconf information
---
Abonnieren Sie unseren Newsletter und bleiben Sie auf dem Laufenden:
https://www.gdsys.de/newsletter-anmeldung/

Subscribe to our newsletter and stay up to date:
https://www.gdsys.de/newsletter-subscription-int/
---
---
Messehighlights 2020: https://www.gdsys.de/events
Trade fair highlights 2020: https://www.gdsys.de/en/events
---
Besuchen Sie unseren Blog auf | Visit our corporate blog
https://blog.gdsys.de

oder folgen Sie uns auf | or join us at:
Linkedin: https://de.linkedin.com/company/guntermann-&-drunck-gmbh
Twitter: https://twitter.com/#!/gdsys
Facebook: https://www.facebook.com/pages/Guntermann-Drunck-GmbH/318396891518396
YouTube: 

Bug#944282: stretch-pu: monit 1:5.20.0-6+deb9u1

[Sergey B Kirpichev]

On Tue, Jan 28, 2020 at 08:37:37AM +, Adam D. Barratt wrote:
> On 2019-11-07 08:49, Sergey B Kirpichev wrote:
> > I would like to make an upload to stable in order to fix bug
> > #941895 (CSRF check) in the monit package.
> 
> Please go ahead; sorry for the delay.

Thanks, uploaded.

Bug#950008: gfan: assertion fails on riscv64

[Tobias Hansen]

Source: gfan
Version: 0.6.2-2
Severity: normal

Hi,

many of sagemath's doctests in the interface to gfan fail on riscv64 with the 
following error:

gfan_*: src/application.cpp:42: char* tail(char*): Assertion `*p==*m' failed.

It looks like the pointer arithmetic in the function tail() in application.cpp 
does not work like this on riscv64. Unfortunately there are no porterboxes for 
riscv64 yet, so I can't come up with a minimal example triggering the bug.

Best,
Tobias

Bug#950010: linux-image-5.4.0-3-amd64: System fan doesn't spin up anymore after suspend/resume

[Lennert Van Alboom]

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

After resuming from sleep, my laptop's system fan doesn't spin up
anymore, regardless of system load/temperature. It's capable of working
with passive cooling only, but the least bit of load immediately pushes
the CPU to 80°C and more. 

Only solution is rebooting. 

Can't say whether the same thing happens in 5.5-rc5 since suspend-to-ram
is broken in that kernel.




-- Package-specific info:
** Version:
Linux version 5.4.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 
20200117 (Debian 9.2.1-24)) #1 SMP Debian 5.4.13-1 (2020-01-19)

** Command line:
BOOT_IMAGE=/vmlinuz-5.4.0-3-amd64 root=/dev/mapper/NESBITT-ROOT ro quiet

** Tainted: OE (12288)
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[ 1979.596397] mce: CPU6: Package temperature/speed normal
[ 1979.596398] mce: CPU4: Core temperature/speed normal
[ 1979.596398] mce: CPU0: Core temperature/speed normal
[ 1979.596399] mce: CPU2: Package temperature/speed normal
[ 1979.596399] mce: CPU7: Package temperature/speed normal
[ 1979.596400] mce: CPU4: Package temperature/speed normal
[ 1979.596401] mce: CPU0: Package temperature/speed normal
[ 2279.602445] mce: CPU7: Core temperature above threshold, cpu clock throttled 
(total events = 23581)
[ 2279.602446] mce: CPU3: Core temperature above threshold, cpu clock throttled 
(total events = 23581)
[ 2279.602447] mce: CPU4: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602448] mce: CPU5: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602449] mce: CPU0: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602450] mce: CPU1: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602452] mce: CPU6: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602453] mce: CPU2: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602453] mce: CPU3: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.602455] mce: CPU7: Package temperature above threshold, cpu clock 
throttled (total events = 55099)
[ 2279.610462] mce: CPU3: Core temperature/speed normal
[ 2279.610463] mce: CPU7: Core temperature/speed normal
[ 2279.610464] mce: CPU1: Package temperature/speed normal
[ 2279.610464] mce: CPU4: Package temperature/speed normal
[ 2279.610465] mce: CPU2: Package temperature/speed normal
[ 2279.610466] mce: CPU0: Package temperature/speed normal
[ 2279.610466] mce: CPU5: Package temperature/speed normal
[ 2279.610467] mce: CPU6: Package temperature/speed normal
[ 2279.610467] mce: CPU7: Package temperature/speed normal
[ 2279.610468] mce: CPU3: Package temperature/speed normal
[ 2330.044453] PM: suspend entry (s2idle)
[ 2330.058903] Filesystems sync: 0.014 seconds
[ 2330.059649] (NULL device *): firmware: direct-loading firmware 
i915/icl_dmc_ver1_07.bin
[ 2330.059780] (NULL device *): firmware: direct-loading firmware 
intel/ibt-19-32-4.ddc
[ 2330.059930] (NULL device *): firmware: direct-loading firmware 
iwlwifi-Qu-c0-hr-b0-48.ucode
[ 2330.060126] (NULL device *): firmware: direct-loading firmware 
intel/ibt-19-32-4.sfi
[ 2330.060135] (NULL device *): firmware: direct-loading firmware 
iwlwifi-Qu-c0-hr-b0-50.ucode
[ 2330.060408] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 2330.062077] OOM killer disabled.
[ 2330.062077] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 2330.063460] printk: Suspending console(s) (use no_console_suspend to debug)
[ 2330.068369] wlan0: deauthenticating from aa:db:03:14:80:7c by local choice 
(Reason: 3=DEAUTH_LEAVING)
[ 2331.423122] ACPI: EC: interrupt blocked
[ 2333.893013] ACPI: EC: interrupt unblocked
[ 2335.079220] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[ 2335.226967] iwlwifi :00:14.3: FW already configured (0) - re-configuring
[ 2335.234651] iwlwifi :00:14.3: BIOS contains WGDS but no WRDS
[ 2335.471736] OOM killer enabled.
[ 2335.471737] Restarting tasks ... done.
[ 2335.496153] PM: suspend exit
[ 2335.673379] userif-2: sent link down event.
[ 2335.673381] userif-2: sent link up event.
[ 2335.991316] PM: suspend entry (s2idle)
[ 2336.002299] Filesystems sync: 0.010 seconds
[ 2336.002742] Freezing user space processes ... (elapsed 0.821 seconds) done.
[ 2336.824365] OOM killer disabled.
[ 2336.824366] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
[ 2336.825852] printk: Suspending console(s) (use no_console_suspend to debug)
[ 2337.477791] ACPI: EC: interrupt blocked
[58827.790024] ACPI: EC: interrupt unblocked
[58828.840539] ideapad_laptop: Unknown event: 10
[58828.998404] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM
[58829.646084] iwlwifi :00:14.3: FW already configured (0) - re-configuring

Bug#941617: stretch-pu: package publicsuffix/20190925.1705-0+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2019-10-02 22:29, Daniel Kahn Gillmor wrote:




Apologies for the delay in getting back to you on this, but please feel 
free to upload.


Regards,

Adam

Bug#948649: stretch-pu: package libjaxen-java/1.1.6-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-11 10:11, Adrian Bunk wrote:

https://tests.reproducible-builds.org/debian/rb-pkg/stretch/amd64/libjaxen-java.html

  * Ignore the test failures (Closes: #909216)

Backport of the workaround in buster.


Please go ahead.

Regards,

Adam

Bug#948715: stretch-pu: package xml-security-c/1.7.3-4+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-12 14:39, Ferenc Wágner wrote:

+xml-security-c (1.7.3-4+deb9u2) stretch; urgency=medium
+
+  * [12dd825] New patches: DSA verification crashes OpenSSL on invalid
+combinations of key content.
+Particular KeyInfo combinations result in incomplete DSA key 
structures
+that OpenSSL can't handle without crashing.  In the case of 
Shibboleth
+SP software this manifests as a crash in the shibd daemon.  
Exploitation
+is believed to be possible only in deployments employing the PKIX 
trust

+engine, which is generally recommended against.
+The upstream patches backported from 2.0.2 apply analogous 
safeguards to

+the RSA and ECDSA key handling as well.


Please go ahead.

Regards,

Adam

Bug#949900: stretch-pu: package libperl4-corelibs-perl/0.003-2+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 20:40, Adrian Bunk wrote:

  * Add t/timelocal.t fix for Y2K20 problem in t/timelocal.t.
(Closes: #948666)


Please go ahead.

Regards,

Adam

Bug#948653: stretch-pu: package mod-gnutls/0.8.2-3+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-11 10:34, Adrian Bunk wrote:

  * Avoid deprecated ciphersuites in test suite (Closes: #907008)

FTBFS, tests were broken by gnutls28 3.5.8-5+deb9u4.


Please go ahead.

Regards,

Adam

Bug#950004: ITP: ppx-variants-conv -- generation of accessor and iteration functions for OCaml variant types

[Stéphane Glondu]

Package: wnpp
Severity: wishlist
Owner: Stéphane Glondu 

* Package name: ppx-variants-conv
  Version : 0.13.0
  Upstream Author : Jane Street Group, LLC
* URL : https://github.com/janestreet/ppx_variants_conv
* License : MIT
  Programming Lang: OCaml
  Description : generation of accessor and iteration functions for OCaml 
variant types

 ppx_variants_conv is a ppx rewriter that can be used to define first
 class values representing variant constructors, and additional
 routines to fold, iterate and map over all constructors of a variant
 type.

This package is a new dependency of sexplib310. It will be maintained
in the OCaml team.

Bug#949908: buster-pu: package libparse-win32registry-perl/1.0-2+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 21:39, Adrian Bunk wrote:

  * Add patch to fix Y2K20 problem.
(Closes: #948682)


Please go ahead.

Regards,

Adam

Bug#949898: buster-pu: package casacore-data-jplde/2007.07.05+ds.1-0+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 20:23, Adrian Bunk wrote:

  * Include tables up to 2040 in the upstream tarball. Closes: #949219


Please go ahead.

Regards,

Adam

Bug#949904: buster-pu: package libole-storage-lite-perl/0.19-2+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 21:04, Adrian Bunk wrote:

  * Backport upstream fix for years >= 2020 being misinterpreted.
(Closes: #948668)


Please go ahead.

Regards,

Adam

Bug#950007: firejail-profiles: firefox cannot read standard Debian docs folder /usr/share/doc

[Hans-Christoph Steiner]

Package: firejail-profiles
Version: 0.9.62-2~bpo10+1
Severity: normal

Dear Maintainer,

I regularly use offline docs, but a recent change to the firefox profile has 
blocked access to all the docs provided by Debian in /usr/share/doc:

File not found

Firefox can’t find the file at /usr/share/doc/.

Check the file name for capitalization or other typing errors.
Check to see if the file was moved, renamed or deleted.

Or for a specific example:
file:///usr/share/doc/python3.7/html/library/collections.html#collections.OrderedDict

File not found

Firefox can’t find the file at 
/usr/share/doc/python3.7/html/library/collections.html#collections.OrderedDict.

Check the file name for capitalization or other typing errors.
Check to see if the file was moved, renamed or deleted.


 ~ $ ls -ld /usr/share/doc
drwxr-xr-x 3396 root root 131072 Jän 27 18:09 /usr/share/doc
 ~ $ ls -ld /usr/share/doc/python3.7/html/library/collections.html 
-rw-r--r-- 1 root root 165855 Apr  3  2019 
/usr/share/doc/python3.7/html/library/collections.html



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

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Kernel taint flags: 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 firejail-profiles depends on:
ii  firejail  0.9.62-2~bpo10+1

firejail-profiles recommends no packages.

firejail-profiles suggests no packages.

-- Configuration Files:
/etc/firejail/firefox.profile changed:
include firefox.local
include globals.local
noblacklist ${HOME}/.cache/mozilla
noblacklist ${HOME}/.mozilla
mkdir ${HOME}/.cache/mozilla/firefox
mkdir ${HOME}/.mozilla
whitelist ${HOME}/.cache/mozilla/firefox
whitelist ${HOME}/.mozilla
whitelist /usr/share/mozilla
whitelist /usr/share/webext
include whitelist-usr-share-common.inc
include firefox-common.profile

/etc/firejail/transmission-daemon.profile changed:
quiet
include transmission-daemon.local
include globals.local
mkdir ${HOME}/.config/transmission-daemon
whitelist ${HOME}/.config/transmission-daemon
whitelist /var/lib/transmission
caps.keep ipc_lock,net_bind_service,setgid,setuid,sys_chroot
private-bin transmission-daemon
private-etc 
alternatives,ca-certificates,crypto-policies,nsswitch.conf,pki,resolv.conf,ssl
read-write /var/lib/transmission
writable-var-log
writable-run-user
include transmission-common.profile


-- no debconf information

Bug#950005: Seeing the same as well

[Christian Ehrhardt]

Hi,
I was experimenting with 9p last week and thought it was related to that.
But seeing your bug I realize I have seen the same issue:

ubuntu@dradis:~$ virsh start focal-t1 --console
Domain focal-t1 started
Connected to domain focal-t1
Escape character is ^]
Populating /vdevice methods
Populating /vdevice/vty@3000
Populating /vdevice/nvram@7100
Populating /pci@8002000
( 700 ) Program Exception [ 0 ]
R0 .. R7   R8 .. R15 R16 .. R23 R24 .. R31
0dbf0b14   0dc63030      8000
0e67eff0   0e47b010   0e7451bc   f003
0dc25e00   0dc63028      0006
0e7592e8   0fbd00c8   0e771373   0dc1bc00
      0dc63040   0dc20778
      0dbf4750   0003
      0dc20bb8   f001
      0dc20948   
CR / XER   LR / CTR  SRR0 / SRR1DAR / DSISR
8402   0dbf0b14      
2004      80081000   

Unless someone else here has an immediate idea IMHO this might be better
reported upstream. There are more PPC people and IBM itself reading the
report.
@Björn - would you mind doing so with a mail to [1]?

If you happen to do so updating this bug here with a link to the discussion
would be great.

[1]: https://lists.nongnu.org/mailman/listinfo/qemu-devel

P.S. similar old bugs with the same signature are [2][3] but those were due
to grub triggering an illegal instruction. I guess we can assume that we
run into an illegal instruction again here, but whyt/details I can't derive
out of the logs.

[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1400476
[3]: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1459706

-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

Bug#949906: buster-pu: package libtimedate-perl/2.3000-2+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 21:21, Adrian Bunk wrote:

  * Add patch from upstream pull request to fix Y2K20 test failure.
(Closes: #948680)


Please go ahead.

Regards,

Adam

Bug#949899: buster-pu: package libperl4-corelibs-perl/0.004-1+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 20:36, Adrian Bunk wrote:

  * Add t/timelocal.t fix for Y2K20 problem in t/timelocal.t.
(Closes: #948666)


Please go ahead.

Regards,

Adam

Bug#940477: stretch-pu: package tmpreaper/1.6.13+nmu1+deb9u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2019-09-16 10:29, Thijs Kinkhorst wrote:

tmpreaper will clean up PrivateTmp dirs of processes that systemd
started, leading to those services periodically crashing (and it's
usually hard to diagnose that tmpreaper was the culprit here).

This update adds those dirs to tmpreapers' whitelist.


Please go ahead; sorry for the delay.

Regards,

Adam

Bug#944228: stretch-pu: package phpmyadmin/4:4.6.6-4+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2019-11-12 01:24, Matthias Blümel wrote:

phpmyadmin 4.9.1+dfsg1-2 is now in unstable which fixes these issues


Thanks. Please go ahead.

Regards,

Adam

Bug#950002: ITP: ppx-custom-printf -- printf-style format-strings for user-defined string conversion

[Stéphane Glondu]

Package: wnpp
Severity: wishlist
Owner: Stéphane Glondu 

* Package name: ppx-custom-printf
  Version : 0.13.0
  Upstream Author : Jane Street Group, LLC
* URL : https://github.com/janestreet/ppx_custom_printf
* License : MIT
  Programming Lang: OCaml
  Description : printf-style format-strings for user-defined string 
conversion

 ppx_custom_printf is a ppx rewriter that allows the use of
 user-defined string conversion functions in format strings (that is,
 strings passed to printf, sprintf, etc.).
 .
 No new syntax is introduced. Instead a previously ill-typed use of
 the ! operator is re-purposed.

This package is a new dependency of sexplib310. Il will be maintained
in the OCaml team.

Bug#950001: Upgrade libxkbcommon to upstream 0.10.0

[news]

Package: src:libxkbcommon
Version: 0.9.1-1

Dear Maintainer,

The libxkbcommon has a new upstream release 0.10.0. It has several improvements 
and fixes, like the capability of utilizing per-user configuration, and the use 
of includes in the rule files.

Full changelog:

> libxkbcommon 0.10.0 - 2020-01-18
> ===
> 
> - (security) Fix quadratic complexity in the XKB file parser. See commit
>   message 7c42945e04a2107827a057245298dedc0475cc88 for details.
> 
> - Add $XDG_CONFIG_HOME/xkb to the default search path. If $XDG_CONFIG_HOME
>   is not set, $HOME/.config/xkb is used. If $HOME is not set, the path is not
>   added.
> 
>   The XDG path is looked up before the existing default search path 
> $HOME/.xkb.
> 
>   Contributed by Peter Hutterer <@who-t.net>.
> 
> - Add support for include statements in XKB rules files.
> 
>   This is a step towards making local XKB customizations more tenable and
>   convenient, without modifying system files.
> 
>   You can now include other rules files like this:
> 
>   ! include %S/evdev
> 
>   Two directives are supported, %H to $HOME and %S for the system-installed
>   rules directory (usually /usr/share/X11/xkb/rules).
> 
>   See commit message ca033a29d2ca910fd17b1ae287cb420205bdddc8 and
>   doc/rules-format.txt in the xkbcommon source code for more information.
> 
>   Contributed by Peter Hutterer <@who-t.net>.
> 
> - Downgrade "Symbol added to modifier map for multiple modifiers" log to a
>   warning.
> 
>   This error message was too annoying to be shown by default. When working on
>   keymaps, set `XKB_LOG_LEVEL=debug XKB_LOG_VERBOSITY=10` to see all possible
>   messages.
> 
> - Support building on Windows using the meson MSVC backend.
> 
>   Contributed by Adrian Perez de Castro <@igalia.com>.
> 
> - Fix bug where the merge mode only applied to the first vmod in a
>   `virtual_modifiers` statement. Given
> 
>   augment virtual_modifiers NumLock,Alt,LevelThree
> 
>   Previously it was incorrectly treated as
> 
>   augment virtual_modifiers NumLock;
>   virtual_modifiers Alt;
>   virtual_modifiers LevelThree;
> 
>   Now it is treated as
> 
>   augment virtual_modifiers NumLock;
>   augment virtual_modifiers Alt;
>   augment virtual_modifiers LevelThree;
> 
> - Reject interpret modifier predicate with more than one value. Given
> 
>   interpret ISO_Level3_Shift+AnyOf(all,extraneous) { ... };
> 
>   Previously, extraneous (and further) was ignored. Now it's rejected.
> 
> - Correctly handle capitalization of the ssharp keysym.
> 
> - Speed up and improve the internal `xkeyboard-config` tool. This tool
>   compiles all layout/variant combinations in the xkeyboard-config dataset
>   and reports any issues it finds.
> 
>   Contributed by Peter Hutterer <@who-t.net>.
> 
> - Speed up "atoms" (string interning). This code goes back at least to X11R1
>   (released 1987).

-- Iiro Laiho

Bug#950006: gvfsd continuously tries to create /var/cache/samba

[Kevin Price]

Package: gvfs-daemons
Version: 1.38.1-5
Severity: normal

According to my syslog, gvfsd keeps trying to mkdir /var/cache/samba, causing
"Permission denied" errors. This seems to be a continuation of #831329, which
should have been reassigned to gvfs-daemons.



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

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

Versions of packages gvfs-daemons depends on:
ii  gvfs-common 1.38.1-5
ii  gvfs-libs   1.38.1-5
ii  libbluray2  1:1.1.0-1
ii  libc6   2.28-10
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgudev-1.0-0  232-2
ii  libsecret-1-0   0.18.7-1
ii  libsystemd0 241-7~deb10u2
ii  libudisks2-02.8.1-4
ii  lsof4.91+dfsg-1
ii  udisks2 2.8.1-4
ii  x11-utils   7.7+4

Versions of packages gvfs-daemons recommends:
ii  dbus  1.12.16-1
ii  gvfs  1.38.1-5

Versions of packages gvfs-daemons suggests:
ii  gvfs-backends  1.38.1-5

-- no debconf information

Bug#949895: buster-pu: package boost1.67/1.67.0-13+deb10u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On 2020-01-26 19:38, Adrian Bunk wrote:
  * Patch undefined behaviour leading to crashing libboost-numpy 
(closes:

#945987).


Please go ahead.

Regards,

Adam

Bug#949994: [debian-mysql] Bug#949994: mysql-5.7: Security fixes from the January 2020 CPU

[Lars Tangvald]

Thanks. I'm waiting for maintainer access to the source package, and I 
should be able to finally get all these closed.


--
Lars

On 28.01.2020 08:20, Salvatore Bonaccorso wrote:

Source: mysql-5.7
Version: 5.7.26-1
Severity: grave
Tags: security upstream
Justification: user security hole

Hi

See
https://www.oracle.com/security-alerts/cpujan2020.html#AppendixMSQL
for a list of CVEs affecting src:mysql-5.7.

Regards,
Salvatore

___
pkg-mysql-maint mailing list
pkg-mysql-ma...@alioth-lists.debian.net
https://urldefense.proofpoint.com/v2/url?u=https-3A__alioth-2Dlists.debian.net_cgi-2Dbin_mailman_listinfo_pkg-2Dmysql-2Dmaint=DwIGaQ=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE=M-8dedO8w3Vlx9Nb3v_HN_eQTPKU36yJj5mmQmreYMQ=alqB5idfnDxLLAZZRzTyPF-_phj0QvZhm6Pp3-PiXx4=GnTMOde4S5uaLlMk05fv3wrC7xQppp--bnFjJiJ3vW0=

Bug#950088: node-rollup-plugin-string: missing build dependency on node-rollup-plugin-buble

[Adrian Bunk]

Source: node-rollup-plugin-string
Version: 3.0.0-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-rollup-plugin-string.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-rollup-plugin-string-3.0.0'
rollup -c
[!] Error: Cannot find module 'rollup-plugin-buble'
Error: Cannot find module 'rollup-plugin-buble'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
at Function.Module._load (internal/modules/cjs/loader.js:562:25)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object. 
(/build/1st/node-rollup-plugin-string-3.0.0/rollup.config.js:5:29)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.require.extensions..js 
(/usr/share/nodejs/rollup/bin/src/run/loadConfigFile.js:39:24)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)

make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1

Bug#950089: node-chrome-trace-event FTBFS: error TS2300: Duplicate identifier 'IteratorResult'

[Adrian Bunk]

Source: node-chrome-trace-event
Version: 1.0.0-1
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-chrome-trace-event.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-chrome-trace-event-1.0.0'
tsc --typeRoots debian/node_modules/@types --baseUrl debian/node_modules
debian/node_modules/@types/node/index.d.ts(78,11): error TS2300: Duplicate 
identifier 'IteratorResult'.
../../../usr/share/nodejs/typescript/lib/lib.es2015.iterable.d.ts(41,6): error 
TS2300: Duplicate identifier 'IteratorResult'.
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2

Bug#950090: gcc-mingw-w64: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Source: gcc-mingw-w64
Version: 22~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gcc-mingw-w64-x86-64 gfortran-mingw-w64-x86-64 
g++-mingw-w64-x86-64 gobjc-mingw-w64-x86-64 gobjc++-mingw-w64-x86-64 
gnat-mingw-w64-x86-64
Control: affects -1 + gcc-mingw-w64-i686 gfortran-mingw-w64-i686 
g++-mingw-w64-i686 gobjc-mingw-w64-i686 gobjc++-mingw-w64-i686 
gnat-mingw-w64-i686
Control: found -1 gcc-mingw-w64/9.2.1-21+22~exp2

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  sid -> experimental

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m37.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/g++-mingw-w64-i686/changelog.Debian.gz (g++-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base)
/usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/g++-mingw-w64-i686/changelog.gz (g++-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base)
/usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/g++-mingw-w64-i686/copyright (g++-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base)
/usr/share/doc/g++-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-i686/changelog.Debian.gz (gcc-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base)
/usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-i686/changelog.gz (gcc-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base)
/usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-i686/copyright (gcc-mingw-w64-i686) != 
/usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base)
/usr/share/doc/gcc-mingw-w64-i686 -> gcc-mingw-w64-base

0m36.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/gcc-mingw-w64-x86-64/changelog.Debian.gz 
(gcc-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz 
(gcc-mingw-w64-base)
/usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-x86-64/changelog.gz (gcc-mingw-w64-x86-64) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.gz (gcc-mingw-w64-base)
/usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gcc-mingw-w64-x86-64/copyright (gcc-mingw-w64-x86-64) != 
/usr/share/doc/gcc-mingw-w64-base/copyright (gcc-mingw-w64-base)
/usr/share/doc/gcc-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gfortran-mingw-w64-x86-64/changelog.Debian.gz 
(gfortran-mingw-w64-x86-64) != 
/usr/share/doc/gcc-mingw-w64-base/changelog.Debian.gz (gcc-mingw-w64-base)
/usr/share/doc/gfortran-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gfortran-mingw-w64-x86-64/changelog.gz 
(gfortran-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/changelog.gz 
(gcc-mingw-w64-base)
/usr/share/doc/gfortran-mingw-w64-x86-64 -> gcc-mingw-w64-base
  /usr/share/doc/gfortran-mingw-w64-x86-64/copyright 
(gfortran-mingw-w64-x86-64) != /usr/share/doc/gcc-mingw-w64-base/copyright 
(gcc-mingw-w64-base)
/usr/share/doc/gfortran-mingw-w64-x86-64 -> gcc-mingw-w64-base

This seems to affect the full language x arch matrix.

Note that dpkg-maintscript-helper symlink_to_dir etc. don't work
reliably if the architecture changes between any and all.


cheers,

Andreas


g++-mingw-w64-i686_9.2.1-21+22~exp2.log.gz
Description: application/gzip

Bug#947847: please install systemd-sysusers using update-alternatives

[Philipp Kern]

On 1/28/2020 1:33 PM, Thomas Goirand wrote:
>> It'd need to be a script that the systemd maintainers feel reasonably
>> confident will always run systemd's implementation when systemd is
>> running, to avoid the mixed implementations issue.
> 
> Not at all. Systemd maintainers have no say if someone wishes to
> implement things in another way, the same way there's gawk and mawk,
> implementing the same thing. If we don't allow such things, then really,
> Debian is doomed.

The interface in question here is "awk". So if the interface would be a
hypothetical "update-sysusers", then this could be shared with
alternatives. I completely understand the view of the systemd
maintainers that "systemd-sysusers" as a binary should be provided by
their package rather than an alternative.

>> Strikes me as there is a possible solution, though: have opensysusers
>> dpkg-divert it and put a shell script in its place that checks which
>> init system is running, and exec's the right sysusers based on that.
> 
> This is exactly what should be avoided. It's perfectly fine to try to
> use opensysusers with systemd if one wants. In fact, that's exactly the
> best way we could do to be able to test it. Also, dpkg-divert is really
> ugly, and something you use as the last resort, when all other options
> have been exhausted.

If the problem here is that everything embeds a call to systemd-sysusers
directly and you want to provide a different intermediate interface
eventually then diverting it as a workaround in the meantime seems sound
to me, no?

So far I see you present a single option rather than trying to negotiate
within the option space. Good escalations are not "Moreover, I don't see
why /usr/bin/systemd-sysusers would be any different from let's say
/usr/bin/awk." but trying to present the two opposing viewpoints and
potential solutions to them.

Kind regards
Philipp Kern

Bug#950092: node-base64url FTBFS: error TS2688: Cannot find type definition file for 'node'

[Adrian Bunk]

Source: node-base64url
Version: 3.0.1-2
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-base64url.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-base64url-3.0.1'
pandoc --from gfm-raw_html --to html --standalone --output readme.html readme.md
[WARNING] This document format requires a nonempty  element.
  Please specify either 'title' or 'pagetitle' in the metadata,
  e.g. by using --metadata pagetitle="..." on the command line.
  Falling back to 'readme'
pandoc --from gfm-raw_html --to plain --output readme.txt readme.md
tsc
error TS2688: Cannot find type definition file for 'node'.
src/base64url.ts(35,22): error TS4067: Parameter 'input' of call signature from 
exported interface has or is using private name 'Buffer'.
src/base64url.ts(36,28): error TS4075: Parameter 'input' of method from 
exported interface has or is using private name 'Buffer'.
src/base64url.ts(38,34): error TS4075: Parameter 'base64url' of method from 
exported interface has or is using private name 'Buffer'.
src/base64url.ts(40,34): error TS4057: Return type of method from exported 
interface has or is using private name 'Buffer'.
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1

Bug#950093: libblasr-dev: missing Breaks+Replaces: libblasr (<< 5.3.3)

[Andreas Beckmann]

Package: libblasr-dev
Version: 5.3.3+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../2-libblasr-dev_5.3.3+dfsg-3_amd64.deb ...
  Unpacking libblasr-dev (5.3.3+dfsg-3) over (5.3.1+dfsg-2.1+b1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-09Rr1t/2-libblasr-dev_5.3.3+dfsg-3_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libblasr.so', which is also 
in package libblasr:amd64 5.3.1+dfsg-2.1+b1


cheers,

Andreas


libblasr-dev_5.3.3+dfsg-3.log.gz
Description: application/gzip

Bug#950094: ipywidgets FTBFS with node-semver 7.1.1-2

[Adrian Bunk]

Source: ipywidgets
Version: 6.0.0-6
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ipywidgets.html

...
rm -rf "fakewebpack/widgetsnbextension" && mkdir -p 
"fakewebpack/widgetsnbextension" && ./fakewebpack-generate.py 
fakewebpack-meta/widgetsnbextension.files 
fakewebpack-meta/widgetsnbextension.modules 
fakewebpack-unpacked/widgetsnbextension/ True > 
"fakewebpack/widgetsnbextension/extension.js" && touch 
"fakewebpack/widgetsnbextension.stamp"
fs.js:114
throw err;
^

Error: ENOENT: no such file or directory, open './node_modules/semver/semver.js'
at Object.openSync (fs.js:443:3)
at Object.readFileSync (fs.js:343:35)
at Object. 
(/build/1st/ipywidgets-6.0.0/debian/fakewebpack-postprocess.js:233:19)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
at startup (internal/bootstrap/node.js:283:19)
module 00: nodejs ../../fakewebpack-postprocess.js ./src/extension.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 01: nodejs ../../fakewebpack-postprocess.js ./src/manager.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 02: nodejs ../../fakewebpack-postprocess.js 
./node_modules/underscore/underscore.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 03: nodejs ../../fakewebpack-postprocess.js 
./node_modules/backbone/backbone.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 04: nodejs ../../fakewebpack-postprocess.js 
./node_modules/jquery/dist/jquery.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 05: nodejs ../../fakewebpack-postprocess.js 
./node_modules/jupyter-js-widgets/lib/index.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 06: nodejs ../../fakewebpack-postprocess.js 
./node_modules/jupyter-js-widgets/lib/manager-base.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 07: nodejs ../../fakewebpack-postprocess.js 
./node_modules/jupyter-js-widgets/lib/utils.js 
../../fakewebpack-meta/widgetsnbextension.modules
module 08: nodejs ../../fakewebpack-postprocess.js 
./node_modules/semver/semver.js 
../../fakewebpack-meta/widgetsnbextension.modules
Traceback (most recent call last):
  File "./fakewebpack-generate.py", line 97, in 
sys.exit(main(*sys.argv[1:]))
  File "./fakewebpack-generate.py", line 66, in main
cwd=srcdir).decode("utf-8")
  File "/usr/lib/python3.7/subprocess.py", line 411, in check_output
**kwargs).stdout
  File "/usr/lib/python3.7/subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['nodejs', 
'../../fakewebpack-postprocess.js', './node_modules/semver/semver.js', 
'../../fakewebpack-meta/widgetsnbextension.modules']' returned non-zero exit 
status 1.
make[2]: *** [fakewebpack.mk:77: fakewebpack/widgetsnbextension.stamp] Error 1

Bug#949992: Does not take subprocess down when killed

[martin f krafft]

tags 949992 +patch
kthxbye

Attached is a patch. Warning, I'm not a Perl-coder. Seems to work 
though.


--
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems
 
"i never travel without my diary. one should always have something

 sensational to read on the train."
  -- oscar wilde
--- /tmp/run-mailcap	2020-01-29 09:12:51.002973844 +1300
+++ /usr/bin/run-mailcap	2020-01-29 10:37:56.385391104 +1300
@@ -12,6 +12,7 @@
 use Encode qw(decode);
 use I18N::Langinfo qw(langinfo CODESET);
 use File::Spec;
+use POSIX ":sys_wait_h";
 
 $debug=($ENV{RUN_MAILCAP_DEBUG} || 0);
 $norun=0;
@@ -25,8 +26,17 @@
 $quotedsemi=chr(255);
 $quotedprct=chr(254);
 $retcode=0;
+$wait_on_child_pid=0;
 
+sub signal_handler {
+my($sig) = @_;
+print STDERR " - caught signal $sig, cleaning up...\n" if $debug;
+kill $sig, $wait_on_child_pid;
+die "Terminated on signal $sig";
+}
 
+$SIG{INT} = \_handler;
+$SIG{TERM} = \_handler;
 
 sub Usage {
 my($error) = @_;
@@ -542,22 +552,28 @@
 	print $comm,"\n";
 	$res = 0;
 	} else {
-	$res = system $comm;
-	if ($res != 0) {
-		if (!($res & 0xFF)) {
-print STDERR "Warning: program returned non-zero exit code \#$res\n";
-$retcode = $res >> 8;
-		} elsif ($res == -1) {
-		print STDERR "Error: program failed to execute: $!\n";
-		$retcode = -1;
-		} else {
+	my $pid = fork;
+	die "Unable to fork" unless defined $pid;
+	if ($pid == 0) {
+		exec $comm;
+	} else {
+		$wait_on_child_pid=$pid; # so the signal handler knows what to kill.
+		waitpid($pid, 0);
+
+		if ($? & 0xFF) {
 		my $signal = $? & 0x7F;
 		my $core = ($? & 0x80) ? ' (core dumped)' : '';
 		print STDERR "Warning: program died on signal ${signal}${core}\n";
 		$retcode = -1;
+		} elsif ($? == -1) {
+		print STDERR "Error: program failed to execute: $!\n";
+		$retcode = -1;
+		} elsif ($? > 0) {
+		print STDERR "Warning: program returned non-zero exit code \#$?\n";
+		$retcode = $?;
 		}
-}
-}
+	}
+	}
 $done=1;
 unlink $tmpfile if $tmpfile;
 unlink $tmplink if $tmplink;


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#946470: libreoffice-l10n-de: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Followup-For: Bug #946470
Control: found -1 1:6.4.0~rc3-1
Control: affects -1 + libreoffice-l10n-kmr

Hi Rene,

there are still a few left when upgrading from testing (1:6.3.4-2) to
sid (1:6.4.0~rc3-1):

0m37.5s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libreoffice-l10n-in/changelog.Debian.gz (libreoffice-l10n-in) 
!= /usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common)
/usr/share/doc/libreoffice-l10n-in -> libreoffice-common
  /usr/share/doc/libreoffice-l10n-in/copyright (libreoffice-l10n-in) != 
/usr/share/doc/libreoffice-common/copyright (libreoffice-common)
/usr/share/doc/libreoffice-l10n-in -> libreoffice-common

0m35.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libreoffice-l10n-za/changelog.Debian.gz (libreoffice-l10n-za) 
!= /usr/share/doc/libreoffice-common/changelog.Debian.gz (libreoffice-common)
/usr/share/doc/libreoffice-l10n-za -> libreoffice-common
  /usr/share/doc/libreoffice-l10n-za/copyright (libreoffice-l10n-za) != 
/usr/share/doc/libreoffice-common/copyright (libreoffice-common)
/usr/share/doc/libreoffice-l10n-za -> libreoffice-common

0m33.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libreoffice-l10n-kmr/changelog.Debian.gz 
(libreoffice-l10n-kmr) != /usr/share/doc/libreoffice-common/changelog.Debian.gz 
(libreoffice-common)
/usr/share/doc/libreoffice-l10n-kmr -> libreoffice-common
  /usr/share/doc/libreoffice-l10n-kmr/copyright (libreoffice-l10n-kmr) != 
/usr/share/doc/libreoffice-common/copyright (libreoffice-common)
/usr/share/doc/libreoffice-l10n-kmr -> libreoffice-common


Andreas

Bug#949959: debcargo.toml should make it possible to declare additional dependencies for generated autopkgtests

[Daniel Kahn Gillmor]

Control: tag 949959 + patch

On Mon 2020-01-27 11:55:28 -0500, Daniel Kahn Gillmor wrote:
> So it would be good to be able to indicate in debcargo.toml some
> additional autopkgtest dependencies.
>
> Simplest might be to add a dependency for *all* generated autopkgtests,
> but i can imagine there are some subtler requirements which will need to
> be for specific autopkgtests in the future.

Wolfgang created this patch (on the dev/debian_949959 branch in salsa)
to implement this mechanism.

It looks reasonable to me, and it compiles fine.  I'm in the process of
testing it now.

   --dkg

From 9a250f348f31294ccdc11eb629a2b53341ef6814 Mon Sep 17 00:00:00 2001
From: Wolfgang Silbermayr 
Date: Tue, 28 Jan 2020 12:50:59 +0100
Subject: [PATCH] Implement extra_test_deps config option at top level

Add an extra_test_deps to top level of debcargo.toml where autopkgtest
dependencies can be added. A first simple implementation of this feature
for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949959

Might be extended later by adding the same field to the [packages.lib*]
entries if dependencies are required by some tests only, but must not be
present on others.
---
 debcargo.toml.example |  3 +++
 src/config.rs |  2 ++
 src/debian/mod.rs | 10 --
 3 files changed, 13 insertions(+), 2 deletions(-)

diff --git a/debcargo.toml.example b/debcargo.toml.example
index b463f1d..74658ab 100644
--- a/debcargo.toml.example
+++ b/debcargo.toml.example
@@ -45,6 +45,9 @@
 # exceptional cases where the method gives a false-positive, add them here.
 #whitelist = ["libgit2/**"]
 
+# Additional dependencies for the autopkgtests. Gets added to all tests.
+#extra_test_deps = ["llvm", "clang"]
+
 # Whether to allow prerelease deps, by rewriting these to the released version.
 # This should only be enabled for certain crates if really necessary, and first
 # you should check that they can actually build when this is enabled.
diff --git a/src/config.rs b/src/config.rs
index d0d8583..43a9a89 100644
--- a/src/config.rs
+++ b/src/config.rs
@@ -18,6 +18,7 @@ pub struct Config {
 pub overlay: Option,
 pub excludes: Option>,
 pub whitelist: Option>,
+pub extra_test_deps: Option>,
 pub allow_prerelease_deps: bool,
 pub summary: String,
 pub description: String,
@@ -61,6 +62,7 @@ impl Default for Config {
 overlay: None,
 excludes: None,
 whitelist: None,
+extra_test_deps: None,
 allow_prerelease_deps: false,
 summary: "".to_string(),
 description: "".to_string(),
diff --git a/src/debian/mod.rs b/src/debian/mod.rs
index 7969ee8..a06b522 100644
--- a/src/debian/mod.rs
+++ b/src/debian/mod.rs
@@ -503,6 +503,12 @@ pub fn prepare_debian_folder(
 };
 
 if lib {
+let mut test_depends = dev_depends.clone();
+if let Some(ref extra) = config.extra_test_deps {
+test_depends.extend(extra.clone());
+test_depends.sort();
+test_depends.dedup();
+}
 // debian/tests/control
 let mut testctl = io::BufWriter::new(file("tests/control")?);
 write!(
@@ -513,7 +519,7 @@ pub fn prepare_debian_folder(
 _name,
 _version,
 vec!["--all-features"],
-_depends,
+_depends,
 if all_features_test_broken {
 vec!["flaky"]
 } else {
@@ -576,7 +582,7 @@ pub fn prepare_debian_folder(
 } else {
 vec!["--features", feature]
 },
-_depends,
+_depends,
 if test_is_broken {
 vec!["flaky"]
 } else {
-- 
2.24.1



signature.asc
Description: PGP signature

Bug#950099: fonts-inter FTBFS: KeyError: "glyph 'asterisk' already exists"

[Adrian Bunk]

Source: fonts-inter
Version: 3.11-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-inter.html

...
  debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/fonts-inter-3.11'
fontmake -i -o otf -g src/Inter.glyphs
INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs 
source
INFO:glyphsLib.classes:Parsing "src/Inter.glyphs" file into 
Traceback (most recent call last):
  File "/usr/bin/fontmake", line 11, in 
load_entry_point('fontmake==2.0.7', 'console_scripts', 'fontmake')()
  File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 425, in main
project.run_from_glyphs(glyphs_path, **args)
  File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 670, in 
run_from_glyphs
write_skipexportglyphs=write_skipexportglyphs,
  File "/usr/lib/python3/dist-packages/fontTools/misc/loggingTools.py", line 
367, in wrapper
return func(*args, **kwds)
  File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 156, in 
build_master_ufos
ufo_module=ufoLib2,
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/__init__.py", line 
111, in to_designspace
return builder.designspace
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/builders.py", line 
260, in designspace
list(self.masters)  # Make sure that the UFOs are built
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/builders.py", line 
222, in masters
ufo_glyph = ufo_layer.newGlyph(glyph.name)
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/layer.py", line 120, in 
newGlyph
raise KeyError("glyph %r already exists" % name)
KeyError: "glyph 'asterisk' already exists"
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1

Bug#949890: buster-pu: packages tbsync, dav4tbsync and eas4tbsync

[Adam D. Barratt]

Control: tags -1 + moreinfo
Control: clone -1 -2 -3
Control: retitle -1 buster-pu: tbsync
Control: retitle -2 buster-pu: dav4tbsync
Control: retitle -3 buster-pu: eas4tbsync

On Sun, 2020-01-26 at 19:45 +0100, Mechtilde Stehmann wrote:
> I want to upload tbsync, dav4tbsync and eas4tbsync to be compatible
> with thunderbird 68.x in stable

In that case, there should be three separate p-u bugs. There are a
variety of reasons why we might end up releasing some combination (but
not all) of the packages in a given point release and we need to be
able to track the status of each individually.

> These packages are needed to be able to connect to a Calendar at an
> Exchange Server. The older ersion s - now released in buster - don't
> work proper.

Depending on the size, could we have - to the relevant of the cloned
bug set - source debdiffs, or at least binary debdiffs between the
current stable packages and the proposed uploads?

Regards,

Adam

Bug#950108: r-cran-dt: unhandled symlink to directory conversion: /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables{,-extensions}

[Andreas Beckmann]

Package: r-cran-dt
Version: 0.11+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

2m27.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/AutoFill 
(r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/AutoFill 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons 
(r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/Buttons 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/css 
(r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/Buttons/css 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  /usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js 
(r-cran-dt) != /usr/share/javascript/jquery-datatables-extensions/Buttons/js 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.bootstrap.js
 (r-cran-dt) != 
/usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.js
 (libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.bootstrap.min.js
 (r-cran-dt) != 
/usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.bootstrap.min.js
 (libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.colVis.js
 (r-cran-dt) != 
/usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.js 
(libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.colVis.min.js
 (r-cran-dt) != 
/usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.colVis.min.js
 (libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions/Buttons/js/buttons.foundation.js
 (r-cran-dt) != 
/usr/share/javascript/jquery-datatables-extensions/Buttons/js/buttons.foundation.js
 (libjs-jquery-datatables-extensions)
/usr/lib/R/site-library/DT/htmlwidgets/lib/datatables-extensions -> 
../../../../../../share/javascript/jquery-datatables-extensions
  

Bug#950018: buster-pu: package php-horde-text-filter/2.3.5-3

[Adam D. Barratt]

Control: tags -1 + confirmed

On Tue, 2020-01-28 at 12:21 +0100, IOhannes m zmoelnig wrote:
> The 'php-horde-text-filter' contains a few regular expressions that
> are incompatible with the libpcre2 as shipped in Debian/buster.

That's quite a long way of saying "wrong". :-) I wouldn't have expected
them to have ever worked.

I'm not convinced it's worth the orphaning change in stable, as it's
expected that maintainer information will become outdated after
release, but either way please go ahead.

Regards,

Adam

Bug#944485: mmdebstrap: please implement the creation of QEMU/KVM images for autopkgtest-virt-qemu

[Francesco Poli]

On Mon, 27 Jan 2020 23:44:55 +0100 Johannes Schauer wrote:

[...]
> this looks as if the error comes from
> /usr/share/autopkgtest/setup-commands/setup-testbed. To figure out what goes
> wrong, maybe try running setup-testbed with sh -x like so:
> 
> --customize-hook='sh -x /usr/share/autopkgtest/setup-commands/setup-testbed 
> "$1"'
> 
> Your command works fine on my system, so this must be something specific to
> your setup.
> 
> Thanks!

Thanks to you for your super-prompt reply!   :-)

  $ cd Downloads/
  $ TMPDIR='./'
  $ export TMPDIR
  $ mmdebstrap --variant=important --include=linux-image-amd64 \
  >   --customize-hook='chroot "$1" passwd --delete root' \
  >   --customize-hook='chroot "$1" useradd --home-dir /home/user --create-home 
user' \
  >   --customize-hook='chroot "$1" passwd --delete user' \
  >   --customize-hook='echo host > "$1/etc/hostname"' \
  >   --customize-hook='echo "127.0.0.1 localhost host" > "$1/etc/hosts"' \
  >   --customize-hook='sh -x 
/usr/share/autopkgtest/setup-commands/setup-testbed "$1"' \
  > "sid" debian-unstable.tar
  I: automatically chosen mode: fakechroot
  [...]
  I: running --customize-hook in shell: sh -c 'sh -x 
/usr/share/autopkgtest/setup-commands/setup-testbed "$1"' exec 
${HOME}/Downloads/mmdebstrap.pxni4vAjou
  + set -eu
  + umask 0022
  + export DEBIAN_FRONTEND=noninteractive
  + [ ${HOME}/Downloads/mmdebstrap.pxni4vAjou = --help ]
  + root=${HOME}/Downloads/mmdebstrap.pxni4vAjou
  + [ ${HOME}/Downloads/mmdebstrap.pxni4vAjou != / ]
  + cat
  + chmod 755 ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/init.d/autopkgtest
  + chroot ${HOME}/Downloads/mmdebstrap.pxni4vAjou update-rc.d autopkgtest 
defaults
  + [ -d ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/systemd/system ]
  + cat
  + mkdir -p 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/systemd/system/multi-user.target.wants
  + ln -sf ../autopkgtest.service 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/systemd/system/multi-user.target.wants/autopkgtest.service
  + [ -e ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/init/tty2.conf -a ! -e 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/init/ttyS0.conf ]
  + chroot ${HOME}/Downloads/mmdebstrap.pxni4vAjou dpkg --print-architecture
  + ARCH=amd64
  + [ ! -e 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/default/grub.d/90-autopkgtest.cfg ]
  + chroot ${HOME}/Downloads/mmdebstrap.pxni4vAjou which update-grub
  + [ -e ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/os-release ]
  + . ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/os-release
  + PRETTY_NAME=Debian GNU/Linux bullseye/sid
  + NAME=Debian GNU/Linux
  + ID=debian
  + HOME_URL=https://www.debian.org/
  + SUPPORT_URL=https://www.debian.org/support
  + BUG_REPORT_URL=https://bugs.debian.org/
  + echo debian
  + DISTRO_ID=debian
  + [ -z  ]
  + awk /^deb .*debian/ { sub(/\[.*\]/, "", $0); print $2; exit } 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/apt/sources.list
  + MIRROR=http://deb.debian.org/debian
  + [ -z  ]
  + awk /^deb .*debian/ { sub(/\[.*\]/, "", $0); print $3; exit } 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/apt/sources.list
  + RELEASE=sid
  + [ -n  ]
  + [ -n  ]
  + [ -n  ]
  + echo /usr/share/autopkgtest/setup-commands/setup-testbed: Attempting to set 
up Debian/Ubuntu apt sources automatically
  /usr/share/autopkgtest/setup-commands/setup-testbed: Attempting to set up 
Debian/Ubuntu apt sources automatically
  + [ -z sid ]
  + [ -z http://deb.debian.org/debian ]
  + [ http://deb.debian.org/debian != http://deb.debian.org/debian ]
  + echo /usr/share/autopkgtest/setup-commands/setup-testbed: Distribution 
assumed to resemble Debian
  /usr/share/autopkgtest/setup-commands/setup-testbed: Distribution assumed to 
resemble Debian
  + cat
  + [ -e ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/cloud/cloud.cfg ]
  + [ -z  ]
  + ls ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/systemd/network/*.network
  + ls ${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/netplan/*.yaml
  + grep -q source.*interfaces.d 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/network/interfaces
  + IFACE=
  + [ ${HOME}/Downloads/mmdebstrap.pxni4vAjou = / ]
  + IFACE=eth0
  + [ -e 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/udev/rules.d/80-net-setup-link.rules
 ]
  + ln -s /dev/null 
${HOME}/Downloads/mmdebstrap.pxni4vAjou/etc/udev/rules.d/80-net-setup-link.rules
  + chroot ${HOME}/Downloads/mmdebstrap.pxni4vAjou update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-3-amd64
  W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module 
r8169
  [...]
  W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module 
r8169
  cp: failed to access './/mkinitramfs_v8SvPb/lib/systemd/network/': No such 
file or directory
  E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-3-amd64 with 1.
  E: run_chroot failed: E: command failed: sh -x 
/usr/share/autopkgtest/setup-commands/setup-testbed "$1"
  I: main() received signal PIPE: waiting 

Bug#945578: buster-pu: package libapache2-mod-auth-openidc/2.3.10.2-1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Wed, 2019-11-27 at 11:18 +0100, Moritz Schlarb wrote:
> Fixes CVE-2019-14857 (Open redirect in logout url when using URLs
> with backslashes) by improving validation of the post-logout URL
> parameter (backported from upstream, see 
> https://salsa.debian.org/debian/libapache2-mod-
> auth-openidc/commit/17e31b94a71ef02d1417bee6b0ef7b7379b40375)
> 

Please go ahead; sorry for the delay.

Regards,

Adam

Bug#943889: buster-pu: package hbci4java/3.0.22+dfsg-1 hibiscus/2.8.18+dfsg-2

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Thu, 2019-10-31 at 14:00 +0100, Jochen Sprickerhof wrote:
> I would like to integrate new upstream versions of hbci4java and
> hibiscus into Debian 10 (buster). Hibiscus is a electronic banking
> software and hbci4java the underlying library. The update is
> necessary because of the new EU directive on payment services (PSD2)
> [1], leading to changes in the interfaces of most European banks and
> thus breaking Hibiscus for most users.
> 
> Due to the new upstream versions, the diff is quiet big (~1MB) so I
> only include links to the diff [2, 3] here. I can send the full diff
> as well, if you prefer.

They are quite large, particularly the hbci4java diff. :-( I guess it's
unlikely that such a large change would be needed again during buster's
lifetime?

Regards,

Adam

Bug#950112: gplaycli: 502 Bad Gateway, does not work at all

[Thorsten Glaser]

Package: gplaycli
Version: 3.26+dfsg-1
Severity: grave
Justification: renders package unusable

After installation, gplaycli --help works (but please do add
a manual page), but nothing else:

$ gplaycli -s musescore
cache file does not exists or is corrupted
Unknown error: 
502 Bad Gateway

502 Bad Gateway
nginx/1.14.2


$ gplaycli -pvd com.musescore.playerlite
[INFO] GPlayCli version 3.26 [Python3.7.6] 
[INFO] Configuration file is /etc/gplaycli/gplaycli.conf
[INFO] Device is bacon
[ERROR] cache file does not exists or is corrupted
[INFO] Retrieving token ...
[INFO] Token URL is https://matlink.fr/token/email/gsfid/bacon
[ERROR] Unknown error: 
502 Bad Gateway

502 Bad Gateway
nginx/1.14.2




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

Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages gplaycli depends on:
ii  python3   3.7.5-3
ii  python3-crypto2.6.1-13
ii  python3-gpapi 0.4.4-1
ii  python3-pyaxmlparser  0.3.24-1

Versions of packages gplaycli recommends:
pn  dummydroid
pn  fdroidserver  

gplaycli suggests no packages.

-- no debconf information

Bug#950113: warn about debhelper-compat in Build-Depends-Indep

[Jelmer Vernooij]

Package: lintian
Version: 2.47.0
Severity: wishlist

It would be great if lintian could warn about debhelper-compat usage in
Build-Depends-Indep rather than Build-Depends.

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

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

Versions of packages lintian depends on:
ii  binutils 2.33.90.20200122-2
ii  bzip21.0.8-2
ii  diffstat 1.63-1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.38-4
ii  gettext  0.19.8.1-10
ii  gpg  2.2.19-1
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b2
ii  libarchive-zip-perl  1.67-1
ii  libberkeleydb-perl   0.62-1+b1
ii  libcapture-tiny-perl 0.48-1
ii  libcgi-pm-perl   4.45-1
ii  libclass-accessor-perl   0.51-1
ii  libclass-xsaccessor-perl 1.19-3+b3
ii  libclone-perl0.43-2
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libfont-ttf-perl 1.06-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.75-1
ii  libipc-run-perl  20180523.0-2
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmldbm-perl2.05-2
ii  libmoo-perl  2.003006-1
ii  libmoox-aliases-perl 0.001006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.108-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3100-1
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.008001-2
ii  liburi-perl  1.76-1
ii  libxml-libxml-perl   2.0134+dfsg-1+b1
ii  libyaml-libyaml-perl 0.80+repack-2+b1
ii  man-db   2.9.0-2
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-9
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b6

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libhtml-parser-perl3.72-3+b4
ii  libtext-template-perl  1.58-1

-- no debconf information

Bug#944485: mmdebstrap: please implement the creation of QEMU/KVM images for autopkgtest-virt-qemu

[Johannes Schauer]

Hi,

Quoting Francesco Poli (2020-01-28 23:41:38)
>   + chroot ${HOME}/Downloads/mmdebstrap.pxni4vAjou update-initramfs -u
>   update-initramfs: Generating /boot/initrd.img-5.4.0-3-amd64
>   W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module 
> r8169
>   [...]
>   W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module 
> r8169
>   cp: failed to access './/mkinitramfs_v8SvPb/lib/systemd/network/': No such 
> file or directory
>   E: /usr/share/initramfs-tools/hooks/udev failed with return 1.
>   update-initramfs: failed for /boot/initrd.img-5.4.0-3-amd64 with 1.
>   E: run_chroot failed: E: command failed: sh -x 
> /usr/share/autopkgtest/setup-commands/setup-testbed "$1"
>   I: main() received signal PIPE: waiting for setup...
>   W: listening on child socket failed: E: received eof on socket
>   
>   I: removing tempdir ${HOME}/Downloads/mmdebstrap.pxni4vAjou...
> 
> 
> As you can see, a "cp" fails to access file 
> './/mkinitramfs_v8SvPb/lib/systemd/network/',
> and /usr/share/initramfs-tools/hooks/udev fails with exit status 1.
> But, honestly, I cannot understand why.
> 
> The lines that seem to fail are /usr/share/initramfs-tools/hooks/udev:
> 25 and the following ones... But why?

yes, that's where it seems to fail. To further investigate you can try the
following:

Copy /usr/share/autopkgtest/setup-commands/setup-testbed to a location that you
control so that you can edit it. Remove all the parts that are not necessary to
reproduce the problem. I suspect just keeping the line 'chroot "$root"
update-initramfs -u' is not sufficient and something else has to happen before
so that you can see the error? If that line alone is enough, then you should
also be able to reproduce the problem by running mmdebstrap with:

--customize-hook='chroot "$1" update-initramfs -u'

Once you are that far, you either already have found the problem or the next
thing you can try is to debug /usr/share/initramfs-tools/hooks/udev. To do
that, just insert a "set -x" somewhere at the top. For example by adding the
following before you call the failing hook:

--customize-hook='awk "NR==2{print 'set -x'}1" 
"$1/usr/share/initramfs-tools/hooks/udev"'

I would love to help more but I already tried out the failing command on three
different systems and I'm unable to reproduce it.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#950115: report debian/upstream/metadata without upstream Repository

[Jelmer Vernooij]

Package: lintian
Version: 2.47.0
Severity: wishlist

It would be great if lintian warned about debian/upstream/metadata files that
did not contain any upstream repository information (i.e. the 'Repository'
field is not present in debian/upstream/metadata).

This should probably be informational, since there are at least some upstreams
that do not use a VCS, and there is not much the Debian maintainer can do about 
that.

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

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

Versions of packages lintian depends on:
ii  binutils 2.33.90.20200122-2
ii  bzip21.0.8-2
ii  diffstat 1.63-1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.38-4
ii  gettext  0.19.8.1-10
ii  gpg  2.2.19-1
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b2
ii  libarchive-zip-perl  1.67-1
ii  libberkeleydb-perl   0.62-1+b1
ii  libcapture-tiny-perl 0.48-1
ii  libcgi-pm-perl   4.45-1
ii  libclass-accessor-perl   0.51-1
ii  libclass-xsaccessor-perl 1.19-3+b3
ii  libclone-perl0.43-2
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libfont-ttf-perl 1.06-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.75-1
ii  libipc-run-perl  20180523.0-2
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmldbm-perl2.05-2
ii  libmoo-perl  2.003006-1
ii  libmoox-aliases-perl 0.001006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.108-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3100-1
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.008001-2
ii  liburi-perl  1.76-1
ii  libxml-libxml-perl   2.0134+dfsg-1+b1
ii  libyaml-libyaml-perl 0.80+repack-2+b1
ii  man-db   2.9.0-2
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-9
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b6

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libhtml-parser-perl3.72-3+b4
ii  libtext-template-perl  1.58-1

-- no debconf information

Bug#949854: RFS: coinor-vol/1.5.4-3 -- Coin-or linear programming solver (libraries)

[Sudip Mukherjee]

Hi Adam,

On Sun, Jan 26, 2020 at 01:39:00AM +0100, Adam Borowski wrote:
> On Sat, Jan 25, 2020 at 11:53:02PM +, Sudip Mukherjee wrote:
> >  * Package name: coinor-vol
> >Version : 1.5.4-3
> 
> > Changes since the last upload:
> > 
> >* QA upload.
> >* Fix relative paths.
> >* Use dh_autoreconf and dh_auto_configure. (Closes: #949299)
> 
> I'm afraid that it throws an enormous number of errors:

> ./config.status: line 764: : command not found

A new package has been uploaded to mentors for your review.

Changes since the last upload:

   * QA upload.
   * Fix relative paths.
   * Use libtool from system.
   * Use dh_autoreconf and dh_auto_configure. (Closes: #949299)

--
Regards
Sudip

Bug#950096: flatpak: Flatpak fails to open SSL connections with p11-kit 0.23.19

[Lennart Weller]

Package: flatpak
Version: 1.6.1-1
Severity: important

Dear Maintainer,

Currently all SSL connections, probably mostly HTTPS, will fail with
flatpak due to a major API change in p11-kit as discussed in the merge
request[1] for p11-kit 0.23.19, cause obviously a patch-version changes
major API endpoints.


[1] 
https://gitlab.com/freedesktop-sdk/freedesktop-sdk/-/merge_requests/2255?commit_id=e3361c2ddf3ecfff19908effb80d3a648e3dd75a


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

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

Versions of packages flatpak depends on:
ii  adduser3.118
ii  bubblewrap 0.4.0-1
ii  libappstream-glib8 0.7.16-1
ii  libarchive13   3.4.0-1+b1
ii  libc6  2.29-9
ii  libdconf1  0.34.0-2
ii  libfuse2   2.9.9-2
ii  libgdk-pixbuf2.0-0 2.40.0+dfsg-2
ii  libglib2.0-0   2.62.4-1+b1
ii  libgpgme11 1.13.1-3
ii  libjson-glib-1.0-0 1.4.4-2
ii  libostree-1-1  2019.6-1
ii  libpolkit-agent-1-00.105-26
ii  libpolkit-gobject-1-0  0.105-26
ii  libseccomp22.4.2-2
ii  libsoup2.4-1   2.68.2-1
ii  libsystemd0244.1-1
ii  libxau61:1.0.8-1+b2
ii  libxml22.9.4+dfsg1-8
ii  xdg-dbus-proxy 0.1.2-1

Versions of packages flatpak recommends:
ii  desktop-file-utils   0.24-1
ii  gtk-update-icon-cache3.24.13-1
ii  hicolor-icon-theme   0.17-2
ii  libpam-systemd   244.1-1
ii  p11-kit  0.23.19-2
ii  policykit-1  0.105-26
ii  shared-mime-info 1.10-1
ii  xdg-desktop-portal   1.6.0-1
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.6.0-1

Versions of packages flatpak suggests:
ii  avahi-daemon  0.7-5

-- no debconf information

Bug#950098: patsy: exceptions in documentation, FTBFS with new ipython

[Rebecca N. Palmer]

Package: python-patsy-doc
Version: 0.5.1-0.2
Severity: serious
Control: tags -1 patch

Some examples in patsy's spline-regression.rst raise exceptions when 
executed (at documentation build time).  Such exceptions used to appear 
in the documentation output, but in ipython_directive 7.x they default 
to failing the whole build.


This can be turned off, but in the case of patsy it is possible to 
really fix the exceptions, which is probably better:


--- patsy-0.5.1/debian/control
+++ patsy-0.5.1/debian/control
@@ -8,6 +8,7 @@
python3-all,
python3-setuptools,
python3-numpy,
+   python3-scipy,
python3-pandas,
python3-nose,
python3-six,
--- patsy-0.5.1/debian/patches/print3.patch
+++ patsy-0.5.1/debian/patches/print3.patch
@@ -0,0 +1,17 @@
+Description: Use Python 3 syntax in example
+
+Author: Rebecca N. Palmer 
+Bug-Debian: https://bugs.debian.org/
+Forwarded: no
+
+--- patsy-0.5.1.orig/doc/spline-regression.rst
 patsy-0.5.1/doc/spline-regression.rst
+@@ -179,7 +179,7 @@ marginal spline bases patterns can be ob
+   :{"x1": x1.ravel(), "x2": x2.ravel(), "df": df})
+   :
+
+-   In [80]: print y.shape
++   In [80]: print(y.shape)
+
+In [90]: fig = plt.figure()
+
--- patsy-0.5.1/debian/patches/series
+++ patsy-0.5.1/debian/patches/series
@@ -1 +1,2 @@
 up_six_PY
+print3.patch

Bug#950097: rauc: no hardening when building from git repository

[Uwe Kleine-König]

Source: rauc
Version: 1.2-1
Severity: minor

When building rauc 1.2-1 from the git repository cloned from salsa I
get:

$ dpkg-buildpackage -uc -us
...
$ lintian -EL '>=pedantic' ../rauc_1.2-1_amd64.changes
I: rauc: hardening-no-fortify-functions usr/bin/rauc
I: rauc-service: package-supports-alternative-init-but-no-init.d-script 
lib/systemd/system/rauc.service
I: rauc-service: systemd-service-file-missing-install-key 
lib/systemd/system/rauc.service
I: rauc source: testsuite-autopkgtest-missing
X: rauc source: upstream-metadata-file-is-missing

. When I do

mv .git ../rauc.git

before building I get however:

$ dpkg-buildpackage -uc -us
...
$ lintian -EL '>=pedantic' ../rauc_1.2-1_amd64.changes
I: rauc-service: package-supports-alternative-init-but-no-init.d-script 
lib/systemd/system/rauc.service
I: rauc-service: systemd-service-file-missing-install-key 
lib/systemd/system/rauc.service
I: rauc source: testsuite-autopkgtest-missing
X: rauc source: upstream-metadata-file-is-missing

So the hardening-no-fortify-functions problem only occurs in the presence of
the .git directory.

This is related to ./configure assuming that debugging should be enabled if a
.git directory exists which in turn adds -O0 to the command line (additionally
to the -O2 that is present for both cases).

According to
https://wiki.debian.org/Hardening#DEB_BUILD_HARDENING_FORTIFY_.28gcc.2Fg.2B-.2B-_-D_FORTIFY_SOURCE.3D2.29
"for this feature to be fully enabled, the source must also be compiled with
-O1 or higher."

It is only little relevant for Debian as the packages are build from the
source package and there is no .git directory, but it is still ugly.

Maybe we should pass --disable-debugging to configure? Or convince
upstream that this assumption (.git present => --enable-debug) is a bad
idea?

Best regards
Uwe

Bug#950102: DDPO: please remove the icons from the Source Package column again (or as QUERY_STRING option)

[Thorsten Glaser]

Package: qa.debian.org

I’ve barely managed to get the DDPO to fit on my 1024x768 laptop screen
by zooming out, and now there are suddenly icons which make it wider again.
Please allow me to get rid of them.

Similarily, dropping the icon from the Bugs column would be a welcome feature.

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

Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Bug#950101: python-xarray-doc: FTBFS with new ipython

[Rebecca N. Palmer]

Package: python-xarray-doc
Version: 0.14.1-2
Severity: serious
Control: tags -1 patch

ipython_directive examples are executed at build time.  xarray has some 
examples that fail without optional dependencies Debian doesn't have 
(e.g. h5netcdf) and/or downloaded data.  This used to put the error 
message in the documentation (non-ideal but I prefer it to no 
documentation), but in ipython_directive 7, it defaults to failing the 
whole documentation build.


Fix: this can be turned off by adding

ipython_warning_is_error = False

anywhere in the top level of doc/conf.py.

Bug#950100: fonts-oldstandard FTBFS with fontforge using Python 3

[Adrian Bunk]

Source: fonts-oldstandard
Version: 2.2really-3
Severity: serious
Tags: ftbfs bullseye sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-oldstandard.html

...
fontforge -script ost-generate.py
Copyright (c) 2000-2019. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later 
 with many parts BSD . Please read LICENSE.
 Version: 20190801
 Based on sources from 12:20 UTC 13-Nov-2019-ML-D-GDK3.
Cannot find your hotkey definition file!
  File "ost-generate.py", line 37
if ttname[1] == 'SubFamily':
   ^
TabError: inconsistent use of tabs and spaces in indentation
make[1]: *** [debian/rules:11: override_dh_install] Error 1

Bug#950103: fonts-lemonada FTBFS: KeyError: "glyph 'M' already exists"

[Adrian Bunk]

Source: fonts-lemonada
Version: 4.004+git20190612-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-lemonada.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/fonts-lemonada-4.004+git20190612'
fontmake -i -o otf -g sources/*.glyphs
INFO:fontmake.font_project:Building master UFOs and designspace from Glyphs 
source
INFO:glyphsLib.classes:Parsing "sources/Lemonada.glyphs" file into 
Traceback (most recent call last):
  File "/usr/bin/fontmake", line 11, in 
load_entry_point('fontmake==2.0.7', 'console_scripts', 'fontmake')()
  File "/usr/lib/python3/dist-packages/fontmake/__main__.py", line 425, in main
project.run_from_glyphs(glyphs_path, **args)
  File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 670, in 
run_from_glyphs
write_skipexportglyphs=write_skipexportglyphs,
  File "/usr/lib/python3/dist-packages/fontTools/misc/loggingTools.py", line 
367, in wrapper
return func(*args, **kwds)
  File "/usr/lib/python3/dist-packages/fontmake/font_project.py", line 156, in 
build_master_ufos
ufo_module=ufoLib2,
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/__init__.py", line 
111, in to_designspace
return builder.designspace
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/builders.py", line 
260, in designspace
list(self.masters)  # Make sure that the UFOs are built
  File "/usr/lib/python3/dist-packages/glyphsLib/builder/builders.py", line 
222, in masters
ufo_glyph = ufo_layer.newGlyph(glyph.name)
  File "/usr/lib/python3/dist-packages/ufoLib2/objects/layer.py", line 120, in 
newGlyph
raise KeyError("glyph %r already exists" % name)
KeyError: "glyph 'M' already exists"
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 1

Bug#948855: buster-pu: package iputils/3:20180629-2

[Adam D. Barratt]

Control: tags -1 +moreinfo

On Mon, 2020-01-27 at 18:15 -0500, Noah Meyerhans wrote:
> Control: tags -1 - moreinfo
> 
> On Fri, Jan 24, 2020 at 10:11:38PM +, Adam D. Barratt wrote:
> > > I'd like to fix 
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947921 in
> > > buster.  Ping has some issues coping with explicitly specified
> > > source interfaces when pinging DNS names and DNS returns multiple
> > > addresses via getaddrinfo().  Please see the commit messages and
> > > the bug report for in-depth explanation of what's going on.
> > 
> > The metadata for that bug report suggests that it affects the
> > iputils package in unstable, and is not currently fixed there. Is
> > that correct?
> 
> That's correct.  Upstream has not yet made a release containing the
> fix, nor have I backported it to the version currently in testing
> (there are enough changes to make that nontrivial).  I am making my
> request based on the patch author's report that it does, indeed, fix
> the problem in buster, and the fact that the fix has been accepted
> upstream.
> 
> If you'd prefer, we can wait until the next buster point release, by
> which time we'll presumably have more testing of these patches.

In general our workflow is for patches to be applied to unstable first
where appropriate, so that sounds like the best approach; thanks for
confirming.

In the meantime, I'm going to re-add the "moreinfo" tag, as it's the
best signal we currently have for "not ready to be processed by SRM".
Please feel free to remove it once the issues are resolved in unsable.

Regards,

Adam

Bug#949959: debcargo.toml should make it possible to declare additional dependencies for generated autopkgtests

[Daniel Kahn Gillmor]

On Tue 2020-01-28 16:58:52 -0500, Daniel Kahn Gillmor wrote:
> Control: tag 949959 + patch
>
> On Mon 2020-01-27 11:55:28 -0500, Daniel Kahn Gillmor wrote:
>> So it would be good to be able to indicate in debcargo.toml some
>> additional autopkgtest dependencies.
>>
>> Simplest might be to add a dependency for *all* generated autopkgtests,
>> but i can imagine there are some subtler requirements which will need to
>> be for specific autopkgtests in the future.
>
> Wolfgang created this patch (on the dev/debian_949959 branch in salsa)
> to implement this mechanism.
>
> It looks reasonable to me, and it compiles fine.  I'm in the process of
> testing it now.

I've just uploaded rust-clang-sys 0.28.1-5, built with a version of
debcargo that is 2.4.2 plus Wolfgang's patch in debian/patches/

We'll see how it fares on ci.debian.net.

  --dkg


signature.asc
Description: PGP signature

Bug#851747: sysvinit-utils: drop Essential flag

[Michael Biebl]

Am 28.01.2020 um 17:38 schrieb Andreas Henriksson:
> On Tue, Jan 28, 2020 at 05:02:38PM +0100, Michael Biebl wrote:
> [...]
>> Assuming the .service isn't just a wrapper around the init script.
>> Unfortunately, we do have quite a few packages which use this
>> anti-pattern :-/
>>
>> https://codesearch.debian.net/search?q=ExecStart%3D%2Fetc%2Finit.d%2F=1=1
> 
> https://lintian.debian.org/tags/systemd-service-file-wraps-init-script.html

Thanks for that pointer. Totally forgot that we had a lintian check for
that.

> It seems "Debian OpenStack" is the main offender so unless people use
> openstack the problem possibly isn't that widely spread.

Indeed.

> This however serves as a good reminder that it's not enough to just
> check that there's a masking native systemd unit.
> (I'll probably forget about that very soon again, but atleast there's
> now a note/warning about this case in this bugs history! :)
> 
> (It might be time to ask lintian maintainers to consider raising
> severity or turning some warnings into errors for systemd-related
> lintian checks.)

Sounds like a good idea.

-- 
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#950107: ruby-kramdown no longer ships its gemspec file (makes other packages FTBFS)

[Daniel Leidert]

Package: ruby-kramdown
Version: 1.17.0-3
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The package no longer ships the kramdown-1.17.0.gemspec file. Thus packages
using e.g. gem2deb-test-runner --check-dependencies will fail here. For example
jekyll's dependencies cannot longer be fulfilled, because the gem cannot be
found:

https://ci.debian.net/data/autopkgtest/unstable/amd64/r/ruby-jekyll-redirect-from/4086760/log.gz

This is very probably related to the recent split of ruby-kramdown.

Regards, Daniel


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

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

Versions of packages ruby-kramdown depends on:
ii  libjs-jquery  3.3.1~dfsg-3
ii  ruby-coderay  1.1.2-2
ii  ruby-prawn2.2.0+dfsg-1
ii  ruby-prawn-table  0.2.2-1
ii  ruby-rouge3.15.0-1
ii  ruby-stringex 2.8.4-1

ruby-kramdown recommends no packages.

Versions of packages ruby-kramdown suggests:
pn  libjs-mathjax  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl4wtMsACgkQS80FZ8KW
0F3X6g//Y+W4Ivmn076MJDLjVyJBSRAvz9NRjBzzlmb1TOToHX//IO9RGQa32sjG
4o0wVXU9gMppPZsTXy/XedjQLJ5yJ7XSOovQYWF7aGvayywRz5W5HAqGxxUQ1lNL
LM95fzse9qICPjRqQggLIl5puzRvkTaxh5RW8iKz59NF+BnSRMlG32Yvb0VPDvAA
4lP/SD03Jf0MPBduN00urhP5GZRQeIQHdz4hR8JE29WzWJK/9Op3GsDh4K94Z9F8
ULld1NQLBLXmixnH5dQ2C8m5J9ZhesctWIdYTuN1Mgq+UdXRn0oSsSE1YHrNGRmv
Pd6/wCl6ogIE3V4ZowHYXt2qo+tqStLQDu9BjnyHmT+z+0iKyeGSat1pfZZ2Dl/2
68j6giCDq4CcrmBAHHQdiJrnWsdb8W2m8p1wVZWYIvvEaK+oRJHP4xpTEr9vSdyX
9o39KB+fXUUk+yczNxxw64yFXGXY7mBG30VEOLDLhF56Pq6i21OdkxRNvhz0OFXO
k67GF77Qt0F7dtjujVaRtaFf2ZQbY8aUDQKppBGvg4ww6sbAdJYvtfCRDPn9mxHh
Fbuh3aebym4nZ0dTaKgO4V5kh2S8ABc/aIn0/bbtprYPcyWRBSRJHKYw+xwIYwQR
qqQjlDDVEqXHfeylO4xOK1Qatt5ofVEZ9Dj2Q/r7Vh4iPoA5+J8=
=P3st
-END PGP SIGNATURE-

Bug#950106: tdiary-mode: fails to upgrade from 'buster': >>Error occurred processing http.el: File is missing (("Opening input file" "No such file or directory" "/usr/share/emacs/site-lisp/elpa/tdiary

[Andreas Beckmann]

Package: tdiary-mode
Version: 5.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.

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

  Setting up tdiary-mode (5.1.0-1) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install tdiary-mode for emacs
  install/tdiary-mode-20170123.2324: Handling install of emacsen flavor emacs
  install/tdiary-mode-20170123.2324: byte-compiling for emacs
  >>Error occurred processing http.el: File is missing (("Opening input file" 
"No such file or directory" 
"/usr/share/emacs/site-lisp/elpa/tdiary-mode-20170123.2324/http.el"))
  
  In tdiary-new-or-replace:
  tdiary-mode.el:614:12:Warning: Use `with-current-buffer' rather than
  save-excursion+set-buffer
  ERROR: install script from tdiary-mode package failed
  dpkg: error processing package tdiary-mode (--configure):
   installed tdiary-mode package post-installation script subprocess returned 
error exit status 1


cheers,

Andreas


tdiary-mode_5.1.0-1.log.gz
Description: application/gzip

Bug#948786: buster-pu: package apt-cacher-ng/3.2.1-1 pre-approval

[Adam D. Barratt]

On Wed, 2020-01-22 at 22:16 +0100, Eduard Bloch wrote:
> I would like to have some kind of confirmation from the release team
> that this mail does not go straight to /dev/null and that a new
> upstream (minor) version is an acceptable candidate for a Stable
> update.

No mail is ignored, and I don't appreciate the implication.

As you may have noticed, manpower for processing stable updates is
somewhat thin on the ground these days, and there's only so many
requests I can get through in any given time, particularly while trying
to fit in other Debian, dayjob and other activities.

To be entirely honest, it's also not the most fun thing to spend an
evening doing.

> I can, of course, convert all that into debian/patches/XXX but
> honestly, that would really feel like greenwashing.
> 
> The changes reported here can be reviewed at
> https://salsa.debian.org/blade/apt-cacher-ng/commits/temp/debian-merge ,
> starting with the commit from 2019-12-20.

Those look OK as individual commits, thanks. For completeness, could we
please have a finalised source debdiff of the built source package,
compared to current stable?

Regards,

Adam

Bug#949921: buster-pu: package uim_1.8.8-4+deb10u3

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Tue, 2020-01-28 at 13:03 +0900, Takatsugu Nokubi wrote:
> +  [ NOKUBI Takatsugu ]
> +  * d/libuim-data.postint: add uim-mozc (See #939588)
> +
> +  [ HIGUCHI Daisuke (VDR dai) ]
> +  * d/libuim-data.postint: add uim-chewing
> +
> +  [ YOSHINO Yoshihito ]
> +  * d/libuim-data.postinst: unregister not-installed modules
> (Closes: #945344).
> +The previous upload to fix #939588 caused regression, which has
> +accidentally registered some not-installed modules.

Are all of these changes already applied to the package in unstable?

Regards,

Adam

Bug#950109: ITP: chez-srfi -- SRFI libraries for Chez Scheme

[Göran Weinholt]

Package: wnpp
Severity: wishlist
Owner: Göran Weinholt 

* Package name: chez-srfi
  Version : git checkout
  Upstream Author : Aaron W. Hsu
* URL : https://github.com/arcfide/chez-srfi/
* License : mainly MIT/X and BSD
  Programming Lang: Scheme
  Description : SRFI libraries for Chez Scheme

 SRFI stands for Scheme Requests For Implementation. It is a
 standardization process for extensions to the programming language
 Scheme. Since its start in 1998, the project has been working for
 portability between Scheme implementations.
 .
 This package provides SRFI implementations primarily developed for
 Chez Scheme. Most of the libraries are however fully portable to
 other R6RS implementations.

Almost all Scheme compilers come with a few SRFIs, but Chez Scheme
does not come with any. Yet most Scheme code, including my own,
depends on some SRFIs.

I'm working with upstream to resolve some license issues.

I will maintain this package myself, but would like to see some
coordinated maintenance of Scheme in Debian.

Bug#950114: gplaycli: TypeError: search() got an unexpected keyword argument 'nb_result'

[Thorsten Glaser]

Package: gplaycli
Version: 3.26+dfsg-1
Severity: grave
Justification: renders package unusable

After generating an application password and putting it into
/etc/gplaycli/gplaycli.conf (see below) to work around #950112
things still don’t work:

$ gplaycli -s musescore
Traceback (most recent call last):
  File "/usr/bin/gplaycli", line 11, in 
load_entry_point('GPlayCli==3.26', 'console_scripts', 'gplaycli')()
  File "/usr/lib/python3/dist-packages/gplaycli/gplaycli.py", line 716, in main
cli.search(args.search_string, nb_results, not args.paid)
  File "/usr/lib/python3/dist-packages/gplaycli/hooks.py", line 9, in 
check_connection
return function(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/gplaycli/gplaycli.py", line 340, in 
search
results = self.api.search(search_string, nb_result=nb_results)
TypeError: search() got an unexpected keyword argument 'nb_result'


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

Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages gplaycli depends on:
ii  python3   3.7.5-3
ii  python3-crypto2.6.1-13
ii  python3-gpapi 0.4.4-1
ii  python3-pyaxmlparser  0.3.24-1

Versions of packages gplaycli recommends:
pn  dummydroid
pn  fdroidserver  

gplaycli suggests no packages.

-- Configuration Files:
/etc/gplaycli/gplaycli.conf changed:
[Credentials]
gmail_address=XXX
gmail_password=XXX
token=False
token_url=https://matlink.fr/token/email/gsfid
[Cache]
token=~/.cache/gplaycli/token
[Locale]
locale=en_GB
timezone=CEST


-- no debconf information

Bug#950096: flatpak: Flatpak fails to open SSL connections with p11-kit 0.23.19

[Simon McVittie]

On Tue, 28 Jan 2020 at 22:50:31 +0100, Lennart Weller wrote:
> Currently all SSL connections, probably mostly HTTPS, will fail with
> flatpak due to a major API change in p11-kit as discussed in the merge
> request[1] for p11-kit 0.23.19, cause obviously a patch-version changes
> major API endpoints.

Is there something that can be done in the Flatpak executables to make
this work better, or is it a problem with the freedesktop.org reference
runtime?

Is this triggered by the new p11-kit in the host system, or by the new
p11-kit in the runtime, or by them being on opposite sides of the 0.23.19
version threshold, or what?

Thanks,
smcv

Bug#950116: gplaycli: KeyError: 'docId' --or-- 'Item not found.'

[Thorsten Glaser]

Package: gplaycli
Version: 3.26+dfsg-1
Severity: grave
Justification: renders package unusable

Similar to #950114, downloading (getting the ID from the gplay
website) does not work:

$ gplaycli -pvd com.musescore.playerlite
[INFO] GPlayCli version 3.26 [Python3.7.6]
[INFO] Configuration file is /etc/gplaycli/gplaycli.conf
[INFO] Device is bacon
[INFO] Using credentials to connect to API
[INFO] Using plaintext password
Traceback (most recent call last):
  File "/usr/bin/gplaycli", line 11, in 
load_entry_point('GPlayCli==3.26', 'console_scripts', 'gplaycli')()
  File "/usr/lib/python3/dist-packages/gplaycli/gplaycli.py", line 724, in main
cli.download(args.packages_to_download)
  File "/usr/lib/python3/dist-packages/gplaycli/hooks.py", line 9, in 
check_connection
return function(self, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/gplaycli/gplaycli.py", line 254, in 
download
filename = detail['docId']+ ".apk"
KeyError: 'docId'


Another error I see is this:


$ gplaycli -vpd de.hafas.android.db
[INFO] GPlayCli version 3.26 [Python3.7.6]
[INFO] Configuration file is /etc/gplaycli/gplaycli.conf
[INFO] Device is bacon
[INFO] Using credentials to connect to API
[INFO] Using plaintext password
[ERROR] A few packages could not be downloaded :
de.hafas.android.db
'Item not found.'


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

Kernel: Linux 5.4.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages gplaycli depends on:
ii  python3   3.7.5-3
ii  python3-crypto2.6.1-13
ii  python3-gpapi 0.4.4-1
ii  python3-pyaxmlparser  0.3.24-1

Versions of packages gplaycli recommends:
pn  dummydroid
pn  fdroidserver  

gplaycli suggests no packages.

-- Configuration Files:
/etc/gplaycli/gplaycli.conf changed [not included]

-- no debconf information

Bug#950112: gplaycli: 502 Bad Gateway, does not work at all

[Thorsten Glaser]

Dixi quod…

>[ERROR] Unknown error: 
>502 Bad Gateway

It’s apparently possible to work around this error by
getting a Google account, logging in, creating an
application password, then putting that password and
the eMail address used as login, as well as token=False,
into /etc/gplaycli/gplaycli.conf; this process however
is not documented (and don’t forget chown/chmod on the
configuration file to make it not world-readable either!).

Not that it helps making the program usable… (see the two
other bugreports.)

bye,
//mirabilos
-- 
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh

Bug#940536: dhex: hangs on keyboard config screen

[Linux-Fan]

Hello,

this bug is also known for the Ubuntu package:
https://bugs.launchpad.net/ubuntu/+source/dhex/+bug/1814478

There, it is mentioned that the `cpu-load` patch is causing this bug. I just
verified this: Compiling the original (unmodified, unpatched) dhex-0.69
source code does not expose this buggy behaviour. However, if the line from
the `cpu-load` patch is applied (even without the other patches), the setup
screen does not react to keyboard input as described in the respective bug
reports.

I would thus suggest that the `cpu-load` patch be removed or fixed?

Thanks in advance
Linux-Fan


pgpvtF1QsxVrj.pgp
Description: PGP signature

Bug#950087: statsmodels: FTBFS with new ipython

[Rebecca N. Palmer]

Package: python-statsmodels-doc
Severity: serious
Control: tags -1 patch
(only tested in 0.11, but believed to exist earlier)

Some documentation examples (e.g. contrasts.rst) fail in a Debian build 
because they need to download data.


This has been the case for some time, but only became an FTBFS when 
ipython 7.x was uploaded, as ipython_directive now defaults to failing 
the build when an example fails.


Fix: turn this off with

--- statsmodels-0.11.0.orig/docs/source/conf.py
+++ statsmodels-0.11.0/docs/source/conf.py
@@ -63,6 +63,7 @@ else:

 # nbsphinx options
 nbsphinx_allow_errors = True
+ipython_warning_is_error = False
 # sphinxcontrib-spelling options
 spelling_word_list_filename = ['spelling_wordlist.txt', 
'names_wordlist.txt']

 spelling_ignore_pypi_package_names = True

Bug#950091: node-prop-types FTBFS: Error: Can't resolve

[Adrian Bunk]

Source: node-prop-types
Version: 15.6.0+ds-3
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-prop-types.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-prop-types-15.6.0+ds'
webpack --config debian/webpack.config.js --output-library=PropTypes \
--entry index.js --output ./prop-types.js --mode development
Hash: e061ebce6ca8f90025b2
Version: webpack 4.7.0
Time: 1190ms
Built at: 02/27/2021 10:52:30 PM
Asset  Size  Chunks Chunk Names
prop-types.js  28.9 KiBnull  [emitted]  null
Entrypoint null = prop-types.js
[./checkPropTypes.js] 2.81 KiB {null} [built]
[./factoryWithTypeCheckers.js] 19.4 KiB {null} [built]
[./index.js] 956 bytes {null} [built]
[./lib/ReactPropTypesSecret.js] 314 bytes {null} [built]

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'fbjs/lib/emptyFunction' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 10:20-53
 @ ./index.js

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'fbjs/lib/invariant' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 11:16-45
 @ ./index.js

ERROR in ./checkPropTypes.js
Module not found: Error: Can't resolve 'fbjs/lib/invariant' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./checkPropTypes.js 11:18-47
 @ ./factoryWithTypeCheckers.js
 @ ./index.js

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'fbjs/lib/warning' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 12:14-41
 @ ./index.js

ERROR in ./checkPropTypes.js
Module not found: Error: Can't resolve 'fbjs/lib/warning' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./checkPropTypes.js 12:16-43
 @ ./factoryWithTypeCheckers.js
 @ ./index.js

ERROR in ./factoryWithTypeCheckers.js
Module not found: Error: Can't resolve 'object-assign' in 
'/build/1st/node-prop-types-15.6.0+ds'
 @ ./factoryWithTypeCheckers.js 13:13-37
 @ ./index.js
make[1]: *** [debian/rules:8: override_dh_auto_build] Error 2

Bug#950095: ITP: pyout -- interface for writing structured records as a table in a terminal

[Yaroslav Halchenko]

Package: wnpp
Severity: wishlist
Owner: Yaroslav Halchenko 

* Package name: pyout
  Version : 0.5.0
  Upstream Author : Kyle Meyer 
* URL : https://github.com/pyout/pyout
* License : MIT/X
  Programming Lang: Python
  Description : interface for writing structured records as a table in a 
terminal

pyout is a Python package that defines an interface for writing
structured records as a table in a terminal. It is being developed to replace
custom code for displaying tabular data in in ReproMan and DataLad.
.
A primary goal of the interface is the separation of content from style
and presentation. Current capabilities include
.
 - automatic width adjustment and updating of previous values
 - styling based on a field value or specified interval
 - defining a transform function that maps a raw value to the displayed value
 - defining a summary function that generates a summary of a column (e.g., 
value totals)
 - support for delayed, asynchronous values that are added to the table as they 
come in


This package is needed for other upcoming ITPs, and eventually might
also be used in already existing packages (e.g. datalad)

The plan is to team maintain it within Debian Python Modules Team, since pyout 
is
of general utility.

Bug#949897: buster-pu: package golang-github-prometheus-common/0+git20181119.b36ad28-1+deb10u1

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Sun, 2020-01-26 at 21:57 +0200, Adrian Bunk wrote:
>   * Backport upstream patch "config: extend validity of testdata
> certs":
> As the previous test certificates were set to expire on 2019-07-
> 13,
> causing TestNewClientFromConfig to fail after that date.
> See https://github.com/prometheus/common/pull/186
> (Closes: #949189)

I'm hoping that doesn't imply having to rebuild any of the (several) r-
deps?

Regards,

Adam

Bug#950110: liboctomap-dev,...: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Package: liboctomap-dev,liboctovis-dev,octomap-tools,octovis
Version: 1.9.3+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m51.2s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/liboctomap-dev/changelog.Debian.gz (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/changelog.Debian.gz (liboctomap1.8)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/copyright (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/copyright (liboctomap1.8)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data (liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/geb079.bt (liboctomap-dev:amd64) 
!= /usr/share/doc/liboctomap1.8/examples/data/geb079.bt (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/mapcoll.txt 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data/mapcoll.txt (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/scan.dat.bz2 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data/scan.dat.bz2 (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/data/spherical_scan.graph 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/data/spherical_scan.graph (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8
  /usr/share/doc/liboctomap-dev/examples/example-project.tgz 
(liboctomap-dev:amd64) != 
/usr/share/doc/liboctomap1.8/examples/example-project.tgz (?)
/usr/share/doc/liboctomap-dev -> liboctomap1.8

1m12.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/liboctovis-dev/changelog.Debian.gz (liboctovis-dev:amd64) != 
/usr/share/doc/liboctomap1.8/changelog.Debian.gz (liboctomap1.8)
/usr/share/doc/liboctovis-dev -> liboctomap1.8
  /usr/share/doc/liboctovis-dev/copyright (liboctovis-dev:amd64) != 
/usr/share/doc/liboctomap1.8/copyright (liboctomap1.8)
/usr/share/doc/liboctovis-dev -> liboctomap1.8

0m25.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/octomap-tools/changelog.Debian.gz (octomap-tools) != 
/usr/share/doc/liboctomap1.8/changelog.Debian.gz (liboctomap1.8)
/usr/share/doc/octomap-tools -> liboctomap1.8
  /usr/share/doc/octomap-tools/copyright (octomap-tools) != 
/usr/share/doc/liboctomap1.8/copyright (liboctomap1.8)
/usr/share/doc/octomap-tools -> liboctomap1.8

2m14.0s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/octovis/changelog.Debian.gz (octovis) != 
/usr/share/doc/liboctomap1.8/changelog.Debian.gz (liboctomap1.8)
/usr/share/doc/octovis -> liboctomap1.8
  /usr/share/doc/octovis/copyright (octovis) != 
/usr/share/doc/liboctomap1.8/copyright (liboctomap1.8)
/usr/share/doc/octovis -> liboctomap1.8



cheers,

Andreas


liboctomap-dev_1.9.3+dfsg-1.log.gz
Description: application/gzip

Bug#623131: Message about Adobe Acrobat

[Stephane Ascoet]

Hi, this message is inside the PDF. What's missing in Xpdf is the ability to 
read PDF document with writeable fields. It blocks me for administrative forms 
too. And since the maintened Xpdf version is now the "4" branch, needing QT 
library(ies), I wonder what will happen in the future.


--
Sincerely, Stephane Ascoet

Bug#950111: libvigraimpex-doc: unhandled symlink to directory conversion: /usr/share/doc/libvigraimpex-dev/html

[Andreas Beckmann]

Package: libvigraimpex-doc
Version: 1.11.1+dfsg-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  buster -> bullseye

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m58.6s ERROR: installs objects over existing directory symlinks:
  /usr/share/doc/libvigraimpex-dev/html/AlgebraicConcepts.html 
(libvigraimpex-doc) != 
/usr/share/doc/libvigraimpex-doc/html/AlgebraicConcepts.html (?)
/usr/share/doc/libvigraimpex-dev/html -> ../libvigraimpex-doc/html
  /usr/share/doc/libvigraimpex-dev/html/ArgumentObjectFactories.html 
(libvigraimpex-doc) != 
/usr/share/doc/libvigraimpex-doc/html/ArgumentObjectFactories.html (?)
/usr/share/doc/libvigraimpex-dev/html -> ../libvigraimpex-doc/html
  /usr/share/doc/libvigraimpex-dev/html/BorderTreatmentMode.html 
(libvigraimpex-doc) != 
/usr/share/doc/libvigraimpex-doc/html/BorderTreatmentMode.html (?)
/usr/share/doc/libvigraimpex-dev/html -> ../libvigraimpex-doc/html
  /usr/share/doc/libvigraimpex-dev/html/CrackEdgeImage.html (libvigraimpex-doc) 
!= /usr/share/doc/libvigraimpex-doc/html/CrackEdgeImage.html (?)
/usr/share/doc/libvigraimpex-dev/html -> ../libvigraimpex-doc/html
  /usr/share/doc/libvigraimpex-dev/html/CreditsChangelog.html 
(libvigraimpex-doc) != 
/usr/share/doc/libvigraimpex-doc/html/CreditsChangelog.html (?)
/usr/share/doc/libvigraimpex-dev/html -> ../libvigraimpex-doc/html
...


cheers,

Andreas


libvigraimpex-doc_1.11.1+dfsg-6.log.gz
Description: application/gzip

Bug#935970: stretch-pu: package node-fstream/1.0.10-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Sun, 2019-09-01 at 22:42 +0200, Xavier wrote:
> Control: tags -1 - moreinfo
> 
> Le 01/09/2019 à 12:38, Adam D. Barratt a écrit :
> > node-fstream is vulnerable to Arbitrary File Overwrite (#931408,
> > CVE-2019-13173). This little patch fixes the problem.
> 
> Sorry, I forgot to push it. Done (see #939166)

Thanks. Please go ahead.

Regards,

Adam

Bug#939897: stretch-pu: package node-mixin-deep/1.1.3-1+deb9u1

[Adam D. Barratt]

Control: tags -1 + confirmed

On Mon, 2019-09-09 at 22:22 +0200, Xavier Guimard wrote:
> since stretch and buster have the same node-mixin-deep, I added here
> the same security patches than pushed in buster.
> 

Please go ahead; sorry for the long delay.

Regards,

Adam

Bug#950110: liboctomap-dev,...: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Andreas Beckmann]

Followup-For: Bug #950110
Control: affects -1 + libdynamicedt3d-dev

0m24.8s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libdynamicedt3d-dev/changelog.Debian.gz 
(libdynamicedt3d-dev:amd64) != 
/usr/share/doc/libdynamicedt3d1.8/changelog.Debian.gz (libdynamicedt3d1.8)
/usr/share/doc/libdynamicedt3d-dev -> libdynamicedt3d1.8
  /usr/share/doc/libdynamicedt3d-dev/copyright (libdynamicedt3d-dev:amd64) != 
/usr/share/doc/libdynamicedt3d1.8/copyright (libdynamicedt3d1.8)
/usr/share/doc/libdynamicedt3d-dev -> libdynamicedt3d1.8
  /usr/share/doc/libdynamicedt3d-dev/examples (libdynamicedt3d-dev:amd64) != 
/usr/share/doc/libdynamicedt3d1.8/examples (?)
/usr/share/doc/libdynamicedt3d-dev -> libdynamicedt3d1.8
  /usr/share/doc/libdynamicedt3d-dev/examples/CMakeLists.txt 
(libdynamicedt3d-dev:amd64) != 
/usr/share/doc/libdynamicedt3d1.8/examples/CMakeLists.txt (?)
/usr/share/doc/libdynamicedt3d-dev -> libdynamicedt3d1.8
  /usr/share/doc/libdynamicedt3d-dev/examples/exampleEDT3D.cpp 
(libdynamicedt3d-dev:amd64) != 
/usr/share/doc/libdynamicedt3d1.8/examples/exampleEDT3D.cpp (?)
/usr/share/doc/libdynamicedt3d-dev -> libdynamicedt3d1.8
  /usr/share/doc/libdynamicedt3d-dev/examples/exampleEDTOctomap.cpp 
(libdynamicedt3d-dev:amd64) != 
/usr/share/doc/libdynamicedt3d1.8/examples/exampleEDTOctomap.cpp (?)
/usr/share/doc/libdynamicedt3d-dev -> libdynamicedt3d1.8
  /usr/share/doc/libdynamicedt3d-dev/examples/exampleEDTOctomapStamped.cpp 
(libdynamicedt3d-dev:amd64) != 
/usr/share/doc/libdynamicedt3d1.8/examples/exampleEDTOctomapStamped.cpp (?)
/usr/share/doc/libdynamicedt3d-dev -> libdynamicedt3d1.8


Andreas

Bug#945821: stretch-pu: package libofx/1:0.9.10-2+deb9u2

[Adam D. Barratt]

Control: tags -1 + confirmed

On Fri, 2019-11-29 at 09:54 +0100, Dylan Aïssi wrote:
> Upstream has fixed CVE-2019-9656, this CVE is non-dsa. The patch is
> already applied in jessie/buster/testing/unstable (#924350) and now I
> would like to fix the Stretch version. Please find attached a
> debdiff.
> 

Please go ahead; sorry for the delay.

Regards,

Adam

Bug#949897: buster-pu: package golang-github-prometheus-common/0+git20181119.b36ad28-1+deb10u1

[Adrian Bunk]

Control: tags -1 - moreinfo

On Tue, Jan 28, 2020 at 10:34:00PM +, Adam D. Barratt wrote:
> Control: tags -1 + moreinfo
> 
> On Sun, 2020-01-26 at 21:57 +0200, Adrian Bunk wrote:
> >   * Backport upstream patch "config: extend validity of testdata
> > certs":
> > As the previous test certificates were set to expire on 2019-07-
> > 13,
> > causing TestNewClientFromConfig to fail after that date.
> > See https://github.com/prometheus/common/pull/186
> > (Closes: #949189)
> 
> I'm hoping that doesn't imply having to rebuild any of the (several) r-
> deps?

This is testdata for build-time tests of golang-github-prometheus-common,
not certs that are useful for anything (arguably they should be generated
at build time).

These testdata certs are also shipped in the -dev package.
I haven't seen any build failures due to them in other packages.
And at runtime they are not available since they are in a -dev package.

> Regards,
> 
> Adam

cu
Adrian

Bug#950119: ITP: gajim-syntaxhighlight -- highlights source code blocks in chat window

[Martin]

Package: wnpp
Severity: wishlist
Owner: Martin 

* Package name: gajim-syntaxhighlight
  Version : 1.2.5
  Upstream Author : Florian Muenchbach
* URL : 
https://dev.gajim.org/gajim/gajim-plugins/-/wikis/syntaxhighlightplugin
* License : GPL3
  Programming Lang: Python
  Description : highlights source code blocks in chat window

 It uses markdown-style syntax, i.e. text in-between `single backticks` is
 rendered as inline code,
 ```language
 selection is possible in multi-line code snippets in between triple-backticks
 Note the newlines in this case…
 ```

Bug#950117: report debian/upstream/metadata without upstream bug tracking information

[Jelmer Vernooij]

Package: lintian
Version: 2.47.0
Severity: wishlist

It would be great if lintian reported when a debian/upstream/metadata file did
not contain any upstream bug tracking information (i.e. the Bug-Database or
Bug-Submit fields are not set).

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

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

Versions of packages lintian depends on:
ii  binutils 2.33.90.20200122-2
ii  bzip21.0.8-2
ii  diffstat 1.63-1
ii  dpkg 1.19.7
ii  dpkg-dev 1.19.7
ii  file 1:5.38-4
ii  gettext  0.19.8.1-10
ii  gpg  2.2.19-1
ii  intltool-debian  0.35.0+20060710.5
ii  libapt-pkg-perl  0.1.36+b2
ii  libarchive-zip-perl  1.67-1
ii  libberkeleydb-perl   0.62-1+b1
ii  libcapture-tiny-perl 0.48-1
ii  libcgi-pm-perl   4.45-1
ii  libclass-accessor-perl   0.51-1
ii  libclass-xsaccessor-perl 1.19-3+b3
ii  libclone-perl0.43-2
ii  libdpkg-perl 1.19.7
ii  libemail-valid-perl  1.202-1
ii  libfile-basedir-perl 0.08-1
ii  libfile-find-rule-perl   0.34-1
ii  libfont-ttf-perl 1.06-1
ii  libio-async-loop-epoll-perl  0.20-1
ii  libio-async-perl 0.75-1
ii  libipc-run-perl  20180523.0-2
ii  liblist-compare-perl 0.53-1
ii  liblist-moreutils-perl   0.416-1+b5
ii  libmldbm-perl2.05-2
ii  libmoo-perl  2.003006-1
ii  libmoox-aliases-perl 0.001006-1
ii  libnamespace-clean-perl  0.27-1
ii  libpath-tiny-perl0.108-1
ii  libtext-levenshtein-perl 0.13-1
ii  libtimedate-perl 2.3100-1
ii  libtry-tiny-perl 0.30-1
ii  libtype-tiny-perl1.008001-2
ii  liburi-perl  1.76-1
ii  libxml-libxml-perl   2.0134+dfsg-1+b1
ii  libyaml-libyaml-perl 0.80+repack-2+b1
ii  man-db   2.9.0-2
ii  patchutils   0.3.4-2+b1
ii  perl [libdigest-sha-perl]5.30.0-9
ii  t1utils  1.41-3
ii  xz-utils 5.2.4-1+b1

Versions of packages lintian recommends:
ii  libperlio-gzip-perl  0.19-1+b6

Versions of packages lintian suggests:
pn  binutils-multiarch 
ii  libhtml-parser-perl3.72-3+b4
ii  libtext-template-perl  1.58-1

-- no debconf information

Bug#950118: linux-image-4.19.0-6-amd64: Misleading/Confusing dmesgs regarding Spectre V2 user space Mitigation

[Leon Gehling]

Package: src:linux
Version: 4.19.67-2+deb10u2
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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

Kernel yells "Spectre V2 : User space: Vulnerable" at me despite i have newest
microcode , and spectre_v2_user=on bootparameter set, IBPB: always on is also
described in dmesgs.
see here:

sudo dmesg | grep -i spectre
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.19.0-6-amd64
root=/dev/mapper/thanatos--vg-root ro quiet random.trust_cpu=off spectre_v2=on
spectre_v2_user=on
[0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-6-amd64
root=/dev/mapper/thanatos--vg-root ro quiet random.trust_cpu=off spectre_v2=on
spectre_v2_user=on
[0.008350] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user
pointer sanitization
[0.008351] Spectre V2 : Mitigation: Full AMD retpoline
[0.008352] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on
context switch
[0.008357] Spectre V2 : mitigation: Enabling always-on Indirect Branch
Prediction Barrier
[0.008358] Spectre V2 : User space: Vulnerable


CPU is AMD Ryzen 7 2700.
Microcode: CPU0: patch_level=0x0800820d


Output from spectre-meltdown-checker:

CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
* Mitigated according to the /sys interface:  YES  (Mitigation: Full AMD
retpoline, IBPB: always-on, STIBP: disabled, RSB filling)
* Mitigation 1
  * Kernel is compiled with IBRS support:  YES
* IBRS enabled and active:  NO
  * Kernel is compiled with IBPB support:  YES
* IBPB enabled and active:  YES
* Mitigation 2
  * Kernel has branch predictor hardening (arm):  NO
  * Kernel compiled with retpoline option:  YES
* Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports
full retpoline compilation)
> STATUS:  NOT VULNERABLE  (Full retpoline + IBPB are mitigating the
vulnerability)



-- Package-specific info:
** Version:
Linux version 4.19.0-6-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-6-amd64 root=/dev/mapper/thanatos--vg-root ro quiet 
random.trust_cpu=off spectre_v2=on spectre_v2_user=on

** Not tainted

** Kernel log:
[  103.668388] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  103.668436] sd 1:0:0:0: Attached scsi generic sg1 type 0
[  103.668540] sd 4:0:0:0: Attached scsi generic sg2 type 0
[  103.668574] sd 11:0:0:0: Attached scsi generic sg3 type 0
[  103.669725] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[  103.669799] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
[  103.669808] sp5100-tco sp5100-tco: Watchdog hardware is disabled
[  103.679757] ccp :09:00.2: ccp enabled
[  103.679782] ccp :09:00.2: psp initialization failed
[  103.679783] ccp :09:00.2: enabled
[  103.718440] snd_hda_intel :08:00.1: Handle vga_switcheroo audio client
[  103.733222] systemd-journald[493]: Received request to flush runtime journal 
from PID 1
[  103.736906] input: HD-Audio Generic HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:06:00.0/:07:00.0/:08:00.1/sound/card0/input7
[  103.736944] input: HD-Audio Generic HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:06:00.0/:07:00.0/:08:00.1/sound/card0/input8
[  103.736980] input: HD-Audio Generic HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:06:00.0/:07:00.0/:08:00.1/sound/card0/input9
[  103.737015] input: HD-Audio Generic HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:06:00.0/:07:00.0/:08:00.1/sound/card0/input10
[  103.737052] input: HD-Audio Generic HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:06:00.0/:07:00.0/:08:00.1/sound/card0/input11
[  103.737158] input: HD-Audio Generic HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:06:00.0/:07:00.0/:08:00.1/sound/card0/input12
[  103.743417] kvm: Nested Virtualization enabled
[  103.743428] kvm: Nested Paging enabled
[  103.743429] SVM: Virtual VMLOAD VMSAVE supported
[  103.743429] SVM: Virtual GIF supported
[  103.745943] MCE: In-kernel MCE decoding enabled.
[  103.747745] EDAC amd64: Node 0: DRAM ECC enabled.
[  103.747746] EDAC amd64: F17h detected (node 0).
[  103.747786] EDAC MC: UMC0 chip selects:
[  103.747787] EDAC amd64: MC: 0: 16383MB 1: 16383MB
[  103.747788] EDAC amd64: MC: 2: 0MB 3: 0MB
[  103.747789] EDAC amd64: MC: 4: 0MB 5: 0MB
[  103.747789] EDAC amd64: MC: 6: 0MB 7: 0MB
[  103.747791] EDAC MC: UMC1 chip selects:
[  103.747792] EDAC amd64: MC: 0: 16383MB 1: 16383MB
[  103.747793] EDAC amd64: MC: 2: 0MB 3: 0MB
[  103.747793] EDAC amd64: MC: 4: 0MB 5: 0MB
[  

Bug#950026: ser2net: communiction may hang when RFC2217 is used

[Heiko Thiery]

Package: ser2net
Version: 3.5-2
Severity: normal
Tags: upstream



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

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

Versions of packages ser2net depends on:
ii  libc6 2.28-10
ii  libwrap0  7.6.q-28
ii  lsb-base  10.2019051400

ser2net recommends no packages.

Versions of packages ser2net suggests:
ii  telnet  0.17-41.2

-- no debconf information

Bug#950028: nmu: nageru_1.9.1-1.1

[Steinar H. Gunderson]

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

nmu nageru_1.9.1-1.1 . armel armhf i386 mipsel . unstable . -m "rebuild against 
movit 1.6.3-5"

Hi,

I'm unsure if this should be a binNMU request or not, but please retry
nageru 1.9.1-1.1 (currently in Build-Attempted) on 32-bit platforms
armel, armhf, i386, mipsel; newer movit should work around some Mesa breakage
on such platforms.

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

Kernel: Linux 5.3.11 (SMP w/40 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NO:en_US:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#937061: Python3 Port of ModelBuilder

[Scott Talbert]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: model-builder -- RoQA; dead upstream; unmaintained; low 
popcon; blocking py2 removal

Bug#948123: svn-workbench: New version available

[Scott Talbert]

On Sat, 4 Jan 2020, Davide Prina wrote:


Package: svn-workbench
Version: 1.8.2-3
Severity: wishlist

Dear Maintainer,

I see that there is a new upstream version available[¹] and the project home 
page is changed [²].


This new version work also with Python3.

Ciao
Davide

[¹]
https://sourceforge.net/projects/pysvn/files/

[²]
https://pysvn.sourceforge.io/


Actually, pysyn is already packaged in Debian:
https://tracker.debian.org/pkg/pysvn

However, I think SCM Workbench is the successor to SVN Workbench:
http://scm-workbench.barrys-emacs.org/

So, probably svn-workbench should be RM'd and scm-workbench should be 
packaged as a new package.


Scott

Bug#950025: libasound2: using module-echo-cancel in 1.2.1-1 results in no input devices

[Jeffrey Ratcliffe]

Package: libasound2
Version: 1.1.9-1
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

Upgraded from 1.1.9-1 to 1.2.1-1

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

Used the following snipped in /etc/pulse/default.pa

.ifexists module-echo-cancel.so
load-module module-echo-cancel aec_method=webrtc
.endif

   * What was the outcome of this action?

After upgrading, no input devices were available

   * What outcome did you expect instead?

Downgrading back to 1.1.9-1 restored the microphones

Removing the module-echo-cancel line allows 1.2.1-1 to work, but without echo
cancellation.



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

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

Versions of packages libasound2 depends on:
hi  libasound2-data  1.1.9-1
ii  libc62.29-9

libasound2 recommends no packages.

Versions of packages libasound2 suggests:
hi  libasound2-plugins  1.1.9-1

-- no debconf information

Bug#950034: ITP: fonts-compagnon -- typeface family composed of five distinctive styles

[Gürkan Myczko]

Package: wnpp
Severity: wishlist

* Package name: fonts-compagnon
  Version : 0.2
  Upstream Authors: Juliette Duhé 
Léa Pradine 
Valentin Papon 
Sébastien Riollier 
Chloé Lozano 
* URL : https://gitlab.com/velvetyne/compagnon
* License : OFL-1.1
  Description : typeface family composed of five distinctive styles
 Font that finds its inspiration in the online archives of Typewriter 
Database

 specimens and combines different periods of the history of typewriter
 typefaces. Each weight is based on singular references relating to 
significant
 periods aiming to underline the evolution of typewriter characters as 
they are

 called.

Package is available at http://phd-sid.ethz.ch/debian/fonts-compagnon/

Bug#851747: sysvinit-utils: drop Essential flag

[Michael Biebl]

Am 28.01.20 um 16:38 schrieb Michael Biebl:

> And there is also
> /lib/init/init-d-script
> /lib/init/vars.sh
> 
> Those are the more tricky ones. A lot of init scripts use them.
> Not having those installed will render the init scripts of packages
> broken. It's less of an issue, if a package ships a native service file.

Assuming the .service isn't just a wrapper around the init script.
Unfortunately, we do have quite a few packages which use this
anti-pattern :-/

https://codesearch.debian.net/search?q=ExecStart%3D%2Fetc%2Finit.d%2F=1=1

Regards,
Michael



signature.asc
Description: OpenPGP digital signature

Bug#950012: RFP: rust-procfs -- Rust library for reading the Linux procfs filesystem

[Patrick Matthäi]

Package: wnpp
Severity: wishlist

* Package name: rust-procfs
  Version : 0.7.7
  Upstream Author : Andrew Chin 
* URL : https://github.com/eminence/procfs
* License : MIT OR Apache-2.0
  Programming Lang: Rust
  Description : Rust library for reading the Linux procfs filesystem

Bug#950011: RFP: rust-async-trait -- rust Async trait methods

[Patrick Matthäi]

Package: wnpp
Severity: wishlist

* Package name: rust-async-trait
  Version : 0.1.22
  Upstream Author : David Tolnay 
* URL : https://github.com/dtolnay/async-trait
* License : MIT OR Apache-2.0
  Programming Lang: Rust
  Description : rust Async trait methods

Bug#950015: haskell-hledger-lib: FTBFS on s390x

[Graham Inggs]

Source: haskell-hledger-lib
Version: 1.14.1-1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:haskell-hledger
Control: affects -1 + src:haskell-hledger-ui
Control: affects -1 + src:haskell-hledger-web

Hi Maintainer

Since the upload of haskell-hledger-lib 1.14.1-1, it has FTBFS on s390x.
Apparently timing out during the doctests.

✅  189 tests passed, no failures!  
Test suite easytests: PASS
Test suite logged to: dist-ghc/test/hledger-lib-1.14.1-easytests.log
Test suite doctests: RUNNING...
E: Build killed with signal TERM after 150 minutes of inactivity

Regards
Graham

Bug#950016: RFP: rust-pnet -- libpnet provides a cross-platform API for low level networking using Rust

[Patrick Matthäi]

Package: wnpp
Severity: wishlist

* Package name: rust-pnet
  Version : 0.25.0
  Upstream Author : Robert Clipsham 
* URL : https://github.com/libpnet/libpnet
* License : MIT/Apache-2.0
  Programming Lang: Rust
  Description : libpnet provides a cross-platform API for low level 
networking using Rust

Bug#950013: [Pkg-rust-maintainers] Bug#950013: RFP: rust-tokio-sync -- rust synchronization utilities

[Fabian Grünbichler]

On January 28, 2020 11:38 am, Patrick Matthäi wrote:
> Package: wnpp
> Severity: wishlist
> 
> * Package name: rust-tokio-sync
>   Version : 0.1.7
>   Upstream Author : Carl Lerche 
> * URL : https://crates.io/crates/tokio-sync
> * License : MIT
>   Programming Lang: Rust
>   Description : rust synchronization utilities
> 
> Maybe this is covered about the tokio+asnyc package? For bandwhich I explicit
> need tokio+sync.

tokio-sync is packaged already. if you need tokio+sync, you need to wait 
until the tokio transition to 0.2.x has happened[1], it will be provided 
by librust-tokio+fnv-dev. we'll likely attempt to finalize this MR on 
Friday at MiniDebCamp in Brussels, but it will take a while to go 
through NEW even then.

1: https://salsa.debian.org/rust-team/debcargo-conf/merge_requests/73

Bug#931255: Orphaning php-horde*

[Mike Gabriel]

Hi Johannes,

On  Di 28 Jan 2020 11:15:56 CET, IOhannes m zmölnig wrote:


On Sun, 13 Oct 2019 23:32:56 +0200 Mathieu Parent
 wrote:

Hello,

FYI, I'm orphaning php-horde-* packages. See:

https://bugs.debian.org/942282


if nobody objects, i'm going to do a QA-upload to buster/proposed-updates.

i've create a PR [2] for the relevant changes

fgmasdf
IOhannes

[2]
https://salsa.debian.org/horde-team/php-horde-text-filter/merge_requests/2


Please go ahead. I hopefully will be able to give some priority to  
picking up Horde in the next couple of weeks.


Mike
--

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

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



pgpQFg_qIj45M.pgp
Description: Digitale PGP-Signatur

Bug#948570:

[Helge Bahmann]

Verified working (with correct compiler version) -- tested with:

echo -e "#include \nTEST(foo, bar){}" | g++ -xc++ -
`pkg-config gtest_main --libs --cflags`