Bug#914673: Incorrect installation of phpmyadmin.service Avahi service

[Michael Biebl]

Package: phpmyadmin
Version: 4:4.6.6-5
Severity: important

Hi,

avahi as part of it's startup routine, runs chroot.
Since phpmyadmin postinst manually creates a symlink
/etc/avahi/services/phpmyadmin.service -> ../../phpmyadmin/phpmyadmin.service
this results in the following error message in avahi as the file is not
accessible in the chroot:


Nov 26 08:41:42 pluto systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Nov 26 08:41:42 pluto avahi-daemon[695]: Successfully called chroot().
Nov 26 08:41:42 pluto avahi-daemon[695]: Successfully dropped remaining 
capabilities.
Nov 26 08:41:42 pluto avahi-daemon[695]: Loading service file 
/services/phpmyadmin.service.
Nov 26 08:41:42 pluto avahi-daemon[695]: open("/services/phpmyadmin.service", 
O_RDONLY): No such file or directory
Nov 26 08:41:42 pluto avahi-daemon[695]: Failed to load service group file 
/services/phpmyadmin.service, ignoring.


Please consider shipping /etc/avahi/services/phpmyadmin.service as a
real file, i.e. drop the symlink and move
/etc/phpmyadmin/phpmyadmin.service to /etc/avahi/services/phpmyadmin.service

This is how other packages handle it:
$ apt-file search /etc/avahi/services/
apt-cacher-ng: /etc/avahi/services/apt-cacher-ng.service
nut-server: /etc/avahi/services/nut.service
plinth: /etc/avahi/services/domain.service
plinth: /etc/avahi/services/freedombox.service
plinth: /etc/avahi/services/sftp-ssh.service
plinth: /etc/avahi/services/ssh.service
plinth: /etc/avahi/services/xmpp-server.service

Once /etc/avahi/services/phpmyadmin.service is a real file, the result
is:

Nov 26 08:54:41 pluto systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Nov 26 08:54:41 pluto avahi-daemon[3738]: Successfully called chroot().
Nov 26 08:54:41 pluto avahi-daemon[3738]: Successfully dropped remaining 
capabilities.
Nov 26 08:54:41 pluto avahi-daemon[3738]: Loading service file 
/services/phpmyadmin.service.
...
Nov 26 08:54:42 pluto avahi-daemon[3738]: Server startup complete. Host name is 
pluto.local. Local service cookie is 123456789.
Nov 26 08:54:43 pluto avahi-daemon[3738]: Service "phpMyAdmin on pluto" 
(/services/phpmyadmin.service) successfully established.


Regards,
Michael


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

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

Versions of packages phpmyadmin depends on:
ii  dbconfig-common 2.0.10
ii  dbconfig-mysql  2.0.10
ii  debconf [debconf-2.0]   1.5.69
ii  libjs-sphinxdoc 1.7.9-1
ii  perl5.28.0-4
ii  php 2:7.3+68
ii  php-cli 2:7.3+68
ii  php-gettext 1.0.12-0.1
ii  php-mbstring2:7.3+68
ii  php-mysql   2:7.3+68
ii  php-php-gettext 1.0.12-0.1
ii  php-phpseclib   2.0.12-1
ii  php-xml 2:7.3+68
ii  php7.3 [php]7.3.0~rc5-2
ii  php7.3-cli [php-cli]7.3.0~rc5-2
ii  php7.3-json [php-json]  7.3.0~rc5-2
ii  php7.3-mbstring [php-mbstring]  7.3.0~rc5-2
ii  php7.3-mysql [php-mysqli]   7.3.0~rc5-2
ii  php7.3-xml [php-xml]7.3.0~rc5-2
ii  ucf 3.0038

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd]   2.4.37-1
ii  php-bz2   2:7.3+68
pn  php-curl  
ii  php-gd2:7.3+68
ii  php-tcpdf 6.2.13+dfsg-1
ii  php-zip   2:7.3+68
ii  php7.3-bz2 [php-bz2]  7.3.0~rc5-2
ii  php7.3-gd [php-gd]7.3.0~rc5-2
ii  php7.3-zip [php-zip]  7.3.0~rc5-2

Versions of packages phpmyadmin suggests:
ii  epiphany-browser [www-browser]  3.30.1-1+b1
ii  firefox [www-browser]   63.0.1-1
ii  google-chrome-stable [www-browser]  70.0.3538.110-1
ii  lynx [www-browser]  2.8.9rel.1-2
ii  mariadb-server-10.1 [virtual-mysql-server]  1:10.1.37-1
ii  w3m [www-browser]   0.5.3-36+b1

-- debconf information excluded

Bug#914674: gnucash not building on armel anymore because of guile-2.2

[Laurent Bigonville]

Source: gnucash
Version: 1:3.3-2
Severity: serious

Hi,

The guile-2.* packages are not built on the armel architecture anymore
(see #883778) that means that gnucash cannot be built and this blocks
the transition to testing.

To fix this, gnucash should either drop the build-dependency against
guile-2.* (quickly looking at the build system this doesn't look
possible) or the binaries needs to be removed from that architecture.

Could you please have a look?

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Bug#914672: netcdf-parallel: please make the build reproducible

[Chris Lamb]

Source: netcdf-parallel
Version: 1:4.6.1-3
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that netcdf-parallel could not be built reproducibly.

This is because it ships .settings and .cmake files that include the
build arguments which, due to --debug-prefix-map are not reproducible.

Patch attached.

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/rules  2018-11-26 08:31:34.955934061 +0100
--- b/debian/rules  2018-11-26 08:50:57.884600226 +0100
@@ -91,6 +91,8 @@
-find $(CURDIR)/debian/tmp/usr/bin -type f -not -name nc-config -exec 
chrpath --delete {} \;
-find $(CURDIR)/debian/tmp/usr/lib -type f -name "*.so*" -exec chrpath 
--delete {} \;
cp include/netcdf_par.h debian/tmp/$(LIBDIR)/netcdf/mpi/include 
+   find $(CURDIR)/debian/tmp/usr/lib -type f \( -name "*.settings" -or 
-name "*.cmake" \) -print0 | \
+   xargs 0r sed -i -e 's@ [^ ]*-f\(file\|debug\)-prefix-map=[^ 
]*@@g'
 
 override_dh_auto_test:
ARGS="--output-on-failure" dh_auto_test --max-parallel=1 || echo 
"Ignoring test failures"

Bug#914670: RFS: libt3widget/1.0.2-1

[Gertjan Halkes]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: libt3widget
  Version : 1.0.2-1
  Upstream Author : Gertjan Halkes 
* URL : https://os.ghalkes.nl/t3/libt3widget.html
* License : GPLv3
  Section : libs

It builds those binary packages:

  libt3widget-dev - Development files for libt3widget
  libt3widget2 - C++ terminal dialog toolkit

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/libt/libt3widget/libt3widget_1.0.2-1.dsc

Changes since the last upload:

  * New upstream release.

Regards,
  Gertjan Halkes

Bug#914671: RM: kdemultimedia-dev kdemultimedia-kio-plugins -- RoQA; NBS

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal


These are some cruft packages that do not seem to get autoremoved.


anbe@coccia:~$ dak rm -Rn  -b kdemultimedia-dev kdemultimedia-kio-plugins
Will remove the following packages from unstable:

kdemultimedia-dev | 4:16.08.3-1 | all
kdemultimedia-kio-plugins | 4:16.08.3-1 | all

Maintainer: Debian/Kubuntu Qt/KDE Maintainers 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


audiocd-kio   | 4:16.08.3-1   | unstable   | source
audiocd-kio   | 4:17.08.3-1   | unstable   | source
kdemultimedia-dev | 4:16.08.3-1   | unstable   | all
kdemultimedia-kio-plugins | 4:16.08.3-1   | unstable   | all
kio-audiocd   | 4:16.08.3-1   | unstable   | kfreebsd-amd64, 
kfreebsd-i386
kio-audiocd   | 4:17.08.3-1   | unstable   | amd64, arm64, armel, 
armhf, i386, mips, mips64el, mipsel, ppc64el, s390x
kio-audiocd-dev   | 4:16.08.3-1   | unstable   | kfreebsd-amd64, 
kfreebsd-i386
kio-audiocd-dev   | 4:17.08.3-1   | unstable   | amd64, arm64, armel, 
armhf, i386, mips, mips64el, mipsel, ppc64el, s390x


Andreas

Bug#914395: [pkg-gnupg-maint] Bug#914395: dirmngr log

[Werner Koch]

On Sun, 25 Nov 2018 22:22, csm...@debian.org said:
> It seems it needs the SRV record and fails wrong without it.
> Checking on the same system looking up that SRV record I get the
> expected NXDOMAIN error.

That seems to be a Debian specific problem; with a dirmngr started by
the gpg command, I get this with master (and pretty sure also with 2.2.11):

  DBG: chan_7 <- KEYSERVER --clear hkp://keyring.debian.org
  DBG: chan_7 -> OK
  DBG: chan_7 <- KS_GET -- 0xDF50FEA5
  DBG: dns: libdns initialized
  DBG: dns: getsrv(_pgpkey-http._tcp.keyring.debian.org) -> 0 records
  DBG: dns: resolve_dns_name(keyring.debian.org): Success
  resolve_dns_addr for 'keyring.debian.org': 'keyring.debian.org' [already 
known]
  resolve_dns_addr for 'keyring.debian.org': 'keyring.debian.org' [already 
known]
  DBG: dns: resolve_dns_name(keyring.debian.org): Success
  DBG: chan_7 -> S SOURCE http://keyring.debian.org:11371
  DBG: (20847 bytes sent via D lines not shown)

Can you please test with

  standard-resolver
  no-use-tor

in dirmngr.conf ?


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


pgpQo0mPcGr38.pgp
Description: PGP signature

Bug#907573: Please provide u-boot image for qemu

[Vagrant Cascadian]

On 2018-10-10, Vagrant Cascadian wrote:
> On 2018-09-30, Ivo De Decker wrote:
>> I pushed a branch 'qemu' to salsa which creates a u-boot-qemu package with 
>> the
>> images for the architectures that are actually in debian:
...
>> Inspired by other qemu bootloaders (like edk2, openbios, ...), I created this
>> as an arch all package, which is built using the cross compilers available in
>> the archive. This caused some changes in the build of the package. I would be
>> interested to get your feedback on this. Do you think this is an acceptable
>> way forward?

The branch still merges on top of 2018.11-1 and if building arch:all
only, it builds! Cool!

When building arch:amd64+all it FTBFS, as dh_strip is called and
attempts to use amd64 strip on the arm*/mips* binary uboot.elf files. My
local workaround was:

+override_dh_strip:
+   dh_strip -X qemu_

Which seemed to work ok, but of course, leaves them unstripped...

It also needs some updates to debian/bin/update-lintian-overrides, which
I took a quick stab at, but fighting with it probably highlights that
the overrides updating should be refactored a bit anyways, and this
arch:all cross-build just makes it more obvious.


> Overall, I like the improvements, but I have mixed feelings.
>
> With multi-arch being possible, I'm inclined to keep things native... At
> the same time, multi-arch is a bit annoying to require for someone
> wanting to use qemu to boot a foreign architecture...
>
> Since all the cross-compilers are (currently) only available on
> amd64/i386, this would mean you can't build u-boot's arch:all packages
> on anything other than amd64/i386, which might cause problems for
> tests.reproducible-builds.org, which builds both arch:any and arch:all
> packages for amd64, i386, arm64 and armhf.

This all still holds true, especially in light of the dh_strip issues.

So, it still seems like it would be easier to just add u-boot-qemu
native builds, but that's less useful to the end-user. Then again, an
end-user doing u-boot with qemu on non-native architectures is pretty
sophisticated already... maybe requiring multi-arch isn't too much to
ask of them.

> I think it would also be easier to transition to arch:all later and
> start off with native packages than the other way around.

Now I'm not as sure that will be an easier transition... changing later
would probably be just about as annoying either way.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

[Fabian Greffrath]

James Godfrey-Kittle wrote:
> Hm, I'm unable to reproduce this error with fontmake 1.6.1 and the
> latest version of FiraCode from https://github.com/tonsky/FiraCode.

Is this with the fontmake version packaged in Debian?

 - Fabian

Bug#914669: RFS: libt3window/0.3.2-1

[Gertjan Halkes]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: libt3window
  Version : 0.3.2-1
  Upstream Author : Gertjan Halkes 
* URL : https://os.ghalkes.nl/t3/libt3window.html
* License : GPLv3
  Section : libs

It builds those binary packages:

  libt3window-dev - Development files for libt3window
  libt3window0 - Library for creating window-based terminal programs

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

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

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

dget -x
https://mentors.debian.net/debian/pool/main/libt/libt3window/libt3window_0.3.2-1.dsc

Changes since the last upload:

  * New upstream release.

Regards,
  Gertjan Halkes

Bug#914651: perl: -i option broken

[gregor herrmann]

Control: forwarded -1 https://rt.perl.org/Public/Bug/Display.html?id=133659
COntrol: tag -1 + upstream patch

On Mon, 26 Nov 2018 08:18:15 +0700, Igor Liferenko wrote:

> The following command yields "a":
> 
> ( echo a ; echo b ; echo c ) | perl -pe 'last if /b/'
> 
> The following command yields "abc" (one character on a line):
> 
> ( echo a ; echo b ; echo c ) >/tmp/x; perl -i -pe 'last if /b/' /tmp/x; 
> cat /tmp/x

This sounds like upstream bug
https://rt.perl.org/Public/Bug/Display.html?id=133659
to me.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   BOFH excuse #211:  Lightning strikes. 

Bug#895437: QEMU support is lacking

[Laurent Bigonville]

On Wed, 11 Apr 2018 14:57:44 +0100 Corentin =?ISO-8859-1?Q?No=EBl?= 
 wrote:


Hello,

> With GNOME Builder 3.28.1 QEMU support doesn't work on Debian.
> A check is added in this specific commit: https://gitlab.gnome.org/GNOM
> E/gnome-builder/commit/771d70802f46cca181c8c49e14a54b11bac6a75b
> The bug is reported on the QEMU debian side:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868030

I'm not sure about this bug.

