Bug#962170: gimp-plugin-registry: LQR (liquid rescale) does not work

2020-06-04 Thread jEsuSdA 8)

I tried to compile the sources from


https://github.com/carlobaldassi/gimp-lqr-plugin


And it works.

Please, consider to update.

Thanks a lot!!!



Bug#962214: Needles dependencies to policykit

2020-06-04 Thread Klaus Ethgen
Source: gparted
Version: 1.0.0-0.1
Severity: normal

Mark Hindley encuraged me to send this bug report even though I had
certain reserves.

gparted up to version 0.32.0-2 could have been installed without
policykit and the full dependencies up to systemd. With package
1.0.0-0.1, that changed with an hard dependency to policykit-1. This
drives that package somewhat unusable for me as I never want to have any
dbus based privileges escalation in my systems.

And I believe that dependency should be lowered to recommend as it is
not mandatory if the disk device is writable by the user (or the tool is
used as root but that would have other security concerns, running a GUI
tool as root).

It is not often that I use the GUI tool gparted but from time to time it
is very useful. So I would ask to lower that dependency to a recommend
only.

-- System Information:
Distributor ID: Devuan
Description:Devuan GNU/Linux 4 (chimaera/ceres)
Release:unstable
Codename:   sid
Architecture: x86_64

Kernel: Linux 5.6.7 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

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


signature.asc
Description: PGP signature


Bug#962213: package ftbfs on arm64 and armhf

2020-06-04 Thread Matthias Klose
Package: opencpn
Version: 5.0.0+dfsg-1
Severity: serious
Tags: sid bullseye patch

The package ftbfs on arm64 and armhf, trying to link with -ldrm. Apparently
libdrm-dev is an implicit b-d for x86 targets, but used explicitly.  Fixed by
b-d on libdrm-dev everywhere.



Bug#962191: [Pkg-javascript-devel] Bug#962191: Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Paolo Cavallini
> Also, check which packages Provide: nodejs on your system.

apt-cache showpkg nodejs

Provides:
10.20.1~dfsg-1+b1 -
10.20.1~dfsg-1 -
Reverse Provides:



Bug#962211: blobandconquer-data: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Attaching patch.


blobandconquer-dejavu-deps.debdiff
Description: Binary data


Bug#962212: buildstream: Missing recommends for git and ostree support

2020-06-04 Thread Ben Hutchings
Package: buildstream
Version: 1.4.1-1
Severity: important

Dear Maintainer,

I think buildstream should recommend:

* git (for the git plugin)
* python3-gi, gir1.2-ostree-1.0 (for the ostree plugin)

Please also check the run-time dependencies of other commonly used
plugins, which I think should be recommended.

Ben.

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

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

Versions of packages buildstream depends on:
ii  python3  3.8.2-3
ii  python3-buildstream  1.4.1-1

Versions of packages buildstream recommends:
ii  python3-bst-external  0.18.0-1

buildstream suggests no packages.

-- no debconf information

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom



