Bug#960827: nomad FTBFS: cannot find package "github.com/docker/docker/rootless"

[Adrian Bunk]

Source: nomad
Version: 0.10.5+dfsg1-1
Severity: serious
Tags: ftbfs

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

...
cd _build && go install -trimpath -v -p 15 -a -tags "release ui 
nonvidia" github.com/hashicorp/nomad github.com/hashicorp/nomad/acl 
github.com/hashicorp/nomad/api github.com/hashicorp/nomad/api/contexts 
github.com/hashicorp/nomad/api/internal/testutil 
github.com/hashicorp/nomad/api/internal/testutil/discover 
github.com/hashicorp/nomad/api/internal/testutil/freeport 
github.com/hashicorp/nomad/client github.com/hashicorp/nomad/client/allocdir 
github.com/hashicorp/nomad/client/allocdir/input 
github.com/hashicorp/nomad/client/allochealth 
github.com/hashicorp/nomad/client/allocrunner 
github.com/hashicorp/nomad/client/allocrunner/interfaces 
github.com/hashicorp/nomad/client/allocrunner/state 
github.com/hashicorp/nomad/client/allocrunner/taskrunner 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/getter 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/interfaces 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/restarts 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/state 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/template 
github.com/hashicorp/nomad/client/allocwatcher 
github.com/hashicorp/nomad/client/config 
github.com/hashicorp/nomad/client/consul 
github.com/hashicorp/nomad/client/devicemanager 
github.com/hashicorp/nomad/client/devicemanager/state 
github.com/hashicorp/nomad/client/fingerprint 
github.com/hashicorp/nomad/client/interfaces 
github.com/hashicorp/nomad/client/lib/fifo 
github.com/hashicorp/nomad/client/lib/nsutil 
github.com/hashicorp/nomad/client/lib/streamframer 
github.com/hashicorp/nomad/client/logmon 
github.com/hashicorp/nomad/client/logmon/logging 
github.com/hashicorp/nomad/client/logmon/proto 
github.com/hashicorp/nomad/client/pluginmanager 
github.com/hashicorp/nomad/client/pluginmanager/drivermanager 
github.com/hashicorp/nomad/client/pluginmanager/drivermanager/state 
github.com/hashicorp/nomad/client/servers 
github.com/hashicorp/nomad/client/state github.com/hashicorp/nomad/client/stats 
github.com/hashicorp/nomad/client/structs 
github.com/hashicorp/nomad/client/taskenv 
github.com/hashicorp/nomad/client/testutil 
github.com/hashicorp/nomad/client/vaultclient 
github.com/hashicorp/nomad/command github.com/hashicorp/nomad/command/agent 
github.com/hashicorp/nomad/command/agent/consul 
github.com/hashicorp/nomad/command/agent/monitor 
github.com/hashicorp/nomad/command/agent/pprof 
github.com/hashicorp/nomad/devices/gpu/nvidia 
github.com/hashicorp/nomad/devices/gpu/nvidia/cmd 
github.com/hashicorp/nomad/devices/gpu/nvidia/nvml 
github.com/hashicorp/nomad/drivers/docker 
github.com/hashicorp/nomad/drivers/docker/cmd 
github.com/hashicorp/nomad/drivers/docker/docklog 
github.com/hashicorp/nomad/drivers/docker/docklog/proto 
github.com/hashicorp/nomad/drivers/docker/util 
github.com/hashicorp/nomad/drivers/exec github.com/hashicorp/nomad/drivers/java 
github.com/hashicorp/nomad/drivers/mock github.com/hashicorp/nomad/drivers/qemu 
github.com/hashicorp/nomad/drivers/rawexec 
github.com/hashicorp/nomad/drivers/rkt 
github.com/hashicorp/nomad/drivers/shared/eventer 
github.com/hashicorp/nomad/drivers/shared/executor 
github.com/hashicorp/nomad/drivers/shared/executor/proto 
github.com/hashicorp/nomad/helper github.com/hashicorp/nomad/helper/args 
github.com/hashicorp/nomad/helper/boltdd 
github.com/hashicorp/nomad/helper/codec 
github.com/hashicorp/nomad/helper/constraints/semver 
github.com/hashicorp/nomad/helper/discover 
github.com/hashicorp/nomad/helper/escapingio 
github.com/hashicorp/nomad/helper/fields 
github.com/hashicorp/nomad/helper/flag-helpers 
github.com/hashicorp/nomad/helper/flatmap 
github.com/hashicorp/nomad/helper/freeport 
github.com/hashicorp/nomad/helper/gated-writer 
github.com/hashicorp/nomad/helper/logging 
github.com/hashicorp/nomad/helper/noxssrw 
github.com/hashicorp/nomad/helper/pluginutils/catalog 
github.com/hashicorp/nomad/helper/pluginutils/grpcutils 
github.com/hashicorp/nomad/helper/pluginutils/hclspecutils 
github.com/hashicorp/nomad/helper/pluginutils/hclutils 
github.com/hashicorp/nomad/helper/pluginutils/loader 
github.com/hashicorp/nomad/helper/pluginutils/singleton 
github.com/hashicorp/nomad/helper/pool github.com/hashicorp/nomad/helper/stats 
github.com/hashicorp/nomad/helper/testlog 
github.com/hashicorp/nomad/helper/testtask 
github.com/hashicorp/nomad/helper/tlsutil 
github.com/hashicorp/nomad/helper/useragent 
github.com/hashicorp/nomad/helper/uuid github.com/hashicorp/nomad/helper/winsvc 
github.com/hashicorp/nomad/jobspec github.com/hashicorp/nomad/lib/circbufwriter 
github.com/hashicorp/nomad/lib/delayheap github.com/hashicorp/nomad/lib/kheap 
github.com/hashicorp/nomad/nomad 
github.com/hashicorp/nomad/nomad/deploymentwatcher 
github.com/hashicorp/nomad/nomad/drainer github.com/hashicorp/nomad/nomad/mock 

Bug#960465: thunderbird: Xfce "preferred browser" setting ignored when AppArmor profile is enabled

[Vincas Dargis]

Control: user -1 pkg-apparmor-t...@lists.alioth.debian.org
Control: usertag -1 modify-profile

Yes.

I've reproduced this on Debian 10 XFCE VM, and fix is just adding a single line:

```
owner @{HOME}/.config/xfce4/helpers.rc r,
```

I'll prepare upstream MR to update AA profile.

2020-05-15 09:35, Carsten Schoenert rašė:

Hello Vincas,

seems there is some more AppArmor related stuff to fix for Thunderbird
under Xfce. Could you please have a look?

Bug#902643: buggy magic: dump previous vs current swapped

[Christoph Biedl]

Control: tags 902643 moreinfo

Elliott Mitchell wrote...

> SSIA.  When examining files produced by `dump` it gives a date for the
> current file and the date of the previous dump.  Unfortunately the date
> it is giving for the "Previous dump" is the date on the file being
> examined, whereas the date for "This dump" is the date of the previous
> dump.

Hi there,

Debian package search for "dump" returns

/etc/comgt/dumpcomgt
/sbin/dump dump
/usr/lib//dist-packages/cdist/conf/type/__mount/parameter/default/dump 
 cdist
/usr/lib//dumpcorekeeper
/usr/lib//filters-unex/dump   cruft-common
/usr/lib//gwyddion/plugins/file/dump  gwyddion-plugins
/usr/lib//metview/dumpmetview
/usr/lib//planners/dump   apt
/usr/lib//solvers/dumpapt

And libmagic has 69 lines that result in a string containing "dump".
Quite frankly, I'm lost here. Which one of those are you referring to?
How can I reproduce the issue?

Christoph


signature.asc
Description: PGP signature

Bug#960750: chasen: build failure with clang

[Takatsugu Nokubi]

On Sat, 16 May 2020 18:31:50 +0900 Hideki Yamane  wrote:
>  It seems that chasen is failed to build with clang.
>  
> https://github.com/opencollab/clang.debian.net/blob/master/logs/2020-02-24-9.0.1/chasen_2.4.5-44_unstable_clang9.0.1.log

I tried to make fix it, but still failed.
The patch is https://salsa.debian.org/nlp-ja-team/chasen/snippets/438

It has an another problem, linker error:

/bin/bash ../libtool  --tag=CXX   --mode=link g++  -g -O2
-fdebug-prefix-map=/home/knok/draft/debian/nlp-ja-team/chasen/chasen-tainted=.
-fstack-protector-strong -Wformat -Werror=format-security
-I/usr/include -version-info 2:4:0 -Wl,-z,relro -Wl,-z,now -o
libchasen.la -rpath /usr/lib/x86_64-linux-gnu block.lo chalib.lo
connect.lo dartsdic.lo getid.lo getopt.lo grammar.lo init.lo iotool.lo
jfgets.lo katuyou.lo lisp.lo literal.lo mmap.lo parse.lo print.lo
tokenizer.lo
libtool: link: g++  -fPIC -DPIC -shared -nostdlib
/bin/../lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crti.o
/bin/../lib/gcc/x86_64-linux-gnu/9/crtbeginS.o  .libs/block.o
.libs/chalib.o .libs/connect.o .libs/dartsdic.o .libs/getid.o
.libs/getopt.o .libs/grammar.o .libs/init.o .libs/iotool.o
.libs/jfgets.o .libs/katuyou.o .libs/lisp.o .libs/literal.o
.libs/mmap.o .libs/parse.o .libs/print.o .libs/tokenizer.o
-L/bin/../lib/gcc/x86_64-linux-gnu/9
-L/bin/../lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu
-L/bin/../lib/gcc/x86_64-linux-gnu/9/../../../../lib64
-L/lib/x86_64-linux-gnu -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu
-L/usr/lib/../lib64 -L/usr/lib/x86_64-linux-gnu/../../lib64
-L/bin/../lib/gcc/x86_64-linux-gnu/9/../../..
-L/usr/lib/llvm-9/bin/../lib -L/lib -L/usr/lib -lstdc++ -lm -lc
-lgcc_s -lgcc /bin/../lib/gcc/x86_64-linux-gnu/9/crtendS.o
/bin/../lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/crtn.o
-g -O2 -fstack-protector-strong -Wl,-z -Wl,relro -Wl,-z -Wl,now
-Wl,-soname -Wl,libchasen.so.2 -o .libs/libchasen.so.2.0.4
/bin/ld: .libs/dartsdic.o: in function
`Darts::Length::operator()(char const*) const':
/usr/include/darts.h:43: undefined reference to `strlen'
/bin/ld: /usr/include/darts.h:43: undefined reference to `strlen'
/bin/ld: .libs/dartsdic.o: in function
`std::char_traits::length(char const*)':
/bin/../lib/gcc/x86_64-linux-gnu/9/../../../../include/c++/9/bits/char_traits.h:335:
undefined reference to `strlen'
/bin/ld: 
/bin/../lib/gcc/x86_64-linux-gnu/9/../../../../include/c++/9/bits/char_traits.h:335:
undefined reference to `strlen'
/bin/ld: .libs/dartsdic.o: in function
`Darts::Length::operator()(char const*) const':
/usr/include/darts.h:43: undefined reference to `strlen'
/bin/ld: .libs/dartsdic.o:/usr/include/darts.h:43: more undefined
references to `strlen' follow
clang: error: linker command failed with exit code 1 (use -v to see invocation)

It seems `strlen' symbol is missig because of -nostdlib flag on the
linker via libtool.
I think it is llvm side problem, because autotools are trying to
handle toolchains as gcc, but llvm didn't work completely.

Bug#960828: eclipse-jdt-debug binary upload rejected

[Adrian Bunk]

Source: eclipse-jdt-debug
Version: 4.15-1
Severity: serious
Tags: ftbfs

bunk@coccia:~$ cat 
/srv/ftp-master.debian.org/queue/reject/eclipse-jdt-debug_4.15-1_all.changes.reason

Version check failed:
Your upload included the binary package libeclipse-jdt-debug-ui-java, version 
3.10.300+eclipse4.12-3, for all,
however testing already has version 3.10.300+eclipse4.12-3.
Uploads to unstable must have a higher version than present in testing.
bunk@coccia:~$

Bug#960829: minetest-mod-homedecor: should recommend instead of depend on minetest-mod-currency

[Ronny Standtke]

Package: minetest-mod-homedecor
Version: 20190922.1-1
Severity: normal

minetest-mod-homedecor currently depends on minetest-mod-currency. But
this is unnecessary as minetest-mod-homedecor works completely fine
without minetest-mod-currency. There is only an *optional* dependency in
homedecor_gastronomy. Therefore I think the package relationship can be
changed from "Depends" to "Recommends".

Best regards

Ronny

Bug#960830: fonts-jura: short description claims it is a monospaced font

[Andrei POPESCU]

Package: fonts-jura
Version: 5.103-1
Severity: normal

Dear Maintainer,

The short package description claims this is a monospaced font.

As can be seen also from the specimens on the homepage, it is clearly a
variable width font.

Kind regards,
Andrei