The qemu bug (#868030) is fixed since April, is there anything needed to 
be done on the gnome-builder side?


Kind regards,

Laurent Bigonville

Bug#910977: transition: atlas-cpp

[Andreas Beckmann]

Followup-For: Bug #910977

nmu eris_1.3.23-7 . hurd-i386 kfreebsd-amd64 kfreebsd-i386 . unstable .  -m 
"Rebuild against libatlas-cpp-0.6-3."

The atlas-cpp builds were not yet available on these architectures
at the time the other architectures were binNMUed.


Andreas

Bug#914668: Please upgrade to 3.30.2

[Laurent Bigonville]

Source: gnome-builder
Version: 3.30.1-6
Severity: wishlist

Hi,

It seems that gnome-builder 3.30.2 has been released with quite some
changes:

==
Version 3.30.2
==

Changes since last release:

 • Fixes for tracking GNOME's Night Light setting
 • Fix running of Builder's unit tests without installing
 • Fix relative paths from .git gitdir
 • Fix gdb communication over chatty intermediate PTY
 • Allow gtksourceview-3.0 applications to use Builder style-schemes
 • Icon fixes and improvements
 • More UI components display keyboard shortcuts
 • Saving files will now create the necessary directory structure
 • Buffers will mark themselves as "modified on disk" when the backing file
   is deleted
 • Drop SSL/PKI overrides for Flatpak
 • Git plugin now updates status when the checkout directory changes
 • Vim command-bar has improved results when listing files/directories
 • Project creation and cloning wizards now update paths in response to changes
 • ".in" filename suffix will be ignored when guessing syntax language
 • You can specify what Ninja path to use using $NINJA in build preferences
 • RLS is now restarted when Cargo.toml changes
 • Fuzzy matching completion results has been improved for some corner-cases
 • Gtk-sharp3 template now builds correctly
 • Editor is properly focused when re-selecting open buffer from global search
 • Various bug fixes to gstyle
 • Meson toolchain editing improvements

Updated Translations:

  Serbian, Latvian, Brazilian Portuguese, Polish, Italian, Slovenian, Czech,
  Indonesian, Turkish, Romanian, German, Hungarian, Lithuanian, Swedish,
  French


Would probably be a good idea to package it

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

-- no debconf information

Bug#914518: wxmaxima: Homepage field is outdated

[Gunter Königsmann]

Ok... ...will update the other bug as the problem has been resolved by
uploading a new wxMaxima version.

Bug#898820: libicu-dev is not Multi-Arch compatible

[GCS]

Hi Hugh,

On Wed, Nov 21, 2018 at 9:45 PM Hugh McMaster  wrote:
> What help do you need to resolve this bug?
 We have been to this route. As noted, indeed icu-config is deprecated
long time ago and ICU can be detected with pkg-config instead. Several
big projects like PHP (just checked its upcoming release, version 7.3)
still don't handle the missing icu-config.
Please help these projects, convince them to update their ICU library
detection bits. As soon as no project depends on icu-config presence,
I will disable that and make libicu63 Multi-Arch: same.

Regards,
Laszlo/GCS

Bug#912451: staden-io-lib FTBFS on !x86: test failures

[Andreas Tille]

Control: tags -1 forwarded James Bonfield 

Hi James,

version 1.14.11 of staden-io-lib creates an error in the test suite for non x86
architectures.  Here you have an easy overview what architectures are affected:

   https://buildd.debian.org/status/package.php?p=staden-io-lib&suite=sid

and this is basically the failure.  Do you have any idea how to fix this?

...
FAIL: scram
===

Loading ce.fa
Generating ce#sorted.sam
Generating ce#unsorted.sam
=== testing ./data/c1#bounds.sam ===
./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator
 ../progs/scramble  ./data/c1#bounds.sam test.out/c1#bounds.sam
 ../progs/scramble  -r ./data/c1.fa ./data/c1#bounds.sam 
test.out/c1#bounds.full.cram
 ../progs/scramble  ./data/c1#bounds.sam > test.out/tmp.sam
 ../progs/scramble  test.out/c1#bounds.full.cram > test.out/c1#bounds.full.sam
 ../progs/scramble  -O bam test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.bam
 ../progs/scramble  test.out/c1#bounds.full.bam test.out/tmp.sam
corrupted size vs. prev_size
Aborted
FAIL scram.test (exit status: 1)

FAIL: scram_mt
==

=== testing ./data/c1#bounds.sam ===
./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator
 ../progs/scramble -t4 ./data/c1#bounds.sam test.out/c1#bounds.sam
 ../progs/scramble -t4 -r ./data/c1.fa ./data/c1#bounds.sam 
test.out/c1#bounds.full.cram
 ../progs/scramble -t4 ./data/c1#bounds.sam > test.out/tmp.sam
 ../progs/scramble -t4 test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.sam
 ../progs/scramble -t4 -O bam test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.bam
 ../progs/scramble -t4 test.out/c1#bounds.full.bam test.out/tmp.sam
corrupted size vs. prev_size
Aborted
FAIL scram_mt.test (exit status: 1)


Testsuite summary for io_lib 1.14.11

# TOTAL: 9
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See tests/test-suite.log

make[4]: *** [Makefile:716: test-suite.log] Error 1



Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#914667: performous FTBFS on armel/mips/mipsel: undefined reference to `__atomic_load_8'

[Adrian Bunk]

Source: performous
Version: 1.1+git20181118-1
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/package.php?p=performous&suite=sid

...
/usr/bin/c++  -std=c++14 -Wall -Wextra -fcx-limited-range -g -O2 
-fdebug-prefix-map=/<>/performous-1.1+git20181118=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread  -Wl,-z,relro -Wl,--as-needed -pthread -rdynamic 
CMakeFiles/performous.dir/3dobject.cc.o CMakeFiles/performous.dir/audio.cc.o 
CMakeFiles/performous.dir/backgrounds.cc.o CMakeFiles/performous.dir/cache.cc.o 
CMakeFiles/performous.dir/color.cc.o 
CMakeFiles/performous.dir/configuration.cc.o 
CMakeFiles/performous.dir/controllers-joystick.cc.o 
CMakeFiles/performous.dir/controllers-keyboard.cc.o 
CMakeFiles/performous.dir/controllers-midi.cc.o 
CMakeFiles/performous.dir/controllers.cc.o 
CMakeFiles/performous.dir/dancegraph.cc.o 
CMakeFiles/performous.dir/database.cc.o CMakeFiles/performous.dir/dialog.cc.o 
CMakeFiles/performous.dir/engine.cc.o CMakeFiles/performous.dir/execname.cc.o 
CMakeFiles/performous.dir/ffmpeg.cc.o CMakeFiles/performous.dir/fs.cc.o 
CMakeFiles/performous.dir/game.cc.o CMakeFiles/performous.dir/glshader.cc.o 
CMakeFiles/performous.dir/glutil.cc.o 
CMakeFiles/performous.dir/guitargraph.cc.o 
CMakeFiles/performous.dir/hiscore.cc.o CMakeFiles/performous.dir/image.cc.o 
CMakeFiles/performous.dir/instrumentgraph.cc.o 
CMakeFiles/performous.dir/layout_singer.cc.o CMakeFiles/performous.dir/log.cc.o 
CMakeFiles/performous.dir/main.cc.o CMakeFiles/performous.dir/menu.cc.o 
CMakeFiles/performous.dir/midifile.cc.o 
CMakeFiles/performous.dir/musicalscale.cc.o 
CMakeFiles/performous.dir/notegraph.cc.o CMakeFiles/performous.dir/notes.cc.o 
CMakeFiles/performous.dir/opengl_text.cc.o CMakeFiles/performous.dir/pitch.cc.o 
CMakeFiles/performous.dir/platform.cc.o CMakeFiles/performous.dir/player.cc.o 
CMakeFiles/performous.dir/players.cc.o CMakeFiles/performous.dir/playlist.cc.o 
CMakeFiles/performous.dir/progressbar.cc.o 
CMakeFiles/performous.dir/requesthandler.cc.o 
CMakeFiles/performous.dir/screen_audiodevices.cc.o 
CMakeFiles/performous.dir/screen_intro.cc.o 
CMakeFiles/performous.dir/screen_paths.cc.o 
CMakeFiles/performous.dir/screen_players.cc.o 
CMakeFiles/performous.dir/screen_playlist.cc.o 
CMakeFiles/performous.dir/screen_practice.cc.o 
CMakeFiles/performous.dir/screen_sing.cc.o 
CMakeFiles/performous.dir/screen_songs.cc.o CMakeFiles/performous.dir/song.cc.o 
CMakeFiles/performous.dir/songitems.cc.o 
CMakeFiles/performous.dir/songparser-ini.cc.o 
CMakeFiles/performous.dir/songparser-mid.cc.o 
CMakeFiles/performous.dir/songparser-sm.cc.o 
CMakeFiles/performous.dir/songparser-txt.cc.o 
CMakeFiles/performous.dir/songparser-xml.cc.o 
CMakeFiles/performous.dir/songparser.cc.o CMakeFiles/performous.dir/songs.cc.o 
CMakeFiles/performous.dir/svg.cc.o CMakeFiles/performous.dir/texture.cc.o 
CMakeFiles/performous.dir/theme.cc.o CMakeFiles/performous.dir/unicode.cc.o 
CMakeFiles/performous.dir/util.cc.o CMakeFiles/performous.dir/video.cc.o 
CMakeFiles/performous.dir/video_driver.cc.o 
CMakeFiles/performous.dir/webcam.cc.o CMakeFiles/performous.dir/webserver.cc.o  
-o ../performous -lboost_program_options -lboost_filesystem -lboost_iostreams 
-lboost_system -lboost_locale -lboost_regex -licuuc -licudata -licui18n -licuio 
-lepoxy -Wl,-Bstatic -lSDL2main -Wl,-Bdynamic -lSDL2 -lpangocairo-1.0 
-lpango-1.0 -lcairo -lfreetype -lglib-2.0 -lgobject-2.0 -lrsvg-2 -lcairo 
-lfreetype -lgdk_pixbuf-2.0 -lxml++-2.6 -lxml2 -lglibmm-2.4 -lglib-2.0 
-lsigc-2.0 -lavformat -lavcodec -lavutil -lswresample -lavutil -lswscale 
-lavutil -lz -ljpeg -lpng -lz -lportaudio -lfontconfig -lportmidi 
-lboost_chrono -lboost_thread -lboost_system -lboost_date_time -lboost_atomic 
-lpthread -lcpprest -lcrypto -lssl ../lib/libced.a -lboost_locale -lboost_regex 
-licuuc -licudata -licui18n -licuio -lepoxy -Wl,-Bstatic -lSDL2main 
-Wl,-Bdynamic -lSDL2 -lpangocairo-1.0 -lpango-1.0 -lcairo -lfreetype -lglib-2.0 
-lgobject-2.0 -lrsvg-2 -lgdk_pixbuf-2.0 -lxml++-2.6 -lxml2 -lglibmm-2.4 
-lsigc-2.0 -lavformat -lavcodec -lavutil -lswresample -lswscale -lz -ljpeg 
-lpng -lportaudio -lfontconfig -lportmidi -lboost_chrono -lboost_thread 
-lboost_date_time -lboost_atomic -lpthread -lcpprest -lcrypto -lssl 
/usr/bin/ld: CMakeFiles/performous.dir/ffmpeg.cc.o: in function 
`FFmpeg::seek_internal()':
/usr/include/c++/8/atomic:250: undefined reference to `__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to 
`__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/atomic:239: undefined reference to 
`__atomic_store_8'
/usr/bin/ld: CMakeFiles/performous.dir/ffmpeg.cc.o: in function 
`FFmpeg::seek(double, bool)':
/usr/include/c++/8/atomic:239: undefined reference to `__atomic_store_8'
/usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to 
`__atomic_load_8'
/usr/bin/ld: /usr/include/c++/8/atomic:250: undefined reference to 
`__atomic_load_8'
/usr/bin/

Bug#912113: harvest-tools: diff for NMU version 1.3-2.1

[Andreas Tille]

Hi Adrian,

thanks for the patch.  I'm now back from VAC and uploaded including other
pending changes from Git.  In general feel free to choose way shorter term
NMUs since the Debian Med team has a low NMU threshold.

On Sun, Nov 25, 2018 at 06:50:55PM +0200, Adrian Bunk wrote:
> I've prepared an NMU for harvest-tools (versioned as 1.3-2.1) and 
> uploaded it to DELAYED/14. Please feel free to tell me if I should 
> cancel it.

Overridden by recent upload - thanks for all your QA work

 Andreas.

-- 
http://fam-tille.de

Bug#914666: dlt-daemon: FTBFS with glibc 2.28 (upstream fix attached)

[Gianfranco Costamagna]

Package: dlt-daemon
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
Version: 2.17.0-2
Severity: important
Tags: patch

thanks for considering it :)

G.
>From 0be9c2726c45485cb0e00cec57c0bd1c167eb9c5 Mon Sep 17 00:00:00 2001
From: Oleksandr Kravchuk 
Date: Sun, 26 Aug 2018 01:48:48 +0200
Subject: [PATCH] Fix compilation with glibc 2.28

Package compilation fails with GLIBC 2.28:

stat.h:56:8: error: redefinition of 'struct statx_timestamp'
stat.h:99:8: error: redefinition of 'struct statx'

Signed-off-by: Oleksandr Kravchuk 
---
 src/daemon/dlt-daemon.c| 2 +-
 src/daemon/dlt_daemon_client.c | 2 +-
 src/daemon/dlt_daemon_socket.c | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/daemon/dlt-daemon.c b/src/daemon/dlt-daemon.c
index 0232cb1..5695a4b 100644
--- a/src/daemon/dlt-daemon.c
+++ b/src/daemon/dlt-daemon.c
@@ -47,7 +47,7 @@
 #endif
 #include 
 #include 
-#ifdef linux
+#ifdef defined(linux) && defined(__NR_statx)
 #include 
 #endif
 
diff --git a/src/daemon/dlt_daemon_client.c b/src/daemon/dlt_daemon_client.c
index 7c6e1bd..cb59239 100644
--- a/src/daemon/dlt_daemon_client.c
+++ b/src/daemon/dlt_daemon_client.c
@@ -46,7 +46,7 @@
 #endif
 #include 
 #include 
-#ifdef linux
+#ifdef defined(linux) && defined(__NR_statx)
 #include 
 #endif
 
diff --git a/src/daemon/dlt_daemon_socket.c b/src/daemon/dlt_daemon_socket.c
index 961556c..4ae1d86 100644
--- a/src/daemon/dlt_daemon_socket.c
+++ b/src/daemon/dlt_daemon_socket.c
@@ -49,7 +49,7 @@
 #endif
 #include 
 #include 
-#ifdef linux
+#ifdef defined(linux) && defined(__NR_statx)
 #include 
 #endif
 

Bug#588411: Need help dealing with this l10n bug?

[Lionel Debroux]

Hi,

This is upstream :)

> > this German l10n bug is open for more than 8 years. Do you need help
> > dealing with it? I could provide a NMU, but of course a maintainer
> > upload is (much) preferred.
>
> Well, almost 2 years ago this has been commited upstream [1] and the
> bug tagged accordingly.  I always hoped to see some more upstream
> activity and a new upstream release containing the patch.
>
> However, this seems not to happen anymore and perhaps you are right.
> I'll prepare the patch and a new upload.
I working more on the tilibs repo than on the tilp_and_gfm repo anyway,
but indeed, in general, I'm not making frequent releases, to say the
least... so far, 5 releases since I became the maintainer over 9 years ago.
There are still several things I want to fix / improve before making the
next release.


Thanks for your work ;)


Bye,
Lionel.

Bug#912839: 3.1 released soon

[Christian Ehrhardt]

I should reply here instead of the Dup bug I guess :-)

IMHO we are just 8 days away from qemu 3.1 [1]
Maybe do the work just once and directly prep 3.1 instead of doing ->3.0
and then ->3.1 later?

@Michael Tokarev  - just curious, do you have an ETA
if/when you'll get to 3.0 or even 3.1 ?

[1]: https://wiki.qemu.org/Planning/3.1

Bug#914665: O: fonts-tiresias -- Fonts for the visually impaired

[Gürkan Myczko]

Package: wnpp
Severity: normal

I orphan this package now. (Upstream homepage dead, no new place for it
found)

Maintaining a package requires time and skills. Please only adopt this
package if you are *sure* you will have enough time and attention to
work on it.

If you want to be the new maintainer, please see
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Bug#913210: transition: libqalculate

[Vincent Legout]

On Wed, Nov 21, 2018 at 12:59:31PM +0100, Emilio Pozuelo Monfort wrote :
> Control: tags -1 confirmed
> 
> On 08/11/2018 07:12, Vincent Legout wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debian.org
> > Usertags: transition
> > 
> > Hello,
> > 
> > I'd like to request a transition slot for libqalculate.
> > 
> > The new version is in experimental. It has 4 reverse dependencies.
> > qalculate-gtk has also been uploaded to experimental, and I plan to
> > upload it to unstable just after libqalculate. The other 3 build fine
> > with the new version.
> 
> Go ahead.

Thanks. libqalculate and qalculate-gtk have both been uploaded to
unstable. Would it be possible to schedule rebuilds for the remaining
reverse dependencies please? (cantor plasma-workspace step)

Vincent

Bug#914664: RM: icedove-bidiui [all] -- RoQA; NBS; superseded by thunderbird-bidiui

[Andreas Beckmann]

Package: ftp.debian.org
Severity: normal

bidiui | 0.9.7-1   | unstable   | source
bidiui | 0.9.7-2   | unstable   | source
icedove-bidiui | 0.9.7-1   | unstable   | all
thunderbird-bidiui | 0.9.7-2   | unstable   | all


anbe@coccia:~$ dak rm -Rn  -b icedove-bidiui
Will remove the following packages from unstable:

icedove-bidiui |0.9.7-1 | all

Maintainer: Debian Hebrew Packaging Team


--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


Andreas

Bug#890594: salsa script ready to review

[Xavier]