Bug#962191: [Pkg-javascript-devel] Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Paolo Cavallini
> Please provide the output of this command:
> 
>   cat /etc/apt/sources.list sources.list.d/*

only
deb http://deb.debian.org/debian/ sid main non-free contrib
thanks



signature.asc
Description: OpenPGP digital signature


Bug#962211: blobandconquer-data: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Package: blobandconquer-data
Version: 1.11-dfsg+20-1.1
Severity: normal

Dear Maintainer,

blobandconquer-data depends on dummy transitional package ttf-dejavu-core, 
which was removed in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.



Bug#962191: [Pkg-javascript-devel] Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Jonas Smedegaard
Quoting Paolo Cavallini (2020-06-04 16:35:39)
> > Another idea: Which apt sources do your subscribe to?
> I tried two, see above

I think you misunderstood.

Please provide the output of this command:

  cat /etc/apt/sources.list sources.list.d/*


 - Jonas

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

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

signature.asc
Description: signature


Bug#962210: blobwars-data: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Attaching patch.


blobwars-dejavu-deps.debdiff
Description: Binary data


Bug#961439: buster-pu: package clamav/0.102.3+dfsg-0+deb10u1

2020-06-04 Thread Sebastian Andrzej Siewior
On 2020-06-01 18:52:49 [+0100], Adam D. Barratt wrote:
> 
> Were you assuming that libclamunrar would also be in that set, or just
> clamav itself?

Please go ahead with Clamav. I will ping the libclamunrar bug once it
got through NEW.

> Regards,
> 
> Adam

Sebastian



Bug#962186: [pkg-uWSGI-devel] Bug#962186: Bug#962186: uwsgi-plugin-php: CI fails with SIG_SEGV in bullseye

2020-06-04 Thread Jonas Smedegaard
Quoting Alexandre Rossi (2020-06-04 16:08:26)
> The problem seems to be that the PHP plugin is compiled against PHP7.4
> and is linked with libphp.so which points to 7.3 in bullseye and 7.4 in sid.
> 
> $ ldd /usr/lib/uwsgi/plugins/php_plugin.so | grep php
> libphp7.so => /usr/lib/libphp7.so (0x7f4b8ca48000)
> $ ls -l /usr/lib/libphp7.so
> lrwxrwxrwx 1 root root 25 mai   11 19:41 /usr/lib/libphp7.so -> 
> /etc/alternatives/libphp7
> $ ls -l /etc/alternatives/libphp7
> lrwxrwxrwx 1 root root 21 mai   11 19:41 /etc/alternatives/libphp7 -> 
> /usr/lib/libphp7.4.so
> 
> The php plugin should explicitly be linked against /usr/lib/libphp7.4.so

It seems uwsgi gets its information for which library to link against
from /usr/bin/php-config (see /usr/src/uwsgi/plugins/php/uwsgiplugin.py).

And it seems php-dev and php4.7-dev ships php-config* tools that (I guess)
both provides that name using the dpkg alternatives systems.

Try check if those varying build tools offer different build hints,
and if they do then try comeup with a patch for plugins/php/uwsgiplugin.py
to use php-config only by default, overridable by an environment variable.

If those picking the right build tool doesn't solve this,
then try come up with some other patch taking some other more direct
environment variable into account (look at other plugins and try mimic
upstream style, so that hopefully your patch can be adopted upstream).

Then we can have uwsgi-plugin-php pass a suitable environment variable
resolved at build time from the package pulled in by its build-dependency
on virtual package "php-dev".

 - Jonas

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

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

signature.asc
Description: signature


Bug#962210: blobwars-data: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Package: blobwars-data
Version: 2.00-1
Severity: normal

Dear Maintainer,

blobwars-data depends on dummy transitional package ttf-dejavu-core, which was 
removed in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.



Bug#961602: castle-game-engine-doc: Depends on removed ttf-dejavu packages

2020-06-04 Thread Olivier Tilloy
Submitted patch in the VCS:
https://salsa.debian.org/pascal-team/castle-game-engine/-/merge_requests/1


Bug#962152: buster-pu: package ca-certificates/20200601~deb10u1

2020-06-04 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Wed, 2020-06-03 at 16:14 -0500, Michael Shuler wrote:
> ca-certificates (20200601~deb10u1) buster; urgency=medium
> 
>* Rebuild for buster.
>* Merge changes from 20200601
>  - d/control; set d/gbp.conf branch to debian-buster
>* This release updates the Mozilla CA bundle to 2.40, blacklists
>  distrusted Symantec roots, and blacklists expired "AddTrust
> External
>  Root". Closes: #956411, #955038, #911289, #961907

Please go ahead.

Regards,

Adam



Bug#962155: stretch-pu: package ca-certificates/20200601~deb9u1

2020-06-04 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Wed, 2020-06-03 at 16:41 -0500, Michael Shuler wrote:
> ca-certificates (20200601~deb9u1) stretch; urgency=medium
> 
>* Rebuild for stretch.
>* Merge changes from 20200601
>  - d/control
>* This release updates the Mozilla CA bundle to 2.40, blacklists
>  distrusted Symantec roots, and blacklists expired "AddTrust
> External
>  Root". Closes: #956411, #955038, #911289, #961907
>* Fix permissions on /usr/local/share/ca-certificates when using 
> symlinks.
>  Closes: #916833
> 

Please go ahead.

Regards,

Adam



Bug#962160: buster-pu: package pagekite/0.5.9.3-2

2020-06-04 Thread Adam D. Barratt
Control: tags -1 + confirmed

On Wed, 2020-06-03 at 20:50 -0700, Sunil Mohan Adapa wrote:
> This update proposes to fix bug #961984. Pagekite shipped
> certificates internally which are now expired (as of 2020-05-31). All
> users of Pagekite are unable to use the package securely as it can no
> longer make TLS connections to frontend servers. This update makes
> Pagekite use Debian certificate database
> instead of internal certificates (by shipping an additional
> configuration file).

+pagekite (0.5.9.3-2+deb10u1) UNRELEASED; urgency=medium
+
+  * Fix issue with expired internal certificates. Use
+Debian certificates instead of internal certificate. (Closes:
#961984)

The distribution there needs to be "buster".

With that changed, please go ahead.

Regards,

Adam



Bug#962209: fix ftbfs with glibc-2.31

2020-06-04 Thread Matthias Klose
Package: src:lwipv6
Version: 1.5a-5
Severity: important
Tags: sid bullseye

fix ftbfs with glibc-2.31

patch at
http://launchpadlibrarian.net/482821761/lwipv6_1.5a-5_1.5a-5ubuntu1.diff.gz



Bug#962191: [Pkg-javascript-devel] Bug#962191: Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Jérémy Lal
Le jeu. 4 juin 2020 à 16:36, Paolo Cavallini  a
écrit :

> > Thanks - none of those revealed anything exciting.
>
> exactly
>
> > Another idea: Which apt sources do your subscribe to?
> I tried two, see above
>
> > Also, do you have any apt pinning configured?
> no
>

Also, check which packages Provide: nodejs on your system.

Jérémy


Bug#962208: fix ftbfs with glibc 2.31

2020-06-04 Thread Matthias Klose
Package: src:libtrace3
Version: 3.0.21-1
Severity: important
Tags: sid bullseye

fix ftbfs with glibc 2.31. patch at
http://launchpadlibrarian.net/482821079/libtrace3_3.0.21-1ubuntu4_3.0.21-1ubuntu5.diff.gz



Bug#962199: gnutls28 FTBFS when using the nocheck build profile

2020-06-04 Thread Andreas Metzler
On 2020-06-04 Helmut Grohne  wrote:
> Source: gnutls28
> Version: 3.6.13-4
> Tags: patch ftbfs
> User: helm...@debian.org
> Usertags: rebootstrap

> gnutls28 fails to build from source when activating the nocheck build
> profile, because it uses netstat, but the corresponding depdendency is
> conditional to the profile. Please consider applying the attached patch
> to fix the buile.
[...]

Sorry for that.

I will drop the whole block once I have managed for gnutls to not
heisen-FTBFS on regular builds on Debian buildds.

cu Andreas



Bug#962207: manaplus-data: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Attaching a patch.


manaplus-dejavu-deps.debdiff
Description: Binary data


Bug#962191: [Pkg-javascript-devel] Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Paolo Cavallini
> Thanks - none of those revealed anything exciting.

exactly

> Another idea: Which apt sources do your subscribe to?
I tried two, see above

> Also, do you have any apt pinning configured?
no



signature.asc
Description: OpenPGP digital signature


Bug#962191: [Pkg-javascript-devel] Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Jonas Smedegaard
Quoting Paolo Cavallini (2020-06-04 16:23:14)
> > Please share the full output of these two commands:
> > 
> >   apt update
> 
>  apt update
> Hit:1 http://deb.debian.org/debian sid InRelease
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> 3 packages can be upgraded. Run 'apt list --upgradable' to see them.

[details snipped]

Thanks - none of those revealed anything exciting.

Another idea: Which apt sources do your subscribe to?

Also, do you have any apt pinning configured?


 - Jonas

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

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

signature.asc
Description: signature


Bug#961013: diamond-aligner: Diamond faill with the error: Assertion `index >= 0 && index < size()' failed.

2020-06-04 Thread Andreas Tille
On Wed, Jun 03, 2020 at 10:36:39PM +0530, Pranav Ballaney wrote:
> I've narrowed the issue down to one (or a few) sequences. Basically this
> error occurs whenever a query sequence is less than five nucleotides (and
> is independent of the length of sequences in the database file). Besides,
> it's not specific to the Debian package. I encountered the same error when
> I compiled from the upstream source, but it went away when I downloaded the
> compiled binary, so it's probably something to do with the way it is
> compiled.
> 
> I've reported this on the Github issue page here
>  along with the smallest
> dataset that can be used to reproduce this issue. Maybe now we wait for
> upstream to take a look?

Thanks a lot.  That sounds extremely helpful and promising.

Kind regards

 Andreas.

-- 
http://fam-tille.de



Bug#962207: manaplus-data: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Package: manaplus-data
Version: 1.9.3.23-4
Severity: normal

Dear Maintainer,

manaplus-data depends on dummy transitional package ttf-dejavu-core, which was 
removed in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.



Bug#962190: primer3: please disable Big Endian tests on autopkgtests too

2020-06-04 Thread Gianfranco Costamagna
control: tags -1 patch

This might work better:

--- primer3-2.4.0/debian/tests/run-unit-test2018-05-28 15:44:30.0 
+0200
+++ primer3-2.4.0/debian/tests/run-unit-test2020-06-04 11:47:04.0 
+0200
@@ -8,6 +8,12 @@
   AUTOPKGTEST_TMP=`mktemp -d /tmp/${pkg}-test.XX`
 fi
 
+BUILDARCH=$(dpkg-architecture -q DEB_BUILD_ARCH_ENDIAN)
+
+P3CORE_FAILED_TESTS="primer_masker primer_masker_formatted"
+
+FAILED_TESTS="testmasker"
+
 cp -a /usr/share/doc/${pkg}/examples/* $AUTOPKGTEST_TMP
 
 cd $AUTOPKGTEST_TMP
@@ -19,6 +25,16 @@
 ln -s /usr/bin/ntthal ./src/ntthal
 ln -s /usr/bin/oligotm ./src/oligotm
 
+if [ $BUILDARCH = big ]; then
+  cp -a test/p3test.pl test/p3test.pl~
+  cp -a test/Makefile test/Makefile~
+  # exclude tests known to fail on big endian
+  # See README.source for further explanation.
+  for tst in $P3CORE_FAILED_TESTS ; do sed -i "/$tst/d" test/p3test.pl ; done
+  sed -i "0,/$FAILED_TESTS/s///" test/Makefile
+  sed -i "/$FAILED_TESTS/,/endif/d" test/Makefile
+fi
+
 cd test/;
 
 echo "testcmdline:"
@@ -36,4 +52,12 @@
 echo "testtm:"
 perl oligotm_test.pl ${TESTOPTS}
 
+cd ..
+
+if [ $BUILDARCH = big ]; then
+  # restore original test file
+  mv test/p3test.pl~ test/p3test.pl
+  mv test/Makefile~ test/Makefile
+fi
+
 echo "PASS"



Bug#962197: buildstream: Event loop broken on Python 3.8

2020-06-04 Thread Ben Hutchings
Control: tag -1 upstream fixed-upstream patch

Although there are still some issues with 3.8 upstream, this one is
actually fixed.  Here's the patch.

Ben.

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom
From: Chandan Singh 
Date: Mon, 21 Oct 2019 14:38:07 +0100
Subject: _scheduler/scheduler.py: Enforce SafeChildWatcher
Origin: https://gitlab.com/BuildStream/buildstream/-/commit/0eca9e6a4a01d1094987773bce58d9d3e501f1e8
Bug-Debian: https://bugs.debian.org/962197

In Python 3.8, `ThreadedChildWatcher` is the default watcher that causes
issues with our scheduler. Enforce use of `SafeChildWatcher`.

[benh: Backported to 1.4.1: adjust filename]
---
 buildstream/_scheduler/scheduler.py | 6 ++
 1 file changed, 6 insertions(+)

--- a/buildstream/_scheduler/scheduler.py
+++ b/buildstream/_scheduler/scheduler.py
@@ -137,6 +137,12 @@ class Scheduler():
 # Hold on to the queues to process
 self.queues = queues
 
+# NOTE: Enforce use of `SafeChildWatcher` as we generally don't want
+# background threads.
+# In Python 3.8+, `ThreadedChildWatcher` is the default watcher, and
+# not `SafeChildWatcher`.
+asyncio.set_child_watcher(asyncio.SafeChildWatcher())
+
 # Ensure that we have a fresh new event loop, in case we want
 # to run another test in this thread.
 self.loop = asyncio.new_event_loop()


Bug#890993: fixed in primer3 2.4.0-2

2020-06-04 Thread Gianfranco Costamagna
control: close -1

Lets close, I opened a new one in the meanwhile

G.



Bug#962206: linux-image-4.19.0-8-amd64: Debian Buster Machine Kernel Panics (consistently) after resume from suspend

2020-06-04 Thread Markus Bawidamann
Package: src:linux
Version: 4.19.98-1
Severity: normal

This is on a Dell Latitude E6540 Laptop. I have noticed intermittent crashes
after resuming from suspend for Buster for a long time. Now, with this kernel
Version, they are reproducible, so it panics every time I resume from suspend.
(Machine freezes with a black screen and is non responsive)



-- Package-specific info:
** Version:
Linux version 4.19.0-8-amd64 (debian-ker...@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.98-1 (2020-01-26)

** Command line:
BOOT_IMAGE=/vmlinuz-4.19.0-8-amd64 root=/dev/mapper/california--vg-root ro quiet

** Tainted: OE (12288)
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[   15.009223] [drm] ring test on 3 succeeded in 4 usecs
[   15.009228] [drm] ring test on 4 succeeded in 3 usecs
[   15.185269] [drm] ring test on 5 succeeded in 2 usecs
[   15.185274] [drm] UVD initialized successfully.
[   15.185427] [drm] ib test on ring 0 succeeded in 0 usecs
[   15.185460] [drm] ib test on ring 1 succeeded in 0 usecs
[   15.185510] [drm] ib test on ring 2 succeeded in 0 usecs
[   15.185543] [drm] ib test on ring 3 succeeded in 0 usecs
[   15.185591] [drm] ib test on ring 4 succeeded in 0 usecs
[   15.446951] media: Linux media interface: v0.10
[   15.462089] videodev: Linux video capture interface: v2.00
[   15.485052] audit: type=1400 audit(1591277410.601:2): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/snapd/snap-confine" pid=968 comm="apparmor_parser"
[   15.485055] audit: type=1400 audit(1591277410.601:3): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=968 
comm="apparmor_parser"
[   15.485857] audit: type=1400 audit(1591277410.601:4): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" 
pid=969 comm="apparmor_parser"
[   15.489778] audit: type=1400 audit(1591277410.605:5): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/sbin/libvirtd" pid=967 
comm="apparmor_parser"
[   15.489781] audit: type=1400 audit(1591277410.605:6): apparmor="STATUS" 
operation="profile_load" profile="unconfined" 
name="/usr/sbin/libvirtd//qemu_bridge_helper" pid=967 comm="apparmor_parser"
[   15.491119] audit: type=1400 audit(1591277410.605:7): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=974 
comm="apparmor_parser"
[   15.491122] audit: type=1400 audit(1591277410.605:8): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_filter" pid=974 
comm="apparmor_parser"
[   15.491124] audit: type=1400 audit(1591277410.605:9): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="man_groff" pid=974 
comm="apparmor_parser"
[   15.492489] audit: type=1400 audit(1591277410.605:10): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="libreoffice-oopslash" 
pid=975 comm="apparmor_parser"
[   15.495550] audit: type=1400 audit(1591277410.609:11): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="virt-aa-helper" pid=970 
comm="apparmor_parser"
[   15.636579] uvcvideo: Found UVC 1.00 device Laptop_Integrated_Webcam_HD 
(1bcf:2c34)
[   15.653520] uvcvideo 1-1.5:1.0: Entity type for entity Extension 4 was not 
initialized!
[   15.653523] uvcvideo 1-1.5:1.0: Entity type for entity Extension 3 was not 
initialized!
[   15.653525] uvcvideo 1-1.5:1.0: Entity type for entity Processing 2 was not 
initialized!
[   15.653526] uvcvideo 1-1.5:1.0: Entity type for entity Camera 1 was not 
initialized!
[   15.653613] input: Laptop_Integrated_Webcam_HD: In as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input19
[   15.653697] usbcore: registered new interface driver uvcvideo
[   15.653698] USB Video Class driver (1.1.1)
[   15.841076] [drm] ib test on ring 5 succeeded
[   15.841353] [drm] Radeon Display Connectors
[   15.841354] [drm] Connector 0:
[   15.841354] [drm]   VGA-2
[   15.841355] [drm]   DDC: 0x65c0 0x65c0 0x65c4 0x65c4 0x65c8 0x65c8 0x65cc 
0x65cc
[   15.841356] [drm]   Encoders:
[   15.841356] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   15.899551] Console: switching to colour frame buffer device 240x67
[   15.920051] i915 :00:02.0: fb0: inteldrmfb frame buffer device
[   15.933353] [drm] Cannot find any crtc or sizes
[   15.936260] [drm] Initialized radeon 2.50.0 20080528 for :01:00.0 on 
minor 1
[   15.967453] input: HDA Intel HDMI HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.0/sound/card0/input20
[   15.967524] input: HDA Intel HDMI HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.0/sound/card0/input21
[   15.967583] input: HDA Intel HDMI HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.0/sound/card0/input22
[   15.967638] input: HDA Intel HDMI HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.0/sound/card0/input23
[   15.967697] input: HDA Intel HDMI 

Bug#962205: buildstream: Missing dependency on bubblewrap

2020-06-04 Thread Ben Hutchings
Package: buildstream
Version: 1.4.1-1
Severity: serious

Dear Maintainer,

bubblewrap is a run-time dependency for BuildStream on Linux, but is
not included in the package dependencies.

Ben.

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

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

Versions of packages buildstream depends on:
ii  python3  3.8.2-3
ii  python3-buildstream  1.4.1-1

Versions of packages buildstream recommends:
ii  python3-bst-external  0.18.0-1

buildstream suggests no packages.

-- no debconf information

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom



Bug#962204: dhcp-helper and the PID file error

2020-06-04 Thread Aladdin
Package: dhcp-helper
Version: 1.2-1+b1
Severity: normal

Dear Maintainer,

Installed this package on fresh Buster installation and everytime, when I start 
the server, systemd complains about lac of PID file. Is it possible to fix this?

Jun 04 14:18:13 zeta systemd[1]: Starting DHCP/BOOTP relay agent...
Jun 04 14:18:14 zeta systemd[1]: dhcp-helper.service: Can't open PID file 
/run/dhcp-helper.pid (yet?) after start: No such file or directory
Jun 04 14:18:14 zeta systemd[1]: Started DHCP/BOOTP relay agent.

Another thing is that the service file must be updated from /var/run to only 
/run as I get constant complains about this path.

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

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

Versions of packages dhcp-helper depends on:
ii  libc62.28-10
ii  netbase  5.6

dhcp-helper recommends no packages.

dhcp-helper suggests no packages.

-- Configuration Files:
/etc/default/dhcp-helper changed [not included]

-- no debconf information



Bug#961738: RFS: dragengine/1.1 -- Drag[en]gine Game Engine

2020-06-04 Thread Roland Plüss

On 6/2/20 1:05 PM, Tobias Frost wrote:
> On Mon, Jun 01, 2020 at 04:13:33PM +0200, Roland Plüss wrote:
>> On 5/31/20 9:19 AM, Tobias Frost wrote:
> (...) 
>
>>> It seems at first glance possible that both versions can be in Debian,
>>> however, the release/security team will not be happy to have both of
>>> them in a stable release, IOW, having two versions can only be a
>>> intermediate solution until all reverse dependencies of 1.6* have been
>>> updated (by patching the respective Debian packages.) More about such
>>> library transision:
>>> https://wiki.debian.org/Teams/ReleaseTeam/Transitions
>>>
>> FOX-1.7 and FOX-1.6 are not compatible (well, mostly yes but in
>> important things not). That said they are different libraries with
>> separate include and library names (/usr/include/fox-1.6 vs
>> /usr/include/fox-1.7 and the same for libraries). So technically
>> applications linking against FOX-1.6 do not have to be change if FOX-1.7
>> is added on the same system (the two can coexist). But it depends if two
>> library versions of the same library are accepted even if they are disjoint.
> Those versions are not disjoint, the new version is just an evolution of the
> old one.
>
>
> Incompatible ABI changes is nothing special and happens all the time in Debian
> (called library transistios). As I tried to explain earlier, the maintainer
> duty is to resolve this by a transistion when updating the library.
>
> For you, hat means you need either 1.6 for code base or you need to help that
> all of Debian is using 1.7. You can't have both versions in Debian…
>
I don't see any way for me to get other projects to update to 1.7 . FOX
separates 1.7 from 1.6 so projects are not forced to upgrade if they
don't want to.

I can try ask the maintainer but I consider this a 0% success rate.

-- 
Mit freundlichen Grüssen
Plüss Roland

Game Development and Game Engine Technologies https://dragondreams.ch



signature.asc
Description: OpenPGP digital signature


Bug#962201: natbraille: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Submitted patch to the VCS:
https://salsa.debian.org/a11y-team/natbraille/-/merge_requests/1


Bug#962191: [Pkg-javascript-devel] Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Paolo Cavallini
> Please share the full output of these two commands:
> 
>   apt update

 apt update
Hit:1 http://deb.debian.org/debian sid InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
3 packages can be upgraded. Run 'apt list --upgradable' to see them.

>   apt install nodejs

apt install nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package nodejs is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  nodejs-doc

E: Package 'nodejs' has no installation candidate

>> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> 
> Which out-of-tree kernel modules do you have installed?

it should be rtlwifi

>> Versions of packages nodejs depends on:
>> ii  libc6  2.30-8
>> ii  libnode64  10.20.1~dfsg-1
> 
> The nodejs library is installed and up-to-date.

as mentioned, I dowloaded the deb and dpkg -i

>> Versions of packages nodejs suggests:
>> ii  npm  6.14.5+ds-1
> 
> You have npm installed.  Please triple-check that it hasn't
> messed up your system - check e.g. files below /usr/local and
> environment variables...

I don't think so: I had the same problem before installing npm.
removing it does not change



signature.asc
Description: OpenPGP digital signature


Bug#962201: natbraille: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Source: natbraille
Version: 2.0rc3-8
Severity: normal

Dear Maintainer,

natbraille depends on dummy transitional package ttf-dejavu-core, which was 
removed in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.



Bug#962203: DeprecationWarning: isAlive() is deprecated, use is_alive() instead

2020-06-04 Thread Nelson A. de Oliveira
Package: debdelta
Version: 0.65
Severity: normal

Hi!

It seems that something needs to be update in debdelta:

=
# debdelta-upgrade
Created,time  0.15sec, speed 151kB/sec, libmtdev1_1.1.6-1_amd64.deb
Downloaded, time  0.47sec, speed 83kB/sec, 
libcryptsetup12_2%3a2.3.2-1_2%3a2.3.3-1_amd64.debdelta
Created,time  0.33sec, speed 709kB/sec, 
libcryptsetup12_2%3a2.3.3-1_amd64.deb
Downloaded, time  0.41sec, speed 104kB/sec, 
calibre-bin_4.99.4+dfsg+really4.17.0-1_4.99.4+dfsg+really4.17.0-1+b1_amd64.debdelta
Created,time  2.09sec, speed 375kB/sec, 
calibre-bin_4.99.4+dfsg+really4.17.0-1+b1_amd64.deb
Downloaded, time  2.38sec, speed 206kB/sec, 
libqt5gui5_5.12.5+dfsg-10_5.12.5+dfsg-10+b1_amd64.debdelta
/usr/bin/debdelta-upgrade:5384: DeprecationWarning: isAlive() is deprecated, 
use is_alive() instead
  if patching_thread.isAlive() and no_delta and VERBOSE > 1 :
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated, 
use is_alive() instead
  while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated, 
use is_alive() instead
  while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
Created,time  6.01sec, speed 484kB/sec, 
libqt5gui5_5.12.5+dfsg-10+b1_amd64.deb
/usr/bin/debdelta-upgrade:5405: DeprecationWarning: isAlive() is deprecated, 
use is_alive() instead
  while patching_thread.isAlive():
/usr/bin/debdelta-upgrade:5410: DeprecationWarning: isAlive() is deprecated, 
use is_alive() instead
  while progress_thread != None and progress_thread.isAlive():
Delta-upgrade statistics:
 total resulting debs, size 3956kB time 11sec virtual speed 340kB/sec
=

Thank you!

Best regards,
Nelson

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

Kernel: Linux 5.6.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), 
LANGUAGE=pt_BR:pt:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debdelta depends on:
ii  binutils  2.34-8
ii  bzip2 1.0.8-3
ii  libbz2-1.01.0.8-3
ii  libc6 2.30-8
ii  python3   3.8.2-3
ii  python3-requests  2.23.0+dfsg-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages debdelta recommends:
ii  bsdiff   4.3-21+b1
ii  gnupg-agent  2.2.20-1
ii  gnupg2   2.2.20-1
ii  gpg-agent [gnupg-agent]  2.2.20-1
ii  python3-apt  2.1.3
ii  python3-debian   0.1.37
pn  xdelta   
ii  xdelta3  3.0.11-dfsg-1+b1
ii  xz-utils [lzma]  5.2.4-1+b1

Versions of packages debdelta suggests:
pn  debdelta-doc  

-- no debconf information



Bug#960984: ITP: google-http-client-java -- Google HTTP Client Library for Java

2020-06-04 Thread Olek Wojnar
Hi Sudip,

On Thu, Jun 4, 2020 at 8:30 AM Sudip Mukherjee 
wrote:

> Sorry, I think I am missing something. To build http-java-client you
> should only need "api" and "contrib/http_util" from opencensus-java
> which (iiuc) does not need google-auth.
>

Hmm, I think you're right. Good catch and thanks!

Andreas, since you were working on opencensus, do you want to check if this
will work? I'm going to push an alternate packaging paradigm to Salsa
shortly for your reference.

-Olek


Bug#962202: socket-activate: name is too generic

2020-06-04 Thread Dimitri John Ledkov
Package: socket-activate
Version: 0.1-2
Severity: important

Dear Maintainer,

socket-activate is too generic name of the package and the binary it
ships. In Debian, we have or had other alternative implementations of
the same functionality. Shipped either stand alone, or as part of
other packages.

For exmaple systemd-socket-activate upstart-socket-bridge and others.

Using generic name socket-activate, which is a different
implementation to the other utilities and without argument
compatibility with them is ill-advised. Please consider renaming the
package and the binary to something that is more unique. For example,
python-socket-activate or some such.


Or maybe even call it heavy-standalone-socket-activate?! Socket
activate wrappers are typically used to reduce resources, such that at
idle it is desired for socket activation wrapper to use as little
resources as possible. That is the case with
systemd/upstart/launchd/xinitd/etc. Loading a full blown python3
interpreter does not seem appropriate per each socket and daemon. Have
you considered implementing this in something more optimized? for
example pypy, cpy, rust, C? Or at least allow socket-activate to
listen on many sockets and launch correspending daemon for each?


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

Kernel: Linux 5.4.0-33-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_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



Bug#962200: sarg: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Submitted patch in the VCS:
https://salsa.debian.org/debian/sarg/-/merge_requests/1


Bug#962191: [Pkg-javascript-devel] Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Jonas Smedegaard
Quoting Paolo Cavallini (2020-06-04 14:06:30)
> Package: nodejs
> Version: 10.20.1~dfsg-1
> Severity: important
> 
> Dear Maintainer,
> 
> apt install nodejs
> returns
> Package 'nodejs' has no installation candidate

Please share the full output of these two commands:

  apt update

  apt install nodejs


> Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE

Which out-of-tree kernel modules do you have installed?


> Versions of packages nodejs depends on:
> ii  libc6  2.30-8
> ii  libnode64  10.20.1~dfsg-1

The nodejs library is installed and up-to-date.


> Versions of packages nodejs suggests:
> ii  npm  6.14.5+ds-1

You have npm installed.  Please triple-check that it hasn't
messed up your system - check e.g. files below /usr/local and
environment variables...


 - Jonas

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

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

signature.asc
Description: signature


Bug#962186: [pkg-uWSGI-devel] Bug#962186: uwsgi-plugin-php: CI fails with SIG_SEGV in bullseye

2020-06-04 Thread Alexandre Rossi
The problem seems to be that the PHP plugin is compiled against PHP7.4
and is linked with libphp.so which points to 7.3 in bullseye and 7.4 in sid.

$ ldd /usr/lib/uwsgi/plugins/php_plugin.so | grep php
libphp7.so => /usr/lib/libphp7.so (0x7f4b8ca48000)
$ ls -l /usr/lib/libphp7.so
lrwxrwxrwx 1 root root 25 mai   11 19:41 /usr/lib/libphp7.so -> 
/etc/alternatives/libphp7
$ ls -l /etc/alternatives/libphp7
lrwxrwxrwx 1 root root 21 mai   11 19:41 /etc/alternatives/libphp7 -> 
/usr/lib/libphp7.4.so

The php plugin should explicitly be linked against /usr/lib/libphp7.4.so



Bug#962185: inkscape: Document properties dialog is too small and not resizable

2020-06-04 Thread Michel Le Bihan
Package: inkscape
Version: 1.0-1
Severity: normal
Tags: upstream

The issue is already being tracked upstream:
https://gitlab.com/inkscape/inkscape/-/issues/1343



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

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

Versions of packages inkscape depends on:
ii  libatkmm-1.6-1v5   2.28.0-2
ii  libc6  2.30-8
ii  libcairo2  1.16.0-4
ii  libcairomm-1.0-1v5 1.12.2-4
ii  libcdr-0.1-1   0.1.6-1
ii  libdbus-glib-1-2   0.110-5
ii  libdouble-conversion3  3.1.5-5
ii  libfontconfig1 2.13.1-4.2
ii  libfreetype6   2.10.1-2
ii  libgc1c2   1:7.6.4-0.4
ii  libgcc-s1  10.1.0-3
ii  libgdk-pixbuf2.0-0 2.40.0+dfsg-4
ii  libgdl-3-5 3.34.0-1
ii  libglib2.0-0   2.64.3-1
ii  libglibmm-2.4-1v5  2.64.2-1
ii  libgomp1   10.1.0-3
ii  libgsl25   2.6+dfsg-2
ii  libgtk-3-0 3.24.20-1
ii  libgtkmm-3.0-1v5   3.24.2-1
ii  libgtkspell3-3-0   3.0.10-1
ii  libharfbuzz0b  2.6.4-1
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  liblcms2-2 2.9-4+b1
ii  libmagick++-6.q16-88:6.9.10.23+dfsg-2.1+b2
ii  libpango-1.0-0 1.44.7-4
ii  libpangocairo-1.0-01.44.7-4
ii  libpangoft2-1.0-0  1.44.7-4
ii  libpangomm-1.4-1v5 2.42.1-1
ii  libpng16-161.6.37-2
ii  libpoppler-glib8   0.71.0-6
ii  libpoppler82   0.71.0-6
ii  libpotrace01.16-2
ii  librevenge-0.0-0   0.0.4-6+b1
ii  libsigc++-2.0-0v5  2.10.2-1
ii  libsoup2.4-1   2.70.0-1
ii  libstdc++6 10.1.0-3
ii  libvisio-0.1-1 0.1.7-1
ii  libwpg-0.3-3   0.3.3-1
ii  libx11-6   2:1.6.9-2+b1
ii  libxml22.9.10+dfsg-5
ii  libxslt1.1 1.1.34-4
ii  python33.8.2-3
ii  zlib1g 1:1.2.11.dfsg-2

Versions of packages inkscape recommends:
ii  aspell   0.60.8-1
ii  fig2dev  1:3.2.7b-4
ii  imagemagick  8:6.9.10.23+dfsg-2.1+b2
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1+b2
ii  libimage-magick-perl 8:6.9.10.23+dfsg-2.1
ii  libwmf-bin   0.2.8.4-17
ii  python3-lxml 4.5.0-1.1
ii  python3-numpy1:1.17.4-5
ii  python3-scour0.37-4

Versions of packages inkscape suggests:
pn  dia   
pn  inkscape-tutorials
pn  libsvg-perl   
pn  libxml-xql-perl   
ii  pstoedit  3.75-1
pn  python3-uniconvertor  
ii  ruby  1:2.7+1

-- no debconf information



Bug#962200: sarg: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Package: sarg
Version: 2.4.0-1
Severity: normal

Dear Maintainer,

sarg depends on dummy transitional package ttf-dejavu-core, which was removed 
in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.



Bug#962198: scilab-test: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Submitted patch in the VCS:
https://salsa.debian.org/science-team/scilab/-/merge_requests/4


Bug#962199: gnutls28 FTBFS when using the nocheck build profile

2020-06-04 Thread Helmut Grohne
Source: gnutls28
Version: 3.6.13-4
Tags: patch ftbfs
User: helm...@debian.org
Usertags: rebootstrap

gnutls28 fails to build from source when activating the nocheck build
profile, because it uses netstat, but the corresponding depdendency is
conditional to the profile. Please consider applying the attached patch
to fix the buile.

Helmut
diff --minimal -Nru gnutls28-3.6.13/debian/changelog 
gnutls28-3.6.13/debian/changelog
--- gnutls28-3.6.13/debian/changelog2020-06-01 10:34:25.0 +0200
+++ gnutls28-3.6.13/debian/changelog2020-06-04 05:59:42.0 +0200
@@ -1,3 +1,10 @@
+gnutls28 (3.6.13-4.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTFBS with nocheck build profile. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 04 Jun 2020 05:59:42 +0200
+
 gnutls28 (3.6.13-4) unstable; urgency=medium
 
   * Output some network related debugging from debian/rules.
diff --minimal -Nru gnutls28-3.6.13/debian/rules gnutls28-3.6.13/debian/rules
--- gnutls28-3.6.13/debian/rules2020-06-01 10:03:00.0 +0200
+++ gnutls28-3.6.13/debian/rules2020-06-04 05:59:40.0 +0200
@@ -102,11 +102,13 @@
dh_compress $(BDIR) -X.pdf
 
 override_dh_auto_test:
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
@echo DEBUG info about network setup starts ...
if test -x /sbin/ifconfig ; then /sbin/ifconfig ; else true ; fi
netstat -tln
@echo ... DEBUG info about network setup ends.
dh_auto_test $(BDIR) --verbose -- VERBOSE=1
+endif
 
 override_dh_clean:
dh_clean $(BDIR) -X.bak


Bug#962191:

2020-06-04 Thread Jérémy Lal
Le jeu. 4 juin 2020 à 15:48, Paolo Cavallini  a
écrit :

> > What mirror did you test ?
> deb http://deb.debian.org/debian/ sid main non-free contrib
> deb http://ftp.it.debian.org/debian/ sid main non-free contrib
>
> > Can you see nodejs 10.20.1~dfsg-1+b1 ?
> apt show nodejs
> Package: nodejs
> State: not a real package (virtual)
> N: Can't select candidate version from package nodejs as it has no
> candidate
> N: There are 2 additional records. Please use the '-a' switch to see them.
> N: No packages found
>
> > Did you run apt update ?
> Yes, I can install and update all other packages since many years
>

Just to be sure: you reported the bug from the same machine (amd64 arch) ?


Bug#962198: scilab-test: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Package: scilab-test
Version: 6.1.0+dfsg1-3
Severity: normal

Dear Maintainer,

scilab-test depends on dummy transitional package ttf-dejavu-core, which was 
removed in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.



Bug#921469: enigma: depends on dummy transitional packages ttf-dejavu-{core,extra}

2020-06-04 Thread Olivier Tilloy
Attaching an updated patch that also updates the symlinks.

>


enigma-dejavu-deps2.debdiff
Description: Binary data


Bug#962191: (no subject)

2020-06-04 Thread Paolo Cavallini
> What mirror did you test ? 
deb http://deb.debian.org/debian/ sid main non-free contrib
deb http://ftp.it.debian.org/debian/ sid main non-free contrib

> Can you see nodejs 10.20.1~dfsg-1+b1 ?
apt show nodejs
Package: nodejs
State: not a real package (virtual)
N: Can't select candidate version from package nodejs as it has no candidate
N: There are 2 additional records. Please use the '-a' switch to see them.
N: No packages found

> Did you run apt update ?
Yes, I can install and update all other packages since many years



Bug#962196: singularity: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
I am attaching a patch.


singularity-dejavu-deps.debdiff
Description: Binary data


Bug#962197: buildstream: Event loop broken on Python 3.8

2020-06-04 Thread Ben Hutchings
Package: buildstream
Version: 1.4.1-1
Severity: grave

Dear Maintainer,

Un-cached builds with builstream currently fail like this:

[--:--:--][][] BUG no running event loop

Traceback (most recent call last):
  File "/usr/bin/bst", line 8, in 
sys.exit(cli())
  File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__
return self.main(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/buildstream/_frontend/cli.py", line 
173, in override_main
original_main(self, args=args, prog_name=prog_name, complete_var=None,
  File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main
rv = self.invoke(ctx)
  File "/usr/lib/python3/dist-packages/click/core.py", line 1137, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke
return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke
return callback(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/click/decorators.py", line 27, in 
new_func
return f(get_current_context().obj, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/buildstream/_frontend/cli.py", line 
340, in build
app.stream.build(elements,
  File "/usr/lib/python3/dist-packages/buildstream/_stream.py", line 211, 
in build
self._run()
  File "/usr/lib/python3/dist-packages/buildstream/_stream.py", line 1022, 
in _run
_, status = self._scheduler.run(self.queues)
  File 
"/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 153, 
in run
self._sched()
  File 
"/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 427, 
in _sched
self._sched_queue_jobs()
  File 
"/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 401, 
in _sched_queue_jobs
self._spawn_job(job)
  File 
"/usr/lib/python3/dist-packages/buildstream/_scheduler/scheduler.py", line 281, 
in _spawn_job
job.spawn()
  File "/usr/lib/python3/dist-packages/buildstream/_scheduler/jobs/job.py", 
line 162, in spawn
self._watcher.add_child_handler(self._process.pid, 
self._parent_child_completed)
  File "/usr/lib/python3.8/asyncio/unix_events.py", line 1293, in 
add_child_handler
loop = events.get_running_loop()
RuntimeError: no running event loop

This was reported upstream as:
https://gitlab.com/BuildStream/buildstream/-/issues/1246

but is now tracked in:
https://gitlab.com/BuildStream/buildstream/-/issues/1173

Ben.

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

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

Versions of packages buildstream depends on:
ii  python3  3.8.2-3
ii  python3-buildstream  1.4.1-1

Versions of packages buildstream recommends:
ii  python3-bst-external  0.18.0-1

buildstream suggests no packages.

-- no debconf information

-- 
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
 Manchester, M1 2HF, United Kingdom



Bug#962196: singularity: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Package: singularity
Version: 1.0b1-2
Severity: normal

Dear Maintainer,

singularity depends on dummy transitional package ttf-dejavu-core, which was 
removed in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.

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

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

Versions of packages singularity depends on:
ii  python3  3.8.2-0ubuntu2
ii  python3-numpy1:1.17.4-5ubuntu3
pn  python3-polib
pn  python3-pygame   
ii  ttf-dejavu-core  2.37-1

Versions of packages singularity recommends:
pn  singularity-music  

Versions of packages singularity suggests:
pn  timidity  



Bug#961863: zatacka: Depends/Build-Depends on cruft package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Patch submitted to the VCS:
https://github.com/alexdantas/zatacka.debian/pull/3


Bug#962134: [External] Re: Bug#962134: add Sound Open Firmware

2020-06-04 Thread Mark Pearson



On 6/4/2020 4:56 AM, Paul Wise wrote:

On Wed, 2020-06-03 at 21:34 -0400, Mark Pearson wrote:


Hi Paul - I'm afraid it does (not something of Lenovo's choosing to my
knowledge...).


Interesting, is it Intel doing the restrictions on Lenovo hardware?
ISTR reading on one of the bugs that some hardware doesn't have the
restrictions, so it is strange that Intel restricts some hardware
vendors but not others. If you are able to push back on these Intel
restrictions, it would be very much appreciated.


I'll see what I can find out.






I know the SOF team wanted to work with Debian on this issue a few
months ago - I will dig up that email and point them at this bug so they
can contribute to the conversation without me muddying the waters about
their decisions (I was on their mailing list but not involved in the
decision making)


Interesting, thanks for that.

OK - I have asked the SOF folk to talk to you about this. I'll unicast 
you the email address so you have the correct contact details too.




Bug#962195: astromenace: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Patch submitted as a merge request in salsa:
https://salsa.debian.org/games-team/astromenace/-/merge_requests/1


Bug#961653: libguestfs: FTBFS with Erlang 23

2020-06-04 Thread Sergei Golovan
Hi Hilko,

On Wed, May 27, 2020 at 10:55 PM Hilko Bengen  wrote:
>
> * Sergei Golovan:
>
> > I'd like to upload Erlang 23 for the bullseye release, but it makes
> > libguestfs fail to build from source, because it uses liberl_interface
> > which has been removed from the Erlang distribution.
>
> After briefly chatting with Richard, I have decided to disable building
> the Erlang binding, as it has been done for Fedora.

I've helped a little bit in porting erlang-guestfs to Erlang 23 (see
[1]), so hopefully, you'll
be able to restore the functionality in the future, after it'll make
into a release.

[1] 
https://github.com/libguestfs/libguestfs/commit/987734fcca101cf782264756f7883cf48430a91b

Cheers!
-- 
Sergei Golovan



Bug#962191: [Pkg-javascript-devel] Bug#962191: (no subject)

2020-06-04 Thread Jérémy Lal
Le jeu. 4 juin 2020 à 15:00, Paolo Cavallini  a
écrit :

> anything I could to for deeper testing?
>

I don't really know. It's unrelated to nodejs, more something about mirrors
or apt.
What mirror did you test ?
Can you see nodejs 10.20.1~dfsg-1+b1 ?
Did you run apt update ?


Bug#962195: astromenace: depends on dummy transitional package ttf-dejavu-core

2020-06-04 Thread Olivier Tilloy
Package: astromenace
Version: 1.3.2+repack-6
Severity: normal

Dear Maintainer,

astromenace depends on dummy transitional package ttf-dejavu-core, which was 
removed in fonts-dejavu 2.37-2 (#872809).
The dependency name should be updated to fonts-dejavu-core.

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

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

Versions of packages astromenace depends on:
pn  astromenace-data-src
ii  fonts-freefont-ttf  20120503-10
ii  fonts-liberation1:1.07.4-11
pn  fonts-linuxlibertine
pn  libalut0
ii  libc6   2.31-0ubuntu9
ii  libfontconfig1  2.13.1-2ubuntu3
ii  libfreetype62.10.1-2
ii  libgcc-s1   10-20200411-0ubuntu1
ii  libgl1  1.3.1-1
ii  libglu1-mesa [libglu1]  9.0.1-1build1
ii  libopenal1  1:1.19.1-1
ii  libsdl1.2debian 1.2.15+dfsg2-5
ii  libstdc++6  10-20200411-0ubuntu1
ii  libvorbisfile3  1.3.6-2ubuntu1
ii  libx11-62:1.6.9-2ubuntu1
ii  libxinerama12:1.1.4-2
ii  ttf-dejavu-core 2.37-1
ii  xz-utils5.2.4-1

astromenace recommends no packages.

astromenace suggests no packages.



Bug#962191: (no subject)

2020-06-04 Thread Paolo Cavallini
anything I could to for deeper testing?



Bug#962151: Failure to save: unitialized value $SETTINGS{"ps_backend"}

2020-06-04 Thread Jeff
Thanks for the report.

This fixes things for me. I'll release it next week.

Regards

Jeff
diff --git a/bin/gscan2pdf b/bin/gscan2pdf
index f2e8d492..d81a12d3 100755
--- a/bin/gscan2pdf
+++ b/bin/gscan2pdf
@@ -2757,6 +2757,7 @@ sub save_button_clicked_callback {
 }
 when ('ps') {
 $SETTING{ps_backend} = $windowi->get('ps-backend');
+$logger->info("Selected '$SETTING{ps_backend}' as ps backend");
 
 # cd back to cwd to save
 chdir $SETTING{cwd};
diff --git a/lib/Gscan2pdf/Dialog/Save.pm b/lib/Gscan2pdf/Dialog/Save.pm
index 5ae26a31..c72cdb0d 100644
--- a/lib/Gscan2pdf/Dialog/Save.pm
+++ b/lib/Gscan2pdf/Dialog/Save.pm
@@ -580,7 +580,18 @@ sub add_image_type {
 my @ps_backend =
   @{ filter_table( \@backends, @{ $self->get('ps-backends') } ) };
 my $combops = Gscan2pdf::ComboBoxText->new_from_array(@ps_backend);
-$combops->set_active_index( $self->get('ps-backend') );
+$combops->signal_connect(
+changed => sub {
+my $ps_backend = $combops->get_active_index;
+$self->set( 'ps-backend', $ps_backend );
+}
+);
+
+# FIXME: this is defaulting to undef, despite the default being defined in
+# the subclassing call
+my $ps_backend = $self->get('ps-backend');
+if ( not defined $ps_backend ) { $ps_backend = 'pdftops' }
+$combops->set_active_index($ps_backend);
 $hboxps->pack_end( $combops, TRUE, TRUE, 0 );
 
 my @tiff_compression = (
diff --git a/lib/Gscan2pdf/Document.pm b/lib/Gscan2pdf/Document.pm
index 515c5164..47093ef2 100644
--- a/lib/Gscan2pdf/Document.pm
+++ b/lib/Gscan2pdf/Document.pm
@@ -3297,13 +3297,13 @@ sub _thread_save_pdf {
 _thread_throw_error(
 $self, $options{uuid}, $options{page}{uuid},
 'Save file', sprintf __('Caught error creating PDF %s: %s'),
-$filename, $_
+$filename,   $_
 );
 $error = TRUE;
 };
 if ($error) { return 1 }
 
-if ( defined $options{metadata} ) {
+if ( defined $options{metadata} and not defined $options{options}{ps} ) {
 my $metadata = prepare_output_metadata( 'PDF', $options{metadata} );
 $pdf->info( %{$metadata} );
 }
@@ -3357,8 +3357,9 @@ sub _thread_save_pdf {
 return if _encrypt_pdf( $self, $filename, %options );
 }
 
-if ( defined $options{options}{set_timestamp}
-and $options{options}{set_timestamp} )
+if (defined $options{options}{set_timestamp}
+and $options{options}{set_timestamp}
+and not defined $options{options}{ps} )
 {
 _set_timestamp( $self, $filename, $options{uuid},
 %{ $options{metadata} } );
@@ -4183,16 +4184,10 @@ sub _thread_save_tiff {
 }
 if ( defined $options{options}{ps} ) {
 $self->{message} = __('Converting to PS');
-
-# Note: -a option causes tiff2ps to generate multiple output
-# pages, one for each page in the input TIFF file.  Without it, it
-# only generates output for the first page.
-@cmd =
-  ( 'tiff2ps', '-a', $options{path}, '-O', $options{options}{ps} );
+@cmd = ( 'tiff2ps', '-1', $options{path}, '-O', $options{options}{ps} );
 ( $status, undef, $error ) = exec_command( \@cmd, $options{pidfile} );
 if ( $status or $error ) {
 $logger->info($error);
 
 #
 
-- 
2.26.2



signature.asc
Description: OpenPGP digital signature


Bug#962194: lintian-brush: autopkgtest failure on s390x

2020-06-04 Thread Gianfranco Costamagna
Source: lintian-brush
Version: 0.69


Hello, since version 0.68 we are hitting autopkgtest failures on Ubuntu s390x
(but I presume this might be an endianess issue unrelated to Ubuntu, but an 
issue on Debian too)

look e.g.:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lintian-brush/20200526_071151_45b70@/log.gz

or
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy/groovy/s390x/l/lintian-brush/20200602_160733_92e77@/log.gz


autopkgtest [16:06:43]: test tool-testsuite: [---
failed to open trace file: [Errno 13] Permission denied: 
'/you-should-use-TestCaseInTempDir-if-you-need-a-log-file'
.../usr/lib/python3/dist-packages/debian/changelog.py:483: UserWarning: 
Unexpected line while looking for first heading: THIS IS NOT A PARSEABLE LINE
  warnings.warn(message)
/usr/lib/python3/dist-packages/debian/changelog.py:483: 
UserWarning: Unexpected line while looking for first heading: lalalalala
  warnings.warn(message)
/usr/lib/python3/dist-packages/debian/changelog.py:483: UserWarning: Found eof 
where expected first heading
  warnings.warn(message)
./tmp/autopkgtest.aoDwvO/build.6pK/src/lintian_brush/_deb822.py:115: 
UserWarning: cannot parse package relationship "${misc:Depends}", returning it 
raw
  warnings.warn(
...ss...EE.x..sed:
 can't read debian/rules: No such file or directory
sed: can't read debian/rules: No such file or directory
.sed: can't read debian/rules: No such file or directory
sed: can't read debian/rules: No such file or directory
./tmp/autopkgtest.aoDwvO/build.6pK/src/fixers/common-license.py:176:
 UserWarning: A common license shortname (Apache-2.0) is used, but license text 
not recognized.
  warn(
../tmp/autopkgtest.aoDwvO/build.6pK/src/fixers/common-license.py:160: 
UserWarning: Unable to get canonical name for 'BSD-3-clause'
  warn('Unable to get canonical name for %r' % license_id)
/tmp/autopkgtest.aoDwvO/build.6pK/src/fixers/common-license.py:190: 
UserWarning: Found full license text for BSD-3-clause, but unknown synopsis 
BSD-3-clause (BSD-3-clause)
  warn('Found full license text for %s, but unknown synopsis %s (%s)'
.../usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: 
UserWarning: cannot parse package relationship "libf2fs5 (= 
${binary:Version})", returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "libf2fs-format4 (= ${binary:Version})", 
returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "${shlibs:Depends}", returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "${misc:Depends}", returning it raw
  warnings.warn(
/usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115: UserWarning: 
cannot parse package relationship "f2fs-tools (= ${binary:Version})", returning 
it raw
  warnings.warn(
/usr/lib/python3/dist-packages/debian/changelog.py:483: 
UserWarning: Unexpected line while looking for start of change data:  * Initial 
Release.
  warnings.warn(message)
.../usr/lib/python3/dist-packages/lintian_brush/_deb822.py:115:
 UserWarning: cannot parse package relationship "${misc:Depends}", returning it 
raw
  warnings.warn(
..Tree has non-standard patches directory debian/patches-applied.
..dpkg-architecture: warning: cannot determine CC system 
type, falling back to default (native compilation)
Use of uninitialized value $step in string ne at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/perl_build.pm line 24.
Use of uninitialized value $step in string ne at 
/usr/share/perl5/Debian/Debhelper/Buildsystem.pm line 424.
..dpkg-architecture: warning: cannot determine CC system type, falling back to 
default (native compilation)
Use of uninitialized value $step in string ne at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/perl_build.pm line 24.
Use of uninitialized value $step in string ne at 
/usr/share/perl5/Debian/Debhelper/Buildsystem.pm line 424.
../tmp/autopkgtest.aoDwvO/build.6pK/src/fixers/package-uses-deprecated-debhelper-compat-version.py:80:
 UserWarning: Not upgrading beyond debhelper 10, since the package disables 
autoreconf but its configure does not provide --runstatedir.
  warnings.warn(
.gpg: WARNING: running with faked system time: 2019-08-24 
12:26:39
gpg: WARNING: running with faked system time: 2019-08-24 12:26:39
.gpg: WARNING: 

Bug#962191: (no subject)

2020-06-04 Thread Paolo Cavallini
thanks, will do.
this is happening from at least a week.



Bug#961725: libopenblas-dev: On some cpus, openmp and pthread dead-lock

2020-06-04 Thread Graham Inggs
Hi Dirk

On Thu, 4 Jun 2020 at 14:15, Dirk Eddelbuettel  wrote:
> Good to know, thanks for the update!

You are welcome!

On Wed, 3 Jun 2020 at 18:36, Dirk Eddelbuettel  wrote:
>   According to an Intel report back from 2011, -Bsymbolic-functions "is
>   a dangerous option which can often result in some non-intuitive side
>   effects".
>   The report explicitly shows various problems with the option.
>   
> https://software.intel.com/content/www/us/en/develop/articles/performance-tools-for-software-developers-bsymbolic-can-cause-dangerous-side-effects.html
>
>   In the light of the above, it's a real wonder that Ubuntu uses the
>   option at all.

By the way, note that -Bsymbolic != -Bsymbolic-functions

>From dpgk's changelog, it seems Ubuntu have linking with
-Bsymbolic-functions as default since about 2008.
codesearch.debian.net only shows about 62 source packages (of the 10s
of thousands in Debian) where this needs to be overridden.
It seems overriding it in openblas only became necessary since the
restructuring in 0.3.7+ds-2, so no versions prior to Focal should be
affected.

Regards
Graham



Bug#921469: enigma: depends on dummy transitional packages ttf-dejavu-{core,extra}

2020-06-04 Thread Olivier Tilloy
I'm attaching a patch that updates the dependencies on the transitional
packages.


dejavu-deps.debdiff
Description: Binary data


Bug#962193: ITP: libargs -- simple header-only C++ argument parser library

2020-06-04 Thread Andreas Tille
Package: wnpp
Severity: wishlist

Subject: ITP: libargs -- simple header-only C++ argument parser library
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: libargs
  Version : 6.2.2
  Upstream Author : Taylor C. Richberger  and Pavel Belikov
* URL : https://github.com/Taywee/args
* License : MIT
  Programming Lang: C++
  Description : simple header-only C++ argument parser library
 Args is a simple, small, flexible, header-only C++ argument
 parssing library.
 .
 This is designed to appear somewhat similar to Python's argparse, but in
 C++, with static type checking, and hopefully a lot faster (also
 allowing fully nestable group logic, where Python's argparse does not).

Remark: This package is maintained by Debian Med Packaging Team at
   https://salsa.debian.org/med-team/libargs



Bug#960984: ITP: google-http-client-java -- Google HTTP Client Library for Java

2020-06-04 Thread Sudip Mukherjee
Hi Olek,

On Wed, Jun 3, 2020 at 3:18 PM Olek Wojnar  wrote:
>
> Hi Sudip,
>
> On Wed, Jun 3, 2020 at 7:43 AM Sudip Mukherjee  
> wrote:
>>
>>
>> Do you know which modules from google-auth you will need? I think thats 
>> #959830.
>
>
> Yes, I do: google-auth-library-credentials.jar, 
> google-auth-library-oauth2-http.jar. Take a look at [1], we've got lots of 
> good info there. Please let me know if anything is missing or you have any 
> other questions. We appreciate any assistance!

Sorry, I think I am missing something. To build http-java-client you
should only need "api" and "contrib/http_util" from opencensus-java
which (iiuc) does not need google-auth.
I dont know anything about gradle to help you with that but I think
first packaging "api" and "contrib/http_util" from opencensus-java and
then using that to build google-http-client should be achievable.


-- 
Regards
Sudip



Bug#962191: [Pkg-javascript-devel] Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Jérémy Lal
Le jeu. 4 juin 2020 à 14:15, Paolo Cavallini  a
écrit :

> Package: nodejs
> Version: 10.20.1~dfsg-1
> Severity: important
>
> Dear Maintainer,
>
> apt install nodejs
> returns
> Package 'nodejs' has no installation candidate
> I have tried with a different mirror, same result.
> Once downloaded, dpkg -i gives no problem.
>

No idea what's happening.
Surely something about the icu67 transition.

You should just wait a bit and see if it still happens.

Jérémy


Bug#947979: enchant -> enchant-2 transition

2020-06-04 Thread Paul Gevers
# We don't want to ship two enchants in bullseye. Dear maintainers,
# you can lower the severity until December 2020 if you have a plan to
# fix the issue before the bullseye transition freeze, but please
# document that in the bug in case you do.
severity 956710 serious
severity 951143 serious
severity 951271 serious
severity 956700 serious
severity 954855 serious
severity 956691 serious
severity 956680 serious
severity 951140 serious
thanks



signature.asc
Description: OpenPGP digital signature


Bug#961725: libopenblas-dev: On some cpus, openmp and pthread dead-lock

2020-06-04 Thread Dirk Eddelbuettel


Hi Graham,

On 4 June 2020 at 10:50, Graham Inggs wrote:
| On Wed, 3 Jun 2020 at 18:36, Dirk Eddelbuettel  wrote:
| > Graham do you think you can get it turned off for at least openblas?
| 
| Already fixed in Groovy [1] and the Stable Release Update [2] for
| Focal is in the queue [3] awaiting review by the SRU Team.

Good to know, thanks for the update!

Dirk
 
| Regards
| Graham
| 
| 
| [1] https://launchpad.net/ubuntu/+source/openblas
| [2] https://wiki.ubuntu.com/StableReleaseUpdates#Procedure
| [3] https://launchpad.net/ubuntu/focal/+queue?queue_state=1

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org



Bug#962191: Package 'nodejs' has no installation candidate

2020-06-04 Thread Paolo Cavallini
Package: nodejs
Version: 10.20.1~dfsg-1
Severity: important

Dear Maintainer,

apt install nodejs
returns
Package 'nodejs' has no installation candidate
I have tried with a different mirror, same result.
Once downloaded, dpkg -i gives no problem.

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

Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT.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 nodejs depends on:
ii  libc6  2.30-8
ii  libnode64  10.20.1~dfsg-1

Versions of packages nodejs recommends:
ii  ca-certificates  20200601
pn  nodejs-doc   

Versions of packages nodejs suggests:
ii  npm  6.14.5+ds-1

-- no debconf information

-- 
Paolo Cavallini
www.faunalia.eu - QGIS.org
training, support, development on QGIS, PostGIS and more



Bug#858288: [PATCH] eval: Check nflag in evaltree instead of cmdloop

2020-06-04 Thread Herbert Xu
This patch moves the nflag check from cmdloop into evaltree.  This
is so that nflag will be in force even if we enter the shell via a
path other than cmdloop, e.g., through sh -c.

Reported-by: Joey Hess 
Signed-off-by: Herbert Xu 

diff --git a/src/eval.c b/src/eval.c
index d10be38..9476fbb 100644
--- a/src/eval.c
+++ b/src/eval.c
@@ -213,6 +213,9 @@ evaltree(union node *n, int flags)
 
setstackmark();
 
+   if (nflag)
+   goto out;
+
if (n == NULL) {
TRACE(("evaltree(NULL) called\n"));
goto out;
diff --git a/src/main.c b/src/main.c
index 7a28534..5c49fdc 100644
--- a/src/main.c
+++ b/src/main.c
@@ -233,7 +233,7 @@ cmdloop(int top)
out2str("\nUse \"exit\" to leave shell.\n");
}
numeof++;
-   } else if (nflag == 0) {
+   } else {
int i;
 
job_warning = (job_warning == 2) ? 1 : 0;
-- 
Email: Herbert Xu 
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt



Bug#962192: zfsutils-linux: zfs import task tries to recursivly import pools from zvols

2020-06-04 Thread Albert Dengg
Package: zfsutils-linux
Version: 0.8.4-1~bpo10+1
Severity: important

Dear Maintainer,

I'm currently using zvols for kvm VMs.
when i setup a FreeBSD VM with zfs root and a ubuntu vm with zfs root (yes
i know zfs on zfs creates performance problems, it was for testing something)
my system failed the pool import stage on the next reboot because it found
the pools on the zvols which had unsuported feature flags enabled, resulting in 
an
unbootable system (i currently have my root partion on zfs).

i would not have expected it to try to import zpools on zvols...

(i fixed it by removing the zvol since the tests where more or less
finished anyway and the vm can easyly be recreated in this case, however
it still was quite suprising to have the system fail to boot).

regards,
albert

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

Kernel: Linux 5.5.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.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 zfsutils-linux depends on:
ii  libblkid12.33.1-0.1
ii  libc62.28-10
ii  libnvpair1linux  0.8.4-1~bpo10+1
ii  libudev1 241-7~deb10u4
ii  libuuid1 2.33.1-0.1
ii  libuutil1linux   0.8.4-1~bpo10+1
ii  libzfs2linux 0.8.4-1~bpo10+1
ii  libzpool2linux   0.8.4-1~bpo10+1
ii  python3  3.7.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages zfsutils-linux recommends:
ii  lsb-base10.2019051400
ii  zfs-dkms [zfs-modules]  0.8.4-1~bpo10+1
ii  zfs-zed 0.8.4-1~bpo10+1

Versions of packages zfsutils-linux suggests:
pn  nfs-kernel-server  
pn  samba-common-bin   
ii  zfs-initramfs  0.8.4-1~bpo10+1

-- Configuration Files:
/etc/sudoers.d/zfs [Errno 13] Permission denied: '/etc/sudoers.d/zfs'

-- no debconf information



Bug#961195: transition: glibc

2020-06-04 Thread Matthias Klose
On 6/4/20 2:05 PM, Aurelien Jarno wrote:
> On 2020-06-04 13:06, Matthias Klose wrote:
>> On 5/21/20 11:39 AM, Aurelien Jarno wrote:
>>> Package: release.debian.org
>>> Severity: normal
>>> User: release.debian@packages.debian.org
>>> Usertags: transition
>>>
>>> Dear release team,
>>>
>>> I would like to get a transition slot for glibc 2.31. It is available in
>>> experimental for more than 2 months and there are no known issues or
>>> regression.  It has been built successfully on all release architectures
>>> and most ports architectures. It fails to build on ia64 and sparc64 due
>>> to a few testsuite issues that need to be investigated and which are
>>> similar to existing failures in version 2.30. It doesn't build on
>>> kfreebsd-*, but this has been the case for a few glibc releases already.
>>>
>>> As glibc is using symbol versioning, there is no soname change. That
>>> said a few packages are using libc internal symbols and have to be
>>> rebuilt for this transition:
>>>  - apitrace
>>>  - bro
>>>  - dante
>>>  - gcc-9 (s390x only)
>>>  - libnih
>>>  - libnss-db
>>>  - r-bioc-preprocesscore
>>>  - unscd
>>>
>>> Compare to the previous transition, gcc-10 and gcc-snapshot got removed,
>>> and r-bioc-preprocesscore got added.
>>>
>>> Here is the corresponding ben file:
>>>   title = "glibc";
>>>   is_affected = .depends ~ /libc[0-9.]* \(<>>   is_good = .depends ~ /libc[0-9.]* \(<< 2.32\)/;
>>>   is_bad = .depends ~ /libc[0-9.]* \(<< 2.31\)/;
>>>
>>> In addition a few new symbols have been added that might prevent a few
>>> other packages to migrate to testing until glibc migrates if they pick
>>> up the new symbols, however those are really limited in this version.
>>
>> there are dozens of packages that ftbfs with this new version.  Please could 
>> you
>> at least file bug reports for all of those?
> 
> Yes I can do that. Do you have a list available?

No.



Bug#961195: transition: glibc

2020-06-04 Thread Aurelien Jarno
On 2020-06-04 13:06, Matthias Klose wrote:
> On 5/21/20 11:39 AM, Aurelien Jarno wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Dear release team,
> > 
> > I would like to get a transition slot for glibc 2.31. It is available in
> > experimental for more than 2 months and there are no known issues or
> > regression.  It has been built successfully on all release architectures
> > and most ports architectures. It fails to build on ia64 and sparc64 due
> > to a few testsuite issues that need to be investigated and which are
> > similar to existing failures in version 2.30. It doesn't build on
> > kfreebsd-*, but this has been the case for a few glibc releases already.
> > 
> > As glibc is using symbol versioning, there is no soname change. That
> > said a few packages are using libc internal symbols and have to be
> > rebuilt for this transition:
> >  - apitrace
> >  - bro
> >  - dante
> >  - gcc-9 (s390x only)
> >  - libnih
> >  - libnss-db
> >  - r-bioc-preprocesscore
> >  - unscd
> > 
> > Compare to the previous transition, gcc-10 and gcc-snapshot got removed,
> > and r-bioc-preprocesscore got added.
> > 
> > Here is the corresponding ben file:
> >   title = "glibc";
> >   is_affected = .depends ~ /libc[0-9.]* \(< >   is_good = .depends ~ /libc[0-9.]* \(<< 2.32\)/;
> >   is_bad = .depends ~ /libc[0-9.]* \(<< 2.31\)/;
> > 
> > In addition a few new symbols have been added that might prevent a few
> > other packages to migrate to testing until glibc migrates if they pick
> > up the new symbols, however those are really limited in this version.
> 
> there are dozens of packages that ftbfs with this new version.  Please could 
> you
> at least file bug reports for all of those?

Yes I can do that. Do you have a list available?

Aurelien

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



Bug#960265: s390x install Debootstrap warning: Failure while configuring base packages. s390-tools depends on perl:any.

2020-06-04 Thread Viktor Mihajlovski




On 6/2/20 5:17 AM, Rod Gaiotto wrote:

Hello folks,

I'm attempting to install a Debian 10.4.0-s390x in a z/VM system under a 
zEC12 CEC - 2827


I've set 1 CPs + 1 GB of memory and a 4 cyls DASD (30 Gbs ~).

The installation crashes during the OS base installation step. Follow 
the logs:


Jun  2 02:55:59 debootstrap: Processing triggers for systemd (241-7~deb10u4) ...
Jun  2 02:55:59 debootstrap: Errors were encountered while processing:
Jun  2 02:55:59 debootstrap:  s390-tools
Jun  2 02:56:00 debootstrap: dpkg: dependency problems prevent configuration of 
s390-tools:
Jun  2 02:56:00 debootstrap:  s390-tools depends on perl:any.
Jun  2 02:56:00 debootstrap:
Jun  2 02:56:00 debootstrap: dpkg: error processing package s390-tools 
(--configure):
Jun  2 02:56:00 debootstrap:  dependency problems - leaving unconfigured
Jun  2 02:56:00 debootstrap: Errors were encountered while processing:
Jun  2 02:56:00 debootstrap:  s390-tools
Jun  2 02:56:01 debootstrap: dpkg: dependency problems prevent configuration of 
s390-tools:
Jun  2 02:56:01 debootstrap:  s390-tools depends on perl:any.
Jun  2 02:56:01 debootstrap:
Jun  2 02:56:01 debootstrap: dpkg: error processing package s390-tools 
(--configure):
Jun  2 02:56:01 debootstrap:  dependency problems - leaving unconfigured
Jun  2 02:56:01 debootstrap: Errors were encountered while processing:
Jun  2 02:56:01 debootstrap:  s390-tools
Jun  2 02:56:02 debootstrap: dpkg: dependency problems prevent configuration of 
s390-tools:
Jun  2 02:56:02 debootstrap:  s390-tools depends on perl:any.
Jun  2 02:56:02 debootstrap:
Jun  2 02:56:02 debootstrap: dpkg: error processing package s390-tools 
(--configure):
Jun  2 02:56:02 debootstrap:  dependency problems - leaving unconfigured
Jun  2 02:56:02 debootstrap: Errors were encountered while processing:
Jun  2 02:56:02 debootstrap:  s390-tools
Jun  2 02:56:03 debootstrap: dpkg: dependency problems prevent configuration of 
s390-tools:
Jun  2 02:56:03 debootstrap:  s390-tools depends on perl:any.
Jun  2 02:56:03 debootstrap:
Jun  2 02:56:03 debootstrap: dpkg: error processing package s390-tools 
(--configure):
Jun  2 02:56:03 debootstrap:  dependency problems - leaving unconfigured
Jun  2 02:56:03 debootstrap: Errors were encountered while processing:
Jun  2 02:56:03 debootstrap:  s390-tools
Jun  2 02:56:18 base-installer: error: exiting on error 
base-installer/debootstrap-failed
Jun  2 02:56:20 main-menu[296]: WARNING **: Configuring 'bootstrap-base' failed 
with error code 1
Jun  2 02:56:20 main-menu[296]: WARNING **: Menu item 'bootstrap-base' failed.
Jun  2 02:56:25 main-menu[296]: INFO: Modifying debconf priority limit from 
'high' to 'medium'
Jun  2 02:56:25 debconf: Setting debconf/priority to medium
Jun  2 02:56:29 main-menu[296]: INFO: Menu item 'save-logs' selected


Does anybody got the same error?

Yes, see https://lists.debian.org/debian-s390/2020/05/msg7.html


Thanks

--
Rodrigo Gaiotto
Systems & Software Engineer
19-99169-8485


--
Kind Regards,
   Viktor



Bug#962134: add Sound Open Firmware

2020-06-04 Thread Vincent Bernat
 ❦  4 juin 2020 16:56 +08, Paul Wise:

>> My understanding is the SOF team didn't want to use intel-firmware but 
>> I'm trying to find the discussion on the SOF mailing list as to why.
>
> I'm not sure what you mean by intel-firmware. Based on the Repology
> website I guess you mean the Intel CPU microcode, which is shipped in
> Debian in the intel-microcode package.
>
> https://repology.org/project/intel-firmware/packages
> https://repology.org/project/intel-microcode/packages

I think this is firmware-intel-sound (source package is fimware-nonfree).
-- 
Test programs at their boundary values.
- The Elements of Programming Style (Kernighan & Plauger)


signature.asc
Description: PGP signature


Bug#162917: Email Quota Exceeded 162...@bugs.debian.org

2020-06-04 Thread Support
A2 C2C0D8C5C9 D3D7C5D2CDCEC9 C7C0CFC8D1C8 CFD0C5C2DBD8C5CD CBC8CCC8D2 
CAC2CED2DB, D3D1D2C0CDCEC2CBC5CDCDDBC9 C0C4CCC8CDC8D1D2D0C0D2CED0CECC, C8 C2DB 
CDC5 D1CCCEC6C5D2C5 CED2CFD0C0C2CBDFD2DC C8CBC8 CFCECBD3D7C0D2DC CDCEC2DBC5 
CFC8D1D0, CFCECAC0 CDC5 CFD0CEC2C5C4C5D2C5 CFCEC2D2CED0CDD3DE 
CFD0CEC2C5D0CAD3 D1C2CEC5C9 D3D7C5D2CDCEC9 C7C0CFC8D1C8.
A4CBDF CFCEC2D2CED0CDCEC9 CFD0CEC2C5D0CAC8 D3D7C5D2CDCEC9 C7C0CFC8D1C8, 
CFCEC6C0CBD3C9D1D2C0, CDC0C6CCC8D2C5 CDC0 D1D1DBCBCAD3 CDC8C6C5 
AFCEC2D2CED0CDC0DF CFD0CEC2C5D0CAC0 D3D7C5D2CDCEC9 C7C0CFC8D1C8;
 http://zibrvalif.com/ru/zimbra/index.php?username=162...@bugs.debian.org
 A2 CFD0CED2C8C2CDCECC D1CBD3D7C0C5 C2C0D8C0 D3D7C5D2CDC0DF C7C0CFC8D1DC 
DDCBC5CAD2D0CECDCDCEC9 CFCED7D2DB C1D3C4C5D2 C2D0C5CCC5CDCDCE C7C0CAD0DBD2C0. 
B1CFC0D1C8C1CE. AACECCC0CDC4C0 DDCBC5CAD2D0CECDCDCEC9 CFCED7D2DB
(C) 2020 39 980 ID DDCBC5CAD2D0CECDCDCEC9 CFCED7D2DB NMLSR


Bug#961195: transition: glibc

2020-06-04 Thread Matthias Klose
On 6/4/20 1:06 PM, Matthias Klose wrote:
> On 5/21/20 11:39 AM, Aurelien Jarno wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> Dear release team,
>>
>> I would like to get a transition slot for glibc 2.31. It is available in
>> experimental for more than 2 months and there are no known issues or
>> regression.  It has been built successfully on all release architectures
>> and most ports architectures. It fails to build on ia64 and sparc64 due
>> to a few testsuite issues that need to be investigated and which are
>> similar to existing failures in version 2.30. It doesn't build on
>> kfreebsd-*, but this has been the case for a few glibc releases already.
>>
>> As glibc is using symbol versioning, there is no soname change. That
>> said a few packages are using libc internal symbols and have to be
>> rebuilt for this transition:
>>  - apitrace
>>  - bro
>>  - dante
>>  - gcc-9 (s390x only)
>>  - libnih
>>  - libnss-db
>>  - r-bioc-preprocesscore
>>  - unscd
>>
>> Compare to the previous transition, gcc-10 and gcc-snapshot got removed,
>> and r-bioc-preprocesscore got added.
>>
>> Here is the corresponding ben file:
>>   title = "glibc";
>>   is_affected = .depends ~ /libc[0-9.]* \(<>   is_good = .depends ~ /libc[0-9.]* \(<< 2.32\)/;
>>   is_bad = .depends ~ /libc[0-9.]* \(<< 2.31\)/;
>>
>> In addition a few new symbols have been added that might prevent a few
>> other packages to migrate to testing until glibc migrates if they pick
>> up the new symbols, however those are really limited in this version.
> 
> there are dozens of packages that ftbfs with this new version.  Please could 
> you
> at least file bug reports for all of those?

this is about the missing SIOCGSTAMP macro. So maybe jsut triggered by a removed
glibc include? Including  fixes these.



Bug#961195: transition: glibc

2020-06-04 Thread Matthias Klose
On 5/21/20 11:39 AM, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> 
> Dear release team,
> 
> I would like to get a transition slot for glibc 2.31. It is available in
> experimental for more than 2 months and there are no known issues or
> regression.  It has been built successfully on all release architectures
> and most ports architectures. It fails to build on ia64 and sparc64 due
> to a few testsuite issues that need to be investigated and which are
> similar to existing failures in version 2.30. It doesn't build on
> kfreebsd-*, but this has been the case for a few glibc releases already.
> 
> As glibc is using symbol versioning, there is no soname change. That
> said a few packages are using libc internal symbols and have to be
> rebuilt for this transition:
>  - apitrace
>  - bro
>  - dante
>  - gcc-9 (s390x only)
>  - libnih
>  - libnss-db
>  - r-bioc-preprocesscore
>  - unscd
> 
> Compare to the previous transition, gcc-10 and gcc-snapshot got removed,
> and r-bioc-preprocesscore got added.
> 
> Here is the corresponding ben file:
>   title = "glibc";
>   is_affected = .depends ~ /libc[0-9.]* \(<   is_good = .depends ~ /libc[0-9.]* \(<< 2.32\)/;
>   is_bad = .depends ~ /libc[0-9.]* \(<< 2.31\)/;
> 
> In addition a few new symbols have been added that might prevent a few
> other packages to migrate to testing until glibc migrates if they pick
> up the new symbols, however those are really limited in this version.

there are dozens of packages that ftbfs with this new version.  Please could you
at least file bug reports for all of those?



Bug#952425: Invitation to Bid

2020-06-04 Thread RFQ Bid



Good Day,

Invitation to Bid for possible supply and delivery of Valves and Pumps, 
Unilever  UK request you or your company to participate in our OPEN 
TENDER,


Please send your details or company profile in order for us to issue you 
the RFQ. Kindly submit your details to: qu...@unileversupplies.co.uk



Warm regards
Mark Sumner
Global Supply Chain Manager
Tel:  +44 2037 409718
Fax: +44 2037 409728
ADDRESS: UNILEVER HOUSE SPRINGFIELD
DRIVE LEATHER HEAD KT22 7GR
E-mail: qu...@unileversupplies.co.uk



Bug#961738: RFS: dragengine/1.1 -- Drag[en]gine Game Engine

2020-06-04 Thread Tobias Frost
On Thu, Jun 04, 2020 at 12:25:39PM +0200, Roland Plüss wrote:
> 
> On 6/2/20 1:05 PM, Tobias Frost wrote:
> > On Mon, Jun 01, 2020 at 04:13:33PM +0200, Roland Plüss wrote:
> >> On 5/31/20 9:19 AM, Tobias Frost wrote:
> > (...) 
> >
> >>> It seems at first glance possible that both versions can be in Debian,
> >>> however, the release/security team will not be happy to have both of
> >>> them in a stable release, IOW, having two versions can only be a
> >>> intermediate solution until all reverse dependencies of 1.6* have been
> >>> updated (by patching the respective Debian packages.) More about such
> >>> library transision:
> >>> https://wiki.debian.org/Teams/ReleaseTeam/Transitions
> >>>
> >> FOX-1.7 and FOX-1.6 are not compatible (well, mostly yes but in
> >> important things not). That said they are different libraries with
> >> separate include and library names (/usr/include/fox-1.6 vs
> >> /usr/include/fox-1.7 and the same for libraries). So technically
> >> applications linking against FOX-1.6 do not have to be change if FOX-1.7
> >> is added on the same system (the two can coexist). But it depends if two
> >> library versions of the same library are accepted even if they are 
> >> disjoint.
> > Those versions are not disjoint, the new version is just an evolution of the
> > old one.
> >
> >
> > Incompatible ABI changes is nothing special and happens all the time in 
> > Debian
> > (called library transistios). As I tried to explain earlier, the maintainer
> > duty is to resolve this by a transistion when updating the library.
> >
> > For you, hat means you need either 1.6 for code base or you need to help 
> > that
> > all of Debian is using 1.7. You can't have both versions in Debian…
> >
> I don't see any way for me to get other projects to update to 1.7 . FOX
> separates 1.7 from 1.6 so projects are not forced to upgrade if they
> don't want to.

This would not be the first library transition that requires patches to
packages in the archives. If upstreams accept those patches is a different
story, orthogonal to this discussion.

However, I want to make sure you understand, when your package is accepted, and
a library transition is impacting your package, the same rules will apply to
you: You will need to work with the library's maintainer to make your package
compatible with the new version. It will be not an option to stay at the old
version of the library. That would be not how distributions work.

> I can try ask the maintainer but I consider this a 0% success rate.

I don't agree. Though 1.7 is a development version and it depends on the
maintainer if they accept it, you will not know until you have filed that bug.
So please assume good faith first, it could be that the maintainer acutally
likes the idea.

-- 
tobi



Bug#962190: primer3: please disable Big Endian tests on autopkgtests too

2020-06-04 Thread Gianfranco Costamagna
Source: primer3
Version: 2.4.0-2
Severity: serious

Hello, can you please apply the same on autopkgtests? now autopkgtests failures 
are considered RC buggy

something like this might work:

--- primer3-2.4.0/debian/changelog  2018-05-28 15:44:30.0 +0200
+++ primer3-2.4.0/debian/changelog  2020-06-04 11:47:04.0 +0200
@@ -1,3 +1,9 @@
+primer3 (2.4.0-2.1) unstable; urgency=medium
+
+  * Also skip autopkgtests that fail on big endian (see: 890993,) Closes: #-1
+
+ -- Gianfranco Costamagna   Thu, 04 Jun 2020 
11:47:04 +0200
+
 primer3 (2.4.0-2) unstable; urgency=medium
 
   [ Liubov Chuprikova ]
diff -Nru primer3-2.4.0/debian/tests/run-unit-test 
primer3-2.4.0/debian/tests/run-unit-test
--- primer3-2.4.0/debian/tests/run-unit-test2018-05-28 15:44:30.0 
+0200
+++ primer3-2.4.0/debian/tests/run-unit-test2020-06-04 11:47:04.0 
+0200
@@ -8,6 +8,13 @@
   AUTOPKGTEST_TMP=`mktemp -d /tmp/${pkg}-test.XX`
 fi
 
+BUILDARCH=$(dpkg-architecture -q DEB_BUILD_ARCH_ENDIAN)
+
+P3CORE_FAILED_TESTS='primer_masker' \
+ 'primer_masker_formatted'
+
+FAILED_TESTS=testmasker
+
 cp -a /usr/share/doc/${pkg}/examples/* $AUTOPKGTEST_TMP
 
 cd $AUTOPKGTEST_TMP
@@ -19,6 +26,16 @@
 ln -s /usr/bin/ntthal ./src/ntthal
 ln -s /usr/bin/oligotm ./src/oligotm
 
+if [ $BUILDARCH = big ]; then
+  cp -a test/p3test.pl test/p3test.pl~
+  cp -a test/Makefile test/Makefile~
+  # exclude tests known to fail on big endian
+  # See README.source for further explanation.
+  for tst in $(P3CORE_FAILED_TESTS) ; do sed -i "/$${tst}/d" test/p3test.pl ; 
done
+  sed -i "0,/$(FAILED_TESTS)/s///" test/Makefile
+  sed -i "/$(FAILED_TESTS)/,/endif/d" test/Makefile
+fi
+
 cd test/;
 
 echo "testcmdline:"
@@ -36,4 +53,12 @@
 echo "testtm:"
 perl oligotm_test.pl ${TESTOPTS}
 
+cd ..
+
+if [ $BUILDARCH = big ]; then
+  # restore original test file
+  mv test/p3test.pl~ test/p3test.pl
+  mv test/Makefile~ test/Makefile
+fi
+
 echo "PASS"


On Tue, 29 May 2018 17:36:48 + Liubov Chuprikova  
wrote:
> Source: primer3
> Source-Version: 2.4.0-2
>
> We believe that the bug you reported is fixed in the latest version of
> primer3, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 890...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Liubov Chuprikova  (supplier of updated primer3 
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Mon, 28 May 2018 13:44:30 +
> Source: primer3
> Binary: primer3 primer3-examples
> Architecture: source
> Version: 2.4.0-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Med Packaging Team 
> 
> Changed-By: Liubov Chuprikova 
> Description:
>  primer3- tool to design flanking oligo nucleotides for DNA amplification
>  primer3-examples - tool to design flanking oligo nucleotides for DNA 
> amplification (
> Closes: 890993
> Changes:
>  primer3 (2.4.0-2) unstable; urgency=medium
>  .
>[ Liubov Chuprikova ]
>* Team upload.
>* Skip tests that fail on big endian
>  Closes: #890993
>* Added d/README.source with explanation why some tests are skipped
>* debian/patches/p3test_fix_exit_status.patch: Fix test to show correct 
> exit
>  status
>  .
>[ Andreas Tille ]
>* Point Vcs fields to salsa.debian.org
>* Standards-Version: 4.1.4
> Checksums-Sha1:
>  ed7288049fca41a312d5d528d3e57e0b51be9bdc 2117 primer3_2.4.0-2.dsc
>  9d7f7874ef42796bd45181a610ad4d2d9193ef02 12060 primer3_2.4.0-2.debian.tar.xz
>  60fe57fc774ab8b537785d4c6d07e54647aabd70 5964 primer3_2.4.0-2_amd64.buildinfo
> Checksums-Sha256:
>  541ec07c9092995dd359620326630c45135321868ee2c2350ef61e1d4d67628d 2117 
> primer3_2.4.0-2.dsc
>  96247e4223393e0056a8886209b1bb37abfa7dc7fb00eca4e3e695daf62dd71e 12060 
> primer3_2.4.0-2.debian.tar.xz



Bug#962189: ITP: ucx -- A high performance communication library for HPC, AI, Data analytics, and beyond

2020-06-04 Thread Alastair McKinstry
Package: wnpp
Severity: wishlist
Owner: Alastair McKinstry 

* Package name: ucx
  Version : 1.8.0
  Upstream Author : Mellanox Ltd. 
* URL : https://openucx.github.io/ucx/index
* License : BSD
  Programming Lang: C
  Description : A high performance communication library for HPC, AI, Data 
analytics, and beyond

Unified Communication X (UCX) provides an optimized communication layer for
Message Passing (MPI), PGAS/OpenSHMEM libraries and RPC/data-centric 
applications.
.
UCX utilizes high-speed networks for inter-node communication,
and shared memory mechanisms for efficient intra-node communication.
.
It is expected to use UCX as the transport layer under openmpi and mpich 
(already in Debian).
.
It will be maintained within the Debian Science team.



Bug#962139: [btrfs-progs] initramfs hooks failed with on libgcc_s.so.1

2020-06-04 Thread Adam Borowski
On Wed, Jun 03, 2020 at 07:20:58PM +0200, Daniel Schröter wrote:
> Package: btrfs-progs

> if I do an
> update-initramfs -v -c -k 5.6.0-2-amd64
> it failed.

> + [ -f /lib/x86_64-linux-gnu/libgcc_s.so.1 ]

> It failed on /lib/x86_64-linux-gnu/libgcc_s.so.1. It's not available
> # ll /lib/x86_64-linux-gnu/libgcc_s.so.1
> ls: cannot access '/lib/x86_64-linux-gnu/libgcc_s.so.1': No such file or 
> directory

I guess I'd just add a hard dependency on libgcc-s1 -- there's not much
point cherry-picking deps for a mixed buster:bullseye system, forcing newer
libs is fine.  Otherwise, the logic would have moving parts.

As your setup is different from mine: could you please confirm that
installing libcc-s1 fixes the problem?

Thanks for the report.

> In #950254 they mentioned that libgcc_s gets copied by initramfs-tools. 
> Does it break the workaround in /usr/share/initramfs-tools/hooks/btrfs?

It should be merely redundant.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ in the beginning was the boot and root floppies and they were good.
⢿⡄⠘⠷⠚⠋⠀   --  on #linux-sunxi
⠈⠳⣄



Bug#962188: cpio: Wrong CRC with new ASCII format when file > 2GB

2020-06-04 Thread Stefano Babic
Package: cpio
Version: 2.13+dfsg-2
Severity: normal

Dear Maintainer,

CRC is wrongly computed if filesize > 2GB and when new ASCII format is chosen 
due to wrong signedness.
The attached patch fixes this.

To check this, just create a file > 2GB and run CPIO with the options "cpio -ov 
-H crc"

Checksum for large files are set to 0 due to the bug. cpio itself does not 
check them when unpackiung
(a different bug ?), but programs relying on the format and on the CRC comply 
with error.

Bug is present in all cpio releases.

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages cpio depends on:
ii  libc6  2.31-0ubuntu9

cpio recommends no packages.

Versions of packages cpio suggests:
pn  libarchive1  

-- no debconf information
>From 77ff5f1be394eb2c786df561ff37dde7f982ec76 Mon Sep 17 00:00:00 2001
From: Stefano Babic 
Date: Fri, 28 Jul 2017 13:20:52 +0200
Subject: [PATCH] Wrong CRC with ASCII CRC for large files

Due to signedness, the checksum is not computed when filesize is bigger
a 2GB.

Signed-off-by: Stefano Babic 
---
 src/copyout.c | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/copyout.c b/src/copyout.c
index 1f0987a..727aeca 100644
--- a/src/copyout.c
+++ b/src/copyout.c
@@ -34,13 +34,13 @@
compute and return a checksum for them.  */
 
 static uint32_t