-- System Information:
Debian Release: 10.4
  APT prefers proposed-updates
  APT policy: (500, 'proposed-updates'), (500, 'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 3.18.0-12-ARCH (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8), 
LANGUAGE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

-- no debconf information

Bug#960817: yiyantang FTCBFS: builds for the build architecture

[atzlinux 肖盛文]

control: tags 960817 + fixed pending

Hi Helmut,

    Thanks for your patch.

I'd applied the patch and uploaded the new package to the mentors.

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


在 2020/5/17 下午12:48, Helmut Grohne 写道:
> Source: yiyantang
> Version: 0.7.0-7
> Tags: patch
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
>
> yiyantag fails to cross build from source, becuase it configures for the
> build architecture. Usually, fixing that requires passing --host, but in
> this case ./configure is too old and needs environment variables such as
> CC. A handy tool to export them is dpkg's buildtools.mk. While at it,
> the attached patch also fixes the very strange argument to --build
> passed to ./configure. Please consider applying it.
>
> Helmut

-- 
肖盛文 Faris Xiao
微信：atzlinux
ＱＱ：909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统：https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature

Bug#935868: liblog-dispatch-perl-perl: Abandoned upstream ⇒ consider removing from Debian

[intrigeri]

Hi,

The only reverse (build-)dependency in the archive is that
Log::Dispatch::Perl is used by RT (src:request-tracker4)'s test suite.
The use case looks entirely legitimate to me and I could not easily
find a suitable replacement.

This module was removed from CPAN but it can be found on BackPAN:

  https://cpan.metacpan.org/authors/id/E/EL/ELIZABETH/
  https://metacpan.org/release/ELIZABETH/Log-Dispatch-Perl-0.04

This module has a total of 111 SLOC, which appear to have worked just
fine since the last upstream release (2012).

The RT queue currently has 1 feature request 

  https://rt.cpan.org/Dist/Display.html?Name=Log-Dispatch-Perl

The maintenance cost on our side seems limited to keeping the
packaging up-to-date with current Debian best practices.

My current thinking is that it's OK to keep this package in the
archive, at least until it breaks with a new perl or Log-Dispatch
release (which seems unlikely to me).

What do others think?

If we agree to keep it:

 - I would drop the rm-candidate usertag.

 - I'm not sure what to do about the Homepage control field and
   debian/watch: shall we remove debian/watch and point the Homepage
   to BackPAN?

Finally, I've poked Karen Etheridge, who offered to take over the
module upstream in 2013 (!), on
https://rt.cpan.org/Ticket/Display.html?id=77369

Cheers!

Bug#960753: transition: yara

[Sebastian Ramacher]

Hi Hilko

On 2020-05-16 14:55:37 +0200, Sebastian Ramacher wrote:
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-yara.html
> Control: tags -1 + confirmed
> 
> On 2020-05-16 12:17:11 +0200, Hilko Bengen wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Dear release team,
> > 
> > the libyara3 -> libyara4 transition is necessary due to the simple
> > SONAME bump due to incompatible API and ABI changes. There are two
> > reverse dependencies, python-yara and libguestfs both of which I
> > maintain. libguestfs can already be built against with yara/4 and
> > python-yara/4.x will be uploaded at the same time as yara/4.
> 
> Go ahead.

The uploaded of yara 4.0.1-1 contained binaries for amd64 and all.
Please perform a source only upload so that yara will be able to migrate
to testing.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#956694: purify: FTBFS with spdlog 1.5.0

[Ole Streicher]

Hi Sebastian,

if spdlog does not ship with internal headersin Debian, shouldn't that
define be already set internally in spdlog?

Cheers

Ole

On 10.05.20 17:52, Sebastian Ramacher wrote:
> On 2020-05-10 17:45:00 +0200, Sebastian Ramacher wrote:
>> On 2020-04-26 10:49:31 +0200, Ole Streicher wrote:
>>> Control: affects -1 src:purify
>>>
>>> This now also affects the "purify" package, which is supposed to be
>>> rebuilt during the auto-casacore transition.
>> As far as I can tell, spdlog's pkg-config file adds
>> -DSPDLOG_FMT_EXTERNAL. With that define set, spdlog would use the
>> correct include files. However, purify seems to ignore these flag and
>> thus fails to build.
> … and spdlog's cmake config also contains this define.
>
> Best

Bug#960825: minetest-mod-player-3d-armor: should recommend minetest-mod-unified-inventory

[Ronny Standtke]

Package: minetest-mod-player-3d-armor
Version: 0.4.13-2
Severity: normal

minetest-mod-player-3d-armor should recommend
minetest-mod-unified-inventory because it is needed for putting on and
taking off the pieces of armor.

Best regards

Ronny

Bug#952326: libcrcutil: diff for NMU version 1.0-5.2

[Dmitry Smirnov]

On Sunday, 17 May 2020 3:30:46 PM AEST Adrian Bunk wrote:
> I've prepared an NMU for libcrcutil (versioned as 1.0-5.2) and uploaded
> it to DELAYED/15. Please feel free to tell me if I should cancel it.

Thank you for preparing this NMU. Much appreciated.

-- 
Cheers,
 Dmitry Smirnov.

---

The cure for the evils of democracy is more democracy.
-- H. L. Mencken


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

Bug#960827: nomad FTBFS: cannot find package "github.com/docker/docker/rootless"

[Dmitry Smirnov]

On Sunday, 17 May 2020 4:22:07 PM AEST Adrian Bunk wrote:
> src/github.com/docker/docker/registry/registry.go:22:2: cannot find
> package "github.com/docker/docker/rootless" in any of:
> /build/1st/nomad-0.10.5+dfsg1/_build/src/github.com/docker/docker/vendor/g
> ithub.com/docker/docker/rootless (vendor tree)

Yes, yes... Already fixed:

  https://salsa.debian.org/docker-team/docker/-/commit/4e4e7f42

-- 
Cheers,
 Dmitry Smirnov.

---

A Sunday school is a prison in which children do penance for the evil
conscience of their parents.
-- H. L. Mencken


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

Bug#934135: [Aptitude-devel] Bug#934135: aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer

[intrigeri]

Hi,

Guillem Jover (2019-08-09):
> After some thought, I think a local aptitude-specific wrapper might be
> even better and obviates the question of whether dpkg-parsechangelog
> should be moved or not. :)

FWIW, this makes sense to me.

> See the attached patch, which has seen no testing, but can do that
> once and if it is deemed a good path forward.

Thanks a lot!

Dear Aptitude maintainers, FYI this is now the last remaining blocker
for the removal of libparse-debian-changelog-perl, so I'm trying
to facilitate the integration of Guillem's patch:

I have applied Guillem's patch and fixed the typo mentioned below, on
top of current sid's 0.8.12-3 (after disabling the build of doc
translations as this makes the package FTBFS for me with current po4a;
same on the Reproducible Builds infra¹), and I did these tests:

 - `aptitude changelog apt` works
 - In the Aptitude UI I could view the changelog of both
   installed and non-installed packages.

I'm not sure if any of those exercises the affected code path.

I'm happy to do more tests if it helps fix this bug, but I would
need some guidance regarding what/how to test :)

> -dist_bin_SCRIPTS = aptitude-create-state-bundle aptitude-run-state-bundle
> +dist_bin_SCRIPTS = apitude-changelog-parser \
> + aptitude-create-state-bundle aptitude-run-state-bundle

Typo: apitute-changelog-parser → aptitude-changelog-parser