Le 25/11/2018 à 23:25, Raphael Hertzog a écrit :
> On Sun, 25 Nov 2018, Xavier wrote:
>> My last change produces this bug. Fixed now, I pushed a new .deb in the
>> same place.
> 
> Next try with a package whose HEAD points to the wrong branch (upstream)
> but that already has the desired target branch (debian/master)
> 
> $ salsa --conf-file +./salsa-pkg-security.conf update_safe radare2-cutter 
> --verbose --debug
> salsa info: Project radare2-cutter => pkg-security-team/radare2-cutter
> salsa info: pkg-security-team/radare2-cutter id is 29721
> radare2-cutter:
>   bad description: Packaging for cutter from radare project
>   Default branch is upstream
> 1 packages misconfigured, update them ? (Y/n)
> salsa info: Project radare2-cutter => pkg-security-team/radare2-cutter
> salsa info: Configuring radare2-cutter
> salsa warn: Error POSTing 
> https://salsa.debian.org/api/v4/projects/29721/repository/branches (HTTP 
> 400): Bad Request {"message":"Branch already exists"} at 
> /usr/share/perl5/Devscripts/Salsa/update_repo.pm line 51.
> 
> Now a well configured repository but I inversed SOURCE_BRANCH and 
> DEST_BRANCH. The operation
> seems to work:
> $ salsa --conf-file +./salsa-pkg-security.conf update_safe acct --verbose 
> --debug
> salsa info: Project acct => pkg-security-team/acct
> salsa info: pkg-security-team/acct id is 6641
> acct:
>   Default branch is debian/master
> 1 packages misconfigured, update them ? (Y/n) 
> salsa info: Project acct => pkg-security-team/acct
> salsa info: Configuring acct
> salsa warn: Deleting old email-on-push (redirected to 
> dispa...@tracker.debian.org)
> salsa info: Email-on-push hook added to project 6641 (recipients: 
> dispa...@tracker.debian.org)
> salsa warn: Deleting old tagpending (was 
> https://webhook.salsa.debian.org/tagpending/acct)
> salsa info: Tagpending hook added to project 6641
> salsa info: Project 6641 updated
> 
> Now I put SOURCE_BRANCH and DEST_BRANCH to their desired value and the next 
> run doesn't work:
> $ salsa --conf-file +./salsa-pkg-security.conf update_safe acct --verbose 
> --debug
> salsa info: Project acct => pkg-security-team/acct
> salsa info: pkg-security-team/acct id is 6641
> acct:
>   Default branch is master
> 1 packages misconfigured, update them ? (Y/n) 
> salsa info: Project acct => pkg-security-team/acct
> salsa info: Configuring acct
> salsa warn: Error POSTing 
> https://salsa.debian.org/api/v4/projects/6641/repository/branches (HTTP 400): 
> Bad Request {"message":"Branch already exists"} at 
> /usr/share/perl5/Devscripts/Salsa/update_repo.pm line 51.
> 
> Maybe you should separate the "rename branch" operation from the "set HEAD to"
> operation. Because we want to fix HEAD pointing to the wrong branch even when
> there's nothing to rename. And it could be useful for example to rename all
> "upstream" into "upstream/latest" for example (without changing HEAD).
> 
> SALSA_RENAME_BRANCH="upstream:upstream/latest master:debian/master"
> SALSA_SET_HEAD="debian/master"
> 
> Cheers,

Hello,

half fixed:
 - "rename head" is tried even if branch already exists
 - original branch is deleted only if new branch creation was successful
 - I'll write a separate "rename" command to rename another branch.
 - .deb updated

Cheers,

Bug#914663: gxtuner does not trap errors from make

[Helmut Grohne]

Source: gxtuner
Version: 3.0-1
Severity: serious
Justification: policy 4.6

gxtuner's upstream Makefile does not trap errors from the compiler. Most
compiler invocations carry a "-" prefix used for ignoring errors. That
prefix violates policy section 4.6. It also makes debugging build
failures unnecessarily hard and facilitates misbuilds.

Helmut

Bug#914662: transition: hypre

[Drew Parsons]

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

With the hdf5 transition completed, I'd like to proceed with the hypre
transition from 2.14.0 to 2.15.1.  

I've updated hypre packaging to remove circular dependencies between
libHYPRE sublibraries.  petsc and sundials will build and pass tests
with a trivial fix to handle the new hypre libraries.

FYI: a transition of petsc/slepc from 3.9 to 3.10 will follow, subject to
being able to fix the petsc FTBFS (memory exhausted) on mips.

Ben file:

title = "hypre";
is_affected = .depends ~ "libhypre-2.14.0" | .depends ~ "libhypre-2.15.1";
is_good = .depends ~ "libhypre-2.15.1";
is_bad = .depends ~ "libhypre-2.14.0";


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

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

Bug#914661: parchive FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: parchive
Version: 1.1-4.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

parchive fails to cross build from source, because it builds for the
build architecture as a make default. Nothing tells make which CC to
use. The easiest way of fixing that is using dh_auto_build. After doing
so, parchive cross builds successfully. Please consider applying the
attached patch.

Helmut
diff -u parchive-1.1/debian/changelog parchive-1.1/debian/changelog
--- parchive-1.1/debian/changelog
+++ parchive-1.1/debian/changelog
@@ -1,3 +1,10 @@
+parchive (1.1-4.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Let dh_auto_build pass cross tools to make. (Closes: #-1)
+
+ -- Helmut Grohne   Mon, 26 Nov 2018 06:15:14 +0100
+
 parchive (1.1-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u parchive-1.1/debian/rules parchive-1.1/debian/rules
--- parchive-1.1/debian/rules
+++ parchive-1.1/debian/rules
@@ -22,7 +22,7 @@
dh_testdir
 
# Add here commands to compile the package.
-   $(MAKE)
+   dh_auto_build
#/usr/bin/docbook-to-man debian/parchive.sgml > parchive.1
 
touch build-stamp

Bug#914660: entr FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: entr
Version: 4.1-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

entr fails to cross build from source, because it builds for the wrong
architecture. Its configure inspects uname output with no way to
override it. Therefore, my patch reimplements configure in debian/rules.
Furthermore, the upstream Makefiles hard code the build architecture
pkg-config. My patch makes it substitutable and dh_auto_build will
substitute it. Please consider applying it as it makes entr cross
buildable.

Helmut
diff --minimal -Nru entr-4.1/debian/changelog entr-4.1/debian/changelog
--- entr-4.1/debian/changelog   2018-08-21 13:51:44.0 +0200
+++ entr-4.1/debian/changelog   2018-11-26 06:07:33.0 +0100
@@ -1,3 +1,12 @@
+entr (4.1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Reimplement ./configure in debian/rules without uname.
++ cross.patch: Make pkg-config substitutable.
+
+ -- Helmut Grohne   Mon, 26 Nov 2018 06:07:33 +0100
+
 entr (4.1-1) unstable; urgency=low
 
   [ Otto Kekäläinen ]
diff --minimal -Nru entr-4.1/debian/patches/cross.patch 
entr-4.1/debian/patches/cross.patch
--- entr-4.1/debian/patches/cross.patch 1970-01-01 01:00:00.0 +0100
+++ entr-4.1/debian/patches/cross.patch 2018-11-26 06:07:33.0 +0100
@@ -0,0 +1,35 @@
+--- entr-4.1.orig/Makefile.debian
 entr-4.1/Makefile.debian
+@@ -5,8 +5,9 @@
+ # make test -f Makefile.linux-lbsd
+ # sudo make install
+ 
+-CFLAGS += -D_GNU_SOURCE -I/usr/include/kqueue $(shell pkg-config --cflags 
libbsd-overlay)
+-LDFLAGS += -lpthread -lkqueue $(shell pkg-config --libs libbsd-ctor)
++PKG_CONFIG ?= pkg-config
++CFLAGS += -D_GNU_SOURCE -I/usr/include/kqueue $(shell $(PKG_CONFIG) --cflags 
libbsd-overlay)
++LDFLAGS += -lpthread -lkqueue $(shell $(PKG_CONFIG) --libs libbsd-ctor)
+ MANPREFIX ?= ${PREFIX}/share/man
+ 
+ include Makefile.bsd
+--- entr-4.1.orig/Makefile.kfreebsd
 entr-4.1/Makefile.kfreebsd
+@@ -1,5 +1,6 @@
+-CFLAGS += -D_GNU_SOURCE $(shell pkg-config --cflags libbsd-overlay)
+-LDFLAGS += $(shell pkg-config --libs libbsd-overlay)
++PKG_CONFIG ?= pkg-config
++CFLAGS += -D_GNU_SOURCE $(shell $(PKG_CONFIG) --cflags libbsd-overlay)
++LDFLAGS += $(shell $(PKG_CONFIG) --libs libbsd-overlay)
+ MANPREFIX ?= ${PREFIX}/share/man
+ 
+ include Makefile.bsd
+--- entr-4.1.orig/Makefile.linux
 entr-4.1/Makefile.linux
+@@ -1,5 +1,6 @@
++PKG_CONFIG ?= pkg-config
+ CPPFLAGS += -D_GNU_SOURCE -D_LINUX_PORT -Imissing
+-LDFLAGS += $(shell pkg-config --libs libbsd-ctor)
++LDFLAGS += $(shell $(PKG_CONFIG) --libs libbsd-ctor)
+ MANPREFIX ?= ${PREFIX}/share/man
+ EXTRA_SRC = missing/strlcpy.c missing/kqueue_inotify.c
+ 
diff --minimal -Nru entr-4.1/debian/patches/series 
entr-4.1/debian/patches/series
--- entr-4.1/debian/patches/series  2018-08-21 13:51:44.0 +0200
+++ entr-4.1/debian/patches/series  2018-11-26 06:06:02.0 +0100
@@ -1,2 +1,3 @@
 libbsd-overlay.patch
 kfreebsd-support.patch
+cross.patch
diff --minimal -Nru entr-4.1/debian/rules entr-4.1/debian/rules
--- entr-4.1/debian/rules   2018-08-21 13:51:44.0 +0200
+++ entr-4.1/debian/rules   2018-11-26 06:05:58.0 +0100
@@ -7,12 +7,20 @@
 # Hardening
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all future=+lfs
 
+# Reimplement ./configure without relying on uname.
+include /usr/share/dpkg/architecture.mk
+ifeq (,$(filter linux kfreebsd,$(DEB_HOST_ARCH_OS)))
+UPSTREAM_MAKEFILE=Makefile.bsd
+else
+UPSTREAM_MAKEFILE=Makefile.$(DEB_HOST_ARCH_OS)
+endif
+
 # Rules
 %:
-   dh $@ --parallel
+   dh $@ --parallel --buildsystem=makefile
 
-override_dh_auto_configure:
-   ./configure
+override_dh_auto_build:
+   dh_auto_build -- -f $(UPSTREAM_MAKEFILE)
 
 override_dh_auto_install:
dh_auto_install -- PREFIX=/usr

Bug#914495: linux-image-4.18.0-3-amd64: does not boot here

[TS]

Amy Kos schrieb/wrote:
> Could be graphics related, boot stops at:
> 
>  fb: switching to inteldrmfb from EFI VGA
> 
> Disabling kernel mode setting with parameter nomodeset boots to tty.
> 

confirming, adding 'nomodeset' to linux boot options lets
linux-image-4.18.0-3-amd64 boot. Thanks Amy for the hint.

HTH



kind regards,

 Thilo

Bug#914646: piuparts: failed-testing with no prpblem listed

[Andreas Beckmann]

Control: reassign -1 sslsplit 0.5.4-1
Control: retitle -1 sslsplit: ships /var/run/sslsplit
Control: severity -1 serious

On 2018-11-25 23:02, Adrian Bunk wrote:
> https://piuparts.debian.org/sid/fail/sslsplit_0.5.4-1.log

> There is nothing in the log indicating why this is failed-testing.

There is, although it is not abvious:

0m21.0s INFO: dirname part contains a symlink:
  /var/run/sslsplit (sslsplit) != /run/sslsplit (?)
/var/run -> /run

Lintian reports this error as dir-or-file-in-var-run

https://lintian.debian.org/maintainer/ben...@debian.org.html#sslsplit


Andreas

Bug#911297: wpasupplicant: WPA EAP broken

[Christoph Anton Mitterer]

Hi.

Indeed, it's likely a duplicate of #907518.

I'd also agree with Andrej, that the defaults shouldn't be changed just
to please people who haven't done their homework and support at least
1.2 (which is already 10 years old).
Why should others suffer in their security just because of them?!


OTOH it's unfortunately a fact that many EAP WiFis will not change...
so in the next stable release, many people will suffer from this issue.

For many cases people will anyway distrust such WiFis and just use them
to connect to the internet... so one more reason not to lower the
security for openssl system-wide but at most for wpasupplicant only.

I could however not find the user configurable setting for it, that
Andrej mentioned.


Cheers,
Chris.

Bug#914659: ITP: djangorestframework-filters -- Filters for Django REST Framework

[Wookey]

Package: wnpp
Severity: wishlist
Owner: Wookey 

* Package name: djangorestframework-filters
  Version : 0.10.2.post0
  Upstream Author : Philip Neustrom 
* URL : https://github.com/philipn/django-rest-framework-filters

* License : Expat
  Programming Lang: Python
  Description : Filters for Django REST Framework

An extension to Django REST framework and Django filter that makes it easy
to filter across relationships. Historically, this extension also provided
a number of additional features and fixes, however many of these have been 
merged back into django-filter
 
 
This package is needed for lava support in Debian (Lava is an
automated test system, developed by Linaro)
https://www.linaro.org/engineering/projects/lava/

I plan to maintain it within the debian python modules team.

There is a question about which version to package:
The last released version is 0.10.2.post0 which needs:

**Python**: 2.7 or 3.3+
**Django**: 1.8, 1.9, 1.10, 1.11
**DRF**: 3.5, 3.6

Debian testing has Python 3.6 (unstable 3.7), Django 1.11 and DRF 3.8.
That DRF 3.8 would appear to be a problem.

There is also a v1.0.0.dev0 of djangorestframework-filters which is not 
released yet, but is tagged,
so we could presumably upload that (I've packaged that as well). That
needs:

**Python**: 3.4, 3.5, 3.6
**Django**: 1.11, 2.0, 2.1b1
**DRF**: 3.8
**django-filter**: 2.0

Which fixes the DRF issue, by only v1.1.0 of django-filter is in debian 
unstable/testing.

Anyone know what the best thing to do here is? 

Bug#914657: Acknowledgement (stdout is flodded with debug messages)

[Michael Biebl]

Control: retitle -1 missing snmp.conf triggers flood of error messages
Control: severity -1 serious

I wanted to further investigate, if this was a libsane problem or not so
I installed another libsnmp30 client and for that I chose the "snmp"
package.
And suddenly all the errors were gone.

As soon as /etc/snmp/snmp.conf was available, all errors were gone.
It seems like either libsnmp3 should gracefully deal with
/etc/snmp/snmp.conf being missing or ensure that /etc/snmp/snmp.conf is
always installed (e.g. by moving it into the libsnmp-base package).

Regards,
Michael

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



signature.asc
Description: OpenPGP digital signature

Bug#914658: ITP: authheaders -- Python library for the generation of email authentication headers

[Scott Kitterman]

Package: wnpp
Severity: wishlist
Owner: Scott Kitterman 

* Package name: authheaders
  Version : 0.10.0
  Upstream Author : Valimail Inc 
* URL : https://github.com/ValiMail/authentication-headers
* License : BSD like, ZPL 2.1, MPL 2.0
  Programming Lang: Python
  Description : Python library for the generation of email authentication 
headers

 Authheaders can generate both authentication results header fields and DKIM/
 ARC sighatures.  It can perform DKIM, SPF, and DMARC validation, and the
 results are packaged into a single Authentication-Results header.  It can
 also DKIM and ARC sign messages and output the corresponding signature
 headers fields.

It supports both python2.7 and python3 (tested with python3.6 and 3.7).

I intend to maintail it within the Debian Python Modules Team.

I am packaging this as a dependency for another project I expect to upload
relatively shortly.

Bug#914657: stdout is flodded with debug messages

[Michael Biebl]

Package: libsnmp30
Version: 5.7.3+dfsg-4+b1
Severity: important


Hi,

when I start an application like gscan2pdf or colord, I get flodded with
the following messages on stdout:

MIB search path: 
/home/michael/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp
Cannot find module (SNMPv2-MIB): At line 1 in (none)
Cannot find module (IF-MIB): At line 1 in (none)
Cannot find module (IP-MIB): At line 1 in (none)
Cannot find module (TCP-MIB): At line 1 in (none)
Cannot find module (UDP-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-MIB): At line 1 in (none)
Cannot find module (NOTIFICATION-LOG-MIB): At line 1 in (none)
Cannot find module (DISMAN-EVENT-MIB): At line 1 in (none)
Cannot find module (DISMAN-SCHEDULE-MIB): At line 1 in (none)
Cannot find module (HOST-RESOURCES-TYPES): At line 1 in (none)
Cannot find module (MTA-MIB): At line 1 in (none)
Cannot find module (NETWORK-SERVICES-MIB): At line 1 in (none)
Cannot find module (SNMPv2-TC): At line 15 in 
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-SMI): At line 34 in 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Cannot find module (SNMPv2-TC): At line 37 in 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Did not find 'TruthValue' in module #-1 (/usr/share/snmp/mibs/UCD-SNMP-MIB.txt)
Unlinked OID in UCD-SNMP-MIB: ucdavis ::= { enterprises 2021 }
Undefined identifier: enterprises near line 39 of 
/usr/share/snmp/mibs/UCD-SNMP-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt)
Unlinked OID in UCD-DISKIO-MIB: ucdDiskIOMIB ::= { ucdExperimental 15 }
Undefined identifier: ucdExperimental near line 19 of 
/usr/share/snmp/mibs/UCD-DISKIO-MIB.txt
Cannot find module (SNMPv2-TC): At line 10 in 
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt)
Unlinked OID in UCD-DLMOD-MIB: ucdDlmodMIB ::= { ucdExperimental 14 }
Undefined identifier: ucdExperimental near line 13 of 
/usr/share/snmp/mibs/UCD-DLMOD-MIB.txt
Cannot find module (SNMPv2-TC): At line 15 in 
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Did not find 'ucdExperimental' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/LM-SENSORS-MIB.txt)
Unlinked OID in LM-SENSORS-MIB: lmSensors ::= { ucdExperimental 16 }
Undefined identifier: ucdExperimental near line 32 of 
/usr/share/snmp/mibs/LM-SENSORS-MIB.txt
Did not find 'ucdavis' in module UCD-SNMP-MIB 
(/usr/share/snmp/mibs/UCD-DEMO-MIB.txt)
Unlinked OID in UCD-DEMO-MIB: ucdDemoMIB ::= { ucdavis 14 }
Undefined identifier: ucdavis near line 7 of 
/usr/share/snmp/mibs/UCD-DEMO-MIB.txt
Cannot find module (SNMP-TARGET-MIB): At line 1 in (none)
Cannot find module (SNMP-FRAMEWORK-MIB): At line 9 in 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Cannot find module (SNMPv2-SMI): At line 8 in 
/usr/share/snmp/mibs/NET-SNMP-MIB.txt
Did not find 'enterprises' in module #-1 (/usr/share/snmp/mibs/NET-SNMP-MIB.txt)
Unlinked OID in NET-SNMP-MIB: netSnmp ::= { enterprises 8072 }
Undefined identifier: enterprises near line 10 of 
/usr/share/snmp/mibs/NET-SNMP-MIB.txt
Cannot find module (SNMPv2-TC): At line 21 in 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Did not find 'SnmpAdminString' in module #-1 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpObjects' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpModuleIDs' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpNotifications' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'netSnmpGroups' in module NET-SNMP-MIB 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'DisplayString' in module #-1 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'RowStatus' in module #-1 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Did not find 'TruthValue' in module #-1 
(/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt)
Unlinked OID in NET-SNMP-AGENT-MIB: nsAgentNotifyGroup ::= { netSnmpGroups 9 }
Undefined identifier: netSnmpGroups near line 545 of 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Unlinked OID in NET-SNMP-AGENT-MIB: nsTransactionGroup ::= { netSnmpGroups 8 }
Undefined identifier: netSnmpGroups near line 536 of 
/usr/share/snmp/mibs/NET-SNMP-AGENT-MIB.txt
Unlinked OID in NET-SNMP-AGENT-MIB: nsConfigGroups ::= { netSnmpGroups 7 }
Undefined identifier: netSnmpGroups near line 515 of 
/usr/share/s

Bug#914656: libvirt: Failed to install KVM virtual machine

[linwenkai]

Source: libvirt
Severity: normal

Dear Maintainer,

  When I run virt-install to install 'kvm', it shows
  `ERROR Host does not support domain type kvm for virtualization type'.
  Here is a transcript:

  root@debian:~# virt-install --name=debian_01 --vcpus=2
  --memory=4096 --cdrom /var/lib/libvirt/images/boot.iso --disk
  /home/dingyu/debian_01.qcow2 --virt-type kvm
  ERROR Host does not support domain type kvm for virtualization
  type 'hvm' arch 'alpha'
  root@debian:~# virt-install --name=debian_02 --vcpus=2
  --memory=4096 --cdrom /var/lib/libvirt/images/boot.iso --disk
  /home/dingyu/debian_01.qcow2 
  ERROR Error: --disk /home/dingyu/debian_01.qcow2: internal
  error: Cannot find suitable emulator for aarch64


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

Kernel: Linux 4.18.0-6-arm64 (SMP w/96 CPU cores)
Locale: LANG=en_HK.UTF-8, LC_CTYPE=en_HK.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_HK:en (charmap=locale: Cannot set LC_ALL to default locale: 
No such file or directory
UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#914655: python-scipy: _flapack undefined symbol: ilaver_

[ryan]

Package: python-scipy
Version: 0.18.1-2
Severity: normal

Dear Maintainer,

This is from an application that uses scipy.

$ python2.7
Python 2.7.13 (default, Sep 26 2018, 18:42:22)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from scipy.linalg import _flapack
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/__init__.py", line 174, 
in 
from .misc import *
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/misc.py", line 6, in 

from .lapack import get_lapack_funcs
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/lapack.py", line 374, in 

from scipy.linalg import _flapack
ImportError: 
/usr/lib/python2.7/dist-packages/scipy/linalg/_flapack.x86_64-linux-gnu.so: 
undefined symbol: ilaver_
>>>



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

Kernel: Linux 4.4.155 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages python-scipy depends on:
ii  lapack3 [liblapack.so.3]  3.0.2531a-6
ii  libatlas3-base [liblapack.so.3]   3.10.3-1+b1
ii  libblas3 [libblas.so.3]   3.7.0-2
ii  libc6 2.24-11+deb9u3
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgfortran3  6.3.0-18+deb9u1
ii  liblapack3 [liblapack.so.3]   3.7.0-2
ii  libquadmath0  6.3.0-18+deb9u1
ii  libstdc++66.3.0-18+deb9u1
ii  python2.7.13-2
ii  python-decorator  4.0.11-1
ii  python-numpy [python-numpy-abi9]  1:1.12.1-3
ii  refblas3 [libblas.so.3]   1.2-8

Versions of packages python-scipy recommends:
ii  clang-3.8 [c++-compiler]  1:3.8.1-24
ii  g++ [c++-compiler]4:6.3.0-4
ii  g++-4.4 [c++-compiler]4.4.7-2
ii  g++-4.9 [c++-compiler]4.9.2-10+deb8u1
ii  g++-6 [c++-compiler]  6.3.0-18+deb9u1
ii  python-dev2.7.13-2
ii  python-imaging4.0.0-4

Versions of packages python-scipy suggests:
pn  python-scipy-doc  

-- debconf-show failed

Bug#914654: "/etc/apt/sources.list", ask the user to choose between the distribution name and status

[21naown]

Package: debian-installer
Severity: wishlist
Tags: d-i


To complete the file "/etc/apt/sources.list", it would be very 
appreciable to ask the user to choose between the distribution name 
("stretch" for example) and status ("stable" for example).


I think the distribution status should be the default choice.


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

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE= (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#913816: dpkg-dev: dpkg_vendor_derives_from documentation produces wrong results

[Jeremy Bicha]

Yes, I would appreciate a less cumbersome  way of checking the build
vendor than what we have now.

One package that makes fairly extensive use of dpkg-vendor is gnome-software:

https://salsa.debian.org/gnome-team/gnome-software/blob/debian/master/debian/rules#L45

Thanks,
Jeremy Bicha

Bug#914652: nautilus: takes many seconds to start; becomes irresponsive on search

[Leandro Doctors]

Package: nautilus
Version: 3.30.3-1
Severity: important

Dear Maintainer,

   * What led up to the situation?

Starting the program. Or performing a search once the program has
loaded.

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

I tried to execute the program. I tried to perform a search using the
address bar.

   * What was the outcome of this action?

The program takes many seconds to load (5-10). Sometimes, it does not
load at all. When trying to search, sometimes it becomes irresponsive.

   * What outcome did you expect instead?

The program should start instantly. The search results should start
appearing after a short delay (1-2 seconds).



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

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

Versions of packages nautilus depends on:
ii  bubblewrap 0.3.1-2
ii  desktop-file-utils 0.23-4
ii  gsettings-desktop-schemas  3.28.1-1
ii  gvfs   1.38.1-1
ii  libatk1.0-02.30.0-1
ii  libc6  2.27-8
ii  libcairo-gobject2  1.16.0-1
ii  libcairo2  1.16.0-1
ii  libgdk-pixbuf2.0-0 2.38.0+dfsg-6
ii  libgexiv2-20.10.8-1
ii  libglib2.0-0   2.58.1-2
ii  libglib2.0-data2.58.1-2
ii  libgnome-autoar-0-00.2.3-1
ii  libgtk-3-0 3.24.1-2
ii  libnautilus-extension1a3.30.3-1
ii  libpango-1.0-0 1.42.4-4
ii  libpangocairo-1.0-01.42.4-4
ii  libseccomp22.3.3-3
ii  libselinux12.8-1+b1
ii  libtracker-sparql-2.0-02.1.6-1
ii  nautilus-data  3.30.3-1
ii  shared-mime-info   1.10-1
ii  tracker2.1.6-1

Versions of packages nautilus recommends:
ii  gnome-sushi  3.30.0-1
ii  gvfs-backends1.38.1-1
ii  librsvg2-common  2.44.9-1

Versions of packages nautilus suggests:
ii  eog 3.28.4-1
ii  evince [pdf-viewer] 3.30.2-1
ii  nautilus-extension-brasero  3.12.2-4
ii  nautilus-sendto 3.8.6-2
ii  totem   3.26.2-1
ii  vlc [mp3-decoder]   3.0.4-3+b3
ii  xdg-user-dirs   0.17-1

-- no debconf information

Bug#908843: terminology: Please add support for WINDOWID environment variable

[Ross Vandegrift]

Control: forwarded -1 https://phab.enlightenment.org/T7484

On Sat, Sep 15, 2018 at 12:30:09AM +0200, Sebastian Reichel wrote:
> Package: terminology
> Version: 1.2.1-1
> Severity: wishlist
> Tags: upstream
> 
> Hi,
> 
> Please add support for setting the WINDOWID environment variable,
> which is done for example by Xterm and most libvte terminal emulators.
> It's a very useful feature to automatically set a nice icon with
> xseticon based on the running application.
> 
> -- Sebastian
> 
> 

Bug#914651: perl: -i option broken

[Igor Liferenko]

Package: perl
Version: 5.28.0-3
Severity: important

Dear Maintainer,

The following command yields "a":

( echo a ; echo b ; echo c ) | perl -pe 'last if /b/'

The following command yields "abc" (one character on a line):

( echo a ; echo b ; echo c ) >/tmp/x; perl -i -pe 'last if /b/' /tmp/x; cat 
/tmp/x


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

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

Versions of packages perl depends on:
ii  dpkg   1.19.0.5+b1
ii  libperl5.285.28.0-3
ii  perl-base  5.28.0-3
ii  perl-modules-5.28  5.28.0-3

Versions of packages perl recommends:
ii  netbase  5.4

Versions of packages perl suggests:
pn  libb-debug-perl 
pn  liblocale-codes-perl
pn  libterm-readline-gnu-perl | libterm-readline-perl-perl  
ii  make4.2.1-1.1
ii  perl-doc5.28.0-3

-- no debconf information

Bug#874051:

[S. Christian Collins]

According to the Red Hat bug report for their Swami package, the Swami 
segfault is caused by an invalid pointer cast (with GPOINTER_TO_INT) on 
64-bit systems. Link here: 
https://bugzilla.redhat.com/show_bug.cgi?id=1541394#c2

Bug#914619: "LibreOffice Still" should be used by the stable distribution

[21naown]

Hello,

On Sun, 25 Nov 2018 20:19:54 +0100 Rene Engelhard  wrote:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820350
I am sorry I did not search enough for the existence of such a bug.
Also I did not search enough for information about the usefulness of the 
backported packages.


Regards.

Bug#881333: Qt with GLES on arm64 maintainer's decision - Was:: Upcoming Qt switch to OpenGL ES on arm64

[Paul Wise]

On Sun, Nov 25, 2018 at 8:58 PM Lisandro Damián Nicanor Pérez Meyer wrote:

> Both Dmitry and I just learned that the RPI has the VC4 driver which enables
> it to do hardware acceleration for Desktop OpenGL, we must admit that this is
> a game changer in many ways, even if we are talking on just one board (but
> quite an ubiquitous one).

I expect this also applies to any driver in (or soon to be in) mesa,
including freedreno (Qualcomm), panfrost (Mali), lima (Mali), Etnaviv
(Vivante), Tegra etc. Drivers only supporting GLES seems to be a
something that happens only with the proprietary drivers. I don't have
any ARM devices with GPUs to be able to test this though.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#900777: fontmake: fails to rebuild fonts-firacode from its glyphs source

[James Godfrey-Kittle]

Hm, I'm unable to reproduce this error with fontmake 1.6.1 and the
latest version of FiraCode from https://github.com/tonsky/FiraCode. My
output:

$ fontmake -g FiraCode.glyphs
INFO:fontmake.font_project:Building master UFOs and designspace from
Glyphs source
INFO:glyphsLib.classes:Parsing "FiraCode.glyphs" file into 
INFO:fontmake.font_project:Building OTF for FiraCode-Bold
INFO:ufo2ft:Pre-processing glyphs
INFO:ufo2ft.filters:Running DecomposeComponentsFilter on FiraCode-Bold
INFO:ufo2ft.filters:Running RemoveOverlapsFilter on FiraCode-Bold
INFO:ufo2ft:Building OpenType tables
INFO:ufo2ft.outlineCompiler:The copyright was normalized for storage
in the CFF table and consequently some characters were dropped:
'Copyright Copyright 2015 by Nikita Prokopov'
INFO:fontmake.font_project:Saving master_otf/FiraCode-Bold.otf
INFO:fontmake.font_project:Building OTF for FiraCode-Regular
INFO:ufo2ft:Pre-processing glyphs
INFO:ufo2ft.filters:Running DecomposeComponentsFilter on FiraCode-Regular
INFO:ufo2ft.filters:Running RemoveOverlapsFilter on FiraCode-Regular
INFO:ufo2ft:Building OpenType tables
INFO:ufo2ft.outlineCompiler:The copyright was normalized for storage
in the CFF table and consequently some characters were dropped:
'Copyright Copyright 2015 by Nikita Prokopov'
INFO:fontmake.font_project:Saving master_otf/FiraCode-Regular.otf
INFO:fontmake.font_project:Building TTF for FiraCode-Bold
INFO:ufo2ft:Pre-processing glyphs
INFO:ufo2ft.filters:Running DecomposeComponentsFilter on FiraCode-Bold
INFO:ufo2ft.filters:Running RemoveOverlapsFilter on FiraCode-Bold
INFO:ufo2ft.filters:Running CubicToQuadraticFilter on FiraCode-Bold
INFO:ufo2ft.filters.cubicToQuadratic:New spline lengths: 1: 266, 2:
2368, 3: 740, 4: 188, 5: 23
INFO:ufo2ft:Building OpenType tables
INFO:fontmake.font_project:Saving master_ttf/FiraCode-Bold.ttf
INFO:fontmake.font_project:Building TTF for FiraCode-Regular
INFO:ufo2ft:Pre-processing glyphs
INFO:ufo2ft.filters:Running DecomposeComponentsFilter on FiraCode-Regular
INFO:ufo2ft.filters:Running RemoveOverlapsFilter on FiraCode-Regular
INFO:ufo2ft.filters:Running CubicToQuadraticFilter on FiraCode-Regular
INFO:ufo2ft.filters.cubicToQuadratic:New spline lengths: 1: 257, 2:
2313, 3: 783, 4: 208, 5: 25
INFO:ufo2ft:Building OpenType tables
INFO:fontmake.font_project:Saving master_ttf/FiraCode-Regular.ttf

Am I running fontmake with different arguments?

Bug#914650: RFS: python-cassandra-driver/3.16.0-1 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-cassandra-driver"

* Package name: python-cassandra-driver
  Version : 3.16.0-1
  Upstream Author : DataStax 
* URL : https://github.com/datastax/python-driver
* License : Apache License 2.0
  Section : python

It builds those binary packages:

  python-cassandra - Python driver for Apache Cassandra
  python-cassandra-dbg - Python driver for Apache Cassandra (debug)
  python3-cassandra - Python driver for Apache Cassandra (Python 3)
  python3-cassandra-dbg - Python driver for Apache Cassandra (Python 3
debug)

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

  https://mentors.debian.net/package/python-cassandra-driver


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

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-cassandra-driver/python-cassandra-driver_3.16.0-1.dsc

More information about python-cassandra-driver can be obtained from
https://github.com/datastax/python-driver

Changes since the last upload:

  [ Ondřej Nový ]
  * Convert git repository from git-dpm to gbp layout

  [ Emmanuel Arias ]
  * New upstream release
  * Add DPMT to Maintainer field on d/control
  * Add myself to Uploaders field on d/control
  * Closes: #888400
  * Update Standards Version from 4.1.4 to 4.2.1
  * Update Copyright of d/* files
  * Update d/compat from 10 to 11
  * FIx problems on d/copyright

Regards,
Emmanuel Arias


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#914649: libvigraimpex: FTBFS against boost1.67: undefined reference to symbol 'pthread_condattr_setclock@@GLIBC_2.4'

[Gilles Filippini]

Source: libvigraimpex
Version: 1.10.0+git20160211.167be93+dfsg-6
Severity: serious
Tags: patch ftbfs
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

libvigraimpex FTBFS against boost1.67 on armel [1]:

[ 19%] Linking CXX executable test_blockwisewatersheds
cd 
/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg/obj/test/blockwisealgorithms
 && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/test_blockwisewatersheds.dir/link.txt --verbose=1
/usr/bin/c++  -W -Wall -Wextra -Wno-unused-parameter -Wno-sign-compare 
-Wno-unused-variable -Wno-type-limits -g -O2 
-fdebug-prefix-map=/<>/libvigraimpex-1.10.0+git20160211.167be93+dfsg=.
 -fstack-protector-strong -Wformat -Werror=format-security -pipe -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++11  -rdynamic 
CMakeFiles/test_blockwisewatersheds.dir/test_watersheds.cxx.o 
CMakeFiles/test_blockwisewatersheds.dir/testsuccess.cxx.o  -o 
test_blockwisewatersheds -lboost_thread -lboost_system -lboost_date_time 
-lboost_chrono 
/usr/bin/ld: CMakeFiles/test_blockwisewatersheds.dir/test_watersheds.cxx.o: 
undefined reference to symbol 'pthread_condattr_setclock@@GLIBC_2.4'
/usr/bin/ld: //lib/arm-linux-gnueabi/libpthread.so.0: error adding symbols: DSO 
missing from command line
collect2: error: ld returned 1 exit status

[1] 
https://buildd.debian.org/status/fetch.php?pkg=libvigraimpex&arch=armel&ver=1.10.0%2Bgit20160211.167be93%2Bdfsg-6%2Bb2&stamp=1542723257&raw=0

Not sure about the Good Way of solving this, but the attached patch is 
successful as a workaround (tested on armel and amd64).

Thanks,

_g.

- -- System Information:
Debian Release: buster/sid
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-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

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoJObzArDE05WtIyR7+hsbH/+z4MFAlv7H6QACgkQ7+hsbH/+
z4O6EQf/XBfegp9DOLxippoKKUv0XBuUI89BY3GwMbH5hYJBB1kCSaSE4t0gJxqs
dPel3rXn+O3uQVtNjzKNFYEfjU5cq2mT2vT5lSxPkUroA/XXhwZa+UTxYW76Mphr
J7FzfZAp+/d0tKW0Y1gzp1D6w5F7mNA9vw+SyhAUe0QTlNOEFZmAKsg73gc34pWe
x3n8sK8KWHlfo7HsFYmvq2CbIHbCZ/4FJ1k07GjRMCzTqQL5dT6itRbeXA/ly+Co
KYGx3NJYvioRRHkoGm/FKzrgWP7PhofKTgwMVZ6UQq4wTjjpjltUU72I52+Gfnb3
zjpEO/8tROT9uSJAFTEBVpsLT6Qzkg==
=Lpjx
-END PGP SIGNATURE-
diff -Nru libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog
--- libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog  
2018-08-11 06:20:04.0 +0200
+++ libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/changelog  
2018-11-25 20:43:26.0 +0100
@@ -1,3 +1,10 @@
+libvigraimpex (1.10.0+git20160211.167be93+dfsg-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * New patch link-with-pthread.patch to fix FTBFS against boost1.67 on armel
+
+ -- Gilles Filippini   Sun, 25 Nov 2018 20:43:26 +0100
+
 libvigraimpex (1.10.0+git20160211.167be93+dfsg-6) unstable; urgency=medium
 
   * add multi_convolution_fix_incomplete_template_paramater.patch
diff -Nru 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
--- 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
1970-01-01 01:00:00.0 +0100
+++ 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/link-with-pthread.patch
2018-11-25 20:43:26.0 +0100
@@ -0,0 +1,13 @@
+Index: 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/config/VigraConfigureThreading.cmake
+===
+--- 
libvigraimpex-1.10.0+git20160211.167be93+dfsg.orig/config/VigraConfigureThreading.cmake
 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/config/VigraConfigureThreading.cmake
+@@ -9,7 +9,7 @@ macro(VIGRA_CONFIGURE_THREADING)
+ set(THREADING_FOUND 1)
+ if(THREADING_IMPLEMENTATION MATCHES "boost")
+ include_directories(${Boost_INCLUDE_DIR})
+-set(THREADING_LIBRARIES ${Boost_THREAD_LIBRARY} 
${Boost_SYSTEM_LIBRARY} ${Boost_DATE_TIME_LIBRARY} ${Boost_CHRONO_LIBRARY})
++set(THREADING_LIBRARIES ${Boost_THREAD_LIBRARY} 
${Boost_SYSTEM_LIBRARY} ${Boost_DATE_TIME_LIBRARY} ${Boost_CHRONO_LIBRARY} 
pthread)
+ elseif(THREADING_IMPLEMENTATION MATCHES "std")
+ # Great, we can use the std library.  Nothing to do here...
+ elseif(THREADING_IMPLEMENTATION MATCHES "none")
diff -Nru libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series 
libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series
--- libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series 
2018-08-11 06:18:32.0 +0200
+++ libvigraimpex-1.10.0+git20160211.167be93+dfsg/debian/patches/series 
2018-11-25 20:43:26.00

Bug#914648: tracker store restart loops

[Daniel Leidert]

Source: tracker
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

The tracker-store service keeps restarting. It fills my logs with:

[..]
Nov 25 23:47:18 beeblebrox systemd[1475]: Stopped Tracker metadata database 
store and lookup manager.
Nov 25 23:47:18 beeblebrox systemd[1475]: Starting Tracker metadata database 
store and lookup manager...
Nov 25 23:47:18 beeblebrox systemd[1475]: Started Tracker metadata database 
store and lookup manager.
Nov 25 23:47:20 beeblebrox tracker-store[27951]: Cannot initialize database: 
error in view fts_view: no such table: 
main.nie:InformationElement_nie:keyword_TEMP (strerror of errno (not 
necessarily related): Datei oder Verzeichnis nicht gefunden)
Nov 25 23:47:21 beeblebrox systemd[1475]: tracker-store.service: Main process 
exited, code=exited, status=1/FAILURE
Nov 25 23:47:21 beeblebrox systemd[1475]: tracker-store.service: Failed with 
result 'exit-code'.
Nov 25 23:47:21 beeblebrox systemd[1475]: tracker-store.service: Service 
RestartSec=100ms expired, scheduling restart.
Nov 25 23:47:21 beeblebrox systemd[1475]: tracker-store.service: Scheduled 
restart job, restart counter is at 3020.
Nov 25 23:47:21 beeblebrox systemd[1475]: Stopped Tracker metadata database 
store and lookup manager.
Nov 25 23:47:21 beeblebrox systemd[1475]: Starting Tracker metadata database 
store and lookup manager...
Nov 25 23:47:21 beeblebrox systemd[1475]: Started Tracker metadata database 
store and lookup manager.
[..]

It might be related to this:
https://gitlab.gnome.org/GNOME/tracker/issues/40

Unfortunately it seems, I cannot easily remove this piece of software without
removing other software parts too. So please take a look and don't hesitate
to ask, if you need more information.

Regards, Daniel


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

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

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAlv7J7MACgkQS80FZ8KW
0F0v7Q//R0ZVp3/XGFMQwNOJWxBXM/3z15gTw95U5XAXVFm1rWH2TJIuNnIWHVIv
x4KZjRxLFTxmXfegYDF2z3yayQOJnFKjqOzLatYDHEXYe66suOpFK+bJSDCPr3Am
W2RU4jUgCzIFtNKYGYy6rkm6gSEVvy3kEw2LSOHQ+fHtlMflrHD8rCYvFi8+V0mf
HKLvTp6cOcAlNMI8/6R0gV0Ju8xLiNNElq1F9J9GmwbM+5/jGRBuTwRTna/6rpIf
ae0jq+gQ9Hg7hZhi9R9ujtepwMm9IMReXtiASM8U4WC8qKwWXyXecFJXWxIGmiu6
i7+LTPlmGUV9Y53vnCwBQe1WOrTPtXIb63Q34MVD1GRpmp3AkwaFx0SzGO9JKZ+l
ppjli7dbM5lf6b2ltop6PuCblHN9hznQyN9Ehvet4CnBGqQ9hJCPqJjqyg1vTMwd
SgdwkAu38OxbDWG7x0dvifNmkM25REv9PG4VB+ANxDbTsSI9Gycczl9rOaQm47Fw
6qWwYNJTeST3id9g3W9dH7TN3sq8qtbfrEiwAX09tOA7Ixp0PBFiuLcPmDlSWFfO
2+EfR593cLQTg+lxJ+G+rSTkbo/z80aAKinO/g412dP5ph8RkQClUeqE0rLgP4HL
chdun9fnvzCik6+6s0QBa0YsJ+4avMd0haN/sJC8qZlqvdxGHt4=
=pG4o
-END PGP SIGNATURE-

Bug#912143: fixed upstream

[Daniel Pocock]

https://github.com/resiprocate/resiprocate/commit/9a3abc0118e40805dd93a9ab2e6852ea640a0f64


Need to add a macro (upstream) to support backport builds on Debian
systems running stretch / asio 1.10

Bug#550676: [Bash-completion-devel] Bug#550676: Bug#550676: please make bash-completion falling back to path completion if nothing else is found

[Gabriel F. T. Gomes]

On Sat, 19 Jul 2014 16:33:07 +0300 =?UTF-8?Q?Ville_Skytt=C3=A4?= 
 wrote:
> On Fri, Jul 18, 2014 at 10:14 PM, David Paleino  wrote:
> >
> > Just use Alt-/, which is the default bash shortcut for "complete on all 
> > files".
> 
> ...or try the COMP_FILEDIR_FALLBACK environment variable:
> http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=blob;f=doc/bash_completion.txt;h=c6e53d4;hb=HEAD#l33

Unless I did not understand how this variable works, I think it needs
an extra patch to work (at least in the unzip case reported above), as
reported in https://github.com/scop/bash-completion/pull/260

Cheers,
Gabriel

Bug#840580: apache2-bin: crashes when issuing a restart while mod_cgid is enabled

[Stefan Fritsch]

On Sunday, 25 November 2018 19:07:56 CET Bernhard Übelacker wrote:
> Dear Maintainer,
> tried to find out the actual location that the backtrace points to.
> 
> Unfortunately I could not make any clue out of the line
> containing /usr/sbin/apache2(+0x29e450).
> 
> But at least, I think, the line containing mod_mpm_prefork.so(+0x4c08)
> translates to function prefork_run in server/mpm/prefork/prefork.c.
> 
> As this is a rather big function, and looks like it is never left while
> the server runs, and there are no local arrays accessed, the stack
> canary may be overwritten by some function called from there.
> But the stack canary is just checked when prefork_run exits.
> 
> Kind regards,
> Bernhard

The  "bt full" gdb command is the important one. Please show its output as 
described in README.backtrace

Bug#914297: apache2: getrandom call blocks on first startup, systemd kills with timeout

[Stefan Fritsch]

How long is the timeout after which it is killed? What is the status of 
systemd-random-seed.service in that case? I don't see why it should take so 
long for the random number generator to initialize. But maybe apache2 needs to 
add a dependency.

Please provide the output of

journalctl -b UNIT=apache2.service + UNIT=systemd-random-seed.service + 
_TRANSPORT=kernel|grep -i -e apache -e random

when apache2 has failed to start.

Bug#890594: salsa script ready to review

[Raphael Hertzog]

On Sun, 25 Nov 2018, Xavier wrote:
> My last change produces this bug. Fixed now, I pushed a new .deb in the
> same place.

Next try with a package whose HEAD points to the wrong branch (upstream)
but that already has the desired target branch (debian/master)

$ salsa --conf-file +./salsa-pkg-security.conf update_safe radare2-cutter 
--verbose --debug
salsa info: Project radare2-cutter => pkg-security-team/radare2-cutter
salsa info: pkg-security-team/radare2-cutter id is 29721
radare2-cutter:
bad description: Packaging for cutter from radare project
Default branch is upstream
1 packages misconfigured, update them ? (Y/n)
salsa info: Project radare2-cutter => pkg-security-team/radare2-cutter
salsa info: Configuring radare2-cutter
salsa warn: Error POSTing 
https://salsa.debian.org/api/v4/projects/29721/repository/branches (HTTP 400): 
Bad Request {"message":"Branch already exists"} at 
/usr/share/perl5/Devscripts/Salsa/update_repo.pm line 51.

Now a well configured repository but I inversed SOURCE_BRANCH and DEST_BRANCH. 
The operation
seems to work:
$ salsa --conf-file +./salsa-pkg-security.conf update_safe acct --verbose 
--debug
salsa info: Project acct => pkg-security-team/acct
salsa info: pkg-security-team/acct id is 6641
acct:
Default branch is debian/master
1 packages misconfigured, update them ? (Y/n) 
salsa info: Project acct => pkg-security-team/acct
salsa info: Configuring acct
salsa warn: Deleting old email-on-push (redirected to 
dispa...@tracker.debian.org)
salsa info: Email-on-push hook added to project 6641 (recipients: 
dispa...@tracker.debian.org)
salsa warn: Deleting old tagpending (was 
https://webhook.salsa.debian.org/tagpending/acct)
salsa info: Tagpending hook added to project 6641
salsa info: Project 6641 updated

Now I put SOURCE_BRANCH and DEST_BRANCH to their desired value and the next run 
doesn't work:
$ salsa --conf-file +./salsa-pkg-security.conf update_safe acct --verbose 
--debug
salsa info: Project acct => pkg-security-team/acct
salsa info: pkg-security-team/acct id is 6641
acct:
Default branch is master
1 packages misconfigured, update them ? (Y/n) 
salsa info: Project acct => pkg-security-team/acct
salsa info: Configuring acct
salsa warn: Error POSTing 
https://salsa.debian.org/api/v4/projects/6641/repository/branches (HTTP 400): 
Bad Request {"message":"Branch already exists"} at 
/usr/share/perl5/Devscripts/Salsa/update_repo.pm line 51.

Maybe you should separate the "rename branch" operation from the "set HEAD to"
operation. Because we want to fix HEAD pointing to the wrong branch even when
there's nothing to rename. And it could be useful for example to rename all
"upstream" into "upstream/latest" for example (without changing HEAD).

SALSA_RENAME_BRANCH="upstream:upstream/latest master:debian/master"
SALSA_SET_HEAD="debian/master"

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#914500: lintian: False positive package-contains-documentation-outside-usr-share-doc for file readMesh_off.m

[Chris Lamb]

tags 914500 + pending
thanks

Thanks for the report. I've fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/e35d7381a9beee8665f2ed5184cda55dbf6dcefc

  data/files/documentation-file-regex | 3 ++-
  debian/changelog| 6 ++
  t/tests/files-package-contains-foo/debian/rules | 9 +
  t/tests/files-package-contains-foo/tags | 5 +
  4 files changed, 22 insertions(+), 1 deletion(-)


Regards,

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

Bug#914647: RFP: talisman -- By hooking into the pre-push hook provided by Git, Talisman validates the outgoing changeset for things that look suspicious - such as authorization tokens and private key

[Varac]

Package: wnpp
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: talisman
  Version : 0.3.3
  Upstream Author : Misc
* URL : https://thoughtworks.github.io/talisman/
* License : MIT
  Programming Lang: golang
  Description : By hooking into the pre-push hook provided by Git, Talisman 
validates the outgoing changeset for things that look suspicious - such as 
authorization tokens and private keys.

Talisman is a tool to validate code changes that are to be pushed out of a 
local Git repository on a developer's workstation. By hooking into the pre-push 
hook provided by Git, it validates the outgoing changeset for things that look 
suspicious - such as potential SSH keys, authorization tokens, private keys etc.

The aim is for this tool to do this through a variety of means including file 
names and file content. We hope to have it be an effective check to prevent 
potentially harmful security mistakes from happening due to secrets which get 
accidentally checked in to a repository.

The implementation as it stands is very bare bones and only has the skeleton 
structure required to add the full range of functionality we wish to 
incorporate. However, we encourage folks that want to contribute to have a look 
around and contribute ideas/suggestions or ideally, code that implements your 
ideas and suggestions!

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEESvqqiCmYrIkee91NVGXnfnh27QQFAlv7H/wQHHZhcmFjQHZh
cmFjLm5ldAAKCRBUZed+eHbtBH4OD/9GlGw+3o4auVsGuy47tekhAJMhS2cj1oAx
+iaFGJkNw7Zs4+iRxVcDTftbIdtOsyU8X60hVPLqePxAsDXypq16vdOV1fbpBJmH
J71DqlbXFbIuiWhBgFmRoUqy5bg74MyfQjilacbYhh5V/D/Hz6+ZUQdRC9KdtExO
ejZgfmUD9Z/OnxehHHU0ygyXWunBKmimZO2fQZ0TgtAffZMCgXmdiDTYDiB/7Bix
arbdUyV7VljiCaTyROn+DZv4y1HoWIECX54wlvE/Zw623vFUprYaNlyLz+LNwLLk
mZrPtdFs+1mqTawsr1OCTUygg4eP0P5PttAaG1WIYLTLzBJmcq7u/0lXJtFNHOoW
NtbBlhebJZzBl0CgD2nt/pbMJrDb+jN/Pp9yehoL5JwZIzfry2tdBWV8WKb0AdlF
3kVkBUIDOrfFXEUA/J/dBgTvQEX4cm3A4PQmcrJI83d//O6l7MBxUrzhcrZgXIPP
JHLdgB9kyOVVeAv1Kq0qhqdYbT67Vsq/ajikjCkoWsiQZszAykuRGJuM4Ez4qa/x
Lif/TtVivEiuVhP7hEeEogkSFlcxL7uvtzj6IXwagHxiZ3bBaQfZUkxf7PEwOUEj
CrzFsIIn+B2CQJGpjhXvX52bTUP58D9S0lJ9wNfvLVHFH8wyd1dDEWNE5P7LdtAY
RI6bwpUgng==
=wOGZ
-END PGP SIGNATURE-

Bug#914646: piuparts: failed-testing with no prpblem listed

[Adrian Bunk]

Package: piuparts
Version: 0.94
Severity: important
Control: affects -1 src:sslsplit sslsplit
Control: block 912052 by -1

https://piuparts.debian.org/sid/source/s/sslsplit.html
https://piuparts.debian.org/sid/fail/sslsplit_0.5.4-1.log

...
0m21.5s DEBUG: Starting command: ['umount', 
'/srv/piuparts.debian.org/tmp/tmpd4RZGU/dev/pts']
0m21.5s DEBUG: Command ok: ['umount', 
'/srv/piuparts.debian.org/tmp/tmpd4RZGU/dev/pts']
0m21.5s DEBUG: Starting command: ['umount', 
'/srv/piuparts.debian.org/tmp/tmpd4RZGU/proc']
0m21.5s DEBUG: Command ok: ['umount', 
'/srv/piuparts.debian.org/tmp/tmpd4RZGU/proc']
0m21.5s DEBUG: Starting command: ['rm', '-rf', '--one-file-system', 
'/srv/piuparts.debian.org/tmp/tmpd4RZGU']
0m21.7s DEBUG: Command ok: ['rm', '-rf', '--one-file-system', 
'/srv/piuparts.debian.org/tmp/tmpd4RZGU']
0m21.7s DEBUG: Removed directory tree at /srv/piuparts.debian.org/tmp/tmpd4RZGU
0m21.7s ERROR: piuparts run ends.

ret=1
End: 2018-11-25 13:49:58 UTC


There is nothing in the log indicating why this is failed-testing.

Bug#914500: lintian: False positive package-contains-documentation-outside-usr-share-doc for file readMesh_off.m

[Chris Lamb]

Control: found -1 2.5.92

Hi Rafael,

> Package: lintian
> Version:
> Severity: normal

Whoops ;)


Regards,

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

Bug#914633: r-cran-readr breaks autopkgtests: librcon.so can't be found

[Dirk Eddelbuettel]

Ok -- I just put a pretty rough "cowboy" patch in which

 - alters src/Makevars to not require the extra shared library
 
 - moves the dozen of so lines of actual C code from src/rcon/
   into a file in src/ to have in the same C library

See 
https://salsa.debian.org/edd/r-cran-readr/commit/1d010ed32525fb2bebaf84e7bff7aae70927438f

That builds and loads. Let's see what the autopkgtests say; it will give us
some breathing time while upstream can figure out if this really needs to be
a shared library.  Static may work too and is simpler, including the code as
I did even more so.  There may be other goals I am unaware of.

Dirk

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

Bug#890594: salsa script ready to review

[Xavier]

Le 25/11/2018 à 22:39, Xavier a écrit :
> On Sun, 25 Nov 2018, Raphael Hertzog wrote:
>> On Thu, 22 Nov 2018, Xavier wrote:
>>> Last .deb contains the SALSA_RENAME_HEAD. Could you test it ?
>>
>> I wanted to do some test but something else broke:
>>
>> $ salsa --conf-file +./salsa-pkg-security.conf update_safe sandsifter 
>> --verbose --debug
>> salsa info: Project sandsifter => pkg-security-team/sandsifter
>> salsa info: pkg-security-team/sandsifter id is 30154
>> sandsifter:
>>  bad description: x86 processor fuzzer
>> 1 packages misconfigured, update them ? (Y/n)
>> salsa info: Project sandsifter => pkg-security-team/sandsifter
>> salsa info: Configuring sandsifter
>> salsa warn: The #1 argument ($project_id) to project must be a scalar at 
>> /usr/share/perl5/Devscripts/Salsa/update_repo.pm line 49.
> 
> Here is the fix, I'm building a new .deb:
> 
> diff --git a/lib/Devscripts/Salsa/update_repo.pm
> b/lib/Devscripts/Salsa/update_repo.pm
> index 316baec9..3d637a72 100644
> --- a/lib/Devscripts/Salsa/update_repo.pm
> +++ b/lib/Devscripts/Salsa/update_repo.pm
> @@ -46,7 +46,7 @@ sub _update_repo {
>  my $project;
>  # 1 - creates new branch if --rename-head
>  if ($self->config->rename_head) {
> -my $project = $self->api->project($_[0]);
> +my $project = $self->api->project($_->[0]);
>  if ($project->{default_branch} ne
> $self->config->dest_branch) {
>  $self->api->create_branch(
>  $id,
> @@ -57,7 +57,7 @@ sub _update_repo {
>  $configparams->{default_branch}
>= $self->config->dest_branch;
>  } else {
> -ds_verbose "Head already renamed for $_[1]";
> +ds_verbose "Head already renamed for $_->[1]";
>  $project = undef;
>  }
>  }

My last change produces this bug. Fixed now, I pushed a new .deb in the
same place.
Thanks for this report!

Bug#914633: r-cran-readr breaks autopkgtests: librcon.so can't be found

[Dirk Eddelbuettel]

On 25 November 2018 at 21:59, Paul Gevers wrote:
| Hi Dirk,
| 
| On 25-11-18 21:42, Dirk Eddelbuettel wrote:
| > The new version of readr relies on rpath to encode a path. We are caught
| > between a rock and hard place:  as shipped (and built my yesterday), the
| > package "builds" but does not longer autotest you saw here.
| 
| I have difficulty parsing what you mean here. I guess you mean
| r-cran-readr doesn't have an autopkgtest by itself anymore?

No I said you may want to consider turning the autotest off by choice while
the upstream code remains broken (in the "simultaneously requiring two
different rpath settings" sense).
 
| > Not quite sure what we can do -- maybe for once suspend autotests on this 
one?
| 
| Are you talking about the build-time tests? Because aren't the
| autopkgtests of r-cran-alakazam and r-cran-tidyverse saying that the
| current package of r-cran-readr in unstable is broken?

Of course.  And that is what you reported to me, the maintainer of r-cran-readr.

And I am trying to explain to you, and failing, that this is a bad upstream
choice I have limited influence over which caused this.

Dirk

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

Bug#890594: salsa script ready to review

[Xavier]

Le 25/11/2018 à 22:37, Raphael Hertzog a écrit :
> On Sun, 25 Nov 2018, Raphael Hertzog wrote:
>> On Thu, 22 Nov 2018, Xavier wrote:
>>> Last .deb contains the SALSA_RENAME_HEAD. Could you test it ?
>>
>> I wanted to do some test but something else broke:
>>
>> $ salsa --conf-file +./salsa-pkg-security.conf update_safe sandsifter 
>> --verbose --debug
>> salsa info: Project sandsifter => pkg-security-team/sandsifter
>> salsa info: pkg-security-team/sandsifter id is 30154
>> sandsifter:
>>  bad description: x86 processor fuzzer
>> 1 packages misconfigured, update them ? (Y/n)
>> salsa info: Project sandsifter => pkg-security-team/sandsifter
>> salsa info: Configuring sandsifter
>> salsa warn: The #1 argument ($project_id) to project must be a scalar at 
>> /usr/share/perl5/Devscripts/Salsa/update_repo.pm line 49.
> 
> Forgot to show my file:
> $ cat salsa-pkg-security.conf 
> SALSA_GROUP=pkg-security-team
> #SALSA_GROUP_ID=2586
> 
> # Skip the pkg-security-team project (containing this file)
> SALSA_SKIP=pkg-security-team
> 
> SALSA_DESC_PATTERN="%p packaging"
> SALSA_DESC=yes
> 
> SALSA_EMAIL=yes
> SALSA_EMAIL_RECIPIENTS=dispa...@tracker.debian.org
> 
> SALSA_IRKER=yes
> SALSA_IRKER_HOST=ruprecht.snow-crash.org
> SALSA_IRC_CHANNEL=debian-pkg-security
> 
> SALSA_TAGPENDING=yes
> 
> SALSA_SOURCE_BRANCH=master
> SALSA_DEST_BRANCH=debian/master
> SALSA_RENAME_HEAD=yes
> 
> SALSA_ENABLE_MR=yes
> SALSA_DISABLE_ISSUES=yes
> 
> Cheers,
> 

Here is the fix, I'm building a new .deb:

diff --git a/lib/Devscripts/Salsa/update_repo.pm
b/lib/Devscripts/Salsa/update_repo.pm
index 316baec9..3d637a72 100644
--- a/lib/Devscripts/Salsa/update_repo.pm
+++ b/lib/Devscripts/Salsa/update_repo.pm
@@ -46,7 +46,7 @@ sub _update_repo {
 my $project;
 # 1 - creates new branch if --rename-head
 if ($self->config->rename_head) {
-my $project = $self->api->project($_[0]);
+my $project = $self->api->project($_->[0]);
 if ($project->{default_branch} ne
$self->config->dest_branch) {
 $self->api->create_branch(
 $id,
@@ -57,7 +57,7 @@ sub _update_repo {
 $configparams->{default_branch}
   = $self->config->dest_branch;
 } else {
-ds_verbose "Head already renamed for $_[1]";
+ds_verbose "Head already renamed for $_->[1]";
 $project = undef;
 }
 }

Bug#890594: salsa script ready to review

[Raphael Hertzog]

On Sun, 25 Nov 2018, Raphael Hertzog wrote:
> On Thu, 22 Nov 2018, Xavier wrote:
> > Last .deb contains the SALSA_RENAME_HEAD. Could you test it ?
> 
> I wanted to do some test but something else broke:
> 
> $ salsa --conf-file +./salsa-pkg-security.conf update_safe sandsifter 
> --verbose --debug
> salsa info: Project sandsifter => pkg-security-team/sandsifter
> salsa info: pkg-security-team/sandsifter id is 30154
> sandsifter:
>   bad description: x86 processor fuzzer
> 1 packages misconfigured, update them ? (Y/n)
> salsa info: Project sandsifter => pkg-security-team/sandsifter
> salsa info: Configuring sandsifter
> salsa warn: The #1 argument ($project_id) to project must be a scalar at 
> /usr/share/perl5/Devscripts/Salsa/update_repo.pm line 49.

Forgot to show my file:
$ cat salsa-pkg-security.conf 
SALSA_GROUP=pkg-security-team
#SALSA_GROUP_ID=2586

# Skip the pkg-security-team project (containing this file)
SALSA_SKIP=pkg-security-team

SALSA_DESC_PATTERN="%p packaging"
SALSA_DESC=yes

SALSA_EMAIL=yes
SALSA_EMAIL_RECIPIENTS=dispa...@tracker.debian.org

SALSA_IRKER=yes
SALSA_IRKER_HOST=ruprecht.snow-crash.org
SALSA_IRC_CHANNEL=debian-pkg-security

SALSA_TAGPENDING=yes

SALSA_SOURCE_BRANCH=master
SALSA_DEST_BRANCH=debian/master
SALSA_RENAME_HEAD=yes

SALSA_ENABLE_MR=yes
SALSA_DISABLE_ISSUES=yes

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#890594: salsa script ready to review

[Raphael Hertzog]

On Thu, 22 Nov 2018, Xavier wrote:
> Last .deb contains the SALSA_RENAME_HEAD. Could you test it ?

I wanted to do some test but something else broke:

$ salsa --conf-file +./salsa-pkg-security.conf update_safe sandsifter --verbose 
--debug
salsa info: Project sandsifter => pkg-security-team/sandsifter
salsa info: pkg-security-team/sandsifter id is 30154
sandsifter:
bad description: x86 processor fuzzer
1 packages misconfigured, update them ? (Y/n)
salsa info: Project sandsifter => pkg-security-team/sandsifter
salsa info: Configuring sandsifter
salsa warn: The #1 argument ($project_id) to project must be a scalar at 
/usr/share/perl5/Devscripts/Salsa/update_repo.pm line 49.

On Fri, 23 Nov 2018, Xavier wrote:
> One important thing: I set ruprecht.snow-crash.org as default value for
> --irker-host. Is it a good idea ? Is this server secured [1] ?
> 
> [1]: http://www.catb.org/~esr/irker/security.html

I don't know. But this server is maintained by a salsa admin so I guess it's 
fine and
he probably restricted it so that only salsa can talk to it (if not he can
likely easily do it).

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#914564: dh_makefont: invalid choice: 'reateorig'

[Craig Small]

On Sun, 25 Nov. 2018, 10:27 Adam Borowski 

Hi Adam,
 For some reason dh_makefont calls dh_make with -createorig instead of
double dashed --createorig. I had to tighten up the command line parsing in
dh_make for some other bugs which is why it's happening now.

A simple edit on line 296 and it should be fine. I'll make an update soon.

 - Craig

Bug#550676: make bash-completion falling back to path completion if nothing else is found

[Gabriel F. T. Gomes]

Control: fixed -1 bash-completion/1:1.3-1

On Wed, 03 Feb 2010 08:44:24 +0900 Norbert Preining  wrote:
> 
> My usual reminder ... since I am in kernel-build mood ATM I am again
> hit by that
>   make -f debian/rules KDIR=/usr/src/li
> nothing nothing nothing.

Since the upstream commit

commit f7240b82a4d45f03b741f11b771fae17d3c1c713
Author: Ville Skyttä 
Date:   Fri May 11 23:28:57 2012 +0300

make: Add generic variable completion.

this bug is fixed, although it was not marked as fixed when downstream
version 1:1.3-1 was uploaded.

I'm setting the fixed version to this bug report, then I'll close it.

> As far as I remember that was one of the reasons I removed bash
> completion from my system.

If you haven't yet done so, I suggest you try it again and I hope it
works better for you, now.

Cheers,
Gabriel

Bug#473379:

[Jakob Unterwurzacher]

Still happens in Jessie.

Bug#907256: mkdocs: Remaining work items for version 1.0.x in unstable

[Dmitry Shachnev]

Hi Jonas!

On Sat, Nov 24, 2018 at 11:13:11PM +0100, Jonas Smedegaard wrote:
> lunr has now been packaged: Bug#914555.

Thanks a lot for packaging it! That is going to resolve a large part
of this bug.

Just in case, are you also going to package lunr-languages [1]?

[1]: https://www.npmjs.com/package/lunr-languages

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#914395: dirmngr log

[Craig Small]

It seems it needs the SRV record and fails wrong without it.
Checking on the same system looking up that SRV record I get the
expected NXDOMAIN error.

$ host -t srv _pgpkey-http._tcp.keyring.debian.org
Host _pgpkey-http._tcp.keyring.debian.org not found: 3(NXDOMAIN)

dirmngr log file:

2018-11-26 08:16:13 dirmngr[15805.0] certificate 
'/etc/ssl/certs/ca-certificates.crt' already cached
2018-11-26 08:16:13 dirmngr[15805.0] permanently loaded certificates: 136
2018-11-26 08:16:13 dirmngr[15805.0] runtime cached certificates: 0
2018-11-26 08:16:13 dirmngr[15805.0]trusted certificates: 136 
(135,0,0,1)
2018-11-26 08:16:13 dirmngr[15805.6] handler for fd 6 started
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> # Home: /home/csmall/.gnupg
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> # Config: 
/home/csmall/.gnupg/dirmngr.conf
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> OK Dirmngr 2.2.11 at your 
service
2018-11-26 08:16:13 dirmngr[15805.6] connection from process 15804 (1000:1000)
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 <- GETINFO version
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> D 2.2.11
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> OK
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 <- KEYSERVER --clear 
hkp://keyring.debian.org
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> OK
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 <- KS_GET -- 0xDF50FEA5
2018-11-26 08:16:13 dirmngr[15805.6] DBG: dns: libdns initialized
2018-11-26 08:16:13 dirmngr[15805.6] DBG: dns: 
getsrv(_pgpkey-http._tcp.keyring.debian.org): No route to host
2018-11-26 08:16:13 dirmngr[15805.6] command 'KS_GET' failed: No route to host
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> ERR 167804970 No route to 
host 
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 <- BYE
2018-11-26 08:16:13 dirmngr[15805.6] DBG: chan_6 -> OK closing connection
2018-11-26 08:16:13 dirmngr[15805.6] handler for fd 6 terminated
-- 
Craig Small   https://dropbear.xyz/ csmall at : enc.com.au
Debian GNU/Linux  https://www.debian.org/   csmall at : debian.org
Mastodon: @smalls...@social.dropbear.xyz   Twitter: @smallsees  
GPG fingerprint:5D2F B320 B825 D939 04D2  0519 3938 F96B DF50 FEA5

Bug#879188: Likely caused by running as nobody

[Marcel Veldhuizen]

I'm experiencing the same error running a combination of spamassassin 
and pyzor. I turned on debug logging for spamd (-D option) to get a 
little more information.


The issue appears to be that pyzor is running as "nobody" (which is a 
good thing, imo) and it is trying to create a .pyzor configuration file 
in a directory that doesn't exist.


Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response 
"Traceback (most recent call last):"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response " 
File "/usr/bin/pyzor", line 408, in "
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response " 
main()"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response " 
File "/usr/bin/pyzor", line 131, in main"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response " 
config, options, args = load_configuration()"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response " 
File "/usr/bin/pyzor", line 107, in load_configuration"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response " 
os.mkdir(options.homedir)"
Nov 25 21:21:35 server spamd[26523]: pyzor: failure to parse response 
"FileNotFoundError: [Errno 2] No such file or directory: 
'/nonexistent/.pyzor'"


The user nobody has /nonexistent/ as its home directory.

I haven't yet found a way to specify the --homedir parameter in 
spamassassin configuration, which could potentially work around this 
problem. Still, it would be good if the default pyzor behavior wouldn't 
make it fail when running as nobody.


spamassassin 3.4.2-1
pyzor 1:1.0.0.0-3

Bug#914645: zita-at1 FTBFS: freetype-config not found

[Helmut Grohne]

Source: zita-at1
Version: 0.6.0-1
Severity: serious
Tags: ftbfs

zita-at1 fails to build from source, because freetype-config cannot be
found. freetype-config was removed from Debian and one is supposed to
use pkg-config now.

Helmut

Bug#914644: libicns FTCBFS: debian/rules uses the wrong pkg-config

[Helmut Grohne]

Source: libicns
Version: 0.8.1-3.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libicns fails to cross build from source, because debian/rules (not the
build system) uses the wrong pkg-config. The attached patch fixes that
and makes libicns cross build successfully. Please consider applying it.

Helmut
diff --minimal -Nru libicns-0.8.1/debian/changelog 
libicns-0.8.1/debian/changelog
--- libicns-0.8.1/debian/changelog  2016-11-12 05:12:44.0 +0100
+++ libicns-0.8.1/debian/changelog  2018-11-25 22:01:14.0 +0100
@@ -1,3 +1,10 @@
+libicns (0.8.1-3.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Use the host pkg-config. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 25 Nov 2018 22:01:14 +0100
+
 libicns (0.8.1-3.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru libicns-0.8.1/debian/rules libicns-0.8.1/debian/rules
--- libicns-0.8.1/debian/rules  2016-11-12 05:12:44.0 +0100
+++ libicns-0.8.1/debian/rules  2018-11-25 22:01:13.0 +0100
@@ -1,8 +1,11 @@
 #!/usr/bin/make -f
 
 #export DH_VERBOSE=1
+/usr/share/dpkg/buildtools.mk:
+-include /usr/share/dpkg/buildtools.mk
+PKG_CONFIG ?= pkg-config
 
-export CPPFLAGS += $(shell pkg-config --cflags libopenjp2)
+export CPPFLAGS += $(shell $(PKG_CONFIG) --cflags libopenjp2)
 %:
dh $@ --parallel --with autoreconf
 

Bug#914633: r-cran-readr breaks autopkgtests: librcon.so can't be found

[Paul Gevers]

Hi Dirk,

On 25-11-18 21:42, Dirk Eddelbuettel wrote:
> The new version of readr relies on rpath to encode a path. We are caught
> between a rock and hard place:  as shipped (and built my yesterday), the
> package "builds" but does not longer autotest you saw here.

I have difficulty parsing what you mean here. I guess you mean
r-cran-readr doesn't have an autopkgtest by itself anymore?

> Not quite sure what we can do -- maybe for once suspend autotests on this one?

Are you talking about the build-time tests? Because aren't the
autopkgtests of r-cran-alakazam and r-cran-tidyverse saying that the
current package of r-cran-readr in unstable is broken?

Paul



signature.asc
Description: OpenPGP digital signature

Bug#911985: libvoikko FTBFS with hfst-ospell 0.5.0

[John Paul Adrian Glaubitz]

Package: src:libvoikko
Followup-For: Bug #911985

Hi!

I just uploaded an updated version (4.2) of libvoikko to
DELAYED/7 which fixes this bug.

Please let me know whether this acceptable or not. If not, I
will remove the upload from the queue again, of course.

I have taken action in this case because this particular package
keeps back a lot of KDE packages in the Debian Ports architectures
like riscv64.

Thanks,
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#914643: tika: CVE-2018-8017

[Salvatore Bonaccorso]

Source: tika
Version: 1.5-5
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for tika.

CVE-2018-8017[0]:
| In Apache Tika 1.2 to 1.18, a carefully crafted file can trigger an
| infinite loop in the IptcAnpaParser.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-8017
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8017

Regards,
Salvatore

Bug#914642: netsniff-ng FTCBFS: builds for the wrong architecture

[Helmut Grohne]

Source: netsniff-ng
Version: 0.6.5-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

netsniff-ng fails to cross build from source, because nothing tells its
./configure which architecture we are building for and thus it just
builds for the build architecture. We cannot use dh_auto_configure,
because netsniff-ng's ./configure is very much unlike autotools. Rather
one is supposed to stuff the host architecture into a variable called
CROSS_COMPILE. The attached patch implements that and makes netsniff-ng
cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru netsniff-ng-0.6.5/debian/changelog 
netsniff-ng-0.6.5/debian/changelog
--- netsniff-ng-0.6.5/debian/changelog  2018-09-20 15:06:14.0 +0200
+++ netsniff-ng-0.6.5/debian/changelog  2018-11-25 21:47:27.0 +0100
@@ -1,3 +1,10 @@
+netsniff-ng (0.6.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Tell ./configure about the host architecture. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 25 Nov 2018 21:47:27 +0100
+
 netsniff-ng (0.6.5-1) unstable; urgency=low
 
   * New upstream release.
diff --minimal -Nru netsniff-ng-0.6.5/debian/rules 
netsniff-ng-0.6.5/debian/rules
--- netsniff-ng-0.6.5/debian/rules  2018-09-20 15:01:55.0 +0200
+++ netsniff-ng-0.6.5/debian/rules  2018-11-25 21:47:27.0 +0100
@@ -5,7 +5,9 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 DPKG_EXPORT_BUILDFLAGS = 1
+include /usr/share/dpkg/architecture.mk
 include /usr/share/dpkg/buildflags.mk
+export CROSS_COMPILE=$(DEB_HOST_GNU_TYPE)-
 
 CFLAGS+=$(CPPFLAGS)
 CXXFLAGS+=$(CPPFLAGS)

Bug#914641: faad2: CVE-2018-19502 CVE-2018-19503 CVE-2018-19504

[Salvatore Bonaccorso]

Source: faad2
Version: 2.8.8-1
Severity: important
Tags: security upstream
Forwarded: https://sourceforge.net/p/faac/bugs/240/

Hi,

The following vulnerabilities were published for faad2.

CVE-2018-19502[0]:
| An issue was discovered in Freeware Advanced Audio Decoder 2 (FAAD2)
| 2.8.1. There was a heap-based buffer overflow in the function
| excluded_channels() in libfaad/syntax.c.

CVE-2018-19503[1]:
| An issue was discovered in Freeware Advanced Audio Decoder 2 (FAAD2)
| 2.8.1. There was a stack-based buffer overflow in the function
| calculate_gain() in libfaad/sbr_hfadj.c.

CVE-2018-19504[2]:
| An issue was discovered in Freeware Advanced Audio Decoder 2 (FAAD2)
| 2.8.1. There is a NULL pointer dereference in ifilter_bank() in
| libfaad/filtbank.c.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-19502
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19502
[1] https://security-tracker.debian.org/tracker/CVE-2018-19503
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19503
[2] https://security-tracker.debian.org/tracker/CVE-2018-19504
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19504

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#914640: supercollider FTBFS on amd64/i386 with boost 1.67

[Adrian Bunk]

Source: supercollider
Version: 1:3.8.0~repack-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=supercollider&suite=sid

...
In file included from 
/<>/server/supernova/sc/../server/synth.hpp:29,
 from /<>/server/supernova/sc/sc_synth.hpp:31,
 from 
/<>/server/supernova/sc/sc_synth_definition.cpp:25:
/<>/server/supernova/./utilities/time_tag.hpp: In member function 
'boost::posix_time::ptime nova::time_tag::to_ptime() const':
/<>/server/supernova/./utilities/time_tag.hpp:233:102: error: no 
matching function for call to 
'boost::date_time::subsecond_duration::subsecond_duration(double)'
 time_duration offset = seconds(get_secs() - ntp_offset) + 
microseconds(get_nanoseconds()/1000);

  ^
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_config.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/posix_time_system.hpp:13,
 from /usr/include/boost/date_time/posix_time/ptime.hpp:12,
 from 
/usr/include/boost/date_time/posix_time/posix_time_types.hpp:12,
 from /usr/include/boost/thread/thread_time.hpp:11,
 from /usr/include/boost/thread/lock_types.hpp:18,
 from /usr/include/boost/thread/pthread/mutex.hpp:16,
 from /usr/include/boost/thread/mutex.hpp:16,
 from /usr/include/boost/thread/pthread/shared_mutex.hpp:14,
 from /usr/include/boost/thread/shared_mutex.hpp:28,
 from 
/<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:27,
 from 
/<>/server/supernova/./utilities/named_hash_entry.hpp:27,
 from /<>/server/supernova/sc/sc_synthdef.hpp:30,
 from 
/<>/server/supernova/sc/sc_synth_definition.hpp:24,
 from /<>/server/supernova/sc/sc_synth.hpp:29,
 from 
/<>/server/supernova/sc/sc_synth_definition.cpp:25:
/usr/include/boost/date_time/time_duration.hpp:285:14: note: candidate: 
'template boost::date_time::subsecond_duration::subsecond_duration(const T&, typename 
boost::enable_if, void>::type*)'
 explicit subsecond_duration(T const& ss,
  ^~
/usr/include/boost/date_time/time_duration.hpp:285:14: note:   template 
argument deduction/substitution failed:
/usr/include/boost/date_time/time_duration.hpp: In substitution of 
'template 
boost::date_time::subsecond_duration::subsecond_duration(const T&, typename 
boost::enable_if, void>::type*) [with T = double]':
/<>/server/supernova/./utilities/time_tag.hpp:233:102:   required 
from here
/usr/include/boost/date_time/time_duration.hpp:285:14: error: no type named 
'type' in 'struct boost::enable_if, void>'
In file included from 
/usr/include/boost/date_time/posix_time/posix_time_config.hpp:16,
 from 
/usr/include/boost/date_time/posix_time/posix_time_system.hpp:13,
 from /usr/include/boost/date_time/posix_time/ptime.hpp:12,
 from 
/usr/include/boost/date_time/posix_time/posix_time_types.hpp:12,
 from /usr/include/boost/thread/thread_time.hpp:11,
 from /usr/include/boost/thread/lock_types.hpp:18,
 from /usr/include/boost/thread/pthread/mutex.hpp:16,
 from /usr/include/boost/thread/mutex.hpp:16,
 from /usr/include/boost/thread/pthread/shared_mutex.hpp:14,
 from /usr/include/boost/thread/shared_mutex.hpp:28,
 from 
/<>/external_libraries/nova-tt/nova-tt/rw_mutex.hpp:27,
 from 
/<>/server/supernova/./utilities/named_hash_entry.hpp:27,
 from /<>/server/supernova/sc/sc_synthdef.hpp:30,
 from 
/<>/server/supernova/sc/sc_synth_definition.hpp:24,
 from /<>/server/supernova/sc/sc_synth.hpp:29,
 from 
/<>/server/supernova/sc/sc_synth_definition.cpp:25:
/usr/include/boost/date_time/time_duration.hpp:270:30: note: candidate: 
'boost::date_time::subsecond_duration::subsecond_duration(const 
boost::date_time::subsecond_duration&)'
   class BOOST_SYMBOL_VISIBLE subsecond_duration : public base_duration
  ^~
/usr/include/boost/date_time/time_duration.hpp:270:30: note:   no known 
conversion for argument 1 from 'double' to 'const 
boost::date_time::subsecond_duration&'
/usr/include/boost/date_time/time_duration.hpp:270:30: note: candidate: 
'boost::date_time::subsecond_duration::subsecond_duration(boost::date_time::subsecond_duration&&)'
/usr/include/boost/date_time/time_duration.hpp:270:30: note:   no known 
conversion for argument 1 from 'double' to 
'boost::date_time::subsecond_duration&&'
make[3]: *** [server/supernova/CMakeFiles/libsupernova.dir/build.make:66: 
server/supernova/CMakeFiles/libsupernova.dir/sc/sc_synth_definition.cpp.o] 
Error 1

Bug#914639: gpsshogi FTBFS with boost 1.67

[Adrian Bunk]

Source: gpsshogi
Version: 0.7.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=gpsshogi&suite=sid

...
/usr/bin/ld: gpsusi.o: in function `makePlayer(osl::Player, osl::SimpleState 
const&, std::ostream&)':
./bin/gpsusi.cc:1412: undefined reference to 
`osl::search::UsiMonitor::setUdpLogging(std::__cxx11::basic_string, std::allocator >&, 
boost::asio::basic_datagram_socket*, 
boost::asio::ip::basic_endpoint*)'
collect2: error: ld returned 1 exit status
make[1]: *** [: gpsusi] Error 1

Bug#914638: ambdec FTBFS: freetype-config not found

[Helmut Grohne]

Source: ambdec
Version: 0.5.1-5
Severity: serious
Tags: ftbfs

ambdec fails to build from source, because it uses freetype-config,
which got removed from Debian. Please use pkg-config instead.

Helmut

Bug#914637: jwm FTCBFS: uses the wrong pkg-config

[Helmut Grohne]

Source: jwm
Version: 2.3.7-2
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

jwm fails to cross build from source, because it uses the wrong
pkg-config. The attached patch fixes that and makes jwm cross buildable.
Please consider applying it.

Helmut
--- jwm-2.3.7.orig/configure.ac
+++ jwm-2.3.7/configure.ac
@@ -93,17 +93,7 @@
 # Check for pkg-config.
 
 
-AC_DEFUN([JWM_PKGCONFIG_EXISTS],
-[
-   AC_MSG_CHECKING([for pkg-config])
-   if which pkg-config >/dev/null ; then
-  PKGCONFIG=pkg-config
-  AC_MSG_RESULT($PKGCONFIG)
-   else
-  PKGCONFIG=""
-  AC_MSG_RESULT([no])
-   fi
-])
+AC_DEFUN([JWM_PKGCONFIG_EXISTS],[AC_PATH_TOOL(PKGCONFIG,pkg-config)])
 
 AC_DEFUN([JWM_PKGCONFIG],
 [

Bug#914634: Sorry for the noise

[Josua Mayer]

Hi there again,

I might have noticed what is going wrong on my side :( I did some evil
dependency mangling about libegl1.
So please close this report!

best regards
Josua Mayer

Bug#914636: stringencoder FTFBS: CC_FOR_BUILD turns out to be empty

[Helmut Grohne]

Source: stringencoders
Version: 3.10.3+git20180306-1
Severity: serious
Tags: ftbfs

stringencoders fails to build from source on the buildds (e.g.
https://buildd.debian.org/status/fetch.php?pkg=stringencoders&arch=arm64&ver=3.10.3%2Bgit20180306-1&stamp=1542718062&raw=0).
It seems that the variable CC_FOR_BUILD turns out to be empty. I guess
that the AC_ARG_VAR overrides the previous value and thus makes the
native build fail.

Helmut

Bug#896698: deprecating needs-recommends

[Paul Gevers]

Control: tags -1 - wontfix

Hi all,

On 18-09-18 21:17, Antonio Terceiro wrote:
> On Tue, Sep 18, 2018 at 08:53:05PM +0200, Paul Gevers wrote:
>> On 18-09-18 17:21, gregor herrmann wrote:
>>> On Mon, 17 Sep 2018 15:11:30 -0700, Antonio Terceiro wrote:
 Maybe we want autopkgtest to also support @recommends@ alongside
 @builddeps@?
>>>
>>> From a user's point of view, that sounds ok to me.
>>> Updating a few bits of documentation and a handful of packages with
>>> manual d/t/control shouldn't be a problem.
>>
>> On the one hand, I wonder what that is going to help. This is just
>> changing semantics as it still means that autopkgtest needs to figure it
>> out. The current situation is going to waste peoples time debugging why
>> a test is a regression, just to find out that every tool is silent on
>> not installing the recommends. On the other hand, it is a clearer
>> statement and it means that we can explain and document what we really
>> mean with it.
>>
>> @recommends@ or needs-recommends should mean that direct recommends of
>> the binary packages from the package that provides the autopkgtest are
>> test dependencies. Implementation wise, this would mean that we would
>> add all recommends, whether the binary that recommends it is installed
>> or not.
>>
>> If the feature to have recommends in the test dependencies isn't going
>> away, how bad would it be if we change the behavior in a sustainable
>> way? In my endeavors to fix this bug, I have missed the option to just
>> add the sum of all the Recommends lines to the test dependencies, like
>> we do with @builddeps@. What do people think?
> 
> That would work as well, with the benefit that it would require changing
> only autopkgtest and nothing else. And I think that adding the packages
> in Recommends to test dependencies is compatible with the original
> spirit of needs-recommends, which is "this test needs the recommended
> packages installed", but does it in a way that actually works.

dpkg is going to add all the test dependencies except ones own packages
to the Testsuite-Triggers field [1]. That means that @recommends@ would
enable britney2 to also be aware of this, so I actually like that route
for that reason.

For the record, I currently am of the opinion that we should fix this
bug and move to a new declaration: @recommends@ in the test dependencies.

Paul

[1] https://bugs.debian.org/910734



signature.asc
Description: OpenPGP digital signature

Bug#911107: Acknowledgement (deluged sends port=0 via IPv6 announce instead of the correct port)

[Tiger!P]

Hello,

This bug has been fixed in the new upstream release 1.1.11 [1].

[1] https://github.com/arvidn/libtorrent/releases/tag/libtorrent_1_1_11

-- 
Tiger!P

Bug#914634: logs

[Josua Mayer]

Please find attached the log of installing the build environment, and
the log file from the failed fmtutil run.

fmtutil: fmtutil is using the following fmtutil.cnf files (in precedence order):
fmtutil:   /usr/share/texmf/web2c/fmtutil.cnf
fmtutil:   /usr/share/texlive/texmf-dist/web2c/fmtutil.cnf
fmtutil: fmtutil is using the following fmtutil.cnf file for writing changes:
fmtutil:   /etc/texmf/web2c/fmtutil.cnf
fmtutil [INFO]: writing formats under /var/lib/texmf/web2c
fmtutil [INFO]: --- remaking luatex with luatex
fmtutil: running `luatex -ini   -jobname=luatex -progname=luatex luatex.ini' ...
luatex: error while loading shared libraries: libEGL.so.1: cannot open shared 
object file: No such file or directory
fmtutil [INFO]: --- remaking pdftex with pdftex
fmtutil: running `pdftex -ini   -jobname=pdftex -progname=pdftex 
-translate-file=cp227.tcx *pdfetex.ini' ...
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) (INITEX)
 restricted \write18 enabled.
 (/usr/share/texlive/texmf-dist/web2c/cp227.tcx)
entering extended mode
(/usr/share/texlive/texmf-dist/tex/plain/config/pdfetex.ini
(/var/lib/texmf/tex/generic/config/pdftexconfig.tex)
(/usr/share/texlive/texmf-dist/tex/plain/etex/etex.src
(/usr/share/texlive/texmf-dist/tex/plain/base/plain.tex
Preloading the plain format: codes, registers, parameters, fonts, more fonts,
macros, math definitions, output routines, hyphenation
(/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex
[skipping from \patterns to end-of-file...]))
(/usr/share/texlive/texmf-dist/tex/plain/etex/etexdefs.lib
Skipping module "grouptypes"; Loading module "interactionmodes";
Skipping module "nodetypes"; Skipping module "iftypes";)
(/usr/share/texlive/texmf-dist/tex/generic/config/language.def
(/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex))
Augmenting the Plain TeX definitions: \tracingall;
Adding new e-TeX definitions: \eTeX, \loggingall, \tracingnone,
register allocation; extended register allocation; 
Recycling: \addlanguage, \@nswer (not defined), \@sk, \b@dresponsetrue,
\b@dresponsefalse, \ch@ckforyn, \mayber@cycle, \et@xabort, \et@xbuf,
\et@xfmtsrc, \et@xfilehdr, \et@xinf, \et@xpatterns, \l@ngdefnfile, \n@xt,
\p@rse (not defined), \pr@mpt (not defined), \pr@mptloop (not defined),
\forcer@cycle, \usef@llback, \usef@llbacktrue, \usef@llbackfalse, 
Retaining: \et@xerr, \et@xinput, \et@xlibhdr, \et@xmsg, \et@xtoks, \et@xwarn,
\et@xl@@d, \et@xl@ad, \et@xload, \et@xlang, \et@xhash, \eTeX, \etexhdrchk,
\etexstatus, \module, \uselanguage, \r@tain, \r@cycle,)
(/usr/share/texlive/texmf-dist/tex/plain/config/pdftexmagfix.tex) )
Beginning to dump on file pdftex.fmt
 (preloaded format=pdftex 2018.11.25)
2895 strings of total length 43145
7960 memory locations dumped; current usage is 203&7321
1263 multiletter control sequences
\font\nullfont=nullfont
\font\tenrm=cmr10
\font\preloaded=cmr9
\font\preloaded=cmr8
\font\sevenrm=cmr7
\font\preloaded=cmr6
\font\fiverm=cmr5
\font\teni=cmmi10
\font\preloaded=cmmi9
\font\preloaded=cmmi8
\font\seveni=cmmi7
\font\preloaded=cmmi6
\font\fivei=cmmi5
\font\tensy=cmsy10
\font\preloaded=cmsy9
\font\preloaded=cmsy8
\font\sevensy=cmsy7
\font\preloaded=cmsy6
\font\fivesy=cmsy5
\font\tenex=cmex10
\font\preloaded=cmss10
\font\preloaded=cmssq8
\font\preloaded=cmssi10
\font\preloaded=cmssqi8
\font\tenbf=cmbx10
\font\preloaded=cmbx9
\font\preloaded=cmbx8
\font\sevenbf=cmbx7
\font\preloaded=cmbx6
\font\fivebf=cmbx5
\font\tentt=cmtt10
\font\preloaded=cmtt9
\font\preloaded=cmtt8
\font\preloaded=cmsltt10
\font\tensl=cmsl10
\font\preloaded=cmsl9
\font\preloaded=cmsl8
\font\tenit=cmti10
\font\preloaded=cmti9
\font\preloaded=cmti8
\font\preloaded=cmti7
\font\preloaded=cmu10
\font\preloaded=cmmib10
\font\preloaded=cmbsy10
\font\preloaded=cmcsc10
\font\preloaded=cmssbx10
\font\preloaded=cmdunh10
\font\preloaded=cmr7 at 14.51799pt
\font\preloaded=cmtt10 at 14.4pt
\font\preloaded=cmssbx10 at 14.4pt
\font\preloaded=manfnt
14787 words of font info for 50 preloaded fonts
14 hyphenation exceptions
Hyphenation trie of length 6075 has 181 ops out of 35111
  181 for language 0
0 words of pdfTeX memory
0 indirect objects
No pages of output.
Transcript written on pdftex.log.
fmtutil [INFO]: /var/lib/texmf/web2c/pdftex/pdftex.fmt installed.
fmtutil [INFO]: --- remaking tex with tex
fmtutil: running `tex -ini   -jobname=tex -progname=tex tex.ini' ...
This is TeX, Version 3.14159265 (TeX Live 2016/Debian) (INITEX)
(/usr/share/texlive/texmf-dist/tex/plain/config/tex.ini
(/usr/share/texlive/texmf-dist/tex/plain/base/plain.tex
Preloading the plain format: codes, registers, parameters, fonts, more fonts,
macros, math definitions, output routines, hyphenation
(/usr/share/texlive/texmf-dist/tex/generic/hyphen/hyphen.tex)) )
Beginning to dump on file tex.fmt
 (preloaded format=tex 2018.11.25)
2027 strings of total length 29297
4990 memory locations dumped; current usage is 110&4877
926 multiletter control sequences
\font\nullfont=nullfont
\font\tenrm=cmr10

Bug#366899: Updating ancient bug #366899

[Gabriel F. T. Gomes]

Control: tags -1 unreproducible
Control: close -1

This message addresses (see below) all the topics that have been raised
in this bug report (except those related to _dpkg_source, which are
tracked by bug #503317).  Then, since all of the bugs are no longer
reproducible, this message marks this bug as unreproducible and closes
it.

If you have more information and would like to reopen this bug (or
open a new one), please do not hesitate to do so.

Thanks,
Gabriel


On Fri, 12 May 2006 01:11:18 +0200 Jonas Meyer
 wrote:
>
> if i type for example dpkg-source -i /u 
> and press tab it changes it to:
> dpkg-source -i -

This is no longer true with current bash-completion:

  $ dpkg-source -i /u[TAB][TAB][TAB][...]
  (no output)
  $ dpkg-source -i /u[CURSOR]


> and on the next tab this:
> -b   -c   -D   -E   -F   -i   -I   -l   -sa  -sA  -sk  -sK  -sn  -sp
> -sP -sr  -sR  -ss  -su  -sU  -T   -U   -V   -W   -x
> dpkg-source -x /u 
> completes to /usr but then adds an extra space.

Likewise:

  $ dpkg-source -x /usr[TAB]
  $ dpkg-source -x /usr/[CURSOR]


On Fri, 02 Mar 2007 18:04:20 +0100 Frank Küster  wrote:
>
> That the completion cannot properly handle absolute paths is not a
> problem for me.  However, the added space is:
> 
> dpkg-source -x tru TAB gives
> 
> 'dpkg-source -x trunk '
> 
> but of course what I want is 'dpkg-source -x trunk/'

Likewise:

  $ ls
  dir1  dir2  file1  file2

  $ dpkg-source -x di[TAB]
  dir1/ dir2/ 


On Sat, 17 May 2008 11:04:47 +0200 Frank Küster  wrote:
>
> David Paleino  wrote:
> 
> > What you're trying to do is using "/usr" (or "trunk") as output directories,
> > while dpkg-source (and its completion), "correctly" thinks they're Debian
> > Source Packages (and that's why it adds a space at the end -- "trunk " and 
> > not
> > "trunk/"; "/usr " and not "/usr/").
> 
> No, that's not what I'm trying to do. I'm trying to unpack a dsc that is
> in a different directory:
> 
> dpkg-source -x some/where/else/whatever.dsc
> 
> But that is hard to type, because I have to type
> 
> dpkg-so TAB -x so TAB BKSP /wh TAB BKSP /e TAB BKSP /wh TAB
> 
> instead of
> 
> dpkg-so TAB -x so TAB wh TAB e TAB wh TAB

Likewise:

  $ pwd
  /tmp/dpkg-source
  $ ls 
  dir1  dir2  file1  file2

  $ dpkg-source -x /t[TAB]
  $ dpkg-source -x /tmp/[CURSOR]
  $ dpkg-source -x /tmp/dpk[TAB]
  $ dpkg-source -x /tmp/dpkg-source/[CURSOR]
  $ dpkg-source -x /tmp/dpkg-source/[TAB][TAB]
  dir1/ dir2/ fake.dsc
  $ dpkg-source -x /tmp/dpkg-source/fa[TAB]
  $ dpkg-source -x /tmp/dpkg-source/fake.dsc [CURSOR]


On Mon, 28 Dec 2009 18:42:03 +0900 Norbert Preining  wrote:
> 
> yes, that is the case, yesterday we were discussing the problems of
> bash-completion, and immediately I stumbled into another problem,
> but already reported
>   dpkg-source -b --no-preparation ma
> changes to
>   dpkg-source -b --no-preparation -
> offering more options.

Likewise:

  $ dpkg-source -b di[TAB]
  $ dpkg-source -b dir[CURSOR]
  $ dpkg-source -b dir[TAB]
  dir1/ dir2/


All working as designed, imo.

Bug#914635: woo FTBFS with boost 1.67

[Adrian Bunk]

Source: woo
Version: 1.0+dfsg1-3
Severity: serious
Tags: ftbfs

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

...
In file included from build-src-tree/woo/lib/base/openmp-accu.hpp:5,
 from build-src-tree/woo/core/EnergyTracker.hpp:3,
 from build-src-tree/../core/EnergyTracker.cpp:1,
 from build-src-tree/src/chunk-91-EnergyTracker.cpp:1:
build-src-tree/woo/lib/base/Math.hpp:71:37: error: expected identifier before 
'!' token
  #define likely(x) __builtin_expect(!!(x),1)
 ^
build-src-tree/woo/lib/base/Math.hpp:71:37: error: expected ',' or '...' before 
'!' token
In file included from /usr/include/boost/date_time/format_date_parser.hpp:17,
 from /usr/include/boost/date_time/date_generator_parser.hpp:20,
 from /usr/include/boost/date_time/date_facet.hpp:25,
 from 
/usr/include/boost/date_time/gregorian/gregorian_io.hpp:16,
 from /usr/include/boost/date_time/gregorian/gregorian.hpp:31,
 from 
/usr/include/boost/date_time/posix_time/time_formatters.hpp:12,
 from /usr/include/boost/date_time/posix_time/posix_time.hpp:24,
 from build-src-tree/woo/core/Master.hpp:3,
 from build-src-tree/../core/EnergyTracker.cpp:2,
 from build-src-tree/src/chunk-91-EnergyTracker.cpp:1:
/usr/include/boost/date_time/special_values_parser.hpp: In static member 
function 'static bool boost::date_time::special_values_parser::__builtin_expect(int)':
/usr/include/boost/date_time/special_values_parser.hpp:107:18: error: 
overloaded function with no contextual type information
 if (!str.empty()) {
  ^
/usr/include/boost/date_time/special_values_parser.hpp:108:26: error: invalid 
types '[int]' for array subscript
 switch (str[0]) {
  ^
In file included from build-src-tree/woo/lib/base/openmp-accu.hpp:5,
 from build-src-tree/woo/core/EnergyTracker.hpp:3,
 from build-src-tree/../core/EnergyTracker.cpp:1,
 from build-src-tree/src/chunk-91-EnergyTracker.cpp:1:
/usr/include/boost/date_time/time_parsing.hpp: In function 'time_type 
boost::date_time::parse_iso_time(const string&, char)':
build-src-tree/woo/lib/base/Math.hpp:71:38: error: no match for 'operator!' 
(operand type is 'const string' {aka 'const std::__cxx11::basic_string'})
  #define likely(x) __builtin_expect(!!(x),1)
  ^~~~
build-src-tree/woo/lib/base/Math.hpp:71:38: note: candidate: 'operator!(bool)' 

build-src-tree/woo/lib/base/Math.hpp:71:38: note:   no known conversion for 
argument 1 from 'const string' {aka 'const std::__cxx11::basic_string'} 
to 'bool'
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: build-arch] Error 25


The Ubuntu diff seems to contain a fix.

Bug#914634: texlive-binaries: luatex requires libEGL

[Josua Mayer]

Package: texlive-binaries
Version: 2016.20160513.41080.dfsg-2+deb9u1
Severity: normal

Dear Maintainer,

While doing automated builds using the openbuildservice to rebuild quilt from 
stretch-backports,
I have encountered a failing maintainer script of tex-common.

Investigating the produced log-file shows that the luatex application attempts 
to load libEGL.so.1, and fails:
luatex: error while loading shared libraries: libEGL.so.1: cannot open shared 
object file: No such file or directory

Sure enough in the produced build-root nothing has pulled in libegl1.
I suspect that the texlive-binaries package should have a dependency on libegl1.

I will attach the full logs to a reply.

Yours sincerely
Josua Mayer


-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armhf (armv7l)

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

Versions of packages texlive-binaries depends on:
ii  dpkg  1.18.25
ii  libc6 2.24-11+deb9u3
ii  libcairo2 1.14.8-1sr1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgcc1   1:6.3.0-18+deb9u1
ii  libgmp10  2:6.1.2+dfsg-1
ii  libgraphite2-31.3.10-1
ii  libgs99.25~dfsg-0+deb9u1
ii  libharfbuzz-icu0  1.4.2-1
ii  libharfbuzz0b 1.4.2-1
ii  libice6   2:1.0.9-2
ii  libicu57  57.1-6+deb9u2
ii  libkpathsea6  2016.20160513.41080.dfsg-2+deb9u1
ii  libmpfr4  3.1.5-1
ii  libpaper1 1.1.24+nmu5
ii  libpixman-1-0 0.34.0-1
ii  libpng16-16   1.6.28-1
ii  libpoppler64  0.48.0-2+deb9u2
ii  libpotrace0   1.13-3
ii  libptexenc1   2016.20160513.41080.dfsg-2+deb9u1
ii  libsm62:1.2.2-1+b3
ii  libstdc++66.3.0-18+deb9u1
ii  libsynctex1   2016.20160513.41080.dfsg-2+deb9u1
ii  libtexlua52   2016.20160513.41080.dfsg-2+deb9u1
ii  libtexluajit2 2016.20160513.41080.dfsg-2+deb9u1
ii  libx11-6  2:1.6.4-3+deb9u1
ii  libxaw7   2:1.0.13-1+b2
ii  libxext6  2:1.3.3-1+b2
ii  libxi62:1.7.9-1
ii  libxmu6   2:1.1.2-2
ii  libxpm4   1:3.5.12-1
ii  libxt61:1.1.5-1
ii  libzzip-0-13  0.13.62-3.1
ii  perl  5.24.1-3+deb9u4
ii  t1utils   1.39-2
ii  tex-common6.06
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages texlive-binaries recommends:
ii  python2.7.13-2
ii  ruby  1:2.3.3
ii  texlive-base  2016.20170123-5
ii  tk [wish] 8.6.0+9

texlive-binaries suggests no packages.

-- no debconf information

Bug#914632: uw-imap: CVE-2018-19518

[Salvatore Bonaccorso]

Source: uw-imap
Version: 8:2007f~dfsg-5
Severity: important
Tags: security upstream

Hi,

The following vulnerability was published for uw-imap.

CVE-2018-19518[0]:
| University of Washington IMAP Toolkit 2007f on UNIX, as used in
| imap_open() in PHP and other products, launches an rsh command (by
| means of the imap_rimap function in c-client/imap4r1.c and the
| tcp_aopen function in osdep/unix/tcp_unix.c) without preventing
| argument injection, which might allow remote attackers to execute
| arbitrary OS commands if the IMAP server name is untrusted input (e.g.,
| entered by a user of a web application) and if rsh has been replaced by
| a program with different argument semantics. For example, if rsh is a
| link to ssh (as seen on Debian and Ubuntu systems), then the attack can
| use an IMAP server name containing a "-oProxyCommand" argument.

This was originally filled for PHP (cf. #913775 and cloned bugs), but
the issue could possibly be fixed within osdep/unix/tcp_unix.c in the
IMAP Toolkit code. See the security-tracker page for further
references.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-19518
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19518

Regards,
Salvatore

Bug#914633: r-cran-readr breaks autopkgtests: librcon.so can't be found

[Paul Gevers]

Package: r-cran-readr
Version: 1.2.1-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Dear maintainers,

With a recent upload of r-cran-readr the autopkgtests of
r-cran-tidyverse and r-cran-alakazam fail in testing when that
autopkgtest is run with the binary packages of r-cran-readr from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
r-cran-readr   from testing1.2.1-1
r-cran-tidyverse   from testing1.2.1-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. From the error
message it seems that the librcon.so file is installed into the wrong
directory.

Currently this regression is contributing to the delay of the migration
of r-cran-readr to testing [1]. Can you please investigate the
situation? If needed, please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-readr

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-tidyverse/1376704/log.gz

> library('tidyverse')
Error: package or namespace load failed for ‘tidyverse’ in
dyn.load(file, DLLpath = DLLpath, ...):
 unable to load shared object '/usr/lib/R/site-library/readr/libs/readr.so':
  librcon.so: cannot open shared object file: No such file or directory
Execution halted
autopkgtest [04:17:23]: test command1: ---]



signature.asc
Description: OpenPGP digital signature

Bug#914631: nmu: mpb_1.5-3

[Adrian Bunk]

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

nmu mpb_1.5-3 . ANY . unstable . -m "Merged /usr considered harmful"

$ mpb-split
bash: /usr/bin/mpb-split: /usr/bin/bash: bad interpreter: No such file or 
directory
$

Bug#895456: Fw: Re: [Linux-ham] axlisten: colors for command line

[folkert]

Hi,

Maybe this patch can help?

It is against git://git.linux-ax25.org/pub/scm/ax25-apps.git


This patch below has the following features:
- colors in non-ncurses mode (-C)
- press 'q' to exit (-e to enable)

diff --git a/AUTHORS b/AUTHORS
index 7b91e72..d0d 100644
--- a/AUTHORS
+++ b/AUTHORS
@@ -17,6 +17,7 @@ Heikki Hannikainen OH7LZB 
 Alan Cox GW4PTS 
 Jean-Paul for rose decoding
 Jeroen Vreeken for INP decoding
+Folkert van Heusden 
 
 call:
 Alexander Tietzel DG6XA 
diff --git a/listen/listen.c b/listen/listen.c
index 6504ed5..fb80987 100644
--- a/listen/listen.c
+++ b/listen/listen.c
@@ -3,6 +3,8 @@
 #include 
 
 #include 
+#include 
+#include 
 #include 
 #include 
 #include 
@@ -202,9 +204,15 @@ int main(int argc, char **argv)
struct ifreq ifr;
int proto = ETH_P_AX25;
int exit_code = EXIT_SUCCESS;
+   char q_exit = 0;
+   struct pollfd fds[2];
+   struct termios oldtermios, newtermios;
 
-   while ((s = getopt(argc, argv, "8achip:rtv")) != -1) {
+   while ((s = getopt(argc, argv, "e8acChip:rtv")) != -1) {
switch (s) {
+   case 'e':
+   q_exit = 1;
+   break;
case '8':
sevenbit = 0;
break;
@@ -214,6 +222,9 @@ int main(int argc, char **argv)
case 'c':
color = 1;
break;
+   case 'C':
+   a_color = 1;
+   break;
case 'h':
dumpstyle = HEX;
break;
@@ -276,6 +287,17 @@ int main(int argc, char **argv)
return 1;
}
 
+   fds[0].fd = sock;
+   fds[0].events = POLLIN;
+
+   fds[1].fd = STDIN_FILENO;
+   fds[1].events = POLLIN;
+
+   tcgetattr(STDIN_FILENO, &oldtermios);
+   newtermios = oldtermios;
+
+   cfmakeraw(&newtermios);
+
if (color) {
color = initcolor();/* Initialize color support */
if (!color)
@@ -285,93 +307,120 @@ int main(int argc, char **argv)
setservent(1);
 
while (!sigint) {
+   int rc;
+
asize = sizeof(sa);
 
-   signal(SIGINT, handle_sigint);
-   signal(SIGTERM, handle_sigint);
-   size = recvfrom(sock, buffer, sizeof(buffer), 0, &sa, &asize);
-   if (size == -1) {
-   /*
-* Signals are cared for by the handler, and we
-* don't want to abort on SIGWINCH
-*/
-   if (errno == EINTR) {
-   refresh();
-   continue;
-   } else if (!(errno == EBADF && sigint)) {
-   perror("recv");
-   exit_code = errno;
-   }
+   tcsetattr(STDIN_FILENO, TCSANOW, &newtermios);
+   fds[0].events = fds[1].events = POLLIN;
+   fds[0].revents = fds[1].revents = 0;
+
+   rc = poll(fds, q_exit ? 2 : 1, -1);
+   if (rc == -1) {
+   perror("poll");
break;
}
-   gettimeofday(&t_recv, NULL);
-   signal(SIGINT, SIG_DFL);
-   signal(SIGTERM, SIG_DFL);
-   if (sock == -1 || sigint)
-   break;
 
-   if (dev != NULL && strcmp(dev, sa.sa_data) != 0)
+   if (rc == 0)
continue;
 
-   if (proto == ETH_P_ALL) {
-   strcpy(ifr.ifr_name, sa.sa_data);
+   if (q_exit && fds[1].revents == POLLIN) {
+   int c = getchar();
+   if (c == 'q' || c == 3)
+   break;
+   }
+
+   tcsetattr(STDIN_FILENO, TCSANOW, &oldtermios);
+
+   if (fds[0].revents == POLLIN) {
signal(SIGINT, handle_sigint);
signal(SIGTERM, handle_sigint);
-   if (ioctl(sock, SIOCGIFHWADDR, &ifr) == -1) {
-   if (!(errno == EBADF && sigint)) {
-   perror("SIOCGIFHWADDR");
+   size = recvfrom(sock, buffer, sizeof(buffer), 0, &sa, 
&asize);
+   if (size == -1) {
+   /*
+* Signals are cared for by the handler, and we
+* don't want to abort on SIGWINCH
+*/
+   if (errno == EINTR) {
+   refresh();
+   continue;
+   } else if (!(errno == EBADF && sigint)) {
+   

Bug#914630: ht FTCBFS: tools/bin2c: Exec format error

[Helmut Grohne]

Source: ht
Version: 2.1.0+repack1-3
Tags: patch upstream
User: helm...@debian.org
Usertags: rebootstrap

ht fails to cross build from source, because it fails running
tools/bin2hc. That file is a build tool and needs to be built with the
build architecture compiler rather than the host architecture one. The
attached patch implements that. Please consider applying it as it makes
ht cross buildable.

Helmut
--- ht-2.1.0+repack1.orig/configure.ac
+++ ht-2.1.0+repack1/configure.ac
@@ -100,6 +100,8 @@
 AC_PATH_PROGS(MAKE, gmake make, :)
 AC_PROG_MAKE_SET
 AC_PROG_CC
+AC_PATH_PROG(CC_FOR_BUILD,cc gcc)
+AC_SUBST(CC_FOR_BUILD)
 AC_PROG_CPP
 AC_PROG_CXX
 AC_PROG_YACC
--- ht-2.1.0+repack1.orig/tools/Makefile.am
+++ ht-2.1.0+repack1/tools/Makefile.am
@@ -8,3 +8,6 @@
 
 bin2c_LDADD =
 bin2c_SOURCES = bin2c.c
+
+bin2c:bin2c.c
+	$(CC_FOR_BUILD) -o $@ $<

Bug#914629: owncloud-client: in gome3 password is managed by kwallet instead of gnome-keyring, hence autostart fails

[Chris Becker]

Package: owncloud-client
Version: 2.4.1+dfsg-1.1
Severity: normal
Tags: patch

Dear Maintainer,

please see also
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900556

However, please note that with
owncloud-client 2.4.1+dfsg-1.1
and
libqt5keychain1 0.9.0-2
the subject bug still exists.

Probably missing dependency (see below).


* What led up to the situation?
Using owncloud client with gnome3 (wayland or x).
On first run owncloud client asks for password and tries to save it in kwallet.
One may setup kwallet with gpg or a password. However, when owncloud is started
within gnome environment, which does not start/initialize kwallet but gnome-
keyring, one has to enter the kwallet password, everytime.


* What exactly did you do that was ineffective?
Password management of owncloud client is based on qtkeychain.
I tried to deinstall/remove kwallet and its components (to force owncloud to
use gnome-keyring). However, this just caused an error message regarding
password storage/retrieval.


* What exactly did you do that was effective?
As outlined in above linked bug, owncloud client requires gnome-keyring and
additionally libgnome-keyring0 and libgnome-keyring-common in order to use
gnome-keyring.

Because libgnome-keyring0 and libgnome-keyring-common were not available for
buster, I installed these packages from sid. This solved the problem, i.e. the
password for owncloud is now stored by gnome-keyring, so one has to enter the
password only once during first run/setup.


* What outcome do you expect?
Add dependency libgnome-keyring0 and libgnome-keyring-common to owncloud client
package and add libgnome-keyring0 and libgnome-keyring-common packages to
buster repository.


Best,
Chris




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

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

Versions of packages owncloud-client depends on:
ii  libc6 2.27-8
ii  libgcc1   1:8.2.0-10
ii  libowncloudsync0  2.4.1+dfsg-1.1
ii  libqt5core5a  5.11.2+dfsg-7
ii  libqt5dbus5   5.11.2+dfsg-7
ii  libqt5gui55.11.2+dfsg-7
ii  libqt5keychain1   0.9.0-2
ii  libqt5network55.11.2+dfsg-7
ii  libqt5sql5-sqlite 5.11.2+dfsg-7
ii  libqt5webkit5 5.212.0~alpha2-17+b1
ii  libqt5widgets55.11.2+dfsg-7
ii  libqt5xml55.11.2+dfsg-7
ii  libstdc++68.2.0-10
ii  owncloud-client-l10n  2.4.1+dfsg-1.1

Versions of packages owncloud-client recommends:
ii  owncloud-client-doc  2.4.1+dfsg-1.1

owncloud-client suggests no packages.

-- no debconf information

Bug#913732: audacity: Cannot select PulseAudio and Audacity is not shown in pavucontrol

[luca]

Package: audacity
Version: 2.2.2-1+b1
Followup-For: Bug #913732

libasound2-plugins 1.1.7-3 is installed



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

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

Versions of packages audacity depends on:
ii  audacity-data   2.2.2-1
ii  libasound2  1.1.7-1
ii  libavcodec587:4.0.3-1
ii  libavformat58   7:4.0.3-1
ii  libavutil56 7:4.0.3-1
ii  libc6   2.27-8
ii  libexpat1   2.2.6-1
ii  libflac++6v51.3.2-3
ii  libflac81.3.2-3
ii  libgcc1 1:8.2.0-10
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-6
ii  libglib2.0-02.58.1-2
ii  libgtk2.0-0 2.24.32-3
ii  libid3tag0  0.15.1b-13
ii  liblilv-0-0 0.24.2~dfsg0-2
ii  libmad0 0.15.1b-9
ii  libmp3lame0 3.100-2+b1
ii  libogg0 1.3.2-1+b1
ii  libportaudio2   19.6.0-1
ii  libportsmf0 0.1~svn20101010-5
ii  libsndfile1 1.0.28-4
ii  libsoundtouch1  2.0.0-1
ii  libsoxr00.1.2-3
ii  libstdc++6  8.2.0-10
ii  libsuil-0-0 0.10.0~dfsg0-1
ii  libtwolame0 0.3.13-4
ii  libvamp-hostsdk3v5  2.7.1~repack0-1
ii  libvorbis0a 1.3.6-1
ii  libvorbisenc2   1.3.6-1
ii  libvorbisfile3  1.3.6-1
ii  libwxbase3.0-0v53.0.4+dfsg-7
ii  libwxgtk3.0-0v5 3.0.4+dfsg-7

audacity recommends no packages.

Versions of packages audacity suggests:
pn  ladspa-plugin  

-- no debconf information

Bug#914628: darkstat FTCBFS: uses the host architecture compiler for build tool c-ify

[Helmut Grohne]

Source: darkstat
Version: 3.0.719-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

darkstat fails to cross build from source. The package is quite prepared
for cross building and even has a separate make variable for using a
different compiler for c-ify. It just happens that the variable "HOSTCC"
is wrongly initialized. The attached patch fixes that and makes darkstat
cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru darkstat-3.0.719/debian/changelog 
darkstat-3.0.719/debian/changelog
--- darkstat-3.0.719/debian/changelog   2016-01-24 17:15:48.0 +0100
+++ darkstat-3.0.719/debian/changelog   2018-11-25 20:38:41.0 +0100
@@ -1,3 +1,10 @@
+darkstat (3.0.719-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Supply HOSTCC to make. (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 25 Nov 2018 20:38:41 +0100
+
 darkstat (3.0.719-1) unstable; urgency=low
 
   * New upstream release
diff --minimal -Nru darkstat-3.0.719/debian/rules darkstat-3.0.719/debian/rules
--- darkstat-3.0.719/debian/rules   2014-03-23 14:28:35.0 +0100
+++ darkstat-3.0.719/debian/rules   2018-11-25 20:38:26.0 +0100
@@ -8,6 +8,8 @@
 
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/buildflags.mk
+-include /usr/share/dpkg/buildtools.mk
+CC_FOR_BUILD ?= cc
 
 configure: configure-stamp
 configure-stamp: 
@@ -22,7 +24,7 @@
 
 build-stamp: configure-stamp
dh_testdir
-   $(MAKE)
+   $(MAKE) HOSTCC=$(CC_FOR_BUILD)
touch $@
 
 clean: 

Bug#914419: debhelper mustn't set pass V to make

[Adrian Bunk]

On Sun, Nov 25, 2018 at 07:21:17PM +, Luca Boccassi wrote:
>...
> In general, I realise that not every makefile might implement
> VERBOSE/V, but I think it's the most common pattern, so I think it's
> the best chance we have to support it automagically via debhelper. If
> some package uses a different set of variables for verbosity (or none
> at all), then they'll have to use overrides, but they'd be no worse
> than now - of course unless there are more breakages, in which case we
> can revert/use a compat level. Does this sound like a plan?
>...

The problem is not about finding the correct variable for verbosity.

The problem is that Makefiles are allowed to use variables like V or 
VERBOSE for whatever purpose they want, and with whatever values they 
want.

It is not even clear that all breakages are FTBFS,
we might end up with misbuilt packages due to that.

> Kind regards,
> Luca Boccassi

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#914627: wallstreet: newsbeuter is abandoned - please use newsboat instead

[Jonas Smedegaard]

Package: wallstreet
Version: 1.14-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

newsbeuter is abandoned upstream, and Debian package now recommends its
successor, newsboat.

Please consider switching to use newsboat directly.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlv6+mkACgkQLHwxRsGg
ASHm2hAArq+nZHx+FJ/o//EMlkqbX54RzCVaa37o6M1aMTd6LCu97AtJAQzm7eSE
70OkVFdzxetNJclrdS08Mn5DdepnZpfYx5LlU+qa5Iaujs5w73GPrJF7cDCsl0kX
98iew35KqmwYuc/wNH/m51qXHW4KAcaNyp3v6l/F+ypVExEGgoazpnIIxbbZORCE
KWd009eidyaEL+6Z9w+F4FuYVmRKSddBwMamwWfhN1xoZJ/5aFWXwHGDyWD3bR1r
eCWnbgXBH1exmJytMDny6aI+rc95qGM6crfoL5BmLe3K+AfPTztEh8ap9DnMW+2i
MWWPbRtzEhOuct9lHHQQnNokz7G1F4gNlnXCTEdeo0c78tkNuo51WOcOOlydKNrr
qMX/1rA6yupgK0Ku6I6NeorZHAw9RgIbM1x9GPKyh2Li9felTiX20tt6HoOXEc2q
4bKhOUtvWW5QSaha5B04Yjt8uZaapCgyDBbtT3q+H+wjR59hR13YAWn7dtfrQZl7
TOOcgJxdId6yr6iBhLJIjhk/gAvtf7djTcjH2j5R7Ca5zFq92fgoV31PpmaQt9bD
iakPaRaXHeFyC166CwSTKVveMHsNgRclCm/FLoxdCXX1VQ/fbOJVNzubayAOessG
xcnRkR10XmQ73WvVw0fHgTeF34BV08i3O33oDLSI34ZZprxETtA=
=EXL/
-END PGP SIGNATURE-