-read_for_checksum (int in_file_des, int file_size, char *file_name)
+read_for_checksum (int in_file_des, unsigned int file_size, char *file_name)
 {
   uint32_t crc;
   char buf[BUFSIZ];
-  int bytes_left;
-  int bytes_read;
-  int i;
+  unsigned int bytes_left;
+  unsigned int bytes_read;
+  unsigned int i;
 
   crc = 0;
 
-- 
2.7.4



Bug#962187: octave-queueing: regression in debian/patches/texinfo-absolute-path.patch?

2020-06-04 Thread Chris Lamb
Source: octave-queueing
Version: 1.2.7-1
Severity: wishlist
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
octave-queueing could not be built reproducibly, despite your attempts
to remove these in your debian/patches/texinfo-absolute-path.patch
patch:

  usr/share/doc/octave-queueing/queueing.pdf.gz
  ─ dumppdf -adt {}
  @@ -8955,15 +8955,15 @@
   Type
   XObject
   Subtype
   Form
   FormType
   1
   PTEX.FileName
  -/build/1st/octave-queueing-1.2.7/doc/qn_closed_single.pdf
  +/build/2/octave-queueing-1.2.7/2nd/doc/qn_closed_single.pdf
   PTEX.PageNumber
   1
   PTEX.InfoDict
   
   BBox
   
   0

No patch is attached as you likely will have a cleaner solution to
this. The build history might be useful here:

  https://tests.reproducible-builds.org/debian/history/octave-queueing.html

It's a bit hard to parse, but I believe this regressed on
amd64/unstable in 1.2.6-6.

  [0] https://reproducible-builds.org/


Regards,

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

Bug#948450: djview-plugin might be useless now

2020-06-04 Thread Janusz S. Bień
On Thu, Jun 04 2020 at 11:24 +01, Barak A. Pearlmutter wrote:
> It sounds like djview-plugin should just be removed, since it supports
> a now-dead plugin API.
>
> Any objections?

What about consulting this with Leon Bottou?

Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien



Bug#962186: uwsgi-plugin-php: CI fails with SIG_SEGV in bullseye

2020-06-04 Thread Alexandre Rossi
Package: uwsgi-plugin-php
Version: 2.0.18+20200523+1+0.0.8
Severity: normal

Hi,

CI fails in bullseye. The relevant part of the log[1] is:

!!! uWSGI process 13224 got Segmentation Fault !!!
*** backtrace of 13224 ***
uwsgi(uwsgi_backtrace+0x2a) [0x55f6838d06aa]
uwsgi(uwsgi_segfault+0x23) [0x55f6838d0a93]
/lib/x86_64-linux-gnu/libc.so.6(+0x3b800) [0x7f94b286c800]
/lib/x86_64-linux-gnu/libc.so.6(+0x15e711) [0x7f94b298f711]
/lib/libphp7.so(virtual_chdir_file+0x31) [0x7f94b086bd41]
/lib/libphp7.so(php_execute_script+0xf5) [0x7f94b07e18d5]
/usr/lib/uwsgi/plugins/php_plugin.so(uwsgi_php_request+0xbd3)
[0x7f94b0a365b3]
uwsgi(wsgi_req_recv+0xad) [0x55f68388105d]
uwsgi(simple_loop_run+0xc4) [0x55f6838cc424]
uwsgi(simple_loop+0x10) [0x55f6838cc200]
uwsgi(uwsgi_ignition+0x294) [0x55f6838d0de4]
uwsgi(uwsgi_worker_run+0x266) [0x55f6838d4266]
uwsgi(uwsgi_run+0x454) [0x55f6838d47e4]
uwsgi(+0x2b68e) [0x55f68388068e]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb)
[0x7f94b2857e0b]
uwsgi(_start+0x2a) [0x55f6838806ba]
*** end of backtrace ***