[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/aptitude.html

Bug#960831: RFS: yiyantang/0.7.0-7.1 [NMU] -- Terminal-based Chinese automatic encoding converter

[铜豌豆 Linux]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "yiyantang"

* Package name : yiyantang
Version : 0.7.0-7.1
Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstream's web site]
* License : [fill in]
* Vcs : https://salsa.debian.org/debian/yiyantang
Section : text

It builds those binary packages:

yiyantang - Terminal-based Chinese automatic encoding converter

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/y/yiyantang/yiyantang_0.7.0-7.1.dsc

Changes since the last upload:

* Non-maintainer upload.
* Fix FTCBFS: Let dpkg's buildtools.mk supply CC and friends to configure.
(Closes: #960817)
* Also fix bad argument to --build.

Regards,

-- 
肖盛文 Faris Xiao
邮箱：atzli...@yeah.net
微信：atzlinux
ＱＱ：909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统：https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature

Bug#960814: diffoscope: comparing an unsigned and a signed buildinfo file gives a hex diff

[Chris Lamb]

forwarded 960814 
https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/122
thanks

I've forwarded this 'upstream' here:

  https://salsa.debian.org/reproducible-builds/diffoscope/-/issues/122


Regards,

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

Bug#945467: Fix available (fwd)

[Jeremy Sanders]

Hi Andreas

Thanks very much for looking at this. I forgot to update my build 
environment and something has changed in the extension module naming 
since then. I'm sorry about that. I've put in a fix to the repo, and 
checked it builds in pbuilder on an up to date sid.


Thanks again

Jeremy

On 16/05/2020 21:23, Andreas Tille wrote:

Hi Jeremy,

please make sure to inject pristine-tar (according to Debian Science
policy).  I did so now.  Unfortunately the package does not build in
a pbuilder chroot:

...
dh_sip3
make[1]: Leaving directory '/build/veusz-3.2.1'
dh_install -O--buildsystem=pybuild
dh_install: warning: Cannot find (any matches for) 
"usr/lib/python3*/*-packages/veusz/helpers/*.cpython-[0-9]*[!d]m-*.so" (tried 
in ., debian/tmp)

dh_install: warning: python3-veusz.helpers missing files: 
usr/lib/python3*/*-packages/veusz/helpers/*.cpython-[0-9]*[!d]m-*.so
dh_install: error: missing files, aborting
make: *** [debian/rules:23: binary] Error 25
...

Kind regards

   Andreas.

On Sat, May 16, 2020 at 03:05:10PM +0300, Adrian Bunk wrote:

Andreas, could you sponssor that one?
You already sponsored the latest 2 uploads of this package.

Thanks
Adrian


- Forwarded message from Jeremy Sanders  -

Date: Fri, 17 Apr 2020 09:10:00 +0200
From: Jeremy Sanders 
To: 945...@bugs.debian.org
Subject: Bug#945467: Fix available
Resent-From: Jeremy Sanders 
Resent-To: debian-bugs-dist@lists.debian.org
Resent-Date: Fri, 17 Apr 2020 07:21:01 +

I've updated the version control to have the latest version of Veusz, 3.2.1,
which should fix this bug:
https://salsa.debian.org/science-team/veusz

It would be great if a developer with permissions could have a look and
consider uploading it.

Thanks

Jeremy

- End forwarded message -

Bug#873809: Packaging newer upstreams

[Ronny Standtke]

Hi all

I just wanted to let you know that I packaged the current WorldEdit mod
version (v1.2 plus git master branch) here:
https://packages.lernstick.ch/lernstick/pool/main/m/minetest-mod-worldedit/

I am not a Debian maintainer or Debian developer myself. I just hope
that this somehow helps fixing this bug. Please let me know if there is
something else I can do.

Best regards

Ronny

Bug#935867: libclass-forward-perl: Abandoned upstream ⇒ consider removing from Debian

[intrigeri]

Hi,

so, indeed this dist is not on CPAN anymore, although its author is
still very active: https://metacpan.org/author/AWNCORP

Given the functionality this module provides, to me it sounds like
this was a potential good idea at the time, worth trying, but no CPAN
author found it useful enough to use it, and it was abandoned.

There's no reverse-dependency in the archive, popcon says
5 installations, 1 vote, and only 1 recent.

I propose we remove this module from Debian.

FTR, this dist can be found on BackPAN:
http://backpan.perl.org/authors/id/A/AW/AWNCORP/

Bug#960626: Solution

[cyrille]

Hi,

 

I've received help from some nice guy on #debian-boot

 

The problem is in all likelihood linked to this strange partition layout
shown by parted.

 

Anyway, here's the trick I used to solve my issue:

 

1- format my USB stick using a GPT partition table

2- create a single vfat partition of type ef00 spanning the whole USB stick
(I've used gdisk to be able to set the partition's type)

3- mount the partition

4- mount the debian iso

5- copy all files from the debian iso to the partition (taking care to also
copy the ".disk" folder), while ignoring the several warnings that some
symbolic links can't be copied 

6- unmount the partition

7- use the USB disk to install debian on my new hp laptop

 

That's it.

 

So, my issue is solved: You may do wathever you like with this bug report
now.

 

Thanks to the folks on #debian-boot for the assistance.

 

Cyrille

Bug#960823: minetest-mod-moreblocks: should recommend minetest-mod-intllib

[Ronny Standtke]

Package: minetest-mod-moreblocks
Version: 2.0.0-1
Severity: normal

minetest-mod-moreblocks should recommend minetest-mod-intllib because it
is needed for showing the translated block descriptions.


Best regards

Ronny

Bug#960824: restinio: Missing atomic library on several architectures

[Petter Reinholdtsen]

Package: restinio
Version: 0.6.6-1
Tags: upstream

The package fail to build on several architectures.  The issue at hand
seem to be missing atomic support in the compiler.  I found a similar
problem and a proposed CMake fix in
https://github.com/kimwalisch/primesieve/pull/46 >.

-- 
Happy hacking
Petter Reinholdtsen

Bug#960632: src:plm: Please add support to build against libjson-simple-java >= 3

[Martin Quinson]

Hello Gilles,

many thanks for your help, this package is in a rather sorry state,
and I promise myself to do something about it since a long time.
Hopefully this will be the nodge I needed :)

I happen to be the upstream maintainer of this software, and I'd like
to make things simpler if possible. Is it possible to update the code
so that the patch does not depend on the used version?

I will try to apply this patch, and then patch upstream to use json-simple-3 
only.

Thanks, Mt.

On Thu, May 14, 2020 at 11:28:01PM +0200, Gilles Filippini wrote:
> Package: src:plm
> Version: 2.6+repack-3
> Severity: normal
> Tags: patch
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hi,
> 
> I'd like to transition json-simple 3.1.1 to unstable, but plm is a blocker 
> since it builds against libjson-simple-java << 3 only.
> 
> The json-simple classes used by plm were deprecated in version 2.0.0 [1]. 
> There were removed in versions 3.x [2].
> 
> [1] 
> https://github.com/cliftonlabs/json-simple/blob/json-simple-2.0.0/README.txt
> [2] 
> https://github.com/cliftonlabs/json-simple/blob/json-simple-3.0.1/CHANGELOG
> 
> Please find attached a patch proposal to use the current json-simple classes. 
> I've tested that the package builds correctly against libjson-simple-java 
> version 2.3.0-1 from unstable and version 3.1.1-1~exp2 currently in 
> experimental. But I don't known how to test the package afterward.
> 
> Thanks in advance for considering.
> 
> _g.
> 
> -- System Information:
> Debian Release: buster/sid
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
> 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
> 
> 

> diff -Nru plm-2.6+repack/debian/changelog plm-2.6+repack/debian/changelog
> --- plm-2.6+repack/debian/changelog   2016-09-18 16:39:19.0 +0200
> +++ plm-2.6+repack/debian/changelog   2020-05-14 18:05:12.0 +0200
> @@ -1,3 +1,10 @@
> +plm (2.6+repack-3.1) UNRELEASED; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Tentative patch to build against json-simple 3
> +
> + -- Gilles Filippini   Thu, 14 May 2020 18:05:12 +0200
> +
>  plm (2.6+repack-3) unstable; urgency=medium
>  
>* Add run-time dependencies on default-jdk, jython and jruby.
> diff -Nru plm-2.6+repack/debian/patches/json-simple-3.patch 
> plm-2.6+repack/debian/patches/json-simple-3.patch
> --- plm-2.6+repack/debian/patches/json-simple-3.patch 1970-01-01 
> 01:00:00.0 +0100
> +++ plm-2.6+repack/debian/patches/json-simple-3.patch 2020-05-14 
> 18:05:12.0 +0200
> @@ -0,0 +1,595 @@
> +Description: Migrate away from deprecated json-simple 1.x classes
> + See json-simple 2.0.0 changelog:
> + > * Deprecated JSONParse and JSONValue in favor of Jsoner.
> + > * Deprecated JSONStreamAware and JSONAware in favor of Jsonable.
> + > * Deprecated JSONObject in favor of JsonObject.
> + > * Deprecated JSONArray in favor of JsonArray.
> + .
> + This patch uses the new json-simple Json* classes. It is compatible with
> + both 2.x and 3.x json-simple releases, with a few ajustments regarding
> + backward incompatible changes in json-simple 3.x:
> + - The package name, changed to com.github.cliftonlabs.json_simple
> + - The exception DeserializationExcetpion renamed as JsonException
> + These two changes are handled using place-holders @JSON_SIMPLE_PACKAGE@
> + and @JSON_EXCETPION@ which are substituted at build time by debian/rules.
> + .
> + With these tricks the package is compatible with json-simple 2.x and 3.x.
> +Author: Gilles Filippini 
> +Index: plm-2.6+repack/src/plm/core/model/Course.java
> +===
> +--- plm-2.6+repack.orig/src/plm/core/model/Course.java
>  plm-2.6+repack/src/plm/core/model/Course.java
> +@@ -4,9 +4,9 @@ import java.io.IOException;
> + import java.util.ArrayList;
> + import java.util.Map;
> + 
> +-import org.json.simple.JSONArray;
> +-import org.json.simple.JSONObject;
> +-import org.json.simple.JSONValue;
> ++import @JSON_SIMPLE_PACKAGE@.JsonArray;
> ++import @JSON_SIMPLE_PACKAGE@.JsonObject;
> ++import @JSON_SIMPLE_PACKAGE@.Jsoner;
> + 
> + /**
> +  * Class to manage course data online
> +@@ -50,7 +50,7 @@ public abstract class Course {
> +  * A user password is set to push data, a teacher password to 
> administrate course
> +  */
> + public ServerAnswer create() {
> +-JSONObject jsonObject = new JSONObject();
> ++JsonObject jsonObject = new JsonObject();
> + jsonObject.put("action", "new");
> + jsonObject.put("course", courseId);
> + jsonObject.put("password", password);
> +@@ -72,7 +72,7 @@ public abstract class Course {
> +  * and by exercise
> +  */
> + public String refresh() {
> +-JSONObject jsonObject = new 

Bug#906727: file: Shared libraries wrongly detected as 'pie executable'

[Christoph Biedl]

Control: found 906727 1:5.35-4+deb10u1
Control: fixed 906727 1:5.37-1

WHR wrote...

> I found the file(1) tool on Debian buster would erroneously detect ELF shared 
> libraries as 'pie executable'; for example:
> 
> ~/src$ cat sample.c 
> #include 
> 
> void func1(int a) {
>   fprintf(stderr, "function: func1(%d)\n", a);
> }
> ~/src$ gcc -Wall -O1 --shared sample.c -o libsample.so
> ~/src$ file libsample.so 
> libsample.so: ELF 32-bit LSB pie executable, Intel 80386, version 1 (SYSV), 
> dynamically linked, BuildID[sha1]=56c53c1ca858c31c2d58bf9ee80e3eb9ff4ac36d, 
> not stripped

That was introduced in upstream commit
FILE5_32-87-g6876ebad
and later fixed in
FILE5_35-45-g03084b16

So, only the buster version is affected. I've queued this up for a
stable point release but am somewhat concerned about side effects, there
have been issues with the ELF detection in the past.

Christoph




signature.asc
Description: PGP signature

Bug#958170: file: misidentifies wikicode '''foo''' as troff

[Christoph Biedl]

Vincent Lefevre wrote...

> The file utility misidentifies wikicode '''foo''' as troff.

Thanks for already forwarding upstream, let's see what will happen there.

Just a clarification, AFAICS this is valid troff as well, and probably
the submitter assumed that sequence does not appear anywhere else and
use it for identification:

https://github.com/file/file/blob/master/magic/Magdir/troff#L17

Sorting this out is not an easy job.

Christoph



signature.asc
Description: PGP signature

Bug#960160: mutt: stack overflow DoS fixed in 1.14

[Salvatore Bonaccorso]

Source: mutt
Source-Version: 1.14.0-1

Hi,

On Sun, May 10, 2020 at 02:28:01AM +, A mutt user wrote:
> Relevant upstream commit is 758d406ede97ad627ab804ab049e77396d18746c
> https://gitlab.com/muttmua/mutt.git

This one was included in the mutt upload to unstable as 1.14.0-1, so
track the fixed version for there.

Regards,
Salvatore

Bug#958170: file: misidentifies wikicode '''foo''' as troff

[Vincent Lefevre]

On 2020-05-17 09:13:56 +0200, Christoph Biedl wrote:
> Vincent Lefevre wrote...
> 
> > The file utility misidentifies wikicode '''foo''' as troff.
> 
> Thanks for already forwarding upstream, let's see what will happen there.
> 
> Just a clarification, AFAICS this is valid troff as well, and probably
> the submitter assumed that sequence does not appear anywhere else and
> use it for identification:
> 
> https://github.com/file/file/blob/master/magic/Magdir/troff#L17
> 
> Sorting this out is not an easy job.

Well, the triple quote just means bold text in wikicode. Thus it can
appear at arbitrary places. Note also that it is also used in some
programming languages (e.g. Python). So basing the recognition on
the occurrence of this sequence only is too ambiguous.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#960656: sdpb: FTBFS on mipsel

[Sebastiaan Couwenberg]

On Fri, 15 May 2020 10:10:19 +0200 Sebastian Ramacher wrote:
> sdpb failed to build on mipsel while rebuilding for the tinyxml2 transition:
> https://buildd.debian.org/status/fetch.php?pkg=sdpb=mipsel=1.0-3%2Bb5=1589492907=0

sdpb has been removed from mipsel (#960747) to unblock the transition.

Kind Regards,

Bas

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

Bug#929181: libmagic1: "brotli" compression not detected

[Christoph Biedl]

Control: tags 929181 upstream
Control: forwarded 929181 
https://mailman.astron.com/pipermail/file/2020-May/000336.html
Control: severity 929181 wishlist
Control: retitle 929181 New magic: "brotli" compression

Philipp Marek wrote...

> Please include detection for the "brotli" compression algorithm.

This doesn't look like an easy job but it's on the list now.

Regards,
Christoph


signature.asc
Description: PGP signature

Bug#960826: libquazip FTBFS on 32bit: symbol difference

[Adrian Bunk]

Source: libquazip
Version: 0.9-1
Severity: serious
Tags: ftbfs

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

...
dpkg-gensymbols -plibquazip5-1 -Idebian/libquazip5-1.symbols 
-Pdebian/libquazip5-1 
-edebian/libquazip5-1/usr/lib/i386-linux-gnu/libquazip5.so.1.0.0
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libquazip5-1/DEBIAN/symbols doesn't match 
completely debian/libquazip5-1.symbols
--- debian/libquazip5-1.symbols (libquazip5-1_0.9-1_i386)
+++ dpkg-gensymbolsEylc_P   2020-05-16 15:33:10.245761374 +
@@ -331,7 +331,8 @@
  _ZNK9QuaZipDir9entryListE6QFlagsIN4QDir6FilterEES0_INS1_8SortFlagEE@Base 0.7.3
  
_ZNK9QuaZipDir9entryListERK11QStringList6QFlagsIN4QDir6FilterEES3_INS4_8SortFlagEE@Base
 0.7.3
  _ZNK9QuaZipDirixEi@Base 0.7.3
- 
_ZSt13__adjust_heapIN5QListI16QuaZipFileInfo64E8iteratorExS1_N9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_T0_SA_T1_T2_@Base
 0.9
+ 
_ZSt13__adjust_heapIN5QListI16QuaZipFileInfo64E8iteratorEiS1_N9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_T0_SA_T1_T2_@Base
 0.9-1
+#MISSING: 0.9-1# 
_ZSt13__adjust_heapIN5QListI16QuaZipFileInfo64E8iteratorExS1_N9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_T0_SA_T1_T2_@Base
 0.9
  
_ZSt13__heap_selectIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_S9_T0_@Base
 0.9
  
_ZSt16__insertion_sortIN5QListI16QuaZipFileInfo64E8iteratorEN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_T0_@Base
 0.9
  
_ZSt16__introsort_loopIN5QListI16QuaZipFileInfo64E8iteratorEiN9__gnu_cxx5__ops15_Iter_comp_iterI19QuaZipDirComparatorEEEvT_S9_T0_T1_@Base
 0.9
dh_makeshlibs: error: failing due to earlier errors
mv debian/.debhelper/generated/libquazip5-1/triggers.new 
debian/.debhelper/generated/libquazip5-1/triggers
rm -f debian/libquazip5-dev/DEBIAN/shlibs
make: *** [debian/rules:19: binary-arch] Error 25

Bug#930547: Detect common Android file types

[Christoph Biedl]

Control: tags 930547 moreinfo

積丹尼 Dan Jacobson wrote...

> # apt install anbox
> $ set /var/lib/anbox/rootfs/file_contexts.bin
> $ file $@
> /var/lib/anbox/rootfs/file_contexts.bin: data

/var/lib/anbox/rootfs/file_contexts.bin: cannot open 
`/var/lib/anbox/rootfs/file_contexts.bin' (No such file or directory)

Something is missing here, and it's not obvious to me how to create or
retrieve that file.

Possibly these are created by sefcontext_compile from the
sefcontext_compile package, but that's just wild guessing.

Christoph


signature.asc
Description: PGP signature

Bug#846667: [rt.cpan.org #119351] occasional failures of t/poe_loop_event/wheel_run.t

[intrigeri via RT]

https://rt.cpan.org/Ticket/Display.html?id=119351 >

Dear Maintainer,

The Debian perl group is reviewing packages with bugs which make them
un-releasable; in particular when they are not heavily used by Debian users.
We would like to remove such modules from Debian if we don't think they are
likely to be fixed.

POE::Loop::Event is one such module, owing to this bug, and we would like to
know whether you have any plans to look at the bug in the foreseeable future
before we remove the package from Debian.

If we don't hear anything we will remove the package from Debian at some point,
though not earlier than June 8.

This of course does not affect the standing of your module on CPAN.

Thank you for maintaining this module so far!

Bug#923396: file -e should silently ignore nonexistent testnames

[Christoph Biedl]

Control: tags 923396 confirmed moreinfo

Vincent Lefevre wrote...

> I get the following error:
(...)
> because testname foo does not exist. This should silently be ignored,
> so that if the testname is added in a later version, one can
> unconditionally use "file -e foo" on all machines.
> 
> As an example, "file -e json" works in Debian/unstable, but not
> in stretch.

While I understand the wish to create scripts around file(1) that work
in all Debian distributions, and I'd agree probing the features of the
available file(1) version first is annoying and painful ... I am somewhat
uneasy about that particular way of solving issue: If anyone
accidentially mistypes the requested testname, file(1) will happily
continue while it certainly should break then.

Can we find another way of handling your request?

One idea was relaxing that check, but via an additional option and not
by default. Feels bad since this a permanent digression from upstream.

Another idea was using backports. They have been requested in several
places and I'm confident there will be a way to provide them on a
regular base soon.

And finally, I could hack the known testnames into old versions, making
them a no-op there. If you convince SRT to accept that, I'll be happy to
do my part.

... and I'm open for other ideas.

Cheers,

Christoph



signature.asc
Description: PGP signature

Bug#960832: dch, fix with --vendor=Debian?

[Gianfranco Costamagna]

Hello again, I'm not sure but this might be a fix for the issue:

It works, but I'm not sure if this is a good fix or not, I'm not tagging the 
bug as "patch" :)

--- lintian-brush-0.64/lintian_brush/__init__.py2020-05-16 
16:33:36.0 +0200
+++ lintian-brush-0.64ubuntu2/lintian_brush/__init__.py 2020-05-17 
12:55:43.0 +0200
@@ -617,7 +617,7 @@
   path: Path to the changelog file
   summary: Entry to add
 """
-args = ["dch", "--no-auto-nmu"]
+args = ["dch", "--no-auto-nmu", "--vendor=debian"]
 if qa:
 args.append('--qa')
 p = subprocess.Popen(


thanks for considering it and maintaining the package,

Gianfranco

Bug#960301: firefox-esr: [regression] cannot find the microphone

[Francesco Poli]

On Sun, 17 May 2020 07:19:59 +0900 Mike Hommey wrote:

> On Sun, May 17, 2020 at 07:16:50AM +0900, Mike Hommey wrote:
[...]
> > Are you using pulseaudio?

No, I am using jackd (JACK Audio Connection Kit), with the well known
ALSA configuration file ~/.asoundrc that redirects applications using
ALSA to the ports provided by JACK.

In case you need to see the details of my audio configuration, they are
[documented] on my website.

[documented]: 


Needless to say, the audio configuration is the same that works
perfectly with firefox-esr/68.7.0esr-1 ...

> > If not, can you try setting
> > security.sandbox.content.level to 5 in about:config?
> 
> Err, make that 1, rather. Or 0.

Let me see.

After upgrading again to 68.8.0esr-1:

  [UPGRADE] firefox-esr:amd64 68.7.0esr-1 -> 68.8.0esr-1

For each of the following values I set the level, restarted firefox,
and tested the microphone again on .

The outcome was:

security.sandbox.content.level   microphone
===
   0  fails
   1 no page loading at all
   4 (default)fails
   5  fails



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp2B21xOcjJw.pgp
Description: PGP signature

Bug#960835: Debian Jessie site lists only 4 archs as supported

[Holger Wansing]

Package: www.debian.org
Severity: normal
X-Debbugs-CC: b...@decadent.org.uk

Debians Jessie release page lists only 4 archs (i386, amd64, armel and armhf) 
as 
supported archs. These are the LTS-supported archs.
This is inconsistent with the other release pages. They globally list all 
archs, 
which have been supported in the initial release (aka Debian 8.0 in this case).

This situation was introduced with the last point release 8.11.1 in commit
https://salsa.debian.org/webmaster-team/webwml/-/commit/0a388832cb4a7e9dfe1265fa04d1c441e9730e23
(Ben as committer in x-debbugs-cc).

To keep the webpage consistent, there is needed another concept to show the 
current state of archs (4 archs still supported via LTS, the other ones no
longer supported).


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#845807: libterm-editoredit-perl: uses deprecated Any::Moose

[intrigeri]

Hi,

Niko Tyni (2016-11-26):
> The only reverse dependency is pinto […]

The Changes file for the last pinto upstream release (0.14000) reads:

  Switched to an internal fork of Term::EditorEdit to avoid unwanted
  dependency on deprecated module Any::Moose

On top of that:

 - popcon show only a few more votes for libterm-editoredit-perl than
   for pinto.

 - Term::EditorEdit authors never commented on the upstream bug report
   since 5 years.

⇒ I propose we update pinto, then remove libterm-editoredit-perl
from sid.

Bug#845811: libwww-nicovideo-download-perl: uses deprecated Any::Moose

[intrigeri]

Control: forwarded -1 https://rt.cpan.org/Ticket/Display.html?id=132647

Hi,

Niko Tyni (2016-11-26):
> There are no reverse dependencies in Debian.

That's still the case. Add to this: no upstream release since 10
years, very low popcon.

I propose we remove this package if upstream does not answer within
3 months.

Bug#845809: libtext-clip-perl: uses deprecated Any::Moose

[intrigeri]

Hi,

Niko Tyni (2016-11-26):
> The only reverse dependency is libterm-editoredit-perl, which also
> use Any::Moose (see #845807).

On #845807 I've proposed a way forward to remove
libterm-editoredit-perl.

> The upstream ticket has had no comment from the maintainer in 1.5 years.

… make that 5 years.

Upstream is inactive and popcon is very low.

I propose we remove libtext-clip-perl once libterm-editoredit-perl
is gone.

Bug#960838: get-flash-videos: Abandoned upstream, broken for many use cases ⇒ consider removing

[intrigeri]

Package: get-flash-videos
Severity: normal
User: debian-p...@lists.debian.org
Usertags: rm-candidate

AFAICT upstream has been inactive for 2 years.

This kind of software needs constant updating to remain useful, as
indicated by #750872 and the pile of non-handled upstream bug reports
that report breakage on website X or Y.

Given this, it's not surprise to me that popcon has been steadily
decreasing since 2015.

In contrast, youtube-dl is actively maintained and its popcon steadily
increasing. Judging by the package descriptions, youtube-dl claims to
support vastly more websites, including most of those that
get-flash-videos itself claims to support.

So at first glance, I don't think we're serving our users well by
including get-flash-videos in the distribution. I'd rather see them
not have to wonder and choose, and instead directly find the best
maintained piece of software.

On top of this,get-flash-videos is the only reverse-dependency of
libdata-amf-perl, which causes trouble (#845812).

I propose we remove both packages from the archive.
Thoughts?

Bug#960859: node-clipboard: broken symlink to /usr/share/javascript/clipboard.js

[Doug Torrance]

Package: node-clipboard
Version: 2.0.6+ds-2
Severity: important
Tags: patch

Dear Maintainer,

There is a typo in debian/links which causes a broken symlink:

profzoom@gloria:~$ test -e /usr/share/javascript/clipboard.js; echo $?
1
profzoom@gloria:~$ ls -l /usr/share/javascript/clipboard.js
lrwxrwxrwx 1 root root 24 May 10 04:42 /usr/share/javascript/clipboard.js 
-> ../nodejs/clibboard/dist

In particular, "clipboard" is misspelled as "clibboard".

I have submitted a merge request at Salsa [1] and have attached a patch.

Thanks!
Doug

[1] https://salsa.debian.org/js-team/node-clipboard/-/merge_requests/1
>From 2bc8ed1bbba19dea16bd82b711125b20ac5eff7c Mon Sep 17 00:00:00 2001
From: Doug Torrance 
Date: Wed, 13 May 2020 22:41:22 -0400
Subject: [PATCH] Fix typo

---
 debian/links | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/links b/debian/links
index 1303eb0..eaf4159 100644
--- a/debian/links
+++ b/debian/links
@@ -1 +1 @@
-/usr/share/nodejs/clibboard/dist /usr/share/javascript/clipboard.js
+/usr/share/nodejs/clipboard/dist /usr/share/javascript/clipboard.js
-- 
2.20.1

Bug#919872: new magic: HDT (RDF) files

[Christoph Biedl]

Control: tags 919872 confirmed upstream
Control: forwarded 919872 
https://mailman.astron.com/pipermail/file/2020-May/000337.html

chrysn wrote...

> A working rule set for those files I'd suggest is:
> 
> 0 string $HDT HDT file (binary compressed indexed RDF triples)
> !:mime application/vnd.hdt
> 
> I'm not sure whether `file` keeps track of common file extensions; if
> it's relevant: such files typically have names ending with `.hdt`.

Thanks for the input, that rule set is a bit too weak so I added the
type number (binary 1) at offset 4 to strengthen the detection.

And yes, file(1) can handle file extensions as well, taken care of.

Regards,

Christoph


signature.asc
Description: PGP signature

Bug#957288: Fixed in Gentoo (by myself)

[MindMe Incorporated]

Dear Debian,

I hope I got the process of submitting a patch right :)

https://bugs.gentoo.org/attachment.cgi?id=639798=edit

Thanks,
Tom

Bug#937314: Removed python2 from b-ds

[Jann Haber]

I think I fixed this bug, by simply removing the python-all and 
python-setuptools from the b-ds. These seem to be unused anyway.


Created an MR in Salsa: 
https://salsa.debian.org/lavamind/powerline-gitstatus/-/merge_requests/4

Bug#960824: restinio: Missing atomic library on several architectures

[Petter Reinholdtsen]

Control: forwarded -1 https://github.com/Stiffstream/restinio/issues/98

I've registered an issue upstream tracking this problem.

-- 
Happy hacking
Petter Reinholdtsen

Bug#960836: buster-pu: package gnutls28/3.6.7-4+deb10u4

[Andreas Metzler]

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

Hello,

I would like to update gnutls to fix #95664 aka
https://gitlab.com/gnutls/gnutls/-/issues/841 fixing TLS1.2 client side
resumption errors. And while I am at it I would also pick a one-line
fix for a memory leak (Fix requested in #958704.)

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru gnutls28-3.6.7/debian/changelog gnutls28-3.6.7/debian/changelog
--- gnutls28-3.6.7/debian/changelog	2020-04-03 21:31:50.0 +0200
+++ gnutls28-3.6.7/debian/changelog	2020-05-17 13:45:29.0 +0200
@@ -1,3 +1,12 @@
+gnutls28 (3.6.7-4+deb10u4) buster; urgency=medium
+
+  * 42_rel3.6.11_10-session-tickets-parse-extension-during-session-resum.patch
+from GNUTLS 3.6.11: Fix TL1.2 resumption errors. Closes: #956649
+  * 47_rel3.6.14_10-session_pack-fix-leak-in-error-path.patch from GNUTLS
+3.6.14: One line fix for memory leak. Closes: #958704
+
+ -- Andreas Metzler   Sun, 17 May 2020 13:45:29 +0200
+
 gnutls28 (3.6.7-4+deb10u3) buster-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru gnutls28-3.6.7/debian/patches/42_rel3.6.11_10-session-tickets-parse-extension-during-session-resum.patch gnutls28-3.6.7/debian/patches/42_rel3.6.11_10-session-tickets-parse-extension-during-session-resum.patch
--- gnutls28-3.6.7/debian/patches/42_rel3.6.11_10-session-tickets-parse-extension-during-session-resum.patch	1970-01-01 01:00:00.0 +0100
+++ gnutls28-3.6.7/debian/patches/42_rel3.6.11_10-session-tickets-parse-extension-during-session-resum.patch	2020-05-17 10:08:09.0 +0200
@@ -0,0 +1,610 @@
+From afa6e340c084542ef416afc96dd0329f5507 Mon Sep 17 00:00:00 2001
+From: Nikos Mavrogiannopoulos 
+Date: Tue, 8 Oct 2019 07:23:31 +0200
+Subject: [PATCH] session tickets: parse extension during session resumption on
+ client side
+
+It is possible for a server to send a new session ticket during
+TLS1.2 resumption. To be able to parse it as client we need to
+check the extension during resumption as well.
+
+Resolves: #841
+
+Signed-off-by: Nikos Mavrogiannopoulos 
+---
+ NEWS|  3 +++
+ lib/ext/alpn.c  |  3 ++-
+ lib/ext/client_cert_type.c  |  3 ++-
+ lib/ext/cookie.c|  3 ++-
+ lib/ext/dumbfw.c|  3 ++-
+ lib/ext/early_data.c|  3 ++-
+ lib/ext/ec_point_formats.c  |  3 ++-
+ lib/ext/etm.c   |  3 ++-
+ lib/ext/ext_master_secret.c |  3 ++-
+ lib/ext/heartbeat.c |  3 ++-
+ lib/ext/key_share.c |  3 ++-
+ lib/ext/max_record.c|  3 ++-
+ lib/ext/post_handshake.c|  3 ++-
+ lib/ext/pre_shared_key.c|  3 ++-
+ lib/ext/psk_ke_modes.c  |  3 ++-
+ lib/ext/record_size_limit.c |  3 ++-
+ lib/ext/safe_renegotiation.c|  3 ++-
+ lib/ext/server_cert_type.c  |  3 ++-
+ lib/ext/server_name.c   |  3 ++-
+ lib/ext/session_ticket.c|  7 ++-
+ lib/ext/signature.c |  3 ++-
+ lib/ext/srp.c   |  3 ++-
+ lib/ext/srtp.c  |  3 ++-
+ lib/ext/status_request.c|  3 ++-
+ lib/ext/supported_groups.c  |  3 ++-
+ lib/ext/supported_versions.c|  3 ++-
+ lib/hello_ext.c | 36 ++---
+ lib/hello_ext.h |  3 ++-
+ lib/includes/gnutls/gnutls.h.in |  4 ++--
+ tests/gnutls-cli-resume.sh  | 17 
+ 30 files changed, 98 insertions(+), 44 deletions(-)
+
+ 
+diff --git a/lib/ext/alpn.c b/lib/ext/alpn.c
+index b9991f0a1..7cc799756 100644
+--- a/lib/ext/alpn.c
 b/lib/ext/alpn.c
+@@ -39,7 +39,8 @@ const hello_ext_entry_st ext_mod_alpn = {
+ 	.tls_id = 16,
+ 	.gid = GNUTLS_EXTENSION_ALPN,
+ 	/* this extension must be parsed even on resumption */
+-	.parse_type = GNUTLS_EXT_MANDATORY,
++	.client_parse_point = GNUTLS_EXT_MANDATORY,
++	.server_parse_point = GNUTLS_EXT_MANDATORY,
+ 	.validity = GNUTLS_EXT_FLAG_TLS | GNUTLS_EXT_FLAG_DTLS |
+ 		GNUTLS_EXT_FLAG_CLIENT_HELLO | GNUTLS_EXT_FLAG_EE |
+ 		GNUTLS_EXT_FLAG_TLS12_SERVER_HELLO,
+diff --git a/lib/ext/client_cert_type.c b/lib/ext/client_cert_type.c
+index b627b71f9..34f4dcfa4 100644
+--- a/lib/ext/client_cert_type.c
 b/lib/ext/client_cert_type.c
+@@ -48,7 +48,8 @@ const hello_ext_entry_st ext_mod_client_cert_type = {
+ 	.name = "Client Certificate Type",
+ 	.tls_id = 19,
+ 	.gid = GNUTLS_EXTENSION_CLIENT_CERT_TYPE,
+-	.parse_type = GNUTLS_EXT_TLS,
++	.client_parse_point = GNUTLS_EXT_TLS,
++	.server_parse_point = GNUTLS_EXT_TLS,
+ 	.validity = GNUTLS_EXT_FLAG_TLS |
+ 		GNUTLS_EXT_FLAG_DTLS |
+ 		GNUTLS_EXT_FLAG_CLIENT_HELLO |
+diff --git a/lib/ext/cookie.c b/lib/ext/cookie.c
+index 0feb2f0e5..b4608f3a9 100644
+--- a/lib/ext/cookie.c
 b/lib/ext/cookie.c
+@@ -41,7 +41,8 @@ const hello_ext_entry_st 

Bug#882086: Same on Packard bell TS11HR-200GE i7-2630QM Intel HD 3000

[Ben Hutchings]

On Sat, 2020-05-16 at 21:30 +0200, Umut Erdogan wrote:
> Package: src:linux
> Version: 4.9.210-1
> Followup-For: Bug #882086
> 
> I am having the same problem.
> as a workaround you can hibernate using
> echo disk > /sys/power/state as root.
> Doing this, resume works quite fine.
> 
> I have found this possible kernel patch and I wanted to know if this patch is
> already assembled in my current debian kernel:
> https://patchwork.kernel.org/patch/9169527/

That's for an entirely different driver so it's not relevant.

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky




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

Bug#960752: FTBFS on arch-all, test-suite failure - conova buildd has broken "localhost"

[Aurelien Jarno]

control: tag -1 + ipv6

On 2020-05-16 19:27, Aurelien Jarno wrote:
> On 2020-05-16 17:45, Martin Pitt wrote:
> > Michael Biebl [2020-05-16 12:39 +0200]:
> > > Source: cockpit
> > > Version: 219-1
> > > Severity: serious
> > > 
> > > Hi Martin,
> > > 
> > > looks like the latest release reliably triggers a FTBFS on arch-all:
> > > 
> > > https://buildd.debian.org/status/logs.php?pkg=cockpit=219-1=all
> > > 
> > > The relevant part from the build log
> > > **
> > > cockpit-protocol:ERROR:src/common/test-webserver.c:374:perform_request: 
> > > assertion failed (error == NULL): Error resolving 
> > > ?2a02:16a8:dc41:100::238:46259?: Name or service not known 
> > > (g-resolver-error-quark, 0)

The address 2a02:16a8:dc41:100::238:46259 is not correct. When combining
and IPv6 address and a port, the address must be escaped with []. This
means that the following code from test-webserver.c is incorrect:

|   inet = cockpit_test_find_non_loopback_address ();
|   /* this can fail in environments with only localhost */
|   if (inet != NULL)
| str = g_inet_address_to_string (inet);

  ...

|   if (str)
| tc->hostport = g_strdup_printf ("%s:%d", str, port);

As g_network_address_parse() supports escaping addresses with [] even
for IPv4 addresses, I guess the following *untested* patch should fix
the issue.

--- a/src/common/test-webserver.c
+++ b/src/common/test-webserver.c
@@ -93,7 +93,7 @@
   /* HACK: this should be "localhost", but this fails on COPR; 
https://github.com/cockpit-project/cockpit/issues/12423 */
   tc->localport = g_strdup_printf ("127.0.0.1:%d", port);
   if (str)
-tc->hostport = g_strdup_printf ("%s:%d", str, port);
+tc->hostport = g_strdup_printf ("[%s]:%d", str, port);
   if (inet)
 g_object_unref (inet);
   g_free (str);

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

Bug#960856: binnmus for perl mini-transition

[Dominic Hargreaves]

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

Hi

Due to the upload of perl 5.20.2, we need a small number of binNMUs, as
below:

wb nmu libpar-packer-perl libdevel-cover-perl libclass-xsaccessor-perl 
libcommon-sense-perl . ANY . -m "Rebuild against perlapi-5.30.2." 
--extra-depends 'perl-base (>= 5.30.2)'

Thanks!
Dominic

Bug#934135: Bug#934135: aptitude: depends on libparse-debianchangelog-perl that has no upstream maintainer

[Axel Beckert]

Control: clone -1 -2 aptitude FTBFS with new po4a
Control: reassign -2 src:aptitude 0.8.12-3
Control: severity -2 serious
Control: tag -2 = ftbfs

Hi,

one more thing:

intrigeri wrote:
> I have applied Guillem's patch and fixed the typo mentioned below, on
> top of current sid's 0.8.12-3

You also need to remove the hunk which modifies debian/control. Doing
that from debian/patches is bad.

> (after disabling the build of doc translations as this makes the
> package FTBFS for me with current po4a; same on the Reproducible
> Builds infra¹),

Worked for me last weekend. But indeed, it FTBFS now. Hence
documenting it. Will fix that, too.

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

___
Aptitude-devel mailing list
aptitude-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/aptitude-devel

Bug#960861: barnowl: unnecessarily build-depends on the deprecated Any::Moose

[intrigeri]

Package: barnowl
Version: 1.10-1
Severity: normal
User: debian-p...@lists.debian.org
Usertags: any-moose

Hi Sam,

the Any::Moose Perl module has been deprecated since more than 5 years.
For more details, see http://shadow.cat/blog/matt-s-trout/moo-versus-any-moose/

I see that barnowl build-depends on libany-moose-perl. In the source tree I see
that the code under perl/modules/Facebook/lib/Facebook indeed uses Any::Moose.
But that code is not installed by the binary package.
And indeed, the good news is that src:barnowl appears to build just fine without
libany-moose-perl.

So I propose the following course of action:

1. Remove the unnecessary build dependency on libany-moose-perl

   That would be enough to close this bug and make my cleanup work,
   as a member of the Debian Perl group, easier :)

2. Let upstream know about the deprecated dependency.

   Switching from Any::Moose to Moose should be a simple string search &
   replace.

   Another option would be to migrate to Moo, but that's probably a bit more
   involved; the main benefit would be faster startup of the app, which
   I suppose does not matter much for an app that's primarily meant to run for
   a long while, e.g. in GNU Screen or similar.

Bug#945824: [python3-numpy] Depends on python3.8 and python3.7

[Ralf Jung]

Dear numpy maintainers,

python3-numpy is the only reason python3.7 is installed on my system at all.  In
fact, right now it is not installed, but doing "apt full-upgrade" will pull in
the outdated python3.7 even though I already have python3.8 installed. (I will
explore if I can uninstall numpy to avoid this problem, but I suspect it is
installed for a reason.)

Clearly, that is rather silly, so I would much appreciate if the maintainers
could fix that. :)

Kind regards,
Ralf

Bug#945467: Fix available (fwd)

[PICCA Frederic-Emmanuel]

you can look also at the CI, now that it works :)


https://salsa.debian.org/science-team/veusz/pipelines/137494

Cheers

Frederic

Bug#858037: ikarus FTBFS on i386: recipe for target 'ikarus.boot' failed (Segmentation fault)

[Adrian Bunk]

On Sat, Apr 22, 2017 at 08:35:01PM +0100, Barak A. Pearlmutter wrote:
> Well, vicare is a sort-of fork/continuation of ikarus.
> If that compiles on i386, we could transition.
> Or, since this problem is i386-only, and I'd imagine most users are
> amd64, could just stop supporting i386.

The Ubuntu patch (linked from tracker.debian.org) disables PIE on i386,
which fixes the build.

cu
Adrian

Bug#950585: binutils-dev: included log files introduce reproducibility issues

[Matthias Klose]

On 5/17/20 12:58 AM, Chris Lamb wrote:
> Hi Paul,
> 
>> There is already the BYHAND (and automatic BYHAND) mechanisms for files
>> that get installed outside of pool/ in the Debian apt repository. Each
>> one needs support from dak too though.
> [..]
>> It strikes me that these files are most similar to .buildinfo or the
>> build logs in that they are data *about* the builds. I've wanted
>> maintainers to be able to also upload build logs with their binary
>> builds and started a WIP patch for that.

I thought I also had filed a bug report for Debian, but there's only one in LP,
describing build artifacts for both successful and failing builds. See
https://bugs.launchpad.net/launchpad/+bug/1845159

Any idea which package this should be filed for?

Matthias

Bug#845808: libtest-cukes-perl: uses deprecated Any::Moose

[intrigeri]

Control: forwarded -1 https://rt.cpan.org/Ticket/Display.html?id=132646

Hi,

given:

 - This is leaf package
 - No upstream release since more than 8 years
 - popcon is very low
 - In my experience, Test::BDD::Cucumber is much more complete,
   and it's actively developed

I propose we remove this package from the archive if there's no answer
from upstream within 3 months.

Bug#903393: [initramfs-tools] update-initramfs -u warns: Unknown X keysym "dead_belowmacron"

[bakhelit]

Dear Maintainer,

On Debian 9 (with console-setup 1.164) running "sudo update-initramfs 
-u" produces:

update-initramfs: Generating /boot/initrd.img-4.9.0-12-amd64
WARNING: Unknown X keysym "dead_belowbreve"
WARNING: Unknown X keysym "dead_belowbreve"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowring"
WARNING: Unknown X keysym "dead_belowring"
WARNING: Unknown X keysym "dead_belowcircumflex"
WARNING: Unknown X keysym "dead_belowcircumflex"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_greek"
WARNING: Unknown X keysym "dead_belowdiaeresis"
WARNING: Unknown X keysym "dead_belowdiaeresis"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"
WARNING: Unknown X keysym "dead_belowtilde"

On Debian 10 (with console-setup 1.193~deb10u1) running "sudo 
update-initramfs -u" produces:

update-initramfs: Generating /boot/initrd.img-4.19.0-9-amd64

This is with my custom XKB keyboard layout where I included the quite a 
few "dead_*" X keysyms.


The problem is indeed caused by the Perl script "/usr/bin/ckbcomp" because:

- The script does not support all X keysyms.

- Despite not supporting all X keysyms the supported X keysyms are used 
as if the remaining unknown X keysyms are potentially invaild X keysyms.


- On Debian 9 the "/usr/share/initramfs-tools/hooks/keymap" script calls 
"/bin/setupcon" via "setupcon --save-keyboard ..." which causes it to 
call "/usr/bin/ckbcomp".


- On Debian 10 the "/usr/share/initramfs-tools/hooks/keymap" script 
calls "/bin/setupcon" via "setupcon --setup-dir ..." which causes it to 
not call "/usr/bin/ckbcomp".


Perhaps the Perl script "/usr/bin/ckbcomp" should be updated to support 
all X keysyms or the current supported X keysyms should be used as just 
an incomplete whitelist, where the remaining unknown X keysyms are also 
potentially vaild keysyms. In other words an info or warning about 
unsupported X keysym could be printed only in verbose or debug mode or 
not at all.


Regards,
Bakhelit

Bug#952710: firmware-amd-graphics: AMD Navi GPU doesn't work

[Matthew Toseland]

Package: firmware-amd-graphics
Version: 20190717-2
Followup-For: Bug #952710

Dear Maintainer,

I can confirm that this is still broken. Without navi10_gpu_info.bin, on an RX 
5700 XT,
the modesetting driver does not load, so text mode does not work. Once booted 
up, virtual
terminals are unavailable and the graphics is not hardware accelerated. If the 
disks are 
encrypted, then booting up is hard because the prompt is not shown. Recovery 
mode is 
impossible without setting nomodeset in grub.

Copying navi10_* from linux-firmware git to /lib/firmware/amdgpu fixes the 
problem.

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

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

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


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

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

firmware-amd-graphics depends on no packages.

firmware-amd-graphics recommends no packages.

Versions of packages firmware-amd-graphics suggests:
ii  initramfs-tools  0.137

-- no debconf information

Bug#960837: opendht: Need -latomic on at least RISC-V architecture

[Petter Reinholdtsen]

Package: opendht
Version: 2.1.1-1
Severity: wishlist

I had a look at the build failure on RISC-V, as reported by the
autobuilders[1], and the problem seem to be that -latomic is not used
during linking.

 [1] https://buildd.debian.org/status/package.php?p=opendht >

A similar problem is reported against aktualizr on github[2], which in
turn link to a riscv-gnu-toolchain issue[3] suggesting that every use of
'include ' should be accompanied by -latomic to the linker.

  [2] https://github.com/advancedtelematic/aktualizr/issues/1427
  [3] https://github.com/riscv/riscv-gnu-toolchain/issues/183#issuecomment-253721765 >

Setting severity to wishlist as the RISC-V architecture is not a release
architecture.

A similar problem exist with restinio[4], for a different set of atomic
operations, and for this issue I found a cmake recipe/patch[5] that
might be useful to look at when trying to fix opendht too.

 [4] https://buildd.debian.org/status/package.php?p=restinio=sid >
 [5] https://github.com/kimwalisch/primesieve/pull/46 >.

-- 
Happy hacking
Petter Reinholdtsen

Bug#960844: RFS: libhx/3.25-1~exp1 -- C library providing queue, tree, I/O and utility functions

[Jörg Frings-Fürst]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libhx"

   Package name: libhx
   Version : 3.25-1~exp1
   Upstream Author : Jan Engelhardt 
   URL : https://inai.de/projects/libhx/
   License : LGPL-2.1+
   Vcs : https://jff.email/cgit/libhx.git
   Section : libs

It builds those binary packages:

  libhx32 - C library providing queue, tree, I/O and utility functions
  libhx-dev - Development files for libhx
  libhx-doc - Documentation files for libhx

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/libh/libhx/libhx_3.25-1~exp1.dsc

or from git 

  https://jff.email/cgit/libhx.git/?h=release%2Fexperimental%2F3.25-1_exp1

Changes since the last upload:

   * New upstream release.
   * Migrate to debhelper 13:
 - Bump minimum debhelper-compat version in debian/control to = 13.
   * Declare compliance with Debian Policy 4.5.0 (No changes needed).
   * Bump package name depending on the SONAME to libhx32.
   * debian/copyright:
 - Refresh years.
 - Add Upstream-Contact.
 - Replace Homepage.
   * debian/control:
 - Change homepage.
 - Add Replaces / Breaks.
 - Add Rules-Requires-Root: no.


CU
Jörg Frings-Fürst

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:  https://jff.email/cgit/

Threema:  SYR8SJXB
Wire: @joergfringsfuerst
Skype:joergpenguin
Ring: jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.



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

Bug#960847: RFP: cpplint -- static code checker for C++

[Bálint Réczey]

Package: wnpp
Severity: wishlist

* Package name: cpplint
  Version : 14.5
  Upstream Author : Google Inc. et al.
* URL : https://github.com/cpplint/cpplint
* License : BSD 3 clause
  Programming Lang: Python
  Description : static code checker for C++

Cpplint is a command-line tool to check C/C++ files for style issues
following Google’s C++ style guide. Cpplint is developed and
maintained by Google Inc. at google/styleguide, also see the wikipedia
entry

While Google maintains cpplint, Google is not (very) responsive to
issues and pull requests, this fork aims to be (somewhat) more open to
add fixes to cpplint to enable fixes, when those fixes make cpplint
usable in wider contexts.

Thanks in advance,
Balint

Bug#960839: util-linux: Outdated references to kernel documentation

[Chris Hofstaedtler]

Control: tags -1 - patch
Control: tags -1 + upstream

* наб  [200517 14:57]:
> The patch applies cleanly on top of 2.35.1-5 and current upstream HEAD
> (366e163961add54f4822541f3d660b4e0578b207);
> I cannot signoff on the patch for personal reasons,
> but I'm licensing it as public domain and can certify (a), so,
> if my reading of the DCO is right, you could certify either (b) or (c),
> should you wish to bring the patch upstream;
> thank you for understanding.

In this case I can do nothing with y our patch, because "public
domain" is not a concept the jurisdiction I live in has. You'll have
to do the upstreaming yourself or find someone else.

Untagging "patch" for the reason stated above.

Thanks for your understanding,
Chris

Bug#960848: The GVFS dialog "Enter a passphrase to unlock the volume" shows radio buttons when there is no keyring

[bakhelit]

Package: gvfs
Version: 1.38.1-5

Dear Maintainers,

the GVFS dialog "Enter a passphrase to unlock the volume" shows radio 
buttons with passphrase saving options even when there is no keyring 
running or installed.


Obviously this is just a non-critical wishlist type bug report, but I 
think it would be less confusing for the user if the radio buttons are 
displayed only if there is an available keyring that can actually save 
the passphrase. Otherwise the default action should be "Forget password 
immediately" without showing the radio buttons. Also perhaps the dialog 
should use just the word "passphrase" or "password" but not both.


Regards,
Bakhelit

Bug#960702: ethtool -m values change when output is redirected

[Yannis Aribaud]

16 mai 2020 01:29 "Ben Hutchings"  a écrit:

> Control: tag -1 moreinfo
> 
> [...]
>
>> I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP
>> Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10
> 
> And which network driver are you using?

root@localhost:~# ethtool -i enp10s0
driver: mlx4_en
version: 4.0-0
firmware-version: 2.42.5000
expansion-rom-version: 
bus-info: :0a:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes

root@localhost:~# modinfo mlx4_en 
filename:   
/lib/modules/4.19.0-9-amd64/kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko
version:4.0-0
license:Dual BSD/GPL
description:Mellanox ConnectX HCA Ethernet driver
author: Liran Liss, Yevgeny Petrilin
srcversion: 5E7CBA2E401F495296DC544
depends:mlx4_core,devlink
retpoline:  Y
intree: Y
name:   mlx4_en
vermagic:   4.19.0-9-amd64 SMP mod_unload modversions 
sig_id: PKCS#7
signer: Debian Secure Boot CA
sig_key:A7:46:8D:EF
sig_hashalgo:   sha256
signature:  27:8D:17:13:F5:5B:EA:8E:DC:88:30:FD:2C:89:50:64:E8:2A:C6:7A:
25:F5:67:A9:DB:82:CD:5E:46:0E:F6:2A:2F:3F:EF:6B:BE:EF:49:AA:
27:1D:4D:95:28:AA:6C:88:5A:B1:C7:75:5F:C2:78:71:7F:1B:FC:CC:
E0:F4:33:DE:9E:51:99:C2:FE:D1:2A:9B:EF:17:63:5C:1E:29:9A:4F:
00:56:6F:3E:ED:C5:4A:72:63:8A:4C:EE:33:FD:FE:7C:73:2B:D0:0D:
80:80:A0:91:36:0D:7E:B0:C2:AC:2D:5C:A3:55:BF:03:94:52:64:30:
DF:14:BC:FB:AF:3B:60:D3:4C:02:78:4D:51:61:D8:F2:E4:02:9C:D5:
A4:05:81:D9:47:92:5A:C2:0D:D5:00:71:37:85:9B:F4:E5:54:3F:22:
CD:4C:67:12:63:15:C2:1D:87:C8:03:3C:4E:23:6C:A5:F3:C6:12:99:
0E:D1:40:AA:47:45:64:0F:AB:C2:E0:71:64:03:AD:4B:F2:0C:02:F3:
D3:D5:E4:4C:26:63:14:93:46:5F:31:3B:4C:9B:4B:5D:CD:30:C0:DF:
28:8A:4D:9A:0E:A8:5A:87:F4:7F:DD:F6:0E:A3:3A:B2:99:C0:75:F9:
00:13:B0:44:06:D1:1C:FE:34:A1:77:36:2A:15:29:F7
parm:   udp_rss:Enable RSS for incoming UDP traffic or disabled (0) 
(uint)
parm:   pfctx:Priority based Flow Control policy on TX[7:0]. Per 
priority bit mask (uint)
parm:   pfcrx:Priority based Flow Control policy on RX[7:0]. Per 
priority bit mask (uint)
parm:   inline_thold:Threshold for using inline data (range: 17-104, 
default: 104) (uint)

Latest firmware available on Mellanox website for this NIC and default kernel 
driver.

Regards,

-- 
Yannis Aribaud

Bug#844452: ITA: json-c -- JSON manipulation library

[Boyuan Yang]

Control: retitle -1 O: json-c -- JSON manipulation library
X-Debbugs-CC: camerontnor...@gmail.com

Hi Cameron,

Thanks for offering to adopt the package json-c in Debian. However, you
submitted the ITA request back in Feb 2019 and it has been more than
one year without activity.

Due to inactivity, I am converting your ITA request back to the
orphaning status.
If you are to work on json-c package soon, please let me know ASAP.
Otherwise it would be better to provide chance to others on fixing this package.

Let me know if you have any questions.

-- 
Regards,
Boyuan Yang

Bug#960860: pcsx2: 1.7.0 released

[Beta Version]

Package: pcsx2
Version: 1.5.0~gfc1d9aef0+dfsg-2
Severity: wishlist

Dear Maintainer, please, update PCSX2 to 1.7.0.



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

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

Versions of packages pcsx2 depends on:
ii  libaio1   0.3.112-8
ii  libasound21.2.2-2.1
ii  libc6 2.30-8
ii  libfreetype6  2.10.1-2
ii  libgcc-s1 10.1.0-1
ii  libgdk-pixbuf2.0-02.40.0+dfsg-4
ii  libgl11.3.1-1
ii  libgl1-mesa-dri   20.0.6-1
ii  libglib2.0-0  2.64.2-1
ii  libgtk-3-03.24.20-1
ii  liblzma5  5.2.4-1+b1
ii  libpng16-16   1.6.37-2
ii  libportaudio2 19.6.0-1
ii  libsdl2-2.0-0 2.0.10+dfsg1-3
ii  libsoundtouch12.1.2+ds1-1
ii  libstdc++610.1.0-1
ii  libudev1  245.5-2
ii  libwxbase3.0-0v5  3.0.5.1+dfsg-1
ii  libwxgtk3.0-gtk3-0v5  3.0.5.1+dfsg-1
ii  libx11-6  2:1.6.9-2+b1
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages pcsx2 recommends:
ii  libasound2-plugins  1.2.2-1
ii  libc6 [libc6-i686]  2.30-8

pcsx2 suggests no packages.

-- no debconf information

Bug#960832: lintian-brush: please exclude dch tests in Ubuntu

[Gianfranco Costamagna]

Source: lintian-brush
Version: 0.64
Severity: normal

Hello, looks like in Ubuntu dch -i is different w.r.t. Debian, so the package 
FTBFS there.
https://launchpadlibrarian.net/480139410/buildlog_ubuntu-groovy-amd64.lintian-brush_0.64_BUILDING.txt.gz

fixer test: simple for binary-control-field-duplicates-source ... ok

==
FAIL: test_add_new (lintian_brush.tests.test_run.ChangelogAddEntryTests)
lintian_brush.tests.test_run.ChangelogAddEntryTests.test_add_new
--
testtools.testresult.real._StringException: log: {{{
1.156  creating repository in 
file:///tmp/testbzr-11xllwu6.tmp/lintian_brush.tests.test_run.ChangelogAddEntryTests.test_add_new/work/.bzr/.
1.157  creating branch  in 
file:///tmp/testbzr-11xllwu6.tmp/lintian_brush.tests.test_run.ChangelogAddEntryTests.test_add_new/work/
1.161  trying to create missing lock 
'/tmp/testbzr-11xllwu6.tmp/lintian_brush.tests.test_run.ChangelogAddEntryTests.test_add_new/work/.bzr/checkout/dirstate'
1.162  opening working tree 
'/tmp/testbzr-11xllwu6.tmp/lintian_brush.tests.test_run.ChangelogAddEntryTests.test_add_new/work'
}}}

Traceback (most recent call last):
  File "/<>/lintian_brush/tests/test_run.py", line 913, in 
test_add_new
self.assertEqual([
  File "/usr/lib/python3/dist-packages/breezy/tests/__init__.py", line 1315, in 
assertEqual
raise AssertionError("%snot equal:\na = %s\nb = %s\n"
AssertionError: not equal:
a = ['lintian-brush (0.36) UNRELEASED; urgency=medium', '', '  * Add a foo', '']
b = ['lintian-brush (0.35ubuntu1) UNRELEASED; urgency=medium',
 '',
 '  * Add a foo',
 '']


--
Ran 574 tests in 37.609s

FAILED (failures=1, expected failures=1)


The Ubuntu patch currently is now to ignore that test in Ubuntu
http://launchpadlibrarian.net/480139452/lintian-brush_0.64_0.64ubuntu1.diff.gz

Can you please have a look and fix the package so it works on both Debian and 
Ubuntu?

thanks

Gianfranco

Bug#960834: RFS: fqterm/0.9.9-3 -- BBS client written in Qt

[atzlinux 肖盛文]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "fqterm"

* Package name : fqterm
Version : 0.9.9-3
Upstream Author : Iru Cai 
* URL : https://github.com/mytbk/fqterm
* License : GPL-2+ with OpenSSL exception
* Vcs : https://salsa.debian.org/chinese-team/fqterm
Section : x11

It builds those binary packages:

fqterm - BBS client written in Qt

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/f/fqterm/fqterm_0.9.9-3.dsc

Changes since the last upload:

[ 肖盛文 ]
* d/control:
- Bump debhelper-compat (= 13)
- Bump Standards-Version: 4.5.0
- add Rules-Requires-Root: no
- add New Uploaders: xiao sheng wen 
* d/rules:
- delete export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed
- delete dh_missing --fail-missing
- use execute_after_dh_installchangelogs target
* d/watch:
- use @ANY_VERSION@@ARCHIVE_EXT@
* d/copyright:
- add Upstream-Contact: Iru Cai 
* delete *.patch line in .gitignore file
* add fix-spelling-error-fqterm_decode.cpp.patch
* convert text from gb2312 character encoding to UTF-8 on
usr/share/FQTerm/skin/dpstyle/ReadMe.txt
* add lintian-overrides
* add upstream/metadata

Regards,

-- 
肖盛文 Faris Xiao
微信：atzlinux
ＱＱ：909868357
铜豌豆 Linux 
基于 Debian 的 Linux 中文桌面操作系统：https://www.atzlinux.com




signature.asc
Description: OpenPGP digital signature

Bug#960839: util-linux: Outdated references to kernel documentation

[наб]

Source: util-linux
Version: 2.35.1-5
Severity: minor
Tags: patch

Dear Maintainer,

I noticed that fdisk(8) references a file that is no longer there,
so I went through all references to the kernel Documentation/ tree in
util-linux and fixed them for the latest git release (v5.7-rc5).

The one ref I wasn't 100% sure about is fdisk(8)'s
Documentation/admin-guide/devices.txt, which has a ReST version as well,
though it seems less useful.

The patch applies cleanly on top of 2.35.1-5 and current upstream HEAD
(366e163961add54f4822541f3d660b4e0578b207);
I cannot signoff on the patch for personal reasons,
but I'm licensing it as public domain and can certify (a), so,
if my reading of the DCO is right, you could certify either (b) or (c),
should you wish to bring the patch upstream;
thank you for understanding.

Best,
наб

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

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

-- no debconf information
From f40fcda769cf7e19f222041800f62dd0e81310d5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=BD=D0=B0=D0=B1?= 
Date: Sun, 17 May 2020 13:36:41 +0200
Subject: [PATCH] Fix dead references to kernel documentation

Based on v5.7-rc5, most date back to reorganisation of the
Documentation/ tree in 2016:

fdisk.8:   Documentation/{,admin-guide/}devices.txt
eject.c:   Documentation/{,userspace-api/}ioctl/cdrom.rst
mount.8:   Documentation/filesystems/adfs.{txt,rst}
rfkill.8:  Documentation/{rfkill.txt,driver-api/rfkill.rst}
tunelp.8:  Documentation/{parport.txt,admin-guide/parport.rst}
zramctl.8: Documentation/{blockdev/zram.txt,admin-guide/blockdev/zram.rst}
---
 disk-utils/fdisk.8  | 2 +-
 sys-utils/eject.c   | 2 +-
 sys-utils/mount.8   | 2 +-
 sys-utils/rfkill.8  | 2 +-
 sys-utils/tunelp.8  | 2 +-
 sys-utils/zramctl.8 | 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/disk-utils/fdisk.8 b/disk-utils/fdisk.8
index cc172a0a5..dcc587fed 100644
--- a/disk-utils/fdisk.8
+++ b/disk-utils/fdisk.8
@@ -161,7 +161,7 @@ The
 .I partition
 is a device name followed by a partition number.  For example, /dev/sda1 is the
 first partition on the first hard disk in the system.  See also Linux kernel
-documentation (the Documentation/devices.txt file).
+documentation (the Documentation/admin-guide/devices.txt file).
 
 .SH SIZES
 The "last sector" dialog accepts partition size specified by number of sectors
diff --git a/sys-utils/eject.c b/sys-utils/eject.c
index 2f3b200bf..651ecc7d8 100644
--- a/sys-utils/eject.c
+++ b/sys-utils/eject.c
@@ -330,7 +330,7 @@ static void auto_eject(const struct eject_control *ctl)
  * Stops CDROM from opening on manual eject button press.
  * This can be useful when you carry your laptop
  * in your bag while it's on and no CD inserted in it's drive.
- * Implemented as found in Documentation/ioctl/cdrom.txt
+ * Implemented as found in Documentation/userspace-api/ioctl/cdrom.rst
  */
 static void manual_eject(const struct eject_control *ctl)
 {
diff --git a/sys-utils/mount.8 b/sys-utils/mount.8
index 13a5f7167..7f5da2d2b 100644
--- a/sys-utils/mount.8
+++ b/sys-utils/mount.8
@@ -1342,7 +1342,7 @@ Set the owner and group of the files in the filesystem (default: uid=gid=0).
 Set the permission mask for ADFS 'owner' permissions and 'other' permissions,
 respectively (default: 0700 and 0077, respectively).
 See also
-.IR /usr/src/linux/Documentation/filesystems/adfs.txt .
+.IR /usr/src/linux/Documentation/filesystems/adfs.rst .
 
 .SS "Mount options for affs"
 .TP
diff --git a/sys-utils/rfkill.8 b/sys-utils/rfkill.8
index 9eff913b8..eb640954f 100644
--- a/sys-utils/rfkill.8
+++ b/sys-utils/rfkill.8
@@ -110,7 +110,7 @@ for the Debian project (and may be used by others).
 .SH "SEE ALSO"
 .BR powertop (8),
 .BR systemd-rfkill (8),
-.UR https://\:git.\:kernel.\:org/\:pub/\:scm/\:linux/\:kernel/\:git/\:torvalds/\:linux.git/\:tree/\:Documentation/\:rfkill.txt
+.UR https://\:git.\:kernel.\:org/\:pub/\:scm/\:linux/\:kernel/\:git/\:torvalds/\:linux.git/\:tree/\:Documentation/\:driver-api/\:rfkill.rst
 Linux kernel documentation
 .UE
 .SH AVAILABILITY
diff --git a/sys-utils/tunelp.8 b/sys-utils/tunelp.8
index 5c927458f..7716ba7e1 100644
--- a/sys-utils/tunelp.8
+++ b/sys-utils/tunelp.8
@@ -34,7 +34,7 @@ irq is handled by the parport driver.  You can change the parport irq for
 example via
 .IR /proc/parport/*/irq .
 Read
-.I /usr/src/linux/Documentation/parport.txt
+.I /usr/src/linux/Documentation/admin-guide/parport.rst
 for more details on parport.
 .TP
 \fB\-t\fR, \fB\-\-time\fR \fImilliseconds\fR
diff --git 

Bug#950585: binutils-dev: included log files introduce reproducibility issues

[Paul Wise]

On Sun, 2020-05-17 at 13:12 +0200, Matthias Klose wrote: 

> Any idea which package this should be filed for?

I think this is going to require a bunch of different changes in
various places including dpkg-dev, debhelper, reprepro, dak, launchpad
and any other apt repos that have an incoming system. As long as the
files are mentioned in the .changes files dupload/dput won't change. So
probably there needs to be a discussion on debian-devel CCed to the
debian-dpkg list and to the ftp-masters and other folks.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#233864: marked as done ([powerpc] document need for BootX on oldworld)

[John Paul Adrian Glaubitz]

On 5/17/20 2:15 PM, Debian Bug Tracking System wrote:
> Initial boot: doesn't work on oldworld PPC. BootX works. Yeah, it's a known 
> problem. What about providing BootX in the cdrom and adding this hint to 
> debian-installer documentation?

That's actually a good point. I can look adding OldWorld support in the
future provided that booting on OldWorld machines currently works.

I remember there being issues, in particular with PowerBook 34xx machines.

BootX might also help with the NewWorld machines that have early OpenFirmware
implementations that are not properly supported by GRUB.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#960842: add -go wrappers and golang-go-for-host

[Helmut Grohne]

Source: golang-defaults
Version: 2:1.14~1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:canid src:go-qrcode src:golang-bindata 
src:golang-github-benbjohnson-tmpl src:golang-github-calmh-xdr 
src:golang-github-eknkc-amber src:golang-github-odeke-em-cli-spinner 
src:golang-github-odeke-em-ripper src:golang-github-rakyll-statik 
src:golang-gogoprotobuf

On Fri, May 15, 2020 at 06:51:18AM +0200, Helmut Grohne wrote:
> On Fri, May 15, 2020 at 08:34:48AM +1200, Michael Hudson-Doyle wrote:
> > (The gccgo-go / golang-go split is another dimension to this, I guess to
> > cross build with gccgo you need something like option 5)
> 
> That's an interesting wrinkle that I completely overlooked. Thank you!

Given this, I went ahead and implemented a part of this that seems
relatively obvious and uncontroversial to me.

In my draft, I argued that for supporting cross compilation with
golang-any, one must ensure that the triplet-prefixed go is called in
order to support gccgo. But then, the golang go will also have to
provide a triplet-prefixed go to provide a shared interface.

For that reason, I'm attaching a patch that adds these go wrappers to
golang-defaults. It adds new binary packages golang-go- and a
package golang-go-for-host.

A few remarks about the patch:
 * It adds new binary packages. Uploading golang-defaults with the patch
   will make it stuck in NEW.
 * debian/control becomes a generated file. The generator is
   debian/control.sh.
 * It fixes a typo in debian/control where one "mips64el" was misspelled
   as "mips64".

This is not a full solution to cross compiling go packages. Like my
previous patches, it is to be considered an incremental step.

Once this is in place, I suggest that we can reduce complexity in
dh-golang. Instead of setting up the magic variables there, we can now
call into the cross wrapper.

Helmut
diff --minimal -Nru golang-defaults-1.14~1/debian/changelog 
golang-defaults-1.14~1.1/debian/changelog
--- golang-defaults-1.14~1/debian/changelog 2020-03-07 13:47:33.0 
+0100
+++ golang-defaults-1.14~1.1/debian/changelog   2020-05-17 14:16:54.0 
+0200
@@ -1,3 +1,10 @@
+golang-defaults (2:1.14~1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Introduce golang-go-for-host package. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 17 May 2020 14:16:54 +0200
+
 golang-defaults (2:1.14~1) unstable; urgency=medium
 
   * Update to Go 1.14 (src:golang-1.14). Closes: #952831
diff --minimal -Nru golang-defaults-1.14~1/debian/control 
golang-defaults-1.14~1.1/debian/control
--- golang-defaults-1.14~1/debian/control   2020-03-07 13:45:40.0 
+0100
+++ golang-defaults-1.14~1.1/debian/control 2020-05-17 14:16:54.0 
+0200
@@ -70,6 +70,233 @@
  native toolchain ("gc compiler"). Packages that want to build with whichever
  of gc or gccgo is available should depend on golang-any.
 
+Package: golang-go-x86-64-linux-gnu
+Architecture: all
+Multi-Arch: foreign
+Depends: golang-go (>= ${source:Version})
+Description: Go programming language compiler wrapper for amd64
+ The Go programming language is an open source project to make programmers more
+ productive. Go is expressive, concise, clean, and efficient. Its concurrency
+ mechanisms make it easy to write programs that get the most out of multicore
+ and networked machines, while its novel type system enables flexible and
+ modular program construction. Go compiles quickly to machine code yet has the
+ convenience of garbage collection and the power of run-time reflection. It's a
+ fast, statically typed, compiled language that feels like a dynamically typed,
+ interpreted language.
+ .
+ This is a wrapper package that contains the x86_64-linux-gnu-go
+ wrapper used for compiling go programs to amd64.
+ When depending on this wrapper package, go must be called through the wrapper
+ only.
+
+Package: golang-go-aarch64-linux-gnu
+Architecture: all
+Multi-Arch: foreign
+Depends: golang-go (>= ${source:Version})
+Description: Go programming language compiler wrapper for arm64
+ The Go programming language is an open source project to make programmers more
+ productive. Go is expressive, concise, clean, and efficient. Its concurrency
+ mechanisms make it easy to write programs that get the most out of multicore
+ and networked machines, while its novel type system enables flexible and
+ modular program construction. Go compiles quickly to machine code yet has the
+ convenience of garbage collection and the power of run-time reflection. It's a
+ fast, statically typed, compiled language that feels like a dynamically typed,
+ interpreted language.
+ .
+ This is a wrapper package that contains the aarch64-linux-gnu-go
+ wrapper used for compiling go programs to arm64.
+ When depending on this wrapper package, go must be called through the wrapper
+ only.
+
+Package: golang-go-arm-linux-gnueabi
+Architecture: all
+Multi-Arch: foreign
+Depends: golang-go (>= 

Bug#960841: libcleri FTCBFS: builds for the build architecture

[Helmut Grohne]

Source: libcleri
Version: 0.12.1-1
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

libcleri fails to cross build from source, because it uses the build
architecture compiler. debian/rules does not pass cross tools to make
and the makefile does not honour cross tools passed via the environment.
Please consider applying the attached patch to fix both.

Helmut
diff --minimal -Nru libcleri-0.12.1/debian/changelog 
libcleri-0.12.1/debian/changelog
--- libcleri-0.12.1/debian/changelog2020-05-16 21:42:47.0 +0200
+++ libcleri-0.12.1/debian/changelog2020-05-17 12:14:38.0 +0200
@@ -1,3 +1,12 @@
+libcleri (0.12.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ cross.patch: Make gcc substitutable.
+
+ -- Helmut Grohne   Sun, 17 May 2020 12:14:38 +0200
+
 libcleri (0.12.1-1) unstable; urgency=medium
 
   * Add new symbols
diff --minimal -Nru libcleri-0.12.1/debian/patches/cross.patch 
libcleri-0.12.1/debian/patches/cross.patch
--- libcleri-0.12.1/debian/patches/cross.patch  1970-01-01 01:00:00.0 
+0100
+++ libcleri-0.12.1/debian/patches/cross.patch  2020-05-17 12:14:17.0 
+0200
@@ -0,0 +1,21 @@
+--- libcleri-0.12.1.orig/Release/makefile
 libcleri-0.12.1/Release/makefile
+@@ -33,7 +33,7 @@
+ libcleri: $(OBJS) $(USER_OBJS)
+   @echo 'Building target: $@'
+   @echo 'Invoking: Cross GCC Linker'
+-  gcc -shared -Wl,-$(SO_NAME),$(FN).$(MAJOR) -o $(FN) $(OBJS) 
$(USER_OBJS) $(LIBS) $(LDFLAGS)
++  $(CC) -shared -Wl,-$(SO_NAME),$(FN).$(MAJOR) -o $(FN) $(OBJS) 
$(USER_OBJS) $(LIBS) $(LDFLAGS)
+   @chmod -x $(FN)
+   @echo 'Finished building target: $@'
+   @echo ' '
+--- libcleri-0.12.1.orig/Release/src/subdir.mk
 libcleri-0.12.1/Release/src/subdir.mk
+@@ -77,6 +77,6 @@
+ src/%.o: ../src/%.c
+   @echo 'Building file: $<'
+   @echo 'Invoking: Cross GCC Compiler'
+-  gcc -DNDEBUG -I../inc -O3 -Winline -Wall $(CPPFLAGS) $(CFLAGS) -c 
-fmessage-length=0 -fPIC -MMD -MP -MF"$(@:%.o=%.d)" -MT"$(@)" -o "$@" "$<"
++  $(CC) -DNDEBUG -I../inc -O3 -Winline -Wall $(CPPFLAGS) $(CFLAGS) -c 
-fmessage-length=0 -fPIC -MMD -MP -MF"$(@:%.o=%.d)" -MT"$(@)" -o "$@" "$<"
+   @echo 'Finished building: $<'
+   @echo ' '
diff --minimal -Nru libcleri-0.12.1/debian/patches/series 
libcleri-0.12.1/debian/patches/series
--- libcleri-0.12.1/debian/patches/series   1970-01-01 01:00:00.0 
+0100
+++ libcleri-0.12.1/debian/patches/series   2020-05-17 12:14:01.0 
+0200
@@ -0,0 +1 @@
+cross.patch
diff --minimal -Nru libcleri-0.12.1/debian/rules libcleri-0.12.1/debian/rules
--- libcleri-0.12.1/debian/rules2020-05-16 21:42:47.0 +0200
+++ libcleri-0.12.1/debian/rules2020-05-17 12:14:37.0 +0200
@@ -12,7 +12,7 @@
dh $@
 
 override_dh_auto_build-arch:
-   $(MAKE) --directory=Release all
+   dh_auto_build --sourcedirectory=Release -- all
 
 override_dh_auto_clean:
$(MAKE) --directory=Release clean

Bug#960137: ITA: duck -- checks URLs in debian/control and debian/upstream files

[Baptiste BEAUPLAT]

Control: retitle 960137 ITA: duck -- checks URLs in debian/control and 
debian/upstream files
Control: owner 960137 !

I'm interested in maintaining the duck package and the associated
service at http://duck.debian.net.

I do not have the mean to host the service myself,
so it will need either a sponsored or a DSA VM
(as suggested by pabs).

Note that I'm not a DD (just a DM) so I will need a someone
to grant me right on both salsa projects.

Best,
-- 
Baptiste BEAUPLAT - lyknode




signature.asc
Description: OpenPGP digital signature

Bug#960843: clamav FTCBFS: fails running tests despite DEB_BUILD_OPTIONS=nocheck

[Helmut Grohne]

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

clamav regressed in the reported version in that it now runs tests
despite DEB_BUILD_OPTIONS=nocheck. In a cross build setting, this makes
the build fail. Please consider applying the attached patch to restore
nocheck support.

Helmut
diff --minimal -Nru clamav-0.102.3+dfsg/debian/changelog 
clamav-0.102.3+dfsg/debian/changelog
--- clamav-0.102.3+dfsg/debian/changelog2020-05-16 17:12:04.0 
+0200
+++ clamav-0.102.3+dfsg/debian/changelog2020-05-17 12:15:30.0 
+0200
@@ -1,3 +1,10 @@
+clamav (0.102.3+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Honour DEB_BUILD_OPTIONS=nocheck again. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 17 May 2020 12:15:30 +0200
+
 clamav (0.102.3+dfsg-1) unstable; urgency=medium
 
   * Import 0.102.3
diff --minimal -Nru clamav-0.102.3+dfsg/debian/rules 
clamav-0.102.3+dfsg/debian/rules
--- clamav-0.102.3+dfsg/debian/rules2020-05-16 15:01:00.0 +0200
+++ clamav-0.102.3+dfsg/debian/rules2020-05-17 12:15:28.0 +0200
@@ -136,11 +136,13 @@
dh_auto_build -a -- V=1
 
 override_dh_auto_test:
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 ifneq (,$(filter ia64 sparc, $(DEB_HOST_ARCH)))
T=900 $(MAKE) check EF_ALIGNMENT=8 V=1 VERBOSE=1
 else
T=900 $(MAKE) check V=1 VERBOSE=1
 endif
+endif
 
 override_dh_install:
dh_install

Bug#960815: fdisk: will be autoremoved on many systems now

[Chris Hofstaedtler]

Hi Thorsten,

* Thorsten Glaser  [200517 04:15]:
> I’ve noticed that fdisk will now be autoremoved on many systems
> because the dependencies on it are gone from everywhere else.

Indeed. I've had to remove Important: yes because of a weird
apt/piuparts interaction, but that would have been a stopgap at
best.


> While this is probably ok for new installations, existing systems
> might… find this not so much agreeable.
>
> I’d suggest running 'apt-mark manual fdisk' in the upgrade case
> in a maintainer script, but since the package database is locked
> during their execution I know this isn’t doable.
>
> Any better ideas?

I gave this some thought, and now I'm not sure autoremoving fdisk is
such a bad idea. It's suprising, and to my server-focused eyes
certainly disturbing. But so are many other packages that we no
longer install by default -- telnet being one of those I'll always
miss.

Also, over the past decade or so the recommended tool for
partitioning has changed a number of times; we went from fdisk to
parted to gdisk and maybe now that it again understands enough, to
fdisk. However, I suspect desktop users will never want to interact
with fdisk, but would use the GUI tool of the day to format their
USB keys.

If we'd had a fictional "task-server" task package (like we have
task-desktop today), I'd suggest it should depend on fdisk. But we
don't, and it appears, we don't need to have that. (It certainly
would not help me.)

fdisk will be one `apt install` away if it gets autoremoved; once
you need a partitioning tool you can pick one again, preferably
fdisk ;-)

TL;DR: I think it is okay to have fdisk autoremoved for almost
everyone.


Thanks for the report!
Chris

(I've bcc'ed the Grml team, giving them a heads up. Other Debian
based Linux Live systems should probably also check their dependency
lists.)

Bug#951877: Patch: OpenSSL linking without license exception

[Petter Reinholdtsen]

[Bastian Germann]
> This patch builds the package without OpenSSL.

Dropping https support will make the library unusable for at least some
of its current users.  I thus would recommend coming up with a different
approach, for example the idea about linking against wolfssl.
-- 
Happy hacking
Petter Reinholdtsen

Bug#931776: snapd: Installed snaps do not appear in desktop launcher in Debian buster.

[Vlad Orlov]

Hi,

So, snapd sets $PATH and $XDG_DATA_DIRS in /etc/profile.d/apps-bin-path.sh, but 
/etc/profile
and /etc/profile.d aren't used in the graphical logins in Debian. [1]

Older versions of snapd also had set $XDG_DATA_DIRS in 
/etc/X11/Xsession.d/65snappy, which
was used in the X sessions. But that was dropped upstream in [2], which 
happened some time
after Stretch was released, but before Buster was released.

I guess this is the cause of the problem...


[1] https://wiki.debian.org/EnvironmentVariables
[2] https://github.com/snapcore/snapd/pull/3398

Bug#960702: ethtool -m values change when output is redirected

[Ben Hutchings]

Control: tag -1 - moreinfo
Control: reassign -1 src:linux
Control: found -1 4.9.210-1
Control: found -1 4.19.118-2
Control: found -1 5.6.7-1
Control: tag -1 security

On Sun, 2020-05-17 at 14:41 +, Yannis Aribaud wrote:
> 16 mai 2020 01:29 "Ben Hutchings"  a écrit:
> 
> > Control: tag -1 moreinfo
> > 
> > [...]
> > 
> > > I am using Debian GNU/Linux 10 (buster), kernel 4.19.0-9-amd64 #1 SMP
> > > Debian 4.19.118-2 (2020-04-29) x86_64 GNU/Linux and libc6 2.28-10
> > 
> > And which network driver are you using?
> 
> root@localhost:~# ethtool -i enp10s0
> driver: mlx4_en
> version: 4.0-0
> firmware-version: 2.42.5000
> expansion-rom-version: 
> bus-info: :0a:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: no
> supports-register-dump: no
> supports-priv-flags: yes
> 
> root@localhost:~# modinfo mlx4_en 
> filename:   
> /lib/modules/4.19.0-9-amd64/kernel/drivers/net/ethernet/mellanox/mlx4/mlx4_en.ko
[...]

Right, this turns to have exactly the bug I suspected. :-/

Tagged security because this is leaking kernel memory.

Ben.

-- 
Ben Hutchings
Logic doesn't apply to the real world. - Marvin Minsky



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

Bug#955835: enchant-2: unnecessarily Build-Depends on deprecated dbus-glib

[Kentaro Hayashi]

Hi,

I've send MR to this bug
https://salsa.debian.org/gnome-team/enchant-2/-/merge_requests/2

Regards,

Bug#900739: crashing in toke.c, keyword plugin pointer is left pointing to an XS module that's been unloaded

[Dominic Hargreaves]

On Wed, Jun 06, 2018 at 01:22:26PM +1000, Dean Hamstead wrote:
> Rolling it in to the official release would be much appreciated as it
> will spare us maintaining our own patched version, plus might help a
> few lonely travelers who are stumped on a segfault.

I'm sorry that we weren't able to get to this in a timely
fashion. Given that this is now fixed in current stable (and
anyone affected must surely have worked around it by now), I
think it's unlikely that applying this fix now will be that
helpful (even if an oldstable update is going to happen at
this stage). Therefore, I'm inclined to close this bug now.
Let me know if you disagree.

Best
Dominic

Bug#960846: The "path-exclude" and "path-include" configurations are not taken into account on package removals

[bakhelit]

Package: dpkg
Version: 1.19.7

Dear Maintainers,

The "path-exclude" and "path-include" configurations in 
"/etc/dpkg/dpkg.cfg.d/00path-exclude-and-include" are not taken into 
account on package removals.


To reproduce you can for example:

- Install the package "xfwm4".

- Add "path-exclude /usr/share/themes/*" to 
"/etc/dpkg/dpkg.cfg.d/00path-exclude-and-include".


- Remove or reinstall the package "xfwm4".

- See that "xfwm4" themes in "/usr/share/themes/*" are gone.

This is obviously problematic when one wants to modify some files from a 
given package while preserving their names/paths. Then any update, 
reinstall or removal of the given package removes also the customized 
files even if those files are excluded using the "path-exclude" 
configurations in "/etc/dpkg/dpkg.cfg.d/00path-exclude-and-include".


Currently I need to use custom workaround scripts to periodically 
restore the such modifications and try to minimize such modifications, 
but still it would be nice if the current "path-exclude" and 
"path-include" mechanisms could be improved in this regard.


Regards,
Bakhelit

Bug#960841: libcleri FTCBFS: builds for the build architecture

[Paul Gevers]

Hi Jeroen,

On 17-05-2020 12:18, Helmut Grohne wrote:
> libcleri fails to cross build from source, because it uses the build
> architecture compiler. debian/rules does not pass cross tools to make
> and the makefile does not honour cross tools passed via the environment.
> Please consider applying the attached patch to fix both.

Can you please apply the Release/makefile and Release/src/subdir.mk part
upstream? This isn't Debian specific and I would like to avoid carrying
such a patch in the Debian part.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#960781: dh-missing don't check again compressed files

[Niels Thykier]

Control: tags -1 wontfix

On Sat, 16 May 2020 17:44:54 +0200
=?utf-8?q?J=C3=B6rg_Frings-F=C3=BCrst?=  wrote:
> Package: debhelper
> Version: 13
> Severity: important
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hello,
> 
> I get
> 
> dh_missing: warning: usr/share/doc/libhx/libHX_Documentation.pdf exists in
> debian/tmp but is not installed to anywhere
> 
> and
> 
> #ls -l debian/libhx-doc/usr/share/doc/libhx-doc/
> total 540
> [...]
> - -rw-r--r-- 1 pbuilder pbuilder 515595 May 14 09:48 
> libHX_Documentation.pdf.gz
> - -rw-r--r-- 1 pbuilder pbuilder903 May 14 09:48 ux-file.txt
> - -rw-r--r-- 1 pbuilder pbuilder753 May 14 09:48 ux-mmap.txt
> 
> 
> Please add a test for compressed files
> 
> CU
> Jörg
> 
> 
> [...]

Hi Jörg,

The problem lies elsewhere - namely that in libhx installs
"libHX_Documentation.pdf" from "./doc/libHX_Documentation.pdf" rather
than "debian/tmp/usr/share/doc/libhx/libHX_Documentation.pdf" (based on
debian/libhx-doc.docs).

In that sense, dh_missing is correct; nothing installed
"usr/share/doc/libhx/libHX_Documentation.pdf".

I recommend that you replace "doc/libHX_Documentation.pdf" with
"usr/share/doc/libhx/libHX_Documentation.pdf" in debian/libhx-doc.docs
if they are identical.

~Niels

Bug#845811: libwww-nicovideo-download-perl: uses deprecated Any::Moose

[intrigeri]

Hi,

also, note that we have nicovideo-dl in the archive: updated last year
upstream, Python 3, 6 times more votes in popcon.

This increases my confidence that removing
libwww-nicovideo-download-perl is OK.

Bug#958431: gkrellmd: CIDR match in allow_host not working for IPv6 connections

[Peter Denison]

Package: gkrellmd
Version: 2.3.10-2
Followup-For: Bug #958431

Further to this report, I've tracked down the issue to the fact that for 
the main client build, INET6 is defined in src/inet.h, but for the build 
of the server gkrellmd, this file is not included, and therefore INET6 
is not defined.

Bug#956712: emacs: https to plain http downgrade after unhandled GNUTLS_E_AGAIN error in TLS1.3 connection

[Simon Frei]

fixed 956712 1:26.3+1-2
thanks

I can confirm that as reported by Heenec, this is fixed in unstable 
given it's on 26.3 now.

Bug#960858: libmousex-types-perl: uses deprecated Any::Moose

[intrigeri]

Package: libmousex-types-perl
Version: 0.06-2
Severity: normal
User: debian-p...@lists.debian.org
Usertags: any-moose
Forwarded: https://github.com/yappo/p5-mousex-types/issues/5

Also on CPAN RT: https://rt.cpan.org/Ticket/Display.html?id=104943

I've just poked upstream on their GitHub.

Bug#959883: gnome-shell: randomly crashes: segfaults and restarts

[debian-edid]

Hi,

Same problem here:

        gnome-shell[1153]: segfault at 0 ip 7f989dac846a sp 
7ffc28aef5a0 error 4 in libst-1.0.so[7f989daa9000+4a000]


Still no gnome-shell 3.36.2 update even in sid



Regards,
Edi D

Bug#945824: [python3-numpy] Depends on python3.8 and python3.7

[Ralf Jung]

Oh, I see latest unstable version 1:1.18.4-1 fixes this.
Thanks a lot. :)

; Ralf

Bug#879061: file: add support for FIT image (linux kernel file: *.itb)

[Christoph Biedl]

Control: tags 879061 unreproducible moreinfo

Mathieu Malaterre wrote...

> It would be nice to have something a bit more descriptive for FIT image:
> 
> $ file arch/mips/boot/vmlinux.gz.itb
> arch/mips/boot/vmlinux.gz.itb: data

For lack of a reproducer I tried to find some according files and found
something in the u-boot-rockchip_2020.04+dfsg-2_arm64.deb - these
however have been recognized by file/libmagic for years.

Christoph


signature.asc
Description: PGP signature

Bug#845772: libconfig-jfdi-perl: uses deprecated Any::Moose

[intrigeri]

Control: forwarded -1 https://rt.cpan.org/Ticket/Display.html?id=120987

Hi,

given:

 - Very low popcon

 - Upstream never replied in 3 years on the corresponding bug report.

 - The only reverse-dependency is libmojomojo-perl, which is itself
   low popcon, no upstream release since 3 years, and has a PR open
   since 2 years to migrate it away from Config::JDFI for this exact
   same reason (https://github.com/mojomojo/mojomojo/pull/155),
   with no answer from upstream so far.

I propose we remove both libconfig-jfdi-perl and libmojomojo-perl
from the archive.

Bug#924290: [rfc] information about EFI partitions

[Holger Wansing]

Hi,

 wrote:
> Package: installation-guide
> Version: 20180930
> Severity: wishlist
> Tags: patch
> 
> Hi
> 
> recently I was learning about presseding UEFI installs and
> I think the install guide could use a small addition to make
> that journey easier. I also sent a patch to partman-auto-recipe.txt
> but I am sure the readership of that is much less than the d-i manual.

I am unable to proof the patch correct or not, could anyone comment on that?



>From 4697c54b3f61bc145980f52206bb20e2280c0a63 Mon Sep 17 00:00:00 2001
From: Vincent McIntyre 
Date: Mon, 11 Mar 2019 15:38:19 +1100
Subject: [RFC PATCH] Add some information about preseeding EFI partitions

---
 en/appendix/preseed.xml | 17 +
 1 file changed, 17 insertions(+)

diff --git a/en/appendix/preseed.xml b/en/appendix/preseed.xml
index c55860e34..9e334738a 100644
--- a/en/appendix/preseed.xml
+++ b/en/appendix/preseed.xml
@@ -1211,6 +1211,20 @@ d-i partman-auto/choose_recipe select atomic
 # system labels, volume group names and which physical devices to include
 # in a volume group.
 
+## Partitioning for EFI
+# If your system needs an EFI partition you could add something like
+# this to the recipe above, as the first element in the recipe:
+#   538 538 1075 free  \
+#  $iflabel{ gpt } \
+#  $reusemethod{ } \
+#  method{ efi }   \
+#  format{ }   \
+#   .  \
+#
+# The fragment above is for the amd64 architecture; the details may be
+# different on other architectures. The 'partman-auto' package in the
+# D-I source repository may have an example you can follow.
+
 # This makes partman automatically partition without confirmation, provided
 # that you told it what to do using one of the methods above.
 d-i partman-partitioning/confirm_write_new_label boolean true
@@ -1218,6 +1232,9 @@ d-i partman/choose_partition select finish
 d-i partman/confirm boolean true
 d-i partman/confirm_nooverwrite boolean true
 
+# Force UEFI booting ('BIOS compatibility' will be lost). Default: false.
+#d-i partman-efi/non_efi_system boolean true
+
 # When disk encryption is enabled, skip wiping the partitions beforehand.
 #d-i partman-auto-crypto/erase_disks boolean false
 
-- 
2.11.0



-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#960840: Please provide a buster-backports of lzf

[Picca Frédéric-Emmanuel]

Source: liblzf
Severity: normal


Hello, I would like at the end to backport the bitshuffle packahe which contain 
hdf5 plugins.
Since lzf will become a dependency of bitshuffle, It would be great to have 
this backports.

thanks for considering

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

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
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

Bug#515249: marked as done (installation-reports: Various issues on IBM Power5 (lvm, multipath, yaboot.conf))

[John Paul Adrian Glaubitz]

Hello Holger!

Closing the bug report in this case is okay, but the actual reason why
this can be closed is that I have switched the powerpc and ppc64 ports
over from Yaboot to GRUB meaning that Yaboot-specific installation issues
should no longer be relevant.

Thanks,
Adrian

On 5/17/20 2:15 PM, Debian Bug Tracking System wrote:
> Base System Installation Checklist:
> * Although the URL above is for the SID installer, when the
> install was complete, I noticed that LENNY had been installed.
> I noticed this by looking at the /etc/apt/sources.list file.
> 
> Other issues that I was not particularly happy with were:
> 
> 1.
> Selecting guided LVM allowed a the root filesystem to be
> placed in a logical volume (which I wanted), but then the
> yaboot.conf file was still writted to /etc/yaboot.conf.
> I had to manually rescue the system after the install and
> move /etc/yaboot.conf to /boot/etc/yaboot.conf. In my view
> LVM is going to be the way forward and this configuration
> file should not been located on the root filesystem. I
> hope everyone is aware of this issue and has looked at
> keeping files required to boot the system in /boot
> 
> 2.
> After fixing the location of the yaboot.conf file, the
> system refused to boot. It was trying to boot the label
> "old" which was invalid because the kernel has not yet
> been upgraded. I therefore had to add the following to
> the yaboot.conf before the correct default entry would
> boot:
> 
> defaultos=Linux
> 
> 
> 3.
> I also had issues with multipath root and LVM:
> 
> 3.1
> I had to add multipath to the lvm2 PREREQ's in order
> for multipath to be started before LVM.
> 
> 3.2
> Debian installer was called with:
> 
> disk-detect/multipath/enable=true
> 
> However, once the install had completed, the lvm.conf
> was not configured to filter out the underlying SCSI
> devices. I had to add the following filter:
> 
> filter = [ "r/disk/", "r/sd.*/", "a/.*/" ]
> 
> 
> After rebuilding the initramfs (above two changes
> commited), it all worked quite nicely ;)

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#960845: ITP: jskeus -- Lisp based integrated programming system for intelligent robots

[Kei Okada]

Package: wnpp
Severity: wishlist
Owner: Kei OKADA 
X-Debbugs-CC: debian-de...@lists.debian.org, debian-de...@lists.debian.or.jp

* Package name: euslisp
  Version: 1.2.1
  Upstream Author: Kei OKADA ,
* URL: https://github.com/euslisp/jskeus
  License: BSD
  Description:  Lisp based intelligent robots programming system
 jskeus contains software developed and used by JSK at The University
 of Tokyo. This provides modeling classes for sensors, actuators and
 robot body as well as kinematics and dynamics function library for
 writing intelligent robot behaviors. It also contains graph data
 strucutre, point cloud data class, Bullet collision detection, BVH
 character animation, STL/WRL/DAE reader and writer and some
 extensions to EusLisp language

Bug#960832: dch, fix with --vendor=Debian?

[Jelmer Vernooij]

On Sun, May 17, 2020 at 01:30:05PM +0200, Gianfranco Costamagna wrote:
> Hello again, I'm not sure but this might be a fix for the issue:
> 
> It works, but I'm not sure if this is a good fix or not, I'm not tagging the 
> bug as "patch" :)
> 
> --- lintian-brush-0.64/lintian_brush/__init__.py  2020-05-16 
> 16:33:36.0 +0200
> +++ lintian-brush-0.64ubuntu2/lintian_brush/__init__.py   2020-05-17 
> 12:55:43.0 +0200
> @@ -617,7 +617,7 @@
>path: Path to the changelog file
>summary: Entry to add
>  """
> -args = ["dch", "--no-auto-nmu"]
> +args = ["dch", "--no-auto-nmu", "--vendor=debian"]
>  if qa:
>  args.append('--qa')
>  p = subprocess.Popen(
> 
> 
> thanks for considering it and maintaining the package,
Thanks, I've committed a slightly modified version of this that just
does this for the test suite.

Cheers,

Jelmer

Bug#960850: game-data-packager: Add support for Myst 2: Riven

[Frodo Looijaard]

Package: game-data-packager
Version: 63
Severity: wishlist
Tags: patch

Dear Maintainer,

please consider support for the game Riven: the sequel to Myst.
I have attached the yaml-file that worked for me, based on the 5 CD-ROM 
version for Windows.

Kind regards,
  Frodo Looijaard
---
franchise: Myst
longname: Riven
copyright: © 1997 Cyan, Inc. and Ubi Soft Entertainment
plugin: scummvm_common
engine: scummvm (>= 1.9.0)
wiki: Riven

packages:
  riven-data:
longname: "Riven: the Sequel to Myst"
copyright: © 1997 Cyan, Inc. and Ubi Soft Entertainment
gameid: mohawk
install:
- assets
optional:
- patch102
doc:
- documentation

groups:
  assets:
group_members: |
  10148976  d6450e937791232c201ab933451815b2 a_Data.mhk
  5696789658363d21012c757ed8ef5412c4f363 a_Sounds.mhk
  334753908 ea84fee7c06975b030841706dee24dec b_Data.mhk
  13367590  3b4d8ef0037eb0d53ffafb4ddc084233 b_Sounds.mhk
  401356410 32742619cd38a9c82d6403c9ea8acf2b g_Data.mhk
  17672352  7998b57be99188e03a9ff292e71e169a g_Sounds.mhk
  312808786 cbbfe924f4f64b61901841fab44751b6 j_Data1.mhk
  351121758 310c4f169d96c124122133ae9cafcf36 j_Data2.mhk
  36480544  b27fcc84564db0776b28781ad0a24c2d j_Sounds.mhk
  434167498 53ec0d4c6c683c172b311994529a1ef6 o_Data.mhk
  7767514   c058991c942024cf7fcbe7fc8a4a194e o_Sounds.mhk
  154638574 a1d052cc19d17a52fd34909b859ffc20 p_Data.mhk
  5403024   8381d115e9739344abbf15e19edddb62 p_Sounds.mhk
  72825506  36ef4d193f46415a5d59f6a958f1200d r_Data.mhk
  11162816  827a4009dce6c43d35592b26752c8db2 r_Sounds.mhk
  658519154 9c4201dc16c7878bd47c571af79e35f3 t_Data.mhk
  27807630  e44fc1a958455a5a7076a4cd70b9f30c t_Sounds.mhk
  762689fae235a3ff26ad32a2b084c22168acd4 arcriven.z

  patch102:
group_members: |
  1212  fa08d302e0dd0c124203c0b95cc2223f b_Data1.mhk
  50490 173c3b218b9603ab42c0f27546d37b22 j_Data3.mhk

  documentation:
doc: true
group_members: |
  1725262   762a3acab001fecd382f25cafbbd4902 Manual.pdf

sha1sums: |
  86abfaa5cf206724229e2b6f82687eec6d95cf75 a_Data.mhk
  245349b5a0715406198aaaeabe26fdeae732e92f a_sounds.mhk
  917480dd6f931b3cac324f63efa370a6a971c120 b_Data.mhk
  00cf01b77408bba91332965e80da374cbb75c3e6 b_sounds.mhk
  aab4876fb74693ca1608db62cf6877a3a1d534e2 g_Data.mhk
  2eaae89538fb2f2d65e5ec7247b98cb782d070c5 g_Sounds.mhk
  f9b2d9dfbd9ac5229a260d3b0b2769cf318f73e2 j_Data1.mhk
  07d3deb6177554909ce28d48f5e4493b693fb803 j_Data2.mhk
  4a38695c974d7bc89cd1c8bf37b2d733db43947c j_Sounds.mhk
  a9942c8d45a6b21d814ced8c7daca32db9b5f3ef o_Data.mhk
  9ea6f7fb97a4d08269d376eefb6f6a8796004813 o_Sounds.mhk
  a9777d5992e897038611468e0aef2a6ba58f2f4c p_Data.mhk
  4534e64423a2be856fd3ee656c03f1798a56f0bd p_Sounds.mhk
  303dca424f497e0cf3ca70ffb128c1c276f6f33e r_Data.mhk
  0a1f0e33fed61ffd1802e46ce4c2dbef17a460b8 r_Sounds.mhk
  e8d9a9a685b253d7ca4e2c2788df333ef20c0bef t_Data.mhk
  c2accd26714a76f641e0d99ef82b8e6e20fe9f80 t_Sounds.mhk
  aae085ca50f6e555f4cefd745663faa53dbac1ed arcriven.z
  b08b179a3853ef54906aaccd87ffebda4a3f4e87 b_data1.mhk
  30d5f1d3dc345453cbb62e255b31ff82945c301d j_data3.mhk
  0dd27cf1cdf9b30354fab15a321cc2237326a632 Manual.pdf


sha256sums: |
  8ac1c23f6fe2c8ea4efd23cb1830f0dffd044288d9aecec717822d7fb639290f a_Data.mhk
  91e0b5f41a55da9a0d7307e682c60e5c5d028de61142708826bf8863e65b0932 a_sounds.mhk
  8c2a88dac31a0220605d9427782da8d2dd2bc697cc4d91885cd17537650d4745 b_Data.mhk
  caa6f9bae659265154e71ca0e0351cf687fdd2e0957e9191abb319262a7a5e93 b_sounds.mhk
  7c3a276c784bfaea5aa30188548b51bccce9ee3248a28fabb55a91562bff0537 g_Data.mhk
  4d66d7466cdd3d7ce0cacad751c7c751ac305d84c55b80339eca43b9cc4c0a11 g_Sounds.mhk
  ec2b8cada0f560916cfba08145f08cb7eafa2985a9338c1915edb0dadc4eaa98 j_Data1.mhk
  e69f8ee7d17c3bf6ee54183f5745a4b86401486854962d5d7e47672e8c85a644 j_Data2.mhk
  f98f5d3fec6f6d1c8eaafceaee342684f4e15afbe7a19b244ce048eb9e9d0b5c j_Sounds.mhk
  fbdeb926142896d44628b149a00c218ef8a7de3c1adeb31cca5def113129bbb5 o_Data.mhk
  b2712b86bb284403a8b68f33d883339ce55ed6b100fe75bb1ed16d8da6996ae4 o_Sounds.mhk
  b9b80bc8012c9c4248f6b3067d9cd9f40b37ea65eae0b3fe8e7d32888a043eaa p_Data.mhk
  047e37af947a8be956c2486d97612ac5f2c48092d7ff24c9ebcc497e23ac67a8 p_Sounds.mhk
  ab10561a7026eee98b9741de8237576a90c2243f8f8919ec175175f17774e803 r_Data.mhk
  4f41f91049c657575fd028409c6bc42b11c4806507a85d2c967d4f405822ed3e r_Sounds.mhk
  725e0342efe159d296eb9cf690eb9dcbf3f30c7e1356df0201bccdd22cf22b05 t_Data.mhk
  674ef1f0559645478fb2f15d334e61ddad3ce56741d9346de41f12ca316068a4 t_Sounds.mhk
  114a233a170367959615c692d7a73f71739db7532cb70ef701b30b70bf1f38a1 arcriven.z
  6f6c1c5539b5879e0e43dbc56c8c40010b9979e084ffefe2be1a1f691c0424f2 b_data1.mhk
  ca0b4025a1df2f43f3dc7c31c56fc84d94d17cd7006ae3a433867080f2b59a5d j_data3.mhk
  d0e0f3cfb3092ac626f1e1c1229da8e1e3569b0416c6f769a5aab53c74ae2541 Manual.pdf

...

Bug#960849: RM: python-scales -- ROM; abandoned upstream; low popcon

[Federico Ceratto]

Package: ftp.debian.org
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Please remove the package: the last upstream release is from 2015 and
the package always had low popcon.

Thanks!

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEfKfd+zM5IUCMbyuWbzG8RPUXfaoFAl7BS9IUHGZlZGVyaWNv
QGRlYmlhbi5vcmcACgkQbzG8RPUXfaqBQg/9FKLA+QpEj2lgH17ePxZFi8gmCUJ6
SsJfc6xQ4fziwX4a1SahOPOP988daDpapwcmrSrPbPHShCkrHL2MdRfHOuxHBKEE
HCYfKtCicKQoFu5M4+q2KjS5TRAkU2wcMvtg/jL+Bn9f8nRqO4coiPnPzt1A3+IX
dYVpbfr2RkDcYUyFfE2Z1QWZGIVlS08rFsWs5ieUGJsYAEFiQ8aSZTosI1NauK6J
WyLT8aG0uzcETTyww10NUUEnXcYwfsunETBZet+8KlxVAI5TTpHfEO+IH1YGMbeo
W+XMPdlALHjgeVWiZl9Zchn/wsy/I0bZvefbHlerr+WtqCg34aUdEm2FJTqJzws4
lfL23RS+j9QPnLOFJ679ZWSRmkW2NPWLL1pNQM3C3/ITpiULaHOm284Efw19O0ay
0plx1fjNWSQhcb9e7sFslR2uIvxrLy1HFNuzsZW5a0pZsv8Y7x1AYvscrsy80fjS
QrIPr+H7c82qnIpXhA4LJxtlyF+fZx1GqZHJDxy9XacBNg/y5qo8NH18M8BHtQvS
dzJp+1VKVmVd1zReC8KZmauK/chFw2JKUnIcwzPjPzB9yf1qAtqDtm9TPyc/9/Q8
KbGDWMhu/XIeNvldzLO6I006K6baZwMMo8dxlfF/nQx6cIOf4ILnlozq5ZqVsvDo
7f2eRhG1kNZoX1g=
=sNiE
-END PGP SIGNATURE-