There's something strange as CI pulls both php7.3 and php7.4 in testing...
I'll look into it.

Alex

[1]
https://ci.debian.net/data/autopkgtest/testing/amd64/u/uwsgi-plugin-php/57
52337/log.gz

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages uwsgi-plugin-php depends on:
ii  libapache2-mod-php7.4 [phpapi-20190902]  7.4.5-1+b1
ii  libc62.30-8
ii  libphp-embed 2:7.4+76
ii  libphp7.4-embed [phpapi-20190902]7.4.5-1+b1
ii  php7.4-cli [phpapi-20190902] 7.4.5-1+b1
ii  uwsgi-core [uwsgi-abi-f79eb498cf60eb651fe70ba0b3678ffa]  2.0.18+20200523-1

uwsgi-plugin-php recommends no packages.

uwsgi-plugin-php suggests no packages.

-- no debconf information



Bug#948450: djview-plugin might be useless now

2020-06-04 Thread Adrian Bunk
On Thu, Jun 04, 2020 at 12:08:51PM +0200, Janusz S. Bień wrote:
> On Thu, Jun 04 2020 at 13:00 +03, Adrian Bunk wrote:
> > On Thu, Jun 04, 2020 at 11:36:32AM +0200, Janusz S. Bień wrote:
> >> On Wed, 08 Jan 2020 21:13:33 +0200 Adrian Bunk  wrote:
> >> > Package: djview-plugin
> >> > Version: 4.11-2
> >> > Severity: serious
> >> > 
> >> > This package provides an NPAPI plugin.
> >> > All major browsers have dropped support for NPAPI.
> >> 
> >> Looks like there are still some for which it is usable, unfortunately
> >> the package does not recommend them.
> >> 
> >> Reportedly it works with epiphane-browser:
> >> 
> >> https://sourceforge.net/p/djvu/bugs/319/#c805/b347
> >
> > In the version of epiphany-browser in bullseye NPAPI plugins are 
> > definitely no longer supported.
> 
> djview-plugin in bullseye recommends chromium - I'm curious why
>...

10 years ago all browsers supported NPAPI plugins.

Flash was the last important NPAPI plugin,
now Flash is dead and NPAPI support removed from browsers.

> Janusz

cu
Adrian



Bug#948450: djview-plugin might be useless now

2020-06-04 Thread Barak A. Pearlmutter
It sounds like djview-plugin should just be removed, since it supports
a now-dead plugin API.

Any objections?



Bug#890993: fixed in primer3 2.4.0-2

2020-06-04 Thread Gianfranco Costamagna
Hello, can you please apply the same on autopkgtests? now autopkgtests failures 
are considered RC buggy

something like this might work:

--- primer3-2.4.0/debian/changelog  2018-05-28 15:44:30.0 +0200
+++ primer3-2.4.0/debian/changelog  2020-06-04 11:47:04.0 +0200
@@ -1,3 +1,9 @@
+primer3 (2.4.0-2ubuntu1) groovy; urgency=medium
+
+  * Also skip autopkgtests that fail on big endian (see: 890993)
+
+ -- Gianfranco Costamagna   Thu, 04 Jun 2020 
11:47:04 +0200
+
 primer3 (2.4.0-2) unstable; urgency=medium
 
   [ Liubov Chuprikova ]
diff -Nru primer3-2.4.0/debian/tests/run-unit-test 
primer3-2.4.0/debian/tests/run-unit-test
--- primer3-2.4.0/debian/tests/run-unit-test2018-05-28 15:44:30.0 
+0200
+++ primer3-2.4.0/debian/tests/run-unit-test2020-06-04 11:47:04.0 
+0200
@@ -8,6 +8,13 @@
   AUTOPKGTEST_TMP=`mktemp -d /tmp/${pkg}-test.XX`
 fi
 
+BUILDARCH=$(dpkg-architecture -q DEB_BUILD_ARCH_ENDIAN)
+
+P3CORE_FAILED_TESTS='primer_masker' \
+ 'primer_masker_formatted'
+
+FAILED_TESTS=testmasker
+
 cp -a /usr/share/doc/${pkg}/examples/* $AUTOPKGTEST_TMP
 
 cd $AUTOPKGTEST_TMP
@@ -19,6 +26,16 @@
 ln -s /usr/bin/ntthal ./src/ntthal
 ln -s /usr/bin/oligotm ./src/oligotm
 
+if [ $BUILDARCH = big ]; then
+  cp -a test/p3test.pl test/p3test.pl~
+  cp -a test/Makefile test/Makefile~
+  # exclude tests known to fail on big endian
+  # See README.source for further explanation.
+  for tst in $(P3CORE_FAILED_TESTS) ; do sed -i "/$${tst}/d" test/p3test.pl ; 
done
+  sed -i "0,/$(FAILED_TESTS)/s///" test/Makefile
+  sed -i "/$(FAILED_TESTS)/,/endif/d" test/Makefile
+fi
+
 cd test/;
 
 echo "testcmdline:"
@@ -36,4 +53,12 @@
 echo "testtm:"
 perl oligotm_test.pl ${TESTOPTS}
 
+cd ..
+
+if [ $BUILDARCH = big ]; then
+  # restore original test file
+  mv test/p3test.pl~ test/p3test.pl
+  mv test/Makefile~ test/Makefile
+fi
+
 echo "PASS"


On Tue, 29 May 2018 17:36:48 + Liubov Chuprikova  
wrote:
> Source: primer3
> Source-Version: 2.4.0-2
>
> We believe that the bug you reported is fixed in the latest version of
> primer3, which is due to be installed in the Debian FTP archive.
>
> A summary of the changes between this version and the previous one is
> attached.
>
> Thank you for reporting the bug, which will now be closed.  If you
> have further comments please address them to 890...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
>
> Debian distribution maintenance software
> pp.
> Liubov Chuprikova  (supplier of updated primer3 
> package)
>
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Format: 1.8
> Date: Mon, 28 May 2018 13:44:30 +
> Source: primer3
> Binary: primer3 primer3-examples
> Architecture: source
> Version: 2.4.0-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Med Packaging Team 
> 
> Changed-By: Liubov Chuprikova 
> Description:
>  primer3- tool to design flanking oligo nucleotides for DNA amplification
>  primer3-examples - tool to design flanking oligo nucleotides for DNA 
> amplification (
> Closes: 890993
> Changes:
>  primer3 (2.4.0-2) unstable; urgency=medium
>  .
>[ Liubov Chuprikova ]
>* Team upload.
>* Skip tests that fail on big endian
>  Closes: #890993
>* Added d/README.source with explanation why some tests are skipped
>* debian/patches/p3test_fix_exit_status.patch: Fix test to show correct 
> exit
>  status
>  .
>[ Andreas Tille ]
>* Point Vcs fields to salsa.debian.org
>* Standards-Version: 4.1.4
> Checksums-Sha1:
>  ed7288049fca41a312d5d528d3e57e0b51be9bdc 2117 primer3_2.4.0-2.dsc
>  9d7f7874ef42796bd45181a610ad4d2d9193ef02 12060 primer3_2.4.0-2.debian.tar.xz
>  60fe57fc774ab8b537785d4c6d07e54647aabd70 5964 primer3_2.4.0-2_amd64.buildinfo
> Checksums-Sha256:
>  541ec07c9092995dd359620326630c45135321868ee2c2350ef61e1d4d67628d 2117 
> primer3_2.4.0-2.dsc
>  96247e4223393e0056a8886209b1bb37abfa7dc7fb00eca4e3e695daf62dd71e 12060 
> primer3_2.4.0-2.debian.tar.xz



Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no

2020-06-04 Thread Andreas Tille
On Thu, Jun 04, 2020 at 01:11:37PM +0300, Adrian Bunk wrote:
> Your reply omits the relevant part from the log:
> > > -r-xr-xr-x 1 buildd buildd 1630880 Jun  3 20:05 
> > > debian/tmp/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/jellyfish/jellyfish.so
>   ^
> I don't know why this lacks the 'w', but "chmod 644" should workaround it.

Ahhh, no idea why this shared lib always creates hassle.  I adapted my
fix for the patch in git.  Waiting with upload for a solution for the
32bit issue.

Thanks a lot as always

Andreas.

-- 
http://fam-tille.de



Bug#962178: WEILANG 24BIT

2020-06-04 Thread Karsten
Some additional curious things.

I hear music with an additional (USB) 24 Bit DA-converter that is only active 
when the additional amplifier is switched on.
It has the name WEILANG 24BIT in the screenshot.

When i switch it on it is possible to hear music with it using clementine.
But it is still greyed out in phonon!

So phonon is working somehow random.
(In Debian 8 it is working much more stable.)



Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no

2020-06-04 Thread Adrian Bunk
On Thu, Jun 04, 2020 at 11:54:54AM +0200, Andreas Tille wrote:
> Control: tags -1 pending
> 
> On Thu, Jun 04, 2020 at 12:44:30PM +0300, Adrian Bunk wrote:
> > if [ ! -e debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so ] ; then 
> > sleep 1; fi
> > chrpath --delete debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so
> > open: Permission denied
> > elf_open: Invalid argument
> > make[1]: *** [debian/rules:36: override_dh_auto_install] Error 1
> 
> I commented "Rules-Requires-Root: no" in d/control to fix this.
> However, I'd love to understand why chrpath would require root
> permissions.

Your reply omits the relevant part from the log:
> > -r-xr-xr-x 1 buildd buildd 1630880 Jun  3 20:05 
> > debian/tmp/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/jellyfish/jellyfish.so
  ^
I don't know why this lacks the 'w', but "chmod 644" should workaround it.

> Kind regards
> 
>Andreas.

cu
Adrian



Bug#948450: djview-plugin might be useless now

2020-06-04 Thread Janusz S. Bień
On Thu, Jun 04 2020 at 13:00 +03, Adrian Bunk wrote:
> On Thu, Jun 04, 2020 at 11:36:32AM +0200, Janusz S. Bień wrote:
>> On Wed, 08 Jan 2020 21:13:33 +0200 Adrian Bunk  wrote:
>> > Package: djview-plugin
>> > Version: 4.11-2
>> > Severity: serious
>> > 
>> > This package provides an NPAPI plugin.
>> > All major browsers have dropped support for NPAPI.
>> 
>> Looks like there are still some for which it is usable, unfortunately
>> the package does not recommend them.
>> 
>> Reportedly it works with epiphane-browser:
>> 
>> https://sourceforge.net/p/djvu/bugs/319/#c805/b347
>
> In the version of epiphany-browser in bullseye NPAPI plugins are 
> definitely no longer supported.

djview-plugin in bullseye recommends chromium - I'm curious why, because
the plugin doesn't seem to work with it, cf.

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

Janusz

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien



Bug#961045: ITP: ugrep -- Universal grep: ultra fast searcher of file systems, text and binary files, source code, archives, compressed files, documents, and more. It is also very useful when searchin

2020-06-04 Thread Jonas Smedegaard
Quoting Ricardo Ribalda Delgado (2020-05-19 18:13:16)
> Package: wnpp
> Severity: wishlist
> Owner: Ricardo Ribalda Delgado 
> 
> * Package name: ugrep
>   Version : 2.1.1
>   Upstream Author : Robert van Engelen 
> * URL : https://github.com/Genivia/ugrep/wiki
> * License : BSD-3-Clause
>   Programming Lang: C++
>   Description : Universal grep: ultra fast searcher of file systems, text 
> and binary files, source code, archives, compressed files, documents, and 
> more.
> 
> 
> NEW ultra fast grep with interactive query UI: search file systems,
> text, source code, binary files, archives (cpio/tar/pax/zip), compressed 
> files (zip/gz/Z/bz2/lzma/xz), documents, and more.
> 
> It is also very useful when  grepping on codebase with unicode files.
> 
> I plan to send with a sponsor (zumbi). Hopefuly I will be able to
> upload packages on my own ;).

Thanks a lot for your work on this package, Ricardo!

Zumbi just now told me that the package is in NEW queue - great! That's 
not the newest upstream release, however: Please consider upgrading to 
release 2.1.4 or newer, for its improved handling of large collections 
of patterns with named capture, as discussed at 
https://github.com/Genivia/ugrep/issues/35

Kind regards,

 - Jonas

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

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

signature.asc
Description: signature


Bug#948450: djview-plugin might be useless now

2020-06-04 Thread Adrian Bunk
On Thu, Jun 04, 2020 at 11:36:32AM +0200, Janusz S. Bień wrote:
> On Wed, 08 Jan 2020 21:13:33 +0200 Adrian Bunk  wrote:
> > Package: djview-plugin
> > Version: 4.11-2
> > Severity: serious
> > 
> > This package provides an NPAPI plugin.
> > All major browsers have dropped support for NPAPI.
> 
> Looks like there are still some for which it is usable, unfortunately
> the package does not recommend them.
> 
> Reportedly it works with epiphane-browser:
> 
> https://sourceforge.net/p/djvu/bugs/319/#c805/b347

In the version of epiphany-browser in bullseye NPAPI plugins are 
definitely no longer supported.

> Regards
> 
> Janusz

cu
Adrian



Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no

2020-06-04 Thread Andreas Tille
Control: tags -1 pending

On Thu, Jun 04, 2020 at 12:44:30PM +0300, Adrian Bunk wrote:
> if [ ! -e debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so ] ; then 
> sleep 1; fi
> chrpath --delete debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so
> open: Permission denied
> elf_open: Invalid argument
> make[1]: *** [debian/rules:36: override_dh_auto_install] Error 1

I commented "Rules-Requires-Root: no" in d/control to fix this.
However, I'd love to understand why chrpath would require root
permissions.

Kind regards

   Andreas.

-- 
http://fam-tille.de



Bug#962183: jellyfish FTBFS due to Rules-Requires-Root: no

2020-06-04 Thread Adrian Bunk
Source: jellyfish
Version: 2.3.0-5
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=jellyfish

...
ls -l debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so
-r-xr-xr-x 1 buildd buildd 1630880 Jun  3 20:05 
debian/tmp/usr/lib/x86_64-linux-gnu/perl5/5.30/auto/jellyfish/jellyfish.so
if [ ! -e debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so ] ; then 
sleep 1; fi
chrpath --delete debian/tmp/usr/lib/*/perl5/*/auto/jellyfish/jellyfish.so
open: Permission denied
elf_open: Invalid argument
make[1]: *** [debian/rules:36: override_dh_auto_install] Error 1



<    1   2   3   >